Hi Ben > Ok, the patch is now getting "good enough" for wider testing. It applies > on current "git" tree (or 2.6.12-rc6 when/if that is ever released).
I have just tested your patch with the 2.5.12-rc5-git5 on the new powerbook 12". And yes, the suspend to disk works very well, even if X is running (I report my problem with X and the suspend to disk with a 2.6.12-rc4 in another discussion). It is really good. Thanks for your good job Ben. Mickael On 5/30/05, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote: > Ok, the patch is now getting "good enough" for wider testing. It applies > on current "git" tree (or 2.6.12-rc6 when/if that is ever released). It > requires one other patch to be applied first: > > http://gate.crashing.org/~benh/ppc32-remove-macserial.diff > > The PM patch itself can be found at: > > http://gate.crashing.org/~benh/ppc32-rework-pm.diff > > This patch completely reworks both suspend-to-ram and suspend-to-disk > support on PowerMac: > > - suspend-to-ram code is moved away from the via-pmu.c driver > - both suspend-to-disk & to-ram consolidated to use the same > infrastructure and code base in a new pmac_pm.c file > - significants fixes & improvements to suspend-to-disk > - for now (may change), use the "refrigerator" with suspend-to-ram as > well as suspend-to-disk. This may help make it a bit more robust vs. > userland activity during the sleep process > - CONFIG_PMAC_PBOOK is gone. CONFIG_PMAC_MEDIABAY is new and controls > wether the powerbook hostwap bay driver is included. The rest of bits > formerly under CONFIG_PMAC_PBOOK control are now either always on > (like /dev/pmu interface on PMU based machines) or dependent on other > config options (like CONFIG_PM, CONFIG_PPC_PMAC, ...) > > The patch will not be in 2.6.12 (though will probably apply on top of > it). I aim for a 2.6.13 release, knowing that the patch changes a bunch > of non-ppc-specific power management bits, and thus may need some time > to be fully merged upstream. > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > >