Sugar Desktop

Sugar Desktop

[David Farning]

I am wondering if there is interest in creating OE packages for the
Sugar desktop [1].  Development of Sugar, which was originally designed
for the One Laptop Per Child, has been spun off to Sugar Labs.

We are interest in expanding the number of devices which run Sugar.  Our
goals of running on inexpensive, low power machines aligns nicely with
those of embedded devices.

Please let me know if anyone is interested in this type of project.  If
so, I will try to get something started.

thanks
dfarning



1. http://sugarlabs.org/go/Main_Page

Re: Sugar Desktop

[Stefan Schmidt]

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

Hello.

On Tue, 2008-08-19 at 00:04, David Farning wrote:
> I am wondering if there is interest in creating OE packages for the
> Sugar desktop [1].

There is interest. I got a XO laptop from the OLPC Germany at the linuxtag. The
two goals are XO machine support in OE and packages for all kind of sugar
applications. So far I worked on machine support in my small spare time. Machine
is added, kernel compiles and boots fine, something is still worng when booting
the rootfs. Once this is fixed I'll send the patches for review.

> Please let me know if anyone is interested in this type of project.  If
> so, I will try to get something started.

Getting help on the sugar front wuld be great. So I you have someone who would
like to help out here let us know.

regards
Stefan Schmidt

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

Re: Sugar Desktop

[David Farning]

On Tue, 2008-08-19 at 13:13 +0200, Stefan Schmidt wrote:
> Hello.
> 
> On Tue, 2008-08-19 at 00:04, David Farning wrote:
> > I am wondering if there is interest in creating OE packages for the
> > Sugar desktop [1].
> 
> There is interest. I got a XO laptop from the OLPC Germany at the linuxtag. The
> two goals are XO machine support in OE and packages for all kind of sugar
> applications. So far I worked on machine support in my small spare time. Machine
> is added, kernel compiles and boots fine, something is still worng when booting
> the rootfs. Once this is fixed I'll send the patches for review.

As of last week,  OLPC has started working directly with Fedora to make
a native Fedora desktop run on the XO.  I hope this leads to more
upstream interest porting more platforms to the XO.  Currently, OLPC is
working pretty hard to get 8.2 released.  Please remind me in a couple
of weeks (in case I forget) to set up some hardware contacts for you.

> > Please let me know if anyone is interested in this type of project.  If
> > so, I will try to get something started.
> 
> Getting help on the sugar front wuld be great. So I you have someone who would
> like to help out here let us know.
> 

We are working with Jason Kridner from TI about doing a port to the
beagleboard using the OE toolkit.  We are setting up a colobration
infrastructure at http://elinux.org/BeagleBoardSugar .  From an upstream
perspective, is this list and the OE wiki the best places to have
OE/Sugar discussions.

thanks
dfarning

Re: Sugar Desktop

[Stefan Schmidt]

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

Hello.

On Tue, 2008-08-19 at 12:56, David Farning wrote:
> On Tue, 2008-08-19 at 13:13 +0200, Stefan Schmidt wrote:
> > 
> > On Tue, 2008-08-19 at 00:04, David Farning wrote:
> 
> As of last week,  OLPC has started working directly with Fedora to make
> a native Fedora desktop run on the XO.  I hope this leads to more
> upstream interest porting more platforms to the XO.  Currently, OLPC is
> working pretty hard to get 8.2 released.  Please remind me in a couple
> of weeks (in case I forget) to set up some hardware contacts for you.

Made a note. Not sure if this will be really neeed, but having a contact handy
is always good.

> We are working with Jason Kridner from TI about doing a port to the
> beagleboard using the OE toolkit.  We are setting up a colobration
> infrastructure at http://elinux.org/BeagleBoardSugar .  From an upstream
> perspective, is this list and the OE wiki the best places to have
> OE/Sugar discussions.

For discussion the ml is indeed the best place. Wiki is of course fine for
documenting your stuff.

How do you plan to work on OE? Do you have some people with commit rights or do
you plan to do patches? While OE is on its way to git they also set up some
policies for contributions.
http://wiki.openembedded.net/index.php/Category:Policy

I have commit right and can help to get easy patches applied. Bigger changes
like bbclasses or other stuff needs review on the list as I'm not really
familiar with it.

