Date: Fri, 3 Sep 2010 19:13:44 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: Piet Skiet <tuksgig@gmail.com> Cc: freebsd-usb@freebsd.org Subject: Re: USB synchronous control transfers (for usb-to-serial) Message-ID: <201009031913.44078.hselasky@c2i.net> In-Reply-To: <AANLkTi=Erhq_2kYg5D5teQoOoOLE=3BSEF=yE==BoM-a@mail.gmail.com> References: <AANLkTinr3KbWOqgQoKVvF84H2c02fHh9SQRDeUkSRn4B@mail.gmail.com> <201008310947.07460.hselasky@c2i.net> <AANLkTi=Erhq_2kYg5D5teQoOoOLE=3BSEF=yE==BoM-a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Hi, > > Attached is the patch adding a 250ms polling control transfer to > update the port status flags. I've also added CRTSCTS hardware flow > control. I did some tests with minicom and with gtkterm. Minicom works > perfectly, but gtkterm has problems at baud 115200 and also with > hardware flow control. I also testes the Prolific driver (uplcom) with > minicom and gtkterm, and gtkterm has the same problems at 115200 baud, > so I'm assuming it's a gtkterm bug (not maintained anymore). > > BTW, do the usb-to-serial drivers need the force_short_xfer usb > transfer flag? gtkterm seems to work slightly better without the > flag... > > Anyway, thanks for the help so far You can remove the force_short_xfer usb transfer flag, if you can verify that the chip receive data if you send a USB packet of exactly 64 or 512 bytes, depending on USB full or high-speed. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201009031913.44078.hselasky>