On Mit, 2010-11-10 at 18:36 +1100, Russell Shaw wrote:
>
> In mesa/src/driclient/src/XF86dri.c, if i use the
> api to make a drawable, how can i find the buffer
> pixel format?
From the underlying X drawable.
Beware that this is old DRI1 stuff, which shouldn't be used for new
development.
--
Hi,
I compiled mesa from sources.
In mesa/src/driclient/src/XF86dri.c, if i use the
api to make a drawable, how can i find the buffer
pixel format?
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/me
Hi all,
When comparing the buffers created by X11 and OSMesa i found that
the functions that put values to the buffers are different and their logic
is different both take different origins to put values. Is this normal or is
there any changes that should be done ?
https://bugs.freedesktop.org/show_bug.cgi?id=31514
--- Comment #2 from Adrienne Walker 2010-11-09 17:09:21 PST
---
(In reply to comment #1)
> Can you tell me exactly where it says that in the spec (and which version of
> the spec)? I don't doubt you, but I'm having trouble finding that language
Any comment? If no problem, I will check in this fix.
Thanks
Haihao
> Oleksiy Krivoshey reported commit
> b4bb6680200b5a898583392f4c831c02f41e63f7(dri: Unset current context and
> dispatch table when unbinding) causes a regression when he used vaapi
> with OpenGL render output on Ironlake.
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=31514
--- Comment #1 from Brian Paul 2010-11-09 15:57:41 PST ---
Can you tell me exactly where it says that in the spec (and which version of
the spec)? I don't doubt you, but I'm having trouble finding that language.
The original GL_ARB_vertex_buffe
https://bugs.freedesktop.org/show_bug.cgi?id=31514
Summary: isBuffer returns true for unbound buffers
Product: Mesa
Version: 7.9
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Still having the problem , i attached the config file , anybody can help !?
On Fri, Nov 5, 2010 at 5:09 PM, Clurado cl wrote:
> yes , those configs has -DFEATURE_ES1=y
>
>
> On Fri, Nov 5, 2010 at 5:19 AM, Chia-I Wu wrote:
>
>> On Fri, Nov 5, 2010 at 1:34 AM, Clurado cl wrote:
>> >
>> >
>> >
https://bugs.freedesktop.org/show_bug.cgi?id=31439
Brian Paul changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On 11/09/2010 11:00 AM, Francisco Jerez wrote:
Francisco Jerez writes:
Brian Paul writes:
+static GLboolean
+alpha_test_bitmap(struct gl_context *ctx)
+{
+ struct gl_colorbuffer_attrib *color =&ctx->Color;
+ GLenum func = (color->AlphaEnabled ? color->AlphaFunc : GL_ALWAYS);
+ GLubyte
Francisco Jerez writes:
> Brian Paul writes:
>
>>> +static GLboolean
>>> +alpha_test_bitmap(struct gl_context *ctx)
>>> +{
>>> + struct gl_colorbuffer_attrib *color = &ctx->Color;
>>> + GLenum func = (color->AlphaEnabled ? color->AlphaFunc : GL_ALWAYS);
>>> + GLubyte ref = FLOAT_TO_UBYTE(c
On Tue, Nov 9, 2010 at 12:05 PM, Roland Scheidegger wrote:
> On 09.11.2010 17:17, Alex Deucher wrote:
>> On Mon, Nov 8, 2010 at 4:12 PM, Roland Scheidegger
>> wrote:
>>> DD_POINT_SIZE got never set for some time now (as it was set only in ifdefed
>>> out code), which caused the r200 driver to us
On 09.11.2010 17:17, Alex Deucher wrote:
> On Mon, Nov 8, 2010 at 4:12 PM, Roland Scheidegger wrote:
>> DD_POINT_SIZE got never set for some time now (as it was set only in ifdefed
>> out code), which caused the r200 driver to use the point primitive mistakenly
>> in some cases which can only do s
On Mon, Nov 8, 2010 at 4:12 PM, Roland Scheidegger wrote:
> DD_POINT_SIZE got never set for some time now (as it was set only in ifdefed
> out code), which caused the r200 driver to use the point primitive mistakenly
> in some cases which can only do size 1 instead of point sprite. Since the
> log
Have you compiled with --enable-debug option to get more information from
MESA?
What's your INTEL chipset?
art...@arthur-laptop:/sys/class/drm/card0/device$ cat device
0x0046
const static struct pci_device_id pciidlist[] = {
INTEL_VGA_DEVICE(0x3577, &intel_i830_info),
INTEL_VGA_DEVICE(0x2
On Sun, Nov 07, 2010 at 01:21:36PM +0800, Arthur Zhu wrote:
> >
> > The build directions recommend disabling gallium in order to get intel
> > working properly. However I've not gotten a successful build with
> > --disable-gallium added. Unless someone has a suggestion, I'm going to
> > try a mes
On Die, 2010-11-09 at 16:41 +1100, Russell Shaw wrote:
> Hi,
> How should the "format" of a DRI2 buffer be determined?
>
>
> http://www.x.org/releases/current/doc/dri2proto/dri2proto.txt
>
> DRI2ATTACH_FORMAT { attachment: CARD32
> format: CARD32 }
>
> The DRI2ATTACH_FORM
17 matches
Mail list logo
