Tiny Core Base > Raspberry Pi

picore-kit

(1/7) > >>

roberts:
With the many arm platforms and their specific configurations my approach is to create a kit.
Like a remastering tool to be based on using an actual current core.gz and updating it to arm via existing known working Arm distribution.

This way we can jump start on open community development on several arm platforms. Without having to initially build all the necessary support tools and GPL compliant sources. Don't make such a commitment until you know the results would be worth the effort!

This approach also allows our strong and very talented community to participate in the early stages of development.

Call it protyping, jump starting, or remastering your own arm Core system. I have now posted the first cut of such an approach.
http://distro.ibiblio.org/tinycorelinux/4.x/arm/armv6/picore-kit.tgz

It contains three small scripts, Core custom compiled arm binaries and their sources.

Please be certain to read the README as one can easily wipe out a hard drive or an existing Debian Arm sdcard.

Comment, suggestions, patches, etc are all welcomed.

Who knows, hopefully this approach will be successful and via our community be extended to jump start other Arm platforms.

If and when such time all the PiCore sources and infrastructure have been completed then an image with GPL compliant sources can be hosted. Until such time, those who are comfortable with reading and running scripts, well, let the fun begin.

netnomad:
hi roberts,

thank you for your efforts behind the scenes!
one question:
is there a reason that you took the debian6-19-04-2012.zip,
in the moment the    2012-07-15-wheezy-raspbian.zip is the actual one!?
is it possible to use 2012-07-15-wheezy-raspbian.zip, too or is there a fundamental difference?
i'm looking forward to use tinycore on the rpi.

thank you for your work, help and, at the end, your reply.

bmarkus:

--- Quote from: roberts on August 13, 2012, 04:19:30 PM ---With the many arm platforms and their specific configurations my approach is to create a kit.
Like a remastering tool to be based on using an actual current core.gz and updating it to arm via existing known working Arm distribution.

This way we can jump start on open community development on several arm platforms. Without having to initially build all the necessary support tools and GPL compliant sources. Don't make such a commitment until you know the results would be worth the effort!


--- End quote ---

What is about a virtual environment, like http://sourceforge.net/projects/rpiqemuwindows/ ? Actually I do not have a Pi but would be interesting to play in a virtaul environment before grabbing one.

roberts:
netnomad, I started with standard Debian and used Qemu to get Core working. Once I got my pi and could verify that root filesystem worked I then I took my notes and made some scripts to make a kit.

I did this precisely for the reason that you posted. Imagine if I had dedicated so much time to compile each and every binary component needed for Core. I would not be happy to start all over again. My methodology is too quickly prototype to see if an end result is worth the effort. And with Arm development still evolving, a kit seems to be more efficient way to get started.

Since so much work has been done over the years to whittle down Core to a minimum, I thought it would not be difficult to identify the x86 binaries and replace only those. Because I commented the scripts it should not be difficult to change the actual Arm binary replacements for an alternate Arm distribution. I am currently focused on the same method for the Allwinner A10 Mele.

I posted this early cut of picore-kit. I am hoping that the community will take advantage of the opportunity to be involved in the early development of Pi Core.

So I suggest to try Raspbian. Look at the code in setup.sh and change as needed for Raspbian's arm binaries. Post your results here.

My scripts are only a starting point, a concept, a strategy, a way to share how to get Core on Arm platforms. I am truly hoping that the community will get involved.

Once the community is satisfied with a particular kit, then the dependency Arm binaries replacements can be dropped for actual compiled from sources and we can host a complete image.

roberts:
@bmarkus, I actually used Qemu on TinyCore to produce the root filesystem for Core on Pi. We already have all the needed extensions in the repository. I can tarball it up and send to you. I don't have Windows so Qemu on Windows is not something I can help with. It would be great if you would be willing to help.

Navigation

[0] Message Index

[#] Next page