On Tue, Jan 11, 2005 at 04:11:48PM +0100, Gernot Fink wrote:
> On Tue, 11 Jan 2005, Greg KH wrote:
> > On Mon, Jan 10, 2005 at 02:24:22PM -0800, Pete Zaitcev wrote:
> > > The 2.4 version looks sane, but I would like someone who has a
> > > known-working
> > > pl2303 to test the patch below against possible breakage on 2.6. Unless
> > > it's
> > > in 2.6 and we know that it does not make anything worse I'm not taking it
> > > into 2.4.
> > >
> > > Best wishes,
> > > -- Pete
> > >
> > > --- linux-2.6.10/drivers/usb/serial/pl2303.c 2005-01-05
> > > 00:37:59.000000000 -0800
> > > +++ linux-2.6.10-lem/drivers/usb/serial/pl2303.c 2005-01-10
> > > 14:14:17.532446800 -0800
> > > @@ -510,6 +510,12 @@
> > > dbg ("0xa1:0x21:0:0 %d - %x %x %x %x %x %x %x", i,
> > > buf[0], buf[1], buf[2], buf[3], buf[4], buf[5], buf[6]);
> > >
> > > + if (cflag & CLOCAL) {
> > > + i = usb_control_msg (serial->dev, usb_sndctrlpipe (serial->dev,
> > > 0),
> > > + VENDOR_WRITE_REQUEST,
> > > VENDOR_WRITE_REQUEST_TYPE,
> > > + 0x0, 0x0, NULL, 0, 100);
> > > + dbg ("0x40:0x1:0x0:0x0 %d", i);
> > > + }
> > > if (cflag & CRTSCTS) {
> > > __u16 index;
> > > if (priv->type == HX)
> > >
> >
> > Where does this "0x00 0x00" message come from? It isn't in the 2.6
> > driver, and I don't know what it does to the device.
> >
> It comes of the Headerfile from the PL2303-driver from
> Sam Kuo ([EMAIL PROTECTED])
>
> #define PROLIFIC_SA_FLOW_NONE 0x0000 /* No flow control */
> #define PROLIFIC_SA_FLOW_OCTS 0x0001 /* use CTS input to
> throttle output */
> #define PROLIFIC_SA_FLOW_ODSR 0x0002 /* use DSR input to
> throttle output */
> #define PROLIFIC_SA_FLOW_IDSR 0x0004 /* use DSR input to
> enable receive */
> #define PROLIFIC_SA_FLOW_IDTR 0x0008 /* use DTR output for
> input flow control */
> #define PROLIFIC_SA_FLOW_IRTS 0x0010 /* use RTS output for
> input flow control */
> #define PROLIFIC_SA_FLOW_ORTS 0x0020 /* use RTS to indicate
> data available to send */
> #define PROLIFIC_SA_FLOW_ERRSUB 0x0040 /* ???? guess ????
> substitute inline errors */
> #define PROLIFIC_SA_FLOW_OXON 0x0080 /* use XON/XOFF for
> output flow control */
> #define PROLIFIC_SA_FLOW_IXON 0x0100 /* use XON/XOFF for input
> flow control */
I'm sorry, but these values are known to be incorrect. Pretty funny
that prolific now recommends that their users use the in-kernel driver,
instead of their own version, as their own version did not support any
of these settings.
thanks,
greg k-h
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
