Ok thanks! Then when you do a full re-build, does it delete the entire local tree and re-git evertyhing from the same 4.4.y branch that you checkedout locally on the server?
I generated a custom device tree, am57xx-custom,dts which essentially uses am57xx-evm-reva3.dts as a starting point and relies on all of the other dts and dtsi files that it pulls in. I build am57xx-custom.dtb by copying am57xx-custom.dts into the 4.4.y tree's arch/arm/boot/dts directory and adding it to Makefile. Whenever FULL_REBUILD is defined, am57xx-custom.dts/dtb get deleted from arch/arm/boot/dts and the corresponding Makefile.. Maybe I should try your device tree builder... On Friday, January 5, 2018 at 8:58:40 AM UTC-6, RobertCNelson wrote: > > On Thu, Jan 4, 2018 at 9:25 AM, Jeff Andich <[email protected] > <javascript:>> wrote: > > Ok, so if I understand correctly, if I git the kernel and checkout the > 4.4.y > > or 4.9.y branches and then build the kernel using build_kernel.sh with > > FULL_REBUILD defined, any updates to the mainline or the patchset could > > affect my build or functionality, right? > > Nope, once you do a checkout, the kernel version and kernel sha are > locked into the script.. > > So if you lock everything 'down' including your OS (aka no updates), > the script will work and pull all the same stuff 10 years from now.. > (well as long as github.com and kernel.org git servers don't change > anything).. > > 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/74a9fd36-f80c-4769-b9a9-e58fb18a2d9f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
