my Xinput module for the tablet

Peter Hutterer peter at
Thu Jun 5 15:02:49 PDT 2008

On Thu, Jun 05, 2008 at 11:29:00AM -0400, Chuck Robey wrote:
> Hash: SHA1
> Nicholas King wrote:
> > Peter Hutterer wrote:
> >> the current evdev driver is very easy to understand and gives you a good
> >> structure on how input drivers look like. Additionally, there's
> >> (which
> >> would
> >> appreciate updating as you learn :)
> OK, I hadn't seen that page, it'll help.  My problem is one of finding the
> standard way of doing things ... as an example (this is example only, I'm not
> asking you to answer this, because I have 10 other questions, and I will ask
> questions here only when I get really stuck) like, I wanted to have two kinds of
> error prints, those that presage module failure, and those that only show up
> when you ask for a verbose boot arraangement, but  ican't yet find out the call.
>  I've been hunting thru various other drivers, because at least some of them
> must do that.

I'll answer anyway. Try and stop me :P

xf86Msg(X_ERROR, "blah blah"); 
works like printf, and will be filtered depending on the verbosity setting.
xserver/include/os.h has the enum with the allowed flags. X_INFO is common for
more verbose stuff.


More information about the xorg mailing list