Date: Thu, 24 Aug 2000 18:11:42 +0200 From: Graham Wheeler <gram@cequrux.com> To: freebsd-stable@freebsd.org Subject: Requesting input for a handbook section entry Message-ID: <39A5493E.B130936C@cequrux.com>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------069F5FA767340AFAE3E3409F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all Following up on my query on ISA card configuration, I have written up a section for the Handbook on this. It's brief, may have inaccuracies, and certainly has ommisions. I have put comments in upper case enclosed in square braces for the areas that definitely need peer review/completion. Can peeps have a look at this, and send me comments, so that I can complete it and submit it to the doccie folks? Thanks gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 --------------069F5FA767340AFAE3E3409F Content-Type: text/plain; charset=us-ascii; name="config.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="config.txt" Configuring An Already Compiled Kernel If you don't want to create a custom kernel, you can configure many hardware settings without doing so, by putting them in the /boot/kernel.conf file. This file contains a sequence of commands compatible with those that are supported by the kernel configuration editor (which you may have seen when you first installed FreeBSD, and which is also accessible by booting with a `-c' argument). Because the commands in this file are essentially fed to the kernel configuration editor, it is important to have the last command in the file be `q' for `quit'. [IS THE LAST SENTENCE TRUE? READING userconfig.c IT APPEARS THAT AN IMPLICIT QUIT WILL BE DONE IF NO `q' COMMAND IS PRESENT...] The commands that the kernel configuration editor understands are: di(sable) <devicename> Disable device en(able) <devicename> Enable device dr(q) <devicename> <drq> Set DMA channel for device to <drq> ei(sa) <numslots> Set number of EISA slots to probe f(lags) <devicename> <flags> Set the device-specific flags for the device iom(em) <devicename> <address> Sets the base address of the I/O memory ios(ize) <devicename> <size> Sets the size of the I/O memory ir(q) <devicename> <irqnum> Set the IRQ for the device pn(p) <csn> <ldn> enable Enable device pn(p) <csn> <ldn> disable Disable device pn(p) <csn> <ldn> os Set parameters using FreeBSD pn(p) <csn> <ldn> bios Set parameters using BIOS pn(p) <csn> <ldn> portX <addr> Set addr for port X (0..7) pn(p) <csn> <ldn> memX <maddr> Set addr for memory range X (0..3) pn(p) <csn> <ldn> irqX <number> Set irq X (0..1) to number, 0=unused pn(p) <csn> <ldn> drqX <number> Set drq X (0..1) to number, 4=unused po(rt) <devicename> <port> Set the I/O port base address for the device ex Exit (quit) q Quit The commands are shown with their full names, and the optional parts parenthesised. Thus, for example, the "enable" command can be abbreviated to "en". There are other commands, for example to list the devices or reset the CPU, but these only make sense when using the interactive editor, and not when using kernel.conf. <irqnum>, <flags>, <drq>, <address>, <size> are all numeric arguments. They can be either decimal numbers, or hexadecimal numbers (in which case they must be prefixed by "0x"). For Plug 'n' Play devices, <csn> is the slot number and <ldn> the logical device number. [I'M JUST MAKING THIS UP; I HAVEN'T A CLUE REALLY WHAT THESE ARE; SOMEONE PLEASE ENLIGHTEN ME!] Here is a simple example, which sets the interrupt and port for device ed0 to be irq 10, port 0x320: irq ed0 10 port ed0 0x320 q --------------069F5FA767340AFAE3E3409F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39A5493E.B130936C>