Date: Fri, 10 Oct 1997 07:33:26 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: mdean@best.com (mdean) Subject: Re: config questions Message-ID: <19971010073326.WG52815@uriah.heep.sax.de> In-Reply-To: <Pine.SGI.3.95.971009150431.13341A-100000@shellx.best.com>; from mdean on Oct 9, 1997 15:07:36 -0700 References: <Pine.SGI.3.95.971009150431.13341A-100000@shellx.best.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As mdean wrote: > in the kernel config file, what does the modifier after the port number do? > i.e. port 0x250 bio or port 0x250 tty RTFM spl(9) for this. > could > you have it on the same line as the driver like > > ... port 0x250 tty irq 5 vector drivervec goodies 1 > > and get it put in driver.h? No. You can have two things: device foo port 0x250 tty irq 5 vector foovec flags 0x234 ...where the man page for foo(4) is supposed to explain the meaning of the flags values. This is pretty obscure, but on the plus side, you can change the flags on a per-device basis (as opposed to per-driver), and you can change them at boot-time with UserConfig (or /kernel.config). The other option is, well, an `option': options FOOOPT options "FOOZOOLIX=23" ...which will convert into #define FOOOPT 1 #defien FOOZOOLIX 23 but needs a kernel recompilation in order to take effect. The preferable style for options is now to mention all valid options in either /sys/conf/options, or /sys/$arch/conf/options.$arch, so there will be a file named "opt_fooopt.h" etc. in your kernel compile directory with the above #defines. (The old way translated them into -D options in the Makefile, but this loses when it comes to dependencies.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971010073326.WG52815>