Age | Commit message (Collapse) | Author | Files |
|
The 3.4 kernel is released, and is the default for qemu* builds, so
we can safely update the default libc-headers version to 3.4.
Built and booted for qemu*
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Remove a stray character at the end of the meta SRCREV.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating the kern-tools SRCREV to pick up the following fix:
Out of tree feature descriptions (.scc files) take two forms: normal
features and BSP descriptions.
A normal feature is detected and added to the end of the current machine
being processed. During tree processing, it's configuration and patches
will be applied.
A BSP description on the other hand must be matched based on three
critera (which are in the .scc file via "define <foo>"):
- machine
- kernel type
- architecture
Since features that define machines are only explicitly added, they
are removed from the list of features that should be automatically
added.
The criteria for removing them from the auto-add list is the
definitions found in the .scc file. The existing check was simply
for KMACHINE anywhere in the file. This meant that a conditional
or even a comment containing that phrase would exclude a file.
Properly anchoring the KMACHINE test to "^define.*KMACHINE" fixes the
problem of overly agreesive exclusions.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating meta to move Kernel Features out of the BSP and add to
the Cedartrail Machine branch.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Bumping the 3.2 SRCREVs to pickup the following configuration changes for
the new chiefriver BSP and the existing fri2 machines:
5b4c9dc fri2: update base config
cdfbb50 fri2: add usb-mass-storage to standard and preempt-rt
3c1af06 fri2 update: drop NETDEVICE, e1xxx, usb-mass-storage, add iwlwifi feature
26a4d79 iwlagn: Correct a comment typo
ade9c57 iwlwifi: Add a feature for iwlwifi
571b6cb fri2: Configuration update (usb, wifi, i2c)
b257485 meta: add tmp/rc6 feature
24c6494 chiefriver: create initial BSP infrastructure
All branches are also updated with the following fix:
1ce6700 efi: Add patch to fix 32bit EFI service mapping (rhbz 726701)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Introducing the 3.4 kernel recipe. At this point there are three
supported kernel 3.4, 3.2 and 3.0.
Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and
qemuppc
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
To avoid mapping machine names to kernel machine names in recipes,
we can define multiple KMACHINE names for a single in tree board.
This allows the tools to match a board description to multiple
different MACHINEs.
As a result, we can remove the explicit KMACHINE mappings from
the linux-yocto recipes and allow the KMACHINE=${MACHINE} default
to handle mappings. Individual recipes an bbappends can override
this as required.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
With the introduction of the 3.4 kernel recipe, the 2.6.37 kernel
recipe is removed, keeping the supported list at three kernels.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating the 3.0 kernel SRCREVs to integrate the v3.0.32 -stable
release.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating the 3.2 kernel SRCREVs to pickup the -stable update
to v3.2.18.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating the kern-tools SRCREV to pick up fixes that remove unused
code, transition code (tree format changes) and to remove assumptions
about branch and directory naming.
There are no user visible changes with this update, but the plumbing
changes will be used in future updates for more generalized support.
The commit details are below:
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Fri May 11 12:13:12 2012 -0400
kgit-publish: remove --remote option
The ability to publish and automatically push a repository was
never used, and is error prone. The complexit isn't needed in
the script, so removing it is the best option.
An explicit push after tree publication is suggested, or a
wrapper script (specific to a particular infrastructure) around
this script.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Fri May 11 12:04:09 2012 -0400
kern-tools: remove unused code, scripts and transition code
The period of supporting old trees with a different meta
branch name and directory structure are gone. So the cleanup
and removal of the old structure can be completed.
The meta branch and directory are now controlled via command line,
or via the KMETA environment variable. No testing and conditional
processing of the tree are required.
Additionally, the generate_cfg script is no longer used, or is the
branch conditing code in createme. So they can be safely removed
from the tools and repository.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Thu May 10 12:18:19 2012 -0400
kern-tools: remove meta tag and directory assumptions
During repository sanity checks (createme) and during the
checkpoint process, there were several assumptions about the tree
that either relied on a tag, or a particular directory name.
With this set of changes, simply passing the meta branch name is
enough to sanitize and restore the checkpoint. If no meta branch
name is passed, the default of 'meta' is used for both the branch
and meta data directory name.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
* discussed on [1]
* patch sent to systemtap [2]
[1] http://lists.linuxtogo.org/pipermail/openembedded-core/2012-June/023377.html
[2] http://sourceware.org/ml/systemtap/2012-q2/msg00202.html
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Without this, the installed files get mangled when a dash shell is used.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
|
Removed patch for ARM compilation, as it seems that the upstream fixed
the ARM compilation problem in a slightly different way (tested by compiling
lttng-tools for MACHINE=qemuarm)
Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
|
|
Tested with 'lttv' on core-image-lsb.
Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
|
|
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
Updating the meta SRCREVs to pickup configuration policy cleanups:
49f931b meta/fishriver: remove redundant features and options
51a6d3f meta/emenlow: remove redundant features and options
101dd7f meta/crownbay: remove redundant features and options
4110ecd meta/sugarbay: remove redundant features and options
0f1304a meta/jasperforest: remove redundant features and options
0a56a3b meta/common-pc-64: factor out SCSI CDROM option
b71938a meta/common-pc-64: use usb-mass-storage feature
0724f40 meta: add scsi cdrom feature
438bca8 meta/common-pc: use usb-mass-storage feature
c970881 meta: factor out SCSI options from the usb-mass-storage feature
4c8135e meta: add scsi disk feature
6872a81 meta: add scsi feature
e706ec5 meta/sugarbay: factor out policy-related options
8b7fbc2 meta/jasperforest: factor out policy-related options
fea1b0e meta/fishriver: factor out policy-related options
13bf9ab meta/emenlow: factor out policy-related options
4748d50 meta/crownbay: factor out policy-related options
44f592f meta/common-pc-64: factor out policy-related options
5a3f5c7 meta/common-pc: factor out policy-related options
1f5a10b meta/common-pc-64: use usb features
4b87723 meta/common-pc: use usb features
594ba05 meta: add ROOT_HUB_TT config option to the usb/ehci-hcd feature
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The LICENSE field for kern-tools was generic and leads to QA warnings
from the license classs:
"No generic license file exists for: GPL in any provider"
Updating to a specific GPL version that matches the source fixes the
warning.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating the meta SRCREV for the following fixes:
1dfd60f meta/fishriver: move smp options from recipe-space
012780a meta/emenlow: move smp options from recipe-space
b59b1a5 meta/crownbay: move smp options from recipe-space
74dc6ac meta/sugarbay: remove boot-live options
a4bedcb meta/jasperforest: remove boot-live options
4ae7b81 meta/sugarbay: use usb features
30e7e8c meta/jasperforest: use usb features
22d0c5d meta/fishriver: use usb features
e262965 meta/emenlow: use usb features
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The commit breaks pkgconfig and after discussing it with the kmod and udev maintainers the conclusion was reached that putting the libraries in /lib instead of /usr/lib is not supported.
This reverts commit 6b74f2461735272bd950a4f060dab6e778a36f92.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
* PROVIDES does not need _${PN}
* CONFLICTS should be RCONFLICTS
* opkg needs RREPLACES to automatically remove older module-init-tools
instead of just reporting it conflicts with kmod
SHR root@gjama ~ $ opkg install kmod
Installing kmod (7+git02629fa02e96763db7460a930239cc93649a52f8-r0.0) to root...
Downloading http://jama.dyndns-home.com/org.openembedded.shr-core//armv4t/kmod_7+git02629fa02e96763db7460a930239cc93649a52f8-r0.0_armv4t.ipk.
Removing package module-init-tools-depmod from root...
update-alternatives: removing //sbin/depmod as no more alternatives exist for it
Removing package module-init-tools from root...
update-alternatives: Linking //sbin/insmod to ../bin/busybox
update-alternatives: Linking //sbin/modprobe to ../bin/busybox
update-alternatives: Linking //sbin/rmmod to ../bin/busybox
update-alternatives: removing //sbin/modinfo as no more alternatives exist for it
update-alternatives: removing //bin/lsmod as no more alternatives exist for it
update-alternatives: Linking //sbin/lsmod to ../bin/busybox
Configuring kmod.
update-alternatives: Linking //sbin/insmod to /sbin/insmod.kmod
update-alternatives: Linking //sbin/modprobe to /sbin/modprobe.kmod
update-alternatives: Linking //sbin/rmmod to /sbin/rmmod.kmod
update-alternatives: Linking //sbin/modinfo to /sbin/modinfo.kmod
update-alternatives: Linking //bin/lsmod to /bin/lsmod.kmod
update-alternatives: Linking //sbin/lsmod to /bin/lsmod.kmod
update-alternatives: Linking //sbin/depmod to /sbin/depmod.kmod
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This also helps avoid QA errors about binaries
accessing contents from /usr/lib
Also fixes emptry libkmod problem since now
the files are installed in expected place
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
The linux-yocto repository and scripts can support a mode of
meta data management that merges a base meta branch to every
BSP branch. In this case, the scripts don't have to restore
a checkpoint for the meta data to be globally accessible.
The decision to restore or not is made based on whether or
not the meta branch is part of all branches or not.
The linux-yocto recipes have a sanity check to determine if
the requested SRCREV for meta data matches the head of the
meta branch (via do_validate_branches). If the wrong commit
is at the head, the meta branch is moved aside and the branch
reset to the right commit. This creates two meta branches that
contain the base meta data.
The test for integrated meta data mistakes this for a globally
merged set of meta data and doesn't restore the checkpoint, which
leads to build failures.
The immediate fix is to allow two branches to have the meta
data. The long term fix is to make the detection only consider
if the build branch contains the meta data.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
* until it's decided it should be installed in base_libdir or libdir
* fixes libkmod packaging
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating the SRCREV to pick up two minor fixes:
1/2:
kgit-init: correct spelling of createme
kgit-init copies the kern-tools scripts and intends to copy createme.
The typo is in the usage() of updateme as well.
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
2/2:
kconf_check: fix bad quoting around missing_required.cfg
missing_required.cfg won't have it's path truncated (if applicable), since
the quoting it wrong.
Signed-off-by: Andrea Adami <andrea.adami@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
In order to support repositories of various types (with or without
meta data, branched, pristine, custom, etc) information about the
type of processing that is required was passed to the processing
phases via variables.
The combination of variables involved in coordinating the processing
creates a learning curve and overly complicates recipe extensions.
With minor tweaks to the kern-tools, adding flexibility and keying
off the existence of the meta branch it is possible to remove all
of the variables that were added to support different repository
types.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Updating the 3.2 SRCREVs to import the following meta/config
changes:
6b3d4e0 meta: add mei feature
519abac meta: add usb/uhci-hcd feature
a67c5a3 meta/crownbay: use usb features
0855066 meta: add usb/ohci-hcd feature
15f1a99 meta: add usb/ehci-hcd feature
8fa6408 meta: add usb/xhci-hcd feature
c724a55 meta: add usb/base feature
b55b3a1 sys940x: Cleanup sys940x.scc
93f2e97 sys940x: Use PHYSICAL_START of 0x200000 to boot
aaa034b sys940x: Add common standard and preempt-rt features
e2b1286 sys940x: Add efi-ext to standard and preempt-rt configs
d188c21 sys940x: Move emgd-1.10 data to the standard scc file
72d9369 fri2: Cleanup fri2-$KTYPE.scc files re efi-ext.scc
dbcb120 fri2: Use emgd-1.10 feature and branch
And the following driver fix:
f39a0a9 pch_gbe: Do not abort probe on bad MAC
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Since its provided by kmod
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
kmod is replacement for module-init-tools
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
Updating the meta SRCREVs to pickup the following meta change for the
3.0 and 3.2 kernels:
[
meta: Clean up BSPs kernel config
Clean up some QEMU and non-x86 BSPs kernel config, including
qemuarm
qemuppc
qemux86
beagleboard
mpc8315e_rdb
Only obsolete/invalid kernel configs are removed.
Signed-off-by: Yang Shi <yang.shi@windriver.com>
]
With this commit, the configuration audit for the qemu and hardware
reference boards is (largely) warning free.
Signed-off-by: Yang Shi <yang.shi@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating the meta SRCREV for both the 3.0 and 3.2 kernel trees to
pickup the beagleboard xM boot fix:
[
meta/beagleboard: disable CONFIG_PREEMPT
The boot hangs with the message:
mmc0: error -110 whilst initialising SD card
The MMC driver has issues initializing when PREEMPT is enabled (either forced
or voluntary). Unplugging and then plugging the card back will reset the
driver and continue booting. Alternatively, disable preemption.
]
[YOCTO: #1892]
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
In fixing an existing patch migration bug, the list of valid extensions
got out of sync from the core patch class. As a result, valid patches
were not being applied to the tree.
Updating the tools to migrate .diff files fixes the issue.
Also in this fix is the removal of .patch in the find_sccs() routine, since
it will never be returned by patch.bbclass when all non-patches are
requested, it is simply confusing.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This allows systemtap-uprobes to build again after the recently
added patch broke the builds.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Building the systemtap documentation adds significantly to the build
time, so disable it by default.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
When building docs in systemtap, docproc is used to generate the
tapset documentation, but it gets built for the target, while it needs
to be build for the host instead. This change causes that to happen.
Fixes [YOCTO #2193].
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
During testing/extension of the linux-yocto-tiny kernel it was found that
defconfigs were not always properly applied. This was due to two issues:
- not being able to fully control the order of objects applied to the
git tree on the SRC_URI
- defconfigs triggering --allnoconfig before being applied
To fix this, the recipe space code that previously detected and generated
automatic features moves back to the kernel tools (where it was before) and
is updated to also process .cfg and defconfigs. Moving this back to the
tools allow other recipes to automatically benefit from the additional
support.
The second issue is addressed by allowing configme to take --alldefconfig
when a recipe wishes to pass a defconfig and override the default
behaviour.
Fixes [YOCTO: 2250]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating the 3.2 recipe SRCREVs to pickup the following meta change:
[
meta: Add igb.scc to Romley
Romley machine has 82580 Giga bit Ethernet Controller.
Add the relavent Nic driver to it.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The dtb files were not being installed into a location compatible with sstate and
the do_deploy task. This means in builds just using sstate, the dtb files disappeared.
This patch fixes the code to use the correct location for deploy files.
[YOCTO #2190]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Fixes [YOCTO #1501]
hello-mod is an example kernel module, and does not provide any real
functionality. As such, it would be better placed under meta-skeleton than
meta.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Recent Linux kernel tries to load the libertas firmware with the version
string in its name first. This results in a delayed firmware load on
system boot. Keep the default libertas firmware name and add a link for
older driver versions.
Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
|
|
Migrate linux-yocto-tiny from 3.0 to 3.2. The 3.0 recipe was
based entirely on recipe-space fragments and was only a proof of concept.
The 3.2 linux-yocto meta-data now has a proper tiny KTYPE defined.
By default this recipe supports only the qemux86 machine, which builds the
common-pc support (including networking, sound, USB, VGA and serial consoles,
etc.). New machines can be added and will use the tiny KTYPE, but will need to
add any desired hardware support as the base config is very minimal.
No filesystems are supported by default, only the initramfs.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating the META SRCREV to pickup these commits:
59f350e meta: Add common-pc-tiny.scc
0996ca9 tiny: Minimize the tiny config
d6b57bb meta: common-pc add dependencies to cfg
Which update the configuration for the tiny profile of the kernel
for the 3.2 release.
cc: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Updating the meta SRCREV to pick up this commit:
[
common-pc: Add PCNET32 to the config
Qemu and VM Ware both support PCNET32 and the latter requires it for
32 bit images.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
]
Signed-off-by: Darren Hart <dvhart@linux.intel.com>5A
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
* show warning for old /etc/modutils/* files without .conf extension
* v2: keep adding modules also from old /etc/modutils/* after showing
warning, this way update-modules will be backward compatible also on
images without kernel upgrade
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The linux-libc-headers-yocto is not required in oe-core, it can be
moved to yocto specific layers. The linux-libc-headers_* recipes
provide sufficient headers fore core users.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The 3.1 kernel was never released or directly supported via
oe-core. So as part of update the libc-headers to 3.2 we can
take the opportunity to remove it.
Built and booted on the qemu* targets.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|