From: "Hans-Jürgen 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 01:54:53 +0100 [thread overview]
Message-ID: <20080217015453.2a4e4142@dilbert.local> (raw)
In-Reply-To: <20080216143946.6d532a41@laptopd505.fenrus.org>
Am Sat, 16 Feb 2008 14:39:46 -0800
schrieb Arjan van de Ven <arjan@infradead.org>:
> On Sat, 16 Feb 2008 22:59:32 +0100
> Hans-Jürgen Koch <hjk@linutronix.de> wrote:
>
> > I'm playing around with a vanilla 2.6.25-rc1, adding patches to make
> > it work on an Asus EeePC. That one has the problem that its Mini
> > PCIe WLAN module doesn't show up in lspci. That brought up a few
> > questions that I couldn't answer yet:
> >
> > How can they "hide" a PCIe card?
> > What could be their motive to do that?
> > How can I make it appear?
>
>
> go to the bios, enable the wireless card.
>
> that did it for me ;)
It didn't for me. I tried all combinations (booting with/without WLAN
enabled, enabling WLAN through /proc with/without pciehp loaded and so
on). What kernel did you use, and which patches did you apply?
Yes, I want to make it work, but I'd really like to understand what's
going on there and what's behind it.
Thanks,
Hans
next prev parent reply other threads:[~2008-02-17 0:55 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 [this message]
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
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=20080217015453.2a4e4142@dilbert.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox