[meta-freescale] [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Eric Nelson]

On 12/11/2012 01:23 AM, Eric Bénard wrote:
> Hi Eric,
>
> Le Mon, 10 Dec 2012 20:58:22 -0700,
> Eric Nelson <eric.nelson at boundarydevices.com> a écrit :
>> | 6x_bootscript-nitrogen6x.txt: No such file or directory
>
> Does that work if you do bibake u-boot-script-boundary before building
> the image ?
>

Thanks Eric,

That allows things to work, so it seems we have a missing dependency.

We still have an issue though. The generic boot script in our git
repository has a couple of references that presume a single
partition:

	https://github.com/boundarydevices/u-boot-imx6/blob/production/board/boundary/nitrogen6x/6x_bootscript.txt#L56

In particular, the 'root=/dev/mmcblk0p1' clause and the 1 in the
command:
	${fs}load mmc ${disk}:1

The SD card created by bitbake is configured for two:

	~/yocto/build$ fdisk -l 
tmp/deploy/images/fsl-image-test-nitrogen6x-20121211024022.rootfs.sdcard
	...
	Device Boot      Start         End      Blocks   Id  System
      ...sdcard1            8192       24575        8192   83  Linux
      ...sdcard2           24576      753663      364544   83  Linux

It trivially easy to create a boot script specifically for Yocto
images, but this should probably be discussed.

Why should we use two partitions? It seems that unless we're loading
a RAM disk, there's no benefit in having multiple partitions.

I suspect that there's a way to create a RAM disk in Yocto, but
I'm not sure where to start besides Googling the MLs and grepping
the sources.

If we decide to use a single partition, it also seems that the
.sdcard target is a bit of overkill, and a tar-ball of the RFS
is sufficient.

Regards,


Eric