Devices don't get linked to their class.
flat view
From: Nigel Cunningham <hidden>
Date: 2004-09-03 05:05:27
Hi all. Some of my suspend2 users have reported that their displays go blank as soon as suspend starts writing to disk. I understand why. I suspend everything else except the storage device and it's parents at the start of writing the image. Interestingly, though, the issue doesn't occur with all display drivers, perhaps (I guess) because they haven't had PM support written yet. Having switched from the vesafb driver to the radeon one, I'm now able to reproduce the behaviour described above. This morning I began work on addressing the problem. I thought the best approach would be to use device classes to find the struct dev for the frame buffer driver, and then use the same code I use for storage devices to avoid suspending the frame buffer until later. I successfully wrote a helper to find the 'graphics' class that fbmem.c creates, but now I've run into a more serious issue. register_framebuffer (in the same time) calls class_simple_device_add with a NULL for the pointer to the struct device. Is it possible for this issue to be addressed? I can see that (at least in the Radeon case) one could simply call register_framebuffer with an additional parameter, but thought I'd email you and seek your wisdom. By the way, am I missing something? It looks like framebuffer_alloc does nothing with the dev parameter passed to it. Regards, Nigel -- Nigel Cunningham Pastoral Worker Christian Reformed Church of Tuggeranong PO Box 1004, Tuggeranong, ACT 2901 Many today claim to be tolerant. True tolerance, however, can cope with others being intolerant. ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click