libraw1394 - Fork of libraw1394 that allows for externally managed buffers

	Commit message (Collapse)	Author	Age	Files	Lines
*	Make sure variables are initialized before used.	Erik Hovland	2008-10-28	1	-1/+2
\| \| \| \| \|	Signed-off-by: Erik Hovland <erik@hovland.org> Signed-off-by: Dan Dennedy <dan@dennedy.org>
*	Fix raw1394_read_cycle_timer after juju integration	Stefan Richter	2008-07-05	1	-0/+19
\| \| \| \| \| \| \| \|	The ieee1394 version of raw1394_read_cycle_timer() fell over the cliff in "First cut at integrating juju". This brings it back and adds a juju version of it. Also correct a typo in the inline documentation: s/get/read/
*	Plug dir leak and initialize data structs	Philippe Troin	2008-07-05	1	-0/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	While trying to track down some crashes in kino, I found the following problems with libraw1394: * There is a DIR* leak in raw1394_set_port(). * Lots of data structures are not fully initialized when calling IEEE1394 ioctl()s. These cause valgrind errors (benign, as valgrind does not know how to interpret all ioctls. However these also cause kino to crash in libraw1394. I've added a bunch of memset()s to prevent this problem from happening. Forward-ported to libraw1394 git tree by Jarod Wilson.
*	Move the source code files in the juju directory into the src directory and	Dan Dennedy	2008-04-30	1	-0/+529
	give them 'fw' names instead of 'juju.'