[Bug 17381] New: mesa build failed for dri2

http://bugs.freedesktop.org/show_bug.cgi?id=17381

           Summary: mesa build failed for dri2
           Product: Mesa
           Version: unspecified
          Platform: Other
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Other
        AssignedTo: mesa3d-dev <at> lists.sourceforge.net
        ReportedBy: haien.liu <at> intel.com
                CC: shuang.he <at> intel.com

when compile mesa ,it failed with below info:
---------------
dri2.c: In function ‘DRI2GetBuffers’:
dri2.c:208: error: ‘xDRI2GetBuffersReply’ undeclared (first use in this
function)
dri2.c:208: error: (Each undeclared identifier is reported only once
dri2.c:208: error: for each function it appears in.)
dri2.c:208: error: expected ‘;’ before ‘rep’
dri2.c:209: error: ‘xDRI2GetBuffersReq’ undeclared (first use in this
function)
dri2.c:209: error: ‘req’ undeclared (first use in this function)
dri2.c:211: error: ‘xDRI2Buffer’ undeclared (first use in this function)
dri2.c:211: error: expected ‘;’ before ‘repBuffer’
dri2.c:218: error: ‘sz_xDRI2GetBuffersReq’ undeclared (first use in this
function)

[Bug 17381] mesa build failed for dri2

http://bugs.freedesktop.org/show_bug.cgi?id=17381

--- Comment #1 from liuhaien <haien.liu <at> intel.com>  2008-08-31 23:26:18 PST ---
xserver also cannot build against dri2:
../hw/xfree86/dri2/dri2.h:36:39: error: X11/extensions/dri2tokens.h: No such
file or directory
glxdri2.c:72: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or
‘__attribute__’ before ‘*’ token
glxdri2.c:93: error: expected specifier-qualifier-list before ‘__DRIbuffer’
glxdri2.c: In function ‘__glXDRIbindTexImage’:
glxdri2.c:205: error: ‘__GLXDRIscreen’ has no member named ‘texBuffer’
glxdri2.c: In function ‘__glXDRIscreenCreateContext’:
glxdri2.c:295: error: ‘__GLXDRIscreen’ has no member named ‘dri2’
glxdri2.c: In function ‘__glXDRIscreenCreateDrawable’:
glxdri2.c:336: error: ‘__GLXDRIscreen’ has no member named ‘dri2’
glxdri2.c: At top level:
glxdri2.c:342: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
glxdri2.c:375: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘loaderExtension’
glxdri2.c:382: error: ‘loaderExtension’ undeclared here (not in a function)
glxdri2.c: In function ‘initializeExtensions’:
glxdri2.c:425: error: ‘__GLXDRIscreen’ has no member named
‘glx_enable_bits’
glxdri2.c:426: warning: passing argument 1 of ‘__glXEnableExtension’ from
incompatible pointer type
glxdri2.c:432: error: ‘__GLXDRIscreen’ has no member named
‘swapControl’
glxdri2.c:433: warning: statement with no effect
glxdri2.c:434: error: ‘__GLXDRIscreen’ has no member named

Reg: AIGLX architecture & it's difference from DRI

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

demos/fogcoord not work good on r200 (black lines)

  I try demos/fogcoord and it show some diagonal black lines when move camera
with Z/z. This happens in any Mesa version i tried (6.4.1 >> 7.1) with r200
driver in tcl_mode 3,2 or 1. With tcl_mode=0 (sw)
it is correct or with Xlib Mesa. I also tried to change cam +- to
smaller/bigger values but that not help.
With smaller, black lines renders much more and with bigger it also display
but less. 

 If someone want quick look on this - video is attached.
http://www.nabble.com/file/p19252860/r200_hwtcl.lzma r200_hwtcl.lzma 
--

-- 
View this message in context: http://www.nabble.com/demos-fogcoord-not-work-good-on-r200-%28black-lines%29-tp19252860p19252860.html
Sent from the mesa3d-dev mailing list archive at Nabble.com.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: demos/fogcoord not work good on r200 (black lines)

