From: Larry Finger <larry.finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
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 10:17:25 -0600 [thread overview]
Message-ID: <45CF4195.10709@lwfinger.net> (raw)
In-Reply-To: <200702111703.13702.mb@bu3sch.de>
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
next prev parent reply other threads:[~2007-02-11 16:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 16:18 [PATCH] bcm43xx: Fix loss of association after resume Larry Finger
2007-02-09 16:53 ` Michael Buesch
2007-02-10 17:11 ` Rafael J. Wysocki
2007-02-10 20:33 ` Larry Finger
2007-02-11 12:56 ` Rafael J. Wysocki
2007-02-11 13:07 ` Michael Buesch
2007-02-11 14:02 ` Rafael J. Wysocki
2007-02-11 14:14 ` Michael Buesch
2007-02-11 14:41 ` Johannes Berg
2007-02-11 14:45 ` Rafael J. Wysocki
2007-02-11 14:48 ` Johannes Berg
2007-02-11 15:59 ` Larry Finger
2007-02-11 16:03 ` Michael Buesch
2007-02-11 16:16 ` Michael Buesch
2007-02-11 16:17 ` Larry Finger [this message]
2007-02-12 0:50 ` Rafael J. Wysocki
2007-02-12 1:18 ` Larry Finger
2007-02-12 20:48 ` Rafael J. Wysocki
2007-02-12 22:20 ` Larry Finger
2007-02-12 23:08 ` Rafael J. Wysocki
2007-02-12 23:18 ` Larry Finger
2007-02-12 23:24 ` Michael Buesch
2007-02-13 16:25 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45CF4195.10709@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).