Re: [stable] Wanted: Allow adding new device IDs during the -stable cycle



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 :)

So, because of that, I don't really see a need to be adding new device
ids to the -stable tree.

Maybe you are just not seeing all the developers that keep bringing this
up??

This is the second time it has occurred that I know of.

Really, it is just silly to think that one-line PCI IDs patches will cause
any harm at all, and it should be self-evident that there is clear potential
to HELP Linux users. That's why we're all here, right?

I'm not disagreeing that it will help a set of users, or that it will
cause any harm at all. It's just currently outside the scope for what
we defined -stable as, and it will slightly increase the workload that
Chris and I have in keeping up with these patches.

So, if there is an overwhelming majority of people that strongly feel
that this is a good thing, fine, we can try it out.

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.)

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: DTrace vs. Strace (was Re: The sorry state of SUNW)
    ... > kernel.org, they add tons of so called (features) hense a fork, so it is ... This is same reason why most big ISV's only ... "Andrew's vision, as expressed at the summit, is that the mainline kernel ... specific distros for support reasons, and because no two distros ever ship ...
    (comp.unix.solaris)
  • Re: reiser4 plugins
    ... >>There's been sloppy code in the kernel before. ... this had all of the PCI ids and the names and ... Reiser does some stuff that VFS already does! ... the best way to "prove" it would be to package it with the kernel. ...
    (Linux-Kernel)
  • Re: Damn you, FEDEX! or Nikon D40 lost in Springfield, MO blackhole.
    ... the 2 mp Mavica he had been using with a Nikon D40. ... After shopping around, he got me to order one for him. ... The shipper had it insured, but from what I have read it could take weeks to sort this crap out. ... You may get your insurance from FedEx and a couple weeks later they find it and deliver it. ...
    (alt.photography)
  • Re: dapper upgrade no sound
    ... I maybe have recompiled my kernel trying to get a newer ... snd-emu10k1's emu10k1_main.c contains the pci ids. ... user-space pci id file is for user-space programs ... Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org ...
    (Ubuntu)
  • Re: How to check if kernel sources are installed on a system?
    ... Mandrake and CentOS - how about other RPM based distros? ... I'd really like to see a distro-agnostic way to retrieve the kernel ... What's the reason for distros to disable /proc/config.gz? ...
    (Linux-Kernel)