Stupid driver build/debug questions

[pluknet]

On 27/03/2008, Alexander Sack <pisymbol at gmail.com> wrote:
> On Thu, Mar 27, 2008 at 3:25 PM, Julian Elischer <julian at elischer.org> wrote:
>  > Alexander Sack wrote:
>  >  > Hello:
>  >  >
>  >  > New to the FreeBSD kernel and I'm investigating a driver problem
>  >  > (wasn't sure what list this should go on).
>  >  >
>  >  > I was wondering how to make a driver statically built instead of a
>  >  > loadable module?  Is this an artifact of the driver source build or
>  >  > the generic kernel configuration mechanism via options etc.?  i.e.
>  >  > does a driver need to use something different than the bsd.kmod.mk
>  >  > template make file to build a static driver.
>  >  >
>  >  > What I am trying to do is break at attach time more easily than
>  >  > stepping through driver_probe_and_attach()/driver_attach_child() until
>  >  > the attach routine gets called.  I realize I can add a kdb_enter() but
>  >  > I was trying to do this on a live system without rebuilding the kernel
>  >  > (I understand this contradicts my first question but I still want to
>  >  > know how to build drivers statically).
>  >
>  >  put the filennames in /sys/conf/files or files.i386 (or whatever)
>  >
>  >  at one stage you could also have a files.{CONFIGNAME} but I haven't
>  >  tried that for a long time.
>
>
> Thanks for the response.  I will try this but I do have an obvious
>  question, the build scripts do not need to be edited at all with the
>  extra directory/files?  It will just pickup my driver directory and
>  link against the kernel automagically?

Yes, It will if you add them to standard files list (see conf/files).
(Otherwise if you want it as options directive in your kernel config
than you should mark its module name in conf/files and also put
an appropriate record into conf/options).

-
pluknet