From: Rune Torgersen
Finally got it (sort-of) working.
Turned out that for some reason the console init is setting
the baudrate
to 9600
the options string passed in to the console init fuunction is NULL.
Any idea oon how this should be passed in from u-boot?
Ok, needed a valid console=
Rune Torgersen wrote:
Ok, needed a valid console= line on the command line. WHen we tried
that, we had a typo, so it was not recognized.
Our old 2.6.18 arch/ppc kernel didn't need a console parameter, it got
the baudrate from u-boot somehow.
Anyway of doing that here too?
You could add
Rune Torgersen wrote:
From: Scott Wood
You could add something to the cuboot code to fill in current-speed
based on the value in the bd_t.
Ahh.. That was what I'm missing.
Where in the devicetree is that supposed to be at?
In the serial node.
-Scott
From: Scott Wood
You could add something to the cuboot code to fill in current-speed
based on the value in the bd_t.
Ahh.. That was what I'm missing.
Where in the devicetree is that supposed to be at?
___
Linuxppc-dev mailing list
From: Scott Wood
The tree looks OK. The checkstop may be from erratum SIU18;
I had this issue on the ep8248e board.
Try clearing BCR[PLDP].
Not sure what was wrong. We took a step back, and redid some stuff, and
now we have serial output from the boot-wrapper.
THe checkstop came from the
Rune Torgersen wrote:
Not sure what was wrong. We took a step back, and redid some stuff, and
now we have serial output from the boot-wrapper.
THe checkstop came from the wrapper grying to access the bcsr and doing
the chip select fixup. We don';t have a bcsr on our board, and the cs
layout
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?
[EMAIL PROTECTED] {
device_type = serial;
Rune Torgersen wrote:
Ok we're now using
[EMAIL PROTECTED] {
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
From: Scott Wood
Don't forget to exclude the SMC parameter RAM from the muram
data area
in /soc/cpm/muram/data/reg. If you have an older device tree binding
that has no /soc/cpm/muram node, but instead has two resources in
/soc/cpm/reg, you need to move to head-of-tree to get this to
Rune Torgersen wrote:
From: Scott Wood
Don't forget to exclude the SMC parameter RAM from the muram
data area
in /soc/cpm/muram/data/reg. If you have an older device tree binding
that has no /soc/cpm/muram node, but instead has two resources in
/soc/cpm/reg, you need to move to
From: Scott Wood [mailto:[EMAIL PROTECTED]
Rune Torgersen wrote:
From: Scott Wood
Don't forget to exclude the SMC parameter RAM from the muram
data area
in /soc/cpm/muram/data/reg. If you have an older device
tree binding
that has no /soc/cpm/muram node, but instead has two
11 matches
Mail list logo
