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

Eric Nelson eric.nelson at boundarydevices.com
Tue Dec 11 06:29:34 PST 2012

On 12/11/2012 07:15 AM, Otavio Salvador wrote:
> On Tue, Dec 11, 2012 at 12:09 PM, Eric Nelson <
> eric.nelson at boundarydevices.com> wrote:
>> On 12/11/2012 01:23 AM, Eric Bénard wrote:
>> It trivially easy to create a boot script specifically for Yocto
>> images, but this should probably be discussed.
> We can apply a patch in the script for it. Can you please generate a patch
> to adapt the script for our environment?
Can do.

There's another issue though. The boot scripts need to be wrapped
by 'mkimage' so that U-Boot will 'source' them properly.

	mkimage -A arm -O linux -T script -C none -a 0 -e 0 \
		-n "boot script" -d 6x_bootscript.txt 6x_bootscript

I just copied the SD card image and found that the .txt files
were copied, but not compiled.

>> 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.
> The real benefit here is to avoid too much complexity in sdcard class. For
> accomplish it in a single partition we'd need to flexibilize the class even
> more and I am not sure it is worth the effort.
>> 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.
> The idea to provide a sdcard image is to allow for easier test and use of
> the build images. It is a matter of dd the fine, directly in the sdcard and
> be done with that.

Okay with me for now. At least this will get us up and bootable.



More information about the meta-freescale mailing list