[Hal] Re: [PATCH] add detection of Tablet PCs with WACOM tablet
devices
Danny Kukawka
danny.kukawka at web.de
Tue Aug 16 00:13:02 PDT 2005
On Monday 15 August 2005 21:13, David Zeuthen wrote:
> Hi,
>
> sorry for me being slow,
No problem
[...]
> + 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.
> 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.
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.
> 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. ;-)
Cheers,
Danny
More information about the hal
mailing list