[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=kTQpTkCF6-DE+LdNLH_aki9bD9NPF0L2qRr=Q@mail.gmail.com>
Date: Thu, 7 Oct 2010 15:49:05 -0500
From: Mario Limonciello <superm1@...ntu.com>
To: Matthew Garrett <mjg59@...f.ucam.org>
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 08:35, Matthew Garrett <mjg59@...f.ucam.org> wrote:
>
> On Thu, Oct 07, 2010 at 08:30:57AM -0500, Mario Limonciello wrote:
>
> > In this specific scenario that Ken Yu submitted this patch for, the
> > firmware will return the same return codes for the SMI's as a functional
> > machine will. Machines affected by this will fail to recover after rfkill
> > is toggled twice. The symptom will be that the soft block always appears
> > set to the same setting with continued keypresses.
> > During the prototype phase this option is quite useful to help debug the
> > problem it addresses.
>
> Is the kernel able to unblock it under those circumstances?
Manually running rfkill unblock will unblock it in this broken
firmware scenario in question.
--
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