Ian Romanick wrote:
>
> On Tue, Apr 23, 2002 at 12:31:46AM +0100, Keith Whitwell wrote:
> > Ian Romanick wrote:
> > > What ends up happening is glXGetProcAddress returns the address of the
> > > glBegin symbol from my executable (in this case the address of the pointer
> > > to function) instead
On Tue, Apr 23, 2002 at 12:31:46AM +0100, Keith Whitwell wrote:
> Ian Romanick wrote:
> > What ends up happening is glXGetProcAddress returns the address of the
> > glBegin symbol from my executable (in this case the address of the pointer
> > to function) instead of the address of the glBegin sym
Ian Romanick wrote:
>
> I may be totally misunderstanding glXGetProcAddress, but it seems to me that
> the following *should* be valid:
>
> void (*glBegin)( GLenum mode ) = NULL;
>
> void begin_wrapper( GLenum mode )
> {
> if ( glBegin == NULL )
> {
> glBegin = glXGetProcAddress
Peter,
The status of the current Mach64 driver is very well documented by Leif on
it's homepage, http://www.retinalburn.net/linux/dri_status.html. As you
can see there, things aren't yet finished but are shaping up. There is a
problem though: so far no attempt has been made to get it running o
I may be totally misunderstanding glXGetProcAddress, but it seems to me that
the following *should* be valid:
void (*glBegin)( GLenum mode ) = NULL;
void begin_wrapper( GLenum mode )
{
if ( glBegin == NULL )
{
glBegin = glXGetProcAddress( "glBegin" );
}
(*glBegin)( m
Hi,
due to my limited hardware equipment I implemented a mechanism that
automatically detects X server deadlocks and recovers from them as long
as the Kernel isn't locked either. It consists of a C programme which
detects the lockup and a shell script which starts the xserver and uses
kbd_mode an
I had CC'd to dri-devel but for some reason it didn't reached to the list
so I'm sending it again.
On 2002.04.22 18:37 José Fonseca wrote:
Peter,
The status of the current Mach64 driver is very well documented by Leif on
it's homepage, http://www.retinalburn.net/linux/dri_status.html. As you
On Mon, 2002-04-22 at 20:04, José Fonseca wrote:
> On 2002.04.22 18:45 Leif Delgass wrote:
> > Unfortunately, the driver doesn't support ppc yet. It will probably be
> > some time before that is added, as we still need to complete the driver
> > for x86. I think Frank Earl worked on ppc support
On 2002.04.22 18:45 Leif Delgass wrote:
> Unfortunately, the driver doesn't support ppc yet. It will probably be
> some time before that is added, as we still need to complete the driver
> for x86. I think Frank Earl worked on ppc support for the XFree 3.x
> utah-glx driver, but I'm not sure if
Unfortunately, the driver doesn't support ppc yet. It will probably be
some time before that is added, as we still need to complete the driver
for x86. I think Frank Earl worked on ppc support for the XFree 3.x
utah-glx driver, but I'm not sure if it's complete.
There's a ppc branch in DRI CV
After missing it several times on your home page i finally saw that
development for Ati Mach64 is underway. So i just thought i would
announce my interest in the project. I don´t know anything about writing
code but if you need some "test pilots" please let me know. I am
currently using an Ibo
On 2002.04.22 15:58 Jens Owen wrote:
> "José Fonseca" wrote:
> >
> > Nightly snapshots of tcl-0-0-branch are now also available from
> > http://dri.sourceforge.net/snapshots/bleeding-edge/ with the name
> > radeon-tcl-* . Now is really very easy to build any other branch.
>
> Jose,
>
> Nice work
"José Fonseca" wrote:
>
> Nightly snapshots of tcl-0-0-branch are now also available from
> http://dri.sourceforge.net/snapshots/bleeding-edge/ with the name
> radeon-tcl-* . Now is really very easy to build any other branch.
Jose,
Nice work. I'm going to continue building the TG version of th
Martin Spott wrote:
>
> > Can people with outstanding problems wrt. the tcl branch please let me
> > know.
>
> I have been reporting some synchronization issues two weeks ago and an
> additional EMail yesterday. Unfortunately the latter didn't reach the list,
Can you forward them to me again?
> Can people with outstanding problems wrt. the tcl branch please let me
> know.
I have been reporting some synchronization issues two weeks ago and an
additional EMail yesterday. Unfortunately the latter didn't reach the list,
Martin.
--
Unix _IS_ user friendly - it's just selective about who
Can people with outstanding problems wrt. the tcl branch please let me know.
I'd like to get that code merged pretty soon, perhaps by the end of the month.
Keith
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo
16 matches
Mail list logo
