All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Niklas Wulf <niklas@wulf-home.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFT] b43: Rewrite PHY API for N-PHY/LP-PHY  -- good on 4311
Date: Tue, 19 Aug 2008 17:18:20 -0500	[thread overview]
Message-ID: <48AB46AC.3090703@lwfinger.net> (raw)
In-Reply-To: <48AB5D89.5090705@wulf-home.de>

Niklas Wulf wrote:
> I tested this one on my Macbook Pro (3,1).
> 
> # lspci -v
> 0b:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n
> (rev 05)
> Subsystem: Apple Computer Inc. Device 008c
> Flags: bus master, fast devsel, latency 0, IRQ 16
> Memory at 97300000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [40] Power Management version 3
> Capabilities: [58] Vendor Specific Information <?>
> Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
> Enable-
> Capabilities: [d0] Express Endpoint, MSI 00
> Kernel driver in use: b43-pci-bridge
> Kernel modules: ssb
> 
> It is not recognized by the driver... should it? I don't get a wireless
> device listed in ifconfig nor does dmesg show any device.

No, the driver is not loading correctly because the N PHY is not yet 
supported. The reverse engineering for that device is barely started.

> # ifconfig
> eth0 [...]
> lo [...]
> 
> # dmesg
> [...]
> Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]
> [...]
> 
> I'm kind of new to all this wireless stuff. Linuxwireless.org tells me
> 4328 does not work because of missing N Phys support, so I hoped this
> patch would make some difference.

No, that patch is just preparation for what will happen in the future 
when both LP and N PHYs are supported.

> A problem could be the wrong firmware version. OS X says the Chip has
> 4.150.10.__6__ but I can only find 4.150.10.5. Is this important?

Driver 4.150.10.5 is a MIPS driver for Linux. Obviously 4.150.10.6 is 
an OS X driver. I wouldn't expect any difference in the embedded 
firmware between them.

Larry


  reply	other threads:[~2008-08-19 22:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 23:55 [PATCH RFT] b43: Rewrite PHY API for N-PHY/LP-PHY -- good on 4311 Niklas Wulf
2008-08-19 22:18 ` Larry Finger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-15 22:29 [PATCH RFT] b43: Rewrite PHY API for N-PHY/LP-PHY Michael Buesch
2008-08-17 19:26 ` [PATCH RFT] b43: Rewrite PHY API for N-PHY/LP-PHY -- good on 4311 Ehud Gavron
2008-08-17 20:42   ` Larry Finger
2008-08-18  7:41     ` Holger Schurig
2008-08-18 12:57       ` Michael Buesch
2008-08-18 13:48       ` Larry Finger
2008-08-18 13:01   ` Michael Buesch

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=48AB46AC.3090703@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=niklas@wulf-home.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.