why aren't y'all coding in preparation for the upcoming release of the pyra? we'll need some fun software/games
.
In excitement about the Pyra, and dismay about the cost of dev boards, I did some hunting for similar-ish enough hardware that should be able to run binaries compiled for the Pyra, and perhaps vice versa.
Turns out the early version of the RPI2 is Armv-7A. And later versions are Armv-8a, but if you were careful about compilation flags to make sure you didn't include Armv-8a opcodes, it should be possible to compile biniaries on a Raspberry Pi that at a basic level should run on the Pyra. Especially if you are careful about libc and other library versions and you're running the RPI in aarch32 ARMv-7A compatibility mode.
Yes yes, I know. No RPI has a big little configuration. So it'd be hard to make and test software that tries to take advantage of the m4 cores. And the video core is pretty different.
The BeagleBoard X15 would be even closer, but it also costs over $250, which puts it much closer to the Omap dev board pricing than a Raspberry Pi.
Basically, the idea is that either using existing ports for the rpi as a start, or porting software to the rpi could in theory get one close to something that will work on the Pyra.
In my amateur porting attempts for the Pandora, I have found plenty of projects in c and c++ that don't compile well for an Arm target. And a RPI would in theory let you test basic NEON functionality.
On a different note, years ago I was able to run Raspbian for the RPI 1 in a chroot on a Pandora, which was cool to see. So there's at least a level of compatibility there as well.
--------
Also forgot to mention that since the Pyra OS is using Debian as a base, that should make a bunch of software and at least some games available right from the start. It might not be optimized for the Pyra, but it'd be a start.
