On Fri, Feb 04, 2000 at 03:45:06AM +0000, [EMAIL PROTECTED] wrote:
> Message-Id: 1462_kb2shu
> From: kb2shu@kb2shu.#sca.ca.usa.noam
> To: [EMAIL PROTECTED]
>
>
> > > I've created the following init file:
> > >
> > > [root@gateway /proc]# cat /etc/rc.d/rc.serial
> > > SETSERIAL=/bin/setserial
> > > echo "Configuring serial ports...."
> > > #
> > > ${SETSERIAL} /dev/ttyS0 uart 16550a port 0x3f0 irq 4 ^fourport
> > > ${SETSERIAL} /dev/ttyS1 uart 16550a port 0x2f0 irq 3 ^fourport
> > > ${SETSERIAL} /dev/ttyS2 uart 16550a port 0x3e0 irq 10 ^fourport
> > > ${SETSERIAL} /dev/ttyS3 uart 16550a port 0x2e0 irq 10 ^fourport
> > > #
> > > echo "done"
>
> Try this instead........works here!
>
> ${SETSERIAL} /dev/cua0 uart 16550a port 0x3f0 irq 4 ^fourport
> ${SERSERIAL} /dev/cua1 uart 16550a port 0x2f0 irq 3 ^fourport
Rubbish. (excuse me :) )
/dev/ttyS0 and /dev/cua0 are in fact the same device so your change makes
absolutely no difference. The only difference between the two is the
opening behaviour. ttyS0 blocks when the attached device is not
ready (DCD low etc.) while cua0 lets you go on. And IIRC cua0 blocks if there
is an other user already _connected_ (i.e. transmitting data).
*** THE USE OF ANY cua* PORT IS DEPRECATED ***
because most (all) serial commuication programs expect and use lockfiles
which won't work with differently named devices.
You should not be surprised if someday suddenly all cua* prots are gone :-)
> and so on.
Brians real problem seams he want to adjust the base address to 0x3f8 (he says
so in his text) but infact uses 0x3f0 (typo!) in his rc-script
73 Thorsten
--
| Thorsten Kranzkowski Internet: [EMAIL PROTECTED] |
| Mobile: ++49 161 7210230 Snail: Niemannsweg 30, 49201 Dissen, Germany |
| Ampr: dl8bcu@db0lj.#rpl.deu.eu, [EMAIL PROTECTED] [44.130.8.19] |
