Hi Michal,
> On 17 Jul 2025, at 14:00, Orzel, Michal wrote:
>
>
>
> On 17/07/2025 14:58, Hari Limaye wrote:
>> Hi Michal,
>>
>>> On 17 Jul 2025, at 13:54, Orzel, Michal wrote:
+/*
+ * DTB starting at a different address has been mapped, so destroy
this
+ * be
On 17/07/2025 14:58, Hari Limaye wrote:
> Hi Michal,
>
>> On 17 Jul 2025, at 13:54, Orzel, Michal wrote:
>>> +/*
>>> + * DTB starting at a different address has been mapped, so destroy this
>>> + * before continuing.
>> I don't understand this scenario. Can you describe it in more
Hi Michal,
> On 17 Jul 2025, at 13:54, Orzel, Michal wrote:
>> +/*
>> + * DTB starting at a different address has been mapped, so destroy this
>> + * before continuing.
> I don't understand this scenario. Can you describe it in more details?
> I know that early_fdt_map will be called
On 15/07/2025 09:45, Hari Limaye wrote:
> From: Luca Fancellu
>
> Implement the function early_fdt_map(), which is responsible for mapping
> the Device Tree Blob in the early stages of the boot process, for MPU
> systems.
>
> We make use of the map_pages_to_xen() and destroy_xen_mappings() AP
From: Luca Fancellu
Implement the function early_fdt_map(), which is responsible for mapping
the Device Tree Blob in the early stages of the boot process, for MPU
systems.
We make use of the map_pages_to_xen() and destroy_xen_mappings() APIs.
In particular the latter function is necessary in the
