[PATCH 3/3] configs: CONFIG_CONSOLE_RECORD=y on qemu-riscv64_smode_acpi
Heinrich Schuchardt
heinrich.schuchardt at canonical.com
Thu Nov 6 00:56:25 CET 2025
On 11/6/25 00:10, Tom Rini wrote:
> On Thu, Nov 06, 2025 at 12:07:27AM +0100, Heinrich Schuchardt wrote:
>> On 11/3/25 12:07, Bin Meng wrote:
>>> On Sat, Nov 1, 2025 at 3:59 AM Heinrich Schuchardt
>>> <heinrich.schuchardt at canonical.com> wrote:
>>>>
>>>> For testing ACPI on QEMU we need a defconfig that supports acpi command
>>>> test.
>>>>
>>>> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt at canonical.com>
>>>> ---
>>>> configs/qemu-riscv64_smode_acpi_defconfig | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>
>>> Reviewed-by: Bin Meng <bmeng.cn at gmail.com>
>>
>> For some tests to pass we need to increase CONFIG_CONSOLE_RECORD_OUT_SIZE.
>>
>> The sandbox uses CONFIG_CONSOLE_RECORD_OUT_SIZE=0x6000.
>
> It's worth seeing if we should set a much larger default too, given how
> infrequently it's set:
> $ ./tools/qconfig.py -f CONFIG_CONSOLE_RECORD_OUT_SIZE
> 10 matches
> corstone1000 sandbox64 sandbox64_lwip sandbox sandbox_flattree sandbox_nocmdline sandbox_noinst sandbox_spl sandbox_vpl voyager_spl
>
corstone1000_defconfig and voyager_spl_defconfig seem to be the only
boards relying on the current default value. All other boards explicitly
set higher values.
voyager_spl_defconfig is really odd: Why should
CONFIG_CONSOLE_RECORD_OUT_SIZE_F=0x2000 be larger than
CONFIG_CONSOLE_RECORD_OUT_SIZE=0x400?
Best regards
Heinrich
More information about the U-Boot
mailing list