fwd to [email protected]
---------- Forwarded message ----------
=46rom: Xose Vazquez Perez <[email protected]>
Date: Fri, Feb 27, 2009 at 18:46
Subject: b43* linux driver, more ids dev
To: [email protected], [email protected],
[email protected], [email protected]
hi,
are there any trouble with these devices ? why are they not =A0inside
b43* drivers ?
PCI_VENDOR_ID_BROADCOM, 0x4313
PCI_VENDOR_ID_BROADCOM, 0x4315
PCI_VENDOR_ID_BROADCOM, 0x432a
PCI_VENDOR_ID_BROADCOM, 0x432b
PCI_VENDOR_ID_BROADCOM, 0x432c
PCI_VENDOR_ID_BROADCOM, 0x432d
taken from the vendor's driver src:
http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-x86_32-v5_10_27_1=
4.tar.gz
more info at: http://www.broadcom.com/support/802.11/linux_sta.php
-thanks-
regards,
--
Polycommander, Erkowit, Urquiola, Andros Patria, Cason, Aegean Sea,
Prestige, ...
--=20
Polycommander, Erkowit, Urquiola, Andros Patria, Cason, Aegean Sea,
Prestige, ...
Larry Finger wrote:
> Xose Vazquez Perez wrote:
>
>> are there any trouble with these devices ? why are they not inside
>> b43* drivers ?
>>
>> PCI_VENDOR_ID_BROADCOM, 0x4313
>> PCI_VENDOR_ID_BROADCOM, 0x4315
>> PCI_VENDOR_ID_BROADCOM, 0x432a
>> PCI_VENDOR_ID_BROADCOM, 0x432b
>> PCI_VENDOR_ID_BROADCOM, 0x432c
>> PCI_VENDOR_ID_BROADCOM, 0x432d
>
> Those devices are either LP PHY (4315 and probably 4313) or N PHY (432X)
> devices. The reverse engineering for the LP PHY was just completed, but the code
> is not yet written. The RE for the N PHY has barely begun.
>
> Once there is code to drive those devices, their ID's will be added.
It smells like another crap_driver for staging tree.
--
Polycommander, Erkowit, Urquiola, Andros Patria, Cason, Aegean Sea, Prestige, ...
Xose Vazquez Perez wrote:
> are there any trouble with these devices ? why are they not inside
> b43* drivers ?
>
> PCI_VENDOR_ID_BROADCOM, 0x4313
> PCI_VENDOR_ID_BROADCOM, 0x4315
> PCI_VENDOR_ID_BROADCOM, 0x432a
> PCI_VENDOR_ID_BROADCOM, 0x432b
> PCI_VENDOR_ID_BROADCOM, 0x432c
> PCI_VENDOR_ID_BROADCOM, 0x432d
Those devices are either LP PHY (4315 and probably 4313) or N PHY (432X)
devices. The reverse engineering for the LP PHY was just completed, but the code
is not yet written. The RE for the N PHY has barely begun.
Once there is code to drive those devices, their ID's will be added.
Larry
Michael Buesch wrote:
> On Friday 27 February 2009 20:15:17 Xose Vazquez Perez wrote:
>>
>> It smells like another crap_driver for staging tree.
>>
> No it doesn't. It is closed source.
> Please read the documentation before posting the next mail. Thanks.
I did a grep and I saw "GPL", but now I also see the
"special exception" in the head of the code and the lib/wlc_hybrid.o_shipped file
Sorry about that.
-thanks-
regards,
--
Polycommander, Erkowit, Urquiola, Andros Patria, Cason, Aegean Sea, Prestige, ...
On Fri, Feb 27, 2009 at 06:55:15PM +0100, Xose Vazquez Perez wrote:
> fwd to [email protected]
>=20
>=20
> ---------- Forwarded message ----------
> From: Xose Vazquez Perez <[email protected]>
> Date: Fri, Feb 27, 2009 at 18:46
> Subject: b43* linux driver, more ids dev
> To: [email protected], [email protected],
> [email protected], [email protected]
>=20
>=20
> hi,
>=20
> are there any trouble with these devices ? why are they not =A0inside
> b43* drivers ?
>=20
> PCI_VENDOR_ID_BROADCOM, 0x4313
> PCI_VENDOR_ID_BROADCOM, 0x4315
> PCI_VENDOR_ID_BROADCOM, 0x432a
> PCI_VENDOR_ID_BROADCOM, 0x432b
> PCI_VENDOR_ID_BROADCOM, 0x432c
> PCI_VENDOR_ID_BROADCOM, 0x432d
>=20
>=20
> taken from the vendor's driver src:
> http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-x86_32-v5_10_27=
_14.tar.gz
>=20
> more info at: http://www.broadcom.com/support/802.11/linux_sta.php
If I'm not mistaken, that driver only covers hardware that is _not_
supported by b43 or b43legacy today.
John
--=20
John W. Linville Someday the world will need a hero, and you
[email protected] might be all we have. Be ready.
On Friday 27 February 2009 20:15:17 Xose Vazquez Perez wrote:
> Larry Finger wrote:
>
> > Xose Vazquez Perez wrote:
> >
> >> are there any trouble with these devices ? why are they not inside
> >> b43* drivers ?
> >>
> >> PCI_VENDOR_ID_BROADCOM, 0x4313
> >> PCI_VENDOR_ID_BROADCOM, 0x4315
> >> PCI_VENDOR_ID_BROADCOM, 0x432a
> >> PCI_VENDOR_ID_BROADCOM, 0x432b
> >> PCI_VENDOR_ID_BROADCOM, 0x432c
> >> PCI_VENDOR_ID_BROADCOM, 0x432d
> >
> > Those devices are either LP PHY (4315 and probably 4313) or N PHY (432X)
> > devices. The reverse engineering for the LP PHY was just completed, but the code
> > is not yet written. The RE for the N PHY has barely begun.
> >
> > Once there is code to drive those devices, their ID's will be added.
>
> It smells like another crap_driver for staging tree.
>
No it doesn't. It is closed source.
Please read the documentation before posting the next mail. Thanks.
--
Greetings, Michael.