On 11/25/2013 01:54 PM, Rafał Miłecki wrote:
2013/11/25 Christopher Horler <cshor...@googlemail.com>:
On 25 November 2013 16:42, Larry Finger <larry.fin...@lwfinger.net> wrote:
On 11/25/2013 05:32 AM, Hauke Mehrtens wrote:
On 11/25/2013 11:33 AM, Christopher Horler wrote:
Hi All,
I enabled the (broken) LCN PHY support. I understand it's broken, I'm
not expecting it to work... at least not yet!
Is anyone looking at this?
Are there any obvious major blocking issues (so as to avoid unnecessary
effort)?
Chris
I do not think anybody will work on adding support for the LCN PHY
(BCM4313) to b43 any more, because brcmsmac already supports this device.
There is some code missing to make this card working in b43, it is not
working at all, you should use brcmsmac.
As the only person working on reverse engineering of Broadcom chips, I am
certain that anything missing from the LCN specs is unlikely to be added. I
agree that you should use brcmsmac and report all problems.
Larry
Thanks for the info guys.
okay, will use brcmsmac - I've just noted the same info about LCN PHY
support is also here:
http://wireless.kernel.org/en/users/Drivers/b43#Comparison_of_recent_drivers
I also failed to notice that my system is automatically loading b43,
ssb, brcmsmac and bcma. Is it normal (or necessary) for both drivers
to be loaded?
Things still seem to work correctly if I blacklist b43.
This is weird, even if b43 claims 802.11 device on your card, it
should simply exit after detecting unsupported hardware. That should
let brcmsmac load and work just fine.
If that doesn't work that way, I think it's something wrong there.
In the very first post in this thread, the OP said that he enabled the LCN PHY
option. Does that change the behavior?
Larry
_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev
