From: Tachwali <ytachwali@signalogic.com>
To: linuxppc-embedded@ozlabs.org
Subject: lspci vs scanpci
Date: Fri, 22 Aug 2008 15:20:01 -0700 (PDT) [thread overview]
Message-ID: <19116424.post@talk.nabble.com> (raw)
Hello folks,
I have a general question regarding lspci and scanpci. Upon porting a kernel
2.6.24 to a ppc platform, the kernel seems to be working fine. However, upon
scaning for PCI devices, we have got reasonable results upon running lspci
however scanpci, we are not getting the same results, and scanpci results
looks not right (such as INT_LINE=0xFF) in the PCI devices detected.
Should I be worried about some hardware problem if lspci is working and
scanpci is not? Any advise?
--
View this message in context: http://www.nabble.com/lspci-vs-scanpci-tp19116424p19116424.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
reply other threads:[~2008-08-22 22:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19116424.post@talk.nabble.com \
--to=ytachwali@signalogic.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).