From: Knut Petersen <Knut_Petersen@t-online.de>
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
Date: Thu, 24 Nov 2005 18:21:44 +0100 [thread overview]
Message-ID: <4385F6A8.60808@t-online.de> (raw)
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
WARNING: multiple messages have this Message-ID (diff)
From: Knut Petersen <Knut_Petersen@t-online.de>
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
Date: Thu, 24 Nov 2005 18:21:44 +0100 [thread overview]
Message-ID: <4385F6A8.60808@t-online.de> (raw)
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
next reply other threads:[~2005-11-24 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 17:21 Knut Petersen [this message]
2005-11-24 17:21 ` Patch to framebuffer Knut Petersen
-- strict thread matches above, loose matches on Subject: below --
2005-11-24 6:08 Nathan Cline
2005-11-24 7:43 ` Antonino A. Daplas
2005-11-24 8:49 ` Antonino A. Daplas
2005-11-24 9:08 ` Matt Keenan
2005-11-24 9:46 ` Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4385F6A8.60808@t-online.de \
--to=knut_petersen@t-online.de \
--cc=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan.cline@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.