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 #2019: Headphone Jack Event
(Openmoko Public Trac)
2. Re: Openmoko Bug #1983: eth0 doesn't exist / Oops during
bootup (Openmoko Public Trac)
3. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
4. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
5. Re: Openmoko Bug #2020: USB connection messes with
suspend/resume state machine (Openmoko Public Trac)
6. Re: Openmoko Bug #676: dfu-util upload causes data corruption
(Openmoko Public Trac)
7. Re: Openmoko Bug #1158: Charging stops even while connected
(Openmoko Public Trac)
8. Re: Openmoko Bug #1158: Charging stops even while connected
(Openmoko Public Trac)
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by werner):
I installed Om2008.9-gta02-20080916 on a GTA02v6 and I can definitely see
something happening when I plug in or remove a plug (tried all items shown
on http://people.openmoko.org/werner/headset-suppressor.jpg )
while running cat /dev/input/event0
Did the headset event ever work on that device ?
By the way, u-boot I have on that device is version
U-Boot 1.3.2-dirty-moko12 (Aug 20 2008 - 18:41:45)
Since u-boot sets up the GPIOs, a change in u-boot may affect this.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1983: eth0 doesn't exist / Oops during bootup
----------------------------+-----------------------------------------------
Reporter: Weiss | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: wifi kernel | Blockedby:
Reproducible: always | Blocking:
----------------------------+-----------------------------------------------
Comment(by Weiss):
Ok - here's the dmesg log with the SDIO bus driver messages enabled. I
can see the initial messages working properly, the switch to four-bit I/O,
some power settings etc. The errors start, as you suggested, when the
function is enabled. There are some response and error codes in the log,
but I don't know what they mean.
I also added a debug message just before the
SDIO_STATUS_FUNC_ENABLE_TIMEOUT exit, and it looks like this happens
multiple times before the timeout messages appear.
I tried adding a udelay(10) just after the Cmd52WriteByteCommon in
SDEnableFunction (after creating the current log), but this didn't appear
to make any difference.
So, unless it'd be useful to probe any deeper (which I'd be very willing
to do - I'm enjoying learning about how to poke around in the kernel),
I'll initiate the warranty repair/replacement procedure with my reseller
and this ticket can be closed. Thanks for all the help and advice.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1983#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by Zoup):
My uboot version is exactly as yours without '-dirty-' , err ... is this
something good that its clean ? :)
yeas , headset is OK , its the official one that i get from openmoko , and
it does play music perfectly when i switch alsa states .
ill try http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin and
let you know the result
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by Zoup):
I have tried Latest Daily uboot image and om2008 first release ( its was
24 aug , i have tried that since it was near your uboot date ) , still no
output again .
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2020: USB connection messes with suspend/resume state machine
------------------------+---------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by vnevoa):
Yes, it does look like a duplicate.
However, I thought my case was different because it seems linked to USB
connection, which I think was deliberately taken into consideration by the
developers in the suspend/resume system?...
If what I say does not make sense, then go ahead and mark it as duplicate.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2020#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#676: dfu-util upload causes data corruption
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: host utilities | Version:
Severity: normal | Resolution:
Keywords: dfu | Blockedby:
Reproducible: | Blocking:
-------------------------------------+--------------------------------------
Comment(by xbaldauf):
Same error "-84" for me, same filesize:
dfu-util - (C) 2007 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY
Opening USB Device 0x1d50:0x5119...
Found Runtime: [0x1d50:0x5119] devnum=8, cfg=0, intf=0, alt=6,
name="rootfs"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuERROR, status = 14
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
dfu_upload error -84
-rwxr--r-- 1 root root 258076672 2008-09-20 16:54 rootfs
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/676#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1158: Charging stops even while connected
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: Om2008.10
Component: System Software | Version: unspecified
Severity: critical | Resolution:
Keywords: power management | Blockedby:
Reproducible: sometimes | Blocking:
---------------------------------+------------------------------------------
Comment(by werner):
By the way, how the PMU is set up, it will automatically stop charging
when
the battery has reached 4.2V (MBCC2.vmax) and resume when it has dropped
to
4.032V (MBCC2.vmax*96%, see description of MBCC1.autores).
So as long as the voltage does not leave these boundaries, that's just
normal behaviour of our charging hardware. The battery pack is specified
for a charge voltage of 4.2V+/-0.05V, so the MBCC2.vmax setting of
4.2V+/-1%
is as high as possible without violating the battery specification.
If this is just a GUI problem, a solution might be to read MBCS2.mbcmod
and
to display something less disturbing than a discharging battery when in
state "Battery Full mode", 10 decimal.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:23>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1158: Charging stops even while connected
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: Om2008.10
Component: System Software | Version: unspecified
Severity: critical | Resolution:
Keywords: power management | Blockedby:
Reproducible: sometimes | Blocking:
---------------------------------+------------------------------------------
Comment(by Abraxa):
Replying to [comment:23 werner]:
> By the way, how the PMU is set up, it will automatically stop charging
[...] and resume
The problem here however is that the PMU stops charging even when the
battery is not full and does not resume charging at any point either.
> If this is just a GUI problem, a solution might be to read MBCS2.mbcmod
and
> to display something less disturbing than a discharging battery when in
> state "Battery Full mode", 10 decimal.
I'm afraid this has nothing to do with this bug as the charging stops due
to a perceived loss of charger power by the kernel, seemingly regardless
of battery level.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:24>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
