Subject: Re: [RFC] enhancing the kernel's graphics subsystem
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Keith Packard <keithp@keithp.com>
Cc: Jesse Barnes <jesse.barnes@intel.com>,
       James Simmons <jsimmons@pentafluge.infradead.org>,
       dri-devel@lists.sourceforge.net, Dave Airlie <airlied@gmail.com>,
       linux-kernel@vger.kernel.org, "Antonino A. Daplas" <adaplas@gmail.com>
In-Reply-To: <1179795093.5826.391.camel@neko.keithp.com>
References: <200705171423.46748.jesse.barnes@intel.com>
	 <1179792587.32247.769.camel@localhost.localdomain>
	 <1179795093.5826.391.camel@neko.keithp.com>
Content-Type: text/plain
Date: Tue, 22 May 2007 12:48:25 +1000
Message-Id: <1179802105.32247.780.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1108
Lines: 28

On Mon, 2007-05-21 at 17:51 -0700, Keith Packard wrote:
> 
> 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.

Ok, good plan then.

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

Ok. Fair enough.

Cheers,
Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/