From: wixor <wixorpeek@gmail.com>
To: "Greg KH" <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: using usblp with ppdev?
Date: Tue, 7 Mar 2006 18:02:12 +0100 [thread overview]
Message-ID: <c43b2e150603070902l10659822ib6ffe1c4b0b296bf@mail.gmail.com> (raw)
In-Reply-To: <20060306172532.GB8697@kroah.com>
>
> But if you want to play around and verify this, try modifying the USB
> device table in the drivers/usb/misc/uss720.c file (look for the
> structure called "uss720_table" and add a new entry with the vendor and
> product id of your device there.)
>
Well, it seems the device doesn't like the driver or vice-verse. When
added entry to the uss720_table, /proc/bus/usb/devices reports that
the device is being handled by this driver, but when I plug the device
in, dmesg gets full of error reports, and the device file doesn't
appear in /dev . Now, my question is: is the cable named "usb to
parallel cable" an interface that converts classic printer to usb
printer? Shouldn't it be rather a real usb to parallel cable? Is it
some kind of protocol limitation that the device is unable to perform
per-pin i/o tasks or maybe the protocol isn't simply fully
implemented by the device? Or maybe I should use some another protocol
(and driver) to use advanced (?) functions? The uss720 driver
complains about usb error -32 (like: get_1284_register: usb error -32
[but: async_complete: urb error -32 - shouldn't it be USB error? a
typo?])
thanks for help
wixor
next prev parent reply other threads:[~2006-03-07 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 15:32 wixor
2006-03-02 16:55 ` Greg KH
2006-03-02 17:46 ` Thomas Sailer
2006-03-03 13:12 ` wixor
2006-03-03 17:07 ` Greg KH
2006-03-06 14:31 ` wixor
2006-03-06 17:25 ` Greg KH
2006-03-07 17:02 ` wixor [this message]
2006-03-07 17:22 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c43b2e150603070902l10659822ib6ffe1c4b0b296bf@mail.gmail.com \
--to=wixorpeek@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®