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:	Mon, 21 May 2007 17:51:32 -0700
From:	Keith Packard <keithp@...thp.com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	keithp@...thp.com, Jesse Barnes <jesse.barnes@...el.com>,
	James Simmons <jsimmons@...tafluge.infradead.org>,
	dri-devel@...ts.sourceforge.net, Dave Airlie <airlied@...il.com>,
	linux-kernel@...r.kernel.org,
	"Antonino A. Daplas" <adaplas@...il.com>
Subject: Re: [RFC] enhancing the kernel's graphics subsystem

On Tue, 2007-05-22 at 10:09 +1000, Benjamin Herrenschmidt wrote:

> I do stongly beleive that the decision of what mode to choose should not
> be made in the kernel.

That's the plan; the kernel just provides mechanism. The architecture
used in the X server splits precisely at this point with the mechanism
in the driver and the configuration and policy up in the X server
proper. Quite a bit of that code could be broken out into a shared
library for fbdev-based apps and the X server to share, but that's down
the road a bit after the kernel APIs look a lot more solid.

With the goal of getting to a single-mode-set boot to avoid screen
flashing before login, the key here is to make any early user-mode
graphics apps share the same kernel graphics infrastructure as the X
server to identify the common cases where the startup and X modes are
the same and avoid resetting the configuration.

-- 
keith.packard@...el.com

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)