git: aps(4): changes for DragonFly -- welcome aps(4)!
johannes.hofmann at gmx.de
Sun Feb 21 01:59:15 PST 2010
Constantine A. Murenin <mureninc at gmail.com> wrote:
> On 20 February 2010 06:26, Johannes Hofmann <johannes.hofmann at gmx.de> wrote:
>> Constantine A. Murenin <cnst at crater.dragonflybsd.org> wrote:
>>> commit 23e32507c5673806886375832fea602a16115cdd
>>> Author: Constantine A. Murenin <cnst+dfly at bugmail.mojo.ru>
>>> Date: Thu Feb 18 21:30:09 2010 -0500
>>> aps(4): changes for DragonFly -- welcome aps(4)!
>> Works fine on a thinkpad T42p when compiled into the kernel. However I
>> can't make it work when kldloading it. Is this expected?
> Yes; in fact, the module is not documented as supported and is not
> connected to the build intentionally. The isa(4) modules in general
> do not appear to be supported ? if you load it after boot, the
> respective device_probe method will never be called even once (note
> that there is an extra device_printf in the module's aps_probe), so
> it's not anything that's specific to aps(4).
Ah ok. I didn't find any application using aps(4) yet anyway :)
> If you can compile it both as a module and in-kernel, and load the
> module before boot, then you can, however, unload the module when the
> system is running, and then load it once again, but it seems that
> after this you'll no longer be able to unload it successfully. :-)
More information about the Commits