From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: framebuffer ioctl
Date: Tue, 7 Sep 2004 10:38:13 -0400 [thread overview]
Message-ID: <9e4733910409070738a46cafb@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0409071623550.518@waterleaf.sonytel.be>
On Tue, 7 Sep 2004 16:26:47 +0200 (MEST), Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Tue, 7 Sep 2004, 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.
>
> I think (but I'm not sure) Michel wants you to compare Cairo on OpenGL vs.
> traditional 2D accelerated X.
That's what the numbers compare. I think he wants me to compare it to
his new render implementation that uses the 3D hardware. But that's
what I'm against. I don't want to see even more drivers trying to take
control of the 3D hardware and causing even more conflicts.
Implementing X on GL completely removes the need for expanding XAA to
include using the 3D hardware. This pratice of ten different groups
programming the video hardware however they want has got to stop or
Linux is never going to be competitive with Mac/Longhorn.
>
> I.e. while X on top of hardware accelerated OpenGL is _much_ faster than X on
> top of software OpenGL, what we really care about is whether it's much faster
> than traditional 2D accelerated X.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
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_id=5047&alloc_id=10808&op=click
next prev parent reply other threads:[~2004-09-07 14:38 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 [this message]
2004-09-07 15:58 ` Otto Wyss
2004-09-07 14:45 ` Jon Smirl
2004-09-07 15:52 ` Michel Dänzer
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=9e4733910409070738a46cafb@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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).