Re: [U-Boot] [RFC] sandbox: Enable 1:1 map

2018-06-20 Thread Simon Glass
Hi Heinrich, On 20 June 2018 at 20:01, Simon Glass wrote: > Hi Heinrich, > > On 20 June 2018 at 19:23, Heinrich Schuchardt wrote: >> On 06/20/2018 07:51 PM, Simon Glass wrote: >>> Hi Alex, >>> >>> On 14 June 2018 at 17:13, Alexander Graf wrote: So far we've always had a split address

Re: [U-Boot] [RFC] sandbox: Enable 1:1 map

2018-06-20 Thread Simon Glass
Hi Heinrich, On 20 June 2018 at 19:23, Heinrich Schuchardt wrote: > On 06/20/2018 07:51 PM, Simon Glass wrote: >> Hi Alex, >> >> On 14 June 2018 at 17:13, Alexander Graf wrote: >>> So far we've always had a split address space situation with >>> "U-Boot addresses" (a number space starting from

Re: [U-Boot] [RFC] sandbox: Enable 1:1 map

2018-06-20 Thread Heinrich Schuchardt
On 06/20/2018 07:51 PM, Simon Glass wrote: > Hi Alex, > > On 14 June 2018 at 17:13, Alexander Graf wrote: >> So far we've always had a split address space situation with >> "U-Boot addresses" (a number space starting from 0) and "host >> virtual addresses" (128MB mapped randomly in address

Re: [U-Boot] [RFC] sandbox: Enable 1:1 map

2018-06-20 Thread Simon Glass
Hi Alex, On 14 June 2018 at 17:13, Alexander Graf wrote: > So far we've always had a split address space situation with > "U-Boot addresses" (a number space starting from 0) and "host > virtual addresses" (128MB mapped randomly in address space). > > This meant that we had to make sure all code

[U-Boot] [RFC] sandbox: Enable 1:1 map

2018-06-14 Thread Alexander Graf
So far we've always had a split address space situation with "U-Boot addresses" (a number space starting from 0) and "host virtual addresses" (128MB mapped randomly in address space). This meant that we had to make sure all code is properly aware that addresses and pointers are not the same