New joyride build 2492

2008-09-29 Thread Build Announcer v2
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2492

Changes in build 2492 from build: 2491

Size delta: 0.00M

-sugar-toolkit 0.82.11-3.olpc3
+sugar-toolkit 0.82.11-4.olpc3

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [sugar] Another pass through some basic Activity test results

2008-09-29 Thread Tomeu Vizoso
On Sun, Sep 28, 2008 at 2:32 AM, Gary C Martin [EMAIL PROTECTED] wrote:
 On 26 Sep 2008, at 19:31, Arjun Sarwal wrote:

 Hi,

 2008/9/26 Gary C Martin [EMAIL PROTECTED]:
 Here's a set of basic Activity test results for build 8.2-763, hope
 the ASCI
 art doesn't get too mangled by the list server (need to view with a
 fixed
   Measure-20 . . - . x x x . x Doesn't sleep when Activity is
 in the
background (eats 75% cpu). Can't
 seem to
record anything. Keep error when

 -- When Measure is in background and some other Activity comes in
 foreground, then Measure releases sound device - you can record sound
 using any other program/application. In this state Measure also
 doesn't hog CPU.

 Just testing with Measure-21 and 8.2-765, yes I see this now. However
 switching to any of the Neighborhood/Group/Home views does not seem
 count as putting Measure into the background, it still consumes the
 cpu and claims the sound input device. I'm guessing this is a Sugar
 behaviour? Is this a bug or a feature (feels like a Sugar bug that
 would make the UI sluggish for no go reason)?

In Sugar, there's always one and only one active activity. You can see
which it is by looking at the icon below the XO in the favorites view
or by looking at the selected activity button in the top frame. This
is the activity that will be brought to the front when you go to the
Activity zoom level.

I'm guessing Measure uses its active activity status to decide if it
should update itself or not, but from earlier emails I think the
desired behavior is rather to stop updating while the activity window
is not visible. For this, the activity author can use the information
that the window manager (or is it X?) provides to each top level
window, in pygtk:

http://pygtk.org/docs/pygtk/class-gtkwidget.html#signal-gtkwidget--visibility-notify-event

Just listen for that signal and check the value of event.state, it can
be one of gtk.gdk.VISIBILITY_FULLY_OBSCURED,
gtk.gdk.VISIBILITY_PARTIAL or gtk.gdk.VISIBILITY_UNOBSCURED. You will
want to stop updating the screen when fully obscured and update it
otherwise.

Faisal, could you please update the almanac with this info?

Thanks,

Tomeu
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Feedback on Measure (was Re: Another pass through some basic Activity test results)

2008-09-29 Thread Tomeu Vizoso
2008/9/29 Erik Blankinship [EMAIL PROTECTED]:

 On Sun, Sep 28, 2008 at 6:02 AM, Gary C Martin [EMAIL PROTECTED]
 wrote:
  On 26 Sep 2008, at 19:31, Arjun Sarwal wrote:
 
  2008/9/26 Gary C Martin [EMAIL PROTECTED]:
 
  Here's a set of basic Activity test results for build 8.2-763, hope
  the
  ASCI
  art doesn't get too mangled by the list server (need to view with a
  fixed
   Measure-20 . . - . x x x . x Doesn't sleep when Activity is in
  the
background (eats 75% cpu). Can't
  seem
  to
record anything. Keep error when
 
  -- When Measure is in background and some other Activity comes in
  foreground, then Measure releases sound device - you can record sound
  using any other program/application. In this state Measure also
  doesn't hog CPU.
 
  Just testing with Measure-21 and 8.2-765, yes I see this now. However
  switching to any of the Neighborhood/Group/Home views does not seem
  count as
  putting Measure into the background, it still consumes the cpu and
  claims
  the sound input device. I'm guessing this is a Sugar behaviour? Is this
  a
  bug or a feature (feels like a Sugar bug that would make the UI sluggish
  for
  no go reason)?

 See #7856. Seems like a Sugar related issue to me. I had borrowed the
 code and concept from Record activity, which now apparently uses some
 other method to determine switch of view/context/activity.( I think
 they detect whether one of the main gtk widgets is the topmost or not
 etc. not sure) I should try exploring that. Any help on this would be
 great.

 Record listens for visibility-notify-event:

 self.playOggWindow.add_events(gtk.gdk.VISIBILITY_NOTIFY_MASK)
 self.playOggWindow.connect(visibility-notify-event, self._visibleNotifyCb)

 Because Record has many different windows, we listen on each window and run
 through a series of checks on the callback to determine if it is the active
 activity anymore.

Oops, just replied with similar information to the old thread, sorry.

Do you need to do that for each window? Why don't you just listen for
that signal in just the main activity window and stop everything when
gtk.gdk.VISIBILITY_FULLY_OBSCURED and resume when otherwise?

Regards,

Tomeu
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: idea for running out of RAM

2008-09-29 Thread Tomeu Vizoso
On Mon, Sep 29, 2008 at 2:07 AM, Walter Bender [EMAIL PROTECTED] wrote:
 So UI changes that help make this clearer will probably be a good idea
 for a 9.1 ... :-/

 There was an early sketch of a mechanism similar to the old Home View
 circle, where there was a space allocated to each open activity
 proportional to the amount of memory it was consuming. In any case, it
 is just as easy to make a bar graph as a pie chart...

