From: Siju Viswanath K E <siju@india.tejasnetworks.com>
To: "hubert.loewenguth" <hubert.loewenguth@thales-bm.com>
Cc: "Hunter, David" <David.Hunter@ipc.com>, linuxppc-embedded@ozlabs.org
Subject: Re: [BULK] Re: "transmit timed out" on FCC in MPC8260 => bug corrected
Date: 27 Mar 2006 10:01:20 +0530 [thread overview]
Message-ID: <1143433880.1476.10.camel@Blaze> (raw)
In-Reply-To: <4423DB92.5070305@thales-bm.com>
Thanks for the patch.. I have implemented the changes but since it is
not very frequent in my case, I dont know whether it works for me yet.
regards,
siju
On Fri, 2006-03-24 at 17:14, hubert.loewenguth wrote:
> Hi to the community.
>
> I'm the man who has posted numerous questions about this problem of
> fcc_enet timeout in ppc8260.
> I just want to say that the 2.6 kernel doesn't solve the problem if
> you have it on your board (I tried it, normally I have a 2.4-20 linux
> too).
> I have search for this bug during a long time, and fortunatly, I 'm
> happy to say you that finally, it is corrected since few days.
> Special thanks to "Hunter, David" for having take in consideration my
> problem, and proposing me some way of invastigations in this thread:
>
> http://ozlabs.org/pipermail/linuxppc-embedded/2006-January/021842.html
>
> In fact the solution comes from the new "MPC8260 PowerQUICC II Family
> Reference Manual" fresescale has delivered 01/19/2006.
> http://www.freescale.com/files/product/doc/MPC8260UM.pdf
next prev parent reply other threads:[~2006-03-27 4:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 5:20 "transmit timed out" on FCC in MPC8260 as well as MPC8247 Siju Viswanath K E
2006-03-24 7:51 ` Wolfgang Denk
2006-03-24 9:47 ` [BULK] " Siju Viswanath K E
2006-03-24 11:44 ` "transmit timed out" on FCC in MPC8260 => bug corrected hubert.loewenguth
2006-03-27 4:31 ` Siju Viswanath K E [this message]
2006-03-25 0:10 ` [BULK] Re: "transmit timed out" on FCC in MPC8260 as well as MPC8247 Wolfgang Denk
2006-03-27 4:34 ` Siju Viswanath K E
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=1143433880.1476.10.camel@Blaze \
--to=siju@india.tejasnetworks.com \
--cc=David.Hunter@ipc.com \
--cc=hubert.loewenguth@thales-bm.com \
--cc=linuxppc-embedded@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).