Help with device tree binding for SMC serial

[Rune Torgersen]

> From: Scott Wood 
> Sent: Wednesday, January 09, 2008 1:46 PM
> > We're trying to get a SMC serial port on a8280 to work.
> > I cannot find any ecxamples on the binding, so we've tried 
> to make one.
> > 
> > is this anywhere close to workable?
> > 
> > serial at 11a80 {
> > 	device_type = "serial";
> > 	compatible = "fsl,mpc8280-smc-uart",
> > 				 "fsl,cpm2-smc-uart";
> > 	reg = <11a80 10 87fc 2>;
> 
> The current binding has the actual parameter ram block as the 
> second reg 
> property, not the two-byte pointer.  If your firmware doesn't 
> initialize 
> the pointer, you'll have to do it in platform code.
> 
> > 	interrupts = <4 8>;
> > 	interrupt-parent = <&PIC>;
> > 	fsl,cpm-brg = <7>;
> > 	fsl,cpm-command = <01000000>;
> > };
> 
> cpm-command should be <1d000000> for SMC1.
> 
> Otherwise, it looks OK.

Ok we're now using
serial at 11a80 {
	device_type = "serial";
	compatible = "fsl,mpc8280-smc-uart",
				 "fsl,cpm2-smc-uart";
	reg = <11a80 10 0 40>;            // <base_address length
parameter_ram_address length>
	interrupts = <4 8>;                 // Interrupt from table 4.3
of mpc8280rm, interrupt is level or edge
	interrupt-parent = <&PIC>;
	fsl,cpm-brg = <7>;
	fsl,cpm-command = <1d000000>;       // Page and Sub-block code
of the CPCR
};

Right now we're trying to just get a kernel to give us some serial
output, so we can continue the porting job.
We're unsig a cuImage (using the pq2fads code right now).

Now our problem is that the serial port is spitting out 0x0a's as fast
as it can.
Seems to be repeadtin the linefeed at the end of "Uncompressing Kernel
Image ... OK"