On Tue, 2007-05-22 at 16:36 -0700, Jesse Barnes wrote: > On Tuesday, May 22, 2007, Benjamin Herrenschmidt wrote: > > On Tue, 2007-05-22 at 08:39 -0700, Jesse Barnes wrote: > > > The current code does its best to figure out what modes are available > > > and tries to pick a good one for each display. It sounds like you're > > > mainly concerned with the actual mode picking, not the mode and output > > > detection and enumeration? If so, that's a pretty easy change to > > > make. But if you're also worried about the kernel building mode > > > lists, then we'll have bigger changes to make... > > > > I'm worried that the EDID we get from the monitor is bogus and needs to > > be overriden. > > > > Now, if the kernel builds a mode list, that's find if we have a call to > > "feed" it with a replacement one later on from userland. > > > > In addition, there are all those monitors that cannot be probed (no > > DDC/EDID) and for which only userland can reasonably provide a mode or a > > mode list. > > Yeah, we already have a call to add modes to the kernel's list, so we > should be covered. >
We actually have a function that will replace the entire mode list with a new one safely. Tony ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
