All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm-extra][PATCH v3 3/3] nitrogen6x: Add machine definition
Date: Wed, 12 Dec 2012 09:51:48 -0700	[thread overview]
Message-ID: <50C8B624.5060700@boundarydevices.com> (raw)
In-Reply-To: <1355262632-19265-4-git-send-email-otavio@ossystems.com.br>

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

Hi Otavio,

On 12/11/2012 02:50 PM, Otavio Salvador wrote:
> This adds the machine definition to Nitrogen6x from Boundary Devices.
> More information at:
>
> http://boundarydevices.com/products/nitrogen6x-board-imx6-arm-cortex-a9-sbc/
>
>  <snip>
>
> diff --git a/conf/machine/nitrogen6x.conf b/conf/machine/nitrogen6x.conf
> new file mode 100644
> index 0000000..d668eb2
> --- /dev/null
> +++ b/conf/machine/nitrogen6x.conf
> @@ -0,0 +1,30 @@
 >
 > <snip>
 >
> +
> +# Boot scripts to install
> +BOOT_SCRIPTS = "6x_bootscript-${MACHINE}:6x_bootscript"

Was the omission of 6x_upgrade intentional?

I tested with the attached patch and got both installed properly
on the SD card.

Otherwise:

Tested-by: Eric Nelson <eric.nelson@boundarydevices.com>


[-- Attachment #2: 0001-nitrogen6x-add-6x_upgrade-script.patch --]
[-- Type: text/x-patch, Size: 894 bytes --]

From d06b03a4a227db6d80c65187c837ccdbe7f71cb8 Mon Sep 17 00:00:00 2001
From: Eric Nelson <eric.nelson@boundarydevices.com>
Date: Wed, 12 Dec 2012 09:43:43 -0700
Subject: [PATCH] nitrogen6x: add 6x_upgrade script

Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
---
 conf/machine/nitrogen6x.conf |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/nitrogen6x.conf b/conf/machine/nitrogen6x.conf
index d668eb2..f118bba 100644
--- a/conf/machine/nitrogen6x.conf
+++ b/conf/machine/nitrogen6x.conf
@@ -19,7 +19,7 @@ IMAGE_BOOTLOADER ?= ""
 do_rootfs[depends] += "u-boot-script-boundary:do_deploy"
 
 # Boot scripts to install
-BOOT_SCRIPTS = "6x_bootscript-${MACHINE}:6x_bootscript"
+BOOT_SCRIPTS = "6x_bootscript-${MACHINE}:6x_bootscript 6x_upgrade-${MACHINE}:6x_upgrade"
 
 UBOOT_MACHINE = "nitrogen6X_config"
 
-- 
1.7.9.5


  parent reply	other threads:[~2012-12-12 16:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 21:50 [meta-fsl-arm-extra][PATCH v3 0/3] Initial support for Nitrogen6X Otavio Salvador
2012-12-11 21:50 ` [meta-fsl-arm-extra][PATCH v3 1/3] u-boot-boundary: Add U-Boot recipe for Boundary Devices version Otavio Salvador
2012-12-11 21:50 ` [meta-fsl-arm-extra][PATCH v3 2/3] u-boot-script-boundary: Add recipe to deploy the boot scripts Otavio Salvador
2012-12-11 21:50 ` [meta-fsl-arm-extra][PATCH v3 3/3] nitrogen6x: Add machine definition Otavio Salvador
2012-12-12 13:28   ` Eric Nelson
2012-12-12 15:49     ` Otavio Salvador
2012-12-12 16:13       ` Eric Nelson
2012-12-12 16:23         ` Otavio Salvador
2012-12-12 17:20           ` Eric Nelson
2012-12-12 17:26             ` Otavio Salvador
2012-12-12 16:51   ` Eric Nelson [this message]
2012-12-12 16:56     ` Otavio Salvador
2012-12-11 21:53 ` [meta-fsl-arm-extra][PATCH v3 0/3] Initial support for Nitrogen6X Otavio Salvador
2012-12-12 17:30   ` 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=50C8B624.5060700@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.