Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Tom Rini <tom_rini@mentor.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] classes/image_types: add a variable to list	available IMAGE_FSTYPE's
Date: Tue, 12 Jul 2011 18:52:09 -0600	[thread overview]
Message-ID: <4E1CEC39.1030202@mlbassoc.com> (raw)
In-Reply-To: <4E1CEA80.70806@mentor.com>

On 07/12/2011 06:44 PM, Tom Rini wrote:
> On 07/12/2011 05:37 PM, Gary Thomas wrote:
>> On 07/12/2011 05:38 PM, Tom Rini wrote:
>>> On 07/12/2011 04:24 PM, Joshua Lock wrote:
>>>> This is for use in the Hob GUI to enable the user to change the type
>>>> of the
>>>> generated image.
>>>>
>>>> Signed-off-by: Joshua Lock<josh@linux.intel.com>
>>>> ---
>>>>    meta/classes/image_types.bbclass |    2 ++
>>>>    1 files changed, 2 insertions(+), 0 deletions(-)
>>>>
>>>> diff --git a/meta/classes/image_types.bbclass
>>>> b/meta/classes/image_types.bbclass
>>>> index 89a745c..29d7a57 100644
>>>> --- a/meta/classes/image_types.bbclass
>>>> +++ b/meta/classes/image_types.bbclass
>>>> @@ -102,3 +102,5 @@ IMAGE_DEPENDS_cpio.xz = "xz-native"
>>>>    IMAGE_DEPENDS_ubi = "mtd-utils-native"
>>>>    IMAGE_DEPENDS_ubifs = "mtd-utils-native"
>>>>
>>>> +# This variable is available to request which values are suitable
>>>> for IMAGE_FSTYPES
>>>> +IMAGE_TYPES = "jffs2 cramfs ext2 ext2.gz ext3 ext3.gz squashfs
>>>> squashfs-lzma ubi ubifs"
>>>
>>> Concept is fine, but please don't list ubi and ubifs just list ubi.
>>
>> Perhaps the [brokwn] rule to explicitly build ubifs should also be purged?
>
> Nope, that's how the ubi is created.  Essentially at the time anyhow, OE
> didn't make it too easy to add in an image that needs to be in a
> container to be used.  So we have the ubifs rule (yes, that needs a
> cherry-pick from oe.dev) for 'advanced' users and the ubi rule to create
> a simple ubi image.

I might be missing something, but I don't see why this rule is necessary
in image_types.bbclass:
   IMAGE_CMD_ubifs = "mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.ubifs.img ${MKUBIFS_ARGS}"

Having it there leads to the confusion (I was) that ubifs was useful.

At least for me, I can build ubi images with that rule removed.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



  reply	other threads:[~2011-07-13  0:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 23:24 [PATCH 0/2] Hob integration patches Joshua Lock
2011-07-12 23:24 ` [PATCH 1/2] classes/image_types: add a variable to list available IMAGE_FSTYPE's Joshua Lock
2011-07-12 23:38   ` Tom Rini
2011-07-13  0:37     ` Gary Thomas
2011-07-13  0:44       ` Tom Rini
2011-07-13  0:52         ` Gary Thomas [this message]
2011-07-13  1:11           ` Tom Rini
2011-07-13 11:24             ` Richard Purdie
2011-07-13 14:10               ` Tom Rini
2011-07-13 19:55                 ` Koen Kooi
2011-07-13  2:33     ` Joshua Lock
2011-07-12 23:24 ` [PATCH 2/2] scripts/hob: wrapper script to run hob gui with a UI specific config file Joshua Lock
2011-07-19 18:29 ` [PATCH 0/2] Hob integration patches Saul Wold
2011-07-19 19:10   ` Joshua Lock
     [not found] <cover.1310524498.git.josh@linux.intel.com>
2011-07-13  2:36 ` [PATCH 1/2] classes/image_types: add a variable to list available IMAGE_FSTYPE's Joshua Lock
2011-07-13 11:22   ` Richard Purdie

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=4E1CEC39.1030202@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tom_rini@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox