linux-kernel - Re: Introducing the LCD-Linux project

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: <20100729190515.6ec85db2@lxorguk.ukuu.org.uk>
Date:	Thu, 29 Jul 2010 19:05:15 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	James Simmons <jsimmons@...radead.org>
Cc:	Mattia Jona-Lasinio <mattia.jona@...il.com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Florian Tobias Schandinat <FlorianSchandinat@....de>,
	linux-kernel@...r.kernel.org, lcd-linux-users@...ts.sourceforge.net
Subject: Re: Introducing the LCD-Linux project

> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/