[openbeos] Re: Add-ons/Module problems/ideas??

>If a kernel module need to publish a /dev/* entry, why it's not a
>*driver* instead? If some part of his code need to be (re)used by
>another driver(s), let's split it into a module and a driver (even
>in the same binary file!)... it's a the purpose of kernel modules,
>in fact.

This brings up a simple question I was curious about (being a 
non-driver programmer). What really is the difference between modules 
and drivers? I know that modules are there to provide common 
functionality to many drivers, but is that it? Seems like there's 
something else I'm missing, otherwise why doesn't the kernel treat 
modules and drivers as the same thing, and let them decide whether 
they publish devices or export APIs?

Rudyatek

Other related posts: