Age | Commit message (Collapse) | Author |
|
The systemtap feature can use the new kprobes and uprobes feature and
remove the corresponding open-coded options.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Add kprobes support to ktypes/standard alongside uprobes and other
tracing options enabled there.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Add config options to turn KPROBES on, along with KPROBE_EVENT which
provides an trace events interface that can be used by other tools
such as perf.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
The uprobe feature includes the patches for uprobes but doesn't
include config options for it - add them.
Also, add description and compatibility strings.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Add config options to turn UPROBES on, along with UPROBE_EVENT which
provides an trace events interface that can be used by other tools
such as perf.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Enable Single Root PCI I/O Virtualization feature.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
|
|
Add Single Root PCI I/O Virtualization feature to meta.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
|
|
Since this BSP now uses 3.4.x kernel, this option is obsolete
and generates a warning. The option was removed in mainline:
commit 7c5763b8453a94871d356f20df30f350f8631e8b
Author: Fabio Estevam <festevam@gmail.com>
Date: Tue Jan 24 02:11:25 2012 -0200
drivers: misc: Remove MISC_DEVICES config option
as of v3.3-rc4 and so is gone in v3.4.x codebase.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Initial checkin for the new Crystal Forest Machine Branch.
This Machine is based on Sandybridge CPU and Cave Creek Chipset.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
|
|
qemuppc had some old profiling options in its BSP configuration
fragments. These are better pulled from the profiling feature.
This also removes a warning when options like CONFIG_FRAME_POINTER
are dropped from the final .config (since they are not available
on the arch).
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To ensure that the kernel is debugable by default, and that self tests
pass, we should enable KDB, and KDB_KEYBOARD and KGDB_LOW_LEVEL_TRAP
for x86 boards.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Hash is the correct comment format.
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
|
|
Warnings are not clear because base.scc exists both in ktypes/base/ and
features/usb/. Rename features/usb/base.scc and features/usb/base.cfg
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
|
|
This has largely no effect, since the default is y, and since
it is as fundamental as CONFIG_NET, it should be in the base.
Move it there and delete any other instances of it. This will
resolve any BSP configuration audit warnings on CONFIG_BLOCK
caused by a BSP that includes scsi.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
A scan of this file reveals that it is full of UART specific
settings for various embedded platforms, and should be listed
in the hardware category. This will also stop the audit from
warning that SERIAL_CORE and SERIAL_CORE_CONSOLE are being
set by BSPs as if it were non-hardware related.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Call out the two filesystems used by this specific BSP in
the hardware list. While filesystems aren't generally
hardware items, boards with MTD devices will need certain
specific filesystems, so there is a hardware linkage.
Regardless, the point of the audit is to inform people in
a way that lets them think about their choices. We've
done that here, and know we need these.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
This BSP patches into existence a new Kconfig file in
the drivers/net/ethernet dir, and it creates a new
Kconfig option (PACKET_MANGLE) in what would otherwise
be a non board (hardware) specific Kconfig file.
Inform the audit subsystem about both, so that it does
not create false positive warnings about either.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
This file describes a CPU variant, so it is hardware, and
since it is in the mainline kernel, it should be listed
here and not in the BSP specific dir (where BSP added
Kconfig files would be listed).
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
So that we don't get audit warnings telling us that UART
related settings are non-hardware related.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Unlike the previous config, this is a more minimalistic one
that sticks to just specifying hardware items.
The watchdog minifrag gets an update too, as a config option
got renamed.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Import of the openwrt files from trunk, as of this commit:
----------
commit c1d79f64eed0a7ac36b5b9bca52275b397bec424
Author: nbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73>
Date: Mon Jul 16 16:26:51 2012 +0000
uboot-ar71xx: fix compile on recent mac os x versions
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32750 3c298f89-4303-0410-b956-a3cf2f4a3e73
----------
Due to the nature of how the openwrt source is managed, new
files are found separate from the commits which actually
make use of them, so that unused stuff could not easily
be left behind, but it is what it is.
Path to files in the repo is:
target/linux/generic/files
target/linux/ar71xx/files
Repo is: git://nbd.name/openwrt.git
The process used was creating a booting kernel based on a
v3.3 baseline and a subset of the openwrt patches (there
are over 200), with the obvious (aka "easy") cull made.
This subset was then forward ported to v3.4 -- it is by
no means the absolute minimum it could be; things like
ar93xx/95xx support could also be culled, or some of the
board specific init files, but given this board is already
EOL, I can't justify spending additional time doing that.
Some of the patches (ones with Patchworks links and SOB via
Ralf) made it upstream in v3.5-rc1, and I've added the
upstream IDs to those where appropriate. However they were
not compared one-by-one to verify what (if any) deltas were
introduced in the backport to openwrt's 3.3 kernel.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Since this was largely a full .config file, just zero it out
before reducing it to the key needed config items, since a
diff of the two will be a meaningless spray of +- lines.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Ensure the preempt-rt kernel has usb-mass-storage and boot-live support
in support of booting the hddimg images over USB.
Add the latencytop and profiling scc files to keep the default policy
consistent with the 'standard' kernel.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Ensure the preempt-rt kernel has usb-mass-storage and boot-live support
in support of booting the hddimg images over USB.
Add the latencytop and profiling scc files to keep the default policy
consistent with the 'standard' kernel.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
|
|
Ensure the preempt-rt kernel has usb-mass-storage and boot-live support
in support of booting the hddimg images over USB.
Add the latencytop and profiling scc files to keep the default policy
consistent with the 'standard' kernel.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
|
|
Ensure the preempt-rt kernel has usb-mass-storage and boot-live support
in support of booting the hddimg images over USB.
Add the latencytop and profiling scc files to keep the default policy
consistent with the 'standard' kernel.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
|
|
Ensure the preempt-rt kernel has usb-mass-storage and boot-live support
in support of booting the hddimg images over USB.
Add the latencytop and profiling scc files to keep the default policy
consistent with the 'standard' kernel.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Kishore Bodke <kishore.k.bodke@intel.com>
|
|
Ensure the preempt-rt kernel has usb-mass-storage and boot-live support
in support of booting the hddimg images over USB.
Add the latencytop and profiling scc files to keep the default policy
consistent with the 'standard' kernel.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Kishore Bodke <kishore.k.bodke@intel.com>
|
|
Ensure the preempt-rt kernel has usb-mass-storage and boot-live support
in support of booting the hddimg images over USB.
Add the latencytop and profiling scc files to keep the default policy
consistent with the 'standard' kernel.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/1 [
Author: Bruce Ashfield
Email: bruce.ashfield@windriver.com
Subject: preempt-rt: import 3.4.4-rt14
Date: Fri, 20 Jul 2012 12:53:28 -0400
Importing 3.4.4-rt14 from:
http://www.kernel.org/pub/linux/kernel/projects/rt/3.4/patch-3.4.4-rt14.patch
Only minor context adjustments were made.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
1/2 [
Author: Nitin A Kamble
Email: nitin.a.kamble@intel.com
Subject: yocto/emgd: emgd 1.14 driver
Date: Mon, 16 Jul 2012 07:14:38 -0700
The starting-point code that subsequent patches will modify. This is
a straight copy of the code in the emgd 1.14 emgd driver, specifically
IEMGD_HEAD_Linux/common/drm/emgd_drm.tgz from
LIN_IEMGD_1_14_GOLD_2443.tgz, the 'Linux Tar Ball' release downloaded
from http://edc.intel.com/Software/Downloads/EMGD/.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
]
2/2 [
Author: Nitin A Kamble
Email: nitin.a.kamble@intel.com
Subject: emgd/pvr: get it building with v3.4 kernel
Date: Mon, 16 Jul 2012 07:14:50 -0700
Add emgd config option (DRM_EGD) and modify Makefiles for in-tree
builds.
rebased to v3.4 code
Fix build errors caused by changes to kernel interfaces introduced by
linux 3.2 such as:
error: 'THIS_MODULE' undeclared here (not in a function)
due to a missing THIS_MODULE definition which can be found in linux/export.h.
It also fixes a ream of errors like:
error: expected ')' before string constant
due to missing MODULE_PARM_DESC definition which can be found in
linux/moduleparam.h, included by linux/module.h, needed also for
MODULE_AUTHOR, etc.
variable name "pitch" from drm_framebuffer structure has changed
to "pitches" array in v3.4 kernel soruces.
avoid errors like these:
emgd_fbcon.c:128:28: error: 'struct drm_framebuffer' has no member named 'pitch'
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
CONFIG_MTD_NAND_VERIFY_WRITE option: this works ok with JFFS2 fs but
leads to errors when using UBI.
http://www.linux-mtd.infradead.org/faq/ubi.html#L_subpage_verify_fail
http://lists.infradead.org/pipermail/linux-mtd/2011-February/034089.html
Reported-by: Andrea Adami <andrea.adami@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
CONFIG_KMEMCHECK depends on !FUNCTION_TRACER but
CONFIG_FUNCTION_TRACER is being turned on by a combination of other
configs which are set. In order to prevent this we need to explicitely
disable CONFIG_STACK_TRACER.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
|
|
Add support for generic syscall entry/exit tracing.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
1/1 [
Author: Bruce Ashfield
Email: bruce.ashfield@windriver.com
Subject: preempt-rt: import 3.4.4-rt13
Date: Sun, 1 Jul 2012 00:19:31 -0400
Importing 3.4.4-rt13 from:
http://www.kernel.org/pub/linux/kernel/projects/rt/3.4/patch-3.4.4-rt13.patch
The only changes were minor context adjustments.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
We've enabled (=m) INGRESS, but we should also explicitly
select ACT, since we have this in Kconfig:
config NET_SCH_INGRESS
tristate "Ingress Qdisc"
depends on NET_CLS_ACT
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Removed in mainline commit a77aea92010acf54ad785047234418d5d68772e2
-----------
cgroup: remove the ns_cgroup
The ns_cgroup is an annoying cgroup at the namespace / cgroup frontier and
leads to some problems:
* cgroup creation is out-of-control
* cgroup name can conflict when pids are looping
* it is not possible to have a single process handling a lot of
namespaces without falling in a exponential creation time
* we may want to create a namespace without creating a cgroup
The ns_cgroup was replaced by a compatibility flag 'clone_children',
where a newly created cgroup will copy the parent cgroup values.
The userspace has to manually create a cgroup and add a task to
the 'tasks' file.
This patch removes the ns_cgroup as suggested in the following thread:
https://lists.linux-foundation.org/pipermail/containers/2009-June/018616.html
[...]
-----------
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
The mti malta board description for a little endian config can't
be found by default unless it has a matching KMACHINE, or the
KMACHINE is set in a kernel recipe. In this case, it is easier to
just add qemumipsel in the KMACHINE list, so the recipe doesn't
need to do the mapping.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|