Openmoko Bug #1682: Neo turns off before reaching X
Openmoko Public Trac
bugs at docs.openmoko.org
Wed Jul 30 10:43:42 CEST 2008
#1682: Neo turns off before reaching X
-----------------------------+----------------------------------------------
Reporter: queen6 | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: ASU
Component: System Software | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by queen6):
Replying to [comment:1 andy]:
> Charging is handled by the kernel driver, 500mA is allowed after USB
stack informs us we are enumerated by a host for 500mA.
>
> You shouldn't get forced off just because it wants to charge anyway, I
guess something else goes on.
Hmm.. that way it should initiate 500mA _before_ INIT (correct me if I'm
wrong).
Does it mean FR can't charge when it's powered down (the phone is turned
off and you connect wall charger), or will it charge but using 100mA? (if
it does, what initiate charging? HW or u-boot?)
What if the phone is suspended? Does it charge with 100mA, 500mA or
doesn't charge at all?
Anyway I can't reproduce glamo/mmc error messages linked above after
manually (dfu_util) flashing with newer kernel (btw because of
end_request: I/O error, dev mmcblk0, I couldn't access SD card at all). I
think this error message came up after opkg update (from community list it
seems you guys are aware there was/is a problem there).
I will drain my FR's battery to 0 (wifi+gps+no_apm) and see if I can
reproduce the problem.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1682#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the openmoko-kernel
mailing list