* Patch to framebuffer
@ 2005-11-24 17:21 Knut Petersen
0 siblings, 0 replies; only message in thread
From: Knut Petersen @ 2005-11-24 17:21 UTC (permalink / raw)
To: nathan.cline
Cc: linux-fbdev-devel, Linux Kernel Development, Antonino A. Daplas
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
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-11-24 17:21 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-24 17:21 Patch to framebuffer Knut Petersen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).