Dan Winship explained the issues with this approach here:
http://wiki.laptop.org/go/Activity_ring .

Regards,

Tomeu
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New release8.2 build 764

2008-09-29 Thread Walter Bender
Cute, but unlike the IPhone, the XO has always had an above-the-board
mechanism for unlocking machines. You don't need to go to Hong Kong to
get an unlocked machine, just ask for a key. This thread is about how
to make that process more transparent and comprehensible.

-walter

On Mon, Sep 29, 2008 at 1:28 AM, John Gilmore [EMAIL PROTECTED] wrote:
 many people who would be good testers don't consider themselves 'developers'
 so would not get them on their own.

 Why not call it a tester's key?  It is principally useful for testing
 late-breaking versions.

 Now that the unfortunately popular iPhone ships with the same centralized-
 control model as the XO, there's a new term for a machine that is under
 the full control of its owner:

  Jailbroken

 (http://en.wikipedia.org/wiki/Privilege_escalation or see Jailbreak)
  DRM-encumbered devices such as the Xbox, iPhone and iPod Touch have
  repeatedly been subject to jailbreaks, allowing the execution of
  arbitrary code ...

 So we could call it a jailbreaking key...

John
 ___
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/listinfo/devel




-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Greg Smith's Weekly Report

2008-09-29 Thread Greg Smith
Hi All,

Here's my weekly report for week ending 9/26.

***
Status against last week goals:
1 - Hound engineers to close all 8.2.0 blockers (see
http://dev.laptop.org/report/28) and get a firm date for the Release
Candidate build. Triage bugs and keep the release on schedule.

GS - Done! In the end, no hounding was needed :-) Triaged bugs but fell 
a little behind the incoming rate this week. Also picked and tested
a set of additional activities to add to the G1G1 default install.

2 - Clean up open bugs section of 8.2. release notes. Get release notes
ready for final review.

GS - Mostly done. Top section finished and ready for final review. Human
readable explanation and categorization of key bugs started. Final edits
and comments welcome: http://wiki.laptop.org/go/Release_notes/8.2.0

3 - Write 8.2 launch plan and technical overview presentation.

GS - Not done. Wrote brief blurb on the release for re-use in promoting 
it. Still need to list communication vehicles, choose the right landing 
page (Release notes?) and refine the high level message for the release.

First pass release message:
8.2 has major enhancements including:
- A flexible Home view and Journal with several options for searching 
and organizing activities.
- An enhanced Frame for accessing other XOs and peripherals and for
switching between running activities.
- A Graphical Control Panel for setting language, network, power and
other defaults.
- An automated Software Update tool which finds the latest version of
activities and updates them over the Internet.
- Capability to backup XOs to a school server and restore files to the
Journal as needed.
- A new manual shipped with the XO as an activity.
- Many other bug fixes and enhancements.

For more details, see the final draft of the Release Notes at:
http://wiki.laptop.org/go/Release_notes/8.2.0

4 - Share and post 8.2.1 time frame and operating procedure (e.g. Trac
queries). Start planning for Early Field Trial/Beta of 8.2.1. Keep
pushing for an engineering leader/owner of 8.2.1.

GS - Not done. Pushed for an engineering owner a little but not too hard
until 8.2 is done.

5 - Review and finalize short 9.1 strategy description. Restructure
requirements section to align with strategy. Fold in more deployment
requirements. Keep pushing for an engineering leader/owner of 9.1.
Stretch goal: prepare to write detailed requirements sections and start
scrubbing bugs to create working Trac queries.

GS - Mostly not done. Added a few more details, discussed strategy and
country demands. Added some more detailed requirements for deployability
  at:
http://wiki.laptop.org/go/9.1.0#Security.2C_Activation_and_Deployability

6 - Update deployments page. Update releases page and start using new
semantic format (thanks to S Page for laying out the structure). Also
update XS sections of releases page.

GS - Not done but did get approval to repost statistics on XOs
Delivered, shipped and ordered by country. See also this URL for new
deployment and XO information:

http://wiki.laptop.org/go/Learning_Workshops
Some of this will be integrated in my next update of the Deployments page.

**
Goals for next week in priority order:

1 - Get 8.2 to manufacturing. Catch up on bug triage.

2 - Finish 8.2 Release notes and get final review of them from engineering.

3 - Finalize blurb used to promote the release and start sending it out
to internal lists. Write more generally usable Release message.

4 - Update deployments page and releases page.

5 - Post more detailed 8.2.1 page and restructure 9.1 page.

6 - Once 8.2 ships, open a bottle of Champagne. One glass then start 
work on the next release :-)

Thanks,

Greg S


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Feedback on Measure (was Re: Another pass through some basic Activity test results)

2008-09-29 Thread Erik Blankinship
 Do you need to do that for each window? Why don't you just listen for
 that signal in just the main activity window and stop everything when
 gtk.gdk.VISIBILITY_FULLY_OBSCURED and resume when otherwise?



Full screen modes in Record completely obscure the main activity window.

We don't just listen for visibility events on the video windows because
sometimes these are fully obscured (when transcoding, for example).

Therefore we listen on both the main activity window and the video windows,
and in consultation with the activity's current state (fullscreen, normal,
transcoding), decide if Record is the current activity.

