From: Andre Przywara <andre.przywara@amd.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] add missing firmware configuration channel numbers to BIOS
Date: Mon, 22 Dec 2008 10:36:30 +0100 [thread overview]
Message-ID: <494F5F9E.1020801@amd.com> (raw)
In-Reply-To: <f43fc5580812212229q6bc10785ne84768f99e479383@mail.gmail.com>
Blue Swirl wrote:
>>
>> although we currently don't use firmware config channel
>> numbers higher than '0x02' in the PC-BIOS, add the channel
>> names to the BIOS source to mark already used entries.
>> This will make picking new number easier in the future.
>
> Isn't it possible to use fw_cfg.h directly? To get just the constants,
> you can use NO_QEMU_PROTOS.
Nice idea, but this would require to have the QEMU sources directly
available when building the BIOS ROM. This is not a real problem, but
would require to pull in the QEMU source path from the BOCHS autotools
Makefile (with what default? Revert to the current code if no QEMU
source path is given?). Currently you can build the BIOS independently
with just the QEMU patches applied. If you (or Anthony) think this OK,
I'd prepare a patch for this.
Regards,
Andre.
>
> This is how it is used in OpenBIOS/Sparc64 as an example:
>
> http://tracker.coreboot.org/trac/openbios/browser/openbios-devel/arch/sparc64/entry.S#L14
>
> http://tracker.coreboot.org/trac/openbios/browser/openbios-devel/arch/sparc64/openbios.c#L29
>
next prev parent reply other threads:[~2008-12-22 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 23:49 [Qemu-devel] [PATCH] add missing firmware configuration channel numbers to BIOS Andre Przywara
2008-12-22 6:29 ` Blue Swirl
2008-12-22 9:36 ` Andre Przywara [this message]
2008-12-22 10:34 ` Blue Swirl
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=494F5F9E.1020801@amd.com \
--to=andre.przywara@amd.com \
--cc=qemu-devel@nongnu.org \
/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).