All of lore.kernel.org
 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>,
	"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>
Subject: brcmsmac on BCM47XX SoCs
Date: Sat, 14 Apr 2012 22:20:27 +0200	[thread overview]
Message-ID: <4F89DC0B.20106@hauke-m.de> (raw)
In-Reply-To: <4F815181.6030007@broadcom.com>

On 04/08/2012 10:51 AM, Arend van Spriel wrote:
> On 04/06/2012 11:43 PM, Hauke Mehrtens wrote:
>> 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?
> 
> brcmsmac is targetted for bcm4313, bcm43224, and bcm43225 so the lowest
> is ccrev 32. The bcm4718 seems to have ccrev 31.
> 

Now I am at the pci core rev. Are there any bcma/ai based devices with a
PCI not PCIE core on the chip? The PCIE cores of my devices are rev 14
(BCM4718) and 15 (BCM43224) are there any devices with a bus supported
by bcma available with a revision less than 14? In brcmsmac is lots of
code to do something different on devices with such PCI(E) core revs.

Hauke

WARNING: multiple messages have this Message-ID (diff)
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>,
	"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>
Subject: Re: brcmsmac on BCM47XX SoCs
Date: Sat, 14 Apr 2012 22:20:27 +0200	[thread overview]
Message-ID: <4F89DC0B.20106@hauke-m.de> (raw)
In-Reply-To: <4F815181.6030007@broadcom.com>

On 04/08/2012 10:51 AM, Arend van Spriel wrote:
> On 04/06/2012 11:43 PM, Hauke Mehrtens wrote:
>> 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?
> 
> brcmsmac is targetted for bcm4313, bcm43224, and bcm43225 so the lowest
> is ccrev 32. The bcm4718 seems to have ccrev 31.
> 

Now I am at the pci core rev. Are there any bcma/ai based devices with a
PCI not PCIE core on the chip? The PCIE cores of my devices are rev 14
(BCM4718) and 15 (BCM43224) are there any devices with a bus supported
by bcma available with a revision less than 14? In brcmsmac is lots of
code to do something different on devices with such PCI(E) core revs.

Hauke

  parent reply	other threads:[~2012-04-14 20:20 UTC|newest]

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