Re: [Sugar-devel] Error on Write activity: no module named abiword

2014-07-18 Thread Daniel Drake
On Thu, Jul 17, 2014 at 9:21 PM, Gonzalo Odiard godi...@sugarlabs.org wrote:

 Do you have a abiword rpm with introspection enabled?
 Hint: we use a custom rpm

 http://harvest.one-education.org/public/au1b-updates/RPMS/abiword-2.9.3-1.git20121011.fc18.olpc12.armv7hl.rpm

The error that he's seeing suggests that the activity isn't trying to
use introspection

from abiword import Canvas

so maybe the problem is that the Write version is too old?
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: gnome applet can't initialize Clutter

2014-05-10 Thread Daniel Drake
Hi Scott,

On Sat, May 10, 2014 at 11:55 AM, Scott Chapman sc...@mischko.com wrote:
 We don't have opengl support in the X drivers because of the video type on
 these?

There is indeed a GPU capable of 3D graphics in the hardware, but we
never completed the engineering effort required to make
OpenGL/OpenGLES work in our software offering. We did try, but it was
hard and the closed-source nature of the drivers made our lives
unreasonably difficult, it was not our top priority, and we did not
get it working right. Sorry about that.

 I wonder why OLPC published a build with Gnome if it is this broken?

Any complex desktop product is going to have software bugs, and sadly
it seems like you ran into one. However, outside of this limitation, I
think you'll find that our minimal GNOME environment mostly works.

Bluetooth is indeed a bit unexplored on this platform. During XO-4
development we did the necessary hardware and driver work, but did not
have many resources to devote to offering a bluetooth user experience
- this was planned to be addressed in a future software development
cycle, and/or by OLPC's customers who were requesting bluetooth at a
hardware level.

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


Re: gnome applet can't initialize Clutter

2014-05-10 Thread Daniel Drake
On Sat, May 10, 2014 at 12:40 PM, Scott Chapman sc...@mischko.com wrote:
 Paul,
 The Gnome Control Panel is not present in the build.  Am I missing something
 or is it left out also?

You aren't missing anything - based on feedback from OLPC's
deployments we always tried to ship a minimal GNOME environment
without too much configuration.

You are welcome to make your own changes to add more bits, but
unfortunately the control center will not work for the same reason as
the bluetooth applet, mentioned at
http://wiki.laptop.org/go/Release_notes/13.2.0#GNOME

 How do you edit the menu system in Gnome without it, etc?

Looking at the gnome control center on my non-XO laptop I don't really
see any menu configuration options there. Really the menu contents are
defined automatically by the apps that are installed.

But GNOME does indeed have some underlying configuration which can
affect the appearance. If you clarify exactly what you're trying to
do, maybe someone will check if it is possible and if so, look up the
exact gconf/gsettings command invocation for you.

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


Re: XO on Fedora 20 (was Re: [Sugar-devel] [GSoC] Porting To Python3)

2014-05-09 Thread Daniel Drake
On Wed, May 7, 2014 at 9:01 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
 On 7 May 2014 01:44, James Cameron qu...@laptop.org wrote:

 On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote:
  [...] And with the XO stuck on Fedora 18 we might not have good
  enough introspection to make the port compatible with it.

 If anybody would like to work on moving olpc-os-builder to something
 more recent, feel free.  It isn't something OLPC is looking at right
 now, but it would be helpful to the users.

 Not the die hard 0.98 users, of course.  ;-)


 I'm giving that a try. I was able to build a Fedora 20 image for XO 1.5

 https://github.com/dnarvaez/olpc-os-builder

olpc-os-builder git master also has F20 support, as of a few months
ago. Can't remember how good the result was.

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


XO-1.75 early boot codes

2014-01-08 Thread Daniel Drake
Hi,

When booting the XO-1.75 with the check key pressed, 2-digit boot
codes fill the screen briefly before OFW boots the system.

Can anyone remind me where these numbers are defined in the code? I
know it's in cforth git somewhere...

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


Re: The mouse touch pad doesn't work on XO4

2013-12-21 Thread Daniel Drake
On Tue, Dec 17, 2013 at 7:50 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
 On Tue, Dec 17, 2013 at 4:07 AM, Basanta Shrestha
 basanta.shres...@olenepal.org wrote:
 yes it works! But the value goes back to original ie. '1' after reboot and
 /etc/rc.local doesn't work here.

 It works, but it will get overridden by olpc-configure which runs later.

I don't think /etc/rc.local does work. The correct path is /etc/rc.d/rc.local

 Change olpc-configure, or run your fixup after olpc-configure.

The mouse setup is done by udev.
/lib/udev/olpc_mouse_setup

rc.local will probably run after this is done but that may not be guaranteed.

If that turns out to be unreliable, the write to disable_gesture could
be done in olpc_mouse_setup after this line:

  echo -n SynRelPS/2  $protocol_path

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


Re: Using a new keyboard layout for XO4

2013-12-14 Thread Daniel Drake
Hi Basanta,

On Thu, Nov 21, 2013 at 4:27 AM, Basanta Shrestha
basanta.shres...@olenepal.org wrote:
 Dear all,
 We are planing on using a different keyboard layout for XO4. The new layout 
 we think is phonetically based and easier for children. I simply switched the 
 /usr/share/X11/symbols/np file with a new one but did not work. I guess there 
 are some other works that needs to be done before we can use this file. Can 
 you suggest what needs to be done?

Yeah, it's not quite that simple. You need to leave the interaction
with the OLPC mode/variant in place. Add the following lines to the
end of the file:

partial alphanumeric_keys
xkb_symbols olpc {
  include np
  include group(olpc)
};

Now it should work.

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


Re: The mouse touch pad doesn't work on XO4

2013-12-13 Thread Daniel Drake
On Fri, Dec 13, 2013 at 4:49 AM, Basanta Shrestha
basanta.shres...@olenepal.org wrote:
 Its SynRelPS/2

 And I created file /etc/modprobe.d/olpc-psmouse.conf with line
 options psmouse proto=bare taptoclick=1

 But it altogether made my touchpad to stop functioning.

Looks like that wiki page is out of date for recent software releases.

Should be possible to change this by tweaking the value in the
disable_gesture file in /sys.
find /sys -name disable_gesture

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


Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4

2013-11-13 Thread Daniel Drake
On Tue, Nov 12, 2013 at 10:14 PM, Basanta Shrestha
basanta.shres...@olenepal.org wrote:
 Amazingly changing the manufacturing data didn't do the job but changing
 /etc/sysconfig/keyboard did. Wow! Now I have Nepali input system. Thank you
 all.

 Now I need to find a place to change default locale to ne_NP, so that the
 default interface is in Nepali. There is an option to do this in
 manufacturing data but it would be better if it can be done using file.

If all you want to do is change default keyboard and language, you can
avoid doing any manufacturing data changes, and just do the [base]
olpc-os-builder configuration I mentioned in my last email.

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


Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4

2013-11-11 Thread Daniel Drake
On Sun, Nov 10, 2013 at 5:18 PM, James Cameron qu...@laptop.org wrote:
 If you need to scale up this change to many laptops, contact
 reu...@laptop.org or myself.  I must know the SKU number.

In the particular case of changing language/keyboard defaults as we
are discussing, instead of changing manufacturing data I would
recommend doing it via olpc-os-builder, configuration for [base], see
http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/README#n46

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


Re: seeking help to enable nepali keyboard input for XO-4

2013-11-08 Thread Daniel Drake
On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha
basanta.shres...@olenepal.org wrote:
 But for XO-4 we will just be getting ones with English layout. I was
 wondering how we can enable nepali keyboard input on it.

Are these keyboards hard/clicky/high-school style, or soft/membrane?

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


[Server-devel] XS-0.7 fakeroot package updated to solve xs-rsync issue

2013-10-01 Thread Daniel Drake
Hi,

German R in Nicaragua identified a problem with xs-rsync, where some
files in the OS builds served to XOs are sent with bad permissions.
This fails olpc-update's verification checks, and the systems can't
update.

This was a bug in fakeroot, not processing internal messages
correctly, and recording bad permissions as a result. Fixed in
fakeroot-1.18.4-1.el6.olpc1.i686.rpm, available in the usual repo:
http://dev.laptop.org/xs/repos/stable/olpc/xs-0.7/i386/

Daniel
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


New 13.2.0 NetworkManager package fixes upgrades

2013-09-07 Thread Daniel Drake
Hi,

Upgrading from 12.1.0 to 13.2.0 results in previous wifi connections
not re-activating (haven't tried 13.1.0).

This was a NetworkManager bug:

https://mail.gnome.org/archives/networkmanager-list/2013-September/msg00018.html

Fixed in NetworkManager-0.9.8.1-3.git20130514.fc18.olpc1 available at:
http://dev.laptop.org/~dsd/20130907/

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


[Server-devel] xs-activity-server updates

2013-09-02 Thread Daniel Drake
Hi,

2 recent updates to xs-activity-server, new version 0.4.0 published just now:

1. Dotted activity versions (e.g. Browse-149.3) are now supported.

2. Separated input and output a bit better, easier to use with puppet
and similar. Use rsync to sync your activities into
/library/xs-activity-server/activities and then run
xs-regenerate-activities when done. The files are then linked
elsewhere and the output html files are also kept separately.

3. Support for multiple activity groups. e.g. put some activities in
/library/xs-activity-server/activities/2014 and they will come up in a
new activity group at http://schoolserver/activities/2014

Thanks
Daniel
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


pygobject performance optimizations posted

2013-08-27 Thread Daniel Drake
Hi,

http://rpmdropbox.laptop.org/f18/ now includes
pygobject3-3.4.2-6.fc18.olpc2 (on 13.2.0 developers can install with
yum update pygobject3)

This new package includes some optimizations from pygobject upstream.

I can't say the improvement is as visible as I was hoping for, but
some progress is being made, and there is hopefully more to come.

Any testing appreciated. It's also important to know that nothing has
broken with these changes.

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


Re: gst-vmeta testing

2013-08-27 Thread Daniel Drake
On Sun, Aug 25, 2013 at 5:30 PM, Carlos Rafael Giani
d...@pseudoterminal.org wrote:
 Now for human observation: there is no flicker problem.

 Interesting. Try again with this video please:
 http://download.openbricks.org/sample/H264/SampleClip.m4v
 With this one, I could definitely see flickering in past tests.

No flickering with that video.


 However, the
 video is noticably choppier when played back in the gstreamer-1.0
 environment. For example, look at the smoothness of the front door
 opening in that video.

 This looks like an issue with the parser. I am not sure what to make of it.
 I find it rather unlikely that this is caused by the decoder. I see warnings
 like these often with somewhat broken videos. Marvell's decoder does the
 parsing on its own, while mine doesn't ; instead, it leaves the parsing up
 to the existing GStreamer MPEG parsers. It is possible then that the custom
 Marvell parser code simply swallows broken timestamps etc. without saying
 anything.
 I wasn't able to try the video myself, since I have been very busy the last
 few days with something else. I will get to try it out tomorrow hopefully.

SampleClip.m4v plays back really smoothly with none of the frame drop
errors. And I just checked another sample,
http://techslides.com/demos/sample-videos/small.mp4 and that works
too.

So it does seem like you are right in suspecting something else at
play with the hellmans_mayonnaise_commercial.mpeg file.

Either way it would be nice if you could confirm/deny the findings
there, next time you have your device booted.

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


rawhide changes pushed to olpc-os-builder

2013-08-24 Thread Daniel Drake
Hi,

olpc-os-builder master now includes a few updates to build for rawhide
(currently F21). This work is experimental, for developers. The main
reason I did it was to have an easy platform to check the latest Sugar
against the latest pygobject etc.

Various things broken, some things working :)
Contributions welcome of course. Maybe someone will post a build or two.

To keep things simple and easily maintainable I have slimmed down the
build configs (no GTK2, no gstreamer-0.10, etc), trying to focus just
on the new stuff. Also I've dropped pretty much everything we've
forked.

No ARM support at the moment. We need a new kernel, and that is coming
little by little as we upstream support for our platform.

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


gst-vmeta testing

2013-08-23 Thread Daniel Drake
Hi Carlos,

I have given your gstreamer-1.0 plugins a spin on XO-4. Thanks for
working on this.

I additionally installed gstreamer1-plugins-bad-free for the mpeg4
container support and I'm testing with this video:
http://archive.org/download/hellmans_mayonnaise_commercial/hellmans_mayonnaise_commercial.mpeg

No audio support is installed.


Comparing gstreamer-0.10:

 gst-launch-0.10 filesrc location=hellmans_mayonnaise_commercial.mpeg
! decodebin ! vmetaxvimagesink

To your work:

 gst-launch-1.0 filesrc location=hellmans_mayonnaise_commercial.mpeg !
decodebin ! vmetaxvsink


As an initial check, vmeta does seem to be being used. I added some
prints into the X driver to check the hacky accelerated Xv path and it
is indeed hit, and the vmeta interrupts do increase during playback.

