Date: Fri, 29 Jan 1999 09:38:46 -0700 From: Nate Williams <nate@mt.sri.com> To: Mike Smith <mike@smith.net.au> Cc: Nate Williams <nate@mt.sri.com>, Michael Smith <msmith@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/boot/common help.common Message-ID: <199901291638.JAA06504@mt.sri.com> In-Reply-To: <199901291632.IAA00932@dingo.cdrom.com> References: <199901290431.VAA03906@mt.sri.com> <199901291632.IAA00932@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > sys/boot/common help.common > > > Log: > > > Document the machdep.pccard.pcic_irq tunable, which allows the user to tune > > > the interrupt which will be given to the PCIC. If the value supplied is > > > illegal or not available, interrupts will be turned off and polled mode > > > used instead. > > > > Cool. How can this be tuned in a config file to give it a default > > setting? > > It can't. Put > > set machdep.pccard.pcic_irq=<value> > > in /boot/loader.rc > > My current philosophy leans towards separating code (the kernel) and > data (the IRQ value). If you desperately wanted to be able to compile > in a default, I would probably look the other way. (Note that you've > argued against using a compile-time option for this previously...) No, I argued *for* a compile-time option that didn't involve making the PCIC an ISA device, or using 'Yet Another' option. Both are unacceptable options. Also, what do we do about those machines that have multiple PCIC's? (There are quite a few...) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901291638.JAA06504>