From: Sharad Gupta <sharad@buckeye.ece.drexel.edu>
To: Jeff Angielski <jangiels@speakeasy.net>,
LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: System ACE MPU interface to CF card
Date: Mon, 19 Apr 2004 14:06:18 -0400 [thread overview]
Message-ID: <4084151A.4050805@buckeye.ece.drexel.edu> (raw)
In-Reply-To: <1082322389.23738.13.camel@localhost.localdomain>
Jeff Angielski wrote:
> Sounds to me like you do not have your interrupts configured properly
> between the SystemACE and the CPU or your xsa_thread is dying
> prematurely.
>
> Either way, the kernel is getting no response when it actually tries to
> access the CF thru the SystemACE.
>
>
> Jeff Angielski
> The PTR Group
I do not enable interrupts between SystemACE and the CPU. Following the
debug cycle:
xsysace_init()
->register_disk()
-->grok_partitions()
--->check_partition()
---->msdos_partition()
----->read_dev_sector()
------>read_cache_page()
------->lock_page()
-------->__lock_page()
--------->schedule()
And it never resumes after that. The code just goes to power_save mode.
Any help would be appreciated.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-19 18:06 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 [this message]
2004-04-19 18:38 ` Jeff Angielski
2004-04-19 23:07 ` more SystemACE problems Sharad Gupta
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=4084151A.4050805@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).