From: d_north@ondec.lonestar.org (David G. North, CCP)
Newsgroups: comp.unix.pc-clone.32bit
Subject: Re: COM3-4 on SCO SVR3.2.4
Date: 5 Nov 92 14:59:33 GMT
Organization: onDEC systems, Dallas, TX

In article <Bx4B8x.H3x@mudos.ann-arbor.mi.us>,
 mju@mudos.ann-arbor.mi.us (Marc Unangst) writes:
> In article <1992Nov02.072948.23137@lasernet.co.za>,
>   aris@lasernet.co.za (Aris Stathakis) writes:
>>In <1cjl6pINN2it@usenet.INS.CWRU.Edu>
>>  ba014@cleveland.Freenet.Edu (Matthew C. Brinkhoff) writes:
>>>Is it possible to use the COM3/4 addresses at non-standard interrupts
>>>(ie, 2,5,or 7) with SCO SVR3.2.4?  It claims that it only supports 2
>>>serial ports 'IBM Standard'.
>>
>>Sure.  Just edit the relevant fields in /etc/conf/sdevice.d/sio
> 
> The 3.2v4.0 sio driver does not pick up the interrupt and I/O address
> range from the sdevice file.  The only purpose of those fields is for
> conflict checking by idbuild; it will refuse to build a kernel if the
> sdevice information for two configured devices conflicts.
> 
> The 3.2v4.0 sio driver gets its configuration information from a table
> in /etc/conf/pack.d/sio/space.c.  To change the configuration, you
> first need to add a table entry to this file, and fill in the
> appropriate information for your card.  (You can probably use the
> AT-IBM-COM3 entry as a template.)  Then, count entries from the top of
> the file, and enter your table entry's number in the sdevice file into
> the "unit number" field.  You should probably fill in the interrupt
> and I/O address range fields of the sdevice file, just for
> completeness.
> 
> At this point, I'll plead with SCO -- please, please put numbers every
> 10th entry or something in the sio device array in 3.2v4.2.  Counting
> lines from the top of a 60-some entry array gets real old real fast
> when you're trying to manually configure a new serial board,
> especially if it's over a voice connection to a client on the other
> side of the continent who is still learning how to use "vi".
Jeez - maybe it'd be easier to fix "vi".  I just went thru exactly
this process - I came from VMS, had to learn 'vi' basics, _and_ how to
do the serial stuff at the same time.  I had to put 3 digiboard modem/8
cards in the box.  One more file I had to work with - I can't remember
the precise location - was something like /etc/mkdev/serial/perms/SER or
some such.  I had to do that so that the mkdev serial command knew what
device id's to use to create the tty devices corresponding to the
modems.  Maybe this was a fluke of having 24 modems in one box, but
it may be important also.

> -- 
> Marc Unangst, N8VRH         | "There are two ways to solve this problem:
> mju@mudos.ann-arbor.mi.us   | the hard way, and the easy way.  Let's start
>                             | with the hard way."
>                             |   - W. Scheider, from a Physics lecture
Scheider was evidently not talking about UNIX.  Otherwise the quote would've
contained something like '...to solve this problem: the hard way, and an even
_more_ confusing way than that. ...'
-- 
David G. North, CCP
d_north@ondec.lonestar.org {...!texsun!montagar!ondec!d_north}
onDEC systems                                 "Everyone's crazy but you & me...
P.O.Box 795848, Dallas TX  75379-5848          and come to think about it, I'm
(214)985-1316 ... (214)902-3957                not so sure about you either!"