From: "Marc-F. Lucca-Daniau" <mfld.fr@gmail.com>
To: Paul Osmialowski <pawelo@king.net.pl>,
Derek Johansen <djohanse678@gmail.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Obsolete documentation?
Date: Sun, 16 Feb 2020 18:05:36 +0100 [thread overview]
Message-ID: <85e27a46-034f-f927-9169-e633c18909e8@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.21.1.2002161200100.29710@localhost.localdomain>
Hello Derek and Paul,
ELKS is indeed still SLIP capable :
https://github.com/elks-org/elks/issues/304
One has just to change the command line of 'ktcp' to remove Ethernet and
put back SLIP.
Documentation is quite outdated. Georges made an effort to document
Ethernet and some other things while debugging networking features, but
there are still many legacy documents that need to be reorderer and updated.
Thanks,
MFLD
Le 16/02/2020 à 12:08, Paul Osmialowski a écrit :
> So what happened to SLIP support in ELKS? 8-bit ISA ethernet cards
> (with RJ-45 connector) are very rare (I have only one of them, work nicely
> under FreeDOS and in theory it should be supported by ELKS's ne2k driver,
> but it isn't). Within my one more XT machine to play with ELKS, serial
> port is the only means of external communication. PPP/IP or SLIP is
> something ELKS should definitely have IMHO.
>
> Cheers,
> Paul
>
> On Sat, 15 Feb 2020, Derek Johansen wrote:
>
>> Does elks/Documentation/text/networking_guide.txt make
>> elks/Documentation/text/networking.txt obsolete? The latter in
>> Section 2 says ELKS only supports SLIP connections. I don't think
>> this is still true?
>>
next prev parent reply other threads:[~2020-02-16 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 4:51 Obsolete documentation? Derek Johansen
2020-02-16 11:08 ` Paul Osmialowski
2020-02-16 17:05 ` Marc-F. Lucca-Daniau [this message]
2020-02-16 18:10 ` Georg Potthast
2020-02-16 18:37 ` Paul Osmialowski
2020-02-16 21:17 ` Georg Potthast
2020-02-16 23:26 ` Paul Osmialowski
[not found] ` <CALgV52jgt1U0MNAxEy6jsDykdkMHGGopBxT4o6itW4UzWrXx5A@mail.gmail.com>
2020-02-17 13:10 ` Paul Osmialowski
2020-02-17 14:47 ` Georg Potthast 2
2020-02-17 15:07 ` Paul Osmialowski
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=85e27a46-034f-f927-9169-e633c18909e8@gmail.com \
--to=mfld.fr@gmail.com \
--cc=djohanse678@gmail.com \
--cc=linux-8086@vger.kernel.org \
--cc=pawelo@king.net.pl \
/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