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?

What is the best way to get updated when either the kernel and/or patch 
set(s) change?  What mailing lists do we need to join?

Thanks!!

jeff  

On Tuesday, January 2, 2018 at 8:48:10 AM UTC-6, RobertCNelson wrote:
>
> On Tue, Jan 2, 2018 at 8:41 AM, Jeff Andich <[email protected] 
> <javascript:>> wrote: 
> > 
> > FYI, I THINK I ran into something similar over the holidays when I tried 
> to 
> > fetch and build the 4.4.y and 4.9.y kernels using eewiki.  I tried both 
> BBB 
> > and BB-X15.  I ran into an issue with a build error in an assembly file 
> > which apparently had to do with some kind of networking package.  The 
> kernel 
> > built again, when this package was de-selected in makemenuconfig.  I was 
> > getting ready to post something on this, but then some time after 
> Christmas, 
> > I re-fetched everything using the instructions on eewiki and everything 
> > built again.... 
> > 
> > 
> > Regards and happy new year! 
>
> for 4.9.x it was me last week, i fubared up the pocketbeagle 
> simplegaming device tree binary. 
>
> also the wireguard patchset merge the last few weeks had some issues with 
> thumb2 
>
> But Wireguard + https://github.com/StreisandEffect/streisand + linode 
> (or any of the other supported ones) has been working awesome for me. 
> ;) 
>
> 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/25803f4d-5d82-40b7-a040-fcfd60b2e152%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to