mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Greg KH <greg@kroah.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 10:24:46 -0700	[thread overview]
Message-ID: <20030515172446.GD17496@bougret.hpl.hp.com> (raw)
In-Reply-To: <20030515071317.GB6497@kroah.com>

On Thu, May 15, 2003 at 12:13:18AM -0700, Greg KH wrote:
> On Wed, May 14, 2003 at 04:32:35PM -0700, Jean Tourrilhes wrote:
> > 	Ok, so I ask it this way : currently the kernel include some
> > drivers containing some binary firmwares blobs which are linked
> > directly into the kernel/module (including networking). Does this mean
> > that you are going to remove those driver from the kernel ASAP ? Or
> > does this mean that the rule above only apply to wireless drivers ?
> > 	Let's be logical and coherent here...
> 
> I've stated this for _years_ now, I'm very glad to take patches to move
> the firmware blobs out of the usb drivers that currently have them, and
> move it to userspace, if people send me those patches.  For all the
> whining on debian-legal about them over the _years_, no one has sent me
> such a patch.
> 
> Ok, yes, I did get the start of some patches in the early 2.4 series, I
> said I would accept them in 2.5 as it was too radical of a change to
> take during a stable kernel series (the developer agreed with me.)  They
> were never resubmitted to me during the entire 2.5 development time.
> 
> thanks,
> 
> greg k-h

	At this point, we must get something ASAP in the kernel,
otherwise the various drivers waiting for it will just implement their
own proprietary solutions and be done with it. And it doesn't need to
be perfect at this stage, as long as it can evolve in the right
direction.
	Manuel Estrada sent me a proposal for that. As it seems it's
the only one we have on the table right now, I will spend some time
looking at it and convincing other wireless driver authors to adopt
it. I hope you will help us getting that integrated and adopted.
	Thanks...

	Jean

  reply	other threads:[~2003-05-15 17:12 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 [this message]
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=20030515172446.GD17496@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=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

all inboxes | Powered by JetHome®