From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: Dan Malek <dmalek@jlc.net>,
bsimon@ctam.com.au, linuxppc-embedded@lists.linuxppc.org
Subject: Re: mpc8xx-2.3.10 configuration questions.
Date: Thu, 16 Sep 1999 11:32:56 -0400 [thread overview]
Message-ID: <37E10DA8.4E819A64@netx4.com> (raw)
In-Reply-To: 19990916073633.38BA67B8@elph.research.canon.com.au
Graham Stoney wrote:
> Accordingly, I offer the following changes, which were necessary to build a
> kernel for the RPCg CLLF board with an 860T.
The CLLF isn't a really a lite...it's a Classic with less stuff.
I am currently working on this now, and if you actually have a
CLLF (I don't know how you would) the FEC isn't going to work
because of the faulty magnetics on the board (not RPCg fault, the
manufacturer acknowledged an error after we found it). The new
CLLFs will be available within a few days.
> *** arch/ppc/8xx_io/fec.c.dist Wed Sep 15 17:32:26 1999
What is fec.c.dist? It seems like I am always fixing this one.
I pretty sure I got it right in the 2.3.18 kernel.
> + /* Interrupt level assignments.
> + */
> + #define FEC_INTERRUPT SIU_LEVEL1 /* FEC interrupt */
> +
The CLLF will be built from the Classic configuration, so it
isn't appropriate to put this here. There is also more that needs
to be added for the MII interrupts through a Port C bit.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-16 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-15 1:25 mpc8xx-2.3.10 configuration questions Brendan Simon
1999-09-15 19:28 ` Dan Malek
1999-09-15 23:48 ` Brendan Simon
1999-09-16 15:39 ` Dan Malek
1999-09-16 7:36 ` Graham Stoney
1999-09-16 15:32 ` Dan Malek [this message]
1999-09-17 0:48 ` Graham Stoney
1999-09-17 1:47 ` Dan Malek
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=37E10DA8.4E819A64@netx4.com \
--to=dan@netx4.com \
--cc=bsimon@ctam.com.au \
--cc=dmalek@jlc.net \
--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 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).