On Wed, 2007-05-16 at 16:17 -0700, David Miller wrote:

From: "Antonino A. Daplas" <adaplas@gmail.com>
Date: Thu, 17 May 2007 07:15:05 +0800

quoted

A flag may be the easiest. But we can also define an arch-specific
function (ie, fb_get_primary_device()) in asm/fb.h. With the x86, this
can be easily done by checking the IORESOURCE_ROM_SHADOW bit flag.  

I'll add this for the x86, and then perhaps others can follow suit.

What would this iterate over?  The list of all registered
fb_info's?

For each driver that calls register_framebuffer(), fbcon will check if
it is the primary device.  If it is, it will revise the
console-to-framebuffer mapping (with set_con2fbmap()).

So something like this can happen:

fb0 registers and becomes the default console for vc0-vc63, for the
moment.

fb1 registers, and it is the primary device.  fbcon now maps fb1 to
vc0-vc63.

fb2 registers, it is not the primary device.  fbcon ignores fb2.

fb3 registers, it drives the same hardware as fb1, and thus is also the
primary device.  fbcon still ignores fb3 since fb1 is already determined
to be as the primary device.

All the above is overridden by using the fbcon=map: option.

Most of the pieces are already in place (ie the console-to-framebuffer
remapping), so there should be minimal work for fbcon.

The question is, will this work for sparc?

Tony



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/