Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!su-news-hub1.bbnplanet.com!news.bbnplanet.com!newsfeed.direct.ca!nntp.portal.ca!cynic.portal.ca!not-for-mail From: cjs@cynic.portal.ca (Curt Sampson) Newsgroups: comp.unix.bsd.misc Subject: Re: BSD driver structures question Date: 25 Apr 1997 10:22:03 -0700 Organization: Internet Portal Services, Inc. Lines: 19 Message-ID: <5jqp7r$45t@cynic.portal.ca> References: <5jqcpu$en9@chavvy.spider.com> NNTP-Posting-Host: cynic.portal.ca Xref: euryale.cc.adfa.oz.au comp.unix.bsd.misc:3094 In article <5jqcpu$en9@chavvy.spider.com>, Stewart Potter <stewart@spider.com> wrote: > >The thing is, how does the kernel know about >a structure in a device driver C-source file? Is a reference to it stored >in some table somewhere or is there some magical jiggery-pokery going on >here? A reference to it is stored in a table. Try running /usr/sbin/config on a config file (just the way you start a normal kernel compile) and then going and looking at the stuff it put in the build directory for that kernel. You'll notice it created a bunch of .c and .h files that include tables of devices to probe. cjs -- Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite myst, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly.