From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de, Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
Anatolij Gustschin <agust@denx.de>, Tom Rini <trini@konsulko.com>,
Bin Meng <bmeng.cn@gmail.com>, Asherah Connor <ashe@kivikakk.ee>,
Alexander Graf <agraf@csgraf.de>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PATCH v2 7/7] x86: qemu: Enable ramfb by default
Date: Mon, 28 Aug 2023 18:40:10 +0300 [thread overview]
Message-ID: <69354e85-2c73-4623-b286-e4820aef494b@gmail.com> (raw)
In-Reply-To: <CAPnjgZ36NmL0jkHaRyeCSQQm78bDaYwei84WVLt32-ZX0M_J1w@mail.gmail.com>
On 2023-08-22 21:56 +03:00, Simon Glass wrote:
> Hi Alper,
>
> On Tue, 22 Aug 2023 at 06:10, Alper Nebi Yasak <alpernebiyasak@gmail.com> wrote:
>>
>> Now that we have everything in place to support ramfb, let's wire it up
>> by default in the x86 QEMU targets. That way, we can use ramfb graphical
>> console instead of the default by passing -vga none -device ramfb to the
>> QEMU command line.
>>
>> Also increase SYS_MALLOC_F_LEN for QEMU x86_64 to be the same as its SPL
>> counterpart, because we're running out of alloc space in pre-reloc stage
>> with ramfb enabled.
>>
>> Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
>> ---
>> This also suffers from the same issue with distros as the Bochs display
>> driver [1], where it results in a hang after GRUB menu selection before
>> the kernel can display anything. Couldn't reproduce on arm*/riscv*.
>
> Yes I see that problem too. I wonder how we can debug it?
No idea, and I couldn't find a good commit to bisect from, tried as far
back as v2021.10.
>> But just having it enabled doesn't seem to cause problems unless you run
>> QEMU with -device ramfb, so this (unlike the Bochs video driver) can
>> actually be co-enabled with VIDEO_VESA.
>
> Indeed...which makes me wonder if we can do something similar with
> Bochs, so that (from the cmdline) it is possible to chose ramfb, bochs
> or vesa?
(Tried to answer video choice and DT concerns in another mail)
>> [1] https://lore.kernel.org/u-boot/20230724145210.304917-4-sjg@chromium.org/
>>
>> Changes in v2:
>> - Add patch "x86: qemu: Enable ramfb by default"
>>
>> arch/x86/cpu/qemu/Kconfig | 4 +++
>> board/emulation/qemu-x86/qemu-x86.c | 47 +++++++++++++++++++++++++++++
>> configs/qemu-x86_64_defconfig | 4 +--
>> configs/qemu-x86_defconfig | 1 -
>> 4 files changed, 52 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/x86/cpu/qemu/Kconfig b/arch/x86/cpu/qemu/Kconfig
>> index f8f2f6473088..e0a57ac2d687 100644
>> --- a/arch/x86/cpu/qemu/Kconfig
>> +++ b/arch/x86/cpu/qemu/Kconfig
>> @@ -13,6 +13,10 @@ config QEMU
>> imply USB
>> imply USB_EHCI_HCD
>> imply VIDEO_VESA
>> + imply VIDEO_RAMFB
>> + imply BOARD_EARLY_INIT_F
>> + imply BOARD_EARLY_INIT_R
>> + imply CMD_QFW
>>
>> if QEMU
>>
>> [...]
>>
>> @@ -59,7 +58,6 @@ CONFIG_CMD_USB=y
>> CONFIG_BOOTP_BOOTFILESIZE=y
>> CONFIG_CMD_EFIDEBUG=y
>> CONFIG_CMD_TIME=y
>> -CONFIG_CMD_QFW=y
>
> What is happening here? Why disable it?
I used `imply CMD_QFW` above to be consistent with previous patches, so
it's no longer necessary in defconfigs. Should I drop the imply and keep
these in defconfig?
next prev parent reply other threads:[~2023-08-28 15:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 12:10 [PATCH v2 0/7] Add support for QEMU's ramfb display Alper Nebi Yasak
2023-08-22 12:10 ` [PATCH v2 1/7] qfw: Add WRITE definition Alper Nebi Yasak
2023-08-22 12:10 ` [PATCH v2 2/7] ramfb: Add driver for ramfb display Alper Nebi Yasak
2023-08-22 18:56 ` Simon Glass
2023-08-22 12:10 ` [PATCH v2 3/7] qfw: Spawn ramfb device if its file is present Alper Nebi Yasak
2023-08-22 18:56 ` Simon Glass
2023-08-28 10:33 ` Alper Nebi Yasak
2023-08-22 12:10 ` [PATCH v2 4/7] qfw: Add flag to allow probing before relocation Alper Nebi Yasak
2023-08-22 18:56 ` Simon Glass
2023-08-28 15:22 ` Alper Nebi Yasak
2023-08-28 15:27 ` Tom Rini
2023-08-22 12:10 ` [PATCH v2 5/7] arm: qemu: Enable ramfb by default Alper Nebi Yasak
2023-08-22 18:56 ` Simon Glass
2023-08-28 15:46 ` Alper Nebi Yasak
2023-08-28 17:54 ` Simon Glass
2023-08-28 18:28 ` Alper Nebi Yasak
2023-08-28 20:32 ` Alexander Graf
2023-08-28 20:38 ` Simon Glass
2023-08-28 20:56 ` Alexander Graf
2023-08-22 12:10 ` [PATCH v2 6/7] riscv: " Alper Nebi Yasak
2023-08-22 18:56 ` Simon Glass
2023-08-22 12:10 ` [PATCH v2 7/7] x86: " Alper Nebi Yasak
2023-08-22 18:56 ` Simon Glass
2023-08-28 15:40 ` Alper Nebi Yasak [this message]
2023-08-28 15:47 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69354e85-2c73-4623-b286-e4820aef494b@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=agraf@csgraf.de \
--cc=agust@denx.de \
--cc=ashe@kivikakk.ee \
--cc=bmeng.cn@gmail.com \
--cc=mark.kettenis@xs4all.nl \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=tuomas.tynkkynen@iki.fi \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.