From: George Kashperko <george@znau.edu.ua>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
Russell King <rmk@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Arend van Spriel <arend@broadcom.com>,
Jonas Gorski <jonas.gorski@gmail.com>,
b43-dev@lists.infradead.org, Greg KH <greg@kroah.com>,
Andy Botting <andy@andybotting.com>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: Could I (ab)use bus (struct bus_type) for virtual Broadcom bus?
Date: Thu, 14 Apr 2011 16:15:00 +0300 [thread overview]
Message-ID: <1302786900.21965.52.camel@dev.znau.edu.ua> (raw)
In-Reply-To: <BANLkTinu+Q367oqQPiUehPcbMs-SBxbwFg@mail.gmail.com>
> W dniu 14 kwietnia 2011 14:34 użytkownik Hauke Mehrtens
> <hauke@hauke-m.de> napisał:
> > On 04/14/2011 02:04 PM, Rafał Miłecki wrote:
> >> Hauke: you were proposing integrating with drivers/amba. I really
> >> expect you to comment on this, please tell us how do you see this now,
> >> when we have better overview. I took your proposal seriously, you can
> >> see the results above.
> >
> > I had no closer look at drivers/amba and this bus driver, I just saw
> > that there was a discussion about drivers/amba and this implementation
> > with no result. When the Bradcom cores are not directly connected to
> > AMBA, but are using some sort of wrapper and there are no benefits in
> > using drivers/amba, just leave it.
> >
> > As the implementation of the Braodcom AIX Bus contains some Broadcom
> > extensions and there seams to be no normal AMBA device being connected
> > to some Broadcom devices with this special interface number 3) "Broadcom
> > specific bus (bcmai)" seams to the the best approach in my opinion.
>
> Thanks for commenting.
>
> Russell: you were asking:
> > What does this do which the 'amba' bus support doesn't?
> I believe I explained it well in this thread. Do you still think about
> using amba/driver? Do you think we should use it?
>
> Arnd: I found you saying:
> > I believe the one thing we really want from this driver is the bus
> > scan code, which is not present in the amba bus implementation,
> I explained how it works, I believe scanning (EPROM in this case) it
> Broadcom specific, not really AMBA standard. How do you see it?
>
It might not Broadcom specific as EPROM core seems to be CoreLink one
core and maybe is arm-developed. But it isn't documented publicly and we
don't know yet if it is obligatory for all amba (or at least axi)
interconnects or not.
Have nice day,
George
next prev parent reply other threads:[~2011-04-14 13:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 11:28 Rafał Miłecki
2011-04-14 11:43 ` George Kashperko
2011-04-14 12:04 ` Rafał Miłecki
2011-04-14 12:34 ` Hauke Mehrtens
2011-04-14 13:07 ` Rafał Miłecki
2011-04-14 13:15 ` George Kashperko [this message]
2011-04-14 13:45 ` Rafał Miłecki
2011-04-15 18:36 ` George Kashperko
2011-04-15 19:21 ` Rafał Miłecki
2011-04-15 19:42 ` George Kashperko
2011-04-15 19:52 ` Rafał Miłecki
2011-04-15 19:56 ` Peter Stuge
2011-04-16 14:00 ` Rafał Miłecki
2011-04-16 14:13 ` Jonas Gorski
2011-04-15 19:50 ` George Kashperko
2011-04-17 17:38 ` Arnd Bergmann
2011-04-18 12:19 ` Rafał Miłecki
2011-04-18 14:19 ` Arnd Bergmann
2011-04-18 14:31 ` Rafał Miłecki
2011-04-18 15:35 ` George Kashperko
2011-04-18 15:53 ` Rafał Miłecki
2011-04-18 16:48 ` George Kashperko
2011-04-19 13:46 ` Arnd Bergmann
2011-04-19 13:58 ` Arend van Spriel
2011-04-19 14:02 ` Greg KH
2011-04-20 6:39 ` Arend van Spriel
2011-04-20 6:44 ` Arnd Bergmann
2011-04-19 14:20 ` Rafał Miłecki
2011-04-19 14:35 ` Arnd Bergmann
2011-04-20 7:16 ` Arend van Spriel
2011-04-20 7:26 ` Arnd Bergmann
2011-04-20 7:57 ` Arend van Spriel
2011-04-20 7:29 ` Rafał Miłecki
2011-05-05 12:33 ` AXI driver status => previously: " Arend van Spriel
2011-05-05 12:48 ` Rafał Miłecki
2011-05-05 12:54 ` Arend van Spriel
2011-04-14 13:03 ` 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=1302786900.21965.52.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=greg@kroah.com \
--cc=hauke@hauke-m.de \
--cc=jonas.gorski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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
all inboxes | Powered by JetHome®