Lines Matching refs:It
33 3. It is not always obvious by their names which drivers/options
40 This was a conscious decision by core@ some years ago. It is
45 boot loader "push" the module at boot time. (It used to do
70 is not. Thus, even though bpf_filter is modular, it MUST be
74 Another example is sysmon_taskq module. It is required by
77 sysmon_power code is modularized, it is referenced by the
85 which has not been modularized makes it extremely difficult to test
103 currently, config(1) doesn't handle this - it doesn't allow an
106 and bus1/foo_bus1.c ... busn/foo_busn.c is annoying. It would be
113 13. It seems that we might want some additional sets-lists "attributes"
115 architectures have PCI bus capabilities, but not all. It is rather
168 to declare the list of vendor/product/other tuples that it can
181 17. (From John Nemeth) It would be potentially useful if a "push" from
182 the bootloader could also load-and-push a module's .plist (if it
190 based on module classes and declared dependencies. It might be
192 invocations of module_class_init(), and it might be useful to have a
198 the name of file from which the module is loaded. Thus, it is
205 It would take some serious thought to get such support right. For
225 really cool. (See sys/kern/kern_exec.c?) It ends up auto-loading
Indexes created Tue Oct 28 02:10:10 GMT 2025