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 #1670: Battery life too short; phone should
sleep (Openmoko Public Trac)
2. Re: Openmoko Bug #1670: Battery life too short; phone should
sleep (Openmoko Public Trac)
3. Re: Openmoko Bug #1549: [exposure] want to launch exposure
again while it is in the e-illume bar, need 5~10 sec
(Openmoko Public Trac)
4. Openmoko Bug #1671: SD-card non-working after resume
(Openmoko Public Trac)
--- Begin Message ---
#1670: Battery life too short; phone should sleep
-------------------------+--------------------------------------------------
Reporter: kenrestivo | Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by nomeata):
* cc: nomeata (added)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1670#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1670: Battery life too short; phone should sleep
-------------------------+--------------------------------------------------
Reporter: kenrestivo | Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by wendy_hung):
* cc: [EMAIL PROTECTED] (added)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1670#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1549: [exposure] want to launch exposure again while it is in the e-illume bar,
need 5~10 sec
--------------------------+-------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: assigned
Priority: normal | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: must have pm | Blocking:
Blockedby: |
--------------------------+-------------------------------------------------
Comment(by raster):
1) i just changed the sensitivity... look at asu dev images built these
days... have to wait for holger to propagate to stable.
2) the problem again is python (bindings). if u kept an ecore main loop
running then you could use the Signal_User event and do it all cleanly...
and in c it's trivial, as above, but python, i believe doesnt wrap these.
thus blocks their use from you (until wrapped). they were put in there for
this kind of usage scenario - if you want to use simple system signals for
some form of ipc. as such i use this in several places myself - in e17 i
use it for the init splash to synchronize startup, sigchilds are handled
all the time for exiting subprocesses (and converted to events with the
whole waitpid() thing done for you collecting exit code and other
information all nicely delivered in an event). e17 also uses sighup as a
restart and re-loadconfig signal... so it all works... but it works
because it uses the constructs created for just this (to make it reliable
and simple without "gotchas" of normal signal handlers). :( python is
being your problem - or more specifically the bindings and the fact they
are a subset. so as such signalling via sigusr1/2 will work just fine...
IF you use the constructs designed to streamline this into the main loop.
because you set your own signal handler - you removed that feature
basically (which you couldn't use anyway as the bindings don't support
it)...
now... choices are:
1. add more to the python bindings to allow use of these events:
or
2. try another mechanism that the bindings already support.
with #2 - you have fd_handlers.. you could create a pipe (named pipe
somewhere - not unix socket) and then st up an fd handler to listen for a
read on it - write to it to wake it up, on any data being written just
activate...
look for fd_handler_add in the ecore bindings...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1549#comment:16>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1671: SD-card non-working after resume
-----------------------------+----------------------------------------------
Reporter: proquar | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: OM-2007.2
Component: System Software | Version: GTA02v6
Severity: major | Keywords: sd, resume
Blocking: | Blockedby:
-----------------------------+----------------------------------------------
I'm using the 2007.2 stack on my Freerunner. Set to 'dim first, then
lock', so it automatically goes to sleep.
Kernel-version is:
uImage-2.6.24+git25+8533927964761f4e2078ccd8607b90f5acc60b93-r0-om-
gta02.bin
Openmoko goes sleeping, after a resume I cannot access the SD-card
anymore. Here's the output:
{{{
[EMAIL PROTECTED]:/media# ls card/
? ? rraa rraa �.o n �.o n
[EMAIL PROTECTED]:/media# umount card/
umount: /media/card: device is busy
umount: /media/card: device is busy
[EMAIL PROTECTED]:/media# mount card/
mount: special device /dev/mmcblk0p1 does not exist
}}}
(I had the strange characters in my console, too.)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1671>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
