public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] libfdt: Add support for appending the values to a existing property
Date: Sat, 15 Sep 2012 11:19:18 -0400	[thread overview]
Message-ID: <50549C76.4020804@gmail.com> (raw)
In-Reply-To: <6AE080B68D46FC4BA2D2769E68D765B708059FF7@039-SN2MPN1-023.039d.mgd.msft.net>

On 09/15/2012 11:00 AM, Tabi Timur-B04825 wrote:
> On Sat, Sep 15, 2012 at 9:36 AM, Jerry Van Baren <gvb.uboot@gmail.com> wrote:
> 
>> Queued up 2 of 2 patches to the u-boot-fdt "next" branch.  I'll issue a
>> pull request when the merge window opens.
> 
> I thought libfdt patches were suppose to go to dtc.git?

That is where they came from.  Since the u-boot libfdt is a subset of
the whole dtc.git repository (just the libfdt part), I've been cherry
picking only the libfdt/* patches (with the help of others).

I see David has another patch for the libfdt library that I probably
should pick up so that we stay in sync (18 lines of code by counting
semicolons).

commit be6026838e45b67800ac803f4ad8cca3cde57d6d
Author: David Gibson <david@gibson.dropbear.id.au>
Date:   Fri Jun 1 14:12:38 2012 +1000

    libfdt: Add helper function to create a trivial, empty tree

    The libfdt read/write functions are now usable enough that it's become a
    moderately common pattern to use them to build and manipulate a device
    tree from scratch.  For example, we do so ourself in our rw_tree1
testcase,
    and qemu is starting to use this model when building device trees
for some
    targets such as e500.

    However, the read/write functions require some sort of valid tree to
begin
    with, so this necessitates either having a trivial canned dtb to
begin with
    or, more commonly, creating an empty tree using the serial-write
functions
    first.

    This patch adds a helper function which uses the serial-write
functions to
    create a trivial, empty but complete and valid tree in a supplied
buffer,
    ready for manipulation with the read/write functions.

    Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

  reply	other threads:[~2012-09-15 15:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28  0:38 [U-Boot] [PATCH 1/2] libfdt: Add support for appending the values to a existing property Kim Phillips
2012-08-28  0:39 ` [U-Boot] [PATCH 2/2] libfdt: Add helpers for 64-bit integer properties Kim Phillips
     [not found] ` <20120912190843.fce4abe4031e3bf1c3f29c78@freescale.com>
2012-09-13  1:43   ` [U-Boot] [PATCH 1/2] libfdt: Add support for appending the values to a existing property Jerry Van Baren
2012-09-15 14:36 ` Jerry Van Baren
2012-09-15 15:00   ` Tabi Timur-B04825
2012-09-15 15:19     ` Jerry Van Baren [this message]
2012-11-09  1:41   ` Kim Phillips
2012-11-09  1:48     ` Simon Glass
2012-11-13  2:41     ` Jerry Van Baren
2012-11-13 21:02       ` Kim Phillips

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=50549C76.4020804@gmail.com \
    --to=gvb.uboot@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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