I think the simple answer is: the scheme I've outlined doesn't work
with on-demand loading drivers. Richard has indicated that devfs can
manage both cases which is great. [ Although I've never been entirely
sure that demand loading based on accesses to device inodes is the
right level of abstraction -- at a higher level it could be accesses
to "services" of some kind, which can in turn invoke scripts, install
modules etc etc ].
I'm not beating on devfs, I just wanted to tell people writing modular
drivers today that if they run in to problems with major numbers then
there is an workable approach which is both backward and forward
compatible. That's hugely important for anything outside the main
kernel distribution.
Cheers,
Matt
-
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/