All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: James Abernathy <jfabernathy@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: README.hardware
Date: Wed, 09 Nov 2011 14:41:26 +0000	[thread overview]
Message-ID: <1589795.WumM70vV8d@helios> (raw)
In-Reply-To: <CANFv2EkEsY92-+=Beqw_L68K0bT5HHSfy3fkw90xJgBre4wfHQ@mail.gmail.com>

On Wednesday 09 November 2011 09:34:40 James Abernathy wrote:
> In the atom-pc platform section, the Hard Disk option mentions a bitbake
> target of 'core-image-minimal-directdisk'.  This target is not listed as an
> option for bitbake after 'source oe-init-build-env' and if you try to use
> it, the bake will fail at some point due to invalid target.
> 
> Am I missing something or is this a documentation problem.

This is a documentation problem - for 1.1 there are no -directdisk or -live 
images; instead this is done by adding "live" to IMAGE_FSTYPES which is done 
automatically if MACHINE is set to atom-pc, so all you need to do is build the 
image you want (e.g. core-image-minimal) and you will also get a corresponding 
live image.

I noticed that we missed updating this document the other day and am putting 
together a patch for README.hardware to fix it.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2011-11-09 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 14:34 README.hardware James Abernathy
2011-11-09 14:41 ` Paul Eggleton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-08 13:47 README.hardware Gary Thomas
2010-12-09 19:08 ` README.hardware Joshua Lock
2010-12-09 19:18   ` README.hardware Gary Thomas
2010-12-09 19:35     ` README.hardware Tom Zanussi
2010-12-10 11:42       ` README.hardware Joshua Lock

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=1589795.WumM70vV8d@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=jfabernathy@gmail.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.