From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Solomon Peachy <solomon@linux-wlan.com>
Cc: "David S. Miller" <davem@rth.ninka.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] New ARPHRD types
Date: 24 Oct 2002 18:01:14 +0100 [thread overview]
Message-ID: <1035478874.9867.65.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20021024155345.GC11876@linux-wlan.com>
On Thu, 2002-10-24 at 16:53, Solomon Peachy wrote:
> 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.
I trust it back to 2.2, Im not sure about 2.0 but its probably ok.
> > > 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..
Remember that you want to land IP frame headers on a 4 byte boundary if
possible. Thats sometimes a conflicting constraint alas
prev parent reply other threads:[~2002-10-24 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 22:19 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
2002-10-24 17:01 ` Alan Cox [this message]
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=1035478874.9867.65.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davem@rth.ninka.net \
--cc=linux-kernel@vger.kernel.org \
--cc=solomon@linux-wlan.com \
/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®