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 #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
2. Openmoko Bug #2218: [Om 2008.12] BlueZ d-bus system not
working (Openmoko Public Trac)
3. Re: Openmoko Bug #558: Most processes running as root?!
(Openmoko Public Trac)
4. Re: Openmoko Bug #1177: '-e command' and '-x command' support
for virtual terminal (Openmoko Public Trac)
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
I think this can be due to process spread of Glamo meaning that not every
device can handle the 89MHz memory clock that is used in 2.6.28.
I have seen this symptom when working wth Glamo registers but don't see it
on devices with kernels from the last few months. If you pretty reliably
can reproduce it, it will be something about your GTA02 I think.
The problem is actually communication to Glamo internal SDRAM is broken,
and as the MMC traffic travels through that it is also broken.
I'll add a kernel commandline option to push this back to 80MHz from 89MHz
(although the 89MHz was recommended by SMedia) so we can test and see if
makes any change for you.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2218: [Om 2008.12] BlueZ d-bus system not working
---------------------+------------------------------------------------------
Reporter: VDVsx | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone: Om2008.12
Component: Distro | Version:
Severity: blocker | Keywords: bluetooth bluez d-bus
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
The BlueZ d-bus system isn't working in the Om 2008.12 images, this is a
blocker for applications that use this services.
=== Test Om2008.12 ===
Turn Bluetooth on and in a terminal type:
dbus-send --system --print-reply --dest=org.bluez /org/bluez/service_input
org.bluez.Service.Stop
Output:
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was
not
provided by any .service files
=== Test Om2008.08/09 and FSO ML 4 ===
Turn Bluetooth on and in a terminal type:
dbus-send --system --print-reply --dest=org.bluez /org/bluez/service_input
org.bluez.Service.Stop
Output:
method return sender=:1.4 -> dest=:1.15 reply_serial=2
OR
Error org.bluez.Error.Failed: Operation not permitted (If the service is
already stopped)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2218>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#558: Most processes running as root?!
---------------------------------------------+------------------------------
Reporter: gregory.fow...@… | Owner: mickey
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Distro | Version: unspecified
Severity: normal | Resolution: invalid
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
---------------------------------------------+------------------------------
Changes (by mickey):
* status: new => closed
* haspatch: => 0
* resolution: => invalid
Comment:
I acknowledge it's a problem, but a proper fix will have to be deployed in
OpenEmbedded. Therefore I'm closing this as 'WONTFIX' here and hoping you
will open a bug upstream at bugs.openembedded.net. Please continue
pestering us (in OE) to fix this.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/558#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1177: '-e command' and '-x command' support for virtual terminal
-------------------------------------------------+--------------------------
Reporter: andrew.paul...@… | Owner: mickey
Type: enhancement | Status: assigned
Priority: high | Milestone:
Component: openmoko-terminal | Version: 2007.2
Severity: minor | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
-------------------------------------------------+--------------------------
Changes (by mickey):
* status: new => assigned
Comment:
still valid, but I have yet to find time to take care of that. Patches
appreciated.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1177#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
