From: Philipp Marek <philipp@marek.priv.at>
To: linux-wireless@vger.kernel.org
Subject: I'd like to help with bcm4328
Date: Sat, 23 Aug 2008 16:00:02 +0200 [thread overview]
Message-ID: <200808231600.02840@marek.priv.at> (raw)
Hello everybody,
I'd like to help with driver development for the bcm4328, on a Dell Latitude
630.
If I read the mail from Larry Finger (Aug 19th):
> No, the driver is not loading correctly because the N PHY is not yet
> supported. The reverse engineering for that device is barely started.
(http://marc.info/?l=linux-wireless&m=121918438723617&w=2)
I've done a fair share of assembler on i386 (and partly later, too); and I
know a bit about disassembling, too (see Games::Hack for an example:
http://search.cpan.org/search?query=Games%3A%3AHack&mode=all).
Can you give me some hint if/where I could help, or which parts of the
driver/IO space operations I could write documents for (that might be of most
value for you)?
Please keep me CC'ed.
Regards,
Phil
reply other threads:[~2008-08-23 14:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200808231600.02840@marek.priv.at \
--to=philipp@marek.priv.at \
--cc=linux-wireless@vger.kernel.org \
/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).