From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND
Date: Fri, 24 Oct 2014 09:02:03 -0700 [thread overview]
Message-ID: <544A77FB.2020802@freescale.com> (raw)
In-Reply-To: <OF5ACB7C6F.ED74126E-ONC1257D7B.0055C4CC-C1257D7B.00560A06@transmode.se>
On 10/24/2014 08:39 AM, Joakim Tjernlund wrote:
> Booting my t1042 I get:
> Loading Ramdisk to 2e639000, end 2ffffcc4 ... OK
> Loading Device Tree to 03fe4000, end 03fffd45 ... OK
> WARNING Could not get liodn of node /pcie at ffe240000: FDT_ERR_NOTFOUND
> WARNING Could not get liodn of node /pcie at ffe250000: FDT_ERR_NOTFOUND
> WARNING Could not get liodn of node /pcie at ffe240000: FDT_ERR_NOTFOUND
> WARNING Could not get liodn of node /pcie at ffe250000: FDT_ERR_NOTFOUND
> ....
>
> This apperas to come from
> base_liodn = fdt_getprop(fdt, off, "fsl,liodn", &rc);
> if (!base_liodn) {
> char path[64];
>
> if (fdt_get_path(fdt, off, path, sizeof(path)) <
> 0)
> strcpy(path, "(unknown)");
> printf("WARNING Could not get liodn of node %s:
> %s\n",
> path, fdt_strerror(rc));
> continue;
> }
>
> but I cannot find out what what this property should be. Anyone?
>
Laurentiu,
Can you take a look?
York
next prev parent reply other threads:[~2014-10-24 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 15:39 [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND Joakim Tjernlund
2014-10-24 16:02 ` York Sun [this message]
2014-11-24 7:30 ` Joakim Tjernlund
2014-11-24 16:57 ` York Sun
2014-11-25 8:49 ` Laurentiu Tudor
2014-11-26 8:55 ` Joakim Tjernlund
2014-11-26 12:34 ` Laurentiu Tudor
2014-12-01 17:26 ` York Sun
2014-12-01 18:31 ` Joakim Tjernlund
2014-12-01 18:43 ` York Sun
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=544A77FB.2020802@freescale.com \
--to=yorksun@freescale.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