All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Grimm <patrick@lunatiki.de>
To: Richard Scherping <richard@scherping.de>
Cc: "Chatre, Reinette" <reinette.chatre@intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [HOTFIX] Re: mac80211/iwl4965: ad-hoc broken in 2.6.25-rc1
Date: Sat, 16 Feb 2008 01:19:07 +0100	[thread overview]
Message-ID: <200802160119.07856.patrick@lunatiki.de> (raw)
In-Reply-To: <47B60044.9000801@scherping.de>

Am Freitag, 15. Februar 2008 22:12:36 schrieb Richard Scherping:
> Chatre, Reinette schrieb:
> >>> One more question ... did ad-hoc work for you before this patch?
> >>
> >> No. In my tests only ipw3945 works in Ad-Hoc mode.
> >
> > ok - that explains things. The patch assumes that ad-hoc mode is
> > working, which is unfortunately not the case. We have to fix this.
> >
> > Reinette
>
> As I said, I have tested with iwl4965 only. Seems as if there are more
> problems with ad-hoc and iwl3945. Did ad-hoc work in the "old" iwl3945
> (before the API change with old version 1.1.17, compared to new version
> 1.2.23/26)?
I have made some short tests with my working kernel 2.6.23.
Version 1.1.17 - 1.1.22 Ad-Hoc mode is working.
Version 1.1.23 -            Ad-Hoc mode is not working.

Changes in 1.2.23

* fix problem when rf_kill switch change during suspend/resume
* fix possible priv->mutex deadlock during suspend
* 3954 renames iwl3945_rate_scale_priv to iwl3945_rs_sta
* 4965 unify rate scale variable names for station data
* move uCode helper functions to iwl-helpers.h
* Makefile: enable building using "make -C /path/to/iwlwifi"
* fix iwl_mac_add_interface handler
* Fix race conditional panic
* remove redundant declaration of 'iwl3945_priv' and 'iwl4965_priv' structs
* document scan command
* remove iwl4965_tx_cmd
* move iwl4965_get_dma_hi_address function to iwl-helpers.h
* fix rate control algo reference leak
* fix rf_kill state inconsistent during suspend and resume
* fix priv->ucode_data_backup save problem
* iwl4965: fix mutex_unlock missed problem in iwl_mac_config exit path
* iwl4965: Remove redundant code in iwl4965_tx_cmd
* fix compilation warnings
* use pci_save_state() before calling pci_disable_device()
* skip mac80211 conf during a hardware scan and replay it afterwards
* delay firmware loading from pci_probe to network interface open
* Makefile: enable HT and HT_AGG by default

Patrick

  parent reply	other threads:[~2008-02-16 13:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 19:31 mac80211/iwl4965: ad-hoc broken in 2.6.25-rc1 Richard Scherping
2008-02-12 21:51 ` Chatre, Reinette
2008-02-12 23:06   ` Richard Scherping
2008-02-13  9:06     ` [HOTFIX] " Richard Scherping
2008-02-13 22:20       ` Chatre, Reinette
2008-02-14 18:26         ` Richard Scherping
2008-02-14 23:40           ` Patrick Grimm
2008-02-14 23:57             ` Chatre, Reinette
2008-02-15  0:21               ` Chatre, Reinette
2008-02-15  1:29                 ` Patrick Grimm
2008-02-15 16:39                   ` Chatre, Reinette
2008-02-15 21:12                     ` Richard Scherping
2008-02-15 21:21                       ` Chatre, Reinette
2008-02-16  0:19                       ` Patrick Grimm [this message]
2008-02-17 21:37                         ` Patrick Grimm

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=200802160119.07856.patrick@lunatiki.de \
    --to=patrick@lunatiki.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=richard@scherping.de \
    /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.