There's a lot of buzz around the Raspberry Pi at the moment, and I'm pleased to confirm two things:

Slackware ARM's packages (from 13.37 and -current) will run on the Raspberry Pi as is
Slackware ARM will provide a ready-to-run Kernel for the Raspberry Pi once a Pi is physically available to us (a couple of others in the Slackware core team are ordering one and I might get one too). Currently for those of your who have a Pi in your hands, you'll need to compile your own Kernel. I'll look into whether the Pi can be installed using the regular Slackware installer once the Kernels are prepared.

This will be the most "hardcore" Linux thing I have ever done, dont get me wrong been dabling for quite a while and due to dam HD failure Slacko is my day to day OS until I get home and get it sorted (Slacko, 3G MiFi and any piece of junk I can stick my USB drive into ha ha)

Now in X86 world you would boot up via CD/DVD drive using you fav iso and install to hd / usb etc but I believe in Pi land you cant do that and can only boot of the SD slot, is that correct?

You will find info on the RaspberryPy blog (Puppy style blog) on how I did this from the Puppy command line - with three commands
http://raspberrypy.tumblr.com/

. . . and now for something not completely different . . .
Like the PuPi name - very good.

The PARM project includes all migration to ARM (Puppy ARM is the full meaning). Here for example is what Barry is planning . . .

Quote:

Posted on 13 Mar 2012, 16:42 by BarryK
ARM architectures
A clarification, for those not familiar with ARM architectures. The Raspberry Pi has an ARMv6 CPU (also known as ARM11, just to confuse you), whereas most ARM boards these days have at least a Cortex-A8, which is ARMv7 (+NEON).

ARMv6 and ARMv7 refer to the instruction set. From my fairly brief reading, it seems that ARMv6 has "thumb" instructions but they are not very usable, whereas ARMv7 has "thumb-2" instructions which are usable -- these can considerably reduce the size of executables. Most ARMv7 CPUs also have the NEON multimedia instruction set, which can speed up multimedia operations.

What it comes down to, is if code is compiled for those extra goodies of ARMv7, then it won't work on an ARMv6 CPU. However, code compiled for ARMv6 will work on an ARMv7 CPU.

I want those extra features of ARMv7, if I am going to be using a board with an ARMv7 CPU. So that means I am going to have to build two different puppies, one targeting the Raspberry Pi, another targeting the ARMv7-based board.

Precise Pangolin is a suitable source of binary packages for the ARMv7-based Puppy (except for the omission of NEON). For RasPi, I will have to build from another distro such as Debian, that does have ARMv6 binary packages.

I hope that clarifies things.

My gold plated HDMI cables arrived from Amazon.
I suppose that is geek bling?
Good length. Good quality. I got 4 new cables including postage for less than US $8 including tax and postage

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum