Hi!
> thanks for explaining this, i am obviously not too deep into that
> PCI bus stuff :-)
>
...
> > > I thought that this should somehow go away by the PCI bus suspend/resume
> > > methods that somewhen back got merged by Greg K-H.
> >
> > The kernel will only save and restore the standardised PCI configuration
> > registers - anything else needs to be handled by the specific device
> > driver. Unfortunately, in the graphics hardware case, the closest thing
> > to that is the framebuffer driver. Which we don't tend to use.
>
> So the question is: should we either
> - implement a minimal "graphics card PCI suspend resume" "driver" in the
> kernel that will do this even if no framebuffer is used, or
We are going there, but it is *hard* to do, due to kernel graphics
missdesign. Could take years.
> - implement this as a workaround in userspace?
>
> I mean - it is not rocket science to do it in s2ram, but it just seems
> more correct (to me) to do it in the kernel, where the correct locking
> and ordering is more or less guaranteed.
Lets do it in userspace. Doing in kernel is right, but it will be
hard.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