I've never fully understood the rationale for why the sugar api does not
alert activities as to when they are active or not, thereby saving all
activity authors these hassles.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [sugar] Another pass through some basic Activity test results

2008-09-29 Thread Erik Blankinship

 In Sugar, there's always one and only one active activity. You can see
 which it is by looking at the icon below the XO in the favorites view
 or by looking at the selected activity button in the top frame. This
 is the activity that will be brought to the front when you go to the
 Activity zoom level.

 I'm guessing Measure uses its active activity status to decide if it
 should update itself or not, but from earlier emails I think the
 desired behavior is rather to stop updating while the activity window
 is not visible. For this, the activity author can use the information
 that the window manager (or is it X?) provides to each top level
 window, in pygtk:


 http://pygtk.org/docs/pygtk/class-gtkwidget.html#signal-gtkwidget--visibility-notify-event

 Just listen for that signal and check the value of event.state, it can
 be one of gtk.gdk.VISIBILITY_FULLY_OBSCURED,
 gtk.gdk.VISIBILITY_PARTIAL or gtk.gdk.VISIBILITY_UNOBSCURED. You will
 want to stop updating the screen when fully obscured and update it
 otherwise.

 Faisal, could you please update the almanac with this info?


The basics of this idea are in the almanac:

http://wiki.laptop.org/go/Sugar_Almanac#How_do_I_know_when_my_activity_is_.22active.22_or_not.3F
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Feedback on Measure (was Re: Another pass through some basic Activity test results)

2008-09-29 Thread Tomeu Vizoso
On Mon, Sep 29, 2008 at 2:47 PM, Erik Blankinship [EMAIL PROTECTED] wrote:

 Do you need to do that for each window? Why don't you just listen for
 that signal in just the main activity window and stop everything when
 gtk.gdk.VISIBILITY_FULLY_OBSCURED and resume when otherwise?


 Full screen modes in Record completely obscure the main activity window.

 We don't just listen for visibility events on the video windows because
 sometimes these are fully obscured (when transcoding, for example).

 Therefore we listen on both the main activity window and the video windows,
 and in consultation with the activity's current state (fullscreen, normal,
 transcoding), decide if Record is the current activity.

 I've never fully understood the rationale for why the sugar api does not
 alert activities as to when they are active or not, thereby saving all
 activity authors these hassles.

Well, the Sugar API alerts activities when they are the active
activity (SetActive method in the dbus service), but it has a
different meaning that being visible (see my earlier email from
today). For visibility, the X stuff already provides all that is
needed and though we would like to make activity author's life as
simple as possible, properly maintaining an API is something very
expensive and we just don't have the resources for now.

Faisal's work is the best that we have right now regarding activity
author support.

Regards,

Tomeu
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [sugar] Feedback on Measure (was Re: Another pass through some basic Activity test results)

2008-09-29 Thread Erik Garrison
On Mon, Sep 29, 2008 at 08:47:36AM -0400, Erik Blankinship wrote:
  Do you need to do that for each window? Why don't you just listen for
  that signal in just the main activity window and stop everything when
  gtk.gdk.VISIBILITY_FULLY_OBSCURED and resume when otherwise?
 
 
 
 Full screen modes in Record completely obscure the main activity window.
 
 We don't just listen for visibility events on the video windows because
 sometimes these are fully obscured (when transcoding, for example).
 
 Therefore we listen on both the main activity window and the video windows,
 and in consultation with the activity's current state (fullscreen, normal,
 transcoding), decide if Record is the current activity.
 
 I've never fully understood the rationale for why the sugar api does not
 alert activities as to when they are active or not, thereby saving all
 activity authors these hassles.

Is there any particular reason why Record does not use a single window?

Erik
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


[Fwd: 8.2.0 blockers stats and status]

2008-09-29 Thread Mel Chua
Whoops - should have sent this to the lists as well. All of these stats 
are public and grabbed from Trac.

 Original Message 
Subject:8.2.0 blockers stats and status
Date:   Mon, 29 Sep 2008 07:40:36 -0400
From:   Mel Chua [EMAIL PROTECTED]
Organization:   One Laptop Per Child
To: Greg Smith [EMAIL PROTECTED], Kimberley Quirk [EMAIL PROTECTED], 
Joseph Feinstein [EMAIL PROTECTED], Frances Hopkins [EMAIL PROTECTED], 
Ed McNierney [EMAIL PROTECTED], Mel Chua [EMAIL PROTECTED]



Morning, everyone!

If you look at http://dev.laptop.org/report/28 you'll notice that there 
are now 29 primary or secondary blockers for 8.2.0 (1 is a repeat). This 
is pretty good. We're down something like 50% from before this weekend.

Here is the status on 8.2.0 blockers as of this moment. I welcome ideas 
on how to make this list more legible (or better yet, automatically 
generated by Trac or similar):

--
things that would need to be in release notes as of right now - 13 
total, or 45%
--

Not fixed at all (cannot test because there is no fix, still open): 
7845, 8558, 8493, 7818, 7579, 7893, 7972, 7932, 8674 (9 total)

Recently reopened: 7426, 7764 (2 total)

We think they're fixed, but we can't test them now: 8394 [probably 
fixed, but presence service bugs prevent verification the memory leak is 
gone], 7837 [waiting for final release candidate] (2 total)

