From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: maobibo <maobibo@loongson.cn>
Cc: gaosong@loongson.cn, jiaxun.yang@flygoat.com,
qemu-devel@nongnu.org, thomas@t-8ch.de, xry111@xry111.site
Subject: Re: [PATCH v2] hw/loongarch: virt: support up to 4 serial ports
Date: Sat, 7 Sep 2024 16:57:56 +0200 [thread overview]
Message-ID: <Ztxp9BxTAyao6cb7@zx2c4.com> (raw)
In-Reply-To: <Ztxm3YFqC-PlN94K@zx2c4.com>
On Sat, Sep 07, 2024 at 04:44:45PM +0200, Jason A. Donenfeld wrote:
> On Sat, Sep 07, 2024 at 11:37:09AM +0800, maobibo wrote:
> > Hi Jason,
> >
> > It works well with ELF kernel, however it fails to boot with UEFI BIOS.
> > Maybe it is problem of UEFI BIOS, can we create UART in reverse order?
> > so that it can work well on both ELF kernel and UEFI BIOS.
> >
> > Also for develops they usually use as earlycon with command line
> > -serial stdio --append "... earlycon=uart,mmio,0x1fe001e0", this
> > requires to uart with address 0x1fe001e0 as the first serial port.
> >
> > Just small code base your patch like this:
> >
> > - for (i = 0; i < VIRT_UART_COUNT; ++i) {
> > + for (i = VIRT_UART_COUNT - 1; i >= 0; i--) {
> > hwaddr base = VIRT_UART_BASE + i * VIRT_UART_SIZE;
> > int irq = VIRT_UART_IRQ + i - VIRT_GSI_BASE;
> > serial_mm_init(get_system_memory(), base, 0,
> > qdev_get_gpio_in(pch_pic, irq),
> > - 115200, serial_hd(VIRT_UART_COUNT - 1 - i),
> > + 115200, serial_hd(i),
> > DEVICE_LITTLE_ENDIAN);
> > - fdt_add_uart_node(lvms, pch_pic_phandle, base, irq, i ==
> > VIRT_UART_COUNT - 1 - i);
> > + fdt_add_uart_node(lvms, pch_pic_phandle, base, irq, i == 0);
> > }
>
> Fixed: https://lore.kernel.org/all/20240907143439.2792924-1-Jason@zx2c4.com/
By the way, I don't know who is picking patches into which development
tree from the list, but this is starting to be kind of a lot of patches,
so I've queued them all up here:
https://git.zx2c4.com/qemu/log/?h=loongarch64
In case that makes it easier for whoever the maintainer is to pick them.
next prev parent reply other threads:[~2024-09-07 14:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1738d60a-df3a-4102-b1da-d16a29b6e06a@t-8ch.de>
2023-10-10 1:12 ` qemu direct kernel boot on LoongArch maobibo
2024-09-05 3:12 ` Jason A. Donenfeld
2024-09-05 3:45 ` maobibo
2024-09-05 4:04 ` Jason A. Donenfeld
2024-09-05 5:25 ` Thomas Weißschuh
2024-09-05 6:11 ` maobibo
2024-09-05 14:54 ` Jason A. Donenfeld
2024-09-05 15:49 ` Jason A. Donenfeld
2024-09-06 1:09 ` maobibo
2024-09-05 14:53 ` Jason A. Donenfeld
2024-09-05 15:05 ` Thomas Weißschuh
2024-09-05 15:07 ` Jason A. Donenfeld
2024-09-05 15:16 ` Thomas Weißschuh
2024-09-05 15:18 ` Jason A. Donenfeld
2024-09-05 16:03 ` Thomas Weißschuh
2024-09-06 1:14 ` maobibo
2024-09-06 4:04 ` Jason A. Donenfeld
2024-09-06 4:48 ` Jason A. Donenfeld
2024-09-06 4:49 ` [PATCH] hw/loongarch: virt: support up to 4 serial ports Jason A. Donenfeld
2024-09-06 8:34 ` maobibo
2024-09-06 14:30 ` Jason A. Donenfeld
2024-09-06 14:31 ` [PATCH v2] " Jason A. Donenfeld
2024-09-07 3:37 ` maobibo
2024-09-07 14:44 ` Jason A. Donenfeld
2024-09-07 14:57 ` Jason A. Donenfeld [this message]
2024-09-07 14:34 ` [PATCH v3] " Jason A. Donenfeld
2024-09-09 1:22 ` maobibo
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=Ztxp9BxTAyao6cb7@zx2c4.com \
--to=jason@zx2c4.com \
--cc=gaosong@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=maobibo@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=thomas@t-8ch.de \
--cc=xry111@xry111.site \
/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;
as well as URLs for NNTP newsgroup(s).