From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Bosko Radivojevic <bosko.radivojevic@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Intel EP80579 support
Date: Tue, 21 Apr 2009 11:53:22 +0200 [thread overview]
Message-ID: <49ED9792.8010304@domain.hid> (raw)
In-Reply-To: <d6c8ef150904201621md0fd3dcq329207f0d235aac8@domain.hid>
Bosko Radivojevic wrote:
> Hi Gilles,
>
> thank you for your answers. I'm doing pretty much the same thing as I
> did on ARM platform - I'm using one of GPIO pins as Interrupt source.
> On ARM platform I was using one of the GPIO pins as IRQ 110, also
> without having it in /proc/interrupts.
>
> Intel provides API (accessible through ioctl()) which I use to set
> GPIO pin (#25 in my case) in input mode and, as manual says, it can be
> used as Interrupt source (for #25 it says IRQ 38).
>
> Sincerely,
> Bosko
The difference between ARM and x86 is that on ARM, all irqs are created
when the board support is initialized. From what I understand, on x86,
irqs are created when requested. Which is why for instance, you see that
PCI irqs are only routed when the PCI device is requested by a driver.
So, for the IRQ 38 to exist, you probably need to request it as if you
were going to use it on Linux side, then you may request it on Xenomai side.
--
Gilles.
next prev parent reply other threads:[~2009-04-21 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 23:28 [Xenomai-help] Intel EP80579 support Bosko Radivojevic
2009-04-11 20:10 ` Gilles Chanteperdrix
2009-04-15 23:13 ` Bosko Radivojevic
2009-04-15 23:26 ` Bosko Radivojevic
2009-04-15 23:45 ` Gilles Chanteperdrix
2009-04-15 23:55 ` Bosko Radivojevic
2009-04-20 11:24 ` Bosko Radivojevic
2009-04-20 18:17 ` Gilles Chanteperdrix
2009-04-20 23:21 ` Bosko Radivojevic
2009-04-21 9:53 ` Gilles Chanteperdrix [this message]
2009-04-12 20:08 ` Gilles Chanteperdrix
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=49ED9792.8010304@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=bosko.radivojevic@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.