From mboxrd@z Thu Jan  1 00:00:00 1970
From: Troy Kisky <troy.kisky@boundarydevices.com>
Date: Thu, 06 Mar 2014 10:46:03 -0700
Subject: [U-Boot] Single u-boot for quad/duallite
In-Reply-To: <CAP9ODKpr5X=xqwKsaTFoh0BbgUx+mnU0-HURviW9NMV-mC76cA@mail.gmail.com>
References: <53177B4C.20906@boundarydevices.com>
	<CAP9ODKpr5X=xqwKsaTFoh0BbgUx+mnU0-HURviW9NMV-mC76cA@mail.gmail.com>
Message-ID: <5318B45B.2040901@boundarydevices.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 3/5/2014 12:38 PM, Otavio Salvador wrote:
> On Wed, Mar 5, 2014 at 4:30 PM, Troy Kisky
> <troy.kisky@boundarydevices.com> wrote:
>> Since we are slowly heading toward a single u-boot for quad/duallite,
>> can we find a solution to this now.
>>
>> mx6sabre_common.h:      "fdt_file=" CONFIG_DEFAULT_FDT_FILE "\0" \
>> mx6sabresd.h:#define CONFIG_DEFAULT_FDT_FILE    "imx6q-sabresd.dtb"
>> mx6sabresd.h:#define CONFIG_DEFAULT_FDT_FILE    "imx6dl-sabresd.dtb"
>>
>> Perhaps common code could create this environment variable by
>> concatenating with the board name if not already existing in the
>> environment.
>>
>> Opinions?
> 
> I fully agree. Are you going to look at this?
> 
Sure, I'll cook something up.

Troy