linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Milton Miller <miltonm@bga.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: hollisb@us.ibm.com, pantelis@embeddedalley.com,
	xen-ppc-devel@lists.xensource.com, linuxppc-dev@ozlabs.org,
	linuxppc-embedded@ozlabs.org
Subject: Re: [RFC] consolidated libdt proposal
Date: Thu, 10 Aug 2006 23:55:32 -0500	[thread overview]
Message-ID: <a90773d560ff8b4efc68c2de3c3bf7d5@bga.com> (raw)
In-Reply-To: <20060810185514.GA12848@mag.az.mvista.com>

On Aug 10, 2006, at 1:55 PM, Mark A. Greer wrote:
> On Thu, Aug 10, 2006 at 11:51:30AM -0500, Milton Miller wrote:
>> On Tue Aug  8 2006 01:04:08 PM CDT, Mark A. Greer wrote:
>>> If we're going to allow cmdline editing in the bootwrapper, we would
>>> need to extend the size of a property.
...
>> We already have replace the command line merged (it's why my patches
>> don't apply).
> That's different.
...

Yes, but it still requires changing the size or inserting a
property, which is the real requirement we were discussing.

Yes, editing at command line would require an input function.

milton

  reply	other threads:[~2006-08-11  4:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10 16:51 [RFC] consolidated libdt proposal Milton Miller
2006-08-10 18:55 ` Mark A. Greer
2006-08-11  4:55   ` Milton Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-19 23:05 [PATCH 3/6] bootwrapper: Add device tree ops for flattened device tree Mark A. Greer
2006-08-07  0:38 ` Hollis Blanchard
2006-08-07 21:58   ` [RFC] consolidated libdt proposal Hollis Blanchard
2006-08-08  5:37     ` Haren Myneni
2006-08-08  9:34       ` Pantelis Antoniou
2006-08-09  3:19         ` Haren Myneni
2006-08-08 18:04     ` Mark A. Greer
2006-08-08 18:25       ` Hollis Blanchard
2006-08-08 18:51         ` Mark A. Greer
2006-08-08 18:46     ` Matthew McClintock
2006-08-08 19:12       ` Matthew McClintock
2006-08-11 19:33         ` 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=a90773d560ff8b4efc68c2de3c3bf7d5@bga.com \
    --to=miltonm@bga.com \
    --cc=hollisb@us.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mgreer@mvista.com \
    --cc=pantelis@embeddedalley.com \
    --cc=xen-ppc-devel@lists.xensource.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).