From: Francois Romieu <romieu@cogenit.fr>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
henrique@cyclades.com
Subject: Re: 2.4 + generic HDLC update? Any ideas?
Date: Thu, 19 Sep 2002 21:17:38 +0200 [thread overview]
Message-ID: <20020919211738.A12722@fafner.intra.cogenit.fr> (raw)
In-Reply-To: <m3r8fqm7ez.fsf@defiant.pm.waw.pl>; from khc@pm.waw.pl on Thu, Sep 19, 2002 at 03:32:36PM +0200
Krzysztof Halasa <khc@pm.waw.pl> :
[...]
> - 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?
dscc4 maintainer:
I use a code marrying the core 2.4.x dscc4 with a 2.5.x hdlc to test 2.5.x
dscc4. Thus no real extra load. Hdlc glue in current 2.4.x dscc4 does its
job but I wouldn't recommend it as a model for the newer generation.
dscc4 users:
Migration from specific scctool.c + sethdlc to single sethdlc. Definitely
a simpler life.
If users damn me, I'll surely meet someone from Infineon in hell to discuss
dscc4 :o)
vendors:
- dscc4 not included in rh 2.4 last time I looked at it (I labelled it
'EXPERIMENTAL');
- 2.4.18 mdk kills it using Krzysztof's post-2.4-didn't-make-2.5 (!) hdlc;
- don't know what the others do.
Imho dscc4 doesn't need to be taken too much in consideration regarding
2.4.x hdlc stack change.
--
Ueimor
next prev parent reply other threads:[~2002-09-19 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 13:32 Krzysztof Halasa
2002-09-19 19:17 ` Francois Romieu [this message]
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=20020919211738.A12722@fafner.intra.cogenit.fr \
--to=romieu@cogenit.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=henrique@cyclades.com \
--cc=jgarzik@mandrakesoft.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®