From: Sven Luther <sven.luther@wanadoo.fr>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
James Simmons <jsimmons@infradead.org>,
Nicolas Souchu <nsouch@free.fr>,
dri-devel <dri-devel@lists.sourceforge.net>,
mesa3d-dev <mesa3d-dev@lists.sourceforge.net>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [Linux-fbdev-devel] Redesign of kernel graphics interface
Date: Fri, 14 May 2004 21:31:12 +0200 [thread overview]
Message-ID: <20040514193112.GB27048@pegasos> (raw)
In-Reply-To: <20040514175135.41336.qmail@web14921.mail.yahoo.com>
On Fri, May 14, 2004 at 10:51:35AM -0700, Jon Smirl wrote:
> Just look at this picture and you can see the trend of 2D vs 3D (coprocessor
> based) graphics.
> http://www.de.tomshardware.com/graphic/20040504/images/architecture.gif
> Within one or two generations the 2D box is going to be gone.
Sorry, but i am not able to see this over the remote link i am having
now, i will look at it more in detail when i am back home on sunday.
> If Linux wants to stay current with technology we have to start using the
> coprocessor features of the GPU. Most of the benchmarks I have seen show
> coprocessor vs programmed at 100:1 speed differential. This is also a
> competitive problem, Microsoft and Apple have both decided to go with the GPU
> coprocessor this year.
Fine with me, i believe that this is also the way to go, but saddly
this is probably not going to happen unless we put some pressure on the
graphic companies, and i somehow doubt that nvidia will go with it. I
only wanted to raise the problematic, so we don forget about where we
come from, and create a framework which would depend on non-free parts.
> Lack of free drivers is no reason to ignore the GPU coprocessor. It just means
Well, it probably means nonaccelerated drivers, if even that.
> more effort needs to be put into mesa and prying the docs out of the graphics
> chip vendors. If the current open drivers don't work on a non-x86 platform just
> go fix them. All of the necessary data is available. Progress is being made with
> ATI for getting the R300 specs now that the R400 series has shipped.
>
If this is true, then it would be a great new, but still, if you want to
go forward with this plan, we have to get at least a partial
functionality open source drm/fbdev module for even the newer model of
graphic cards, and even from players like nvidia. They can hide all
their stuff in proprietary userland libraries afterward still, but the
right thing would be to have this integrated kernel driver be a real
GPLed driver, with source and all.
Friendly,
Sven Luther
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-14 19:31 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 18:16 Redesign of kernel graphics interface Jon Smirl
2004-05-06 19:46 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-05-06 23:20 ` James Simmons
2004-05-06 20:57 ` Otto Solares
2004-05-06 23:19 ` Nicolas Souchu
2004-05-06 21:42 ` Jon Smirl
2004-05-07 0:30 ` Nicolas Souchu
2004-05-06 22:48 ` James Simmons
2004-05-07 0:50 ` Jon Smirl
2004-05-07 1:20 ` [Dri-devel] " Keith Packard
2004-05-07 1:33 ` Jon Smirl
2004-05-07 8:31 ` Geert Uytterhoeven
2004-05-14 17:20 ` Sven Luther
2004-05-14 17:35 ` Alex Deucher
2004-05-14 19:25 ` Sven Luther
2004-05-14 17:51 ` Jon Smirl
2004-05-14 18:08 ` Ville Syrjälä
[not found] ` <20040514184004.16621.qmail@web14930.mail.yahoo.com>
2004-05-14 19:01 ` Ville Syrjälä
2004-05-15 7:27 ` Holger Waechtler
2004-05-15 8:25 ` Ville Syrjälä
2004-05-17 17:40 ` Alan Cox
2004-05-14 19:31 ` Sven Luther [this message]
2004-05-10 0:57 ` [Dri-devel] " Benjamin Herrenschmidt
2004-05-10 16:14 ` James Simmons
2004-05-10 16:28 ` [Dri-devel] " Ville Syrjälä
2004-05-10 22:42 ` Nicolas Souchu
2004-05-10 18:29 ` Jon Smirl
2004-05-10 19:16 ` Mike Mestnik
2004-05-10 21:05 ` James Simmons
2004-05-10 22:39 ` Nicolas Souchu
2004-05-10 20:47 ` Otto Solares
2004-05-10 23:58 ` James Simmons
2004-05-11 22:57 ` Nicolas Souchu
2004-05-11 21:17 ` Otto Solares
2004-05-11 21:29 ` Ville Syrjälä
2004-05-10 19:33 ` [Dri-devel] Re: [Linux-fbdev-devel] " Alan Cox
2004-05-11 8:33 ` Geert Uytterhoeven
2004-05-10 23:40 ` Benjamin Herrenschmidt
2004-05-10 23:50 ` James Simmons
2004-05-11 22:13 ` Compiling Rage xlinit.c Richard Smith
2004-05-14 19:41 ` Richard Smith
2004-05-14 21:28 ` Steve Longerbeam
2004-05-14 22:16 ` Richard Smith
2004-05-14 22:48 ` Steve Longerbeam
2004-05-14 23:57 ` Richard Smith
2004-05-15 0:22 ` Steve Longerbeam
2004-05-15 0:42 ` Ville Syrjälä
2004-05-18 22:06 ` James Simmons
2004-05-19 14:36 ` Richard Smith
2004-05-19 22:20 ` James Simmons
2004-05-07 8:30 ` [Linux-fbdev-devel] Redesign of kernel graphics interface Geert Uytterhoeven
2004-05-06 23:21 ` James Simmons
2004-05-10 12:07 ` [Dri-devel] " Egbert Eich
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=20040514193112.GB27048@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@yahoo.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=mesa3d-dev@lists.sourceforge.net \
--cc=nsouch@free.fr \
/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).