Re: Problems running example isr

Adam Lackorzynski <[email protected]>
Newsgroups gmane.comp.micro-kernel.l4.devel
Message-ID <[email protected]>
Hi,

On Sat Mar 12, 2016 at 14:09:20 +0100, Nourhan Mohamed wrote:
> Thank you for your reply! I have already changed the IRQ no inside the code
> to 44. But could you give me more insight on what needs to be modified to
> capture the interrupt on an ARM device?

You need to have/write the driver for that. Likely the pl050 is not
initialized, thus does not trigger any interrupts. It's a driver...


Adam

> On Thu, Mar 10, 2016 at 12:22 AM, Adam Lackorzynski <
> [email protected]> wrote:
> 
> >
> > On Wed Mar 02, 2016 at 16:47:03 +0100, Nourhan Mohamed wrote:
> > > Dear L4Hackers,
> > >
> > > I have a problem running the example "isr" in the pkg/examples/sys/isr
> > > folder in l4 source. It prints "isr     | Press keys now, Shift-Q to
> > exit"
> > > then It fails to detect any interrupts and just keeps waiting. My
> > > configuration is as follows, emulated using Qemu on vexpress-a15 machine:
> >
> > This example is somewhat special because it goes for IRQ 1 which is the
> > PS/2 keyboard interrupt on x86.
> > The pl050 is basically the same so you could just change the
> > number in the example to 44. But I guess there's some more work required
> > to init the controller as there's no magic x86 BIOS that already did
> > it.
> >
> >
> >
> > Adam
> > --
> > Adam                 [email protected]
> >   Lackorzynski         http://os.inf.tu-dresden.de/~adam/
> >
> > _______________________________________________
> > l4-hackers mailing list
> > [email protected]
> > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
> >

> _______________________________________________
> l4-hackers mailing list
> [email protected]
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Adam
-- 
Adam                 [email protected]
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.