On Thu, Oct 7, 2010 at 16:49, Matthew Garrett <mjg59@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxx > 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@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
