This adds initial support for kernel 4.14 based on the patches for kernel 4.9. In the configuration I deactivated some of the new possible security features like: CONFIG_REFCOUNT_FULL CONFIG_SLAB_FREELIST_HARDENED CONFIG_SOFTLOCKUP_DETECTOR CONFIG_WARN_ALL_UNSEEDED_RANDOM And these overlay FS options are also deactivated: CONFIG_OVERLAY_FS_INDEX CONFIG_OVERLAY_FS_REDIRECT_DIR I activated this: CONFIG_FORTIFY_SOURCE CONFIG_POSIX_TIMERS CONFIG_SLAB_MERGE_DEFAULT CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED I am not sure if I did the porting correct for the following patches: target/linux/generic/backport-4.14/020-backport_netfilter_rtcache.patch target/linux/generic/hack-4.14/220-gc_sections.patch target/linux/generic/hack-4.14/321-powerpc_crtsavres_prereq.patch target/linux/generic/pending-4.14/305-mips_module_reloc.patch target/linux/generic/pending-4.14/611-netfilter_match_bypass_default_table.patch target/linux/generic/pending-4.14/680-NET-skip-GRO-for-foreign-MAC-addresses.patch Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
		
			
				
	
	
		
			53 lines
		
	
	
		
			2.0 KiB
		
	
	
	
		
			Diff
		
	
	
	
	
	
			
		
		
	
	
			53 lines
		
	
	
		
			2.0 KiB
		
	
	
	
		
			Diff
		
	
	
	
	
	
From dd36f935973d91644449bd9749f6062a2bed821b Mon Sep 17 00:00:00 2001
 | 
						|
From: Christian Lamparter <chunkeey@googlemail.com>
 | 
						|
Date: Fri, 7 Jul 2017 17:26:46 +0200
 | 
						|
Subject: misc: owl-loader for delayed Atheros ath9k fixup
 | 
						|
 | 
						|
Some devices (like the Cisco Meraki Z1 Cloud Managed Teleworker Gateway)
 | 
						|
need to be able to initialize the PCIe wifi device. Normally, this is done
 | 
						|
during the early stages of booting linux, because the necessary init code
 | 
						|
is read from the memory mapped SPI and passed to pci_enable_ath9k_fixup.
 | 
						|
However,this isn't possible for devices which have the init code for the
 | 
						|
Atheros chip stored on NAND in an UBI volume. Hence, this module can be
 | 
						|
used to initialze the chip when the user-space is ready to extract the
 | 
						|
init code.
 | 
						|
 | 
						|
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
 | 
						|
Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
 | 
						|
---
 | 
						|
 drivers/misc/Kconfig  | 12 ++++++++++++
 | 
						|
 drivers/misc/Makefile |  1 +
 | 
						|
 2 files changed, 13 insertions(+)
 | 
						|
 | 
						|
--- a/drivers/misc/Kconfig
 | 
						|
+++ b/drivers/misc/Kconfig
 | 
						|
@@ -151,6 +151,18 @@ config SGI_IOC4
 | 
						|
 	  If you have an SGI Altix with an IOC4-based card say Y.
 | 
						|
 	  Otherwise say N.
 | 
						|
 
 | 
						|
+config OWL_LOADER
 | 
						|
+	tristate "Owl loader for initializing Atheros PCI(e) Wifi chips"
 | 
						|
+	depends on PCI
 | 
						|
+	---help---
 | 
						|
+	This kernel module helps to initialize certain Qualcomm
 | 
						|
+	Atheros' PCI(e) Wifi chips, which have the init data
 | 
						|
+	(which contains the PCI device ID for example) stored
 | 
						|
+	together with the calibration data in the file system.
 | 
						|
+
 | 
						|
+	This is necessary for devices like the Cisco Meraki Z1, say M.
 | 
						|
+	Otherwise say N.
 | 
						|
+
 | 
						|
 config TIFM_CORE
 | 
						|
 	tristate "TI Flash Media interface support"
 | 
						|
 	depends on PCI
 | 
						|
--- a/drivers/misc/Makefile
 | 
						|
+++ b/drivers/misc/Makefile
 | 
						|
@@ -13,6 +13,7 @@ obj-$(CONFIG_ATMEL_TCLIB)	+= atmel_tclib
 | 
						|
 obj-$(CONFIG_DUMMY_IRQ)		+= dummy-irq.o
 | 
						|
 obj-$(CONFIG_ICS932S401)	+= ics932s401.o
 | 
						|
 obj-$(CONFIG_LKDTM)		+= lkdtm.o
 | 
						|
+obj-$(CONFIG_OWL_LOADER)	+= owl-loader.o
 | 
						|
 obj-$(CONFIG_TIFM_CORE)       	+= tifm_core.o
 | 
						|
 obj-$(CONFIG_TIFM_7XX1)       	+= tifm_7xx1.o
 | 
						|
 obj-$(CONFIG_PHANTOM)		+= phantom.o
 |