TY - GEN
T1 - Prototype of the device driver generation system for unix-like operating systems
AU - Katayama, Tetsuro
AU - Saisho, Keizo
AU - Fukuda, Akira
PY - 2000/1/1
Y1 - 2000/1/1
N2 - Writing device drivers spends much time and makes efforts because it needs knowledge of the target device and operating system (OS). In order to lighten the burden, the authors have proposed a model to generate device drivers and a device driver generation system before. The system generates a source code of a device driver from three inputs: device driver specification, OS dependent specification, and device dependent specification. The device drivers generated in the model are evolutionary because they can be expanded their features easily. They, however, are not always effective because the burden in describing the device dependent specification, which is one of the inputs, is nearly as same as the traditional method. In this paper, to aim at more reduction of the burden, device drivers are abstracted again, each input is defined afresh, and then a prototype of the system is implemented. As an example of the generation, an interrupt handler of a network device, FreeBSD and Linux as the target OS, and Etherlink XL as the target device are chosen. The OS dependent specification and the device dependent specification can be reused in each OS and device, respectively. As a result, an identical device dependent specification can be applied to the both OSs. The burden in generating new device drivers or porting ones to other OSs can be reduced.
AB - Writing device drivers spends much time and makes efforts because it needs knowledge of the target device and operating system (OS). In order to lighten the burden, the authors have proposed a model to generate device drivers and a device driver generation system before. The system generates a source code of a device driver from three inputs: device driver specification, OS dependent specification, and device dependent specification. The device drivers generated in the model are evolutionary because they can be expanded their features easily. They, however, are not always effective because the burden in describing the device dependent specification, which is one of the inputs, is nearly as same as the traditional method. In this paper, to aim at more reduction of the burden, device drivers are abstracted again, each input is defined afresh, and then a prototype of the system is implemented. As an example of the generation, an interrupt handler of a network device, FreeBSD and Linux as the target OS, and Etherlink XL as the target device are chosen. The OS dependent specification and the device dependent specification can be reused in each OS and device, respectively. As a result, an identical device dependent specification can be applied to the both OSs. The burden in generating new device drivers or porting ones to other OSs can be reduced.
UR - http://www.scopus.com/inward/record.url?scp=44949102885&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=44949102885&partnerID=8YFLogxK
U2 - 10.1109/ISPSE.2000.913251
DO - 10.1109/ISPSE.2000.913251
M3 - Conference contribution
AN - SCOPUS:44949102885
T3 - International Workshop on Principles of Software Evolution (IWPSE)
SP - 302
EP - 310
BT - Proceedings - International Symposium on Principles of Software Evolution, ISPSE 2000
PB - Institute of Electrical and Electronics Engineers Inc.
T2 - International Symposium on Principles of Software Evolution, ISPSE 2000
Y2 - 1 November 2000 through 2 November 2000
ER -