[Trac #340] Marvell Wireless Upgrades: Hubs on other USB ports cause failures!

[Zarro Boogs per Child]

#340: Marvell Wireless Upgrades: Hubs on other USB ports cause failures!
---------------------+------------------------------------------------------
 Reporter:  mfoster  |       Owner:  mbletsas
     Type:  defect   |      Status:  new     
 Priority:  blocker  |   Milestone:  BTest-1 
Component:  distro   |    Keywords:          
---------------------+------------------------------------------------------
 Hi, Folks,

 After many hours at the USB protocol analyzer, we can see some device
 combinations that routinely induce Boot2 upgrade or downgrade failures on
 the Marvell wireless module.  All of these tests were performed booting
 from NAND.

 Specifically, if a USB2 hub is present on one of the system's USB ports,
 with a USB1 device attached to it, the wireless upgrade will fail with
 nearly 100% certainty.  It appears that the presence of the Split
 transactions which occur in this configuration confuse the Marvell module.

 USB Protocol data for this failure is at:

 http://www.talix.com/Wireless_Upgrade_Failure_Hub-Keyboard.ufo

 If a USB2 hub is present on one of the system's USB ports with a USB2
 device attached to it, there is a very high probability that the wireless
 upgrade will fail.

 http://www.talix.com/Wireless_Upgrade_Failure_Hub-Disk.ufo


 If a USB2 hub is present on one of the system's USB ports with no USB
 devices attached, the wireless upgrade will succeed.

 http://www.talix.com/Wireless_Upgrade_Success_Hub-Only.ufo


 Note that it is the character of the USB traffic which appears to
 determine success of firmware upgrades.  IMPORTANT NOTE is that we believe
 that the failures seen during programming attempts correlate well with
 failures loading the runtime RAM-based code in the normal driver.

-- 
Ticket URL: <http://dev.laptop.org/ticket/340>
One Laptop Per Child <http://laptop.org/>