I have opened PR #44 on the GitHub meta-xilinx to address the qemu-oe-bridge-helper issue in the qemu-xilinx-helper-native recipe.
On Wed, Aug 17, 2022 at 06:35:24PM -0400, Corey Thompson wrote: > This works for me; however, now I might see the reason why > setup_net_bridge() didn't get as much love. setup_tap() is able to use > the tap number to generate a unique MAC address, but when using -netdev > bridge, tap allocation is delegated to QEMU, so runqemu can't get that > information until it's too late. Similarly, setup_slirp() uses the > hostfwd ports in its MAC pattern. Hmm, I can't think of a good source > for bridge-mode MAC generation at the moment... I have also written a patch for runqemu to get rid of that hard-coded network device in bridge mode and use the machine.conf provided one. I am sure that what I did will stir some discussion and probably invite changes. What is the best method to submit this patch to poky for review? Should I open a PR to the GitHub/Xilinx poky repo, or should I attach it with a post to [email protected], or other? I just want to be sure that it goes somewhere that will eventually make its way into the Xilinx poky stream. Thanks, Corey
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5048): https://lists.yoctoproject.org/g/meta-xilinx/message/5048 Mute This Topic: https://lists.yoctoproject.org/mt/93070424/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
