From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] rk3288: config change for enable dram capacity auto-detect.
Date: Thu, 22 Sep 2016 10:10:28 +0800 [thread overview]
Message-ID: <57E33D94.9090001@rock-chips.com> (raw)
In-Reply-To: <CABCGj3aF=9jVhOsNMSeTja8ErHZrTgUy_frcr=myhFKZ3X8Vsg@mail.gmail.com>
Hi Sandy,
On 09/21/2016 07:53 PM, Sandy Patterson wrote:
>
> On Tue, Sep 20, 2016 at 11:00 PM, Kever Yang
> <kever.yang at rock-chips.com <mailto:kever.yang@rock-chips.com>> wrote:
>
> Hi Sandy,
>
> On 09/20/2016 09:21 PM, Sandy Patterson wrote:
>> You're probably going to need to change this around now that the
>> Kconfig stuff has been applied to master. Suggest following patch
>> instead:
>
> I didn't enable the BACK_TO_BROM for all of rk3288 board, because
> boards like firefly and chromebook-jerry have enough space without
> this macro,
> and I'm not able to test them, so I only change for those boards
> which must enable this macro.
>
> That's fine, I only meant to suggest you use Kconfig instead. If you
> want to only change a few boards you can do this with *_defconfig file
> now. This way those options are controllable from "make menuconfig"
> after make *_defconfig.
OK, I will move the definition to Kconfig.
Thanks,
- Kever
>
> What's you opinion for firefly-rk3288 and chrome-jerry?
>
> I had a firefly, I expect this should work fine with BACK_TO_BROM
> option, but I have broken it, so I can't test. Vagrant probably can
> though. I don't know anything about chrome-jerry, but it has a lot of
> different storage settings.
>
next prev parent reply other threads:[~2016-09-22 2:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 3:28 [U-Boot] [PATCH v2 0/3] Add sdram capacity auto detect for rk3288 Kever Yang
2016-09-20 3:28 ` [U-Boot] [PATCH v2 1/3] rk3288: config change for enable dram capacity auto-detect Kever Yang
2016-09-20 13:21 ` Sandy Patterson
2016-09-21 3:00 ` Kever Yang
2016-09-21 11:53 ` Sandy Patterson
2016-09-22 2:10 ` Kever Yang [this message]
2016-09-20 3:28 ` [U-Boot] [PATCH v2 2/3] rk3288: sdram: auto-detect the capacity Kever Yang
2016-09-23 2:53 ` Simon Glass
2016-10-07 9:14 ` Kever Yang
2016-10-06 0:28 ` Vagrant Cascadian
2016-09-20 3:28 ` [U-Boot] [PATCH v2 3/3] dts: rk3288: remove node in dmc which not need anymore Kever Yang
2016-09-23 2:58 ` Simon Glass
2016-10-06 0:28 ` Vagrant Cascadian
2016-09-20 15:04 ` [U-Boot] [PATCH v2 0/3] Add sdram capacity auto detect for rk3288 Sandy Patterson
2016-09-21 2:56 ` Kever Yang
2016-09-21 12:41 ` Sandy Patterson
2016-09-22 2:15 ` Kever Yang
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=57E33D94.9090001@rock-chips.com \
--to=kever.yang@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox