> I'm sending an updated patch series adding a set_config method to > drm_encoder_slave_funcs to allow dynamically changing the encoder > specific DVO port parameters (the previous API enforced them to remain > the same until the end of its life).
so I'm not a 100% sure what to do with these yet. > > [PATCHv2 1/6] drm: Slave encoder interface. > [PATCHv2 2/6] drm: Define DRM_MODE_CONNECTOR_TV > [PATCHv2 3/6] drm: Define DRM_MODE_SUBCONNECTOR_SCART > [PATCHv2 4/6] drm: Define some new standard TV properties. I've pushed the above 4 to drm-next, > [PATCHv2 5/6] drm: Import driver for the ch7006 I2C TV encoder chip. > [PATCHv2 6/6] drm/nouveau: Import <nv17 TV-out support. > I'm not sure whether we want to push these via nouveau, or maybe I should queue the i2c chip bits up, any preferences or suggestions? Dave. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
