All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] Enable PXE boot on meson-gxbb.
Date: Mon, 17 Apr 2017 15:26:03 -0700	[thread overview]
Message-ID: <87y3uyr7r8.fsf@aikidev.net> (raw)
In-Reply-To: <cc794d12-4e01-648a-e0de-fb9c4f42d0bb@suse.de>

On 2017-04-16, Andreas Färber wrote:
> 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.
...
>> 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.

Apologies, I'm not subscribed to the list and must have missed that
discussion.


> PXE has a lengthy list of fallbacks and I fail to see what is U-Boot
> specific about DHCP.

DHCP the protocol is not at all u-boot specific, sure, but the boot
method:

#define BOOTENV_DEV_DHCP(devtypeu, devtypel, instance) \
	"bootcmd_dhcp=" \
		BOOTENV_RUN_NET_USB_START \
		BOOTENV_RUN_NET_PCI_ENUM \
		"if dhcp ${scriptaddr} ${boot_script_dhcp}; then " \
			"source ${scriptaddr}; " \
		"fi;" \
		BOOTENV_EFI_RUN_DHCP \
		"\0"

I guess I was referring to "source ${scriptaddr}; " line, which is quite
u-boot specific. I didn't realize that "DHCP" also had support for EFI
loaded over the network.

It seems unforunate that the EFI network boot is only a fallback to
loading a boot script over the network, as boot scripts and EFI boot
seem to me like two unrelated features.

When loading from MMC, I think the order goes something like EFI,
extlinux, u-boot boot scripts. With the current implementation, it
appears a similar ordering is not possible with general cases of network
boot. Which kind of reduces the consistancy for config_distro_bootcmd
for different boot methods. Hrm.

That said, I'm fine to resubmit the patch to put PXE boot after DHCP
boot...


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170417/57366bd5/attachment.sig>

  reply	other threads:[~2017-04-17 22:26 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
2017-04-17 22:26     ` Vagrant Cascadian [this message]
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=87y3uyr7r8.fsf@aikidev.net \
    --to=vagrant@debian.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.