From mboxrd@z Thu Jan  1 00:00:00 1970
From: Georg Potthast 2 <nospam@georgpotthast.de>
Subject: Re: Question on ELKS networking maturity
Date: Mon, 20 Feb 2017 14:41:52 +0100 (CET)
Message-ID: <1011882660.176981.1487598112712@com4.strato.de>
References: <CACpuWUnAtCnD2oTHG3CLPEAQMNa0m0gU+HNFLVoyJr7N4s+Nuw@mail.gmail.com>
 <3941d5b3-8234-0c6f-eb43-4c6cc37de722@jodybruchon.com>
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Return-path: <linux-8086-owner@vger.kernel.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1487598475;
        l=1968; s=domk; d=georgpotthast.de;
        h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject:
        References:In-Reply-To:To:From:Date;
        bh=lK/xraM2301CllpbQzyC127YKuPVWu0gpBImjFZvJHM=;
        b=AEbBGaj1zhHIFHHAUyfW0hgm+Jfd0Kb7yk24rvvFziF00INMUyYcKsxD2ZzFvpNJVU
        LSeTgLl6RMnIFDD2cqtGTAW7Rfmp4Eqb1v8CrmJFAVbUWMOmNfS5853ol/IIgQgHfX3s
        QU1GJ82EEVQB/doOTVhx+Ho3tbLE9EC4UJCds=
In-Reply-To: <3941d5b3-8234-0c6f-eb43-4c6cc37de722@jodybruchon.com>
Sender: linux-8086-owner@vger.kernel.org
List-ID: <linux-8086.vger.kernel.org>
Content-Type: text/plain; charset="utf-8"
To: ELKS <Linux-8086@vger.kernel.org>, Jody Bruchon <jody@jodybruchon.com>

I have already done some work on getting ktcp to work with Marc-Fran=C3=A7o=
is' NE2K driver and am pretty sure to get it functional, however, it requir=
es some time. Uncovering bugs I consider not unusual in this process.

Since I am interested to continue with this I suggest not to put this to th=
e side. It would be a big step forward for ELKS to get ethernet working. Yo=
u could add drivers for different network cards in the future.

Georg

> Jody Bruchon <jody@jodybruchon.com> hat am 20. Februar 2017 um 13:57 gesc=
hrieben:
>=20
>=20
> On 2017-02-20 6:49 AM, Marc-Fran=C3=A7ois LUCCA-DANIAU wrote:
> > I made the assumption at the beginning that ELKS was reasonably mature
> > on networking, but obviously I was wrong, and have to revise my
> > development plan.
> ELKS networking was never remotely mature. It was written to use SLIP=20
> and as far as I can tell it was only ever minimally functional. Given=20
> the show-stopping bugs fixed in the past three years, it makes sense=20
> that networking would be put to the side. When something as simple as=20
> logging in after logging out freezes the entire system, that's a much=20
> bigger priority than networking support. There has also been a general=20
> lack of working network hardware available for would-be network devs to=
=20
> test on. I once got a NE2K-compliant 8-bit ISA card but then the 8086 PC=
=20
> it was going to go into blew up.
>=20
> At one time I'm sure the network programs were working, but it would be=
=20
> safe to assume they are working at "proof-of-concept" quality only.
>=20
> Assume everything on the network side was test code cobbled together and=
=20
> abandoned; that's basically how it has worked out.
>=20
> -Jody
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html