We are developing the 4-port serial interface in qnx4.
The board of 16552 chipset was tested very well.
The successful driver command is follow as:
Dev32.ser -N/dev/ser1 3f8,4 &
Dev32.ser -N/dev/ser2 2f8,3 &
Dev32.ser -N/dev/ser3 300,6 &
Dev32.ser -N/dev/ser4 308,9 &
We can read and write the 4 port at same time.
The port ser1 and ser2 are for the on-board serial port.
Now, the interrupt num of ser3 and ser4 is only valid on 6 and 9.
We’d like to handle the same interrupt number for the ser3 and ser4 port.
Please let me know how to share an irq in the multi serial port.
Thanks in advance.
±±±±±±±±±±±±±±±
Byoung-Hweh Huh
E-mail: purunsan@philtera.com
Byoung-Hweh Huh <purunsan@philtera.com> wrote:
We are developing the 4-port serial interface in qnx4.
The board of 16552 chipset was tested very well.
The successful driver command is follow as:
Dev32.ser -N/dev/ser1 3f8,4 &
Dev32.ser -N/dev/ser2 2f8,3 &
Dev32.ser -N/dev/ser3 300,6 &
Dev32.ser -N/dev/ser4 308,9 &
We can read and write the 4 port at same time.
The port ser1 and ser2 are for the on-board serial port.
Now, the interrupt num of ser3 and ser4 is only valid on 6 and 9.
We’d like to handle the same interrupt number for the ser3 and ser4 port.
I think the important question is where logically are these
serial ports. If they are on the ISA bus, you will not
be able to share interrupts unless you have a special
hardware board that OR’s the interrupt lines. If the
serial ports are on the PCI bus, then they should be sharable.
This brings up a question that maybe someone can answer.
Even the latest motherboards seem to have ISA serial
ports on them. This seems like a big waste of an
interrupt. Is this just to keep things as they always
were, or is there some real reason to do things this way?
Mitchell Schoenbrun --------- maschoen@pobox.com
Byoung-Hweh Huh <purunsan@philtera.com> wrote in message
news:8mvm0f$92d$1@b5nntp2.channeli.net…
We are developing the 4-port serial interface in qnx4.
The board of 16552 chipset was tested very well.
The successful driver command is follow as:
Dev32.ser -N/dev/ser1 3f8,4 &
Dev32.ser -N/dev/ser2 2f8,3 &
Dev32.ser -N/dev/ser3 300,6 &
Dev32.ser -N/dev/ser4 308,9 &
We can read and write the 4 port at same time.
The port ser1 and ser2 are for the on-board serial port.
Now, the interrupt num of ser3 and ser4 is only valid on 6 and 9.
We’d like to handle the same interrupt number for the ser3 and ser4 port.
Please let me know how to share an irq in the multi serial port.
If your multiport serial card handled sharing interupts, you could do the
following…
Dev.ser 3f8,4 2f8,3 300,6 308,6 &
Dev.ser will automatically assign the names ser1 - ser4
also, Dev.ser should be a link to Dev32.ser
-Glenn Sherman
One IRQ => use One Driver
Dev32.ser 300,6 308,6
Assuming of course that the hardware is correct and allows shared
interrupts. Many motherboard’s onboard ports don’t allow sharing of IRQs
-Paul
Byoung-Hweh Huh <purunsan@philtera.com> wrote in message
news:8mvm0f$92d$1@b5nntp2.channeli.net…
We are developing the 4-port serial interface in qnx4.
The board of 16552 chipset was tested very well.
The successful driver command is follow as:
Dev32.ser -N/dev/ser1 3f8,4 &
Dev32.ser -N/dev/ser2 2f8,3 &
Dev32.ser -N/dev/ser3 300,6 &
Dev32.ser -N/dev/ser4 308,9 &
We can read and write the 4 port at same time.
The port ser1 and ser2 are for the on-board serial port.
Now, the interrupt num of ser3 and ser4 is only valid on 6 and 9.
We’d like to handle the same interrupt number for the ser3 and ser4 port.
Please let me know how to share an irq in the multi serial port.
Thanks in advance.
±±±±±±±±±±±±±±±
Byoung-Hweh Huh
E-mail: > purunsan@philtera.com