From: Jan Kiszka <jan.kiszka@domain.hid>
To: Richard Cochran <richardcochran@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [RFC 0/1] Class driver for raw Ethernet packets
Date: Fri, 23 Sep 2011 15:50:42 +0200 [thread overview]
Message-ID: <4E7C8EB2.1020308@domain.hid> (raw)
In-Reply-To: <cover.1316774468.git.richard.cochran@domain.hid>
On 2011-09-23 13:02, Richard Cochran wrote:
> This patch adds a class driver for raw Ethernet drivers under
> Xenomai. The goal is to support industrial protocols such as EtherCAT
> and IEC 61850, where the "stack" is a user space program needing
> direct access at the packet level. The class driver offers interfaces
> for registration, buffer management, and packet sending/receiving.
>
> Although this patch is a kind of first draft, still I have it working
> on the Freescale P2020 with a real world application, with very good
> results. I can post a patch series for the gianfar driver in the ipipe
> tree, if anyone is interested.
>
> The user space interface is a character device and not a socket, simply
> because my applications will probably never need fancy socket
> options. The class driver could surely be made to offer a socket
> instead, but I think the character is sufficient.
Many interesting interfaces already exists for standard PF_PACKET (e.g.
time stamping), plus you gain portability this way. So let's not create
something special here even if it's sufficient for the first use case.
>
> The class driver is clearly in the wrong directory within the source
> tree, but I put it there just to get started. It really does not fit
> to any of the other drivers, so it probably would need its own place
> under ksrc/drivers.
New class, new directory.
However, the key question is how this approach relates to RTnet. Right
now its likely comparing apples to onions, but that may change as things
evolve in the right direction.
Can you explain a bit about your NIC driver architecture and the
maintenance strategy? It looks like you are taking an approach of
patching existing drivers in-tree. Anything that resolves the
maintenance pain we have with the RTnet model is already worth
considering. Did you take this approach intentionally? What pros and
cons do you see?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-09-23 13:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 11:02 [Xenomai-core] [RFC 0/1] Class driver for raw Ethernet packets Richard Cochran
2011-09-23 11:02 ` [Xenomai-core] [RFC 1/1] Add a class " Richard Cochran
2011-09-23 11:27 ` [Xenomai-core] [RFC 0/1] Class " Richard Cochran
2011-09-23 13:34 ` Peter Soetens
2011-09-23 13:50 ` Jan Kiszka [this message]
2011-09-26 11:41 ` Richard Cochran
2011-09-27 8:26 ` Jan Kiszka
2011-09-27 12:01 ` Richard Cochran
2011-09-27 12:20 ` Jan Kiszka
2011-09-27 15:10 ` Richard Cochran
2011-09-27 15:16 ` Jan Kiszka
2011-09-27 16:05 ` Richard Cochran
2011-09-27 16:26 ` Jan Kiszka
2011-09-27 16:30 ` Jan Kiszka
2011-09-27 17:04 ` Richard Cochran
2011-09-27 17:25 ` Jan Kiszka
2011-09-27 17:00 ` Richard Cochran
2011-09-27 17:25 ` Jan Kiszka
2011-09-28 8:16 ` Richard Cochran
2011-09-28 8:29 ` Jan Kiszka
2011-09-27 18:02 ` Gilles Chanteperdrix
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=4E7C8EB2.1020308@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=richardcochran@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.