From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by mx1.pokylinux.org (Postfix) with ESMTP id 6DBAD4C800C1 for ; Thu, 14 Jul 2011 08:56:13 -0500 (CDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id p6EDuAZe027049 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Jul 2011 06:56:10 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Thu, 14 Jul 2011 06:56:10 -0700 Message-ID: <4E1EF577.2080807@windriver.com> Date: Thu, 14 Jul 2011 09:56:07 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10 ThunderBrowse/3.3.5 MIME-Version: 1.0 To: Koen Kooi References: <4E1EEB87.1020200@windriver.com> <9BDFCF4A-EA10-4963-87E0-556604F3E0AB@dominion.thruhere.net> In-Reply-To: <9BDFCF4A-EA10-4963-87E0-556604F3E0AB@dominion.thruhere.net> Cc: Yocto discussion list Subject: Re: IMAGE_FSTYPES that are supported? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2011 13:56:13 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 07/14/11 09:40, Koen Kooi wrote: > > Op 14 jul 2011, om 15:13 heeft Bruce Ashfield het volgende geschreven: > >> On 07/14/11 09:05, Kumar Gala wrote: >>> Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not. >> >> I'm not 100% where the list is, but I can confirm that >> uImages are supported and work nicely. Assuming that >> you are talking about the common use case, and not something >> more exotic :) > > > I think he means partitioned uimages where you have a kernel + initrd in a single uimage. We don't support that *yet*, but all the needed blocks are there. And we finally get a usecase for having the loadadresses in the machine.conf files :) Yah, that's what I wondered as well. I've done this locally, but nothing out of the box .. so I had nagging doubts! Cheers, Bruce