* Fwd: b43* linux driver, more ids dev [not found] <ee588a540902270946h13e03b6el71de5237a458b7a3@mail.gmail.com> @ 2009-02-27 17:55 ` Xose Vazquez Perez 2009-02-27 18:41 ` John W. Linville 2009-02-27 18:56 ` Larry Finger 0 siblings, 2 replies; 6+ messages in thread From: Xose Vazquez Perez @ 2009-02-27 17:55 UTC (permalink / raw) To: linux-wireless fwd to linux-wireless@vger.kernel.org ---------- Forwarded message ---------- =46rom: Xose Vazquez Perez <xose.vazquez@gmail.com> Date: Fri, Feb 27, 2009 at 18:46 Subject: b43* linux driver, more ids dev To: mb@bu3sch.de, Larry.Finger@lwfinger.net, johannes@sipsolutions.net, stefano.brivio@polimi.it 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, ... -- To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Fwd: b43* linux driver, more ids dev 2009-02-27 17:55 ` Fwd: b43* linux driver, more ids dev Xose Vazquez Perez @ 2009-02-27 18:41 ` John W. Linville 2009-02-27 18:56 ` Larry Finger 1 sibling, 0 replies; 6+ messages in thread From: John W. Linville @ 2009-02-27 18:41 UTC (permalink / raw) To: Xose Vazquez Perez; +Cc: linux-wireless On Fri, Feb 27, 2009 at 06:55:15PM +0100, Xose Vazquez Perez wrote: > fwd to linux-wireless@vger.kernel.org >=20 >=20 > ---------- Forwarded message ---------- > From: Xose Vazquez Perez <xose.vazquez@gmail.com> > Date: Fri, Feb 27, 2009 at 18:46 > Subject: b43* linux driver, more ids dev > To: mb@bu3sch.de, Larry.Finger@lwfinger.net, > johannes@sipsolutions.net, stefano.brivio@polimi.it >=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 linville@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Fwd: b43* linux driver, more ids dev 2009-02-27 17:55 ` Fwd: b43* linux driver, more ids dev Xose Vazquez Perez 2009-02-27 18:41 ` John W. Linville @ 2009-02-27 18:56 ` Larry Finger 2009-02-27 19:15 ` Xose Vazquez Perez 1 sibling, 1 reply; 6+ messages in thread From: Larry Finger @ 2009-02-27 18:56 UTC (permalink / raw) To: Xose Vazquez Perez; +Cc: linux-wireless 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Fwd: b43* linux driver, more ids dev 2009-02-27 18:56 ` Larry Finger @ 2009-02-27 19:15 ` Xose Vazquez Perez 2009-02-27 19:19 ` Michael Buesch 0 siblings, 1 reply; 6+ messages in thread From: Xose Vazquez Perez @ 2009-02-27 19:15 UTC (permalink / raw) To: Larry Finger, linux-wireless 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, ... ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Fwd: b43* linux driver, more ids dev 2009-02-27 19:15 ` Xose Vazquez Perez @ 2009-02-27 19:19 ` Michael Buesch 2009-02-27 19:31 ` Xose Vazquez Perez 0 siblings, 1 reply; 6+ messages in thread From: Michael Buesch @ 2009-02-27 19:19 UTC (permalink / raw) To: Xose Vazquez Perez; +Cc: Larry Finger, linux-wireless 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Fwd: b43* linux driver, more ids dev 2009-02-27 19:19 ` Michael Buesch @ 2009-02-27 19:31 ` Xose Vazquez Perez 0 siblings, 0 replies; 6+ messages in thread From: Xose Vazquez Perez @ 2009-02-27 19:31 UTC (permalink / raw) To: Michael Buesch; +Cc: Larry Finger, linux-wireless 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, ... ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-02-27 19:31 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <ee588a540902270946h13e03b6el71de5237a458b7a3@mail.gmail.com>
2009-02-27 17:55 ` Fwd: b43* linux driver, more ids dev Xose Vazquez Perez
2009-02-27 18:41 ` John W. Linville
2009-02-27 18:56 ` Larry Finger
2009-02-27 19:15 ` Xose Vazquez Perez
2009-02-27 19:19 ` Michael Buesch
2009-02-27 19:31 ` Xose Vazquez Perez
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).