1. Device driver calling another device driver.
I am having a problem writing a "meta-driver", ie one that is sandwiched
between the kernel and a real device driver. The platform I am using
consists of a Sun IPC, running SunOS 4.1.1.
My problem is that in attempting to use the OPEN(2V) system call from within
the "xxopen" routine of my metadriver (to open another device-driver (which
then opens the device)); OPEN(2V) "fails".
It appears that calling OPEN(2V) from within the kernel requires a different
calling sequence and argument list. Viz-a-viz: instead of a file descriptor
being returned by OPEN(2V), it seems a pointer is returned (which itself is
a pointer to something else).
Is this true? Is the OPEN(2V) syscall different for a process executing in
user address space, compared to the OPEN call executed by a process running
in kernel mode/address space?
If this is true for OPEN, what about CLOSE, READ, WRITE, etc? Unfortunately,
I don't have (easy) access to any Unix (source) code, to verify this.
Thanks in advance for help/advice.
2. connecting serial ports of two Linux pc's
3. Device driver question (generic device driver)
4. xntpd - stopping it reporting to the console?
5. PCI device vs SCSI device driver
6. HP LaserJet 4L
7. Device driver for a device
8. Different log files for virtual hosts
9. Device driver devices.pci.scsi missing
10. New device device driver development tool for Solaris.
11. one device driver and 2 devices for it, impossible with linux ?
12. My first device driver => "No such device" :(
13. New device device driver development tool for Solaris.