On Tue, Apr 30, 2024 at 02:18:54PM GMT, Rob Herring (Arm) wrote:
[...]
> diff --git a/arch/arm64/boot/dts/nvidia/tegra210-smaug.dts b/arch/arm64/boot/dts/nvidia/tegra210-smaug.dts
> index 9ebb7369256e..2e5b6b2c1f56 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra210-smaug.dts
> +++ b/arch/arm64/boot/dts/nvidia/tegra210-smaug.dts
> @@ -25,7 +25,7 @@ chosen {
> stdout-path = "serial0:115200n8";
> };
>
> - memory {
> + memory@80000000 {
> device_type = "memory";
> reg = <0x0 0x80000000 0x0 0xc0000000>;
> };
[trimming the recipient list and adding Diogo]
Sorry I just noticed this as I was doing a cleanup path of patchwork.
For tegra210-smaug, unfortunately we can't do this. The problem is that
the firmware for this device looks for a hard-coded /memory device when
updating with the proper memory size and this firmware can't always be
updated.
Diogo, you're one of the few remaining people that I know of that still
use this device (with an upstream kernel). Do you have any more details
about this? Is there any way the firmware can be safely updated on these
devices?
Thierry
Attachment:
signature.asc
Description: PGP signature
