> Oliver Xymoron wrote:
> > My point is that module != driver. A module is something that may be
> > compiled separately from the kernel.
>
> "may" is the key word. A driver can be compiled separately from the
> kernel too, of course, making a driver and module the same thing.
No, you still misunderstand. A driver is a driver, a module is a module.
Some drivers happen to be modules and most modules happen to be drivers.
But they're _different concepts_. A driver can also be several modules or
a module can contain several drivers. Things can be modules that aren't
drivers - for instance, I once wrote a module that was a filesystem
image.
And I still maintain that simplified register functions are needed at the
top level of proc. It's a mess.
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/