> I'm not passing device information, but devices *do* have internal > state. I quiesce them before booting new kernel, but there's probably > more than one way to quiesce devices... Not that many. You don't quite know in what state they are when the BIOS calls you neither in most cases :) Nor when waking up from BIOS-managed state.... It's usually safe if they just don't bust master and are idle. > No, I really do not want to make things more complicated in 2.6. And > you should not want to complicate it, too. I will not impose that limitation on a ppc implementation. I don't even want to load the resume image from the boot kernel, it's much more easier to load it from the bootloader for me anyway. And the copy routine is just a tricky bit of asm, not even _that_ tricky I'd say (well, I don't do x86 asm, but I've certainly had to deal with more tricky stuffs on ppc so far). Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: Help port swsusp to ppc.Pavel Machek
- Help port swsusp to ppc.Hugang
- Re: Help port swsusp to ppc.Benjamin Herrenschmidt
- Re: Help port swsusp to ppc.Nigel Cunningham
- Re: Help port swsusp to ppc.Benjamin Herrenschmidt
- Re: Help port swsusp to ppc.Pavel Machek
- Re: Help port swsusp to ppc.Benjamin Herrenschmidt
- Re: Help port swsusp to ppc.Pavel Machek
- Re: Help port swsusp to ppc.Benjamin Herrenschmidt
- Re: Help port swsusp to ppc.Pavel Machek
- Prev by Date: Re: AIC7xxx kernel problem with 2.4.2[234] kernels
- Next by Date: Re: Help port swsusp to ppc.
- Previous by thread: Re: Help port swsusp to ppc.
- Next by thread: Re: Help port swsusp to ppc.
- Indexes:[Main][Thread]