From: Larry Finger <Larry.Finger@lwfinger.net>
To: feng tian <feng.of.tian@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: Abour linux driver supports BCM4325
Date: Sat, 22 Aug 2009 21:59:18 -0500 [thread overview]
Message-ID: <4A90B086.1020503@lwfinger.net> (raw)
In-Reply-To: <f42a38140908221927qabc3f25t60f348f7c4a446c9@mail.gmail.com>
feng tian wrote:
> Thank you for the information.
> I get your point. As for the radio and phy driver, I think it's some
> command based configurations for the chip via SDIO. And that I can
> refer to the BCM 43xx PCI driver codes.
> Wonder if it's feasible. Needs your comments.
> Thanks
The first step is to be able to read/write the various registers via
SDIO. That will be similar to the PCI operations. The next step is
knowing what to read/write and when. We are still working that out for
PCI. It is not trivial. See the recent postings of patches for the LP
pHY in the linux-wireless mailing list. These are _NOT_ complete.
next prev parent reply other threads:[~2009-08-23 3:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 6:19 Abour linux driver supports BCM4325 feng tian
2009-08-21 6:22 ` feng tian
2009-08-21 13:13 ` Dan Williams
2009-08-22 5:11 ` feng tian
2009-08-21 12:13 ` Larry Finger
2009-08-21 12:40 ` Johannes Berg
2009-08-22 5:42 ` feng tian
2009-08-22 14:27 ` Larry Finger
2009-08-22 18:13 ` Johannes Berg
2009-08-23 2:27 ` feng tian
2009-08-23 2:59 ` Larry Finger [this message]
2009-08-23 9:13 ` Johannes Berg
2009-08-23 12:55 ` Michael Buesch
2009-08-23 13:24 ` Gábor Stefanik
2009-08-23 13:30 ` Michael Buesch
2009-08-23 13:33 ` Gábor Stefanik
2009-08-23 15:30 ` feng tian
2009-08-24 6:03 ` feng tian
2009-08-24 9:08 ` Michael Buesch
2009-08-24 9:35 ` feng tian
2009-08-25 7:16 ` feng tian
2009-08-25 10:53 ` Michael Buesch
2009-08-27 9:33 ` feng tian
2009-08-27 10:40 ` Michael Buesch
2009-08-24 8:06 ` Holger Schurig
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=4A90B086.1020503@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=feng.of.tian@gmail.com \
--cc=johannes@sipsolutions.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.