Looking at CPU usage: playing back that video at the standard size is
about 15% in both tests.


Now for human observation: there is no flicker problem. However, the
video is noticably choppier when played back in the gstreamer-1.0
environment. For example, look at the smoothness of the front door
opening in that video.

The log also fills up with:

gstbasesink.c(2705): gst_base_sink_is_too_late ():
/GstPipeline:pipeline0/GstVmetaXvSink:vmetaxvsink0:
There may be a timestamping problem, or this computer is too slow.
WARNING: from element
/GstPipeline:pipeline0/GstVmetaXvSink:vmetaxvsink0: A lot of buffers
are being dropped.

It is strange. It is not as if the CPU is too busy to keep up, after
all there is only 15% utilization. I ran it under perf (CPU-wide mode)
and that also confirmed that the system is 80% idle and didn't suggest
any obvious causes of the problem.

So, there is probably something in the gstreamer pipeline which is
doing sleep() or select() or similar, for extended time periods,
causing frames to be discarded when it wakes back up again. And
whatever it is waiting on is not eating CPU in a noticable way.

For future reference my test packaging is at
http://dev.laptop.org/~dsd/20130823/

Any ideas?

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


Re: vMeta GStreamer 1.0 plugins

2013-08-22 Thread Daniel Drake
On Thu, Aug 22, 2013 at 6:48 AM, Carlos Rafael Giani
d...@pseudoterminal.org wrote:
 First, I will paste from a chat I had in IRC with an X and Wayland
 developer:

 dv_ are you familiar with xvideo together with xshm?
 dv_ if not, who could know about internals?
 daniels hi, sure
 daniels what about it?
 dv_ the problem is that there seems to be no guarantee that xvshmputimage
 actually finished drawing the frame internally when it returns
 dv_ causing this bug: http://dev.laptop.org/ticket/12644#comment:7
 dv_ I have experienced a related problem. my decoder sends the frame to
 xv, where it is drawn, and xvshmputimage apparently returns too soon. so,
 frame buffers that havent been fully read yet by the driver are filled with
 new data
 daniels yeah, there's a 'completion' event for that, analogous to
 wl_buffer::release
 dv_ I tried that one, didnt help
 dv_ is there a known issue with this?
 daniels oh
 daniels no, your driver's buggy then, if it sends a completion before it's
 finished using the frame
 dv_ okay
 daniels tbf, the server does always send a shm completion event
 _immediately_ after XvdiPutImage returns, and there's no facility for doing
 otherwise
 daniels so if your driver does anything other than copy the data out
 immediately (e.g. schedules a draw using that area), then it's going to be
 buggy
 dv_ this could very well be
 dv_ because the hack that was added to it uses (actually abuses) the shm
 buffers as carriers for physical addresses
 dv_ that is, instead of copying pixel data, it writes a 32bit-address into
 it, plus a magic number
 dv_ the driver sees that magic number, knows that the next 4 bytes arent
 pixels but a physical address, and draws the pixels from that address
 daniels hah, right
 daniels yeah, you'd need to add new server - driver api for delayed
 completions
 dv_ so I guess either I have to block XvdiPutImage until the hardware has
 drawn it fully,
 dv_ or add something extra, yes
 dv_ to add credence to that theory, I put an usleep call right after
 xvshmputimage(). 10ms. the flickering disappeared.
 daniels haw
 daniels oh yeah, and with the second-last para, what you'll be seeing
 there is the ReputImage hook, i suspect
 daniels if the window isn't yet visible, it'll just bin all the drawing
 requests
 daniels but when it comes with a non-zero clip, suddenly it'll just fire
 requests at the driver's ReputImage hook

That is interesting, nice to have some expert input backing up my
findings on #12644.

 So I looked into the dove driver in the kernel, and I see nothing to cause
 the driver to wait for the hardware to finish the drawing. I tried adding a
 vsync wait, but that did not help. (Or perhaps I put it in the wrong place?)

Maybe you have overtaken me in your understanding here, but from the
above conversation, I can't see how this is related to the kernel
driver. Instead we face these problems:

1. The X client cannot assume that the image has been drawn by the X
driver after XvShmPutImage(). It might be drawn some time later.
2. The X client cannot assume that the image has been drawn by the X
driver after XvShmPutImage(). It might never be drawn at all.
3. There is no alternative way of communicating that required
information from the X driver to the X client (unless we implement
something).

So as far as I understand, this communication problem sits between the
X client and DDX, not related to the kernel, and there is nothing that
the DDX can immediately do about it (tbf, the server does always send
a shm completion event _immediately_ after XvdiPutImage returns, and
there's no facility for doing otherwise)

 John Nettleton then told me they don't have this issue because the OLPCs use
 the GPU for drawing, so the driver will use the texturedoverlay path. I
 cannot use the
 GPU mode, since then, symbols are missing (gcoHAL_QuerySeparated3D2D).

We definitely do have the issue described at #12644 and clarified by
daniels. I did work around it in a way that will result in occasional
bad frames being drawn (flickering?) but we have not seen that so
far with gstreamer-0.10. If that problem is avoided due to using
textured overlays, I am not sure why, but it may be so.

I will try to run your code in the next few days and see if we do see
the flicker issue.

Note that we work with two versions of libgalcore, one for each
version of our hardware. The XO-1.75 version that runs against an
older version of libgalcore does not use that symbol. You can find it
in the xo-1.75 branch of
http://dev.laptop.org/git/projects/xf86-video-dove/

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


Re: vMeta GStreamer 1.0 plugins

2013-08-21 Thread Daniel Drake
On Wed, Aug 21, 2013 at 12:02 AM, Carlos Rafael Giani
d...@pseudoterminal.org wrote:
 I have written GStreamer 1.0 plugins for vMeta . You can find it here:
 https://github.com/dv1/gst-vmeta

Excellent! Thanks for working on this and sharing it.
It looks like you have rewritten the plugin more or less from scratch,
is that right? A wise move...

I see you have already included our recent fix for the Xv plugin too,
nice. The IPP deinterlace flag handling is not present, I guess you
have excluded that for good reason, I'm not even sure what it does...

Also looks great that you have got the xv plugin using vmeta libs to
allocate physical memory areas. Rather than facing the
libbmm/libphycontmem mess directly like the previous version did.

 The decoder should be stable. The existing sink has a flickering problem
 which seems to be caused by a race condition in the X11 driver that wasn't
 noticed so far due to timing coincidences in Marvell's 0.10 plugins. John
 Nettleton tried out my plugins on OLPCs and informed me that they worked.
 Perhaps it would be usefult to mention it here:
 http://wiki.laptop.org/go/Vmeta

I will mention it. That flickering problem will have to be solved
before this becomes useful to anyone though.

 I have heard about a new KMS X driver which will be pushed upstream soon.
 Until I can get it, I will not be addressing the sink's flickering, since
 the new driver may have fixed it already.

The new driver source is available on the dri-devel mailing list.
However there are several complications that must be solved before it
goes upstream.

Then a new X driver will be needed, and whoever steps up to maintain
that will have to decide if they really want to support the horrible
hack used by the vmetaxv plugin. And then implement it, test it, etc.

Then there will be a few other hurdles to go over before the new
drivers are really a convincing replacement. Like GPU support.

In other words, I don't see this being upstream soon, and even when
that does happen, there will probably be other major steps required
before it is really useful. So I would continue to focus on the
existing stack.

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


Re: vMeta GStreamer 1.0 plugins

2013-08-21 Thread Daniel Drake
On Wed, Aug 21, 2013 at 8:03 AM, Carlos Rafael Giani
d...@pseudoterminal.org wrote:
 Yes, it is written from scratch. First, I wanted to use the GStreamer video
 decoder base class, which the Marvell decoder didn't. Second, the Marvell
 code uses many hacks that simply won't translate to GStreamer 1.0 . Third,
 it was much less work, and the code is much cleaner this way :)


 I see you have already included our recent fix for the Xv plugin too,
 nice. The IPP deinterlace flag handling is not present, I guess you
 have excluded that for good reason, I'm not even sure what it does...

 To be honest, this is a todo. But I was told that deinterlacing does not
 work in the X11 driver yet. So I cannot test it, and therefore cannot add
 support for it.
 As for the fix, do you mean the one about the alignment?

I mean the recent commits at
http://dev.laptop.org/git/users/dsd/gst-plugins-vmetaxv
I did not announce them to the cubox community so I'm glad you found
them somehow.

 The race condition I mentioned is really weird. The flickering disappears if
 I add a sleep call right after drawing the shm buffer with XShmPutImage.
 This indicates that the frames are filled with new data before they are
 fully drawn. In other words, the driver does not cause the plugin to wait
 long enough.

There are certainly some strange/unpredictable interactions between
the XShmPutImage call and the actual PutImage implementation inside
the X driver. I found that at
http://dev.laptop.org/ticket/12644#comment:7

Maybe it is my change there that is causing the flickering? As the
gstreamer plugin no longer waits for the X driver to actually
acknowledge that it has rendered the frame.

http://dev.laptop.org/git/users/dsd/gst-plugins-vmetaxv/commit/?id=56a35b8d7f3ed5f52371dc826502f1a08894ea46

 Also looks great that you have got the xv plugin using vmeta libs to
 allocate physical memory areas. Rather than facing the
 libbmm/libphycontmem mess directly like the previous version did.

 True. As it turns out, Marvell's xv sink only used bmm/phycontmem to get a
 physical address for a corresponding virtual one. Since I send the
 virtual/physical address information inside the GstMemory blocks contained
 in the GstBuffers, I do not need these libraries. The Marvell plugins do not
 put the physical address inside the GstBuffers (there is no field for that).

 The decoder should be stable. The existing sink has a flickering problem
 which seems to be caused by a race condition in the X11 driver that
 wasn't
 noticed so far due to timing coincidences in Marvell's 0.10 plugins. John
 Nettleton tried out my plugins on OLPCs and informed me that they worked.
 Perhaps it would be usefult to mention it here:
 http://wiki.laptop.org/go/Vmeta

 I will mention it. That flickering problem will have to be solved
 before this becomes useful to anyone though.

 Okay. Hopefully this will be fixed soon. I will see if there are updates.

 I have heard about a new KMS X driver which will be pushed upstream soon.
 Until I can get it, I will not be addressing the sink's flickering, since
 the new driver may have fixed it already.

 The new driver source is available on the dri-devel mailing list.
 However there are several complications that must be solved before it
 goes upstream.

 Then a new X driver will be needed, and whoever steps up to maintain
 that will have to decide if they really want to support the horrible
 hack used by the vmetaxv plugin. And then implement it, test it, etc.

 Then there will be a few other hurdles to go over before the new
 drivers are really a convincing replacement. Like GPU support.

 In other words, I don't see this being upstream soon, and even when
 that does happen, there will probably be other major steps required
 before it is really useful. So I would continue to focus on the
 existing stack.

 Russell King added an alternative to the BMM hack; something DMABUF-based,
 which is much cleaner.
 His alternative can also be detected, unlike the BMM hack (the decoder
 cannot find out if the driver contains the hack).

Maybe you know more about this then I do then. But I still do not see
this new driver stack being deployed as a replacement any time this
year...

 Do you think there is demand for vMeta encoder plugins as well?

Technically, it would be great to have such functionality, for
capturing good quality videos from the camera.
However, I believe shipping a product with encoding support for these
closed formats adds a load of legal costs/headaches, enough to cancel
out any demand.

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


Re: Headphone volume adjustment

2013-08-16 Thread Daniel Drake
On Thu, Aug 15, 2013 at 6:27 PM, Mark Brown broo...@kernel.org wrote:
 Yes, we try not to.  I do not recall the technical arguments in full,
 Daniel would, but they included very limited processing power, very
 limited memory, it didn't work when we first tried it, and a suite of
 applications that use the ALSA controls directly that we would have to
 port.

 Hrm, I suspect you'll find that either the processing power stuff is all
 fixed or it's due to bugs in the DMA in the driver which will probably
 get you sooner or later - worth checking out just in case, Pulse gets a
 lot of stick for things that are actually driver issues, it ends up
 being a really good test of the DMA implementation (some of the issues
 I saw mentioned in the changelogs sound like they might've been an issue
 for Pulse).  Even if you don't use it it might help validate the driver
 layer.

The last time we tried PulseAudio, it segfaulted on startup, and we
didn't get into the diagnosis. It was years ago though, and we haven't
tried since. We do want to give it another go but it has never taken a
high enough priority for us to actually do it.

We also agree that UCM looks like it will solve some of our problems,
and we'd like to fix/use the dynamic routing in the upstream codec
driver. Just need to find time to work on it.

3 of us have already spent a considerable amount of time on the
routing issue with little progress :/  Manually validating the links
between the components against the spec seems to be a very time
consuming process and prone to human error. Maybe you have some
suggestions or tools to help on that front. The issue is that upon
playback, nothing is reproduced, and the dapm files in sysfs show that
almost everything on the codec is powered down.

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


