linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: fbdev hardware cursor support
Date: Wed, 25 May 2005 11:22:27 -0400	[thread overview]
Message-ID: <1117034547.5506.376.camel@localhost> (raw)
In-Reply-To: <9e47339105052508084ee66dd2@mail.gmail.com>

On Wed, 2005-05-25 at 11:08 -0400, Jon Smirl wrote:
> On 5/25/05, Michel Dänzer <michel@daenzer.net> wrote:
> > > Software generated will be supported sooner or later but the code is
> > > not written yet.
> > 
> > These claims of yours have been refuted on the dri-egl list. Why are you
> > repeating them here?
> 
> I'm writing the Xegl server and I can tell you for sure that I haven't
> written the software cursor support yet. How can you know the status
> of the Xgl code when I haven't checked it into CVS yet?

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.

> Personally I'd prefer to start with the hardware one which I know will
> work. Drawing in Xgl is not stable and there is a good chance a
> software generated cursor isn't going to work half of the time until
> the code is fixed.

And for the hardware cursor, you only need to:

      * enable/implement/improve (does what is disabled right now even
        remotely fit the needs of an X server? I didn't think so) the
        fbdev hardware cursor support
      * design and implement an EGL extension for it
      * add support for that to glitz
      * add support for that to Xegl

Indeed, that seems much easier and less prone to problems...


PS: Please don't add random e-mail addresses to the CC: list.

-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer



-------------------------------------------------------
SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
online with coworkers and clients while avoiding the high cost of travel and
communications. There is no equipment to buy and you can meet as often as
you want. Try it free.http://ads.osdn.com/?ad_idt02&alloc_id\x16135&op=click

  reply	other threads:[~2005-05-25 15:23 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 [this message]
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
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=1117034547.5506.376.camel@localhost \
    --to=michel@daenzer.net \
    --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).