I have a debian (jessie) installed in a BeagleBone Black board using the RCN (http://repos.rcn-ee.net/debian/) repository. I noticed that there are several linux images there. For example:
linux-image-3.19.0-rc7-armv7-lpae-x0 - Linux kernel, version 3.19.0-rc7-armv7-lpae-x0
linux-image-3.19.0-rc7-armv7-x3 - Linux kernel, version 3.19.0-rc7-armv7-x3
linux-image-3.19.0-rc7-bone2 - Linux kernel, version 3.19.0-rc7-bone2
linux-image-3.19.0-rc7-bone3 - Linux kernel, version 3.19.0-rc7-bone3
What are the differentes between each kernel image ?What do the different suffixes (lpae, x0, x3, bone2, bone3) stands for ?
Best regards,
armv7-lpae-x:
lpae = https://en.wikipedia.org/wiki/ARM_architecture#Large_Physical_Address_Extension
It was added with the Cortex-A15, The Cortex-A7,A12,A15,A17 all have it..
Devices which don't have it, Cortex-A5,A8,A9 will NOT boot with it enabled..
Right now, this only supports the omap5_uevm, BeagleBoard-X15...
armv7-x:
general image that'll work with most boards...
bone:
tweaked config for the BeagleBone family (am335x), which enable a few
things we can't enable on the general image due to errata on the older
Cortex-A8 used on the BeagleBoard/Beagleboard-xM.. (Which allow us to
get a little more performance out of the am335x)
Regards,
ti: ?
whats the story of the ti kernel?
The "main" reason for the ti kernel is:
http://elinux.org/Beagleboard:BeagleBoard-X15
As a secondary, we got a lot of bugs fixed from ti on am335x, that
were issues in 3.8 for some users.
pm/usb/ethernet/etc..
Right now there's three variants:
The first two have been around for awhile:
linux-image-3.14.33-ti-r51
linux-image-3.14.33-ti-xenomai-r51
the "ti" is just:
http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-3.14.y
Thanks for the info and as always thanks for an amazing job!
Happily running a stable ti-r51 kernel,
Michiel
As a secondary, we got a lot of bugs fixed from ti on am335x, that
were issues in 3.8 for some users.
pm/usb/ethernet/etc…
Right now there’s three variants:
The first two have been around for awhile:
linux-image-3.14.33-ti-r51
How does the 3.14.33-ti series kernels compare to 3.19.0-bone3? Have the TI patches in 3.14.33 been upstreamed into later kernels such as 3.19.0?
I have been running on the 3.19.0 series for awhile (Debian Jessie rootfs from November and late January). When I tried the 3.14.xx-ti series back in the January time frame the kernel was hanging periodically under heavy I/O load (like doing an rsync of the rootfs to a remove host). I was also having issues with the kernel hanging when doing performance testing using “iperf3” between 2 BBB’s on a wireless network (the iperf “server” host would hiccup periodically). The 3.19.0 series has proved to be more stable. (I have been working with an 802.11s mesh setup using TP-Link WN722N in case anyone is interested.)
Should I be going back to the 3.14.33-ti series? I know “don’t fix it if it ain’t broke”, but just wondering about the details of 3.14.33-ti versus later kernels.
Great work Robert! Hope to see you at ELC next month.
ba