From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Michael Buesch <mb@bu3sch.de>,
bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: Broadcom cards for free
Date: Fri, 09 Oct 2009 10:22:27 -0500 [thread overview]
Message-ID: <4ACF5533.70307@lwfinger.net> (raw)
In-Reply-To: <69e28c910910090314j4e9885dfofbc58e901965b4ab@mail.gmail.com>
On 10/09/2009 05:14 AM, Gábor Stefanik wrote:
> Sounds interesting... especially now that N-PHY is actually being
> reverse-engineered (or is it?).
I'm still working on it, although a lot of my time is taken in testing
openSUSE 11.2 pre-release code. As the release date is Nov. 12, that
will soon be over.
Larry
prev parent reply other threads:[~2009-10-09 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 9:39 Broadcom cards for free Michael Buesch
2009-10-09 10:14 ` Gábor Stefanik
2009-10-09 10:34 ` Michael Buesch
2009-10-09 15:22 ` Larry Finger [this message]
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=4ACF5533.70307@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netrolller.3d@gmail.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).