linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: Roman Fietze <roman.fietze@telemotive.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: MPC5200B XLB Configuration Issues, FEC RFIFO Events, ATA Crashes
Date: Thu, 04 Feb 2010 20:35:12 +0100	[thread overview]
Message-ID: <1265312112.2256.1@antares> (raw)
In-Reply-To: <201002030716.31280.roman.fietze@telemotive.de> (from roman.fietze@telemotive.de on Wed Feb  3 07:16:31 2010)

[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]

Hi Roman:

Am 03.02.10 07:16 schrieb(en) Roman Fietze:
> Sorry for the delay ... your mail got stuck in a Notes "spam filter".

Never mind.  I didn't know yet that I'm *such* a nasty guy... ;-)

> Are you using MWDMA2 with the compact flash cards? What is the load on the different (DMA) channels? ATA reads or writes?

Actually, I forgot that I have to explicitly enable libata dma on the 5200b, due to the known silicon bugs...  I will repeat my tests with the proper configuration, stay tuned.

>> ... a signal processor attached to the localbus, using bestcomm and the fifo for the bulk transfer
> 
> Are you using an own driver, or are you using Grant's SCLPC+SDMA driver? BD task?

Basically Grant's driver, but with a slightly modified variant of the gen_bd task.  The signal processor is a LE, and I managed to insert the LE/BE conversion into the bestcomm task (see also <http://patchwork.ozlabs.org/patch/35038/>).  Unfortunately, there is no good documentation of the engine; I would like to also shift crc calculation into bestcomm, which seems to be possible in principle, but I never got it running.

> The best thing is to run very ugly tests with very high load for at least 24h.

Thanks again for this tip!  I hope I manage to run a test over the weekend.  Throughput onto the cf cards is not critical for me (so I could live with pio there), but I'm a little afraid I might also see similar effects with fec and the signal processor (in particular, the latter *is* critical).

Thanks, Albrecht.

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2010-02-04 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1264191106.2224.0-2010-02-02-19-31-49@antares>
2010-02-03  6:16 ` MPC5200B XLB Configuration Issues, FEC RFIFO Events, ATA Crashes Roman Fietze
2010-02-04 19:35   ` Albrecht Dreß [this message]
2010-02-19 18:04     ` Albrecht Dreß
2009-12-09 14:29 Roman Fietze
2009-12-09 14:57 ` Wolfram Sang
2009-12-10  6:09   ` Roman Fietze
2009-12-16 11:37   ` Roman Fietze
2009-12-18  8:24     ` Wolfgang Grandegger
2009-12-18  9:07       ` Roman Fietze
2010-01-22 20:11     ` Albrecht Dreß

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=1265312112.2256.1@antares \
    --to=albrecht.dress@arcor.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=roman.fietze@telemotive.de \
    /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).