Werner Almesberger fd09655773 Requests following a rejected SETUP requests failed too, which sometimes ... produces user-visible errors and may confuse implementations. (E.g., when probing for an unimplemented feature and subsequently being greeted by a timeout.) - fw/comon/usb.c (handle_setup): set SOPRDY when answering a request error with a stall, according to the example in AN139. This seems to eliminate the timeouts observed in requests following after bad requests. - fw/boot/boot.c (run_payload): described how the host is expected to respond to the device resetting its USB stack		2010-08-24 19:12:22 -03:00
..
Makefile.common	version.h is no longer generated and it thus only creates confusion if	2010-08-20 14:26:35 -03:00
Makefile.system	Use config.h as the main source of configuration data. Fixed some boot.c	2010-08-19 01:01:08 -03:00
regs-f32x.h	Added timer register values.	2010-08-23 18:11:51 -03:00
regs-f320.h	Added timer register values.	2010-08-23 18:11:51 -03:00
regs-f326.h	Registers and register values are now CPU-specific.	2010-08-23 14:26:01 -03:00
uart.c	fw/common/ - copied from IDBG and generalized a little	2010-08-13 08:47:13 -03:00
uart.h	fw/common/ - copied from IDBG and generalized a little	2010-08-13 08:47:13 -03:00
usb-regs.h	fw/common/ - copied from IDBG and generalized a little	2010-08-13 08:47:13 -03:00
usb.c	Requests following a rejected SETUP requests failed too, which sometimes	2010-08-24 19:12:22 -03:00
usb.h	fw/common/ - copied from IDBG and generalized a little	2010-08-13 08:47:13 -03:00
version.h	Use config.h as the main source of configuration data. Fixed some boot.c	2010-08-19 01:01:08 -03:00