[U-Boot] [PATCH 1/4] Tegra: All Tamonten-derived boards use onboard NAND

[Tom Rini <trini@ti.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/08/2013 11:36 AM, Tom Warren wrote:
> On Mon, Mar 4, 2013 at 4:39 PM, Stephen Warren
> <swarren@wwwdotorg.org> wrote:
>> On 03/04/2013 04:26 PM, Tom Warren wrote:
>>> Thierry,
>>> 
>>> On Mon, Mar 4, 2013 at 3:41 PM, Thierry Reding 
>>> <thierry.reding@avionic-design.de> wrote:
>>>> On Mon, Mar 04, 2013 at 01:46:48PM -0700, Tom Warren wrote: 
>>>> [...]
>>>>> I kinda lost track of this patchset. I'd like to move it
>>>>> into u-boot-tegra/next if you think it's ready, but I'm not
>>>>> sure if it conflicts with/works with Stephen's 4th patch of
>>>>> his v2 series ("ARM: tegra: enable a common set of
>>>>> disk-related commands").
>>>> 
>>>> I can rebase my patches on top of Stephen's work and resend
>>>> them if it helps.
>>>> 
>>>> Thierry
>>> The only problem I see is that Stephen's patchset isn't
>>> exclusively Tegra-based, so I'm not sure I want to bring it
>>> into the Tegra tree and cause problems when I do a PR. The
>>> other half of the patchset is assigned to Tom Rini.
>>> 
>>> Stephen - how would you like me to resolve this?
>> 
>> Hmmm. Thierry's patch series does quite a few things at once.
>> 
>> I'd suggest that Thierry posts a series that /just/ enables NAND 
>> support. It should be possible to apply that on its own without
>> any conflicts/dependencies on my series.
>> 
>> Enabling FIT could also be a separate series without any 
>> conflicts/dependencies.
>> 
>> A lot of the rest of that series is effectively part of my
>> series, since I ended up enabling all those new options in the
>> various common Tegra config files in my series.
>> 
>> The only thing left over is the removal of the custom definition
>> of CONFIG_BOOTCOMMAND in the AD headers. That should happen after
>> my series.
>> 
>> Re: How to get my series into Tegra's tree. I think it'd be fine
>> to apply my series to the Tegra tree even though it touches
>> disk/partition code if you can get the/a maintainer for that code
>> to ack it. Probably someone like Tom Rini. That way, Thierry's
>> CONFIG_BOOTCOMMAND changes wouldn't have to wait long I hope.
> Sorry, kinda dropped the ball on this while I was working on the
> padcfg changes.
> 
> Tom Rini - do you agree with Stephen's approach for the disk parts
> of his patchset? If so, I can apply it to u-boot-tegra/next today &
> push.

Can you give me some patchwork links?  I'm getting going on another
round of pulling things into master today.  Thanks!

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJROhV4AAoJENk4IS6UOR1WgboP/iZFuJFTOf9lLyR38dNHk66p
7h/wexQRQr7CIMYUwHsS55IStunXNif4Njm9u6ehNbjz45v0vpIVUlV37NjhFG82
3XwTRLvt1w9Aag6h8jB/We+Z73rArhHfpq3dbB5FuyX4n+J3Dq+7sRp7kZkRu7gS
skSzcAE5b0eMB6OiPwuG0zkVkMaf0ryYZAzjsRvXgT9302YSigHdM0TnZColzcLt
LQREK58EiQiO20DGuTYIyRUzEG9MlSiv9J7GOLbtgdEbXES/P/v40lybvPwtNdre
q3UmPrDRCMJ2eqtyVZbTRLEAxN9vUhd11cfDBb2HOSsFTilJkpu1GBaR80nmca3p
HgyeHvZnABQ/rvAVRPHP54UT+iXF531Z3CRUF5vQcT0N/JHH1LuyHVuij23b5Fxt
LcM51YNijmFkisZVTxgX4mrFNpGmSvP+4jEky+t6Vz26uZ8YYfa26Lwlby6EFrKy
Nz8QduohPsuSi92QQjSb5LJn86QxFNwz+20UjXPLilQRet/W5WosGJqdUKdH1aun
tkZlUZw7mtu9lIEqJJq4JpNKYP7NoMmDygyob0v+VCUPshqKig6Xs3voQMaAC44i
90OBzokS/Vj/AYJQ7eXwpVsdYkrPc5UXBU70/5QMftEVDR6wk0cLHou18F3wYeQd
HpIFPnhpM0/7rMKXchV3
=FTH6
-----END PGP SIGNATURE-----