IRQ's

Is there a way to show what IRQ’s are used by what in 6.2.x, like
sin ir sin 4.25?

Thanks,
Tom.

Tom <pwc@ag-signs.com> wrote in message news:b9hm07$h9a$1@inn.qnx.com

Is there a way to show what IRQ’s are used by what in 6.2.x, like
sin ir sin 4.25?

This is 6.2.1

$ pkgctl /bin/pidin
— Information from /dev/pkginfo7 —
Localpath: [/bin/pidin]
Fullpath: [/pkgs/repository/qnx/os/core-2.1.4/x86/bin/pidin]
Repository: [/pkgs/repository]
Vendor: [qnx/os/core-2.1.4]
Tree: [x86/bin/pidin]
$ /bin/pidin -p io-net irq
pid tid name
184339 1 sbin/io-net
184339 2 sbin/io-net
184339 3 sbin/io-net
8 0xa 0 TPS- =PULSE 0x40000017:21 0:0
184339 4 sbin/io-net
184339 5 sbin/io-net
184339 6 sbin/io-net
184339 7 sbin/io-net
770069 1 o-net/x86/o/io-net
9 0x5 0 TPS- =PULSE 0x40000006:21 0x3:0
770069 2 o-net/x86/o/io-net
770069 3 o-net/x86/o/io-net
770069 4 o-net/x86/o/io-net
770069 5 o-net/x86/o/io-net
770069 6 o-net/x86/o/io-net

-xtang

Neat, but this only shows IRQ’s attached to processes.

Is there a way to see what hardware is attached to what IRQ.
pci -v is pretty good at this for PCI devices, but what about non-pci
devices…?

Thanks,

John Eddy

“Xiaodan Tang” <xtang@qnx.com> wrote in message
news:b9hpqj$nrr$1@nntp.qnx.com

Tom <> pwc@ag-signs.com> > wrote in message news:b9hm07$h9a$> 1@inn.qnx.com> …
Is there a way to show what IRQ’s are used by what in 6.2.x, like
sin ir sin 4.25?

This is 6.2.1

$ pkgctl /bin/pidin
— Information from /dev/pkginfo7 —
Localpath: [/bin/pidin]
Fullpath: [/pkgs/repository/qnx/os/core-2.1.4/x86/bin/pidin]
Repository: [/pkgs/repository]
Vendor: [qnx/os/core-2.1.4]
Tree: [x86/bin/pidin]
$ /bin/pidin -p io-net irq
pid tid name
184339 1 sbin/io-net
184339 2 sbin/io-net
184339 3 sbin/io-net
8 0xa 0 TPS- =PULSE 0x40000017:21 0:0
184339 4 sbin/io-net
184339 5 sbin/io-net
184339 6 sbin/io-net
184339 7 sbin/io-net
770069 1 o-net/x86/o/io-net
9 0x5 0 TPS- =PULSE 0x40000006:21 0x3:0
770069 2 o-net/x86/o/io-net
770069 3 o-net/x86/o/io-net
770069 4 o-net/x86/o/io-net
770069 5 o-net/x86/o/io-net
770069 6 o-net/x86/o/io-net

-xtang

“John Eddy” <john.h.eddy@lmco.com> wrote in message
news:b9qnji$qhd$1@inn.qnx.com

Neat, but this only shows IRQ’s attached to processes.

Is there a way to see what hardware is attached to what IRQ.
pci -v is pretty good at this for PCI devices, but what about non-pci
devices…?

There is no way.

Thanks,

John Eddy

“Xiaodan Tang” <> xtang@qnx.com> > wrote in message
news:b9hpqj$nrr$> 1@nntp.qnx.com> …

Tom <> pwc@ag-signs.com> > wrote in message news:b9hm07$h9a$> 1@inn.qnx.com> …
Is there a way to show what IRQ’s are used by what in 6.2.x, like
sin ir sin 4.25?

This is 6.2.1

