> > > Ok, have you _read_ the documentation on the driver model? In it,
> > > classes and devices are clearly spelled out as to what the differences
> > > are, and what shows up where.
> >
> > Yes, of course I've read it. It's lacking a number of important details.
>
> Hey, we've tried. I realize it's missing details, and though I know it's
> important to keep it updated, many other things take precedence.
Believe me, I understand how hard it is to keep documentation in sync with
a developing system.
> > Let me ask you this: Given a device that doesn't fit clearly into any of
> > the existing classes, how would you decide whether or not to create a new
> > class for it?
>
> If it does not fit into the existing classes, then there is probably a new
> class that needs to be created for it. While you're at it, please update
> the documentation and set a good example for the rest of us ;)
I'll offer a deal. When you and Greg have gotten the current set of
updates into the documentation, let me know and I'll add in explanations
of all the stuff that has puzzled me and been thrashed out in this thread.
At least I seem to be making progress. Thanks for the help.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/