From: Keith Whitwell <keith@tungstengraphics.com>
To: Ian Romanick <idr@us.ibm.com>
Cc: James Simmons <jsimmons@infradead.org>,
linux-fbdev-devel@lists.sourceforge.net,
dri-devel@lists.sourceforge.net
Subject: Re: [Dri-devel] Re: Re: Current discussion about the future of free software graphics
Date: Wed, 12 May 2004 09:48:19 +0100 [thread overview]
Message-ID: <40A1E4D3.40705@tungstengraphics.com> (raw)
In-Reply-To: <40A13BA0.609@us.ibm.com>
Ian Romanick wrote:
> James Simmons wrote:
>
>>> 1: Design must provide a mechanism for basic mode setting in a
>>> device independent manner from an application with user level
>>> permissions. ("Basic" to be defined)
>>
>>
>> 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.
>
>
> Are you completely without a clue? Nobody from TG is even participating
> in this discussion (except a couple messages from Jens a week or so
> ago). Why would you even say such a thing?
I do feel remiss that I'm not engaged more fully in this, but really much of
the ground covered is way outside the areas in which I feel qualified to
comment, or perhaps it's just that I don't have an opinion either way about
mode-setting, etc, based on long years of just having the X server take care
of it for me...
Anyway. I've got a lot of respect for the people involved in the discussion,
even when they hold quite conflicting views, so I'm hopeful that some sort of
direction can be reached for moving forward.
My one worry about the discussion is that because of confusion over where the
X developers are hanging out nowadays, they are missing out on having their
say on this - and they probably care deeply about modesetting. Though, given
the mad flamewar it's turned into, maybe smaller is better...
Keith
-------------------------------------------------------
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 8:48 UTC|newest]
Thread overview: 25+ 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 ` Keith Whitwell [this message]
2004-05-12 17:09 ` [Dri-devel] Re: " James Simmons
2004-05-13 3:32 ` Keith Packard
2004-05-12 14:14 ` Alan Cox
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
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=40A1E4D3.40705@tungstengraphics.com \
--to=keith@tungstengraphics.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=idr@us.ibm.com \
--cc=jsimmons@infradead.org \
--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).