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. [Bug 560] Removing battery from Neo makes nasty noise
      ([EMAIL PROTECTED])
   2. [Bug 1046] Bridges game allows number to connect to itself.
      ([EMAIL PROTECTED])
   3. [Bug 810] constant white screen and vibrator on
      ([EMAIL PROTECTED])
   4. [Bug 812] "neo1973 gsm version" command does not respond
      ([EMAIL PROTECTED])
   5. [Bug 1083] pulseaudio 0.9.8 can't load module-alsa-sink
      ([EMAIL PROTECTED])
   6. [Bug 872] Implement GPS and BT power in neod power button
      menu ([EMAIL PROTECTED])
   7. [Bug 1086] New: White pixel "noise" corrupts display
      dynamically       after some boots ([EMAIL PROTECTED])
   8. [Bug 1086] White pixel "noise" corrupts display dynamically
      after     some boots ([EMAIL PROTECTED])
   9. [Bug 1087] New: Screen refresh rate vs power
      ([EMAIL PROTECTED])
  10. [Bug 1088] New: Move production test code out of U-Boot into
      kernel    module ([EMAIL PROTECTED])
  11. [Bug 1088] Move production test code out of U-Boot into
      kernel    module ([EMAIL PROTECTED])
  12. [Bug 1089] New: More components needed
      ([EMAIL PROTECTED])
  13. [Bug 1089] More components needed
      ([EMAIL PROTECTED])
  14. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
  15. [Bug 956] GTA02 charging with 1000mA using wall-outlet
      charger ([EMAIL PROTECTED])
  16. [Bug 956] GTA02 charging with 1000mA using wall-outlet
      charger ([EMAIL PROTECTED])
  17. [Bug 1089] More components needed
      ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=560





------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 01:03 -------
Is this still reproducible with GTA-02 hardware?



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1046

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 01:05 -------
Dug around in the source, and it seems this isn't a bug but some features called
'mark' (which seems broken, another bug for another time).  Don't know for
certain why I could not unselect them before figuring this out, but I suspect it
was just qemu not playing nicely with the emulated touchscreen.  I  can unselect
them now, after a few tries.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=810





------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 01:05 -------
Why did we open this again Willie?  Did we try to reproduce, or did we ever 
see crashes on USB insertion ourselves?  If so are the problems still seen on 
GTA-02?

Can it be related to #560?



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=812





------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 01:08 -------
What did you find out Jim from the old firmware test?



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1083

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 01:08 -------
Heisenbug... don't mix module-alsa-sink from 0.9.6 with pulseaudio 0.9.8 :D



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=872





------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 01:12 -------
This does not seem to need any action from the kernel side, is there a better 
person to assign it to than Willie?



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1086

           Summary: White pixel "noise" corrupts display dynamically after
                    some boots
           Product: Neo1973 Hardware
           Version: GTA02v2
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Screen
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


Willie explained that occasionally during boot when the display is 
initialized, it suffers from white "noise" pixels that obscures the actual 
display data and moves around randomly per frame.

This symptom sounds like memory bus bandwidth being used up and the video data 
is not able to keep the display pixel pipeline full all the time.  If he 
manages to get a boot that exhibits this behaviour, it seems to persist for 
the whole boot.

He reports seeing it something like once a day, but of course he reboots a 
lot.

If it is due to starvation of the video pipeline then it's interesting that it 
only happens sometimes.  Maybe init of SDRAM timings or video chip timings is 
not 100% reliable.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1086

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|[EMAIL PROTECTED]    |[EMAIL PROTECTED]



------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 01:35 -------
Reassigned to willie, it's not a physical screen issue



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1087

           Summary: Screen refresh rate vs power
           Product: Neo1973 Hardware
           Version: GTA02v2
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Screen
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


It seems from the console output I noticed in Bugzilla that we currently run 
the video at a 60Hz frame rate.

Will the panel allow to reduce this to 30Hz?  Not only will this help with 
power consumption but it will reduce the reservation of the memory bus for 
video data.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1088

           Summary: Move production test code out of U-Boot into kernel
                    module
           Product: Neo1973 Hardware
           Version: GTA02v2
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core System
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


Supporting the PBE kernel and the U-Boot codebase is less good than supporting 
one environment for all the purposes, the shipping kernel.

Migrate any testing stuff that is in PBE or U-Boot world instead into modules 
for the current shipping kernel, and generally favour adding test stuff into 
the kernel rather than U-Boot so there is less to maintain outside of the one 
kernel.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1088

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|[EMAIL PROTECTED]    |[EMAIL PROTECTED]





------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1089

           Summary: More components needed
           Product: Site Infrastructure
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Bugzilla
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


There needs to be components for

WLAN
kernel

added to the public BZ



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1089





------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 02:17 -------
Sorry, looking under Neo and not OpenMoko for "kernel", but WLAN really is 
needed as a component for Neo



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.

All of these bugs are in the NEW state, and have not been touched
in 7 days or more.  You need to take a look at them, and 
decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
    else.  (Hint: if you don't know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):

    
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL 
PROTECTED]

Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.

Appended below are the individual URLs to get to all of your NEW bugs that 
haven't been touched for a week or more.

You will get this message once a day until you've dealt with these bugs!

  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=934
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=935



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=956





------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 05:09 -------
Now it can be divided three cases here
* USB Device Mode : R > 100k
   - charging with 100mA
* USB Host Mode: R < 10
   - no charging
* Charger Mode: R = 48k  1%
   - charging with 1000mA





------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=956





------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 06:24 -------
Please show me the code.  Where and how are those cases differentiated? when was
the patch sent to the openmoko-kernel list?  Or is it attached to bugzilla?



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1089





------- Additional Comments From [EMAIL PROTECTED]  2007-12-05 07:01 -------
I would remove the Component field, together with Platform, OS, Version, 
Priority, Severity, Target 
Milestone.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to