On Thu, May 24, 2012 at 2:09 PM, Akos Vandra <[email protected]> wrote:
> Hi Andreas,
>
> The new ftdi driver is spamming the output with debug level messages,
> and it's hard to debug own code. Is there an easy way to disable them,
> without disabling debug level messages altogether?
>
Hi!
Spencer has pointed this out in gerrit. My intention was to keep the
debug messages until the driver proved stable enough. The messages are
valuable if someone reports problems with the driver. Once the driver
is merged, the idea is to change the messages from debug level to
conditionally enabled at compile time.
A better solution is perhaps to introduce yet another, more verbose,
debug level for this kind of low level debug output.
I'll probably post an updated patch soonish, with the debug messages
removed. Until then, for your own purpose, you can redefine the
LOG_DEBUG macro locally in the mpsse.c file. Something like:
#undef LOG_DEBUG
#define LOG_DEBUG(x ...) do {} while (0)
inserted *after* the block of includes.
/Andreas
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