--
things that hopefully don't need to be in release notes, but need 
checking by someone else, or more time - 16 total, or 55%
--

We think they're fixed, somebody else can test them, but Mel can't: 
7269, 7587, 7588, 7921, 8487 [Language/keyboard/i18n/NAND-full, kimquirk 
to test - Mel would like to watch and learn how if possible] and 6930, 
4265 [licensing issues] (7 total)

We think they're fixed, the tests take a long time and are still 
running: 7879 [extreme power management; we should know by Tuesday 
morning] (1 total)

Tests still outstanding: 8281, 8372, 5428, 8369, 8376 [connectivity 
issues at 1cc this weekend, or new fix posted recently that I haven't 
gotten a chance to test yet] and 8510, 8106, 8300 [I think we can test 
these, but I'm not sure how yet, need to talk with devels] (8 total) - I 
am working on these today.

--
things that do not have to go into release notes at all - a.k.a. the 
happy list
--

We know they're fixed, verified fixed and closed (no longer on the 
blockers list - note that I might be missing closed bugs from this list 
but that's ok because we don't need to worry about them any more): 8149, 
8307, 8287, 8234, 7733, 8318, 8436, 7480, 8062, 8089, 8375, 8395, 8361, 
8354 (14 total)

-- 
Mel Chua
QA/Support Engineer
[EMAIL PROTECTED]

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [sugar] Feedback on Measure (was Re: Another pass through some basic Activity test results)

2008-09-29 Thread Erik Blankinship

 Is there any particular reason why Record does not use a single window?



Record's GUI overlays widgets on top of video windows.

This is how we create the picture in a picture effect (using XV in a
window) and also how we add the fullscreen toggle button.  GTK doesn't play
well with overlapping widgets -- gtk.Fixed() doesn't guarantee Z-order.  So
we use a stack of gtk.Windows without decoration.

Unfortunately, when we put xv video into a widget (e.g. gtk.DrawingArea with
a gstreamer xvimagesink) into a gtk.Fixed, that widget's video always
displays on top of other widgets, regardless of its z-order.

It was recommended at one point to create a new version of gtk.Fixed that
guarantees z-order, but the use of gtk.Window was well underway and works.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


#7788 Touchpad behavior, [was 8.2.0 blockers stats and status]

2008-09-29 Thread Ton van Overbeek
What about #7788 (Worse touchpad behavior in 8.2).
It is still there even in 8.2-765, at least on my XO-1.
I am not the only one seeing this, Daniel Drake (dsd) complained about this
while developing the bridge activity in the physics jam and I have also seen
other mails on the list.
My hunch is that somehow the EC and the kernel psmouse code get out of sync
since it always starts OK after boot, but then deteriorates later.

There is no reason to block the release for this, but I believe something
about this should be mentioned in the release notes.

Ton van Overbeek
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Major differences between releases

2008-09-29 Thread Morgan Collett
On Sun, Sep 28, 2008 at 21:43, C. Scott Ananian [EMAIL PROTECTED] wrote:
 On Sun, Sep 28, 2008 at 2:56 PM, Bert Freudenberg [EMAIL PROTECTED] wrote:
 I think it would be a good idea for everyone (activity authors in
 particular) to cross-check the changes in what packages are included
 in the new stable release, in particular what packages are *going away*:

http://dev.laptop.org/~bert/update.1-8.2.html

 That list is slightly misleading, as it includes several cases where
 two packages were folded into one or a package was renamed.

 Others changes are inherited from the F7-F9 transition -- does anyone
 know if Fedora documents API changes between releases of Fedora?

 Also, is there any chance someone will take on

http://dev.laptop.org/ticket/4695
(Document API changes between Ship.1 and Update.1 and 8.2)

 after the release before working on the next one?

 I did see an email from morgs recently mentioning his interest in
 documenting sugar API changes?

Heh, I did volunteer to broadcast known API changes far and wide, but
I'll take a look at Sugar API changes as I'm aware of a few of those.
(Don't let that stop anyone else from looking into other APIs though!)

Regards
Morgan
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


New joyride build 2494

2008-09-29 Thread Build Announcer v2
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2494

Changes in build 2494 from build: 2493

Size delta: -0.13M

-libxml2-python 2.7.1-1.fc9
+libxml2-python 2.6.32-3.fc9
-olpc-utils 0.87-1.olpc3
+olpc-utils 0.87-2.olpc3
-libxml2 2.7.1-1.fc9
+libxml2 2.6.32-3.fc9

--- Changes for libxml2 2.6.32-3.fc9 from 2.7.1-1.fc9 ---
  + upstream release of 2.7.1
  + fix python serialization which was broken in 2.7.0
  + upstream release of 2.7.0
  + switch to XML 1.0 5th edition
  + switch to RFC 3986 for URI parsing
  + better entity handling
  + option to remove hardcoded limitations in the parser
  + more testing
  + a new API to allocate entity nodes
  + and lot of fixes and cleanups

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: semantic black ops for Activities? (Re: Greg Smith's Weekly Report)

2008-09-29 Thread Bobby Powers
On Sun, Sep 28, 2008 at 3:47 AM, S Page [EMAIL PROTECTED] wrote:
 Hey activity maintainers,

 I shrank the wasteful junky layout slightly and got rid of all the
 warning triangles for empty values.  If you see any yellow triangles
 after updating your activity page, please let me know.

thanks a lot, the wiki has been looking pretty sharp these days :)

bobby

 The Template:Activity_page could omit altogether table rows that have no
 value.  That would shrink it further but you'd lose the reminder to fill
 in Related projects, Contributors, etc.  Speak up if you want empty rows
 omitted.

 Gary C Martin wrote:
 I think the main weird oddity I see now is that every activity page now
 using the new for has two blocks of apparently duplicate data showing,
 very confusing. There's a nicely formatted table at the very bottom
 (Facts about Moon),

 That's the factbox you see on pages with semantic info.  (Since it
 repeats info that's annotated somewhere else on the page, the newer
 version of Semantic MediaWiki hides it by default.)

  but before it is a great long ~page screed of the
 same data in a wasteful junky layout (Activity Summary).

 --
 =S Page   user:skierpage
 ___
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/listinfo/devel

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: rendering test

