Hi David,

>> +/ {
>> +    model = "unknown,dbox2"; // boot wrapper fills in correct manufacturer
> 
> Probably better just to leave model out of the dts and let the
> bootwrapper add it.

Unfortunately, dtc requires a model:

$ dtc arch/powerpc/boot/dts/dbox2.dts
DTC: dts->dts  on file "arch/powerpc/boot/dts/dbox2.dts"
ERROR: Missing "model" property in /

>> +            [EMAIL PROTECTED],0 {
>> +                    compatible = "cfi-flash";
>> +                    reg = <0 0 800000>;
>> +                    bank-width = <4>;
>> +                    device-width = <1>;
>> +                    #address-cells = <1>;
>> +                    #size-cells = <1>;
>> +                    [EMAIL PROTECTED] {
>> +                            label = "BR bootloader";
>> +                            reg = <0 20000>;
>> +                            read-only;
>> +                    };
>> +                    [EMAIL PROTECTED] {
>> +                            label = "FLFS (U-Boot)";
>> +                            reg = <20000 20000>;
>> +                    };
>> +                    [EMAIL PROTECTED] {
>> +                            label = "rootfs";
>> +                            reg = <40000 7c0000>;
>> +                    };
>> +                    [EMAIL PROTECTED] {
> 
> Uh.. I really don't know what the MTD driver will handle these
> overlapping partitions.  I suspect it will not be pretty...
> 
>> +                            label = "Flash without bootloader";
>> +                            reg = <20000 7e0000>;
>> +                    };
>> +                    [EMAIL PROTECTED] {
>> +                            label = "Complete Flash";
>> +                            reg = <0 800000>;
>> +                            read-only;
>> +                    };
>> +            };
>> +    };

MTD handles this correctly. dbox2 uses "Flash without bootloader" for flashing 
image updates and "Complete Flash" for creating a backup of everything.
OpenWRT also uses overlapping partitions BTW (and also for flashing updates).

Thanks,
Jochen
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Reply via email to