[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201511041607.30577.marex@denx.de>
Date: Wed, 4 Nov 2015 16:07:30 +0100
From: Marek Vasut <marex@...x.de>
To: Vostrikov Andrey <andrey.vostrikov@...entembedded.com>
Cc: Aleksander Morgado <aleksander@...ksander.es>,
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 Wednesday, November 04, 2015 at 04:03:16 PM, Vostrikov Andrey wrote:
> Hi, Marek.
Hi,
> > 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.
> Parity is not the only property that needs to be configured in HW,
> following could be needed as well,
> - label bit flipping (on or off)
This is hardware property.
> - rate change (low / high)
This is again hardware configuration -- you have to configure the link speed
before you do RX/TX.
> - label filters and label priority matching (this could be HoltIC
> specific)
>
> I suppose all these properties are configured only once, at
> interface initialization.
These three above, yes. Parity, I don't think so.
Best regards,
Marek Vasut
--
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