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] [RFC] Variable video ram size option
Date: Sat, 10 Jan 2009 08:45:45 +0200	[thread overview]
Message-ID: <f43fc5580901092245v328d1732rf76b73ec6ead63b5@mail.gmail.com> (raw)
In-Reply-To: <4967F942.7040306@eu.citrix.com>

On 1/10/09, Trolle Selander <trolle.selander@eu.citrix.com> wrote:
> Paul Brook wrote:
>
> > On Friday 09 January 2009 12:45:47 Trolle Selander wrote:
> >
> >
> > > +#ifdef TARGET_SPARC
> > > +    vga_ram_size += (1024 * 1024);
> > > +#endif
> > >
> > >
> >
> > This looks pretty bogus.
> >
> >
> >
>  Possibly. The previous static definition added one meg to the default
>  VGA_RAM_SIZE if TARGET_SPARC was set, and I merely wanted to retain that
>  behavior. If someone who is familiar with the SPARC target and knows the
>  reason for the added meg of ram in the previous code can assure that
>  this won't be needed with the configurabe ram patch, I'll be happy to
>  drop that bit.

In 24 bit mode, TCX uses a 32 bit framebuffer, 32 bit control plane
(selects whether 24 bit mode or 8 bit mode is used for each pixel) and
there is still the 8 bit framebuffer, all full screen (1024x768) size.
This translates to 4 + 4 + 1 MB.

I think the -videoram switch should be disabled for targets with fixed
framebuffer hardware in machine description or with:
#if !defined(TARGET_SPARC) || defined(TARGET_SPARC64)

  reply	other threads:[~2009-01-10  6:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 19:45 [Qemu-devel] [PATCH] [RFC] Variable video ram size option Trolle Selander
2009-01-10  0:02 ` Paul Brook
2009-01-10  1:26   ` Trolle Selander
2009-01-10  6:45     ` Blue Swirl [this message]
     [not found]   ` <4967E7D7.4040605@eu.citrix.com>
     [not found]     ` <200901091716.00827.paul@codesourcery.com>
2009-01-10  1:27       ` Trolle Selander
     [not found]       ` <4967ECA7.6040809@eu.citrix.com>
     [not found]         ` <200901091747.06462.paul@codesourcery.com>
2009-01-10  1:28           ` Trolle Selander
2009-01-10  1:47             ` Jamie Lokier
2009-01-11  7:53 ` Avi Kivity
2009-01-12 17:43   ` Trolle Selander
2009-01-21 18:07   ` [Qemu-devel] [PATCH] [RFC] Variable video ram size option - revised Trolle Selander
2009-01-21 18:23     ` Daniel P. Berrange
2009-01-21 21:51       ` Anthony Liguori
2009-01-21 21:21     ` [Qemu-devel] " Trolle Selander
  -- strict thread matches above, loose matches on Subject: below --
2009-01-12 19:13 [Qemu-devel] [PATCH] [RFC] Variable video ram size option Trolle Selander
2009-01-14 20:07 ` Paul Brook
2009-01-14 20:41   ` Trolle Selander
2009-01-14 21:30     ` Paul Brook
2009-01-14 22:47       ` Trolle Selander
2009-01-15 13:08         ` Jamie Lokier
2009-01-15 15:37           ` Rene Rebe
2009-01-15 16:23             ` Jamie Lokier
2009-01-15 17:36               ` Gerd Hoffmann
2009-01-15 20:57                 ` Jamie Lokier
2009-01-15 21:41                   ` Gerd Hoffmann

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=f43fc5580901092245v328d1732rf76b73ec6ead63b5@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).