Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH] configs/qemu_or1k_defconfig: enable ethernet
Date: Sat, 12 Aug 2023 17:11:15 +0200	[thread overview]
Message-ID: <ZNehEzTstrXcE4bf@waldemar-brodkorb.de> (raw)

The issue seems to be fixed. I checked qemu and linux git repositories
but can not find any information when this is starting to work.

System gets successfully an IP, no further testing was done.
Tested with Qemu 8.0.3 and Linux 6.1.x.

Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
 board/qemu/or1k/readme.txt  | 2 --
 configs/qemu_or1k_defconfig | 3 +++
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/board/qemu/or1k/readme.txt b/board/qemu/or1k/readme.txt
index 2ea797440a..ed0359a0f5 100644
--- a/board/qemu/or1k/readme.txt
+++ b/board/qemu/or1k/readme.txt
@@ -3,5 +3,3 @@ Run the emulation with:
  qemu-system-or1k -kernel output/images/vmlinux -nographic # qemu_or1k_defconfig
 
 The login prompt will appear in the terminal that started Qemu.
-
-Ethernet support is not working, yet.
diff --git a/configs/qemu_or1k_defconfig b/configs/qemu_or1k_defconfig
index 166e5ea5ca..37b980a9bd 100644
--- a/configs/qemu_or1k_defconfig
+++ b/configs/qemu_or1k_defconfig
@@ -1,6 +1,9 @@
 # Architecture
 BR2_or1k=y
 
+# System
+BR2_SYSTEM_DHCP="eth0"
+
 # Filesystem
 # BR2_TARGET_ROOTFS_TAR is not set
 BR2_TARGET_ROOTFS_INITRAMFS=y
-- 
2.39.2

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-08-12 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12 15:11 Waldemar Brodkorb [this message]
2023-08-12 19:55 ` [Buildroot] [PATCH] configs/qemu_or1k_defconfig: enable ethernet Thomas Petazzoni via buildroot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZNehEzTstrXcE4bf@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=buildroot@buildroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox