Hi! I have compiled OSELAS.BSP 2012.06.0 with Kernel 3.4 for Mini2440. Works fine! The console on ttySAC0 is ok, but how can i get text on the framebuffer? I want to use nurses in a little program. The frame buffer itself is working, ts_calibrate, ts_test is working and the QT4-demo too. Is there a way to get messages on the screen with C++? Thank you and good night! ;-) Titus
Console Output OSELAS.BSP Mini2440
Device Drivers ---> Character devices ---> [*] Virtual terminal [*] Enable character translations in console [*] Support for console on virtual terminal
or maybe this: Graphics support ---> [*] Support for frame buffer devices ---> <*> S3C2410 LCD framebuffer support Console display driver support ---> <*> Framebuffer Console support [*] Map the console to the primary display device [*] Select compiled-in fonts [*] VGA 8x8 font
Works perfectly, thank you very much! I followed both of your suggestions. While booting the kernel now Tux is shown in the upper left corner, and in /dev are tty1 ... ttyn and vcs devices i never seen before. Writing to screen can be done by directing the output to /dev/tty1. Directing the output to /dev/vcs1 works too, but give a strange sign at the end of each line caused by the CR character and is always started at the first line of the screen. I did not tested it, but i think the tty devices were created by the 'Console display driver support' option and the vas devices by 'Virtual termimal'. Great, thanks a lot! Titus
I have another question regarding the framebuffer console... Is it possible to enable colors on the console? I did not find any useful kernel option to solve this. Thanks! Titus
The console emulates a standard terminal. So, you should be able to use the ANSI colour strings to change the colour of the chars.
I do not use sound, but i will test it this evening and report. With ANSI colour strings i did not succeed, but i try it again later, thank you Jürgen!
With the 3.4 kernel from the Mini2440 BSP the sound will not work. Its broken since 3.2. Don't know why yet. Use the 3.1 kernel from the Mini2440 BSP and sound still works.
I solved the problem with the colored terminal... Declaring environment variable TERM as 'linux' instead of vt100 gives the screen the ability of showing and declaring colors. Curses functions hasColors() and canChangeColors() returning true now. To get an nice output of Midnight Commander on ssh i exported TERM=xterm in /etc/profile.environment and in the start script of my application TERM=linux for having colors and no wracked lines. Don't know why it would not work with vt100, but this is unimportant now ;-)
Titus, I built MC with gpm mouse support then did a site search to see if anyone had tried using it. Then I noticed your comments about TERM=linux. I had to do this to get syntax highlighting working properly in nano. Your comment: > i exported TERM=xterm in /etc/profile.environment and in the start > script of my application TERM=linux for having colors and no wracked > lines. I found just TERM=linux was enough for nano. Is there some reason you use TERM=xterm for other applications and then switch to TERM-linux for MC? Is "my application" something other than Midnight Commander itself, so you had to make your own configuration file. Thanks, Dave