On Wed, Oct 15, 2014 at 08:28:31PM +0700, Robert Elz wrote:
> [...]
> | Including "std.ath_hal" means that you pull in ath device code in your
> | kernel.
>
> No it doesn't. All it is is a bunch of option definitions, by themselves,
> those do (or should do) nothing. What's more, I verified that my DomU
> kernels from before this change had no ath related code in them at all (I'm
> not interested in the possibility of pci passthrough, or at least, not
> right now) and my Dom0 kernel did (as it was intended to).
OK, I didn't really check this, but it removing ath from the kernel
config file really cause all ath-related files to be ommitted, then there's
no reason to not have std.ath_hal inclued by default.
One can still use "no options ..." if he really wants to strip down
the kernel with only the required ath bits.
--
Manuel Bouyer <bou...@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
