Return-path: Received: from mail-wy0-f174.google.com ([74.125.82.174]:55874 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756371Ab0EYCVr (ORCPT ); Mon, 24 May 2010 22:21:47 -0400 MIME-Version: 1.0 In-Reply-To: References: <1274726029.2091.15160.camel@rchatre-DESK> <1274738896.2091.15438.camel@rchatre-DESK> Date: Tue, 25 May 2010 07:51:45 +0530 Message-ID: Subject: iwl3945 bug in 2.6.34 From: Satish Eerpini To: linux-kernel , linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: > Actually, sorry, but that patch will not work on 2.6.34 since the > feature it enables is not present there - it will be in 2.6.35 though. > To enable the feature in 2.6.34 will take some more backporting effort > that I'm looking into now. > the patch does lead to a reject, I am not very experienced with code-fu in the kernel, and have no clue about the iwl code base, but comparing the code from 2.6.24 and the latest compat-wireless tarball, I found that in iwl-core.c iwl_check_stuck_queue iwl_bg_monitor_recover are not present in the 2.6.34 version of the file, is there a particular reason for doing this ? is there a patch series/discussion I can follow to know the details on this ? and I am trying to compile 2.6.34 by adding just these two functions to iwl-core.c. If that works I will report back (though you might already know if it will work or not) Cheers Satish -- http://tuxitter.blogspot.com -- http://tuxitter.blogspot.com