| Age | Commit message (Collapse) | Author | Files |
|---|
|
The special key kernel-module- is necessary for the system to avoid a package
rename when installing a multilib image. For example:
local.conf: IMAGE_INSTALL_append = " hello-mod"
bitbake lib32-core-image-minimal
The system will translate names and prepend 'lib32-', unless the package
begins with kernel-module-.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
"packages" was the old name (pre-2010) under which the recipe files were
stored.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
bitbake handles immediate expansions of LAYERDIR for us automatically.
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Add LAYERVERSION and LAYERDEPENDS to following oe-core layers:
meta-hob, meta-skeleton
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
It is necessary to supply file://defconfig to the SRC_URI when using
a defconfig (it is not implicitly understood as the commentary might
currently suggest).
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
There has been some confusion over proper use of the linux-yocto-custom
recipe. It is not intended to build as is from meta-skeleton. It should
be modified via a bbappend file to provide a Linux kernel config at the
very least.
Update the commentary to make this requirement more explicit. Add some
additional detail about how to create a bbappend file and how and when
to modify the various variables.
Clear COMPATIBLE_MACHINE so bitbake will not attempt to build the recipe
unless the user explicitly adds there machine to the variable, which
should encourage them to read the recipe comments before attempting to
build it.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
It is considered good practice to use the build system provided
variables instead of directly specify hardcoded paths.
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Remove the linux-tools include as perf is now packaged independently.
Without this, including meta-skeleton in bblayers.conf results in a
build failure as linux-tools.inc cannot be found.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
|
|
Adding a skeleton/refrence recipe for using a subset of the yocto
kernel tools against kernel git repositories.
Sample/reference configuration fragments, features and a patch are
provided and documented in the recipe.
From the recipe itself:
Provides an example/minimal kernel recipe that uses the linux-yocto
and oe-core kernel classes to apply a subset of yocto kernel
management to git managed kernel repositories.
Notes:
kconfig(s): the kernel must be configured with a defconfig, or via
configuration fragment(s). Either of these can be added
via bbappend.
patches: patches can be merged into to the source git tree itself, added
using standard bbappend syntax or controlled via .scc feature
descriptions (also via bbappends)
example configuration addition:
SRC_URI += "file://smp.cfg"
example patch addition (for kernel v3.4 only):
SRC_URI += "file://0001-linux-version-tweak.patch
example feature addition (for kernel v3.4 only):
SRC_URI += "file://feature.scc"
Warning:
Building the sample kernel tree (kernel.org) without providing any
configuration will result in build or boot errors. This is not a bug
it is a required element for creating a valid kernel.
[YOCTO #2397]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
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>
|
|
Clarify that only packages listed in USERADD_PACKAGES will
include the user/group creation code.
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
|
|
An example recipe for demonstrating/documenting how user and
group manipulation is done with 'inherit useradd'
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
|
|
Add a skeleton for init scripts, the original structure is from
/etc/init.d/skeleton of Ubuntu 10.10, it is in sysvinit_2.87dsf, so add
the COPYRIGHT(GPLv2) of sysvinit_2.87dsf. Modified the original skeleton
a lot to make it as easy as possible, just use posix shell command, and
have tested it with core-image-minimal.
* The skeleton implements the following actions:
- start, stop, restart, status, try-restart and force-reload.
# force-reload is a alias of try-restart.
- not implements reload, since only a few programs have it, just leave
it as placeholder.
* Add /usr/sbin/skeleton-test to test /etc/init.d/skeleton
* The /etc/init.d/skeleton can be run and output the example messages:
1) #./skeleton start (test start)
Starting skeleton ...
2) #./skeleton start (test start again when running)
skeleton already running (1078).
3) #./skeleton status (test status when running)
skeleton is running (1078).
4) #./skeleton stop (test stop)
Stopped skeleton (1078).
5) #./skeleton stop (test stop again)
skeleton is not running; none killed.
6) #./skeleton status (test status when stopped)
skeleton is not running.
7) #./skeleton restart (test restart when running)
Stopped skeleton (1128).
Starting skeleton ...
8) #./skeleton restart (test restart when stopped)
skeleton is not running; none killed.
Starting skeleton ...
9) try-restart (or force-reload) means restart the service if the
service is already running
#./skeleton try-restart (test try-restart when stopped)
skeleton is not running; none killed.
#./skeleton try-restart (test try-restart when running)
Stopped skeleton (1181).
Starting skeleton ...
* Have used syslogd to test it in a real world(with both
core-image-minimal and core-image-sato)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
|
|
Add the layer meta-skeleton, it will be used to place the various
canonical examples.
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
|
