public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Gerd Hoffmann <kraxel@redhat.com>,
	edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [edk2-devel] EDK2 ArmVirtQemu behaviour with multiple UARTs
Date: Mon, 2 Oct 2023 03:51:26 +0200	[thread overview]
Message-ID: <1aee726a-4522-5513-95da-0160d92a1de2@redhat.com> (raw)
In-Reply-To: <CAFEAcA_P5aOTQnM2ARYgR5WvKouvndMbX95XNmDsS0KTxMkMMw@mail.gmail.com>

On 9/21/23 12:50, peter.maydell at linaro.org (Peter Maydell) wrote:

> If you want to play around with this, I have some WIP patches at
> https://git.linaro.org/people/pmaydell/qemu-arm.git uart-edk-investigation
> (content wise they should be fine, but I haven't cleaned them up into
> a coherent set of distinct patches yet, so they're a bit messy.)
> A run of QEMU with both UARTs which sends all output to files looks like:
> 
> ./build/arm-clang/qemu-system-aarch64 -display none -vga none \
>   -machine virt,acpi=on,virtualization=on,mte=on,gic-version=max,iommu=smmuv3 \
>   -smp 2 -m 1024 -cpu max,pauth-impdef=on \
>   -bios ~/linaro/edk2/QEMU_EFI_DEBUG.fd \
>   -drive file=/home/petmay01/avocado/data/cache/by_location/0154b7cd3a4f5e135299060c8cabbeec10b70b6d/alpine-standard-3.17.2-aarch64.iso,format=raw
> \
>   -device virtio-rng-pci,rng=rng0 \
>   -object rng-random,id=rng0,filename=/dev/urandom \
>   -chardev file,id=chr0,path=/tmp/uart0-rev.txt \
>   -chardev file,id=chr1,path=/tmp/uart1-rev.txt \
>   -serial chardev:chr0 -serial chardev:chr1
> 
> (adjust -serial options to taste)

Is the "uart-edk-investigation" branch still the most recent one for
this? (I've not checked it yet, but coming close.)

Thanks
Laszlo



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109241): https://edk2.groups.io/g/devel/message/109241
Mute This Topic: https://groups.io/mt/101498371/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2023-10-02  1:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 10:50 [edk2-devel] EDK2 ArmVirtQemu behaviour with multiple UARTs Peter Maydell
2023-09-21 12:02 ` Ard Biesheuvel
2023-09-28  7:54   ` Laszlo Ersek
2023-09-28 11:24     ` Peter Maydell
2023-09-28 11:50       ` Laszlo Ersek
2023-10-01  9:54         ` Laszlo Ersek
2023-09-21 15:25 ` Gerd Hoffmann
2023-09-21 15:34   ` Peter Maydell
2023-09-21 17:06     ` Gerd Hoffmann
2023-10-02  1:51 ` Laszlo Ersek [this message]
2023-10-02 23:05   ` Laszlo Ersek
2023-10-02 23:14     ` Laszlo Ersek

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-list 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=1aee726a-4522-5513-95da-0160d92a1de2@redhat.com \
    --to=devel@edk2.groups.io \
    /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