They phymask comes from a hardware register read by the davinci_mdio driver, which gets passed to the linux phy libraries. The problem is that the cpsw driver gets the value from device tree, which is hardcoded to address 0. Usually the values are the same (address 0), but sometimes the phy gets registered to a different address, usually in my case address 2. You calculate the address using the phymask. If you changed the phymask than, you pointing back to address 0, so that wouldn't help you.
I rebuilt the dtb file. On Thursday, July 24, 2014 4:10:18 PM UTC-4, Loren Amelang wrote: > > On Wednesday, July 23, 2014 3:54:00 PM UTC-7, cmid...@gmail.com wrote: >> >> The davinci mdio driver should report a phymask and that value is used to >> update the device tree. >> > > Back when I had this problem I tried hard to find out where the phymask > comes from, and never succeeded. At that time people who received a phymask > of fffffffe booted successfully, those with fffffffb failed. Do you know > where the mask is found and how to change it? > > I also remove the second phy slave from the device tree. >> > > That seems like a great idea, if only to stop all the useless messages > about it never being found. Can that be done in the uEnv.txt, like when you > disable HDMI, or do you have to rebuild the device tree binary? Would > setting the phymask to ffffffff accomplish the same thing? > > Loren > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
