From: Cory Fields <Cory@atlastechnologiesinc.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Define a new route for sending data to bios
Date: Thu, 12 Feb 2009 12:35:43 -0500 [thread overview]
Message-ID: <200902121235.43112.Cory@atlastechnologiesinc.com> (raw)
> Are these config parameters relevant to platforms other then x86?
Admittedly, I haven't looked beyond x86, so I'm not sure how the other bios
function. Should they be ifdef'd or defined elsewhere?
Cory Fields
next reply other threads:[~2009-02-12 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 17:35 Cory Fields [this message]
2009-02-15 6:49 ` [Qemu-devel] [PATCH] Define a new route for sending data to bios Gleb Natapov
-- strict thread matches above, loose matches on Subject: below --
2009-02-14 23:57 [Qemu-devel] [PATCH 0/4] Option to suppress bios output and prompt (v2) Cory Fields
2009-02-14 23:57 ` [Qemu-devel] [PATCH] Define a new route for sending data to bios Cory Fields
2009-02-12 6:48 [Qemu-devel] [PATCH 0/4] Cory Fields
2009-02-12 6:48 ` [Qemu-devel] [PATCH] Define a new route for sending data to bios Cory Fields
2009-02-12 6:41 ` Gleb Natapov
2009-02-12 15:50 ` 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=200902121235.43112.Cory@atlastechnologiesinc.com \
--to=cory@atlastechnologiesinc.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).