linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "FIXED-TERM Seeh Thomas (BEG/EMS1)"
	<fixed-term.Thomas.Seeh@de.bosch.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: LITE5200 configuration
Date: Thu, 27 Aug 2009 15:11:51 +0200	[thread overview]
Message-ID: <20090827131151.537EC833DBD2@gemini.denx.de> (raw)
In-Reply-To: <6E9D235B18CE694399D781F05D9C42E79F0C2C12@SI-MBX11.de.bosch.com>

Dear "FIXED-TERM Seeh Thomas (BEG/EMS1)",

In message <6E9D235B18CE694399D781F05D9C42E79F0C2C12@SI-MBX11.de.bosch.com> you wrote:
>
> I'll try to run a 2.6.31-rc7 kernel on my Lite5200 board.

Is this really a Lite5200, or is it a Lite5200B?

Hint: if U-Boot prints something like "CPU: MPC5200B v2.2, Core v1.4"
then its a 5200B, and thus a Lite5200 board.

> For the device tree I use lite5200.dts and compiled it simply with
> 
>         make ARCH=powerpc CROSS_COMPILE=ppc_6xx- lite5200.dtb

For a Lite5200B you should use the lite5200b device tree.

> But I'm not sure what configuration for the kernel I should choose. There is no
> lite5200_defconfig only one for the lite5200b.

Rigth. Because there are virtually no lite5200 boards out there.

> I tried it with mpc5200_defconfig and lite5200b_defconfig, but I'm not sure which
> is the right way.

Both will work. On a Lite5200 board I would use lite5200b_defconfig,
though.

> For compiling the kernel I use:
>
>         make ARCH=powerpc CROSS_COMPILE=ppc_6xx- "CONFIG_FILE"

That's:

	make ARCH=powerpc CROSS_COMPILE=ppc_6xx- mrproper
	make ARCH=powerpc CROSS_COMPILE=ppc_6xx- 52xx/lite5200b_defconfig

>         make ARCH=powerpc CROSS_COMPILE=ppc_6xx- uImage
>         make ARCH=powerpc CROSS_COMPILE=ppc_6xx- modules
>         make ARCH=powerpc CROSS_COMPILE=ppc_6xx- modules_install


> I use U-Boot 2009.06, with the following settings for bootup:

Looks as if you have a Rev. B CPU with the wrong device tree.

Unfortunaltey you omit the interesting part (i. e. the U-Boot boot
message) which would contain this important piece of information.

> --_000_6E9D235B18CE694399D781F05D9C42E79F0C2C12SIMBX11deboschc_
> Content-Type: text/html; charset"iso-8859-1"
> Content-Transfer-Encoding: quoted-printable

And *please* do not post HTML to mailing lists. Never ever do that.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
If I ever needed a brain transplant, I'd choose a teenager's  because
I'd want a brain that had never been used.

  reply	other threads:[~2009-08-27 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27  8:01 LITE5200 configuration FIXED-TERM Seeh Thomas (BEG/EMS1)
2009-08-27 13:11 ` Wolfgang Denk [this message]
2009-08-27 14:14   ` AW: " FIXED-TERM Seeh Thomas (BEG/EMS1)
2009-08-27 16:02     ` Wolfgang Grandegger
2009-08-28  5:32       ` AW: " FIXED-TERM Seeh Thomas (BEG/EMS1)
2009-08-28 14:10     ` Grant Likely

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=20090827131151.537EC833DBD2@gemini.denx.de \
    --to=wd@denx.de \
    --cc=fixed-term.Thomas.Seeh@de.bosch.com \
    --cc=linuxppc-dev@lists.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).