Michael Buesch wrote: > On Sunday 11 February 2007 16:59, Larry Finger wrote: >> Michael Buesch wrote: >>> On Sunday 11 February 2007 15:02, Rafael J. Wysocki wrote: >>>> PM: Removing info for No Bus:0000:30:00.0 >>>> bcm43xx: IRQ_READY timeout >>>> bcm43xx: core_up for active 802.11 core failed (-19) >>> I never tried suspend to disk with the driver. >> This implies that suspend to RAM works. Is that true? > > No. > >>> Larry, an idea why the microcode doesn't respond? >> Is this code snippet supposed to keep the firmware loaded when the system is suspended? > > Well, eh, no. Don't confuse suspend-to-ram with suspend-to-disk. > On suspend-to-disk the kernel is (mostly) reloaded as usual. > Just userspace is restored. > So the driver enters through the probe routine on resume from disk. > Does it then call the resume entry? Rafael's dmesg output has the line "bcm43xx: Resuming..." that only gets printed if the resume routine was called. Larry - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
