public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Milan Bouchet-Valat <nalimilan@club.fr>
To: Arend van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BCM4313 doesn't work after suspend (brcmsmac on compat-wireless-next)
Date: Fri, 20 Jan 2012 18:22:57 +0100	[thread overview]
Message-ID: <1327080177.3285.26.camel@milan> (raw)
In-Reply-To: <4F199EAC.3050602@broadcom.com>

Hi and thanks for the reply!

Le vendredi 20 janvier 2012 à 18:04 +0100, Arend van Spriel a écrit :
> I am not sure when compat-wireless-next was generated, but several
> patches were made for suspend/resume.
It was generated on January 17th, with sources from the 16th. Is that
recent enough?

(Packages are from
http://people.redhat.com/sgruszka/compat-wireless-next/F-16/)

> You also need bcma patches. Is
> bcma included in the compat-wireless package.
I'm not sure I understand. The bcma module is indeed installed from
compat-wireless-next and loaded:
$ lsmod|grep bcma
bcma                   23804  2 brcmsmac,b43

$ uname -r
3.1.9-1.fc16.x86_64

$ find /lib/modules/3.1.9-1.fc16.x86_64 -name bcma
/lib/modules/3.1.9-1.fc16.x86_64/updates/drivers/bcma
/lib/modules/3.1.9-1.fc16.x86_64/backports/drivers/bcma

(updates/ is from compat-wireless-next, and takes precedence over
backports/ as per /etc/depmod.d/dist.conf)

So should I apply more patches?


Regards


  reply	other threads:[~2012-01-20 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 13:54 BCM4313 doesn't work after suspend (brcmsmac on compat-wireless-next) Milan Bouchet-Valat
2012-01-20 17:04 ` Arend van Spriel
2012-01-20 17:22   ` Milan Bouchet-Valat [this message]
2012-01-21  9:58     ` Arend van Spriel
2012-01-24 10:25       ` Milan Bouchet-Valat

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=1327080177.3285.26.camel@milan \
    --to=nalimilan@club.fr \
    --cc=arend@broadcom.com \
    --cc=linux-wireless@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