Daniel Kulp <[email protected]> wrote: > [-- multipart/alternative, encoding 7bit, 71 lines --] > > [-- text/plain, encoding 7bit, charset: UTF-8, 27 lines --] > > > > On Friday, February 15, 2019 at 3:48:25 PM UTC-5, Chris Green wrote: > > > > > > Anyway, are there any particular reasons for going for any specific > > kernel other than the latest? Presumably 3.8.x will start getting > > less support (if it hasn't already). > > > > There are certain apps that behave very differently with various kernels. > I know my application does not work nearly as well with the "-ti" kernels > but works perfectly with the "-bone" kernels. We've had major issues with > 4.19 (looks like that is getting resolved soon). The -rt and non-rt > kernels have various uses cases where they are either needed or should not > be used. Boot times are also affected by the kernel selection. So yes, > there are definite reasons for being able to control exactly which kernel > is used on your device. > I just run some simple Python scripts that read values from the analog inputs and also use one of the serial ports. Speed really isn't an issue, nor is start-up time. I do depend on a lot of standard stuff like ssh and resync though to transfer data. Thus I want as default/standard Debian as possible.
-- Chris Green ยท -- 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/0lhojf-h9n.ln1%40esprimo.zbmc.eu. For more options, visit https://groups.google.com/d/optout.
