From: Cort Dougan <cort@fsmlabs.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Benjamin Herrenschmidt <bh40@calva.net>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
linuxppc-bk@fsmlabs.com
Subject: Re: Latest OpenPic changes
Date: Fri, 11 Feb 2000 14:17:32 -0700 [thread overview]
Message-ID: <20000211141732.F15548@hq.fsmlabs.com> (raw)
In-Reply-To: <Pine.HPX.4.10.10002111826230.1866-100000@gra-ux1.iram.es>; from Gabriel Paubert on Fri, Feb 11, 2000 at 06:30:06PM +0100
} Note that there are still problems, some functions use check_arg_irq(irq)
} and then use irq while othre use irq-open_pic_irq_offset after the same
} check. I'm still trying to understand how it should work since I suspect
} something is wrong given the behaviour of my nfsroot machines :-(
}
} Oh and BTW there is a typo in the kernel.org sources:
}
} if ( !(_machine && (_MACH_gemini|_MACH_Pmac)) )
}
} ^^
} should be & otherwise the cascade interrupt will never be requested.
I think we should drop the check_irq_arg() calls everywhere. They will
always fail for IPI's and since we remap the irqs anyway it doesn't matter.
I'll fix the typo... Thanks :)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-11 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-11 16:43 Latest OpenPic changes Geert Uytterhoeven
2000-02-11 17:05 ` Benjamin Herrenschmidt
2000-02-11 17:16 ` Geert Uytterhoeven
2000-02-11 17:11 ` Gabriel Paubert
2000-02-11 17:16 ` Geert Uytterhoeven
2000-02-11 17:30 ` Gabriel Paubert
2000-02-11 21:17 ` Cort Dougan [this message]
2000-02-11 17:31 ` Benjamin Herrenschmidt
2000-02-11 17:49 ` Gabriel Paubert
2000-02-11 18:38 ` Benjamin Herrenschmidt
2000-02-11 20:25 ` Gabriel Paubert
2000-02-12 14:15 ` BenH
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=20000211141732.F15548@hq.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=bh40@calva.net \
--cc=geert@linux-m68k.org \
--cc=linuxppc-bk@fsmlabs.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
/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).