On 24/06/2011, at 2:04 AM, Michael Schwingen wrote: > On 23.06.2011 14:39, Laurent Gauch wrote: >>> />>/ I don't see how. >>> />/ />/ I haven't followed this(big discussions), but I've seen on the >>> list >>> />/ in the past that casting is frowned upon and using these >>> />/ macros is cheered... Anyway... I'm happy to follow the path >>> />/ of using these macros, I certainly don't want to become an >>> />/ expert! :-) >>> / >> We do not ask maintainers, as you, to be experts. >>> I guess I'm not quite sure what you want. >>> Feel free to apply a modified patch if you want, >>> as long as it removes the warnings. > >> I do not understand too ! >> Please explain us exactly what you want, or please merge the steve's >> patch asap. > > I think he did: using casts is no solution, since it only removes the > warnings on *some* systems. Using the PRxxx macros as done in other parts of > the code is the right way, so a new patch using the macros should be > submitted - this is not a task for a maintainer, but for the patch submitter.
Then perhaps this is what you are after. I'm not sure if it is any more correct, since FT_STATUS is ULONG which is unsigned int (!), not uint32_t Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002
0001-ft2232-Fix-warnings-when-building-against-D2XX.patch
Description: Binary data
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
