linux-kernel - Re: [RFC] enhancing the kernel's graphics subsystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9e4733910705211210h7b993da8g67d31a010eb4c3f3@mail.gmail.com>
Date:	Mon, 21 May 2007 15:10:20 -0400
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Dave Airlie" <airlied@...il.com>
Cc:	"Jesse Barnes" <jbarnes@...tuousgeek.org>,
	"Jesse Barnes" <jesse.barnes@...el.com>,
	linux-kernel@...r.kernel.org,
	"Antonino A. Daplas" <adaplas@...il.com>,
	"Luc Verhaegen" <libv@...net.be>
Subject: Re: [RFC] enhancing the kernel's graphics subsystem

On 5/21/07, Dave Airlie <airlied@...il.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@...il.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/