Excellent - thank you, Robert. You mentioned OMAP... I'm still trying to figure out how to tell what commits end up in a given release. For example: https://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git/log/drivers/net/can/c_can/c_can_platform.c Latest Commit: https://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git/commit/drivers/net/can/c_can/c_can_platform.c?id=a7380db5f0d6dd94981e73da08d8fa863ee72235
Is that part of what's getting pushed for v3.19-rc? How do I look that up? On Friday, December 5, 2014 3:49:15 PM UTC-8, RobertCNelson wrote: > > On Fri, Dec 5, 2014 at 5:34 PM, Mike Zahalan <mikez...@gmail.com > <javascript:>> wrote: > > Thanks Robert! > > > > Those scripts in your EOLd repo are so promising/helpful. > > > > Due to some CAN bugs, I think I'm going to either have to patch > > 3.14.something, or go for a new kernel like 3.17.x > > > > I noticed you've got 3.17 stuff here: > > http://rcn-ee.net/deb/wheezy-armhf/v3.17.2-bone5/ > > > > But if I needed to get the source to patch/rebuild, how would you > recommend > > I go about doing that? > > So can on omap is getting a big push for v3.19-rc (as v3.18.0 should > be tagged this sunday) it'll still be a couple weeks before v3.19-rc0 > will be bootable.. > > either use: v3.14.x > https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/ti-linux-3.14.y > > or, v3.18-rc: > https://github.com/RobertCNelson/bb-kernel/tree/am33x-v3.18 > > Regards, > > -- > Robert Nelson > http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.