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 12:55:16 -0700	[thread overview]
Message-ID: <20030515195516.GA18244@bougret.hpl.hp.com> (raw)
In-Reply-To: <20030515174648.GA9549@kroah.com>

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.
	As long as kernel 2.6.X is not standard in most major
distributions (including Debian), whatever scheme we decide on must be
easy to implement on 2.4.X. Let be realistic : all of us still
continue to update 2.4.X on a regular basis. Those 3 drivers are ready
today (one of them has been waiting on this issue for already 6
months), and I want them in 2.4.X not long after they go in 2.5.X.
	Therefore, unless you plan to port sysfs to 2.4.X real soon,
the scheme can't depend exclusively on sysfs. I would even say,
because sysfs change on a weekly basis, it might even be wise to take
a two phase approach, with sysfs used only in the second phase and
based on the feedback and the results from the first phase (I
personally don't believe we will get it perfect at the first try). The
hotplug facility is flexible enough to migrate to sysfs smoothly.
	I'm pragmatic : I prefer to have something imperfect now
rather than something perfect later. I think Manuel's solution is a
good stepping stone to where we want to go. If you make it too
difficult, this will never happen (and each driver will use a
proprietary solution or be kept in a black hole).

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

	Have fun...

	Jean

  reply	other threads:[~2003-05-15 19:42 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 [this message]
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=20030515195516.GA18244@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®