[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinSgzLtNk1nrVejX0zafxzE0mG-p6rHD8dnhJBP@mail.gmail.com>
Date: Thu, 7 Oct 2010 16:52:51 -0500
From: Mario Limonciello <superm1@...ntu.com>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
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
On Thu, Oct 7, 2010 at 16:49, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> On Thu, Oct 07, 2010 at 04:45:22PM -0500, Mario Limonciello wrote:
>> Matthew:
>>
>> On Thu, Oct 7, 2010 at 16:42, Matthew Garrett <mjg59@...f.ucam.org> wrote:
>> > I don't understand this. You know which code is broken - surely you're
>> > able to determine which products shipped with BIOSes derived from the
>> > broken code?
>>
>> Not all product's BIOS are developed in-house. The ones that are, yes
>> it quite possible to identify. Matter of fact, this issue tends to
>> not exist on the in-house developed BIOS codebase.
>
> Ok, so let's approach this differently. What is it that results in this
> issue not affecting Windows?
>
> --
> Matthew Garrett | mjg59@...f.ucam.org
>
Depending on the third-party vendor that worked on the BIOS, they may
have an additional method for modifying the wireless and another tool
in addition to the standard one used on a majority of the machines.
That method is not necessarily documented.
--
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