In kernel source's Documentation/driver-model there are a few other documented structures for Linux Kernel drivers: device.txt platform.txt devres.txt binding.txt bus.txt class.txt driver.txt interface.txt overview.txt porting.txt On Wed, Apr 1, 2009 at 3:51 AM, xin yuepeng <yuepeng.xin@xxxxxxxxx> wrote: > Hi, > I met this situation as you. I chose the platform_driver... It seems > ok. > > Lucky > > 2009/3/31 Ole Loots <ole@xxxxxxxxxxxxx> >> >> Hello there, >> >> I'm writing a Driver that uses an not-so-well-known Bus System. I'm >> developing for the at91 Processor, the processor has an "Extension Bus >> Interface" ... it's good enough to make CF Cards, IDE disks, etc. work. >> >> I'm developing a driver for an Hardware device that is connected to the >> Bus. ( the device is some kind of higher-voltage IO Pin collection... 15 - >> 45 V) >> >> My questions is: Should I work with structure: platform_driver or is >> there some kind of different structure that fit's better? >> >> -- >> To unsubscribe from this list: send an email with >> "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx >> Please read the FAQ at http://kernelnewbies.org/FAQ >> > > -- Regards, Peter Teoh -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
