All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@linutronix.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: What's needed for a PCIe card to be recognized?
Date: Sun, 17 Feb 2008 19:48:36 +0100	[thread overview]
Message-ID: <20080217194836.3a8a3b97@bluebox.local> (raw)
In-Reply-To: <20080217072927.4b6c5964@laptopd505.fenrus.org>

Am Sun, 17 Feb 2008 07:29:27 -0800
schrieb Arjan van de Ven <arjan@infradead.org>:

> On Sun, 17 Feb 2008 13:37:53 +0100
> "Hans J. Koch" <hjk@linutronix.de> wrote:
> > > Of course there's no driver for the wlan, but that's a different
> > > story ;)
> > 
> > I replaced that unsupported Atheros 5007 card with an ipw3945, so I
> > haven't got that problem.
> 
> oh but then you have a MUCH bigger problem ;(
> The bios of that animal is hardcoded to the 5007 (or at least
> Atheros). If you stick your own card in, for FCC reasons, the bios
> refuses the card. (this is not unique to Asus; all notebooks do this
> for cards they're not certified with. This apparently  has to do with
> the antenna being part of the laptop, and thus part of the radio in
> FCC speak)

Someone claims he's done it:

http://beta.ivancover.com/wiki/index.php/Eee_PC_Internal_Upgrades#Wifi

Hans

      parent reply	other threads:[~2008-02-17 18:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 21:59 What's needed for a PCIe card to be recognized? Hans-Jürgen Koch
2008-02-16 22:39 ` Arjan van de Ven
2008-02-17  0:54   ` Hans-Jürgen Koch
2008-02-17  2:29     ` Arjan van de Ven
2008-02-17 12:37       ` Hans J. Koch
2008-02-17 15:29         ` Arjan van de Ven
2008-02-17 16:47           ` Hans J. Koch
2008-02-17 22:05             ` Mark Lord
2008-02-17 22:09               ` Mark Lord
2008-02-17 23:03                 ` Hans-Jürgen Koch
2008-02-17 18:48           ` Hans J. Koch [this message]

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=20080217194836.3a8a3b97@bluebox.local \
    --to=hjk@linutronix.de \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.