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 419] dfu download doesn't clean jffs2 partition
([EMAIL PROTECTED])
2. [Bug 463] jffs2 fork error message during kernel bootup
([EMAIL PROTECTED])
3. [Bug 684] New: [PATCH] fix for endianness bug with transfer
size ([EMAIL PROTECTED])
4. [Bug 663] jffs2 image endianess depends on build hosts
byteorder ([EMAIL PROTECTED])
5. [Bug 482] phone still consumes energy when powered off
([EMAIL PROTECTED])
6. [Bug 685] New: Detect a dedicated USB charger according to
the USB battery charging specification
([EMAIL PROTECTED])
7. [Bug 90] GSM TS07.10 multiplex missing
([EMAIL PROTECTED])
8. [Bug 90] GSM TS07.10 multiplex missing
([EMAIL PROTECTED])
9. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
10. [Bug 686] New: USB descriptor incorrectly claims 5 interfaces
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=419
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-08-04 15:16 -------
I seem to have finally found the bug in question.
The calculation for the size of the to-be-erased tail of the partiton was wrong.
So while in principle it worked, the last 0x2e4000 bytes (roughly 3MB) were
never erased.
So i suspect only people who ever ended up using all/most of the rootfs
partition and actually had non-0xff data in the last 3MB would see the problem.
Fixed in SVN rev. 2632
------- 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=463
------- Additional Comments From [EMAIL PROTECTED] 2007-08-04 15:22 -------
this might be related to bug #419, i.e. a not entirely clean partition before
flashing a new rootfs.
------- 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=684
Summary: [PATCH] fix for endianness bug with transfer size
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: dfu-util
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
http://svn.nslu2-linux.org/svnroot/optware/trunk/sources/dfu-util/fix-endianess.patch
------- 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=663
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-08-04 20:06 -------
thanks, committed in svn rev. 2634
------- 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=482
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-08-04 20:09 -------
This is by now known as the 'Q1001' problem. Basically, while switching off the
S3C2410, the GSM Modem was reset by some spike on the nGSM_RESET line, which
caused the GSM Modem to power-up again.
This problem exists in GTA01Bv3 and early (phase-0) GTA01Bv4. Phase 1 GTA01Bv4
don't exhibit the problem anymore, since Q1001 was not placed during
manufacturing.
------- 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=685
Summary: Detect a dedicated USB charger according to the USB
battery charging specification
Product: Neo1973 Hardware
Version: unspecified
Platform: Neo1973
URL: http://www.usb.org/developers/devclass_docs#approved
OS/Version: Linux
Status: NEW
Severity: wishlist
Priority: P2
Component: PMU (Power Management Unit)
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
The recent Battery Charging Specification defines a way of detecting a dedicated
USB charger, without needing any special circuit on the charger itself (the
charger needs only to connect D+ to D-). According to
http://wiki.openezx.org/EMU, the Motorola chargers short D+ to D-, meaning that
if this specification is implemented, these chargers would work with the Neo.
This would need hardware changes; even with the kernel already running, it does
not seem possible to use the method described on the specification with the
current hardware.
------- 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=90
------- Additional Comments From [EMAIL PROTECTED] 2007-08-04 22:45 -------
Created an attachment (id=239)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=239&action=view)
Use struct gsmd_port instead of fd's.
Ok, attached is a working and tested patch that makes atcmd.c use the abstract
gsmd_port struct for communication, it applies on top of the Jserv's
patchset and I think it makes atcmd.c slightly cleaner.
------- 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=90
------- Additional Comments From [EMAIL PROTECTED] 2007-08-04 22:50 -------
Created an attachment (id=240)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=240&action=view)
TS 07.10 multiplexing (incomplete).
Here's a first cut at implementing the multiplexer. It is fairly incomplete but
the most necessary parts are in there. The communication through channels has
not been debugged yet but opening of new channels works.
If anyone will be implementing TS 07.10 they can perhaps start with this patch
(or not) at their option. (posting here because the mailing list blocked the
message due to size)
------- 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=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=129
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=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=344
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=347
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=352
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=412
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=422
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=470
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=471
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=511
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=571
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=605
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=639
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=643
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=644
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=661
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=686
Summary: USB descriptor incorrectly claims 5 interfaces
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: u-boot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
We have six altsettings (0 = ram, 1..5 = NAND partitions) in the DFU
configuration, but not five interfaces.
the bNumInterfaces value should therefore be 1, not 6.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
