From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] Add Boundary Devices Nitrogen6X boards
Date: Mon, 11 Mar 2013 15:30:38 +0100 [thread overview]
Message-ID: <513DEA8E.7070501@denx.de> (raw)
In-Reply-To: <513DE411.4060802@boundarydevices.com>
On 11/03/2013 15:02, Eric Nelson wrote:
> Thanks Stefano,
>
> On 03/11/2013 06:44 AM, Stefano Babic wrote:
>> On 11/03/2013 14:18, Fabio Estevam wrote:
>>> Hi Stefano,
>>>
>>> On Mon, Mar 11, 2013 at 9:04 AM, Stefano Babic <sbabic@denx.de> wrote:
>>>
>>>> As set previously, my position is, since RFC patches were pushed in
>>>> January, that some kind of complexity can be well managed with SPL
>>>> instead of with very SOC specific code. However, in the meantime I said
>>>> explicitely that I was not against the current patchset in the form
>>>> Eric
>>>> posted now. I understand this can be seen as a temporary solution, but
>>>> let's increase the number of users using these boards, and taking into
>>>> account that some other pending patches can help to switch to SPL.
>>>>
>>>> In fact, there also other patchsets that I hope will be merged soon and
>>>> will make the swicth to SPL easier - I mean Benoit's patches regarding
>>>> NAND on MX5 and dropping old spl code from some boards.
>>>
>>> Just to make sure I understand the plan:
>>>
>>> Do you mean that you are willing to accept current Eric's series for
>>> adding nitrogen support into 2013.04, and after this we should work on
>>> converting it to the SPL mechanism for 2013.07?
>>
>> IMHO, yes. The long term solution is using SPL, as well as it is already
>> used in other SOCs. But at the moment, I tend to not block the current
>> series, taking into account that we have not yet a i.MX6 board with SPL.
>>
>
> Then I'll forward a V3 (without get_ram_size()).
>
> Do you want me to restrict the number of configurations to the
> "standard" memory configurations?
Well, this could avoid that we add now a lot of files with the hope that
later they will be cleanued up, and then this does not happen - and
further configurations will be added later after switching to SPL.
Best regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2013-03-11 14:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 0:04 [U-Boot] [PATCH V2] Add Boundary Devices Nitrogen6X boards Eric Nelson
2013-03-10 0:49 ` Troy Kisky
2013-03-10 8:02 ` Wolfgang Denk
2013-03-10 14:15 ` Eric Nelson
2013-03-10 7:59 ` Wolfgang Denk
2013-03-10 15:09 ` Eric Nelson
2013-03-10 15:45 ` Wolfgang Denk
2013-03-10 16:25 ` Eric Nelson
2013-03-10 22:03 ` Wolfgang Denk
2013-03-10 23:36 ` Eric Nelson
2013-03-11 11:15 ` Wolfgang Denk
2013-03-11 12:04 ` Stefano Babic
2013-03-11 13:18 ` Fabio Estevam
2013-03-11 13:44 ` Stefano Babic
2013-03-11 13:54 ` Fabio Estevam
2013-03-11 14:02 ` Eric Nelson
2013-03-11 14:30 ` Stefano Babic [this message]
2013-03-11 14:39 ` Tom Rini
2013-03-11 13:37 ` Eric Nelson
2013-03-11 16:48 ` Wolfgang Denk
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=513DEA8E.7070501@denx.de \
--to=sbabic@denx.de \
--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