On Thu, Jul 2, 2020 at 8:51 AM Bob Ham <[email protected]> wrote: > > Hi there, > > My BeagleBone Green has had major problems with the Ethernet phy since I > got it many years ago. There is a patch for Linux here: > > https://github.com/RobertCNelson/bb-kernel/blob/am33x-v5.3/patches/drivers/ti/cpsw/0001-cpsw-search-for-phy.patch > > I asked in #beagle on FreeNode IRC about this some months ago, after > finally getting around to building my device. Here is an abridged log, > which will save me rewriting it: > > <+rcn-ee[m]> rah: that's fixed in u-boot... it'll be going away.. > <+rcn-ee[m]> rah: here is the u-boot fix: (which is better then the > kernel fix) > https://github.com/u-boot/u-boot/blob/master/board/ti/am335x/board.c#L629-L700 > <+rcn-ee[m]> rah: thus the only reason i still carry the patch, is for > user still running old u-boot.. > <+rcn-ee[m]> Here's the commit: > https://github.com/u-boot/u-boot/commit/20c37fb1bfb9f20804645b2199699cd815a4d55c > < rah> U-Boot 2019.04-00002-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500), > Build: jenkins-github_Bootloader-Builder-128 > < rah> github seems to think that patch went into 2019.10 > < rah> is there a beaglebone image with a later u-boot image that I can > flash? > <+rcn-ee[m]> rah: special build for you: sudo > /opt/scripts/tools/developers/update_bootloader.sh --beta > <+rcn-ee[m]> rah: , there should be a new print: printf("fixing up > phy_id for %s, old: %d, new: %d\n", > < rah> rcn-ee[m]: it looks like I was wrong about the release version > though, it looks like this patch went in from v2018.11-rc1 onwards > < rah> rcn-ee[m]: I'm not seeing this printf: > https://paste.debian.net/1111765/ > <+rcn-ee[m]> rah: ugh CONFIG_OF_BOARD_SETUP, that's the fdt path, we are > still using the classic board path.. > <+rcn-ee[m]> i'll need to do some testing, the last time i tried > switching over the fdt path, it was a shit show... > <+rcn-ee[m]> atleast now, we spec a larger hole at the start of the > partition. > < rah> ok, that's all going over my head but I get that you can't sort > it out now :-) > < rah> thanks anyway > > I've been waiting patiently for months to hear more but nothing has > materialised. I've been waiting in #beagle to pounce on rcn-ee but he > has not appeared. > > > I just downloaded the latest Debian image, wrote it to the eMMC, booted > it, ran > > $ sudo /opt/scripts/tools/developers/update_bootloader.sh --beta > > and this is the resulting version: > > U-Boot 2019.04-00002-g31a8ae0206 (May 13 2020 - 09:26:17 -0500), Build: > jenkins-github_Bootloader-Builder-139 > > Which apparently still does not contain the fix: > > [ 23.440684] cpsw 4a100000.ethernet: phy > "/ocp/interconnect@4a000000/segment@0/target-module@100000/ethernet@0/mdio@1000/ethernet-phy@0" > not found on slave 0 > > > Can anyone tell me whether the fix is going to appear in u-boot?
The fix has been in u-boot for a few years. It relies on the device-tree path, we are still shipping the old "board" file path in u-boot. I've been very busy with my day job, so I haven't had any free time to re-test every board combination in u-boot to convert to a newer version. Regards, -- Robert Nelson https://rcn-ee.com/ -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhMouVY-MKGkz%2B4%3DgW-Q%2BZegWF91a6n-egDvmew2%3D3YFA%40mail.gmail.com.