$ pkgctl /bin/pidin
— Information from /dev/pkginfo7 —
Localpath: [/bin/pidin]
Fullpath: [/pkgs/repository/qnx/os/core-2.1.4/x86/bin/pidin]
Repository: [/pkgs/repository]
Vendor: [qnx/os/core-2.1.4]
Tree: [x86/bin/pidin]
$ /bin/pidin -p io-net irq
pid tid name
184339 1 sbin/io-net
184339 2 sbin/io-net
184339 3 sbin/io-net
8 0xa 0 TPS- =PULSE 0x40000017:21 0:0
184339 4 sbin/io-net
184339 5 sbin/io-net
184339 6 sbin/io-net
184339 7 sbin/io-net
770069 1 o-net/x86/o/io-net
9 0x5 0 TPS- =PULSE 0x40000006:21 0x3:0
770069 2 o-net/x86/o/io-net
770069 3 o-net/x86/o/io-net
770069 4 o-net/x86/o/io-net
770069 5 o-net/x86/o/io-net
770069 6 o-net/x86/o/io-net

-xtang
\

Mario Charest postmaster@127.0.0.1 wrote:

MC > “John Eddy” <john.h.eddy@lmco.com> wrote in message
MC > news:b9qnji$qhd$1@inn.qnx.com

Neat, but this only shows IRQ’s attached to processes.

Is there a way to see what hardware is attached to what IRQ.
pci -v is pretty good at this for PCI devices, but what about non-pci
devices…?

MC > There is no way.

It shouldn’t be too difficult to iterate through the process table to
extract the IRQs used by each process and display a summary at the end.

When you finish, please post your code.
It really is extreamly helpful.

Bill Caroselli <qtps@earthlink.net> wrote in message
news:b9ra2f$h8g$2@inn.qnx.com

It shouldn’t be too difficult to iterate through the process table to
extract the IRQs used by each process and display a summary at the end.

The original request was for ISA IRQ device assignments, not irq vector
attachments by processes.

Walking around on the ISA bus is a dangerous thing, causing many bizzare
behaviours; one of the many reasons why ISA PnP doesn’t work all that
reliably.

-Adam

Adam Mallory <amallory@qnx.com> wrote:
AM > Bill Caroselli <qtps@earthlink.net> wrote in message
AM > news:b9ra2f$h8g$2@inn.qnx.com

It shouldn’t be too difficult to iterate through the process table to
extract the IRQs used by each process and display a summary at the end.

AM > The original request was for ISA IRQ device assignments, not irq vector
AM > attachments by processes.

I’m sorry. I misunderstood. I was replying to the following post.

Sat, 10 May 2003 02:17:44 qdn.public.qnxrtp.os Thread 2454 of 2463
Lines 7 IRQ’s 5 Responses
Tom <pwc@ag-signs.com> at QNX Developers Network (inn.qnx.com)

Is there a way to show what IRQ’s are used by what in 6.2.x, like
sin ir sin 4.25?

Thanks,
Tom.

But there certainly is a lot of information that you can never get from
an ISA bus.

You have to remember that when the ISA bus was developed IBM was
developing a toy. The PC was never meant to be taken seriously as
a computer (nor cut into the sales of their very expensive computers).

Like, who’s idea was it that an IRQ line should normally be pulled to
ground and when a device wanted to assert an IRQ then the IRQ line
would be allowed to float high. I pray that that was done inten-
tionally just to keep people from pluggin in more devices than a toy
would require. Because if they were that stupid then that is a
pretty sorry state of affairs.


AM > Walking around on the ISA bus is a dangerous thing, causing many bizzare
AM > behaviours; one of the many reasons why ISA PnP doesn’t work all that
AM > reliably.

I agree. Give me the good old days when the system integrator got to
select all interrupts and port addresses via jumpers. The more they
try to make smart hardware, the more it just gets in my way.

And there is nothing faster than telling the OS:

  1. this is the hardware that I have, it’s addresses and IRQs
  2. this is the order that I want them initialized

Personally I’m not fond of the way that QNX6 tries to enumerate
everything it tries to load. It still makes mistakes. It still
occasionally has negitive side effects and it still misses things.