On Mon, Mar 13, 2017 at 10:37:11PM +0100, Rafa?? Mi??ecki wrote:
> On 03/13/2017 08:27 PM, Jon Mason wrote:
> >On Mon, Mar 13, 2017 at 3:15 PM, Rafa?? Mi??ecki <rafal@xxxxxxxxxx> wrote:
> >>On 03/13/2017 08:14 PM, Andrew Lunn wrote:
> >>>
> >>>On Mon, Mar 13, 2017 at 07:48:26PM +0100, Rafa?? Mi??ecki wrote:
> >>>>
> >>>>On 03/12/2017 06:10 PM, Andrew Lunn wrote:
> >>>>>>
> >>>>>>+ chosen {
> >>>>>>+ bootargs = "console=ttyS0,115200 earlycon";
> >>>>>
> >>>>>
> >>>>>Using bootargs to pass the serial settings has been deprecated for a
> >>>>>while. Please use stdout-path instead.
> >>>>
> >>>>
> >>>>I tried following patch with my SR400ac (I put Archer C5 aside for now).
> >>>
> >>>
> >>>Hi Rafael
> >>>
> >>>Take a look at for example the bcm911360k.dts
> >>>
> >>> aliases {
> >>> serial0 = &uart3;
> >>> };
> >>>
> >>> chosen {
> >>> stdout-path = "serial0:115200n8";
> >>> };
> >>>
> >>>You need an alias to the serial device you want to us, and you should
> >>>list the speed, parity, bits etc.
> >>
> >>
> >>That was actually my first try (just with s/uart3/uart0) and I got the same
> >>problem.
> >
> >I have a similar line in the bcm953012k.dts, and the serial there works for me.
>
> Well, the serial seems to work OK (I'm getting boot log & I can see my chars
> being echoed back). I just can't log in. Can this kernel change somehow affect
> user space?
Yes, it can. You probably don't have a getty running on ttyS0. But you
do have on /dev/console? Look in /etc/inittab.
Andrew
--
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
