From: NZG <ngustavson@emacinc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] fec structure errors?
Date: Wed, 16 Mar 2005 17:58:11 -0600 [thread overview]
Message-ID: <200503161758.11033.ngustavson@emacinc.com> (raw)
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?
On page 374 of the Coldfire manual it gives a memory map of the registers.
The first thing I noticed is that the ethernet controller register (ECR) is
located at offset 0x1024 in the manual, but appears to be at offset 0x1000 in
the structure
ypedef struct fec {
uint fec_ecntrl; /* ethernet control register */
uint fec_ievent; /* interrupt event register */
uint fec_imask; /* interrupt mask register */
uint fec_ivec; /* interrupt level and vector status */
uint fec_r_des_active; /* Rx ring updated flag */
uint fec_x_des_active; /* Tx ring updated flag */
uint res3[10]; /* reserved */
.............
Has anyone gotten the fec to work with u-boot with the 5282?
Is it possible the structure is wrong?
thx,
NZG.
next reply other threads:[~2005-03-16 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 23:58 NZG [this message]
2005-03-17 3:45 ` [U-Boot-Users] fec structure errors? Zachary Landau
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=200503161758.11033.ngustavson@emacinc.com \
--to=ngustavson@emacinc.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