Questions on new framebuffer API:

[Antonino D. <ad...@po...>]

Hi,

I just downloaded the ruby tree and tried it.  It compiles without
errors and the sytem boots okay.  It seems that tty0 was used only for
"printk" console dumps since I wasn't able to see a login prompt
afterwards.  I was able to switch to tty1 and login from there.  Is this
"normal" for the  current snapshot?

Secondly, is the new framebuffer API already workable?  I looked at some
of the specific driver codes and a few have already been ported
(aty128fb, pm3fb, vga16fb, etc).  I tried vga16fb (only one that works
for the i810 chipset), it fails to compile with "undefined reference to
spinlock_init" although changing "spinlock_init" to "spin_lock_init" in
vga16fb.c seems to correct the error (not sure if this is the correct
way to do this).  I enabled "framebuffer console support" in the kernel
config and rebooted.  I just got a blank/corrupted screen though, and
the machine never finished the booting and locks up at the end.  Never
got to log any debugging messages to a file.  

I'm asking the above since while trying to write an i810 driver for the
new API, I met the same problem as with the vga16fb.  The "check_var"
and "set_var" fb_ops seem to work since I was able to properly set the
video mode using those functions during a test.  I was able to directly
write to info->screen_base and correctly display the pixel data. I was
also able to use cfb_rectfill to display a 64x64 pixel square.

Anything I might have missed or anything I need to examine more
closely?  

Thanks.

Tony