mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>, Jeff Garzik <jgarzik@pobox.com>
Cc: David Gibson <hermes@gibson.dropbear.id.au>,
	Benjamin Reed <breed@almaden.ibm.com>,
	Javier Achirica <achirica@ttd.net>,
	Jouni Malinen <jkmaline@cc.hut.fi>
Subject: Re: 2.6 must-fix list, v3
Date: Wed, 14 May 2003 14:12:22 -0700	[thread overview]
Message-ID: <20030514211222.GA10453@bougret.hpl.hp.com> (raw)

Andrew Morton wrote :
> 
> Quite a lot of changes here.  Mostly additions, but some things have been
> crossed off.
> 
> Also at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/must-fix

	I don't like making todo list for other people, because it's
up to them to decide, but here is my wishlist for 2.6.X in term of
Wireless stuff.
	I hope those concerned will react and send you their real todo
list.

	o get latest orinoco changes from David. Linus seems timely in
picking David's changes, so I'm not worried about this one.

	o get the latest airo.c fixes from CVS. This will hopefully
fix problems people have reported on the LKML.

	o get HostAP driver in the kernel. No consolidation of the
802.11 management across driver can happen until this one is in (which
is probably 2.7.X material). I think Jouni is mostly ready but didn't
find time for it.

	o get more wireless drivers into the kernel. The most
"integrable" drivers at this point seem the NWN driver, Pavel's
Spectrum driver and the Atmel driver.

	o The last two drivers mentioned above are held up by firmware
issues (see flamewar on LKML a few days ago). So maybe fixing those
firmware issues should be a requirement for 2.6.X, because we can
expect more wireless devices to need firmware upload at startup coming
to market.
	As this firmware business seems to me not a wireless specific
issue (see for example drivers/scsi/qlogicfc_asm.c or
drivers/atm/atmsar11.data), I would prefer a generic solution to that
problem, either saying it's OK to put firmware in the kernel (with
proper licensing) or providing working technical solutions.
	My personal position is that I don't want to hold wireless
drivers in higher standard than other drivers in the kernel, and I
don't want to leave those drivers in the black hole where they
currently are.

	Have fun...

	Jean

             reply	other threads:[~2003-05-14 20:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 21:12 Jean Tourrilhes [this message]
2003-05-14 22:06 ` airo and firmware upload (was Re: 2.6 must-fix list, v3) Jeff Garzik
2003-05-14 23:32   ` Jean Tourrilhes
2003-05-14 23:38     ` Andrew Morton
2003-05-15  1:04       ` David Gibson
2003-05-16  7:27         ` Manuel Estrada Sainz
2003-05-14 23:43     ` Dave Jones
2003-05-14 23:53       ` Jeff Garzik
2003-05-15  0:59         ` Jouni Malinen
2003-05-15  2:20           ` Jean Tourrilhes
2003-05-15  6:16             ` James Morris
2003-05-15  1:02         ` Jean Tourrilhes
2003-05-15  4:21         ` CryptoAPI and WEP/stream ciphers (was: airo and firmware upload) Jouni Malinen
2003-05-15  6:04           ` James Morris
2003-05-15  0:55       ` airo and firmware upload (was Re: 2.6 must-fix list, v3) Jean Tourrilhes
2003-05-15  7:13     ` Greg KH
2003-05-15 17:24       ` Jean Tourrilhes
2003-05-15 17:46         ` Greg KH
2003-05-15 19:55           ` Jean Tourrilhes
2003-05-15 20:10             ` Greg KH
2003-05-17 16:58 ` 2.6 must-fix list, v3 Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 10:27 Andrew Morton
2003-05-14 10:27 ` Andrew Morton
2003-05-14 10:28 ` Jens Axboe
2003-05-14 16:41 ` Tom Rini
2003-05-14 16:57 ` Greg KH
2003-05-14 17:10 ` Matt Mackall
2003-05-14 17:44   ` Andrew Morton

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=20030514211222.GA10453@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=achirica@ttd.net \
    --cc=akpm@digeo.com \
    --cc=breed@almaden.ibm.com \
    --cc=hermes@gibson.dropbear.id.au \
    --cc=jgarzik@pobox.com \
    --cc=jkmaline@cc.hut.fi \
    --cc=jt@hpl.hp.com \
    --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 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®