Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!rpi!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!nebulus!root
From: root@nebulus.UUCP (Dennis S. Breckenridge)
Newsgroups: comp.unix.wizards
Subject: Re: AT&T SysV 386 Driver for Targa
Message-ID: <1990Mar28.150834.10821@nebulus.UUCP>
Date: 28 Mar 90 15:08:34 GMT
References: <1990Mar28.045430.6491@ncsuvx.ncsu.edu>
Reply-To: root@nebulus.UUCP (Dennis S. Breckenridge)
Distribution: usa
Organization: Alchemy Mindworks, Vancouver, Canada
Lines: 25

In article <1990Mar28.045430.6491@ncsuvx.ncsu.edu> fostel@cscadm.UUCP (Gary Fostel) writes:
> 
>     Does anyone have those AT&T manuals and recommend them highly enough
>     to scrape up the money to buy them?  Is the 386 SysV enough like 
>     other "generic" unix systems that I can assume common kernel functions
>     are there with the names I expect?  Not having the sources to this

I could not think of writing a driver without the BCS manuals. They are
invaluable! Be aware that they are porting base specific (read that as 
3B2/**) but it is the only place, short of the source, to get a list of
kernel functions. The second part of the equation is procuring a copy
of the Integrated Software Design Guide for the 386. This gives a good
overview of a simple device driver, how to install it in the 386 driver
layout, etc... Spend the 350 + whatever the ISDG is worth. I have done 
quite a bit of driver work without these manuals in the past an I found
I was spending more time reverse engineering parts of the O/S than generating
new code. Now driver work comes easy! ;-)



-- 
-----------------------------------------------------------------------------
Dennis S. Breckenridge  (604) 277-7413   dennis@nebulus.uucp           VE7TCP
               EMACS: Eight Megabytes And Constantly Swapping!
-----------------------------------------------------------------------------