[PATCH] Add MPC5200B base board mvBC-P

[Jon Smirl]

On 7/4/08, Grant Likely <grant.likely at 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 at 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 at 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 at 0x0 {
>  > +                             reg = <0x0 0x40000>;
>  > +                     };
>  > +                     u-boot_autoscript at 0x40000 {
>  > +                             reg = <0x40000 0x10000>;
>  > +                     };
>  > +                     u-boot_autoscript_red at 0x50000 {
>  > +                             reg = <0x50000 0x10000>;
>  > +                     };
>  > +                     fpga at 0x60000 {
>  > +                             reg = <0x60000 0x40000>;
>  > +                     };
>  > +                     user at 0xa0000 {
>  > +                             reg = <0xa00000 0x60000>;
>  > +                     };
>  > +                     rfs at 0x100000 {
>  > +                             reg = <0x100000 0x300000>;
>  > +                     };
>  > +                     kernel at 0x400000 {
>  > +                             reg = <0x400000 0x3c0000>;
>  > +                     };
>  > +                     dtb at 0x7c0000 {
>  > +                             reg = <0x7c0000 0x10000>;
>  > +                     };
>  > +                     dtb at 0x7d0000 {
>  > +                             reg = <0x7d0000 0x10000>;
>  > +                     };
>  > +                     ppcboot_env at 0x7e0000 {
>  > +                             reg = <0x7e0000 0x10000>;
>  > +                     };
>  > +                     ppcboot_env at 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 at gmail.com