On Thu, Oct 30, 2014 at 12:03:22PM +0100, Geert Uytterhoeven wrote:
> On Thu, Oct 30, 2014 at 11:44 AM, Laurent Pinchart
> <laurent.pinchart@xxxxxxxxxxxxxxxx> wrote:
> > On Wednesday 29 October 2014 15:28:38 Geert Uytterhoeven wrote:
> >> Since commit 595c6a4bb77f0096 ("ARM: shmobile: koelsch: Remove legacy C
> >> board code"), koelsch is restricted to booting from DT, so
> >> chosen/stdout-path is always used, and we can drop the "console="
> >> parameter from chosen/bootargs.
> >
> > I'm curious, how is the baud rate now selected ?
>
> >From an earlier response for kzm9d:
>
> "I forgot emev is the only supported SoC not using sh-sci.
> drivers/tty/serial/sh-sci.c:serial_console_setup() defaults to 115200 baud,
> while serial8250_console_setup() defaults to 9600 baud."
Hi Geert,
while backporting this and similar changes for other boards
to v3.14/LTSI-3.14 I noticed that koelsch, alt and ape6evm-reference
come up without a console. Which is not ideal.
I am wondering if you have any thoughts on why this may occur.
My wild stab in the dark is some interaction with PM.
For reference my backport is the backport/v3.14.23/snapshot2.wip1 tag in my
renesas-backports tree. At the very top it includes reversions of the
backports of the troublesome patches.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
