> Hi Dimitar, > > I have not decided on anything to mainline as of now as I am new to BBB. So > the first step is to build the kernel from the right tree (which itself is > confusing) and see where I can improve. At least try to solve simple > problems and then move on to harder stuff. I will also start documenting > stuff as I go along. > > Working on the i.mx6 and i.mx7 I find the approach of NXP better where I can > just "git pull" from the NXP source tree and build the kernel rather than > apply a set of patches using a script. Submissions of patches would be to > the i.mx maintainers which would be eventually mainlined.
We "are not" TI... TI does the same thing, you can go grab their tree here: http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.14.y or: http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.9.y or: http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.4.y and they push things mainline.. We just use it as a base for BeagleBoard.org and then include things that have been rejected multple times on mainline, but our users use. 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/CAOCHtYgGLKqnb2Z76iVfeW1fKRBE5jpi0sQTgjNBoBhz7sHXUw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
