linux-8086.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marc-F. LUCCA-DANIAU" <mfld.fr@gmail.com>
To: ELKS <Linux-8086@Vger.Kernel.Org>
Subject: Re: Guidelines to plug NE2K driver in ELKS
Date: Tue, 14 Feb 2017 20:08:55 +0100	[thread overview]
Message-ID: <b87e688a-72cf-f7fe-0b4e-836c8ad11998@gmail.com> (raw)
In-Reply-To: <1e796b52-f460-922d-0ad3-1258049a0453@gmail.com>

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
>
>


      parent reply	other threads:[~2017-02-14 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05 11:12 Guidelines to plug NE2K driver in ELKS Marc-F. LUCCA-DANIAU
2017-02-05 19:47 ` Georg Potthast
2017-02-14 19:08 ` Marc-F. LUCCA-DANIAU [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b87e688a-72cf-f7fe-0b4e-836c8ad11998@gmail.com \
    --to=mfld.fr@gmail.com \
    --cc=Linux-8086@Vger.Kernel.Org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).