Hi Rob,
On 21 September 2017 at 08:22, Rob Clark wrote:
> On Thu, Sep 21, 2017 at 12:58 AM, Simon Glass wrote:
>> Hi,
>>
>> On 20 September 2017 at 08:09, Rob Clark wrote:
>>> On Wed, Sep 20, 2017 at 5:08 AM, Alexander Graf
On Thu, Sep 21, 2017 at 12:58 AM, Simon Glass wrote:
> Hi,
>
> On 20 September 2017 at 08:09, Rob Clark wrote:
>> On Wed, Sep 20, 2017 at 5:08 AM, Alexander Graf wrote:
>>>
>>>
>>> On 14.09.17 00:05, Rob Clark wrote:
Similar to a
> Am 21.09.2017 um 06:58 schrieb Simon Glass :
>
> Hi,
>
>> On 20 September 2017 at 08:09, Rob Clark wrote:
>>> On Wed, Sep 20, 2017 at 5:08 AM, Alexander Graf wrote:
>>>
>>>
On 14.09.17 00:05, Rob Clark wrote:
Similar
Hi,
On 20 September 2017 at 08:09, Rob Clark wrote:
> On Wed, Sep 20, 2017 at 5:08 AM, Alexander Graf wrote:
>>
>>
>> On 14.09.17 00:05, Rob Clark wrote:
>>>
>>> Similar to a "real" UEFI implementation, the bootmgr looks at the
>>> BootOrder and Boot
On Wed, Sep 20, 2017 at 5:08 AM, Alexander Graf wrote:
>
>
> On 14.09.17 00:05, Rob Clark wrote:
>>
>> Similar to a "real" UEFI implementation, the bootmgr looks at the
>> BootOrder and Boot variables to try to find an EFI payload to load
>> and boot. This is added as a
On 14.09.17 00:05, Rob Clark wrote:
Similar to a "real" UEFI implementation, the bootmgr looks at the
BootOrder and Boot variables to try to find an EFI payload to load
and boot. This is added as a sub-command of bootefi.
The idea is that the distro bootcmd would first try loading a
Similar to a "real" UEFI implementation, the bootmgr looks at the
BootOrder and Boot variables to try to find an EFI payload to load
and boot. This is added as a sub-command of bootefi.
The idea is that the distro bootcmd would first try loading a payload
via the bootmgr, and then if that
7 matches
Mail list logo