On 01.09.2008 13:08, smoki wrote:
>   I try demos/fogcoord and it show some diagonal black lines when move camera
> with Z/z. This happens in any Mesa version i tried (6.4.1 >> 7.1) with r200
> driver in tcl_mode 3,2 or 1. With tcl_mode=0 (sw)
> it is correct or with Xlib Mesa. I also tried to change cam +- to
> smaller/bigger values but that not help.
> With smaller, black lines renders much more and with bigger it also display
> but less. 
> 
>  If someone want quick look on this - video is attached.
> http://www.nabble.com/file/p19252860/r200_hwtcl.lzma r200_hwtcl.lzma 

This seems reproducible on rv250 too (never noticed it before...). Note
that it's completely independent of the fog settings, so I'm not sure
what's going on. It reminds me of some bugs though we fought a lot a
long time ago, which were solved by using a fixed ordering of emitting
state atoms - the more correct solution finally was to write to the
RADEON_SE_TCL_STATE_FLUSH when emitting certain tcl state. Maybe those
tcl flushes still don't quite happen always when necessary, it isn't
well understood really when exactly that's necessary.

Roland

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: demos/fogcoord not work good on r200 (black lines)

 I tried to change near value in glfrustum() from 1.0 to 0.9 and then it's
OK. The same issue happen when tried to use gluPerspective(90, 1.0, 1.0,
100) instead of glfrustum(), but if i change fovy value to 89.9 or (seem
to?) any other then 90 = no black lines;).
--

-- 
View this message in context: http://www.nabble.com/demos-fogcoord-not-work-good-on-r200-%28black-lines%29-tp19252860p19263698.html
Sent from the mesa3d-dev mailing list archive at Nabble.com.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[patch]invert depth/stenval value

Hi, 
   GL_EXT_packed_depth_stencil spec doesn't support 8/24 reversed format
and Mesa doesn't support it as well. Unfortunately Intel devices hold
24-bit Z depth value in lower 3 bytes and 8-bit stencil value in upper
byte, so currently a depth_stencil texture doesn't work well on 915/965.
   The attached patch tries to  fix this issue in mesa core. (Although
this can be done in a device driver, I think it is more simple to do in
mesa core). Could you take a look?

Thanks
Haihao  

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

[Bug 17404] New: glColor3i does not set implicitly the value of the alpha ( RGBA color)

http://bugs.freedesktop.org/show_bug.cgi?id=17404

           Summary: glColor3i does not set implicitly the value of the alpha
                    (RGBA color)
           Product: Mesa
           Version: 6.4
          Platform: All
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: GLX
        AssignedTo: mesa3d-dev <at> lists.sourceforge.net
        ReportedBy: apetrosyan <at> linuxtesting.org

The standard states:
"glColor sets a new four-valued RGBA color. glColor has two major variants:
glColor3 and glColor4. glColor3 variants specify new red, green, and blue
values explicitly and set the current alpha value to 1.0 (full intensity)
implicitly.", but invocation of the glColor3i interface does not set the alpha
value to 1.0 (full intensity).

--

-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[Bug 17404] glColor3i does not set implicitly the value of the alpha ( RGBA color)

http://bugs.freedesktop.org/show_bug.cgi?id=17404

Artak Petrosyan <apetrosyan <at> linuxtesting.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|GLX                         |Mesa core

--

-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[Bug 17407] New: Invocation of the interface glGetString between glBegin and glEnd does not generate GL_INVALID_OPERATION error

http://bugs.freedesktop.org/show_bug.cgi?id=17407

           Summary: Invocation of the interface glGetString between glBegin
                    and glEnd does not generate GL_INVALID_OPERATION error
           Product: Mesa
           Version: 6.4
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Mesa core
        AssignedTo: mesa3d-dev <at> lists.sourceforge.net
        ReportedBy: apetrosyan <at> linuxtesting.org

The standard states:
"GL_INVALID_OPERATION is generated if glGetString is executed between the
execution of glBegin and the corresponding execution of glEnd.", but invocation
of the interface glGetString(GL_VERSION) between glBegin and glEnd does not
generate GL_INVALID_OPERATION error.

--

-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/