Hi all!
I need to check wich interrupts are already in use under Neutrino (Like
qnx_hint_query under QNX4, which is not longer supported in Neutrino).
Is there a way to do that?
TYA,
Leonel Vicente Mota Ivo
Leonel Vicente Mota Ivo <leonel@atan.com.br> wrote:
Hi all!
I need to check wich interrupts are already in use under Neutrino (Like
qnx_hint_query under QNX4, which is not longer supported in Neutrino).
Is there a way to do that?
You need to walk the /proc filesystem, issuing DCMD_PROC_IRQS to each
file…
Cheers,
-RK
–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~pdp8/
Robert Krten <rk@parse.com> wrote:
Leonel Vicente Mota Ivo <> leonel@atan.com.br> > wrote:
Hi all!I need to check wich interrupts are already in use under Neutrino (Like
qnx_hint_query under QNX4, which is not longer supported in Neutrino).
Is there a way to do that?You need to walk the /proc filesystem, issuing DCMD_PROC_IRQS to each
file…
Which is what “pidin irq” does for you.
BTW, in both cases this only tells you which interrupts have had processes
register handlers (or events) for them. It does NOT tell you which ones
have hardware associated with them. That is, it does not let you know
what are free hardware irqs for doing hardware configuration. (Though,
it may be taken as a hint towards that information.)
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Thanks Robert and David. I’m using that to mark a list of used interrupts
for an ISA plug-and-play card driver.
Leonel.
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:bpglhe$qku$1@nntp.qnx.com…
Robert Krten <> rk@parse.com> > wrote:
Leonel Vicente Mota Ivo <> leonel@atan.com.br> > wrote:
Hi all!I need to check wich interrupts are already in use under Neutrino (Like
qnx_hint_query under QNX4, which is not longer supported in Neutrino).
Is there a way to do that?You need to walk the /proc filesystem, issuing DCMD_PROC_IRQS to each
file…Which is what “pidin irq” does for you.
BTW, in both cases this only tells you which interrupts have had processes
register handlers (or events) for them. It does NOT tell you which ones
have hardware associated with them. That is, it does not let you know
what are free hardware irqs for doing hardware configuration. (Though,
it may be taken as a hint towards that information.)-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Hi again.
I’ve found an example of how to walk in the /proc filesystem in the
migration lib (qnx_psinfo) and I could get the interrupt info from the pids
on that. The problem is that the result it’s not the same of the command
pidin irq because I couldn’t find an example of how to get that info of the
threads of those process.
Does anyone have an example of how to do that?
TYA,
Leonel
I’ve found an example of
“Leonel Vicente Mota Ivo” <leonel@atan.com.br> wrote in message
news:bptlmh$lle$1@inn.qnx.com…
Thanks Robert and David. I’m using that to mark a list of used interrupts
for an ISA plug-and-play card driver.Leonel.
“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:bpglhe$qku$> 1@nntp.qnx.com> …
Robert Krten <> rk@parse.com> > wrote:
Leonel Vicente Mota Ivo <> leonel@atan.com.br> > wrote:
Hi all!I need to check wich interrupts are already in use under Neutrino
(Like
qnx_hint_query under QNX4, which is not longer supported in
Neutrino).
Is there a way to do that?You need to walk the /proc filesystem, issuing DCMD_PROC_IRQS to each
file…Which is what “pidin irq” does for you.
BTW, in both cases this only tells you which interrupts have had
processes
register handlers (or events) for them. It does NOT tell you which ones
have hardware associated with them. That is, it does not let you know
what are free hardware irqs for doing hardware configuration. (Though,
it may be taken as a hint towards that information.)-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Leonel Vicente Mota Ivo wrote:
Hi again.
I’ve found an example of how to walk in the /proc filesystem in the
migration lib (qnx_psinfo) and I could get the interrupt info from the pids
on that. The problem is that the result it’s not the same of the command
pidin irq because I couldn’t find an example of how to get that info of the
threads of those process.
I think Rob would probably point you towards his book (and if he had one, he
might even point you to his on-line ordering system 
)
Rennie Allen <rgallen@attbi.com> wrote:
Leonel Vicente Mota Ivo wrote:
Hi again.
I’ve found an example of how to walk in the /proc filesystem in the
migration lib (qnx_psinfo) and I could get the interrupt info from the pids
on that. The problem is that the result it’s not the same of the command
pidin irq because I couldn’t find an example of how to get that info of the
threads of those process.I think Rob would probably point you towards his book (and if he had one, he
might even point you to his on-line ordering system >
I’m trying to avoid shameless plugs, especially in light of not having an
online ordering system
However, if you insist
http://www.parse.com/products/books/book_v2/index.html
Cheers,
-RK
–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~pdp8/
Thanks Rob. I will buy your book, but lukily your sample chapter about the
Thread Fingerprint Utility has just what I need to know by now. The code in
process_pid shows how to figure out what are the threads of a given pid.
Regards,
Leonel.
“Robert Krten” <rk@parse.com> wrote in message
news:bqbak2$a3p$1@inn.qnx.com…
Rennie Allen <> rgallen@attbi.com> > wrote:
Leonel Vicente Mota Ivo wrote:
Hi again.
I’ve found an example of how to walk in the /proc filesystem in the
migration lib (qnx_psinfo) and I could get the interrupt info from the
pids
on that. The problem is that the result it’s not the same of the
command
pidin irq because I couldn’t find an example of how to get that info of
the
threads of those process.I think Rob would probably point you towards his book (and if he had
one, he
might even point you to his on-line ordering system >I’m trying to avoid shameless plugs, especially in light of not having an
online ordering system >However, if you insist >
http://www.parse.com/products/books/book_v2/index.html
Cheers,
-RK–
[If replying via email, you’ll need to click on the URL that’s emailed to
you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector > http://www.parse.com/~pdp8/
In article <bqfog3$cfn$1@inn.qnx.com>, leonel@atan.com.br says…
Thanks Rob. I will buy your book, but lukily your sample chapter about the
Thread Fingerprint Utility has just what I need to know by now. The code in
process_pid shows how to figure out what are the threads of a given pid.
There is a source of pidin in QNX on-line CVS as well.
http://cvs.qnx.com/cgi-bin/cvsweb.cgi/utils/p/pidin/
Eduard.
Regards,
Leonel.
“Robert Krten” <> rk@parse.com> > wrote in message
news:bqbak2$a3p$> 1@inn.qnx.com> …
Rennie Allen <> rgallen@attbi.com> > wrote:
Leonel Vicente Mota Ivo wrote:
Hi again.
I’ve found an example of how to walk in the /proc filesystem in the
migration lib (qnx_psinfo) and I could get the interrupt info from the
pids
on that. The problem is that the result it’s not the same of the
command
pidin irq because I couldn’t find an example of how to get that info of
the
threads of those process.I think Rob would probably point you towards his book (and if he had
one, he
might even point you to his on-line ordering system >I’m trying to avoid shameless plugs, especially in light of not having an
online ordering system >However, if you insist >
http://www.parse.com/products/books/book_v2/index.html
Cheers,
-RK–
[If replying via email, you’ll need to click on the URL that’s emailed to
you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector > http://www.parse.com/~pdp8/
ed1k <ed1k@humber.bay> wrote:
In article <bqfog3$cfn$> 1@inn.qnx.com> >, > leonel@atan.com.br > says…
Thanks Rob. I will buy your book, but lukily your sample chapter about the
Thread Fingerprint Utility has just what I need to know by now. The code in
process_pid shows how to figure out what are the threads of a given pid.
There is a source of pidin in QNX on-line CVS as well.
http://cvs.qnx.com/cgi-bin/cvsweb.cgi/utils/p/pidin/
Eduard.
Yes, but that is the 6.1.1 version, which I think was before the
“pidin irq” command was implemented. It is, still, useful
for looking at how to collect other system information.
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Thank you Eduard.
David you are right, there is no “pidin irq” command in this version, but it
is useful anyway.
Thank you all!
Leonel.
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:bqnnev$4tq$1@nntp.qnx.com…
ed1k <> ed1k@humber.bay> > wrote:
In article <bqfog3$cfn$> 1@inn.qnx.com> >, > leonel@atan.com.br > says…
Thanks Rob. I will buy your book, but lukily your sample chapter about
the
Thread Fingerprint Utility has just what I need to know by now. The
code in
process_pid shows how to figure out what are the threads of a given
pid.
There is a source of pidin in QNX on-line CVS as well.
http://cvs.qnx.com/cgi-bin/cvsweb.cgi/utils/p/pidin/
Eduard.Yes, but that is the 6.1.1 version, which I think was before the
“pidin irq” command was implemented. It is, still, useful
for looking at how to collect other system information.-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.