From: Michal Simek <monstr@monstr.eu>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
John Williams <john.williams@petalogix.com>
Subject: remoteproc: Load coprocessor code to the specific main memory location
Date: Tue, 24 Jan 2012 18:20:33 +0100 [thread overview]
Message-ID: <4F1EE861.4030405@monstr.eu> (raw)
Hi,
I have a question how to setup resource table to support firmware loading
to specific memory location.
I have allocated the part of ram which is at physical address 0x0
which coprocessor needs for rtos code.
Currently I am using carveout with setup size but from rproc_handle_carveout
is __dma_alloc_buffer which is remapped by __dma_alloc_remap function to any
0xffc00000 address. But IRC this could be useful for system with iommu which we don't have.
devmem entry is the same case.
Coprocessor can directly access memory of the main cpu.
Please correct me if I am wrong but the whole code is designed to use carveout
and remap it to coprocessor address space to requested memory location.
Is there any option how to handle these cases?
For example extending resource type to support direct mapping to preallocated space or so.
Thanks for your comments,
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 reply other threads:[~2012-01-24 17:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 17:20 Michal Simek [this message]
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
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=4F1EE861.4030405@monstr.eu \
--to=monstr@monstr.eu \
--cc=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ohad@wizery.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