From: Zachary Landau <kapheine@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] fec structure errors?
Date: Wed, 16 Mar 2005 22:45:22 -0500 [thread overview]
Message-ID: <a04f56da0503161945394f2ba0@mail.gmail.com> (raw)
In-Reply-To: <200503161758.11033.ngustavson@emacinc.com>
On Wed, 16 Mar 2005 17:58:11 -0600, NZG <ngustavson@emacinc.com> wrote:
> Got u-boot up on the 5282, but the ethernet isn't working, I'm debugging it
> and it seems really weird.
>
> Is it just me or is the fec structure in immap_5282.h incorrect?
It is not just you, the config is wrong. Take a look at the
immap_5282.h included in the tarball I sent you.
Also, if you still have problems, make sure you setup the timers
correctly on the coldfire. There are various delays in the ethernet
code that won't delay at all with the original 5282 code.
If anyone else needs it, the rough 5282 support I implemented is
available here[1] for now. It needs work and is in no way official,
but it works for me on the 5282 uCdimm.
[1] http://kapheine.hypa.net/tmp/u-boot-5282.tar.bz2
--
Zachary P. Landau <kapheine@gmail.com>
prev parent reply other threads:[~2005-03-17 3:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 23:58 [U-Boot-Users] fec structure errors? NZG
2005-03-17 3:45 ` Zachary Landau [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=a04f56da0503161945394f2ba0@mail.gmail.com \
--to=kapheine@gmail.com \
--cc=u-boot@lists.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