librambutan - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	Move CDC ACM config. descriptor into usb_cdcacm.c.	Marti Bolivar	2012-07-31	1	-2/+15
\| \| \| \|	Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
*	Move bootloader reset signal detection to Wirish.	Marti Bolivar	2012-07-31	1	-126/+24
\| \| \| \| \| \| \| \|	Use usb_cdcacm hooks to move the DTR edge and "1EAF" magic packet detection to usb_serial.cpp. We'll later be able to extend this system to support Leonardo-style reset signalling. Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
*	usb_cdcacm: Add usb_cdcacm_peek().	Marti Bolivar	2012-07-31	1	-27/+38
\| \| \| \| \| \| \| \| \| \| \|	We need this so the bootloader reset signal detector can look ahead in the byte stream without stealing bytes from the user when "1EAF" isn't received. While we're doing this, take the time to fix a bunch of RX-related code (dead code removal, adding volatile, etc.) Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
*	usb_cdacm: Use config instead of magic numbers.	Marti Bolivar	2012-07-31	1	-2/+2
\| \| \| \| \| \|	Sigh. Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
*	usb_cdcacm: Add hook system.	Marti Bolivar	2012-07-31	1	-0/+31
\| \| \| \| \| \| \| \|	Provide hooks so users can reach into the CDC ACM callbacks with their own code. We'll use this to move the bootloader reset signals to Wirish. Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
*	usb_cdcacm: Expose some internal configuration and values.	Marti Bolivar	2012-07-31	1	-84/+51
\| \| \| \| \| \| \| \| \|	Mark the API as unstable so people don't rely on these too hard. (This header is not part of the official libmaple docs). We'll need some of this configuration elsewhere later, and it doesn't make much sense to expose it piecemeal. Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
*	usb_cdcacm.c: Add another verification TODO.	Marti Bolivar	2012-07-31	1	-0/+2
\| \| \| \| \| \| \|	Not sure what the comment above the new TODO is supposed to mean, but it looks like something that should be checked. Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
*	usb_cdcacm.c: Resolve TODO and improve comments.	Marti Bolivar	2012-07-31	1	-5/+7
\| \| \| \| \| \| \| \| \|	The disc pin code was copy-pasted when the CDC ACM pieces were extracted from the rest of the USB code, and I didn't really understand what was going on when I moved it over. Having checked the spec, the comments can be safely improved. Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
*	Doxygen hacks and fixups.	Marti Bolivar	2012-06-28	1	-1/+1
\| \| \| \| \| \| \| \|	- Shut Doxygen up in various places - Fix some genuine docs bugs - Ignore sources we're not responsible for Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
*	Slightly improve and generify the USB infrastructure.	Marti Bolivar	2012-06-03	1	-0/+762
	The good news is that <libmaple/usb.h> and <libmaple/usb_cdcacm.h> did turn out generic enough in what they specify to go on unchanged. However, we can't just go on assuming that there's USB just because we're on an F1. Now that there's value line in the tree, we need to be more careful (value line F1s don't have USB peripherals). To that end, make all the F1 board-includes/*.mk files specify what line their MCU is with an MCU_F1_LINE variable. Use that to hack libmaple/usb/rules.mk so we only try to build the USB module under appropriate circumstances. While we're at it, add a vector_symbols.inc for value line MCUs under support/ld/. We need this to get the target-config.mk modifications implied by the addition of MCU_F1_LINE. We'll fix up some other performance-line-isms under libmaple/stm32f1 in a separate commit. Also in libmaple/usb/: - Move everything into a new stm32f1 directory. Due to aforementioned rules.mk hacks, there is no immediate need for an stm32f2 directory (USB support doesn't exist there). - Update the README for style and content. Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>