On Thu, May 04, 2023 at 09:00:22AM -0500, Andrew Davis wrote: > On 5/2/23 2:38 PM, Denys Dmytriyenko wrote: > >On Fri, Apr 28, 2023 at 10:13:26AM -0500, Andrew Davis wrote: > >>On 4/27/23 3:31 PM, Denys Dmytriyenko wrote: > >>>On Tue, Apr 25, 2023 at 12:23:40PM -0500, Andrew Davis via > >>>lists.yoctoproject.org wrote: > >>>>This will no longer build after we switch away from k3-image-gen. Remove > >>>>this version until it can be rebased on the latest U-Boot with binman > >>>>support. > >>> > >>>>For now switch current users of this over to u-boot-ti v2021.01. > >>> > >>>This comment is not very clear - aren't you also removing that here? > >> > >>Not here, I do that in the *next* patch :) > >> > >>I usually sort my patches from least to most controversial, so the first > >>3-4 can be taken stopping here without breaking as much. > >> > >>>Would it be possible to preserve at least Beagle build flows intact? Can > >>>the existing ti-sci-fw recipe that uses k3-image-gen be kept for now > >>>alongside the new one, e.g. move it to ti-sci-fw-legacy or something? > >> > >>I have found no such way :( > >> > >>All the multiconf and deploy logic expects k3-image-gen and now needs > >>moved over to the new way. Supporting both would mean forking almost > >>everything removed by this series. > > > >But on the other hand, BBAI64 and BeaglePlay only support GP and don't set > >any > >additional multiconfigs besides the main k3r5. I feel like creating a > >separate > >ti-sci-fw-bb.org with k3-image-gen might be possible. But I haven't tried > >that > >myself yet... > > > > > >>The benefit is not there IMHO since the beagle platforms should boot > >>almost exactly the same on our TI tree as the bb.org version. > >> > >>Moving forward, bb.org will also have to make this migration as > >>k3-image-gen will soon be deprecated. When they do, if we still want > >>their fork in meta-ti we can bring it back in. > > > >The issue is that it will take time for bb.org to switch over to the latest > >TI > >6.1 kernel and 2023 U-boot with binman. Moreover, they only support Debian, > >so > >don't expect timely OE recipe updates. And in all this potentially long time > >there won't be any OE support for BB platforms. But there are active OE BB > >users here and I'm trying to find a way to not throw them under the bus... > > > > This will only force them to use 2023 U-boot, which seems to boot the BB > boards > just fine already. The kernel can remain 5.10 until bb.org upgrades.
Interesting. I would have to try this combination some time soon...
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16490): https://lists.yoctoproject.org/g/meta-ti/message/16490 Mute This Topic: https://lists.yoctoproject.org/mt/98497784/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/leave/6695321/21656/1393940836/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
