From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 2/2] ARM: dts: imx6q: add Novena board
Date: Mon, 14 Dec 2015 15:41:13 +0100 [thread overview]
Message-ID: <201512141541.14107.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5DXnMfrdsUfptbErNdULAYCRg0KuPELYWYVxx5HtezHMw@mail.gmail.com>
On Monday, December 14, 2015 at 03:17:04 PM, Fabio Estevam wrote:
> Hi Marek,
Hi!
> On Mon, Dec 14, 2015 at 12:12 PM, Marek Vasut <marex@denx.de> wrote:
> > So it was correct from the get-go ? Uh ...
> >
> > Thanks for clarification, I will remember this :)
>
> If you prefer, you can even remove this memory node entry from the dts
> and let the bootloader pass the correct amount of RAM to the kernel.
>
> This is useful when a board has variants in RAM size.
Well that's a good idea, but some sort of sane default should be present
anyway, right ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-12-14 14:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 14:47 [PATCH V2 1/2] devicetree: bindings: Add vendor prefix for Kosagi Marek Vasut
2015-11-28 14:47 ` [PATCH V3 2/2] ARM: dts: imx6q: add Novena board Marek Vasut
2015-11-30 10:19 ` Lucas Stach
2015-11-30 12:21 ` Marek Vasut
2015-11-30 10:57 ` Fabio Estevam
2015-12-02 7:53 ` Shawn Guo
2015-12-02 15:41 ` Marek Vasut
2015-12-11 11:07 ` Shawn Guo
2015-12-12 3:25 ` Marek Vasut
2015-12-12 3:27 ` [PATCH V4 " Marek Vasut
2015-12-14 1:38 ` Shawn Guo
2015-12-14 3:56 ` Marek Vasut
2015-12-14 13:53 ` Sergei Shtylyov
2015-12-14 14:12 ` Marek Vasut
2015-12-14 14:17 ` Fabio Estevam
2015-12-14 14:41 ` Marek Vasut [this message]
2015-12-14 14:45 ` Fabio Estevam
2015-12-14 14:47 ` Marek Vasut
2015-12-15 3:33 ` Marek Vasut
2015-12-14 1:36 ` [PATCH V2 1/2] devicetree: bindings: Add vendor prefix for Kosagi Shawn Guo
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=201512141541.14107.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.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).