lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 10 Mar 2014 07:50:12 -0400 (EDT)
From:	Jon Ringle <>
To:	Alexander Shiyan <>
	Jon Ringle <>
Subject: Re: [PATCH] RFC: WIP: sc16is7xx [v0.4]

On Mon, 10 Mar 2014, Alexander Shiyan wrote:

> Понедельник, 10 марта 2014, 2:26 -04:00 от
> > From: Jon Ringle <>
> ...
> > +config SERIAL_SC16IS7XX
> > +	tristate "SC16IS7xx RS485 serial support"
> > +	  select SERIAL_CORE
> > +	  default n
> > +	  help
> > +	  This selects support for SC16IS7xx for use as a RS485 serial port
> Documentation says:
> The SC16IS740/750/760 is a slave I²C-bus/SPI interface to a single-channel
> high performance UART.
> ...
> The SC16IS740/750/760 also provides additional advanced features such
> as auto hardware and software flow control, automatic RS-485 support...
> So why do you position this chip as RS485 only? Automatic direction for
> RS485 is just a feature as an addition for standart UART.

You're right. This is just how we are using the chip in our board. Would a 
configuration flag in platform_data make sense to use the auto rs485 

Any thoughts as to the latency issue I report?



Powered by blists - more mailing lists