robertcnelson / linux-stable-rcn-ee Goto Github PK

the kernel package does not include am335x-sancloud-bbe-uboot-univ.dtb and am335x-sancloud-bbe-uboot.dtb.
(the corresponding files for the more generic bbb/bbb-wireless's are present, ie. am335x-boneblack-uboot-univ.dtb, am335x-boneblack-uboot.dtb)

without am335x-sancloud-bbe-uboot-univ.dtb u-boot (at least all the 2019 versions that i've been looking at) fails to load any overlay for universal cape support if and only if you have any uboot_overlay_addrN in your uEnv.txt. if you have no
uboot_overlay_addr lines then u-boot correctly falls back to loading one of the univ-bbb-whatever.dtbo files.
(reason for this misbehaviour: uboot_overlay_addrN things are loaded using the capeloadoverlay function, which sets
cape_uboot which deeply inside uname_boot mistriggers the logic for external capes, prints "uboot_overlays: cape universal disabled, external cape enabled or detected" and disables looking for univ-bbb-whatever.)

i'd say the root cause is that these files aren't included, because on a bbb or a bbb-wireless with the same kernel package, uboot and uEnv.txt it loads a few addon overlays and enables cape universal without problems.

I have a Beaglebone black running Linux beaglebone 3.8.13-bone79 #1 SMP Tue Oct 13 20:44:55 UTC 2015 armv7l GNU/Linux
Can I use the 3.8.13 tag from this repository to build kernel modules for my board or will they be incompatible?

On tag 4.14.108-ti-xenomai-r127, i use custom kernel configuration and i get this compile error :

CC drivers/pci/dwc/pcie-designware-host.o
drivers/pci/dwc/pcie-designware-host.c: In function ‘dw_pcie_host_init’:
drivers/pci/dwc/pcie-designware-host.c:408:10: error: too many arguments to function ‘pp->ops->msi_host_init’
408 | ret = pp->ops->msi_host_init(pp, &dw_pcie_msi_chip);
| ^~
make[2]: *** [scripts/Makefile.build:327: drivers/pci/dwc/pcie-designware-host.o] Error 1
make[1]: *** [scripts/Makefile.build:585: drivers/pci/dwc] Error 2
make: *** [Makefile:1039: drivers] Error 2

There does not seem to be a device tree from the bealgebone wireless that allow for use of the audio pins (e.g. P9_31). I need them for the pru and / or gpio

Hello,

I've a BeagleBone AI running binary 4.19.94-ti-rt-r36 "focal" with success. But I experienced some issues with remoteproc for c66x DSP cores and the driver lacks some useful debug messages I've added.
Because of realtime Ethernet constraints, I cannot upgrade to a more up-to-date revision (4.19.94-ti-rt-r68 does not meet timing constraints).

I'd like to rebuild the 4.19.94-ti-rt-r36 kernel for beaglebone AI with these few patches applied.

I ran the following commands on a copy of the tag 4.19.94-ti-rt-r36 from this repo :
"copy /boot/config to .config"
$ make oldconfig
"modify Makefile in oder to add "-debug" suffix"
"modify source files"
$ make
--> everything was fine (compiled by BBAI in a couple of hours)
$ sudo make modules_install
--> everything was fine
"sudo cp bzImage to /boot/vmlinuz-4.19.94-r36-debug"
"sudo cp System.map to /boot/..."
"sudo cp .config to /boot/..."
"modify /boot/uEnv.txt to use new kernel"

Unfortunately kernel does not boot... Not sure what I'm missing here... Are there any difference between this tag and the binary rcn-ee package ? Should I reinstall the dtbs over the existing ones (make dtbs_install ?). Any other step to get the same kernel as the one available in rcn-ee binary packages ?

Thanks for your help,

• Florent