From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] configs: Migrate CONFIG_NR_DRAM_BANKS
Date: Fri, 17 Aug 2018 08:45:43 -0400 [thread overview]
Message-ID: <20180817124543.GH30947@bill-the-cat> (raw)
In-Reply-To: <CAHCN7xJwRKD9K-2porLLKt3=8YD66b1i0JZdQ8RV7vFcJf=8Vg@mail.gmail.com>
On Fri, Aug 17, 2018 at 07:03:04AM -0500, Adam Ford wrote:
> On Thu, Aug 16, 2018 at 8:14 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > We have the following cases:
> > - CONFIG_NR_DRAM_BANKS was defined, migrate normally
> > - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
> > CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
> > - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
> > 2), set this to 8.
> >
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
>
> What are the chances of using defaults based on architectures? The
> number of defconfig changes can go down, and those that need changes
> that differ from their standard architecture can still do it.
Well, one of the things I'm wondering about is how many places really
need / benefit from using something other than 4 or 8 and dropping the
usage of 1/2/3/6/7 and just defaulting to 8 if 64bit, else 4.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180817/5261cf49/attachment.sig>
prev parent reply other threads:[~2018-08-17 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 1:12 [U-Boot] [PATCH] configs: Migrate CONFIG_NR_DRAM_BANKS Tom Rini
2018-08-17 2:04 ` Tom Rini
2018-08-17 6:17 ` Michal Simek
2018-08-17 12:46 ` Tom Rini
2018-08-17 12:03 ` Adam Ford
2018-08-17 12:45 ` Tom Rini [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=20180817124543.GH30947@bill-the-cat \
--to=trini@konsulko.com \
--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 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.