From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: DRI Devel <dri-devel@lists.sourceforge.net>
Cc: sottek <sottek@sottekland.com>,
eich@pdx.freedesktop.org, agd5f@yahoo.com, michel@daenzer.net,
keithp@keithp.com, jonsmirl@yahoo.com,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Current discussion about the future of free software graphics
Date: Wed, 12 May 2004 15:14:23 +0100 [thread overview]
Message-ID: <1084371262.26224.11.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0405112050570.17349-100000@phoenix.infradead.org>
On Maw, 2004-05-11 at 20:55, James Simmons wrote:
> Ug. I see I'm fighting a losing battle but it doesn't matter. I couldn't
> never win this fight. There is MONEY involved here. This is a sure way
> to make sure Tungstengraphics has a income coming in. They want a monoply
> on the linux graphics arena then fine they can have it.
Current DRI is certainly a PITA unless you know it well but the kernel
side is quite trivial underneath the macrotrastrophe and preprocessor
abuse.
Its mappable buffers, queue, interrupt handler, X<->kernel auth mapping,
and thats it
Also I'd note several folks are doing DRI nowday without Tungsten - VIA
did the Savage and VIA drivers, sis6326 is a WIP but its also not
tungsten stuff.
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
--
next prev parent reply other threads:[~2004-05-12 14:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 18:09 Current discussion about the future of free software graphics sottek
2004-05-11 19:55 ` James Simmons
2004-05-11 20:46 ` Ian Romanick
2004-05-12 3:30 ` Jon Smirl
2004-05-12 14:41 ` Richard Smith
2004-05-12 17:56 ` James Simmons
2004-05-12 18:56 ` Geert Uytterhoeven
2004-05-12 19:11 ` James Simmons
2004-05-12 19:40 ` Geert Uytterhoeven
2004-05-12 21:09 ` James Simmons
2004-05-12 19:23 ` Richard Smith
2004-05-12 20:45 ` Richard Smith
2004-05-12 16:45 ` James Simmons
2004-05-12 19:00 ` Geert Uytterhoeven
2004-05-12 22:45 ` Nicolas Souchu
2004-05-13 10:39 ` Michel Dänzer
2004-05-12 8:48 ` [Dri-devel] Re: " Keith Whitwell
2004-05-12 17:09 ` James Simmons
2004-05-13 3:32 ` Keith Packard
2004-05-12 14:14 ` Alan Cox [this message]
2004-05-11 20:07 ` Geert Uytterhoeven
2004-05-11 23:10 ` James Simmons
2004-05-11 23:15 ` Nicolas Souchu
2004-05-12 13:34 ` Michel Dänzer
2004-05-12 13:54 ` Egbert Eich
-- strict thread matches above, loose matches on Subject: below --
2004-05-11 0:11 [Linux-fbdev-devel] " Sottek, Matthew J
2004-05-11 2:20 ` Adam Jackson
[not found] ` <200405102120.48640.ajax-TAsg7VrFCGc@public.gmane.org>
2004-05-11 13:24 ` Michel Dänzer
[not found] <1084205711.804.43.camel@thor.asgaard.local>
2004-05-10 23:45 ` James Simmons
2004-05-10 16:15 Michel Dänzer
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=1084371262.26224.11.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=agd5f@yahoo.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=eich@pdx.freedesktop.org \
--cc=jonsmirl@yahoo.com \
--cc=keithp@keithp.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=michel@daenzer.net \
--cc=sottek@sottekland.com \
/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).