[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=bj3T5hcX9r3j5kyEQkNb7PAZK948kcrx4R8tC@mail.gmail.com>
Date: Thu, 7 Oct 2010 15:53:37 -0500
From: Mario Limonciello <superm1@...ntu.com>
To: Matthew Garrett <mjg@...hat.com>
Cc: Keng-Yu Lin <keng-yu.lin@...onical.com>, len.brown@...el.com,
alan-jenkins@...fmail.co.uk, platform-driver-x86@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dell-laptop: Add hwswitch_only module parameter
Hi Matthew:
On Thu, Oct 7, 2010 at 15:50, Matthew Garrett <mjg@...hat.com> wrote:
> On Thu, Oct 07, 2010 at 03:49:05PM -0500, Mario Limonciello wrote:
>> Hi Matthew:
>> > Is the kernel able to unblock it under those circumstances?
>>
>> Manually running rfkill unblock will unblock it in this broken
>> firmware scenario in question.
>
> So the issue is in the firmware's response to the keystroke? Ok. I'd
> rather have a DMI list of the broken machines than a module parameter.
Yes the issue is the firmware's response to the keystroke. The
intention here is to individual submit machines in future patches as
they're discovered. The parameter's primary purpose is to assist in
building the list. If someone reports a bug with these symptoms, they
can add the parameter to their kernel command line, and report if it
helps them. If it helps, their machine can be added to the DMI table.
--
Mario Limonciello
superm1@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists