linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Dan Williams <dcbw@redhat.com>,
	yi.zhu@intel.com, linux-wireless@vger.kernel.org,
	Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: iwl4965 detection problem
Date: Fri, 26 Oct 2007 14:45:50 +0200	[thread overview]
Message-ID: <4721E17E.2020908@sgi.com> (raw)
In-Reply-To: <20071026123044.GB23415@tuxdriver.com>

John W. Linville wrote:
> I've been seeing this behaviour _sometimes_ as well.  (/me hates _sometimes_)
> 
> Fresh off the presses, an F8-based build w/ the latest round of
> iwl4965 updates from Zhu Yi and friends:
> 
> 	http://koji.fedoraproject.org/koji/taskinfo?taskID=215212
> 
> I haven't had a chance to test it yet myself (built it overnight),
> so YMMV.  Still, there is a lot of iwl4965 churn in there so it is
> probably worth some testing.  (Newer than wireless-2.6!)

Hi John,

Thanks for the suggestion, just tried it out - seems to behave the
same way as the old kernel :-(

At least it's consistent here as opposed to sometimes.

One thing I noted is that rmmod often takes a few seconds, no idea
if it has any value?

Cheers,
Jes

  reply	other threads:[~2007-10-26 12:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 13:37 iwl4965 detection problem Jes Sorensen
2007-10-25 13:45 ` Dan Williams
2007-10-25 14:15   ` Jes Sorensen
2007-10-25 17:32     ` Dan Williams
2007-10-26  8:05       ` Jes Sorensen
2007-10-26 12:30         ` John W. Linville
2007-10-26 12:45           ` Jes Sorensen [this message]
2007-10-26 14:10             ` Jes Sorensen
2007-10-26 14:41               ` John W. Linville
2007-10-26 14:43                 ` Jes Sorensen
2007-10-26 15:17               ` Jes Sorensen
2007-10-26 15:23                 ` dragoran
2007-10-26 16:50                   ` John W. Linville
2007-10-29  1:14               ` Zhu Yi

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=4721E17E.2020908@sgi.com \
    --to=jes@sgi.com \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tomas.winkler@intel.com \
    --cc=yi.zhu@intel.com \
    /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 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).