Closed tangyanli closed 4 years ago
@tillkamppeter and @alexpevzner I'm still convinced that the problem comes from the packaging since the problem is only present on debian.
@Ordissimo,
regardless of that, it makes sense to drop from the ippusbxd
the old legacy code, that extracts information from the USB DeviceId, because this source of information is not very reliable, and rely on IPP printer attributes, as ipp-usb
does.
IPP printer attributes are always reliable, because without them IPP printing will not work
@alexpevzner , It's partially done, in fact we could use that mechanism
@Ordissimo I am sorry that I didn’t give a clear comment. This issue is found when I test another device. And it also happens on ubuntu.
Yes, the USB-Device-ID-based code for finding device capabilities can be removed. IPP/eSCL is much more reliable.
@tillkamppeter The usb is no longer used for registrations that are based on IPP and eSCL.
Accepted pull request #37, thanks, @Ordissimo.
Hello, The ippusbxd fails to register my device when the device is connected via USB. Because my device doesn't return correct CMD Info (device-id).
But ipp-usb works well, and the ipp-usb can get pdl info from document-format-supported which returned correctly by my device.