Re: [Linux-fbdev-devel] 2 pm3fb questions/problesm ...

[James S. <jsi...@tr...>]

> I'm far off the mark :-) I've ripped-off pm2fb for pm3fb, so
> there's _set_var before the register_frambuffer. That's
> also the way it's done in skeletonfb...

_set_var must be called before register_framebuffer. Otherwise the machien
will oops. regsiter_framebuffer calls take_over_console which calls
fbcon_startup which expects a struct display disp in fb_info to be
initialized. info->disp is initalized in xxxfb_set_var. 

> So, is there any way to prevent vgacon to try to force is
> way inside the memory that rightfully belong to pm3fb ? :-)
> That way, there would be neither previous content nor
> garbage...

Has nothing to do with vgacon. I bet it is vc_resize that is having
problems. How Do I know this. Because I rewrote vc_resize for ruby and 
I had these same problem until I fixed them. Plus most PC cards are
designed to startup in vga text mode. Unless you flash the card bios, if
possible, you are stuck with it.