linux-kernel - Re: Regarding USB-RS485 Cable Manufacturer: FTDI SerialNumber: FTU6Z938

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 10 Aug 2011 10:34:17 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Raju Rameshwar Uprade" <rajsingh@...a.tifr.res.in>
Cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: Regarding USB-RS485 Cable Manufacturer: FTDI SerialNumber:
 FTU6Z938

On Wed, 10 Aug 2011 10:55:39 +0530
"Raju Rameshwar Uprade" <rajsingh@...a.tifr.res.in> wrote:

> 
> Hello Greg,
>            I have purchased a USB-RS485 Cable Manufacturer: FTDI SerialNumber: FTU6Z938.
> And I have written a user space program to communicate with my Rs-485 device at the
> other end.The device at the other end expect 1 address byte with mark parity and rest of
> the bytes with space parity

Linux will be doing RS232/422 by default. If you are doing EIA-485 then
you also need to manage the transmitter and how that is handled is going
to depend upon the cable you have. It may need driver changes, it may
simply need you to manage the carrier assert and sometimes carrier
presence in order to implement the transmitter.

Really you'll need to look at the suppliers data sheets and see.

Alan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/