[yocto] Doubt about layer priority and package version preference
Hi, I am having some doubt about the yocto 1.3. can anyone clarify the same? Is there any change done in yocto 1.3 about the layer priority and package version preference? I observed that In yocto1.2: Package version takes preference over the layer priority. Ex. If 1.0 version of package-1 is present in layer1 with higher priority then layer2 which contains 2.0 version of package-1, then while building 2.0 version of package-1 is considered though layer priority is otherwise but In Yocto1.3: Layer priority takes preference over package version. Regards, Saurav ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] RFC: Post build configuration
This is in reference to my previous post regarding post build configuration, with few points re-iterating to set the ground. https://lists.yoctoproject.org/pipermail/yocto/2012-November/012867.html Post build configuration and need for configuration platform/model: There have been several discussions regarding need for image format, file system and disk configuration, network, users addition etc. Most are of these features are configurable in other distributions like opensuse, fedora during the image installation on the target. Considering the Embedded Linux distribution scenario, these features can be configured offline and the generated image can be directly deployed on the target. Example configuration options that can be supported include Configure the users/passwords Configure the network Configure the host name Select the services to be started by default Security related configuration Configure image formats ramfs/ext3/... paritions,disk management etc Serial port configuration etc.. Also a userscenario include Offline Binary Configuration, which allows a binary image customization before making a final target image. This case will be more evident in larger companies, where platform teams, product teams, application teams are distributed and Linux build from source will be owned and lab tested by a single team, like platform team. Other teams just configure to use it for product variants from same platform build. As configuration needs and options vary based on packages/features selected during for the distribution, so there is a need for a configuration platform/model 1) which allows new configuration options can be added easily and each package/distribution knows how it can be configured, so that selection of package or feature will expose those configuration options to the user. 2) Tools like HOB and Webhob also need a clean configuration interface to configure the image. 3) This can be extended to support Generic configuration UI like kernel menuconfig. Considering the above Post build configuration in mind, I like to put forward a model (high level flow) detailing 1. How the configuration functions/logic are maintained in poky? 2. How is configuration functions shipped along with image? 3. How configuration functions are used by configuration tool(s) to apply them over binary image, based on user configuration inputs? 1. How the configuration functions/logic are maintained in poky? --- Various configuration functions supporting the distribution configuration needs are maintained in current poky layers. a) Configuration functions include Image level and package level configuration functions. Where package level configuration functions kept along with package recipe(say pkgname_version.cfg). b) Package level configuration functions can override the image level configuration functions. Example: Useradd logic need to be different, if busybox is selected or if pwdutils package is selected. c) Each layer can override configuration functions, just like bb files. d) Menu Definition Information contains the metadata about configuration functions and their parameters allowing it to represent it in Generic UI, is also kept along with configuration functions. Menu definition Information can be represented in Menu Definition Language (MDL, say xml based). 2. How is configuration functions shipped along with image? - Configuration Library (ConfigLib) is created from configuration functions and MDL (from step1) during the package build time. ConfigLib is based on build time packages and features selected. This configuration Library is added to package feed. 3. How configuration functions are used by configuration tool(s) to apply them over binary image, based on user input/need? --- New tool can be created or existing tool(s) can be extended to support Post build package selection, image generation and configuration. Its functionality includes a) Selection of packages from package feed. b) Install the selected packages to relocatable rootfs. c) Copy configuration functions corresponding to selected packages from ConfigLib to SelectedConfigLib. d) User can configure the image by - Manually modifying offline configuration file (oct.conf) - Using a generic configuration UI which generates offline configuration file (oct.conf) e) Tool reads the offline configuration file(oct.conf) and maps the user configuration inputs to configuration functions in SelectedConfigLib. It applies the configuration options on the
[yocto] New OE layer index now available
Hi folks, There is a new index for OpenEmbedded layers available here: http://layers.openembedded.org It can be used to browse and search for existing layers, as well as the recipes and machines contained within them. In addition to the short description, repository location and usage link we were collecting in the existing wiki, we can now store information on maintainers, layer dependencies, and the associated mailing list, as well as a longer description. New layers can be submitted easily using a simple form which does not require a login. I've imported all the data from the existing index on the OE wiki and filled in the blanks by hand - please check the entries for your layers and if I've missed anything or entered something incorrectly, please let me know (reply off-list) and I'll fix it; alternatively if you're already listed as the maintainer of a layer you can create an account with the same email address and you'll be able to edit the entry yourself at any time. The index also supports multiple branches, but for the moment there is only a master branch configured as I'd like to have people check the layer data before adding the additional stable branches (danny and denzil). Feedback on the new site is welcome. The code is also available in case you want to take a look / improve something - see the TODO file for possible future improvements: http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/ Once people have had a chance to give feedback I'll replace the content of the existing OE wiki page with a link to the new index. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] New OE layer index now available
On Fri, Mar 29, 2013 at 6:34 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: There is a new index for OpenEmbedded layers available here: http://layers.openembedded.org It can be used to browse and search for existing layers, as well as the recipes and machines contained within them. In addition to the short description, repository location and usage link we were collecting in the existing wiki, we can now store information on maintainers, layer dependencies, and the associated mailing list, as well as a longer description. New layers can be submitted easily using a simple form which does not require a login. I'd like to update some info in some layers I am the maintainer; how can I do it? -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] New OE layer index now available
On Friday 29 March 2013 18:58:09 Otavio Salvador wrote: On Fri, Mar 29, 2013 at 6:34 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: There is a new index for OpenEmbedded layers available here: http://layers.openembedded.org It can be used to browse and search for existing layers, as well as the recipes and machines contained within them. In addition to the short description, repository location and usage link we were collecting in the existing wiki, we can now store information on maintainers, layer dependencies, and the associated mailing list, as well as a longer description. New layers can be submitted easily using a simple form which does not require a login. I'd like to update some info in some layers I am the maintainer; how can I do it? Just click on login in the top right hand corner, then on Create one now, enter your details, you'll need to confirm your email, then you should be able to log in and then click on the Edit button on the layer info page. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem creating bootable flash
I'm still having no luck booting my system. I've built core-image-base-cedartrail-nopvr, with only one modification (added samba from OE), and I'm trying to boot it on an Intel DN2800MT mobo from a 1GB eUSB SSD. Here's what I've done: Opened gparted, selected /dev/sdb, which is the SSD. Created a fresh MSDOS partition table. Selected the 979MB unallocated space, created a new 949MB FAT16 partition. Selected the remaining 30MB unallocated space, created a new FAT16 partition, which will hold my application data. Invoked the pending operations. Selected the first partition, set the boot flag. Exited gparted. In terminal, went into my images directory, and did sudo dd if=core-image-base-cedartrail-nopvr.hddimg of=/dev/sdb1 After a few seconds, it finished. I then unplugged and plugged the SSD from the USB header, and it automounted the two partitions and popped up two windows showing their contents. Closed the second one, and examined the first one. It contained the usual five files for booting a live image. Opened syslinux.cfg in an editor. It showed that syslinux is configured to use a serial port, which is wrong for my system. Also, it showed two boot choices, one called boot for running the live image, and the other called install. Eventually, I'll get the build to supply a custom syslinux.cfg, but for now, I figured I'd just manually edit it. Since I want it to interact with the screen and keyboard, and not a serial port, I removed serial 1 115200. The default is supposedly console 1, which I would expect would use the video and keyboard from the text mode it inherits from the BIOS. I also removed the install section. The options on the minimal boot kernel included console=ttyS0,115200 and console=tty0 video=vesafb vga=0x318. Since I don't know what my mobo supports for VGA video, I figured I'd just let it use text mode, so I replaced them both with just console=tty0. The final contents of syslinux.cfg were: ALLOWOPTIONS 1 DEFAULT boot TIMEOUT 10 PROMPT 1 LABEL boot KERNEL /vmlinuz APPEND initrd=/initrd LABEL=boot root=/dev/ram0 console=tty0 I did a Safely remove on the device, unplugged it, plugged it into my test motherboard, and fired it up. I went into the BIOS boot menu, to make sure the BIOS recognized it as a bootable device, and it did. I hit Enter to boot it. All I got was a standard black VGA text mode screen with a blinking gray cursor. At that point, Ctrl-Alt-Del wouldn't reboot. If my device wasn't bootable, I'd expect the BIOS to complain. If it was still in the BIOS, I'd expect to be able to reboot with Ctrl-Alt-Del. If it actually ran ldlinux.sys, and yet didn't properly use the video, I'd expect it to time out and boot the live image. But I don't see any evidence that it's doing that. Does my syslinux.cfg look correct for showing the syslinux stuff on the text mode output? Do my kernel options look correct for getting the live image boot kernel to talk to the screen in text mode? Can anyone see anything else that might be wrong? -- Ciao, Paul D. DeRocco Paulmailto:pdero...@ix.netcom.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
