From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Luke-Jr <luke@dashjr.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI bridge missing
Date: Fri, 29 Sep 2006 00:14:15 +0100 [thread overview]
Message-ID: <1159485255.13029.7.camel@localhost.localdomain> (raw)
In-Reply-To: <200609281624.16082.luke@dashjr.org>
Ar Iau, 2006-09-28 am 16:24 -0500, ysgrifennodd Luke-Jr:
> However, this bridge is completely ignored and unseen by Linux. It does not
> show up in lspci or dmesg (as far as I can tell) at all. The daughterboard is
> plugged in, and the PCI cards on it are powered.
lspci -vvxxx would be interesting
Linux on PC assumes the BIOS did the work needed so if there is some
custom "enabler" driver in the Windows for it that might explain
problems.
next prev parent reply other threads:[~2006-09-28 22:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 21:24 PCI bridge missing Luke-Jr
2006-09-28 21:39 ` Mark Knecht
2006-09-28 21:52 ` Mark Felder
2006-09-28 23:14 ` Alan Cox [this message]
2006-09-29 0:17 ` Luke-Jr
2006-09-29 11:36 ` Mark Brown
2006-09-29 17:28 ` Luke-Jr
2006-09-29 18:18 ` Alan Cox
2006-09-29 17:57 ` Luke-Jr
2006-09-29 18:53 ` Luke-Jr
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=1159485255.13029.7.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@dashjr.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