From: "Kumar, Udit" <u-kumar1@ti.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: <trini@konsulko.com>, <nm@ti.com>, <u-boot@lists.denx.de>,
<j-humphreys@ti.com>, <marcel.ziswiler@toradex.com>,
<vigneshr@ti.com>, <b-padhi@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH] configs: j784s4_evm : Increase Dynamic memory allocation size
Date: Wed, 17 Jul 2024 09:40:11 +0530 [thread overview]
Message-ID: <ddef3081-76a2-4985-bc47-9a18bcd7ed93@ti.com> (raw)
In-Reply-To: <20240716200555.GC85916@francesco-nb>
Hi Francesco
On 7/17/2024 1:35 AM, Francesco Dolcini wrote:
> Hello,
>
> On Mon, Jul 15, 2024 at 11:13:01PM +0530, Udit Kumar wrote:
>> Increase malloc size to 32 MB to align with other J7
>> family devices.
> Is this needed for any specific reason? I am asking to understand if
> other boards using the same SOC should be updated to prevent
> $random_issue.
In our downstream version, we are seeing an issue , while using DFU to MMC
Please see
https://gist.github.com/uditkumarti/b8209f61eff3154f6eb288ba63715263#file-gistfile1-txt-L82
Since DFU is not supported yet in mainline u-boot, so I avoided to
mention that failure.
Also this change is generic, so i thought of pushing it now instead of
waiting for DFU series.
> Francesco
>
next prev parent reply other threads:[~2024-07-17 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 17:43 [PATCH] configs: j784s4_evm : Increase Dynamic memory allocation size Udit Kumar
2024-07-16 20:05 ` Francesco Dolcini
2024-07-17 4:10 ` Kumar, Udit [this message]
2024-07-17 7:33 ` Francesco Dolcini
2024-07-17 14:10 ` Nishanth Menon
2024-07-17 14:09 ` Nishanth Menon
2024-07-17 14:22 ` Francesco Dolcini
2024-07-20 17:10 ` Tom Rini
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=ddef3081-76a2-4985-bc47-9a18bcd7ed93@ti.com \
--to=u-kumar1@ti.com \
--cc=b-padhi@ti.com \
--cc=francesco@dolcini.it \
--cc=j-humphreys@ti.com \
--cc=marcel.ziswiler@toradex.com \
--cc=nm@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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.