[Sugar-devel] ARM fork

[Ryan Cunningham]

Here is a link to an updated file system image, incorporating an updated
RAM disk.

This updated RAM disk incorporates changes to
`/usr/lib/dracut/hooks/pre-mount/10-olpc-boot-premount.sh' and
`/usr/lib/dracut/hooks/cmdline/20-olpc-boot-cmdline.sh', to remove
XO-specific information.

 32013o4.img
<https://docs.google.com/file/d/0BykD1OG4zPMHT0J1MVlxQV9hcDQ/edit?usp=drive_web>



On Fri, Jun 20, 2014 at 7:41 PM, Ryan Cunningham <rvskmbrly3 at gmail.com>
wrote:

> Here is an updated initial RAM file system image and a file listing.
>
> It's up to you to merge the initial RAM file system into the root image I
> gave you previously.
>
> The image is updated to remove some XO-specific content.
>
>
> On Fri, Jun 20, 2014 at 5:35 PM, Ryan Cunningham <rvskmbrly3 at gmail.com>
> wrote:
>
>> Here are some SVG icons that can be used by OEMs for the front panel
>> buttons.
>>
>>
>>
>>
>> On Fri, Jun 20, 2014 at 3:50 PM, Ryan Cunningham <rvskmbrly3 at gmail.com>
>> wrote:
>>
>>> I have now updated the README to provide for the addition of a
>>> requirement of a Power button, and to provide for the addition of a
>>> statement disallowing any rotation sensor.
>>>
>>>
>>>  README.equipment
>>> <https://docs.google.com/file/d/0BykD1OG4zPMHSzFaYkJGODRHOVk/edit?usp=drive_web>
>>>
>>>
>>>
>>> On Fri, Jun 20, 2014 at 3:32 PM, Ryan Cunningham <rvskmbrly3 at gmail.com>
>>> wrote:
>>>
>>>> I will now post Google Drive links to my port of the OLPC OS for other
>>>> ARM devices.
>>>>
>>>> Here is what I did to make this port:
>>>>
>>>> 1. I downloaded the file system tree for the XO-4 version of OLPC OS
>>>> 13.2.0.
>>>> 2. I then extracted the contents of that tree using `tar -xv --lzma'.
>>>> 3. I then moved the runtime version to the root of the tree and deleted
>>>> the ``pristine'' backup.
>>>> 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.
>>>> 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).
>>>> 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.
>>>> 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.)
>>>> 8. Then I archived all of that into the Ext4 file system image linked
>>>> here and created the README.
>>>>
>>>> (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.)
>>>>
>>>>
>>>>
>>>>
>>>> *(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. 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.) *
>>>>  README.equipment
>>>> <https://docs.google.com/file/d/0BykD1OG4zPMHVmN1MUVGWHM2ajA/edit?usp=drive_web>
>>>>   32013o4.img
>>>> <https://docs.google.com/file/d/0BykD1OG4zPMHZ0NGbWtPeGF4eEU/edit?usp=drive_web>
>>>>
>>>> On Thu, Jun 19, 2014 at 9:31 AM, Ryan Cunningham <rvskmbrly3 at gmail.com>
>>>> wrote:
>>>>
>>>>> I've now deleted my fork; similar software, as you have pointed out,
>>>>> already exists.
>>>>>
>>>>>
>>>>> --
>>>>> Sent from my iPad
>>>>>
>>>>> On Jun 19, 2014, at 5:53 AM, Gonzalo Odiard <godiard at sugarlabs.org>
>>>>> wrote:
>>>>>
>>>>> This is very a very interesting development.
>>>>> Two comments:
>>>>> * In xo-4, we define the env variable GTK_IM_MODULE=Maliit and Gtk
>>>>> open the on screen keyboard
>>>>> when needed, without need modify the code. I think you should explore
>>>>> a similar solution.
>>>>> If not, you will need modify, not only sugar, but every activity. In
>>>>> the end will not be sustainable.
>>>>>
>>>>> * Please send patches for bin/sugar.in
>>>>> and src/jarabe/view/keyhandler.py, and will be accepted,
>>>>> other will need more analysis/testing.
>>>>>
>>>>> Gonzalo
>>>>>
>>>>>
>>>>> On Wed, Jun 18, 2014 at 1:05 PM, Ryan Cunningham <rvskmbrly3 at gmail.com
>>>>> > wrote:
>>>>>
>>>>>> I have forked your "sugarlabs/sugar" GitHub repository and made some
>>>>>> changes necessary to enable Sugar to operate successfully on ARM tablets.
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> The new repository branch is at <
>>>>>> https://github.com/rcunning01/sugar/tree/arm>. It is public;
>>>>>> however, only I have authorization to modify it.
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> The results should be as follows, if any errors are generated:
>>>>>>
>>>>>> * Abnormal tracebacks from the Python interpreter (said tracebacks
>>>>>> are accessed via the Log activity)
>>>>>> * Abnormal exception reports from ADB (the Android Debugger)
>>>>>> * Suggestions for correction
>>>>>>
>>>>>> 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:
>>>>>>
>>>>>> * X11
>>>>>> * The Metacity window manager
>>>>>> * GTK+
>>>>>> * Pango
>>>>>> * GLib
>>>>>> * GObject-Introspection
>>>>>> * ATK
>>>>>> * GDK-Pixbuf
>>>>>> * PyGObject
>>>>>> * Python 2.7
>>>>>> * sugar-artwork
>>>>>> * sugar-toolkit-gtk3
>>>>>>
>>>>>> Tell me if more are needed.
>>>>>>
>>>>>> (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.)
>>>>>>
>>>>>> --
>>>>>> Sent from my iPad
>>>>>> _______________________________________________
>>>>>> Sugar-devel mailing list
>>>>>> Sugar-devel at lists.sugarlabs.org
>>>>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Gonzalo Odiard
>>>>>
>>>>> SugarLabs - Software for children learning
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Ryan Cunningham
>>>>
>>>
>>>
>>>
>>> --
>>> Ryan Cunningham
>>>
>>
>>
>>
>> --
>> Ryan Cunningham
>>
>
>
>
> --
> Ryan Cunningham
>



-- 
Ryan Cunningham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140621/480f1e6b/attachment.html>