All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Ilya Smelykh <ilya.smelykh@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: nitrogen6x and imx6qsabrelite machines uboot scripts
Date: Fri, 25 Jul 2014 09:25:56 -0700	[thread overview]
Message-ID: <53D28514.80901@boundarydevices.com> (raw)
In-Reply-To: <CAA6dmAeXFvqU_0oxCCHSzcR+reqA1fNWks8Ez=UJReA6s_rWdA@mail.gmail.com>

Hi Ilya,

On 07/25/2014 08:39 AM, Ilya Smelykh wrote:
> Hi Eric,
>
> 2014-07-25 21:49 GMT+07:00 Eric Nelson <eric.nelson@boundarydevices.com>:
> 
>     Hi Ilya,
> 
> <snip>
>
>     Can you explain what you mean by this (use of zImage)?
> 
>     The current machine definition will generate a uImage, not a zImage,
>     and the boot script is configured to load the same.
> 
> Its strange, but in my case I can see only zImage in deploy directory
> for both machines after bitbaking the image...
> 

Apparently I was wrong, and the machine definitions weren't explicity
about the kernel image type. The default must have changed somewhere
along the way, so I just sent patches to address this.

Regards,


Eric


  reply	other threads:[~2014-07-25 16:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 18:16 nitrogen6x and imx6qsabrelite machines uboot scripts Ilya Smelykh
2014-07-24 20:11 ` Morgan McKenzie
2014-07-25 14:49 ` Eric Nelson
2014-07-25 15:39   ` Ilya Smelykh
2014-07-25 16:25     ` Eric Nelson [this message]
2014-07-25 16:27       ` Ilya Smelykh
2014-07-25 16:39         ` Eric Nelson
2014-07-25 16:51           ` Ilya Smelykh
2014-07-25 17:05             ` Eric Nelson
2014-07-25 17:17               ` Gary Thomas
2014-07-25 17:22                 ` Gary Thomas
2014-07-25 17:25                   ` Eric Nelson
2014-07-25 19:05                     ` Gary Thomas
2014-07-25 19:15   ` 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=53D28514.80901@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=ilya.smelykh@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    /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.