From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
"Ville Syrjälä" <syrjala@sci.fi>
Cc: Andrew Morton <akpm@osdl.org>, Olaf Hering <olh@suse.de>
Subject: Re: [PATCH 7/8] fbdev: atyfb_base.c requires atyfb_cursor()
Date: Wed, 3 Nov 2004 05:31:36 +0800 [thread overview]
Message-ID: <200411030531.36468.adaplas@hotpop.com> (raw)
In-Reply-To: <20041102135843.GA13761@sci.fi>
On Tuesday 02 November 2004 21:58, Ville Syrjälä wrote:
> On Tue, Nov 02, 2004 at 07:46:26PM +0800, Antonino A. Daplas wrote:
> > atyfb_base.c requires atyfb_cursor, but it is only available for linking
> > if CONFIG_FB_ATY_CT=y.
> > This patch moves the .o file to the CONFIG_FB_ATY rule.
>
> Here's a better fix. It was a part of my swcursor patch which was
> partially included. Looks like Alex accidentally dropped this part.
>
>
> Fix atyfb cursor problems:
> - oops with noaccel option
> - CONFIG_FB_ATY_CT dependency problem
>
If I read Alex's patch correctly, it looks like the aty has a working
hardware cursor implementation, is this correct? Then a better patch may be
to use soft_cursor if noaccel is true, and atyfb_cursor otherwise.
Tony
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
next prev parent reply other threads:[~2004-11-02 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 11:46 [PATCH 7/8] fbdev: atyfb_base.c requires atyfb_cursor() Antonino A. Daplas
2004-11-02 13:14 ` S1D13506 CRT ramprasad
2004-11-02 13:58 ` [PATCH 7/8] fbdev: atyfb_base.c requires atyfb_cursor() Ville Syrjälä
2004-11-02 21:31 ` Antonino A. Daplas [this message]
2004-11-02 22:26 ` Ville Syrjälä
2004-11-03 2:39 ` Antonino A. Daplas
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=200411030531.36468.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=olh@suse.de \
--cc=syrjala@sci.fi \
/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).