In article <jane.714294486@munagin> jane@mullian.ee.mu.OZ.AU (jane lynette cosham) writes:
quoted text
>Hi!
>
>I am using linux 0.96c and having problems using ttys0 and ttys2 at
>the same time.
>
>If ttys0 is in use (for example for the mouse in X) then attempts to
>open ttys2 fail - reporting that the device is busy.  The reverse also
>happens - if ttys2 is in use then ttys0 reports as busy.
>
>This is not dependent on what is trying to open the port or which one
>has the first port open - X for the mouse, kermit, getty or just a 
>write to that device.  It also is not dependent on the hardware - I 
>have tried different i/o cards or even removing the card altogether.  
>(kermit doesn't mind opening a port that isn't installed and writes 
>to the other one still say the device is in use)
>
>Is this a bug?  Am I doing something wrong?  Would it be fixed if I
>upgraded to 0.97?

This is a feature, not a bug.  The ISA bus cannot share interrupts.
If one line is not asserting an interrupt condition (ie, pulling the 
IRQ line low), and another has the IRQ driver enabled, and triggers
an interrupt, it will short out with the one pulling the line low,
the IRQ line will stay in a logic low state, and you will never 
see the interrupt.
-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but 
marketing's sins don't come close to those of legal departments.
Boycott AT&T for their absurd anti-BSDI lawsuit.