https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194209
Garrett Cooper <n...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ahciems should be optional |ahciems should be optional
| |(at build or at run time)
--- Comment #2 from Garrett Cooper <n...@freebsd.org> ---
(In reply to Alexander Motin from comment #1)
> Not sure I understand your proposition. Do you want ahciem to be separate
> module, or do you want some tunable to disable it, or something else?
I jumped to a conclusion without providing a proper problem statement.
Basically we have a platform at work that has ahciems support, but our software
isn't coded up to handle ahciems currently, so this causes our software to poke
at the boot drives for ahciems status a little too much.
Having the support on by default makes sense from a usability perspective. In
general, being able to enable/disable ahciems on a global or a per-controller
basis (like atc.wc.enable) is desirable, because the end-user might not want
ahciems support to be enabled, or the device support provided/integrated in
with some vendors might be buggy/broken.
PS I was working on a patch to separate out the drivers, but then I realized
that it would introduce unnecessary complexity because of how the driver
currently hangs ahciems devices off of ahci controllers, and how the ahciems
instances are created/destroyed at ahci controller attach/detach.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
