On Sunday 11 February 2007 17:03, 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. I've been told this is wrong. Well, ok. Anyway. I don't think we need to re-request the fw, as it's restored, too. Can you try bcm43xx-d80211 from my tree? There it reinitializes the device completely on resume. So it might work there. -- Greetings Michael. - 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
