From: Keith Packard <keithp@keithp.com>
To: Kenneth Graunke <kenneth@whitecape.org>,
Emil Velikov <emil.l.velikov@gmail.com>,
mesa-dev@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] Don't use libudev for glx/dri3
Date: Sun, 17 Nov 2013 22:03:01 -0800 [thread overview]
Message-ID: <86mwl29rhm.fsf@miki.keithp.com> (raw)
In-Reply-To: <528992C7.9030507@whitecape.org>
[-- Attachment #1.1: Type: text/plain, Size: 411 bytes --]
Kenneth Graunke <kenneth@whitecape.org> writes:
> For non-API facing stuff, you can just use stdbool.h's
> bool/true/false.
tnx. I pushed that to my dri3 branch. Btw, that branch also has some
gallium support for __DRIimageDriverExtension. I don't have any hardware
to test with, so it's surely broken in some major ways, but it might
show where the hooks need to be.
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
next prev parent reply other threads:[~2013-11-18 6:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 0:55 [PATCH] Don't use libudev for glx/dri3 Keith Packard
2013-11-18 1:08 ` Keith Packard
2013-11-18 1:31 ` Emil Velikov
2013-11-18 2:43 ` Keith Packard
2013-11-18 4:08 ` Kenneth Graunke
2013-11-18 6:03 ` Keith Packard [this message]
2013-11-18 21:59 ` Ian Romanick
2013-11-18 20:58 ` Emil Velikov
2013-11-19 6:46 ` Keith Packard
2013-12-14 2:33 ` Kenneth Graunke
2013-12-14 10:37 ` [Mesa-dev] " Daniel Vetter
2013-12-16 19:19 ` Eric Anholt
2013-12-16 19:57 ` [Mesa-dev] " Daniel Vetter
2013-11-19 18:41 ` Eric Anholt
2013-11-19 19:41 ` Keith Packard
2013-11-19 20:19 ` [Mesa-dev] " Eric Anholt
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=86mwl29rhm.fsf@miki.keithp.com \
--to=keithp@keithp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=kenneth@whitecape.org \
--cc=mesa-dev@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.