linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Jon Smirl <jonsmirl@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	"Antonino A. Daplas" <adaplas@hotpop.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Re: [PATCH] mach64 atari patch
Date: Tue, 09 Aug 2005 07:55:58 +0800	[thread overview]
Message-ID: <42F7F10E.7080700@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0508081907150.27739@pentafluge.infradead.org>

James Simmons wrote:
>>>> I just don't think this patch is as complex as you are making it out
>>>> to be. It is large simply because the same action has been repeated
>>>> for each of the 65 drivers. The action is only a simple deletion of
>>>> two lines.
>>> I'm not arguing over this. What is wrong with breaking this patch up!!!!!
>>> I still have no answer to this!!!! I'm using the hardware flag because
>>> sometimes the driver that does have a hardware cursor wants to turn
>>> support off for it.
>> Set  .fb_cursor = NULL; to turn off the support.
> 
> So forbid hardware drivers that support hware cursors to never turn off 
> there hardware cursor support!!!!!
> 
> Let see what drivers have a flag to control using the hardware cursor.
> 
> au1100fb	int nohwcursor
> intelfb		int hwcursor
> nvidia		int hwcur
> cyberfb
> 
> You need to remove this!!!!
>

Majority of the drivers that does support hardware cursors are written by myself.
If the driver does not want to turn on the hardware cursor, just return -ENODEV.
No need to fudge with pointers.

Tony 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-08-09 23:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07  2:27 [PATCH] mach64 atari patch James Simmons
2005-08-07 11:39 ` Geert Uytterhoeven
2005-08-07 16:46   ` Andrew Morton
2005-08-07 23:09     ` James Simmons
2005-08-07 23:31       ` Antonino A. Daplas
2005-08-07 23:48         ` Jon Smirl
2005-08-08 17:30           ` James Simmons
2005-08-08 17:56             ` Jon Smirl
2005-08-08 18:15               ` James Simmons
2005-08-08 18:34                 ` Jon Smirl
2005-08-08 18:44                   ` James Simmons
2005-08-08 19:01                     ` Jon Smirl
2005-08-08 19:07                       ` Jon Smirl
2005-08-08 23:55                 ` Antonino A. Daplas [this message]
2005-08-09  0:04         ` James Simmons
2005-08-09  0:59           ` Antonino A. Daplas
2005-08-09  1:08             ` Antonino A. Daplas
2005-08-09  8:05             ` Geert Uytterhoeven
2005-08-09  1:04           ` Jon Smirl
2005-08-12 17:47   ` James Simmons
2005-08-08 19:49 ` Alexander Kern

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=42F7F10E.7080700@gmail.com \
    --to=adaplas@gmail.com \
    --cc=adaplas@hotpop.com \
    --cc=akpm@osdl.org \
    --cc=geert@linux-m68k.org \
    --cc=jonsmirl@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 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).