From: Philippe Gerum <rpm@xenomai.org>
To: Matthias Fuchs <matthias.fuchs@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] No hardware interrupts with xenomai on ppc405
Date: Mon, 11 Sep 2006 12:20:27 +0200 [thread overview]
Message-ID: <1157970027.4934.6.camel@domain.hid> (raw)
In-Reply-To: <200609111058.44417.matthias.fuchs@domain.hid>
On Mon, 2006-09-11 at 10:58 +0200, Matthias Fuchs wrote:
> On Sunday 10 September 2006 13:02, Wolfgang Grandegger wrote:
> > Hi Matthias,
> >
> > Matthias Fuchs wrote:
> > > Hi,
> > >
> > > I was trying to use some external hardware interupts on a PPC405 board
> > > as part of a hacking session with Jan to bring up the rtcan driver on
> > > this board.
> > >
> >
> > Could you please add printk statements to the ack, enable and end
> > functions to arch/ppc/syslib/ppc4xx_pic.c if the irq number matches.
> > Please print also SR, ER and status.
>
> 1) insmodding the driver:
> bash-3.00# modprobe xeno_rtcan_isa mem=0xf0000000 irq=25
> rtcan: registered rtcan0
> _enable: ER=003f0040, SR=c0000000
>
> 2) receiving
> bash-3.00# /sbin/rtcanconfig rtcan0 -b 500000 up
> bash-3.00# ./bin/rtcanrecv rtcan0
> _ack: ER=003f0000, SR=c0000040
> _end: ER=003f0000, SR=c0000000
> #0: (1) <0x000> [8] 00 00 00 00 01 00 00 00
>
> That's it. When sending a 2nd message to the board, nothing happens.
> We have a LED on the SJA1000 interrupt signal. After sending the 2nd message
> this LED stays on, so the interrupt is never handled.
>
> It seems that the interrupt is not reenabled (bit 25) in the "end" function.
>
It's likely an Adeos issue. Could you try this patch? TIA,
--- arch/ppc/syslib/ppc4xx_pic.c~ 2005-10-28 02:02:08.000000000 +0200
+++ arch/ppc/syslib/ppc4xx_pic.c 2006-09-11 12:18:14.000000000 +0200
@@ -72,7 +72,8 @@
mtdcr(DCRN_UIC_SR(UIC##n), mask); \
ACK_UIC##n##_PARENT \
} \
- if (!(status & (IRQ_DISABLED | IRQ_INPROGRESS))) { \
+ if (!ipipe_root_domain_p || \
+ !(status & (IRQ_DISABLED | IRQ_INPROGRESS))) { \
ppc_cached_irq_mask[n] |= mask; \
mtdcr(DCRN_UIC_ER(UIC##n), ppc_cached_irq_mask[n]); \
} \
> Matthias
>
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
--
Philippe.
next prev parent reply other threads:[~2006-09-11 10:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 10:40 [Xenomai-core] No hardware interrupts with xenomai on ppc405 Matthias Fuchs
2006-09-10 11:02 ` Wolfgang Grandegger
2006-09-11 8:58 ` Matthias Fuchs
2006-09-11 10:00 ` Wolfgang Grandegger
2006-09-11 10:20 ` Philippe Gerum [this message]
2006-09-11 12:02 ` Matthias Fuchs
2006-09-11 12:20 ` Wolfgang Grandegger
2006-09-11 13:09 ` Philippe Gerum
2006-09-11 14:22 ` Jan Kiszka
2006-09-11 15:32 ` Philippe Gerum
2006-09-11 15:46 ` Wolfgang Grandegger
2006-09-11 17:04 ` Matthias Fuchs
2006-09-11 18:13 ` Wolfgang Grandegger
2006-09-12 7:32 ` Matthias Fuchs
2006-09-12 10:37 ` Wolfgang Grandegger
2006-09-13 10:06 ` Philippe Gerum
2006-09-13 10:34 ` Wolfgang Grandegger
2006-09-13 11:36 ` Philippe Gerum
2006-09-13 11:39 ` Philippe Gerum
2006-09-13 12:38 ` Wolfgang Grandegger
2006-09-13 12:45 ` Philippe Gerum
2006-09-13 12:50 ` Philippe Gerum
2006-09-15 14:18 ` Philippe Gerum
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=1157970027.4934.6.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=matthias.fuchs@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.