Hi Laszlo > Are you using the latest edk2? Yes, when I hit the bug, first step was to move to latest edk2. But this didn't helped.
I am not sure, why we are keeping PL011 Fifo mode off in default configuration. Regards Udit > -----Original Message----- > From: Laszlo Ersek <ler...@redhat.com> > Sent: Monday, December 3, 2018 3:27 PM > To: Udit Kumar <udit.ku...@nxp.com>; af...@apple.com > Cc: Ni, Ruiyu <ruiyu...@intel.com>; edk2-devel@lists.01.org; Zeng, Star > <star.z...@intel.com> > Subject: Re: [edk2] Help on boot manager 'Boot Manager Menu' and direct boot > > 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 <ler...@redhat.com> > >> Sent: Thursday, November 29, 2018 11:31 PM > >> To: Udit Kumar <udit.ku...@nxp.com>; af...@apple.com > >> Cc: Ni, Ruiyu <ruiyu...@intel.com>; edk2-devel@lists.01.org; Zeng, Star > >> <star.z...@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 _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
