Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Mar 2008 12:25:12 -0700
From:      Julian Elischer <julian@elischer.org>
To:        Alexander Sack <pisymbol@gmail.com>
Cc:        freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org
Subject:   Re: Stupid driver build/debug questions
Message-ID:  <47EBF498.9090409@elischer.org>
In-Reply-To: <3c0b01820803270851x24bfe739pea0bd4fb0ebecfb0@mail.gmail.com>
References:  <3c0b01820803270851x24bfe739pea0bd4fb0ebecfb0@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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!
> 
> -aps
> 

_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47EBF498.9090409>