On 28/05/2025 19:35, Aaron Kling wrote: >>>> >>>> Friendly reminder to the Tegra maintainers about this question. >>>> >>> In lieu of a response from the Tegra subsystem maintainers, I can only >>> hazard an assumption, Krzysztof. I presume the pstore carveout is >>> bootloader controlled because various stages of the boot stack can >>> dynamically allocate memory, and this became bootloader controlled to >>> prevent any of those from overwriting pstore. I worry about hardcoding >>> an address in the kernel dt, then finding out later that there's an >>> in-use configuration that overwrites or corrupts that section of ram >>> during boot. What are your thoughts on this? And is there any way for >>> this patch to proceed? >> >> I haven't been able to find anything out about this yet. Generally it's >> difficult to get the bootloaders updated for these devices. Tegra194 and >> Tegra234 may be new enough to make an update eventually go into a >> release, but for Tegra186 and older, I honestly wouldn't hold my >> breath. >> >> Thierry > > Krzysztof, based on this response, is there any way or form that the > Tegra186 part of this could be submitted? I can drop the newer > platforms from this patch if Thierry can get a response to his other > reply about how the bootloader could conform. > I don't NAK it. Eventually it is up to platform maintainer if they accept known DTC warnings.
Best regards, Krzysztof
