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 19:18:40 +0100 [thread overview]
Message-ID: <1159553920.13029.62.camel@localhost.localdomain> (raw)
In-Reply-To: <200609291228.38799.luke@dashjr.org>
Ar Gwe, 2006-09-29 am 12:28 -0500, ysgrifennodd Luke-Jr:
> On Thursday 28 September 2006 6:14 pm, Alan Cox wrote:
> > lspci -vvxxx would be interesting
>
Ok so the 21152 just isn't seen by Linux. Ok try this
lspci -vvxxx -H1 -M
that will try and do a hardware level scan and map
next prev parent reply other threads:[~2006-09-29 17:53 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
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 [this message]
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=1159553920.13029.62.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