> Perfect, thanks a lot for all the answers. I guess the U-Boot output is not
> present in the kernel syslog as U-Boot loads the capes before the kernel
> starts.
There was project to support ^ a few years ago, the patches for u-boot
and the kernel never got merged..
> Quick questions on this, though:
>
> - Are there any plans to make reading the currently loaded overlays from
> userspace possible? E.g. similarly as they could be read before from the
> 'slots' file
I've started passing "uboot_detected_capes=" thru /proc/cmdline, but
this is only enabled for capes detected via an eeprom.
Yeah, stage 2 is effectively v4.14.x
During the v4.15.x merge, the bone_capemgr's infrastructure pretty
much got nuked from all the device tree overlay changes done in the
kernel.
>
> And regarding the loading of overlays:
>
> - What is the difference between the uboot_overlay_addr{0..7} and the
> dtb_overlay options in /boot/uEnv.txt? It seems they all can be used to
> specify a custom overlay to load on top of the universal cape overlay?
Address 0...3 are directly tied to the 4 i2c at24 eeprom address in
the Cape Spec.
Address 4...7 are me being lazy on not coming up a with a new variable name..
dtb_overlay is a remnant from when i first started testing U-Boot
overlays. Since i posted, "try this with dtb_overlay=" on a public
forum, i have no plans to remove it.
> - To be clear, when you say 'really only used with the "v4.4.x-ti" kernel'
> do you mean only with that particular kernel, or "v4.4.x-ti and later"? I'm
> just trying to understand which cape I should best use and which procedure
> (UIO vs. rproc) I should learn to start using the PRUSS.
in v4.4.x-ti, it's possible to enable "either" UIO or rproc, via just
tweaking the device tree.
In v4.9.x-ti, TI's rproc changes broke the device tree node enough
where i haven't spent enough time getting UIO to work.
>
> I also just learnt recently that there seems to be a "TI kernel" and a "Bone
> kernel". If I understand it correctly, the "TI kernel" is shipped by default
> on the Debian images and has TI patches, whereas the "Bone kernel" is
> effectively the mainline kernel.
>
> - Is this correct?
TI Kernel:
Mainline +
ti.com patches + Our Patchset
Bone Kernel:
Mainline + Our Patchset
> - If so, what are their main differences?
The biggest diff:
TI Kernel: (targeting am335x and am57xx devices)
CONFIG_SMP=y
Bone Kernel: (targeting am335x devices)
CONFIG_THUMB2_KERNEL=y
> - Are they both maintained, and where is each repo?
https://github.com/RobertCNelson/ti-linux-kernel-dev
https://github.com/RobertCNelson/bb-kernel