qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 1/6] Use IO port for qemu<->guest BIOS communication.
Date: Sun, 31 Aug 2008 14:40:00 +0300	[thread overview]
Message-ID: <f43fc5580808310440t213dd720q75e4df1be8e155c1@mail.gmail.com> (raw)
In-Reply-To: <20080831111206.GF6192@minantech.com>

On 8/31/08, Gleb Natapov <gleb@qumranet.com> wrote:
> On Sat, Aug 30, 2008 at 10:57:34PM +0300, Blue Swirl wrote:
>  > On 8/29/08, Gleb Natapov <gleb@qumranet.com> wrote:
>  > > On Thu, Aug 28, 2008 at 09:04:11PM +0300, Blue Swirl wrote:
>  > >  > On 8/28/08, Gleb Natapov <gleb@qumranet.com> wrote:
>  > >  > >  +    fw_cfg_add(fw_cfg, FW_CFG_ID, (uint8_t *)&bios_cfg_id,
>  > >  > >  +               sizeof(bios_cfg_id));
>  > >  >
>  > >  > On second thought, this is in host byte order, which is not a good idea.
>  > >  >
>  > >
>  > > Is there some function to convert from host byte order to target byte
>  > >  order?
>  >
>  > I made an updated version of the patch 1/6, with explicit little
>  > endian conversions. I'm not very happy with that. Another way would be
>  > to add functions just to put different size numbers into device and
>  > they would hide the conversion.
>  >
>
> So what approach we should go with? We can go with the second one (add
>  functions for each type) and extend interface as needed.

Okay, I'll make a new version.

  reply	other threads:[~2008-08-31 11:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 16:52 [Qemu-devel] [PATCH v3 0/6] Add UUID command-line option Gleb Natapov
2008-08-28 16:52 ` [Qemu-devel] [PATCH v3 1/6] Use IO port for qemu<->guest BIOS communication Gleb Natapov
2008-08-28 17:57   ` Blue Swirl
2008-08-28 18:04   ` Blue Swirl
2008-08-29 19:00     ` Gleb Natapov
2008-08-29 19:26       ` Blue Swirl
2008-08-30 19:57       ` Blue Swirl
2008-08-31 11:12         ` Gleb Natapov
2008-08-31 11:40           ` Blue Swirl [this message]
2008-08-31 12:45           ` Blue Swirl
2008-08-31 13:02             ` Gleb Natapov
2008-08-31 13:39               ` Blue Swirl
2008-08-31 14:18                 ` Gleb Natapov
2008-08-31 18:41                   ` Blue Swirl
2008-08-31 19:24                     ` Gleb Natapov
2008-08-28 16:52 ` [Qemu-devel] [PATCH v3 2/6] Add -uuid command line option Gleb Natapov
2008-08-28 16:52 ` [Qemu-devel] [PATCH v3 3/6] Add "info uuid" command to monitor Gleb Natapov
2008-08-28 16:52 ` [Qemu-devel] [PATCH v3 4/6] Use libuuid if available Gleb Natapov
2008-08-28 16:52 ` [Qemu-devel] [PATCH v3 5/6] Add UUID to firmware configuration info Gleb Natapov
2008-08-28 16:53 ` [Qemu-devel] [PATCH v3 6/6] Pass cpu speed into SM BIOS Gleb Natapov

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=f43fc5580808310440t213dd720q75e4df1be8e155c1@mail.gmail.com \
    --to=blauwirbel@gmail.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).