linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Henrique Oliveira <henrique2.gobbi@cyclades.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Kevin Curtis <kevin.curtis@farsite.co.uk>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Why is generic hldc beig ignored?   RE:Linux 2.4.22-pre4
Date: 11 Jul 2003 10:12:41 +0100	[thread overview]
Message-ID: <1057914760.8028.27.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <003101c34712$a9b8f480$602fa8c0@henrique>

On Iau, 2003-07-10 at 19:39, Henrique Oliveira wrote:
> Hi,
> The patch for the generic HDLC layer was included on the kernel 2.4.21. Thus
> this layer is already on the main tree (unless, of course, someone has
> removed it, I havent checked 2.4.22 yet). This layer provides data link
> protocol (ppp, hdlc, raw-hdlc, x25, frame-relay, cisco-hdlc) for the kernel.
> It's mainly used by synchronous cards drivers (Cyclades, Moxa, SDL, Farsite,
> etc, etc, etc).

2.4.21 has much older code than the current stuff (which has been in -ac
for a while). As I understand it the new hdlc layer needs newer tools ?


  reply	other threads:[~2003-07-11  9:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10 15:38 Why is generic hldc beig ignored? RE:Linux 2.4.22-pre4 Kevin Curtis
2003-07-10 17:11 ` Marcelo Tosatti
2003-07-10 18:39   ` Henrique Oliveira
2003-07-11  9:12     ` Alan Cox [this message]
2003-07-11 16:55       ` Henrique Oliveira
2003-07-11 17:18         ` Marcelo Tosatti
2003-07-11 17:27           ` Jeff Garzik
2003-07-11 18:05             ` Krzysztof Halasa
2003-07-11 18:00       ` Krzysztof Halasa
2003-07-11  8:30 Kevin Curtis
     [not found] <20030711212551.A25528@electric-eye.fr.zoreil.com>
2003-07-14 11:36 ` Frantisek Rysánek
2003-07-14 12:27   ` Francois Romieu
2003-07-14 13:16   ` 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=1057914760.8028.27.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=henrique2.gobbi@cyclades.com \
    --cc=kevin.curtis@farsite.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).