From: Jon Smirl <jonsmirl@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
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: Mon, 8 Aug 2005 15:01:24 -0400 [thread overview]
Message-ID: <9e473391050808120111ee33ee@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0508081939260.27739@pentafluge.infradead.org>
On 8/8/05, James Simmons <jsimmons@infradead.org> wrote:
>
> > > au1100fb int nohwcursor
> > > intelfb int hwcursor
> > > nvidia int hwcur
> > > cyberfb
> > >
> > > You need to remove this!!!!
> > >
> > > What I am arguing is that drivers with hardware cursor support should be
> > > able to turn off and on hardware cursor support. That is why the
> > > HWACCEL_CURSOR flag. Your test the fb_cursor field prevents this!!!
> >
> > If you want fbconsole to use the software cusor instead of the
> > hardware cursor, that's between you and fbconsole to decide. Control
> > over that choice needs to be in fbconsole, not the base fbdev.
> >
> > The fbdev drivers should just unconditionally offer the hardware
> > cursor if they support it. It is up to the user of the cursor to
> > choose whether to use it or ignore it.
>
> Finally you see the point I was making. I wanted it be very clear to every
> one here the implications of your changes. You remove the power to control
> the use of a hardware cursor from the driver. At this point driver writers
> need to speak up if they have no problem with this.
I'm not working on fbconsole so it did not occur to me what your
issues was. My user space apps have always had control of whether they
used the hardware cursor or not.
You will need to ask Tony for a switch. Easiest way is to make it a
module parameter on fbconsole. That way it will appear in
/sys/module/fbconsole/parameters and you can use echo to set it from a
script. There is no need for an ioctl.
It only takes about five lines of code to implement this, something like this...
fbconsole.c
int use_hw_cursor = 0;
module_parm(use_hw_cursor);
if (fb_info->fb_cursor && use_hw_cursor)
fb_info->fb_cursor(...)
else
softcursor
>
> P.S
> The patch still needs to broken into smaller pieces.
>
>
>
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-08-09 23:44 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 [this message]
2005-08-08 19:07 ` Jon Smirl
2005-08-08 23:55 ` Antonino A. Daplas
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=9e473391050808120111ee33ee@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=adaplas@hotpop.com \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--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).