On Mon, Aug 15, 2016 at 11:48:31AM -0500, Scott Wood wrote:
> On Mon, 2016-08-15 at 11:56 -0400, Tom Rini wrote:
> > Now that nand_info[] is an array of pointers we need to ensure that it's
> > been populated prior to use. We may for example have ENV in NAND set in
> > configurations that run on b
On Mon, 2016-08-15 at 11:56 -0400, Tom Rini wrote:
> Now that nand_info[] is an array of pointers we need to ensure that it's
> been populated prior to use. We may for example have ENV in NAND set in
> configurations that run on boards with and without NAND (where default
> env is fine enough, suc
Now that nand_info[] is an array of pointers we need to ensure that it's
been populated prior to use. We may for example have ENV in NAND set in
configurations that run on boards with and without NAND (where default
env is fine enough, such as omap3_beagle and beagleboard (NAND) vs
beagle xM (no N
3 matches
Mail list logo