| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
We now have dma-buf support on 3.2 and as such we can
enable nouveau on it.
1 2.6.24 [ OK ]
2 2.6.25 [ OK ]
3 2.6.26 [ OK ]
4 2.6.27 [ OK ]
5 2.6.28 [ OK ]
6 2.6.29 [ OK ]
7 2.6.30 [ OK ]
8 2.6.31 [ OK ]
9 2.6.32 [ OK ]
10 2.6.33 [ OK ]
11 2.6.34 [ OK ]
12 2.6.35 [ OK ]
13 2.6.36 [ OK ]
14 2.6.37 [ OK ]
15 2.6.38 [ OK ]
16 2.6.39 [ OK ]
17 3.0.65 [ OK ]
18 3.1.10 [ OK ]
19 3.2.38 [ OK ]
20 3.3.8 [ OK ]
21 3.4.32 [ OK ]
22 3.5.7 [ OK ]
23 3.6.11 [ OK ]
24 3.7.9 [ OK ]
25 3.8.0 [ OK ]
26 3.9-rc1 [ OK ]
real 24m6.405s
user 666m43.904s
sys 81m27.213s
signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
dma-buf support is added now via compat so there's no need
to ifdef around support for it. Tested with ckmake.
1 2.6.24 [ OK ]
2 2.6.25 [ OK ]
3 2.6.26 [ OK ]
4 2.6.27 [ OK ]
5 2.6.28 [ OK ]
6 2.6.29 [ OK ]
7 2.6.30 [ OK ]
8 2.6.31 [ OK ]
9 2.6.32 [ OK ]
10 2.6.33 [ OK ]
11 2.6.34 [ OK ]
12 2.6.35 [ OK ]
13 2.6.36 [ OK ]
14 2.6.37 [ OK ]
15 2.6.38 [ OK ]
16 2.6.39 [ OK ]
17 3.0.65 [ OK ]
18 3.1.10 [ OK ]
19 3.2.38 [ OK ]
20 3.3.8 [ OK ]
21 3.4.32 [ OK ]
22 3.5.7 [ OK ]
23 3.6.11 [ OK ]
24 3.7.9 [ OK ]
25 3.8.0 [ OK ]
26 3.9-rc1 [ OK ]
real 23m50.218s
user 658m35.410s
sys 80m19.785s
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This is now part of compat. Having this here was
tainting the kernel as its not a module upstream,
its either enabled and built into the kernel or
disabled.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This adds backport support for the first media subsystem
drivers:
* v4l2 - Video4Linux
* uvcvideo - UVC webcam devices
http://linuxtv.org/wiki/index.php/UVC_Webcam_Devices
I've run time tested these modules and build tested
against all kernels against next-20130328.
1 2.6.24 [ OK ]
2 2.6.25 [ OK ]
3 2.6.26 [ OK ]
4 2.6.27 [ OK ]
5 2.6.28 [ OK ]
6 2.6.29 [ OK ]
7 2.6.30 [ OK ]
8 2.6.31 [ OK ]
9 2.6.32 [ OK ]
10 2.6.33 [ OK ]
11 2.6.34 [ OK ]
12 2.6.35 [ OK ]
13 2.6.36 [ OK ]
14 2.6.37 [ OK ]
15 2.6.38 [ OK ]
16 2.6.39 [ OK ]
17 3.0.65 [ OK ]
18 3.1.10 [ OK ]
19 3.2.38 [ OK ]
20 3.3.8 [ OK ]
21 3.4.32 [ OK ]
22 3.5.7 [ OK ]
23 3.6.11 [ OK ]
24 3.7.9 [ OK ]
25 3.8.0 [ OK ]
26 3.9-rc1 [ OK ]
real 23m54.735s
user 660m4.939s
sys 80m26.078s
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The signature for struct bin_attribute.read changed.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
the signature for struct rchan_callbacks.create_buf_file changed.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
drv_set_multicast_list() does not take a pinter but the direct
parameter on kernel < 2.6.35.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This is needed to make the common intel driver module export its
symbols.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This needs to be carried over to linux-3.9.y.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
I manually edited the patch but failed to test it...
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The collateral evolution (CE) on the fb_info data structure
that added the skip_vt_switch element can be simplified
further by replacing the #ifdef hell with a static inline.
Furthermore, if the static inline is added upstream it'd mean
we can get rid of all these static inline replacements for
this data structure element CE.
Cc: cocci@systeme.lip6.fr
Cc: backports@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: Julia Lawall <julia.lawall@lip6.fr>
Cc: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Commit 3cf2667 as of next-20130301 extended the struct fb_info
with a skip_vt_switch to allow drivers to skip the VT switch
at suspend/resume time. For older kernels we can skip this
as all this switch does is call pm_vt_switch_required() with true
or false depending on this new flag and later
pm_vt_switch_unregister() would not have been made.
This patch cannot be broken down further so I'm pegging
this as the first one with 4 digits under the DRM folder
for collateral evolutions. This reflects its as atomic as
is possible. As we'll see on the next commit, these type
of collateral evolutions can best be backported not by
keeping ifdef's as below but instead by using a wrapper
caller, to help reduce with the amount of lines of code
we need. If a static inline is added upstream for these
changes, then no code is required for backporting, at all,
we'd just implement the static inline later upstream as
a no-op.
The tradeoffs to consider for this is if we can live with
these practices upstream, we may be able to support full
subsystems only with a compat module, and no need for
patches. This also means less code and likely less bugs
on the distribution front when backporting is required.
At least IMHO this may be worthy to consider at least to
support kernels listed as supported on kernel.org. We could
just leave the ifdef hell to older unsupported kernels.
Relevant commits below, starting with the first one that
added this new collateral evolution.
commit 3cf2667b9f8b2c2fe298a427deb399e52321da6b
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date: Mon Feb 4 13:37:21 2013 +0000
fb: add support for drivers not needing VT switch at suspend/resume time
Use the new PM routines to indicate whether we need to VT switch at suspend
and resume time. When a new driver is bound, set its flag accordingly,
and when unbound, remove it from the PM's console tracking list.
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
commit 24576d23976746cb52e7700c4cadbf4bc1bc3472
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date: Tue Mar 26 09:25:45 2013 -0700
drm/i915: enable VT switchless resume v3
With the other bits in place, we can do this safely.
v2: disable backlight on suspend to prevent premature enablement on resume
v3: disable CRTCs on suspend to allow RTD3 (Kristen)
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: cocci@systeme.lip6.fr
Cc: backports@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: Julia Lawall <julia.lawall@lip6.fr>
Cc: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This adds intial development kconfig support (make menuconfig).
Synching in kconfig from linux-next next-20130326.
Support is still under development so to enable it
if you want to work on it, just run manually:
make -f scripts/kconfig/Makefile menuconfig
compat already provides its own set of scripts that
computes the kernels you need and spits it out to .config
through the call:
./compat/scripts/gen-compat-config.sh > $(COMPAT_CONFIG)
Perhaps something along these lines will do it:
--- a/Makefile
+++ b/Makefile
@@ -29,6 +29,7 @@ DESTDIR?=
ifneq ($(KERNELRELEASE),)
-include $(COMPAT_CONFIG)
+-include $(BACKPORT_CONFIG)
include $(COMPAT_CONFIG_CW)
NOSTDINC_FLAGS := \
@@ -86,7 +87,8 @@ export CFLAGS += \
# These exported as they are used by the scripts
# to check config and compat autoconf
export COMPAT_CONFIG_CW=$(PWD)/config.mk
-export COMPAT_CONFIG=$(PWD)/.config
+export COMPAT_CONFIG=$(PWD)/compat/.config
+export BACKPORT_CONFIG=$(PWD)/.config
But I'm done for the day.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Synchs with next-20130326
The addition of the new mac80211 driver callback
set_multicast_list() uses the struct netdev_hw_addr_list
added as of 2.6.35. We already dealt with backporting
this collateral evolution through the changes that
went in on for the prepare_multicast() callback, as
well as porting Ethernet driver usage of this. This
is all dealt with on the patch:
patches/collateral-evolutions/network/25-multicast-list_head.patch
Reviewing that gave a quick idea of how to backport this
new callback in a similar way.
commit 488b366a452934141959384c7a1b52b22d6154ef
Author: Alexander Bondar <alexander.bondar@intel.com>
Date: Mon Feb 11 14:56:29 2013 +0200
mac80211: add driver callback for per-interface multicast filter
Some devices have multicast filter capability for each individual
virtual interface rather than just a global one. Add an interface
specific driver callback allowing such drivers to configure this.
Signed-off-by: Alexander Bondar <alexander.bondar@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
1 2.6.24 [ OK ]
2 2.6.25 [ OK ]
3 2.6.26 [ OK ]
4 2.6.27 [ OK ]
5 2.6.28 [ OK ]
6 2.6.29 [ OK ]
7 2.6.30 [ OK ]
8 2.6.31 [ OK ]
9 2.6.32 [ OK ]
10 2.6.33 [ OK ]
11 2.6.34 [ OK ]
12 2.6.35 [ OK ]
13 2.6.36 [ OK ]
14 2.6.37 [ OK ]
15 2.6.38 [ OK ]
16 2.6.39 [ OK ]
17 3.0.65 [ OK ]
18 3.1.10 [ OK ]
19 3.2.38 [ OK ]
20 3.3.8 [ OK ]
21 3.4.32 [ OK ]
22 3.5.7 [ OK ]
23 3.6.11 [ OK ]
24 3.7.9 [ OK ]
25 3.8.0 [ OK ]
26 3.9-rc1 [ OK ]
real 23m32.940s
user 650m11.334s
sys 79m7.021s
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Commit cfe9f9 did indeed fix the new changes on the TI
driver for newer kernels but failed to address the removal
of the wl12xx_hardirq handle no longer required for older
kernels. Fix this.
commit cfe9f97862b7c6eceb25932a6fec32ed0887171b
Author: Luis R. Rodriguez <mcgrof@do-not-panic.com>
Date: Tue Mar 26 16:14:42 2013 -0700
compat-drivers: fix collateral-evolutions/network/09-threaded-irq.patch
Manual edits required due to some context changes. The change
in question that caused this is
commit 97236a0656034ef8512ded648cfaa3d7282534e8
Author: Luciano Coelho <coelho@ti.com>
Date: Fri Mar 8 09:41:53 2013 +0200
wlcore: move handling from hardirq to the irq thread function
Spin locks and completions are expensive in hard IRQ context and cause
problems with RT kernels. In RT kernels, both spin locks and
completions can schedule(), so we can't use them in hard irq context.
Move handling code into the irq thread function to avoid that.
Reported-by: Gregoire Gentil <gregoire@alwaysinnovating.com>
Signed-off-by: Luciano Coelho <coelho@ti.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Manual edits required due to some context changes. The change
in question that caused this is
commit 97236a0656034ef8512ded648cfaa3d7282534e8
Author: Luciano Coelho <coelho@ti.com>
Date: Fri Mar 8 09:41:53 2013 +0200
wlcore: move handling from hardirq to the irq thread function
Spin locks and completions are expensive in hard IRQ context and cause
problems with RT kernels. In RT kernels, both spin locks and
completions can schedule(), so we can't use them in hard irq context.
Move handling code into the irq thread function to avoid that.
Reported-by: Gregoire Gentil <gregoire@alwaysinnovating.com>
Signed-off-by: Luciano Coelho <coelho@ti.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
0005-netlink-portid.patch requies addition of one more hunk.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
nl80211_dump_wiphy() got some huge updates throwing
off the hunks completley. This required some manual
updates.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The nl80211_send_wiphy() routine expects a dev
argument first now, so the first two hunks
required manual adjustments.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The genlog script was giving the incorrect command
we use to generate the log for the kernel, fix this.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
GNU Patch does not yet support giving a different
error return value for patches detected as reversed or
already applied. We can add that support but for now
we distinguish this by grep'ing the results. We nuke
already applied patches, this typically would come from
linux-next, on linux-stable branches given that there is
no linearity between the two.
To support this change however it means we now have
the double amount of time it takes to apply patches
given that we now need a dry run first. The algorithm
for checking if a patch is reversed only works by
analyzing the first hunk of a patch though so perhaps
what we need on GNU Patch is a check for asking if
a patch is reversed, that would not cause much
overhead here, it would just dry run on the first
hunk by reducing the search space considerably.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This correctly copies the pending-stable patches for each
subsystem. When running ./scripts/admin-update.sh -s
we will now stats pending-stable for each subsystem:
compat-drivers code metrics
1320032 - Total upstream lines of code being pulled
network
----------------------------------------
3105 - backport code changes
2602 - backport code additions
503 - backport code deletions
15003 - backport from compat module
18108 - total backport code
1.3718 - % of code consists of backport work
192 - Code changes brought in from pending-stable
124 - Code additions brought in from pending-stable
68 - Code deletions brought in from pending-stable
0.0145 - % of code being cherry picked from pending-stable
drm
----------------------------------------
437 - backport code changes
293 - backport code additions
144 - backport code deletions
15003 - backport from compat module
15440 - total backport code
1.1697 - % of code consists of backport work
Base tree: linux-stable.git
Base tree version: v3.9-rc1
compat.git: compat-v3.9-rc1-1
compat-drivers release: compat-drivers-v3.9-rc1-2-4-g9f5e67f-s
Code metrics archive: http://bit.ly/H6BTF7
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
After we got DRM subsystem support the patches for each
subsystem were separated. Stable patches then need to
be broken down as well. This fixes this and restores
the behaviour allowing us to make -s releases.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Expand the patch documentation so users can know why
they may want to upgrade.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Rename this from:
70-disable-dump-adjust-on-old-kernels.patch
to:
0006-disable-dump-adjust-on-old-kernels.patch
4 digit patches are patches which have undergone review for
breaking it down as much as possible to help with seeing if
some of these can later be expressed as SmPL grammer for usage
with Coccinelle.
At this point SmPL grammer is possible for 0001-netdev_ops.patch
but that is because we have all the other 2 digit patches yet to
break down further.
This patch submitted by Johannes is already well broken down
so rename it to annotate it has been reviewed and is as atomic
as can be.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The netlink callback min_dump_alloc only exists on kernel
3.1 so only enable using it for those kernels. If you're
on an older 64-bit kernel and want this functionality of
resizing the data sent to userspace for a wiphy dump then
you better upgrade.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This was added by Hauke to try to avoid causing compile
errors where old kernels had warnings enabled by default
such as -Werror=unused-but-set-variable. This is a common
error and enabling -Werror would make compilation fail.
The following upstream patch however sould take care of this
by disabling -Werror if *any* -W* flag is found on EXTRA_FLAGS:
commit 6f56b06e74e2805577bf7940dc0fb17b3310d6b6
Author: Chen Gang <gang.chen@asianux.com>
Date: Wed Feb 27 14:55:06 2013 +0800
drivers/net/wireless/ath/wil6210: Makefile, only -Werror when no -W* in EXTRA_CFLAGS
When make with EXTRA_CFLAGS=-W, it will report error.
so give a check in Makefile.
Signed-off-by: Chen Gang <gang.chen@asianux.com>
Acked-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
The change was as follows:
-subdir-ccflags-y += -Werror
+ifeq (, $(findstring -W,$(EXTRA_CFLAGS)))
+ subdir-ccflags-y += -Werror
+endif
Since this is now upstream, just nuke this work around!
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This required a manual fix for one hunk on nl80211.c
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
CONFIG_USB_NET_AX88179_178A is part of the hunk now, this
required a manual update.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
CONFIG_USB_NET_AX88179_178A is now part of the first hunk,
this required a manual update.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Stefan Kuhn <stefan.kuhn@hispeed.ch>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
chip revsion less than C0 has INTX/MSI issue.
this patch should be removed after the kernel drivers/pci/quirks.c
contains this workaround.
Signed-off-by: xiong <xiong@qca.qualcomm.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Adrian is now maintaining the alx tree given that
the BSD OS port work is now on his court.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
All these changes are now merged on Adrian's alx.git tree.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This module is needed by the drm driver now.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This refreshes the patches on next-20130227
Some of the drm patches needed manual editing.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Refresh patches on next-20130220
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
__sock_create() is not available on kernel version < 2.6.37.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Code or other references in the kernel would point to
a file called "COPYING" (as in the upstream kernel),
so rename the GPL file to that name.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Refresh patches on next-20130218.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
drm should be disabled when disable_bt_usb_ethernet is selected. This
disables drm also for e.g. b43.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Refresh patches on next-20130213.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
deactivated
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Refresh patches on linux-next next-20130208
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
drivers/net/wireless/ti/wlcore/scan.c and drivers/net/wireless/ti/wlcore
/event.c need an #include <linux/export.h> to add EXPORT_SYMBOL_GPL on
kernel 3.2 and 3.3.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Some older kernels are missing the declaration of struct inet6_dev in
this file.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
bluetooth hci_core uses a second workqueue.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
kernel version < 2.6.31 does not support tasklet_hrtimer, so deactivate
the driver there.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
This was done against alx-20130124.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
ETH_TEST_FL_EXTERNAL_LB and ETH_TEST_FL_EXTERNAL_LB_DONE are not
available in kernel version < 3.1.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Older kernel version show more warnings like -Werror=unused-but-set-variable
and with this option they are treated as an error.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
devinit and devexit were removed from kernel version 3.8 and using it
causes compile problems.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The addition of the new wil6210 driver added a new ATH_CARDS
option to be used to describe Atheros cards and now uses ATH_COMMON
for the common module ath. This requires fixing the driver-select
script so that the drivers are enabled properly.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
We can skip the make clean process for unified drivers given
that the script that makes compat-drivers releases, gen-releases.sh,
already ensures that we call $(git clean -f -x -d) on each git
tree we are cherry picking code from.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
When using driver-select disable DRM driver sfor 802.11 drivers.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This reverts commit efe0d228ae559546ffea85be9047899f10a13d30.
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Fix section mismatch introduced by removing __devinitconst usage from
the kernel.
WARNING: /home/hauke/compat-wireless/compat-wireless/drivers/net/wireless/ath/ath5k/ath5k.o(.text+0x13898): Section mismatch in reference from the function ath5k_init_leds() to the variable .devinit.rodata:ath5k_led_devices
The function ath5k_init_leds() references
the variable __devinitconst ath5k_led_devices.
This is often because ath5k_init_leds lacks a __devinitconst
annotation or the annotation of ath5k_led_devices is wrong.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
As with the previous commit this follows the kernel.org
model as well as the older releases we were making.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This follows the kernel.org releases as well as our old
releases.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This updates genlog-3.8 so it adds the extra version postfix
number. Even though the Linux kernel release may remain stable
we may at times make a new release of compat-drivers to update
fixes for backporting.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Refreshes patches for next-20130108
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The following two patches adjusted uses of NET_ADDR_RANDOM
on some Ethernet drivers. This change adopts these changes
on the 61-netdev-addr_assign_type.patch patch.
commit 15c6ff3bc0ff3464a8c7efcdea09c86454571622
Author: Jiri Pirko <jiri@resnulli.us>
Date: Tue Jan 1 03:30:17 2013 +0000
net: remove unnecessary NET_ADDR_RANDOM "bitclean"
NET_ADDR_SET is set in dev_set_mac_address() no need to alter
dev->addr_assign_type value in drivers.
Signed-off-by: Jiri Pirko <jiri@resnulli.us>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit e41b2d7fe7803e85e1202d0eb172717d7bf1bbaf
Author: Jiri Pirko <jiri@resnulli.us>
Date: Tue Jan 1 03:30:15 2013 +0000
net: set dev->addr_assign_type correctly
Not a bitfield, but a plain value.
Signed-off-by: Jiri Pirko <jiri@resnulli.us>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The brcmfmac driver was updated recently to only define
pr_fmt() once and it also had the undef for us. Technically
Joe should not have had to add the undef as I previously
went on a crusade to verify that this was not needed at the
driver level so an upstream patch is welcomed to remove that
undef upstream and then to add it for backporting purposes.
commit 79d7c4e8da4ac3cfa98e8e622a17baaeb3c9d29d
Author: Arend van Spriel <arend@broadcom.com>
Date: Wed Jan 2 21:20:10 2013 +0100
brcmfmac: define pr_fmt in one place
Several source files (but not all) define the pr_fmt() macro in exactly
the same way. Instead this commit defines it in a header file so driver
logging is consistent.
Cc: Joe Perches <joe@perches.com>
Reviewed-by: Hante Meuleman <meuleman@broadcom.com>
Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com>
Signed-off-by: Arend van Spriel <arend@broadcom.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
All the suspend resume functions are only activated when
CONFIG_PM_SLEEP is set and not when CONFIG_PM is set.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Fedora doesn't ship lsb_release anymore. So try to read /etc/os-release
to find whether distribution is Fedora.
If Fedora is found, generate a new initramfs suffixed with -compat-drivers
to not override the distribution kernel's default one. Also add a new
kernel entry to grub2 configuration without overriding the default boot
entry.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Silence lsb_release output to avoid command not found errors
on distributions not having lsb_release like Fedora.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
update-initramfs is crucial for DRM drivers, let's clarify this.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Refresh patches again.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The hunks required some manual fixing due to some
new code changes on the alx driver.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This allows you to run git-paranoia on your current directory.
It will return 0 if everything is squeeky clean. This is useful
if for example you want to run a cronjob to update git trees but
never update them if you have any deltas in place of any kind.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This work is now upstream.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
CONFIG_HOTPLUG is going away soon so a few helpers can
be removed now.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
CONFIG_HOTPLUG is going away soon so a few init/remove helpers
are being removed.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The __devexit_p() was removed from a few drivers given that
CONFIG_HOTPLUG is going away.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The patch bellow remove the usage of ksize() so just
remove that hunk.
commit 9caf03640279e64d0ba36539b42daa1b43a49486
Author: Johannes Berg <johannes.berg@intel.com>
Date: Thu Nov 29 01:25:20 2012 +0100
cfg80211: fix BSS struct IE access races
When a BSS struct is updated, the IEs are currently
overwritten or freed. This can lead to races if some
other CPU is accessing the BSS struct and using the
IEs concurrently.
Fix this by always allocating the IEs in a new struct
that holds the data and length and protecting access
to this new struct with RCU.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The -u argument was used to upload releases to kernel.org. Lets
rename this to -r for 'release to kernel.org' given that we have
no introduced -u for unified-drivers support into compat-drivers.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The declarations compat_pci_suspend() and compat_pci_resume()
must be placed before SIMPLE_DEV_PM_OPS().
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The alx Ethernet driver depends on the MDIO module.
This module has UAPI and kernel headers. The headers are
carried over intact to help *both* backport it for older
drivers and also provide the newer driver to other kernels
that may have it enabled after it was introduced in 2.6.31.
The way support for MDIO is enabled is by carrying over both
the UAPI and Linux kernel header files along with the module
with in compat-drivers. The exported symbols of the module
however are renamed with a compat_* prefix within compat
in include/linux/compat-2.6.31.h. This enables Linux
distributions shipping a driver that depends on older
versions of the MDIO to keep using it while allowing the
supplied drivers in compat-drivers to become users of
the newer module it likely will require a tighter
dependency on.
An alternative to using different exported symbol names
is for compat-drivers to work under a separate namespace
and while I hear some folks already implemented that support
we never got those patches sent to us.
C'est la vie.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Hauke had sent out patches to help clean up
the pm run time callbacks to allow this patch
to be simplified. This takes care of the
required changes.
This goes compile tested against next-20121203
mcgrof@drvbp1 ~/devel/compat-drivers (git::master)$ time ckmake
Trying kernel 3.6.5-030605-generic [OK]
Trying kernel 3.5.7-030507-generic [OK]
Trying kernel 3.4.17-030417-generic [OK]
Trying kernel 3.3.8-030308-generic [OK]
Trying kernel 3.2.33-030233-generic [OK]
Trying kernel 3.1.10-030110-generic [OK]
Trying kernel 3.0.50-030050-generic [OK]
Trying kernel 2.6.39-02063904-generic [OK]
Trying kernel 2.6.38-02063808-generic [OK]
Trying kernel 2.6.37-02063706-generic [OK]
Trying kernel 2.6.36-02063604-generic [OK]
Trying kernel 2.6.35-02063513-generic [OK]
Trying kernel 2.6.34-02063413-generic [OK]
Trying kernel 2.6.33-02063320-generic [OK]
Trying kernel 2.6.32-02063260-generic [OK]
Trying kernel 2.6.31-02063113-generic [OK]
Trying kernel 2.6.30-02063010-generic [OK]
Trying kernel 2.6.29-02062906-generic [OK]
Trying kernel 2.6.28-02062810-generic [OK]
Trying kernel 2.6.27-020627-generic [OK]
Trying kernel 2.6.26-020626-generic [OK]
Trying kernel 2.6.25-020625-generic [OK]
Trying kernel 2.6.24-020624-generic [OK]
real 18m42.239s
user 327m50.029s
sys 53m37.317s
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The commit below removed by mistake some entries on the top
level Makefile.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This updates the hunks that deal with the netdevice
features. We no longer need device checks given that
the driver no longer supports atl1c devices.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This splits up admin-update.sh into a few sections
by separating functionality into routine helpers.
This allows us to add base refresh with -b so that
drivers that only need the base code can update the
compat labels.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
I've tested this on Debian now.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This updates the refresh-compat scripts to account for
having patches in extended directories.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Companies typically write Linux device drivers either from
scratch of alternatively based on some internal unified
source code tree. Typically the unified driver architecture
is a mess and porting a driver to linux is always a painful
task to the extent at times a full rewrite is required and
at times preferred.
In order to try to help with these type of unified driver
strategies one possibility that has been proposed is to
make the unified driver strategy an open source project and
to not make many compromises on the style and requirements
for Linux. The alx Linux driver [1] is not yet upstream and
is undergoing changes to try to accomodate it to a format
and use new technologies to help address unification attempts
in both an open manner and also lead by the community.
compat-drivers will support these type of driver efforts
only if they adhere to the principles of never compromising
Linux upstream requirements and are targetting getting
upstream into the Linux kernel. Once these drivers are upstream,
their respective git trees will be removed and we'll simply
cherry pick the driver as we do from upstream Linux. If a
compat-drivers releases contains drivers that are from a
unified git repository the release will be postfixed with
a "-u".
[1] http://www.linuxfoundation.org/collaborate/workgroups/networking/alx
Cc: Julia Lawall <julia.lawall@lip6.fr>
Cc: Adrian Chadd <adrian@freebsd.org>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The number of patch directories for the different life
cycle a patch can be on its way upstream had reached 4:
* pending-stable
* linux-next-pending
* linux-next-cherry-picks
* crap
Apart from this we also had the backport related patches.
In the future I see potential for other directories for
different categories of patches. Consider how we are
breaking down the backport patches into specific documented
collateral evolutions and of those type of collateral
evolutions there may be different types of collateral
evolutions which we could likely treat / document differently.
Another type of patch that I forsee us having to deal with
are patches for drivers that are not upstrea -- like crap,
but for drivers in a unified driver tree that is *designed*
from scratch to be targetting upstream Linux inclusion using
the same coccinelle technology I forsee us using for backporting
collateral evolutions.
Since the number of patch directories can get out of hand
at the top level lets just stuff then all under patches/
and deal with patches there. This also places the backport
patches into a directory called collateral-evolutions/ to
help promote and educate on the nature of the changes
that we have to deal with when backporting.
Cc: Julia Lawall <julia.lawall@lip6.fr>
Cc: Adrian Chadd <adrian@freebsd.org>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Without this patch the patches are applied in the natural sort order of
numbers, which caused this order for patches/network/:
patches/network/0001-netdev_ops.patch
patches/network/02-ksize.patch
patches/network/0002-net-misc.patch
patches/network/0003-netdev-needed_headroom_tailroom.patch
patches/network/03-rfkill.patch
patches/network/04-netns.patch
patches/network/0004-wext-namespace.patch
patches/network/0005-netlink-portid.patch
patches/network/05-usb.patch
The non natural sort order of numbers is more the intended way to order
the patches as now the spdiff patches are in front of all the other
patches. This makes the patches in patches/network/ to be applied in
the flowing order:
patches/network/0001-netdev_ops.patch
patches/network/0002-net-misc.patch
patches/network/0003-netdev-needed_headroom_tailroom.patch
patches/network/0004-wext-namespace.patch
patches/network/0005-netlink-portid.patch
patches/network/02-ksize.patch
patches/network/03-rfkill.patch
patches/network/04-netns.patch
patches/network/05-usb.patch
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
In the past refresh with quilt was just run for the last patch
directory being applied and not for all, because our script had
problems when patchRefresh() was called more then once in a single
admin-update.sh run. This was fixed in the last patch and now it is
safe to run it on all patches.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The refresh script is able to take an already existing quilt run and
just refresh the further needed patches. This is needed to make it
possible to manually fix a patch which is not applying any more and
then automatically integrate it into the patches directory again. With
the integration of drm it could happen that quilt is running on two
different source directories like patches/network and patches/drm in one
call of admin-update.sh. If some of the drm patches did not apply and
needed a manual fix, quilt moved the patch in the second run into the
patches/network directory, because it was taken in the network refresh
run. This patch does not run quilt if there is still an unfinished
quilt job for a different patch directory.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
There is no README file in the patches folder like patches/drm/README
any more.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
In the old version patches.orig/<patch name>.patch was printed as the
current patch quilt is working on in refresh, now e.g. patches/network
/<patch name>.patch is printed.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
struct spinlock does not exists on kernel version <= 2.6.32, use
spinlock_t instead.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
On kernel version <= 2.6.28, I saw the following compile error without
this patch:
/net/wireless/util.c: In function ‘cfg80211_get_p2p_attr’:
/net/wireless/util.c:1120:4: error: implicit declaration of function
‘get_unaligned_le16’ [-Werror=implicit-function-declaration]
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This was done by running "./scripts/admin-refresh.sh refresh".
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This driver is building on all supported kernel versions.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The alx driver was removed from crap and also remove the config option.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
mwifiex got Multiqueue support and while we do port multiqueue
I'm really fucking lazy to port this driver particular changes
over given that I really don't think anyone on planet earth will
be using it for kernels older than 2.6.27.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Note this driver is disabled for now. I really want to start
applying SmPL for porting this driver for all known collateral
evolutions. At least for the netdev_attach_ops() one.
I'm adding this in to help build the tree as without this the
compilation was failing.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
When config symbols are renamed they should be renamed at all places
and not just at some places.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The driver at least compiles with all supported kernel versions.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The device driver was removed from crap some time ago.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The device driver was removed from the kernel some time ago.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This option is not available any more.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
acpi_get_table_with_size() was exported with kernels >= 3.6. Revert the
size checking for kernels < 3.6.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Prefix it with CONFIG_COMPAT_ to allow setting it correctly.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Add GPU subsystem information to README.md.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Enable Nouveau DRM driver for kernels >= 3.3.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The comments were wrong causing a misunderstanding while analyzing
the script's function.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This was forgotten during the generation of the renaming patch.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
No configuration change was retriggering config update because
of this missing line unless you give the 'bt' target.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Nouveau used 2 Kconfig defined vars to set debugging log levels.
Rename to for being able to set them from config.mk correctly.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Some Kconfig variables take integer values instead of y/m/N like
CONFIG_NOUVEAU_DEBUG and CONFIG_NOUVEAU_DEBUG_DEFAULT. Currently all
values other than y/m/N were escaped with double-quotes to define
them as strings. Fix this to allow integer values for Kconfig
variables.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This was introduced with the latest nouveau code rewrite. Copy
this directory too.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This was added in 3.4. Rename the option in the relevant source file
and enable CONFIG_COMPAT_DRM_LOAD_EDID_FIRMWARE in config.mk to build
the symbol into DRM_KMS_HELPER kernel module.
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Add a subsystem marker before code metrics to differentiate between
multiple subsystems, e.g. drm, network, etc.:
compat-drivers code metrics
1181683 - Total upstream lines of code being pulled
network
----------------------------------------
3109 - backport code changes
2580 - backport code additions
529 - backport code deletions
12754 - backport from compat module
15863 - total backport code
1.3424 - % of code consists of backport work
drm
----------------------------------------
301 - backport code changes
219 - backport code additions
82 - backport code deletions
12754 - backport from compat module
13055 - total backport code
1.1048 - % of code consists of backport work
Signed-off-by: Ozan Çağlayan <ozancag@gmail.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Sujith reported that building after admin-update.sh network
we get a build error with drm. Fix this by creating an empy
drm Makefile.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Forgot to add the target directory for kup upload on the
ChangeLog file.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This will now produce something like: ChangeLog-v3.7-rc1-4
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This will generate log files for our releases.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This should fix uploading via kup using scripts/gen-release.sh
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This adds support for uploading stable compat-drivers releases.
The new stable releases will go on:
http://www.kernel.org/pub/linux/kernel/projects/backports/stable/
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The replacement was removing the 's' from the compat-drivers
name, and generating 'compat-driers'. We don't yet backport
support for laundry machines so fix this.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The rfkill.h header was moved to the UAPI path,
copy it over. But there is one more issue we would
need to address.
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.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This can be reverted once wil6210 get into Linux upstream.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This can be reverted once the driver gets onto Linux upstream.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Moving forward no full drivers will be accepted
into crap/. As the alx drivers has proven this only
slows down access to getting users a proper driver.
Restricting the driver to be made available only
through compat-drivers has provided less visibility
and access to the drivers.
The purpose of adding drivers into crap/ over upstream
drivers/staging/ was that some developers may prefer to
not go through the staging development process if they
were sure they could meet the proper upstream quailty
criteria in a timely manner. Practice shows that even
if this is claimed in the end the driver just ends up
bit rotting away in crap/ over a few kernel releases.
Lets stop that. If you want your driver accessible or
automatically backported you have two options:
* Linux upstream drivers/staging/
* Linux upstream proper
Choose wisely.
The additional patch directories then remain useful
only for patches content that is already present on
Linux upstream, nothing more.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This will let us ensure we can query these files for
stable patch generation purposes.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The kernel make file uses an include path of kernel/include,
kernel/include/uapi (I removed all the other unrelated paths). Now
compat-drivers should also use this path otherwise we have to patch
many files. With this patch for compat-drivers it creates a include
path like this: w-d/include, w-d/include/uapi, kernel/include,
kernel/include/uapi that way this is similar to the way the kernel does
it.
When copying all the upai headers like it was done before in compat-
drivers, some headers in c-d/include/uapi will overwrite some important
headers in the kernel, we should just copy the files we actually need.
With this patch compat-drivers compiles for me against my Ubuntu 3.2
kernel, it still fails on some other kernel versions, with as I see it,
uapi unrelated errors.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The patch was posted for inclusion upstream. The
DRM code uses some include headers and if we are
not specific about the path what ends up happening
is our old kernel header files gets used instead of
the new UAPI header files.
For details on the UAPI changes:
http://lwn.net/Articles/507794/
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
For details on the new UAPI changes see:
http://lwn.net/Articles/507794/
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
When making a kernel.org release you should use gen-release.sh -u,
so just checking for the usage of that variable is better.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This should be used for those who really know what
they are doing and making proper releases. This will
force using 'git clean -x -d -f'. You really should
understand what this does before you use this.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Be a bit more descriptive on usage for flags.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
gen-release.sh is updated to force git-paranoia to run
git clean for us when uploading to kernel.org. Note
that usage of kup is only for kernel.org uploading
and as such not for the faint of heart.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
git clean can be used to further sanitize releases.
git clean -x -d -f
Will spit shine your release from any even files
you may have lying around that you tell git to
ignore. We use the -n option to git clean to warn
the user of unwanted content. If someone is really
make releases they should read and understand
git clean man pages and also understand that
running git-paranoia with -c will wipe out clean
all content found by 'git clean -x -d -n'.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
The config value should be set to a lowercase 'm' or the config is
ignored and the associated module doesn't build. Fix this.
Signed-off-by: Kyle Manna <kyle.manna@fuel7.com>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This fixes patches/drm/98-pr_fmt.patch for next-20121008
for header path updates for DRM drivers.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
This fixes the patch patches/drm/04-revert-prime-support.patch
for next-20121008. There is quite a bit of changes with hunk
differences that required manual editing.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Brought to us by Intel via:
commit 903e45411099ae8292f5ce637ad0c72f6fef61db
Author: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
Date: Thu Sep 27 17:26:09 2012 +0300
Bluetooth: AMP: Use HCI cmd to Read Loc AMP Assoc
When receiving A2MP Get AMP Assoc Request execute Read Local AMP Assoc
HCI command to AMP controller. If the AMP Assoc data is larger than it
can fit to HCI event only fragment is read. When all fragments are read
send A2MP Get AMP Assoc Response.
Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Required manual intervention due to hunk differences.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Hunk offsets differences required manual intervention.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Ozan Çağlayan had done most of the work to suck in all
the DRM drivers but left out the enablement of compiling
the drm drivers. The DRM drivers were also not load
tested. This patch enables to test compilation by
renaming the DRM Kconfig options with a _COMPAT prefix
and enables compilation by default for the i915 drm
driver which I can test against at run time on my
laptop running on v3.2.
Users and developer can help enable older kernels
down to 3.0 (as this was the oldest supported target
kernel for DRM drivers) or other DRM drivers as they
are run time tested.
The admin-update.sh script is modified to now always
run by including the DRM code and patching it accordingly.
If you happen to only want networking code you can do so
by supplying the network argument to the script as follows:
./scripts/adming-update.sh network
This will disable taking in DRM code.
It should be noted that although only the i915 drm driver
is being enabled all other drivers except the following have
been test compiled to work down to v3.0.
-obj-$(CONFIG_COMPAT_DRM_TDFX) += tdfx/
-obj-$(CONFIG_COMPAT_DRM_R128) += r128/
-obj-$(CONFIG_COMPAT_DRM_MGA) += mga/
-obj-$(CONFIG_COMPAT_DRM_SIS) += sis/
-obj-$(CONFIG_COMPAT_DRM_SAVAGE)+= savage/
-obj-$(CONFIG_COMPAT_DRM_EXYNOS) +=exynos/
-obj-$(CONFIG_COMPAT_DRM_UDL) += udl/
Apart from the above drivers we should be able to enable the
other drivers as reports come in for run time testing on them.
As it is right now only the i915 goes run time tested -- by me.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Backport e2377fe0b -- this could likely be implemented
on compat.git but I'd much prefer a better review of that.
For now this stays as a patch.
commit e2377fe0b65e3c7577ff6df1701c56ef477d336f
Author: Hugh Dickins <hughd@google.com>
Date: Mon Jun 27 16:18:19 2011 -0700
drm/i915: use shmem_truncate_range
The interface to ->truncate_range is changing very slightly: once "tmpfs:
take control of its truncate_range" has been applied, this can be applied.
For now there is only a slight inefficiency while this remains unapplied,
but it will soon become essential for managing shmem's use of swap.
Change i915_gem_object_truncate() to use shmem_truncate_range() directly:
which should also spare i915 later change if we switch from
inode_operations->truncate_range to file_operations->fallocate.
Signed-off-by: Hugh Dickins <hughd@google.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Keith Packard <keithp@keithp.com>
Cc: Dave Airlie <airlied@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Kernels older than 3.6 don't have intel_enable_gtt() exported
and most Linux distributions have CONFIG_AGP_INTEL as built-in
(y) and as such we don't bother to make it available as
modular here. The change to export intel_enable_gtt() was
made through commit 8ecd1a66 but previous to this the driver
never called intel_enable_gtt() so we can safely assume we
can do the same for older kernels.
There should be a way to export an intel_enable_gtt() for
kernels with CONFIG_AGP_INTEL as built-in but that itself
is a project.
commit 8ecd1a6615f0d9de6759aafe229bc1cc4ee99c7b
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Thu Jun 7 15:56:03 2012 +0200
drm/i915: call intel_enable_gtt
When drm/i915 is in control of the gtt, we need to call
the enable function at all the relevant places ourselves.
Reviewed-by: Jani Nikula <jani.nikula@linux.intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
This now goes with i915 run time tested against 3.2.0-3-amd64
and code extrated from linux-next next-20120926.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
|
Turns out DRM drivers use this:
#include "drmP.h"
Instead of:
#include <drm/drmP.h>
Withtout this change we are using the older kernel's header
file and not the one we are cherry pickng over from the kernel
we want to help backport.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
|
