Hi Alexandre,
On Friday 07 May 2021 at 17:15:20 (+0200), Alexandre TORGUE wrote:
> Did you get time to continue some tests on this issue ?
I did try a few things, but still fail to reproduced :/
> On my side this DT is not working:
>
> memory@c000 {
> reg = <0xc000 0x2000>;
On Wednesday 21 Apr 2021 at 08:17:28 (-0700), Florian Fainelli wrote:
> 5.10.31 works correctly and shows the following for my platform:
>
> 4000-fdffefff : System RAM
> 4020-40ea : Kernel code
> 40eb-4237 : reserved
> 4238-425a : Kernel data
> 4500-450f
On Wednesday 21 Apr 2021 at 07:33:52 (-0700), Florian Fainelli wrote:
> It is not, otherwise I would have noticed earlier, can you try the same
> thing that happens on my platform with a reserved region (without
> no-map) adjacent to a reserved region with 'no-map'?
I just tried, but still no luck
On Wednesday 21 Apr 2021 at 08:31:00 (+), Quentin Perret wrote:
> FWIW I did test this on Qemu before posting. With 5.12-rc8 and a 1MiB
> no-map region at 0x8000, I have the following:
>
> 4000-7fff : System RAM
> 4021-417f : Kernel code
> 4180-4
On Tuesday 20 Apr 2021 at 09:33:56 (-0700), Florian Fainelli wrote:
> I do wonder as well, we have a 32MB "no-map" reserved memory region on
> our platforms located at 0xfe00. Without the offending commit,
> /proc/iomem looks like this:
>
> 4000-fdffefff : System RAM
> 40008000-40ff