2008-09-29 Thread Jordan Crouse
On 28/09/08 18:46 +0200, Bernie Innocenti wrote:
 Tomeu Vizoso wrote:
  Ooops. cc'ing to some other people/list in the hope someone more
  knowledgeable than me will comment.
 
 Thanks.  Please Cc me on posts like these to make sure I don't miss them. 
   No, it doesn't bother me to receive 0.001% more mail.
 
 I've also Cc'd the Xorg list in case someone can give us more insight.
 
 
  On Sun, Sep 28, 2008 at 12:46 PM, Riccardo Lucchese
  [EMAIL PROTECTED] wrote:
  On Sun, 2008-09-28 at 12:43 +0200, Riccardo Lucchese wrote:
  * build 703, xorg driver = amd, redraws = 200
  - pixbuf:
98.63s
96.96s
96.58s
97.14s
99.21s
 
  * build 703, xorg driver = fbdev, redraws = 200
  - pixbuf:
55.81s
55.40s
55.22s
55.50s
55.63s
 
  * build 2489, xorg driver = amd, redraws = 200
  - pixbuf:
84.21s
84.81s
81.94s
81.79s
85.29s
 
  * build 2489, xorg driver = fbdev, redraws = 200
  - pixbuf:
62.83s
62.81s
62.81s
62.66s
63.14s
 
  - joyride regressed sensibly at rendering with cairo since 703
  - rendering pixbufs is extremely slow on the xo
  - server side surfaces are awesome ;)
 
  and btw why is fbdev faster than the geode driver at rendering pixbufs ?
 
 Was fbdev running with EXA or XAA?  (does fbdev even support EXA?)
 
 My performance tests with X 1.3 and 1.4 had shown that turning on EXA 
 makes many operations slower.  It's hard to tell why, but it might have to 
 do with loosing XShmPut() (MIT shared memory), excessive migration of 
 pixmaps to the framebuffer, and so on.  X 1.5 was supposed to have a much 
 better EXA, at least judging from the stream of patches landed on the tree.

Indeed - migration is probably what is hurting us the most here.   We 
would probably have to do a more in-depth analysis of what is actually
happening in the engine, but the general rule of thumb is that it is very
very very very very bad to read from the video memory. 

Jordan

(Did I mention it was bad?)

-- 
Jordan Crouse
Systems Software Development Engineer 
Advanced Micro Devices, Inc.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: #7788 Touchpad behavior, [was 8.2.0 blockers stats and status]

2008-09-29 Thread [EMAIL PROTECTED]
I noticed over the weekend that the touchpad is very jumpy in 765.  
Never really had any problems with touchpad previously.

On Sep 29, 2008, at 7:02 AM, Ton van Overbeek wrote:

 What about #7788 (Worse touchpad behavior in 8.2).
 It is still there even in 8.2-765, at least on my XO-1.
 I am not the only one seeing this, Daniel Drake (dsd) complained  
 about this
 while developing the bridge activity in the physics jam and I have  
 also seen
 other mails on the list.
 My hunch is that somehow the EC and the kernel psmouse code get out  
 of sync
 since it always starts OK after boot, but then deteriorates later.

 There is no reason to block the release for this, but I believe  
 something
 about this should be mentioned in the release notes.

 Ton van Overbeek
 ___
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/listinfo/devel

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


New joyride build 2495

2008-09-29 Thread Build Announcer v2
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2495

Changes in build 2495 from build: 2494

Size delta: 0.13M

-olpc-library-common 1-28
+olpc-library-common 1-29

--- Changes for olpc-library-common 1-29 from 1-28 ---
  + updated common to include wiki searchbar and devkey/release-notes links
  + removing core from /usr/share, moving to customization key
  + separated the two searchbars visually and with icons
  + made the laptop search more useful (all of laptop.org)

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Signed candidate-765 and gg-765-2 builds available for testing.

2008-09-29 Thread Carlo Falciola
I did not worked for me:
I've a G1G1 without developer  key, already updated to 711. 
I just tried to olpc-update via USB picking up the 765 from the link available 
from wiki. 
After a long run, the olpc-update command  terminated with a message like:
update aborted: need a development key...
 
I've to admit I'm a bit confused by abundance of docs/versions :-)

ciao carlo 



  Scopri il blog di Yahoo! Mail:
Trucchi, novità e la sua opinione.
http://www.ymailblogit.com/blog
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [sugar] rendering test

