Maintainership for the abandoned acecad driver

[Giuseppe Bilotta]

On 4/25/07, Daniel Stone <daniel at fooishbar.org> wrote:
> On Wed, Apr 25, 2007 at 02:15:09AM +0200, Giuseppe Bilotta wrote:
> > No, much simpler. I got the idea (and much of the code) from the synaptics
> > driver: it tries each /dev/input/eventX until one is found whose driver
> > name begins with "acecad". It's a little too braindead at the moment, but I
> > don't know if it's possible to just ask the kernel "tell me about the
> > eventX handled by the usb_acecad module".
>
> Egh.  It would be really nice if this was _only_ triggered if Device was
> explicitly set to 'auto' or so.

This is indeed the case: autodetection is only triggered if Device is
missing or set to auto-dev.

> We can handle this much, much better in
> newer versions of the server (input hotplug).

Of course. But in the mean time it's nice to have something that works
without a need to specify
/dev/input/by-id/usb-ACECAD_Tablet-event-mouse as Device :D

> Ah, that explains it.  Patches 1 and 2 are a reply to 0, but 3 and 4 are
> separate.  So yeah, I guess it does DTRT.  Having a sleep in between the
> mails would be great, too.  (The reason I do them separately is because
> Exchange has somewhat random delivery, so any patches I send like this
> at work can end up randomised unless I sleep for a few seconds in
> between.)

Yeah, I'll file a ticket to the git guys about that :)

-- 
Giuseppe "Oblomov" Bilotta