From: Nishanth Menon <nm@ti.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: "Kumar, Udit" <u-kumar1@ti.com>, <trini@konsulko.com>,
<u-boot@lists.denx.de>, <j-humphreys@ti.com>,
<marcel.ziswiler@toradex.com>, <vigneshr@ti.com>,
<b-padhi@ti.com>
Subject: Re: [PATCH] configs: j784s4_evm : Increase Dynamic memory allocation size
Date: Wed, 17 Jul 2024 09:10:19 -0500 [thread overview]
Message-ID: <20240717141019.xy2rjdnlukh542d6@eternity> (raw)
In-Reply-To: <20240717073342.GA3312@francesco-nb>
On 09:33-20240717, Francesco Dolcini wrote:
> Hello,
>
> On Wed, Jul 17, 2024 at 09:40:11AM +0530, Kumar, Udit wrote:
> > On 7/17/2024 1:35 AM, Francesco Dolcini wrote:
> > > 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.
> > 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.
>
> Thanks for the update, on our board DFU works fine on our j784s4 based
> board (UUU or UMS are not working, but this is off topic for this
> conversation ;-)
I still think your comment is valid - commit message does need to
explain something like "make space for future standard features such as
DFU etc.."
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2024-07-17 14: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
2024-07-17 7:33 ` Francesco Dolcini
2024-07-17 14:10 ` Nishanth Menon [this message]
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=20240717141019.xy2rjdnlukh542d6@eternity \
--to=nm@ti.com \
--cc=b-padhi@ti.com \
--cc=francesco@dolcini.it \
--cc=j-humphreys@ti.com \
--cc=marcel.ziswiler@toradex.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox