From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Roland Elek <elek.roland@gmail.com>
Subject: Re: [Qemu-devel] GSoC projects about AHCI and S3 Trio
Date: Thu, 1 Apr 2010 11:55:19 +0000 [thread overview]
Message-ID: <201004011255.19796.paul@codesourcery.com> (raw)
In-Reply-To: <bf8739da1003301152l16b9af3ava8fd1ec63e2188f3@mail.gmail.com>
> I will contact jai soon about the S3 Trio. I'll also skim through the
> documentation so that I can set reasonable goals in my timeline.
TBH I'm less convinced about the utility of emulating an S3 graphics card.
You'd want to make sure you know what you're expecting from it.
While it may have a bit wider OS support that the Cirrus Logic cards, it's
still an extremely old card that AFAIK ceased production many years ago.
In modern terms it also has extremely limited capabilities.
Even the 2D engine is likely to be tricky accelerate because. The framebuffer
is exposed to the guest, so you have to accomodate the guest reading back the
results.
Some models have rudimentary 3D acceleration, however in practice I doubt this
is worth much. I did a bit of 3D graphics when these cards were common, and
IIRC they're missing some common features (multitexturing, possibly even
prespective correction) and [as real hardware] are generally slower than a
good software renderer.
If you want useful 3D acceleration, then you pretty much have to go for a
paravirtual interface. The interface exposed by real hardware is closely tied
to the implementation, which makes it hard (and slow) to emulate. This has
been discussed a few times before, and amounts to feeding OpenGL commands (or
equivalents such as Gallium pipes) over a remote transport.
Paul
prev parent reply other threads:[~2010-04-01 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 23:52 [Qemu-devel] GSoC projects about AHCI and S3 Trio Roland Elek
2010-03-30 0:55 ` Alexander Graf
2010-03-30 4:56 ` Natalia Portillo
2010-03-30 12:14 ` Paul Brook
2010-03-30 18:52 ` Roland Elek
2010-04-01 11:55 ` Paul Brook [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=201004011255.19796.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=elek.roland@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).