udev-ish replacement for hal-cups-utils?
twaugh at redhat.com
Sat Jul 18 10:22:40 PDT 2009
On Tue, 2009-07-14 at 18:32 +0200, Martin Pitt wrote:
> So, one immediate workaround would be to not pass the device ID
> itself, but the path (%p) and just read that value plus "/ieee1284_id"
> from the python program. That's a little tricky with identifying the
> ID at removal time, though (you'd need to remember the quoted one as
> well, i. e. consider that an abstract identifier for the real device
Bad news on this front: that ieee1284_id file is supplied by the usblp
module, which we are trying to avoid.
> A more interesting approach is to use libgudev, which provides a
> gobject-based interface to udev. Ideally it'd be easy to auto-generate python
> bindings with gobject introspection, but I never did that before. I'll
> look into that in the next days, and report back if that's a viable
There's no need, we are in C at the point we need to read the Device ID.
So I guess I'll have to do it using libusb. (Not sure how libgudev or
libudev would help there...)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/devkit-devel/attachments/20090718/6f1da08c/attachment.pgp
More information about the devkit-devel