From: Scott Wood <scottwood@freescale.com>
To: Mike Timmons <mike_timmons@trimble.com>
Cc: Mark Gibson <Mark_Gibson@trimble.com>, linuxppc-embedded@ozlabs.org
Subject: Re: porting pci driverfrom arch=ppc on kernel 2.6.16 to arch=powerpc on 2.6.24...
Date: Tue, 06 May 2008 14:41:57 -0500 [thread overview]
Message-ID: <4820B485.1020506@freescale.com> (raw)
In-Reply-To: <161B3BAD77161449A144FF054231C3D6020D6B08@uss-am-xch-01.am.trimblecorp.net>
Mike Timmons wrote:
> If I'm not supposed to read the interrupt using config_read, should I
> also not be writing to the host register on the coral P to clear the
> interrupt?
>
> Should I instead be using some PCI helper functions?
No, clearing interrupts is device-specific.
Have you verified that the device does not think it's generating an
interrupt during the interrupt storm? Do other PCI cards work?
-Scott
prev parent reply other threads:[~2008-05-06 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 17:39 porting pci driverfrom arch=ppc on kernel 2.6.16 to arch=powerpc on 2.6.24 Mike Timmons
2008-05-06 18:12 ` Scott Wood
2008-05-06 19:27 ` Mike Timmons
2008-05-06 19:36 ` Mike Timmons
2008-05-06 19:41 ` Scott Wood [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=4820B485.1020506@freescale.com \
--to=scottwood@freescale.com \
--cc=Mark_Gibson@trimble.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mike_timmons@trimble.com \
/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).