[rtems commit] bsp/motorola_powerpc: README.qemu

[Sebastian Huber]

Module:    rtems
Branch:    master
Commit:    6f9c3e5537ec8ab62fa95c301e1e15223d044d64
Changeset: http://git.rtems.org/rtems/commit/?id=6f9c3e5537ec8ab62fa95c301e1e15223d044d64

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Wed Mar 23 11:24:18 2016 +0100

bsp/motorola_powerpc: README.qemu

---

 c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu b/c/src/lib/libbsp/powerpc/motorola_powerpc/README.qemu
index cc23af6..9ccf377 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: