From: George Kashperko <george@znau.edu.ua>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: balbi@ti.com, linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev@lists.infradead.org, "Michael Büsch" <mb@bu3sch.de>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
"Arend van Spriel" <arend@broadcom.com>,
linux-arm-kernel@lists.infradead.org,
"Russell King" <rmk@arm.linux.org.uk>,
"Arnd Bergmann" <arnd@arndb.de>,
"Andy Botting" <andy@andybotting.com>,
linuxdriverproject <devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] axi: add AXI bus driver
Date: Tue, 12 Apr 2011 23:57:34 +0300 [thread overview]
Message-ID: <1302641854.14216.77.camel@dev.znau.edu.ua> (raw)
In-Reply-To: <BANLkTim8dmTL-BVK3fcWHNBU9Eyz1k_T+Q@mail.gmail.com>
> 2011/4/12 George Kashperko <george@znau.edu.ua>:
> >> 2011/4/12 Rafał Miłecki <zajec5@gmail.com>:
> >> That way I see really low (or not at all) relation between out
> >> (not)Broadcom bus and present AMBA bus.
> >>
> > Agree.
>
> Ehh, sounds like one more renaming to functions, defines, prefixes.
>
> Let's wait for Arend comments, he was the one voting for not-bcm-specific name.
>
Sounds like good plan :)
Btw, while waiting.... Digging the web clearing different things around
ssb/axi found few broadcom ssb docs some of you maybe find interesting
to look through.
http://read.pudn.com/downloads127/doc/fileformat/537112/mips/bcm5836/5836-5836P-PG01-RDS.pdf
http://www.broadcom.com/collateral/pg/440X-PG02-R.pdf
Also, one more question to Arend:
could you please ask if there are any plans on lifting UNPUBLISHED
PROPRIETARY for GMAC core driver sources (etcgmac.c, have this core at
bcm4716-based ASUS N16, might used at other bcm471X socs as well) or
possibly Broadcom could publish some doc for the chip?
Have nice day,
George
next prev parent reply other threads:[~2011-04-12 21:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 23:57 [RFC][PATCH] axi: add AXI bus driver Rafał Miłecki
2011-04-11 23:22 ` Rafał Miłecki
2011-04-11 23:35 ` Greg KH
2011-04-12 13:04 ` Rafał Miłecki
2011-04-12 13:18 ` Arend van Spriel
2011-04-12 13:21 ` Rafał Miłecki
2011-04-12 13:27 ` Arend van Spriel
2011-04-12 13:36 ` Felipe Balbi
2011-04-12 18:47 ` George Kashperko
2011-04-12 18:59 ` Rafał Miłecki
2011-04-12 19:12 ` George Kashperko
2011-04-12 19:27 ` Rafał Miłecki
2011-04-12 19:34 ` George Kashperko
2011-04-12 19:46 ` Rafał Miłecki
2011-04-12 20:07 ` George Kashperko
2011-04-12 19:47 ` Hauke Mehrtens
2011-04-12 19:58 ` Rafał Miłecki
2011-04-12 20:13 ` Rafał Miłecki
2011-04-12 20:35 ` George Kashperko
2011-04-12 20:44 ` Rafał Miłecki
2011-04-12 20:57 ` George Kashperko [this message]
2011-04-13 8:16 ` Arend van Spriel
2011-04-13 19:50 ` Rafał Miłecki
2011-04-13 20:23 ` George Kashperko
2011-04-13 21:05 ` Rafał Miłecki
2011-04-13 21:58 ` Rafał Miłecki
2011-04-13 23:07 ` Rafał Miłecki
2011-04-13 23:31 ` Rafał Miłecki
2011-04-13 20:49 ` Nick Bowler
2011-04-12 20:23 ` 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=1302641854.14216.77.camel@dev.znau.edu.ua \
--to=george@znau.edu.ua \
--cc=Larry.Finger@lwfinger.net \
--cc=andy@andybotting.com \
--cc=arend@broadcom.com \
--cc=arnd@arndb.de \
--cc=b43-dev@lists.infradead.org \
--cc=balbi@ti.com \
--cc=devel@linuxdriverproject.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=rmk@arm.linux.org.uk \
--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).