All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giordon Stark <gstark@cern.ch>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
	"Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: yocto@yoctoproject.org, Gary Thomas <gary@mlbassoc.com>
Subject: Re: [Openembedded-architecture] Standalone image writer
Date: Mon, 29 Feb 2016 20:05:44 +0000	[thread overview]
Message-ID: <CAFzUWGnCD1m3jmbgyNqhhM0QeeO1mGnGuk7qy=F329r1zLoTqA@mail.gmail.com> (raw)
In-Reply-To: <3422071.a5vtJpgWht@peggleto-mobl.ger.corp.intel.com>

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

Hi all,

In a similar problem -- I find that the boot.bin file does not work out of
the box when I copy the files over to the SDCard to boot on a Xilinx board.
I end up having to open the SDK and generate a BOOT image myself using the
other files that were generated (u-boot, devicetree) with the SDK's
FSBL.elf. Is this a known problem or would a centralized solution for
creating the image solve this?

Giordon

On Mon, Feb 29, 2016 at 1:53 PM Paul Eggleton <paul.eggleton@linux.intel.com>
wrote:

> On Mon, 29 Feb 2016 11:27:15 Barros Pena, Belen wrote:
> > On 29/02/2016 08:12, "yocto-bounces@yoctoproject.org on behalf of Paul
> > Eggleton" <yocto-bounces@yoctoproject.org on behalf of
> > paul.eggleton@linux.intel.com> wrote:
> > >There isn't a frontend UI for wic that I am aware of though - as I
> > >mentioned earlier image-writer has no support for it, it's just doing a
> > >straight dd to the device.
> >
> > We would really like to add support for wic at some point.
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=8769
>
> True, but that's a slightly different usage of wic - i.e. preparing the
> formatted image, which we should support. However, writing a formatted
> image
> to an SD card / USB stick isn't something you could practically do from a
> web-
> based application I don't think - not without help from a local
> application at
> any rate.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 2534 bytes --]

  reply	other threads:[~2016-02-29 20:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  2:49 Removing Hob for 2.1 Paul Eggleton
2016-02-26  2:54 ` [Openembedded-architecture] " Khem Raj
2016-02-26 19:15   ` Anders Darander
2016-02-26 13:37 ` Philip Balister
2016-02-26 14:26   ` nick
2016-02-28 20:42     ` Paul Eggleton
2016-02-26 14:29   ` nick
2016-02-29 12:29     ` Barros Pena, Belen
2016-02-29  0:17 ` Standalone image writer Paul Eggleton
2016-02-29  1:46   ` [Openembedded-architecture] " Khem Raj
2016-02-29  3:31     ` Trevor Woerner
2016-02-29  3:48       ` Gary Thomas
2016-02-29  7:12         ` Paul Eggleton
2016-02-29 11:27           ` Barros Pena, Belen
2016-02-29 19:52             ` Paul Eggleton
2016-02-29 20:05               ` Giordon Stark [this message]
2016-03-02 21:16                 ` Paul Eggleton
2016-03-02 23:18                   ` Andrei Gherzan
2016-02-29 20:13               ` Philip Balister
2016-02-29 11:04 ` FW: Removing Hob for 2.1 Barros Pena, Belen

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='CAFzUWGnCD1m3jmbgyNqhhM0QeeO1mGnGuk7qy=F329r1zLoTqA@mail.gmail.com' \
    --to=gstark@cern.ch \
    --cc=belen.barros.pena@intel.com \
    --cc=gary@mlbassoc.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@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.