Hi Alex,
On 14 June 2018 at 13:15, Alexander Graf wrote:
>
>
> On 14.06.18 21:02, Simon Glass wrote:
>> Hi Alex,
>>
>> On 14 June 2018 at 12:22, Alexander Graf wrote:
>>> With efi_loader we do not control payload applications, so we can not
>>> teach them about the difference between virtual and
Hi Heinrich,
On 14 June 2018 at 13:21, Heinrich Schuchardt wrote:
> On 06/14/2018 09:02 PM, Simon Glass wrote:
>> Hi Alex,
>>
>> On 14 June 2018 at 12:22, Alexander Graf wrote:
>>> With efi_loader we do not control payload applications, so we can not
>>> teach them about the difference between v
On 06/14/2018 09:02 PM, Simon Glass wrote:
> Hi Alex,
>
> On 14 June 2018 at 12:22, Alexander Graf wrote:
>> With efi_loader we do not control payload applications, so we can not
>> teach them about the difference between virtual and physical addresses.
>>
>> Instead, let's just always map host v
On 14.06.18 21:02, Simon Glass wrote:
> Hi Alex,
>
> On 14 June 2018 at 12:22, Alexander Graf wrote:
>> With efi_loader we do not control payload applications, so we can not
>> teach them about the difference between virtual and physical addresses.
>>
>> Instead, let's just always map host virt
Hi Alex,
On 14 June 2018 at 12:22, Alexander Graf wrote:
> With efi_loader we do not control payload applications, so we can not
> teach them about the difference between virtual and physical addresses.
>
> Instead, let's just always map host virtual addresses in the efi memory
> map. That way we
With efi_loader we do not control payload applications, so we can not
teach them about the difference between virtual and physical addresses.
Instead, let's just always map host virtual addresses in the efi memory
map. That way we can be sure that all memory allocation functions always
return cons
6 matches
Mail list logo
