Hi Deepak,
I'm seeing one of these commits:
http://dev.laptop.org/git/olpc-2.6/commit/?h=2.6.30-rc5&id=351881b12fa5628ee44f27dd4d28482b0d66dff4
http://dev.laptop.org/git/olpc-2.6/commit/?h=2.6.30-rc5&id=8dc06e452713a214220516649d216fd603888ad9
... as stopping commands like "rtcwake -m mem -a -s
> As for speedups, I see 2 different ways :
> a) using a SD with a fat partition + ext2 filesystem
> b) using the nand with a fat partition + ubifs - this requires 2.6.29
> which is not ready yet.
>
A FAT partition will not work well on the raw NAND of XO-1, because of
blocksize, erase bloc
I still don't see how two SD cards are required. One can swap to a given
subset of an SD card and only wear out those sectors.
But no, the SD card is only temporary until we have the SDIO wireless card
in place AFAIK.
2009/6/3 Tiago Marques
>
>
> On Tue, Jun 2, 2009 at 10:51 PM, wrote:
>
>> O
If the rushes are in PAL DV, this may be useful:
$ ffmpeg2theora rawfootage.dv -x 352 -y 288 -v 2 -S 0 -K 128 -c 1 -H
32000 -o rawfootage.ogv
Sean
On Tue, Jun 2, 2009 at 5:32 PM, Seth Woodworth wrote:
> I've been emailing back and forth with Charbax, he's limited for bandwidth
> while still fi
http://wiki.laptop.org/go/OLPC:Volunteer_Infrastructure_Group#Meeting_Minutes_and_Logsis
the location.
On Thu, Jun 4, 2009 at 2:31 PM, David Farning wrote:
> Dogi,
>
> Can you post a link to the logs?
>
> david
>
> On Tue, Jun 2, 2009 at 1:05 PM, Stefan Unterhauser
> wrote:
> > The Volunteer Inf
Hello,
On Thu, Jun 4, 2009 at 07:18, John Gilmore wrote:
> Um, you're not using OLPC hardware to teach kids, but because someone
> gave it to you for free? It's not appropriate -- an ordinary netbook
I think you deserve an explain.
My first contact with OLPC was during my PhD. I studied the va
Dogi,
Can you post a link to the logs?
david
On Tue, Jun 2, 2009 at 1:05 PM, Stefan Unterhauser wrote:
> The Volunteer Infrastructure Group (/gang) Meeting is today (June 2th)
> at 4pm (EST)
>
> The Volunteer Infrastructure Group is a team of Volunteer Sysadmins
> who help maintain services and
I've just pushed to
http://dev.laptop.org/git/users/martin/olpcrd-rootskel.git an update
that teaches the initrd to ask the server for a signed time, and reset
its RTC to it.
This tests well with the clock wildly ahead and wildly behind -- I'm
hopeful that it'll help with RTC problems in the field
If you head to http://dev.laptop.org/git/projects/olpc-update/ -
you'll see a string of updates, as follows:
- It now accepts sig02 formatted leases (based on dsd's patch, adding
sig02 support).
- It will set the RTC if the OAT server gives us a signed time, and
our RTC differs by more than a d
On Thu, Jun 4, 2009 at 5:55 AM, Mitch Bradley wrote:
>> 18 seconds to initrd load
>
> dominated by decompression time. Eliminate the initrd ...
I'm working on the initrd a but so tested a few things today.
Once under linux, a cold-cache read of the initrd takes ~300ms, and
the decompression ab
> I'm not using sugar. The OLPC will be used [by doctors] to access
> drug information, so I made some different choices. At the moment,
> I am using a bootstrapped lenny where I removed everything I
> could. No udev, no hotplug but a custom made script to provide the
> firmware and do automounts,
> I'm thinking about ext4, but I must confess that my experience with ext2
> has been pretty frustrating. The ext2/3 on-disk format has sprouted many
> new features over time. Supporting people who plug in disks that are
> formatted with the latest fancy feature, then complain that an old
> firmwa
On Thu, Jun 4, 2009 at 10:36 AM, Mitch Bradley wrote:
> My point is that, while each individual step is rather straightforward,
A ton of careful detail work. As you point out, kernel, firmware and
distro hackers have been looking at this for a while, and there are no
obvious easy wins left.
If G
Martin Langhoff wrote:
>
>> Easily? Yeah, right.
>>
>
> Well, he can show us how it's done. I'll definitely be impressed :-)
>
>
>
My point is that, while each individual step is rather straightforward,
requiring no new technology, putting together all the pieces to
accomplish the goa
On Thu, Jun 4, 2009 at 5:55 AM, Mitch Bradley wrote:
>> 18 seconds to initrd load
>
> dominated by decompression time. Eliminate the initrd ...
Or pare it down significantly. I suspect that
- some bits of python libs are not used
- a newer python that does -O the right way can help
- replac
> I will try fedora 11, if only to have a good refence point.
> But since you said many of the speedups where dependant on kernel
> fixes, how is 2.6.29 doing on the XO?
> Could anyone using f11/2.6.29 on the XO give some feedback ?
Off the top of my head from the last time I tested it sound and c
On Thu, Jun 4, 2009 at 3:41 AM, Guylhem Aznar wrote:
> Of course I do, but IMHO there are also some things that could have
> been done differently.
Ah, hindsight is so easy ;-)
As Mitch's reply shows, we have been looking at the boot times and
studying any low-hanging-fruit there.
Your stat
The kernel init improvements will certainly bring 15 other seconds.
Maybe some parallelisation of the sysvinit will save some time, say 5
seconds (low end estimation)
Parallelization will not help at all if you are using JFFS2. The low
level NAND driver that JFFS2 uses busy waits for
On Wed, 2009-06-03 at 14:28 +0200, Tomeu Vizoso wrote:
> On Wed, Jun 3, 2009 at 14:21, Bryan Berry wrote:
> > I am curious if a number of other deployments have encountered this
> > problem or just us.
> >
> > We find that the XO occasionally hangs on shutdown. We are using 0.82
> >
> > I have cre
19 matches
Mail list logo
