The Ten64 networking platform is a product by Traverse Technologies and they kindly provided me with a full system. It's a NXP LS1088a based platform featuring DPAA2 (FreeBSD driver development) support with 8xGE + 2xSFP+, USB3, multiple mPCIe slots, .. See their excellent documentation for all the details.
insert nice photos of the machine here
Traverse Technologies recently published a FreeBSD preview for Ten64 image.
I am just jotting down my notes regarding FreeBSD support here.
device ds1307 into the kernel or loading the module from loader seems to make things happy.sysctl debug.clock_do_io=1. Reason for this is that vfs_moutroot() is responsible to have the clock set and calls CLOCK_GETTIME() indirectly so that log files or other timestamps do not appear to go backwards (if no RTC is found it'll use the vfs root node date?). Look for the inittodr() call.sh -c 'while : ; do echo "0" > /dev/led/ten64:admin && sleep 1 && echo "1" >> /dev/led/ten64:admin && sleep 3; done' will turn the LED off for 1s and then on for 3s. Look at led(4) for more ideas like morse …
I need to go and see what else then. soctherm timeouts probably? That's WIP now. Review D35759 limits the number of sites to the values found in device-tree for the SoC as a first step. Next is to deal with the differences of the SoCs, Review D35764. commit 1 to main and commit 2 to main, commit to stable/13, commit to stable/13.
hw.temperature.core-cluster: 58.0C hw.temperature.soc: 57.0C root@ten64-01:~ # sysctl hw.temperature hw.temperature.core-cluster: 55.0C hw.temperature.soc: 55.0C
uart0: console (115131,n,8,1) - where does this odd value come from?
Here's a list of device compat strings, not disabled, with no driver attached:
1 arm,mmu-500 (no driver attached) -- iommu 8 arm,sp805-wdt (no driver attached) 1 fsl,dpaa2-console (no driver attached) -- I got code for DDB for this already 1 fsl,dpaa2-ptp (no driver attached) 1 fsl,ls1088a-ftm-alarm (no driver attached) 1 fsl,ls1088a-rcpm (no driver attached) 1 fsl,sec-v5.0 (no driver attached) 1 gpio-keys (no driver attached)
If you want to make use of link-state and media information and be able to set it for the 8 GE ports you want to follow the documentation and do the following in the U-Boot console once:
env delete gbemode saveenv reset
You do not want to do the same for sfpmode just yet until FreeBSD grows FDT/SFP support.
I am not sure what the proper method is but I ended up adjusting the U-Boot menu and added a run setup_distroboot_efi && before the run dhcp which makes sure all the bits needed for DPAA2 are loaded.