From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Troy Kisky <troy.kisky@boundarydevices.com>
Subject: Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X
Date: Tue, 11 Dec 2012 07:29:34 -0700 [thread overview]
Message-ID: <50C7434E.2050505@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKr4EG8pDo_5=MW9RBB5PYVKgPmRRHnEn=WrX4qXRtWNYw@mail.gmail.com>
On 12/11/2012 07:15 AM, Otavio Salvador wrote:
> On Tue, Dec 11, 2012 at 12:09 PM, Eric Nelson <
> eric.nelson@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.
e.g.
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.
Regards,
Eric
next prev parent reply other threads:[~2012-12-11 14:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 16:06 [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X Otavio Salvador
2012-12-10 16:06 ` [meta-fsl-arm-extra][PATCH 1/3] u-boot-boundary: Add U-Boot recipe for Boundary Devices version Otavio Salvador
2012-12-10 16:06 ` [meta-fsl-arm-extra][PATCH 2/3] u-boot-script-boundary: Add recipe to deploy the boot scripts Otavio Salvador
2012-12-10 16:06 ` [meta-fsl-arm-extra][PATCH 3/3] nitrogen6x: Add machine definition Otavio Salvador
2012-12-10 16:11 ` [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X Otavio Salvador
2012-12-10 19:47 ` Eric Nelson
2012-12-10 19:50 ` Otavio Salvador
2012-12-11 3:58 ` Eric Nelson
2012-12-11 8:23 ` Eric Bénard
2012-12-11 14:09 ` Eric Nelson
2012-12-11 14:15 ` Otavio Salvador
2012-12-11 14:29 ` Eric Nelson [this message]
2012-12-11 14:35 ` Otavio Salvador
2012-12-11 13:27 ` Harmalkar, Subodh S.
2012-12-11 14:10 ` Otavio Salvador
2012-12-11 14:10 ` Otavio Salvador
2012-12-11 14:24 ` Eric Nelson
2012-12-11 14:35 ` Otavio Salvador
2012-12-11 15:48 ` Eric Nelson
2012-12-11 18:28 ` Otavio Salvador
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=50C7434E.2050505@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
--cc=troy.kisky@boundarydevices.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.