diff options
author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2016-03-23 11:24:18 +0100 |
---|---|---|
committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2016-03-29 07:26:43 +0200 |
commit | 6f9c3e5537ec8ab62fa95c301e1e15223d044d64 (patch) | |
tree | e939619f8a443e11042d3efc2cdf45f971c88bd0 | |
parent | score: Use constant for maximum count of CORE sema (diff) | |
download | rtems-6f9c3e5537ec8ab62fa95c301e1e15223d044d64.tar.bz2 |
bsp/motorola_powerpc: README.qemu
-rw-r--r-- | c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu b/c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu index cc23af65a1..9ccf3779a9 100644 --- a/c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu +++ b/c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu @@ -82,7 +82,12 @@ can be used with unbundled/libbsdport drivers]) I use networking with a 'tap' interface on the host machine and can then communicate with the emulated target in any -desired way. +desired way. The Ethernet address specified in the RTEMS network interface +configuration and the Qemu command line must match, otherwise uni-cast frames +are not received. It is best to use a NULL pointer in the RTEMS network +interface configuration for the Ethernet address, so that the default from Qemu +is used. Make sure that your firewall settings allow communication between +different Qemu instances and your host. On (linux) host: |