Hello Pavel,
On 30/05/16 15:57, Pavel Pisa wrote:
Hello Jin-Hyun and Sebastian,
On Monday 30 of May 2016 15:06:40 Sebastian Huber wrote:
>Wouldn't it make sense to use the libbsd for this network interface driver?
my feeling is that from long run perspective is libBSD.
But I think that virtio netwok included in basic RTEMS stack is very
important which is based on assumption that there are more people
who use and are familiar with RTEMS integrated stack than who
started to use libBSD.
So I personally like idea to include this option to the standard sources.
I would like a little more if x86 specific part of virtio ends
in c/src/lib/libbsp/i386/pc386/virtio, but common part which can
be reused for other architectures and network driver specific part
is placed in rtems/c/src/lib/libbsp/shared and rtems/c/src/libchip/network.
It would worth to add x86 virtio to libBSD and even to lwIP
to have option to test all these stacks under quite spread KVM
based virtualization/test environment.
But generally, I would like if the code can be accepted to mainline.
the x86 architecture is not really interesting for me. So, I am not
against a mainline integration. However, I think we reached a dead end
with the pc386 BSP. The RTEMS driver infrastructure is not capable
enough to deal with a plug-and-play architecture like x86.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
