On Thu, Oct 7, 2010 at 16:50, Matthew Garrett <mjg59@xxxxxxxxxxxxx> 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. > > -- > Matthew Garrett | mjg59@xxxxxxxxxxxxx > Making it more difficult to enable the alternative functionality wouldn't necessarily make the list any more comprehensive, it just raises the bar for users who want to try to help. If users report the bugs to their distros, distros will help to forward them upstream. You can't expect to fix a social problem here just by making it more difficult to fix the original problem at hand for individuals. -- Mario Limonciello superm1@xxxxxxxxx -- 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