Re: Headphone volume adjustment

2013-08-16 Thread Daniel Drake
On Fri, Aug 16, 2013 at 12:01 PM, Mark Brown broo...@sirena.org.uk wrote:
 Do you know if a mainline kernel will actually run sensibly on your
 system?  I have a XO-1.75 (this was part of the reason I was looking)
 but I'm mostly interested in advancing the state of the art.

I am working on that at the moment, there are some arch patches needed
(DT bindings and so on) and the Marvell maintainers are not being
overly responsive. It is progressing though, I will try to remember to
send you an email when it can be booted easily on mainline.

 3 of us have already spent a considerable amount of time on the
 routing issue with little progress :/  Manually validating the links
 between the components against the spec seems to be a very time
 consuming process and prone to human error. Maybe you have some
 suggestions or tools to help on that front. The issue is that upon
 playback, nothing is reproduced, and the dapm files in sysfs show that
 almost everything on the codec is powered down.

 Hrm, no issues reported upstream with this :(

Thanks for the pointers - those scripts look like they will help find
the problems.

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


Re: olpc-os-builder

2013-08-12 Thread Daniel Drake
On Mon, Aug 12, 2013 at 5:48 PM, James Cameron qu...@laptop.org wrote:
 Yes.  I would prefer if olpc-os-builder could operate in two modes;
 one where it did all the downloads, and a separate one where it can be
 used offline.  This is what I did for mktinycorexo.

Try the --cache-only option.

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


Re: [Server-devel] Interesting opportunity to study upstream - downstream relationship Was: Root fs on XO1

2013-08-10 Thread Daniel Drake
On Sat, Aug 10, 2013 at 10:29 AM, David Farning
dfarn...@activitycentral.com wrote:
 The is an example of the opportunities and potential challenges that
 can occur between the community and the Association. This is why I was
 very pleased that the XSCE-XS thread last week shifted to
 clarification.

 The motivations and drives behind community volunteer decisions can be
 very different than the motivations and drives behind the decisions of
 an Association employee. As expressed in this thread, when working
 with large and remote deployments, the Association must be very risk
 adverse. Sending a qualified engineer to diagnose and fix a flakey SD
 card can take days... during which time their reputation takes a
 beating. I have some experience wearing those shoes :(

I think you raise a valid question but we could revisit your thought process.

By Association I assume you are referring to the OLPC Association.
(actually perhaps it doesn't even matter which association you are
referring to for the purpose of this mail)

The above paragraph suggests to me:
 1. Community projects can be deployed and it doesn't matter if they
do not work properly
 2. Association projects must be stable/reliable so that the
reputation of the company is not damaged

I disagree with both points and would reword them like this:
 1. All projects aimed for deployment (regardless of developer) should
strive for quality - which includes being risk averse.
 2. The reason for striving for quality is so that the project
actually serves the users, and is stable and reliable. (nothing to do
with reputation of the developer)

Doing a mental search-replace of those points in the rest of your mail
results in something that makes more sense to me, with the key
question of how to ensure stability and quality.

Daniel
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] Dealing with the disruptions caused by XSCE.

2013-08-08 Thread Daniel Drake
On Thu, Aug 8, 2013 at 1:47 AM, David Farning
dfarn...@activitycentral.com wrote:
 This disruption is particularly evident in the relationship between
 XSCE and OLPC. Long term, XSCE _might_ be valuable to OLPC in their
 role as The world food bank of education. Short term. in their roles
 as a sustainable business, it is a pain in the ass. What do you say to
 a customer when they ask for features which are still in a unreleased
 version of a community project... which just showed up on their wiki
 one day.

I don't see an issue here. You can leave communication between OLPC
and its customers to the relevant parties of the communication. That
should not stop anyone from writing code.

 A first question is should the XSCE wiki remain in a username space at
 wiki.laptop.org ? Should it move to another home? Should it move to
 http://wiki.laptop.org/go/XSCE ? or should we wait 3 months and
 revisit the issue?

OLPC has historically been happy to host community project info on the
wiki and I don't see any exception here. In some cases notices are
added to pages noting that OLPC does not provide direct customer
support but I hope that does not stop any efforts.

Daniel
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] Attempting to upgrade XO 1.5 firmware. Says activation lease not found

2013-07-18 Thread Daniel Drake
On Thu, Jul 18, 2013 at 3:15 PM, Kevin Cole dc.l...@gmail.com wrote:
 I thought I had given sufficient detail, but...

Your original mail raised several questions which the additional
detail below answer perfectly clearly, thanks.

 On the first day of summer vacation, I went downtown to look for a
 job and hung out in front of the drug store. On the the second day of
 summer vacation, I went downtown to look for a job and hung out in
 front of the drug store. On the third day of summer vacation, I went
 downtown to look for a job and hung out in front of the drug store...
 --  Cheech  Chong (Sister Mary Elephant)

 * I booted my Ubuntu laptop.
 * I inserted a 1 GB USB thumb drive.
 * I opened Chrome
 * I went to http://wiki.laptop.org/go/Release_notes
 * I clicked on Release_notes/13.2.0
 * I clicked on 4.3 XO-1.5
 * I clicked on 32013o1.zd which saved it to ~/Download/
 * I clicked on 32013o1.zd.zsp.fs1.zip which saved it to ~/Download/
 * I opened a terminal window
 * I typed:
  cd ~/Download/
  mv 32013o1.zd.zsp.fs1.zip fs1.zip
  cp -v fs2 /media/usb/
  cp -v 32013o1.zd /media/usb/
  diff fs2 /media/usb/
  diff 32013o1.zd /media/usb/
  sudo shutdown -h now

What is the fs2 thing? Can you post ls /media/usb output for double-checking?

 * I inserted the 1 GB USB thumb drive in the XO and pressed the
   power button while holding the X key on the gamepad.
 * I released the X when told it to do so.
 * I received an error about NANDblaster.  (Sorry, I don't have the
 exact text of that message.)

And if you can, post the output from the XO screen of the above. The
NANDblaster error is not interesting, but the previous lines are.

Another useful verification item: turn on the laptop, wait to hear the
boot jingle, press escape. Connect USB disk. At the ok prompt type
dir u:\
This will check that the laptop can read the USB disk successfully.

 * I booted my Ubuntu laptop.
 * I inserted the 1 GB USB thumb drive.
 * I opened Chrome
 * I went to http://wiki.laptop.org/go/Firmware
 * I clicked on XO-1.5
 * I clicked on OLPC Firmware q3c16
 * I clicked on q3c16.rom which saved it to ~/Download/
 * I typed
  mkdir /media/usb/boot
  cp -v q3c16.rom /media/usb/boot
  diff q3c16.rom /media/usb/boot
  sudo shutdown -h now

 * I inserted the 1 GB USB thumb drive in the XO and pressed the
   power button while holding the X key on the gamepad.
 * I released the X when told it to do so.
 * After a few minutes, I saw three icons, and a message at the top
   of the screen Activation lease not found.

It's not clear to me why you are holding the X key here, are you
expecting that to upgrade the firmware from the rom file?

It doesn't quite work like that. What the X does is make the laptop
boot in secure mode. Your laptop has security disabled (as you
mentioned: no wp tag) but by pressing X you are simulating
security-enabled. As designed, this then goes and looks for an
activation lease or developer key, and fails. (it wouldn't have
upgraded the firmware from the .rom even if you made it happy with the
appropriate lease/key)

Anyway, no manual firmware upgrade should be necessary. Lets figure
out why the reflashing doesn't work.

Thanks
Daniel
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: Issue

2013-07-17 Thread Daniel Drake
On Tue, Jul 16, 2013 at 10:52 PM, Julian Goldstein
julian.goldste...@gmail.com wrote:
 Here are the logs for the hello world and turtle art.

This is an incompatibility between old sugar-toolkit-gtk3 versions and
new pygobject versions. You need to update your version of
sugar-toolkit-gtk3 where this issue is solved. If you are already
running the latest available in Ubuntu, it means that the Ubuntu
packages are old or broken.

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


Re: Issue

2013-07-17 Thread Daniel Drake
Please keep the list on CC.

On Wed, Jul 17, 2013 at 11:00 AM, Julian Goldstein
julian.goldste...@gmail.com wrote:
 Should I just apt-get those packages?

I don't know, sorry. Here we generally work with Fedora where these
things are known to be working.

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


Re: Issue

2013-07-17 Thread Daniel Drake
On Wed, Jul 17, 2013 at 11:28 AM, Julian Goldstein
julian.goldste...@gmail.com wrote:
 Ok thanks! I may just install Fedora then. Is there any C, or non-GUI stuff
 I can contribute with on Ubuntu like any low level projects?

We normally do have a short wishlist for the components sits directly
beneath Sugar, i.e. the GTK+ stack. pygobject performance is a current
item that springs to mind.
https://mail.gnome.org/archives/python-hackers-list/2013-July/msg7.html

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


Announcing OLPC OS 13.2.0

2013-07-17 Thread Daniel Drake
Hi,

We're pleased to announce the release of OLPC OS 13.2.0 for XO-1,
XO-1.5, XO-1.75 and XO-4. Details of new features, known issues, and
how to download/install/upgrade can all be found in the release notes:
http://wiki.laptop.org/go/Release_notes/13.2.0

Many thanks to all contributors, testers, upstreams, and those who
have provided feedback of any kind.

For those who were following the release candidate process in the last
few weeks: candidate build 13 is released as final with no changes.

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


13.2.0 release candidate 6 (build 13) released

2013-07-15 Thread Daniel Drake
Hi,

We're pleased to announce the next release candidate of our new 13.2.0
software release. Probably the final build.

Information and installation instructions can be found here:
http://wiki.laptop.org/go/Release_notes/13.2.0

Quick links for those who know which files need to be grabbed and save
to USB disks:
http://download.laptop.org/xo-4/os/candidate/13.2.0-13
http://download.laptop.org/xo-1.75/os/candidate/13.2.0-13
http://download.laptop.org/xo-1.5/os/candidate/13.2.0-13
http://download.laptop.org/xo-1/os/candidate/13.2.0-13

This is a signed release candidate that can be installed on all XOs,
even those with security enabled.

We're looking for any final testing and feedback on all aspects of the
system. Thanks for any help you can offer, and for all the feedback
that was received throughout development.

Changes since the last release candidate:

