David Suffield [2008-03-27 16:59 -0000]:
> You do not need explicit usb-pids for HP printer products. You can
> determine if the udev event is a HP printer product by performing a
> wild-card compare on the idProduct. See 55-hpmud.rules file.
Ah, thanks for the hint. Unfortunately hal cannot do string-based
matching on integer properties, so we need a longer FDI rule.
But generating that should not be a problem with the data which we
have now.
Till, maybe you can start experimenting with that? Use the Perl script
from above to generate an FDI and put that into
/usr/share/hal/fdi/preprobe/10osvendor/20-hplip-scanners.fdi and check
whether it works?
David Suffield [2008-03-27 16:59 -0000]:
> You do not need explicit usb-pids for HP printer products. You can
> determine if the udev event is a HP printer product by performing a
> wild-card compare on the idProduct. See 55-hpmud.rules file.
Ah, thanks for the hint. Unfortunately hal cannot do string-based
matching on integer properties, so we need a longer FDI rule.
But generating that should not be a problem with the data which we
have now.
Till, maybe you can start experimenting with that? Use the Perl script hal/fdi/ preprobe/ 10osvendor/ 20-hplip- scanners. fdi and check
from above to generate an FDI and put that into
/usr/share/
whether it works?
Thanks all,
Martin
-- www.piware. de
Martin Pitt | http://
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)