All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de, "Pali Rohár" <pali@kernel.org>,
	"Simon Glass" <sjg@chromium.org>,
	"Francesco Dolcini" <francesco@dolcini.it>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v2 0/2] common/memsize.c: Fix get_ram_size() when cache is enabled
Date: Thu, 22 Jun 2023 10:00:44 -0400	[thread overview]
Message-ID: <168744241829.1369808.5834074653724684657.b4-ty@konsulko.com> (raw)
In-Reply-To: <20230530133327.178278-1-francesco@dolcini.it>

On Tue, 30 May 2023 15:33:25 +0200, Francesco Dolcini wrote:

> From: Francesco Dolcini <francesco.dolcini@toradex.com>
> 
> Ensure that every write is flushed to memory and afterward reads are
> from memory.
> Since the algorithm rely on the fact that accessing to not existent
> memory lead to write at addr / 2 without this modification accesses
> to aliased (not physically present) addresses are cached and
> wrong size is returned.
> 
> [...]

Applied to u-boot/next, thanks!

-- 
Tom


      parent reply	other threads:[~2023-06-22 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 13:33 [PATCH v2 0/2] common/memsize.c: Fix get_ram_size() when cache is enabled Francesco Dolcini
2023-05-30 13:33 ` [PATCH v2 1/2] sandbox: Add a dummy dcache_status() function Francesco Dolcini
2023-06-01  3:28   ` Simon Glass
2023-05-30 13:33 ` [PATCH v2 2/2] common/memsize.c: Fix get_ram_size() when cache is enabled Francesco Dolcini
2023-05-30 13:42   ` Michael Nazzareno Trimarchi
2023-05-30 13:48     ` Francesco Dolcini
2023-05-30 14:04       ` Michael Nazzareno Trimarchi
2023-06-22 14:00 ` 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=168744241829.1369808.5834074653724684657.b4-ty@konsulko.com \
    --to=trini@konsulko.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=francesco@dolcini.it \
    --cc=pali@kernel.org \
    --cc=sjg@chromium.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.