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 08:48:27 -0700 [thread overview]
Message-ID: <50C755CB.7050701@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKpc-pL9Ue3ibtkbcRKMixtJgaFEkRxFZqLC1KGPgK6GGQ@mail.gmail.com>
Hi Otavio,
On 12/11/2012 07:35 AM, Otavio Salvador wrote:
> On Tue, Dec 11, 2012 at 12:24 PM, Eric Nelson <
> eric.nelson@boundarydevices.com> wrote:
>>
>> On 12/11/2012 07:10 AM, Otavio Salvador wrote:
>>> On Tue, Dec 11, 2012 at 1:58 AM, Eric Nelson <
>>> eric.nelson@boundarydevices.**com <eric.nelson@boundarydevices.com>>
>>> wrote:
>>>
>>>>
>>> The sdcard generation routine works this way and I'd like to do minimal
>>> changes on this, if possible. Currently the change I am doing is to have
>>> the boot script in the first partition. Maybe we'd need to patch the boot
>>> script to be able to load kernel and pass the right root param, but rest
>>> should work fine.
>>>
>> I have no problem building 6x_bootscript_yocto and adding it to our git
>> repository. I think this will require a bump in the revision.
>>
>> Do you want to keep uImage in the root of the first partition, and
>> format that as FAT?
>>
> At least for now. I'd like to keep the change at minimum. We can refactor
> and improve it later.
>
Do you know the context (directory) in which the patch will be applied?
Will it be from the root of the U-Boot tree and patch
board/boundary/nitrogen6x/6x_bootscript.txt
board/boundary/nitrogen6x/6x_upgrade.txt
Or will it be applied somewhere in the work directory?
Also, the 6x_upgrade script is useless unless we copy u-boot.imx
into one of the partitions. Should it go into the FAT partition or
the ext3 partition?
Please advise,
Eric
next prev parent reply other threads:[~2012-12-11 15:48 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
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 [this message]
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=50C755CB.7050701@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.