From: Sharad Gupta <sharad@buckeye.ece.drexel.edu>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: System ACE MPU interface to CF card
Date: Thu, 15 Apr 2004 15:05:27 -0400 [thread overview]
Message-ID: <407EDCF7.2020009@buckeye.ece.drexel.edu> (raw)
In-Reply-To: <25757-52278@sneakemail.com>
Stephen Williams wrote:
> The attached patch demonstrates how I enabled the SYSACE driver
> for my (JSE) board. I'm not so sure I'm happy with it, because
> each board will have to do something similar. I'm thinking that
> the CONFIG_XILINX_SYSACE define should lose its dependence on
> CONFIG_XILINX_OCP, but I'm not clear on the best way to account
> for this in the xilinx_ocp/Makefile.
Thanks Stephen,
Your patch helped me a lot in compiling and configuring my kernel. Just
on a side note, have you been able to talk to compact flash (mount fs on
it, fsck it ?) through system ace ?
My kernel hangs while doing partition check on the drive. All I ever see is
Partition check:
xsysacea:
(then nothing happens)
I am using SanDisk's 128MB CF card and system ace is configured in the
byte mode. Any pointers as to why it is not going ahead will be highly
appreciated.
Thanks
Sharad.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-15 19:05 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 [this message]
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 ` 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=407EDCF7.2020009@buckeye.ece.drexel.edu \
--to=sharad@buckeye.ece.drexel.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.