All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Jeff Garzik <jeff@garzik.org>, Chuck Ebbert <cebbert@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [stable] Wanted: Allow adding new device IDs during the -stable cycle
Date: Tue, 22 May 2007 18:56:40 -0400	[thread overview]
Message-ID: <20070522225640.GG22628@redhat.com> (raw)
In-Reply-To: <20070522221718.GC2302@kroah.com>

On Tue, May 22, 2007 at 03:17:18PM -0700, Greg Kroah-Hartman wrote:

 > >  > >  I haven't found a single distro that (a) makes it trivial to add PCI IDs at 
 > >  > >  install time, and then (b) ensures those PCI IDs remain persistent for each 
 > >  > >  boot.  We are not at all to the "just works" stage yet.
 > >  > 
 > >  > Well, SuSE handles this just fine, but I do notice that RHEL 5 disables
 > >  > the new_id stuff entirely, so I can see why you might get this
 > >  > impression :)
 > > 
 > > That's news to me.  I didn't even realise it was possible to disable this.
 > > Pointer?
 > 
 > Jon Masters told me this last week at FreedomHEC, so I don't have a
 > pointer to the patch that disables it, sorry.

Either there's some miscommunication, or bonghits.

(18:54:00:davej@gelk:kernel-2.6.18)$ kdiff vanilla/drivers/pci/pci-driver.c linux-2.6.18.noarch/drivers/pci/pci-driver.c 
(18:54:10:davej@gelk:kernel-2.6.18)$ 

And as there's no CONFIG option other than CONFIG_HOTPLUG (which we obviously enable)
I don't see any reason why this wouldn't be enabled in RHEL5.
(And I think mdomsch would have probably had a fit if he found out we were
 disabling it, but that's another story ;-)

 > > Theres more to this than just PCI IDs though.
 > > ac97 ID updates, usb id updates, etc, etc.
 > 
 > USB ids also can be added through sysfs :)

oh cool, I had missed that.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-05-22 22:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 18:14 [stable] Wanted: Allow adding new device IDs during the -stable cycle Chuck Ebbert
2007-05-22 18:47 ` Greg KH
2007-05-22 18:53   ` Dave Jones
2007-05-22 19:36     ` Greg KH
2007-05-22 19:04   ` Jeff Garzik
2007-05-22 19:35     ` Greg KH
2007-05-22 19:51       ` Dave Jones
2007-05-22 22:17         ` Greg KH
2007-05-22 22:56           ` Dave Jones [this message]
2007-05-23  0:06             ` Greg KH
2007-05-24  1:20           ` David Hollis
2007-05-24 20:44             ` Jeff Garzik
2007-05-22 20:24       ` Jeff Garzik
2007-05-22 22:15         ` Greg KH
2007-05-22 22:00       ` Chris Wright
2007-05-22 22:19         ` Greg KH
2007-05-22 22:47         ` Jeff Garzik
2007-05-23  0:25           ` Chris Wright
2007-05-24 10:04     ` Pavel Machek
2007-05-24 10:06       ` Jeff Garzik
2007-05-25  6:46         ` 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=20070522225640.GG22628@redhat.com \
    --to=davej@redhat.com \
    --cc=cebbert@redhat.com \
    --cc=chrisw@sous-sol.org \
    --cc=greg@kroah.com \
    --cc=jeff@garzik.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.