From: David Gibson <hermes@gibson.dropbear.id.au>
To: jt@hpl.hp.com
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Benjamin Reed <breed@almaden.ibm.com>,
Javier Achirica <achirica@ttd.net>
Subject: Re: New irq stuff on airo/hermes + SMP
Date: Tue, 13 May 2003 11:10:25 +1000 [thread overview]
Message-ID: <20030513011025.GC2941@zax> (raw)
In-Reply-To: <20030512182840.GC24830@bougret.hpl.hp.com>
On Mon, May 12, 2003 at 11:28:40AM -0700, Jean Tourrilhes wrote:
[snip]
> hermes.c: 4 Jul 2002 David Gibson <hermes@gibson.dropbear.id.au>
> orinoco.c 0.13a (David Gibson <hermes@gibson.dropbear.id.au> and others)
> orinoco_cs.c 0.13a (David Gibson <hermes@gibson.dropbear.id.au> and others)
> eth0: Station identity 001f:0001:0007:001c
> eth0: Looks like a Lucent/Agere firmware version 7.28
> eth0: Ad-hoc demo mode supported
> eth0: IEEE standard IBSS ad-hoc mode supported
> eth0: WEP supported, 104-bit key
> eth0: MAC address 00:60:1D:F0:3A:8A
> eth0: Station name "HERMES I"
> eth0: ready
> eth0: index 0x01: Vcc 5.0, irq 5, io 0x0100-0x013f
> eth0: New link status: Connected (0001)
> orinoco_lock() called with hw_unavailable (dev=cb6ca800)
> irq 5: nobody cared!
> Call Trace:
> [<c010a998>] handle_IRQ_event+0x94/0xf8
> [<c010aba6>] do_IRQ+0x96/0x100
> [<c0106d70>] default_idle+0x0/0x34
> [<c0105000>] _stext+0x0/0x48
> [<c0109570>] common_interrupt+0x18/0x20
> [<c0106d70>] default_idle+0x0/0x34
> [<c0105000>] _stext+0x0/0x48
> [<c0106d9c>] default_idle+0x2c/0x34
> [<c0106e23>] cpu_idle+0x37/0x48
> [<c0105045>] _stext+0x45/0x48
> [<c030c738>] start_kernel+0x13c/0x144
>
> handlers:
> [<cc877074>] (orinoco_interrupt+0x0/0x25c [orinoco])
> orinoco_lock() called with hw_unavailable (dev=cb6ca800)
Jean, I think this was a mistake in the original adaption of the
driver to the new irq stuff (which I didn't do). It mistakenly
returns IRQ_NONE if hw_unavailable is set in the interrupt handler
(wrong based on the "return IRQ_HANDLED" if in doubt rule). Does this
still happen with 0.13e? I've properly implemented the new IRQ stuff
there.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
prev parent reply other threads:[~2003-05-13 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 18:28 New irq stuff on airo/hermes + SMP Jean Tourrilhes
2003-05-13 1:10 ` David Gibson [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=20030513011025.GC2941@zax \
--to=hermes@gibson.dropbear.id.au \
--cc=achirica@ttd.net \
--cc=breed@almaden.ibm.com \
--cc=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
/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).