> Hi Brian, > > It's better you see the existing PCI device driver in > /usr/src/linux/drivers/ directory. E.g. PCI ethernet card, you can see how > to detect the base address, irq, registers, etc. > Starting with PCI drivers from the Linux tree is not realy that helpfull I belive, as the structure of RTLinux drivers is quite different. The init and cleanup sections are comparable with respect to the way PCI resources are managed - but there is no need to implement the fops unless you also want full access to the device from the non-RT side of the system.
The structure of a PCI driver for RTLinux I would see as *) resource managment in the linux kernel (init_module/cleanup_module) *) a set of low-level functions that are called by RT-threads So there is no need to register this device with the Linux kernel - you only need to lock the I/O and irq resources. In this model a device driver for RTLinux is no more than a "library" of low-level functions - so generally its easier to write than Linux device drivers. hofrat -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/
