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: <1179766255.7699.216.camel@frg-rhel40-em64t-04>
Date:	Mon, 21 May 2007 18:50:55 +0200
From:	Xavier Bestel <xavier.bestel@...e.fr>
To:	Dave Airlie <airlied@...il.com>
Cc:	Jon Smirl <jonsmirl@...il.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Helge Hafting <helge.hafting@...el.hist.no>,
	Jesse Barnes <jesse.barnes@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] enhancing the kernel's graphics subsystem

On Mon, 2007-05-21 at 17:27 +0100, Dave Airlie wrote:
> > What about modifying the existing fbdev API? You could start with
> one
> > fbdev device per CRTC and then add a new IOCTL to control the output
> > device. I haven't seen anything yet that justifies abandoning the
> > existing fbdev API.
> 
> Then you can't aribtrate properly output hooking is a root level
> thing, you cannot allow the user in multiseat to just pick his own
> outputs, if you claim to want a truly flexible interfaces, also the
> crtc->output mappings aren't always simple, there are limitations on
> most hw about which crtc can map to which output and when you can
> clone etc.. putting policy for this stuff in-kernel would heavily
> restrict what the user can do...

Policy for this kind of thing should just go in HAL's ConsoleKit:
http://lists.freedesktop.org/archives/hal/2007-January/007111.html

	Xav


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