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 #2309: hangs during resume after printing
GSTATUS4 (Openmoko Public Trac)
2. Re: Openmoko Bug #2362: 2.6.32.20 kernel from SHR-U has angle
offset in the Accelerometer's output (Openmoko Public Trac)
3. Re: Openmoko Bug #2362: 2.6.32.20 kernel from SHR-U has angle
offset in the Accelerometer's output (Openmoko Public Trac)
4. Re: Openmoko Bug #2362: 2.6.32.20 kernel from SHR-U has angle
offset in the Accelerometer's output (Openmoko Public Trac)
5. Re: Openmoko Bug #2364: Hanging micro sdhc card
(Openmoko Public Trac)
--- Begin Message ---
#2309: hangs during resume after printing GSTATUS4
--------------------+-------------------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: kernel | Version:
Severity: normal | Keywords: resume suspend kernel
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: rarely
--------------------+-------------------------------------------------------
Comment(by lindi):
< anarsoul> gena2x: lindi- : you can try to enable CONFIG_SAMSUNG_PM_CHECK
in kernel
< anarsoul> just to check that there's no memory corruption
< anarsoul> and also look through steppingstone part of u-boot to ensure
that it does not use memory at all
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2309#comment:17>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2362: 2.6.32.20 kernel from SHR-U has angle offset in the Accelerometer's
output
---------------------+------------------------------------------------------
Reporter: GarthPS | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: kernel | Version:
Severity: normal | Keywords: kernel Accelerometer
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
---------------------+------------------------------------------------------
Comment(by pwerken):
Are you (/ your apps) using the correct input device?
On the [ttp://wiki.openmoko.org/wiki/Accelerometer_data_retrieval wiki
page] it is noted that the devices moved from /dev/input2&3 to
/dev/input3&4 when using a 2.6.34 kernel.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2362#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2362: 2.6.32.20 kernel from SHR-U has angle offset in the Accelerometer's
output
---------------------+------------------------------------------------------
Reporter: GarthPS | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: kernel | Version:
Severity: normal | Keywords: kernel Accelerometer
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
---------------------+------------------------------------------------------
Comment(by lindi):
Is there any sanity in trying to hardcode such numbers? Why not just use
/dev/accelerometer-top and /dev/accelerometer-bottom in userland code?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2362#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2362: 2.6.32.20 kernel from SHR-U has angle offset in the Accelerometer's
output
---------------------+------------------------------------------------------
Reporter: GarthPS | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: kernel | Version:
Severity: normal | Keywords: kernel Accelerometer
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
---------------------+------------------------------------------------------
Comment(by pwerken):
Hardcoding such things is always a Bad Idea.
Userland can already look in /sys/class/input/inputX to find the right
device
(in this case "lis302-2 (bottom)"). Or alternatively use it to generate a
list of
found/compatible devices for the user to select from.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2362#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2364: Hanging micro sdhc card
---------------------+------------------------------------------------------
Reporter: janvlug | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: kernel | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Comment(by jama):
Seems like using non-kms config (./arch/arm/configs/gta02_defconfig) is
enough or even not using DRM kernel glamo driver (by using xf86-video-
fbdev instead of glamo).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2364#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
