From: Konstantin Olchanski <olchansk@ux1.phy.bnl.gov>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Problem requesting IRQ with 2.4.2 kernel
Date: Wed, 28 Feb 2001 20:07:56 -0500 [thread overview]
Message-ID: <20010228200756.E252@ux1.phy.bnl.gov> (raw)
In-Reply-To: <200102280559.XAA05414@lists.linuxppc.org>; from owner-linuxppc-dev-digest@lists.linuxppc.org on Tue, Feb 27, 2001 at 11:59:28PM -0600
> Date: Tue, 27 Feb 2001 17:56:53 +0100
> From: xav <grave@ipno.in2p3.fr>
> Subject: Problem requesting IRQ with 2.4.2 kernel
>
> Hi !
>
> I'm using a clone of the bk tree to compile a 2.4.2 kernel.
> I have also downloaded the code from Gabriel Paubert for the
> pci2vme chip from TUNDRA.
>
I see the same problem- on my kernels (older bitkeeper 2.4 tree)
pdev->irq comes out as zero.
By experimenting, I determined (and hardwired into the driver)
a working Universe irq on the MVME230x: "11".
I do not know how to kludge the "prep" routing tables- none of the
numbers in those tables match the board and vxworks BSP documentation.
I guess this will be ultimately fixed by Matt Porter's new MVME support
in the 2.5 tree.
--
Konstantin Olchanski
Physics Department, Brookhaven National Laboratory, Long Island, New York
olchansk@bnl.gov
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2001-03-01 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200102280559.XAA05414@lists.linuxppc.org>
2001-03-01 1:07 ` Konstantin Olchanski [this message]
2001-02-27 16:56 Problem requesting IRQ with 2.4.2 kernel xav
2001-02-27 15:10 ` Matt Porter
2001-02-28 12:44 ` xav
2001-03-01 13:33 ` Gabriel Paubert
2001-02-27 17:02 ` xav
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=20010228200756.E252@ux1.phy.bnl.gov \
--to=olchansk@ux1.phy.bnl.gov \
--cc=linuxppc-dev@lists.linuxppc.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).