Stacey Sheldon dab400c80d usb: decouple "available" from "cable connected" ... The bootloader needs to understand whether the USB cable is connected. The HID and CDC drivers need to know if the cable is connected _and_ the device has been enumerated already. Separate these two concepts in the API. Combining these was resulting in the BL not properly detecting that the cable was plugged in, and trying to boot the firmware image immediately. This effectively bricked the board if you ever had an invalid firmware image. It also happens to be the case that the BU images automatically invalidate themselves after updating the BL so they don't run again. The cable detect bug + this intended behaviour of the BU image resulted in a bricked board after upgrading the BL.		2012-05-22 00:21:24 -04:00
..
Boards	Merge commit 'c4df0c0ceff8ba985bb20d815f27910b9e59d992' into revolution	2012-03-11 13:14:06 -05:00
Common	usb util: Add common utility functions for USB descriptors	2012-05-19 16:14:10 -04:00
inc	usb: decouple "available" from "cable connected"	2012-05-22 00:21:24 -04:00
STM32F4xx	Make revolution work with the FreeRTOS queue based MPU6000 driver	2012-04-03 03:41:52 -05:00
STM32F10x	usb: decouple "available" from "cable connected"	2012-05-22 00:21:24 -04:00
pios.h	Merge branch 'stac/revo-usb' into revolution	2012-03-02 13:00:13 -06:00