DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=bAXa1LWCAbVKTYFhWmFtQxYsq7508Bw8Ks36ruZ3U2VMnL91vuBXS+MOamjhd9T8M7IiMq7EnkMuLokMQ7XzAsyqZGq3D+FFLZDh5InWnJNdr/CCtkqI36ynmK7fy+fo/k6DKfZ/NkIWbANBZzBkSLSOlI5xm4dYuYLd9mlbtAY=
Message-ID: <9e4733910705211210h7b993da8g67d31a010eb4c3f3@mail.gmail.com>
Date: Mon, 21 May 2007 15:10:20 -0400
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Dave Airlie" <airlied@gmail.com>
Subject: Re: [RFC] enhancing the kernel's graphics subsystem
Cc: "Jesse Barnes" <jbarnes@virtuousgeek.org>,
       "Jesse Barnes" <jesse.barnes@intel.com>, linux-kernel@vger.kernel.org,
       "Antonino A. Daplas" <adaplas@gmail.com>,
       "Luc Verhaegen" <libv@skynet.be>
In-Reply-To: <21d7e9970705211144j219fa8f5n3e5ceab90f7d3f0b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200705171423.46748.jesse.barnes@intel.com>
	 <9e4733910705210901v5996cacas640f211404c519c6@mail.gmail.com>
	 <200705210914.22663.jbarnes@virtuousgeek.org>
	 <200705210934.58559.jbarnes@virtuousgeek.org>
	 <9e4733910705211005k761c976o1a6b270d87b49589@mail.gmail.com>
	 <21d7e9970705211014j6eb59326u85f7347a3000f3d3@mail.gmail.com>
	 <9e4733910705211042o8926e4cy2225c2dbcbf3ff2@mail.gmail.com>
	 <21d7e9970705211047n2328f970ref96ea85856f3ba8@mail.gmail.com>
	 <9e4733910705211104u143e7abercccc4f351441343e@mail.gmail.com>
	 <21d7e9970705211144j219fa8f5n3e5ceab90f7d3f0b@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2581
Lines: 62

On 5/21/07, Dave Airlie <airlied@gmail.com> wrote:
> >
> > You are describing a transition plan without knowing what the final
> > design is going to look like. We really need to hash out the final
> > design so that the right path is taken to get there.
> >
> > For example I didn't have per CRTC device nodes or user space consoles
> > in my original design, but after talking to some of the people that
> > really wanted the multi-seat feature it led me down the user space
> > console path and to the per CRTC device node solution. I also got beat
> > up at OLS by people wanting full Unicode support on the console.
> >
>
> No we are defining steps towards improving the drivers on Linux, the
> first step is the requirement to fix suspend/resume, and allow
> modesetting on multiple crtc/output combinations, the other goals are
> not directly within the scope of this work, you can take steps to do
> get where we want, but we don't need to move all drivers at once to
> get there... we also can't just merge something like that to the
> kernel...
>
> Your old ideas were mostly limited by the fact that you didn't get the
> crtc/output distinction and persisted with the idea of heads which put
> policy in the kernel, this was a major failing you never discovered,
> and I didn't probably look enough at the time, since then Keith
> Packard has done a lot of work on randr 1.2 to show the path to what
> we actually wanted.

I thought Luc Verhaegen figured that out not Keith.

Call it whatever you want and I have wasted far too much time arguing
with you and Keith and I can never get agreement on anything.  BTW,
should I search the LKML archives and find the messages where you call
me stupid and block my patches merging fbdev/DRM? That's effectively
what you are doing right now.

There is a significant group of Linux users who want to be able to
login separate users to each screen/head/crtc/output device. These
people are concentrated in the third world and don't show up at OLS to
argue their case.

There is another group that wants Unicode consoles. The people I
talked to were from India and Japan.

I am not a member of either group. So go ahead and ignore me, I'd just
like to see these two groups get features implemented that have been
ignored for a long time.


>
> Dave.
>


-- 
Jon Smirl
jonsmirl@gmail.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/