diff options
Diffstat (limited to 'patches')
3 files changed, 0 insertions, 81 deletions
diff --git a/patches/collateral-evolutions/network/0008-rfkill.patch b/patches/collateral-evolutions/network/0008-rfkill.patch deleted file mode 100644 index 7e494a10..00000000 --- a/patches/collateral-evolutions/network/0008-rfkill.patch +++ /dev/null @@ -1,52 +0,0 @@ -rfkill was re-implemented on 2.6.31. We port it to -older kernels with a simple hack, just rename the -module as a new one rfkill_backport, and every -exported symbol gets redefined with a _backport -postfix through compat-2.6.31.h. The changes below -are the ones we could not do through compat-2.6.31.h - -Do older kernels have /dev/rfkill ? I not then we can -just keep /dev/rfkill and not /dev/rfkill_backport. - -Note that 2.6.31 added netdevice notifier upon interface -dev_open() which on cfg80211 will check if checks to see -if rfkill is enabled (or if the mode of operation is not -supported) on the cfg80211_netdev_notifier_call() and if -so deny bringing the interface up. This was added via -commit: - -3b8bcfd5d31ea0fec58681d035544ace707d2536 - -Since older kernels will not have the notifier call -on dev_open() if we *really want* to port this we could have -mac80211's subif_open() call : - - ret = call_netdevice_notifiers(NETDEV_PRE_UP, dev); - ret = notifier_to_errno(ret); - if (ret) - return ret; - -This would do the policing from within mac80211. - ---- a/net/rfkill/core.c -+++ b/net/rfkill/core.c -@@ -826,7 +826,7 @@ static int rfkill_resume(struct device * - } - - static struct class rfkill_class = { -- .name = "rfkill", -+ .name = "rfkill_backport", - .dev_release = rfkill_release, - .dev_attrs = rfkill_dev_attrs, - .dev_uevent = rfkill_dev_uevent, ---- a/net/rfkill/input.c -+++ b/net/rfkill/input.c -@@ -230,7 +230,7 @@ static int rfkill_connect(struct input_h - - handle->dev = dev; - handle->handler = handler; -- handle->name = "rfkill"; -+ handle->name = "rfkill_backport"; - - /* causes rfkill_start() to be called */ - error = input_register_handle(handle); diff --git a/patches/collateral-evolutions/network/66-uapi-changes/INFO b/patches/collateral-evolutions/network/66-uapi-changes/INFO deleted file mode 100644 index aac02254..00000000 --- a/patches/collateral-evolutions/network/66-uapi-changes/INFO +++ /dev/null @@ -1,18 +0,0 @@ -The UAPI changes split up the kernel and userspace API -headers into separate directories. We provide backport -support for the new rfkill module to kernels older than -2.6.31. To allow us to dynamically provide only backport -support for those kernels we have a trick within compat -to provide its own include/linux/rfkill.h header which -then will include either your own kernel's rkfill.h or -include the one we are taking from linux-next. The one -we take from linux-next is renamed to rfkill_backport.h. -In order to allow the call to include your own kernel's -rfkill.h the compat rfkill.h uses include_next. The UAPI -changes would mean though that instead of getting your -own kernel's rfkill.h you'd end up getting the UAPI -header file. Fix this by ensuring that for new kernels -we linux_next into the user's kernels rfkill.h and if -the kernel is old we still to the rfkill_backport.h -naming scheme. - diff --git a/patches/collateral-evolutions/network/66-uapi-changes/include_linux_rfkill_backport.patch b/patches/collateral-evolutions/network/66-uapi-changes/include_linux_rfkill_backport.patch deleted file mode 100644 index f5d69d4f..00000000 --- a/patches/collateral-evolutions/network/66-uapi-changes/include_linux_rfkill_backport.patch +++ /dev/null @@ -1,11 +0,0 @@ ---- a/include/linux/rfkill_backport.h -+++ b/include/linux/rfkill_backport.h -@@ -18,7 +18,7 @@ - #ifndef __RFKILL_H - #define __RFKILL_H - --#include <uapi/linux/rfkill.h> -+#include <uapi/linux/rfkill_backport.h> - - /* don't allow anyone to use these in the kernel */ - enum rfkill_user_states { |