2008-09-29 Thread Riccardo Lucchese
On Mon, 2008-09-29 at 09:08 -0600, Jordan Crouse wrote:
 On 28/09/08 18:46 +0200, Bernie Innocenti wrote:
  Tomeu Vizoso wrote:
   Ooops. cc'ing to some other people/list in the hope someone more
   knowledgeable than me will comment.
  
  Thanks.  Please Cc me on posts like these to make sure I don't miss them. 
No, it doesn't bother me to receive 0.001% more mail.
  
  I've also Cc'd the Xorg list in case someone can give us more insight.
  
  
   On Sun, Sep 28, 2008 at 12:46 PM, Riccardo Lucchese
   [EMAIL PROTECTED] wrote:
   On Sun, 2008-09-28 at 12:43 +0200, Riccardo Lucchese wrote:
   * build 703, xorg driver = amd, redraws = 200
   - pixbuf:
 98.63s
 96.96s
 96.58s
 97.14s
 99.21s
  
   * build 703, xorg driver = fbdev, redraws = 200
   - pixbuf:
 55.81s
 55.40s
 55.22s
 55.50s
 55.63s
  
   * build 2489, xorg driver = amd, redraws = 200
   - pixbuf:
 84.21s
 84.81s
 81.94s
 81.79s
 85.29s
  
   * build 2489, xorg driver = fbdev, redraws = 200
   - pixbuf:
 62.83s
 62.81s
 62.81s
 62.66s
 63.14s
  
   - joyride regressed sensibly at rendering with cairo since 703
   - rendering pixbufs is extremely slow on the xo
   - server side surfaces are awesome ;)
  
   and btw why is fbdev faster than the geode driver at rendering pixbufs ?
  
  Was fbdev running with EXA or XAA?  (does fbdev even support EXA?)
  
  My performance tests with X 1.3 and 1.4 had shown that turning on EXA 
  makes many operations slower.  It's hard to tell why, but it might have to 
  do with loosing XShmPut() (MIT shared memory), excessive migration of 
  pixmaps to the framebuffer, and so on.  X 1.5 was supposed to have a much 
  better EXA, at least judging from the stream of patches landed on the tree.
 
 Indeed - migration is probably what is hurting us the most here.   We 
 would probably have to do a more in-depth analysis of what is actually
 happening in the engine, but the general rule of thumb is that it is very
 very very very very bad to read from the video memory. 
 

Timings with X 1.5 (I picked up the most recent package I could find on
koji for fc9) don't change at all.

riccardo

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


New joyride build 2497

2008-09-29 Thread Build Announcer v2
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2497

Changes in build 2497 from build: 2495

Size delta: 0.00M

-olpc-library-common 1-29
+olpc-library-common 1-21

--- Changes for olpc-library-common 1-21 from 1-29 ---
  + updated common to include wiki searchbar and devkey/release-notes links
  + removing core from /usr/share, moving to customization key
  + separated the two searchbars visually and with icons
  + made the laptop search more useful (all of laptop.org)

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New joyride build 2497

2008-09-29 Thread Bobby Powers
On Mon, Sep 29, 2008 at 4:13 PM, Build Announcer v2 [EMAIL PROTECTED] wrote:
 http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2497

 Changes in build 2497 from build: 2495

 Size delta: 0.00M

 -olpc-library-common 1-29
 +olpc-library-common 1-21

any reason for the large version drop?

 --- Changes for olpc-library-common 1-21 from 1-29 ---
  + updated common to include wiki searchbar and devkey/release-notes links
  + removing core from /usr/share, moving to customization key
  + separated the two searchbars visually and with icons
  + made the laptop search more useful (all of laptop.org)

 --
 This mail was automatically generated
 See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
 See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
 comparison
 ___
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/listinfo/devel

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New joyride build 2497

2008-09-29 Thread Samuel Klein
A changelog quirk.  the next joyride should have 1-30.

On Mon, Sep 29, 2008 at 5:31 PM, Bobby Powers [EMAIL PROTECTED] wrote:
 On Mon, Sep 29, 2008 at 4:13 PM, Build Announcer v2 [EMAIL PROTECTED] wrote:
 http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2497

 Changes in build 2497 from build: 2495

 Size delta: 0.00M

 -olpc-library-common 1-29
 +olpc-library-common 1-21

 any reason for the large version drop?

 --- Changes for olpc-library-common 1-21 from 1-29 ---
  + updated common to include wiki searchbar and devkey/release-notes links
  + removing core from /usr/share, moving to customization key
  + separated the two searchbars visually and with icons
  + made the laptop search more useful (all of laptop.org)

 --
 This mail was automatically generated
 See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
 See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
 comparison
 ___
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/listinfo/devel

 ___
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/listinfo/devel

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New joyride build 2497

2008-09-29 Thread Samuel Klein
(I got a changelog warning when it wasn't picked up but didn't see it
right away.) SJ

