From: Russell King <rmk@arm.linux.org.uk>
To: James Simmons <jsimmons@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: [BK PATCHS] fbdev updates.
Date: Fri, 18 Oct 2002 22:37:08 +0100 [thread overview]
Message-ID: <20021018223708.C15827@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0210181421110.3591-100000@maxwell.earthlink.net>; from jsimmons@infradead.org on Fri, Oct 18, 2002 at 02:24:48PM -0700
On Fri, Oct 18, 2002 at 02:24:48PM -0700, James Simmons wrote:
> Your right. That is a bug from the old fbgen code. Since few driver used
> the old fbgen code it never appeared. I suggest we remove can_soft_blank
> and just test to see if the function pointer exist for fb_blank. If it
> doesn't then we can resort to other tricks in suggested in the ther email.
Ok. What about the case where you're running in true colour / static
pseudo colour, and can't blank the palette, but do have a fb_blank
method to handle the direct colour / pseudo colour case?
--
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-18 21:37 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
2002-10-18 17:27 ` James Simmons
2002-10-18 18:32 ` Russell King
2002-10-18 21:24 ` James Simmons
2002-10-18 21:37 ` Russell King [this message]
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=20021018223708.C15827@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).