On Tue, 1 Mar 2011, Jason Helfman wrote:
On Tue, Mar 01, 2011 at 12:01:48PM -0800, Carl thus spake:
I can explicitly include ucom in a kernel by adding "device ucom" in the
configuration file, in which case it would call DRIVER_MODULE(), right?
That would then make it appear in the "kldstat -v" list? So why is it a
driver when it's done explicitly, but not a driver when done implicitly?
That makes no sense to me since the functionality doesn't change. IMHO,
this is a bug that needs to be fixed, not just for ucom but any
implicitly included driver.
Who should submit a bug report?
There was a documentation bug that was put in regarding the ucom device, and
it was to update the device name in the documentation.
http://www.freebsd.org/cgi/query-pr.cgi?pr=155074
I don't know if a PR is still required, but this may be worth a look first.
usb_quirk.4 appears to be a copy and edit of ucom.4. The device name
edit was missed, so it still referred to ucom.
I don't think this affects what you're talking about.
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
