All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Larry Finger <larry.finger@lwfinger.net>,
	wireless <linux-wireless@vger.kernel.org>,
	bcm43xx-dev@lists.berlios.de,
	John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] bcm43xx: Fix loss of association after resume
Date: Tue, 13 Feb 2007 00:24:20 +0100	[thread overview]
Message-ID: <200702130024.20876.mb@bu3sch.de> (raw)
In-Reply-To: <200702130008.47684.rjw@sisk.pl>

On Tuesday 13 February 2007 00:08, Rafael J. Wysocki wrote:
> On Monday, 12 February 2007 23:20, Larry Finger wrote:
> > Rafael J. Wysocki wrote:
> > > On Monday, 12 February 2007 02:18, Larry Finger wrote:
> > >> Rafael J. Wysocki wrote:
> > >>> It doesn't help in my case.  The behavior is similar to that without the patch,
> > >>> but also with the patch it loses the association entirely.
> > >> Thanks for trying.
> > >>
> > >> Do you have this patch installed? If you do, please try increasing the 100 to 200.
> > > 
> > > Hm, but it wouldn't help to get the microcode to respond after the resume ...
> > 
> > Yes it would. That count is how long the system waits for the firmware to respond.
> > 
> > > I'm still thinking the problem is with the firmware.  Where exactly is it
> > > stored?
> > 
> > In the memory of the microprocessor on the card.
> > 
> > Please do what I asked.
> 
> With or without the previous patch?

Both, please.

-- 
Greetings Michael.

  parent reply	other threads:[~2007-02-12 23:24 UTC|newest]

Thread overview: 26+ 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:18 ` Larry Finger
2007-02-09 16:53 ` Michael Buesch
2007-02-09 16:53   ` Michael Buesch
2007-02-10 17:11   ` Rafael J. Wysocki
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
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 [this message]
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=200702130024.20876.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.