libsigrokdecode.git - libsigrokdecode

Age	Commit message (Collapse)	Author
2013-10-11	usb_signalling: Document protocol output format.	Uwe Hermann
	Also, add missing output for some packet types.
2013-09-29	usb_signalling: Fix packet annotation.	Uwe Hermann

2013-09-29	usb_signalling: Fix EOP handling and annotation.	Uwe Hermann

2013-09-29	usb_signalling: Properly use different annotation types.	Uwe Hermann

2013-09-29	usb_signalling: Fix decode of individual bits.	Uwe Hermann
	After a Start of Packet (SOP) has been detected, "sample" the individual USB symbolѕ/bits in the middle of the respective bittime (depending on whether full-speed or low-speed signalling is used). This fixes various incorrectly decoded cases (bug #158).
2013-09-20	usb_signalling: Simplify symbols handling a bit.	Uwe Hermann

2013-09-20	usb_signalling: Refactor/simplify bitrate/bitwidth handling.	Uwe Hermann

2013-09-15	usb_signalling: Fix start/end sample numbers.	Uwe Hermann
	This makes the decoder suitable for GUI usage. This fixes bug #155.
2013-04-23	GPL headers: Use correct project name.	Uwe Hermann

2013-01-01	Small cosmetic/consistency fixes in the PDs.	Uwe Hermann

2012-11-24	All PDs: Name the files pd.py consistently.	Uwe Hermann
	The Python module name is determined by the directory name (e.g. dcf77), the *.py file names in that directory don't matter and can be kept consistent.
2012-07-11	srd: Performance improvements for various PDs.	Uwe Hermann
	Ignore/skip identical samples in most (low-level) PDs, as we're usually (but not necessarily always) only interested in pin changes. This yields a significant performance improvement for the PDs. The mechanism was already used in the 'i2s', 'jtag', and 'lpc' PDs, but not yet in all supported low-level decoders. The following PDs now also use this mechanism: 'dcf77', 'i2c', 'spi', 'uart', and 'usb_signalling'. Thanks Lars-Peter Clausen <lars@metafoo.de> for bringing this to our attention.
2012-06-21	srd: Split USB decoder in two PDs (which stack).	Uwe Hermann
	The 'usb_signalling' decoder just decodes symbols from D+/D- levels, handles bit stuffing and outputs the symbols and (potential) packets. The 'usb_protocol' decoder takes that output and tried to parse USB packets from it (SOF, SETUP, IN, OUT, DATA0, and so on). This is the base decoder on top of which various others will stack later on. The two new PDs are work in progress, so we still keep the old 'usb' PD around for a little while, until the two new ones are fully working and well-tested.