From: Conor Dooley <conor@kernel.org>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: stage TC <stagethalescristal@gmail.com>, qemu-riscv@nongnu.org
Subject: Re: qemu icicle kit es
Date: Fri, 13 Jan 2023 12:56:57 +0000 [thread overview]
Message-ID: <2882065D-831B-4E8C-BFD3-677BB8ECA2AD@kernel.org> (raw)
In-Reply-To: <CAEUhbmUa0kCssKBxmkt5qvH5oQmjrbDk_LBb4S2acfGLmzUh5g@mail.gmail.com>
On 13 January 2023 00:35:11 GMT, Bin Meng <bmeng.cn@gmail.com> wrote:
>On Fri, Jan 13, 2023 at 2:03 AM Conor Dooley <conor@kernel.org> wrote:
>>
>> +CC Bin Meng
>>
>> Bin Meng, you're listed as a supporter (in master anyway) but is that
>> still accurate? I figure there's a good chance it isn't anymore?
>> Have you tested the platform from HSS init at all lately?
>
>Yes, I am still maintaining the QEMU PolarFire SoC. The WiKi page
>listed the exact HSS version I tested and if it doesn't, it should be
>a regression in QEMU. If yes, I would like to have a look at that.
That'd be great.
I submitted a few patches for fixing the direct kernel boot & hopefully haven't broken anything!
I'll try to test it also, if I get some time.
>Running more recent HSS is known to break, because QEMU does not
>follow up quite closely with the HSS implementation as HSS has evolved
>quite quickly in the past.
Yeah, although the rate of change has slowed down now.
I think there's a decent but of emulation missing though to get a recent version of the HSS working.
Thanks,
Conor.
next prev parent reply other threads:[~2023-01-13 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 14:21 qemu icicle kit es stage TC
2023-01-11 16:40 ` Conor Dooley
2023-01-12 9:52 ` stage TC
2023-01-12 18:03 ` Conor Dooley
2023-01-13 0:35 ` Bin Meng
2023-01-13 12:56 ` Conor Dooley [this message]
2023-01-14 14:30 ` Conor Dooley
2023-01-19 5:45 ` Bin Meng
2023-01-26 18:51 ` Conor Dooley
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=2882065D-831B-4E8C-BFD3-677BB8ECA2AD@kernel.org \
--to=conor@kernel.org \
--cc=bmeng.cn@gmail.com \
--cc=qemu-riscv@nongnu.org \
--cc=stagethalescristal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.