linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Christian Lamparter <chunkeey@googlemail.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 15:36:49 -0700	[thread overview]
Message-ID: <4F5E7A81.8090605@candelatech.com> (raw)
In-Reply-To: <201203122332.16325.chunkeey@googlemail.com>

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.

Thanks for all the info!

Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2012-03-12 22:36 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
2012-03-12 22:16 ` Julian Calaby
2012-03-12 22:32 ` Christian Lamparter
2012-03-12 22:36   ` Ben Greear [this message]
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=4F5E7A81.8090605@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=chunkeey@googlemail.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).