From: Jon Smirl <jonsmirl@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: fbdev hardware cursor support
Date: Fri, 27 May 2005 20:31:19 -0400 [thread overview]
Message-ID: <9e47339105052717311dc73685@mail.gmail.com> (raw)
In-Reply-To: <1117035165.5677.386.camel@localhost>
On 5/25/05, Michel Dänzer <michel@daenzer.net> wrote:
> > > David Reveman pointed out that Xglx has working software cursor code. I
> > > can't see that caring about whether glitz uses a GLX or EGL backend.
> >
> > Xglx gets it software cursor support from the nested X server it runs
> > inside of.
>
> You didn't even read David's correction of this. Great.
Three days later I have software cursors working. It wasn't anywhere
near as simple as turning on a flag. They're ugly and they lag, but
they can probably be fixed with more effort. I would have had the
hardware one up in a day at most since I knew exactly what was doing.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
next prev parent reply other threads:[~2005-05-28 0:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 5:40 fbdev hardware cursor support Jon Smirl
2005-05-25 6:16 ` Ville Syrjälä
2005-05-25 14:10 ` Jon Smirl
2005-05-25 14:50 ` Michel Dänzer
2005-05-25 15:08 ` Jon Smirl
2005-05-25 15:22 ` Michel Dänzer
2005-05-25 15:30 ` Jon Smirl
2005-05-25 15:32 ` Michel Dänzer
2005-05-25 15:52 ` Jon Smirl
2005-05-28 0:31 ` Jon Smirl [this message]
2005-06-06 18:42 ` James Simmons
2005-06-06 19:33 ` Jon Smirl
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=9e47339105052717311dc73685@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=michel@daenzer.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).