[OE-core] [PATCH 5/5] grub-efi.bbclass: Add serial and graphics menu options

Jason Wessel jason.wessel at windriver.com
Tue Sep 17 12:19:56 UTC 2013


On 09/16/2013 12:49 PM, Darren Hart wrote:
> 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.


This is fixed in the new series. 

The auto menu is intended to offer the end user the choice of which is their default console.  Obviously you can emit text to both, but you only get one selected as the default input device.

It might not be obvious but we use mingetty and selectively use the console.   The whole alternate boot thing is completely optional.  Now if you set the SERIAL stuff to be "".

It might even be better to point this out more directly by changing the variable names to something like ALT_CONSOLE...


>
>>  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....


This is addressed to, but we may yet go another round to clean up the understanding of things.  A v3 to arrive soon.

Cheers,
Jason.




More information about the Openembedded-core mailing list