From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] Enable PXE boot on meson-gxbb.
Date: Mon, 17 Apr 2017 00:04:40 +0200 [thread overview]
Message-ID: <cc794d12-4e01-648a-e0de-fb9c4f42d0bb@suse.de> (raw)
In-Reply-To: <20170416220133.31043-3-vagrant@debian.org>
Am 17.04.2017 um 00:01 schrieb Vagrant Cascadian:
> Enable distro_bootcmd PXE functions on meson-gxbb systems.
>
> While DHCP boot is already supported, the format is fairly u-boot
> specific, while PXE boot supports the widely used syslinux style boot
> configuration format.
>
> Signed-off-by: Vagrant Cascadian <vagrant@debian.org>
> ---
>
> include/configs/meson-gxbb-common.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/configs/meson-gxbb-common.h b/include/configs/meson-gxbb-common.h
> index c3229ea2cf..0339feaed9 100644
> --- a/include/configs/meson-gxbb-common.h
> +++ b/include/configs/meson-gxbb-common.h
> @@ -41,6 +41,7 @@
> #define BOOT_TARGET_DEVICES(func) \
> func(MMC, mmc, 0) \
> func(MMC, mmc, 1) \
> + func(PXE, pxe, na) \
> func(DHCP, dhcp, na)
>
> #include <config_distro_bootcmd.h>
This should go after DHCP as discussed a while ago.
PXE has a lengthy list of fallbacks and I fail to see what is U-Boot
specific about DHCP.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-04-16 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 22:01 [U-Boot] [PATCH 0/2] Enable MMC and PXE boot on meson-gxbb systems Vagrant Cascadian
2017-04-16 22:01 ` [U-Boot] [PATCH 1/2] Enable MMC boot on meson-gxbb Vagrant Cascadian
2017-04-16 22:02 ` Andreas Färber
2017-04-16 22:01 ` [U-Boot] [PATCH 2/2] Enable PXE " Vagrant Cascadian
2017-04-16 22:04 ` Andreas Färber [this message]
2017-04-17 22:26 ` Vagrant Cascadian
2017-04-17 22:42 ` Andreas Färber
2017-04-17 23:05 ` Vagrant Cascadian
2017-05-01 16:56 ` Andreas Färber
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=cc794d12-4e01-648a-e0de-fb9c4f42d0bb@suse.de \
--to=afaerber@suse.de \
--cc=u-boot@lists.denx.de \
/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