Re: listing all modules compiled into a kernel instance

2011-03-03 Thread Carl
On 2011-03-03 7:08 AM, John Baldwin wrote: Ah, but your assertion is what is wrong. There is no 'apic' module for 'device apic' for example. Also, a single 'device foo' might enable multiple "modules" (e.g. if foo supports devices on both PCI and ISA buses, you will have foo/pci and foo/isa mod

Re: listing all modules compiled into a kernel instance

2011-03-03 Thread John Baldwin
On Thursday, March 03, 2011 3:03:02 am Carl wrote: > On 2011-03-01 2:13 PM, John Baldwin wrote: > >> On 2011-03-01 5:00 AM, John Baldwin wrote: > Maybe ucom doesn't appear because it doesn't have a DRIVER_MODULE() > declaration (because it isn't a driver). > >>> > >>> Yes, that would expl

Re: listing all modules compiled into a kernel instance

2011-03-03 Thread Carl
On 2011-03-01 2:13 PM, John Baldwin wrote: On 2011-03-01 5:00 AM, John Baldwin wrote: Maybe ucom doesn't appear because it doesn't have a DRIVER_MODULE() declaration (because it isn't a driver). Yes, that would explain it. I can explicitly include ucom in a kernel by adding "device ucom" in

Re: listing all modules compiled into a kernel instance

2011-03-02 Thread John Baldwin
On Tuesday, March 01, 2011 3:01:48 pm Carl wrote: > On 2011-03-01 3:20 AM, Maxim Khitrov wrote: > > kldstat provides information about components that were loaded > > dynamically. If your kernel was built with INCLUDE_CONFIG_FILE option > > (enabled by default in GENERIC), then you can see the stat

Re: listing all modules compiled into a kernel instance

2011-03-01 Thread Warren Block
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

Re: listing all modules compiled into a kernel instance

2011-03-01 Thread Jason Helfman
On Tue, Mar 01, 2011 at 12:01:48PM -0800, Carl thus spake: On 2011-03-01 3:20 AM, Maxim Khitrov wrote: kldstat provides information about components that were loaded dynamically. If your kernel was built with INCLUDE_CONFIG_FILE option (enabled by default in GENERIC), then you can see the static

Re: listing all modules compiled into a kernel instance

2011-03-01 Thread Carl
On 2011-03-01 3:20 AM, Maxim Khitrov wrote: kldstat provides information about components that were loaded dynamically. If your kernel was built with INCLUDE_CONFIG_FILE option (enabled by default in GENERIC), then you can see the static components using: config -x /boot/kernel/kernel As has b

Re: listing all modules compiled into a kernel instance

2011-03-01 Thread John Baldwin
On Tuesday, March 01, 2011 6:49:17 am Daniel O'Connor wrote: > > On 01/03/2011, at 15:10, Carl wrote: > > Kernel drivers can be (and in at least one case are) compiled into the > > kernel but are not reported when queried for, at least not in a way that I am aware of. For example, the ucom drive

Re: listing all modules compiled into a kernel instance

2011-03-01 Thread Damien Fleuriot
On 3/1/11 12:20 PM, Maxim Khitrov wrote: > On Mon, Feb 28, 2011 at 11:40 PM, Carl wrote: >> Kernel drivers can be (and in at least one case are) compiled into the >> kernel but are not reported when queried for, at least not in a way that I >> am aware of. For example, the ucom driver is present i

Re: listing all modules compiled into a kernel instance

2011-03-01 Thread Bruce Cran
On Tue, 1 Mar 2011 06:20:29 -0500 Maxim Khitrov wrote: > kldstat provides information about components that were loaded > dynamically. If your kernel was built with INCLUDE_CONFIG_FILE option > (enabled by default in GENERIC), then you can see the static > components using: It seems it can also

Re: listing all modules compiled into a kernel instance

2011-03-01 Thread Maxim Khitrov
On Mon, Feb 28, 2011 at 11:40 PM, Carl wrote: > Kernel drivers can be (and in at least one case are) compiled into the > kernel but are not reported when queried for, at least not in a way that I > am aware of. For example, the ucom driver is present in the GENERIC kernel > in this way. My expecta

Re: listing all modules compiled into a kernel instance

2011-03-01 Thread Damien Fleuriot
On 3/1/11 5:40 AM, Carl wrote: > Kernel drivers can be (and in at least one case are) compiled into the > kernel but are not reported when queried for, at least not in a way that > I am aware of. For example, the ucom driver is present in the GENERIC > kernel in this way. My expectation was that "k

Re: listing all modules compiled into a kernel instance

2011-03-01 Thread Daniel O'Connor
On 01/03/2011, at 15:10, Carl wrote: > Kernel drivers can be (and in at least one case are) compiled into the kernel > but are not reported when queried for, at least not in a way that I am aware > of. For example, the ucom driver is present in the GENERIC kernel in this > way. My expectation w

listing all modules compiled into a kernel instance

2011-02-28 Thread Carl
Kernel drivers can be (and in at least one case are) compiled into the kernel but are not reported when queried for, at least not in a way that I am aware of. For example, the ucom driver is present in the GENERIC kernel in this way. My expectation was that "kldstat -v" would list it, if presen