#11845 HIGH -: Firmware q2f10: Hardware Test: USB: on second attempt after a device is removed, does not detect port in use correctly

[Zarro Boogs per Child]

#11845: Firmware q2f10: Hardware Test: USB: on second attempt after a device is
removed, does not detect port in use correctly
-------------------------------------------+--------------------------------
           Reporter:  earias               |       Owner:  Quozl               
               Type:  defect               |      Status:  reopened            
           Priority:  high                 |   Milestone:                      
          Component:  ofw - open firmware  |     Version:  Development firmware
         Resolution:                       |    Keywords:                      
        Next_action:  design               |    Verified:  0                   
Deployment_affected:                       |   Blockedby:                      
           Blocking:                       |  
-------------------------------------------+--------------------------------

Comment(by reuben):

 Replying to [comment:14 Quozl]:
 > Summary: I propose:
 >  * removing the fisheye pattern feature, as it is of no use to
 deployments or laptop owners, and has caused misinformation,

 Instead of removing:

 *Prompt user to insert USB before testing testing the port
 *If no USB is inserted in 5(?) seconds begin fisheye pattern and allow
 automated tests to continue
 *If User inserts USB launch actual port testing

 This has the benefit of not halting automated testing unless the user know
 they want to actually test port operation.

 >  * probing each port and reporting the type of device found.
 >
 > This will allow a deployment to begin testing USB ports, provided they
 have at least one USB device available in the repair location.  It will
 not require that devices be fed to it though.
 >
 > Background detail:
 >
 > As far as the USB host is concerned, the current test does test the
 host.
 >
 > As far as the USB ports are concerned, the current test does not test
 them.  The test has the following attributes:
 >
 >  * it does not check that a port is working,
 >  * it provides a test signal for an electrical check, as part of design
 verification,
 >  * it requires the use of an external instrument,
 >  * the result must be determined by observation of the instrument,
 >  * the firmware part of the test cannot determine, alone, whether the
 test is successful,
 >  * the firmware part of the test avoids a port if it is in use, so that
 the test signal is not sent to any device.
 >
 > It appears that this has led to your deployment using the test as
 evidence that a port is working.  We apologise for letting you think that.
 >
 > Still, that the test does not properly detect which ports are in use
 after the first attempt, may be leading to the test signal being sent
 unnecessarily to USB devices.  I plan to fix that too.

-- 
Ticket URL: <http://dev.laptop.org/ticket/11845#comment:15>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system