[PATCH] kdrive: output meaningful error message for HAL devices.

[Peter Hutterer]

On Wed, Sep 09, 2009 at 03:28:13PM -0700, Dan Nicholson wrote:
> On Wed, Sep 9, 2009 at 3:09 PM, Peter Hutterer <peter.hutterer at who-t.net> wrote:
> > On Wed, Sep 09, 2009 at 08:29:38AM -0700, Dan Nicholson wrote:
> >> On Tue, Sep 8, 2009 at 5:14 PM, Daniel Stone <daniel at fooishbar.org> wrote:
> >> > On Wed, Sep 09, 2009 at 09:31:34AM +1000, Peter Hutterer wrote:
> >> >> kdrive ignores all devices from hal as they don't have the 'type' option
> >> >> set. Instead of "Unrecognised device identifier!" print out "Ignoring
> >> >> device from HAL." to indicate that the errors surrounding the device don't
> >> >> really matter.
> >> >>
> >> >> Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
> >> >
> >> > Signed-off-by: Daniel Stone <daniel at fooishbar.org>
> >> >
> >> > That being said, if we do actually keep the other KDrive DDXes beyond
> >> > 1.7's release, we should actually get around to unifying input device
> >> > handling in KDrive.
> >>
> >> I've got some patches I'm working on that are tangential to this
> >> issue, but they do pass the type from HAL. Or, they just set some
> >> booleans from the input.keys and input.mouse capabilities. Let me know
> >> if you'd like to see them sooner than later when I finish polishing up
> >> the other stuff I'm using it for.
> >
> > If you want or need them in 1.7, sooner is better.
> 
> No, it's pretty late in the game for 1.7 and I think they'll need some
> review (and they break the NIDR ABI). This was the InputClass stuff I
> mentioned to you a few weeks ago. The code just happens to push some
> of the properties out to NIDR.

Oh, ic. In that case there's no need to hurry. It might be good to get them
ready to merge ASAP after 1.7 though.

Cheers,
  Peter