linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: Michael Buesch <mb@bu3sch.de>,
	Tim Gardner <tim.gardner@canonical.com>,
	John Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org,
	"bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>
Subject: Re: Open source driver with binary HAL for BCM4313 from Broadcom
Date: Wed, 11 Jun 2008 15:02:11 -0500	[thread overview]
Message-ID: <48502F43.6040000@lwfinger.net> (raw)
In-Reply-To: <69e28c910806111250k4bfe0190h9cfd5937d47b1bbc@mail.gmail.com>

Stefanik G=E1bor wrote:
> On Wed, Jun 11, 2008 at 8:47 PM, Michael Buesch <mb@bu3sch.de> wrote:
>> On Wednesday 11 June 2008 19:44:52 Tim Gardner wrote:
>>> John,
>>>
>>> Here is the URL to Broadcom's web site advertising their open sourc=
e
>>> driver with support for the BCM4313.
>>>
>>> http://www.broadcom.com/support/802.11/linux_sta.php
>>>
>>> rtg
>> <quote>
>> Make sure that you download the appropriate tar because the hybrid b=
inary
>> file must be of the appropriate architecture type. The hybrid binary=
 file
>> is agnostic to the specific version of the Linux kernel because it i=
s
>> designed to perform all interactions with the operating system throu=
gh
>> operating-system-specific files...
>> </quote>
>>
>> --
>> Greetings Michael.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wire=
less" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>=20
> Also, the download links are broken. And AFAIK we do support BCM4312,
> although not PCI ID 0x4315 (that would be BCM4310).
> (CCing the bcm43xx mailing list.)

Watch out for their tarballs as they will dump all over the directory=20
that you are in when you invoke tar.

Larry
--
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

  reply	other threads:[~2008-06-11 20:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 17:44 Open source driver with binary HAL for BCM4313 from Broadcom Tim Gardner
2008-06-11 18:47 ` Michael Buesch
2008-06-11 19:47   ` Pavel Roskin
2008-06-11 20:26     ` Stefanik Gábor
2008-06-11 21:00       ` Larry Finger
2008-06-11 21:02       ` Pavel Roskin
2008-06-11 21:31       ` Broadcom's Hybrid Driver Larry Finger
2008-06-11 21:46         ` Stefanik Gábor
2008-06-11 21:53         ` Pavel Roskin
2008-06-11 21:55           ` Johannes Berg
2008-06-11 19:50   ` Open source driver with binary HAL for BCM4313 from Broadcom Stefanik Gábor
2008-06-11 20:02     ` Larry Finger [this message]
2008-06-11 19:46 ` Stephen Hemminger
2008-06-11 21:28   ` Johannes Berg
2008-06-11 21:12 ` Hauke Mehrtens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48502F43.6040000@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=netrolller.3d@gmail.com \
    --cc=tim.gardner@canonical.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).