Re: DRI integration
Jon Smirl <jonsmirl-/[email protected]>
| Newsgroups | gmane.comp.freedesktop.xserver |
|---|---|
| Message-ID | <[email protected]> |
There is code for EDID1, EDID2, DDC, and mode lines from a file. Code for accessing the I2C bus. There is support for two different kinds on internal laptop displays (DFP and something else). There is code for detecting what is connected to each of the three video output ports. Code for dealing with wiring mistakes in various OEM cards. Code for save/restore of a lot of registers on VT switch. Code for enabling/disabling/save/restore of the VGA interface. Code for dealing with about 20 different versions of Radeon chips. Code for dealing with register save/restore during DPMS (power management) events. You have to set up the PLL with values out of the ROM. I probably missed a few things too --- Jim Gettys <[email protected]> wrote: > On Wed, 2003-11-12 at 20:42, Jon Smirl wrote: > > > > - Video card initialization, mode switching, etc. > > I am working on that right now for Radeon. This involves over 10,000 lines > of > > code so I am doing a lot of it in a user level library. I think it is risky > to > > put 100KB of relatively infrequently used code into a device driver. > > > > Can someone educate this naive person how it could possibly take > this much code to get the chip set up? I could believe a lot > of tables, but code???? > Thanks, > - Jim > > -- > Jim Gettys <[email protected]> > HP Labs, Cambridge Research Laboratory > ===== Jon Smirl jonsmirl-/[email protected] __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree