beagle-ai: needs `next` manifest and manifest fix

[leonheldattoradex]

To build with MACHINE="beagle-ai" we need to use the next manifest:

repo init -u git://git.toradex.com/toradex-manifest.git -b scarthgap-7.x.y -m common-torizon/ti/default.xml

And fix this ref:

leon@scheie:~/common-torizon$ ag --hidden "refs/tags/2.8"
.repo/manifests/common-torizon/ti/next.xml
10:  <project name="bitbake" path="sources/bitbake" remote="oe" revision="refs/tags/2.8"/>

to

leon@scheie:~/common-torizon$ ag --hidden "=2.8"
.repo/manifests/common-torizon/ti/next.xml
10:  <project name="bitbake" path="sources/bitbake" remote="oe" revision="2.8"/>

I'm documenting this in case anyone wants to build this image. I suppose these changes will eventually land in the default.xml manifest.

[EdTheBearded]

This is "not an issue". We know we're missing a bump in our common manifests so that not only BeagleY but AM62L and P can build. We decided to hold this bump until past the release, because of the meta-ti kernel issues (namely the bump from 6.6 to 6.12).

[leonheldattoradex]

Sure, thanks for the explanation. Can you close this ticket when the bumps are done? I think having this issue is worthwhile until following the README doesn't generate a working build.