[OE-core] [PATCHv2 1/2] Add wic support to generate rootfs image for uboot

Adrian Calianu Adrian.Calianu at enea.com
Fri Jun 13 06:43:21 UTC 2014


Hi Otavio,

	First step was to add support in wic to generate rootfs images only from packages out of bitbake environment.
	To test this functionality was chosen to generate ramdisk images for now. We have plans to extend the U-Boot plugin in order to generate other types of rootfs images.

Thanks,
Adrian

> -----Original Message-----
> From: openembedded-core-bounces at lists.openembedded.org
> [mailto:openembedded-core-bounces at lists.openembedded.org] On Behalf
> Of Otavio Salvador
> Sent: Thursday, June 12, 2014 5:02 PM
> To: y at enea.se
> Cc: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] [PATCHv2 1/2] Add wic support to generate rootfs
> image for uboot
> 
> Hello,
> 
> On Thu, Jun 12, 2014 at 5:43 AM,  <y at enea.se> wrote:
> > From: Adrian Calianu <adrian.calianu at enea.com>
> >
> > Add support in wic to build ramdisk uboot images from list of packages
> > or from an existing rootfs folder.
> >
> > Providing the list of packages starting with XXX-core-boot
> > package(into wks file) will generate an rootfs image for uboot out of
> bitbake.
> > There is also possible to combine an existing/application rootfs with
> > a list of packages that can be installed but the user must take care
> > to provide a basic core boot rootfs or XXX-core-boot package and
> reporul(wic.conf).
> >
> > Some prerequisites are required for this new build setup:
> > ../poky/scripts/lib/image/config/wic.conf
> > [create]
> > arch=target_arch (example: powerpc, arm, x86) pkgmgr=opkg
> > repourl=http://example.distro/p2020rdb/ipk/all
> > http://example.distro/p2020rdb/ipk/p2020rdb
> > http://example.distro/p2020rdb/ipk/ppce500v2
> >
> >     1) Build an rootfs image from an existing bitbake build:
> >        wic create ../poky/scripts/lib/image/canned-wks/uboot.wks -e
> > core-image-minimal -o .../output
> >
> >     2) Build an rootfs image from an existing rootfs and native_sysroot:
> >        wic create ../poky/scripts/lib/image/canned-wks/uboot.wks -r
> > .../path_to_rootfs -n .../path_to_native_sysroot -o .../output
> >
> >     3) Build an rootfs image only from a package list (on wks file):
> >
> >        Add the package list to be installed as rootfs on
> ../poky/scripts/lib/image/canned-wks/uboot.wks:
> >        %packages
> >        packagegroup-core-boot
> >        pramfs-init
> >        run-postinsts
> >        packagegroup-core-ssh-dropbear
> >        %end
> >
> >        Generate rootfs image:
> >        wic create ../poky/scripts/lib/image/canned-wks/uboot.wks  -n
> > .../path_to_native_sysroot -o .../output
> >
> > Signed-off-by: Adrian Calianu <adrian.calianu at enea.com>
> 
> I really liked the idea and it is a nice step further but it is not clear to me how
> we'll "tell" wic about platform specific U-Boot installation like i.MX vs MXS
> where the layout of the uSD image is very different.
> 
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



More information about the Openembedded-core mailing list