[Hal] Re: [PATCH] add detection of Tablet PCs with WACOM tablet devices

[David Zeuthen]

Hi,

Sorry for the lag.. there's been some issues with fd.o and this mailing
list too...

On Tue, 2005-08-16 at 09:13 +0200, Danny Kukawka wrote:
> > +       hal_device_add_capability (d, "input");
> > +       hal_device_add_capability (d, "input.tablet");
> >
> > Do we set properties, e.g.
> >
> >  input.device
> >  input.physical_device
> >
> > that is required for having the 'input' capability? Also, what's wrong
> > with just matching on pnp.id
> 
> No, we set them not. What should we set there? This device is the 
> input.physical_device. 

Then it shouldn't have any input.* properties nor the capability.. What
input.* properties mean is that there is a kernel abstraction for the
device and users can e.g. expect to read input.device which contains the
name of the device file used to access the input device...

> >  WACf00[4-6]
> >
> > from a .fdi file and doing the setserial from there? Also, after doing
> > the setserial stuff will we get a hotplug event for the input device?
> 
> The problem: if we do only a match from a fdi-file for pnp.id, we don't get 
> the informtation about the serial irq and port to use setserial. Them are all 
> different for every manufacturer of Tablet PCs and sometimes between models 
> from one manufacturer (e.g ACER: 0x93f8/4 and 0x06f8/6, FSC:0x0220/4, 
> HP/Compaq: 0x0300/4 and 0x0200/6 ...) so we can't add this to a fdi-file for 
> all machines. I collected data about many different Tablet PCs for my diploma 
> thesis (but not for all) and I think it's also complicated to collect this 
> data (irq/port/pnp.id and dmimatch) for all and keep the information 
> up-to-date. Since the kernel provides the information to sysfs HAL is the 
> perfect place to parse this information.

Well, yea, I see your point but I'm not sure there is big difference
whether this is in hald or in a helper invoked by hald?

> This is a internal serial device. The information about the device come from 
> the bios/dsdt. I tested if you get a hotplug event: no event if you use 
> setserial. Also not from e.g. /dev/ttyS0.

oh.. so there is no Linux Input Event device file, eg. /dev/input/event3
for the abstraction for this physical device? There really needs to be..
that's what ppl expect from a hal device object of capability input. If
there isn't maybe the kernel driver needs to get updated?

> > Sorry for all these questions; maybe it would easier if you showed a few
> > hal-device-manager screenshots from the different stages in the
> > initialization.
> 
> Questions are no problem. ;-)

Great!

Cheers,
David