| Age | Commit message (Collapse) | Author | Files |
|---|
|
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
The mapping of qemu to kernel branch name for the stable
kernel had a small leak from the devel kernel. Nothing
broke since qemux86 prefers the 2.6.37 kernel and this was
hidden.
This fixes the mapping for anyone who does want a 2.6.34 based
qemux86 kernel.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The existing 2.6.34 kernel tree uses _ where poky typically
uses -. This is a historical artifact, since working with
gnu Make and shells means avoiding - is wise. The opposite
is true in Yocto.
To avoid using the _ reserved character wherever possible
we can simply remove it from the branch names in the
new 2.6.37 kernel, but to keep the content stable in the
0.9 2.6.34 kernel, we map _ to - for the purposes of
packaging.
To further faciliate this switch, the branch names no
longer need to be shortened in the KMACHINE mappings, but
can be fully specified and the tools/processing adapt as
required. This gives us the flexibility to map multiple
boards to a single branch for building.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
During the last phase of the recipe factoring, the board compatibility
lists ended up in the wrong place, which meant we had an incomplete
list of boards, and the same set of boards for both kernels (stable
and devel).
To fix this, I've yanked the compatibility to the recipes themselves and
updated the emenlow to have a -stable bbappend.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
In order to extend and create more kernel recipes based on the
supported yocto kernel common routines need to be placed in
re-usable blocks.
To accomplish this meta/recipes-kernel/linux/linux-yocto_git.bb
is broken into three parts:
- meta/classes/kernel-yocto.bbclass: contains common routines
for checking out and configuring a yocto kernel git repository.
This should be inherited by recipes that need this functionality.
- meta/recipes-kernel/linux/linux-yocto.inc: Contains the machine
mappings, compatibility, build directives and common task
definitions for a yocto kernel based recipe. This inherits
kernel-yocto, and is the typical point of entry for other recipes.
- meta/recipes-kernel/linux/linuux-tools.inc: tasks and function definitions
for kernel recipes that want to build/export perf
It also updates the linux-yocto recipe to default to 2.6.37.
As part of the update to 2.6.37 the branch naming and conventions
have been modified to show inheritance, and be more generic.
For example:
master
meta
yocto/base
yocto/standard/arm_versatile_926ejs
yocto/standard/base
yocto/standard/beagleboard
yocto/standard/common_pc/atom-pc
yocto/standard/common_pc/base
yocto/standard/common_pc_64
yocto/standard/fsl-mpc8315e-rdb
yocto/standard/intel_atom_z530
yocto/standard/intel_core_qm57_pch
yocto/standard/mti_malta32_be
yocto/standard/preempt_rt/base
yocto/standard/preempt_rt/common_pc
yocto/standard/preempt_rt/common_pc_64
yocto/standard/preempt_rt/intel_atom_z530
yocto/standard/preempt_rt/intel_core_qm57_pch
yocto/standard/qemu_ppc32
yocto/standard/routerstationpro
In this structure:
master: tracks the mainline kernel
meta: meta information for the BSPs and kernel features
yocto/base: baseline kernel branch
yocto/standard/base: 'standard' kernel, contains features
and configs for all BSPs
yocto/standard/<machine>: represents a BSP with specific
features or configurations
The tools, tree and libc-headers have all been updated to
deal with this new structure. Also in addition to dealing with
the new structure, they continue to work with the existing
tree and will adapt at runtime to the differences.
The linux-yocto-stable_git.bb recipe continues to build the
2.6.34 based tree,and linux-yocto_git.bb builds 2.6.37. As
boards are enabled for the new kernel they will move from
-stable to the development kernel. As of now, only the
emulated targets have moved to 2.6.37-rcX
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The existing preferred yocto kernel wasn't named appropriately
and needs to be updated.
In keeping the changes small and isolated, this commit simply
renames the recipe and some internal variables. Future commits
will refactor the code into more usable blocks.
Now that linuy-wrs has been renamed linux-yocto, we need
to rename and update an board configurations and append
files.
Now that linux-wrs has been renamed linux-yocto, we need to
update the SRCREVs to have the new name.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When creating a new BSP there isn't always an upstream branch
to validate SRCREVs against. Therefore, creating a new BSP
required extra manipulations of the git repository, even though
the branch for the build would be dynamically created.
To fix this, provide a fallback to the 'standard' branch if
WRMACHINE is not assigned a specific value for the given MACHINE.
The fallback saved in KBRANCH, and represents the branch that
we should build, even if no fallback is required. Some substeps
of the recipe have been updated to use KBRANCH rather than
enforcing MACHINE-KERNELTYPE.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
It is useful to override revision checking from a layer or other
recipe. In order to show the global nature of the variable rename
it KERNEL_REVISION_CHECKING and make it a weak assignment.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Fixes [BUGID #199]
Although an optional feature to a base BSP, most of the machines
currently supported want/need the netfilter options. To enforce
this configuration, it is temporarily forced in the kernel
recipe itself, but can move to machine configurations in the
future.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Fixes [BUGID #199]
Reinstate the ability to specify optional/additional kernel features
when updating the tree.
This is done via the variable KERNEL_FEATURES which specifies
a list of features to be appended to the current branch and
config. These features are part of the wrs_meta branch in the
kernel repository and hence are self contained within the
kernel tree waiting to be activated. This saves multiple
branches simply to allow a machine to have many profiles.
The kernel patching/configuration phases will locate these
features and add them to the meta_series, which in turn
modifies the tree.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The emenlow didn't have the default 8250 serial ports.
Including the common serial config fragment fixes this
problem.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Fixes [BUGID #432, #438, #437, #422]
[atom-pc: switch to the atom-pc branch
The atom-pc has a dedicated branch and merged kernel commits.
Swtich the kernel recipe to use the fully integrated BSP
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>]
[atom-pc: add kernel config options needed for -live images
Fixes [BUGID #432]
Live images require VFAT filesystem and loop device support - this
adds the required kernel config options for them.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>]
[atom-pc: Add netbook wireless networking support for NB305 and eee901
Add the atom-pc-wifi.cfg to enable wireless networking support for the netbooks
mentioned in the atom-pc machine config file.
Note: this adds a staging tree driver (rt2860sta) for the eee901 wifi.
[BUGID #438]
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Richard Purdie <rpurdie@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>]
[atom-pc: Add netbook wired networking support for NB305, Aspire One, and eee901
Add the atom-pc-eth.cfg to enable wired networking support for the three
netbooks mentioned in the atom-pc machine config file.
[BUGID #437]
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Richard Purdie <rpurdie@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>]
[routerstationpro: add missing kernel patches
[BUGID: #422]
Add the kernel patches required for routerstaion pro boot
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>]
[netbook: allow hardisk booting
[BUGID: #445]
Signed-off-by: Darren Hart <dvhart@linux.intel.com>]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The atom-pc has a dedicated branch and merged kernel commits.
Swtich the kernel recipe to use the fully integrated BSP
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
[BUGID #363]
Integrate the x86 gfx options into the existing x86 graphics
options for the common_pc and common_pc_64 boards.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
BUGID: 421
Create the infrastructure to build the beagleboard against the
linux-wrs kernel.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
BUGID: 423
Introduce the basic mpc8315e BSP. By default this BSP uses
the basic 603 tuning and soft-float. There are issues with
the e300 tuning and eglibc, and the compiler. Subsequent
commits will further tune this BSP.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
BUGID: 422
Add the machine configuration and kernel infrastructure for building
the routerstation pro BSP.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Init scripts assume uvesafb as module, and also need CONFIG_FRAMEBUFFER_CONSOLE
to set some mode parameter, else wrong parameter cause psplash's mmap failure.
This is just a quick fix as we don't know how to change the wrs kernel config
in a clean way. Should revert it with clean way of changing.
[BUGID #363] fixed by this
Signed-off-by: Tian Kevin <kevin.tian@intel.com>
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
|
|
Add CONFIG_FRAMEBUFFER_CONSOLE to the i915.cfg config fragment for
the atom-pc machine. This allows the BlackSand to boot to the sato
desktop with text after the fb switch as well as the poky splash
screen.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Richard Purdie <rpurdie@linux.intel.com>
|
|
Add serial port support for atom-pc.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Add the option of using linux-wrs as the kernel provider for atom-pc. This
patch uses poky to apply config fragments to the common_pc-standard branch
of the linux-wrs kernel. A follow-on patch will remove these once linux-wrs
has an atom-pc branch and the config fragments are present in the kernel
repository.
This configuration boots to a prompt on the BlackSand, but panics unable
to find the root partition on the Toshiba NB305 where the "rootwait"
kernel boot option appears to be being ignored.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
In preparation for the more generic atom-pc, rename the netbook machine and all
the relevant overrides. Leave the linux-netbook kernel recipe intact and as the
default kernel for the atom-pc machine. A future patch will convert this over
to linux-wrs and likely remove the linux-netbook kernel recipe.
Cc: Tom Zanussi <tom.zanussi@intel.com>
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Part of [BUGID #373]
In order to generate BSP definitions for new boards, we need
to know the architecture. So we'll arrange to pass it to
updateme.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Fixes [BUGID #372]
If for some unknown reason, the kernel git repository hasn't been properly
updated and is *older* than the revisions listed in default-revisions the
branch sanity checking kicks in and tries to force branches to the right
revs. The problem is, the revisions it is looking for don't exist in the
tree. As a result, error messages are thrown about invalid commit IDs.
These aren't helpful, and are simply confusing for the user.
Instead we can test for the commit ID, and if it isn't valid, indicate
that the commit ID isn't valid and that the tree is potentially out
of sync.
This situation is not common, but it is an easy test and the extra
sanity checking is useful.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
to meta
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
|
|
Fix for unresolved libelf error when running perf:
perf: error while loading shared libraries: libelf.so.1: cannot open
shared object file: No such file or directory
Signed-off-by: <tom.zanussi@intel.com>
Signed-off-by: <bruce.ashfield@windriver.com>
|
|
* Add binary devicetree generation support
* Taken from OE
* v2 reorder patch set
* v3 remove package_stagefile_shell
* v4 rename devicetree_image function to install_append
* remove pkg_postinst_kernel-devicetree,
pkg_postrm_kernel-devicetree functions
* Update KERNEL_DEVICETREE_FLAGS use "-p" option instead
of "-S" which is deprecated
Signed-off-by: Adrian Alonso <aalonso00@gmail.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
It is possible for the git repository to have commits on branches
that are ahead of the SRCREVs for those branches. Since the
kern tools will simply checkout and build, we can end up building
a different kernel than what is expected.
It is up to the recipe to ensure that the branches are at the
correct commits. To do this, we simply check the current machine
branch against the SRCREV and if they don't match we move the
existing branch and do a checkout at the desired commit.
Note: This probably needs to be disabled with AUTOREV.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
By defining the perf package in the shared kernel class bitbake will be able to
find the package provider even when the preferred kernel doesn't build perf,
preventing dependency resolution failures.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Updating the SRCREVs for the recent port of bug fixes for all boards
and the integration of qemux86-64 config and connector changes.
Now that the qemux86-64 changes are in tree, we can drop them from
the linux-wrs recipe.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Having one monolithic packages directory makes it hard to find things
and is generally overwhelming. This commit splits it into several
logical sections roughly based on function, recipes.txt gives more
information about the classifications used.
The opportunity is also used to switch from "packages" to "recipes"
as used in OpenEmbedded as the term "packages" can be confusing to
people and has many different meanings.
Not all recipes have been classified yet, this is just a first pass
at separating things out. Some packages are moved to meta-extras as
they're no longer actively used or maintained.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
