From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: framebuffer ioctl
Date: Mon, 6 Sep 2004 17:02:20 -0400 [thread overview]
Message-ID: <9e4733910409061402372095b1@mail.gmail.com> (raw)
In-Reply-To: <413CC0EA.8070709@comcast.net>
On Mon, 06 Sep 2004 12:56:26 -0700, Zack <plinius@comcast.net> wrote:
> I think you may be misinterpreting my intent. I am strictly anti-bloat,
> so I don't want a larger kernel. By the same token, I don't use
> X because it is bloated--X uses 16 megs minimum on my system,
> and that is very much not to my taste.
Mesa-solo is not X it is the OpenGL layer. mesa-solo runs standalone
without needing X. Using mesa-solo will give you access the full
acceleration capabilities of many chip families - i810, i830, i915,
radeon, r128, mga, sis, ffb, tdfx. Nvidia is not supported because
the hardware documentation is secret. There is also a mode for
building an embedded version of mesa-solo which removes about 50% of
the OpenGL functions and makes it smaller if that is really a problem.
Check out the Cairo benchmarks. The OpenGL drivers can beat the
performance of 2D drivers 100:1 and some cases 400:1. OpenGL uses the
GPU to do the drawing instead of the main CPU.
Writing fully accelerated drivers is very complicated and it takes
years of work.
--
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-06 21:02 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 [this message]
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
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=9e4733910409061402372095b1@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).