From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: linuxppc-dev list <Linuxppc-dev@ozlabs.org>
Subject: Re: Comments on device tree for pcm030
Date: Mon, 9 Jun 2008 11:13:35 +0200 [thread overview]
Message-ID: <20080609091335.GC13036@pengutronix.de> (raw)
In-Reply-To: <9e4733910806081208r1a8d0987j6eab0d73bc446640@mail.gmail.com>
Hi,
On Sun, Jun 08, 2008 at 03:08:33PM -0400, Jon Smirl wrote:
> Why not a compatible field in the top of the tree? Then you wouldn't
> need to list the boards in mpc5200_simple.c.
> compatible = "phytec,pcm030","simple-mpc5200";
>
> Device tree has an entry for AC97 on PSC1. I don't think the Phytec
> module or carrier board has AC97 hardware.
>
> The RTC chip says pcf8563, phytec doc says it is a pcf8564.
>
> There should be an i2c entry for the eeprom but I don't know the part
> number for it.
>
> What about the flash on the local bus? Could we use something like
> this, or the same without the partition data?
>
> lpb@ff000000 {
> compatible = "fsl,lpb";
> ranges = <0 ff000000 01000000>;
>
> flash@00000000 {
> compatible = "cfi-flash";
> reg = <00000000 01000000>;
> bank-width = <2>;
The board comes with different flash sizes with different bank widths.
That's why I decided to no put the flash entries into the tree.
We used to detect the flash size/bankwidth using the bootcs config
register (which was previously set by U-Boot). We could change U-Boot to
adjust the device tree accordingly, but we haven't done this so far,
sorry.
> #size-cells = <1>;
> #address-cells = <1>;
> partition@0 {
> label = "ubootl";
> reg = <00000000 00040000>;
> };
> partition@40000 {
> label = "kernel";
> reg = <00040000 001c0000>;
> };
> partition@200000 {
> label = "jffs2";
> reg = <00200000 00D00000>;
> };
> partition@f00000 {
> label = "uboot";
> reg = <00f00000 00040000>;
> };
> partition@f40000 {
> label = "oftree";
> reg = <00f40000 00040000>;
> };
> partition@f80000 {
> label = "space";
> reg = <00f80000 00080000>;
> };
I think partitions shouldn't go into the default device tree, as people
may have different partitioning.
Sascha
--
Pengutronix e.K. - Linux Solutions for Science and Industry
-----------------------------------------------------------
Kontakt-Informationen finden Sie im Header dieser Mail oder
auf der Webseite -> http://www.pengutronix.de/impressum/ <-
next prev parent reply other threads:[~2008-06-09 9:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 19:08 Comments on device tree for pcm030 Jon Smirl
2008-06-08 23:28 ` Grant Likely
2008-06-09 7:56 ` Juergen Beisert
2008-06-09 12:37 ` Jon Smirl
2008-06-09 13:05 ` Juergen Beisert
2008-06-09 12:41 ` Jon Smirl
2008-06-09 13:57 ` Grant Likely
2008-06-09 9:13 ` Sascha Hauer [this message]
2008-06-09 21:00 ` Robert Schwebel
2008-06-09 16:31 ` Juergen Beisert
2008-06-09 21:30 ` Jon Smirl
2008-06-10 8:20 ` Juergen Beisert
2008-06-10 9:05 ` Juergen Beisert
2008-06-10 13:26 ` Grant Likely
2008-06-11 4:08 ` Jon Smirl
2008-06-09 21:05 ` Robert Schwebel
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=20080609091335.GC13036@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=Linuxppc-dev@ozlabs.org \
--cc=jonsmirl@gmail.com \
/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).