From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: gaosong <gaosong@loongson.cn>, "Thomas Huth" <thuth@redhat.com>,
"Xiaojuan Yang" <yangxiaojuan@loongson.cn>
Cc: "QEMU devel" <qemu-devel@nongnu.org>
Subject: Re: tests/avocado: Add LoongArch machine start test
Date: Thu, 30 May 2024 14:16:18 +0100 [thread overview]
Message-ID: <bd599efc-1b5a-47a1-b0e9-15c59907a256@app.fastmail.com> (raw)
In-Reply-To: <f2840fc6-0a16-b9ba-937e-f381d2c60bdb@loongson.cn>
在2024年5月30日五月 下午2:00，gaosong写道：
[...]
>> FYI, the test does not seem to work anymore - apparently the binaries
>> have changed and now the hashes do not match anymore. Could you please
>> update it? (preferably with some versioned binaries that do not change
>> in the course of time?)
>>
> Thank you, I had send a patch to fix it.
Hi Song,
As LoongArch EDK2 support has been merged long ago, do you to make a clean
build and add it to pc-bios directory?
Thanks
- Jiaxun
>
> Thanks.
> Song Gao
--
- Jiaxun
next prev parent reply other threads:[~2024-05-30 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 11:19 [PULL 0/5] loongarch-to-apply queue Song Gao
2023-05-15 11:19 ` [PULL 1/5] loongarch: mark loongarch_ipi_iocsr re-entrnacy safe Song Gao
2023-05-15 11:19 ` [PULL 2/5] tests/avocado: Add LoongArch machine start test Song Gao
2024-05-29 10:31 ` Thomas Huth
2024-05-30 13:00 ` gaosong
2024-05-30 13:16 ` Jiaxun Yang [this message]
2024-05-31 1:52 ` gaosong
2024-05-31 5:34 ` Jiaxun Yang
2024-05-31 8:38 ` gaosong
2023-05-15 11:19 ` [PULL 3/5] hw/loongarch/virt: Modify ipi as percpu device Song Gao
2023-05-15 11:19 ` [PULL 4/5] hw/loongarch/virt: Set max 256 cpus support on loongarch virt machine Song Gao
2023-05-15 11:19 ` [PULL 5/5] hw/intc: Add NULL pointer check on LoongArch ipi device Song Gao
2023-05-15 17:13 ` [PULL 0/5] loongarch-to-apply queue Richard Henderson
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=bd599efc-1b5a-47a1-b0e9-15c59907a256@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=gaosong@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=yangxiaojuan@loongson.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).