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 #1328: Sometimes X does not start
(Openmoko Public Trac)
2. Re: Openmoko Bug #1673: GTK Theme Font Size (Openmoko Public Trac)
3. Re: Openmoko Bug #1703: SYSFS: Bluetooth power_on entry
inversety inconsistent (Openmoko Public Trac)
4. Openmoko Bug #1709: [ASU] receiving or passing call doesn't
work (Openmoko Public Trac)
5. Openmoko Bug #1710: Tearing (Vertical Sync) (Openmoko Public Trac)
6. Openmoko Bug #1711: opkg upgrade of kernel on 31-07-2008
breaks usb0 (Openmoko Public Trac)
7. Openmoko Bug #1712: Phone will not boot if battery is fully
discharged, even if it is plugged in (Openmoko Public Trac)
8. Re: Openmoko Bug #1682: Neo turns off before reaching X
(Openmoko Public Trac)
9. Re: Openmoko Bug #1710: Tearing (Vertical Sync)
(Openmoko Public Trac)
--- Begin Message ---
#1328: Sometimes X does not start
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mickeyl
Type: defect | Status: closed
Priority: high | Milestone:
Component: Applications & Dependencies | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Blocking:
Blockedby: |
-----------------------------------------+----------------------------------
Changes (by mickeyl):
* status: new => closed
* resolution: => fixed
Comment:
fixed months ago.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1328#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1673: GTK Theme Font Size
-------------------------+--------------------------------------------------
Reporter: kriss | Owner: julian_chu
Type: enhancement | Status: closed
Priority: highest | Milestone: FSO
Component: Distro | Version:
Severity: normal | Resolution: fixed
Keywords: GTK | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by mickeyl):
* status: new => closed
* resolution: => fixed
Comment:
patches in, thanks.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1673#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1703: SYSFS: Bluetooth power_on entry inversety inconsistent
------------------------------+---------------------------------------------
Reporter: kriss | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: GTA02v6
Severity: normal | Resolution:
Keywords: Bluetooth, SYSFS | Blocking:
Blockedby: |
------------------------------+---------------------------------------------
Changes (by mickeyl):
* milestone: FSO =>
Comment:
Andy?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1703#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1709: [ASU] receiving or passing call doesn't work
----------------------+-----------------------------------------------------
Reporter: feydreva | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: ASU
Component: unknown | Version: unspecified
Severity: critical | Keywords:
Blocking: | Blockedby:
----------------------+-----------------------------------------------------
Hello,
I install the ASU of july 22nd.
Receiving call and passing call do work while connected by USB to a
computer.
Receiving call and passing call do NOT work if not connected.
Regards
Philippe
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1709>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1710: Tearing (Vertical Sync)
-----------------------------+----------------------------------------------
Reporter: Mercury | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: vsync vblank sync tearing
Blocking: | Blockedby:
-----------------------------+----------------------------------------------
I've noticed a lot of screen tearing, especially in the bootsplash (before
and after X starts). I think syncing to vblank should be implemented
wherever feasible.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1710>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1711: opkg upgrade of kernel on 31-07-2008 breaks usb0
----------------------+-----------------------------------------------------
Reporter: cfrazier | Owner: tick
Type: defect | Status: new
Priority: high | Milestone: OM-2007.2
Component: opkg | Version: GTA02v5
Severity: blocker | Keywords:
Blocking: | Blockedby:
----------------------+-----------------------------------------------------
Upon rebooting after a opkg update/upgrade in which the kernel was
updated, all connectivity via usb was lost. The FR failed to detect the
presence of a charging source and usb0 was down. Oddly, the usb icon was
shown while the cable was connected.
Reverting to the 28-07-2008 kernel removed this problem.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1711>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1712: Phone will not boot if battery is fully discharged, even if it is plugged
in
------------------------+---------------------------------------------------
Reporter: kenrestivo | Owner: tick
Type: defect | Status: new
Priority: normal | Milestone:
Component: Assassin | Version: GTA02v5
Severity: normal | Keywords:
Blocking: | Blockedby:
------------------------+---------------------------------------------------
The phone fails to boot-- or even to recharge-- when plugged in to the
wall power supply, if the battery is fully discharged. It is unacceptable
to have to remove the battery and place it into a separate phone from
another manufacturer, or into a separate battery recharger (not supplied),
in order to bring the phone back to an operational state.
The phone should have a power cube that delivers sufficient current to
operate the phone even if the battery is fully discharged.
Likewise, the power connector to the phone should be capable of delivering
that full load. If USB can't do that, then a separate power connector that
is not limited by USB current limitations should be provided and it should
mate with the power cube.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1712>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1682: Neo turns off before reaching X
-----------------------------+----------------------------------------------
Reporter: queen6 | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: ASU
Component: System Software | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by werner):
This may be the VB_SYS bypass capacitor: GTA02v5 has a very small
capacitor to
stabilize the system voltage. It's perfectly conceivable that a different
pattern of load changes could cause VB_SYS to break down before the USB
host
adjusts its output.
If you like to play with a soldering iron, you could try to modify a USB
cable
and put a big capacitor (I'd try about 100uF) between GND and VBUS. The
whole
setup won't be USB-compliant (USB 2.0 section 7.2.4.1, page 177, only
allows
10uF, and we already exceed that by a considerable margin), but you can
usually
get away with that.
You may also be able to get better results with a shorter or better
quality
USB cable, since it may reduce the voltage drop from host to device. Also
a
different host may perform better or worse.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1682#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1710: Tearing (Vertical Sync)
---------------------------------------+------------------------------------
Reporter: Mercury | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: System Software | Version:
Severity: normal | Resolution:
Keywords: vsync vblank sync tearing | Blocking:
Blockedby: |
---------------------------------------+------------------------------------
Comment(by andy):
Glamo doesn't have a VSYNC interrupt, I had to ask them directly because I
couldn't believe it.
What it does have is some double buffering flipping which is tied to
VSYNC, but I don't think it matches X AFAIK (but I know next to nothing
about X).
The other trick that's possible is it has a "line counter" register that
says which line it is issuing. One could use a timer to track this,
reading it in the timer ISR and the precomputing the time represented by
the remaining lines and setting the next interrupt for then, this would
give you a kind of vsync action.
If nobody implements those, you're stuck with tearing.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1710#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
