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 #1867: Dhclient is not working
      (Openmoko Public Trac)
   2. Openmoko Bug #1993: Phone numbers instead of Names in qtmail
      (sms) (Openmoko Public Trac)
   3. Openmoko Bug #1994: Links in qthumbstyle are too great
      (Openmoko Public Trac)
   4. Re: Openmoko Bug #1983: eth0 doesn't exist / Oops during
      bootup (Openmoko Public Trac)
   5. Re: Openmoko Bug #1991: [Suspend] unable to suspend,      just
      stay black screen after wake up by power button from suspend
      (Openmoko Public Trac)
   6. Re: Openmoko Bug #1992: Suspend/Resume plays up when
      initiated manually (Openmoko Public Trac)
   7. Openmoko Bug #1995: Qtopia Quicker Finger Scrolling
      (Openmoko Public Trac)
   8. Re: Openmoko Bug #1966: The qtopia addressbook does not
      provide a search bar (Openmoko Public Trac)
--- Begin Message ---
#1867: Dhclient is not working
-------------------------------------+--------------------------------------
    Reporter:  Zoup                  |        Owner:  openmoko-kernel
        Type:  defect                |       Status:  new            
    Priority:  normal                |    Milestone:                 
   Component:  System Software       |      Version:  Om2008.8       
    Severity:  normal                |   Resolution:                 
    Keywords:  dhclient dhcp-client  |    Blockedby:                 
Reproducible:                        |     Blocking:                 
-------------------------------------+--------------------------------------

Comment(by maxious):

 A possible workaround is to use udhcpc which is part of busybox.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1867#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1993: Phone numbers instead of Names in qtmail (sms)
-----------------------+----------------------------------------------------
 Reporter:  BENtheTEN  |          Owner:  zecke                   
     Type:  defect     |         Status:  new                     
 Priority:  normal     |      Milestone:  Om2008.8                
Component:  Qtopia     |        Version:  Om2008.8                
 Severity:  normal     |       Keywords:  qtmail messages contacts
Blockedby:             |   Reproducible:  sometimes               
 Blocking:             |  
-----------------------+----------------------------------------------------
 Contact names are sometimes not resolved if I get a text message (sms).
 There's just the phone number as name, but if I check the contact the
 messages show up in the history. Seems strange to me.

 All my contacts' phone numbers have the country code for example: "+41 79
 xxx xx xx"

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1993>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1994: Links in qthumbstyle are too great
-------------------------+--------------------------------------------------
 Reporter:  Treviño      |          Owner:  zecke       
     Type:  enhancement  |         Status:  new         
 Priority:  normal       |      Milestone:              
Component:  Qtopia       |        Version:  Om2008.9-dev
 Severity:  blocker      |       Keywords:              
Blockedby:               |   Reproducible:  always      
 Blocking:               |  
-------------------------+--------------------------------------------------
 The font size of the links in qthumbstyle (i.e. the contact numbers and
 email in addressbook) have a size of 20pt that is too much for this
 device.

 This small patch (attached) reduces them at 8pt (greather than the rest,
 but really more readable).

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1994>
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 werner):

 Thanks for the logs ! It seems that the complaints only start after the
 SDIO stack has already decided that there is a WLAN device. I.e., after
 it has accessed the module.

 The command it was trying to issue is a read operation that normally
 follows a sequence of other read operations, and is roughly the 146th
 command sent to the device. So basic communication appears to work.

 The switch from a 1-bit bus to the 4-bit bus happens much earlier,
 around the 36th command. So it seems that this was uneventful.

 What does happen around that time is that the function is activated.
 (IOE1 is set in CCCR.) The failing access is still for the CCCR,
 though.

 So it appears that enabling the function upsets your WLAN module such
 that it either completely fails to communicate over SDIO, or that it
 sends information the SDIO stack is unhappy with (after which it tries
 to remove the device, causing the Oops).

 So this would make the operation that sometimes begins the string of
 timeouts the call to Cmd52ReadByteCommon following the call to
 Cmd52WriteByteCommon in the function SDEnableFunction in
 drivers/sdio/stack/busdriver/sdio_bus_misc.c

 The "silent" failure path (i.e., no timeout messages) is probably
 the error exit where SDEnableFunction sets status =
 SDIO_STATUS_FUNC_ENABLE_TIMEOUT. This theory could be confirmed by
 putting a printk there.

 If this is only a temporary confusion, e.g., a race condition inside
 the WLAN module, perhaps adding a delay(10) after Cmd52WriteByteCommon
 might help.

 Otherwise, this still looks like a defective WLAN module.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1983#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1991: [Suspend] unable to suspend, just stay black screen after wake up by 
