How to release IRQ15 from Secondary IDE Channel

NTDEV
1

Hi to All,

I’m envolved on a developing touch screen driver that will use IRQ15.
All others IRQ are used from other devices, thus, I can’t use another IRQ.

System is a embedded platform with XPE.
Actually the IRQ15 resource is taken from secondary IDE channel.
when I try to configure the T.S. driver with IRQ15 I have a conflict.

The uninstall operation of secondary Ide; by the way, this last one device
is not used, is totally useless, because
at the next reboot it’s reintroduced.

I analyzied the problem with BIOS people, and them informed me that this
resource is disable at BIOS Level.
(P.S.: BIOS is not PnP).
Is not totally clear for me, but, shouldn’t to be a shared interrupt ? Or
it is a exclusive resurce for 2nd IDE Channel?

How is possible, if it is, release the IRQ15 permanently from Second
Channel ?
What can I do and check in my TS driver, or if the problem isn’t here,
where find the problem ?
I forgot something ?

Please, someone can help me, or knows where is possible take the right
infos ?

Thanks in advance.
Best regards . Giandomenico Vassia.

2

> I’m envolved on a developing touch screen driver that will use IRQ15.

All others IRQ are used from other devices, thus, I can’t use another IRQ.

Maybe it is much better to make your touch screen dynamically configurable and not tied to particular IRQ?

Max

3

If the BIOS allows disabling the second channel it should release the IRQ.
Not all BIOSs allow this.

It would be event better to make your hardware and driver so that your
device can share an interrupt. Otherwise, what would you do with the many,
many machines out there configured with an IDE hard disk on the first
channel (IRQ 14) and the CD-ROM on the second channel (IRQ 15)?

++PLS

-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Subject: [ntdev] Re: How to release IRQ15 from Secondary IDE Channel

I’m envolved on a developing touch screen driver that will use IRQ15.
All others IRQ are used from other devices, thus, I can’t use another
IRQ.

Maybe it is much better to make your touch screen dynamically configurable
and not tied to particular IRQ?

Max