From: Siju Viswanath K E <siju@india.tejasnetworks.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [BULK] Re: "transmit timed out" on FCC in MPC8260 as well as MPC8247
Date: 24 Mar 2006 15:17:39 +0530 [thread overview]
Message-ID: <1143193658.22246.20.camel@Blaze> (raw)
In-Reply-To: <20060324075148.4C106353BFB@atlas.denx.de>
Hi Denk,
Thanks for the suggestion. I had a look at the source repository
at projects/linuxppc_2_4_devel.git site. Outdated code doesnt seem to be
the issue. My repository is patched upto
"Patch by Wojciech Kromer, 06 Jan 2004" and later changes are only
adding extra board support.
regards,
Siju Viswanath
On Fri, 2006-03-24 at 13:21, Wolfgang Denk wrote:
> In message <1143177651.22246.3.camel@Blaze> you wrote:
> >
> > I am using denk's linuxppc-2.4.20 . I am getting this problem of
>
> Why don't you try using a more current version of the code? 2.4.20 is
> *very* old, and *lots* of bugs and problems have been fixed since.
>
> It really does not make sense to spend effort on such old code.
>
> Best regards,
>
> Wolfgang Denk
next prev parent reply other threads:[~2006-03-24 10:07 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 ` Siju Viswanath K E [this message]
2006-03-24 11:44 ` "transmit timed out" on FCC in MPC8260 => bug corrected hubert.loewenguth
2006-03-27 4:31 ` [BULK] " Siju Viswanath K E
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=1143193658.22246.20.camel@Blaze \
--to=siju@india.tejasnetworks.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.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).