I'm glad to hear this. The path of least resistance would be to merge the driver into the pc386 BSP on rtems.git. That bsp tree is currently undergoing a lot of activity, but once you get your driver merged I would imagine it is not too hard to maintain. It would also be of interest to get instructions for using RTEMS-pc386 on KVM added to the RTEMS wiki.
By merging the driver into RTEMS it will be more easily shared and can be community-maintained especially if we can eventually get the KVM version included in our planned continuous integration efforts. Gedare On Tue, Mar 8, 2016 at 5:43 AM, Jinhyun <jinh...@konkuk.ac.kr> wrote: > Hi, > I am a graduate student of System Software Lab at Konkuk University > (http://sslab.konkuk.ac.kr). > We are implementing a virtio front-end network driver for RTEMS and have > published some preliminary results in ACM SIGBED Review > (http://sigbed.seas. > upenn.edu/archives/2016-01/EWiLi15_5.pdf). > The current version of our implementation runs quite stably with RTEMS-pc386 > over KVM hypervisor (linux 3.18.0). > Now we are trying to make it work over VirtualBox. > > If the RTEMS community is interested in our work, we’d like to open the > source codes and contribute to RTEMS. However, currently, we are not sure > whether our virtio driver is better to be incorporated in an RTEMS > source branch or to be managed separately through our own GitHub for > example. Please give your advice. > > with best regards, > Jin-Hyun > > > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel