meta-agl - meta-agl layer (core AGL)

Age	Commit message (Collapse)	Author	Files	Lines
2018-05-31	3rd part of the layer/profile rework [1/2]	Jan-Simon Möller	1	-0/+10
	This is the last larger commit in this series and deals with the graphical part. We introduce the graphical profiles: - meta-agl-profile-graphical -- meta-agl-profile-graphical-html5 -- meta-agl-profile-graphical-qt5 Notable changes: - weston-ini-conf moved to the meta-agl-bsp layer. Most BSPs have bbappends, so we need to have the recipes present (but unused) even in the console images. - new image: agl-image-boot = terminal-only + network + package-manaager. Ready for using package-feeds - new image/sdk: agl-image-minimal-crosssdk - agl-service-mediaplayer has a dependency on weston, thus it cannot be in the 'core'. Moved it to profile-graphical. - The wayland-ivi-extension moved to the agl-demo-platform. - The app-framework layer included and pulled 'web-runtime' as dependency. This broke console-only images. This has been moved to be in meta-agl-demo only for now. - added and massaged the agl-features. - found and added a useful script 'oe-depends-dot' that helps to work with the dot files (produced with bitbake -g) Todo: - we'll need another pass through the packagegroups. The dependencies for the layers/profiles are now sorted-out but we might have to add/shuffle a few packages. For further details, see meta-agl/docs/profiles.md. v2: fix meta-agl/meta-security/conf/layer.conf - the immediate expansion previously used in there caused some recipes not being added to BBFILES. v3: fix packagegroup renaming (packagegroup-agl-devel -> packagegroup-agl-core-devel) v4: fix missing packagegroup inclusion (tnx Jose, Scott, Stephane) v5: fix missing packagegroup inclusion v6: explicitely put profile-graphical-qt5 on-top of profile-graphical v7: re-add 'procps' when agl-devel feature is on Bug-AGL: SPEC-145 Change-Id: I24cdcd1118932758d0c55d333338238f2a770877 Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>

meta-netboot ============ This layer contains some recipes and configuration adjustments to allow network boot through NBD (network block device). Content and usage ----------------- This layer creates a new supplementary initrd image which can be downloaded through TFTP with the kernel. At boot time, the init script will try to mount the rootfs based on the following kernel command line parameters: * nbd.server: IP address to reach the NBD server * nbd.port: TCP port on which server is listening (default: 10809) * nbd.dev: nbd device to use (default: /dev/nbd0) * nbd.debug: activate debug mode (init script is then interruptible) The layer meta-netboot contains recipes for the following components: * busybox: activate the built-in NBD client * initramfs-netboot: contains the init script started by the kernel: basically, this script mounts the real root filesystem, then pivot_root on it and finally exec systemd. * initramfs-netboot-image: image to specify for building the initrd To enable the build of the netboot initrd and ext4 rootfs, add the following line in conf/local.conf: INHERIT += "netboot" Server side ----------- On the server side (assuming that the build dir is stored in $BUILD) we can run: * a TFTP server, for example tftpd-hpa started with $BUILD/tmp/deploy/images as the TFTP dir: /usr/sbin/in.tftpd --listen --user tftp --address 0.0.0.0:69 --secure $BUILD/tmp/deploy/images * a NBD server, for example xnbd-server, used to expose the whole ext4 rootfs as a network block device: xnbd-server --target --lport 10809 $BUILD/tmp/deploy/images/$MACHINE/agl-demo-platform-$MACHINE.ext4 Target side ----------- On the target board, a specific setup should also be done. For example, for Renesas Porter board, the following U-boot environment could be used (adjust IP addresses !): ------------------------------------------------------------------ setenv 'bootkfile' 'uImage+dtb' setenv 'bootkaddr' '0x40007fc0' setenv 'bootifile' 'initramfs-netboot-image-porter.ext4.gz.u-boot' setenv 'bootiaddr' '0x50000000' setenv 'ipaddr' '<board_IP>' setenv 'serverip' '<server_IP>' setenv 'bootargs_console' 'console=ttySC6,38400 ignore_loglevel' setenv 'bootargs_video' 'vmalloc=384M video=HDMI-A-1:1280x960-32@60' setenv 'bootargs_extra' 'rw rootfstype=ext4 rootwait rootdelay=2' setenv 'bootargs_root' 'root=/dev/ram0 ramdisk_size=16384 ip=dhcp' setenv 'bootkload_net' 'tftp ${bootkaddr} porter/${bootkfile}' setenv 'bootiload_net' 'tftp ${bootiaddr} porter/${bootifile}' setenv 'bootcmd' 'setenv bootargs ${bootargs_console} ${bootargs_video} ${bootargs_root} ${bootargs_extra} nbd.server=${serverip}; run bootkload_net; run bootiload_net; bootm ${bootkaddr} ${bootiaddr}' saveenv # optional: saves env in flash run bootcmd # boots the board, executed automatically after power up ------------------------------------------------------------------