On Thursday, October 25, 2007 9:59 pm Greg KH wrote: > On Thu, Oct 25, 2007 at 04:53:18PM -0700, Jesse Barnes wrote: > > Ok, here's yet another version that uses the device model for the > > suspend/resume, rather than pci hooks. > > > > Greg, DRM desperately needs review of its device model usage, can > > you take a look at this patch and the current drm_sysfs.c code? > > Right now, we're mixing class_devices and regular devices (the > > latter seem to be required for suspend/resume to work correctly), > > but this seems wrong. Any ideas? Should we just rip out the > > class_device stuff and create full-on DRM device nodes? > > The class_device stuff is already ripped out in the latest -mm trees > and I will be forwarding that change on for 2.6.25 after 2.6.24 is > out. So yes, it should be taken away :) > > But converting from class_device to struct device does not mean you > use a "device node". But you could if you want to :)
Yeah, bad choice of words. :) To retain compatibility, we need to have directories under the DRM class dir (/sys/class/drm) for each card (e.g. card0) that contains a file describing which graphics driver is bound to the device. For class devices, we could just add an attributes structure to the device. Can we do the same with regular, non-class devices? Thanks, Jesse ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
