On 7/23/07, Pavel Machek <[EMAIL PROTECTED]> wrote: > > They can... > > There is no difference between doing: > > vbe -> s2disk -> s2ram -> vbe > > s2disk -> vbe -> s2ram -> vbe > > No. vbe data need to go unswappable memory, so we can display messages > in case of something breaks etc... and passing vbe data from script to > s2ram would be ugly.
Please remember that these hacks are required only after s2ram wakeup, you don't need them after s2disk wakeup. So there is no progress. As hacks->s2disk snapshot->s2ram sleep->s2ram wakeup->hacks > > The same for radeon. > > It is useful to keep radeon up as long as possible so that user sees > progress and can help with debugging. No messages during s2ram wakeup... Alon. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
