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:	Thu, 29 Jul 2010 16:58:57 +0100 (BST)
From:	James Simmons <jsimmons@...radead.org>
To:	Mattia Jona-Lasinio <mattia.jona@...il.com>
cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Florian Tobias Schandinat <FlorianSchandinat@....de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	lcd-linux-users@...ts.sourceforge.net,
	Andrew Morton <akpm@...l.org>
Subject: Re: Introducing the LCD-Linux project


> <geert@...ux-m68k.org> wrote:
> > On Sat, Jul 24, 2010 at 16:43, Florian Tobias Schandinat
> > <FlorianSchandinat@....de> wrote:
> >> Mattia Jona-Lasinio <mattia.jona <at> gmail.com> writes:
> >>> Moreover I wanted something that COULD be used as a console but not
> >>> necessarily, that is
> >>> something that could run happily in the presence of a normal monitor
> >>> as well. It seems to me, but I may be
> >>> wrong, that through the standard console system only the current
> >>> visible console is actually updated
> >>> while other consoles are just "software" updated. An external LCD
> >>> would therefore be updated
> >>> only when you "switch" to it, so it would not be possible to use it to
> >>> display diagnostics.
> >>
> >> True, that's a general problem one has when multiple framebuffers exist.
> >> Therefore I'd be very happy if someone could come up with a general solution.
> >
> > Fixing that was (one of the) goal of the linux-console project. James?
> 
> Hmmm, the linux-console project seems to be dead. There are no file
> releases after nearly ten
> years and the CVS is three years old.

	We never did file releases. Mostly people just checked out cvs 
and then built and tested out the kernel. At first it was a massive
project which covered several areas. That tree was used as a staging 
ground for the input api and the new fbdev api. We even for a time had had 
the serial api that you find drivers/serial. All of that has been made 
main stream :-) Then we saw graphics cards all becoming agp and mother 
boards with multiple apg slots where extremely rare. So interest in the 
project died off. Now with usb and pcie plus graphics cards with multiple 
crtcs its is becoming possible again. 
	Recently I have been looking at and working on the DRI mode setting api
since it covers the bulk of the graphics cards out there for the PC market which
are pcie which means the possiblity of multiple graphics cards in 
parrallel. You are not the only one looking at this solution.  

> Implementing this  in the standard Linux terminal emulation
> would require
> a rewrite of most of the code, which I personally would do only if
> there is some interest from
> the community in improving the standard Linux console, and I don't
> think it is the case
> looking at the age of the Linux console project. So I decided to keep
> it separate.
> But never say never! In the future the two consoles could merge in a
> single one. ;)

Hum. Only in the last year have I started to see a interest in this area 
again. A few months ago someone else was discussing with me the 
limitations of the linux console system. I have a few drm changes I like 
to push first for the next merge widow. Perhaps if Andrew Morton is 
willing to merge the my linuxconsole git tree into his -mm branch for wide 
area testing then I can start the linux console stuff up again. Currently 
my console git tree has no commits. Its just a raw tree. BTW yes it is 
alot of work to cleanup the console system.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