On 05.11.24 12:42, Michal Orzel wrote:
On 04/11/2024 13:39, Grygorii Strashko wrote:
Hi All,
On 04.11.24 12:49, Michal Orzel wrote:
On 27/09/2024 00:24, Shawn Anastasio wrote:
Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to
bootinfo.reserved_mem") changes the way reser
On 04/11/2024 13:39, Grygorii Strashko wrote:
>
>
> Hi All,
>
> On 04.11.24 12:49, Michal Orzel wrote:
>>
>>
>> On 27/09/2024 00:24, Shawn Anastasio wrote:
>>>
>>>
>>> Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to
>>> bootinfo.reserved_mem") changes the way reserve map regions
On 04.11.24 14:39, Grygorii Strashko wrote:
Hi All,
On 04.11.24 12:49, Michal Orzel wrote:
On 27/09/2024 00:24, Shawn Anastasio wrote:
Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to
bootinfo.reserved_mem") changes the way reserve map regions are tracked,
and as a result br
Hi All,
On 04.11.24 12:49, Michal Orzel wrote:
On 27/09/2024 00:24, Shawn Anastasio wrote:
Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to
bootinfo.reserved_mem") changes the way reserve map regions are tracked,
and as a result broke bootfdt's ability to handle device trees in
On 27/09/2024 00:24, Shawn Anastasio wrote:
>
>
> Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to
> bootinfo.reserved_mem") changes the way reserve map regions are tracked,
> and as a result broke bootfdt's ability to handle device trees in which
> the reserve map and the `reserve
On 27.09.2024 00:24, Shawn Anastasio wrote:
> Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to
> bootinfo.reserved_mem") changes the way reserve map regions are tracked,
> and as a result broke bootfdt's ability to handle device trees in which
> the reserve map and the `reserved-memory`
Commit 53dc37829c31 ("xen/arm: Add DT reserve map regions to
bootinfo.reserved_mem") changes the way reserve map regions are tracked,
and as a result broke bootfdt's ability to handle device trees in which
the reserve map and the `reserved-memory` node contain the same entries
as each other, as is