On Jul 21, 2010, at 11:52 AM, Bradley Hughes wrote:
> On Wed, Jul 21, 2010 at 10:24 AM, Kumar Gala <ga...@kernel.crashing.org>
> wrote:
>>>
>>> + soc8...@e0000000 {
>>> + #address-cells = <1>;
>>> + #size-cells = <1>;
>>> + device_type = "soc";
>>> + compatible = "simple-bus";
>>> + ranges = <0x0 0xe0000000 0x100000>;
>>> + bus-frequency = <0>;
>>> +
>>> + ecm-...@0 {
>>> + compatible = "fsl,ecm-law";
>>> + reg = <0x0 0x1000>;
>>> + fsl,num-laws = <8>;
>>> + };
>>> +
>>> + e...@1000 {
>>> + compatible = "fsl,mpc8555-ecm", "fsl,ecm";
>>> + reg = <0x1000 0x1000>;
>>> + interrupts = <17 2>;
>>> + interrupt-parent = <&mpic>;
>>> + };
>>> +
>>> + memory-control...@2000 {
>>> + compatible = "fsl,8555-memory-controller";
>>
>> fsl,mpc8555?
>
> Ah, yes -- it seems the dts I used for an example also has this
> problem. In drivers/edac/mpc85xx_edac.c, bindings still work for
> fsl,85.. style notation, but a comment claims that this notation would
> be deprecated at some point (2.6.29 or 2.6.30). I have updated my
> local copy and it works fine, should I send a new patch? I could also
> extend this change to the other DTS files affected (A quick search
> found 14 instances of fsl,85.. style notation.) Please let me know
> what I should do.
Send two patches. One to update your patch and another to fix the in tree dts
that have the old name.
- k
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
