public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: airo and firmware upload (was Re: 2.6 must-fix list, v3)
Date: Thu, 15 May 2003 13:10:27 -0700	[thread overview]
Message-ID: <20030515201027.GA10502@kroah.com> (raw)
In-Reply-To: <20030515195516.GA18244@bougret.hpl.hp.com>

On Thu, May 15, 2003 at 12:55:16PM -0700, Jean Tourrilhes wrote:
> On Thu, May 15, 2003 at 10:46:48AM -0700, Greg KH wrote:
> > On Thu, May 15, 2003 at 10:24:46AM -0700, Jean Tourrilhes wrote:
> > > 	Manuel Estrada sent me a proposal for that.
> > 
> > I provided some feedback to him that I think will make his proposal work
> > for almost everyone.  Hopefully he has the time to implement it :)
> > 
> > thanks,
> > 
> > greg k-h
> 
> 	I read that thread and I don't agree with some of your
> unrealistic requirements.

If you think that having a common firmware interface for any kind of
device for 2.5 is unrealistic, then this is going to be a very short
discussion.

<2.4 is here for a long time ramble snipped>

> 	So, my question for you is :
> 	o how do you plan to make it work with 2.4.X.

In short, I don't care how you do it for 2.4.x.  Do it like the
bluetooth usb drivers do it, that's a good place to start with.  Or do
it like the usb drivers that do firmware download from userspace, that's
also a good way to do this for 2.4.  So for 2.4 you have a lot of
different options on how to do this, _because_ we don't have the
goodness of sysfs and the driver model there.

For 2.5 do it the way I proposed, that way _all_ devices in the kernel
have a single way to have firmware downloaded to them, which will result
in peace and harmony for many years to come, during which we will gaze
thoughtfully back on the anarchistic ways of 2.4 and laugh at how
foolish we were then.

thanks,

greg k-h

  reply	other threads:[~2003-05-15 19:55 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 ` 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 [this message]
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=20030515201027.GA10502@kroah.com \
    --to=greg@kroah.com \
    --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