From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
Graeme Gregory <graeme@xora.org.uk>,
wangyuquan1236@phytium.com.cn, chenbaozi@phytium.com.cn,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/1] hw/arm/sbsa-ref: use XHCI to replace EHCI
Date: Thu, 1 Jun 2023 19:11:52 +0200 [thread overview]
Message-ID: <5b8e5ca1-2fba-6edd-6fa7-14b003ec2ff8@linaro.org> (raw)
In-Reply-To: <CAFEAcA9pUGUa4ev_y3U1z1BdU+AaGGKtRMcQjC5prvWvT9AWEg@mail.gmail.com>
W dniu 1.06.2023 o 18:39, Peter Maydell pisze:
>> So something like below? I only tested does system boot into Debian.
>> To make it work also changes to EDK2 would be needed to list XHCI
>> controller in DSDT.
> Yes, and you also want to drop the useless EHCI controller,
> and (as you note) both these things mean firmware changes
> so presumably that's a version-bump event?
First we need to get two patches through TF-A to get current information
from QEMU. And it takes time.
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/20871
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/20953
next prev parent reply other threads:[~2023-06-01 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 7:02 [PATCH 0/1] hw/arm/sbsa-ref: use XHCI to replace EHCI wangyuquan1236
2023-05-31 7:02 ` [PATCH 1/1] " wangyuquan1236
2023-05-31 14:58 ` Graeme Gregory
2023-05-31 15:27 ` Peter Maydell
2023-05-31 16:23 ` Marcin Juszkiewicz
2023-05-31 16:36 ` Leif Lindholm
2023-05-31 17:12 ` Graeme Gregory
2023-06-01 2:37 ` Chen Baozi
2023-06-01 15:01 ` Peter Maydell
2023-06-01 15:30 ` Marcin Juszkiewicz
2023-06-01 16:39 ` Peter Maydell
2023-06-01 17:11 ` Marcin Juszkiewicz [this message]
2023-06-01 17:59 ` Leif Lindholm
2023-06-01 18:07 ` Ard Biesheuvel
2023-06-02 3:24 ` Yuquan Wang
2023-06-02 9:29 ` Leif Lindholm
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=5b8e5ca1-2fba-6edd-6fa7-14b003ec2ff8@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=chenbaozi@phytium.com.cn \
--cc=graeme@xora.org.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_llindhol@quicinc.com \
--cc=wangyuquan1236@phytium.com.cn \
/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).