linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "André Schwarz" <Andre.Schwarz@matrix-vision.de>
To: linux-ppc list <linuxppc-dev@ozlabs.org>
Subject: simple MPC5200B system
Date: Sun, 16 Mar 2008 20:15:28 +0100	[thread overview]
Message-ID: <47DD71D0.2010203@matrix-vision.de> (raw)

All,

I'm quite stuck in getting our MPC5200B based systems work on 2.6.24+=20
... maybe someone could give me some hints.
Up to now the systems have been running on 2.6.19 without any problems.

This is what I've done so far :

- get a recent system with 2.6.19 running and keep the toolchain (gcc=20
4.0) including RFS uImage.
- latest bootloader (u-boot 1.3.2) is running fine with dtb support.
- Kernel and RFS images are available via bootp/tftp
- device tree blob seems ok, i.e. u-boot can display the blob and fill=20
in all clocks correctly.
- Kernel gets called with Kernel, RFS and dtb on suitable adresses=20
(0x100000, 0x600000, 0x5F0000).
- nothing more happens. It looks like the console isn't working properly=20
- maybe worse ...

We're using the latest git version from Wolfgang Denk.

The kernel has been build using the "MPC5200 simple" setup. I've added=20
our board identifier "mv,mvbluecougar" to the list of supported boards=20
in the "mpc52xx_simple.c" file. This identifier is used in the dtb as=20
well of course. This should be enough along with a valid device tree=20
blob, isn't it ? Did I miss anything already ?

As far as I did understand by reading the docs it should be possible=20
running a general MPC52xx kernel with a custom dtb ? Is this correct ?

The dts file has already been reduced to a minimum, i.e. only the cpu,=20
pic, xlb and a few nodes like psc1 and psc2 are present. No bestcomm,=20
pci, ata or "advanced" features like mtd partitions. All I want to get=20
working is the serial console on "/dev/ttyPSC0".

Are there any hidden stumbling blocks ?

Sorry for the "simple" questions but obviously there are many questions=20
coming up during move from "ppc" to "powerpc".

Any help is appreciated.

regards,
Andr=E9 Schwarz
Matrix Vision GmbH

MATRIX VISION GmbH, Talstra=DFe 16, DE-71570 Oppenweiler  - Registergeric=
ht: Amtsgericht Stuttgart, HRB 271090
Gesch=E4ftsf=FChrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner

             reply	other threads:[~2008-03-16 19:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 19:15 André Schwarz [this message]
2008-03-16 20:01 ` simple MPC5200B system Grant Likely
2008-03-17  9:35   ` André Schwarz
2008-03-18  8:49   ` Andre Schwarz
2008-03-18 10:34     ` Andre Schwarz
2008-03-18 14:31       ` Grant Likely
2008-03-18 15:14         ` Andre Schwarz
2008-03-18 16:21           ` Grant Likely
2008-03-18 16:44             ` Andre Schwarz
2008-03-20  0:14     ` Wolfgang Denk
2008-03-20  0:21       ` David Gibson
2008-03-20  7:48         ` André Schwarz
2008-03-20  8:20           ` David Gibson
2008-03-20  9:11             ` André Schwarz
2008-03-20  9:29             ` Stefan Roese

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=47DD71D0.2010203@matrix-vision.de \
    --to=andre.schwarz@matrix-vision.de \
    --cc=linuxppc-dev@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).