From: Richard Henderson <richard.henderson@linaro.org>
To: Jason Thorpe <thorpej@me.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] qemu-palcode: Changes to support booting NetBSD/alpha
Date: Wed, 14 Oct 2020 14:52:42 -0700 [thread overview]
Message-ID: <c35e151d-7b9c-849f-e4a0-a9c62d9a31a1@linaro.org> (raw)
In-Reply-To: <20201007025229.7487-1-thorpej@me.com>
On 10/6/20 7:52 PM, Jason Thorpe wrote:
> There are additional changes in Qemu itself. Those will be sent as
> a follow-up.
>
> - Change the $a2 value at VM start from "cpu count" to "config word". Bits
> 0-5 are cpu count, and bit 6 communicates the "-nographic" option from
> the VM.
> - Provide a Console Terminal Block in the HWRPB. Initialize this based on
> the location of the PCI VGA, or to the serial port if Qemu has been run
> with "-nographic".
> - Initialize hwrpb.hwrpb.cpuid correctly; it's the WHAMI of the primary CPU,
> not the CPU type.
> - Don't set the "PALcode memory valid" bit in the PCS flags field; those
> HWRPB fields are not, in fact, valid.
> - Allow swppal() to specify the new $pv value. Use this to pass the
> CPU_Restart_data to the cpu spinup entry point.
> - Fix a bug in PCI address configuration that caused the CMD646 IDE registers
> to be mapped incorrectly.
> - When configuring the PCI bus, program system-specific interrupt routing
> information into the PCI device "line" register (as SRM does).
> - When building the PALcode, don't include outside header files; put everything
> that's needed in protos.h.
I'm certainly open to these changes. But it'll need to be split up -- one
patch per bullet, basically.
r~
next prev parent reply other threads:[~2020-10-14 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 2:52 [PATCH] qemu-palcode: Changes to support booting NetBSD/alpha Jason Thorpe
2020-10-14 21:52 ` Richard Henderson [this message]
2020-10-14 23:16 ` Jason Thorpe
2020-10-15 3:32 ` Richard Henderson
2020-10-15 10:58 ` Philippe Mathieu-Daudé
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=c35e151d-7b9c-849f-e4a0-a9c62d9a31a1@linaro.org \
--to=richard.henderson@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thorpej@me.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 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).