From: Laszlo Ersek <lersek@redhat.com>
To: Andrew Fish <afish@apple.com>
Cc: Tim Lewis <tim.lewis@insyde.com>,
Leif Lindholm <Leif.Lindholm@arm.com>,
"Carsey, Jaben" <jaben.carsey@intel.com>,
edk2-devel-01 <edk2-devel@ml01.01.org>
Subject: Re: Assert in ShellPkg with latest tianocore edk2 source on the Reference Platform
Date: Wed, 5 Oct 2016 23:06:25 +0200 [thread overview]
Message-ID: <f975531f-7c1d-4be9-6324-12942afc9398@redhat.com> (raw)
In-Reply-To: <F4E91DFF-330E-4642-8218-0E25DCE4D917@apple.com>
On 10/05/16 22:59, Andrew Fish wrote:
>
>> On Oct 5, 2016, at 1:58 PM, Laszlo Ersek <lersek@redhat.com> wrote:
>>
>> On 10/05/16 22:44, Tim Lewis wrote:
>>> Jaben --
>>>
>>> In which cases would you have the Shell protocol present and not have the Unicode Collation protocol?
>>
>> That's exactly the question!
>>
>> According to the spec, at least if the system cannot boot from a disk
>> device, then the collation protocol need not be present.
>>
>>> By my count, the Shell itself cannot function without it (see ProcessCommandLine()).
>>
>> In which case though I don't understand why Daniil experiences this
>> change (= commit 583448b441650) as a regression on Juno. If the shell
>> couldn't function without the collation protocol even before commit
>> 583448b441650, then the shell must never have run on Juno -- because it
>> appears to lack collation -- and then this change cannot be a regression.
>>
>
> Looks like he has a DXE Driver that consume the ShellLib.
That's it, thank you. Daniil named ArmJunoDxe.efi in his second (?) email.
Laszlo
next prev parent reply other threads:[~2016-10-05 21:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 22:51 Assert in ShellPkg with latest tianocore edk2 source on the Reference Platform Supreeth Venkatesh
2016-10-05 15:40 ` Carsey, Jaben
2016-10-05 16:02 ` Shah, Tapan
2016-10-05 19:24 ` Daniil Egranov
2016-10-05 19:46 ` Tim Lewis
2016-10-05 19:48 ` Andrew Fish
2016-10-05 20:17 ` Laszlo Ersek
2016-10-05 20:24 ` Shah, Tapan
2016-10-05 20:34 ` Carsey, Jaben
2016-10-05 20:39 ` Shah, Tapan
2016-10-05 20:44 ` Tim Lewis
2016-10-05 20:58 ` Laszlo Ersek
2016-10-05 20:59 ` Andrew Fish
2016-10-05 21:06 ` Laszlo Ersek [this message]
2016-10-05 21:06 ` Tim Lewis
2016-10-05 21:17 ` Carsey, Jaben
2016-10-05 21:33 ` Tim Lewis
2016-10-05 22:17 ` Carsey, Jaben
2016-10-06 7:22 ` Laszlo Ersek
2016-10-05 21:05 ` Tim Lewis
2016-10-05 20:48 ` Laszlo Ersek
2016-10-05 20:53 ` Daniil Egranov
2016-10-05 21:04 ` Laszlo Ersek
2016-10-05 21:05 ` Andrew Fish
2016-10-05 21:15 ` Carsey, Jaben
2016-10-05 21:20 ` Andrew Fish
2016-10-05 21:25 ` Laszlo Ersek
2016-10-05 21:42 ` Daniil Egranov
2016-10-05 21:18 ` Laszlo Ersek
2016-10-05 21:34 ` Kinney, Michael D
2016-10-05 21:48 ` Laszlo Ersek
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=f975531f-7c1d-4be9-6324-12942afc9398@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