@op,
Sorry in advance, but I just can't keep quiet.
What a perfect example of what you can do with scripts for booting - I would just l-o-v-e to see how our systemd-fans would tackle this one ...
(and no, I do not intend to move the systemd-fight (for lack of a better word) over here ...)

Finally, I have chosen (and, yeah, ordered) an ARM netbook, with WM8850 CPU. I expect it to arrive in the near future. But I will not have time to take care of this little & fun project until early next month. My job...

My netbook will be an "standard" chinese & cheap ARM device, but with an 10 inch display and resolution of 1024x600. CPU is, like I said, WM8850 at 1,2 GHz, 1GB RAM, 4GB HDD, err... flash.

Then, what I known?

That netbook come with Android 4.0, then, most likely run an 3.0.x kernel.

We have the sources of this kernel version for Android, published by WonderMedia, without the sources of closed Mali and DSP drivers. It is possible to make a functional source tree, using the diverse trees. Aka, the GIT wm8850, apc-wm8750, etc...

Is very clear that if you want to make advantage of closed source drivers, and most important is Mali, we should stuck on 3.0.8. The question is: we can drive an slackware-current with an 3.0.8 kernel? And that kernel can be easy reconfigured to make an ordinary slack-like kernel, without touching much the configuration, to make the closed drivers to fail?

Second variant can be to use an "modern" kernel, like WKT. Then no sound, no other nice things. Fortunately, we have access to sound driver code (is an alsa device) and the framebuffer (video) driver, so I can try an brute force porting them to 3.9 or 3.10. That can be possible because the WonderMedia code is something isolated from the orthodox code.

I known, that's not nice things to do in a kernel tree, in fact, I should make a reimplementation of code, using the kernel standards, BUT, like I said, this is an pet project, so... if it works, why not?

Then, in few words, I believe that I can make functional that sound driver and the video driver, but not Mali, of course. This means that we will have an (G)2D accelerated framebuffer and sound.

This are the results of my studies, until now.

Finally, It would be nice if WKT would explain how he managed to make his device to work with Slackware, even there are problems with the lack of drivers.

I'm interested in a summary of how he managed to boot the linux kernel.

I known, is something about using the SDCARD, all the information exists somewhere, but a clear summary would be interesting.

Looking forward to this, since I recently picked up the Allwinner A10-based PengPod1000, and wanted to put slack on it.