From: George Kashperko <george@znau.edu.ua>
To: Hauke Mehrtens <hauke@hauke-m.de>
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:23:30 +0300 [thread overview]
Message-ID: <1302639810.14216.57.camel@dev.znau.edu.ua> (raw)
In-Reply-To: <4DA4AC4B.90409@hauke-m.de>
> The specification for the AMBA AXI Interface is available for free
> download from ARM if you register to their website and accept their license:
> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.set.amba/index.html
> I got it from there without any problems and the license does not look
> too bad for me, by having a quick look at it. I do not know if it will
> help you in any way or if it is completely unrelated.
>
> Why is the existing support for the amba bus not extended or used in any
> way for this? It exists for some time in drivers/amba/. There already
> was a discussion about this in https://lkml.org/lkml/2011/3/30/186 , but
> with no result as I see.
Existing AMBA bus might is the proper place to publish axi master port
cores but Rafal's implementation manage those internally. Rafal
introduces separate Broadcom-specific bus intended exclusively for
Broadcom-specific devices management. Those devices share common
identification/management techniques which are completely different from
those implemented by other existant kernel buses and amba bus (at least
at it current state) as well. Might be there are good and proper ways to
extend amba bus driver to support axi as well but its a field for guys
and girls confident with closed proprietary arm docs.
Therefore IMHO the bus introduced by Rafal deserves its own driver and
name. But I'm sure that the "axi" tag isn't good one for this bus.
>
> >>>> Also can't figure out how is this implementation supposed to manage
> >>>> multicore devices.
> >>>
> >>> We have got ideas, but let's first find (wait for) such a device ;)
> >> bcm4716 usb host ? Don't really know if there are any other multicores.
> >
> > This is SoC, we do not have any problems supporting multiple cores on
> > SoCs. All cores are available at the same time, without any sliding
> > windows.
> >
>
> Hauke
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Have nice day,
George
prev parent reply other threads:[~2011-04-12 20:26 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
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 [this message]
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=1302639810.14216.57.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=hauke@hauke-m.de \
--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 \
/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