On 01/31/2016 04:19 PM, Simon Glass wrote:
Hi Alexander,
On 14 January 2016 at 22:06, Alexander Graf wrote:
When an EFI application runs, it has access to a few descriptor and callback
tables to instruct the EFI compliant firmware to do things for it. The bulk
of those
Hi Alex,
On 1 February 2016 at 16:45, Alexander Graf wrote:
>
>
>
> On 01/31/2016 04:19 PM, Simon Glass wrote:
>>
>> Hi Alexander,
>>
>> On 14 January 2016 at 22:06, Alexander Graf wrote:
>>>
>>> When an EFI application runs, it has access to a few descriptor and
On 02/02/2016 12:54 AM, Simon Glass wrote:
Hi Alex,
On 1 February 2016 at 16:45, Alexander Graf wrote:
On 01/31/2016 04:19 PM, Simon Glass wrote:
Hi Alexander,
On 14 January 2016 at 22:06, Alexander Graf wrote:
When an EFI application runs, it has access
On 01/20/2016 01:16 AM, Leif Lindholm wrote:
On Fri, Jan 15, 2016 at 06:06:10AM +0100, Alexander Graf wrote:
When an EFI application runs, it has access to a few descriptor and callback
tables to instruct the EFI compliant firmware to do things for it. The bulk
of those interfaces are "boot
Hi Alexander,
On 14 January 2016 at 22:06, Alexander Graf wrote:
> When an EFI application runs, it has access to a few descriptor and callback
> tables to instruct the EFI compliant firmware to do things for it. The bulk
> of those interfaces are "boot time services". They handle
On Fri, Jan 15, 2016 at 06:06:10AM +0100, Alexander Graf wrote:
> When an EFI application runs, it has access to a few descriptor and callback
> tables to instruct the EFI compliant firmware to do things for it. The bulk
> of those interfaces are "boot time services". They handle all object
>
When an EFI application runs, it has access to a few descriptor and callback
tables to instruct the EFI compliant firmware to do things for it. The bulk
of those interfaces are "boot time services". They handle all object management,
and memory allocation.
This patch adds support for the boot
7 matches
Mail list logo