2009/11/18 Martin Preuss <[email protected]>: > Hi, > > On Mittwoch, 18. November 2009, Ludovic Rousseau wrote: >> 2009/11/18 Emmanuel Deloget <[email protected]>: >> > Giuseppe "Gippa" Paterno' wrote: > [...] >> No. Your driver do not have to support HAL or DeviceKit or libusb or >> any other plug-n-play infrastructure. That is the job of pcscd. >> >> But your driver should interpret the device name passed in DeviceName >> parameter of IFDHCreateChannelByName(). See [1] > [...] > > Right, but for the driver to understand a HAL-device name (e.g. name > containing ":libhal:" it needs to be able to map the given name to a specific > device (well, at least when there is more than one reader in the system).
Exact. My CCID does that for the libusb scheme but not yet for the libhal scheme. > There is no way for a HAL-agnostic driver to deduce the device address to be > used with Libusb from a HAL device name... > > That's why I asked before: Does PC/SC fall back to libusb names if the driver > doesn't understand HAL (or deviceKit ord whatever new they come up with)? > > It would be very nice if pcscd retried with a ":libusb:" name if the driver > doesn't understand ":libhal:"... pcscd does that since version 1.5.4 (24 June 2009) - if RFAddReader() fails with the libhal scheme then we try with the (old) libusb scheme. This patch should allow proprietary drivers to work even if pcsc-lite is compiled with libhal support. Bye -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
