From: Caleb Connolly <caleb.connolly@linaro.org>
To: Tom Rini <trini@konsulko.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Sumit Garg <sumit.garg@linaro.org>, Sam Day <me@samcday.com>
Cc: u-boot-qcom@groups.io, u-boot@lists.denx.de
Subject: Re: [PATCH] mach-snapdragon: do carveouts for qcs404 only
Date: Mon, 13 May 2024 10:27:16 +0200 [thread overview]
Message-ID: <171558883607.3055487.4753666162213612810.b4-ty@linaro.org> (raw)
In-Reply-To: <20240507-qcs404-carveout-only-v1-1-93d06884b862@samcday.com>
On Tue, 07 May 2024 18:41:23 +0000, Sam Day wrote:
> The newly introduced carve_out_reserved_memory causes issues when
> U-Boot is chained from the lk2nd bootloader. lk2nd provides a
> simple-framebuffer device and marks the framebuffer region as no-map in
> the supplied /reserved-memory. Consequently, the simple_video driver
> triggers a page fault when it tries to write to this region.
>
> As per Caleb's advice, this simple patch only does the carveouts for the
> qcs404 SoC for which it was originally designed. The intent is to do the
> carveouts for more Qualcomm SoCs in future.
>
> [...]
Applied, thanks!
[1/1] mach-snapdragon: do carveouts for qcs404 only
https://source.denx.de/u-boot/custodians/u-boot-snapdragon/-/commit/a8910537bb6c
Best regards,
--
Caleb Connolly <caleb.connolly@linaro.org>
prev parent reply other threads:[~2024-05-13 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 18:41 [PATCH] mach-snapdragon: do carveouts for qcs404 only Sam Day
2024-05-08 9:14 ` Sumit Garg
2024-05-08 11:40 ` Sam Day
2024-05-08 12:39 ` Caleb Connolly
2024-05-08 14:48 ` Sumit Garg
2024-05-09 12:59 ` Sam Day
2024-05-10 11:23 ` Caleb Connolly
2024-05-13 8:27 ` Caleb Connolly [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=171558883607.3055487.4753666162213612810.b4-ty@linaro.org \
--to=caleb.connolly@linaro.org \
--cc=me@samcday.com \
--cc=neil.armstrong@linaro.org \
--cc=sumit.garg@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot-qcom@groups.io \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).