From: Guenter Roeck <linux@roeck-us.net>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Adding support for ARINC429 into the Linux kernel
Date: Wed, 19 Jun 2013 13:29:55 -0700 [thread overview]
Message-ID: <20130619202954.GA5594@roeck-us.net> (raw)
Hi all,
I have been asked to explore options for adding ARINC 429 support [1]
into the Linux kernel, primarily to support devices from Holt Integrated
Circuits [2] (the request is unrelated to the chip manufacturer).
ARINC429 is a protocol which is widely used in commercial airplanes.
There are various chips supporting this protocol available, as well as
out-of-tree Linux support. The drivers I have looked at implement it
either as character device or misc device and typically pass raw receive
data to userspace.
I can see a number of options for going forward:
1) Implement as character device (or possibly misc device) and pass
raw data to/from user space
1a) Just implement a driver for the specific chips
2b) Implement some kind of generic infrastructure
2) Implement as network driver with a new address family, similar to,
say, AF_CAN.
Any thoughts / suggestions which approach would be better and, most of all,
which approach might have a better chance of being accepted upstream ?
Thanks,
Guenter
--
[1] http://en.wikipedia.org/wiki/ARINC_429
[2] http://www.holtic.com/category/352-arinc-429.aspx
next reply other threads:[~2013-06-19 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 20:29 Guenter Roeck [this message]
2013-06-19 21:45 ` Adding support for ARINC429 into the Linux kernel Arnd Bergmann
2013-06-20 4:10 ` Guenter Roeck
2013-06-20 8:52 ` Arnd Bergmann
2013-06-28 21:53 ` Guenter Roeck
2013-07-01 10:06 ` Pavel Machek
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=20130619202954.GA5594@roeck-us.net \
--to=linux@roeck-us.net \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).