From: Jordan Crouse <jordan.crouse@amd.com>
To: David Brigada <brigad@rpi.edu>
Cc: jim.cromie@gmail.com, LKML <linux-kernel@vger.kernel.org>,
linux-geode@lists.infradead.org
Subject: Re: PCI-ISA Bridge not operating
Date: Fri, 11 Jul 2008 14:52:53 -0600 [thread overview]
Message-ID: <20080711205253.GA30670@cosmic.amd.com> (raw)
In-Reply-To: <4877C325.7070903@rpi.edu>
On 11/07/08 16:31 -0400, David Brigada wrote:
<snip>
> >> That *is* puzzling. When I do lspci, the entry for the IT8888G does not
> >> appear. I don't have much experience with PCI internals. Would that be
> >> because there is no driver for it in the kernel, or is there something
> >> more insidious afoot?
> >
> > Well - the first step would be to get a dmesg output. if the kernel
> > is doing anything to the device at all, the dmesg will show it.
>
> The dmesg output doesn't have anything related to the device. I have
> attached my dmesg output for completeness. Ignore the last four lines,
> that's my testing. The PCI ID of the IT8888G is 1283:8888.
Okay - interesting. Can you try lcpci with direct hardware access?
By default lspci only lists those devices that Linux found and
enumerated. Direct hardware access does the CF8/CFC dance. If
we find it that way, then its a hunt to figure out why Linux silently
discarded it. Also, check the I/O ports you are trying to access in
/proc/ioports to see if anybody has claimed them.
Jordan
prev parent reply other threads:[~2008-07-11 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 14:58 PCI-ISA Bridge not operating David Brigada
2008-07-11 16:48 ` Jordan Crouse
2008-07-11 16:55 ` David Brigada
2008-07-11 18:58 ` David Brigada
2008-07-11 19:10 ` Jordan Crouse
2008-07-11 20:14 ` David Brigada
2008-07-11 20:29 ` Jordan Crouse
2008-07-11 20:31 ` David Brigada
2008-07-11 20:52 ` Jordan Crouse [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=20080711205253.GA30670@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=brigad@rpi.edu \
--cc=jim.cromie@gmail.com \
--cc=linux-geode@lists.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.