summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* linux-yocto/3.8: qemumips graphical bootBruce Ashfield2013-04-103-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating the meta SRCREV to fix and illegal instruction that is seen when launching X with USB pointing devices. meta/qemumips: build USB_UHCI_HCD into the kernel When booting qemumips and USB_UHCI_HCD built as a module, the following trace is seen, and then prevents X from starting: qemumips user.warn kernel: Call Trace: qemumips user.warn kernel: [<c0028000>] uhci_check_bandwidth+0x0/0x160 [uhci_hcd] qemumips user.warn kernel: [<c002e08c>] uhci_urb_enqueue+0xba4/0xc48 [uhci_hcd] qemumips user.warn kernel: [<8058092c>] usb_hcd_submit_urb+0xdc/0x848 qemumips user.warn kernel: [<805b8fbc>] wacom_open+0x44/0x8c qemumips user.warn kernel: [<805a1990>] input_open_device+0xac/0xec qemumips user.warn kernel: [<805a8cec>] evdev_open+0x188/0x1bc qemumips user.warn kernel: [<802331d8>] chrdev_open+0xc8/0x1c4 qemumips user.warn kernel: [<8022b338>] do_dentry_open+0x248/0x2e4 qemumips user.warn kernel: [<8022b418>] finish_open+0x44/0x68 qemumips user.warn kernel: [<8023e51c>] do_last.isra.29+0x2c0/0xcbc qemumips user.warn kernel: [<8023efd8>] path_openat+0xc0/0x52c qemumips user.warn kernel: [<8023f840>] do_filp_open+0x4c/0xbc qemumips user.warn kernel: [<8022cc3c>] do_sys_open+0x128/0x20c qemumips user.warn kernel: [<8010c07c>] stack_done+0x20/0x44 qemumips user.warn kernel: Code: (Bad address in epc) qemumips user.warn kernel: ---[ end trace 8a48c6046870f8c2 ]--- Building the module into the kernel fixes the problem, but the root cause is still under investigation. The pipelines around jumps to module addresses seem to be triggering invalid instructions. (From OE-Core rev: b7b7ebe57bd6fd248e80be0b7e517a3ceb7cfd11) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.8: aufs, config processing, tiny, mips boot fixesBruce Ashfield2013-04-103-12/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating the SRCREVs to fix a number of bugs, boot issues and ktype support additions. standard/*: Aufs support was misplaced on the move from the -dev to release kernel, this commit restores the support. This is not active unless the aufs configuration items are enabled via the aufs-enable.scc feature. 11998bd aufs: core support f2ea9f4 aufs: standalone support bf529b6 aufs: aufs proc_map b6f0a04 aufs: aufs base support 55b0bc2 aufs: kbuild patch meta: The meta branch has updates for aufs enablement, tiny BSP configs, preempt-rt fixes and a wifi config audit fix. 4c567e0 meta/aufs: add -enable feature and patches 059fe88 meta/aufs: create aufs configuration fragment 7d672cd0 meta: add fri2 tiny BSP config. mti-malta32: This fixes the graphical boot of qemumips, the offending commit is breaking dynamic patching of ftrace on the simulation, so we revert the commit for now. 18c71ab Revert "ftrace/x86: Have x86 ftrace use the ftrace_modify_all_code()" mti-malta64: This enables the boot of qemumips64 by reverting the broken ftrace support for mips64 and by stubbing out inavlid oprofile register writes. 0ec615c Revert "ftrace/x86: Have x86 ftrace use the ftrace_modify_all_code()" bbefde3 oprofile/mips: do not set perf_irq for qemu mips 64 eb6cb79 Revert "MIPS: Function tracer: Fix broken function tracing" [YOCTO #4052] [YOCTO #4129] [YOCTO #2410] (From OE-Core rev: 3d88f61b59f0a07e199306bf3a15ab023e77e17d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: fix excluded configuration processingBruce Ashfield2013-04-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | One of the features introduced early on in the 1.4 release cycle was the ability to include a kernel feature, but only get its patches and not configs (and vice versa). As it turns out, this only was exercised recently and once a single include with dropped configs was started, ALL configuration values following the commit were dropped. To fix the problem, the processing of kernel features has been split into two. Where the features are preprocessed and the assembled/complete file is used to generate the meta-series (which is later applied to the tree). The logic of the tools is the same, but the two phases of processing allows configuration values to be excluded properly and simply, while keeping the logic for modifying the tree in a separate step. All changes are invisible to the user, and are done within the existing scripts and build system bindings. Output series and manipulations to the tree are the same as they were before this change. Updating the kern-tools SRCREV to pickup the kern-tools changes for this. (From OE-Core rev: 961ab0ac53de317c22409d90244a313998959714) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.8: atom-pc: Update atom-pc-preempt-rt.scc to reuse config from ↵Bruce Ashfield2013-04-102-2/+2
| | | | | | | | | | | | | | | | | | | common-pc Updating the meta branch SRCREV to pick up the following change: The atom-pc preempt-rt BSP was omitting the config from common-pc, resulting in very few drivers being built, including USB_STORAGE, preventing preliminary boot testing. Remove the "standard features" as those are covered by the common-pc scc files. (From OE-Core rev: 1e20b3cbc8da3e6729d3825c62422c0dd82e1577) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.8: fix atom-pc config audit warningsBruce Ashfield2013-04-102-2/+2
| | | | | | | | | | | | | | | | The atom-pc was referencing some invalid and unecessary config options that are causing kernel config audit warnings. With this SRCREV update, the configuration is clean against the 3.8 kernel. [YOCTO #3490] (From OE-Core rev: 9f3ff1f907a0cf65d8aff82134463c4321d4b1e2) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux/yocto: update AUTOFS configurationBruce Ashfield2013-04-102-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When systemd is enabled, qemumips failed to boot with the following trace: Reserved instruction in kernel code[#1]: Cpu 0 $ 0 : 00000000 80232500 c0011000 80000000 $ 4 : c0017440 00000000 87032400 8704b000 $ 8 : 00000000 00000000 00000010 003fffff $12 : 00000000 7fafbab4 00000000 87d6fbb0 $16 : 87f98780 c0017440 c0017440 00000000 $20 : 8704a000 00000000 8704a000 00000000 $24 : 00000010 80480630 $28 : 87c22000 87c23e28 7fafbc00 80232408 Hi : 00000000 Lo : 00000000 epc : c0011000 autofs_mount+0x0/0x30 [autofs4] Not tainted ra : 80232408 mount_fs+0x68/0x200 Status: 1000a403 KERNEL EXL IE Cause : d0808028 PrId : 00019300 (MIPS 24Kc) Modules linked in: autofs4 Process systemd (pid: 1, threadinfo=87c22000, task=87c28000, tls=77787490) Stack : 809b3e28 802512bc 00000000 808b0da4 87f3d310 87936c38 87032400 8704b000 87f98780 c0017440 00000020 8704b000 87032400 87032480 00000000 80251a2c 00000006 8022f7fc 87032480 802507f0 00000000 87032400 8704b000 7fafba94 00000000 c0017440 8088275c 80253f40 7fafb9d0 00000016 38513fac 0051b2a8 8704b000 801df604 00000000 0000000a 87f5c000 801f5968 87f3d310 87936c38 ... Call Trace: [<c0011000>] autofs_mount+0x0/0x30 [autofs4] [<80232408>] mount_fs+0x68/0x200 [<80251a2c>] vfs_kern_mount+0x68/0x114 [<80253f40>] do_mount+0x218/0x9d0 [<8025479c>] sys_mount+0xa4/0xec [<8010c07c>] stack_done+0x20/0x44 The policy of building AUTOFS as a module is something that can be changed, since boot processes that use automounting can take advantage of the built in support to reduce complexity. The size increase of the base policy is small with this change, and users of the linux-yocto kernel can still override this value, which is exactly what the poky-tiny kernel does. Keeping the configuration consistent for all boards, and not adding and exception for qemumips makes sense in this case. [YOCTO #4129] (From OE-Core rev: 3570cf11b7dfa6991c43bb041abb9d47cc6f0d70) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: fix read-only-rootfs-hook.sh to start earlierPaul Eggleton2013-04-102-1/+2
| | | | | | | | | | | Mount /var/volatile ourselves so that we can set up the writable area first. This fixes the urandom service not starting properly when read-only-rootfs is enabled. (From OE-Core rev: 44c7d8a27a84a04251408e9a7d9550629bc17704) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: fix read-only-rootfs-hook.sh to avoid using unionfsPaul Eggleton2013-04-101-11/+4
| | | | | | | | | | | Unionfs isn't available everywhere, and we can get similar results (if not quite as neatly) by using bind mounts + tmpfs and copying the data over. (From OE-Core rev: 5a8ba93efa554c3b4d3b48ca8d668419a8c77f42) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm-postinsts: avoid errors during boot with read-only-rootfs enabledPaul Eggleton2013-04-101-2/+5
| | | | | | | | | | | * If /etc/rpm-postinsts doesn't exist, don't error * If deleting the script errors, don't bother printing it (this will always happen if the root filesystem is read-only) (From OE-Core rev: f787b8302ed61bdaf1767473b856f31fe5bba28e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm-postinsts: don't create broken postinst scriptPaul Eggleton2013-04-101-4/+1
| | | | | | | | | | | | | | | | | | Not only was the variable reference in this line broken, but it wasn't going to work anyway - we install the script directly into /etc/rcS.d and not into /etc/init.d, so the code in update-rc.d.bbclass couldn't find anything there. This resulted in a postinstall script for rpm-postinsts being created in /etc/rpm-postinsts which can't work when the root filesystem is read-only. To simplify things just remove the use of update-rc.d.bbclass since we don't really need the added complexity here. Fixes [YOCTO #4222]. (From OE-Core rev: d196d08acafe599c16a7ac8e04121039b1216ba6) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tinylogin: Fix mix of tabs and spaces for SRC_URI indentationMartin Jansa2013-04-101-7/+7
| | | | | | (From OE-Core rev: f9d88a559dd2479893d7570676d42955ee3b8845) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: use update-alternatives.bbclassRadu Moisan2013-04-101-15/+21
| | | | | | | | | | switch from using plain update-alternatives command to update-alternatives.bbclass style (From OE-Core rev: 6e86da976d296b926b462e976d1f79f524f061b3) Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: fail on no mediaSaul Wold2013-04-102-1/+33
| | | | | | | | | | | | | | The current behaviour of busybox is to try all fstype when automounting even when no media exists. The util-linux mount command bails when no media exists, so change the behaviour of busybox to do the same. It could also be argued that the KERN_INFO message from btrfs could be removed, but that would be harder to accomplish. (From OE-Core rev: e5403f55a1e9b1747535450fd95f499c85211771) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* postinst-intercepts, qemu.bbclass: fix segfaults in postinstallsLaurentiu Palcu2013-04-104-5/+15
| | | | | | | | | | | | | | | | Postinstalls that use qemu are throwing a segmentation fault when building for qemux86-64 on a 64bit host (it might also happen for qemux86 if building on a 32bit host but I didn't test). It looks like qemu looks for ld.so.cache which is not found because it is generated after rootfs_(rpm|ipk|deb)_do_rootfs is called and then it tries to load libraries from the default paths (which are the host's). In order to avoid this, pass the LD_LIBRARY_PATH explicitly to the target's dynamic loader. (From OE-Core rev: 48e8b613b3f5c7b1d917bf3147606d44072ce49e) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* update-rc.d: correctly look up the initscript params with overridesRoss Burton2013-04-101-3/+9
| | | | | | | | | | | | | | The creation of a clone of d with extra OVERRIDES was removed in 72c1fd72d3b479c728e249eaa763116d352e945b but some of the lookups are essential so that variables such as ${INITSCRIPT_PARAMS} get overriden and resolved correctly on a per-package basis. [ YOCTO #3960 ] (From OE-Core rev: b016bc9aaabc90fe4dc98af8c5e73dfcb4526ef4) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initrdscripts: Add udev sbin based libexec pathRichard Purdie2013-04-102-2/+2
| | | | | | | | | | | For better or worse we need to use base_sbindir for udev's libexec dir. This updates the initrdscripts to also cover the new location. I'd prevously assumed that it was already covered but its not. udev internal binaries shouldn't be in PATH so we have to do this to deal with the issue. (From OE-Core rev: 7e17cba75c20ad820d30128d9b4b0132e7b924a8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/license: remove outdated commentPaul Eggleton2013-04-101-1/+0
| | | | | | | | | Package listing was implemented in the deb backend some time ago. (From OE-Core rev: e2915b6e1d2088d3a791bf629dabc58f38940961) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-*/conf/layer.conf: tweak BBFILES commentPaul Eggleton2013-04-101-1/+1
| | | | | | | | | | "packages" was the old name (pre-2010) under which the recipe files were stored. (From OE-Core rev: c71fa87bc2e7155e69ea5ff7a284a05073602eed) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/recipes.txt: add recipes-lsb4Paul Eggleton2013-04-101-0/+1
| | | | | | | (From OE-Core rev: 79c2845b12a53d9cdcf4f7beacd09db7ee1ae2bc) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev: fix init script for the location of udevdSaul Wold2013-04-093-3/+5
| | | | | | | | | Ensure we can update the script base don the location of the udevd installation (From OE-Core rev: 25ff5960e41b9d7c62b05a08dd77cf11390962a1) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd.bbclass: restart service in postinst, not startRoss Burton2013-04-091-1/+1
| | | | | | | | | | | | | | | | | When upgrading packages it's possible that the service is already running because opkg doesn't actually execute the prerm hooks on upgrades, which is where the service should be stopped. Handle this case by restarting in postinst instead of starting. If the service isn't already running then this doesn't make a difference, but if it is running then the service will be restarted. [ YOCTO #4213 ] (From OE-Core rev: 319ef0df4ae7ed0372eff90e11244123eccb023c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev: Move udevd back to /sbinRadu Moisan2013-04-092-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | Along with v182 upgrade udevd was moved to ${base_libdir} making scripts like init-live.sh to fail in finding udevd. We have some problems here since the placing binaries into either libdir breaks the way our multilib handling works. That code and its associated sanity tests assume that libdir contains binaries of a particular architecture and that these are not allowed to overlap. This is in contrast to the bindirs where conflicts are expected and handled appropriately. So whilst upstream may desire this directory layout, it won't work for OE's usage of it and we need to configure udev differently. The scripts already have fallback code to handle udev in the two locations so there is no issue is going back to our previous layout. [Yocto #4046] (From OE-Core rev: a866e1e298dab5c52e7b8ba9ab68104604511713) Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Fix matching of MACHINEOVERRIDES in COMPATIBLE_MACHINEOtavio Salvador2013-04-091-5/+6
| | | | | | | | | | | | | | | | | | | The use of SOC_FAMILY here is old code and SOC_FAMILY is now implemented by MACHINEOVERRIDES behind the scenes. It therefore makes more sense to use the replacement value in this code. Just like SOC_FAMILY, this is a ":" delimited variable so we should iterate over the components, not use the value directly. Finally, MACHINEOVERRIDES contains MACHINE so we don't need to check that directly. This makes the functionality match what most users would expect it to do and is also compatible with the way things previously worked. (From OE-Core rev: 8ceef74dd4f662b4c7e3c170ce486e966ebebeff) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpng12: remove prefer version and add it to lsb packagegroupKang Kai2013-04-092-3/+1
| | | | | | | | | | Because rename libpng_1.2.50 to libpng, remove the perfer verion from default-versions.inc and add libpng12 to lsb packagegroup. (From OE-Core rev: 01fa98083df0931e07e8715616dafe600258adba) Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpng12: rename libpng_1.2.50 to libpng12Kang Kai2013-04-091-3/+17
| | | | | | | | | | | | | | | | | | | As Mark's suggestion, rename libpng_1.2.50 to libpng12 that multi-versions libpng could coexist. We want to make sure we have both the old and new versions to meet LSB compliance (for people who have that enabled) as well as the new version for newer applications. And drop link files that conflict with higher version. [YOCTO #4221] (From OE-Core rev: fc626e6861e491b0144b813a5b48b0f5f57664e6) Signed-off-by: Kang Kai <kai.kang@windriver.com> CC: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: Upgrade to v1.0.1eRadu Moisan2013-04-0920-387/+482
| | | | | | | | | | | | | | | | | Dropped obolete patches and pulled updates for debian patches. Addresses CVEs: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-2686 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0166 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0169 [YOCTO #3965] (From OE-Core rev: 0470edd01c0aebaa78db137e365a7e22bfb199e9) Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/buildhistory: fix interaction with rm_workPaul Eggleton2013-04-091-3/+2
| | | | | | | | | | | Change do_write_srcrevs to a postfunc of do_fetch, avoiding a dependency being created that causes large numbers of setscene tasks being executed on every build with both buildhistory and rm_work being enabled. (From OE-Core rev: a751e9042dfffcc5c4701634a1f1f598012d609c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: fix RDEPENDSLaurentiu Palcu2013-04-091-3/+1
| | | | | | | | | The rpm-postinsts runtime dependency was overwritten. (From OE-Core rev: 834ea4ed891c874e0336abb8f0b96664250208c9) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Add backported patch to address random segfaultsRichard Purdie2013-04-092-0/+44
| | | | | | | | | | | | We've been seeing random sefgaults on a variety of architectures which appear to be from an issue in qemu. The attached backport from upstream appears to fix these. [YOCTO #4216] (From OE-Core rev: 55a22b7341571179d5e026d102953a6d9f2045bf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-tools: Fix sys/io.h patchSaul Wold2013-04-081-1/+4
| | | | | | | | | I blew my #if expression! (From OE-Core rev: b458309845185a3cd473daa0969ce17e2ff5c602) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass: do_sizecheck: update path to build image and do not deleteMichel Thebeau2013-04-081-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | do_sizecheck has a few issues especially with vmlinux image type. It breaks because KERNEL_OUTPUT is a path relative to ${B}. When do_sizecheck runs it does not find the file (because the working directory is elsewhere) and does not fail. Also, the image file referenced by KERNEL_OUTPUT may be a link. Finally, when do_sizecheck deletes the oversized kernel image it leaves the previously run do_compile task with inaccurate status. So, do the following: - specify that the working directory should be ${B} - use ls -L to reference to the real file, and ensure that the link file is created - keep the oversized image file so the status of do_compile is valid [YOCTO #3514] (From OE-Core rev: f0b19ddce3c92c5d06976cf73d4c4c480e053dff) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: add systemd-serialgetty to SIGGEN_EXCLUDERECIPES_ABISAFEMartin Jansa2013-04-081-0/+1
| | | | | | | | | | * it was imported from meta-systemd without SIGGEN_EXCLUDERECIPES_ABISAFE change (From OE-Core rev: 40c6090e67fe4def94223954e4ada01115f267dd) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez4: add readline dependencyAlexandru DAMIAN2013-04-081-1/+1
| | | | | | | | | | | bluez4 uses readline to be build, but the dependency is not listed This is listed in the configuration log. So we add it. (From OE-Core rev: 99194be0332ac35da729ec53a2cc423cc520db28) Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: Set the default firmware path to enable firmware loading in udevHolger Hans Peter Freyther2013-04-082-0/+101
| | | | | | | | | | | After some breakage in udev the kernel gained direct firmware loading. For older kernels (e.g. 3.2 in my case) udev still needs to load the firmware. Firmware loading is enabled once a default firmware path is set. Apply a compile fix from the upstream project. (From OE-Core rev: 2009c6899d7d4ddd71350b1026a27336dc3a94b8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcf-agent: Use kill instead of killproc to stop agentIoana Grigoropol2013-04-082-3/+5
| | | | | | | | | | | | | | | | When shutting down a core-image-lsb-sdk image, there is a lot of time spend stopping tcf-agent, which slows down the whole process. The reason for this slowdown is the fact that it tries in a loop to kill tcf-agent service by using killproc with the path of the executable and killproc does not seem to available in lsb images. This patch fixes the issue by using "kill" instead of "killproc". [Yocto #3928] (From OE-Core rev: 251361eb78176a04e3da00e0f77b7f3ff459d571) Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* smart: disable CHANNELSDIRBogdan Marinescu2013-04-082-1/+26
| | | | | | | | | | | | Make CHANNELSDIR in smart empty, since this causes host contamination issues on some RPM-based hosts on which smart is already installed. [YOCTO #3881] (From OE-Core rev: 94e76a98b6cdafe9547630be159401ac1d8c5edd) Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-update-icon-cache-native: create wrapper scriptLaurentiu Palcu2013-04-081-0/+4
| | | | | | | | | | | When using the sstate from another build machine, the path to the pixbuf loader's cache points to a path on the remote machine. Hence, the update of the icon cache fails on host. (From OE-Core rev: f2cb906bdce08441a20eab927ca9e2a2a9735ed0) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: fix postinstall intercepts fallbackLaurentiu Palcu2013-04-081-1/+1
| | | | | | | | | | The wrong type of paranthesis was used so 'continue' did nothing (was in another context) and the packages were marked as installed. (From OE-Core rev: 0bdde53e885aae3506c7b070b6e21f64a7cd4115) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gst-ffmpeg: fix --disable-yasmTom Zanussi2013-04-081-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | The gst-ffmpeg build shows the following warning: configure: WARNING: unrecognized options: --disable-yasm which means that the following test in configure always fails and --disable-yasm never gets passed to the embedded ffmpeg build: 'if test "x$disable_yasm" = "xyes"; then' embffmpeg_configure_args="$embffmpeg_configure_args --disable-yasm" commit 4d309730 ['gst-ffmpeg: configure-fix patch used wrong test'] actually fixed the obviously backwards syntax by reversing the test - prior to that, --disable-yasm would always unconditionally be passed into the embedded ffmpeg config. This fixes things so that the variable actually exists and makes the test meaningful. (From OE-Core rev: da9515621134c26e54f43b96cdad0c6e6c5876bf) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* insane.bbclass: Updated MicroBlaze machine definitionsNathan Rossi2013-04-081-2/+2
| | | | | | | | | | | | | | * Removed existing definition with machine 47787, this definition is outdated, a sanity error should occur if an ELF uses this value. * Added new definition with machine 189. This value replaces the existing value since August 2009. See binutils thread for more information. (http://sourceware.org/ml/binutils/2009-08/msg00127.html) (From OE-Core rev: 0c60d3b04eb77629abc3bbc2a6d8a2b8f0a44309) Signed-off-by: Nathan Rossi <nathan.rossi@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* curl: backport patch to fix segfaultsMartin Jansa2013-04-052-1/+172
| | | | | | | | | * e.g. ecore, efreet segfault a lot without this patch (From OE-Core rev: b93011d3e719c46089ccdb39c60d3a9e9cfa5a14) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto-tiny: Add 3.8.4 recipeDarren Hart2013-04-051-0/+26
| | | | | | | | | Bring linux-yocto-tiny up to the latest linux-yocto 3.8.4 version. (From OE-Core rev: f2a2256f08287baac9cf1f9fd58b5b8244c09610) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: make the main package depend on all sub-packagesRoss Burton2013-04-051-0/+6
| | | | | | | | | | | | | Whilst splitting out specific large firmware blobs is a good move for space saving, it makes installing "all the firmware" tricky. Make linux-firmware depend on all of the separated packages so that installing that pulls in all of the sub-packages. (From OE-Core rev: 644dfe0b13f68a04bdde67b5f1bf210bbe8ab918) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow: add patch to fix crypt: Invalid ArgumentSaul Wold2013-04-052-0/+64
| | | | | | | | | | | | | This patch came from Slackware and address a change in crypt()'s handling of an invalid seed, which in the past returned an encrypted string and now returns a NULL. [YOCTO #4097] related to tinylogin segfault (From OE-Core rev: a7f7e6da8383b4bde6d8ce951e5c3c955073c0bd) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tinylogin: fix segfault from crypt()Saul Wold2013-04-052-1/+26
| | | | | | | | | | | | | | | | In glibc 2.17, crypt() now expects 2 valid chars for the seed or it will error out and return a NULL. The tinylogin code took the result from crypt directly into a strcmp() which caused a segfault Tinylogin has been deperacted, busybox now has login support, I will investigate using busybox login support for 1.5. [YOCTO #4097] (From OE-Core rev: 03034e0f5dff426ee7adaa2364082dd47c23260a) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/classextend.py: avoid extending any kernel packagePaul Eggleton2013-04-051-1/+1
| | | | | | | | | | | | | For multilib and other uses of classextend, we don't want any dependencies on kernel packages to be extended since there should only be one kernel variant. Fixes [YOCTO #2918] (where kernel-dev was being extended.) (From OE-Core rev: b684c0f0d5d93f5147dee79951647eb3ddf4c840) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* postinst-intercepts, qemu.bbclass: fix issue on 32 bit hostsLaurentiu Palcu2013-04-051-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The intercept scripts fail to run on 32 bit hosts. Apparently, the current approach worked on 64 bit hosts due to the larger virtual address space (probably). On 32 bit hosts, however, calling the target binary like: qemu-arm ld-linux.so --library-path /lib:/usr/lib arm_binary fails with: arm_binary: error while loading shared libraries: arm_binary: failed to map segment from shared object: Operation not permitted When run like this, qemu-arm fails to map the arm_binary executable in memory because it's hitting the lower limit of /proc/sys/vm/mmap_min_addr. That's because it loads the ld-linux.so binary successfully, taking into account mmap_min_addr, runs it, and then ld-linux.so will map the arm_binary at a fixed address but this will fail because it is below mmap_min_addr. The qemu's guest base probing, apparently, doesn't work fine when a program runs inside other. One way around this would be to set mmap_min_addr to 0 (on recent distributions is set to 65536 to avoid "kernel NULL pointer dereference" defects) but this approach is not safe. The other way is to call the binary directly but providing qemu with a prefix (-L option) in order to find the elf interpreter correctly. This way, both the target binary and dynamic loader are mapped into memory under qemu's control and, only after, the dynamic loader is started. [YOCTO #4179] (From OE-Core rev: 78f91e08c8a7b0f0c831a087f7c89e2c76047e7a) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* site/common-uclibc: add predefined configure vars for coreutilsHenning Heinold2013-04-051-0/+5
| | | | | | | | | | * this sets some configure vars which will be guessed false in cross-compile case for uclibc (From OE-Core rev: c5337326005c975425b1eb2b62796e9b33f72ac3) Signed-off-by: Henning Heinold <heinold@inf.fu-berlin.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* site: add endianness information for libmemcachedMarcin Juszkiewicz2013-04-042-0/+5
| | | | | | | (From OE-Core rev: 2587a33134fde80dd1367629d9def45ac70256ee) Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus: set INHIBIT_UPDATERCD_BBCLASS without sysvinit in featuresMartin Jansa2013-04-041-0/+6
| | | | | | | | | | | | * fixes udev configure in run-postinsts failing with: update-rc.d: /etc/init.d/dbus-1: file does not exist because dbus-udev is installed only with sysvinit in features but update-rc.d was always called from PN postinst (From OE-Core rev: f15192a65e02026308253e6723b990b24780be5b) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 16:46:31 +0000