From: Paul Fulghum <paulkf@microgate.com>
To: Thomas Stewart <thomas@stewarts.org.uk>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: belkin usb serial converter (mct_u232), break not working
Date: Thu, 04 Nov 2004 13:21:41 -0600 [thread overview]
Message-ID: <1099596101.2834.33.camel@deimos.microgate.com> (raw)
In-Reply-To: <200411041820.21847.thomas@stewarts.org.uk>
On Thu, 2004-11-04 at 12:20, Thomas Stewart wrote:
> I tried the converter on a XP machine and unfortunately while using the
> manufacturer provided drivers I was unable to produce a break :-(
That seems consistent with the code, comments,
and observed behavior.
I doubt this device can generate a break.
> was told the product (F5U109ea) was designed for PDA use only and it would
> generate breaks fine if connected to them.
Sounds like garbage (industry standard for phone support) to me.
I can't see how the bit pattern generated on TxD is dependent
on the attached device. The support person probably
has no idea what a break pattern is.
> Interestingly I got my hands on a F5U103 and it works fine (uses another chip
> and consequently module).
This all looks like a missing/non-functioning feature
for the F5U109.
--
Paul Fulghum
paulkf@microgate.com
prev parent reply other threads:[~2004-11-04 19:37 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
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 [this message]
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=1099596101.2834.33.camel@deimos.microgate.com \
--to=paulkf@microgate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@stewarts.org.uk \
/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.