On Tue, May 22, 2007 at 12:35:38PM -0700, Greg Kroah-Hartman wrote:
> On Tue, May 22, 2007 at 03:04:08PM -0400, Jeff Garzik wrote:
> > Greg KH wrote:
> > > What's wrong with the current sysfs way of adding new device ids without
> > > touching the kernel? Devices described above was the very reason we
> > > added that functionality, so users would not have to constantly update
> > > their kernel. The distros provide userspace tools that enable these ids
> > > to be added and at boot time, everything "just works" properly.
> >
> > 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?
> I'm just trying to point out that the new_id sysfs stuff is there
> explicitly for this very reason, as people were demanding that (Dell
> being the major company behind it.)
Theres more to this than just PCI IDs though.
ac97 ID updates, usb id updates, etc, etc.
We have many different forms of what are fundamentally, the same thing.
Dave
--
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
