Date: Thu, 27 Mar 2008 17:05:24 -0400 From: "Alexander Sack" <pisymbol@gmail.com> To: pluknet <pluknet@gmail.com> Cc: freebsd-hackers@freebsd.org, Julian Elischer <julian@elischer.org>, freebsd-drivers@freebsd.org Subject: Re: Stupid driver build/debug questions Message-ID: <3c0b01820803271405r2351cbbwb20b8b35c5621dcb@mail.gmail.com> In-Reply-To: <a31046fc0803271339l38230426p31292b3cc307ca27@mail.gmail.com> References: <3c0b01820803270851x24bfe739pea0bd4fb0ebecfb0@mail.gmail.com> <47EBF498.9090409@elischer.org> <3c0b01820803271252m488159ebi2af2255461f10358@mail.gmail.com> <a31046fc0803271339l38230426p31292b3cc307ca27@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 27, 2008 at 4:39 PM, pluknet <pluknet@gmail.com> wrote:
>
> On 27/03/2008, Alexander Sack <pisymbol@gmail.com> wrote:
> > On Thu, Mar 27, 2008 at 3:25 PM, Julian Elischer <julian@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).
Thank you very much, that is what I thought regarding it as an options
directive instead of a driver - I just wanted some validation before
going down that path.
Again, thanks guys,
-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@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?3c0b01820803271405r2351cbbwb20b8b35c5621dcb>