search for: 3dlabs

Hi all, Has anybody managed to make this board: 3DLabs Wildcat III 6210 work under CentOS 4/Xorg ? I see on their website they had support for it until RHEL3 but no more support for RHEL4... I tried the 'glint' driver but it does not support this particular chipset. I tried the 'vesa' mode and I could get a 640x480 @ 60Hz but it's...

...2759 3. Relevant releases/architectures: Red Hat Linux 6.0, all architectures 4. Obsoleted by: 5. Conflicts with: 6. RPMs required: Intel: ftp://updates.redhat.com/6.0/i386/ XFree86-3.3.3.1-52.i386.rpm XFree86-100dpi-fonts-3.3.3.1-52.i386.rpm XFree86-75dpi-fonts-3.3.3.1-52.i386.rpm XFree86-3DLabs-3.3.3.1-52.i386.rpm XFree86-8514-3.3.3.1-52.i386.rpm XFree86-AGX-3.3.3.1-52.i386.rpm XFree86-FBDev-3.3.3.1-52.i386.rpm XFree86-I128-3.3.3.1-52.i386.rpm XFree86-Mach32-3.3.3.1-52.i386.rpm XFree86-Mach64-3.3.3.1-52.i386.rpm XFree86-Mach8-3.3.3.1-52.i386.rpm XFree86-Mono-3.3.3.1-52.i386.rpm XFree86-P9...

...3537 3. Relevant releases/architectures: Red Hat Linux 6.0, all architectures 4. Obsoleted by: 5. Conflicts with: 6. RPMs required: Intel: ftp://updates.redhat.com/6.0/i386/ XFree86-3.3.3.1-52.i386.rpm XFree86-100dpi-fonts-3.3.3.1-52.i386.rpm XFree86-75dpi-fonts-3.3.3.1-52.i386.rpm XFree86-3DLabs-3.3.3.1-52.i386.rpm XFree86-8514-3.3.3.1-52.i386.rpm XFree86-AGX-3.3.3.1-52.i386.rpm XFree86-FBDev-3.3.3.1-52.i386.rpm XFree86-I128-3.3.3.1-52.i386.rpm XFree86-Mach32-3.3.3.1-52.i386.rpm XFree86-Mach64-3.3.3.1-52.i386.rpm XFree86-Mach8-3.3.3.1-52.i386.rpm XFree86-Mono-3.3.3.1-52.i386.rpm XFree86-P9...

...the first addition However, this means the backend has to remember the register %a now stores low bytes of the result, and the register %c stores the high bytes of the result. This tracking is not an easy job, I think. > I assume you'll be starting with the reference GLSL parser (from > 3DLabs, IIRC - I don't even know if they stil exist, actually) You can find the 3Dlabs frontend here: http://l4.me.uk/static/glsl/ And I don't think anyone has ported this frontend onto LLVM before. > The issue would be that LLVM would want to store register values as 32 > bits - and do a...

...bytes of the result, and the register %c stores the high > bytes of the result. This tracking is not an easy job, I think. Unextended GLSL doesn't require support for integers larger than 16 bits. > >> I assume you'll be starting with the reference GLSL parser (from >> 3DLabs, IIRC - I don't even know if they stil exist, actually) > > You can find the 3Dlabs frontend here: > http://l4.me.uk/static/glsl/ > > And I don't think anyone has ported this frontend onto LLVM before. > >> The issue would be that LLVM would want to store register va...

...rk with i32 internally, and convert literals during code gen. Since GLSL doesn't require load/store, and it sounds like your HW may not 100% reliable for these ops, you want to make sure your code stays in registers. I assume you'll be starting with the reference GLSL parser (from 3DLabs, IIRC - I don't even know if they stil exist, actually) and having it generate LLVM IR (has anybody done this before?). This will give you much more control over the code - Clang is the front end for the project I'm working on, and it generates stack based code; most of the stack op...

...9;Hood, public shares are accessable, but shares that require authentication are not. Any ideas? I'm hoping it's something obvious (can't see the forest for the trees). The same results occur with versions 1.9.18p4 and 2.0.5a. These are Sun/Solaris 2.5.1 machines. Thanks, Larry Goodman 3Dlabs, Inc. Mail Stop CR1100, Huntsville, AL 35894 (256)730-6529 Fax: (256)730-6152 Larry.Goodman@intense3d.com

...d. If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please delete it and contact the sender immediately. Thank you. 3DLabs Ltd company number 02883883 registered in England and Wales at 79 Knightsbridge, London SW1X 7RB

I have 24-bit integer operations as well as 24-bit floating point (s7.16) operations. The H/W supports load/store instructions, however, they does suggest us not to use these load/store instructions besides debugging purpose. That is to say, you can imagine we don't have load/store instructions, we don't have memory, we just have registers. I will run OpenGL shading laugnage programs on

Hello All, I am trying to get basic CFG display to work. I have read the programmer's manual and it mentions that we can simply call the viewCFGOnly() (part of Function.h) from our sample program. When i read the comments for that method in Function.h, it mentions that i need to call it from the gdb debugger instead. I am confused as to how to get this working. Do we need to call it from a

.... If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please delete it and contact the sender immediately. Thank you. 3DLabs Ltd company number 02883883 registered in England and Wales at 79 Knightsbridge, London SW1X 7RB

Hello David, Thanks for the reply. Would i not need to pass any arguments for viewCFGOnly() method? According to this http://llvm.org/doxygen/Function_8h-source.html seems like we need to? I am building it on top of the example shown at http://llvm.org/docs/WritingAnLLVMPass.html and just added 'F->viewCFGOnly(); line to it. It doesn't compile, i suspect it has to do with the way i

https://bugs.freedesktop.org/show_bug.cgi?id=56340 Priority: medium Bug ID: 56340 Assignee: nouveau at lists.freedesktop.org Summary: [Ubuntu 10.04.4 LTS 32-bit] Severe instability of VIA Technologies Apollo MVP3 chipset and NVIDIA RIVA TNT2 M64 graphics QA Contact: xorg-team at lists.x.org