On Mon, Jan 5, 2009 at 7:55 AM, Kristian Høgsberg k...@bitplanet.net wrote:
Under kernel modesetting, we manage the device at all times, regardless
of VT switching and X servers, so the only decent thing to do is to
claim the PCI device. In that case, we call the suspend/resume hooks
directly
Heya, ping again. We're a real driver now, can we please claim the
PCI device. Can one of you please add it to your git tree, either
current rc or next merge window so we don't drop this on the floor?
thanks,
Kristian
On Tue, Jan 13, 2009 at 9:42 AM, Kristian Høgsberg k...@bitplanet.net wrote:
Under kernel modesetting, we manage the device at all times, regardless
of VT switching and X servers, so the only decent thing to do is to
claim the PCI device. In that case, we call the suspend/resume hooks
directly from the pci driver hooks instead of the current class device detour.
Under kernel modesetting, we manage the device at all times, regardless
of VT switching and X servers, so the only decent thing to do is to
claim the PCI device. In that case, we call the suspend/resume hooks
directly from the pci driver hooks instead of the current class device detour.
