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: <alpine.LFD.2.00.1007291934310.16616@casper.infradead.org>
Date:	Thu, 29 Jul 2010 19:39:22 +0100 (BST)
From:	James Simmons <jsimmons@...radead.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
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.

Correct. What I mean is have the ability to just register the console 
driver but not the tty driver.
  
> > 4) Seperate out the VT emulation layer. Related to 3.
> 
> Separate from what ?

We can still have a basic tty layer without the control characters, think 
do_con_trol in vt.c, junk compiled into the kernel. Make it a options for 
userland to do the vt100 emulation.

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

/dev/tty[0-16]  -> VT display 0
/dev/tty[17-31] -> VT display 1

etc.

At least that is how I handled it  several years ago.

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