On Mon, Sep 29, 2008 at 5:36 PM, Samuel Klein [EMAIL PROTECTED] wrote:
 A changelog quirk.  the next joyride should have 1-30.

 On Mon, Sep 29, 2008 at 5:31 PM, Bobby Powers [EMAIL PROTECTED] wrote:
 On Mon, Sep 29, 2008 at 4:13 PM, Build Announcer v2 [EMAIL PROTECTED] 
 wrote:
 http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2497

 Changes in build 2497 from build: 2495

 Size delta: 0.00M

 -olpc-library-common 1-29
 +olpc-library-common 1-21

 any reason for the large version drop?

 --- Changes for olpc-library-common 1-21 from 1-29 ---
  + updated common to include wiki searchbar and devkey/release-notes links
  + removing core from /usr/share, moving to customization key
  + separated the two searchbars visually and with icons
  + made the laptop search more useful (all of laptop.org)

 --
 This mail was automatically generated
 See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate 
 logs
 See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
 comparison
 ___
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/listinfo/devel

 ___
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/listinfo/devel


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: idea for running out of RAM

2008-09-29 Thread Jim Gettys
Note that more current Linux kernels, such as that in 8.2, are much
better at being able to account for what process is using what memory.
It's probably worth a little experimentation after 8.2 ships to see if
the original concept is now viable.
   - Jim


On Mon, 2008-09-29 at 10:06 +0200, Tomeu Vizoso wrote:
 On Mon, Sep 29, 2008 at 2:07 AM, Walter Bender [EMAIL PROTECTED] wrote:
  So UI changes that help make this clearer will probably be a good idea
  for a 9.1 ... :-/
 
  There was an early sketch of a mechanism similar to the old Home View
  circle, where there was a space allocated to each open activity
  proportional to the amount of memory it was consuming. In any case, it
  is just as easy to make a bar graph as a pie chart...
 
 Dan Winship explained the issues with this approach here:
 http://wiki.laptop.org/go/Activity_ring .
 
 Regards,
 
 Tomeu
 ___
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/listinfo/devel
-- 
Jim Gettys [EMAIL PROTECTED]
One Laptop Per Child

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


New joyride build 2498

2008-09-29 Thread Build Announcer v2
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2498

Changes in build 2498 from build: 2497

Size delta: 0.00M

-olpc-library-common 1-21
+olpc-library-common 1-30

--- Changes for olpc-library-common 1-30 from 1-21 ---
  + updated common to include wiki searchbar and devkey/release-notes links
  + separated the two searchbars visually and with icons
  + made the laptop search more useful (all of laptop.org)

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: What is the URL of the community-created G1G1 QA database?

