linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Masters <jonmasters@gmail.com>
To: Peter Ryser <peter.ryser@xilinx.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: uboot and ppc405
Date: Tue, 26 Oct 2004 16:48:06 +0100	[thread overview]
Message-ID: <35fb2e5904102608487acce066@mail.gmail.com> (raw)
In-Reply-To: <417DE312.6070405@xilinx.com>

On Mon, 25 Oct 2004 22:39:30 -0700, Peter Ryser <peter.ryser@xilinx.com> wrote:

jcm>> btw Peter, I've been moaning about the weird interrupt behaviour of
jcm>> the SysACE on e.g. the Memec board for some time (see archives for
jcm>> various other people's experiences too) - and I've spoken to several
jcm>> folks at Xilinx without getting very far. If there's a fundamental
jcm>> problem then it probably makes sense for us to help get it fixed.

> Hmm, I'm not aware of any interrupt problems with System ACE CF.

It issues an extra interrupt after each sector write on our hardware,
in what seems to be a reasonably reproducible but not entirely
predictable fashion. This is after the interrupt we expect to get on
sector completion - it causes the Monta driver to go belly up because
it has no handling to check for interrupt on QUEUE_EMPTY or similar
error conditions.

I have every confidence that it works on the ML300, just not on other
boards, including both the Memec board and our in house prototypes.
Since it's not a major issue right now to have good performance from
the SysACE (just a reliable driver), I've created the patch I posted
previously to use polled IO instead.

> There is now a MVL preview kit for the Memec board. You might want to
> try it out and see whether the problems you observe persist.

Is this the one which doesn't actually use the SystemACE for a filesystem?

> Looking at the postings back in April I can only say that I never saw
> any similar problems.

Others have done so. I'll check with the hardware guys and see if I
can't send you a simple hardware case that falls over at some point -
I'm slightly constrained to release hardware designs and so on until
after this thing is ready to ship.

> The implementation of System ACE CF functionality in U-Boot is written
> for polled operation. In that case Stephen Williams wrote the actual
> driver and we decided not to publish our own driver but reuse his.

So it probably doesn't use the Xilinx HAL, that can only be a good thing :-)

Jon.

  reply	other threads:[~2004-10-26 15:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-25 10:51 uboot and ppc405 grave
2004-10-25 13:57 ` Jon Masters
2004-10-25 16:35 ` Peter Ryser
2004-10-25 21:07   ` Jon Masters
2004-10-26  5:39     ` Peter Ryser
2004-10-26 15:48       ` Jon Masters [this message]
2004-10-26 16:55         ` Peter Ryser
2004-10-26 20:59       ` Stephen Williams
2004-10-25 18:12 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-10-25 18:40 Shamile Khan
2006-06-21  6:29 Zhang Ke

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=35fb2e5904102608487acce066@mail.gmail.com \
    --to=jonmasters@gmail.com \
    --cc=jonathan@jonmasters.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=peter.ryser@xilinx.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).