From: Derek Fawcus <dfawcus@cisco.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: RFC for new features
Date: Sat, 10 Jul 2004 01:38:45 +0100 [thread overview]
Message-ID: <20040710013845.L10322@edinburgh.cisco.com> (raw)
In-Reply-To: <1089411210.59382.215.camel@pcgem.rdg.cyberkinetica.com>; from antony.t.curtis@ntlworld.com on Fri, Jul 09, 2004 at 11:13:30PM +0100
On Fri, Jul 09, 2004 at 11:13:30PM +0100, Antony T Curtis wrote:
> > 2) There are device emulation issues :
> > The current cirrusvga is a vast improvement over the previous bochs
> > device. However, pushing available memory to more than 4 Mb wold allow for
> > better resolutions : 1024x768x16 is a bit limiting in some uses.
Huh - I don't think there are any specific pitch restrictions on this chipset.
4M should allow 1280x1024@24bpp (or 1152x864@32bpp). Is that not enougth?
> Well - the CL-GD544X chips can only handle 4MB of memory, maximum. For
> larger framebuffers, we would have to emulate a different video chip -
> If we wish to stick to Cirrus Logic, The Laguna CL-GD546x chips can
> address up to 16MB I think....
Nope. Only 8M. The architecture has scope for 2 RAMBUS channels, but they
only implemented chips with 1 RAMBUS channel. One of the fields in the
channel control register is 3 bits, identifying the number of 1M ram banks
available... (Someone who has spent too long playing with Laguna chips).
Besides, the Laguna is a more complex beast with a 3 operand BitBLT engine...
DF
next prev parent reply other threads:[~2004-07-10 0:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 18:14 [Qemu-devel] RFC for new features Fabrice Bellard
2004-07-08 18:46 ` [Qemu-devel] " Emmanuel Charpentier
2004-07-08 18:58 ` Antony T Curtis
2004-07-08 19:05 ` Julian Seward
2004-07-08 19:47 ` Jim C. Brown
2004-07-08 18:54 ` [Qemu-devel] " Antony T Curtis
2004-07-08 19:36 ` Jim C. Brown
2004-07-08 20:31 ` Jernej Simončič
2004-07-08 21:04 ` Jim C. Brown
2004-07-08 22:37 ` Jernej Simončič
2004-07-08 22:57 ` Jim C. Brown
2004-07-09 0:15 ` [Qemu-devel] RFC for new features (Console under Windows) Filip Navara
2004-07-08 23:40 ` OT: Re: [Qemu-devel] RFC for new features Antony T Curtis
2004-07-08 19:45 ` Jocelyn Mayer
2004-07-08 19:00 ` Karel Gardas
2004-07-08 21:44 ` vaise
2004-07-08 19:30 ` Jean-Michel POURE
2004-07-08 19:48 ` Brad Watson
2004-07-08 21:37 ` Jan Dittmer
2004-07-08 22:24 ` malc
2004-07-08 19:35 ` Jim C. Brown
2004-07-09 20:27 ` [Qemu-devel] " Emmanuel Charpentier
2004-07-09 22:13 ` Antony T Curtis
2004-07-10 0:38 ` Derek Fawcus [this message]
2004-07-10 2:44 ` [Qemu-devel] 3Dfx... Just guessing Natalia Portillo
2004-07-10 13:06 ` Fabrice Bellard
2004-07-10 20:41 ` Natalia Portillo
2004-07-11 21:20 ` Ishwar Rattan
2004-07-11 22:42 ` Natalia Portillo
2004-07-11 1:10 ` Jim C. Brown
2004-07-11 11:16 ` Gianni Tedesco
2004-07-11 4:45 ` Re[2]: [Qemu-devel] Re: RFC for new features Igor Shmukler
2004-07-09 21:51 ` [Qemu-devel] (Before) " Hetz Ben Hamo
2004-07-09 9:50 ` Johannes Schindelin
2004-07-10 11:49 ` [Qemu-devel] plugins Hetz Ben Hamo
2004-07-09 13:25 ` Lionel Ulmer
2004-07-10 15:23 ` Hetz Ben Hamo
2004-07-09 13:35 ` Bartosz Fabianowski
2004-07-09 13:48 ` Gianni Tedesco
2004-07-09 13:39 ` Gianni Tedesco
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=20040710013845.L10322@edinburgh.cisco.com \
--to=dfawcus@cisco.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).