rgc@edison.GE.COM (Rick Carl) (01/09/88)
Excuse me if this has been asked and answered previously...BUT
I have been recently assigned the task of writing a device driver
for one of our products that will reside in both the PC and the microVAX
running unix and/or venix or (some 386-ix).
We haven't decided which op sys we want to support on the PC version...
the microVAX may run VAXELN or VMS or System V.
My problem is that I am now just coming of age with the unix system and
know virtually nothing of how to build a device driver for it...this will
be my first major task using a unix op sys.
I am looking for (1) help with generic driver information; (2) examples of
device drivers; or (3) references in which building device drivers are
outlined...
Any and all information will be greatly appreciated.
--
Rick Carl GE Fanuc - Charlottesville, VA 22901
rgc@edison.GE.COM old arpa: rgc%edison.GE.COM@seismo.CSS.GOV
rgc@edison.UUCP old uucp: {seismo,decuac,houxm}!edison!rgcgeorgeh@sco.COM (George Hoffer) (10/10/89)
Questions:
1. Is anyone still writing device drivers to support the
the use of the rint (receive data interrupt) and the
xint (transmit data interrupt) routines? Has anyone
heard of their use in UNIX SV 3.2/386? If so, with
what types of devices are these used?
2. Has anyone heard of an instance where the bdevsw
print routine has been called by the kernel? Also,
would anyone recommend putting code other than a
cmn_err or printf call in this routine? What is so
special about the print routine that it should occupy a
place in the bdevsw?
3. Does anyone know of any standard body establishing
a registry for device driver prefix names, or any
other of the unique names that are used in device
drivers such as STREAMS module names, or interrupt
vector numbers? I am looking for a registry service
that will register this information for any vendor
regardless of whether the device driver is for a
piece of hardware or for a pseudo-device.
Thank you.
George Hoffer
uunet!sco!georgehDave.Wilson@p0.f4.n494.z5.fidonet.org (Dave Wilson) (03/14/90)
I am attempting to write a SVR32 device driver for Bell's ICC multiport card. The idea is to use the driver to download 80186 executable code to the card, and then release the reset latch to run it. What is the best way to download this code? My ICC docs claim that the ICC memory may be dual-ported with that of the 80386, but how will I write the code to a specific memory location in the 80386 from the driver process? Please email answers/code samples. Thanks a lot. Dave Wilson ccdw.rures@f4.n494.z5.fidonet.org -- uucp: uunet!m2xenix!puddle!5!494!4.0!Dave.Wilson Internet: Dave.Wilson@p0.f4.n494.z5.fidonet.org