All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/7] libfdt: Update to resync with dtc/libfdt
Date: Wed, 20 Aug 2008 21:45:04 -0400	[thread overview]
Message-ID: <48ACC8A0.4090903@gmail.com> (raw)
In-Reply-To: <1219199438-21716-1-git-send-email-gvb.uboot@gmail.com>

gvb.uboot at gmail.com wrote:
> The following changesets resynchronize u-boot with the master libfdt.
> 
> Best regards,
> gvb

First results using aliases with David's libfdt improvements...

These are the aliases:

=> fdt p /aliases
aliases {
         ethernet0 = "/qe at e0100000/ucc at 2000";
         ethernet1 = "/qe at e0100000/ucc at 3000";
         serial0 = "/soc8360 at e0000000/serial at 4500";
         serial1 = "/soc8360 at e0000000/serial at 4600";
         pci0 = "/pci at e0008500";
};

Dereference an alias by not using the '/' prefix per OF conventions:

=> fdt print ethernet0
ucc at 2000 {
         device_type = "network";
         compatible = "ucc_geth";
         cell-index = <0x1>;
         reg = <0x2000 0x200>;
         interrupts = <0x20>;
         interrupt-parent = <0x2>;
         local-mac-address = [00 00 00 00 00 00];
         rx-clock-name = "none";
         tx-clock-name = "clk9";
         phy-handle = <0x3>;
         phy-connection-type = "rgmii-id";
         pio-handle = <0x4>;
};

Whooo-heeee!

Dereference the ethernet0 alias and print a property:

=> fdt print ethernet0/phy-connection-type
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND

Doh doh doh!  :-)  Pretty close, though.  I'll have to dig into this a 
bit more to see why the alias expansion doesn't seem to work with 
properties, check how it behaves with nested nodes (maybe).

I've rebased u-boot-fdt against u-boot and pushed David's (and other's) 
libfdt improvements to u-boot-fdt.  This is *NOT* ready to be merged 
into the mainline, but I've made it available in case others want to 
play with it.

Warning: I will be rebasing u-boot-fdt as Wolfgang merges more changes 
into the mainline.  I have not seen problems with rebasing, but YMMV.

Best regards,
gvb

  parent reply	other threads:[~2008-08-21  1:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20  2:30 [U-Boot] [PATCH 0/7] libfdt: Update to resync with dtc/libfdt gvb.uboot at gmail.com
2008-08-20  2:30 ` [U-Boot] [PATCH 1/7] dtc: Enable and fix -Wpointer-arith warnings gvb.uboot at gmail.com
2008-08-20  2:30 ` [U-Boot] [PATCH 2/7] dtc: Enable and fix -Wcast-qual warnings gvb.uboot at gmail.com
2008-08-20  2:30 ` [U-Boot] [PATCH 3/7] libfdt: Increase namespace-pollution paranoia gvb.uboot at gmail.com
2008-08-20  2:30 ` [U-Boot] [PATCH 4/7] libfdt: Improve documentation in libfdt.h gvb.uboot at gmail.com
2008-08-20  2:30 ` [U-Boot] [PATCH 5/7] libfdt: Forgot one function when cleaning the namespace gvb.uboot at gmail.com
2008-08-20  2:30 ` [U-Boot] [PATCH 6/7] libfdt: Implement fdt_get_property_namelen() and fdt_getprop_namelen() gvb.uboot at gmail.com
2008-08-20  2:30 ` [U-Boot] [PATCH 7/7] libfdt: Add support for using aliases in fdt_path_offset() gvb.uboot at gmail.com
2008-08-21  1:45 ` Jerry Van Baren [this message]
2008-08-21  1:51   ` [U-Boot] [PATCH 0/7] libfdt: Update to resync with dtc/libfdt David Gibson
2008-08-21  2:08     ` 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=48ACC8A0.4090903@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 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.