From: Ian Romanick <idr@us.ibm.com>
To: David Dawes <dawes@XFree86.Org>
Cc: dri-devel <dri-devel@lists.sourceforge.net>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Dri-devel] Re: DRM and pci_driver conversion
Date: Mon, 27 Oct 2003 11:38:04 -0800 [thread overview]
Message-ID: <3F9D741C.9010501@us.ibm.com> (raw)
In-Reply-To: <20031027114006.A66611@xfree86.org>
David Dawes wrote:
> On Sat, Oct 25, 2003 at 11:37:05AM -0700, Linus Torvalds wrote:
>
>>But I'm _not_ interested in some interfaces to let user mode just bypass
>>the kernel. Because they will not solve any of the other problems that
>>clearly _do_ need solving, and if the X server continues to believe that
>>it can just access the hardware directly, it will never play well together
>>with projects like fbcon/dri.
>
> XFree86 cares more about being a useable X server on a wide range of
> platforms than on playing well with a few Linux-specific hacks.
>
> The real problem is that you have a mix of ideologies in the Linux
> kernel, each struggling for supremacy. Come back to us when you know
> who the winner is. At that time I'm sure you'll feel free to re-write
> history and claim that we should have been doing things that way all
> along.
I'm really baffled here. Why would you even say such a thing? In
relation to Linus' *whole* message, your first paragraph and second
paragraph are incongruous. Linus (or anyone else) did not suggest that
XFree86 be shoe-horned into any of the existing Linux video driver
architectures. In fact, he said quite the opposite. He said that
XFree86 is trying to do things that really do need kernel support, and
all the existing methods for doing that suck.
Part of the problem is that, with the exception of DRI, the existing
video specific interfaces in Linux were, as far as I know, created
without input from XFree86. You're suggesting that same mistake be
repeated.
I'm also baffled by the general animosty shown towards Linux. Judging
by the traffic on the various lists, it seems to me that Linux and *BSD
represent the lion's share of the XFree86 user base. Making a consious
choice to not support those platforms better is making a consious choice
to not support our users. I simply don't understand the rationalle
behind such a decision.
Not only that, there is no requirement that the drivers use any given
kernel interface. Just because the drivers use a kernel interface on
Linux or *BSD does not mean that they have to use a kernel interface on
Solaris or HPUX. There will be growing pains involved in having a
kernel path and a non-kernel path. I think that several of the DRI
drivers (Radeon and Rage128) have shown that it *is* doable.
The next step is to create a kernel interface that is both generic
enough and specific enough to acomplish the task at hand. After
watching the development of fbdev / fbcon, DRI, and XFree86 for a long
time, I can say that there is no point in squabling over whether or not
a kernel interface is useful for performance or necessary for proper
device configuration. Both of those questions have been sufficiently
answered. The question of where we go from here has not been answered.
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-10-27 19:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1066703516.646.24.camel@leguin>
2003-10-23 19:04 ` DRM and pci_driver conversion Kronos
2003-10-23 21:10 ` [Linux-fbdev-devel] " Eric Anholt
2003-10-23 21:31 ` Jon Smirl
2003-10-23 23:23 ` [Dri-devel] " Linus Torvalds
2003-10-23 23:46 ` Eric Anholt
2003-10-24 1:19 ` [Dri-devel] " Jeff Garzik
2003-10-24 1:52 ` [Dri-devel] Re: [Linux-fbdev-devel] " Jon Smirl
2003-10-24 3:47 ` Multiple drivers for same hardware:, was: " Jon Smirl
2003-10-24 4:40 ` Linus Torvalds
2003-10-28 18:00 ` James Simmons
2003-10-24 16:44 ` [Dri-devel] " Linus Torvalds
2003-10-24 16:57 ` [Dri-devel] Re: [Linux-fbdev-devel] " Petr Vandrovec
2003-10-24 17:59 ` Linus Torvalds
2003-10-24 18:34 ` Jon Smirl
2003-10-24 19:45 ` [Dri-devel] " Ivan Kokshaysky
2003-10-24 19:08 ` Ivan Kokshaysky
2003-10-24 17:06 ` Jeff Garzik
2003-10-24 1:50 ` Jon Smirl
2003-10-25 17:29 ` Egbert Eich
2003-10-25 18:37 ` [Dri-devel] Re: [Linux-fbdev-devel] " Linus Torvalds
2003-10-25 19:17 ` [Dri-devel] " Jeff Garzik
2003-10-27 14:37 ` Ingo Oeser
2003-10-27 15:14 ` Keith Whitwell
2003-10-27 15:38 ` Jeff Garzik
[not found] ` <20031027153824.GA19711@gtf.org>
2003-10-27 15:50 ` Keith Whitwell
[not found] ` <200310271537.30435.ioe-lkml@rameria.de>
2003-10-27 15:43 ` Jeff Garzik
2003-10-28 10:53 ` [Dri-devel] Re: [Linux-fbdev-devel] " Ingo Oeser
2003-10-25 21:02 ` [Dri-devel] " Jon Smirl
2003-10-25 22:07 ` Benjamin Herrenschmidt
2003-10-27 15:10 ` Eric W. Biederman
2003-10-27 15:10 ` Keith Whitwell
[not found] ` <20031027114006.A66611@xfree86.org>
2003-10-27 19:38 ` Ian Romanick [this message]
2003-10-27 21:32 ` Linus Torvalds
2003-10-27 23:55 ` Benjamin Herrenschmidt
2003-10-28 2:13 ` Linus Torvalds
2003-10-28 3:27 ` Philip Brown
2003-10-28 19:40 ` James Simmons
2003-10-28 21:35 ` Benjamin Herrenschmidt
2003-10-28 22:09 ` Jon Smirl
2003-10-28 22:26 ` Benjamin Herrenschmidt
2003-10-28 22:54 ` Linus Torvalds
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=3F9D741C.9010501@us.ibm.com \
--to=idr@us.ibm.com \
--cc=dawes@XFree86.Org \
--cc=dri-devel@lists.sourceforge.net \
--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).