From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: LinuxPPC Embedded Mailing List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: FEC question about setting SIEL register
Date: Tue, 08 Aug 2000 16:11:03 -0400 [thread overview]
Message-ID: <39906957.804A06FD@embeddededge.com> (raw)
In-Reply-To: 20000808055121.7716D220@elph.research.canon.com.au
Graham Stoney wrote:
> .... The culprit was that I hadn't
> configured the PHY MII link interrupt (which is on external IRQ5 on our board)
> as edge triggerred in the SIU Interrupt Edge/Level (SIEL) register.
Yeah....There are about a bazillion different pin multiplexing
combinations on these parts. You really should have a very methodical
procedure to verify all of them, usually as part of the design process
before hardware CAD.
> Setting the SIEL is trivial enough, but where abouts is the right place to
> do it: in the fec.c driver, or in the 8xxrom/boot loader?
Normally I do all of this in a boot rom. The I/O pin configuration
necessary to make even minimal forward progress must be done very early,
so I just do all of it there in one place.
> ...... The FADS code in
> fec.c doesn't set the SIEL,
Nope. It never did.
> .... and it doesn't seem to be set in the FADS code in
> 8xxrom/fadsrom either, so I would conclude that it probably suffers the same
> problem.
It should be, but I screwed that up the first time. The next logical
place (and where it used to exist), was in m8xx_setup.c in the
function m8xx_init_IRQ(). Since I don't have a FADS board any longer
for testing, and everyone else was connecting this interrupt to a
port C pin, the code just disappeared as part of the new interrupt
management.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-08-08 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-08 5:51 FEC question about setting SIEL register Graham Stoney
2000-08-08 8:33 ` Murray Jensen
2000-08-08 20:11 ` Dan Malek [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=39906957.804A06FD@embeddededge.com \
--to=dan@netx4.com \
--cc=greyham@research.canon.com.au \
--cc=linuxppc-embedded@lists.linuxppc.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 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.