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. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
2. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
3. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
4. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
5. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
6. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
7. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
8. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
9. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
10. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
11. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
12. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
13. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:16 -------
Once Bug 255 is fixed you could check the voltage/capacity at boot and only
enter slow charging mode if it is below a given threshhold. Then the Neo could
check periodically (via RTC wakeup?) and boot into fast charging mode once the
battery is charged partially.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:16 -------
Once Bug 255 is fixed you could check the voltage/capacity at boot and only
enter slow charging mode if it is below a given threshhold. Then the Neo could
check periodically (via RTC wakeup?) and boot into fast charging mode once the
battery is charged partially.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:16 -------
Once Bug 255 is fixed you could check the voltage/capacity at boot and only
enter slow charging mode if it is below a given threshhold. Then the Neo could
check periodically (via RTC wakeup?) and boot into fast charging mode once the
battery is charged partially.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:16 -------
Once Bug 255 is fixed you could check the voltage/capacity at boot and only
enter slow charging mode if it is below a given threshhold. Then the Neo could
check periodically (via RTC wakeup?) and boot into fast charging mode once the
battery is charged partially.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:59 -------
The PMU takes care of properly feeding the battery. All we need to do is tell
it how much current it can draw from the charger. But the problem isn't
deciding how to charge the battery, but to avoid trying to bring up the
system when the battery is too weak.
If we have enough juice to last a whole 7 seconds, we could indeed do the
full USB protocol exchange with the host to get permission to use 500 mA
and/or detect the charger, which also lets us use maximum power.
However, I'm afraid that a battery that's even in worse shape may not give
us enough time to get that far. With the backlight turned off (but the LCM
receiving power), my bv2 still wants 160 mA from the battery while idling
in u-boot.
A possible solution may be to do the USB protocol exchange in u-boot before
anything else if the PMU indicates a charger connect (which can be
misleading). We should be able to do this while staying within the 100 mA
envelope. Once this is done, u-boot can return to standby mode and charge
at full speed.
If the PMU doesn't indicate a charger connect, the normal startup process
would happen. I.e., the user wouldn't have to wait for USB.
But I think we still need a mechanism to catch the phone if it enters that
vicious circle. Something slightly more sophisticated than my current hack,
but not too complex either.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:59 -------
The PMU takes care of properly feeding the battery. All we need to do is tell
it how much current it can draw from the charger. But the problem isn't
deciding how to charge the battery, but to avoid trying to bring up the
system when the battery is too weak.
If we have enough juice to last a whole 7 seconds, we could indeed do the
full USB protocol exchange with the host to get permission to use 500 mA
and/or detect the charger, which also lets us use maximum power.
However, I'm afraid that a battery that's even in worse shape may not give
us enough time to get that far. With the backlight turned off (but the LCM
receiving power), my bv2 still wants 160 mA from the battery while idling
in u-boot.
A possible solution may be to do the USB protocol exchange in u-boot before
anything else if the PMU indicates a charger connect (which can be
misleading). We should be able to do this while staying within the 100 mA
envelope. Once this is done, u-boot can return to standby mode and charge
at full speed.
If the PMU doesn't indicate a charger connect, the normal startup process
would happen. I.e., the user wouldn't have to wait for USB.
But I think we still need a mechanism to catch the phone if it enters that
vicious circle. Something slightly more sophisticated than my current hack,
but not too complex either.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:59 -------
The PMU takes care of properly feeding the battery. All we need to do is tell
it how much current it can draw from the charger. But the problem isn't
deciding how to charge the battery, but to avoid trying to bring up the
system when the battery is too weak.
If we have enough juice to last a whole 7 seconds, we could indeed do the
full USB protocol exchange with the host to get permission to use 500 mA
and/or detect the charger, which also lets us use maximum power.
However, I'm afraid that a battery that's even in worse shape may not give
us enough time to get that far. With the backlight turned off (but the LCM
receiving power), my bv2 still wants 160 mA from the battery while idling
in u-boot.
A possible solution may be to do the USB protocol exchange in u-boot before
anything else if the PMU indicates a charger connect (which can be
misleading). We should be able to do this while staying within the 100 mA
envelope. Once this is done, u-boot can return to standby mode and charge
at full speed.
If the PMU doesn't indicate a charger connect, the normal startup process
would happen. I.e., the user wouldn't have to wait for USB.
But I think we still need a mechanism to catch the phone if it enters that
vicious circle. Something slightly more sophisticated than my current hack,
but not too complex either.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:59 -------
The PMU takes care of properly feeding the battery. All we need to do is tell
it how much current it can draw from the charger. But the problem isn't
deciding how to charge the battery, but to avoid trying to bring up the
system when the battery is too weak.
If we have enough juice to last a whole 7 seconds, we could indeed do the
full USB protocol exchange with the host to get permission to use 500 mA
and/or detect the charger, which also lets us use maximum power.
However, I'm afraid that a battery that's even in worse shape may not give
us enough time to get that far. With the backlight turned off (but the LCM
receiving power), my bv2 still wants 160 mA from the battery while idling
in u-boot.
A possible solution may be to do the USB protocol exchange in u-boot before
anything else if the PMU indicates a charger connect (which can be
misleading). We should be able to do this while staying within the 100 mA
envelope. Once this is done, u-boot can return to standby mode and charge
at full speed.
If the PMU doesn't indicate a charger connect, the normal startup process
would happen. I.e., the user wouldn't have to wait for USB.
But I think we still need a mechanism to catch the phone if it enters that
vicious circle. Something slightly more sophisticated than my current hack,
but not too complex either.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:59 -------
The PMU takes care of properly feeding the battery. All we need to do is tell
it how much current it can draw from the charger. But the problem isn't
deciding how to charge the battery, but to avoid trying to bring up the
system when the battery is too weak.
If we have enough juice to last a whole 7 seconds, we could indeed do the
full USB protocol exchange with the host to get permission to use 500 mA
and/or detect the charger, which also lets us use maximum power.
However, I'm afraid that a battery that's even in worse shape may not give
us enough time to get that far. With the backlight turned off (but the LCM
receiving power), my bv2 still wants 160 mA from the battery while idling
in u-boot.
A possible solution may be to do the USB protocol exchange in u-boot before
anything else if the PMU indicates a charger connect (which can be
misleading). We should be able to do this while staying within the 100 mA
envelope. Once this is done, u-boot can return to standby mode and charge
at full speed.
If the PMU doesn't indicate a charger connect, the normal startup process
would happen. I.e., the user wouldn't have to wait for USB.
But I think we still need a mechanism to catch the phone if it enters that
vicious circle. Something slightly more sophisticated than my current hack,
but not too complex either.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:59 -------
The PMU takes care of properly feeding the battery. All we need to do is tell
it how much current it can draw from the charger. But the problem isn't
deciding how to charge the battery, but to avoid trying to bring up the
system when the battery is too weak.
If we have enough juice to last a whole 7 seconds, we could indeed do the
full USB protocol exchange with the host to get permission to use 500 mA
and/or detect the charger, which also lets us use maximum power.
However, I'm afraid that a battery that's even in worse shape may not give
us enough time to get that far. With the backlight turned off (but the LCM
receiving power), my bv2 still wants 160 mA from the battery while idling
in u-boot.
A possible solution may be to do the USB protocol exchange in u-boot before
anything else if the PMU indicates a charger connect (which can be
misleading). We should be able to do this while staying within the 100 mA
envelope. Once this is done, u-boot can return to standby mode and charge
at full speed.
If the PMU doesn't indicate a charger connect, the normal startup process
would happen. I.e., the user wouldn't have to wait for USB.
But I think we still need a mechanism to catch the phone if it enters that
vicious circle. Something slightly more sophisticated than my current hack,
but not too complex either.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:59 -------
The PMU takes care of properly feeding the battery. All we need to do is tell
it how much current it can draw from the charger. But the problem isn't
deciding how to charge the battery, but to avoid trying to bring up the
system when the battery is too weak.
If we have enough juice to last a whole 7 seconds, we could indeed do the
full USB protocol exchange with the host to get permission to use 500 mA
and/or detect the charger, which also lets us use maximum power.
However, I'm afraid that a battery that's even in worse shape may not give
us enough time to get that far. With the backlight turned off (but the LCM
receiving power), my bv2 still wants 160 mA from the battery while idling
in u-boot.
A possible solution may be to do the USB protocol exchange in u-boot before
anything else if the PMU indicates a charger connect (which can be
misleading). We should be able to do this while staying within the 100 mA
envelope. Once this is done, u-boot can return to standby mode and charge
at full speed.
If the PMU doesn't indicate a charger connect, the normal startup process
would happen. I.e., the user wouldn't have to wait for USB.
But I think we still need a mechanism to catch the phone if it enters that
vicious circle. Something slightly more sophisticated than my current hack,
but not too complex either.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:59 -------
The PMU takes care of properly feeding the battery. All we need to do is tell
it how much current it can draw from the charger. But the problem isn't
deciding how to charge the battery, but to avoid trying to bring up the
system when the battery is too weak.
If we have enough juice to last a whole 7 seconds, we could indeed do the
full USB protocol exchange with the host to get permission to use 500 mA
and/or detect the charger, which also lets us use maximum power.
However, I'm afraid that a battery that's even in worse shape may not give
us enough time to get that far. With the backlight turned off (but the LCM
receiving power), my bv2 still wants 160 mA from the battery while idling
in u-boot.
A possible solution may be to do the USB protocol exchange in u-boot before
anything else if the PMU indicates a charger connect (which can be
misleading). We should be able to do this while staying within the 100 mA
envelope. Once this is done, u-boot can return to standby mode and charge
at full speed.
If the PMU doesn't indicate a charger connect, the normal startup process
would happen. I.e., the user wouldn't have to wait for USB.
But I think we still need a mechanism to catch the phone if it enters that
vicious circle. Something slightly more sophisticated than my current hack,
but not too complex either.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
else. (Hint: if you don't know who to reassign it to, make sure that
the Component field seems reasonable, and then use the "Reassign bug to
owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Just use the "Accept bug" command.
To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL
PROTECTED]
Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.
Appended below are the individual URLs to get to all of your NEW bugs that
haven't been touched for a week or more.
You will get this message once a day until you've dealt with these bugs!
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=137
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=192
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=204
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=232
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
