On Mon, Mar 12, 2012 at 3:36 PM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > On 03/12/2012 03:32 PM, Christian Lamparter wrote: >> >> On Monday, March 12, 2012 10:52:49 PM Ben Greear wrote: >>> >>> It seems we bought a Lenovo laptop that has a BIOS lock where it will >>> only >>> support certain wifi NICs based on the pci-id. It came with an Intel >>> NIC, so at least that ID must work... >>> >>> One way around this might be to over-write the pci-id of an Atheros NIC >>> in it's non-volatile storage to make it look like an Intel, at least >>> until >>> the kernel boots. >>> >>> Then maybe add some sort of ugly code to force the Atheros driver >>> to manage this Intel pci-id (and probably disable the same pci-id in >>> the Intel driver). >>> >>> Has anyone tried doing anything like this? Any suggestions for a cleaner >>> way to go about this? >> >> Been down this road before. First an old X41 Tablet and more recently a HP >> dv6 laptop. >> >> I think if you manage to reprogram the cards pciids then you are more than >> halfway there. Because theoretically, you can get away with adding the >> fake >> intel id to ath9k through sysfs: >> >> echo "8086 dead"> /sys/bus/pci/drivers/ath9k/new_id >> [for more information, take a look at the new_id sysfs interface] >> (Of course, you'll have to get rid of the intel driver first) >> >> That said, in both cases I risked flashing a modded bios. So whitelists >> are >> no longer a problem. >> >> PS: AFAIK [Maybe some QCA dev can verify this]: all AR9300+ have OTP ROMs >> for the pciids. So you might want to get an older AR9280 for your laptop. > > > > We're hoping to use the WPEA-127N. I might as well chime in to explain the long story. If we figure out a way to ensure we can always get the antenna gain uniformly across different systems and expose this to the OS I suspect we can convince some OEMs this would be a better solution than simply restricting devices. I looked a the newer generation of dmidecode (its not called DMI, its something else now) thingy but saw no one yet had added 802.11 specifically, perhaps it may be good to consider it in the future for this. that's as far as I got from trying to kill this concern. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
