linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: DHollenbeck <dick@softplc.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	magnus.damm@gmail.com
Subject: Re: yenta_socket rapid fires interrupts
Date: Tue, 11 Jan 2005 16:03:39 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0501111557260.2373@ppc970.osdl.org> (raw)
In-Reply-To: <41E45410.7070004@softplc.com>



On Tue, 11 Jan 2005, DHollenbeck wrote:
> 
> And the dmesg output.  Please look at intctl.  Is this our unsatisfied 
> noise maker?

Hmm. It has I365_PC_RESET set, which does indeed not look right. Could you 
try just forcing it to zero in the initialization path? In fact, that's 
there in the 16-bit card case, but not in the CBCARD case. Something like 
this:

--- 1.65/drivers/pcmcia/yenta_socket.c	2004-12-01 00:14:04 -08:00
+++ edited/drivers/pcmcia/yenta_socket.c	2005-01-11 16:02:45 -08:00
@@ -260,7 +260,7 @@
 
 		/* ISA interrupt control? */
 		intr = exca_readb(socket, I365_INTCTL);
-		intr = (intr & ~0xf);
+		intr &= I365_RING_ENA | I365_INTR_ENA;
 		if (!socket->cb_irq) {
 			intr |= state->io_irq;
 			bridge |= CB_BRIDGE_INTR;

should hopefully take care of it.

		Linus

  reply	other threads:[~2005-01-12  0:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 17:33 yenta_socket rapid fires interrupts DHollenbeck
2005-01-10 19:24 ` Alan Cox
2005-01-11  3:17 ` Linus Torvalds
2005-01-11 19:18   ` DHollenbeck
2005-01-11 19:46     ` Grzegorz Kulewski
2005-01-11 19:54     ` Linus Torvalds
2005-01-11 21:16       ` DHollenbeck
2005-01-11 21:40         ` Linus Torvalds
2005-01-13 14:13           ` Stefan Seyfried
2005-01-13 15:42             ` DHollenbeck
2005-01-13 15:59             ` DHollenbeck
2005-01-11 21:38       ` DHollenbeck
2005-01-11 21:43         ` Linus Torvalds
2005-01-11 22:32           ` DHollenbeck
2005-01-12  0:03             ` Linus Torvalds [this message]
2005-01-12 23:14               ` DHollenbeck

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=Pine.LNX.4.58.0501111557260.2373@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dick@softplc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus.damm@gmail.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).