All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Axj <axjslack@bluebottle.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Request for help...
Date: Thu, 26 Jul 2007 12:22:34 -0400	[thread overview]
Message-ID: <1185466954.14557.5.camel@dv> (raw)
In-Reply-To: <200707261511.l6QFB2jK015121@mi0.bluebottle.com>

On Thu, 2007-07-26 at 08:10 -0700, Axj wrote:

> I  saw onother exit of thje driver, 1.0.0, but I don't trust so much
> (at the momente the compination of mac80211 ver 8.0.2 and
> iwlwifi-0.0.42 work, even if the led doesn't work ad It's impossible
> to set an "Ad-Hoc" connection. )

Actually, it's direct continuation of the 0.0.x series.  It's
unfortunate that the complexity of the build system makes you mistrust
the recent code, although I can relate.  I hope it will be remedied
quickly.

It's possible to compile the 1.0.x driver against recent unpatched
kernels, even against the standard Fedora 7 kernel, by stripping support
for Intel's rate control algorithm:

diff --git a/origin/Makefile b/origin/Makefile
index 8c0bdc7..c5d966f 100644
--- a/origin/Makefile
+++ b/origin/Makefile
@@ -10,7 +10,7 @@
 # -jpk
 
 obj-$(CONFIG_IWL3945)	+= iwl3945.o
-iwl3945-objs		= base-3945.o iwl-3945.o iwl-3945-rs.o
+iwl3945-objs		= base-3945.o iwl-3945.o
 CFLAGS_iwl-3945.o	= -DIWL=3945
 CFLAGS_iwl-3945-rs.o	= -DIWL=3945
 CFLAGS_base-3945.o	= -DIWL=3945 -D"KBUILD_MODNAME=KBUILD_STR(iwl3945)"
@@ -19,7 +19,7 @@ $(obj)/base-3945.o: $(src)/base.c FORCE
 	$(call if_changed_rule,cc_o_c)
 
 obj-$(CONFIG_IWL4965)	+= iwl4965.o
-iwl4965-objs		= base-4965.o iwl-4965.o iwl-4965-rs.o
+iwl4965-objs		= base-4965.o iwl-4965.o
 CFLAGS_iwl-4965.o	= -DIWL=4965
 CFLAGS_iwl-4965-rs.o	= -DIWL=4965
 CFLAGS_base-4965.o	= -DIWL=4965 -D"KBUILD_MODNAME=KBUILD_STR(iwl4965)"
diff --git a/origin/base.c b/origin/base.c
index eda467e..ee6ac8f 100644
--- a/origin/base.c
+++ b/origin/base.c
@@ -6284,7 +6284,6 @@ static void iwl_alive_start(struct iwl_priv *priv)
 		/* Unlock so any user space entry points can call back into
 		 * the driver without a deadlock... */
 		mutex_unlock(&priv->mutex);
-		iwl_rate_control_register();
 		rc = ieee80211_register_hw(priv->hw);
 		priv->hw->conf.beacon_int = 100;
 		mutex_lock(&priv->mutex);
@@ -6950,7 +6949,6 @@ static void iwl_bg_post_associate(struct work_struct *data)
 				  (priv->phymode == MODE_ATHEROS_TURBO)) ?
 				 IWL_RATE_6M_PLCP : IWL_RATE_1M_PLCP,
 				 CMD_ASYNC);
-		iwl_rate_scale_init(priv->hw, IWL_AP_ID);
 
 		break;
 
@@ -6967,7 +6965,6 @@ static void iwl_bg_post_associate(struct work_struct *data)
 				  (priv->phymode == MODE_ATHEROS_TURBO)) ?
 				 IWL_RATE_6M_PLCP : IWL_RATE_1M_PLCP,
 				 CMD_ASYNC);
-		iwl_rate_scale_init(priv->hw, IWL_STA_ID);
 		iwl_send_beacon_cmd(priv);
 
 		break;
@@ -7915,8 +7912,7 @@ static ssize_t show_rs_window(struct device *d,
 			      struct device_attribute *attr,
 			      char *buf)
 {
-	struct iwl_priv *priv = d->driver_data;
-	return iwl_fill_rs_info(priv->hw, buf, IWL_AP_ID);
+	return 0;
 }
 static DEVICE_ATTR(rs_window, S_IRUGO, show_rs_window, NULL);
 
@@ -8851,7 +8847,6 @@ static void iwl_pci_remove(struct pci_dev *pdev)
 
 	if (priv->mac80211_registered) {
 		ieee80211_unregister_hw(priv->hw);
-		iwl_rate_control_unregister();
 	}
 
 	/* ieee80211_unregister_hw calls d_stop, which flushes


-- 
Regards,
Pavel Roskin


  reply	other threads:[~2007-07-26 16:22 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 15:02 Request for help Axj
2007-07-24 16:12 ` John W. Linville
2007-07-24 18:29   ` [ipw3945-devel] " Stephen Clark
2007-07-24 20:30     ` John W. Linville
2007-07-24 21:13       ` Jeff Garzik
2007-07-25  1:15         ` James Ketrenos
2007-07-25  0:03           ` Jeff Garzik
2007-07-25  0:30             ` Stephen Clark
2007-07-25  0:35               ` David Miller
2007-07-25  0:43                 ` Stephen Clark
2007-07-25  0:46                   ` David Miller
2007-07-25  1:05                     ` Stephen Clark
2007-07-25  1:18                       ` David Miller
2007-07-25  1:23                       ` Jeff Garzik
2007-07-25  1:29                         ` Stephen Clark
2007-07-25  1:40                     ` Jeff Garzik
2007-07-25  1:40                   ` Jeff Garzik
2007-07-25  0:45               ` Maurizio Monge
2007-07-25  1:35               ` Jeff Garzik
2007-07-25  8:01             ` James Ketrenos
2007-07-25 14:50               ` John W. Linville
2007-07-27 12:36               ` Jeff Garzik
2007-07-25 14:46             ` John W. Linville
2007-07-25 15:19               ` Jeff Garzik
2007-07-25  9:32 ` Zhu Yi
2007-07-26 15:10   ` Axj
2007-07-26 16:22     ` Pavel Roskin [this message]
2007-07-27  6:34       ` Axj
2007-07-27  7:44         ` Zhu Yi
2007-07-27  8:48           ` Axj
     [not found]           ` <200707270848.l6R8mqkh004526@mi1.bluebottle.com>
2007-07-27  8:56             ` Zhu Yi
2007-07-27  9:10               ` Axj
2007-07-30  0:58                 ` Zhu Yi
2007-08-01  6:40                   ` Axj
  -- strict thread matches above, loose matches on Subject: below --
2023-12-04 14:01 request " devicetree
2020-03-30 12:38 Request " Lev R. Oshvang .
2005-03-17  3:17 request " shashi dhara bhat
     [not found] <200305290413.JAA23492@WS0005.indiatimes.com>
2003-06-02 17:49 ` Request " Eric W. Biederman
2003-06-02 18:48   ` Andy Pfiffer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1185466954.14557.5.camel@dv \
    --to=proski@gnu.org \
    --cc=axjslack@bluebottle.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.