check this: https://ldn.linuxfoundation.org/article/the-linux-driver-model-a-better-way-support-devices In Windows, drivers programming have different models, eg, WDM, but it is practically useless. different version of windows can even afford to change the device model from previous generation. similarly, for linux, if u goto kernel source "drivers" subdirectory, and look at all the drivers written there......there are many different patterns, very difficult to extract out some generic models. neither are they haphazardly written. the point is (personal opinions, please :-)): many of us have different ways of programming, and irregardless of the model, the same program most likely will still compile, for backward compatibility. and because of this, it is unlikely to be modified just to conform to the new model. sorry again, if i am wrong in my thinking..... On Sat, Sep 6, 2008 at 9:42 PM, Steven Zhou <lullaby2005@xxxxxxxxx> wrote: > Hi guys, > > I'm a newbie about Linux driver developing, and now I'm studying the Linux > driver model. > > I have refered the book <Understanding the Linux Kernel>, but... I'm still > confused about Linux drver model. > Such as the relationships among kobject, kset, subsystem, bus(especially > platform-bus), device, drvier. Then > I turned to the book <Linux Device Driver>, but the situation is still > on..... The basic conception in my mind is > not very clear. > > Is there anybody have the good matirial about Linux device model? Can you > share it? > > Thanks in advance. > > -- > Best Regards. > -- 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