[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1003091613390.30952@casper.infradead.org>
Date: Tue, 9 Mar 2010 16:16:24 +0000 (GMT)
From: James Simmons <jsimmons@...radead.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Luca Tettamanti <kronos.it@...il.com>,
Matthew Garrett <mjg59@...f.ucam.org>,
Linux PCI <linux-pci@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
pm list <linux-pm@...ts.linux-foundation.org>,
dri-devel@...ts.sourceforge.net
Subject: Re: [Q] How to tell we're using the KMS (during suspend/resume)
outside the graphics driver
> > > 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)
....
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists