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
[email protected]
cu,
Knut
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