regards
Stefan Schmidt

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

Re: Sugar Desktop

[Koen Kooi]

David Farning wrote:
> I am wondering if there is interest in creating OE packages for the
> Sugar desktop [1].  Development of Sugar, which was originally designed
> for the One Laptop Per Child, has been spun off to Sugar Labs.
>
> We are interest in expanding the number of devices which run Sugar.  Our
> goals of running on inexpensive, low power machines aligns nicely with
> those of embedded devices.

Great! I've started on adding sugar stuff (sugar-toolkit and sugar are 
already in), but then I stumbled across the usual wrong assumptions in 
buildsystems:

sugar-artwork-0.82.0/cursor/cursorthemegen/.libs/lt-cursorthemegen: 
cannot execute binary file

My opterons can't execute ARM code. Could you *please* fix those issues 
upstream so that every sucrose part cross-compiles cleanly?

regards,

Koen

Re: Sugar Desktop

[David Farning]

On Tue, 2008-08-19 at 23:04 +0200, Koen Kooi wrote:
> David Farning wrote:
> > I am wondering if there is interest in creating OE packages for the
> > Sugar desktop [1].  Development of Sugar, which was originally designed
> > for the One Laptop Per Child, has been spun off to Sugar Labs.


> sugar-artwork-0.82.0/cursor/cursorthemegen/.libs/lt-cursorthemegen: 
> cannot execute binary file
> 
> My opterons can't execute ARM code. Could you *please* fix those issues 
> upstream so that every sucrose part cross-compiles cleanly?
> 
Koen,

Would you please file a bug in the tracker at http://dev.laptop.org/ .
We will try to get the situation sorted out.  If You cc me, I will try
to push it along.

thanks
dfarning

Re: Sugar Desktop

[Koen Kooi]

David Farning wrote:
> On Tue, 2008-08-19 at 23:04 +0200, Koen Kooi wrote:
>> David Farning wrote:
>>> I am wondering if there is interest in creating OE packages for the
>>> Sugar desktop [1].  Development of Sugar, which was originally designed
>>> for the One Laptop Per Child, has been spun off to Sugar Labs.
>
>
>> sugar-artwork-0.82.0/cursor/cursorthemegen/.libs/lt-cursorthemegen:
>> cannot execute binary file
>>
>> My opterons can't execute ARM code. Could you *please* fix those issues
>> upstream so that every sucrose part cross-compiles cleanly?
>>
> Koen,
>
> Would you please file a bug in the tracker at http://dev.laptop.org/ .
> We will try to get the situation sorted out.  If You cc me, I will try
> to push it along.

Done: http://dev.laptop.org/ticket/8076

regards,

Koen

Re: Sugar Desktop

[David Farning]

On Thu, 2008-08-21 at 09:42 +0200, Koen Kooi wrote:
> David Farning wrote:
> > Would you please file a bug in the tracker at http://dev.laptop.org/ .
> > We will try to get the situation sorted out.  If You cc me, I will try
> > to push it along.
> 
> Done: http://dev.laptop.org/ticket/8076
> 
> regards,
> 
> Koen

Thanks Koen,

Base on your role in the Open Embedded community, I have ask Marco, our
lead developer, to treat your bugs as blockers to porting Sugar to other
devices.

Until quite recently, we only built for the XO.   Working with others is
not something with which we have a lot of experience.

Thanks
dfarning 

Re: Sugar Desktop

[Koen Kooi]

David Farning wrote:
> I am wondering if there is interest in creating OE packages for the
> Sugar desktop [1].  Development of Sugar, which was originally designed
> for the One Laptop Per Child, has been spun off to Sugar Labs.
>
> We are interest in expanding the number of devices which run Sugar.  Our
> goals of running on inexpensive, low power machines aligns nicely with
> those of embedded devices.

Great! I've started on adding sugar stuff (sugar-toolkit and sugar are 
already in), but then I stumbled across the usual wrong assumptions in 
buildsystems:

sugar-artwork-0.82.0/cursor/cursorthemegen/.libs/lt-cursorthemegen: 
cannot execute binary file

My opterons can't execute ARM code. Could you *please* fix those issues 
upstream so that every sucrose part cross-compiles cleanly?

regards,

Koen