|
mario wrote:
Under QNX4 there is no such think as a driver, it just a program like any other. Depending how you want you other program to interface with the driver, writing it could be very simple.
Linux driver are not portable to QNX, if you have the source it can be use a reference but that's about it.
Thanks for the help... I understand that "drivers" are "other programs"... but note that the official "System Architecure" document for QNX 4.25 on page 113 has a subsection entitled "Device Drivers" so it does appear that QNX uses the term "device driver", although I realize that in Linux these may be "inserted into the monolithic kernel" where as in QNX they are just another process that cooperates with the microkernel... still it seems they do call them "device drivers" at least sometimes.
From that document:
"Device drivers
The following illustration shows a typical QNX device subsystem:
[diagram]
The Device Manager process (Dev) manages the flow of data to and
from the QNX application processes. The hardware interface is
managed by individual driver processes. Data flows between Dev and
its drivers through a set of shared memory queues for each terminal
device."
Anyway, the link that I gave where the other guy tried to use a similar PC/104 he did in fact take a Linux driver and compile it under QNX after just making a very small mod' or 2 and I think it worked for him... just I guess it can't be "installed into the kernel" in the same way... just a separate process.
Thanks for the thoughts in any case.... |