site  contact  subhomenews

Puppy running on Pandaboard (ARM)

December 15, 2011 — BarryK
Forum member dim-kut has beat us all to it! He has got PuppyRus (Russian Puppy) running on a Pandaboard, which has a Cortex-A9 ARM CPU:

Dim-kut is using a 3.0.9 kernel, U-boot, and booting Puppy off a 2GB SD card.

So far, it is booting to the commandline, no X.

I posted about the Pandaboard recently:


( )

Username: Aitch
"Barry, I don't know if you've come across YAFFS for your Raspberry Pi/Arm project....might be worth considering Aitch :)

Username: Aitch
"Barry I also found MTD, which looks interesting, from a perspective of multi device compatibility I forgot to url tag the previous link, sorry Aitch :)

jwm -reload
Username: Iguleder1
"Barry - Joe added "-reload" to JWM, to refresh the root menu. Could be useful :)

re reload
Username: 01micko
"Yep, since jwm-547. I already patched petget .. (files/patches soon) works great! No more flicker :) Joe is currently at 553 (fresh today). He seems busiest on jwm this time of year, so I'll wait a bit. One issue though is that apps like wbar (maybe others, probably imlib2 based) have a layer issue. Fixed with a <Group> setting.

Username: technosaurus
"jwm already has a StartupCommand and a RestartCommand that puppy hasn't used up until now (probably because fixmenus was so slow), ... <ReloadCommand>jwm_menu_create</ReloadCommand> ... would be nice, I can look at patching if others are interested. though I have just started making the use of the <StartupCommand> here: got the puppy-4.1 series initrd down to <1mb with Xvesa, jwm, rxvt and the full build of busybox time to desktop ~2s boot status is in an rxvt terminal TODO - move all init functions to the StartupCommand (with flag to init only on first run) adding Dillo, mp, Xdialog and emelfm only adds ~1Mb, so I may add those too - We'll see. I realize this is way outside of the comfort zone for most - I just grew bored with the norm and wanted to experiment with drastically different ways of doing things. p.s. there is a much lighter window manager than jwm that is based on jwm but uses xcb (which is much lighter and faster and more threadsafe) but since no Xserver or terminal emulator have been ported, I use jwm b/c I can build a static multicall binary against libtinyX11 and uclibc

Username: 01micko
"Latest JWM with petget patches is uploaded to the forum. Petget patches should be backward compatible but I didn't test. NOTE: the executable is for [i]Slacko only[/i]. You can extract the pet and use the hacked petget files and the xdg template if you compile jwm- >= 547 in your puppy of choice. The xdg template has a <Group> setting for wbar which gave issues with the layers and the new jwm exec, perhaps I should mention to Joe but it isn't a big deal. see <--

Re xcb
Username: BarryK
"Wary no longer has xcb. Racy has xcb, a recent version. That is how I got around the problem of potential clash between the old and new xcb. If an app is compiled in Wary, without any xcb, it will work in Racy also. Unless of course, the app actually needs xcb, but very few do.

xcb in Wary
Username: BarryK
"linuxcbon, I can't quite remember, but it might be libX11 that also has to be recompiled -- or get a PET for an older version of Wary prior to 5.2. But the version of Xorg in wary only works with the xcb 1.0, and that clashes with later xcb when upgrade to Racy. There may also be a clash with apps that have been compiled with the later xcb. So, I would recommend, don't do it.

Username: linuxcbon
"Finally I compiled uwm by compiling all existing xcb stuff (lol). One issue is when doing make install, it complains strip --strip-unneeded -R .comment udm strip: 'udm': No such file It starts with xwin but crashes when clicking an icon or starting a programm, so it's not ready. uwm[6097]: segfault at 0 ip 08054aec sp bf9cb560 error 4 in uwm[8048000+22000] Anyway, I was just testing. I will leave that now.

Tags: puppy