On 02/24/2016 06:01 PM, Stephen Warren wrote:
On 02/24/2016 03:55 AM, Alexander Graf wrote:
On 23.02.16 14:17, Simon Glass wrote:
Hi Alex,
On 21 February 2016 at 18:57, Alexander Graf wrote:
The idea to generate our pages tables from an array of memory ranges
is very sound. However, instea
On 02/24/2016 03:55 AM, Alexander Graf wrote:
On 23.02.16 14:17, Simon Glass wrote:
Hi Alex,
On 21 February 2016 at 18:57, Alexander Graf wrote:
The idea to generate our pages tables from an array of memory ranges
is very sound. However, instead of hard coding the code to create up
to 2 lev
On 02/23/2016 09:42 PM, Simon Glass wrote:
Hi Stephen,
On 23 February 2016 at 13:33, Stephen Warren wrote:
On 02/23/2016 01:00 PM, Simon Glass wrote:
Hi Stephen,
On 23 February 2016 at 10:40, Stephen Warren
wrote:
On 02/23/2016 10:30 AM, Simon Glass wrote:
Hi Stephen,
On 23 February
On 23.02.16 14:17, Simon Glass wrote:
> Hi Alex,
>
> On 21 February 2016 at 18:57, Alexander Graf wrote:
>> The idea to generate our pages tables from an array of memory ranges
>> is very sound. However, instead of hard coding the code to create up
>> to 2 levels of 64k granule page tables, we
On 22.02.16 19:45, Stephen Warren wrote:
> On 02/22/2016 11:37 AM, Alexander Graf wrote:
>>
>> On Feb 22, 2016, at 7:18 PM, Stephen Warren
>> wrote:
>>
>>> On 02/21/2016 06:57 PM, Alexander Graf wrote:
The idea to generate our pages tables from an array of memory ranges
is very sound.
Hi Stephen,
On 23 February 2016 at 13:33, Stephen Warren wrote:
> On 02/23/2016 01:00 PM, Simon Glass wrote:
>>
>> Hi Stephen,
>>
>> On 23 February 2016 at 10:40, Stephen Warren
>> wrote:
>>>
>>> On 02/23/2016 10:30 AM, Simon Glass wrote:
Hi Stephen,
On 23 February 2016
On 02/23/2016 01:00 PM, Simon Glass wrote:
Hi Stephen,
On 23 February 2016 at 10:40, Stephen Warren wrote:
On 02/23/2016 10:30 AM, Simon Glass wrote:
Hi Stephen,
On 23 February 2016 at 10:21, Stephen Warren
wrote:
On 02/23/2016 06:17 AM, Simon Glass wrote:
Hi Alex,
On 21 February 201
Hi Stephen,
On 23 February 2016 at 10:40, Stephen Warren wrote:
> On 02/23/2016 10:30 AM, Simon Glass wrote:
>>
>> Hi Stephen,
>>
>> On 23 February 2016 at 10:21, Stephen Warren
>> wrote:
>>>
>>> On 02/23/2016 06:17 AM, Simon Glass wrote:
Hi Alex,
On 21 February 2016 at
On 02/23/2016 10:30 AM, Simon Glass wrote:
Hi Stephen,
On 23 February 2016 at 10:21, Stephen Warren wrote:
On 02/23/2016 06:17 AM, Simon Glass wrote:
Hi Alex,
On 21 February 2016 at 18:57, Alexander Graf wrote:
The idea to generate our pages tables from an array of memory ranges
is very
Hi Stephen,
On 23 February 2016 at 10:21, Stephen Warren wrote:
> On 02/23/2016 06:17 AM, Simon Glass wrote:
>>
>> Hi Alex,
>>
>> On 21 February 2016 at 18:57, Alexander Graf wrote:
>>>
>>> The idea to generate our pages tables from an array of memory ranges
>>> is very sound. However, instead o
On 02/23/2016 06:17 AM, Simon Glass wrote:
Hi Alex,
On 21 February 2016 at 18:57, Alexander Graf wrote:
The idea to generate our pages tables from an array of memory ranges
is very sound. However, instead of hard coding the code to create up
to 2 levels of 64k granule page tables, we really sh
Hi Alex,
On 21 February 2016 at 18:57, Alexander Graf wrote:
> The idea to generate our pages tables from an array of memory ranges
> is very sound. However, instead of hard coding the code to create up
> to 2 levels of 64k granule page tables, we really should just create
> normal 4k page tables
On 02/22/2016 11:37 AM, Alexander Graf wrote:
On Feb 22, 2016, at 7:18 PM, Stephen Warren wrote:
On 02/21/2016 06:57 PM, Alexander Graf wrote:
The idea to generate our pages tables from an array of memory ranges
is very sound. However, instead of hard coding the code to create up
to 2 levels
On 02/21/2016 06:57 PM, Alexander Graf wrote:
The idea to generate our pages tables from an array of memory ranges
is very sound. However, instead of hard coding the code to create up
to 2 levels of 64k granule page tables, we really should just create
normal 4k page tables that allow us to set c
On Feb 22, 2016, at 7:18 PM, Stephen Warren wrote:
> On 02/21/2016 06:57 PM, Alexander Graf wrote:
>> The idea to generate our pages tables from an array of memory ranges
>> is very sound. However, instead of hard coding the code to create up
>> to 2 levels of 64k granule page tables, we really
On 02/21/2016 06:57 PM, Alexander Graf wrote:
The idea to generate our pages tables from an array of memory ranges
is very sound. However, instead of hard coding the code to create up
to 2 levels of 64k granule page tables, we really should just create
normal 4k page tables that allow us to set c
The idea to generate our pages tables from an array of memory ranges
is very sound. However, instead of hard coding the code to create up
to 2 levels of 64k granule page tables, we really should just create
normal 4k page tables that allow us to set caching attributes on 2M
or 4k level later on.
S
17 matches
Mail list logo