From: Jeff Garzik <jgarzik@pobox.com>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>,
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: airo and firmware upload (was Re: 2.6 must-fix list, v3)
Date: Wed, 14 May 2003 18:06:36 -0400 [thread overview]
Message-ID: <3EC2BDEC.6020401@pobox.com> (raw)
In-Reply-To: <20030514211222.GA10453@bougret.hpl.hp.com>
Jean Tourrilhes wrote:
> o get the latest airo.c fixes from CVS. This will hopefully
> fix problems people have reported on the LKML.
please beg Javier to split up his patch. He sends me a _huge_ patch
with tons of changes each time. If I object to one thing, we spin in
another huge-patch loop... :/
Sending me 20, 50, 100 patches to the same file is ok. Even encouraged.
> 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.
yeah, there are many requests for this one
> 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.
We need firmware upload, and, firmware _should_ be uploaded from userspace.
All someone needs to do is actually write the code for their driver to
receive firmware from userspace, and the rest is easy. A working
technical solution is obvious, it just needs interested parties to
implement.
We can upload firmware from initrd, if no boot device is available at
the time.
Jeff
next prev parent reply other threads:[~2003-05-14 21:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 21:12 2.6 must-fix list, v3 Jean Tourrilhes
2003-05-14 22:06 ` Jeff Garzik [this message]
2003-05-14 23:32 ` airo and firmware upload (was Re: 2.6 must-fix list, v3) 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
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=3EC2BDEC.6020401@pobox.com \
--to=jgarzik@pobox.com \
--cc=achirica@ttd.net \
--cc=akpm@digeo.com \
--cc=breed@almaden.ibm.com \
--cc=hermes@gibson.dropbear.id.au \
--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