From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: Mark Lord <lkml@rtr.ca>
Cc: Arjan van de Ven <arjan@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: What's needed for a PCIe card to be recognized?
Date: Mon, 18 Feb 2008 00:03:12 +0100 [thread overview]
Message-ID: <20080218000312.0b38efd5@dilbert.local> (raw)
In-Reply-To: <47B8B0A3.2070005@rtr.ca>
Am Sun, 17 Feb 2008 17:09:39 -0500
schrieb Mark Lord <lkml@rtr.ca>:
> Mark Lord wrote:
> > Hans J. Koch wrote:
> ..
> >> Really? Unbelievable what these guys do to make my live harder...
> >> So, they might use some undocumented GPIO to turn the power on, and
> ...
>
> GPIO lines are not usually very difficult to trace,
> and programming them is pretty easy, too ...
I know :-) I'll do that as soon as I've got some spare time (very rare
ATM).
>
> If I had an EeePC here, I'd do that for you (and everyone else),
> but I'm waiting for a lower-power (fanless) unit to be introduced
> first.
Admirable. I didn't have that patience ;-)
>
> >> refuse that if they don't find the original card? Looks like I
> >> can't have WLAN on an EeePC (I won't run a tainted kernel). Stupid
> >> thing to sell a PC with Linux preinstalled but with hardware not
> >> supported in mainline.
> > ..
> >
> > Try it again with 2.6.25-rc2 and this module option:
> >
> > options pciehp pciehp_force=1
> >
> > Just a thin hope, really, but it might work.
I'll give it a try.
Thanks for your hints,
Hans
next prev parent reply other threads:[~2008-02-17 23:03 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 [this message]
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=20080218000312.0b38efd5@dilbert.local \
--to=hjk@linutronix.de \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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