2008-09-29 Thread Bastien
Mel Chua [EMAIL PROTECTED] writes:

 (Moving to devel at Wad's request, ccing support-gang as they're likely 
 to know the URL that I'm referring to.)

 Brian (currently at the Rwanda deployment) suggested a knowledgebase for 
 XO troubleshooting - iirc, a knowledgebase was started by a volunteer 
 during the G1G1 last year. It was not a forum, it was not a wiki or a 
 chat... interface-wise, it reminded me a little bit of digg. The front 
 page listed common QAs on XO usage, and people could post new questions 
 (and answer-responses to said questions). I think that they were 
 ranked/sorted by popularity or maybe some sort of vote.

 This is a terrible description, but does anybody know the URL of what 
 I'm talking about? See below thread for more context. Feedback on how it 
 worked and how v.2.0 could be improved (and whether such a thing would 
 actually be most useful - maybe there's a better solution) would be 
 great as well.

Maybe something like Stack Overflow?

  http://stackoverflow.com/

Or maybe tags could group XO|Sugar-related questions on Stack Overflow?

-- 
Bastien
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


New joyride build 2499

2008-09-29 Thread Build Announcer v2
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2499

Changes in build 2499 from build: 2498

Size delta: 0.00M

-libxml2-python 2.6.32-3.fc9
+libxml2-python 2.7.1-1.fc9
-olpc-utils 0.87-2.olpc3
+olpc-utils 0.89-1.olpc3
-dhclient 12:4.0.0-17.fc9
+dhclient 12:4.0.0-18.fc9
-dhcp 12:4.0.0-17.fc9
+dhcp 12:4.0.0-18.fc9
-libxml2 2.6.32-3.fc9
+libxml2 2.7.1-1.fc9
-squeak-vm 3.10-3olpc10
+squeak-vm 3.10-3olpc11

--- Changes for libxml2 2.7.1-1.fc9 from 2.6.32-3.fc9 ---
  + upstream release of 2.7.1
  + fix python serialization which was broken in 2.7.0
  + upstream release of 2.7.0
  + switch to XML 1.0 5th edition
  + switch to RFC 3986 for URI parsing
  + better entity handling
  + option to remove hardcoded limitations in the parser
  + more testing
  + a new API to allocate entity nodes
  + and lot of fixes and cleanups

--- Changes for squeak-vm 3.10-3olpc11 from 3.10-3olpc10 ---
  + fix pgUp/pgDown keys (#8536)
  + fix view-source key (#8700)

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


New release8.2 build 766

2008-09-29 Thread Build Announcer v2
http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/build766

Changes in build 766 from build: 765

Size delta: 0.00M

-sugar-update-control 0.15-1
+sugar-update-control 0.17-1
-olpc-utils 0.87-1.olpc3
+olpc-utils 0.89-1.olpc3
-sugar 0.82.9-1.olpc3
+sugar 0.82.9-2.olpc3
-sugar-toolkit 0.82.11-3.olpc3
+sugar-toolkit 0.82.11-4.olpc3

--- Changes for sugar-update-control 0.17-1 from 0.15-1 ---
  + Trac #7845, #8681: don't die if ~/Activities doesn't exist.
  + Filter out library/library.info when it's not in the root directory

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/release8.2-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Activity resume issues (was Re: twenty issues with Paint activity)

2008-09-29 Thread S Page
The double-clicking problem sounds like 
http://dev.laptop.org/ticket/7876 , Double clicking an activity in the 
home ring causes 2 instances to launch.

I get different results from different apps, e.g. click Memorize three 
times, get three icons for three working instances, no doubled menus, 
and two gray circles.  Paint doesn't give me the gray circles.


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Signed candidate-765 and gg-765-2 builds available for testing.

2008-09-29 Thread S Page
Carlo Falciola wrote:
 I did not worked for me:
 I've a G1G1 without developer  key, already updated to 711. 
 I just tried to olpc-update via USB picking up the 765 from the link 
 available from wiki. 

You didn't tell us the exact command you typed, but the link on the 
wiki has been 8.2-765, which isn't signed, hence the error message 
you got.

Please retry with
   sudo olpc-update candidate-765

and let everyone know.  Thanks indeed, you may be the first without a 
developer key to try it!

--
=S Page   user:skierpage
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: New release8.2 build 766

2008-09-29 Thread C. Scott Ananian
On Mon, Sep 29, 2008 at 8:33 PM, Build Announcer v2 [EMAIL PROTECTED] wrote:
 http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/build766


Full changelog at:
 http://dev.laptop.org/git?p=projects/pilgrim;a=shortlog;h=8.2
 http://mock.laptop.org/gitweb/?p=repos;a=shortlog;h=koji.dist-olpc3-testing
 http://mock.laptop.org/gitweb/?p=repos;a=shortlog;h=local.8.2
 http://dev.laptop.org/git?p=olpc-2.6;a=shortlog;h=testing

Summary changelog from my notes:

#7845: Software update after clean install
 sugar-update-control-0.17
#8674: Installing bundles wipes out ~/Activities
 sugar-toolkit 0.82.11-4.olpc3
 pilgrim 9e6f61ba1b7ea471f1d4204d051035840bbf0cf1
#7932: Emergency NAND-full cleanup script doesn't work on secured machines
 olpc-utils 0.89-1.olpc3
#8711: Sugar CPU 'leak'
 sugar 0.82.9-2.olpc3
#8580: Record-57 doesn't keep pictures
 Record-59
#8691: Wikibooks and Help content bundle update
 Wikibooks-8
 Help-10

See http://wiki.laptop.org/go/Release_notes/8.2.0/Changelog for all
release manager's changelogs since 759.
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Stability and Memory Pressure in 8.2

2008-09-29 Thread S Page
On September 8th, Michael Stone wrote:
 Kim, Greg, and I have concluded that the instability we experience under
 memory-pressure in 8.2-759 and similar is the single hard issue that
 we wish to _attempt_ to address before releasing 8.2 on current
 timeframes.

How did it go?

I was going through my journal in 8.2-763.  Browse and Paint open, 
accidentally started Read, suddenly the cursor stopped moving and XO 
completely unresponsive.  I assume it's memory, but we never learned how 
to tell.

Over two minutes later the first page of the PDF appeared and *then* 
immediately Sugar restarted.

Just one datapoint.
Yours sincerely,
--
=S Page
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: idea for running out of RAM

2008-09-29 Thread Albert Cahalan
On Mon, Sep 29, 2008 at 6:04 PM, Jim Gettys [EMAIL PROTECTED] wrote:

 Note that more current Linux kernels, such as that in 8.2, are much
 better at being able to account for what process is using what memory.
 It's probably worth a little experimentation after 8.2 ships to see if
 the original concept is now viable.

I think a memory usage pie graph is beyond excellent.
I'm not so sure it should show current usage though.

It probably should show maximum expected usage,
based on previous behavior and/or RAM reservations.

The point of a pie display is to show the user how much
of the machine is occupied. If an activity is using 12 MB
now but will likely need 34 MB, then that extra 22 MB is
definitely not available for running other stuff.

Things work out nicely this way. The user can see why
the OS is refusing to let him start more activities. The
minimum activity size (for the icon) is no problem; it is
simply the minimum RAM reservation.

If the pie graph is exclusively based on RAM reservation,
then there isn't even any need to mess with /proc data.

An interesting extension of the idea would be to mark
activity icons (or their hover menus) with pie fragments.
This would let the user know in advance if an activity
would be unstartable, and would let the user know how
much he needs to free up to resolve that.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: idea for running out of RAM

2008-09-29 Thread Hal Murray

 I think a memory usage pie graph is beyond excellent. I'm not so sure
 it should show current usage though. 

I'm assuming that each activity gets allocated a chunk of the pie 
corresponding to how much memory it asks for.

How about using part of the circle to show the fraction of memory allocated 
but not used yet?  Say by using the circle from 1-inch dia to 1.25 inch dia.

I can think of two ways to do this.

One would adjust the shading in each activities portion of the circle.  White 
for not used and black for used.  (Red for over allocation?)

The other would be to use the applications chunk of the circle as a pie 
shaped bar graph.  The black section would show what % of the allocated 
memory was currently in use.


-- 
These are my opinions, not necessarily my employer's.  I hate spam.



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel