From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: remoteproc: Load coprocessor code to the specific main memory location
Date: Wed, 15 Feb 2012 15:36:58 +0100 [thread overview]
Message-ID: <4F3BC30A.4030301@monstr.eu> (raw)
In-Reply-To: <4F3BA962.9040109@monstr.eu>
Michal Simek wrote:
> Ohad Ben-Cohen wrote:
>> On Mon, Feb 13, 2012 at 3:20 PM, Michal Simek <monstr@monstr.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
next prev parent reply other threads:[~2012-02-15 14:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F1EE861.4030405@monstr.eu>
2012-01-25 11:42 ` remoteproc: Load coprocessor code to the specific main memory location Ohad Ben-Cohen
2012-01-25 12:41 ` Michal Simek
2012-01-25 13:45 ` Ohad Ben-Cohen
2012-01-25 14:19 ` Michal Simek
2012-01-25 16:24 ` Ohad Ben-Cohen
2012-01-26 10:44 ` Michal Simek
2012-01-27 10:06 ` Michal Simek
2012-01-27 11:38 ` Ohad Ben-Cohen
2012-02-13 14:20 ` Michal Simek
2012-02-14 16:28 ` Ohad Ben-Cohen
2012-02-15 12:47 ` Michal Simek
2012-02-15 14:36 ` Michal Simek [this message]
2012-02-16 9:12 ` Michal Simek
2012-02-16 11:28 ` Ohad Ben-Cohen
2012-02-16 13:07 ` Michal Simek
2012-02-16 13:22 ` Michal Simek
2012-02-16 17:34 ` Ohad Ben-Cohen
[not found] ` <CAHTX3dJ4PruKO-wJLJU8W0boHFL0f6eoF+QNaoNjm5hu26YEow@mail.gmail.com>
2012-02-17 1:55 ` Ohad Ben-Cohen
2012-02-20 14:22 ` Michal Simek
2012-02-20 20:11 ` Ohad Ben-Cohen
2012-02-22 12:10 ` Michal Simek
2012-02-22 12:59 ` Ohad Ben-Cohen
2012-03-06 15:22 ` Michal Simek
2012-03-06 16:26 ` Ohad Ben-Cohen
2012-02-16 17:27 ` Ohad Ben-Cohen
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=4F3BC30A.4030301@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-arm-kernel@lists.infradead.org \
/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).