All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Stewart <thomas@stewarts.org.uk>
To: Paul Fulghum <paulkf@microgate.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: belkin usb serial converter (mct_u232), break not working
Date: Wed, 20 Oct 2004 23:08:02 +0100	[thread overview]
Message-ID: <200410202308.02624.thomas@stewarts.org.uk> (raw)
In-Reply-To: <1098307331.2818.15.camel@deimos.microgate.com>

On Wednesday 20 October 2004 22:22, you wrote:
> Try replacing ioctl(fd, TCSBRK, 0) with
> ioctl(fd, TCSBRKP, duration)
> duration is in 100ms units, so try 10 or 20.
>
> Or you can use tcsendbreak(fd, duration);
> I'm not sure of the units for this function on Linux
> manpage says 'implementation defined',
> a book I have says 250ms units in Linux.

I've tyred various combinations of ioctl(fd, TCSBRKP, x) and tcsendbreak(fd, 
x), where x is 2, 5, 10, 20 and 200.

One thing I did notice is that no mater what the value I use, it always 
finishes very quickly, there does not appear to be any duration.

take porttest.c:
#include <sys/fcntl.h>
#include <sys/ioctl.h>
main(int argc, char ** argv) {
        int fd = open(argv[1], O_RDWR|O_NOCTTY);
        ioctl(fd, TCSBRKP, 20);
        close(fd);
}

$ time ./porttest /dev/ttyS0
real    0m2.001s
user    0m0.001s
sys     0m0.000s

A standard serial port with a 2 second break (20*100ms), takes as expected 
just over 2 seconds.

$ time ./porttest /dev/ttyUSB1
real    0m0.004s
user    0m0.000s
sys     0m0.001s

However with the USB converter instead, it takes 5 ms to complete. Much 
shorter than expected.

Is it a driver issue?

Regards
-- 
Tom

PGP Fingerprint [DCCD 7DCB A74A 3E3B 60D5  DF4C FC1D 1ECA 68A7 0C48]
PGP Publickey   [http://www.stewarts.org.uk/public-key.asc]
PGP ID  [0x68A70C48]

  reply	other threads:[~2004-10-20 22:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 18:46 belkin usb serial converter (mct_u232), break not working Thomas Stewart
2004-10-20 20:48 ` Paul Fulghum
2004-10-20 21:22 ` Paul Fulghum
2004-10-20 22:08   ` Thomas Stewart [this message]
2004-10-20 22:15     ` Paul Fulghum
2004-10-20 22:21     ` Paul Fulghum
2004-10-20 22:27     ` Paul Fulghum
2004-10-20 23:04       ` Thomas Stewart
2004-10-21  2:37         ` Paul Fulghum
2004-10-21 10:06           ` Thomas Stewart
2004-10-21 12:41             ` Paul Fulghum
2004-10-21 19:44               ` Paul Fulghum
2004-11-04 18:20                 ` Thomas Stewart
2004-11-04 19:21                   ` Paul Fulghum

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=200410202308.02624.thomas@stewarts.org.uk \
    --to=thomas@stewarts.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulkf@microgate.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.