Send buglog mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:

   1. Re: Openmoko Bug #2145: Debian: Reading of accelerometers
      broken (Openmoko Public Trac)
   2. Re: Openmoko Bug #2145: Debian: Reading of accelerometers
      broken (Openmoko Public Trac)
   3. Re: Openmoko Bug #2145: Debian: Reading of accelerometers
      broken (Openmoko Public Trac)
   4. Re: Openmoko Bug #2185: AUX button makes interrupt storm
      (Openmoko Public Trac)
   5. Re: Openmoko Bug #2185: AUX button makes interrupt storm
      (Openmoko Public Trac)
--- Begin Message ---
#2145: Debian: Reading of accelerometers broken
-------------------------------------+--------------------------------------
    Reporter:  Defiant               |        Owner:  hardware   
        Type:  defect                |       Status:  closed     
    Priority:  normal                |    Milestone:             
   Component:  hardware              |      Version:  unspecified
    Severity:  normal                |   Resolution:  fixed      
    Keywords:  debian event2 event3  |     Haspatch:  0          
   Blockedby:                        |    Estimated:             
 Patchreview:                        |     Blocking:             
Reproducible:  always                |  
-------------------------------------+--------------------------------------

Comment(by Johannes):

 I just tried Om2008.12-om-gta02.uImage.bin and can now see what the
 original reporter has observed.

 Running the ruby script from Accelerometer_data_retrieval produces
 constant flow of data while the device is laying on the table. When I pick
 it up and start shaking it then the script stops outputting data. Display
 of interrupt count on second console now looks like this.

 {{{
      1  debian-gta02:~# while [ 1 == 1 ] ; do cat /proc/interrupts | grep
 lis302dl ; sleep 10 ; done
      2   16:        124    s3c-ext0  lis302dl
      3   60:       2866     s3c-ext  lis302dl
      4   16:        124    s3c-ext0  lis302dl
      5   60:       3060     s3c-ext  lis302dl
      6   16:        124    s3c-ext0  lis302dl
  >>> 7   60:       3245     s3c-ext  lis302dl
      8   16:        124    s3c-ext0  lis302dl
  >>> 9   60:       3254     s3c-ext  lis302dl
     10   16:        124    s3c-ext0  lis302dl
     11   60:       3259     s3c-ext  lis302dl
     12   16:        124    s3c-ext0  lis302dl
     13   60:       3449     s3c-ext  lis302dl
 }}}

 Shaking took place between line 7 and line 9 above, there are only very
 few interrupts counted although the file is permanently open.

 I must say that I'm confused now. Is this by design and expected
 behaviour?

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2145#comment:22>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2145: Debian: Reading of accelerometers broken
-------------------------------------+--------------------------------------
    Reporter:  Defiant               |        Owner:  hardware   
        Type:  defect                |       Status:  closed     
    Priority:  normal                |    Milestone:             
   Component:  hardware              |      Version:  unspecified
    Severity:  normal                |   Resolution:  fixed      
    Keywords:  debian event2 event3  |     Haspatch:  0          
   Blockedby:                        |    Estimated:             
 Patchreview:                        |     Blocking:             
Reproducible:  always                |  
-------------------------------------+--------------------------------------

Comment(by Defiant):

 Sorry, but no data from the acceleration sensor while the device is
 accelerated as expected behaviour?

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2145#comment:23>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2145: Debian: Reading of accelerometers broken
-------------------------------------+--------------------------------------
    Reporter:  Defiant               |        Owner:  hardware   
        Type:  defect                |       Status:  closed     
    Priority:  normal                |    Milestone:             
   Component:  hardware              |      Version:  unspecified
    Severity:  normal                |   Resolution:  fixed      
    Keywords:  debian event2 event3  |     Haspatch:  0          
   Blockedby:                        |    Estimated:             
 Patchreview:                        |     Blocking:             
Reproducible:  always                |  
-------------------------------------+--------------------------------------

Comment(by SimonKagstrom):

 No, that was a bug (although I can't really say what caused it). 2.6.24
 has this behavior, but newer kernels have fixed it.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2145#comment:24>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2185: AUX button makes interrupt storm
---------------------+------------------------------------------------------
 Reporter:  vnevoa   |          Owner:  openmoko-devel       
     Type:  defect   |         Status:  new                  
 Priority:  normal   |      Milestone:                       
Component:  unknown  |        Version:  Om2008.9-dev         
 Severity:  normal   |       Keywords:  AUX button interrupts
 Haspatch:  0        |      Blockedby:                       
Estimated:           |    Patchreview:                       
 Blocking:           |   Reproducible:  always               
---------------------+------------------------------------------------------

Comment(by vnevoa):

 Yes, this kernel does the right thing for me. 100% accurate after about 30
 clicks. :)

 But it also makes my Neo go WSOD on resume, which never happened before...
 I hope it is just something temporary that you are aware of. :)

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2185#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2185: AUX button makes interrupt storm
---------------------+------------------------------------------------------
 Reporter:  vnevoa   |          Owner:  openmoko-devel       
     Type:  defect   |         Status:  new                  
 Priority:  normal   |      Milestone:                       
Component:  unknown  |        Version:  Om2008.9-dev         
 Severity:  normal   |       Keywords:  AUX button interrupts
 Haspatch:  0        |      Blockedby:                       
Estimated:           |    Patchreview:                       
 Blocking:           |   Reproducible:  always               
---------------------+------------------------------------------------------

Comment(by arhuaco):

 Replying to [comment:13 vnevoa]:
 > Yes, this kernel does the right thing for me. 100% accurate after about
 30 clicks. :)

 Yay! Thanks for testing :-) Then this ticket can be marked as resolved...
 We will use a similar logic for more buttons.

 About the WSOD you might want to comment in this ticket (I seems to be
 relevant for that issue):

 https://docs.openmoko.org/trac/ticket/1841

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2185#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to