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 #2064: [OE] Fails to build machine="x86" on
"89qtopia" is missing (Openmoko Public Trac)
2. Re: Openmoko Bug #2065: [OE] Fails to build machine="x86":
"DEVICE" no such file or directory. (Openmoko Public Trac)
3. Re: Openmoko Bug #2057: 1bit errors in files
(Openmoko Public Trac)
4. Re: Openmoko Bug #2057: 1bit errors in files
(Openmoko Public Trac)
5. Re: Openmoko Bug #2062: xglamo doesn't implement any power
management (Openmoko Public Trac)
6. Openmoko Bug #2066: Voip-Handset.state file does Speakerout
(Openmoko Public Trac)
7. Re: Openmoko Bug #2062: xglamo doesn't implement any power
management (Openmoko Public Trac)
8. Re: Openmoko Bug #1267: Strong echo when calling a Neo from
another phone (Openmoko Public Trac)
--- Begin Message ---
#2064: [OE] Fails to build machine="x86" on "89qtopia" is missing
-------------------------------+--------------------------------------------
Reporter: kempelen | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: host utilities | Version:
Severity: normal | Resolution: fixed
Keywords: | Blockedby:
Reproducible: | Blocking:
-------------------------------+--------------------------------------------
Changes (by zecke):
* status: new => closed
* resolution: => fixed
Comment:
I have added a crippled 89qtopia file, it does not make any sense though.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2064#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2065: [OE] Fails to build machine="x86": "DEVICE" no such file or directory.
-------------------------------+--------------------------------------------
Reporter: kempelen | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: host utilities | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
-------------------------------+--------------------------------------------
Comment(by zecke):
this is no bug, patches are welcome though. Change the recipe to use
default by default, test it, send a patch. org.openmoko.asu.stable and
even org.openmoko.dev is only tested with om-gta01 and om-gta02 as
machines.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2065#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2057: 1bit errors in files
---------------------------------------------+------------------------------
Reporter: Richard.Kralovic | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: file corruption, 1bit errors | Blockedby:
Reproducible: rarely | Blocking:
---------------------------------------------+------------------------------
Comment(by Vladimir.Koutny):
I have a unit from the same (pulster.de) delivery as Richard and I don't
see any memory issues (yet). However, I also can't run mtest in the full
range - the range that doesn't cause crash/han
g is:
30000040 - 33e80000
34008000 - 38000000
(btw. first 0x40 bytes contains vector table - I guess you don't want to
mtest that area :) )
That might be influenced by uboot version - in my case it is 1.3.2-rc2
-dirty-moko12 (NAND) and 1.3.2-moko12 (NOR) (both as shipped), not sure
where uboot code/data are mapped.
Btw., when looking at Freerunner memory map at
http://wiki.openmoko.org/wiki/Neo_FreeRunner_Memory_Mapping, I would guess
that external ram chip would be mapped starting at 38000000...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2057#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2057: 1bit errors in files
---------------------------------------------+------------------------------
Reporter: Richard.Kralovic | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: file corruption, 1bit errors | Blockedby:
Reproducible: rarely | Blocking:
---------------------------------------------+------------------------------
Comment(by werner):
The external RAM is at 0x34..., using the variable bank 6/7 size feature.
See table 5-1 of the 2442 manual. Ignore the left-hand side of figure
5-1 :-)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2057#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2062: xglamo doesn't implement any power management
--------------------------------+-------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: blocker | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
--------------------------------+-------------------------------------------
Comment(by laforge):
I have now implemented at least disabling of the pixel clock. With some
luck, this will already provide significant savings. Unfortunatly we
cannot switch off the memory clock and put it in self-refresh as long as
the sd/mmc driver might still need it. Since most users will have a card
present (and mounted) at all time, it's probably not worth optimizing for
that case.
I've sent the patches to openmoko-kernel but they're not yet in the
archives...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2062#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2066: Voip-Handset.state file does Speakerout
-----------------------------+----------------------------------------------
Reporter: Treviño | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: Om2008.9
Component: System Software | Version: Om2008.9-dev
Severity: blocker | Keywords: HasPatch
Blockedby: | Reproducible: always
Blocking: |
-----------------------------+----------------------------------------------
The default alsa voip-handset.state file isn't really a state file that
could be used for handset calling, since it doesn't use the phone's
earpiece to output the audio, but the main speaker.
Here's a little patch to fix this, setting the earpiece as output device
(I've improved also the volumes).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2066>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2062: xglamo doesn't implement any power management
--------------------------------+-------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: blocker | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
--------------------------------+-------------------------------------------
Comment(by laforge):
I have now implemented at least disabling of the pixel clock. With some
luck, this will already provide significant savings. Unfortunatly we
cannot switch off the memory clock and put it in self-refresh as long as
the sd/mmc driver might still need it. Since most users will have a card
present (and mounted) at all time, it's probably not worth optimizing for
that case.
I've sent the patches to openmoko-kernel but they're not yet in the
archives...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2062#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1267: Strong echo when calling a Neo from another phone
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: sean_chiang
Type: defect | Status: assigned
Priority: high | Milestone:
Component: Audio | Version: unspecified
Severity: normal | Resolution:
Keywords: audio, echo | Blockedby:
Reproducible: | Blocking:
----------------------------------+-----------------------------------------
Comment(by michael):
Daniel Nöthen reports, and Angus Ainslie confirms, a pattern which might
help
debug this issue. Full email at:
http://lists.openmoko.org/pipermail/community/2008-October/032655.html
Excerpt:
1. Boot the freerunner
2. Make a call -> no echo
3. Hang up
4. Make a call -> echo
5. Hang up
6. /etc/init.d/xserver-nodm restart
7. Make a call -> no echo
8. Hang up
9. Make a call -> echo
.
.
.
With the above state file I was able to bring up the "Speaker" volume up
to
100%
without hearing any echo on step 2 and 7.
The volumes on both sides were very good.
On step 4 and 9 I could only bring up the "Speaker" volume to 79%.
Above 79% the echo came back.
So it seems that the echo suppression command (AT%N0187) gets reset after
every call.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1267#comment:17>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
