Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site midacs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!ucdavis!midacs!akp
From: akp@midacs.UUCP (Alan Powers)
Newsgroups: net.unix-wizards,net.wanted
Subject: 4.1 to 4.2 ioctl() differences???
Message-ID: <178@midacs.UUCP>
Date: Fri, 6-Sep-85 16:38:20 EDT
Article-I.D.: midacs.178
Posted: Fri Sep  6 16:38:20 1985
Date-Received: Sun, 8-Sep-85 04:29:49 EDT
Distribution: net
Organization: EG&G Idaho Inc., Idaho Falls
Lines: 30
Xref: watmath net.unix-wizards:14753 net.wanted:7124

HELP!!! Quick response please.


I would like to have the changes or explanation of ioctl() from 4.1 to 4.2 at 
the kernal level. We are trying to port kmc device driver from 4.1 to 4.2.  
The problem is with the interface with ioctl() in the kmc.

We are using the kmc driver for RJE(hasp link) on 4.1 and trying to get it
to work on 4.2.  Does anyone out there have RJE working?


The old interface was
kmcioctl(dev,cmd,arg,mode) 
'dev' is the major,minor number of the device.
'cmd' control the  setting or reading control status registers(CSR).
'arg' is an array of values which was used to set or read the CSR's.
'mode' ?????
At least this what I think it did.

I know on 4.2 ioctl only uses 3 parameters, but I don't know EXACTLY 
how they are used. Also explain how the kernal ioctl has changed from
4.1 to 4.2.

kmcioctl(dev,cmd,data)
'dev'   ?
'cmd'   ?
'data'  ?
-- 
Alan Powers	Phone: 208-526-9498
   ...!ucbvax!ucdavis!midacs!isew01!akp