| Age | Commit message (Collapse) | Author |
|---|
|
The IGB driver is showing up on some general hardware (like MinnowBoard)
which is one of the Yocto Project Reference Platforms.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The the new controllers were added several kernels back and are
required for additional functionality. These are applicable to the
4.9 kernel and newer.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Adds dependencies that were missing. In some BSPs, they were satisfied,
in others they weren't and caused warnings.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
meta-intel (intel-* MACHINEs) plans to use the backported
ixgbe ethernet modules so disable building them in the base kernel
config.
To build the in-kernel drivers, features/ixgbe/ixgbe.scc must be
added in KERNEL_FEATURES.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
In order to build backport-iwlwifi driver (meta-intel has
the recipe) that ships its own MAC80211 and to use the crypto
drivers from the targeted kernel for it, CONFIG_CRYPTO_CCM must
be enabled.
backport-iwlwifi does have a compat implementation of crypto-ccm.c too
that would be used if CONFIG_CRYPTO_CCM is not set but that currently
fails to build (implicit function declaration).
Therefore, just enable CRYPTO_CCM. And while we're at it, enable
all crypto drivers that are needed by MAC80211.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The skylake audio driver enables CONFIG_SDW which in turn does not
correcly select/enable its dependencies so the build fails if
CONFIG_CRC8 is not explicitly enabled.
The build failure triggers when disabling common-pc-wifi.cfg.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/1 [
Author: Bruce Ashfield
Email: bruce.ashfield@windriver.com
Subject: aufs: sync to 4.10-latest
Date: Thu, 24 Aug 2017 14:54:32 -0400
Syncing to the latest aufs4 upstream 4.10 branch to fix compile
(and runtime) issues with aufs.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/11 [
Author: Hugh Dickins
Email: hughd@google.com
Subject: mm: larger stack guard gap, between vmas
Date: Mon, 14 Aug 2017 22:51:22 -0400
commit 1be7107fbe18eed3e319a6c3e83c78254b693acb upstream.
Stack guard page is a useful feature to reduce a risk of stack smashing
into a different mapping. We have been using a single page gap which
is sufficient to prevent having stack adjacent to a different mapping.
But this seems to be insufficient in the light of the stack usage in
userspace. E.g. glibc uses as large as 64kB alloca() in many commonly
used functions. Others use constructs liks gid_t buffer[NGROUPS_MAX]
which is 256kB or stack strings with MAX_ARG_STRLEN.
This will become especially dangerous for suid binaries and the default
no limit for the stack size limit because those applications can be
tricked to consume a large portion of the stack and a single glibc call
could jump over the guard page. These attacks are not theoretical,
unfortunatelly.
Make those attacks less probable by increasing the stack guard gap
to 1MB (on systems with 4k pages; but make it depend on the page size
because systems with larger base pages might cap stack allocations in
the PAGE_SIZE units) which should cover larger alloca() and VLA stack
allocations. It is obviously not a full fix because the problem is
somehow inherent, but it should reduce attack space a lot.
One could argue that the gap size should be configurable from userspace,
but that can be done later when somebody finds that the new 1MB is wrong
for some special case applications. For now, add a kernel command line
option (stack_guard_gap) to specify the stack gap size (in page units).
Implementation wise, first delete all the old code for stack guard page:
because although we could get away with accounting one extra page in a
stack vma, accounting a larger gap can break userspace - case in point,
a program run with "ulimit -S -v 20000" failed when the 1MB gap was
counted for RLIMIT_AS; similar problems could come with RLIMIT_MLOCK
and strict non-overcommit mode.
Instead of keeping gap inside the stack vma, maintain the stack guard
gap as a gap between vmas: using vm_start_gap() in place of vm_start
(or vm_end_gap() in place of vm_end if VM_GROWSUP) in just those few
places which need to respect the gap - mainly arch_get_unmapped_area(),
and and the vma tree's subtree_gap support for that.
Original-patch-by: Oleg Nesterov <oleg@redhat.com>
Original-patch-by: Michal Hocko <mhocko@suse.com>
Signed-off-by: Hugh Dickins <hughd@google.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Tested-by: Helge Deller <deller@gmx.de> # parisc
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[wt: backport to 4.11: adjust context]
[wt: backport to 4.9: adjust context ; kernel doc was not in admin-guide]
Signed-off-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
2/11 [
Author: Hugh Dickins
Email: hughd@google.com
Subject: mm: fix new crash in unmapped_area_topdown()
Date: Mon, 14 Aug 2017 22:51:23 -0400
commit f4cb767d76cf7ee72f97dd76f6cfa6c76a5edc89 upstream
Trinity gets kernel BUG at mm/mmap.c:1963! in about 3 minutes of
mmap testing. That's the VM_BUG_ON(gap_end < gap_start) at the
end of unmapped_area_topdown(). Linus points out how MAP_FIXED
(which does not have to respect our stack guard gap intentions)
could result in gap_end below gap_start there. Fix that, and
the similar case in its alternative, unmapped_area().
Cc: stable@vger.kernel.org
Fixes: 1be7107fbe18 ("mm: larger stack guard gap, between vmas")
Reported-by: Dave Jones <davej@codemonkey.org.uk>
Debugged-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Hugh Dickins <hughd@google.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
3/11 [
Author: Dan Carpenter
Email: dan.carpenter@oracle.com
Subject: ipx: call ipxitf_put() in ioctl error path
Date: Mon, 14 Aug 2017 22:51:24 -0400
upstream ee0d8d8482345ff97a75a7d747efc309f13b0d80 commit
We should call ipxitf_put() if the copy_to_user() fails.
Reported-by: 李强 <liqiang6-s@360.cn>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
4/11 [
Author: Arend van Spriel
Email: arend.vanspriel@broadcom.com
Subject: brcmfmac: fix possible buffer overflow in brcmf_cfg80211_mgmt_tx()
Date: Wed, 16 Aug 2017 04:36:13 -0400
commit 8f44c9a41386729fea410e688959ddaa9d51be7c upstream
The lower level nl80211 code in cfg80211 ensures that "len" is between
25 and NL80211_ATTR_FRAME (2304). We subtract DOT11_MGMT_HDR_LEN (24) from
"len" so thats's max of 2280. However, the action_frame->data[] buffer is
only BRCMF_FIL_ACTION_FRAME_SIZE (1800) bytes long so this memcpy() can
overflow.
memcpy(action_frame->data, &buf[DOT11_MGMT_HDR_LEN],
le16_to_cpu(action_frame->len));
Cc: stable@vger.kernel.org # 3.9.x
Fixes: 18e2f61db3b70 ("brcmfmac: P2P action frame tx.")
Reported-by: "freenerguo(郭大兴)" <freenerguo@tencent.com>
Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
5/11 [
Author: Jan Beulich
Email: jbeulich@suse.com
Subject: xen-blkback: don't leak stack data via response ring
Date: Wed, 16 Aug 2017 04:36:14 -0400
commit: 089bc0143f489bd3a4578bdff5f4ca68fb26f341 upstream
Rather than constructing a local structure instance on the stack, fill
the fields directly on the shared ring, just like other backends do.
Build on the fact that all response structure flavors are actually
identical (the old code did make this assumption too).
This is XSA-216.
Cc: stable@vger.kernel.org
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
6/11 [
Author: Ari Kauppi
Email: ari@synopsys.com
Subject: nfsd: fix undefined behavior in nfsd4_layout_verify
Date: Wed, 16 Aug 2017 04:36:15 -0400
commit: b550a32e60a4941994b437a8d662432a486235a5 upstream
UBSAN: Undefined behaviour in fs/nfsd/nfs4proc.c:1262:34
shift exponent 128 is too large for 32-bit type 'int'
Depending on compiler+architecture, this may cause the check for
layout_type to succeed for overly large values (which seems to be the
case with amd64). The large value will be later used in de-referencing
nfsd4_layout_ops for function pointers.
Reported-by: Jani Tuovila <tuovila@synopsys.com>
Signed-off-by: Ari Kauppi <ari@synopsys.com>
[colin.king@canonical.com: use LAYOUT_TYPE_MAX instead of 32]
Cc: stable@vger.kernel.org
Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
7/11 [
Author: "J. Bruce Fields"
Email: bfields@redhat.com
Subject: nfsd: encoders mustn't use unitialized values in error cases
Date: Wed, 16 Aug 2017 04:36:16 -0400
commit: f961e3f2acae94b727380c0b74e2d3954d0edf79 upstream
In error cases, lgp->lg_layout_type may be out of bounds; so we
shouldn't be using it until after the check of nfserr.
This was seen to crash nfsd threads when the server receives a LAYOUTGET
request with a large layout type.
GETDEVICEINFO has the same problem.
Reported-by: Ari Kauppi <Ari.Kauppi@synopsys.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Cc: stable@vger.kernel.org
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
8/11 [
Author: Eric Dumazet
Email: edumazet@google.com
Subject: dccp/tcp: do not inherit mc_list from parent
Date: Thu, 17 Aug 2017 05:26:12 -0400
commit 657831ffc38e30092a2d5f03d385d710eb88b09a upstream
syzkaller found a way to trigger double frees from ip_mc_drop_socket()
It turns out that leave a copy of parent mc_list at accept() time,
which is very bad.
Very similar to commit 8b485ce69876 ("tcp: do not inherit
fastopen_req from parent")
Initial report from Pray3r, completed by Andrey one.
Thanks a lot to them !
Signed-off-by: Eric Dumazet <edumazet@google.com>
Reported-by: Pray3r <pray3r.z@gmail.com>
Reported-by: Andrey Konovalov <andreyknvl@google.com>
Tested-by: Andrey Konovalov <andreyknvl@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
9/11 [
Author: Willy Tarreau
Email: w@1wt.eu
Subject: char: lp: fix possible integer overflow in lp_setup()
Date: Thu, 17 Aug 2017 05:26:13 -0400
commit 3e21f4af170bebf47c187c1ff8bf155583c9f3b1 upstream
The lp_setup() code doesn't apply any bounds checking when passing
"lp=none", and only in this case, resulting in an overflow of the
parport_nr[] array. All versions in Git history are affected.
Reported-By: Roee Hay <roee.hay@hcl.com>
Cc: Ben Hutchings <ben@decadent.org.uk>
Cc: stable@vger.kernel.org
Signed-off-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
10/11 [
Author: Seunghun Han
Email: kkamagui@gmail.com
Subject: ACPICA: Namespace: fix operand cache leak
Date: Thu, 17 Aug 2017 05:26:14 -0400
commit 3b2d69114fefa474fca542e51119036dceb4aa6f upstream
ACPICA commit a23325b2e583556eae88ed3f764e457786bf4df6
I found some ACPI operand cache leaks in ACPI early abort cases.
Boot log of ACPI operand cache leak is as follows:
>[ 0.174332] ACPI: Added _OSI(Module Device)
>[ 0.175504] ACPI: Added _OSI(Processor Device)
>[ 0.176010] ACPI: Added _OSI(3.0 _SCP Extensions)
>[ 0.177032] ACPI: Added _OSI(Processor Aggregator Device)
>[ 0.178284] ACPI: SCI (IRQ16705) allocation failed
>[ 0.179352] ACPI Exception: AE_NOT_ACQUIRED, Unable to install
System Control Interrupt handler (20160930/evevent-131)
>[ 0.180008] ACPI: Unable to start the ACPI Interpreter
>[ 0.181125] ACPI Error: Could not remove SCI handler
(20160930/evmisc-281)
>[ 0.184068] kmem_cache_destroy Acpi-Operand: Slab cache still has
objects
>[ 0.185358] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.10.0-rc3 #2
>[ 0.186820] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS
virtual_box 12/01/2006
>[ 0.188000] Call Trace:
>[ 0.188000] ? dump_stack+0x5c/0x7d
>[ 0.188000] ? kmem_cache_destroy+0x224/0x230
>[ 0.188000] ? acpi_sleep_proc_init+0x22/0x22
>[ 0.188000] ? acpi_os_delete_cache+0xa/0xd
>[ 0.188000] ? acpi_ut_delete_caches+0x3f/0x7b
>[ 0.188000] ? acpi_terminate+0x5/0xf
>[ 0.188000] ? acpi_init+0x288/0x32e
>[ 0.188000] ? __class_create+0x4c/0x80
>[ 0.188000] ? video_setup+0x7a/0x7a
>[ 0.188000] ? do_one_initcall+0x4e/0x1b0
>[ 0.188000] ? kernel_init_freeable+0x194/0x21a
>[ 0.188000] ? rest_init+0x80/0x80
>[ 0.188000] ? kernel_init+0xa/0x100
>[ 0.188000] ? ret_from_fork+0x25/0x30
When early abort is occurred due to invalid ACPI information, Linux kernel
terminates ACPI by calling acpi_terminate() function. The function calls
acpi_ns_terminate() function to delete namespace data and ACPI operand cache
(acpi_gbl_module_code_list).
But the deletion code in acpi_ns_terminate() function is wrapped in
ACPI_EXEC_APP definition, therefore the code is only executed when the
definition exists. If the define doesn't exist, ACPI operand cache
(acpi_gbl_module_code_list) is leaked, and stack dump is shown in kernel log.
This causes a security threat because the old kernel (<= 4.9) shows memory
locations of kernel functions in stack dump, therefore kernel ASLR can be
neutralized.
To fix ACPI operand leak for enhancing security, I made a patch which
removes the ACPI_EXEC_APP define in acpi_ns_terminate() function for
executing the deletion code unconditionally.
Link: https://github.com/acpica/acpica/commit/a23325b2
Signed-off-by: Seunghun Han <kkamagui@gmail.com>
Signed-off-by: Lv Zheng <lv.zheng@intel.com>
Signed-off-by: Bob Moore <robert.moore@intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
11/11 [
Author: Vladis Dronov
Email: vdronov@redhat.com
Subject: drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl()
Date: Thu, 17 Aug 2017 05:26:15 -0400
commit: ee9c4e681ec4f58e42a83cb0c22a0289ade1aacf upstream
The 'req->mip_levels' parameter in vmw_gb_surface_define_ioctl() is
a user-controlled 'uint32_t' value which is used as a loop count limit.
This can lead to a kernel lockup and DoS. Add check for 'req->mip_levels'.
References:
https://bugzilla.redhat.com/show_bug.cgi?id=1437431
Cc: <stable@vger.kernel.org>
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
Reviewed-by: Sinclair Yeh <syeh@vmware.com>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
QA needs USB OTG to automate some of the testing processes,
this patch adds it to genericx86 builds.
[YOCTO #11740]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
QA needs USB OTG to automate some of the testing processes,
this patch adds it to genericx86-64 builds
[YOCTO #11740]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
QA needs USB OTG to automate some of the testing processes,
this patch adds it to Intel builds.
[YOCTO #11740]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Enable ARM_THUMB which is normally enabled in arch/arm/arm.cfg, however
this config (specifically the .cfg, as the .scc is included via
standard) is not included by the tiny kernel type. This ensures code
built for Zynq targets which might use THUMB instructions (e.g. OE
builds which target 'cortexa9thf-neon') work correctly when using the
tiny kernel type.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add a feature to enable the kernel DYNAMIC_DEBUG config which allows for
dynamic printing of debug messages. Kernel debug messages are normally
not enabled in the kernel unless manually defining DEBUG in code files.
Dynamic debug allows for the messages to be embedded but toggled
dynamically during run time (via boot parameters or from a sysfs
interface).
Enabling this option is useful when debugging multiple parts of the
kernel as well as to allow for enabling of debug messages without
needing to modify the source.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add a general purpose KMACHINE that can be used for general purpose Zynq
BSPs. The main configuration of the Zynq SoC can be configured via
device tree, allowing for a common kernel config. This allows for a
single KMACHINE to target multiple BSPs without needing to be directly
configured for the platform/soc.
This adds configs for -standard and -tiny.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Create configs for the qemumicroblazeeb machine. This includes both
-standard and -tiny configs.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Create configs for the qemumicroblazeel machine. This includes both
-standard and -tiny configs.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add a fragment to enable drivers for Xilinx Soft IP (FPGA devices) which
are used in a number of BSPs including custom MicroBlaze designs.
This fragment has two .cfg files, one is specific to MicroBlaze (kernel
configs have dependency on CONFIG_MICROBLAZE).
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add a config fragment that enables commonly used configs for Xilinx
boards and systems. This includes a number of board level devices (e.g.
I2C, MTD, Ethernet PHYs, etc.)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add the baseline configuration for the MicroBlaze architecture. This
only enables two configs, and sets up the default tick as 100 hz.
MicroBlaze is available in the mainline kernel and requires no
additional patches.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Added configurations to the qat feature which enables the following:
1) CONFIG_CRYPTO_RSA=y
2) CONFIG_CRYPTO_DH=y
Signed-off-by: Syed Johan Arif Bin Syed Mohamad Fauzi <syed.johan.arif.syed.mohamad.fauzi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Added configurations to the netfilter feature which enables the following:
1) CONFIG_IP_NF_TARGET_ULOG=m
2) CONFIG_IP_NF_MATCH_RPFILTER=m
3) CONFIG_IP_NF_TARGET_SYNPROXY=m
4) CONFIG_IP_NF_SECURITY=m
5) CONFIG_BRIDGE_EBT_ULOG=m
Signed-off-by: Syed Mohamad Fauzi, Syed Johan Arif <syed.johan.arif.syed.mohamad.fauzi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When added, this feature enables X2APIC support
Signed-off-by: Syed Mohamad Fauzi, Syed Johan Arif <syed.johan.arif.syed.mohamad.fauzi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When added, this feature enables VFIO(Virtual Function I/O)
This feature helps support virtualization.
Signed-off-by: Syed Johan Arif Bin Syed Mohamad Fauzi <syed.johan.arif.syed.mohamad.fauzi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When added, this feature enables NUMA support
Signed-off-by: Syed Johan Arif Bin Syed Mohamad Fauzi <syed.johan.arif.syed.mohamad.fauzi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When added, this feature enables memory controller and MTD support
Signed-off-by: Syed Johan Arif Bin Syed Mohamad Fauzi <syed.johan.arif.syed.mohamad.fauzi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When added, this feature enables IOMMU support
Signed-off-by: Syed Johan Arif Bin Syed Mohamad Fauzi <syed.johan.arif.syed.mohamad.fauzi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When added, this enables Intel Trusted Execution
Signed-off-by: Syed Johan Arif Bin Syed Mohamad Fauzi <syed.johan.arif.syed.mohamad.fauzi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Enable Broadcom Wifi driver for SDIO mounted hardware on Intel boards
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When selecting SMP, some dependencies are needed, in the case
of a 32 bit build CONFIG_X86_BIGSMP=y is required, but adding that
to a 64 bit build causes warnings to be shown since X86_BIGSMP
requires X86_32 [n] itself, which can only be true for a 32 bit build.
This patch creates a 64 bit version of smp (smp_64), avoiding the
dependecy issues.
[YOCTO #11742]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
mohonpeak.scc and mohonpeak32.scc are based on x86.scc and x86_64.scc
which already include smp.scc, so remove the unnecessary include.
[YOCTO #11743]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
rangeley.scc and rangeley32.scc are based on x86.scc and x86_64.scc
which already include smp.scc, so remove the unnecessary include.
[YOCTO #11743]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add support for sets and IPv4 masquarade.
Signed-off-by: Ismo Puustinen <ismo.puustinen@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Mediatek MT7601U is a common USB WiFi dongle
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The oe-core provides kexec-tools recipe, since we don't
have a manner to enable automatically a kernel feature by
recipe request, this is the best place to enable it in
a kernel developer mode.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
|
|
When added, this allows graphics (i.e. XFCE) to be executed
on virtualbox
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When we set NR_CPUS to something > than 8, we also need to set X86_BIGSMP
according to Kconfig:
config X86_BIGSMP
bool "Support for big SMP systems with more than 8 CPUs"
otherwise NR_CPU will end up being reset to 8
[YOCTO #10362]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Several configurations need the previously mentioned dependencies:
BT_LE is nedded by BT_6LOWPAN
BT_BREDR is needed by:
BT_RFCOMM, BT_RFCOMM_TTY (secondary),
BT_BNEP, BT_BNEP_MC_FILTER (secondary), BNEP_PROTO_FILTER (secondary),
BT_CMTP, BT_HIDP
[YOCTO #10425]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.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>
|
|
These lines don't belong in the .cfg and cause warnings during
the configme process
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The '+' dont belong here and cause warnings
Signed-off-by: Saul Wold <sgw@linux.intel.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>
|
|
This commit adds a kernel feature to have the kernel support
for Intel Memory Protection Extensions (MPX).
A quote from kernel arch/x86/Kconfig:
"MPX provides hardware features that can be used in conjuction
with compiler-instrumented code to check memory references. It
is designed to detect buffer overflow or underflow bugs."
Intel MPX is available, e.g., on Skylake and on Goldmont (e.g.,
Intel 570x).
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
This address the following warning:
From: /srv/sdb/releases/master/builds/4.9/tmp/work-shared/intel-corei7-64/kernel-source/.kernel-meta/configs/standard/intel/features/soc/baytrail/baytrail.cfg
Requested value: CONFIG_DW_DMAC_PCI=m
Actual value: CONFIG_DW_DMAC_PCI=y
Config 'DW_DMAC_PCI' has the following conditionals:
PCI (value: y)
Dependency values are:
PCI [y]
Signed-off-by: Saul Wold <sgw@linux.intel.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>
|
Saul Wold
Jason Wessel
California Sullivan
Mikko Ylinen
Bruce Ashfield
Alejandro Hernandez
Nathan Rossi
Syed Johan Arif Bin Syed Mohamad Fauzi
Ismo Puustinen
Tim Orling
Aníbal Limón