public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Udit Kumar <udit.kumar@nxp.com>, "afish@apple.com" <afish@apple.com>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Zeng, Star" <star.zeng@intel.com>
Subject: Re: Help on boot manager 'Boot Manager Menu' and direct boot
Date: Mon, 3 Dec 2018 10:56:49 +0100	[thread overview]
Message-ID: <3cf90372-14d4-3726-eab3-ab1e87836694@redhat.com> (raw)
In-Reply-To: <VI1PR04MB4640CEBF64ED3314B058C5BD91D30@VI1PR04MB4640.eurprd04.prod.outlook.com>

On 11/30/18 10:13, Udit Kumar wrote:
> Thanks Laszlo/Andrew
> Finally I manage to get logs from user-space,  problem  was fifo of PL011 uart was not getting enable in case of direct boot.
> But in case of boot via UiApp, some piece of code was setting serial port attribute to enable this ( I still to figure out from where). 
> OS rely on boot-loader to enable this bit.

Are you using the latest edk2?

I vaguely recall some refactoring around PL011 (and in general, serial) attributes from a year (or more?) ago. Hmm....

b462f25a21e1 MdeModulePkg/SerialDxe: Describe correctly EFI_DEVICE_ERROR for SetAttributes
13d378fc82d4 MdeModulePkg/SerialDxe: Fix return valued in SerialSetAttributes
7ce5af40c98b MdeModulePkg/SerialDxe: Do not fail reset when SetAttributes is not supported

and

91cc526b15ff MdeModulePkg/SerialDxe: Fix not able to change serial attributes

Thanks
Laszlo

>> -----Original Message-----
>> From: Laszlo Ersek <lersek@redhat.com>
>> Sent: Thursday, November 29, 2018 11:31 PM
>> To: Udit Kumar <udit.kumar@nxp.com>; afish@apple.com
>> Cc: Ni, Ruiyu <ruiyu.ni@intel.com>; edk2-devel@lists.01.org; Zeng, Star
>> <star.zeng@intel.com>
>> Subject: Re: [edk2] Help on boot manager 'Boot Manager Menu' and direct boot
>>
>> On 11/29/18 14:12, Udit Kumar wrote:
>>> Thanks Laszlo,
>>>
>>>
>>>> I can only think of some terminal control sequences that are *not*
>>>> printed to the terminal when you don't enter UiApp manually. I don't
>>>> understand how that could cause the exact symptom you describe, but I have
>> no better explanation.
>>>>
>>>> Can you try other serial communication programs on your desktop? Such
>>>> as "minicom" or "screen"?
>>>
>>> Screen didn't help.
>>> Moreover , using different OS distributions show same similar behavior !!
>>>
>>>> Also, can you try changing your "console=..." kernel param(s)?
>>>
>>> You meant baud-rate ?
>>
>> Yes, and more. The options that the "console=" kernel parameter takes.
>>
>>>
>>> On uefi side,  could you help me if there is some extra information
>>> passed to OS in path UiApp -> BootDevice,
>>
>> I don't think so. Nothing comes to my mind anyway.
>>
>>> I could see , some of additional protocols are installed in above
>>> path, I am not sure if those are used  by  OS or OS Loader (grub in my case)
>> somehow.
>>
>> Well, UiApp generally connects all drivers to all devices -- normally a platform
>> BDS would not want to do this, for the sake of booting quickly --, which likely
>> results in more protocol instances being installed in the system. That shouldn't
>> cause a difference for how serial behaves once the OS has booted.
>>
>> Thanks
>> Laszlo



  reply	other threads:[~2018-12-03  9:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29  1:42 Help on boot manager 'Boot Manager Menu' and direct boot Udit Kumar
2018-11-29  1:52 ` Andrew Fish
2018-11-29  3:09   ` Udit Kumar
2018-11-29 10:21     ` Laszlo Ersek
2018-11-29 13:12       ` Udit Kumar
2018-11-29 18:01         ` Laszlo Ersek
2018-11-30  9:13           ` Udit Kumar
2018-12-03  9:56             ` Laszlo Ersek [this message]
2018-12-03 10:03               ` Udit Kumar
2018-12-03 13:45                 ` Laszlo Ersek
2018-12-03 14:04                   ` Ard Biesheuvel
2018-12-03 14:54                     ` Udit Kumar

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-list 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=3cf90372-14d4-3726-eab3-ab1e87836694@redhat.com \
    --to=devel@edk2.groups.io \
    /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