[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F3BC30A.4030301@monstr.eu>
Date: Wed, 15 Feb 2012 15:36:58 +0100
From: Michal Simek <monstr@...str.eu>
To: Ohad Ben-Cohen <ohad@...ery.com>
CC: LKML <linux-kernel@...r.kernel.org>,
John Williams <john.williams@...alogix.com>,
linux-arm <linux-arm-kernel@...ts.infradead.org>,
"Grosen, Mark" <mgrosen@...com>, Arnd Bergmann <arnd@...db.de>,
Grant Likely <grant.likely@...retlab.ca>,
devicetree-discuss@...ts.ozlabs.org
Subject: Re: remoteproc: Load coprocessor code to the specific main memory
location
Michal Simek wrote:
> Ohad Ben-Cohen wrote:
>> On Mon, Feb 13, 2012 at 3:20 PM, Michal Simek <monstr@...str.eu> wrote:
>>> Here is how it is achieve
>>> ret = dma_declare_coherent_memory(&zynq_freertos.dev, 0,
>>> 0, 0x10000000, DMA_MEMORY_MAP);
>>>
>>> which is fully compatible with remoteproc.
>>
>> Great, this is what we've been doing with davinci too.
>
> Cool.
>
>>
>>> Do you have any example of using it?
>>
>> What exactly are you looking for ? RTOS or Linux side ?
>
> Both side will be great. Rtos is freertos.
>
>>
>> On the Linux side, you can just make the rpmsg sample work (it's part
>> of the rpmsg patch set). For the RTOS side, feel free to just take our
>> code (it's BSD licensed and hosted on github) and adapt it to your
>> environment.
>
> You mean that server_sample and rpmsg_omx right?
> I have also found rpmsg-omx demo application.
> What I am missing is how to probe rpmsg bus.
> Do you have any working example?
>
> Communication between cpus is done through swirqs. I have test sending
> it from linux to rtos.
ok. How that rpmsg channels are created? Is it based on data sent from remoteproc?
Or based on resource table?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists