On Thu, Sep 7, 2017 at 3:36 AM, Sekhar Nori <nsekhar@xxxxxx> wrote: > On Thursday 07 September 2017 03:11 AM, Adam Ford wrote: >> On Mon, Sep 4, 2017 at 11:42 PM, Sekhar Nori <nsekhar@xxxxxx> wrote: >>> Hi Adam, >>> >>> On Wednesday 30 August 2017 11:08 AM, Sekhar Nori wrote: >>>>> I wonder if U-Boot isn't pushing something to Linux because it doesn't >>>>> appear to be running some of the da850 specific code even when I run >>>>> linux-next. Can you tell me what verision of U-Boot you're using? >>>>> Other than using davinci_all_defconfig, did you change the >>>>> configuration at all? >>> >>>> I am using U-Boot 2017.01. Yes, the kernel was built using >>>> davinci_all_defconfig and no other config change. Before booting kernel, >>>> can you confirm that ethaddr is set in U-Boot environment? This is what >>>> fdt_fixup_ethernet() reads to fixup the FDT before boot. >>>> >>>> Here is my complete boot log with environment variable dump. >>>> >>>> http://pastebin.ubuntu.com/25430265/ >>> >>> Were you able to get rid of the random mac address problem? >> >> Not yet. I haven't been able to rebuild Arago using TI's instructions >> on the Wiki. I am not sure if it's a dependency issue or something >> else. When I run Linux 4.13 using Buildroot as the rootfs, it does >> not appear to run da850_evm_m25p80_notify_add(). I am going to >> investigate whether or not da850_evm_init() is getting called. I was >> wondering if you had some insight as to what calls that function? It >> looks like it's defined as part of MACHINE_START(DAVINCI_DA850_EVM, >> "DaVinci DA850/OMAP-L138/AM18x EVM"), but I don't know how it gets >> called. > > These functions are called only when booting using the legacy board file > method. From your logs before, you are booting using device tree. So > these functions are irrelevant. Ok. That makes a lot more sense now. I was really confused why the functions were not getting called. > Can you check if the mac address has been populated in the device-tree > by dumping it from /proc/device-tree/.../local-mac-address? That will > tell us if U-Boot is updating the mac address or not. It does not appear to getting called. # hexdump ./soc@1c00000/ethernet@220000/local-mac-address 0000000 0000 0000 0000 0000006 # I'll work on something that pulls in the MAC address then inserts it into the device tree like the recommendation that Tony made. Thanks for all your help. adam > > Thanks, > Sekhar -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
