linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Arend van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: brcmsmac on BCM47XX SoCs
Date: Sat, 07 Apr 2012 00:43:46 +0200	[thread overview]
Message-ID: <4F7F71A2.40105@hauke-m.de> (raw)

Hi Arend,

I am currently trying to get brcmsmac running on my SoC (bcm4718 +
bcm43224). Using the sprom from bcma and not fetching it in brcmsmac was
not a big problem, are you interested in the patch?
I want to remove the pci code from brcmsmac as it should go into bcma
and some/most parts of the code are already there. I already did some of
this but I still have problems with my device, have you already started
this? I do not know if these problems  are related to my changes or some
other problems with my devices and brcmsmac.

I want to get AP mode working on these device with brcmsmac, but for now
I do not even get station mode running. ;-)

Are there any devices with a ccrev < 20 supported by brcmsmac, the
lowest version I saw was 31 and there are some conditions in brcmsmac
for < 6, < 10 and < 20?

What are your plans to support phy_ht in brcmsmac, for now it is just
supported by b43?

I am a little confused by the vendorid/vid and vendorid/did and the
boardvendor and boardtype members. brcms_c_chipmatch() uses vendorid and
vendorid from the pci config space, but what is the equivalent for SoCs
not on pci bus? boardvendor and boardtype are fetched in
ai_nvram_process and are fetched from nvram when an SoC is used and from
pci config space on a pci device at least that is the way it is done in
the Boradcom SDK.

Hauke

             reply	other threads:[~2012-04-06 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 22:43 Hauke Mehrtens [this message]
2012-04-08  8:51 ` brcmsmac on BCM47XX SoCs Arend van Spriel
2012-04-08 19:54   ` Rafał Miłecki
2012-04-09 11:56     ` Hauke Mehrtens
2012-04-10 14:18       ` Arend van Spriel
2012-04-09 13:32     ` Seth Forshee
2012-04-09 13:06   ` Hauke Mehrtens
2012-04-14 20:20   ` 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=4F7F71A2.40105@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=arend@broadcom.com \
    --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).