From: Hans Feldt <Hans.Feldt@uab.ericsson.se>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: mlocke@mvista.com, LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8xx PCMCIA: request_irq vs. request_8xxirq ?
Date: Tue, 17 Sep 2002 13:48:08 +0200 [thread overview]
Message-ID: <3D871678.9070309@uab.ericsson.se> (raw)
In-Reply-To: 3D86E622.4FE462B0@imc-berlin.de
I ran into the same problem trying to bring up a flashdisk with an IDE
interface connected to the 8260 localbus on our custom board.
init_irq in ide-probe.c calls ide_request_irq which is defined in
asm-ppc/ide.h as request_irq which calls panic.
I changed the request_irq routine in m8260_setup.c to call
request_8xxirq. Doing so I got the disk to work.
But what's the real solution?
Cheers,
Hans
On 09/17/02 10:21 AM, Steven Scholz wrote:
> Otherwise I get a kernel panic when a module (let's say 3c589_cs.o) tries to
> request an IRQ since the wrong request_irq() gets called!
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
parent reply other threads:[~2002-09-17 11:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3D86E622.4FE462B0@imc-berlin.de>]
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=3D871678.9070309@uab.ericsson.se \
--to=hans.feldt@uab.ericsson.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mlocke@mvista.com \
--cc=steven.scholz@imc-berlin.de \
/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).