Message-ID: <4385F6A8.60808@t-online.de>
Date: Thu, 24 Nov 2005 18:21:44 +0100
From: Knut Petersen <Knut_Petersen@t-online.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.7.7) Gecko/20050414
MIME-Version: 1.0
To: nathan.cline@gmail.com
CC: linux-fbdev-devel@lists.sourceforge.net,
       Linux Kernel Development <linux-kernel@vger.kernel.org>,
       "Antonino A. Daplas" <adaplas@gmail.com>
Subject: Patch to framebuffer
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1335
Lines: 40

Hi Nathan,

Updating only one framebuffer console at a time is a real feature for me,
it allows a really quick developement cycle:

            compile vesafb into the kernel, cyblafb as a module
            start with vesafb
loop:    load cyblafb
            switch to cyblafb, test it
            correct bugs, compile new cyblafb module
            switch to vesafb
            unload vesafb
            goto loop
           
Although both vesafb and cyblafb control the same hardware, this is
possible because of the "feature" you want to remove.

On the other hand I do understand that your patch is valuable, if I had
two monitors attached I certainly would like to be able to use both at the
same time.

I believe that you should introduce your code either as a compile time
option or even better it should be possible to disable it via sysfs:

     /sys/class/graphics/fb?/update_mode

0 could be the default and would activate your new code
1 would restore the old "one active" mode.

Please  consider my arguments and join us at

linux-fbdev-devel@lists.sourceforge.net

cu,
 Knut
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/