Stupid driver build/debug questions

[Alexander Sack]

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).

Thanks!

-aps

-- 
"What lies behind us and what lies in front of us is of little concern
to what lies within us." -Ralph Waldo Emerson
_______________________________________________
freebsd-hackers at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"