LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Lukas Hejtmanek" <xhejtman@ics.muni.cz>
Cc: "Chatre, Reinette" <reinette.chatre@intel.com>,
	ipw3945-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Recent driver in linux kernel 2.6.25-rc2
Date: Tue, 11 Mar 2008 13:30:16 +0200	[thread overview]
Message-ID: <1ba2fa240803110430h5cabec18s5be16b586769dec@mail.gmail.com> (raw)
In-Reply-To: <20080311094236.GB4344@ics.muni.cz>

2008/3/11 Lukas Hejtmanek <xhejtman@ics.muni.cz>:
> On Mon, Mar 10, 2008 at 05:35:32PM -0700, Chatre, Reinette wrote:
>  > sorry for the delay - please do submit a bug at bughost.org to enable us
>  > to track this problem.
>  >
>  > The error you get is strange - the reason why the channel could not be
>  > set was because the device is not considered to be ready. Yet, from your
>  > debug log all the required steps appear to have completed successfully.
>  > Could you please add a print to the function
>  > iwl4965-base.c:iwl4965_is_ready to see what the value of priv->status
>  > is?
>
>  I don't have this problem in 2.6.25-rc3 and rc4. However, it seems that the
>  card does not associate with AP if I set iwcofnig wlan0 essid any. Is this
>  a bug or a feature? The AP does not use key and is visible.
>
It looks more like mac80211 bug but frankly I would prefer if this
'any' feature will be not supported.
It has security implications. The decision about to which AP to
associate should be left solely to user space.

Tomas

      reply	other threads:[~2008-03-11 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 15:39 Lukas Hejtmanek
2008-02-19 22:28 ` Chatre, Reinette
2008-02-19 22:44   ` Lukas Hejtmanek
2008-03-11  0:35     ` Chatre, Reinette
2008-03-11  9:42       ` Lukas Hejtmanek
2008-03-11 11:30         ` Tomas Winkler [this message]

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=1ba2fa240803110430h5cabec18s5be16b586769dec@mail.gmail.com \
    --to=tomasw@gmail.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=xhejtman@ics.muni.cz \
    --subject='Re: Recent driver in linux kernel 2.6.25-rc2' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).