<div dir="ltr"><div><div><div><div><div>I will now post Google Drive links to my port of the OLPC OS for other ARM devices.<br><br></div>Here is what I did to make this port:<br><br></div>1. I downloaded the file system tree for the XO-4 version of OLPC OS 13.2.0.<br>
</div>2. I then extracted the contents of that tree using `tar -xv --lzma'.<br></div><div>3. I then moved the runtime version to the root of the tree and deleted the ``pristine'' backup.<br></div></div><div>4. Then I copied the `olpc-dev-kernel' script from that tree into my home folder, changed the created copy appropriately, ran it, and deleted the original.<br>
</div><div>5. I then deleted some other device-specific executable files (whose names and paths I do not remember; Sugar should be able to launch without them).<br></div><div><div><div><div class="gmail_extra">6. After that, I removed (assuming BASH-style brace expansion) the files ``boot/{act,run}{os,rd}4.zip'' and ``boot/bootfw4.zip'', which are unnecessary for this platform.<br>
</div><div class="gmail_extra">7. I then moved `initrd.img.orig' to `initramfs-3.5.7_xo4-20130705.0203.olpc.e77de3d.img', and moved `vmlinuz.orig' to `vmlinuz-3.5.7_xo4-20130705.0203.olpc.e77de3d'. (The version numbers were copied from the name of the `config-3.5.7_xo4-20130705.0203.olpc.e77de3d.xz' file.)<br>
</div><div class="gmail_extra">8. Then I archived all of that into the Ext4 file system image linked here and created the README.<br><br></div><div class="gmail_extra">(The Ext4 file system image is a 5-gigabyte download: client tablets are expected to have exactly 5 GB of NAND flash memory, plus enough storage space for the boot loader the manufacturer decides to use.)<br>
<br></div><div class="gmail_extra"><b>(Note: The act of attaching these Google Drive links may have made this message an RTF or HTML message. If this message is an HTML message, and if your e-mail client instead gives you the source code for any HTML message it is asked to view, copy and paste the URL in the value of the "href" attribute of the "a" element containing these boxes.<br>
<br>I do know that Google Drive is a proprietary service, however, this is the only option I, as a Gmail user, have seen so far for sending files this big: I've tried Sendspace with no luck. I am not liable for any damage Google Drive may cause to these files, whether done with or without my notification.)<br>
</b></div><div class="gmail_extra"><div class="gmail_chip gmail_drive_chip" style="width:396px;height:18px;max-height:18px;background-color:rgb(245,245,245);padding:5px;color:rgb(34,34,34);font-family:arial;font-style:normal;font-weight:bold;font-size:13px;border:1px solid rgb(221,221,221)">
<a href="https://docs.google.com/file/d/0BykD1OG4zPMHVmN1MUVGWHM2ajA/edit?usp=drive_web" target="_blank" style="display:inline-block;max-width:366px;overflow:hidden;text-overflow:ellipsis;white-space:nowrap;text-decoration:none;padding:1px 0;border:none"><img style="vertical-align: bottom; border: none;" src="https://ssl.gstatic.com/docs/doclist/images/icon_10_generic_list.png"> <span dir="ltr" style="color:rgb(17,85,204);text-decoration:none;vertical-align:bottom">README.equipment</span></a><img src="//ssl.gstatic.com/ui/v1/icons/common/x_8px.png" style="opacity: 0.55; cursor: pointer; float: right; position: relative; top: -1px; display: none;"></div>
<div class="gmail_chip gmail_drive_chip" style="width:396px;height:18px;max-height:18px;background-color:rgb(245,245,245);padding:5px;color:rgb(34,34,34);font-family:arial;font-style:normal;font-weight:bold;font-size:13px;border:1px solid rgb(221,221,221)">
<a href="https://docs.google.com/file/d/0BykD1OG4zPMHZ0NGbWtPeGF4eEU/edit?usp=drive_web" target="_blank" style="display:inline-block;max-width:366px;overflow:hidden;text-overflow:ellipsis;white-space:nowrap;text-decoration:none;padding:1px 0;border:none"><img style="vertical-align: bottom; border: none;" src="https://ssl.gstatic.com/docs/doclist/images/icon_10_generic_list.png"> <span dir="ltr" style="color:rgb(17,85,204);text-decoration:none;vertical-align:bottom">32013o4.img</span></a><img src="//ssl.gstatic.com/ui/v1/icons/common/x_8px.png" style="opacity: 0.55; cursor: pointer; float: right; position: relative; top: -1px; display: none;"></div>
<br><div class="gmail_quote">On Thu, Jun 19, 2014 at 9:31 AM, Ryan Cunningham <span dir="ltr"><<a href="mailto:rvskmbrly3@gmail.com" target="_blank">rvskmbrly3@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto"><div>I've now deleted my fork; similar software, as you have pointed out, already exists.<div class=""><br><br><div>-- </div>Sent from my iPad</div></div><div><div class="h5"><div><br>On Jun 19, 2014, at 5:53 AM, Gonzalo Odiard <<a href="mailto:godiard@sugarlabs.org" target="_blank">godiard@sugarlabs.org</a>> wrote:<br>
<br></div><blockquote type="cite"><div><div dir="ltr">This is very a very interesting development.<div>Two comments:</div><div>* In xo-4, we define the env variable GTK_IM_MODULE=Maliit and Gtk open the on screen keyboard </div>
<div>when needed, without need modify the code. I think you should explore a similar solution.</div>
<div>If not, you will need modify, not only sugar, but every activity. In the end will not be sustainable.</div><div><br></div><div>* Please send patches for bin/<a href="http://sugar.in" target="_blank">sugar.in</a> and src/jarabe/view/keyhandler.py, and will be accepted,</div>
<div>other will need more analysis/testing.</div><div><br></div><div>Gonzalo</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 18, 2014 at 1:05 PM, Ryan Cunningham <span dir="ltr"><<a href="mailto:rvskmbrly3@gmail.com" target="_blank">rvskmbrly3@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I have forked your "sugarlabs/sugar" GitHub repository and made some changes necessary to enable Sugar to operate successfully on ARM tablets.<br>
<br>
The most important change is the requirement of installation of the onBoard on-screen keyboard from Ubuntu; it is to be automatically invoked on entry into any text field (except if onBoard is already running) and is to be automatically killed on departure from that field; therefore, some activities may have to be ported specifically for this architecture.<br>
<br>
The new repository branch is at <<a href="https://github.com/rcunning01/sugar/tree/arm" target="_blank">https://github.com/rcunning01/sugar/tree/arm</a>>. It is public; however, only I have authorization to modify it.<br>
<br>
I am writing this e-mail to query for any results from testing this on any Android tablet (this version does not work with Android phones) you might have or desire to purchase. However, such a test causes /all/ existing data on the tablet (including core OS data) to be erased, so deploy carefully. The software itself, however, is, and should continue to be, platform-independent.<br>
<br>
The results should be as follows, if any errors are generated:<br>
<br>
* Abnormal tracebacks from the Python interpreter (said tracebacks are accessed via the Log activity)<br>
* Abnormal exception reports from ADB (the Android Debugger)<br>
* Suggestions for correction<br>
<br>
This version continues to use GTK+. You will need to modify the resulting Android OS image, adding to it cross-compilations (for the ARM platform) of the following applications and libraries:<br>
<br>
* X11<br>
* The Metacity window manager<br>
* GTK+<br>
* Pango<br>
* GLib<br>
* GObject-Introspection<br>
* ATK<br>
* GDK-Pixbuf<br>
* PyGObject<br>
* Python 2.7<br>
* sugar-artwork<br>
* sugar-toolkit-gtk3<br>
<br>
Tell me if more are needed.<br>
<br>
(This version does not have cell phone network support. The Terminal activity, when ported to ARM, should require that the destination device have sufficient access privileges [on Android, this is obtained by rooting], and, with this port, should be a separate download.)<br>
<span><font color="#888888"><br>
--<br>
Sent from my iPad<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Gonzalo Odiard<br><br><div>SugarLabs - Software for children learning <br></div></div>
</div>
</div></blockquote></div></div></div></blockquote></div><br><br clear="all"><br>-- <br>Ryan Cunningham<br>
</div></div></div></div></div>