Re: [PATCH] bcm43xx: Fix loss of association after resume

From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <larry.finger@lwfinger.net>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	bcm43xx-dev@lists.berlios.de,
	wireless <linux-wireless@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] bcm43xx: Fix loss of association after resume
Date: Sun, 11 Feb 2007 17:16:51 +0100	[thread overview]
Message-ID: <200702111716.51539.mb@bu3sch.de> (raw)
In-Reply-To: <200702111703.13702.mb@bu3sch.de>

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.