soundcheck wrote: > > RPI 2 is out. Surprise Surprise. > It's an ARM Cortex A7 now! > ARMv6 vs. ARMv7 are not upwards compatible! We can not use the current > RPI image for the RPI2. >
Not quite sure what you mean..... RPi2B can use an armv6hl compiled image but obviously needs the ARMv7 BCM2709 "flavour" kernel. The F20 base image I use for both B/B+/2B is armv6hl. The "optimised" F21 image, because everything has been built for armv7hl cannot be used with B/B+ even with a BCM2708 kernel. That's not backward compatible. At the point Triode wants to support 2B, he can just add a kernel to existing Pi image. They live side by side. (ARMv7 defaults to /boot/kernel7.img). Or he can choose to have a totally new optimised armv7hl image, and take advantage of Neon in a couple of places, optimised for 2B and leave the current image as-is for the older hardware. I'm quite impressed with the they have achieved with device tree and auto-detection and having one core armv6hl image and detection at boot time, booting the relevant kernel. It's nice that there is the backward compatibility, even if the 2B isn't running the optimised code that it could be. But then, backward compatability has always been one of their main aims, rather than a pissing contest over hardware specs. Even with the less than optimal 10/100 ether via USB and lack of SATA, the 2B is a stupidly good piece of hardware for the money! I actually have 7x Pi2B's humming away right now, running transcoding benchmarks. ;) ------------------------------------------------------------------------ JackOfAll's Profile: http://forums.slimdevices.com/member.php?userid=3069 View this thread: http://forums.slimdevices.com/showthread.php?t=101624 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
