Prev: [PATCH 3 of 5] Linux pvops: evtchn delivery for legacy interrupts
Next: [PATCH] NOMMU: allow private mappings of read-only devices
From: James Simmons on 9 Mar 2010 11:20

> > > 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(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 3 of 5] Linux pvops: evtchn delivery for legacy interrupts
Next: [PATCH] NOMMU: allow private mappings of read-only devices