From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laurentiu Tudor Date: Wed, 26 Nov 2014 14:34:37 +0200 Subject: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND In-Reply-To: References: <544A77FB.2020802@freescale.com> <54736395.2080805@freescale.com> <54744292.9070206@freescale.com> Message-ID: <5475C8DD.1040002@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 11/26/2014 10:55 AM, Joakim Tjernlund wrote: > Laurentiu Tudor wrote on 2014/11/25 09:49:22: >> >> On 11/24/2014 06:57 PM, York Sun wrote: >>> On 11/23/2014 11:30 PM, Joakim Tjernlund wrote: >>>> York Sun wrote on 2014/10/24 18:02:03: >>>>> >>>>> 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 >>>> >>>> I might have missed it, but did this go anywhere? >>>> >>> >>> No. It didn't go anywhere. Laurentiu, can you follow up? >>> >> >> Hi Jocke, York, >> >> Sorry for the late reply. I didn't noticed the thread in time. >> >> You need this patch: >> >> https://patchwork.ozlabs.org/patch/411910/ > > Great, I guess this will hit upstream any day now? > I'm thinking York will pick it up in one of the following pull requests. --- Best Regards, Laurentiu