Alternate proposed logic for fs-update unused blocks optimisation

2011-04-20 Thread James Cameron
On Tue, Apr 19, 2011 at 06:09:09PM +0100, Daniel Drake wrote: > Maybe dependent on the possibility of an extX-specific optimization in > the .zd file, ... Here's another optimisation for review as well. It isn't quite extX-specific though. On a 253MB .zd4 file the fs-update took three minutes on

Re: XO power management

2011-04-20 Thread Richard A. Smith
On 04/19/2011 03:52 PM, Pablo Iguiniz wrote: > Hello Richard, > > This is Eng. Javier Iguiniz from Ceibal. Ismael has recently changed > work so I am now taking over part of his tasks, in particular the > testing related to the XO batteries. Welcome Javier. > I tried to catch up with the plan, so

Re: Alternate proposed logic for fs-update unused blocks optimisation

2011-04-20 Thread James Cameron
On Wed, Apr 20, 2011 at 05:18:50PM +1000, James Cameron wrote: > There is one small problem left to fix; Q3A64 fs-update displays an > error at the end because the total number of blocks written has not > agreed with the number of blocks specified at the top of the file. I > propose to fix that so

[PATCH 1/2] zhashfs, detect fill pattern and suppress blocks in output

2011-04-20 Thread James Cameron
Allows the unused filesystem blocks of the image to be left out of the .zd file, resulting in a factor of two reduction in fs-update times on a typical build on a 4GB microSD. Greater reduction occurs on larger microSD or SD cards. Has no effect if a fill pattern file is not found. --- bin/zhash

[PATCH 2/2] sd_card_image, create a psuedo-random pattern fill for use by zhashfs

2011-04-20 Thread James Cameron
Instead of creating a sparse image file into which the filesystems are created, create the image file from a psuedo-random pattern of 4096 bytes, so that zhashfs may skip the unused blocks. --- modules/sd_card_image/image.50.makefs.sh | 11 ++- modules/sd_card_image/postimage.50.make