From: Daniel Palmer <daniel@0x0f.com>
To: visitorckw@gmail.com
Cc: u-boot@lists.denx.de, Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH v2 3/3] doc: board: virt: m68k: Detail how to use debug uart
Date: Mon, 9 Mar 2026 19:51:10 +0900 [thread overview]
Message-ID: <20260309105110.672832-3-daniel@0x0f.com> (raw)
In-Reply-To: <20260309105110.672832-1-daniel@0x0f.com>
Add a paragraph to explain how to get the address of the goldfish
tty and use it as the debug uart. I think the address is actually
fixed right now but it might change in the future.
Signed-off-by: Daniel Palmer <daniel@0x0f.com>
---
doc/board/emulation/qemu-m68k.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/doc/board/emulation/qemu-m68k.rst b/doc/board/emulation/qemu-m68k.rst
index 6c4de54cf6a8..2f2e6bd6444a 100644
--- a/doc/board/emulation/qemu-m68k.rst
+++ b/doc/board/emulation/qemu-m68k.rst
@@ -31,6 +31,16 @@ The minimal QEMU command line to get U-Boot up and running is:
Note that the `-nographic` option is used to redirect the console to stdio,
which connects to the emulated Goldfish TTY device.
+Debugging U-Boot
+----------------
+
+If you need early debugging output enable `CONFIG_DEBUG_UART_GOLDFISH`.
+The base address for the UART can be found by activating the QEMU monitor,
+running `info qtree`, and then looking for the goldfish tty device and
+taking the mmio address.
+
+Baud rate doesn't matter.
+
Hardware Support
----------------
The following QEMU virt peripherals are supported in U-Boot:
--
2.51.0
next prev parent reply other threads:[~2026-03-09 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 10:51 [PATCH v2 1/3] serial: goldfish: Add debug uart support Daniel Palmer
2026-03-09 10:51 ` [PATCH v2 2/3] m68k: m680x0: Initialise the debug uart Daniel Palmer
2026-03-10 5:58 ` Kuan-Wei Chiu
2026-03-10 8:31 ` Angelo Dureghello
2026-03-09 10:51 ` Daniel Palmer [this message]
2026-03-10 6:07 ` [PATCH v2 1/3] serial: goldfish: Add debug uart support Kuan-Wei Chiu
2026-03-10 16:25 ` Tom Rini
2026-03-11 4:08 ` Kuan-Wei Chiu
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=20260309105110.672832-3-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=u-boot@lists.denx.de \
--cc=visitorckw@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox