linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/8] drivers: add generic remoteproc framework
Date: Mon, 27 Jun 2011 17:35:49 -0600	[thread overview]
Message-ID: <BANLkTi=MDSuiGb64Se1T7zCWG6syxXbhTg@mail.gmail.com> (raw)
In-Reply-To: <20110627232903.GB7736@n2100.arm.linux.org.uk>

On Mon, Jun 27, 2011 at 5:29 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Mon, Jun 27, 2011 at 02:49:58PM -0600, Grant Likely wrote:
>> > +struct {
>> > + ? ? ?char magic[4] = { 'R', 'P', 'R', 'C' };
>> > + ? ? ?u32 version;
>> > + ? ? ?u32 header_len;
>> > + ? ? ?char header[...] = { header_len bytes of unformatted, textual header };
>> > + ? ? ?struct section {
>> > + ? ? ? ? ?u32 type;
>> > + ? ? ? ? ?u64 da;
>> > + ? ? ? ? ?u32 len;
>> > + ? ? ? ? ?u8 content[...] = { len bytes of binary data };
>> > + ? ? ?} [ no limit on number of sections ];
>> > +} __packed;
>>
>> Other have commented on the image format, so I'll skip this bit other
>> than saying that I agree it would be great to have a common format.
>
> (Don't have the original message to reply to...)
>
> Do we really want to end up with header being 5 bytes, header_len set
> as 5, and having to load/store all this data using byte loads/stores ?
>
> If we don't want that, then I suggest we get rid of the packed attribute,
> and require stuff to be naturally aligned.
>
> First issue is that struct section could be much better layed out:
>
> struct section {
> ? ? ? ?u32 type;
> ? ? ? ?u32 len;
> ? ? ? ?u64 da;
> ? ? ? ?u8 content[];
> };
>
> and require sizeof(struct section) % sizeof(u64) == 0 - iow, to find
> the next section, round len up to sizeof(u64). ?Ditto for the header.

Hopefully this will all be moot since it has been proposed to use elf
images directly.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2011-06-27 23:35 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21  7:18 [RFC 0/8] Introducing a generic AMP/IPC framework Ohad Ben-Cohen
     [not found] ` <BANLkTimn-THKipuQVHLA9i3QSoO5RTqMtA@mail.gmail.com>
2011-06-21  9:30   ` Ohad Ben-Cohen
2011-06-21 14:20 ` Arnd Bergmann
2011-06-21 15:54   ` Grant Likely
2011-06-22 11:41   ` Ohad Ben-Cohen
2011-06-22 13:05     ` Arnd Bergmann
2011-06-22 13:09       ` Ohad Ben-Cohen
2011-06-23 12:23 ` Michael Williamson
2011-06-23 16:27   ` Grosen, Mark
2011-06-23 18:46     ` Arnd Bergmann
2011-06-24  4:32       ` Grosen, Mark
     [not found] ` <1308640714-17961-6-git-send-email-ohad@wizery.com>
2011-06-23 15:27   ` [RFC 5/8] remoteproc: add davinci implementation Sergei Shtylyov
2011-06-24  4:25     ` Grosen, Mark
2011-06-24 15:13       ` Sergei Shtylyov
2011-06-24 15:43         ` Nori, Sekhar
2011-06-27 18:31           ` Grosen, Mark
2011-07-05  5:29             ` Nori, Sekhar
2011-07-05 16:54               ` Grosen, Mark
2011-07-05  5:34             ` Nori, Sekhar
2011-07-05 16:54               ` Grosen, Mark
2011-07-06  4:36                 ` Nori, Sekhar
2011-06-27 18:20         ` Grosen, Mark
2011-06-28  9:36           ` Nori, Sekhar
2011-06-24 20:16 ` [RFC 0/8] Introducing a generic AMP/IPC framework Stephen Boyd
2011-06-26  1:11   ` Ohad Ben-Cohen
2011-06-26  1:17     ` Brian Swetland
2011-06-27 21:22     ` Grosen, Mark
2011-06-28 11:26       ` Ohad Ben-Cohen
2011-06-28 11:36         ` Brian Swetland
     [not found] ` <1308640714-17961-2-git-send-email-ohad@wizery.com>
2011-06-22 17:55   ` [RFC 1/8] drivers: add generic remoteproc framework Randy Dunlap
2011-06-22 19:11     ` Ohad Ben-Cohen
2011-06-27 20:49   ` Grant Likely
2011-06-27 21:52     ` Grosen, Mark
2011-06-27 22:24       ` Grant Likely
2011-06-27 23:54         ` Grosen, Mark
2011-06-27 23:29     ` Russell King - ARM Linux
2011-06-27 23:35       ` Grant Likely [this message]
2011-06-28 21:55       ` Ohad Ben-Cohen
2011-06-28 21:41     ` Ohad Ben-Cohen
     [not found] ` <1308640714-17961-3-git-send-email-ohad@wizery.com>
2011-06-22 10:05   ` [RFC 2/8] remoteproc: add omap implementation Will Newton
2011-06-22 10:50     ` Ohad Ben-Cohen
2011-06-27 21:00   ` Grant Likely
2011-06-29 15:04     ` Ohad Ben-Cohen
2011-06-29 15:31       ` Grant Likely
     [not found] ` <1308640714-17961-8-git-send-email-ohad@wizery.com>
2011-06-22  2:42   ` [RFC 7/8] drivers: introduce rpmsg, a remote-processor messaging bus Rusty Russell
2011-06-22  3:11     ` Sasha Levin
2011-06-22 10:46     ` Ohad Ben-Cohen
2011-09-14 18:38       ` Ohad Ben-Cohen
2011-09-15  0:12         ` Rusty Russell
2011-09-15 14:56           ` Ohad Ben-Cohen
2011-06-27 22:21   ` Grant Likely
2011-06-28 22:46     ` Ohad Ben-Cohen
2011-06-28 22:51       ` Grant Likely
2011-06-28 23:00         ` Ohad Ben-Cohen
2011-06-29 15:43           ` Grant Likely
2011-07-01 15:13             ` Ohad Ben-Cohen
2011-06-28 23:44   ` Randy Dunlap
2011-06-29  6:30     ` Ohad Ben-Cohen
2011-06-29 11:59       ` Arnd Bergmann
2011-06-29 12:29         ` Ohad Ben-Cohen
2011-07-18 22:07   ` Pavel Machek
2011-07-19  5:38     ` Ohad Ben-Cohen
     [not found] ` <1308640714-17961-7-git-send-email-ohad@wizery.com>
2011-06-28 10:18   ` [RFC 6/8] davinci: da850: add remoteproc dsp device Sergei Shtylyov

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='BANLkTi=MDSuiGb64Se1T7zCWG6syxXbhTg@mail.gmail.com' \
    --to=grant.likely@secretlab.ca \
    --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).