linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
	linuxppc-dev@ozlabs.org, jdl@jdl.com,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] Add support for binary includes.
Date: Tue, 27 May 2008 12:59:32 -0500	[thread overview]
Message-ID: <483C4C04.9020408@freescale.com> (raw)
In-Reply-To: <7BF8FE6B-8BDD-4DC3-953E-E023C38EBA87@kernel.crashing.org>

Kumar Gala wrote:
> 
> On Feb 25, 2008, at 6:39 PM, David Gibson wrote:
> 
>> On Wed, Feb 20, 2008 at 01:19:41PM -0600, Scott Wood wrote:
>>> A property's data can be populated with a file's contents
>>> as follows:
>>>
>>> node {
>>>     prop = /incbin/("path/to/data");
>>> };
>>>
>>> A subset of a file can be included by passing start and size parameters.
>>> For example, to include bytes 8 through 23:
>>>
>>> node {
>>>     prop = /incbin/("path/to/data", 8, 16);
>>> };
>>>
>>> As with /include/, non-absolute paths are looked for in the directory
>>> of the source file that includes them.

That issue was resolved, I believe.

>> Well, while I discuss the syntax with Jon, here's some comments on the
>> implementation.
> 
> have we made any progress on the syntax?

My last suggestions garnered a "I like that even less." response,
so as far as I know, we're still waiting for a good proposal here.

jdl

  reply	other threads:[~2008-05-27 18:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 19:19 [PATCH] Add support for binary includes Scott Wood
2008-02-22  5:34 ` David Gibson
2008-02-22 18:12   ` Jon Loeliger
2008-02-25  3:38     ` David Gibson
2008-02-22  6:05 ` Grant Likely
2008-02-22  8:34   ` Bartlomiej Sieka
2008-02-22  9:02   ` David Woodhouse
2008-02-22 15:50     ` Grant Likely
2008-02-22 16:08   ` Scott Wood
2008-02-22 16:24     ` Jon Loeliger
2008-02-22 16:28       ` Scott Wood
2008-02-26  0:39 ` David Gibson
2008-02-26 17:26   ` Scott Wood
2008-05-27 15:27   ` Kumar Gala
2008-05-27 17:59     ` Jon Loeliger [this message]
2008-05-28 23:58       ` David Gibson
2008-05-29  0:02         ` David Gibson
2008-05-30 18:54           ` Scott Wood
2008-06-04  4:13             ` David Gibson
2008-06-04 12:36               ` Bartlomiej Sieka
2008-06-04 14:26               ` Jon Loeliger
2008-06-05  3:11                 ` Josh Boyer
2008-06-11  1:58                 ` dtc: " David Gibson
2008-06-12 16:43                   ` Scott Wood
2008-06-13  0:01                     ` David Gibson
2008-06-13  0:46                       ` Jon Loeliger
2008-06-13  3:41                         ` David Gibson
2008-05-29 14:04         ` [PATCH] " Jon Loeliger
2008-05-30  1:34           ` David Gibson
2008-06-02 20:22             ` Jon Loeliger

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=483C4C04.9020408@freescale.com \
    --to=jdl@freescale.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=galak@kernel.crashing.org \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).