From: Christoph Hellwig <hch@infradead.org>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: Pavel Machek <pavel@suse.cz>,
Christoph Hellwig <hch@infradead.org>,
Jeff Chua <jeffchua@silk.corp.fedex.com>,
Tomas Szepe <szepe@pinerecords.com>,
netdev@oss.sgi.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ipw2100 wireless driver
Date: Wed, 11 Aug 2004 11:44:37 +0100 [thread overview]
Message-ID: <20040811114437.A27439@infradead.org> (raw)
In-Reply-To: <4119F203.1070009@linux.intel.com>; from jketreno@linux.intel.com on Wed, Aug 11, 2004 at 05:16:35AM -0500
On Wed, Aug 11, 2004 at 05:16:35AM -0500, James Ketrenos wrote:
> We're currently working to clean up ipw2100 and ieee80211 code for submission to
> netdev for discussion and hopefully inclusion in the future. The ieee80211 code
> is still being heavily developed, but its usable. If anyone wants to help out,
> or if folks feel its ready as-is to get pulled into wireless-2.6, let me know.
Maybe we should switch to your ieee802.11 for a generic wireless stack then
instead of the original hostap code. At least it seems more actively
maintained right now and supports two drivers already.
Btw, I've looked at the ipw2100 and have to concerns regarding the firmware,
a) yo'ure not using the proper firmware loader but some horrible
handcrafted code using sys_open/sys_read & co that's not namespace
safe at all
b) the firmware has an extremly complicated and hard to comply with license,
I'm not sure we want a driver that can't work without a so strangely
licensed blob in the kernel. Can you talk to intel lawyers and put it on
simple redristribution and binary modification for allowed for all purposes
license please?
> Thanks,
> James
>
>
>
---end quoted text---
next prev parent reply other threads:[~2004-08-11 10:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 11:41 ipw2100 wireless driver Pavel Machek
2004-07-14 11:48 ` Jeff Chua
2004-07-14 11:55 ` Pavel Machek
2004-08-09 20:15 ` Tomas Szepe
2004-08-10 5:02 ` Jeff Chua
2004-08-10 6:55 ` Christoph Hellwig
2004-08-10 10:16 ` Pavel Machek
2004-08-10 10:34 ` Christoph Hellwig
2004-08-11 12:17 ` Pavel Machek
2004-08-11 17:54 ` Jeff Garzik
2004-08-11 20:27 ` Pavel Machek
2004-08-11 22:01 ` Jeff Garzik
2004-08-11 10:16 ` James Ketrenos
2004-08-11 10:44 ` Christoph Hellwig [this message]
2004-08-11 10:53 ` Wichert Akkerman
2004-08-11 10:59 ` Christoph Hellwig
2004-08-11 16:21 ` James Ketrenos
2004-08-11 16:30 ` Stephen Hemminger
2004-08-11 16:33 ` Tomas Szepe
2004-08-11 16:51 ` Christoph Hellwig
2004-08-11 17:02 ` Tomas Szepe
2004-08-11 17:11 ` Christoph Hellwig
2004-08-11 17:22 ` Tomas Szepe
2004-08-11 18:55 ` John Stoffel
2004-08-11 23:55 ` Jeff Chua
2004-08-12 3:47 ` Luis R. Rodriguez
2004-08-11 17:51 ` Jeff Garzik
2004-07-14 12:30 ` Tomas Szepe
2004-07-14 12:27 ` Pavel Machek
2004-07-14 13:15 ` Vojtech Pavlik
2004-07-14 13:42 ` Pavel Machek
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=20040811114437.A27439@infradead.org \
--to=hch@infradead.org \
--cc=jeffchua@silk.corp.fedex.com \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pavel@suse.cz \
--cc=szepe@pinerecords.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;
as well as URLs for NNTP newsgroup(s).