Ingo Oeser wrote:

Hi Antonio,

On Friday, 9. June 2006 10:40, Antonino A. Daplas wrote:

quoted

    5. When fbcon is completely unbound from the console layer, fbcon will
       also release (iow, decrement module reference counts to zero) all fbdev
       drivers. In other words, a bind or unbind request from the console layer
       will propagate down to the framebuffer drivers.

    6. If fbcon is not bound to the console, it will ignore all notifier
       events (except driver registration and unregistration) and all sysfs
       requests.

Wow! 

Now one can:

	- implement different framebuffer drivers for a chip. 
	- try a stable and development version without rebooting,
	- have probing with user interaction ("if you see me please 
	  press enter else I will try the previous driver in 15 seconds.") 
	  instead of deciding on "failsafe" (vga/vesa) and "fast" 
	  (special driver) at boot.

Yes, all of the above are possible :-), and with our present user tools,
are currently very, very doable (at least in x86).

I love it!

Just the take_over_console() as alternative API looks strange.

It's not an alternative API, it's the default API and behavior. So, I
just can't remove it without breaking all console drivers.

Tony