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 16:43:30 +0200	[thread overview]
Message-ID: <4721FD12.4060800@sgi.com> (raw)
In-Reply-To: <20071026144137.GD23415@tuxdriver.com>

John W. Linville wrote:
> On Fri, Oct 26, 2007 at 04:10:39PM +0200, Jes Sorensen wrote:
> 
>> Disable interrupts in the iwl4965 before calling request_irq() for
>> the case that the previous OS or the BIOS left a pending interrupt in
>> the chip. This behavior has been observed on some laptops such as T61
>> Thinkpads and Toshiba Portege R500
> 
> Any reason this would not be appropriate for iwl3945 as well?

I cannot say for sure since I don't have one here, but a brief look at
the code indicates that it might.

I'm trying to build a kernel here with the patch now.

Cheers,
Jes

  reply	other threads:[~2007-10-26 14:43 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
2007-10-26 14:10             ` Jes Sorensen
2007-10-26 14:41               ` John W. Linville
2007-10-26 14:43                 ` Jes Sorensen [this message]
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=4721FD12.4060800@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).