On Jan 7, 2008 11:02 AM, Hauke Mehrtens [EMAIL PROTECTED] wrote:
There is an other Problem.
iwconfig shows me Bit Rate=1 Mb/s the hole time, but I'm able to
download with an average of 440K/s as wget says.
It's with PID rate control algorithm.
Thanks for reporting this, how'd it go with
On Jan 11, 2008 5:39 PM, Hauke Mehrtens [EMAIL PROTECTED] wrote:
Luis R. Rodriguez wrote:
On Jan 7, 2008 11:02 AM, Hauke Mehrtens [EMAIL PROTECTED] wrote:
Thanks for reporting this, how'd it go with simple rate control
algorithm instead?
How do I change from pid to simple rate control
this is not true for the exception.
lib/iomap.c | 11 ---
1 files changed, 8 insertions(+), 3 deletions(-)
Signed-off-by: Luis R. Rodriguez [EMAIL PROTECTED]
Luis
diff --git a/lib/iomap.c b/lib/iomap.c
index 864f2ec..33651f8 100644
--- a/lib/iomap.c
+++ b/lib/iomap.c
@@ -247,9 +247,14
On 9/18/07, Alan Cox [EMAIL PROTECTED] wrote:
On Mon, 17 Sep 2007 16:22:07 -0400
Luis R. Rodriguez [EMAIL PROTECTED] wrote:
This patch updates the pci_iomap() kernel-doc to make it clarify the
case when read*()/write*() can be called over ioread*/iowrite*(). When
driver writers read
On 9/18/07, Linus Torvalds [EMAIL PROTECTED] wrote:
On Tue, 18 Sep 2007, Luis R. Rodriguez wrote:
Alright, here is the same patch inline with s/recommended/required/
language:
Well, the thing is, I'm not at all sure that I agree with this.
If you use ioport_map/unmap, then you really
On 9/18/07, Luis R. Rodriguez [EMAIL PROTECTED] wrote:
On 9/17/07, Jiri Slaby [EMAIL PROTECTED] wrote:
On 09/17/2007 10:59 PM, Jeff Garzik wrote:
Jiri Slaby wrote:
NACK, this is wrong. iomap returns platform dependant return value,
which may or
Incorrect. readl() and writel
On 9/17/07, Jiri Slaby [EMAIL PROTECTED] wrote:
On 09/17/2007 10:59 PM, Jeff Garzik wrote:
Jiri Slaby wrote:
NACK, this is wrong. iomap returns platform dependant return value,
which may or
Incorrect. readl() and writel() work just fine on all existing
platforms where Atheros may be
On 9/18/07, Linus Torvalds [EMAIL PROTECTED] wrote:
On Tue, 18 Sep 2007, Luis R. Rodriguez wrote:
ACK -- driver developers use this just to save themselves a few lines
from calling pci_resource_start() and friends. How about having an
inline which does what pci_iomap() does except
On 9/18/07, Linus Torvalds [EMAIL PROTECTED] wrote:
On Tue, 18 Sep 2007, Luis R. Rodriguez wrote:
An extra branch is created on MMIO-only devices on read/writes on the
IO_COND macro using this interface -- or is this optimized out?
Umm. Does anybody actually have any performance numbers
On 9/19/07, Tim Bird [EMAIL PROTECTED] wrote:
Recently, the CE Linux forum has been working to revive the
Linux-tiny project. At OLS, I asked for interested parties
to volunteer to become the new maintainer for the Linux-tiny patchset.
A few candidates came forward, but eventually Michael
I have a USB libertas 1286:2001 with bcdDevice 30.06 (from lsusb -v).
I tried downloading the firmware from marvell:
https://www.marvell.com/drivers/driverDisplay.do?dId=160pId=38
renaming and to usb8388.bin and putting it in firmware dir. Is this
the right firmware??
Upon load this is what I
not available
fix it with adjust the order of inline function body.
Signed-off-by: Dave Young [EMAIL PROTECTED]
Acked-by: Luis R. Rodriguez [EMAIL PROTECTED]
Thanks Dave. What version of gcc were you using? I haven't run into this.
BTW, nothing new was added in this patch, things were just
On Jan 5, 2008 9:47 AM, Hauke Mehrtens [EMAIL PROTECTED] wrote:
Hi
Now the compat-wireless-2.6 package is working and I get an Internet
connection with my rtl8187 based card. (It's on an ASUS P5B Deluxe)
I used the compat-wireless-2.6 package for this log, but I have the same
problem with
On Thu, Oct 4, 2012 at 6:34 PM, xi...@qca.qualcomm.com wrote:
From: xiong xi...@qca.qualcomm.com
1. support new device id (0x10A0/0x10A1).
2. add DEBUG_FS interface for diag/swoi functions.
Signed-off-by: Ren Cloud cj...@qca.qualcomm.com
Signed-off-by: xiong xi...@qca.qualcomm.com
Xiong,
On Mon, Oct 8, 2012 at 5:42 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Mon, Oct 08, 2012 at 03:25:08PM -0700, Luis R. Rodriguez wrote:
On Thu, Oct 4, 2012 at 6:34 PM, xi...@qca.qualcomm.com wrote:
From: xiong xi...@qca.qualcomm.com
1. support new device id (0x10A0/0x10A1
From: Luis R. Rodriguez mcg...@do-not-panic.com
Here are a few minor updates to the UAPI changes [0]. The first
one is to help with the backport effort [1], the second one is
simply space cosmetic change to address my eyes bleeding
while reviewing the changes on next-20121012 with git
From: Luis R. Rodriguez mcg...@do-not-panic.com
The UAPI changes split kernel API and userspace API
content onto two separate header files. The userspace
API drm content was moved to include/uapi/drm/ with the
same file name while kernel specific API content was
kept under include/drm
From: Luis R. Rodriguez mcg...@do-not-panic.com
No functional changes.
Cc: dri-de...@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org
Cc: de...@driverdev.osuosl.org
Cc: backpo...@vger.kernel.org
Cc: Rob Clark r...@ti.com
Cc: Arnd Bergmann a...@arndb.de
Cc: Dave Jones da...@redhat.com
Cc
On Sat, Oct 13, 2012 at 3:33 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Luis,
On Friday 12 October 2012 16:49:31 Luis R. Rodriguez wrote:
From: Luis R. Rodriguez mcg...@do-not-panic.com
The UAPI changes split kernel API and userspace API
content onto two separate
On Tue, Oct 16, 2012 at 5:34 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Luis,
On Saturday 13 October 2012 10:00:42 Luis R. Rodriguez wrote:
On Sat, Oct 13, 2012 at 3:33 AM, Laurent Pinchart wrote:
On Friday 12 October 2012 16:49:31 Luis R. Rodriguez wrote:
From: Luis
On Mon, Oct 8, 2012 at 6:24 PM, Huang, Xiong xi...@qca.qualcomm.com wrote:
Hi Luis
I'm refining the code, I try my best to make it upstream ASAP. Thanks !
Ok great thanks, in that case I'm going to make it policy moving
forward to simply not take in full drivers at all into compat-drivers
Our guidelines for patches [1] for Linux-wireless has been updated.
One section asks Linux-wireless developers to subscribe to the patch
guideline wiki page (section 2) and another which introduces the new
'Changes-licensed-under' (section 10).
Here I'll cover the new 'Changes-licensed-under' tag
I urge developers to not bait into this and just leave this alone.
Those involved know what they are doing and have a strong team of
attorneys watching their backs. Any *necessary* discussions are be
done privately.
Luis
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
On 9/1/07, Constantine A. Murenin [EMAIL PROTECTED] wrote:
On 01/09/07, Jeff Garzik [EMAIL PROTECTED] wrote:
Jason Dixon wrote:
Once the grantor (Reyk) releases his code under that license, it must
remain. You are free to derive work and redistribute under your
license, but the
On 9/5/07, Michael Buesch [EMAIL PROTECTED] wrote:
On Wednesday 05 September 2007, Reyk Floeter wrote:
I'm the author of the free hardware driver layer for wireless Atheros
devices in OpenBSD, also known as OpenHAL.
I'm still trying to get an idea about the facts and the latest state
of
On 8/28/07, Christoph Hellwig [EMAIL PROTECTED] wrote:
On Tue, Aug 28, 2007 at 12:00:50PM -0400, Jiri Slaby wrote:
ath5k, license is GPLv2
The files are available only under GPLv2 since now.
Is this really a good idea? Most of the reverse-engineering was
done by the OpenBSD folks, and
On 7/31/07, Mariusz Kozlowski [EMAIL PROTECTED] wrote:
Signed-off-by: Mariusz Kozlowski [EMAIL PROTECTED]
Acked-by: Luis R. Rodriguez [EMAIL PROTECTED]
drivers/net/wireless/prism54/oid_mgt.c | 25377 - 25297 (-80 bytes)
drivers/net/wireless/prism54/oid_mgt.o | 128460 - 128284 (-176 bytes
Anyone heard of Margit Schubert recently? I have stopped hearing from
her. She was actively working on prism54 and all of a sudden
disappeared. IIRC her husband last told me she was sick...
Luis
--
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84 A34A 6ADD 4937 E20A 525E
On Thu, Apr 4, 2013 at 11:27 AM, Adrian Chadd adr...@freebsd.org wrote:
Hi,
Here's my first take on the version number policy:
https://github.com/qca/open-ath9k-htc-firmware/wiki/VersionPolicy
The summary:
* major version number changes are for firmware API / behaviour
changes that
From: Luis R. Rodriguez mcg...@do-not-panic.com
It is questionable if we'd want to backport calls declared
through late_initcall() or core_initcall() on the kernel
but if this ends up being desired the current of copying
kernel code requires either patching or redefining these
symbols to make
From: Luis R. Rodriguez mcg...@do-not-panic.com
This is enabled only for = 3.2 and enables all regulator
drivers. This is required by some media subsystem drivers.
Signed-off-by: Luis R. Rodriguez mcg...@do-not-panic.com
---
backport/Makefile.kernel |1 +
backport
From: Luis R. Rodriguez mcg...@do-not-panic.com
This adds backport support for all media subsystem
drivers. This is enabled only for = 3.2.
Signed-off-by: Luis R. Rodriguez mcg...@do-not-panic.com
---
.blacklist.map |9 +
backport/Makefile.kernel
From: Luis R. Rodriguez mcg...@do-not-panic.com
This is just test work I've been doing on the side, that really
just started from scratching an itch to see what is possible.
In the compat-drivers trees I had actually gotten to run time
test the USB video camera driver and that worked fine. Under
On Sat, Apr 6, 2013 at 7:35 PM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
Segmentation fault
make[8]: *** [/home/mcgrof/tmp/build/compat/core.o] Error 139
And sorry, *this* set should have gone out as RFCs, not PATCH. The
other 9 should be fine if we just run ckmake to test them.
Luis
On Sat, Apr 6, 2013 at 7:37 PM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
On Sat, Apr 6, 2013 at 7:35 PM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
Segmentation fault
make[8]: *** [/home/mcgrof/tmp/build/compat/core.o] Error 139
I've narrowed the segfault to a core.c file
Do we have a central place to centrally document ARM development
upstream? I'd like to start using a central place to start documenting
things for some stuff I'd like to work on and I don't want to use any
vendor specific stuff. Are we go happy with using elinux.org ? If so
can we add a reference
On Wed, Apr 10, 2013 at 10:20 AM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2013-04-10 at 10:13 -0700, Luis R. Rodriguez wrote:
On Wed, Apr 10, 2013 at 6:22 AM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2013-04-10 at 04:35 -0700, Luis R. Rodriguez wrote:
From: Luis
Curious if anyone has worked on latency and jitter benchmarks in using
netlink, specifically with nl80211. Has anyone benchmarked this? Ben,
have you? If not for nl80211 perhaps this has been done before for
other netlink families?
Luis
--
To unsubscribe from this list: send the line
On Wed, Apr 10, 2013 at 10:59 AM, Ben Greear gree...@candelatech.com wrote:
On 04/10/2013 10:55 AM, Luis R. Rodriguez wrote:
Curious if anyone has worked on latency and jitter benchmarks in using
netlink, specifically with nl80211. Has anyone benchmarked this? Ben,
have you
On Wed, Apr 10, 2013 at 11:20 AM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2013-04-10 at 10:26 -0700, Luis R. Rodriguez wrote:
I guess I'd have to review the async API,
Yeap, reviewing the commit noted would help too.
Yeah ... :)
What's the use of just this when you don't
On Wed, Apr 10, 2013 at 12:27 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2013-04-10 at 12:19 -0700, Luis R. Rodriguez wrote:
However, it seems entirely pointless to backport just a small part of
the API?
Oh I agree don't get me wrong, however porting kernel/async.c seems
On Wed, Apr 10, 2013 at 12:39 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2013-04-10 at 12:32 -0700, Luis R. Rodriguez wrote:
Oh I agree don't get me wrong, however porting kernel/async.c seems
like a rather separate effort worth considering. As-is though I have
not seen any
From: Luis R. Rodriguez mcg...@do-not-panic.com
This backports the latest regulator drivers for kernels = 3.4.
We enable the regulator only on kernels = 3.4 given that
it relies on the new probe deferral mechanism which would
otherwise mean having to support drivers that do not probe
correctly
From: Luis R. Rodriguez mcg...@do-not-panic.com
This adds backport support for all media subsystem
drivers. This is enabled only for = 3.2. Some media
drivers rely on the new probe deferrral mechanism
(-EPROBE_DEFER see commit d1c3414c), those are only
enabled for kernels = 3.4. Some media
On Thu, Mar 28, 2013 at 9:19 AM, Julia Lawall julia.law...@lip6.fr wrote:
On Thu, 28 Mar 2013, Jesse Barnes wrote:
- info-skip_vt_switch = true;
+ fb_enable_skip_vt_switch(info);
So we'd then have to just add this static inline change for each new
driver...
There
On Thu, Mar 28, 2013 at 11:10 AM, Julia Lawall julia.law...@lip6.fr wrote:
On Thu, 28 Mar 2013, Luis R. Rodriguez wrote:
Thanks Julia! I'll be sure to try to add this to compat-drivers if the
upstream fb patch is not accepted. If it is accepted we would not need
this at all!
Then I guess
Greg, folks,
So the staging area of the Linux kernel has proven quite successful
for a few drivers for 802.11 already. Otus [0] for example was
rewritten completely first as ar9170 [1] and then carl9170 [2] even
with open firmware, carl9170.fw [3] and then Otus got nuked. ath6kl
[4] is another
On Thu, Mar 28, 2013 at 3:29 PM, Julia Lawall julia.law...@lip6.fr wrote:
On Thu, 28 Mar 2013, Luis R. Rodriguez wrote:
On Thu, Mar 28, 2013 at 11:10 AM, Julia Lawall julia.law...@lip6.fr wrote:
On Thu, 28 Mar 2013, Luis R. Rodriguez wrote:
Thanks Julia! I'll be sure to try to add
On Thu, Mar 28, 2013 at 3:53 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Thu, Mar 28, 2013 at 01:13:23PM -0700, Luis R. Rodriguez wrote:
huge snip
This has me thinking if it makes sense to have an external driver tree
for staging drivers but lead by engineers who already know
On Thu, Mar 28, 2013 at 11:21 PM, Julia Lawall julia.law...@lip6.fr wrote:
I looked in today's linux-next, and there seems to be only one
initialization of this field, to true, and one test of this field. So
perhaps the case for setting the field to false just isn't needed.
Oh sorry now I
patches
compat-drivers: move disable_drm
compat-drivers: refresh patches
Luis R. Rodriguez (69):
compat-drivers: fix sed for gen-release.sh
compat-drivers: add support for uploading stable releases
compat-drivers: add / to target stable release end dir
compat
On Mon, Mar 18, 2013 at 03:13:41PM -0400, John W. Linville wrote:
Any comments from the ath9k folks?
On Sat, Mar 16, 2013 at 12:38:14PM -0400, Parag Warudkar wrote:
During suspend below warning is seen when ath9k is active. Attached
patch fixes the warning for me. Tested to work across
From: Luis R. Rodriguez mcg...@do-not-panic.com
This patch series deals with the project that aims at
backporting the Linux kernel [0]. If you don't care
for that, at least read this and patch #1, the rest
you can nuke.
Ben reports compat_ namespace is already taken by the
kernel, and while
From: Luis R. Rodriguez mcg...@do-not-panic.com
Ben Hutchings notes that compat_ is already taken as a
prefix for symbols and while this is only slightly true
in practice its best we avoid any future issues.
Others in the past have noted issues with symbols exported
by backporting effort
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.com
There is one change needed here to get compilation
working on v2.6.24, strict_strtoull is now being
redefined and because of a change that went into
v2.6.38.4 kstrtoul() was added there and the old
strict_strtoul was made a define from it. To help
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
From: Luis R. Rodriguez mcg...@do-not-panic.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
On Wed, Mar 20, 2013 at 2:22 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
From: Luis R. Rodriguez mcg...@do-not-panic.com
This patch series deals with the project that aims at
backporting the Linux kernel [0]. If you don't care
for that, at least read this and patch #1, the rest
you
On Thu, Mar 21, 2013 at 12:42:20PM +0100, Stanislaw Gruszka wrote:
On Mon, Mar 18, 2013 at 02:03:08PM -0700, Luis R. Rodriguez wrote:
--- a/drivers/net/wireless/ath/ath9k/link.c
+++ b/drivers/net/wireless/ath/ath9k/link.c
@@ -158,7 +158,8 @@ void ath_start_rx_poll(struct ath_softc *sc
On Fri, Mar 22, 2013 at 10:13:42AM +0100, Stanislaw Gruszka wrote:
On Thu, Mar 21, 2013 at 12:33:31PM -0700, Luis R. Rodriguez wrote:
OK how about this for stable for now:
diff --git a/drivers/net/wireless/ath/ath9k/link.c
b/drivers/net/wireless/ath/ath9k/link.c
index 39c84ec..7fdac6c
From: Luis R. Rodriguez mcg...@do-not-panic.com
I maintain the the compat-drivers project [0] which aims at backporting the
Linux kernel drivers down to older kernels, automatically [1]. Thanks to
Ozan Caglayan as a GSoC project we now backport DRM drivers.
The initial framework we had set up
From: Luis R. Rodriguez mcg...@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
From: Luis R. Rodriguez mcg...@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
From: Luis R. Rodriguez mcg...@do-not-panic.com
This adds helpers to enable and test for the skip_vt_switch.
This gets us two things:
1) It allows us to require less collateral evolutions
should we need changes on the fb_info data structure
later (perhaps a bitmap flag).
2) Allows
From: Luis R. Rodriguez mcg...@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
Linus kicked out v3.9-rc1, the first respective backport of this
release's 802.11, Bluetooth, Ethernet and DRM subsystems down to the
last 30 kernel releases is now available at:
https://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.9-rc1/
ckmake test compile results of these
Many thanks to Adrian for his hard work on all this and to everyone
else who volunteered to help make this happen, including the
understanding by our management at QCA and even Tensilica requires
some handsome applause for their commitment, understanding on letting
us get this out. We now have a
: check if efi_enabled() was already backported
compat: deactivate netdev_set_default_ethtool_ops() for some 3.7 kernels
Johannes Berg (1):
compat: backport unsigned netlink attribute accessors
Luis R. Rodriguez (41):
compat: fix libc dependency on bin/get-compat-kernels
I've kicked out compat-drivers releases based on v3.9-rc2 [0], be sure
to use the temporary release page [1] while we get one in place on
kernel.org. We are on rc2 now... please test and report any issues!
Please submit your patches for anything you think is critical but not
'stable' material for
On Wed, Nov 28, 2012 at 3:07 PM, Hauke Mehrtens ha...@hauke-m.de wrote:
struct spinlock does not exists on kernel version = 2.6.32, use
spinlock_t instead.
Signed-off-by: Hauke Mehrtens ha...@hauke-m.de
---
patches/network/67-use_spinlock_t.patch | 11 +++
1 file changed, 11
From: Luis R. Rodriguez mcg...@do-not-panic.com
Turns out a few drivers have strayed away from using the
spinlock_t typedef and decided to use struct spinlock
directly. This series converts these drivers to use
spinlock_t. Each change has been compile tested with
allmodconfig and sparse checked
From: Luis R. Rodriguez mcg...@do-not-panic.com
spinlock_t should always be used.
I was unable to build test with allmodconfig:
mcgrof@frijol ~/linux-next (git::(no branch))$ make C=1 M=drivers/crypto/ux500/
WARNING: Symbol version dump /home/mcgrof/linux-next/Module.symvers
From: Luis R. Rodriguez mcg...@do-not-panic.com
spinlock_t should always be used.
LD drivers/gpu/drm/i915/built-in.o
CHECK drivers/gpu/drm/i915/i915_drv.c
CC [M] drivers/gpu/drm/i915/i915_drv.o
CHECK drivers/gpu/drm/i915/i915_dma.c
CC [M] drivers/gpu/drm/i915/i915_dma.o
From: Luis R. Rodriguez mcg...@do-not-panic.com
spinlock_t should always be used.
Could not get this to build with allmodconfig:
mcgrof@frijol ~/linux-next (git::(no branch))$ make C=1
M=drivers/media/platform/s5p-fimc/
WARNING: Symbol version dump /home/mcgrof/linux-next/Module.symvers
1 - 100 of 6292 matches
Mail list logo
