All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Richard Henderson <rth@twiddle.net>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, v2] vga: Fix type of lfb/map_addr/end.
Date: Sat, 23 Jul 2011 11:50:22 -0500	[thread overview]
Message-ID: <4E2AFBCE.90406@codemonkey.ws> (raw)
In-Reply-To: <1308081188-19695-1-git-send-email-rth@twiddle.net>

On 06/14/2011 02:53 PM, Richard Henderson wrote:
> These addresses have been passed through pci_to_cpu_addr,
> and thus need to be full target_phys_addr_t.
>
> Signed-off-by: Richard Henderson<rth@twiddle.net>
> Cc: Jan Kiszka<jan.kiszka@siemens.com>

Applied.  Thanks.

Regards,

Anthony Liguori

> ---
>
>   V1->V2:
> 	lfb_addr/end also widened to guest address width.
>
>   hw/vga_int.h |   10 +++++-----
>   1 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/hw/vga_int.h b/hw/vga_int.h
> index d2811bd..eee91a8 100644
> --- a/hw/vga_int.h
> +++ b/hw/vga_int.h
> @@ -106,13 +106,13 @@ typedef void (* vga_update_retrace_info_fn)(struct VGACommonState *s);
>   typedef struct VGACommonState {
>       uint8_t *vram_ptr;
>       ram_addr_t vram_offset;
> +    target_phys_addr_t lfb_addr;
> +    target_phys_addr_t lfb_end;
> +    target_phys_addr_t map_addr;
> +    target_phys_addr_t map_end;
>       uint32_t vram_size;
> -    uint32_t lfb_addr;
> -    uint32_t lfb_end;
> -    uint32_t map_addr;
> -    uint32_t map_end;
> -    uint32_t lfb_vram_mapped; /* whether 0xa0000 is mapped as ram */
>       uint32_t latch;
> +    uint32_t lfb_vram_mapped; /* whether 0xa0000 is mapped as ram */
>       uint8_t sr_index;
>       uint8_t sr[256];
>       uint8_t gr_index;

      parent reply	other threads:[~2011-07-23 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 19:53 [Qemu-devel] [PATCH, v2] vga: Fix type of lfb/map_addr/end Richard Henderson
2011-06-15  7:27 ` Jan Kiszka
2011-07-23 16:50 ` Anthony Liguori [this message]

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=4E2AFBCE.90406@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.