Hi all,
I just tested our cpci 4*serial(16550) board with the standard Dev.ser.
It works wonderful, if I do not share the irq with another pci-card.
If I do, the system gets frozen(irq-everloop).
I this a known issue?
If so, is there a newer version of the driver, which solve this problem?
-Michael
Michael Tasche wrote:
Hi all,
I just tested our cpci 4*serial(16550) board with the standard Dev.ser.
It works wonderful, if I do not share the irq with another pci-card.
If I do, the system gets frozen(irq-everloop).I this a known issue?
Is your board an ISA or PCI ? If it is ISA I would expect a lockup.
Rennie Allen wrote:
Michael Tasche wrote:
Hi all,
I just tested our cpci 4*serial(16550) board with the standard Dev.ser.
It works wonderful, if I do not share the irq with another pci-card.
If I do, the system gets frozen(irq-everloop).I this a known issue?
Is your board an ISA or PCI ? If it is ISA I would expect a lockup.PCI !
Michael Tasche wrote:
Rennie Allen wrote:
Michael Tasche wrote:
Hi all,
I just tested our cpci 4*serial(16550) board with the standard Dev.ser.
It works wonderful, if I do not share the irq with another pci-card.
If I do, the system gets frozen(irq-everloop).I this a known issue?
Is your board an ISA or PCI ? If it is ISA I would expect a lockup.PCI !
yes I see cpci now (I read that as the name of your board). No idea why
sharing wouldn’t work, unless the driver that you are sharing with isn’t
written correctly. What is the driver for the other device ?
Rennie
Rennie Allen <rallen@csical.com> wrote:
RA > Michael Tasche wrote:
Hi all,
I just tested our cpci 4*serial(16550) board with the standard Dev.ser.
It works wonderful, if I do not share the irq with another pci-card.
If I do, the system gets frozen(irq-everloop).I this a known issue?
RA > Is your board an ISA or PCI ? If it is ISA I would expect a lockup.
I wouldn’t expect a lock-up. But I wouldn’t expect it to work right
either. The rule is that an ISA device can not share an interrupt.
When the geniouses designed the ISA bus they designed it so that when
there is no interrupt the IRQ line is pulled high. When there IS an
IRQ the IRQ line is allowed to float low. So if there is more than
one device on an IRQ line it won’t indicate an IRQ unless the ALL have
a pending IRQ.
Then again, there used to be dinosours. Time marches on.
Rennie Allen wrote:
Michael Tasche wrote:
Rennie Allen wrote:
Michael Tasche wrote:
Hi all,
I just tested our cpci 4*serial(16550) board with the standard Dev.ser.
It works wonderful, if I do not share the irq with another pci-card.
If I do, the system gets frozen(irq-everloop).I this a known issue?
Is your board an ISA or PCI ? If it is ISA I would expect a lockup.PCI !
yes I see cpci now (I read that as the name of your board). No idea why
sharing wouldn’t work, unless the driver that you are sharing with isn’t
written correctly. What is the driver for the other device ?
It is the network-driver(On Monday I tell you which one).
But the problem seems to be Dev.ser, which does not clear the irq during
the lockup (We have a led on each 16550 irq-line).
If I unplug the CPCI-Card during the lockup(Risky, isn’t it), the system
comes back.
-Michael
Rennie
Bill Caroselli <qtps@earthlink.net> wrote:
Rennie Allen <> rallen@csical.com> > wrote:
RA > Michael Tasche wrote:
Hi all,I just tested our cpci 4*serial(16550) board with the standard Dev.ser.
It works wonderful, if I do not share the irq with another pci-card.
If I do, the system gets frozen(irq-everloop).I this a known issue?
RA > Is your board an ISA or PCI ? If it is ISA I would expect a lockup.
I wouldn’t expect a lock-up. But I wouldn’t expect it to work right
either. The rule is that an ISA device can not share an interrupt.
As far as i can see, he is trying to share a IRQ between two PCI devices.
That should be OK in principle. I think i have seen problems with Dev.ser sharing
PCI IRQ as well and without having investigated to the end i try to avoid sharing.
I once asked QSSL to confirm wether or not Dev.ser was able to share Interupts but
there was no definitive answer.
When the geniouses designed the ISA bus they designed it so that when
there is no interrupt the IRQ line is pulled high. When there IS an
IRQ the IRQ line is allowed to float low. So if there is more than
one device on an IRQ line it won’t indicate an IRQ unless the ALL have
a pending IRQ.Then again, there used to be dinosours. Time marches on.
On Sat, 18 Oct 2003 11:29:13 +0000, Rennie Allen <rgallen@attbi.com> wrote:
Michael Tasche wrote:
Rennie Allen wrote:Michael Tasche wrote:
Hi all,
I just tested our cpci 4*serial(16550) board with the standard
Dev.ser.
It works wonderful, if I do not share the irq with another pci-card.
If I do, the system gets frozen(irq-everloop).I this a known issue?
Is your board an ISA or PCI ? If it is ISA I would expect a lockup.PCI !
yes I see cpci now (I read that as the name of your board). No idea why
sharing wouldn’t work, unless the driver that you are sharing with isn’t
written correctly. What is the driver for the other device ?
Net.tulip
-Michael
Rennie