From: "Henry Ptasinski" <henryp@broadcom.com>
To: "George Kashperko" <george@znau.edu.ua>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Michael Büsch" <mb@bu3sch.de>,
driverdevel <devel@driverdev.osuosl.org>,
"Henry Ptasinski" <henryp@broadcom.com>,
"Brett Rudley" <brudley@broadcom.com>,
"Roland Vossen" <rvossen@broadcom.com>,
"Arend Van Spriel" <arend@broadcom.com>
Subject: Re: [RFC] AI support
Date: Thu, 17 Feb 2011 18:43:08 -0800 [thread overview]
Message-ID: <4D5DDCBC.2050501@broadcom.com> (raw)
In-Reply-To: <1297958316.5623.27.camel@dev.znau.edu.ua>
On 02/17/2011 07:58 AM, George Kashperko wrote:
> Here is dmesg for AI on embeddable (BCM4716):
> root@OpenWrt:/# dmesg | grep -E "ssb|b43|[Bb]roadcom"
> ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x1F, vendor 0x04BF)
> ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x11, vendor 0x04BF)
> ssb: Core 2 found: Gigabit MAC (cc 0x82D, rev 0x00, vendor 0x04BF)
> ssb: Core 3 found: MIPS 74K (cc 0x82C, rev 0x01, vendor 0x04A7)
> ssb: Core 4 found: USB 2.0 Host (cc 0x819, rev 0x04, vendor 0x04BF)
> ssb: Core 5 found: PCI-E (cc 0x820, rev 0x0E, vendor 0x04BF)
> ssb: Core 6 found: DDR1/2 memory controller (cc 0x82E, rev 0x01, vendor 0x04BF)
> ssb: Core 7 found: Internal Memory (cc 0x80E, rev 0x07, vendor 0x04BF)
> ssb: Core 8 found: I2S (cc 0x834, rev 0x00, vendor 0x04BF)
> ssb: Found END of erom after 9 cores
> ssb: chipcommon status is 0x800
> ssb: Found rev 5 PMU (capabilities 0x11242C05)
> ssb: Initializing MIPS core...
> ssb: ssb_pmu5_clock: p1=1, p2=1, ndiv=48(0x30), m3=8, fc=960, clock=120
> ssb: set_irq: core 0x0812, irq 3 => 3
> ssb: set_irq: core 0x082d, irq 4 => 4
> ssb: set_irq: core 0x0819, irq 5 => 5
> ssb: after irq reconfiguration
> ssb: core 0x0800, irq : 2(S)* 3 4 5 6 D I
> ssb: core 0x0812, irq : 2(S) 3* 4 5 6 D I
> ssb: core 0x082d, irq : 2(S) 3 4* 5 6 D I
> ssb: core 0x082c, irq : 2(S) 3 4 5 6 D I*
> ssb: core 0x0819, irq : 2(S) 3 4 5* 6 D I
> ssb: core 0x0820, irq : 2(S) 3 4 5 6* D I
> ssb: core 0x082e, irq : 2(S)* 3 4 5 6 D I
> ssb: core 0x080e, irq : 2(S) 3 4 5 6 D I*
> ssb: core 0x0834, irq : 2(S)* 3 4 5 6 D I
> ssb: Sonics Silicon Backplane (AI type) found at address 0x18000000
This just reinforces what Michael said about name confusion.
Michael's proposal of separating SSB and AXI, and decoupling the device
drivers from the bus routines, is going to be much more maintainable in
the long run. AXI is going to be far more widespread than SSB ever was,
and it would be really unfortunate if we carry the SSB baggage forward.
I've been poking around at disentangling the sb and ai routines in
drivers/staging/brcm80211/utils/{aiutils,sbutils,siutils}.c. I don't
have anything to put out for comments yet, but it's enough to convince
me that it's the right direction.
- Henry
next prev parent reply other threads:[~2011-02-18 2:43 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 15:58 [RFC] AI support George Kashperko
2011-02-17 22:01 ` Michael Büsch
2011-02-17 22:06 ` [RFC] AI support (1/14 ssb admatch redefine) George Kashperko
2011-02-17 22:08 ` [RFC] AI support (2/14 ssb helpers) George Kashperko
2011-02-18 22:29 ` Michael Büsch
2011-02-18 23:15 ` George Kashperko
2011-02-18 23:29 ` Michael Büsch
2011-02-18 23:27 ` George Kashperko
2011-02-17 22:10 ` [RFC] AI support (3/14 ssb irqflag mips core op) George Kashperko
2011-02-17 22:12 ` [RFC] AI support (4/14 ssb mips core irqflag treatment) George Kashperko
2011-02-17 22:14 ` [RFC] AI support (5/14 ssb core control and state helpers) George Kashperko
2011-02-17 22:16 ` [RFC] AI support (6/14 ssb propagate core control and state helpers usage) George Kashperko
2011-02-17 22:18 ` [RFC] AI support (7/14 ssb bus_check_core routine) George Kashperko
2011-02-17 22:20 ` [RFC] AI support (8/14 ssb ssb_bus_detect routine) George Kashperko
2011-02-18 22:35 ` Michael Büsch
2011-02-17 22:23 ` [RFC] AI support (9/14 ssb SB-specific bus scan routine) George Kashperko
2011-02-17 22:25 ` [RFC] AI support (10/14 ssb bus implementation-specific io unmap) George Kashperko
2011-02-17 22:27 ` [RFC] AI support (11/14 ssb separate SB-specific code) George Kashperko
2011-02-17 22:29 ` [RFC] AI support (12/14 ssb mips74k core defs) George Kashperko
2011-02-17 22:31 ` [RFC] AI support (13/14 ssb add AI support) George Kashperko
2011-02-18 22:45 ` Michael Büsch
2011-02-18 23:07 ` George Kashperko
2011-02-18 23:27 ` Michael Büsch
2011-02-18 23:42 ` George Kashperko
2011-02-18 23:54 ` Michael Büsch
2011-02-18 23:51 ` George Kashperko
2011-02-18 23:46 ` Larry Finger
2011-02-18 23:47 ` George Kashperko
2011-02-19 0:06 ` Larry Finger
2011-02-19 0:08 ` George Kashperko
2011-02-19 0:22 ` Larry Finger
2011-02-17 22:35 ` [RFC] AI support (14/14 ssb AI on pci host (untested)) George Kashperko
2011-02-18 2:43 ` Henry Ptasinski [this message]
2011-02-18 7:39 ` [RFC] AI support George Kashperko
2011-02-18 11:53 ` Michael Büsch
2011-02-18 12:39 ` George Kashperko
2011-02-18 22:21 ` Michael Büsch
2011-02-18 22:52 ` George Kashperko
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=4D5DDCBC.2050501@broadcom.com \
--to=henryp@broadcom.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=george@znau.edu.ua \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=rvossen@broadcom.com \
--cc=zajec5@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).