From: Florian Fainelli <florian@openwrt.org>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Hacking PCI-ids to allow Atheros NIC into Lenovo laptop.
Date: Mon, 12 Mar 2012 23:13:41 +0100 [thread overview]
Message-ID: <4F5E7515.8060801@openwrt.org> (raw)
In-Reply-To: <4F5E7031.4000401@candelatech.com>
Hi,
Le 12/03/2012 22:52, Ben Greear a écrit :
> 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?
The only viable hack that I have came to with my laptop (Lenovo X61) is
to have a patched BIOS. Fortunately the web is full of such modified
BIOSes enabling various features (SATA2 vs SATA1, Wireless NICs
whitelisting ...)
--
Florian
next prev parent reply other threads:[~2012-03-12 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 21:52 Hacking PCI-ids to allow Atheros NIC into Lenovo laptop Ben Greear
2012-03-12 22:13 ` Florian Fainelli [this message]
2012-03-12 22:16 ` Julian Calaby
2012-03-12 22:32 ` Christian Lamparter
2012-03-12 22:36 ` Ben Greear
2012-03-13 0:53 ` Luis R. Rodriguez
2012-03-13 0:57 ` Matthew Garrett
2012-03-13 1:11 ` Luis R. Rodriguez
2012-03-21 5:01 ` Adrian Chadd
2012-03-21 11:15 ` Matthew Garrett
2012-03-13 0:58 ` Ben Greear
2012-03-13 3:13 ` Julian Calaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F5E7515.8060801@openwrt.org \
--to=florian@openwrt.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).