public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "'Aristeu Rozanski'" <arozansk@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tosoni <jp.tosoni@acksys.fr>,
	"'Laurent Pinchart'" <laurentp@cse-semaphore.com>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] 8250: add support for DTR/DSR hardware flow control
Date: Thu, 21 Aug 2008 14:59:39 -0400	[thread overview]
Message-ID: <20080821185938.GG7154@redhat.com> (raw)
In-Reply-To: <20080821112309.6519c29f@lxorguk.ukuu.org.uk>

> > > > About a RS485 ioctl: could you consider the attached files which are already
> > > > in the Linux kernel (in include/asm-cris).
> > > > They define a TIOCSERSETRS485 (ioctl.h), and the data structure (rs485.h)
> > > > with allows to specify timings. Sounds just like what we want ?
> > > 
> > > I had a deeper look at this for RS485 and the answer is "sort of". I've
> > > reworked the structure to keep it the same size irrespective of 32/64bit
> > > systems, and to make stuff flags that can be, plus add some extra u32
> > > words in case we need to (.. when we need to ;)) add stuff later.
> > > 
> > > Comments, thoughts - will this do what people in the RS485 world need ?
> > as for DTR/DSR patch, will be used the same approach?
> 
> I'm still trying to get a sensible answer on how other Unixes handle it
I did some research on that:
Solaris and AIX:
	TC{G,S}ETX for extended options and only input flow control (DTRXOFF)
SCO:
	{S,G}ETFLOW for configuring flow control, TXHARD, RXHARD for DTRDSR
FreeBSD:
	cflags has 'dtrflow' and 'dsrflow'

Having the option to set individually which pins to use for input and output
flow control and which ones should be on/off all the time seem to be a powerful
way to do it, instead of having a "CDTRDSR".

-- 
Aristeu


      reply	other threads:[~2008-08-21 18:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 21:14 [PATCH v1] 8250: add support for DTR/DSR hardware flow control Aristeu Rozanski
2008-08-07  8:32 ` Laurent Pinchart
2008-08-07  9:14   ` Alan Cox
2008-08-07 12:54   ` Tosoni
2008-08-13 11:39     ` Alan Cox
2008-08-18 15:25     ` Alan Cox
2008-08-20 21:43       ` Aristeu Rozanski
2008-08-21 10:23         ` Alan Cox
2008-08-21 18:59           ` 'Aristeu Rozanski' [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=20080821185938.GG7154@redhat.com \
    --to=arozansk@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jp.tosoni@acksys.fr \
    --cc=laurentp@cse-semaphore.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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