Skip to contentSkip to conversation

pci id 14e4:4727 (bcm4313) status?

DISCUSSION Jason 3 participants 3 messages Nov 3, 2010

lore
Share & tools
lore

Jason

author
#0 lore raw

All,

I have a pci-express card that shows itself as pci_id 14e4:4727. According to [1], it says partial support since 2.6.33 (b43/wl/brcm80211). I was hoping that meant b43 since it has much better mac80211 integration than brcm80211. I didn't think brcm80211 was in 2.6.33.

However, compat-wireless (built from tarball) doesn't see it. grep the source code doesn't pull up '4727' in b43... I tried to update my wireless-testing-2.6 tree, but it looks like it's still having trouble, latest is 229aebb... from Oct 24th.

So, what will it take to get it up and running? I've contributed some patches to staging, but they're mainly janitorial/checkpatch stuff for brcm80211. Are there some beginner tasks for b43 (ie dig through brcm80211 and port over) that might help out?

thx,

Jason.

[1] http://linuxwireless.org/en/users/Drivers/b43#Known_PCI_devices

#1 lore raw
Quoted 16 lines · Jason

All,

I have a pci-express card that shows itself as pci_id 14e4:4727. ?According to [1], it says partial support since 2.6.33 (b43/wl/brcm80211). ?I was hoping that meant b43 since it has much better mac80211 integration than brcm80211. ?I didn't think brcm80211 was in 2.6.33.
However, compat-wireless (built from tarball) doesn't see it. ?grep the source code doesn't pull up '4727' in b43... I tried to update my wireless-testing-2.6 tree, but it looks like it's still having trouble, latest is 229aebb... from Oct 24th.

So, what will it take to get it up and running? ?I've contributed some patches to staging, but they're mainly janitorial/checkpatch stuff for brcm80211. ?Are there some beginner tasks for b43 (ie dig through brcm80211 and port over) that might help out?

Quoted 5 lines

thx,

Jason.

[1] http://linuxwireless.org/en/users/Drivers/b43#Known_PCI_devices

Hi,

AFAIK 4313 is an SSB-less device, so it will probably never be supported by b43 (though expect eventual code sharing between the 2 drivers).

Quoted 7 lines

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

Signature · 1 line
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
#2 lore raw
In reply to Jason
Quoted 12 lines · Jason

All,

I have a pci-express card that shows itself as pci_id 14e4:4727. According to [1], it says partial support since 2.6.33 (b43/wl/brcm80211). I was hoping that meant b43 since it has much better mac80211 integration than brcm80211. I didn't think brcm80211 was in 2.6.33.
However, compat-wireless (built from tarball) doesn't see it. grep the source code doesn't pull up '4727' in b43... I tried to update my wireless-testing-2.6 tree, but it looks like it's still having trouble, latest is 229aebb... from Oct 24th.

Quoted 4 lines

So, what will it take to get it up and running? I've contributed some patches to staging, but they're mainly janitorial/checkpatch stuff for brcm80211. Are there some beginner tasks for b43 (ie dig through brcm80211 and port over) that might help out?

That device is not supported by b43. As it now stands, b43 requires a device with the SSB interconnect, which the BCM4313 does not have. If you did fix b43 to operate without the SSB, then you would still have no support for N PHY. That one is being worked on so that N PHYs with SSB can be supported.

My interpretation of the "partially supported" statement is that bleeding-edge compat wireless has been backported that far.

My latest pull of wireless-testing has 2.6.37-rc1 from November 1. It includes brcm80211.

Larry