From: Arnon Kaufman <arnon.kaufman@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: [MPC5200] problem running FEC and ATA
Date: Sun, 16 Dec 2007 15:24:34 +0200 [thread overview]
Message-ID: <47652712.60006@gmail.com> (raw)
does any one succeed running a functional FEC and ATA (pata) running
together ?
If so which version (2.6.x...) and with which architecture (powerpc or
ppc)?.
The machine I'm working on based on v2.6.21-rc6 and another one based on
v2.6.24-rc1, both configured with ARCH=powerpc.
my FEC introduce itself as: "PHY: f0003000:01", and not as f0003000:00,
I've fix it by adjusting the dts file, is that ok?
I'm getting the following, when pinging the machine:
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4401 ttl=64 time=0.249 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4402 ttl=64 time=0.285 ms
wrong data byte #52 should be 0x34 but was 0xa
#8 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20 21 22 23 24 25 26 27
#40 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 a 35 36 37
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4403 ttl=64 time=0.233 ms
wrong data byte #20 should be 0x14 but was 0x0
#8 8 9 a b c d e f 10 11 12 13 0 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20 21 22 23 24 25 26 27
#40 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4404 ttl=64 time=0.232 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4405 ttl=64 time=0.237 ms
-----
The offsets and values of the corrupted data are constant (can it be the
microcode?)
when enabling the PATA driver and doing some Compact flash access
operation the amount of packets corruption is getting worse.
does the pata driver needs to wait on the TIP indicator? cause it
doesn't seems to do it.
next reply other threads:[~2007-12-16 13:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 13:24 Arnon Kaufman [this message]
2007-12-16 15:44 ` [MPC5200] problem running FEC and ATA Robert Schwebel
2007-12-16 17:28 ` Arnon Kaufman
2007-12-16 17:46 ` Robert Schwebel
2007-12-18 10:41 ` Juergen Beisert
-- strict thread matches above, loose matches on Subject: below --
2008-01-21 7:10 Mehlan, Markus (Ritter Elektronik)
2008-01-21 8:57 ` Juergen Beisert
2008-01-21 13:01 ` Mehlan, Markus (Ritter Elektronik)
2008-01-21 16:28 ` Juergen Beisert
2008-01-23 0:20 ` Wolfgang Denk
2008-01-23 6:53 ` Mehlan, Markus (Ritter Elektronik)
2008-01-23 22:58 ` Wolfgang Denk
2008-01-23 9:03 ` Juergen Beisert
2008-01-23 23:01 ` Wolfgang Denk
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=47652712.60006@gmail.com \
--to=arnon.kaufman@gmail.com \
--cc=linuxppc-dev@ozlabs.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).