> Did you use CONFIG_PPC_CPM_NEW_BINDING in 2.6.25? It became mandatory in
> 2.6.26. Also, try commenting out cpm_setbrg() calls in case the
> frequency is not being set properly.
Yes, this option was enabled. Nothing changed with empty cpm_setbrg()
function :(
> 2.6.26 introduced the allocation of the CPM2 SMC parameter RAM area; what
> did your device node look like in 2.6.25? What happens if you use that
> device tree with 2.6.26?
The cpm node for the 2.6.25.4 kernel was the following:
[EMAIL PROTECTED] {
#address-cells = <1>;
#size-cells = <1>;
#interrupt-cells = <2>;
compatible = "fsl,mpc8280-cpm", "fsl,cpm2";
reg = <119c0 30>;
ranges;
muram {
#address-cells = <1>;
#size-cells = <1>;
ranges = <0 0 10000>;
[EMAIL PROTECTED] {
compatible = "fsl,cpm-muram-data";
reg = <100 1f00 9800 800>;
};
};
[EMAIL PROTECTED] {
compatible = "fsl,cpm-brg", "fsl,cpm2-brg";
reg = <119f0 10 115f0 10>;
};
smc1: [EMAIL PROTECTED] {
device_type = "serial";
compatible = "fsl,cpm2-smc-uart";
reg = <11a80 20 0 40>;
interrupts = <4 8>;
interrupt-parent = <&PIC>;
fsl,cpm-brg = <7>;
fsl,cpm-command = <1d000000>;
};
};
(muram node for 2.6.25 is differs from muram node for the 2.6.26)
With this device tree I have a warning message from cpm_uart driver
tells that the dts file needs to be updated.
Ilya.
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
