> Baycom should not care whether you have a 16450 or a 16550, so
> I think yourold chip was broken. It could be that something in
> the kernel changed related to IRQ processing and this affected
> Baycom. Very few people are running Linux with 16450 chips, so
> it is certainly possible that there is a problem which has not
> yet been detected.
HM> This is odd. A licensed ham friend and I (since I am not as
HM> yet) were trying to get Baycom going even with their
HM> software under DOS, and it would not transmit properly. The
HM> baycom people said when we emailed them that some of the new
HM> integrated IO chips (Intel HX in this case) may not support
HM> the special mode Baycom uses since it is not used much, and
HM> to try a standard 16450 card...
HM> We have not tried it yet though.
I would consider an incompatible emulation to be "broken" within the meaning of
my earlier comment. The original message was talking about removing a socketed
40-pin 16450 and replacing it with a socketed 40-pin 16550, which should have
no effect on Baycom. Obviously, if the motherboard has built-in serial chips
that only partially emulate the 16450, then any software could break if it
relied upon the unemulated modes.
With special regard to the Intel 430HX chipset, it does not integrate serial
I/O support for RS-232 interfaces as far as I know. If everyone who used a
430HX motherboard has trouble with Baycom, you would have heard a lot of
screaming by now and someone would have fixed the Baycom driver. Such
motherboards have some additional chips to handle the serial ports.
-- Mike