Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752771Ab0G2Rx0 (ORCPT ); Thu, 29 Jul 2010 13:53:26 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:38315 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752368Ab0G2RxY (ORCPT ); Thu, 29 Jul 2010 13:53:24 -0400 Date: Thu, 29 Jul 2010 19:05:15 +0100 From: Alan Cox To: James Simmons Cc: Mattia Jona-Lasinio , Geert Uytterhoeven , Florian Tobias Schandinat , linux-kernel@vger.kernel.org, lcd-linux-users@lists.sourceforge.net Subject: Re: Introducing the LCD-Linux project Message-ID: <20100729190515.6ec85db2@lxorguk.ukuu.org.uk> In-Reply-To: References: <20100722122111.4cf4ca2f@lxorguk.ukuu.org.uk> <20100728203921.0dd6562d@lxorguk.ukuu.org.uk> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.18.9; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1080 Lines: 26 > 3) Invert the VT layer. Currently the console/printk driver is on top of > the tty layer. It would be nice to be able to only use a very light > weight vt printk without the VT tty on top for embedded platforms. No. printk hits console drivers why may or may not be frame buffer interfaces. Has done for a very long time. Keith Packard has also been doing stuff with crash time oops displays etc over an X display. > 4) Seperate out the VT emulation layer. Related to 3. Separate from what ? > 5) Multiple independent VT support. Which brings up the question what > should the mapping of VCs to a VT look like. I would suggest we borrow the X idea and each VC is int display; /* Display it is on (for console flipping) */ struct something *vt; /* VT which it is displaying */ int x,y,w,h; /* Window onto vt */ -- 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/