power
button from suspend
---------------------------+------------------------------------------------
    Reporter:  regina_kim  |        Owner:  openmoko-devel
        Type:  defect      |       Status:  new           
    Priority:  high        |    Milestone:  Om2008.9      
   Component:  unknown     |      Version:                
    Severity:  critical    |   Resolution:                
    Keywords:              |    Blockedby:                
Reproducible:  sometimes   |     Blocking:                
---------------------------+------------------------------------------------

Comment(by wendy_hung):

 relate bug #1992, thanks for thepizzaking help us to get the log.

 Let me discrib this bug more...
 this bug means first time you set suspend time you'll have suspend time,
 but once you wake it up by power button, the second suspend time will fail
 (become blank time) you can click the screen to wake it up. So if this
 time you press the power button try to wake it up, actually is bring it to
 suspend time(use power button to suspend).
 After second suspend (blank time) it still will go into suspend (third
 suspend) than this time you'll have really suspend time....

 Hope this is clear enough. :)

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1991#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1992: Suspend/Resume plays up when initiated manually
-----------------------------+----------------------------------------------
    Reporter:  thepizzaking  |        Owner:  openmoko-devel
        Type:  defect        |       Status:  closed        
    Priority:  normal        |    Milestone:                
   Component:  unknown       |      Version:                
    Severity:  normal        |   Resolution:  duplicate     
    Keywords:                |    Blockedby:                
Reproducible:  always        |     Blocking:                
-----------------------------+----------------------------------------------
Changes (by wendy_hung):

  * status:  new => closed
  * resolution:  => duplicate


Comment:

 duplicate bug than #1991, thanks for your logread, lets comment more in
 #1991. :)

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1992#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1995: Qtopia Quicker Finger Scrolling
-------------------------+--------------------------------------------------
 Reporter:  Treviño      |          Owner:  zecke       
     Type:  enhancement  |         Status:  new         
 Priority:  normal       |      Milestone:              
Component:  Qtopia       |        Version:  Om2008.9-dev
 Severity:  normal       |       Keywords:  HasPatch    
Blockedby:               |   Reproducible:              
 Blocking:               |  
-------------------------+--------------------------------------------------
 Finger scrolling the qtopia pages is not so easy, that's why I've tried to
 improve it a little.
 The attached patch calculate on the speed of each mouse movement and uses
 this value to increase the scrolling speed.

 So, while before only the dragging-space was considered, now the speed of
 the dragging movement has a role in the scrolling.

 I've tried also to introduce a kind of auto scrolling if the dragging
 power was over some values, but I wasn't able to send automatically to the
 the QScrollBar scroll up/down events every few milliseconds.
 That's why I've added some stub code that actually is used to scroll to
 the begin/end of the list if is the finger scrolling has enough
 acceleration and is made in a quite great space (the values I've hardcoded
 are usable in my tests, give them a try if you want to find better
 values!).

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1995>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1966: The qtopia addressbook does not provide a search bar
-----------------------------------------+----------------------------------
    Reporter:  [EMAIL PROTECTED]  |        Owner:  zecke   
        Type:  enhancement               |       Status:  new     
    Priority:  normal                    |    Milestone:          
   Component:  Qtopia                    |      Version:  Om2008.8
    Severity:  blocker                   |   Resolution:          
    Keywords:  PM, HasPatch              |    Blockedby:          
Reproducible:                            |     Blocking:          
-----------------------------------------+----------------------------------

Comment(by Treviño):

 Emh, could you merge my patch too?

 Maybe you'd like not to make the keyboard pop-up in this case too?

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1966#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

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

Reply via email to