From: Grant Edwards <grante@visi.com>
To: linux-serial@vger.kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: Suggested patch for linux
Date: Fri, 18 Jul 2008 13:55:38 +0000 (UTC) [thread overview]
Message-ID: <g5q7cp$o4j$1@ger.gmane.org> (raw)
In-Reply-To: 200807181219.54170.laurentp@cse-semaphore.com
On 2008-07-18, Laurent Pinchart <laurentp@cse-semaphore.com> wrote:
>> I believe that he is referring to something much simpler than
>> you are thinking. He is talking about 2-wire RS485
>> transmissions in which the RTS signal is used to enable the
>> driver chips just before transmitting data and disabling
>> (tri-stating) them just after transmitting data. There are
>> some UARTs that have this behavior built into them.
>
> And that feature is currently not supported by Linux, even
> with UARTs that have hardware support for "Auto RS485" mode,
> such as the 8250-compatible XR16C2850.
>
> The issue is that no flag is defined for the c_cflag field of
> the termios structure to enable that feature. The following
> patch is an example of what would be required.
I'd definitely be in favor of such a flag. It sucks having to
resort to various hacks to control support of that feature in
Linux serial drivers.
--
Grant Edwards grante Yow! In Newark the
at laundromats are open 24
visi.com hours a day!
next prev parent reply other threads:[~2008-07-18 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 23:16 Suggested patch for linux Axel Hosemann
[not found] ` <487546D5.8050908-3sKltW3hOZofv37vnLkPlQ@public.gmane.org>
2008-07-10 8:59 ` Alan Cox
2008-07-10 14:16 ` Matt Schulte
2008-07-12 21:49 ` Axel Hosemann
2008-07-12 22:33 ` Alan Cox
2008-07-15 20:43 ` Matt Schulte
[not found] ` <1860bbce0807151343rf5cf4apecdc422ba747dd7d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-15 20:46 ` Alan Cox
2008-07-18 10:19 ` Laurent Pinchart
2008-07-18 13:55 ` Grant Edwards [this message]
2008-07-10 14:47 ` Grant Edwards
2008-08-04 13:28 ` Tosoni
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='g5q7cp$o4j$1@ger.gmane.org' \
--to=grante@visi.com \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).