Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!think!husc6!cca!mirror!datacube!ftw
From: ftw@datacube.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Motorola Sys V help
Message-ID: <106600032@datacube>
Date: 11 Feb 88 20:41:00 GMT
References: <106600031@datacube>
Lines: 33
Nf-ID: #R:datacube:106600031:datacube:106600032:000:1270
Nf-From: datacube.UUCP!ftw    Feb 11 15:41:00 1988


...one thing I forgot:

I also need to test if a given piece of hardware exists on the bus.  There
is a function called bprobe() that does this.  It takes two args, the first
is a physical address, the second is a char sized quantity to be *written*
to that address.  For my driver, it is unacceptable for the probe to write
to the address.  Also, since not all of the hardware I intend to support
will respond to byte-width accesses, I need a 16-bit sized probe as well.
There seems to be an "sprobe" function in my kernel, but I it must not
be what I think it is because it never goes out to the bus (confirmed by
using a VME bus analyzer).

Questions: How do I test for *read* access to hardware?  What exactly is
the sprobe() function?

SunOS has peek() and peekc(), which will probe for hardware and return
a 16-bit or 8-bit (resp.) quantity at the address you ask for, or they
returns (int)-1 if there was a bus-error.  These are what I need to model
under System V.


Thank You for Your Support.


				Farrell T. Woods 

Datacube Inc. Systems / Software Group	4 Dearborn Rd. Peabody, Ma 01960
VOICE:	617-535-6644;	FAX: (617) 535-5643;  TWX: (710) 347-0125
INTERNET: ftw@datacube.COM
UUCP: {rutgers, ihnp4, mirror}!datacube!ftw

"OS/2 -- Half an operating system"