From: Mit Matelske <mit@sweeet.net>
To: linuxppc-dev@ozlabs.org
Subject: Re: FEC driver not working after upgrade
Date: Thu, 2 Aug 2007 16:32:30 -0700 (PDT) [thread overview]
Message-ID: <11975001.post@talk.nabble.com> (raw)
In-Reply-To: <20070802205107.C069F352659@atlas.denx.de>
wd wrote:
>
> In message <11952546.post@talk.nabble.com> you wrote:
>>
>> I upgraded from an old 2.4.25 kernel to the latest Denx snapshot and
>> cannot
> ...
>> I am running a 5200B. Thanks for any help.
>
> Do you really have the latest snapshot, i. e. top of tree from the git
> repository?
>
Yes sir. I have the 2007-7-10 snapshot.
Someone posted what I assume to be a similar problem back in March:
http://www.nabble.com/Problems-with-PHY-on-STK5200-tf3326321.html#a9247789
but there was no solution. Thanks for any and all help.
Mit Matelske
--
View this message in context: http://www.nabble.com/FEC-driver-not-working-after-upgrade-tf4202285.html#a11975001
Sent from the linuxppc-dev mailing list archive at Nabble.com.
prev parent reply other threads:[~2007-08-02 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 19:47 FEC driver not working after upgrade Mit Matelske
2007-08-02 20:51 ` Wolfgang Denk
2007-08-02 23:32 ` Mit Matelske [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=11975001.post@talk.nabble.com \
--to=mit@sweeet.net \
--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).