From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: <sebastien_tadeoni@yahoo.fr>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Cross compilation for MPC860
Date: Thu, 16 Sep 1999 21:12:33 -0400 [thread overview]
Message-ID: <37E19581.D5837449@netx4.com> (raw)
In-Reply-To: 19990917002315.B636D7B8@elph.research.canon.com.au
Graham Stoney wrote:
> Anyway, here's the complete list of problems I had building the 2.2.5 snapshot
> for an 860T board.
The only likely 860T board to build with 2.2.5 is the FADS, and
I have not kept that up to date (which is why fec.c is out of date).
> The FEC driver fell through the cracks changing request_irq to request_8xxirq:
There is more that has to change if you are not building for
a FADS board. You have to assign the appropriate MII interrupts
and write the MMI command/status for the particular PHY you are
using.
The RPCg Classic and CLLF are both 860T boards. I will update all
of the fec.c driver when I get a chance to port to those boards.
> The Makefile in arch/ppc/kernel includes openpic.o, i8259.o and pmac_pic.o
> whenever CONFIG_APUS isn't set; even though most other platforms don't want
> them either.
>
> drivers/char/Makefile includes pc_keyb.o and defkeymap.o whenever the ARCH is
> not m68k, which means they get included in all embedded 8xx builds.
>
> drivers/macintosh/Makefile includes via-cuda.o et al whenever CONFIG_MBX is
> not defined. I changed it like this:
You shouldn't have to change it for anything. If your linker
is working properly, it isn't going to include those objects and
there is no harm in building them.
>
> Lots of the EXPORT_SYMBOLs in arch/ppc/kernel/ppc_ksyms.c caused me grief;
> I had to wrap isa_io_base, isa_mem_base and pci_dram_offset in
> #ifdef CONFIG_PCI. I #if 0'd out _prep_type and ucSystemType, and all of:
Something is wrong with your tools or the configuration you have
selected. None of these changes are necessary.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-17 1:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-16 12:52 Cross compilation for MPC860 sébastien tadéoni
1999-09-16 18:21 ` Scott Wood
1999-09-16 23:44 ` Brendan Simon
1999-09-17 0:23 ` Graham Stoney
1999-09-17 1:12 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-21 12:40 sébastien tadéoni
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=37E19581.D5837449@netx4.com \
--to=dan@netx4.com \
--cc=greyham@research.canon.com.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sebastien_tadeoni@yahoo.fr \
/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).