Sugar on the BeagleBoard using the OpenEmbedded toolkit.

Sugar on the BeagleBoard using the OpenEmbedded toolkit.

[David Farning]

Welcome to the Sugar on the BeagleBoard project.  It seems that we have
all of the pieces in place to do a port.

First, some background.

The initial port will be getting Sugar[1] to run on the Beagleboard[2]
using the Open Embedded[3] toolkit.

For a collaboration point, Jason has set up the sugar on beagle wiki[4].

For Sugar related bug, Sugar Labs uses the OLPC trac[5]. Open Embedded
uses bugzilla[6].

If you are interested come introduce yourself on the beagleboard[7]
mailing list.

thanks
dfarning


1. http://sugarlabs.org/go/Main_Page
2. http://beagleboard.org/
3. http://wiki.openembedded.net/index.php/Main_Page

4. http://elinux.org/BeagleBoardSugar

5. http://dev.laptop.org/wiki
6. http://bugs.openembedded.net/

7. http://groups.google.com/group/beagleboard?hl=en

Re: Sugar on the BeagleBoard using the OpenEmbedded toolkit.

[Koen Kooi]

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]


Op 22 aug 2008, om 02:29 heeft David Farning het volgende geschreven:

> Welcome to the Sugar on the BeagleBoard project.  It seems that we  
> have
> all of the pieces in place to do a port.
>
> First, some background.
>
> The initial port will be getting Sugar[1] to run on the Beagleboard[2]
> using the Open Embedded[3] toolkit.

The basics (sugar, sugar-base, sugar-toolkit, sugar-presence-services  
and sugar-artwork) are now running on the beagleboard:

http://www.angstrom-distribution.org/sugar-running-ångström

To build it using OE: 'bitbake sugar'
To install it in angstrom*: 'opkg install sugar'

The Glucose pack is missing sugar-datastore (needs a lot of python  
modules that aren't in OE yet), etoys (haven't looked at that yet) and  
journal (haven't looked at that either).
The Fructose pack is completely missing in OE.

The remaining tasks for people wanting to work on this are:

1) add OE recipes for needed python-modules
2) add OE recipes for remaining Glucose items
3) add OE recipes for Fructose items
4) build it
5) install resulting packages and run them, see them crash due to  
missing python modules, goto 1
6) make screenshots :)

regards,

Koen

* only has armv7a packages at the moment

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 193 bytes --]

Re: [sugar] Sugar on the BeagleBoard using the OpenEmbedded toolkit.

[Koen Kooi]

[-- Attachment #1: Type: text/plain, Size: 3050 bytes --]


Op 3 sep 2008, om 22:14 heeft Edward Cherlin het volgende geschreven:

> On Mon, Sep 1, 2008 at 3:57 AM, Koen Kooi  
> <k.kooi@student.utwente.nl> wrote:
>>
>> Op 22 aug 2008, om 02:29 heeft David Farning het volgende geschreven:
>>
>>> Welcome to the Sugar on the BeagleBoard project.  It seems that we  
>>> have
>>> all of the pieces in place to do a port.
>
> Very good. Thank you.

<snip>

> I assume that OE is intended to be all Free Software

OE is 'merely' a buildsystem (something like gentoos portage or GNOMEs  
jhbuild) and its metadata is MIT licensed.

> , and I see
> scattered references to GPL 2 in the Wiki, but I don't see a clear
> statement on licensing on the main page or in the FAQ. Can somebody
> write one?

I'm unsure what is needed beyond the COPYING.MIT in topdir of the  
repository. The licensing of your buildsystem should have no bearing  
on the resulting distribution.

> Also, one or more architecture pages showing the toolchain,
> relationships with other Free Software projects, and the structure of
> the resulting builds?

As a buildsystem OE has relationships with the interpreter used  
(bitbake, hosted at berlios) and it's users (angstrom, nslu2-linux,  
openmoko, etc).

I suspect you are confusing OE with a distribution (which angstrom  
is), it is not a distro, it's a distro builder :) If you aren't  
confusing it, please elaborate on what you want to know so we can send  
the doc team to fix it.

regards,

Koen


>>> First, some background.
>>>
>>> The initial port will be getting Sugar[1] to run on the  
>>> Beagleboard[2]
>>> using the Open Embedded[3] toolkit.
>>
>> The basics (sugar, sugar-base, sugar-toolkit, sugar-presence- 
>> services and
>> sugar-artwork) are now running on the beagleboard:
>>
>> http://www.angstrom-distribution.org/sugar-running-ångström
>>
>> To build it using OE: 'bitbake sugar'
>> To install it in angstrom*: 'opkg install sugar'
>>
>> The Glucose pack is missing sugar-datastore (needs a lot of python  
>> modules
>> that aren't in OE yet), etoys (haven't looked at that yet) and  
>> journal
>> (haven't looked at that either).
>> The Fructose pack is completely missing in OE.
>>
>> The remaining tasks for people wanting to work on this are:
>>
>> 1) add OE recipes for needed python-modules
>> 2) add OE recipes for remaining Glucose items
>> 3) add OE recipes for Fructose items
>> 4) build it
>> 5) install resulting packages and run them, see them crash due to  
>> missing
>> python modules, goto 1
>> 6) make screenshots :)
>>
>> regards,
>>
>> Koen
>>
>> * only has armv7a packages at the moment
>> _______________________________________________
>> Sugar mailing list
>> Sugar@lists.laptop.org
>> http://lists.laptop.org/listinfo/sugar
>>
>>
>
>
>
> -- 
> Silent Thunder [ 默雷 / शब्दगर्ज / شبدگر ج ]  
> is my name,
> And Children are my nation.
> The Six Worlds are my dwelling place,
> And Truth my destination.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 193 bytes --]

Re: [sugar] Sugar on the BeagleBoard using the OpenEmbedded toolkit.

[David Farning]

On Wed, 2008-09-03 at 13:14 -0700, Edward Cherlin wrote:
> On Mon, Sep 1, 2008 at 3:57 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> >
> > Op 22 aug 2008, om 02:29 heeft David Farning het volgende geschreven:
> >
> >> Welcome to the Sugar on the BeagleBoard project.  It seems that we have
> >> all of the pieces in place to do a port.
> 
> Very good. Thank you.
> 
> I see that BeagleBoards list at $149. Do you have any idea of quantity
> pricing? Apparently TI sells them only through Digikey, which only
> gives single-unit prices on its site. I can see applications for data
> acquisition and control worldwide, as well as for teaching embedded
> systems development. I am thinking of possibilities for placement of
> systems through microfinance, assuming that we can find and document
> ways to increase income using BeagleBoard+Sugar more efficiently than
> by other methods.

The BeagleBoard is a development platform for introducing developers to
the OMAP35x family of processors.  I don't believe that it was meant for
endusers.  The interesting question I my mind is, 'Who will be the first
to leverage the chipset into low cost thin clients or laptops for use
classrooms?'

thanks
dfarning