All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: John Linville <linville@tuxdriver.com>,
	Michael Buesch <mb@bu3sch.de>,
	linux-wireless@vger.kernel.org, Bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH] b43: Changes to enable BCM4311 rev 02 with wireless core revision 13
Date: Wed, 21 Nov 2007 15:49:23 -0600	[thread overview]
Message-ID: <4744A7E3.6090105@lwfinger.net> (raw)
In-Reply-To: <4744A443.6070808@redhat.com>

Chuck Ebbert wrote:
> On 11/21/2007 02:31 PM, Larry Finger wrote:
>> The BCM94311MCG rev 02 chip has an 802.11 core with revision 13 and
>> has not been supported until now. The changes include the following:
>>
> 
> I put this in a private build of the Fedora 8 kernel in place of the
> the one that was added a few days ago.
> 
> This one works, but I get "PHY transmission error", probably because
> the rfkill switch has disabled it. I see two LED devices and an input
> device were registered but pushing the rfkill switch has no effect.
> Googling doesn't yield any directions for enabling the switch...

I don't think the PHY transmission error is caused by the rfkill switch, but I have no idea where it 
arises. It has been present since I enabled the device with 64-bit DMA.

I have not determined how to get rfkill to react to the LED switch, but now that the BCM4311 rev 02 
card is working, I should have some time to look at it.

Larry

      reply	other threads:[~2007-11-21 21:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 19:31 [PATCH] b43: Changes to enable BCM4311 rev 02 with wireless core revision 13 Larry Finger
2007-11-21 19:44 ` Michael Buesch
2007-11-21 20:02   ` Larry Finger
2007-11-21 20:10     ` Michael Buesch
2007-11-21 21:33 ` Chuck Ebbert
2007-11-21 21:49   ` Larry Finger [this message]

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=4744A7E3.6090105@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=cebbert@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    /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.