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]

Date:	Sun, 20 May 2007 16:10:31 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
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 Sunday, May 20, 2007, Jon Smirl 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.

With the interfaces implemented here, a userspace application can create a 
multiseat environment either with a single graphics card with multiple 
outputs or multiple cards.  It could do this by creating several frame 
buffer objects and associating them with whatever CRTCs were available, 
and managing input via existing APIs.  I don't know of anyone that's done 
this yet though...

Jesse
-
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/