From: "Michel Dänzer" <michel@daenzer.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: framebuffer ioctl
Date: Tue, 07 Sep 2004 11:52:00 -0400 [thread overview]
Message-ID: <1094572321.6095.10.camel@admin.tel.thor.asgaard.local> (raw)
In-Reply-To: <9e47339104090707172cdc258d@mail.gmail.com>
On Tue, 2004-09-07 at 10:17 -0400, Jon Smirl wrote:
> The numbers compare two peices of software that exist. Sure you could
> probably write a super optimized library for CPU based drawing in 2D
> mode that would be faster, but this library doesn't exist. No matter
> what you do using the GPU to draw is always going to beat using the
> CPU by a wide margin because of the memory bandwidth difference.
>
> Would Cairo on hardware OpenGL vs Cairo on software only OpenGL be a
> better comparison? Those ratios are even worse.
Examples of fair comparisons would be:
Software rendered OpenGL vs. software rendered Render extension
Hardware-accelerated OpenGL vs. hardware-accelerated Render extension
...
> Why does everyone want to write another accelerated drawing library
> when we already have a really good one that follows standards and has
> excellent documentaition? Why not help integrate DRM and fbdev
> instead.
All I'm saying is that it reflects badly on you if you need to resort to
skewed numbers.
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id\x10808&op=click
next prev parent reply other threads:[~2004-09-08 4:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 11:04 framebuffer ioctl (fwd) Geert Uytterhoeven
2004-09-04 21:44 ` Otto Wyss
2004-09-05 17:13 ` framebuffer ioctl Zack
2004-09-06 1:33 ` Antonino A. Daplas
2004-09-06 15:36 ` Otto Wyss
2004-09-06 21:21 ` Antonino A. Daplas
2004-09-06 21:58 ` Zack
2004-09-06 23:05 ` Antonino A. Daplas
2004-09-06 19:56 ` Zack
2004-09-06 21:02 ` Jon Smirl
2004-09-06 21:11 ` [OT] " Otto Solares
2004-09-06 21:39 ` Jon Smirl
2004-09-07 0:01 ` Otto Solares
2004-09-07 0:11 ` Jon Smirl
2004-09-06 21:24 ` Michel Dänzer
2004-09-07 14:17 ` Jon Smirl
2004-09-07 14:26 ` Geert Uytterhoeven
2004-09-07 14:38 ` Jon Smirl
2004-09-07 15:58 ` Otto Wyss
2004-09-07 14:45 ` Jon Smirl
2004-09-07 15:52 ` Michel Dänzer [this message]
2004-09-08 5:43 ` Jon Smirl
2004-09-08 13:59 ` Ville Syrjälä
2004-09-08 22:47 ` Jon Smirl
2004-09-13 15:54 ` vga softboot code repository Richard Smith
2004-09-13 16:00 ` vga softboot code repository oops Richard Smith
2004-09-13 16:06 ` vga softboot code repository Jon Smirl
2004-09-06 18:43 ` framebuffer ioctl Otto Solares
2004-09-06 19:08 ` Jon Smirl
2004-09-06 19:24 ` Otto Solares
2004-09-06 19:33 ` Jon Smirl
2004-09-07 15:48 ` Otto Wyss
2004-09-07 16:01 ` Jon Smirl
2004-09-07 18:09 ` Otto Solares
2004-09-06 19:33 ` Jon Smirl
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=1094572321.6095.10.camel@admin.tel.thor.asgaard.local \
--to=michel@daenzer.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).