From: Solomon Peachy <solomon@linux-wlan.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "David S. Miller" <davem@rth.ninka.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] New ARPHRD types
Date: Thu, 24 Oct 2002 11:53:45 -0400 [thread overview]
Message-ID: <20021024155345.GC11876@linux-wlan.com> (raw)
In-Reply-To: <1035473936.9867.60.camel@irongate.swansea.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
On Thu, Oct 24, 2002 at 04:38:56PM +0100, Alan Cox wrote:
> On Thu, 2002-10-24 at 15:58, Solomon Peachy wrote:
> > 1) audit the use of hard_header_len in net/* and submit fixes
> We've handled variable length headers for years so that bit I do trust.
And that's exactly what I wanted to know, thanks.
Out of curiousity, how far back to you trust the code? 2.2? 2.0? I only
ask because a lot of the driver work I do is for underpowered
embedded targets running relatively ancient 2.0 kernels.
> AX.25 even has variable length headers on ARP frames 8)
Eww.
> > 2) write an 802.11 equivalent of the code in eth.c
> That may be much cleaner and easier to get right. Its also easier to
> maintain
That's what I've been planning to do all along. It will be nice not
having to convert 802.3<-->802.11 in every wireless driver.. plus the
added benefit of not having to realloc/memcpy buffers to work around
dumb DMA engines that require contiguious buffers..
- Pizza
--
Solomon Peachy solomon@linux-wlan.com
AbsoluteValue Systems http://www.linux-wlan.com
715-D North Drive +1 (321) 259-0737 (office)
Melbourne, FL 32934 +1 (321) 259-0286 (fax)
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-10-24 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 22:19 [PATCH] New ARPHRD types Solomon Peachy
2002-10-22 23:55 ` David S. Miller
2002-10-23 14:16 ` Solomon Peachy
2002-10-24 4:18 ` David S. Miller
2002-10-24 14:58 ` Solomon Peachy
2002-10-24 15:38 ` Alan Cox
2002-10-24 15:53 ` Solomon Peachy [this message]
2002-10-24 17:01 ` Alan Cox
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=20021024155345.GC11876@linux-wlan.com \
--to=solomon@linux-wlan.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@rth.ninka.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.