On Mon, 15 May 2000, Vojtech Pavlik wrote:
> On Sun, May 14, 2000 at 10:11:20PM -0400, Brian F. Hensch wrote:
>
> > Trying to get the printer driver to work I ran across a small problem when
> > I forced it to probe for the uni-directional interface. The probe
> > function assumed that the out endpoint was the first end point. This
> > should be sensible but my HP doesn't make sense and has an in endpoint
> > first. The attached patch fixes this assumption.
>
> Well, in unidirectional mode the device should have the out endpoint
> *only*. This is in the specification. Ok, I'll Extend the probng as you
> suggested.
I'm sorry, what document and what section are you reading the *only*
requirement in? I'm not finding it. I have the Printer Device Class
Definition document version 1.082 draft, Jan 2000. I'm only finding that
a uni-directonal must support a BULK out endpoint and a bidi must support
a BULK in and a BULK out endpoint.
> > I still get extra random characters with the bidi interface unless I
> > comment out the submit read urb "usb_submit_urb(&usblp->readurb);" in
> > usblp_open(). It also works if I force the uni-directional interface.
>
> You mean extra random characters printed? This is really odd. Please try
> with the attached patch.
I guess they don't seem like extra chars. but rather random chars will be
modified into hearts or accented a's. Stuff I can't represent in text
e-mail.
I'll try an example:
A file containing several lines of the text:
This is a test of the HP Deskjet 812C.
Some characters will get messed up.
Some lines will come out:
This is a test of the HP Deskjet 812C.
Some characters will get messW_@#@.
Unless I set the alts = 0 or bidi = 0 in the probe or I comment out the
submit read URB in the open. Then it works fine. It also works well with
2.2.14 with a very old backport patch, before the printer driver was
URBified.
I forgot to let you know I am working with kernel version 2.3.99-pre6. I
can't get pre7 or pre8 to boot.
> > It looks to me that the read is just totally broken. Not being very
> > familiar with this I'm not sure how to fix it.
>
> What seems broken to you? If you have any comments, tell me, I could
> have made some mistake there.
I Shouldn't have said that. Reading is at least broken with my printer.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
