From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Lehmann, Hans (Ritter Elektronik)" <hans.lehmann@ritter-elektronik.de>
Cc: Tim Yamin <plasm@roo.me.uk>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH]: [MPC5200] Add ATA DMA support
Date: Sat, 20 Dec 2008 00:18:26 -0700 [thread overview]
Message-ID: <fa686aa40812192318m397aab91kcd1684fe80b52d67@mail.gmail.com> (raw)
In-Reply-To: <633A55242A59C7488FAAF5A6850929984B814A@SRVEXC01.sts.saurer.vpn>
On Tue, Nov 25, 2008 at 7:45 AM, Lehmann, Hans (Ritter Elektronik)
<hans.lehmann@ritter-elektronik.de> wrote:
> Tim, Grant,
>
> just an info.
>
> Very often the Bestcomm-FEC crashed without any error logs if I initiate a transaction over FEC and save the file to disk (I rememeber I have read something like that). A restart of FEC don't work.
> But no I figured out, if I connect to the other ethernet port of our board (natsemi) the FEC will awake to life again, if I initiate a new transaction over natsemi. This seems a little oddly to me.
Hans, what ATA modes do you see this problem in? UDMA? MWDMA? Or
does just having the patch applied but still using PIO mode expose the
problem?
Thanks,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-12-20 7:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AclPDG6qSkF9cHawTOKR6zBfDIjvgg==>
2008-11-25 14:45 ` AW: [PATCH]: [MPC5200] Add ATA DMA support Lehmann, Hans (Ritter Elektronik)
2008-11-25 15:19 ` Matt Sealey
2008-11-25 15:35 ` AW: " Lehmann, Hans (Ritter Elektronik)
2008-12-20 7:15 ` Grant Likely
2008-12-20 7:18 ` Grant Likely [this message]
2009-01-05 9:25 ` AW: " Lehmann, Hans (Ritter Elektronik)
2009-01-05 15:31 ` Grant Likely
2009-07-09 14:24 ` Roman Fietze
2008-09-05 18:29 WITTROCK
[not found] <DD39B5C3F4963040ADC9768BE7E430CB03202F4F@is-hdq-exchange.marel.net>
[not found] ` <DD39B5C3F4963040ADC9768BE7E430CB03203863@is-hdq-exchange.marel.net>
[not found] ` <792f5f410808111319m20d6e09bi8e9782da1fdd4aab@mail.gmail.com>
[not found] ` <DD39B5C3F4963040ADC9768BE7E430CB0320387D@is-hdq-exchange.marel.net>
[not found] ` <792f5f410808111431g8fafba1n3b10468da0d165bf@mail.gmail.com>
[not found] ` <DD39B5C3F4963040ADC9768BE7E430CB03203A7B@is-hdq-exchange.marel.net>
[not found] ` <792f5f410808120643md72e679o39692c4bfa3f285e@mail.gmail.com>
[not found] ` <DD39B5C3F4963040ADC9768BE7E430CB03203A94@is-hdq-exchange.marel.net>
[not found] ` <792f5f410808120730j7b4be4f2n7a40de880178ccca@mail.gmail.com>
[not found] ` <DD39B5C3F4963040ADC9768BE7E430CB03203ADC@is-hdq-exchange.marel.net>
[not found] ` <792f5f410808120830v311e0446kc8fddfb97d0b9ea6@mail.gmail.com>
2008-08-12 17:30 ` Daniel Schnell
2008-08-13 5:57 ` Tim Yamin
2008-08-13 6:02 ` Grant Likely
2008-08-13 6:06 ` Tim Yamin
2008-08-13 6:11 ` Grant Likely
2008-08-13 9:07 ` Tim Yamin
2008-09-15 5:54 ` Grant Likely
2008-10-29 15:34 ` Matt Sealey
2008-11-11 14:04 ` Lehmann, Hans (Ritter Elektronik)
2008-11-11 14:35 ` Matt Sealey
-- strict thread matches above, loose matches on Subject: below --
2008-06-17 8:28 Tim Yamin
2008-08-06 11:58 ` Daniel Schnell
2008-08-06 12:18 ` Tim Yamin
2008-08-06 13:26 ` Daniel Schnell
2008-08-06 14:31 ` Daniel Schnell
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=fa686aa40812192318m397aab91kcd1684fe80b52d67@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=hans.lehmann@ritter-elektronik.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=plasm@roo.me.uk \
/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).