Re: [PATCH] of/fdt: Make sure no-map does not remove already reserved regions

2021-03-22 Thread Jan Kiszka
On 22.03.21 19:05, Jan Kiszka wrote: > On 22.03.21 08:58, Jan Kiszka wrote: >> On 03.07.19 07:08, Nicolas Boichat wrote: >>> If the device tree is incorrectly configured, and attempts to >>> define a "no-map" reserved memory that overlaps with the kernel >>> data/code, the kernel would crash

Re: [PATCH] of/fdt: Make sure no-map does not remove already reserved regions

2021-03-22 Thread Jan Kiszka
On 22.03.21 08:58, Jan Kiszka wrote: > On 03.07.19 07:08, Nicolas Boichat wrote: >> If the device tree is incorrectly configured, and attempts to >> define a "no-map" reserved memory that overlaps with the kernel >> data/code, the kernel would crash quickly after boot, with no >> obvious clue

Re: [PATCH] of/fdt: Make sure no-map does not remove already reserved regions

2021-03-22 Thread Jan Kiszka
On 03.07.19 07:08, Nicolas Boichat wrote: > If the device tree is incorrectly configured, and attempts to > define a "no-map" reserved memory that overlaps with the kernel > data/code, the kernel would crash quickly after boot, with no > obvious clue about the nature of the issue. > > For

Re: [PATCH] of/fdt: Make sure no-map does not remove already reserved regions

2019-07-21 Thread Nicolas Boichat
On Wed, Jul 17, 2019 at 7:17 AM Florian Fainelli wrote: > > On 7/16/19 4:12 PM, Rob Herring wrote: > > On Tue, Jul 16, 2019 at 4:46 PM Florian Fainelli > > wrote: > >> > >> On 7/2/19 10:08 PM, Nicolas Boichat wrote: > >>> If the device tree is incorrectly configured, and attempts to > >>>

Re: [PATCH] of/fdt: Make sure no-map does not remove already reserved regions

2019-07-16 Thread Florian Fainelli
On 7/16/19 4:12 PM, Rob Herring wrote: > On Tue, Jul 16, 2019 at 4:46 PM Florian Fainelli wrote: >> >> On 7/2/19 10:08 PM, Nicolas Boichat wrote: >>> If the device tree is incorrectly configured, and attempts to >>> define a "no-map" reserved memory that overlaps with the kernel >>> data/code,

Re: [PATCH] of/fdt: Make sure no-map does not remove already reserved regions

2019-07-16 Thread Rob Herring
On Tue, Jul 16, 2019 at 4:46 PM Florian Fainelli wrote: > > On 7/2/19 10:08 PM, Nicolas Boichat wrote: > > If the device tree is incorrectly configured, and attempts to > > define a "no-map" reserved memory that overlaps with the kernel > > data/code, the kernel would crash quickly after boot,

Re: [PATCH] of/fdt: Make sure no-map does not remove already reserved regions

2019-07-16 Thread Florian Fainelli
On 7/2/19 10:08 PM, Nicolas Boichat wrote: > If the device tree is incorrectly configured, and attempts to > define a "no-map" reserved memory that overlaps with the kernel > data/code, the kernel would crash quickly after boot, with no > obvious clue about the nature of the issue. > > For

Re: [PATCH] of/fdt: Make sure no-map does not remove already reserved regions

2019-07-16 Thread Stephen Boyd
Quoting Nicolas Boichat (2019-07-02 22:08:27) > If the device tree is incorrectly configured, and attempts to > define a "no-map" reserved memory that overlaps with the kernel > data/code, the kernel would crash quickly after boot, with no > obvious clue about the nature of the issue. > > For

[PATCH] of/fdt: Make sure no-map does not remove already reserved regions

2019-07-02 Thread Nicolas Boichat
If the device tree is incorrectly configured, and attempts to define a "no-map" reserved memory that overlaps with the kernel data/code, the kernel would crash quickly after boot, with no obvious clue about the nature of the issue. For example, this would happen if we have the kernel mapped at