Information for W32 and ET6000 Chipset Users : Using XF86_W32 on an ET6000-based board
Previous: Using XF86_W32 on a board with an STG1703 GENDAC
Next: Using `XF86_SVGA` with ET4000/W32 and ET6000 cards

## 4. Using XF86_W32 on an ET6000-based board

The ET6000 driver code was developed on top of the existing ET4000/W32 code, because of the many similarities between both devices. As with the other W32 (external) clockchip/RAMDAC devices, the ET6000's built-in clockchip/RAMDAC provides a set of 8 standard clocks, which could be probed with the normal XFree clock probing procedure. In spite of that, XF86_W32 will always use the built-in programmable clockchip and RAMDAC. So there is no need for a

> `

>      ClockChip "et6000"

> `

or a

> `

>      Ramdac "et6000"

> `

line in the Device Section of the XF86Config file. Once it knows it's dealing with an ET6000, XF86_W32 will find its own way. At this moment, accelerated support is very sketchy, and only uses those things the ET4000/W32 code already provided, with some changes due to incompatibilities between the two devices. Major speed improvements should be possible. Tseng Labs specifies a maximum pixel clock of 135 MHz for the ET6000 chips (with higher clocks to come).

There is a known bug in this server when using it with ET6000 cards with 2.25 MB MDRAM: the server will detect 2.5 MB instead, and as a result, most accelerated operations won't work. On cards with 2.25 MB MDRAM, you must insert a

> `

>      VideoRam 2304

> `

line in your XF86Config.

Information for W32 and ET6000 Chipset Users : Using XF86_W32 on an ET6000-based board
Previous: Using XF86_W32 on a board with an STG1703 GENDAC
Next: Using `XF86_SVGA` with ET4000/W32 and ET6000 cards