From: Tachwali <ytachwali@signalogic.com>
To: linux-kernel@vger.kernel.org
Subject: PCI device problem ... how can I debug it guys?
Date: Sun, 24 Aug 2008 10:04:27 -0700 (PDT) [thread overview]
Message-ID: <19132349.post@talk.nabble.com> (raw)
I am experiencing a problem with PCI device on local PCI bus governed by the
MV64662 chip in our board. The board runs Gentoo with kernel 2.6.9. The PCI
device is trying to master PCI bus and access the SDRAM behind the MV64662
chip.
The general description of the problem is that the driver at initialization
writes a pattern "0xfeedface" to specific allocated memory locations in
SDRAM behind the MV64662 chip and upon an interrupt, the interrupt handler
checks these memory locations to see whether they have beed edited to check
the validity of the interrupt (not a spurious one). In my case, the driver
*always* finds the memory is not edited (the driver reads back the same
pattern 0xfeedface) and quit the interrupt handling. Although, an interrupt
is actually have been issued by the PCI device.
I tried to access the SDRAM using a basic read/write memory software to
check the PCI device driver activity on the SDRAM. I used the physical
address used by the driver to access the SDRAM but it seems that the driver
does not write to that physical address. Some IO mapping is going on. or it
could be some kernel configs. I am not sure :(
Have you guys encountered a similar problem? I would appreciate any help or
guidance on this matter or suggesting any areas to look at. Thank you all
--
View this message in context: http://www.nabble.com/PCI-device-problem-...-how-can-I-debug-it-guys--tp19132349p19132349.html
Sent from the linux-kernel mailing list archive at Nabble.com.
reply other threads:[~2008-08-24 17:04 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=19132349.post@talk.nabble.com \
--to=ytachwali@signalogic.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox