On Tue, Jun 15, 2010 at 5:12 PM, Peter Hutterer
peter.hutte...@who-t.net wrote:
Input driver messages are only standardised by convention, with the drivers
prefixing the device name to most messages. This makes it rather hard to
grep on evdev for example when looking for the evdev ouput.
This
On Wed, Jun 16, 2010 at 02:37:48PM +0200, ext Dan Nicholson wrote:
Since this definition is in xf86Xinput.h, xf86Xinput.h is part of the
SDK, and these functions have to do with input devices, does it make
sense to put the declarations there and the code in xf86Xinput.c? Or
keep the code in
Input driver messages are only standardised by convention, with the drivers
prefixing the device name to most messages. This makes it rather hard to
grep on evdev for example when looking for the evdev ouput.
This patch adds three new logging functions, modeled after xf86DrvMsg(), the
logging
+tmpFormat = malloc(strlen(format)+ strlen(dev-drv-driverName) +
strlen(dev-name) + 5);
+if (!tmpFormat)
+return;
+
+sprintf(tmpFormat, %s: %s: %s, dev-drv-driverName, dev-name,
format);
Xprintf() ? (Aka our portable version of the not-yet-universal asprintf().)
--
On Tue, Jun 15, 2010 at 05:32:55PM -0700, Alan Coopersmith wrote:
+tmpFormat = malloc(strlen(format)+ strlen(dev-drv-driverName) +
strlen(dev-name) + 5);
+if (!tmpFormat)
+return;
+
+sprintf(tmpFormat, %s: %s: %s, dev-drv-driverName, dev-name,
format);
