From: Paul Brook <paul@nowt.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [7086] Allocate enough vram for 24-bit planes.
Date: Sat, 11 Apr 2009 16:55:45 +0000 [thread overview]
Message-ID: <E1LsgUb-0003dh-BD@cvs.savannah.gnu.org> (raw)
Revision: 7086
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=7086
Author: pbrook
Date: 2009-04-11 16:55:44 +0000 (Sat, 11 Apr 2009)
Log Message:
-----------
Allocate enough vram for 24-bit planes.
Signed-off-by: Paul Brook <paul@codesourcery.com>
Modified Paths:
--------------
trunk/hw/tcx.c
Modified: trunk/hw/tcx.c
===================================================================
--- trunk/hw/tcx.c 2009-04-11 14:47:08 UTC (rev 7085)
+++ trunk/hw/tcx.c 2009-04-11 16:55:44 UTC (rev 7086)
@@ -506,7 +506,7 @@
int size;
uint8_t *vram_base;
- vram_offset = qemu_ram_alloc(vram_size);
+ vram_offset = qemu_ram_alloc(vram_size * (1 + 4 + 4));
vram_base = qemu_get_ram_ptr(vram_offset);
s = qemu_mallocz(sizeof(TCXState));
reply other threads:[~2009-04-11 16:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1LsgUb-0003dh-BD@cvs.savannah.gnu.org \
--to=paul@nowt.org \
--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).