From: Jon Masters <jcm@redhat.com>
To: Arend Van Spriel <arend@broadcom.com>
Cc: devel <devel@linuxdriverproject.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: PROBLEM: brcm80211 unable to survive suspend/resume cycle
Date: Mon, 14 Mar 2011 03:09:18 -0400 [thread overview]
Message-ID: <1300086558.22748.38.camel@constitution.bos.jonmasters.org> (raw)
In-Reply-To: <1295459500.9781.127.camel@constitution.bos.jonmasters.org>
On Wed, 2011-01-19 at 12:51 -0500, Jon Masters wrote:
> On Wed, 2011-01-19 at 09:43 -0800, Arend Van Spriel wrote:
>
> > I tried to give you a heads up. I submitted the patch last friday to the
> > staging-2.6 repository. Not sure whether it has propagated to the 2.6.3[78]
> > kernels yet.
>
> Awesome. Sometime soon, I guess it will land and I'll test it for you :)
Latest upstream staging is working across suspend quite nicely. I did,
however, separately ping David Woodhouse to let him know that there is
some discrepancy between the firmware names you are looking for in the
brcm80211 driver and the firmware names in the linux-firmware rawhide
(Fedora) package such that one has to manually symlink stuff - can you
confirm that the current naming you're looking for is going to remain
consistent in the future if symlinks are fixed in linux-firmware?
Jon.
next prev parent reply other threads:[~2011-03-14 7:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 3:13 PROBLEM: brcm80211 unable to survive suspend/resume cycle Jon Masters
2010-11-09 3:16 ` Jon Masters
2010-11-09 3:24 ` Greg KH
2010-11-09 7:58 ` Jon Masters
2010-11-09 18:02 ` Brett Rudley
2010-11-09 23:11 ` Jon Masters
2010-11-16 4:04 ` Jon Masters
2010-12-08 7:03 ` Jon Masters
2010-12-08 7:10 ` Jon Masters
2010-12-22 14:31 ` Jon Masters
2011-01-12 9:26 ` Arend Van Spriel
2011-01-19 17:16 ` Jon Masters
2011-01-19 17:43 ` Arend Van Spriel
2011-01-19 17:51 ` Jon Masters
2011-03-14 7:09 ` Jon Masters [this message]
2011-01-19 21:19 ` Greg KH
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=1300086558.22748.38.camel@constitution.bos.jonmasters.org \
--to=jcm@redhat.com \
--cc=arend@broadcom.com \
--cc=devel@linuxdriverproject.org \
--cc=linux-kernel@vger.kernel.org \
/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).