Section 9 is for software engineers responsible for creating, modifying, or maintaining
drivers that run on this operating system and beyond. It assumes that the reader is
familiar with system internals and the C programming language.
PCMCIA Standard
The PC Card 95 Standard is listed under the SEE ALSO heading in some Section 9
reference pages. This refers to documentation published by the Personal Computer
Memory Card International Association (PCMCIA) and the Japan Electronic Industry
Development Association (JEIDA).
How to Use Section 9
Section 9 is divided into the following subsections:
9E Driver Entry Points – contains reference pages for all driver entry point
routines.
9F Kernel Functions – contains reference pages for all driver support routines.
9P Driver Properties – contains reference pages for driver properties.
9S Data Structures – contains reference pages for driver-related structures.
Compatibility Note
Sun Microsystem’s implementation of the DDI/DKI was designed to provide binary
compatibility for third-party device drivers across currently supported hardware
platforms across minor releases of the operating system. However, unforeseen
technical issues may force changes to the binary interface of the DDI/DKI. We cannot
therefore promise or in any way assure that DDI/DKI-compliant device drivers will
continue to operate correctly on future releases.
Section 9E describes the entry-point routines a developer can include in a device
driver. These are called entry-point because they provide the calling and return syntax
from the kernel into the driver. Entry-points are called, for instance, in response to
system calls, when the driver is loaded, or in response to STREAMS events.
Kernel functions usable by the driver are described in section 9F.
In this section, reference pages contain the following headings:
■
NAME describes the routine’s purpose.
■
SYNOPSIS summarizes the routine’s calling and return syntax.
■
INTERFACE LEVEL describes any architecture dependencies. It also indicates
whether the use of the entry point is required, optional, or discouraged.
■
ARGUMENTS describes each of the routine’s arguments.
■
DESCRIPTION provides general information about the routine.
■
RETURN VALUES describes each of the routine’s return values.
■
SEE ALSO gives sources for further information.
Intro(9E)
Introduction to
Section 9E
16 man pages section 9: DDI and DKI Driver Entry Points • Last Revised 15 May 2001
剩余191页未读，继续阅读
weixin_40191861_zj
- 粉丝: 80
- 资源: 1万+
我的内容管理
展开
最新资源
- 批量文件重命名神器：HaoZipRename使用技巧
- 简洁注册登录界面设计与代码实现
- 掌握Python字符串处理与正则表达式技巧
- YOLOv5模块改进 - C3与RFAConv融合增强空间特征
- 基于EasyX的C语言打字小游戏开发教程
- 前端项目作业资源包：完整可复现的开发经验分享
- 三菱PLC与组态王实现加热炉温度智能控制
- 使用Go语言通过Consul实现Prometheus监控服务自动注册
- 深入解析Python进程与线程的并发机制
- 小波神经网络均衡算法：MATLAB仿真及信道模型对比
- PHP 8.3 中文版官方手册(CHM格式)
- SSM框架+Layuimini的酒店管理系统开发教程
- 基于SpringBoot和Vue的招聘平台完整设计与实现教程
- 移动商品推荐系统：APP设计与实现
- JAVA代码生成器：一站式后台系统快速搭建解决方案
- JSP驾校预约管理系统设计与SSM框架结合案例解析
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
