Jose Angel Amador Fundora wrote:
> I have 4 com ports installed with Slackware 3.2, kernel 2.0.35.
>
> Before I made AX.25 work with my kiss TNC's, my mouse (run of the
> mill serial mouse) worked OK. Now it does not. Clearly, IRQ4 seems to
> be taken by kissattach on COM3 (ttyS2, excuse me) and I have to solve
> that dilema.
>
> For a time I was using a modified MS-400 card (4 serial ports)
> modified 'a la AA4RE' for use with BPQ 4.08A, and a single shared
> hardware interrupt for COM3 to COM6 using a 4 input CMOS OR gate
> with a line from each UART chip to a single IRQ line out of the OR
> gate. It worked fine. OS was MSDOS 6.22, and Desqview 2.60 as
> multitasker.
>
> I wonder if that COULD work under Linux, or if somebody uses it under
> Linux. I could attach the TNC's to a single IRQ and leave COM 1 for
> mouse and COM 2 for CAT.
>
> Cheapo but functional solutions welcome.
>
> 73 de Jose, CO2JA
Hola José,
I have a MS-400 clone with the same mod.
Linux works fine with it and the next "serial" script.
SuSE "serial" is the same, Debian "setserial", Slackware "rc.serial" and
so.
Un abrazo
Norberto LU3FPN
--------------05398102AE614511F420A0A9
Content-Type: text/plain; charset=us-ascii; name="Serial"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="Serial"
#!/bin/sh
#
# /sbin/init.d/serial
#
# Initializes the serial ports on your system
#
# Without uncommenting some of the lines in this script, you'll be unable to
# use ports other than the first two, and those only if they use "standard"
# IRQ values (whatever those are... :^) The rc.serial script made a couple
# machines I tested this on hang at this point in the boot process, so it's
# commented out by default. However, if you need to set up extended serial
# ports, it's a very good starting point. It usually works great.
# More info that will be useful: I did some testing and found that the lines
# in /etc/rc.d/rc.serial that are most likely to make the machine hang are the
# one that sets up /dev/cua3, and the last time, which causes a report to be
# issued to the console about how the ports were configured. This tries to
# report on *every* port... if you change it so it only lists the ports you're
# going to use (/dev/cua0 /dev/cua1 /dev/cua2 for example) that it probably
# won't cause a hang. Also, the "wild" interrupt detection used for auto-
# configuration can cause problems as well. I highly recommend using the
# manual configuration lines to avoid trouble.
#
case $1 in
start)
cd /dev
SETSERIAL="/sbin/setserial -b"
PORTS=`echo cua*`
echo -n "Configuring serial ports...."
# Do wild interrupt detection (uncomment if you're brave enough to
# attempt auto-configuration... )
#
# ${SETSERIAL} -W ${PORTS}
###########################################################
###############################################################
#
#
# mouse
${SETSERIAL} /dev/cua0 port 0x3F8 irq 4 autoconfig ${STD_FLAGS}
# no esta en uso ahora
${SETSERIAL} /dev/cua1 port 0x2F8 irq 3 autoconfig ${STD_FLAGS}
# modem
#${SETSERIAL} /dev/cua2 port 0x3E8 irq 11 autoconfig ${STD_FLAGS}
${SETSERIAL} /dev/cua2 port 0x3E8 irq 11 autoconfig ${STD_FLAGS}
# Placa de cuatro puertos y 1 IRQ (modificada)
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# este puerto no funciona
${SETSERIAL} /dev/cua3 uart 16450 port 0x3120 irq 7 ^fourport
# vhf1
${SETSERIAL} /dev/cua4 uart 16450 port 0x3128 irq 7 ^fourport
# uhf
${SETSERIAL} /dev/cua5 uart 16450 port 0x4120 irq 7 ^fourport
# hf
${SETSERIAL} /dev/cua6 uart 16450 port 0x4128 irq 7 ^fourport
###########################################################
###########################################################
#
# Print the results of the serial configuration process
#
###########################################################
echo "done."
${SETSERIAL} -bg ${PORTS}
;;
stop)
;;
*)
echo "usage: serial {start|stop}"
;;
esac
exit 0
# fin de SuSE
##################################################