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 891] Don't power anything up if battery is critical and
charger is inserted ([EMAIL PROTECTED])
2. [Bug 895] libgsmd-tool crashes a lot on invalid inputs
([EMAIL PROTECTED])
3. [Bug 899] New: U-boot seems to trash another partition on
upload...? ([EMAIL PROTECTED])
4. [Bug 899] U-boot seems to trash another partition on
upload...? ([EMAIL PROTECTED])
5. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=891
------- Additional Comments From [EMAIL PROTECTED] 2007-09-29 12:59 -------
To do this right:
U-boot should:
Boot to slow mode, not fast mode (lower power, higher chance of not immediately
crashing out)
Extremely low batt: - under 2.9V, USB power on.
Turn off immediately, charge at low-rate, set RTC to wakeup in 2 min.
Low bat - V under 3.1V, USB power on:
Connected to USB bus in suspend.
Attempt to wake host.
Wake fails: beep to indicate state, power off.
Wake succeeds: next state
Connected to USB bus not in suspend:
Attempt to negotiate for 500mA as a HID device
Negotiation succeeds - high speed mode, boot.
Negotiation fails: beep to indicate state, power off.
Connected to something that is not a USB host in operational or suspend mode:
Check we have not tried high power mode in last minute.
If this has failed, then beep to indicate low-rate charge, power off.
Record that we're trying high power mode at time now.
Turn on high power mode, verify power stays stable for 10s.
High speed, Boot.
All of this happens _before_ the u-boot bootsplash screen.
These thresholds should be set so that they will work with a year old battery,
with increased ESR and lower capacity than the
------- 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=895
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
------- 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=899
Summary: U-boot seems to trash another partition on upload...?
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: dfu-util
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
I've got two GTA01Bv4 Neo's. One came as an Advanced kit the other as a Basic
kit.
Background:
Device 1 -> The basic kit came flashed with a 6 item boot menu, openmoko boot
splash image and whatever roofs.
Device 2 -> The advanced kit neo came with a two item boot menu and simply shows
fb penguin on boot.
Both devices successfully boot new-ish kernels, bootloaders and rootfs and
currently have U-boot 1.3.0-rc11.2.0+git20070917+svn2943 (Sept 17 2007 -
23:42:04) and uImage-2.6.22.5-moko11+svnr2937-r2-fic-gta01.bin.
Situation:
So instead of learning the uboot environ variables tonight (it's saturday night,
beer night) I just decided to use dfu-util to upload the uboot_env and splash
partitions from the first device to the second device.
Problem:
1. After downloading (host->neo) the uboot_env partition data, which I uploaded
(neo->host) from device 1, device 2 now has 6 menu items but the kernel
partition now has bad magic suggesting that the download of the uboot_env
partition data has trashed the uImage partition.
Downloading the uImage again rectifies this situation.
2. After downloading (host->neo) the splash partition data onto device 2, which
I uploaded (neo->host) from device 1, device has backlit but blank screen. So I
ungziped (with trailing garbage) and then re-gziped the splash image and upload,
I now have a splash on device 2.
It does not seem that I need to re-download the rootfs after downloading the
splash.
Granted, I have not done any boot prompt nand erasing... is this a bug or am I
just forgetting something?
------- 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=899
------- Additional Comments From [EMAIL PROTECTED] 2007-09-30 04:51 -------
The subject line erroneously says "on upload" but should really read "on
download of partition 2".
------- 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=41
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
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=129
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=276
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=661
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=675
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=714
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=727
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=742
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=800
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=808
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=835
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=846
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=862
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=864
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=865
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=870
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=881
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=882
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=888
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
