Re: Guidelines to plug NE2K driver in ELKS

Hello all,

An alpha version of the NE2K driver is now available in Jody's master 
branch.

The strong limitation is the missing management of the NE2K ring 
overflow, that has been delayed to a next integration step. So this 
driver should not be used in a heavily loaded network for the moment.

We are now working on KTCP to add the Ethernet path, an ARP transponder 
and a basic IP routing.

Thanks to Georg for his support on that sub-project.

MFLD


Le 05/02/2017 à 12:12, Marc-F. LUCCA-DANIAU a écrit :
> Hello all,
>
> As suggested by Alan and Jody, I delivered a standalone code to drive 
> the NE2K in /elks/arch/i86/drivers/net as a first step, and I intend 
> to connect it to the low end of KTCP (in parallel of SLIP) as a second 
> step.
>
> But because KTCP needs a "selectable" device to operate, and because I 
> am not at ease with the select / poll implementation in ELKS, could I 
> have some guidelines to integrate the current standalone code ?
>
> Thanks,
>
> MFLD
>
>