On 10/18/2010 05:02 PM, RafaÅ MiÅecki wrote:
W dniu 9 paÅdziernika 2010 00:07 uÅytkownik RafaÅ MiÅecki
<zajec5@xxxxxxxxx> napisaÅ:
Hi Broadcom fellows!
It's great that afters long years of... well, pretty horrible
relations with Linux/opensource you have taken actions to change your
image. I guess brcm80211 it's perfect yet, and people may like it more
or less, but it's no doubt you made step in the right direction.
Thanks for that!
As you should know, you released driver and firmware for 802.11n
devices only. I believe it was right, as these device seem to be the
most nowadays and were the only ones without any open source support.
For older devices: G-PHY and LP-PHY we have working b43 driver that is
in relatively good shape. However... there is one thing we still miss
for olders cards.
Every time someone wants to use b43 it's necessary to download quite
big package from openwrt, unpack it, extract firmware and install it.
That simply happens because we don't have just-firmware files with
nice licensing. And of course there goes my request:
*Can you submit G-PHY and LP-PHY firmware to linux-firmware using some
normal licensing, please?*
This is of course not the best I could wish for, but is important
anyway and it should be easy decision. Ideally you could release
sources of firmware (plus toolchain eventualy... however, we have nice
toolchain from Michael), but I guess it would need more time and
decisions to make it happen. So as for now I guess we would be happy
with just closed source but easy-distributable firmware. Could you
release, submit it?
Greg: I didn't receive any answer from Broadcom for any mail. Do you
maybe have any "working" contact with this company? :|
Sorry for the delay in responding. We are exploring what is possible
but for the moment the answer is no. At present our focus is on
providing the best open source solution we can for 4313, 43224, 43225,
4329 and future chips sets.
- Henry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
