All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: "Sjöberg Andreas" <andreas.sjoberg2@saabgroup.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: U-boot patches
Date: Wed, 8 Sep 2021 13:40:17 -0400	[thread overview]
Message-ID: <20210908174017.GG12964@bill-the-cat> (raw)
In-Reply-To: <32b052578281473d9061ca8c74edea80@saabgroup.com>

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

On Wed, Sep 08, 2021 at 07:35:50AM +0000, Sjöberg Andreas wrote:

> Hi,
> We have two patch files for u-boot:
> 
> Bootelf_async_abort_fix.patch:
> Booting a .elf files sometimes triggers an asynchronous abort error disabling the icache and dcahe before boot turned out to prevent this and this patch adds disabling of these caches as a part of the bootelf command.
> 
> Tftp_next_ack_update:
> When running tftp without any additional options (i.e no oack gets sent) the client does not change the expected block number of the next package from 0 to tftp_windowsize preventing acknowledgement of received data. There also was no prober mreset for this counter that instead only reset upon receiveing an oack. This patch increments  the value of next_ack when receiving a data packet instead of an oack and also ensures that sending a new read request or write request resets the counter to 0, indicating that the next packet should be an oack.
> 
> /Andreas Sjöberg

Please see http://www.denx.de/wiki/U-Boot/Patches and re-post each of
these patches with a proper commit message, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2021-09-08 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  7:35 U-boot patches Sjöberg Andreas
2021-09-08 17:40 ` Tom Rini [this message]

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=20210908174017.GG12964@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=andreas.sjoberg2@saabgroup.com \
    --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.