From: Krzysztof Halasa <khc@pm.waw.pl>
To: <linux-kernel@vger.kernel.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Generic HDLC and hw drivers update for 2.4
Date: 20 Jan 2003 01:40:24 +0100 [thread overview]
Message-ID: <m3lm1gbqmf.fsf@defiant.pm.waw.pl> (raw)
Hi,
I've put the generic HDLC update at:
ftp://ftp.pm.waw.pl/pub/linux/hdlc/current/hdlc-2.4.21pre3d.patch.gz
Please apply to linux-2.4.21pre and linux-2.4.21-pre-ac.
Thank you.
(A patch for 2.5 kernel is in the works).
Changes summary: 1.12 - January, 2003
* Added Ethernet device emulation for raw HDLC. VLAN and bridging compatible,
tested with RAD ChipBridge (ChipBridge doesn't work with full size VLAN
frames, though).
* Added Ethernet device emulation for bridged Ethernet frames on Frame-Relay.
* fixed subtle transmit bug in c101.c which could lead to transmitter hangs
and duplicated frames with SCA HD64570 working in 8-bit mode.
* no more "protocol 0008 is buggy" while using tcpdump, at last.
* Frame-Relay DCE (network) side now sorts DLCI list in PVC FULL STATUS.
Some FR DTE had problems with unsorted list.
* Small changes to LMI logic with Frame-Relay.
* tcpdump etc. should see all frames going through physical and logical
interfaces correctly (exception: internal syncppp.c processing).
* You can now query PVC device using sethdlc.
* You can continue to use older sethdlc.c tool, but for new functionality
you need sethdlc-1.12.c.
>From a hardware driver point of view:
A hardware driver has to call hdlc_type_trans(skb, dev) instead of
using ETH_P_HDLC to set skb->protocol before netif_rx(skb):
skb->dev = hdlc_to_dev (&port->hdlc);
- skb->protocol = htons (ETH_P_HDLC);
+ skb->protocol = hdlc_type_trans(skb, skb->dev);
netif_rx (skb);
This change corrects problems with tcpdump/etc not seeing all inbound
frames correctly.
--
Krzysztof Halasa
Network Administrator
next reply other threads:[~2003-01-20 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 0:40 Krzysztof Halasa [this message]
2003-02-12 15:57 Kevin Curtis
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=m3lm1gbqmf.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=alan@lxorguk.ukuu.org.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
all inboxes | Powered by JetHome®