On Wed, Oct 9, 2019 at 3:12 AM Tarmo Kuuse <[email protected]> wrote: > > Hi Robert, > > On 08.10.19 17:34, Robert Nelson wrote: > >> Thank you. That's good to know. > >> > >> A kernel upgrade on our devices requires using the dtb-rebuilder to get > >> our modified base DTB-s (am335x-boneblack.dtb). For the 4.19-ti series the > >> most recent supported kernel version in your repo appears to be > >> "4.19.25-ti-r17" from 6 months ago (when looking at commit comments). > >> > >> The beagleboard repo doesn't list any kernel versions anywhere. When using > >> this repo, how would I recognize which 4.19-ti kernel version I'd be able > >> to apply my modified DTB-s to? > > > > That shouldn't be an issue going forward.. (easy to say as 4.19-ti has > > quieted down, so that might backfire with 5.4-ti) > > > > With the old dtb-rebuilder repo, we'd always push a dts patch to the > > kernel build script first, tag it and then manually copy it back to > > the dtb-rebuilder. So things would get out of sync if i didn't copy > > it over.. > > > > With the new repo, everything gets pushed to the > > BeagleBoard-DeviceTrees repo first, and the files get sync'ed directly > > back to the kernel build script afterwards: > > > > https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.19.y/patch.sh#L353-L409 > > > > It should be less error prone. I hope.. > > Ok, the patch flow process seems sound. > > But I have a rather simpler question. How would I match a specific > kernel deb package to a BeagleBoard-DeviceTrees repo commit which went > into _this_ package?
Yesterday you have to look at the dates: https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.14.y/patches/soc/ti/beagleboard_dtbs/0001-Add-BeagleBoard.org-DTBS-v4.14.x-ti.patch ****************** Subject: [PATCH] Add BeagleBoard.org DTBS: v4.14.x-ti https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.14.x-ti Signed-off-by: Robert Nelson <[email protected]> ****************** I'm working on pushing this change to that commit message: ****************** Subject: [PATCH] Add BeagleBoard.org DTBS: v4.14.x-ti https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.14.x-ti +https://github.com/beagleboard/BeagleBoard-DeviceTrees/commit/f15c95bd3d543557fcbbf9e43778c0483391b64e Signed-off-by: Robert Nelson <[email protected]> ****************** So now that commit will have the branch and git sha.. > I suspect I can't randomly pick a set of DTB files meant for one kernel, > modify and then apply those to another kernel. As long as it's the same branch, it's supposed to work for DT's ABI's rules... > > E.g. I've chosen linux-image-4.19.50-ti-r24 as my kernel (from your apt > repo). Now I wish to modify the DTB-s corresponding to _this_ kernel > package. Not for 5.x, not for some newer or older release of 4.19-ti. > How would I find the DTB-s in this package from the > BeagleBoard-DeviceTrees repo? Okay, let's see if we can work this out as a new user.. So starting with "4.19.50-ti-r24" and the beagle repo, we get this: https://github.com/beagleboard/linux/releases/tag/4.19.50-ti-r24 The only useful link is: https://github.com/beagleboard/linux/commit/ead458b39df6a532f8e8a55cc641669b6a9e8da0 Which is the defconfig push.. If we go this way: https://github.com/RobertCNelson/ti-linux-kernel-dev/releases/tag/4.19.50-ti-r24 The only useful link is: https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/96fca1b9ea8a552c7ea852c3a045a9bbecc79b17 Yeah... so i could find the sha for you, but for the average user it's a pain.. Let me I think i need to add more useful git sha's for pulled in repo's to those commits.. 4.19.50-ti-r24 was Jul 15th so it should be this commit: https://github.com/beagleboard/BeagleBoard-DeviceTrees/commit/d142f8a52827cc500888e11bcee75fea625893bb (even it it wasn't that was for the beaglebone-ai so it should matter).. yeah... let's work on that.. > Off-topic: I'm also assuming that the kernel packages in > repos.rcn-ee.com are all tested and good for production use, which may > or may not be correct. "all tested"... Nope.. The "BeagleBoard" linux repo is "build" tested, either manually, or scanned ever 12 hours (only built on changes..) http://gfnd.rcn-ee.org:8080/view/BeagleBoard/job/beagleboard_kernel_builder/ The feeder script into the BeagleBoard linux repo is "build" tested on every change, as i'm working on it: (to make sure a RT or something else didn't break it) http://gfnd.rcn-ee.org:8080/view/Builds-v4.19.x-ti/ I run test it when i'm doing something significant. After a tag get's pushed, the build farm takes over and builds a *.deb for each distro/release Which today include: bionic-armhf bullseye-armhf buster-armhf disco-armhf eoan-armhf sid-armhf stretch-armhf xenial-armhf Completed *.deb files are added to the apt repo and rsynced to repos.rcn-ee.com ... Then usually every monday morning i update a set of 5 BBB's Running: stretch: http://gfnd.rcn-ee.org:81/farm/uptime/ U-Boot + Mainline linux U-Boot + 4.14.x-ti U-Boot + 4.14.x-ti-rt U-Boot + 4.19.x-ti U-Boot + 4.19.x-ti-rt Then i have 6 X15's running, Debian Buster + 4.19.x-ti, updated every morning (when idle).. Then i have 8 Wand's running, Debian Buster + 4.19.x, updated every morning (when idle) So yeah, i test what i can, can't test everything especially if Ubuntu or Debian throws in a wrench with a broken gcc version or something else in their testing repos.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYj9RQ4u9ZhNjO9On%3DCJYNSFC3TP9y-8LPQdcqHaApG5Qw%40mail.gmail.com.
