Peter Hutterer wrote:
> This way it's more obvious which messages are driver messages and which ones
> aren't, especially when multiple drivers are fighting over the same device.
> Also, grep works much better.
>
> xf86DrvMsgVerb() cannot be used here, it uses the output driver as prefix.
>
> Signed-off-by: Peter Hutterer <[email protected]>
> ---
> There's the option of having another macro for logging but I'd rather have
> the code clean, using the server API directly instead of wrapping around it.
> fwiw, I'm planning to do the same to the other drivers too.
I was going to ask if we didn't already have xf86DrvMsg, but then realized
that's only for video drivers since you specify the screen id to identify
the driver - I wonder if adding a input driver equivalent to the API would
make sense.
--
-Alan Coopersmith- [email protected]
Oracle Solaris Platform Engineering: X Window System
_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
