[U-Boot] [RFC PATCH] Add support for Boundary Devices Nitrogen6x boards

[Eric Nelson <eric.nelson@boundarydevices.com>]

Thanks for the review Fabio,

On 03/08/2013 03:49 PM, Fabio Estevam wrote:
> Hi Eric,
>
> On Wed, Jan 30, 2013 at 4:10 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> This patch adds support for the Nitrogen6X board(s) from
>> Boundary Devices. The boards are based on the i.MX6x
>> processor family with two major variants:
>>          i.MX6Quad/6Dual
>>          i.MX6Dual-Lite/6Solo
> ....
>>   board/boundary/nitrogen6x/800mhz_2x128mx16.cfg     |   37 +
>>   board/boundary/nitrogen6x/800mhz_2x256mx16.cfg     |   37 +
>>   board/boundary/nitrogen6x/800mhz_4x128mx16.cfg     |   37 +
>>   board/boundary/nitrogen6x/800mhz_4x256mx16.cfg     |   37 +
>
> Good work, I really like this series.
>

Glad to hear it.

> I managed to test it and added support for a mx6dl board.
>
> I would like to suggest if you could move the different memory inits
> (like 800mhz_4x256mx16.cfg) into a common directory so that other
> boards can pull their DDR init from there when possible.
>

Okay, but this might be a bit of a stretch. We went through a
lot of our SABRE Lite, Nitrogen6x, and Nitrogen6x SOM boards
to select the right median values for the termination values
and such.

These may not apply for other boards, so another level of
indirection might be appropriate.

IOW, while most of the registers in the files like
800mhz_4x256mx16.cfg are for the memory **arrangement**,
some of them are or could be specific to the layout and
PCB fabrication details.

> Do you think we still can make this go into 2013.04?
>
Yep.

Now that this guy at Freescale fixed up the HDMI stuff,
I can even re-send the HDMI detect patch ;)

I'll send V2 tomorrow.

Regards,


Eric