From: "Garcia Jérémie" <GARCIAJ@3il.fr>
To: <linuxppc-dev@ozlabs.org>
Subject: Interrupts handling?
Date: Tue, 15 Mar 2005 14:14:34 +0100 [thread overview]
Message-ID: <D4FDDD1349B5AC46B68FC26AD8AF42D6226B11@exnet.3il.fr> (raw)
Hi everybody,
Although I am a newbie in linux powerPC development, I am in charge of a =
related project.
The project is the following: I have to move a vXWorks application to a =
Linux (montavista) environnment with a 405EP processor. Unfotunately, my =
knowledges are very limited in BSP and with all the board specific =
functions (device drivers too...).
In my application, we assign IRQ only at its early beginning and we =
never change them after. Furthermore, this application uses an OS API =
layer in order to make it independant of the OS used. For exemple we =
encapsulate all the OS calls in this layer ; as that we theoretically =
only have to change this file to use another OS. To finish, we use POSIX =
pthreads to get an equivalent of vxWorks tasks.
Giving that, here are my questions:
- is it possible to write a driver in this "file" (OS API Layer) or =
wherever I want?
- do I need to use kernel modules even if I need to register my driver =
only one time?
- is it possible for my application to register itself a driver or is =
it only a "kernel job"?
- I have to map other vxWorks routines as "intEnable", "intDisable" =
which respectively enable/disable specified interrupt bit : may I use =
the linux equivalent "enable_irq" and "disqble_irq" and that wherever =
and whenever I want? (same question for the "request_irq" routine)=20
Tks a lot for your precious help cause over here I am really alone on =
that project and none use Linux!
J=E9r=E9mie
next reply other threads:[~2005-03-15 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 13:14 Garcia Jérémie [this message]
2005-03-15 16:47 ` Interrupts handling? James Chapman
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=D4FDDD1349B5AC46B68FC26AD8AF42D6226B11@exnet.3il.fr \
--to=garciaj@3il.fr \
--cc=linuxppc-dev@ozlabs.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