From: Sharad Gupta <sharad@buckeye.ece.drexel.edu>
To: Jeff Angielski <jangiels@speakeasy.net>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: more SystemACE problems
Date: Mon, 19 Apr 2004 19:07:18 -0400 [thread overview]
Message-ID: <40845BA6.6010706@buckeye.ece.drexel.edu> (raw)
In-Reply-To: <1082399912.8706.11.camel@localhost.localdomain>
Jeff Angielski wrote:
> On Mon, 2004-04-19 at 14:06, Sharad Gupta wrote:
> I would suggest instrumenting the code in the driver that actually
> handles the block request from the kernel. For instance, is the request
> being received by the xsa_thread? Is the driver actually making a
> request to the device. And most importantly and where I suspect your
> problem lies, is the xsa_complete_request() ever getting run?
>
> Jeff Angielski
> The PTR Group
Hi Jeff,
Thanks very much for your help. I have enabled the interrupts for
SystemACE now. And in fact xsa_complete_request() was never called. I
fixed that in xsa_thread.
I was wondering if you could send in your modifications to the
xilinx_systemace/* files so that I can know better where else the
potential problems may lie.
Do I need to have a device entry for xsystemacea (0/1) in my /dev
directory ? If yes, then what should it be like ?
Thanks
Sharad.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-04-19 23:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 21:21 System ACE MPU interface to CF card Sharad Gupta
2004-04-07 23:09 ` Stephen Williams
2004-04-08 0:04 ` Tom Rini
[not found] ` <407ADCFE.8080302@buckeye.ece.drexel.edu>
2004-04-13 17:54 ` Stephen Williams
2004-04-15 19:05 ` Sharad Gupta
2004-04-15 20:14 ` Stephen Williams
2004-04-18 0:28 ` Jon Masters
2004-04-20 1:02 ` Jon Masters
2004-04-18 21:06 ` Jeff Angielski
2004-04-19 18:06 ` Sharad Gupta
2004-04-19 18:38 ` Jeff Angielski
2004-04-19 23:07 ` Sharad Gupta [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=40845BA6.6010706@buckeye.ece.drexel.edu \
--to=sharad@buckeye.ece.drexel.edu \
--cc=jangiels@speakeasy.net \
--cc=linuxppc-embedded@lists.linuxppc.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).