From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: tegra: align carveout size
Date: Wed, 1 Aug 2018 20:06:40 -0400 [thread overview]
Message-ID: <20180802000640.GA32145@bill-the-cat> (raw)
In-Reply-To: <17ee589786e44de8b871cb9d9e436395@HQMAIL101.nvidia.com>
On Wed, Aug 01, 2018 at 11:52:36PM +0000, Tom Warren wrote:
> I can add this to my PR list (but probably won't get one out until tomorrow morning), or:
>
> Acked-by: Tom Warren <twarren@nvidia.com>
>
> If that'll get it in sooner.
Applied, thanks!
>
> Tom
>
> -----Original Message-----
> From: Tom Rini <trini@konsulko.com>
> Sent: Wednesday, August 1, 2018 4:47 PM
> To: Stephen Warren <swarren@wwwdotorg.org>
> Cc: Tom Warren <TWarren@nvidia.com>; u-boot at lists.denx.de; Simon Glass <sjg@chromium.org>; Stephen Warren <swarren@nvidia.com>; Mark Kettenis <kettenis@openbsd.org>; Alexander Graf <agraf@suse.de>
> Subject: Re: [U-Boot] [PATCH] ARM: tegra: align carveout size
>
> On Wed, Aug 01, 2018 at 05:26:10PM -0600, Stephen Warren wrote:
> > On 07/31/2018 12:38 PM, Stephen Warren wrote:
> > >From: Stephen Warren <swarren@nvidia.com>
> > >
> > >Align the size of the carveout region to 2M. This ensures that the
> > >size can be accurately represented by an LPAE page table that uses sections.
> > >
> > >This solves a bug (hang at boot time soon after printing the DRAM
> > >size) that only shows up when the following two commits are merged together:
> > >d32e86bde8a3 ARM: HYP/non-sec: enable ARMV7_LPAE if HYP mode is
> > >supported
> > >6e584e633d10 ARM: tegra: avoid using secure carveout RAM
> > >
> > >Cc: Mark Kettenis <kettenis@openbsd.org>
> > >Cc: Alexander Graf <agraf@suse.de>
> > >Signed-off-by: Stephen Warren <swarren@nvidia.com>
> > >---
> > >This should be applied quickly since it fixes a regression that
> > >causes all boots to fail, which in turn causes test/py to reset and
> > >"reflash" the target board for each test, which causes the test to take eons.
> >
> > Could we apply this please? My Jenkins system will love you because of
> > it:-)
>
> I'm looking for one more person to Ack this, thanks!
>
> --
> Tom
> -----------------------------------------------------------------------------------
> This email message is for the sole use of the intended recipient(s) and may contain
> confidential information. Any unauthorized review, use, disclosure or distribution
> is prohibited. If you are not the intended recipient, please contact the sender by
> reply email and destroy all copies of the original message.
> -----------------------------------------------------------------------------------
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180801/919a6114/attachment.sig>
next prev parent reply other threads:[~2018-08-02 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 18:38 [U-Boot] [PATCH] ARM: tegra: align carveout size Stephen Warren
2018-08-01 23:26 ` Stephen Warren
2018-08-01 23:46 ` Tom Rini
2018-08-01 23:52 ` Tom Warren
2018-08-02 0:06 ` Tom Rini [this message]
2018-08-02 17:03 ` Stephen Warren
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=20180802000640.GA32145@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox