From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Marc-F. LUCCA-DANIAU" Subject: Re: Elks networking Date: Sun, 22 Jan 2017 11:37:20 +0100 Message-ID: <0f8c32a2-8e5c-75b1-54db-d10a131821e5@gmail.com> References: <9d6e714d-2117-2f98-5842-8f03930edea5@jodybruchon.com> <20160531115038.07295e62@lxorguk.ukuu.orguk> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:references:cc:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=FL5vR/euw6zQLqquMhkQzLmMTXzRAGyerljdtGinxw4=; b=Z6nhh8UYlqUVNTL80BkcdLbKbaSiRPdz7XxJvAwPixh2LxS6VGYgKFwCFnRBtNShFV dqJNerh0TpUOUx/X3aAj6F0zKVtu1wLAlcOL5u3B1TFodpk+B6Tnmc7kxRUShFsB0h7W G9D2chZq3mp5D9j+oHtTiGJDI+lbetUlDmd5mjy8/x+L4HKsl5c3JNfyjKFGZpVEft3s gOghnXJx3jOiAifU5BBDO6CXvk63tG+slB9ul2W0r+7ZLd4eyxO2nzuha3uzJpeY6sru tMB5VzW2bB4vE+nd8LpI+AOhfWR2M+WdckcrJNy9spbw4WDKtslCQ1ajMvuo5EOghH+8 dvvw== In-Reply-To: <20160531115038.07295e62@lxorguk.ukuu.orguk> Sender: linux-8086-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: Cc: ELKS Not forgotten, and now tracked by: https://github.com/mfld-fr/elks/issues/1 MFLD Le 31/05/2016 =E0 12:50, Alan a =E9crit : >> I am also interested in such NE2000 driver, because the ETH chip on my >> SBC is an Asix AX88796-L, and according to its datasheet, it claims >> "register level compatibility with NE2000". > The best place to start are the DOS packet drivers which are GPL but in > 8086 asm. Unlike the rather convoluted SMP aware IRQ driven Linux > drivers they implement IRQ based receive notification and blocking > transmit in a tiny driver, which is the kind of model needed for a low > end CPU and something like ELKS. > > As a chip it is pretty easy to drive although it is best to debug on an > emulator until it works as the real NE2000 has a very antisocial > attitude to incorrect I/O accesses (it hangs the machine solid). > > On top of that you need an implementation of ARP and then the TCP/IP > stack. > > Alan >