Re: 15.nov CVS ruby and some questions

[Aivils S. <Aiv...@un...>]

> I tried 15.nov CVS ruby.  It is similiar to 29.oct ruby in that
> it works without framebuffer console, and hang with it.

Your previous report contain "I can read oopses" - that mean
matrox fb driver works corectly. fbcon works now on G550.
You can test possible conflict code with disabling all.
I wait for Svetoslav results.

> My previous attempts with 29.oct ruby and G550 framebuffer consoles
> was with devfs. Running without devfs still crashes.
>
>
> There are some things I wonder about.
> Ruby without framebuffer console is compiled with vga console
> (it isn't even possible to deselect it in menuconfig)
> But I don't get a useable vga console.  The framebuffer (without
> console) takes over and there is no switching back.
> Perhaps this isn't ruby specific, but I wonder if it is
> supposed to be that way?

While James work with fbdev, fb device and fb console is
independ. I keep this feature. You can load fbcon module
after init process done.
On fb device init should nothing happen , excluded
2-3 lines of printk output.
On fbcon init screen should show new console.

> The use of dumbcon is another thing.  I use dumbcon=1 because
> I found that in a howto.  Will that be unnecessary when
> the framebuffer consoles work someday?

Each console binded with keyboard, included fbcon,
which creates VT for each fb device.

> I have the understanding that "dumbcon" is something that
> attach a keyboard to a vt, so X may get keyboard input,
> while the dumbcon actually doesn't display anything.

Yes. Good enough for xf86 fans :o))

> I happen to have two framebuffers, so running consoles on both,
> with one keyboard on each ought to be possible.  There seem to
> be no need for a "dumbcon" then, the second framebuffer ought
> to get a keyboard and set of vt's just like the first one.
By default framebuffer have not console, according 2.6.X ideology.
I create simple fb_console_init() - go through registerd fb devices
and create VT for each fbdev. When detected new keyboard, then
routine kbd_connect() search and attach keyboardless VT. After
link console-keyboard is ready.

> But
> how do I arrange that?  How can I tell the kernel which
> keyboard goes with what framebuffer?

Current CVS allow remap VT-keyboard link via /proc.
VT-fbdev link is hidden :o(

Underwater cliffs located everywhere.

Aivils Stoss