From: "André Braga" <meianoite@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] What is the bottleneck?
Date: Thu, 30 Sep 2004 15:43:27 -0300 [thread overview]
Message-ID: <2ad73a04093011436599f77c@mail.gmail.com> (raw)
In-Reply-To: <200409301929.46202.katakombi@web.de>
On Thu, 30 Sep 2004 19:29:46 +0200, Stefan Kombrink <katakombi@web.de> wrote:
> I had a look at the cirrus rop code, it's not optimized yet, even in CVS.
> I think that's the problem.
>
> I don't know the hardware specs of the cirrus, but where's the limit of its
> hardware support?
> Is it really necessary to implement a new graphics card?
It's not necessary, but it's desirable if it's done in a "high level"
way, like mapping primitive card instructions to some high-level
acceleration API, like DirectX, OpenGL or Quartz.
> Area copying and area filling is already possible, although not optimized.
>
> This question might be stupid but why not using
> SDL_FillRect(...) and
> SDL_BlitSurface(....).
> ?
>
> I think SDL accelerates these operations if supported by your driver.
I think it's because at the time nobody bothered to implement those,
and I sincerely don't know how the video emulation is done. I just
observed its effects.
> No promises yet....
> These lines look diffcult to me >8^)
Think of all the good karma you'll get when people start smiling
because of your work to improve QEMU ^_^
cheers,
--
"Dealing with failure is easy: Work hard to improve. Success is also
easy to handle: You've solved the wrong problem. Work hard to improve"
Alan J. Perlis
next prev parent reply other threads:[~2004-09-30 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 21:03 [Qemu-devel] What is the bottleneck? Stefan Kombrink
2004-09-29 21:21 ` André Braga
2004-09-30 17:29 ` Stefan Kombrink
2004-09-30 18:43 ` André Braga [this message]
2004-09-29 21:58 ` Oliver Kopp
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=2ad73a04093011436599f77c@mail.gmail.com \
--to=meianoite@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 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.