Cyril Brulebois dixit:
>Thorsten Glaser (2023-11-27):
>> It’s not. The file documents:
>>
>> # To disable CMA allocation entirely, f.e. for a headless setup, set
>> # CMA=0
>
>Well, that's still the intent behind the commit that introduced support
>for that.
But it totally mismatches the
Thorsten Glaser (2023-11-27):
> It’s not. The file documents:
>
> # To disable CMA allocation entirely, f.e. for a headless setup, set
> # CMA=0
Well, that's still the intent behind the commit that introduced support
for that. And since that went into a stable release, I don't see how we
could
Cyril Brulebois dixit:
>Thorsten Glaser (2023-11-26):
>> Package: raspi-firmware
>> Version: 1.20230405+ds-2
>>
>> When I set CMA=0 the cma=… argument in cmdline.txt is omitted.
>
>This is consistent with the documentation in that file.
It’s not. The file documents:
# To disable CMA allocation
Thorsten Glaser (2023-11-26):
> Package: raspi-firmware
> Version: 1.20230405+ds-2
>
> When I set CMA=0 the cma=… argument in cmdline.txt is omitted.
This is consistent with the documentation in that file.
> However, when I manually add cma=0 to cmdline.txt I get this instead:
>
> [
Package: raspi-firmware
Version: 1.20230405+ds-2
When I set CMA=0 the cma=… argument in cmdline.txt is omitted. This
leads to:
[0.00] Memory: 413440K/507904K available (8192K kernel code, 990K rwdata
, 2024K rodata, 1024K init, 252K bss, 28928K reserved, 65536K cma-reserved)
However,
5 matches
Mail list logo
