From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <45057123.1030908@domain.hid> Date: Mon, 11 Sep 2006 16:22:27 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Xenomai-core] No hardware interrupts with xenomai on ppc405 References: <4503EB88.2040309@domain.hid> <200609111058.44417.matthias.fuchs@domain.hid> <1157970027.4934.6.camel@domain.hid> <200609111402.12493.matthias.fuchs@domain.hid> <45055475.2050705@domain.hid> <1157980145.4934.69.camel@domain.hid> In-Reply-To: <1157980145.4934.69.camel@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4A7F828589BF0B512FF534AF" Sender: jan.kiszka@domain.hid List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: rpm@xenomai.org Cc: xenomai@xenomai.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4A7F828589BF0B512FF534AF Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Philippe Gerum wrote: > On Mon, 2006-09-11 at 14:20 +0200, Wolfgang Grandegger wrote: >> Matthias Fuchs wrote: >>> Hello Philippe, >>> >>> that helps. I will do some further testing. >>> >>> Matthias >>> >>> >>> On Monday 11 September 2006 12:20, Philippe Gerum wrote: >>>> 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 +020= 0 >>>> +++ 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] |=3D mask; \ >>>> mtdcr(DCRN_UIC_ER(UIC##n), ppc_cached_irq_mask[n]); \ >>>> } \ >> Philippe, could you please explain the problem in more detail? And wha= t=20 >> are the consequences for other PowerPC ARCs and PICs, also for Linux 2= =2E4? >=20 > The issue lies in the fact that PICs *_end() routines may be called ove= r > the Xenomai domain, and actually are, most of the time, since > xnintr_irq_handler() -which invokes xnarch_end_irq()- is always called > from the the Xenomai stage in the Adeos pipeline. >=20 > In such a case, we must not check for the Linux-defined IRQ bits (e.g. > IRQ_INPROGRESS), and always send the eoi, since those bits are not > relevant to the Xenomai context. The patch above ensures this. >=20 > And yes, the 2.4 patch has the very same problem, which should be fixed= > the same way for all supported ppc platforms in the various PIC > management code. Oops. And why didn't this render PPC-over-2.4 useless, i.e. what is special about this 405-scenario? Jan --------------enig4A7F828589BF0B512FF534AF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFBXEjniDOoMHTA+kRAq70AJ0Rb0Dr3wpgCZg3gy0asIRXDpNE4QCdH9eY aaJD+9fgcTUr9FP2qj5ZMuQ= =bXXY -----END PGP SIGNATURE----- --------------enig4A7F828589BF0B512FF534AF--