On Tue, Mar 09, 2010 at 10:08:28PM +0100, Rafael J. Wysocki wrote: > On Tuesday 09 March 2010, James Simmons wrote: > > > > > > > Second, in the KMS case, we'd be able to skip the kernel VT switch, > > > > > because > > > > > the KMS driver uses its own framebuffer anyway. > > > > > > > > > > So, is there any reasonable way to check that from the outside of the > > > > > graphics > > > > > driver? It should be general enough to cover the cases when there > > > > > are two > > > > > graphics adapters with different drivers in the system and so forth. > > > > > > > > Inside the kernel? If you have a struct pci_dev you can get the > > > > associated struct drm_device with pci_get_drvdata and then check the > > > > KMS feature: drm_core_check_feature(dev, DRIVER_MODESET). > > > > > > Yeah, I know that. > > > > > > > I'm note sure how to check that a device is graphic card though :| > > > > > > Well, that's the "outside of the graphics driver" part of my question. :-) > > > > if ((pdev->class >> 8) == PCI_CLASS_DISPLAY_VGA) > > .... > > I'm not sure if searching through all PCI devices really is an option. > Why not? The VGA arbitration code tracks a list of VGA class devices, so could easily be queried. It looks like it might need a bit more work for PCI hotplug, but it should already have all of the infrastructure you need for getting at the pdev for the suspend/resume case.
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
