Not in alpha3, but yes it does, see my post here http://murga-linux.com/puppy/viewtopic. ... 419#729419 - Cubieboard2 uses A20. All it needs is a new kernel, a new bootloader, and a new script.bin (what else is new ). I'll probably cobble it together and make an release soon since I've got other things to attend and may disappear for a while. (My goals for "beta" release isn't going to be met so it will just be another alpha).starhawk wrote:Hey, jamesbond, would FatDogARM support the A20? I know it runs (at least somewhat) on A10 now...
The answer is a qualified yes. Bootloader support is there (but you need to compile it); kernel support is probably there unless EOMA does very exotic things; the only thing missing is the script.bin - but I'm sure you can get it from EOMA devs.I'm working with a very nifty project, actually found out about it through something Barry bought to support them -- EOMA-68. Basically a "cartridge motherboard" sort of thing -- the CPU/SoC, RAM, graphics, and some storage (microSD) is in a "CPU Card" with the physical form factor of a PCMCIA card (totally different pinout, though). The CPU card goes into a carrier board (my personal term, not the group's) that has ports and such on it.
More here --> http://elinux.org/Embedded_Open_Modular ... re/EOMA-68
*IF* FatDogARM could be made to work with this I'd just about dance in the streets.
Yes you can, but I doubt how practical it would be due to (low-)speed. You can even do this on your existing x86 machine - you can run qemu-system-x86 (or qemu-system-x86_64 if you want to run Fatdog64) on the real x86 and then boot Puppy in it - and figure out the speed yourself.Another question -- would it be possible to create a "mini-OS" that ran eg QEMU to emulate an x86 environment, on such a CPU, "under" the regular OS but also transparent to that OS? In other words --
base hardware
"mini-OS" emulation layer
some sort of x86 *nix OS
user
That way I could run, say, FatDog or Upup Raring or whatever, on this thing, as if it had eg an Atom CPU in it.
Not really. Many applications are portable; just look at the number packages supported for the ARM architecture.ARM's great for power consumption but I don't think the codebase (set of compatible applications and packages, in this case) is anywhere near as big for *nix ARM as it is for *nix x86...
True, but it has been a long time since Linux moved from being 386-only OS. The main problem with ARM is not the apps or the OS, but with the lack of discoverable bus (like USB or PCI) resulting in OS fragmentation (the analogy would be: a different kernel for every different motherboard).x86 is very much PlugNPlay with software because it's been around since 1981 or so and it's been *nix-able since Linus Torvalds started mucking with Unix memory management in the early 1990s (don't remember if it was '92 or '93...).