So it was a hardware issue, the USB to serial converter is dead. :-#
On May 22, 2015 5:20 PM, "Thomas PERROT" <[email protected]> wrote:

> Ok, thank you for your help, so I should be a problem elsewhere.
>
> I thought that it was the problem because, I just replaced sysvinit by
> systemd on this build and serial console still terribly empty. I have
> checked if the serial device was well mounted and kernel cmdline was
> well formated. So I thought at an incompatibility between systemd and
> rpi recipes.
>
> On Fri, May 22, 2015 at 4:32 PM, Paul Eggleton
> <[email protected]> wrote:
> > On Friday 22 May 2015 16:27:05 Thomas PERROT wrote:
> >> On Fri, May 22, 2015 at 4:06 PM, Paul Eggleton <
> >> [email protected]> wrote:
> >> > On Friday 22 May 2015 15:58:58 Thomas PERROT wrote:
> >> > > Sorry, I meant systemd-serialgetty.bb from meta instead of
> meta-systemd.
> >> > > So replace "?=" by "??=" should be a better solution.
> >> >
> >> > You still haven't described the actual problem, because what you did
> >> > describe (the machine config being overridden by this) shouldn't be
> >> > possible. Again, did  you check bitbake -e systemd-serialgetty | less
> ?
> >>
> >> Attached the result of the command bitbake -e systemd-serialgetty
> >
> > So from what you've just sent, the final value is "115200 ttyAMA0" which
> is the
> > value set by the machine config - so it seems like it's working as it
> should.
> > How are you determining that there is a problem?
> >
> > Cheers,
> > Paul
> >
> > --
> >
> > Paul Eggleton
> > Intel Open Source Technology Centre
>
-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to