On Thu, Oct 07, 2010 at 10:50:28PM +0100, Matthew Garrett wrote: > On Thu, Oct 07, 2010 at 02:46:28PM -0700, Dmitry Torokhov wrote: > > On Thu, Oct 07, 2010 at 10:37:54PM +0100, Matthew Garrett wrote: > > > Dell laptop driver is reasonable. All we need is a list of hardware, and > > > I'd really hope that Dell know which BIOS versions contain this code! > > > > > > > Unfortunately this kind of crap tends to flow from one BIOS version to > > another.. How many DMI entries do we know about so far? Did Dell issue > > firmware updates correcting the issue so new boxes will not exhibit the > > problem? > > Pushing this out to userspace doesn't help. If it's sufficiently > prevelant that it's impossible to have a comprehensive list, then a > module option makes it too easy for people to just post the fix on a > forum somewhere and never actually get it upstream. > Forcing users patching the kernel reduces chances that it will be fixed at all. Also there is load of patches that never make into distributions and even less in mainline. Or if they make it it takes looong time... so I do not think it is a valid argument here. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
