From: Krzysztof Halasa <khc@pm.waw.pl>
To: <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Francois Romieu <romieu@cogenit.fr>, <henrique@cyclades.com>
Subject: 2.4 + generic HDLC update? Any ideas?
Date: 19 Sep 2002 15:32:36 +0200 [thread overview]
Message-ID: <m3r8fqm7ez.fsf@defiant.pm.waw.pl> (raw)
Hi,
The question is probably aimed mainly at people maintaining 2.4 Linux
and/or networking, but I'd like to see an opinion of other users/
developers as well.
What do you think about updating the 2.4 generic HDLC layer to the
newer 2.5 code?
Facts:
- it would break all sethdlc compatibility, users would be required to
get 2.5 sethdlc.c and recompile it. There are even cosmetic sethdlc
syntax changes and additions (sethdlc is a configuration tool).
- it would make it possible to support new boards like Cyclades PC300
(not only this one).
- drivers which are in current 2.4 include Moxa C101 and RISCom/N2,
which are older ISA cards. Most of their users currently use 2.5
generic HDLC (a patch) with 2.4 kernels anyway.
- the other driver affected is DSCC4, but I know exactly nothing about
it (a 2.5 version of it is, of course, available). What do you think,
Francois?
The update, if any, wouldn't take place yet. I would expect it to happen
after some remaining questions regarding 2.5 code are resolved - chances
are there will be small changes to 2.5 generic HDLC interface first.
--
Krzysztof Halasa
Network Administrator
next reply other threads:[~2002-09-19 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 13:32 Krzysztof Halasa [this message]
2002-09-19 19:17 ` Francois Romieu
2002-09-20 15:18 Kevin Curtis
2002-09-20 14:35 ` henrique
2002-09-20 16:40 ` Krzysztof Halasa
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=m3r8fqm7ez.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=henrique@cyclades.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@cogenit.fr \
/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
all inboxes | Powered by JetHome®