> This makes me believe the devclass_t structure defined in a driver is
> never used. Is there another code path I'm missing?
Yes; there is a twisty maze of macros which ultimately results in the
driver_module_data structure ending up in a linker set. The devclass
structure is, as Warner pointed out, critical in maintaining correct
numbering for a class of devices.
For example; you can legitimately have several different drivers calling
themselves "foo", but there must only be one "foo" devclass, and they all
have to reference it.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
