From: Paolo S. <ar...@ti...> - 2000-09-12 18:34:57
|
Hi Geert! > I assume you pass `console=ttyS0' (or something like that) to the kernel? In > that case no console messages are sent to the console on the frame buffer > device. I dont pass anything to the kernel... in the PPC distribution, a kernel parameter is CONFIG_SERIAL_CONSOLE that initializes a console using the serial driver. No parameters are required. It only add a call in 'console_init()'. I looked at the sources, but i still think there's something wrong on console initialization (this is 'main.c'): CONSOLE_INIT CON_INIT (vt initialization) CONSOLE_8xx_INIT (serial console on the PPC) TTY_INIT RS_8xx_INIT (serial driver on the PPC) VIDEO_SETUP Then, i see that VT is not registered because at CON_INIT, the functions tests the value of 'conswitchp' before running any 'con_startup' function, and it is NULL. Who should initialize it if this function has to be called before any other one that initializes the framebuffer? I cannot change virtual terminal because VT is not registered, then there is something wrong on this, isnt it? > You may want to try `console=tty0 console=ttyS0' to get console output on both > the frame buffer device and the serial console. Input for the console will > come from the last console= argument (i.e. the serial console, cfr. > Documentation/serial-console.txt). Sorry, but it still doesnt work! Please reply me because i have no idea on what to do now!!! =-> MAY THE PINGUIN B WITH U! <-= Best regards, Paolo Scaffardi (ar...@ti... - psc...@su...) AIRVENT SAM s.p.a. - RIMINI (ITALY) Tel. 0541 383294 - Fax 0541 387086 |
From: Geert U. <ge...@li...> - 2000-09-12 21:44:21
|
On Tue, 12 Sep 2000, Paolo Scaffardi wrote: > Then, i see that VT is not registered because at CON_INIT, the functions > tests the value of 'conswitchp' before running any 'con_startup' function, > and it is NULL. Who should initialize it if this function has to be called > before any other one that initializes the framebuffer? I cannot change > virtual terminal because VT is not registered, then there is something wrong > on this, isnt it? Make sure to setup the dummy console early in your startup code (cfr. {chrp,pmac}_setup.c): conswitchp = &dummy_con; Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: Paolo S. <ar...@ti...> - 2000-09-21 14:51:58
|
Please, could you explain me differences between /dev/tty, /dev/tty0 and /dev/console? I have an embedded linux box with a custom keyboard and a custom frame buffer. The keyboard driver sends scancodes to 'handle_scancode' in keyboard.c and it is not registered as console, or any type of device. At the boot i dont specify anything to boot the kernel. It uses correctly both the frame buffer console and the keyboard correctly. The only problem is that when using other programs, like GII, that opens /dev/tty to access the keyboard, they dont work and report: /dev/tty - device not configured Who has to register /dev/tty? How could my keyboard be reached by /dev/tty? I'm going mad... 8-((( - may the pinguin b with u - Have a nice day, Paolo Scaffardi. AIRVENT SAM s.p.a. - RIMINI - ITALY |
From: James S. <jsi...@ac...> - 2000-09-21 23:53:54
|
On Thu, 21 Sep 2000, Paolo Scaffardi wrote: > Please, could you explain me differences between /dev/tty, /dev/tty0 and > /dev/console? /dev/console. This is the system console. What display the kernel messages get sent to. /dev/tty TTY the current process is attached to. Could be a VT, serial console, or even a modem. /dev/tty0 The current video terminal that is being displayed. > I have an embedded linux box with a custom keyboard and a custom frame > buffer. The keyboard driver sends scancodes to 'handle_scancode' in > keyboard.c and it is not registered as console, or any type of device. To get your keyboard to work with the console you need a function like void __init xxxkbd_init_hw(void) { } Where xxx is what you want to call your keybaord driver. Take a look at pckbd_init_hw. See in tty_io.c tty_init is called which calls kbd_init which in turn calls kbd_init_hw which calls the specific xxxkbd_init_hw function. This sets up your keyboard for the console system. Of course you will need a little more than this to get the keyboard working right but these are the key parts you need. Understand also the standard tree only works with one keyboard at a time. > The only problem is that when using other programs, like GII, that opens > /dev/tty to access the keyboard, they dont work and report: > > /dev/tty - device not configured > > Who has to register /dev/tty? How could my keyboard be reached by /dev/tty? > > I'm going mad... 8-((( See above. MS: (n) 1. A debilitating and surprisingly widespread affliction that renders the sufferer barely able to perform the simplest task. 2. A disease. James Simmons [jsi...@li...] ____/| fbdev/console/gfx developer \ o.O| http://www.linux-fbdev.org =(_)= http://linuxgfx.sourceforge.net U http://linuxconsole.sourceforge.net |
From: Geert U. <ge...@li...> - 2000-09-22 11:50:21
|
On Thu, 21 Sep 2000, Paolo Scaffardi wrote: > Please, could you explain me differences between /dev/tty, /dev/tty0 and > /dev/console? See Documentation/devices.txt > I have an embedded linux box with a custom keyboard and a custom frame > buffer. The keyboard driver sends scancodes to 'handle_scancode' in > keyboard.c and it is not registered as console, or any type of device. > > At the boot i dont specify anything to boot the kernel. > > It uses correctly both the frame buffer console and the keyboard correctly. > > The only problem is that when using other programs, like GII, that opens > /dev/tty to access the keyboard, they dont work and report: > > /dev/tty - device not configured > > Who has to register /dev/tty? How could my keyboard be reached by /dev/tty? Did you enable CONFIG_VT? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: James S. <jsi...@ac...> - 2000-09-16 00:46:36
|
> > I assume you pass `console=ttyS0' (or something like that) to the kernel? > In > > that case no console messages are sent to the console on the frame buffer > > device. > > I dont pass anything to the kernel... in the PPC distribution, a kernel > parameter is CONFIG_SERIAL_CONSOLE that initializes a console using the > serial driver. No parameters are required. It only add a call in > 'console_init()'. > > I looked at the sources, but i still think there's something wrong on > console initialization (this is 'main.c'): > > CONSOLE_INIT > CON_INIT (vt initialization) > CONSOLE_8xx_INIT (serial console on the PPC) > TTY_INIT > RS_8xx_INIT (serial driver on the PPC) > VIDEO_SETUP The above is right. console_init does early terminal setup and initializes hardware that can be called that early. con_init and console_8xx_init are examples of drivers that can be called early. Later tty_init initialized hardware that needs things like pci to be setup for it. That is why fbcon is called later. Because fbcon can not be called early a dummy console is setup first. Then fbcon takes over this dummy console. > Then, i see that VT is not registered because at CON_INIT, the functions > tests the value of 'conswitchp' before running any 'con_startup' function, > and it is NULL. Who should initialize it if this function has to be called > before any other one that initializes the framebuffer? I cannot change > virtual terminal because VT is not registered, then there is something wrong > on this, isnt it? No. conswitchp is setup in some c file in the arch directory. For the PPC look at linux/arch/ppc/kernel chrp_setup.c: conswitchp = &dummy_con; pmac_setup.c: conswitchp = &dummy_con; prep_setup.c: conswitchp = &vga_con; > > You may want to try `console=tty0 console=ttyS0' to get console output on > both > > the frame buffer device and the serial console. Input for the console will > > come from the last console= argument (i.e. the serial console, cfr. > > Documentation/serial-console.txt). > > Sorry, but it still doesnt work! Did you enable Support for console on virtual terminal after the Virtual terminal option ? MS: (n) 1. A debilitating and surprisingly widespread affliction that renders the sufferer barely able to perform the simplest task. 2. A disease. James Simmons [jsi...@li...] ____/| fbdev/console/gfx developer \ o.O| http://www.linux-fbdev.org =(_)= http://linuxgfx.sourceforge.net U http://linuxconsole.sourceforge.net |