From: Russell King <rmk@arm.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCHS] fbdev updates.
Date: Tue, 15 Oct 2002 10:38:33 +0100 [thread overview]
Message-ID: <20021015103833.C9771@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.GSO.4.21.0210151109180.25245-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Tue, Oct 15, 2002 at 11:14:03AM +0200
On Tue, Oct 15, 2002 at 11:14:03AM +0200, Geert Uytterhoeven wrote:
> So the generic part of the code should behave like this:
>
> if (info->fbops->fb_blank && info->fbops->fb_blank(blank_flag)) {
> /* use hardware blanking */
> } else if (info->fix.visual == FB_VISUAL_PSEUDOCOLOR ||
> info->fix.visual == FB_VISUAL_DIRECTCOLOR) {
> /* use software blanking */
> } else {
> /* no blanking possible, except for filling the screen with black, which
> is not appropriate (unless we save/restore the contents?) */
> }
>
> Is that OK for you?
That's fine for me, but I'd expect other people to find problems with it.
Would it not be better to allow drivers to decide which type of blanking
they want to use depending on the current parameters set via the set_par
callback? Only the drivers themselves know what their fb_blank method is
capable of performing.
I think with the above you'll inadvertently encourage drivers to mundge
the fb_blank function pointer in their set_par method.
There is also the argument about wanting soft blanking, but hardware power
saving.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-10-15 9:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 20:33 [BK PATCHS] fbdev updates James Simmons
2002-10-14 10:10 ` Geert Uytterhoeven
2002-10-14 16:39 ` James Simmons
2002-10-15 8:38 ` Geert Uytterhoeven
2002-10-18 16:48 ` James Simmons
2002-10-15 9:00 ` Russell King
2002-10-15 9:14 ` Geert Uytterhoeven
2002-10-15 9:38 ` Russell King [this message]
2002-10-18 17:27 ` James Simmons
2002-10-18 18:32 ` Russell King
2002-10-18 21:24 ` [Linux-fbdev-devel] " James Simmons
2002-10-18 21:37 ` Russell King
2002-10-22 17:13 ` Geert Uytterhoeven
2002-10-18 17:16 ` James Simmons
2002-10-18 17:05 ` James Simmons
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=20021015103833.C9771@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 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).