multiple SSID support (in BCM4318)

Hello all,
are multiple SSID supported (especially on BCM4318)? I could not find the  
answer through googling.

By tw way, on your page, you say "BCM4318 chipset: AP mode does not work  
because of packet loss in high transmission rates. Hard to debug & fix."  
IS it still true? It seems to me it works fine, but I have been trying it  
only for a while.
Regards,
Tomas

Re: multiple SSID support (in BCM4318)

On 05/06/2012 01:29 AM, Tomáš Hnyk wrote:
> Hello all,
> are multiple SSID supported (especially on BCM4318)? I could not find the answer
> through googling.
>
> By tw way, on your page, you say "BCM4318 chipset: AP mode does not work because
> of packet loss in high transmission rates. Hard to debug & fix." IS it still
> true? It seems to me it works fine, but I have been trying it only for a while.
> Regards,
> Tomas

To my knowledge, there have been no fixes specific for the BCM4318 that were 
aimed at fixing the packet loss at high transmission rates; however, there have 
been a lot of fixes for b43. Perhaps one or more of them helped that problem. 
Your tests will likely tell.

As to the multiple SSID question, that will be a function of mac80211 and 
friends. Comment #3 of http://forums.freebsd.org/showthread.php?t=24268 seems to 
have a prescription for using nl80211 to accomplish that. If that posting 
doesn't answer your question, direct further inquiries to 
linux-wireless@...

Larry

Re: multiple SSID support (in BCM4318)

On May 6, 2012, at 8:29 AM, Tomáš Hnyk wrote:

> Hello all,
> are multiple SSID supported (especially on BCM4318)? I could not find the answer through googling.
> 
> By tw way, on your page, you say "BCM4318 chipset: AP mode does not work because of packet loss in high
transmission rates. Hard to debug & fix." IS it still true? It seems to me it works fine, but I have been
trying it only for a while.
Hi Tomás,

this problem was almost not detectable by users and it was finally addressed here http://lists.infradead.org/pipermail/b43-dev/2011-December/002249.html

Everything should work fine as you say.

KR,
-Francesco

> Regards,
> Tomas
> 
> _______________________________________________
> b43-dev mailing list
> b43-dev@...
> http://lists.infradead.org/mailman/listinfo/b43-dev

Procedure for donating hardware to b43 project

Hello,

I am interested in donating a Broadcom BCM94228HMB Mini-PCIe card for
the purpose of open source driver development. The card has the PCI ID
14e4:4359 This device is listed as not tested on the b43 driver website
[1] and upon binding the pci device to the bcma driver and force loading
b43 in kernel version 3.3.6 I get the following output.

[13174.301451] bcma: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800,
rev 0x25, class 0x0)
[13174.301475] bcma: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812,
rev 0x1E, class 0x0)
[13174.301526] bcma: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev
0x12, class 0x0)
 [13174.301548] bcma: Core 3 found: SDIO Device (manuf 0x4BF, id 0x829,
rev 0x07, class 0x0)
[13174.301667] bcma: PLL init unknown for device 0xA8DC
[13174.301669] bcma: PMU resource config unknown for device 0xA8DC
[13174.301671] bcma: PMU switch/regulators init unknown for device 0xA8DC
[13174.301672] bcma: Workarounds unknown for device 0xA8DC
[13174.308903] bcma: No SPROM available
[13174.308995] bcma: Bus registered
[13174.327537] b43-phy0: Broadcom 43228 WLAN found (core revision 30)
[13174.327953] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 9, Type 9,
Revision 0)
[13174.327958] b43: probe of bcma0:1 failed with error -95
[13174.327968] Broadcom 43xx driver loaded [ Features: PMNLS ]

Incidentally the card seems to have a Bluetooth component as well, but
this does not show up at all under linux.

Basic Structure of b43 wireless driver

Hello everyone,

I am a student and I am doing a research to modify b43 wireless driver
for supporting APE Testbed. So I have to understand the structure of
b43 source code but it is really complicated with multiple files.
Please anyone can guide me!!! (For example: "what is the purpose of
each file or each function?" or "how I can read and understand these
codes?").

Thank you for your supporting.

Re: Basic Structure of b43 wireless driver

On Wed, 23 May 2012 09:38:33 +0700
Le Hoang Phuong <nhoxleesieuquay@...> wrote:

> "how I can read and understand these codes?").

The best way to read and understand code is to read it. Really. I think
this is the only way to get you started. Start in main.c and look through
the code. But first learn how linux device drivers work in general.
There are quite some books and tutorials on the net on this topic.

If you have any _specific_ question about parts of the code, we'll be happy
to answer them.

--

-- 
Greetings, Michael.

PGP encryption is encouraged / 908D8B0E

_______________________________________________
b43-dev mailing list
b43-dev@...
http://lists.infradead.org/mailman/listinfo/b43-dev

[PATCH] b43: ensure ext PA lines are enabled for BCM4331

Some MacBook Pro models with BCM4331 wireless will stop transmitting
after resuming from S3 without external power attached. This is fixed by
ensuring that the ext PA lines are enabled in BCMA_CC_CHIPCTL. Export
the function in bcma which does this for use by b43 and enable the ext
PA lines during wireless core initialization.

BugLink: http://bugs.launchpad.net/bugs/925577
Cc: Arend van Spriel <arend@...>
Cc: stable@...
Signed-off-by: Seth Forshee <seth.forshee@...>
---
 drivers/bcma/driver_chipcommon_pmu.c |    1 +
 drivers/net/wireless/b43/main.c      |    7 +++++++
 2 files changed, 8 insertions(+)

diff --git a/drivers/bcma/driver_chipcommon_pmu.c b/drivers/bcma/driver_chipcommon_pmu.c
index a058842..332d7fb 100644
--- a/drivers/bcma/driver_chipcommon_pmu.c
+++ b/drivers/bcma/driver_chipcommon_pmu.c
 <at>  <at>  -129,6 +129,7  <at>  <at>  void bcma_chipco_bcm4331_ext_pa_lines_ctl(struct bcma_drv_cc *cc, bool enable)
 	}
 	bcma_cc_write32(cc, BCMA_CC_CHIPCTL, val);
 }
+EXPORT_SYMBOL_GPL(bcma_chipco_bcm4331_ext_pa_lines_ctl);

 void bcma_pmu_workarounds(struct bcma_drv_cc *cc)
 {
diff --git a/drivers/net/wireless/b43/main.c b/drivers/net/wireless/b43/main.c
index 5a39b22..6bac5cf 100644
--- a/drivers/net/wireless/b43/main.c

Re: [PATCH] b43: ensure ext PA lines are enabled for BCM4331

On Thu, May 31, 2012 at 04:16:05PM +0200, Hauke Mehrtens wrote:
> Hi Seth,
> 
> why don't you call this from bcma_pmu_workarounds() in
> drivers/bcma/driver_chipcommon_pmu.c instead of calling this from b43? I
> think it looks better to call some workarounds on chip common from bcma
> and not from b43.

Arend recommended calling it from within b43's start op, but I'm not
sure of the reason. Arend?

Agreed though that if there's no need to run it every time the interface
is started then bcma_pmu_workarounds() would be a nicer place for it.

> According to some Broadcom code this should also be called for chip_id
> 43431 when turning it on and in the sprom code.

I'm having trouble parsing this, specifically the "and in the sprom
code" part. Can you clarify?

Thanks,
Seth