On Fri, 2013-09-13 at 16:58 -0500, Jason Wessel wrote:
> On 09/12/2013 03:09 PM, Darren Hart wrote:
> > On Thu, 2013-09-12 at 14:52 -0500, Jason Wessel wrote:
> >> On 09/12/2013 01:16 PM, Darren Hart wrote:
> >>> On Thu, 2013-09-12 at 12:19 -0500, Jason Wessel wrote:
...
> >>>> +GRUB_SERIAL ?= "console=ttyS0,115200"
> >
> > ...
> >
> >>> I'm not very familiar with the cfgfile for menus and such, so I don't
> >>> have much to add. The one thing that catches me by surprise is the need
> >>> for the serial device. On EFI systems, grub here uses the EFI console
> >>> service, so if that uses the serial port you get it for free, no need
> >>> for GRUB to try and use it directly. In fact.... does the above not
> >>> cause some kind of conflict between the EFI console service and grub
> >>> serial?
> >>>
> >>
> >> In part that is why it is optional. With respect to the serial bits,
> >> these are only the kernel boot arguments we are talking about. It
> >
> >
> > Hrm.... this should be handled with APPEND parameter from the machine
> > configs, not a new GRUB_SERIAL statement....
> >
>
>
> Well there is a problem with that. You only have 1 APPEND, but I need
> 2 options. The whole point is the ability to add SERIAL or Graphics
I don't follow. Do you mean you need both serial and VGA? That is still
handled by the single variable. Take the FRI2 for example:
APPEND += "console=ttyPCH1,115200 console=tty0"
With what you have here, it seems to me this will be ignored and GRUB
will instead pass console=ttyS0,115200 - which will not work on the
FRI2.
> console access for early boot all the way through user space hand off
> and seamlessly picking things up later in user space with mingetty
> etc...
>
> This option is mainly used for the installer media and to provide a
> consistent look and feel regardless if you come from EFI or a PCIBIOS
> + syslinux.
SYSLINUX also has some recipe-specific console options, but those are
due to the syntax differences and are used to specify how syslinux talks
to the device, while this appears to be Linux kernel syntax
("console=ttyS0") rather than grub syntax ("serial --unit=0
--speed=115200")... and yet I don't see the "console=ttyS0" being passed
to the kernel.... so I am confused. Where does the GRUB_SERIAL content
actually get used? I mean besides the creation of the btypes array....
--
Darren
>
>
> >
> >> doesn't seem that there is a "primary" display interface for the HCDP
> >> in the EFI firmware I have. Additionally, the kernel throws the EFI
> >> serial console under the bus at ACPI probe time, while this certainly
> >> could also be a bug in the firmware I have on my test board, the only
> >> way to keep the serial port alive for a login and the kernel boot
> >> information was to specify console=ttyS0...
> >
> > Hrm.... interesting. I guess we'll just need to test more broadly.
> > Indeed the kernel should be using it's own console= parameter, but
> > again, that should come from the APPEND_machine variable.
> >
> >
> >> I have yet another system I need to try this on which has a much newer
> >> UEFI and a serial port, but I thought it would be best to get
> >> something out there that covers the "buggy firmwares" as well which
> >> can be built optionally.
> >
> > Agreed, so long as it doesn't break the common case.
>
>
> The common case is not broken. This is something you have to turn on
> in the image or local.conf.
>
> The new patches will available soon for the whole series as soon as
> all the test hardware has booted in legacy and efi mode.
>
> Cheers,
> Jason.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
