[PATCH] fxload fix

[Frank Mori Hess <fmhess@users.sourceforge.net>]

[-- Attachment #1: Type: text/plain, Size: 411 bytes --]

--Boundary-00=_b+ybBv0OXckQSSY
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

I've got a one-line patch attached for fxload.  Without it, it chokes on 
Intel hex image files, unless you add a garbage character to the end of 
every line.  I suppose using DOS instead of UNIX end of line characters in 
the firmware file would also avoid the bug.

[-- Attachment #2: Type: text/plain, Size: 293 bytes --]

Hi,

Is fxload unmaintained?  There haven't been any commits in 2 years, and I'm 
noticing a bug report from 3 months ago here

http://sourceforge.net/tracker/index.php?func=detail&aid=994005&group_id=17679&atid=117679

that fixes the same problem I reported last week (patch attached again).

[-- Attachment #3: ezusb_diff --]
[-- Type: text/x-diff, Size: 290 bytes --]

--- ezusb.c	2004-10-14 21:39:41.000000000 -0400
+++ ezusb-fixed.c	2004-10-14 21:40:27.000000000 -0400
@@ -361,7 +361,7 @@
 	    return -3;
 	}
 
-	if ((len * 2) + 11 >= strlen(buf)) {
+	if ((len * 2) + 11 > strlen(buf)) {
 	    fprintf (stderr, "record too short?\n");
 	    return -4;
 	}