1. 25 3月, 2022 1 次提交
  2. 19 3月, 2022 2 次提交
  3. 22 1月, 2022 4 次提交
  4. 11 1月, 2022 1 次提交
  5. 01 9月, 2021 1 次提交
  6. 09 6月, 2021 1 次提交
    • T
      net: convert TFTP_TSIZE to proper Kconfig option · 2509493c
      Tero Kristo 提交于
      TFTP transfer size can be used to re-size the TFTP progress bar on
      single line based on the server reported file size. The support for
      this has been around from 2019, but it was never converted to proper
      Kconfig.
      
      While adding this new Kconfig, enable it by default for OMAP2+ and K3
      devices also.
      Signed-off-by: NTero Kristo <kristo@kernel.org>
      2509493c
  7. 01 12月, 2020 1 次提交
    • L
      Adds basic support for ProxyDHCP · c8e251f8
      Lyle Franklin 提交于
      - ProxyDHCP allows a second DHCP server to exist alongside your main
        DHCP server and supply additional BOOTP related options
      - When u-boot sends out a DHCP request, the real DHCP server will
        respond with a normal response containing the new client IP address
        while simultaneously the ProxyDHCP server will respond with a blank
        client IP address and a `bootfile` option
      - This patch adds CONFIG_SERVERIP_FROM_PROXYDHCP (default false) to
        enable this behavior and CONFIG_SERVERIP_FROM_PROXYDHCP_DELAY_MS
        (default 100) which tells u-boot to wait additional time after
        receiving the main DHCP response to give the ProxyDHCP response time
        to arrive
      - The PXE spec for ProxyDHCP is more complicated than the solution
        added here as diagramed on page 16:
        http://www.pix.net/software/pxeboot/archive/pxespec.pdf:
      
      ```
      DHCP Discover will be retried four times. The four timeouts are 4, 8, 16
      and 32 seconds respectively. If a DHCPOFFER is received without an Option
      timeouts in an attempt to receive a PXE response.
      ```
      
      - Adding a simple delay worked for my purposes but let me know if a
        more robust solution is required
      Signed-off-by: NLyle Franklin <lylejfranklin@gmail.com>
      c8e251f8
  8. 01 10月, 2020 1 次提交
  9. 05 8月, 2020 1 次提交
    • R
      net: tftp: Add client support for RFC 7440 · cc6b87ec
      Ramon Fried 提交于
      Add support for RFC 7440: "TFTP Windowsize Option".
      
      This optional feature allows the client and server
      to negotiate a window size of consecutive blocks to send as an
      alternative for replacing the single-block lockstep schema.
      
      windowsize can be defined statically during compilation by
      setting CONFIG_TFTP_WINDOWSIZE, or defined in runtime by
      setting an environment variable: "tftpwindowsize"
      If not defined, the windowsize is set to 1, meaning that it
      behaves as it was never defined.
      
      Choosing the appropriate windowsize depends on the specific
      network topology, underlying NIC.
      You should test various windowsize scenarios and see which
      best work for you.
      
      Setting a windowsize too big can actually decreases performance.
      Signed-off-by: NRamon Fried <rfried.dev@gmail.com>
      Reviewed-by: NMarek Vasut <marex@denx.de>
      cc6b87ec
  10. 29 7月, 2020 1 次提交
  11. 28 4月, 2020 1 次提交
  12. 13 2月, 2020 1 次提交
  13. 09 12月, 2019 1 次提交
    • A
      net: tftp: Fix too small block size · 16cdc2da
      Andre Przywara 提交于
      Commit b618b370 ("net: Convert CONFIG_TFTP_BLOCKSIZE to Kconfig")
      accidentally set the default *option* TFTP block size to 512 bytes, even
      though the comment in the code says that this is a terrible choice. Most
      boards didn't define the symbol before, so they got the default block size
      of 1468 bytes before, but now use 512 bytes, which is also the fallback.
      This leads to both abysmal performance and a lot of hashes printed
      on the screen (one character for every 5K), which is both annoying and
      slow over serial links.
      
      Set the default block size in Kconfig back to the value it had before.
      
      This improves TFTP performance from 2.8 MB/s to 6.9 MB/s on a Pine64.
      
      Fixes: b618b370 ("net: Convert CONFIG_TFTP_BLOCKSIZE to Kconfig")
      Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
      Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
      16cdc2da
  14. 15 6月, 2019 2 次提交
  15. 14 4月, 2018 2 次提交
  16. 28 2月, 2018 1 次提交
  17. 24 2月, 2018 1 次提交
  18. 09 2月, 2018 1 次提交
  19. 17 9月, 2016 1 次提交
  20. 28 5月, 2016 2 次提交
  21. 27 5月, 2016 1 次提交
  22. 29 10月, 2015 1 次提交
    • A
      net: TFTP: variables cleanup and addition · f5fb7346
      Albert ARIBAUD \(3ADEV\) 提交于
      TFTP source and destination port variable names are
      'tftpsrcp' and 'tftpdstp' in the code, but 'tftpsrcport'
      and 'tftpdstport' in the README file. Fix the README.
      
      Add environment variable 'tftptimeoutcountmax'. As per the
      comments about the global variable tftp_timeout_count_max,
      make sure tftptimeoutcountmax is nonnegative.
      
      Introduce configuration option CONFIG_NET_TFTP_VARS,
      which controls whether environment variables tftpblocksize,
      tftptimeout, and tftptimoueoutcountmax are read by the TFTP
      client code. CONFIG_NET_TFTP_VARS defaults to y but can be
      set to n by targets with to tight size contraints.
      
      Make bf527-ezkit set CONFIG_NET_TFTP_VARS to n to keep the
      target size below limit.
      f5fb7346
  23. 30 9月, 2015 1 次提交
  24. 09 7月, 2015 1 次提交
  25. 02 6月, 2015 1 次提交
  26. 21 5月, 2015 1 次提交
  27. 20 5月, 2015 1 次提交
  28. 25 9月, 2014 1 次提交