From: Sylvain Munaut <tnt@246tNt.com>
To: John Rigby <jcrigby@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel for MPC Lite 5200 will not compile
Date: Tue, 28 Mar 2006 22:47:33 +0200 [thread overview]
Message-ID: <4429A0E5.8010308@246tNt.com> (raw)
In-Reply-To: <4b73d43f0603280815n3fc7bb5dq38b72f87f18b905f@mail.gmail.com>
Hi Matthias,
You might want to try the "quick start" section of
http://www.246tnt.com/mpc52xx/
The last compile I tried worked just fine ... You just needed to be sure
CONFIG_NET is
enabled (even if you don't use network ... the issue is known and being
taken care of,
I've seen some posts of Russel King and Andrew Morton about it).
If it still doesnt work, report it and I'll have a closer look. Maybe
something changed
recently and I didn't update my tree since a few days ...
Sylvain
John Rigby wrote:
> Sorry I'm not sure what the state of 5200 support in the eldk. I know
> that Wolfgang
> has said that 2.6 is not supported though. You may want to try out
> Sylvains
> kernel: http://gitbits.246tnt.com/gitbits/linux-2.6-mpc52xx.git
>
> You can search in list for Syvains instructions on how to use it.
>
>
> On 3/28/06, *Matthias Fechner* <idefix@fechner.net
> <mailto:idefix@fechner.net>> wrote:
>
> Hello John,
>
> * John Rigby <jcrigby@gmail.com <mailto:jcrigby@gmail.com>>
> [27-03-06 18:01]:
> > try make lite5200_defconfig instead of copying it to .config
> > or make oldconfig after copying ti to .config
>
> I tried now several combinations with:
> make ARCH=ppc CROSS_COMPILE=ppc_6xx- lite5200_defconfig
> make ARCH=ppc CROSS_COMPILE=ppc_6xx- uImage
>
> then coping the file to .config and
> make ARCH=ppc CROSS_COMPILE=ppc_6xx- oldconfig
> make ARCH=ppc CROSS_COMPILE=ppc_6xx- uImage
>
> but it always leads to the same error message...
>
> Best regards,
> Matthias
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org <mailto:Linuxppc-embedded@ozlabs.org>
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2006-03-28 20:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 0:07 Kernel for MPC Lite 5200 will not compile Matthias Fechner
2006-03-28 1:01 ` John Rigby
2006-03-28 9:49 ` Matthias Fechner
2006-03-28 16:15 ` John Rigby
2006-03-28 20:47 ` Sylvain Munaut [this message]
2006-03-29 15:32 ` Matthias Fechner
2006-04-01 9:19 ` Matthias Fechner
2006-04-02 17:42 ` Sylvain Munaut
2006-04-02 19:32 ` Matthias Fechner
2006-03-28 22:33 ` Wolfgang Denk
2006-03-29 15:31 ` Matthias Fechner
2006-03-28 22:31 ` Wolfgang Denk
2006-03-29 15:39 ` Matthias Fechner
2006-03-29 20:11 ` Wolfgang Denk
2006-03-29 23:02 ` Sylvain Munaut
2006-03-30 0:34 ` Wolfgang Denk
2006-03-30 6:36 ` Sylvain Munaut
2006-03-30 16:29 ` John Rigby
2006-03-30 16:39 ` John Rigby
2006-03-30 20:05 ` Dale Farnsworth
2006-03-30 21:51 ` John Rigby
2006-03-30 19:53 ` Dale Farnsworth
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=4429A0E5.8010308@246tNt.com \
--to=tnt@246tnt.com \
--cc=jcrigby@gmail.com \
--cc=linuxppc-embedded@ozlabs.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).