2011/2/15 Blanchard, Hollis :
> OpenMCAPI (http://openmcapi.org) implements the MCAPI specification,
> which is a simple application-level communication API that uses shared
> memory. The API could be layered over any protocol, but was more or less
> designed for simple shared-memory systems, e.g.
On 02/15/2011 10:22 PM, Hiroshi DOYU wrote:
> From: "ext Blanchard, Hollis"
> Subject: Re: [RFC] Inter-processor Mailboxes Drivers
> Date: Tue, 15 Feb 2011 15:38:25 -0800
>
>> On 02/15/2011 01:58 PM, Meador Inge wrote:
>>> On 02/14/2011 04:01 AM, Jamie Iles w
From: "ext Blanchard, Hollis"
Subject: Re: [RFC] Inter-processor Mailboxes Drivers
Date: Tue, 15 Feb 2011 15:38:25 -0800
> On 02/15/2011 01:58 PM, Meador Inge wrote:
>> On 02/14/2011 04:01 AM, Jamie Iles wrote:
>>> On Fri, Feb 11, 2011 at 03:19:51PM -0600, Me
On 02/15/2011 01:58 PM, Meador Inge wrote:
> On 02/14/2011 04:01 AM, Jamie Iles wrote:
>> On Fri, Feb 11, 2011 at 03:19:51PM -0600, Meador Inge wrote:
>>> 1. Hardware specific bits somewhere under '.../arch/*'. Drivers
>>> for the MPIC message registers on Power and OMAP4 mailboxes,
On 02/14/2011 04:01 AM, Jamie Iles wrote:
On Fri, Feb 11, 2011 at 03:19:51PM -0600, Meador Inge wrote:
1. Hardware specific bits somewhere under '.../arch/*'. Drivers
for the MPIC message registers on Power and OMAP4 mailboxes, for
example.
2. A higher level driver und
On 02/13/2011 01:24 PM, Linus Walleij wrote:
>> > 3. Userspace interfaces for accessing the mailboxes. A
>> > '/dev/mailbox1', '/dev/mailbox2', etc... mapping, for example.
> What kind of business does userspace have with directly using
> mailboxes? Enlighten me so I get it... in our
On Mon, Feb 14, 2011 at 12:03:59PM +0200, Ohad Ben-Cohen wrote:
> On Mon, Feb 14, 2011 at 12:01 PM, Jamie Iles wrote:
> > On Fri, Feb 11, 2011 at 03:19:51PM -0600, Meador Inge wrote:
> >> 1. Hardware specific bits somewhere under '.../arch/*'. Drivers
> >> for the MPIC message register
On Mon, Feb 14, 2011 at 12:01 PM, Jamie Iles wrote:
> On Fri, Feb 11, 2011 at 03:19:51PM -0600, Meador Inge wrote:
>> 1. Hardware specific bits somewhere under '.../arch/*'. Drivers
>> for the MPIC message registers on Power and OMAP4 mailboxes, for
>> example.
>> 2. A highe
On Fri, Feb 11, 2011 at 03:19:51PM -0600, Meador Inge wrote:
> 1. Hardware specific bits somewhere under '.../arch/*'. Drivers
>for the MPIC message registers on Power and OMAP4 mailboxes, for
>example.
> 2. A higher level driver under '.../drivers/mailbox/*'. That the
>
From: Hiroshi DOYU
Subject: Re: [RFC] Inter-processor Mailboxes Drivers
Date: Mon, 14 Feb 2011 10:55:53 +0200 (EET)
> From: ext Linus Walleij
> Subject: Re: [RFC] Inter-processor Mailboxes Drivers
> Date: Mon, 14 Feb 2011 09:39:32 +0100
>
>> On Mon, Feb 14, 2011 at 8:32 AM, H
On Mon, Feb 14, 2011 at 9:55 AM, Hiroshi DOYU wrote:
> Does db5500 use IOMMU for mapping shared memories?
Nope, it's a fixed physical allocation from the modem side
of the world.
Yours,
Linus Walleij
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.oz
From: ext Linus Walleij
Subject: Re: [RFC] Inter-processor Mailboxes Drivers
Date: Mon, 14 Feb 2011 09:39:32 +0100
> On Mon, Feb 14, 2011 at 8:32 AM, Hiroshi DOYU wrote:
>
>> OMAP mailbox is the interrupt driven 32bit unit H/W FIFO to other
>> cores.
>
> How is it u
Hi Meador,
From: ext Meador Inge
Subject: [RFC] Inter-processor Mailboxes Drivers
Date: Fri, 11 Feb 2011 15:19:51 -0600
> Hi All,
>
> I am currently working on building AMP systems using OpenMCAPI
> (https://bitbucket.org/hollisb/openmcapi/wiki/Home) as the
> inter-processor communication mecha
On Mon, Feb 14, 2011 at 8:32 AM, Hiroshi DOYU wrote:
> OMAP mailbox is the interrupt driven 32bit unit H/W FIFO to other
> cores.
How is it used? Is it a low-traffic (like single 32bit words etc) signal
control-path link while the actual high-throughput data-path is done
with shared memory? (Tha
From: ext Linus Walleij
Subject: Re: [RFC] Inter-processor Mailboxes Drivers
Date: Sun, 13 Feb 2011 22:16:12 +0100
> 2011/2/12 Sundar :
>
>> At least I would like this; I wanted to generalize such mailbox IPCs
>> right from the day when I was working on one, but coudnt real
2011/2/11 Meador Inge :
> This would entail the traditional
> generic/specific driver split:
>
> 1. Hardware specific bits somewhere under '.../arch/*'. Drivers
> for the MPIC message registers on Power and OMAP4 mailboxes, for
> example.
Having any drivers under arch/* is no good
2011/2/12 Sundar :
> At least I would like this; I wanted to generalize such mailbox IPCs
> right from the day when I was working on one, but coudnt really
> work on that.
>
>> 2. Does something like this already exist?
>
> Not generic as you say; but apart from the OMAP platforms,
> you could
Hi,
On Sat, Feb 12, 2011 at 2:49 AM, Meador Inge wrote:
>
> 1. Hardware specific bits somewhere under '.../arch/*'. Drivers
> for the MPIC message registers on Power and OMAP4 mailboxes, for
> example.
Yes; this can help.
> 2. A higher level driver under '.../drivers/mailbox/
18 matches
Mail list logo
