On Saturday, July 31, 2010 12:08:48 Michael Walle wrote: > the cable pid/vid number parsing changed on the development version. urjtag > 0.10 parsed the numbers as hex string, whereas in latest development > version the numbers are interpreted as decimal ones. Is this intended? In > the former versions you could use the output from lsusb.
yes and no. the unification of parameter parsing is what caused this. while
i can easily restore support for hex values starting with 0x, adding support
for unprefixed hex values (what lsusb shows) is a bit tougher. i'm also not
sure i want to. imo, if you want to use a hex value, it should have a 0x at
the start to avoid ambiguity.
--- src/global/params.c (revision 4746)
+++ src/global/params.c (working copy)
@@ -180,7 +180,7 @@
static int
parse_param_lu(const char *eq, long unsigned *lu)
{
- if (sscanf(eq + 1, "%lu", lu) == 1)
+ if (sscanf(eq + 1, "%li", lu) == 1)
return URJ_STATUS_OK;
urj_error_set (URJ_ERROR_SYNTAX, "need unsigned int, not '%s'", eq + 1);
-mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm
_______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
