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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 21 May 2007 18:27:54 +1000
From:	"Dave Airlie" <airlied@...il.com>
To:	"Jon Smirl" <jonsmirl@...izon.net>
Cc:	"Jesse Barnes" <jesse.barnes@...el.com>, jonsmirl@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] enhancing the kernel's graphics subsystem

On 5/21/07, Jon Smirl <jonsmirl@...izon.net> wrote:
> On Thu, 17 May 2007 14:23:45 -0700, Jesse Barnes wrote:
>
> > In collaboration with the FB guys, we've been working on enhancing the
> > kernel's graphics subsystem in an attempt to bring some sanity to the
> > Linux graphics world and avoid the situation we have now where several
> > kernel and userspace drivers compete for control of graphics devices.
>
> How is supporting different users logged into each head going to work?
> The original model for this was to give each head its own fbdev device.
> It is important that each user be able to set their own mode without being
> root.

TThe problem with that is the concept of heads is flawed... there is
in reality no such
thing, you have crtcs and outputs, no heads. So any attempt to enforce
the head concept involves putting policy into the kernel, as if I have
3 outputs but 2 crtcs how do I decide the mappings without the admin
telling the kernel,

As for moving other card drivers they will move as people see fit to
move them there probably isn't much gain in moving single crtc/output
cards..

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/
>
x.org/lkml/
>
x.org/lkml/
>
-
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/