Latest firmware versions fix NANDBlaster. (#12726)
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Headphone volume adjustment

2013-07-06 Thread Daniel Drake
On Fri, Jul 5, 2013 at 5:47 PM, James Cameron qu...@laptop.org wrote:
 The DAC volume control has the greatest range, all the way down to
 -96.625 dB, which coupled to our XO-1.75 hardware is effectively
 silent, but not guaranteed to be.  You can see the details of this
 control in the XO-1.75 and XO-4 source ... search for dac_vol_tlv.

 The speaker amplifier control has a range of 58.5 dB.  With this set
 to minimum on our XO-4 hardware it is also effectively silent but not
 guaranteed to be.

OK, thanks for the explanation. So, fixing the ALSA controls to
exploit the full volume range of the hardware would probably result in
an OK user experience on this point (minimum volume = inaudible
sound), and I think that would be more consistent with other ALSA
drivers behaviour, but might also come with other headaches.

So I can appreciate the effort taken to not change the audible range
and other behaviour, but simply set the mute bits when the minimum
volume is selected. So this patch looks fine to me. Thanks.

As a point of interest, the pulseaudio volume control on my desktop
automatically sets the mute bit on the underlying ALSA device when the
volume slider is dropped to zero. I presume that behaviour is
implemented by the pulseaudio core. It is probably done for the same
kinds of reasons (minimum volume not guaranteed to to be inaudible,
but muting does the trick).

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


Clock-12.5 startup timing on XO-1

2013-07-06 Thread Daniel Drake
Hi,

I ran Clock-12.5 on 11.3.1, 12.1.0 and 13.2.0 build 11, all on the
same XO-1, to see if we have any difference in startup time. This is a
GTK2 activity.

Launching 10 times from hot caches and averaging, my measurements are:

11.3.1: 12.52 seconds
12.1.0: 11.53 seconds
13.2.0: 11.74 seconds

So, we may have had a slight performance increase introduced in
12.1.0. For the comparison between 13.2.0 and 12.1.0, the numbers
suggest a tiny slowdown, but actually launch time commonly varies by
+/- 0.5 seconds, so I don't see this as significant.

I can't reproduce the interesting difference in X cpu usage % that I
noted in the other thread. That was probably also an insignificant
normal variance.

So, we don't seem to have any regressions in GTK2 activity startup
time in recent years. However, the results on all builds are pretty
bad, it would be nice if we could figure out why a fairly simple
activity takes so much time to launch.

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


Re: Headphone volume adjustment

2013-07-05 Thread Daniel Drake
Hi,

On Fri, Jul 5, 2013 at 12:40 AM, James Cameron qu...@laptop.org wrote:
 Fixed for XO-4 in:

 http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.5id=e77de3d4ec7589af2e88014018c69528ceab3293

Thanks for looking at this.

I'm trying to review the change. I am a bit stuck though, because I
still don't understand the answer to the opening question on this
thread: is this a bug or by design?

Do I gather correctly from your initial response that it is by design
that the headphone volume slider does not cover the full range offered
by the hardware? That is, if I use alsamixer to set the volume as low
as it will go, the value programmed to the hardware is not the lowest
that the hardware can go? If that is the case, why?

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


Re: XO-1(.75)

2013-07-04 Thread Daniel Drake
On Thu, Jul 4, 2013 at 2:53 AM, Gonzalo Odiard gonz...@laptop.org wrote:
 No inconsistency here.
 Most of the activities you see slower were ported to Gtk3.
 Tam-tam suit, speak, calculate, turtle art, maze, moon, record were not
 ported
 scratch and etoys are not related with Gtk
 Browse received a lot of care this months.
 Sadly, while the port to Gtk3 and dynamic bindings promised faster start up
 time (in theory)
 that was never true. Dsd found performance problems and pushed changes
 upstream.
 and 13.2.0 is better than 13.1.0, but anyway more work is needed.
 Maybe some work can be done in the activities to improve it.
 Do you have numbers to share?

Yes, this is the interesting point in this thread. If you take an
old release, on any platforms where we have old releases
available, and do a side-by-side comparison with the latest release,
we may well have a performance regression.

However the possible performance regression is not documented in
technical terms. People have mentioned a slowdown in previous threads,
but nobody posted any numbers. Last time, a video was posted, but that
link is no longer working and I'm not sure if it had numbers in it.

Last time it was discussed I did generate numbers myself and then
solved the problem. However that discussion was focused around Sugar
startup time. This discussion now turns to activity startup time.

So, having someone generate activity startup time numbers in a fair
test (i.e. same platform, different software versions) would be of
value.

If there is a performance regression here, we don't have a technical
diagnosis that I know of. It seems like some people suspect
GTK3/gobject-introspection as the cause, and those may be likely
candidates, but I don't think we have real diagnosis supporting that
(yet), nor any explanation for why those new technologies might be
slower than the old ones.

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


Re: XO-1(.75)

2013-07-04 Thread Daniel Drake
On Thu, Jul 4, 2013 at 12:48 PM, Yioryos Asprobounitis
mavrot...@yahoo.com wrote:
 Tried the following little script but I can not find a way to get the output 
 of 'time' command to the output.txt file.

Not really sure what you are trying to do here - sugar-launch will not
return until the activity exits.

I ran a couple of experiments here, with XO-1s running 12.1.0 and 13.2.0.
Clock (which is a GTK2 activity on both versions) does start 0.5 - 1
second slower on 13.2.0.
On 12.1.0 it starts in 10.5 seconds. That is approx 5% change.

Running under perf, the most noticable difference is that X uses 5% of
CPU time on 12.1.0, and 10% on 13.2.0. A 5% change.

Unfortunately perf doesn't tell me which part of X is eating CPU,
apart from the fact that it is not in the kernel. Need to figure out
why perf can't be more specific.

The risk to this work is that we might fix the 5% X issue and see no
noticable difference. But I will try to continue a bit of
investigation here next week.

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


Re: XO-1(.75)

2013-07-04 Thread Daniel Drake
On Thu, Jul 4, 2013 at 2:00 PM, Yioryos Asprobounitis
mavrot...@yahoo.com wrote:
 The following script appears to work as expected, but is the result valid?

That's hard to judge without having an explanation for what you are
trying to measure. I can't immediately see your intentions from
reading the script.

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


Re: XO-1(.75)

2013-07-04 Thread Daniel Drake
On Thu, Jul 4, 2013 at 2:13 PM, Jerry Vonau jvo...@shaw.ca wrote:
 Of the total available, would that not be a 100% increase in CPU time
 used by the process running X?

What do you mean by the process running X?
The parent process of the X process?

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


Re: GNOME on XO-1.75

2013-07-01 Thread Daniel Drake
On Mon, Jul 1, 2013 at 1:55 AM, Yioryos Asprobounitis
mavrot...@yahoo.com wrote:
 Another little issue is that clicking on the scroll bar in epiphany (and also 
 gedit and terminal) moves the page to the cursor instead of 1 page down.

This was a GNOME design decision. It is configurable somewhere. You
don't see that happen on the Sugar side since we explicitly request
the other behaviour.

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


Re: compiling and running webkit2gtk on xo-1.75/os/candidate/13.2.0-9

2013-06-27 Thread Daniel Drake
On Thu, Jun 27, 2013 at 8:08 AM, NoiseEHC noise...@gmail.com wrote:
 which updated a lot of packages and my program finally started. If I compile
 with webkitgtk1 then it runs, with webkitgtk2 it crashes.
 The crash (SIGSEGV) happens in glXCreateContext in /lib/ligBL.so.1

 As I do not really understand all those package things, it seems to me that
 the compiled webkit2 references OpenGL libraries while webkit1 does not.
 Could we just switch it off somehow while compiling the XO image?

We pull in webkit packages from Fedora, we don't compile them for XO.
So fixing this bug will require a proper investigation into the crash
you have found.

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


13.2.0 release candidate 4 (build 11) released

2013-06-27 Thread Daniel Drake
Hi,

We're pleased to announce the next release candidate of our new 13.2.0
software release.

Information and installation instructions can be found here:
http://wiki.laptop.org/go/Release_notes/13.2.0

Quick links for those who know which files need to be grabbed and save
to USB disks:
http://download.laptop.org/xo-4/os/candidate/13.2.0-11
http://download.laptop.org/xo-1.75/os/candidate/13.2.0-11
http://download.laptop.org/xo-1.5/os/candidate/13.2.0-11
http://download.laptop.org/xo-1/os/candidate/13.2.0-11

This is a signed release candidate that can be installed on all XOs,
even those with security enabled.

We're looking for any final testing and feedback on all aspects of the
system. Thanks for any help you can offer, and for all the feedback
that was received throughout development.

Changes since the last release candidate:

The XO-4 has an experimental new feature allowing the edges of the
screen to be reached with touches (#12713).  To test, enable it with:

 echo 80  /sys/module/zforce/parameters/margin_y
 echo 80  /sys/module/zforce/parameters/margin_x
 echo 2000  /sys/module/zforce/parameters/scale_x
 echo 2000  /sys/module/zforce/parameters/scale_y

This causes events reported within 80 pixels of the screen edge to
have their distance from the edge halved. margin values are pixels,
and scale values are tenths of percent.

XO-4 HDMI output in Linux and the firmware now better meets the HDMI spec.

A memory corruption issue in the new XO-4 8787 wireless driver was
fixed (#12701, this was shipped in build 10).

XO-4 firmware Q7B35 fixes some factory tests, fixes a power
consumption issue (#12415), and solves a couple of minor EC bugs.

XO-1.75 firmware Q4D31 fixes save-mfg-data and some factory test issues.

XO-1.5 firmware Q3C15 fixes save-mfg-data (#12684) and a boot problem
in the presence of unsupported filesystems (#12696)
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: compiling and running webkit2gtk on xo-1.75/os/candidate/13.2.0-9

2013-06-27 Thread Daniel Drake
On Thu, Jun 27, 2013 at 1:11 PM, NoiseEHC noise...@gmail.com wrote:
 Now I looked at the source of webkit2gtk and it seems that opengl support is
 compiled into the library or not, so if OPENGL is specified then it will
 call into libGL.so and will crash. Maybe we should not lie about 3d support?
 What is the status of OpenGL support on the xo-1.75 and xo-4? I have read
 the email about writing an open source driver for the xo-4 but does it imply
 that there is no official binary driver from Marvell? (I know that XO-1 and
 xo-1.5 will not support 3d.)

I don't think there are any lies about 3d support. We do not offer it
at this time, and the GLX extension is disabled in the X server.

 So I will stick to webkit1... On the other hand, going native is clearly the
 way to go, as it launches in 2-5 sec (usually ~3), while Browse launches in
 13 sec on my xo-1.75...

Just curious, what do you mean by going native?

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


Re: Different boot sound on XO1.75

2013-06-20 Thread Daniel Drake
On Thu, Jun 20, 2013 at 9:28 AM, Juan Cubillo jcubi...@fundacionqt.org wrote:
 Hello,

 Quick question  I have two 1.75XO that make a beep beep sound while
 booting instead of the usual XO booting sound. Why is this so? Can this be
 changed?

This likely means that you are running a new firmware on an old OS
release. Downgrading the firmware to the version that was intended for
that release should restore the bootup sound. (or, alternatively,
upgrade the OS to match the firmware)

I imagine James will provide a full explanation when he wakes up later on :)

If you are mixing versions on purpose, do note
http://dev.laptop.org/ticket/12637

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


Re: Different boot sound on XO1.75

2013-06-20 Thread Daniel Drake
On Thu, Jun 20, 2013 at 11:36 AM, Juan Cubillo jcubi...@fundacionqt.org wrote:
 That might be an option, but not in my case. Both XOs have Build 13.0.1 and
 Firmware Q4D28.

 I'll wait for James to wake up :)

In the mean time maybe you can explain why changing firmware version
and/or OS version is not an option. It might help us give good advice.

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


13.2.0 build 10 for XO-4 released

2013-06-17 Thread Daniel Drake
Hi,

Here is a quick XO-4-only build with a memory corruption fix in the
XO-4 wireless driver (#12701). Part of our ongoing work to fix
stability issues preventing successful factory testing.

http://download.laptop.org/xo-4/os/candidate/13.2.0-10/

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


Re: OOB V6.0 does not installs example ini files (SOLVED)

2013-06-13 Thread Daniel Drake
On Wed, Jun 12, 2013 at 8:08 PM, Juan Cubillo jcubi...@fundacionqt.org wrote:
 Thank you for the info!

 Yeah the ../docs/... was a typo... I was looking inside ../doc/

 I also always wondered why the wiki instructions didn't used yum to install
 the software... another mystery solved!

That is mainly because the wiki instructions are rather old, they were
written for XO-1.75 before there was a yum package available. There
are a couple of other redundancies in the docs as well. But if you
have it working, nobody is complaining :)
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Upstreaming MMP clock devicetree support

2013-06-13 Thread Daniel Drake
-clock/sdh1-clock encode-phandle  clocks property
device-end

dev /sd/sdhci@d4281000
\ FIXME clock should be mmp2-only? does appear in XO4 DT
 /apmu-clock/mspro-clock encode-phandle  clocks property
device-end

dev /sd/sdhci@d4280800
 /apmu-clock/sdh2-clock encode-phandle  clocks property
device-end

[ifdef] mmp3
dev /sd/sdhci@d4217000
 /apmu-clock/sdh5-clock encode-phandle  clocks property
device-end
[then]

dev /display
/apmu-clock/lcd-clock encode-phandle  clocks property
device-end

dev /vmeta
/apmu-clock/vmeta-clock encode-phandle  clocks property
device-end

[ifdef] mmp3
dev /gpu
/apmu-clock/gc-clock encode-phandle  clocks property
device-end
[then]




[PATCH] clk: mmp: add support for DT-defined clocks

Add support to the existing mmp clock drivers for clocks to be defined
in the device tree. This will be used on OLPC MMP2/MMP3-based laptops.

If clock info cannot be found in the device tree, we fall back to the
static clock initialization already present.

Signed-off-by: Daniel Drake d...@laptop.org
---
 .../devicetree/bindings/clock/mmp-apbc.txt | 30 ++
 .../devicetree/bindings/clock/mmp-apmu.txt | 30 ++
 drivers/clk/mmp/clk-apbc.c | 66 +-
 drivers/clk/mmp/clk-apmu.c | 37 +++-
 drivers/clk/mmp/clk-mmp2.c | 19 ++-
 5 files changed, 179 insertions(+), 3 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/clock/mmp-apbc.txt
 create mode 100644 Documentation/devicetree/bindings/clock/mmp-apmu.txt

diff --git a/Documentation/devicetree/bindings/clock/mmp-apbc.txt 
b/Documentation/devicetree/bindings/clock/mmp-apbc.txt
new file mode 100644
index 000..88e1253
--- /dev/null
+++ b/Documentation/devicetree/bindings/clock/mmp-apbc.txt
@@ -0,0 +1,30 @@
+* Clock bindings for Marvell MMP Advanced Peripheral Bus clock
+
+Parent apb-clock node
+=
+Required properties:
+- reg: Address and length of the APB clock unit registers
+
+
+Child peripheral clock nodes
+
+Required properties:
+- compatible : shall be marvell,mmp-apb-clock
+- #clock-cells : from common clock binding; shall be set to 1
+- clocks : parent clock, from common clock binding
+- clock-output-names : Array of clock names, from common clock binding
+- reg : Array of control register offsets into APB clock unit register space
+
+
+Example:
+apbc: apb-clock {
+   reg = 0xd4015000 0x1000;
+
+   twsi-clocks {
+   compatible = marvell,mmp-apb-clock;
+   #clock-cells = 1;
+   clocks = vctvxo-clock;
+   clock-output-names = TWSI0, TWSI1;
+   reg = 0x04 0x08;
+   };
+};
diff --git a/Documentation/devicetree/bindings/clock/mmp-apmu.txt 
b/Documentation/devicetree/bindings/clock/mmp-apmu.txt
new file mode 100644
index 000..18bb0f9
--- /dev/null
+++ b/Documentation/devicetree/bindings/clock/mmp-apmu.txt
@@ -0,0 +1,30 @@
+* Clock bindings for Marvell MMP Application Subsystem Power Management Unit
+
+Parent apmu-clock node
+=
+Required properties:
+- reg: Address and length of the CPU Subsystem PMU registers
+
+
+Child peripheral clock nodes
+
+Required properties:
+- compatible : shall be marvell,mmp-apmu-clock
+- #clock-cells : from common clock binding; shall be set to 0
+- clocks : parent clock, from common clock binding
+- reg : Control register offsets into parent register space
+- enable-mask : The bits to be set in the register to enable the clock, or
+cleared to disable.
+
+Example:
+apmu-clock {
+   reg = 0xd4282800 0x1000;
+
+   usb-clock {
+   compatible = marvell,mmp-apmu-clock;
+   #clock-cells = 0;
+   clocks = usb_pll;
+   reg = 0x5c;
+   enable-mask = 0x09;
+   };
+};
diff --git a/drivers/clk/mmp/clk-apbc.c b/drivers/clk/mmp/clk-apbc.c
index 89a146a..d53bc79 100644
--- a/drivers/clk/mmp/clk-apbc.c
+++ b/drivers/clk/mmp/clk-apbc.c
@@ -15,6 +15,8 @@
 #include linux/err.h
 #include linux/delay.h
 #include linux/slab.h
+#include linux/of.h
+#include linux/of_address.h
 
 #include clk.h
 
@@ -129,8 +131,70 @@ struct clk *mmp_clk_register_apbc(const char *name, const 
char *parent_name,
apbc-hw.init = init;
 
clk = clk_register(NULL, apbc-hw);
-   if (IS_ERR(clk))
+   if (WARN_ON(IS_ERR(clk)))
kfree(apbc);
 
return clk;
 }
+
+static void __init mmp_apbc_dt_init(struct device_node *node)
+{
+   struct device_node *parent = of_get_parent(node);
+   const __be32 *regs;
+   struct clk *clk;
+   int rc;
+   int len;
+   int num_clocks;
+   int clock_num;
+   void __iomem *baseaddr;
+   const char *clock_name;
+   const char *parent_name;
+   struct clk **clks;
+   struct clk_onecell_data *clk_data

Re: Upstreaming MMP clock devicetree support

2013-06-13 Thread Daniel Drake
On Thu, Jun 13, 2013 at 11:56 AM, Paul Fox p...@laptop.org wrote:
 does this imply a future flag day, at which time new firmware will be
 incompatible with old kernels, and vice-versa?

Unfortunately even without the DT changes described here, old firmware
versions already will not be able to boot new/upstream kernels, once
we get to that point. The DT is missing regulator information so the
MMC controller doesn't get powered up. This is the old firmware, new
kernel problem.

The DT clock changes described here would also mean that new firmwares
become incompatible with released kernels. This is the new firmware,
old kernel problem. I think this will also be unavoidable.

So yes, we are looking at both of those problems.

There are some thoughts and possibilities here:

http://wiki.laptop.org/go/Device_tree_upgrade_considerations
https://lists.ozlabs.org/pipermail/devicetree-discuss/2012-August/019024.html

but no definite, attractive solution. I suspect it is something we are
just going to have to live with.

I think the old firmware, new kernel is the most painful of the two
problems. Maybe we can fix that up with a bootwrapper type solution
mentioned in the mail linked to above (and maybe I already half-wrote
the bootwrapper in my previous mail).

There is also the possibility that the kernel will accept bindings for
old/imperfect DTs once good bindings are put in place - or
alternatively we could patch them in. I'm working on the good
bindings aspect at the moment.

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


Re: OOB V6.0 does not installs example ini files

2013-06-12 Thread Daniel Drake
On Wed, Jun 12, 2013 at 12:39 PM, Juan Cubillo jcubi...@fundacionqt.org wrote:
 Hello,

 I just flashed a 1.75XO with the stable 13.1.0 image from OLPC. Then, I
 installed OOB via yum install olpc-os-builder

 I wanted to build a test image but no example files were installed in
 /usr/share/docs/

XOs are configured to not install anything in /usr/share/docs to save space.

Either install it on another system (to get the ini files) or grab
them from the source tarball,
http://dev.laptop.org/pub/source/olpc-os-builder/

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


MMP interrupt controller DT layout

2013-06-11 Thread Daniel Drake
Hi,

I am looking at upstreaming these patches:

http://dev.laptop.org/~dsd/20130611/0003-ARM-mmp-Fix-MMP2-interrupt-controller-DT-nodes.patch

http://dev.laptop.org/~dsd/20130611/0004-ARM-mmp-irq-Use-of_get_address-instead-of-of_address.patch

Could one of you summarise the background here, and confirm my
understanding below?

Here is the upstream mmp2 DT which the first patch applies against:

http://lxr.linux.no/linux+v3.9.5/arch/arm/boot/dts/mmp2.dtsi#L34

I can see why this is a strange design. The intc-mux registers clearly
sit inside the intc range, but is this actually forbidden by DT?

The reg values seem to refer to memory address 0x150 and so on (in the
traditional DT sense), which is obviously odd.

As strange as it may be, all of this is documented reasonably well at
http://lxr.linux.no/linux+v3.9.5/Documentation/devicetree/bindings/arm/mrvl/intc.txt

Given the oddness here, I can understand OLPC's desires to go against
spec and fix this up in OLPCs DT. But the end result is not entirely
clear to me. The OLPC DT can be viewed here:
http://dev.laptop.org/~dsd/20130611/0002-ARM-dts-Add-xo-1-75-mmp2-and-xo-4-mmp3-dts.patch

To me, the logical design here would be to have intc as a parent
device and treat it almost like a bus, with:

  reg = 0xd4282000 0x1000;
  #address-cells = 0x1;
  #size-cells = 0x1;
  ranges = 0x0 0xd4282000 0x1000;

Then that would have child devices like:

  interrupt-controller@1d0 {
compatible = mrvl,mmp2-mux-intc;
reg = 0x1d0 0x4 0x1b8 0x4;
  };

And the 0x1d0 would be translated to real memory address 0xd42821d0,
thanks to the ranges property.

What we have in the OLPC DT is almost this, but it is missing the
ranges prop. According to booting-without-of.txt this suggests that
the registers of the child device are not accessible to the parent. As
the address cannot be translated, of_address_to_resource() cannot be
used, which leads to the 0004 patch above.

I am really just interested in clarifying my understand of DT address
mapping and the background here. For compatibility reasons, I will try
to go upstream with what we ship in the DT at the moment. Which leads
to one final question...

The 0004 patch says: This patch depends on ARM: mmp: Fix MMP2
interrupt controller DT nodes.

I can't see why this is true. As far as I can see, of_get_address()
will work OK for both the current upstream mmp2.dtsi, and for the OLPC
intc DT layout which is missing the ranges property. Any hints?

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


13.2.0 release candidate 3 (build 9) released

2013-06-11 Thread Daniel Drake
Sorry - I sent this out yesterday but with the wrong subject line.

On Mon, Jun 10, 2013 at 4:56 PM, Daniel Drake d...@laptop.org wrote:
 Hi,

 We're pleased to announce the next release candidate of our new 13.2.0
 software release.

 Information and installation instructions can be found here:
 http://wiki.laptop.org/go/Release_notes/13.2.0

 Quick links for those who know which files need to be grabbed and save
 to USB disks:
 http://download.laptop.org/xo-4/os/candidate/13.2.0-9
 http://download.laptop.org/xo-1.75/os/candidate/13.2.0-9
 http://download.laptop.org/xo-1.5/os/candidate/13.2.0-9
 http://download.laptop.org/xo-1/os/candidate/13.2.0-9

 This is a signed release candidate that can be installed on all XOs,
 even those with security enabled.

 We're looking for any final testing and feedback on all aspects of the
 system. Thanks for any help you can offer, and for all the feedback
 that was received throughout development.


 Changes since the last release candidate:

 Paint-59 fixes touch widget accessibility (SL#4500)

 Record-99 uses a more standard high-quality video resolution that
 works on XO-4 (SL#4491)

 ImageViewer collaboration is fixed (SL#4520)

 XO-4 max volume is dropped a little to reduce speaker distortion (#12588)

 A memory corruption bug in the 8787 wireless driver was solved (#12688)

 Latest XO-1 firmware (#12514, #12696, #12662)

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


13.2.0 release candidate 2 (build 8) released

2013-06-10 Thread Daniel Drake
Hi,

We're pleased to announce the next release candidate of our new 13.2.0
software release.

Information and installation instructions can be found here:
http://wiki.laptop.org/go/Release_notes/13.2.0

Quick links for those who know which files need to be grabbed and save
to USB disks:
http://download.laptop.org/xo-4/os/candidate/13.2.0-9
http://download.laptop.org/xo-1.75/os/candidate/13.2.0-9
http://download.laptop.org/xo-1.5/os/candidate/13.2.0-9
http://download.laptop.org/xo-1/os/candidate/13.2.0-9

This is a signed release candidate that can be installed on all XOs,
even those with security enabled.

We're looking for any final testing and feedback on all aspects of the
system. Thanks for any help you can offer, and for all the feedback
that was received throughout development.


Changes since the last release candidate:

Paint-59 fixes touch widget accessibility (SL#4500)

Record-99 uses a more standard high-quality video resolution that
works on XO-4 (SL#4491)

ImageViewer collaboration is fixed (SL#4520)

XO-4 max volume is dropped a little to reduce speaker distortion (#12588)

A memory corruption bug in the 8787 wireless driver was solved (#12688)

Latest XO-1 firmware (#12514, #12696, #12662)

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


School networks and electrical equipment damage

2013-06-06 Thread Daniel Drake
Hi,

Those of us familiar with setting up school networks (server + switch
+ APs) in some of our deployments will be familiar with  the
occasional loss of hardware, due to surges in the low quality
electrical supply or whatever, even when the system is protected by a
cheap UPS which supposedly offers some protection.

This has often been the case in Nicaragua, so the group is now buying
more expensive UPSes, PoE switches, and PoE access points for new
schools. This means that the server and switch are connected to mains
power via a UPS which hopefully protects them, and none of the APs are
connected directly to the mains (instead they get Power over Ethernet)
which hopefully offers some isolation from bad electrical conditions.

This equipment is expensive, especially in places like Nicaragua where
lots of import taxes are applied. But the hope is that the investment
pays off in that the equipment doesn't get zapped.

However, one week after deploying this equipment in the first school,
we are left with a server that doesn't boot, 3 out of 4 access points
broken with a nice burning electronics smell, and a broken switch with
a lot of visible damage to the electronics.

And the most surprising thing - we had not even turned on the network
yet, pending some electrical work. Everything was connected up except
one crucial link - the UPS was not plugged into mains power. So all of
this damage happened without any of the devices having a connection to
the mains.

Connectivity-wise, the setup was:
WAN: Phone line - ADSL modem - XS
LAN: XS - Switch - 4 APs

And power connections: the XS, ADSL modem and switch were connected to
the UPS. The APs were connected to the switch over ethernet for both
power and data. Again, since the battery was not connected to mains
power, none of the devices had a power source.

The connectivity engineer's best bet is that a lightening bolt landed
at the school or nearby, and that this caused a power surge on the
phone line. This surge passed through the ADSL modem, server, switch,
and 4 APs, destroying everything in its path (except 1 AP that was
connected over a longer cable than the rest).

I figured this is a story worth sharing, for any other projects
considering splashing out on more expensive equipment...

Also, I'm wondering if anyone has any advice/experience here. Would
others expect this more expensive setup to be more resilient to bad
electrical conditions than a cheaper setup - will the investment pay
off?

I figure that the case of a lightening bolt might be a bit extreme,
but electrical storms are a nightly occurance here almost daily during
the 6 month rainy season.

I have seen that some UPSs (unfortunately not these ones) allow a
phone line to be passed through them, supposedly offering some
protection. Would such a system protect against a lightening bolt,
assuming thats what happened here?

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


[Server-devel] School networks and electrical equipment damage

2013-06-06 Thread Daniel Drake
Hi,

Those of us familiar with setting up school networks (server + switch
+ APs) in some of our deployments will be familiar with  the
occasional loss of hardware, due to surges in the low quality
electrical supply or whatever, even when the system is protected by a
cheap UPS which supposedly offers some protection.

This has often been the case in Nicaragua, so the group is now buying
more expensive UPSes, PoE switches, and PoE access points for new
schools. This means that the server and switch are connected to mains
power via a UPS which hopefully protects them, and none of the APs are
connected directly to the mains (instead they get Power over Ethernet)
which hopefully offers some isolation from bad electrical conditions.

This equipment is expensive, especially in places like Nicaragua where
lots of import taxes are applied. But the hope is that the investment
pays off in that the equipment doesn't get zapped.

However, one week after deploying this equipment in the first school,
we are left with a server that doesn't boot, 3 out of 4 access points
broken with a nice burning electronics smell, and a broken switch with
a lot of visible damage to the electronics.

And the most surprising thing - we had not even turned on the network
yet, pending some electrical work. Everything was connected up except
one crucial link - the UPS was not plugged into mains power. So all of
this damage happened without any of the devices having a connection to
the mains.

Connectivity-wise, the setup was:
WAN: Phone line - ADSL modem - XS
LAN: XS - Switch - 4 APs

And power connections: the XS, ADSL modem and switch were connected to
the UPS. The APs were connected to the switch over ethernet for both
power and data. Again, since the battery was not connected to mains
power, none of the devices had a power source.

The connectivity engineer's best bet is that a lightening bolt landed
at the school or nearby, and that this caused a power surge on the
phone line. This surge passed through the ADSL modem, server, switch,
and 4 APs, destroying everything in its path (except 1 AP that was
connected over a longer cable than the rest).

I figured this is a story worth sharing, for any other projects
considering splashing out on more expensive equipment...

Also, I'm wondering if anyone has any advice/experience here. Would
others expect this more expensive setup to be more resilient to bad
electrical conditions than a cheaper setup - will the investment pay
off?

I figure that the case of a lightening bolt might be a bit extreme,
but electrical storms are a nightly occurance here almost daily during
the 6 month rainy season.

I have seen that some UPSs (unfortunately not these ones) allow a
phone line to be passed through them, supposedly offering some
protection. Would such a system protect against a lightening bolt,
assuming thats what happened here?

Thanks
Daniel
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: Install Firefox

2013-05-30 Thread Daniel Drake
On Wed, May 29, 2013 at 11:50 PM, Peter Robinson pbrobin...@gmail.com wrote:
 Firefox and xulrunner 17 are the late known good (and matching) builds
 for Fedora 17, you need the major versions to be matching (so
 12/13/17) but if you were pulling in all the latest stable updates
 into the build you would have matching ones AFAICT from koji so
 there's some other issue.

Ah yes, you are right, the latest available versions on koji are
matching (v17) and built OK. I didn't spot them in the mass of failed
builds. So the Fedora situation is OK.

 I'm not sure what the following lines translate to but you should
 never use the koji repositories as repos as they contain all sorts of
 randomly tagged bits that the release repos don't.

 olpc_frozen_1=0,koji.dist-f17-armv7hl
 olpc_frozen_2=0,koji.dist-f17-armv7hl-updates-12.1.0

Don't worry, these are not the koji repos you are thinking of. They
are OLPC's frozen versions of fedora repos from the release's freeze
date and are not directly from koji - really we should change the
naming scheme.

And this is the cause of the problem - upon release freeze date, the
firefox/xulrunner situation was in inconsistent state; this problem
has been frozen in our repos.

Basanta, I would advise against adding the official fedora-updates
repo into your build as has been suggested in this thread - while this
will result in a well matched firefox/xulrunner combination, it will
bring in a lot of untested package updates that were not part of the
release and have probably not been tested on OLPC XO.

Instead, create a local repo with these 2 packages and add it to your
build config:
http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=109570
http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=116355

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


13.2.0 release candidate 2 (build 8) released

2013-05-30 Thread Daniel Drake
Hi,

We're pleased to announce the next release candidate of our new 13.2.0
software release.

Information and installation instructions can be found here:
http://wiki.laptop.org/go/Release_notes/13.2.0

Quick links for those who know which files need to be grabbed and save
to USB disks:
http://download.laptop.org/xo-4/os/candidate/13.2.0-8
http://download.laptop.org/xo-1.75/os/candidate/13.2.0-8
http://download.laptop.org/xo-1.5/os/candidate/13.2.0-8
http://download.laptop.org/xo-1/os/candidate/13.2.0-8

This is a signed release candidate that can be installed on all XOs,
even those with security enabled.

We're looking for any final testing and feedback on all aspects of the
system. Thanks for any help you can offer, and for all the feedback
that was received throughout development.


Changes since the last release candidate:

FotoToon-15 fixes touch widget accessibility (SL#4500)

Jukebox-31 fixes an inability to open the Journal file picker (SL#4510)

Portfolio-42 fixes audio recording (#12686)

Write-90 has working collaboration again (SL#4482)

Suspend from GNOME now powers down the screen again (#12321)

A problem with occasional invisible text on XO-1.5 has been solved (#12438)

Cairo can now correctly draw transparent rectangles on XO-1.75 and XO-4 (#12681)

An occasional audio playback hang on XO-1.5 has been fixed (#12580)

XO-4 can now cleanly resume an ongoing sound stream at system resume
time (#12596)

XO-4 firmware Q7B32 fixes a high EC power consumption issue (#12689)

A bluetooth-related common system hang on XO-4 suspend has been fixed (#12657)

powerd no longer chokes on negative dates (#12621)

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


Re: Install Firefox

2013-05-29 Thread Daniel Drake
On Tue, May 28, 2013 at 9:40 PM, Basanta Shrestha
basanta.shres...@olenepal.org wrote:
 Adding firefox did install firefox but gave following error while trying to
 execute on XO:
 
 $ firefox
 Error: Platform version '13.0' is not compatible with
 minVersion = 12.0
 maxVersion = 12.0
 -

Looks like an incompatibility with xulrunner, which hasn't been
successfully built on F17 in a while:
http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=10131
Maybe Peter has some comments.

You could try an older version of firefox to match the latest (old)
version of xulrunner available.

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


Re: Install Firefox

2013-05-23 Thread Daniel Drake
On Wed, May 22, 2013 at 10:36 PM, Basanta Shrestha
basanta.shres...@olenepal.org wrote:
 Hi there,
 I use fedora ARM to build OS for XO1.75. I have recently successfully built
 OS12.1.0 using olpc-os-12.1.0-xo1.75.ini. Now I am in need of preparing a
 build with firefox and flashplugin. Is it possible? If yes, what addition do
 I need to make on which files? Please suggest.

You can use the olpc-os-builder custom_pkgs module to add firefox, and
the adobe_flash module to add the flash player plugin for ARM which
you presumably already have stored separately.

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


Re: 13.2.0 schedule update

2013-05-23 Thread Daniel Drake
On Mon, May 13, 2013 at 1:22 PM, Daniel Drake d...@laptop.org wrote:
 May 23 - packages and activities frozen, first signed release
 candidate published, only fixes to significant regressions taken
 beyond this point.

We have now reached this point, the release candidate will be
published momentarily.

Packages and activities have been frozen as of build 7, we're only
taking regression fixes at this point, and updated activities/packages
must be requested (its no longer automatic).
http://wiki.laptop.org/go/Release_Process/Stabilization#Contributing_changes

I would appreciate the focus to remain on important issues only.

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


13.2.0 release candidate 1 (build 7) released

2013-05-23 Thread Daniel Drake
Hi,

We're pleased to announce the first release candidate of our new
13.2.0 software release.

Information and installation instructions can be found here:
http://wiki.laptop.org/go/Release_notes/13.2.0

Quick links for those who know which files need to be grabbed and save
to USB disks:
http://download.laptop.org/xo-4/os/candidate/13.2.0-7
http://download.laptop.org/xo-1.75/os/candidate/13.2.0-7
http://download.laptop.org/xo-1.5/os/candidate/13.2.0-7
http://download.laptop.org/xo-1/os/candidate/13.2.0-7

This is a signed release candidate that can be installed on all XOs,
even those with security enabled.

We're looking for any final testing and feedback on all aspects of the
system. Thanks for any help you can offer, and for all the feedback
that was received throughout development.

One significant known issue is an XO-4 crash when it goes into deep
sleep with the screen off, which can also be triggered in other
similar sleep modes (#12657). This will be fixed for the next
candidate build.

Changes since the last development build:

Write's document view is no longer corrupted when working in rotated
modes on XO-1.75 and XO-4 (#12339)

Maze no longer spams log files with a harmless sound error (#12677)

Buggy wireless networks no longer disappear from view (#12670)

XO-1.75 speakers no longer become muted after headphone use (#12683)

Squashfs support is present for XO-1.75 and XO-4 (#12682)

The XO-1.75 activation initramfs works again (#12672)

XO-1.75 and XO-4 bootup is no longer interrupted by the presence of an
NTFS filesystem on a USB disk. (#12678)

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


Re: 13.2.0 release candidate 1 (build 7) released

2013-05-23 Thread Daniel Drake
On Thu, May 23, 2013 at 8:47 AM, Daniel Drake d...@laptop.org wrote:
 One significant known issue is an XO-4 crash when it goes into deep
 sleep with the screen off, which can also be triggered in other
 similar sleep modes (#12657).

We've hopefully fixed this issue now, ready for the next build. If
anyone wants to help test on unsecured XO-4s, the command is: yum
update kernel

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


Re: 13.2.0 schedule update

2013-05-15 Thread Daniel Drake
On Mon, May 13, 2013 at 1:22 PM, Daniel Drake d...@laptop.org wrote:
 May 23 - packages and activities frozen, first signed release
 candidate published, only fixes to significant regressions taken
 beyond this point.

To clarify/correct this point:

The build will actually be made a day before. So packages and
activities will actually be frozen on May 22.
This means that the deadline to publish general stuff for 13.2
inclusion is May 21.

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


13.2.0 development build 6 released

2013-05-13 Thread Daniel Drake
Hi,

http://wiki.laptop.org/go/13.2.0
http://build.laptop.org/13.2.0/os6


TamTam updated to v67: fixes audio crackle on XO-4 (#12651)

JournalShare updated to v5

TurtleBlocks updated to v176

The XO-4 bluetooth driver is now loaded, it coexists happily with the
wireless driver (#12657)

XO-4 audio recording works cleanly again (#12400)

XO-4 with 8787 no longer wakes up on all multicast frames (#12605)

Spanish high school keyboard works again (#12645)

Thanks for testing  feedback!
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: 13.2.0 development build 6 released

2013-05-13 Thread Daniel Drake
On Mon, May 13, 2013 at 10:19 AM, Daniel Drake d...@laptop.org wrote:
 Hi,

 http://wiki.laptop.org/go/13.2.0
 http://build.laptop.org/13.2.0/os6

Sorry, made a silly mistake in a kernel patch, and XO-4 audio is not
working as a result.
To fix: yum update kernel

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


13.2.0 schedule update

2013-05-13 Thread Daniel Drake
Hi,

Development on 13.2.0 is going well, we are completing all of the
things we planned to work on. We have defined a schedule:

May 23 - packages and activities frozen, first signed release
candidate published, only fixes to significant regressions taken
beyond this point.
June 13 - final 13.2.0 release.

http://wiki.laptop.org/go/13.2.0/Release_plan has been updated.

Thanks for testing  feedback!
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Question About 13.1.0 on XO-1s

2013-05-04 Thread Daniel Drake
On Fri, May 3, 2013 at 9:31 PM, Caryl Bigenho cbige...@hotmail.com wrote:
 Hi Daniel,

 Do they have to be completely reflashed? They cannot be connected to the
 internet since they are in a shelter for battered women and it is a very
 secure facility. That is why we are field testing Braddock Gaskill's
 Internet-In-A-Box server there.

There is no need to reflash. Just turn them off, plug in external
power, and turn them on again.

This is assuming the first message is the one I am suspecting (about
not updating firmware due to lack of external power).

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


13.2.0 development build 5 released

2013-05-03 Thread Daniel Drake
Hi,

http://wiki.laptop.org/go/13.2.0
http://build.laptop.org/13.2.0/os5

The XO-1.75 build is missing at the moment, it will be added shortly.

Changes are:

Help updated to v16

JournalShare updated to v4

Log updated to v34

MusicKeyboard updated to v7: no longer crackles on XO-4. TamTam still
crackles until the next release is made. (#12651)

TurtleBlocks updated to v175

eToys audio recording now works on XO-4. (#12549)

gobject-introspection optimizations improve Sugar startup time,
activity launch time, and possibly improve performance during general
activity usage (#12631).

We now make full use of audio buffers on XO-4 (#12400)

Screen rotation no longer results in graphics corruption on XO-1.75
and XO-4 (#12542)

GNOME hung on launch on 13.2.0 build 4 for XO-4, this is now fixed (#12658)

Latest firmware releases fix an XO-1.5 time reset problem (#12660) and
a XO-1/XO-1.5 NFS problem (#12662)

Notable package updates: gstreamer1, systemd.

vMeta is now available (via gstreamer-0.10) for XO-4, as well as
XO-1.75, and it is now more stable than before on both platforms.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: 13.2.0 development build 5 released

2013-05-03 Thread Daniel Drake
On Fri, May 3, 2013 at 3:06 PM, Daniel Drake d...@laptop.org wrote:
 Hi,

 http://wiki.laptop.org/go/13.2.0
 http://build.laptop.org/13.2.0/os5

 The XO-1.75 build is missing at the moment, it will be added shortly.

The XO-1.75 build has now been published.

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


Re: Question About 13.1.0 on XO-1s

2013-05-03 Thread Daniel Drake
On Fri, May 3, 2013 at 8:06 PM, Caryl Bigenho cbige...@hotmail.com wrote:
 Hi...

 Today I was helping some folks reflash the XO-1s they will be using in a
 small deployment in Los Angeles. After installing 13.1.0 we found that a
 scrolling display of code or something white on black... went by too
 fast to read appeared on startup. This was not just on the first startup,
 but on all startups. Is this necessary? If not, can it be turned off? How?

Take a look at the very first messages that appear when you turn the
laptop on - those ones (if any) are much easier to read.

Most likely it says something like: Not updating firmware now - no
external power

If so, connect external power, power up again, it will upgrade the
firmware then you will be back to normal.

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


Re: Update firmware with a custom image

2013-04-28 Thread Daniel Drake
On Sun, Apr 28, 2013 at 2:08 PM,  lio...@olpc-france.org wrote:
 I’ve created my own image using OS Builder and customized the bootloader.

 So I’ve got now an USB key that update the os image but I wonder if the key
 could update also the firmware version.

 I understand that the OS Image embed a new firmware. Is it the case?

Yes, check the packages.txt output file from olpc-os-builder, look for
the bootfw or olpc-firmware-q* package version. That firmware is
included in the image and laptops will auto-upgrade on first boot.

 Is there a way to upgrade the firmware easily from the customized
 bootloader?

It's possible, but it might be a little tricky since you would have to
put appropriate code in your olpc.fth boot script on the USB disk. For
simplicity I would stick with the OS-embedded firmware upgrade unless
that is going to be problematic.

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


13.1.0 release candidate 8 (build 36) released

2013-04-22 Thread Daniel Drake
Hi,

We're pleased to announce the next release candidate of our new 13.1.0
software release.

Information and installation instructions can be found here:
http://wiki.laptop.org/go/Release_notes/13.1.0

Quick links for those who know which files need to be grabbed and save
to USB disks:
http://download.laptop.org/xo-4/os/candidate/13.1.0-36
http://download.laptop.org/xo-1.75/os/candidate/13.1.0-36
http://download.laptop.org/xo-1.5/os/candidate/13.1.0-36
http://download.laptop.org/xo-1/os/candidate/13.1.0-36

This is a signed release candidate that can be installed on all XOs,
even those with security enabled.

This build had previously been released (and is unchanged) for XO-4,
now we add the other laptop models to the mix and declare it a release
candidate. It is likely that this build will become 13.1.0 final
within a few days.

We're looking for any final testing and feedback on all aspects of the
system. Thanks for any help you can offer, and for all the feedback
that was received throughout development.


Changes since the previous release candidate:

Write-87 fixes collaboration (SL#4436)

Simultaneous audio recording/playback should be working now (#12606).
The Distance activity is working.

Wireless 8787 power saving is disabled, matching 8686. Solves some
unreliability issues with collaboration.

XO-4 automatic power management is disabled by default. We are still
battling some stability issues with suspend/resume and wakeups. This
will be addressed in a future release.

The new siv120d camera often found in the XO-1.75 and XO-4 now works
when installed in the XO-1.5 and XO-1 (#11611, #12623)

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


Re: Aggressive screen blanking with 13.1.0 build 35

2013-04-18 Thread Daniel Drake
On Thu, Apr 18, 2013 at 3:41 PM, James Cameron qu...@laptop.org wrote:
 Yes, SKU198 doesn't have DCON RAM.

 #10916 has some additional history only half of XO-1.75 B1s have DCON
 RAM -- those that have mechanical keyboards. and SKU-198 (which
 don't have DCON RAM).

And as this is pre-production hardware, with the problem in question
being a physical lack of a specific component on the motherboard, this
is not something that will be fixed by going to newer (or older)
software builds. Sorry about that. I suggest that you just turn off
automatic power management from the Sugar control panel to avoid the
annoyance.

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


13.2.0 development build 4 released

2013-04-16 Thread Daniel Drake
Hi,

http://wiki.laptop.org/go/13.2.0
http://build.laptop.org/13.2.0/os4

Latest Sugar (0.98.7) and activity updates:
- Browse updated to v151.
- FotoToon updated to v14.
- JournalShare updated to v3.
- Jukebox updated to v30.
- Log updated to v33.
- Read updated to v108.

GTK3 fix for Sugar clipboard (SL#4483)

olpc-update should work again (#12650).

Latest XO-4 firmware fixes bluetooth test (#12655).

Scratch audio recording now works on XO-4. (#12498)

XO-1.75/XO-4 should no longer experience graphics corruption after
screen rotation (#12542).

Latest package updates including systemd, maliit and wpa_supplicant
(should improve roaming).


Thanks for testing!
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Updating from 31035o[0,2] to 32002o[0,2]

2013-04-16 Thread Daniel Drake
On Wed, Mar 27, 2013 at 11:13 PM, Yioryos Asprobounitis
mavrot...@yahoo.com wrote:
 On the XO-1 olpc-update failed on 2 consecutive attempts  with different 
 manifest error each time.
 In both case when was getting tight on disk space.
 The update requires significant free space (more than 250MB) and time (more 
 than 2 hours).
 Maybe olpc-update from 13.1.0 to 13.2.0 is un-realistic for the XO-1.
 It requires major cleanup and Activity/Library deletions before attempted.

Maybe so. Sounds like a similar situation to previous major upgrades.

 On the XO-1.75 the update finished eventually (in more than an hour) OK. 
 Updated the firmware upon reboot fine.
 Software update found all the activities up to date.
 I'm assuming the G1G1 Activities list is not updated to include Journal 
 Share, Music Keyboard, Paint-57 etc.

Yes, that will happen later.

 Though I can not tell if it was because of the update or the (manual) 
 installation of Music Keyboard, the XO-1.75 had no sound (not because was no 
 mute ;).
 This persisted through reboots and was fixed after running `alsamixer -V all' 
 (without changing any setting).

There were sound problems on 13.1.0 build 2 on XO-1.75, although I
can't explain why alsamixer changed anything (I couldn't reproduce
this fix). Anyway, this is fixed in newer builds. I just tested an
upgrade from 13.1.0 build 35 to 13.2.0 build 4 on XO-1.75 and sound is
working as usual.

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


Re: [Server-devel] ds-backup

2013-04-16 Thread Daniel Drake
On Fri, Apr 5, 2013 at 3:16 PM, George Hunt georgejh...@gmail.com wrote:
 Hi Daniel,

 I noticed that you were working on ds-backup recently.  I was trying to get
 XSCE running on fc18, and encountered the issue of fedora dropping
 mod-python (see https://fedorahosted.org/rel-eng/ticket/5165).

 Is it ok to just carry the fc17 version along in our repo, and try to see if
 it just works, or should we set a goal of rewriting to mod_wsgi?

Carrying along an old mod_python might be tricky, I think F18 has a
new apache version with some incompatibilities.

I would port it to wsgi.

Daniel
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: olpc-dev-kernel and yum update

2013-04-12 Thread Daniel Drake
On Wed, Apr 3, 2013 at 8:48 PM, John Watlington w...@laptop.org wrote:

 This isn't a bug report, just an observation to keep anyone else from
 spending time on this known condition (cjb's comment was of course!):

 If you want to update a kernel on a 13.1.0/13.2.0 build, you must first
 run olpc-dev-kernel.   Running it after doing the yum update kernel
 will result in a confused system, which cannot be fixed using yum alone.

Just retested:

If you want to update a kernel to a newer official kernel from the
repos, yum update and reboot is enough. No need to run
olpc-dev-kernel at any point.

If you want to run a custom kernel, you need to ensure that an
unzipped initramfs is available on disk. One way to achieve this is to
install/upgrade a kernel RPM, another way is to run olpc-dev-kernel.

Running yum update to retrieve a new kernel, then rebooting, and
running olpc-dev-kernel (for which there is no reason) and rebooting
again, left me with a usable system (albeit running from the kernel
originally shipped in the build).

I suspect in this case you didn't mean to run olpc-dev-kernel (since
yum update had already done the equivalent, allowing you to boot your
own custom kernel with no further steps) and indeed this was an
unintentional behaviour change on top of an earlier version. I might
tweak the behaviour next time I'm working in that area.

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


Re: Re: 13.2.0 development build 3 released

2013-04-08 Thread Daniel Drake
On Sun, Apr 7, 2013 at 3:19 PM,  fors...@ozonline.com.au wrote:
 updating build2 to build3

 [olpc@xo-92-f0-ca ~]$ sudo olpc-update 13.2.0d_xo4-3
 Downloading contents of build 13.2.0d_xo4-3.
 Updating to version hash 41492c63f1bb3013b6b8582ac26057ad
 Trying irsync_pristine update from 
 rsync://updates.laptop.org/build-13.2.0d_xo4-3
  - Fetching contents.
  - Performing incremental rsync.
  - Cleaning up (trac #5051)
 Verifying update.
 Contents manifest failure at line 453
 Last file examined: ping

Thanks, filed http://dev.laptop.org/ticket/12650

This should be fixed for the next build.

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


Re: 13.2.0 development build 3 released

2013-04-07 Thread Daniel Drake
On Sun, Apr 7, 2013 at 3:10 AM,  fors...@ozonline.com.au wrote:
 Hi

 olpc-update 13.2.0d_xo4-3

 contents manifest failure at line453

Please share the full error message, and let us know which build you
are updating from.

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


13.2.0 development build 3 released

2013-04-06 Thread Daniel Drake
Hi,

http://wiki.laptop.org/go/13.2.0
http://build.laptop.org/13.2.0/os3

Another XO-4 bad touchscreen/mouse input interaction was fixed (#12640).

XO-4 cursor corruption after suspend should be fixed (#12556).

An occasional XO-4 8787 wireless failure after wake-on-LAN should be
fixed (#12573).

Some 8787 command queueing bugs were fixed, fixing some occasional
warnings on suspend (#12442).

A libdconf crash preventing various things from working on XO-1 is
fixed (#12639).

XO-1.75 and XO-4 now longer present a harmless kernel panic at the
final stage of power-down (#11785, #12100).

XO-1.75 audio with the latest firmware is working again (#12637).

wacom module is now included (#12642).

Scratch updated to v24; fixes a failure to launch in previous builds.

Latest packages including minor NetworkManager and gstreamer-1.0 updates.

Thanks for testing!
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: wifi power on/off

2013-04-05 Thread Daniel Drake
On Fri, Apr 5, 2013 at 3:36 PM, Mikus Grinbergs mi...@mikusj.com wrote:
 If the system were to use several (static) self-assigned addresses, and
 ifconfig eth0 down was the way to terminate the use of the current IP
 address so that the next IP address could be activated - would it be
 desirable to have the hardware power off on ifconfig down ?

If you create multiple interfaces for the hardware it will do the
right thing, not powering down the hardware while an interface is
active.

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


Re: olpc-dev-kernel and yum update

2013-04-04 Thread Daniel Drake
On Wed, Apr 3, 2013 at 8:48 PM, John Watlington w...@laptop.org wrote:

 This isn't a bug report, just an observation to keep anyone else from
 spending time on this known condition (cjb's comment was of course!):

 If you want to update a kernel on a 13.1.0/13.2.0 build, you must first
 run olpc-dev-kernel.   Running it after doing the yum update kernel
 will result in a confused system, which cannot be fixed using yum alone.

I don't see why, sounds like a bug. Or is there something I'm missing?

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


Re: [Testing] 13.2.0 development build 2 released

2013-04-01 Thread Daniel Drake
On Thu, Mar 28, 2013 at 1:37 AM, Hal Murray hmur...@megapathdsl.net wrote:

 Would somebody with an XO-1 please try switching to Gnome.  Mine went into a 
 loop trying to start X.

I reproduced this too. Filed http://dev.laptop.org/ticket/12643
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Problem compiling bios-crypto in XO1.75 hardware

2013-04-01 Thread Daniel Drake
On Mon, Apr 1, 2013 at 10:51 AM, Juan Cubillo jcubi...@fundacionqt.org wrote:
 Hello,

 I'm creating xo1.75 OS images on a 1.75 XO since that's the only ARM
 hardware I have around. In order to sign the images I need to compile
 bios-crypto following the instructions from the wiki:

 http://wiki.laptop.org/go/OS_Builder#Signing_preparation

 make is not finishing correctly and ends with the following error message:

 bash-4.2# make

Have you tried using the exact instructions given at
http://wiki.laptop.org/go/OS_Builder#Signing_preparation

$ cd bios-crypto/build
$ make cli

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


Re: Problem compiling bios-crypto in XO1.75 hardware

2013-04-01 Thread Daniel Drake
On Mon, Apr 1, 2013 at 11:12 AM, Juan Cubillo jcubi...@fundacionqt.org wrote:
 Yes, I cloned the git repo, changed directory and issued the make command
 but I get the error described. I'm running this on the latest stable image
 for the xo1.75.
 From your reply I assume that this error is not normal. Should the make work
 with no issues on arm hardware?

In your mail you seem to be in the bios-crypto root directory, and you
ran make.
However following the instructions you should be in the
bios-crypto/build directory and the command is make cli.

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


Re: gnome error on WebActivity in 12.1.0 custom

2013-03-31 Thread Daniel Drake
On Sun, Mar 31, 2013 at 1:26 AM, Lionel Laské lio...@olpc-france.org wrote:
 BTW I don't understand where this version come from:
 - Latest Browse version mentioned on Sugar App store is 129 [1],

Click View older versions to view newer versions
http://activities.sugarlabs.org/en-US/sugar/addons/versions/4024
or access the page inside sugar-0.96 itself.

 - Latest Browse version mentioned on Laptop.org G1G1 is 122.2 [2].

http://wiki.laptop.org/go/Activities/G1G1/12.1
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: gnome error on WebActivity in 12.1.0 custom

2013-03-31 Thread Daniel Drake
On Sun, Mar 31, 2013 at 2:26 PM,  lio...@olpc-france.org wrote:
 But: why the latest version is not... the latest version?

The activities.sugarlabs.org admin has decided which version of Sugar
is the most common (he picked an old one, maybe 0.94?), and the
website offers up activities compatible with that Sugar version as
latest. That's unless you access the above URL or the website in
general from within Browse itself, in which case it accurately detects
which Sugar version you want.

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


Re: Confusion regarding 13.1.0 / 13.2.0

2013-03-29 Thread Daniel Drake
On Wed, Mar 27, 2013 at 4:03 PM, Christoph Derndorfer
christoph.derndor...@gmail.com wrote:
 Hey everyone,

 after seeing the 13.2.0 build 2 discussions this morning I'm a bit confused.
 Has 13.1.0 been declared stable and released yet? For all XO models?

The current status is noted in the 13.2.0 build 1 announcement:

13.1.0 was developed with a focus on XO-4 factory requirements for
mass production. We are now very close to that point, so it is likely
that build 36 will be marked as 13.1.0 final shortly.

We are still waiting for final test results from the factory. That
should happen soon.

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


13.2.0 development build 2 released

2013-03-26 Thread Daniel Drake
Hi,

http://build.laptop.org/13.2.0/os2

Sugar updated to 0.98.6. Welcome screen is back (#12628) and now
unlocks the screen at the correct moment (#11995).

Paint updated to v57.

The Journal Share activity was added. This is a prototype/experiment.
We want to provide a non-intrusive initial solution to the problem
where teachers handing out work in a classroom (and collecting
assignments) is not currently easily done in Sugar.

The Music Keyboard activity was also added. This is like a Piano that
you can play with the keyboard or the touchscreen.

The touchscreen was quite unusable in build 1, it should now be
working again (#12630).

First boot is no longer slow.

XO-4 8787 wireless scans faster than before.

Latest packages including a NetworkManager update.

Latest firmware releases on all platforms.


Thanks for testing!
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Customize default language with OS Builder

2013-03-25 Thread Daniel Drake
On Mon, Mar 25, 2013 at 3:16 AM,  lio...@olpc-france.org wrote:
 Great ! I did'nt know that default language could be change directly in the
 firmware.
 I guess it depends of the SKU value. Could I set French with an English
 keyboard ?

Yes. LO is for system language, KL is for keyboard language.

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


Re: Auckland Testing Summary 23 March 2013

2013-03-25 Thread Daniel Drake
Thanks for testing.

On Sat, Mar 23, 2013 at 2:43 AM, Tom Parker t...@carrott.org wrote:
 No sound in TamTam or Speak on 3 out 5 XO-1.75s. Speak hung when saying a
 sentence, scratch failed to start with an error in it’s log about missing
 sound driver. Record hangs when you take a photo on those laptops that have
 broken sound. We have discovered that this is related to firmware Q4D27, as
 the two laptops that worked were still on Q4D24. Updating them caused the
 sound to stop working.

Thanks, I've filed http://dev.laptop.org/ticket/12637

 On Karearea, the UI did not respond to mouse clicks or keyboard input, but
 the neighbourhood/friends/activity list keys worked. After 3 reboots this
 started working and we discovered the wifi doesn’t work, eth0 exists but is
 not configured. This laptop is one of the ones on which sound does not work.

 I have the /var/log/messages from a few laptops including Karearea's bad
 wifi boot if anyone is interested.

I would be interested in that log.

 The context menu on the activity ring is annoying. It takes a long time to
 appear and disappear.

Has this changed since 13.1 (or some other release?).

 Battery life on XO-4 C2 seems significantly improved over previous builds.
 We would be interested in a confirmation or otherwise of this in the power
 log analysis.

I guess you are comparing to 13.1.0 build 36?
The big difference here is that 13.1.0 build 36 has automatic power
management disabled, it is now enabled in 13.2.0 (not 100% stable just
yet, but we continue to shake out the bugs).

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


Re: minimizing footprint

2013-03-25 Thread Daniel Drake
On Sun, Mar 24, 2013 at 4:34 PM, Paul Fox p...@laptop.org wrote:
 i think the point john (gilmore) was making is that it's a bad
 precedent that simply because a) systemd offers a second-rate API for
 scheduling events, and b) we only have a couple of uses for an event
 scheduler, that we should therefore switch from a well-established API
 to a lousy API.  instead, if systemd can be made to support the cron
 API properly, it would be worth making it do so.

systemd's cron-like API is actually more powerful than cron, in that
it can schedule based on seconds precision, and offers monotonic
clocks in addition to calendar times.

It is true that it has not passed the test of time.

 barring that, or if it's too much work (likely), then if it saves us
 boatloads of disk to make the switch, and our use-cases don't lose
 functionality or correctness as a result, then i guess we should
 switch.

It's not a huge saving, but a small amount of work to eliminate a
daemon that runs all the time on every laptop seems worth it to me.

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


Kernel RPMs now auto-install to boot partition

2013-03-22 Thread Daniel Drake
Hi,

Found some time to implement something that has been desired for a
while: now when you install a kernel RPM on the XO, it will
additionally auto-install to the boot partition, so now you can just
install a new kernel RPM with rpm/yum and reboot and expect it to be
used, no additional steps needed.

The root of this strange behaviour (installing kernels twice) is due
to the design of the update system, there might be room to improve on
this in future as well, but at least this detail will now be less
annoying to developers.

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


Removing cron in 13.2

2013-03-21 Thread Daniel Drake
Hi,

As a simple step in reducing base system footprint a little, I'm
thinking of removing cron in 13.2.0.

The 2 current users of cron (ds-backup and olpc-update-query) will be
moved to systemd timer units which have equivalent functionality.

Any objections?
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: XO-1 Sugar startup profiling

2013-03-19 Thread Daniel Drake
On Mon, Mar 18, 2013 at 8:26 AM, Daniel Drake d...@laptop.org wrote:
 2. Do python-level profiling of sugar to figure out why we are also
 spending a lot of time executing pure Python code.

Its easy to hook up the python profiler:

Change the last line of /usr/bin/sugar to

exec python -m cProfile -o /tmp/sugar.prof /bin/sugar-session

Then after sugar exits (e.g. if you add the idle gtk.main_quit call
mentioned earlier) you can run:

python -m pstats  /tmp/sugar.prof

and play away.

The top offender in the startup (which now takes 12 seconds on XO-1.5)
is {method 'send_message_with_reply_and_block' of
'_dbus_bindings.Connection' objects}

Seems to be called 171 times and takes a total of 2.47 seconds.

I guess this means we are sending 171 synchronous dbus messages during
startup. Would be nice to make them async.

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


Re: video broken on 1.75?

2013-03-19 Thread Daniel Drake
On Mon, Mar 18, 2013 at 7:37 PM, Sameer Verma sve...@sfsu.edu wrote:
 We have a bunch of XO 1.75 going to Madagascar. These have build
 13.1.0 (candidate 35). This ogv file [1] works well on a XO-1 but does
 not play via jukebox. The ogv file plays well in Browse (trouble with
 going fullscreen). It plays ok for a few seconds via MediaPlayer in
 GNOME.

 [1] http://verma.sfsu.edu/projects/olpc/sample-for-xo.ogv

Thanks for reporting.
Unfortunately there are many ogg theora files that don't play back on
XO-1.75, but they normally fail with an error message:
http://dev.laptop.org/ticket/12004

So I filed a new ticket for this video: http://dev.laptop.org/ticket/12634

The reason that it works in Browse is probably that it is not using
hardware accelerated playback there.

When I saw a case of #12004 before, I worked around it by re-encoding
the video as it had some slightly special parameters. This video would
appear to be similar. It is a 320x180 video somehow encoded into the
320x192 theora resolution. I suspect if you re-encode it so that both
measurements are equal, it will work OK.

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


Re: video broken on 1.75?

2013-03-19 Thread Daniel Drake
On Tue, Mar 19, 2013 at 7:27 PM, Sameer Verma sve...@sfsu.edu wrote:
 Looking at codec info via VLC tells me that the resolution is 320x180
 but Display Resolution is 320x192
 I don't know enough about this to know the difference. How should I
 got about encoding the MP4 differently?

Maybe try:

ffmpeg2theora -x 320 -y 192

I guess this might distort the video very slightly as you are not
scaling evenly from the original format. If you put time into it you
could probably find a way to do it in a non-distorting way (adding
black bars around the edge to leave the video content as-is).

 BTW, it works fine on a XO-1. Is that because it only does software
 decoding on the XO-1?

In both your XO-1.75 case and the XO-1 case the decoding is done in
software. The accelerated part is the transfer of pixel data from
memory onto the screen. And this acceleration does work at odd
resolutions. So without code-level diagnosis it is not immediately
obvious what the problem is.

Actually, until you've tried rescaling, we're not even sure this is
the problem in question, the resolution thing is just a guess.

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


Re: [Server-devel] puppet

2013-03-19 Thread Daniel Drake
On Mon, Mar 18, 2013 at 7:17 PM, Tim Moody timmo...@sympatico.ca wrote:
 Over the years there have been a number of expressions of interest in
 puppet.  Are there any modules out there for actual XS services?

 I know about http://dev.laptop.org/git/users/martin/puppet-example/tree/,
 which has some manifests.

That's what is currently available.
If you are looking for something specific, please ask, maybe someone
can help you write the appropriate manifest.

Daniel
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


XO-1 Sugar startup profiling

2013-03-18 Thread Daniel Drake
Hi,

I spent an hour comparing and investigating Sugar startup time on XO-1
for 12.1.0 vs 13.2.0 build 1.

To measure this, I modified sugar-session to add a glib idle_add call
to gtk.main_quit(), after the other bunch of idle_add calls that are
made. Then startup can be timed by stopping X and running from a root
console:

time olpc-dm

On 12.1.0 after a couple of runs (for hot caches) this takes 22
seconds. On 13.2.0 the equivalent test takes 32 seconds.

I then re-ran the test through perf on 13.2.0 build 1.
8.66% of this time is spent in g_typelib_get_dir_entry
(libgobject-introspection).
6.79% is spent in pure Python (EvalFrameEx)
5.8% of the time is spent in libc.

Beyond that, there are no clear offenders. There are bucketloads of
places that just occupy around 0.02% of the startup time.

As the next steps I would suggest:

1. Investigate why g_typelib_get_dir_entry takes so long (maybe it is
just slow, or maybe it's being called far too many times?).
http://dev.laptop.org/ticket/12631

2. Do python-level profiling of sugar to figure out why we are also
spending a lot of time executing pure Python code.


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


Re: XO-1 Sugar startup profiling

2013-03-18 Thread Daniel Drake
On Mon, Mar 18, 2013 at 8:26 AM, Daniel Drake d...@laptop.org wrote:
 I then re-ran the test through perf on 13.2.0 build 1.
 8.66% of this time is spent in g_typelib_get_dir_entry
 (libgobject-introspection).
 6.79% is spent in pure Python (EvalFrameEx)
 5.8% of the time is spent in libc.

Oops, I meant to write g_typelib_get_dir_entry_by_gtype().

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


  1   2   3   4   5   6   7   8   9   10   >