kak@hico2.UUCP (Kris A. Kugel) (03/18/91)
In checking out some of the details in the device driver
development guide (I still don't have a volunteer for providing
an temporary archive site), I looked at the include files in
the IHVDIAG+IN.Z file in the att7300/STORE area on osu-cis.
Some of the include files have the same name as some of those already
existing on my version 3.51m, and, when I checked that out,
look like versions from a previous level.
I'd avoid adding these indescriminently into your header directories,
you might wipe out more current versions, and I have no idea what
effect using the other, unmatched include files for purposes other
than diagnostics will have.
Does anybody know how we can update this include file set?
Kris A. Kugel
( 908 ) 842-2707
uunet!tsdiag.ccur.com!hico2!kak
{daver,ditka,zorch}!hico2!kak
internet: kak@hico2.westmark.comfloyd@ims.alaska.edu (Floyd Davidson) (03/18/91)
In article <1271@hico2.UUCP> kak@hico2.UUCP (Kris A. Kugel) writes: > >In checking out some of the details in the device driver >development guide (I still don't have a volunteer for providing >an temporary archive site), I looked at the include files in >the IHVDIAG+IN.Z file in the att7300/STORE area on osu-cis. > >Some of the include files have the same name as some of those already >existing on my version 3.51m, and, when I checked that out, >look like versions from a previous level. > >I'd avoid adding these indescriminently into your header directories, >you might wipe out more current versions, and I have no idea what >effect using the other, unmatched include files for purposes other >than diagnostics will have. > >Does anybody know how we can update this include file set? > Aren't they basically two distinct and separate things? The diagnostics disks build everything into a kernel and that kernel would very likely need to be configured different than a "normal" kernel. I haven't looked all that closely at the header files for diagnostics, but I did take some time to compare disk access code to disassembled code from the normal driver. Not much is the same. I'd be careful about an indescriminent update in that direction too. Floyd -- Floyd L. Davidson | floyd@ims.alaska.edu | Alascom, Inc. pays me Salcha, AK 99714 | Univ. of Alaska | but not for opinions.