From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH 2/2] configs/olimex_a20_olinuxino_lime*: configure eth0 with DHCP
Date: Mon, 10 Apr 2023 19:33:27 +0200 [thread overview]
Message-ID: <20230410173327.GG2819@scaer> (raw)
In-Reply-To: <20230405081842.244610-2-francois.perrad@gadz.org>
François, All,
On 2023-04-05 10:18 +0200, Francois Perrad spake thusly:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> configs/olimex_a20_olinuxino_lime2_defconfig | 1 +
> configs/olimex_a20_olinuxino_lime_defconfig | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/configs/olimex_a20_olinuxino_lime2_defconfig b/configs/olimex_a20_olinuxino_lime2_defconfig
> index a8260a7ea..a38f3a1c5 100644
> --- a/configs/olimex_a20_olinuxino_lime2_defconfig
> +++ b/configs/olimex_a20_olinuxino_lime2_defconfig
> @@ -15,6 +15,7 @@ BR2_TARGET_GENERIC_HOSTNAME="a20-olinuxino"
> BR2_TARGET_GENERIC_ISSUE="Welcome to OLinuXino!"
> BR2_TARGET_GENERIC_GETTY=y
> BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
> +BR2_SYSTEM_DHCP="eth0"
> BR2_ROOTFS_OVERLAY="board/olimex/a20_olinuxino/rootfs_overlay"
> BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
> BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/olimex/a20_olinuxino/genimage.cfg"
> diff --git a/configs/olimex_a20_olinuxino_lime_defconfig b/configs/olimex_a20_olinuxino_lime_defconfig
> index 65a78f535..74b6a764c 100644
> --- a/configs/olimex_a20_olinuxino_lime_defconfig
> +++ b/configs/olimex_a20_olinuxino_lime_defconfig
> @@ -15,6 +15,7 @@ BR2_TARGET_GENERIC_HOSTNAME="a20-olinuxino"
> BR2_TARGET_GENERIC_ISSUE="Welcome to OLinuXino!"
> BR2_TARGET_GENERIC_GETTY=y
> BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
> +BR2_SYSTEM_DHCP="eth0"
> BR2_ROOTFS_OVERLAY="board/olimex/a20_olinuxino/rootfs_overlay"
> BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
> BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/olimex/a20_olinuxino/genimage.cfg"
> --
> 2.37.2
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-04-10 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 8:18 [Buildroot] [PATCH 1/2] configs/olimex_a20_olinuxino_lime*: bump Linux and U-Boot Francois Perrad
2023-04-05 8:18 ` [Buildroot] [PATCH 2/2] configs/olimex_a20_olinuxino_lime*: configure eth0 with DHCP Francois Perrad
2023-04-10 17:33 ` Yann E. MORIN [this message]
2023-04-22 21:06 ` Peter Korsgaard
2023-04-10 17:33 ` [Buildroot] [PATCH 1/2] configs/olimex_a20_olinuxino_lime*: bump Linux and U-Boot Yann E. MORIN
2023-04-22 21:06 ` Peter Korsgaard
2023-04-22 21:07 ` Peter Korsgaard
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=20230410173327.GG2819@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
--cc=fperrad@gmail.com \
/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