El día Tuesday, October 04, 2011 a las 11:14:20AM -0400, Arnaud Lacombe
escribió:
> > Both b43 (via reverse engineering) and brcm (via broadcom developers)
> > is getting active development. It'd be nice to have datasheets but you
> > don't need them to port the code over.
> >
> There was an arti
On Tue, Oct 04, 2011 at 11:16:52AM -0400, Arnaud Lacombe wrote:
> Hi,
>
> On Tue, Oct 4, 2011 at 10:39 AM, Adrian Chadd wrote:
> > The non-embedded atheros NICs (ie, not the ath6k series stuff) is all
> > run by the host CPU. There's no firmware that runs on the NIC.
> > This was why the HAL was
Hi,
On Tue, Oct 4, 2011 at 10:39 AM, Adrian Chadd wrote:
> The non-embedded atheros NICs (ie, not the ath6k series stuff) is all
> run by the host CPU. There's no firmware that runs on the NIC.
> This was why the HAL was binary for so long. Note it is no longer
> binary and hasn't been for a few
Hi,
On Tue, Oct 4, 2011 at 8:28 AM, Adrian Chadd wrote:
> On 4 October 2011 16:37, Matthias Apitz wrote:
>>
>> yes; but with good datasheets this would be more easy;
>
> There's working code for the later chips in Linux and likely (via
> Linux) OpenBSD.
>
> Linux has b43 and brcm drivers. The so
The non-embedded atheros NICs (ie, not the ath6k series stuff) is all
run by the host CPU. There's no firmware that runs on the NIC.
This was why the HAL was binary for so long. Note it is no longer
binary and hasn't been for a few years.
So I think we can ignore the whole "binary firmware" proble
On Tue, Oct 04, 2011 at 10:37:10AM +0200, Matthias Apitz wrote:
> El d?a Tuesday, October 04, 2011 a las 03:34:46PM +0800, Adrian Chadd
> escribi?:
>
> > That's because it's a wifi chip, not an ethernet chip.
>
> Yes, I know and I looked around in their pages; there are no Wifi chips;
> so my qu
On 4 October 2011 16:37, Matthias Apitz wrote:
>
> yes; but with good datasheets this would be more easy;
There's working code for the later chips in Linux and likely (via
Linux) OpenBSD.
Linux has b43 and brcm drivers. The source is there - what's missing
is someone choosing one and porting it
El día Tuesday, October 04, 2011 a las 03:34:46PM +0800, Adrian Chadd escribió:
> That's because it's a wifi chip, not an ethernet chip.
Yes, I know and I looked around in their pages; there are no Wifi chips;
so my question was: why is this?
> We sorely need someone to step up and update the br
That's because it's a wifi chip, not an ethernet chip.
We sorely need someone to step up and update the broadcom wifi support. :)
adrian
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, sen
El día Monday, October 03, 2011 a las 02:33:02PM -0400, Arnaud Lacombe escribió:
> Hi,
>
> On Mon, Oct 3, 2011 at 11:36 AM, Sean Bruno wrote:
> > Didn't realize this until my ride to work today, but Broadcom has their
> > programming spec/docs up on a public page. Just thought folks would
> > l
On Mon, 03 Oct 2011 08:36:39 -0700
Sean Bruno wrote:
> Didn't realize this until my ride to work today, but Broadcom has
> their programming spec/docs up on a public page. Just thought folks
> would like to know.
>
> http://www.broadcom.com/support/ethernet_nic/open_source.php
Thanks for this
Hi,
On Mon, Oct 3, 2011 at 11:36 AM, Sean Bruno wrote:
> Didn't realize this until my ride to work today, but Broadcom has their
> programming spec/docs up on a public page. Just thought folks would
> like to know.
>
> http://www.broadcom.com/support/ethernet_nic/open_source.php
>
That is a very
12 matches
Mail list logo
