From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: Andre Schwarz <andre.schwarz@matrix-vision.de>,
linux-ppc list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Add MPC5200B base board mvBC-P
Date: Fri, 4 Jul 2008 13:27:39 -0400 [thread overview]
Message-ID: <9e4733910807041027v5a75b50ao248d3c2848f99630@mail.gmail.com> (raw)
In-Reply-To: <20080704170041.GD17062@secretlab.ca>
On 7/4/08, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Fri, Jul 04, 2008 at 06:35:39PM +0200, Andre Schwarz wrote:
> > + #address-cells = <2>;
> > + #size-cells = <1>;
> > + ranges = <0x0 0x0 0xff800000 0x00800000>;
> > + flash@0,0 {
> > + compatible = "cfi-flash";
>
> For completeness, it is good practice for the first entry in the compatible
> list to be the actual flash chip, followed by "cfi-flash"
>
> > + reg = <0 0 0x800000>;
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + bank-width = <1>;
> > + device-width = <1>;
> > + nor_total@0x0 {
> > + reg = <0x0 0x800000>;
> > + };
>
> I don't know if this is legal; to have overlapping flash sections (but
> I'm not a cfi-flash binding expert).
>
> > + u-boot@0x0 {
> > + reg = <0x0 0x40000>;
> > + };
> > + u-boot_autoscript@0x40000 {
> > + reg = <0x40000 0x10000>;
> > + };
> > + u-boot_autoscript_red@0x50000 {
> > + reg = <0x50000 0x10000>;
> > + };
> > + fpga@0x60000 {
> > + reg = <0x60000 0x40000>;
> > + };
> > + user@0xa0000 {
> > + reg = <0xa00000 0x60000>;
> > + };
> > + rfs@0x100000 {
> > + reg = <0x100000 0x300000>;
> > + };
> > + kernel@0x400000 {
> > + reg = <0x400000 0x3c0000>;
> > + };
> > + dtb@0x7c0000 {
> > + reg = <0x7c0000 0x10000>;
> > + };
> > + dtb@0x7d0000 {
> > + reg = <0x7d0000 0x10000>;
> > + };
> > + ppcboot_env@0x7e0000 {
> > + reg = <0x7e0000 0x10000>;
> > + };
> > + ppcboot_env@0x7f0000 {
> > + reg = <0x7f0000 0x10000>;
> > + };
>
> I think it would be better to just leave out the partition information
> and modify U-Boot to fill them in (just like memory and clock speed are
> left out). Things like flash partitions are less like hardware
> description and more like configuration data.
Has anyone tried writing a RedBoot type partition table onto their
flash device? If it is there the kernel will read the partition info
from it. It's a config option in the kernel flash support section. Is
there a utility for creating these tables?
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-07-04 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 16:35 [PATCH] Add MPC5200B base board mvBC-P Andre Schwarz
2008-07-04 17:00 ` Grant Likely
2008-07-04 17:27 ` Jon Smirl [this message]
2008-07-05 9:32 ` André Schwarz
2008-07-05 16:13 ` Grant Likely
2008-07-06 23:50 ` David Gibson
2008-07-07 7:49 ` Andre Schwarz
2008-07-07 14:12 ` Grant Likely
2008-07-07 18:51 ` Jon Smirl
2008-07-08 3:41 ` David Gibson
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=9e4733910807041027v5a75b50ao248d3c2848f99630@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=andre.schwarz@matrix-vision.de \
--cc=grant.likely@secretlab.ca \
--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).