On 30/05/2016 23: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.
It would be nice to also see in l
Hello,
I updated the RTEMS 4.12 tool chain to use the
* Binutils 2.26,
* the Newlib 2.4.0.20160527 snapshot, and
* the GCC 6-20160526 release branch snapshot.
The non-FSF based tool chains (or1k and epiphany) are now probably out
of sync.
All users of the RTEMS master branch must update thei
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
import
Wouldn't it make sense to use the libbsd for this network interface driver?
On 30/05/16 13:08, Jinhyun wrote:
Hi,
This is resubmitting of the virtio network driver.
We got delayed again to write ifdef'ed version of the driver.
We ifdef'ed RTEMS specific things of sources by RTEMS_VIRTIO_NET, an
Hi all,
I have ported the code from the present FreeBSD.
Link : https://github.com/spark1729/rtems-libbsd/commits/rpi_sd_card
Kindly review the same and suggest changes.
The commits are a bit unstructured, the second last one being a huge one. I
will be breaking it down into smaller and logical
