From: Jason Wessel <jason.wessel@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/5] grub-efi.bbclass: Add serial and graphics menu options
Date: Fri, 13 Sep 2013 16:58:53 -0500 [thread overview]
Message-ID: <52338A9D.7000307@windriver.com> (raw)
In-Reply-To: <1379016587.1285.38.camel@dvhart-mobl4.amr.corp.intel.com>
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:
>>>> The syslinux.bbclass already has support for automatically generated
>>>> serial and graphics menu choices. This patch adds the same concept to
>>>> the grub-efi menu. That makes it possible to generate a single image
>>>> which can boot on a PCBIOS or EFI firmware with consistent looking
>>>> boot options.
>>>>
>>>> [YOCTO #4100]
>>>>
>>>> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
>>>> ---
>>>> meta/classes/grub-efi.bbclass | 41 ++++++++++++++++++++++++-------------
>>>> meta/conf/machine/qemux86-64.conf | 2 +-
>>>> meta/conf/machine/qemux86.conf | 2 ++
>>>> 3 files changed, 30 insertions(+), 15 deletions(-)
>>>>
>>>> diff --git a/meta/classes/grub-efi.bbclass b/meta/classes/grub-efi.bbclass
>>>> index c6f5d4e..c07e4a1 100644
>>>> --- a/meta/classes/grub-efi.bbclass
>>>> +++ b/meta/classes/grub-efi.bbclass
>>>> @@ -9,6 +9,7 @@
>>>> # External variables
>>>> # ${INITRD} - indicates a filesystem image to use as an initrd (optional)
>>>> # ${ROOTFS} - indicates a filesystem image to include as the root filesystem (optional)
>>>> +# ${GRUB_GFXSERIAL} - set this to 1 to have graphics and serial in the boot menu
>>>> # ${LABELS} - a list of targets for the automatic config
>>>> # ${APPEND} - an override list of append strings for each label
>>>> # ${GRUB_OPTS} - additional options to add to the config, ';' delimited # (optional)
>>>> @@ -16,6 +17,7 @@
>>>>
>>>> do_bootimg[depends] += "grub-efi-${TRANSLATED_TARGET_ARCH}-native:do_deploy"
>>>>
>>>> +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 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.
>
>> 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.
next prev parent reply other threads:[~2013-09-13 21:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 17:19 [PATCH 0/5] Improved EFI boot support Jason Wessel
2013-09-12 17:19 ` [PATCH 1/5] bootimage.bbclass: Move fat image creation into a function Jason Wessel
2013-09-12 17:38 ` Darren Hart
2013-09-12 17:19 ` [PATCH 2/5] cdrtools-native: Update from 3.00 to 3.01a17 Jason Wessel
2013-09-12 17:40 ` Darren Hart
2013-09-12 17:40 ` Saul Wold
2013-09-12 17:19 ` [PATCH 3/5] grub-efi-native: Add support for EFI ISO images Jason Wessel
2013-09-12 17:48 ` Darren Hart
2013-09-12 17:19 ` [PATCH 4/5] bootimage.bbclass: Improve EFI & PCBIOS+EFI ISO support Jason Wessel
2013-09-12 18:09 ` Darren Hart
2013-09-12 20:14 ` Jason Wessel
2013-09-12 20:28 ` Darren Hart
2013-09-12 17:19 ` [PATCH 5/5] grub-efi.bbclass: Add serial and graphics menu options Jason Wessel
2013-09-12 18:01 ` Saul Wold
2013-09-12 18:06 ` Jason Wessel
2013-09-12 18:11 ` Darren Hart
2013-09-12 18:16 ` Darren Hart
2013-09-12 19:52 ` Jason Wessel
2013-09-12 20:09 ` Darren Hart
2013-09-13 21:58 ` Jason Wessel [this message]
2013-09-16 17:49 ` Darren Hart
2013-09-17 12:19 ` Jason Wessel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52338A9D.7000307@windriver.com \
--to=jason.wessel@windriver.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=dvhart@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox