From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
David Miller <davem@davemloft.net>,
Manfred Rudigier <Manfred.Rudigier@omicron.at>
Subject: Re: [PATCH] gianfar: Revive the driver for eTSEC devices (disable timestamping)
Date: Thu, 10 Jun 2010 14:41:32 +0400 [thread overview]
Message-ID: <20100610104132.GA16174@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20100610102226.GA10653@riccoc20.at.omicron.at>
On Thu, Jun 10, 2010 at 12:22:26PM +0200, Richard Cochran wrote:
[...]
> > U-Boot 1.1.6 (Oct 9 2007 - 20:42:39) MPC83XX
> ...
> > CPU: MPC8313E, Rev: 10 at 333.333 MHz
>
> We have a newer CPU revision:
>
> U-Boot 1.3.0 (Dec 23 2008 - 13:38:14) MPC83XX
> CPU: e300c3, MPC8313E, Rev: 21 at 333.333 MHz, CSB: 166 MHz
>
> Perhaps a bug was fixed between revision 10 and 21...
>
> You mentioned having trouble on the MPC8568EMDS. Was it the same
> problem?
Yep, the symptomps were exactly the same, it didn't want to get
the DHCP answer, while I saw the DHCP requests on the host side.
But I don't know if disabling the timestamping fixes 8568, maybe
there is some additional problem with it, no idea as I don't have
8568 board in my hands any longer. I can try any proposed fixes
as soon as I get it back though.
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
prev parent reply other threads:[~2010-06-10 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 19:32 [PATCH] gianfar: Revive the driver for eTSEC devices (disable timestamping) Anton Vorontsov
2010-06-09 19:32 ` Anton Vorontsov
2010-06-09 23:27 ` David Miller
2010-06-10 6:29 ` Richard Cochran
2010-06-10 6:29 ` Richard Cochran
2010-06-10 9:31 ` Anton Vorontsov
2010-06-10 9:31 ` Anton Vorontsov
2010-06-10 10:22 ` Richard Cochran
2010-06-10 10:22 ` Richard Cochran
2010-06-10 10:41 ` Anton Vorontsov [this message]
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=20100610104132.GA16174@oksana.dev.rtsoft.ru \
--to=cbouatmailru@gmail.com \
--cc=Manfred.Rudigier@omicron.at \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.