matrox, ati, nvidia hardware acceleration ...
-
- Member
- Posts: 1600
- Joined: Wed Oct 18, 2006 11:59 am
- Location: Vienna/Austria
- Contact:
matrox, ati, nvidia hardware acceleration ...
... the osdever formerly known as beyond infinity ...
BlueillusionOS iso image
BlueillusionOS iso image
- Pype.Clicker
- Member
- Posts: 5964
- Joined: Wed Oct 18, 2006 2:31 am
- Location: In a galaxy, far, far away
- Contact:
Re:matrox, ati, nvidia hardware acceleration ...
yup. good work. i'll check it again, but iirc, it gives accelerants for 2D features (bitblt, fills, etc), no 3D stuff ...
That's still very valuable source of information and certainly more readable than X sources ...
That's still very valuable source of information and certainly more readable than X sources ...
- Pype.Clicker
- Member
- Posts: 5964
- Joined: Wed Oct 18, 2006 2:31 am
- Location: In a galaxy, far, far away
- Contact:
Re:matrox, ati, nvidia hardware acceleration ...
started http://www.osdev.org/osfaq2/index.php/A ... aphicCards from what i already know ... contributions are welcome ...
Re:matrox, ati, nvidia hardware acceleration ...
For 3D Acceleration, there are docs available for the Voodoo cards, http://www.osdever.net/cottontail/#Video
The docs archived here for Voodoo2 seem to say how all the card registers are mapped in memory but it is missing the crucial "triangle command" section.
The docs archived here for Voodoo2 seem to say how all the card registers are mapped in memory but it is missing the crucial "triangle command" section.
- Pype.Clicker
- Member
- Posts: 5964
- Joined: Wed Oct 18, 2006 2:31 am
- Location: In a galaxy, far, far away
- Contact:
Re:matrox, ati, nvidia hardware acceleration ...
yes, the once-famous "GLide" interface of 3Dfx early chips was one of the rare one to have documentation. Unfortunately, there's not much glide-based cards sold nowadays ...
Actually, i was thinking of using something similar to SANiK's vm86 translator to translate linux NV driver ... Parse code, identify things that are linux-specific and replace them by $(YourOS)-specific...
The i470 of Intel (some embedded 3D chip) also has very open description and the doc is cached at the same website as above.
Actually, i was thinking of using something similar to SANiK's vm86 translator to translate linux NV driver ... Parse code, identify things that are linux-specific and replace them by $(YourOS)-specific...
The i470 of Intel (some embedded 3D chip) also has very open description and the doc is cached at the same website as above.