From: Tony Lindgren <tony@atomide.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: "Matwey V. Kornilov" <matwey@sai.msu.ru>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"open list:OMAP DEVICE TREE SUPPORT" <linux-omap@vger.kernel.org>,
"open list:OMAP DEVICE TREE SUPPORT" <devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm: dts: am335x-boneblack-common: fix memory size
Date: Mon, 13 Jan 2020 09:50:36 -0800 [thread overview]
Message-ID: <20200113175036.GL5885@atomide.com> (raw)
In-Reply-To: <CAOCHtYhKUyUwunnWDT1CuRTpzS78d7xKq3qB3Phys7RgUZnM3w@mail.gmail.com>
* Robert Nelson <robertcnelson@gmail.com> [200107 18:33]:
> On Mon, Jan 6, 2020 at 3:05 PM Tony Lindgren <tony@atomide.com> wrote:
> >
> > * Matwey V. Kornilov <matwey@sai.msu.ru> [200106 20:48]:
> > > пн, 6 янв. 2020 г. в 23:44, Robert Nelson <robertcnelson@gmail.com>:
> > > >
> > > > On Mon, Jan 6, 2020 at 7:10 AM Matwey V. Kornilov <matwey@sai.msu.ru> wrote:
> > > > >
> > > > > BeagleBone Black series is equipped with 512MB RAM
> > > > > whereas only 256MB is included from am335x-bone-common.dtsi
> > > >
> > > > FYI: While all versions from the factory are 512MB, some 3rd parties
> > > > offered 1GB reballing upgrades..
> >
> > So what's the conclusion, is it safe to bump the default size to
> > 512MB then?
> >
> > The custom ones could use their own dts file if bootloader is not
> > setting the RAM.
>
> Yeah this is safe for factory devices. Classic u-boot will update
> these for modified boards.
OK applying into fixes thanks.
Tony
prev parent reply other threads:[~2020-01-13 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 13:09 [PATCH] arm: dts: am335x-boneblack-common: fix memory size Matwey V. Kornilov
2020-01-06 20:43 ` Robert Nelson
2020-01-06 20:47 ` Matwey V. Kornilov
2020-01-06 21:05 ` Tony Lindgren
2020-01-07 18:32 ` Robert Nelson
2020-01-13 17:50 ` Tony Lindgren [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=20200113175036.GL5885@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matwey@sai.msu.ru \
--cc=robertcnelson@gmail.com \
--cc=robh+dt@kernel.org \
/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 NNTP newsgroup(s).