[U-Boot] [PATCH V4 4/5] ARM: OMAP4/5: Change the default boot command to work with device tree

[Sricharan R <r.sricharan@ti.com>]

On Tuesday 02 April 2013 09:43 PM, Tom Rini wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 04/02/2013 11:33 AM, Sricharan R wrote:
>> Hi Tom,
>>
>> On Tuesday 02 April 2013 12:50 AM, Tom Rini wrote:
>>> On Mon, Apr 01, 2013 at 09:22:41PM +0530, Sricharan R wrote:
>>>
>>>> Now with kernel moving to all device tree, the default boot
>>>> command is changed to pass the device tree blob. Also, adding
>>>> the findfdt command to get the dt-blob based on the board.
>>>>
>>>> Thanks to Tom Rini <trini@ti.com> for suggesting this.
>>>>
>>>> Signed-off-by: Sricharan R <r.sricharan@ti.com>
>>> [snip]
>>>> @@ -145,6 +149,10 @@ "loadaddr=0x82000000\0" \ 
>>>> "console=ttyO2,115200n8\0" \ "fdt_high=0xffffffff\0" \ +
>>>> "fdtaddr=0x80f80000\0" \ +	"bootpart=0:1\0" \ +	"bootdir=\0" \ 
>>>> +	"bootfile=uImage\0" \
>>>
>>> What about 0:2 and /boot, ala am335x_evm as well?  I'm not aware
>>> of any distributions being really clever and mounting the FAT
>>> partition to /boot and I know some that have been expecting and
>>> using their ext*-located kernels for a while for various TI
>>> platforms.  And wer're moving in that latter direction too :)
>>> Thanks!
>>>
>> Sorry, i am not clear here. You mean default partition should be
>> '2' and not '1'. why ?. Is there any ordering like FAT-1, EXT2-2,
>> etc ? The reason i added 0:1, was we generally have boot FAT as
>> partition '1' and directly take images from there, without any
>> hierarchies (/boot)
> 
> Right.  I'm saying we should be pulling from the Linux filesystem for
> our kernel / device tree and move people toward pulling from EXT*
> (where the distro or vendor has provided them with a reasonable
> kernel, or they've updated their own there) and away from FAT.
> 
 ok, get it. Will change then.

Regards,
 Sricharan