From: Ben S. <sk...@gm...> - 2009-05-06 02:48:48
|
On Wed, 2009-05-06 at 03:12 +0100, Dave Airlie wrote: > > > > > > This just tries EDID detection, then falls back to the slow path code. > > > I think this is should detect most monitors currently available. > > > > I need to rework the I2C stuff so that it doesn't require the bit-bang > > i2c algo; Display Port needs a custom i2c algo. As such, it seems like > > the slow i2c stuff should be pushed into it's own algo and used by > > whichever modules need it (does anything other than VGA actually need > > this?) > > Well if you just call the get_edid and ignore all the setscl crap that > this code does, then you should be able to just implement a new i2c algo, > and have it all just work. It's definitely possible, the nv50 kms driver used to implement its own i2c algo until recently. Ben. > > I've no idea what monitors this picks up on, radeon used to do it, and the > kernel fb layer does it but I think got it from radeon originally. > > I suspect dropping it might not be a bad idea. > > Dave. > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > -- > _______________________________________________ > Dri-devel mailing list > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-devel |