public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: System freezes with 2.6.33
Date: Tue, 20 Apr 2010 12:07:40 -0500	[thread overview]
Message-ID: <4BCDDF5C.2040901@lwfinger.net> (raw)
In-Reply-To: <20100420162751.25907.qmail@stuge.se>

On 04/20/2010 11:27 AM, Peter Stuge wrote:
> Daniel Kuehn wrote:
>>>> I have also tried disabling the radio using the switch, and then
>>>> there is no freeze. When I enable the radio back, it freezes again.
>>>
>>> Could b43 experts please outline what happens w.r.t. the PCIe bus
>>> when radio is disabled using the switch as described above?
>>
>> Doesnt the switch "just" turn it off hardware wise?

No, the hardware is still powered. I think the signal from the switch
disables the radio, but I'm not sure of that.

> I doubt that. PCIe can do hotplug but it's only used in high-end
> systems, not a mini-note.
> 
> 
>> As in that the OS doesnt even know it exists then because more or
>> less the power is cut to it.
> 
> Usually the switch generates an electrical signal which goes through
> the system board over to the wifi card, and there it will have
> control over the RF part, and yes disable radio communication, but
> no, not the entire wifi card. As I have understood the b43 hardware
> can also read this electrical signal and report it's status to the
> driver, but it is impossible to override the hardwired "kill" switch
> from the driver.
> 
> This is why I ask for advice from the b43 experts, since maybe my
> description above is too simplistic, and the kill signal will
> actually cause more things to happen on the wifi card.
> 
> Anything related to the host bus is of particular interest.

See below.

> What happens in the firmware w.r.t. the kill switch?

I do not think the firmware knows anything about it other than possible
interaction with the driver through the contents of shared memory.

> What does openfwwf do?

Do you mean with respect to the freeze? The openfwwf is only for
Revision 5 802.11 cores - this one is Rev 13.

There are a number of code paths that are not used when the radio switch
is off. For instance, the device will not do DMA, which might be a clue.

Yuval: If you are willing to generate your own kernel, please set
'CONFIG_B43_FORCE_PIO=y' in your configuration. That will skip DMA
completely.

Larry

  reply	other threads:[~2010-04-20 17:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-18  7:19 System freezes with 2.6.33 yhager at yhager.com
2010-04-18 16:16 ` Larry Finger
2010-04-20 14:34   ` yhager at yhager.com
2010-04-20 15:51     ` Peter Stuge
2010-04-20 16:07       ` Daniel Kuehn
2010-04-20 16:27         ` Peter Stuge
2010-04-20 17:07           ` Larry Finger [this message]
2010-04-22 16:12             ` yhager at yhager.com
2010-04-22 17:21               ` Larry Finger
2010-04-22 18:59                 ` yhager at yhager.com
2010-05-01 23:28                 ` Yuval Hager
2010-04-19 16:54 ` Peter Stuge

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=4BCDDF5C.2040901@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.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