1. 03 7月, 2018 3 次提交
    • A
      net: Add option to prefer bootp/dhcp serverip · bdce340c
      Alexander Graf 提交于
      Currently we can choose between 2 different types of behavior for the
      serverip variable:
      
        1) Always overwrite it with the DHCP server IP address (default)
        2) Ignore what the DHCP server says (CONFIG_BOOTP_SERVERIP)
      
      This patch adds a 3rd option:
      
        3) Use serverip from DHCP if no serverip is given
           (CONFIG_BOOTP_PREFER_SERVERIP)
      
      With this new option, we can have the default case that a boot file gets
      loaded from the DHCP provided TFTP server work while allowing users to
      specify their own serverip variable to explicitly use a different tftp
      server.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
      bdce340c
    • A
      net: Prefer command line arguments · 449312c1
      Alexander Graf 提交于
      We can call commands like dhcp and bootp without arguments or with
      explicit command line arguments that really should tell the code where
      to look for files instead.
      
      Unfortunately, the current code simply overwrites command line arguments
      in the dhcp case with dhcp values.
      
      This patch allows the code to preserve the command line values if they
      were set on the command line. That way the semantics are slightly more
      intuitive.
      
      The reason this patch does that by introducing a new variable is that we
      can not rely on net_boot_file_name[0] being unset, as today it's
      completely legal to call "dhcp" and afterwards run "tftp" and expect the
      latter to repeat the same query as before. I would prefer not to break
      that behavior in case anyone relies on it.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
      449312c1
    • L
      net: Add new wol command - Wake on LAN · d8970dae
      Lothar Felten 提交于
      Add a new command 'wol': Wait for an incoming Wake-on-LAN packet or
      time out if no WoL packed is received.
      If the WoL packet contains a password, it is saved in the environment
      variable 'wolpassword' using the etherwake format (dot or colon
      separated decimals).
      
      Intended use case: a networked device should boot an alternate image.
      It's attached to a network on a client site, modifying the DHCP server
      configuration or setup of a tftp server is not allowed.
      After power on the device waits a few seconds for a WoL packet. If a
      packet is received, the device boots the alternate image. Otherwise
      it boots the default image.
      
      This method is a simple way to interact with a system via network even
      if only the MAC address is known. Tools to send WoL packets are
      available on all common platforms.
      
      Some Ethernet drivers seem to pad the incoming packet. The additional
      padding bytes might be recognized as Wake-on-LAN password bytes.
      
      By default enabled in pengwyn_defconfig.
      Signed-off-by: NLothar Felten <lothar.felten@gmail.com>
      Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
      d8970dae
  2. 02 7月, 2018 1 次提交
  3. 24 6月, 2018 1 次提交
  4. 19 6月, 2018 6 次提交
  5. 14 6月, 2018 2 次提交
  6. 13 6月, 2018 1 次提交
  7. 08 6月, 2018 2 次提交
  8. 06 6月, 2018 1 次提交
    • M
      menu: fix timeout duration · 86fbad24
      Masahiro Yamada 提交于
      For distro-boot, the TIMEOUT directive in the boot script specifies
      how long to pause in units of 1/10 sec. [1]
      
      Commit 8594753b ("menu: only timeout when menu is displayed")
      corrected this by simply dividing the timeout value by 10 in
      menu_interactive_choice().
      
      I see two problems:
      
       - For example, "TIMEOUT 5" should wait for 0.5 sec, but the current
         implementation cannot handle the granularity of 1/10 sec.
         In fact, it never breaks because "m->timeout / 10" is zero,
         which means no timeout.
      
       - The menu API is used not only by cmd/pxe.c but also by
         common/autoboot.c .  For the latter case, the unit of the
         timeout value is _second_ because its default is associated
         with CONFIG_BOOTDELAY.
      
      To fix the first issue, use DIV_ROUND_UP() so that the timeout value
      is rounded up to the closest integer.
      
      For the second issue, move the division to the boundary between
      cmd/pxe.c and common/menu.c .  This is a more desirable place because
      the comment of struct pxe_menu says:
      
       * timeout - time in tenths of a second to wait for a user key-press before
       *           booting the default label.
      
      Then, the comment of menu_create() says:
      
       * timeout - A delay in seconds to wait for user input. If 0, timeout is
       * disabled, and the default choice will be returned unless prompt is 1.
      
      [1] https://www.syslinux.org/wiki/index.php?title=SYSLINUX#TIMEOUT_timeoutSigned-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      86fbad24
  9. 03 6月, 2018 3 次提交
  10. 01 6月, 2018 2 次提交
  11. 30 5月, 2018 4 次提交
  12. 29 5月, 2018 1 次提交
    • R
      efi_loader: Enable RISC-V support · 6836adbe
      Rick Chen 提交于
      We have almost all pieces needed to support RISC-V UEFI binaries in place already.
      The only missing piece are ELF relocations for runtime code and
      data.
      
      This patch adds respective support in the linker script and the runtime
      relocation code. It also allows users to enable the EFI_LOADER configuration
      switch on RISC-V platforms.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      6836adbe
  13. 26 5月, 2018 12 次提交
  14. 25 5月, 2018 1 次提交