new milestone : stable-kernel-2009.1 / Tagging current andy-tracking as stable

[Neil Brown]

On Wednesday April 15, michael-tansella at gmx.de wrote:
> On Monday 13 April 2009 09:17:24 Nelson Castillo wrote:
> > Hi.
> >
> > In order to be able to tag current andy-tracking as a stable kernel we
> > need to fix a few bugs. Thus we have created the milestone
> > stable-kernel-2009.1. Here is the (current) list of bugs that need to
> > be fixed.
> >
> > http://docs.openmoko.org/trac/query?status=in_testing&status=reopened&statu
> >s=assigned&status=new&status=accepted&group=status&milestone=stable-kernel-2
> >009.1
> >
> > If you believe that another bug is important and that it belongs to
> > this milestone please let us know.
> 
> I think that accelerometers  still don't work properly. I used the python 
> script from the wiki: 
> http://wiki.openmoko.org/wiki/Accelerometer_data_retrieval#Test_application
> 
> I tested it with latest SHR unstable Kernel (uImage-2.6.28-
> oe1+gitr119785+2bea5c68313577b214b872b0edc5968db0cf3b68-r3.2-om-gta02.bin 
> I think this is andy-tracking, too) and should be the andy-tracking kernel of  
> April 14th.
> 
> The problem is that some values get lost. There should be one value every 10 
> ms

That is not correct.  There should be *at most* one value every 10
ms.  If there is no change between two samples, then nothing will be
reported.

The Linux input subsystem only reports ABS events when they don't
change.

NeilBrown



> 
> [time ms] [X]  [Y]  [Z] [absolute]
> 360.982 108 -36 954 960         
> 371.109 108 -36 936 942         
> 391.299 108 -18 936 942	-> lost 1 value
> 401.498 108 -18 954 960         
> 411.627 126 -18 936 944         
> 421.763 108 -36 936 942         
> 431.896 108 -36 954 960         
> 442.026 126 -18 936 944         
> 472.403 108 -36 954 960       -> lost 2 values
> 
> Greets 
> Michael
>