On 2014/01/15 23:07, patrick keshishian wrote:
> Setting that aside, it doesn't look like I can use ulpt device
> to write a dedicated "driver" for this printer. Is this correct?
> Do I need to "fudge" the kernel to not attach this device to
> ulpt but instead as ugen? Is there a better way? I rather not
> diverge from GENERIC.

There's some support in libusb for accessing non-ugen(4) devices,
specifically control transfers and synchronous reads.

But if this code is to do some necessary initialization for a particular
printer that can be matched by IDs, adding support right in the ulpt(4)
driver would probably be better, there's already some framework for matching
things by ID for printers which need firmware to be uploaded, so you could
possibly hook into this.

Reply via email to