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 #1322: Background noise during conversation
(Openmoko Public Trac)
2. Re: Openmoko Bug #1884: [suspend/resume] if press power
batton right after suspend, the device won't wake up
(Openmoko Public Trac)
3. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
4. Re: Openmoko Bug #1892: Locations doesn't start
(Openmoko Public Trac)
5. Re: Openmoko Bug #1884: [suspend/resume] if press power
batton right after suspend, the device won't wake up
(Openmoko Public Trac)
6. Re: Openmoko Bug #1892: Locations doesn't start
(Openmoko Public Trac)
7. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
8. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
9. Re: Openmoko Bug #1903: zhone_git.bb do_compile failed
(Openmoko Public Trac)
--- Begin Message ---
#1322: Background noise during conversation
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: erin_yueh
Type: defect | Status: assigned
Priority: highest | Milestone:
Component: openmoko-dialer | Version: current svn head
Severity: major | Resolution:
Keywords: | Blockedby:
Blocking: |
------------------------------------+---------------------------------------
Comment(by hiciu):
What about this:
http://lists.openmoko.org/pipermail/community/2008-August/028495.html ?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1322#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1884: [suspend/resume] if press power batton right after suspend, the device
won't wake up
--------------------------------+-------------------------------------------
Reporter: wendy_hung | Owner: andy
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: System Software | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
--------------------------------+-------------------------------------------
Comment(by Treviño):
Another try. I've turned on a led and then launched apm -s. Well... The
led didn't turn off for about 40 seconds (maybe more).
This should mean that the phone didn't go to sleep until then (isn't it?).
However pushing the power button and waiting minutes doesn't help :(
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1884#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1904: om2008.8 wifi don't get always an ipv4 ip
------------------------+---------------------------------------------------
Reporter: dolfje | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by andy):
Just about the alignment traps, these should be informational only. The
alignment error creates a hardware exception which is handled by kernel,
but it is slow. (Actually that code in kernel is really funny, it goes
and looks at the address it would return to and disassembles the
instruction that created the exception, then uses stacked registers to
recreate that instruction's function like a processor emulator :-O) So in
order to allow improving code in the application to remove alignment
issue, it prints the notification.
That's the theory anyway, but most people are using usb0 with static
address, it can be real general issue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1892: Locations doesn't start
--------------------------+-------------------------------------------------
Reporter: flamma | Owner: jeremy
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: Locations | Version: Om2008.9-dev
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
--------------------------+-------------------------------------------------
Changes (by marek):
* owner: marek => jeremy
* status: accepted => assigned
Comment:
Ok, I reassign to jeremy because he knows that application better than me.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1892#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1884: [suspend/resume] if press power batton right after suspend, the device
won't wake up
--------------------------------+-------------------------------------------
Reporter: wendy_hung | Owner: andy
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: System Software | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
--------------------------------+-------------------------------------------
Comment(by Treviño):
Another try. I've turned on a led and then launched apm -s. Well... The
led didn't turn off for about 40 seconds (maybe more).
This should mean that the phone didn't go to sleep until then (isn't it?).
However pushing the power button and waiting minutes doesn't help :(
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1884#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1892: Locations doesn't start
--------------------------+-------------------------------------------------
Reporter: flamma | Owner: jeremy
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: Locations | Version: Om2008.9-dev
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
--------------------------+-------------------------------------------------
Changes (by marek):
* owner: marek => jeremy
* status: accepted => assigned
Comment:
Ok, I reassign to jeremy because he knows that application better than me.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1892#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1904: om2008.8 wifi don't get always an ipv4 ip
------------------------+---------------------------------------------------
Reporter: dolfje | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by andy):
Just about the alignment traps, these should be informational only. The
alignment error creates a hardware exception which is handled by kernel,
but it is slow. (Actually that code in kernel is really funny, it goes
and looks at the address it would return to and disassembles the
instruction that created the exception, then uses stacked registers to
recreate that instruction's function like a processor emulator :-O) So in
order to allow improving code in the application to remove alignment
issue, it prints the notification.
That's the theory anyway, but most people are using usb0 with static
address, it can be real general issue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1904: om2008.8 wifi don't get always an ipv4 ip
------------------------+---------------------------------------------------
Reporter: dolfje | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by dolfje):
And for the completeness:
u-boot: 1.3.2-moko12
(http://downloads.openmoko.org/releases/Om2008.8-update/gta02v5_and_up-u-boot.bin)
kernel:
http://downloads.openmoko.org/releases/Om2008.8-update/Om2008.8-gta02-20080826.uImage.bin
rootfs:
http://downloads.openmoko.org/releases/Om2008.8-update/Om2008.8-gta02-20080830.rootfs.jffs2
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1903: zhone_git.bb do_compile failed
--------------------------+-------------------------------------------------
Reporter: javiroman | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: Distro | Version: FSO-MS2
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
--------------------------+-------------------------------------------------
Comment(by javiroman):
More imformation:
The MokoMakefile settings are:
OM_GIT_SITE := git.openembedded.net
OM_GIT_REPO := org.openembedded.dev
OM_GIT_BRANCH := org.openembedded.dev
I guess that are the correct settings for FSO image.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1903#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
