From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] tdfxfb: hardware cursor
Date: Sat, 28 Jul 2007 17:22:17 +0800 [thread overview]
Message-ID: <1185614537.9324.2.camel@daplas> (raw)
In-Reply-To: <20070728102635.d31fa8ea.krzysztof.h1@wp.pl>
On Sat, 2007-07-28 at 10:26 +0200, Krzysztof Helt wrote:
> From: Krzysztof Helt <krzysztof.h1@wp.pl>
>
> This patch adds hardware cursor support to the tdfxfb driver.
>
> Signed-off-by: Krzysztof Helt <krzysztof.h1@wp.pl>
>
> ---
>
> This patch requires all tdfxfb patches from the -mm tree and the source code
> improvement patch sent yesterday to this list.
>
> I am not sure if the FB_CUR_SETIMAGE and FB_CUR_SETSHAPE are implemented
> correctly (the mask is always mask and the image is xor or and of the mask and data).
> The cursor works correctly on Voodoo3 2000 PCI with this patch.
>
> I added a separate option to Kconfig to enable this feature but I am eager to remove
> the option and make the hardware cursor always used after someone can confirm
> it is ok on Banshee and Voodoo4/5 (no ifdefs).
I would rather that you make the hardware cursor support permanent
(instead of adding another Kconfig option) and just have a boot option
to enable/disable the hardware cursor.
Tony
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-07-28 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 8:26 [PATCH] tdfxfb: hardware cursor Krzysztof Helt
2007-07-28 9:22 ` Antonino A. Daplas [this message]
2007-07-28 16:28 ` [PATCH] tdfxfb: hardware cursor (no ifdefs) Krzysztof Helt
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=1185614537.9324.2.camel@daplas \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.