[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAP7ucJrkhJ=nqwruf0p+YOCdqtH5+N6pgeAY_qF9g7Wc6_XiA@mail.gmail.com>
Date: Wed, 4 Nov 2015 16:19:45 +0100
From: Aleksander Morgado <aleksander@...ksander.es>
To: Vostrikov Andrey <andrey.vostrikov@...entembedded.com>
Cc: Marek Vasut <marex@...x.de>,
Oliver Hartkopp <socketcan@...tkopp.net>,
Marc Kleine-Budde <mkl@...gutronix.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Wolfgang Grandegger <wg@...ndegger.com>,
Andrew Lunn <andrew@...n.ch>
Subject: Re: [RFC][PATCH] net: arinc429: Add ARINC-429 stack
On Wed, Nov 4, 2015 at 4:18 PM, Vostrikov Andrey
<andrey.vostrikov@...entembedded.com> wrote:
>>> > About the parity -- can we add some flag into the datagram to indicate we
>>> > want hardware to calculate the parity for that particular datagram for
>>> > us? And we'd also need to indicate what type of parity. I dunno if this
>>> > is worth the hassle.
>>>
>>> This is HW configuration property, it does not belong to datagram. Also
>>> for TX channels, parity could be two kinds: odd and even, for RX it
>>> is only on/off.
>
>> There are datagrams which do contain parity and ones which do not contain it,
>> correct ? Thus, it's a property of that particular datagram.
All ARINC words have bit #31 as parity bit; whether it's used or not
depends on the setup as Andrey says below.
> For RX side it is both: datagram and HW (is it checked by receiver or not)
> But for TX side it is HW property of transmitter, either OFF or ON (odd or even).
--
Aleksander
https://aleksander.es
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists