From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Linuxppc-dev@ozlabs.org, jdl@jdl.com,
Jerry Van Baren <gvb.uboot@gmail.com>,
david@gibson.dropbear.id.au
Subject: Re: [PATCH dtc] Implement the -R option and add a -S option.
Date: Thu, 05 Apr 2007 13:10:40 -0400 [thread overview]
Message-ID: <46152D90.5070209@smiths-aerospace.com> (raw)
In-Reply-To: <20070405161113.GA28063@ld0162-tx32.am.freescale.net>
Scott Wood wrote:
> On Wed, Apr 04, 2007 at 10:04:33PM -0400, Jerry Van Baren wrote:
>> Implement the -R <number> option to add memory reserve slots.
>> Add a -S <size> option makes the blob at least this number of bytes.
>
> Wouldn't it be better to just specify the amount of extra space, instead
> of the minimum total space? That way, you only need to know what you
> intend to add, not how much is already there.
>
> -Scott
I thought briefly about this, but decided to implement a fixed size so
that someone could allocate, say, 8K of memory in their memory map
(likely flash) and know their blob would fit.
Maybe we need a little -s option to say "add -s bytes".
Jon suggested a --stats option to print out the important statistics.
That would also be a good enhancement.
gvb
next prev parent reply other threads:[~2007-04-05 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 2:04 [PATCH dtc] Implement the -R option and add a -S option Jerry Van Baren
2007-04-05 15:03 ` Jon Loeliger
2007-04-05 15:17 ` Jerry Van Baren
2007-04-05 15:17 ` [U-Boot-Users] " Jerry Van Baren
2007-04-05 16:11 ` Scott Wood
2007-04-05 17:10 ` Jerry Van Baren [this message]
2007-04-12 6:51 ` David Gibson
2007-04-14 12:58 ` Jerry Van Baren
2007-04-14 16:43 ` Jerry Van Baren
2007-04-15 0:42 ` David Gibson
2007-04-15 2:13 ` Jerry Van Baren
2007-04-15 2:22 ` David Gibson
2007-04-15 2:41 ` Jerry Van Baren
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 2:29 [PATCH: " Jerry Van Baren
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=46152D90.5070209@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=david@gibson.dropbear.id.au \
--cc=gvb.uboot@gmail.com \
--cc=jdl@jdl.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.