On Tue, Sep 27, 2011 at 07:25:07PM +0200, Jan Kiszka wrote:
It manages buffers for you, provides NIC drivers and interfaces to
either build the higher protocol layers in the kernel or in user space.
That's the mission, but I would not exclude that there is room for
improvements (lacking safe
On 2011-09-28 10:16, Richard Cochran wrote:
On Tue, Sep 27, 2011 at 07:25:07PM +0200, Jan Kiszka wrote:
It manages buffers for you, provides NIC drivers and interfaces to
either build the higher protocol layers in the kernel or in user space.
That's the mission, but I would not exclude that
On 2011-09-26 13:41, Richard Cochran wrote:
On Fri, Sep 23, 2011 at 03:50:42PM +0200, Jan Kiszka wrote:
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
On Tue, Sep 27, 2011 at 10:26:51AM +0200, Jan Kiszka wrote:
On 2011-09-26 13:41, Richard Cochran wrote:
- Simple to implement new drivers.
Compare my rtpacket.h with the rtnet driver headers to see what I
mean. Or, read rtnet/Documentation/README.drvporting and ask
yourself, is
On 2011-09-27 14:01, Richard Cochran wrote:
Again, every MAC driver needs to be tastefully and wisely adapted. I
don't necessarily need to avoid coalescing. The goal (for me) is *not*
to provide deterministic Ethernet performance. Instead the RT packets
should just be delivered ASAP.
This is
On Tue, Sep 27, 2011 at 02:20:43PM +0200, Jan Kiszka wrote:
On 2011-09-27 14:01, Richard Cochran wrote:
Again, every MAC driver needs to be tastefully and wisely adapted. I
don't necessarily need to avoid coalescing. The goal (for me) is *not*
to provide deterministic Ethernet performance.
On 2011-09-27 17:10, Richard Cochran wrote:
On Tue, Sep 27, 2011 at 02:20:43PM +0200, Jan Kiszka wrote:
On 2011-09-27 14:01, Richard Cochran wrote:
Again, every MAC driver needs to be tastefully and wisely adapted. I
don't necessarily need to avoid coalescing. The goal (for me) is *not*
to
On Tue, Sep 27, 2011 at 05:16:09PM +0200, Jan Kiszka wrote:
On 2011-09-27 17:10, Richard Cochran wrote:
On Tue, Sep 27, 2011 at 02:20:43PM +0200, Jan Kiszka wrote:
On 2011-09-27 14:01, Richard Cochran wrote:
Again, every MAC driver needs to be tastefully and wisely adapted. I
don't
On 2011-09-27 18:05, Richard Cochran wrote:
On Tue, Sep 27, 2011 at 05:16:09PM +0200, Jan Kiszka wrote:
On 2011-09-27 17:10, Richard Cochran wrote:
On Tue, Sep 27, 2011 at 02:20:43PM +0200, Jan Kiszka wrote:
On 2011-09-27 14:01, Richard Cochran wrote:
Again, every MAC driver needs to be
On 2011-09-27 18:26, Jan Kiszka wrote:
I was simply hoping to collect some new ideas how to address the driver
maintenance issue in a better way but without dropping key features
needed for RT networking. Something like let's add generic RT channels
to Linux upstream drivers and then only
On Tue, Sep 27, 2011 at 06:30:00PM +0200, Jan Kiszka wrote:
On 2011-09-27 18:26, Jan Kiszka wrote:
I was simply hoping to collect some new ideas how to address the driver
maintenance issue in a better way but without dropping key features
needed for RT networking. Something like let's add
On Tue, Sep 27, 2011 at 06:26:44PM +0200, Jan Kiszka wrote:
On 2011-09-27 18:05, Richard Cochran wrote:
That's a common misunderstanding: RTnet is a networking stack with many
_optional_ components (like RTmac, RTcfg etc.). I would bet that it's
more frequently used today in minimal setups,
On 2011-09-27 19:00, Richard Cochran wrote:
On Tue, Sep 27, 2011 at 06:26:44PM +0200, Jan Kiszka wrote:
On 2011-09-27 18:05, Richard Cochran wrote:
That's a common misunderstanding: RTnet is a networking stack with many
_optional_ components (like RTmac, RTcfg etc.). I would bet that it's
On 2011-09-27 19:04, Richard Cochran wrote:
On Tue, Sep 27, 2011 at 06:30:00PM +0200, Jan Kiszka wrote:
On 2011-09-27 18:26, Jan Kiszka wrote:
I was simply hoping to collect some new ideas how to address the driver
maintenance issue in a better way but without dropping key features
needed for
On 09/27/2011 07:00 PM, Richard Cochran wrote:
On Tue, Sep 27, 2011 at 06:26:44PM +0200, Jan Kiszka wrote:
On 2011-09-27 18:05, Richard Cochran wrote:
That's a common misunderstanding: RTnet is a networking stack with many
_optional_ components (like RTmac, RTcfg etc.). I would bet that it's
On Fri, Sep 23, 2011 at 03:50:42PM +0200, Jan Kiszka wrote:
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
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
PS Applies to Xenomai 2.5.6.
___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core
On Friday 23 September 2011 13:02:19 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
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
20 matches
Mail list logo
