diff options
Diffstat (limited to 'Documentation')
49 files changed, 4738 insertions, 2340 deletions
diff --git a/Documentation/00-INDEX b/Documentation/00-INDEX index a1d313660..393057142 100644 --- a/Documentation/00-INDEX +++ b/Documentation/00-INDEX @@ -6,6 +6,8 @@ Note that subdirectories have their own index files too. 00-INDEX - this file. +ARM-README + - information for using Linux on the ARM architecture. BUG-HUNTING - brute force method of doing binary search of patches to find bug. Changes @@ -14,10 +16,14 @@ CodingStyle - how the boss likes the C code in the kernel to look. Configure.help - text file that is used for help when you run "make config" +IO-APIC.txt + - info on using the enhanced interrupt hardware on SMP boards. IO-mapping.txt - how to access I/O mapped memory from within device drivers. SMP.txt - notes, and "To Fix" list for multi-processor Linux. (see smp.tex) +VGA-softcursor.txt + - how to change your VGA cursor from a blinking underscore. binfmt_misc.txt - info on the kernel support for extra binary formats. cdrom/ @@ -32,12 +38,12 @@ digiepca.txt - info on Digi Intl. {PC,PCI,EISA}Xx and Xem series cards. exception.txt - how linux v2.1 handles exceptions without verify_area etc. -ez.txt - - documentation for the SyQuest parallel port EZ drive support. filesystems/ - directory with info on the various filesystems that Linux supports. ftape.txt - notes about the floppy tape device driver +hayes-esp.txt + - info on using the Hayes ESP serial driver. ide.txt - important info for users of ATA devices (IDE/EIDE disks and CD-ROMS) initrd.txt @@ -48,30 +54,44 @@ isdn/ - directory with info on the linux ISDN support, and supported cards. java.txt - info on the in-kernel binary support for Java(tm) +joystick.txt + - info on using joystick devices (and driver) with linux. locks.txt - info on file locking implementations, flock() vs. fcntl(), etc. logo.gif - Full colour GIF image of Linux logo (penguin) logo.txt - Info on creator of above logo & site to get additional images from. +m68k/ + - directory with info about Linux on Motorola 68k archtecture. magic-number.txt - list of magic numbers used to mark/protect kernel data structures. mandatory.txt - info on the linux implementation of Sys V mandatory file locking. +md.txt + - info on boot arguments for the multiple devices driver memory.txt - info on typical Linux memory problems. mca.txt - info on supporting Micro Channel Architecture (e.g. PS/2) systems. modules.txt - short guide on how to make kernel parts into loadable modules +nbd.txt + - info on a TCP implementation of a network block device. networking/ - directory with info on various linux networking aspects. nfsroot.txt - short guide on setting up a diskless box with NFS root filesystem oops-tracing.txt - how to decode those nasty internal kernel error dump messages. +pcwd-watchdog.txt + - info and sample code for using with the PC Watchdog reset card. +paride.txt + - information about the parallel port IDE subsystem. parport.txt - how to use the parallel-port driver. +powerpc/ + - directory with info on using linux with the PowerPC. ramdisk.txt - short guide on how to set up and use the RAM disk. riscom8.txt @@ -80,10 +100,22 @@ rtc.txt - notes on how to use the Real Time Clock (aka CMOS clock) driver. scsi.txt - short blurb on using SCSI support as a module. +serial-console.txt + - how to set up linux with a serial line console as the default. +smart-config.txt + - description of the Smart Config makefile feature. smp.tex - TeX document describing implementation of Multiprocessor Linux +specialix.txt + - info on hardware/driver for specialix IO8+ multiport serial card. +spinlocks.txt + - info on using spinlocks to provide exclusive access in kernel. +stallion.txt + - info on using the Stallion multiport serial driver. svga.txt - short guide on selecting video modes at boot via VGA BIOS. +transname.txt + - how to use name translation to ease use of diskless systems. unicode.txt - info on the Unicode character/font mapping used in Linux. watchdog.txt diff --git a/Documentation/ARM-README b/Documentation/ARM-README new file mode 100644 index 000000000..0524ba63e --- /dev/null +++ b/Documentation/ARM-README @@ -0,0 +1,169 @@ + ARM Linux 2.1.78 + ================ + + ** The ARM support contained within is NOT complete - it will not build. ** + ** If you want to build it, then please obtain a full copy of the ARM ** + ** patches from ftp://ftp.arm.uk.linux.org/pub/armlinux/kernel-sources/v2.1 ** + + Since this is a development kernel, it will not be as stable as the 2.0 + series, and can cause very nasty problems (eg, trashing your hard disk). + When running one of these kernels, I advise you to back up the complete + contents of all your hard disks. + +Contributors +------------ + + Here is a list of people actively working on the project (If you + wish to be added to the list, please email me): + + Name: Russell King + Mail: linux@arm.uk.linux.org + Desc: Original developer of ARM Linux, project co-ordinator. + + Name: Dave Gilbert + Mail: linux@treblig.org + Desc: A3/4/5xx floppy and hard disk code maintainer. + + Name: Philip Blundell + Mail: Philip.Blundell@pobox.com + Desc: Architecture and processor selection during make config. + +Todo list +--------- + + This is the list of changes to be done (roughly prioritorised): + + * fully test new A5000 & older MEMC translation code + * fully test new AcornSCSI driver. + * reply to email ;) + +Bugs +---- + + Fixed bugs in this version 2.1.76: + + Modules believed to be buggy (please report your successes/failures): + + * AcornSCSI believed to occasionally corrupt hard drives. + * All NCR5380-based SCSI devices [Cumana I, Oak, EcoSCSI] are slow, + and may not allow write access. + * A5000 and older machine kernel builds may not be as stable as they were. + + Notes + ===== + +Compilation of kernel +--------------------- + + In order to compile ARM Linux, you will need a compiler capable of + generating ARM ELF code with GNU extensions. GCC-2.7.2.2 is good. + + To build ARM Linux natively, you shouldn't have to alter the ARCH = line in + the top level Makefile. However, if you don't have the ARM Linux ELF tools + installed as default, then you should change the CROSS_COMPILE line as + detailed below. + + If you wish to cross-compile, then alter the following lines in the top + level make file: + + ARCH = <whatever> + with + ARCH = arm + + and + + CROSS_COMPILE= + to + CROSS_COMPILE=<your-path-to-your-compiler-without-gcc> + eg. + CROSS_COMPILE=/usr/src/bin/arm/arm-linuxelf- + + Do a 'make config', followed by 'make dep', and finally 'make all' to + build the kernel (vmlinux). A compressed image can be built by doing + a 'make zImage' instead of 'make all'. + +Bug reports etc +--------------- + + Please send patches, bug reports and code for the ARM Linux project + to linux@arm.uk.linux.org. Patches will not be included into future + kernels unless they come to me (or the relevant person concerned). + + When sending bug reports, please ensure that they contain all relevent + information, eg. the kernel messages that were printed before/during + the problem, what you were doing, etc. + + For patches, please include some explaination as to what the patch does + and why (if relevent). + +Modules +------- + + Although modularisation is supported (and required for the FP emulator), + each module on an arm2/arm250/arm3 machine when is loaded will take + memory up to the next 32k boundary due to the size of the pages. Hence is + modularisation on these machines really worth it? + + However, arm6 and up machines allow modules to take multiples of 4k, and + as such Acorn RiscPCs and other architectures using these processors can + make good use of modularisation. + +ADFS Image files +---------------- + + You can access image files on your ADFS partitions by mounting the ADFS + partition, and then using the loopback device driver. You must have + losetup installed. + + Please note that the PCEmulator DOS partitions have a partition table at + the start, and as such, you will have to give '-o offset' to losetup. + +Kernel initialisation abort codes +--------------------------------- + + When the kernel is unable to boot, it will if possible display a colour + at the top of the screen. The colours have the following significance + when run in a 16 colour mode with the default palette: + + Stripes of White,Red,Yellow,Green: + Kernel does not support the processor architecture detected. + +Request to developers +--------------------- + + When writing device drivers which include a separate assember file, please + include it in with the C file, and not the arch/arm/lib directory. This + allows the driver to be compiled as a loadable module without requiring + half the code to be needlessly compiled into the kernel image. + + In general, try to avoid using assembler unless it is really necessary. It + makes drivers far less easy to port to other hardware. + +ST506 hard drives +----------------- + + The ST506 hard drive controllers seem to be working fine (if a little + slowly). At the moment they will only work off the controllers on an + A4x0's motherboard, but for it to work off a Podule just requires + someone with a podule to add the addresses for the IRQ mask and the + HDC base to the source. + + As of 31/3/96 it works with two drives (you should get the ADFS + *configure harddrive set to 2). I've got an internal 20MB and a great + big external 5.25" FH 64MB drive (who could ever want more :-) ). + + I've just got 240K/s off it (a dd with bs=128k); thats about half of what + RiscOS gets; but its a heck of a lot better than the 50K/s I was getting + last week :-) + + Known bug: Drive data errors can cause a hang; including cases where + the controller has fixed the error using ECC. (Possibly ONLY + in that case...hmm). + + +1772 Floppy +----------- + This also seems to work OK, but hasn't been stressed much lately. It + hasn't got any code for disc change detection in there at the moment which + could be a bit of a problem! Suggestions on the correct way to do this + are welcome. diff --git a/Documentation/Changes b/Documentation/Changes index db147780c..6f778a20f 100644 --- a/Documentation/Changes +++ b/Documentation/Changes @@ -14,10 +14,10 @@ functional and running at least 2.0.x. therefore owes credit to the same people as that file (Jared Mauch, Axel Boldt, Alessandro Sigala, and countless other users all over the 'net). Please feel free to submit changes, corrections, gripes, -flames, money, etc. to me (gt1355b@prism.gatech.edu). If you do so, -you don't need to bother doing so in the form of a diff, as this is -generated by texinfo so a diff is useless anyway (though I can -incorporate one by hand if you insist upon sending it that way ;-). +flames, money, etc. to me (kaboom@gatech.edu). If you do so, you don't +need to bother doing so in the form of a diff, as this is generated by +texinfo so a diff is useless anyway (though I can incorporate one by +hand if you insist upon sending it that way ;-). Check out http://www.cviog.uga.edu/Misc/info/LinuxBleed.html for an HTML-ized shopping list. @@ -26,8 +26,14 @@ HTML-ized shopping list. http://www.datanet.hu/generations/linux/Changes2.html is an English-language HTML version. -Last updated: September 13. 1997 -Current Author: Chris Ricker (gt1355b@prism.gatech.edu). + The most current version should always be available from +http://cyberbuzz.gatech.edu/kaboom/linux/ as well. + + Also, don't forget http://www.linuxhq.com/ for all your Linux kernel +needs. + +Last updated: February 16. 1998 +Current Author: Chris Ricker (kaboom@gatech.edu). Current Minimal Requirements **************************** @@ -36,21 +42,24 @@ Current Minimal Requirements encountered a bug! If you're unsure what version you're currently running, the suggested command should tell you. -- Kernel modules modutils-2.1.55 ; insmod -V +- Kernel modules modutils-2.1.85 ; insmod -V - Gnu C 2.7.2.3 ; gcc --version - Binutils 2.8.1.0.1 ; ld -v - Linux C Library 5.4.38 ; ls -l /lib/libc.so.* - Dynamic Linker (ld.so) 1.9.5 ; ldd -v - Linux C++ Library 2.7.2.8 ; ls -l /usr/lib/libg++.so.* -- Procps 1.2 ; ps --version +- Procps 1.2.5 ; ps --version - Procinfo 0.11 ; procinfo -v -- Mount 2.6h ; mount --version +- Mount 2.7l ; mount --version - Net-tools 1.41 ; hostname -V - Loadlin 1.6a - Sh-utils 1.16 ; expr --v -- Autofs 0.3.11 ; automount --version +- Autofs 0.3.11 ; automount --version - NFS 0.4.21 ; showmount --version - Bash 1.14.7 ; bash -version +- Ncpfs 2.1.1 ; ncpmount -v +- Pcmcia-cs 2.9.12 +- PPP 2.3.3 ; pppd -v Upgrade notes ************* @@ -76,7 +85,7 @@ accordingly. For modules to work, you need to be running libc-5.4.x or greater. Since updates to libc fix other problems as well (security flaws, for example) and since 5.4.7 is missing a few needed symbols, try to get -the latest 5.4.x you can. Currently, libc-5.4.38 is the latest public +the latest 5.4.x you can. Currently, libc-5.4.44 is the latest public release. If you upgrade to libc-5.4.x, you also have to upgrade your dynamic @@ -90,10 +99,14 @@ unless you're running glibc2 / libc6. If you upgrade to libc-5.4.x, you may also need to upgrade ypbind if you're using NIS. + If you upgrade to libc-5.4.44, please read and pay attention to its +accompanying release notes. The section about it breaking make is not +a joke. + Modules ======= - You need to upgrade to modutils-2.1.55 for kernels 2.1.55 and later. + You need to upgrade to modutils-2.1.85 for kernels 2.1.85 and later. This version will also work with 2.0.x kernels. Binutils @@ -108,9 +121,13 @@ Gnu C You need at least GCC 2.7.2 to compile the kernel. If you're upgrading from an earlier release, you might as well get GCC 2.7.2.3, -the latest public release. If you already have GCC 2.7.2 on your -system, you don't have to upgrade just so the kernel will work (though -feel free to upgrade if you want the gcc bug fixes). +the latest stable public release. If you already have GCC 2.7.2 on +your system, you don't have to upgrade just so the kernel will work +(though feel free to upgrade if you want the gcc bug fixes). + + Note that the latest compilers (egcs, pgcc, gcc 2.8) may do Bad +Things while compiling your kernel, particularly if absurd +optimizations (like -O9) are used. Caveat emptor. Networking Changes ================== @@ -190,18 +207,13 @@ parallel port may no longer be where you expect it; for example, LPT1 /dev/lp0 with the new Plug-and-Play driver. If printing breaks with the new driver, try checking your lpd configuration. -pppd -==== -This kernel version needs a minor bugfix to pppd. See -Documentation/networking/ppp.txt for more information. - Syncookies ========== -When you build your kernel with Syncookie support (CONFIG_SYN_COOKIES) -the syncookie code still defaults to off (unlike the 2.0.30+ behaviour). -You have to explicitely enable it by add a line like -echo 1 >/proc/sys/net/ipv4/tcp_syncookies -to one of your startup scripts (e.g. /etc/rc.d/rc.local on a redhat system) + + When you build your kernel with Syncookie support +(CONFIG_SYN_COOKIES) the syncookie code still defaults to off (unlike +the 2.0.30+ behavior). You have to explicitly enable it by issuing the +following command: echo 1 > /proc/sys/net/ipv4/tcp_syncookies Bash ==== @@ -210,6 +222,24 @@ Bash cause problems when compiling modules. Upgrade to at least 1.14 to fix this problem. +Ncpfs +===== + + To mount NetWare shares, you'll need to upgrade to a more recent +version of the ncpfs utils. + +Pcmcia-cs +========= + + If you use pcmcia cards, you'll need to upgrade the daemon and +support utils to the latest release of pcmcia-cs. + +PPP +=== + + Due to changes in the routing code, those of you using PPP +networking will need to upgrade your pppd. + Where to get the files ********************** @@ -263,16 +293,16 @@ ftp://sunsite.unc.edu/pub/Linux/GCC/ld.so-1.9.5.tar.gz Modules utilities ================= -The 2.1.55 release: -ftp://ftp.redhat.com/pub/alphabits/modutils/modutils-2.1.55.tar.gz -ftp://ftp.kernel.org/pub/linux/kernel/v2.1/modutils-2.1.55.tar.gz +The 2.1.85 release: +ftp://ftp.redhat.com/pub/alphabits/modutils/modutils-2.1.85.tar.gz +ftp://ftp.kernel.org/pub/linux/kernel/v2.1/modutils-2.1.85.tar.gz Procps utilities ================ The 1.2 release: -ftp://tsx-11.mit.edu/pub/linux/sources/usr.bin/procps-1.2.tar.gz -ftp://sunsite.unc.edu/pub/Linux/system/status/ps/procps-1.2.tgz +ftp://tsx-11.mit.edu/pub/linux/sources/usr.bin/procps-1.2.5.tar.gz +ftp://sunsite.unc.edu/pub/Linux/system/status/ps/procps-1.2.5.tgz Procinfo utilities ================== @@ -317,8 +347,8 @@ ftp://prep.ai.mit.edu/pub/gnu/sh-utils-1.16.tar.gz Mount ===== -The 2.6h release: -ftp://ftp.win.tue.nl/pub/linux/util/mount-2.6h.tar.gz +The 2.7l release: +ftp://ftp.win.tue.nl/pub/linux/util/mount/mount-2.7l.tar.gz Autofs ====== @@ -336,9 +366,8 @@ ftp://linux.nrao.edu/pub/people/okir/linux-nfs-0.4.21.tar.gz Net-tools ========= -The 1.41 release: -ftp://ftp.london.uk.eu.org/pub/ipv6/net-tools-1.41.tar.gz -ftp://ftp.cs-ipv6.lancs.ac.uk/pub/Code/Linux/Net_Tools/net-tools-1.41.tar.gz +The 1.432 release: +ftp://ftp.cs-ipv6.lancs.ac.uk/pub/Code/Linux/Net_Tools/net-tools-1.432.tar.gz Ypbind ====== @@ -352,6 +381,25 @@ Bash The 1.14.7 release: ftp://prep.ai.mit.edu/pub/gnu/bash-1.14.7.tar.gz +Ncpfs +===== + +The 2.1.1 release: +ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/ncpfs-2.1.1.tgz +ftp://sunsite.unc.edu/pub/Linux/system/Filesystems/ncpfs/ncpfs-2.1.1.tgz + +Pcmcia-cs +========= + +The 1.9.12 release: +ftp://hyper.stanford.edu/pub/pcmcia/pcmcia-cs-2.9.12.tar.gz + +PPP +=== + +The 2.3.3 release: +ftp://cs.anu.edu.au/pub/software/ppp/ppp-2.3.3.tar.gz + Other Info ========== @@ -380,5 +428,5 @@ more information and the files. Please send info about any other packages that 2.1.x "broke" or about any new features of 2.1.x that require extra or new packages for use to -Chris Ricker (gt1355b@prism.gatech.edu). +Chris Ricker (kaboom@gatech.edu). diff --git a/Documentation/Configure.help b/Documentation/Configure.help index 85320397e..daea952c7 100644 --- a/Documentation/Configure.help +++ b/Documentation/Configure.help @@ -1,4 +1,4 @@ -# Maintained by Axel Boldt (boldt@math.ucsb.edu) +# Maintained by Axel Boldt (boldt@math.ucsb.edu) # # This version of the Linux kernel configuration help texts # corresponds to the kernel versions 2.1.x. Be aware that these are @@ -18,6 +18,9 @@ # is a work-in-progress effort of the Italian translation team, # currently only for the 2.0 version of this file, maintained # by rubini@linux.it. +# - http://www.cs.net.pl/~cezar/Kernel is the beginning of a Polish +# translation of the 2.0 version of this file, maintained by Cezar +# Cichocki (cezar@cs.net.pl). # # Information about what a kernel is, what it does, how to patch and # compile it and much more is contained in the Kernel-HOWTO, available @@ -112,7 +115,7 @@ CONFIG_BLK_DEV_FD running kernel whenever you want). The module will be called floppy.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. - + RAM disk support CONFIG_BLK_DEV_RAM Saying Y here will allow you to use a portion of your RAM memory as @@ -150,12 +153,18 @@ CONFIG_BLK_DEV_LOOP Network Block Device support CONFIG_BLK_DEV_NBD - Saying Y here will allow computer to serve as client for network - block device - it will be able to use block devices exported by - servers (mount filesystems on them etc.). It also allows you to run - a block-device in userland (making server and client physicaly the same - computer, communicating using loopback). Normal users say N - here. Read Documentation/nbd.txt. + Saying Y here will allow your computer to serve as a client for + network block devices - it will be able to use block devices + exported by servers (mount filesystems on them etc.). Communication + between client and server works over TCP/IP networking, but to the + client program this is hidden: it looks like a regular local file + access to a special file such as /dev/nd0. It also allows you to run + a block-device in userland (making server and client physically the + same computer, communicating using loopback). If you want to compile + this driver as a module ( = code which can be inserted in and + removed from the running kernel whenever you want), say M here and + read Documentation/modules.txt. The module will be called + nbd.o. Normal users say N here. Read Documentation/nbd.txt. Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support CONFIG_BLK_DEV_IDE @@ -163,11 +172,11 @@ CONFIG_BLK_DEV_IDE interfaces, each being able to serve a "master" and a "slave" device, for a combination of up to eight IDE disk/cdrom/tape/floppy drives. Useful information about large (>540MB) IDE disks, - soundcard IDE ports, module support, and other topics, is all + soundcard IDE ports, module support, and other topics, is contained in Documentation/ide.txt. If you have one or more IDE drives, say Y here. If your system has no IDE drives, or if memory requirements are really tight, you could say N here, and select the - Old harddisk driver instead to save about 13kB of memory in the + "Old harddisk driver" instead to save about 13kB of memory in the kernel. To fine-tune IDE drive/interface parameters for improved performance, look for the hdparm package at sunsite.unc.edu:/pub/Linux/kernel/patches/diskdrives/ @@ -248,18 +257,18 @@ CONFIG_BLK_DEV_IDETAPE Include IDE/ATAPI FLOPPY support CONFIG_BLK_DEV_IDEFLOPPY - If you have an IDE floppy drive which uses the ATAPI protocol, say Y. - ATAPI is a new protocol used by IDE CDROM/tape/floppy drives, - similar to the SCSI protocol. IDE floppy drives include the - LS-120 and the ATAPI ZIP (ATAPI PD-CD/CDR drives are not supported - by this driver; support for PD-CD/CDR drives is available through - the SCSI emulation). At boot time, the FLOPPY drive will be - identified along with other IDE devices, as "hdb" or "hdc", or - something similar. If you want to compile the driver as a module ( = - code which can be inserted in and removed from the running kernel - whenever you want), say M here and read Documentation/modules.txt. - The module will be called ide-floppy.o. - + If you have an IDE floppy drive which uses the ATAPI protocol, say + Y. ATAPI is a new protocol used by IDE CDROM/tape/floppy drives, + similar to the SCSI protocol. IDE floppy drives include the LS-120 + and the ATAPI ZIP (ATAPI PD-CD/CDR drives are not supported by this + driver; support for PD-CD/CDR drives is available through the SCSI + emulation). At boot time, the FLOPPY drive will be identified along + with other IDE devices, as "hdb" or "hdc", or something similar. If + you want to compile the driver as a module ( = code which can be + inserted in and removed from the running kernel whenever you want), + say M here and read Documentation/modules.txt. The module will be + called ide-floppy.o. + SCSI emulation support CONFIG_BLK_DEV_IDESCSI This will provide SCSI host adapter emulation for IDE ATAPI devices, @@ -316,8 +325,8 @@ CONFIG_BLK_DEV_IDEPCI Generic PCI bus-master DMA support CONFIG_BLK_DEV_IDEDMA If your PCI IDE controller is capable of bus-master DMA - (Direct Memory Access) transfers (most newer systems), - then you will want to enable this option to reduce CPU overhead. + (Direct Memory Access) transfers (most newer systems are), + then you will want to say Y here to reduce CPU overhead. With this option, Linux will automatically enable DMA transfers in most cases, noting this with "DMA" appended to the drive identification info. You can also use the "hdparm" utility to @@ -341,8 +350,9 @@ CONFIG_BLK_DEV_4DRIVES Certain older chipsets, including the Tekram 690CD, use a single set of I/O ports at 0x1f0 to control up to four drives, instead of the customary two drives per port. Support for this - is enabled at runtime using the "ide0=four" kernel boot parameter. - + can be enabled at runtime using the "ide0=four" kernel boot + parameter if you say Y here. + DTC-2278 support CONFIG_BLK_DEV_DTC2278 This driver is enabled at runtime using the "ide0=dtc2278" kernel @@ -368,17 +378,15 @@ CONFIG_BLK_DEV_PDC4030 "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt and drivers/block/pdc4030.c files for more info. -Tekram TRM290 support (EXPERIMENTAL) CONFIG_BLK_DEV_TRM290 This driver adds support for bus master DMA transfers using the Tekram TRM290 PCI IDE chip. Volunteers are needed for further tweaking and development. Please read the comments at the top of drivers/block/trm290.c. -OPTi 82C621 support (EXPERIMENTAL) +OPTi 82C621 enhanced support (EXPERIMENTAL) CONFIG_BLK_DEV_OPTI621 - This driver allows use of hdparm to change the PIO timings - for drives attached to an OPTi MIDE controller. + This is a driver for the OPTi 82C621 EIDE controller. Please read the comments at the top of drivers/block/opti621.c. NS87415 support (EXPERIMENTAL) @@ -417,22 +425,177 @@ CONFIG_BLK_DEV_XD Documentation/modules.txt. The module will be called xd.o. It's pretty unlikely that you have one of these: say N. -SyQuest EZ parallel port disk support -CONFIG_BLK_DEV_EZ - If you have a parallel port version of SyQuest's EZ135 or EZ230 - removable media devices you can use this driver. Answer Y to build - the driver into the kernel, or M if you would like to build it as a - loadable module. The module will be called ez.o. Read the file - linux/Documentation/ez.txt. It is possible to use several devices - with a single common parallel port (e.g. printer and EZ135); it is - safe to compile both drivers into the kernel. +Parallel port IDE device support +CONFIG_PARIDE + There are many external CD-ROM and disk devices that connect + through your computer's parallel port. Most of them are actually + IDE devices using a parallel port IDE adapter. This option enables + the PARIDE subsystem which contains drivers for many of these + external drives. Read linux/Documentation/paride.txt for more + information. If you have enabled the parallel port support general + configuration option, you may share a single port between your + printer and other parallel port devices. Answer Y to build PARIDE + support into your kernel, or M if you would like to build it as a + loadable module. If your parallel port support is in a loadable + module, you must build PARIDE as a module. If you built PARIDE + support into your kernel, you may still build the individual + protocol modules and high-level drivers as loadable modules. To + use the PARIDE support, you must have this module as well as at + least one protocol module and one high-level driver. If you build + this support as a module, it will be called paride.o. + +Parallel port IDE disks +CONFIG_PARIDE_PD + This option enables the high-level driver for IDE-type disk devices + connected through a parallel port. If you chose to build PARIDE + support into your kernel, you may answer Y here to build in the + parallel port IDE driver, otherwise you should answer M to build + it as a loadable module. The module will be called pd.o. You + must also have at least one parallel port protocol driver in your + system. Among the devices supported by this driver are the SyQuest + EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack + hardrives from MicroSolutions. + +Parallel port ATAPI CD-ROMs +CONFIG_PARIDE_PCD + This option enables the high-level driver for ATAPI CD-ROM devices + connected through a parallel port. If you chose to build PARIDE + support into your kernel, you may answer Y here to build in the + parallel port ATAPI CD-ROM driver, otherwise you should answer M + to build it as a loadable module. The module will be called pcd.o. + You must also have at least one parallel port protocol driver in + your system. Among the devices supported by this driver are the + MicroSolutions backpack CD-ROM drives and the Freecom Power CD. + +Parallel port ATAPI disks +CONFIG_PARIDE_PF + This option enable the high-level driver for ATAPI disk devices + connected through a parallel port. If you chose to build PARIDE + support into your kernel, you may answer Y here to build in the + parallel port ATAPI disk driver, otherwise you should answer M + to build it as a loadable module. The module will be called pf.o. + You must also have at least one parallel port protocol driver in + your system. Among the devices supported by this driver are the + MicroSolutions backpack PD/CD drive and the Imation Superdisk + LS-120 drive. + +Parallel port ATAPI tapes +CONFIG_PARIDE_PT + This option enable the high-level driver for ATAPI tape devices + connected through a parallel port. If you chose to build PARIDE + support into your kernel, you may answer Y here to build in the + parallel port ATAPI disk driver, otherwise you should answer M + to build it as a loadable module. The module will be called pt.o. + You must also have at least one parallel port protocol driver in + your system. Among the devices supported by this driver is the + parallel port version of the HP 5GB drive. + +ATEN EH-100 protocol +CONFIG_PARIDE_ATEN + This option enables support for the ATEN EH-100 parallel port IDE + protocol. This protocol is used in some inexpensive low performance + parallel port kits made in Hong Kong. If you chose to build PARIDE + support into your kernel, you may answer Y here to build in the + protocol driver, otherwise you should answer M to build it as a + loadable module. The module will be called aten.o. You must also + have a high-level driver for the type of device that you want to + support. + +MicroSolutions backpack protocol +CONFIG_PARIDE_BPCK + This option enables support for the MicroSolutions backpack + parallel port IDE protocol. If you chose to build PARIDE support + into your kernel, you may answer Y here to build in the protocol + driver, otherwise you should answer M to build it as a loadable + module. The module will be called bpck.o. You must also have + a high-level driver for the type of device that you want to support. + +DataStor Commuter protocol +CONFIG_PARIDE_COMM + This option enables support for the Commuter parallel port IDE + protocol from DataStor. If you chose to build PARIDE support + into your kernel, you may answer Y here to build in the protocol + driver, otherwise you should answer M to build it as a loadable + module. The module will be called comm.o. You must also have + a high-level driver for the type of device that you want to support. + +DataStor EP-2000 protocol +CONFIG_PARIDE_DSTR + This option enables support for the EP-2000 parallel port IDE + protocol from DataStor. If you chose to build PARIDE support + into your kernel, you may answer Y here to build in the protocol + driver, otherwise you should answer M to build it as a loadable + module. The module will be called dstr.o. You must also have + a high-level driver for the type of device that you want to support. + +Shuttle EPAT/EPEZ protocol +CONFIG_PARIDE_EPAT + This option enables support for the EPAT parallel port IDE + protocol. EPAT is a parallel port IDE adapter manufactured by + Shuttle Technology and widely used in devices from major vendors + such as Hewlett-Packard, SyQuest, Imation and Avatar. If you + chose to build PARIDE support into your kernel, you may answer Y + here to build in the protocol driver, otherwise you should answer M + to build it as a loadable module. The module will be called epat.o. + You must also have a high-level driver for the type of device that + you want to support. + +Shuttle EPIA protocol +CONFIG_PARIDE_EPIA + This option enables support for the (obsolete) EPIA parallel port + IDE protocol from Shuttle Technology. This adapter can still be found + in some no-name kits. If you chose to build PARIDE support into your + kernel, you may answer Y here to build in the protocol driver, + otherwise you should answer M to build it as a loadable module. + The module will be called epia.o. You must also have a high-level + driver for the type of device that you want to support. + +FreeCom power protocol +CONFIG_PARIDE_FRPW + This option enables support for the Freecom power parallel port IDE + protocol. If you chose to build PARIDE support into your kernel, you + may answer Y here to build in the protocol driver, otherwise you + should answer M to build it as a loadable module. The module will be + called frpw.o. You must also have a high-level driver for the type + of device that you want to support. + +KingByte KBIC-951A/971A protocols +CONFIG_PARIDE_KBIC + This option enables support for the KBIC-951A and KBIC-971A parallel + port IDE protocols from KingByte Information Corp. KingByte's adapters + appear in many no-name portable disk and CD-ROM products, especially + in Europe. If you chose to build PARIDE support into your kernel, you + may answer Y here to build in the protocol driver, otherwise you should + answer M to build it as a loadable module. The module will be called + kbic.o. You must also have a high-level driver for the type of device + that you want to support. + +OnSpec 90c20 protocol +CONFIG_PARIDE_ON20 + This option enables support for the (obsolete) 90c20 parallel port + IDE protocol from OnSpec (often marketted under the ValuStore brand + name). If you chose to build PARIDE support into your kernel, you + may answer Y here to build in the protocol driver, otherwise you + should answer M to build it as a loadable module. The module will + be called on20.o. You must also have a high-level driver for the + type of device that you want to support. + +OnSpec 90c26 protocol +CONFIG_PARIDE_ON26 + This option enables support for the 90c26 parallel port IDE protocol + from OnSpec Electronics (often marketted under the ValuStore brand + name). If you chose to build PARIDE support into your kernel, you + may answer Y here to build in the protocol driver, otherwise you + should answer M to build it as a loadable module. The module will + be called on26.o. You must also have a high-level driver for the + type of device that you want to support. Multiple devices driver support CONFIG_BLK_DEV_MD This driver lets you combine several harddisk partitions into one logical block device. Information about how and why to use it and the necessary tools are available over ftp (user: anonymous) from - sweet-smoke.ufr-info-p7.ibp.fr/pub/public/Linux in the md package + sweet-smoke.ufr-info-p7.ibp.fr/pub/Linux in the md package and the md-FAQ. Please read drivers/block/README.md. If unsure, say N. @@ -483,13 +646,23 @@ CONFIG_MD_MIRRORING A RAID-1 set consists of several disk drives which are exact copies of each other. In the event of a mirror failure, the RAID driver will continue to use the operational mirrors in the set, providing - an error free MD device to the higher levels of the kernel. In - a set with N drives, the available space is the capacity of a single - drive, and the set protects against a failure of (N - 1) drives. - raidtools, a set of user-space tools which create and maintain - RAID1/4/5 sets, is available at: + an error free MD (multiple device) to the higher levels of the + kernel. In a set with N drives, the available space is the capacity + of a single drive, and the set protects against a failure of (N - 1) + drives. raidtools, a set of user-space tools which create and + maintain RAID1/4/5 sets, is available at: ftp://ftp.kernel.org/pub/linux/daemons/raid http://luthien.nuclecu.unam.mx/~miguel/raid + If you want to use such a RAID-1 set say Y. This code is also + available as a module called raid1.o ( = code which can be inserted + in and removed from the running kernel whenever you want). If you + want to compile it as a module, say M here and read + Documentation/modules.txt. If unsure, say Y. + +Boot support (linear, striped) +CONFIG_MD_BOOT + To boot with an initial linear or striped md device you have to + select this. For lilo and loadlin options see Documentation/md.txt. RAID-4/RAID-5 mode CONFIG_MD_RAID5 @@ -498,12 +671,17 @@ CONFIG_MD_RAID5 of a single drive. For a given sector (row) number, (N - 1) drives contain data sectors, and one drive contains the parity protection. For a RAID-4 set, the parity blocks are present on a single drive, - while a RAID-5 set distributes the parity accross the drives in one + while a RAID-5 set distributes the parity across the drives in one of the available parity distribution methods. raidtools, a set of user-space tools which create and maintain RAID1/4/5 sets, is available at: ftp://ftp.kernel.org/pub/linux/daemons/raid http://luthien.nuclecu.unam.mx/~miguel/raid + If you want to use such a RAID-5 set, say Y. This code is also + available as a module called raid5.o ( = code which can be inserted + in and removed from the running kernel whenever you want). If you + want to compile it as a module, say M here and read + Documentation/modules.txt. If unsure, say Y. Support for Mips Magnum 4000 CONFIG_MIPS_MAGNUM_4000 @@ -554,30 +732,30 @@ CONFIG_NET kernel, you should consider updating your networking tools too because changes in the kernel and the tools often go hand in hand; see http://www.inka.de/sites/lina/linux/NetTools/index_en.html for - details. - -Packet socket -CONFIG_PACKET - Packet protocol is used by applications directly communicating - to network devices f.e. tcpdump. You want them to work, choose Y. - If you run kerneld, you might want to choose M. - -Kernel/User netlink socket -CONFIG_NETLINK - This protocol family is used for bi-directional communication - between kernel and user level daemons. This option is unlikely to - be useful for common workstation, but if you configure router or - firewall, do not hesitate: press Y. - -Routing messages -CONFIG_RTNETLINK - One of netlink protocols used by kernel routing engine. - You will need it to use advanced routing features. - -Netlink device emulation -CONFIG_NETLINK_DEV - It is backward compatibility option, choose Y for now. - This option will be removed soon. + details. + +Fast switching (read help!) +CONFIG_NET_FASTROUTE + Enable direct NIC-to-NIC data transfers. + *** This option is NOT COMPATIBLE with several important *** + *** networking options: especially CONFIG*FIREWALL. *** + However, it will work with all options in CONFIG_IP_ADVANCED_ROUTER + section (except for CONFIG_IP_ROUTE_TOS). At the moment few of devices + supports it (tulip is one of them, modified 8390 can be found at + ftp://ftp.inr.ac.ru/ip-routing/fastroute-8390.tar.gz). + Remember, short cuts make long delays :-), say N. + +Forwarding between high speed interfaces +CONFIG_NET_HW_FLOWCONTROL + This option enables NIC hardware throttling during periods of + extremal congestion. At the moment only couple of device drivers + support it (really, one --- tulip, modified 8390 can be found + at ftp://ftp.inr.ac.ru/ip-routing/fastroute-8390.tar.gz). + Really, this option is applicable to any machine attached + to enough fast network, and even 10Mb NIC + is able to kill not very slow box, sort of 120MHz Pentium. + However, do not enable this option, if you did not experienced + any serious problems. Network aliasing CONFIG_NET_ALIAS @@ -594,6 +772,14 @@ CONFIG_NET_ALIAS info. If you need this feature (for any protocol, like IP) say Y; if unsure, say N. +Socket filtering +CONFIG_FILTER + The Linux Socket Filter is derived from the Berkeley Packet Filter. + Through Socket Filtering you can have the kernel decide whether the + data is good and to continue processing it. Linux Socket Filtering + works on all socket types except TCP for now. See the text file + linux/Documentation/networking/filter.txt for more information. + Network firewalls CONFIG_FIREWALL A firewall is a computer which protects a local network from the @@ -627,7 +813,7 @@ CONFIG_SYN_COOKIES to continue to connect, even when your machine is under attack. There is no need for the legitimate users to change their TCP/IP software; SYN cookies work transparently to them. For technical - information about syn cookies, check out + information about SYN cookies, check out ftp://koobera.math.uic.edu/pub/docs/syncookies-archive. If you say Y here, note that SYN cookies aren't enabled by default: you need to add the command @@ -636,17 +822,6 @@ CONFIG_SYN_COOKIES /etc/rc.d/rc.local) in addition. If unsure, say Y. -Socket Security API Support (EXPERIMENTAL) -CONFIG_NET_SECURITY - Enable use of the socket security API. This option only really - supports security (via encryption of all traffic) over IPv4 links, - and then only if you add a security protocol which is also supported - at the other end of the link; Linux itself does not include any - security protocols, but you can use the enskip package at - ftp.tik.ee.ethz.ch/pub/packages/skip/. That package also contains - documentation of the API to be used for secure sockets. If unsure, - say N. - Sun floppy controller support CONFIG_BLK_DEV_SUNFD This is support for floppy drives on Sun Sparc workstations. Say Y @@ -795,11 +970,12 @@ CONFIG_PCI PCI BIOS support CONFIG_PCI_BIOS - If you have enabled PCI bus support above, you probably want to allow - Linux to use your PCI BIOS to detect the PCI devices and determine - their configuration. Note: some old PCI motherboards have BIOS bugs - and may crash if this switch is enabled -- for such motherboards, - you should disable PCI BIOS support and use direct PCI access instead. + If you have enabled PCI bus support above, you probably want to + allow Linux to use your PCI BIOS to detect the PCI devices and + determine their configuration. Note: some old PCI motherboards have + BIOS bugs and may crash if this switch is enabled -- for such + motherboards, you should say N here and say Y to "PCI direct access + support" instead. Except for some special cases (embedded systems with no BIOS), you probably should say Y here. @@ -815,9 +991,9 @@ CONFIG_PCI_DIRECT PCI bridge optimization (experimental) CONFIG_PCI_OPTIMIZE This can improve access times for some hardware devices if you have - a really broken BIOS and your computer uses a PCI bus system. Set to Y - if you think it might help, but try turning it off if you experience - any problems with the PCI bus. + a really broken BIOS and your computer uses a PCI bus system. Set to + Y if you think it might help, but try turning it off if you + experience any problems with the PCI bus. N is the safe answer. MCA support CONFIG_MCA @@ -870,7 +1046,7 @@ CONFIG_BINFMT_ELF http://www.sjc.ox.ac.uk/users/barlow/elf-howto.html (To browse the WWW, you need to have access to a machine on the Internet that has a programs like lynx or netscape). If you find that after upgrading - to Linux kernel 1.3 and saying Y here, you still can't run any ELF + from Linux kernel 1.2 and saying Y here, you still can't run any ELF binaries (they just crash), then you'll have to install the newest ELF runtime libraries, including ld.so (check the file Documentation/Changes for location and latest version). If you want @@ -900,18 +1076,45 @@ CONFIG_BINFMT_AOUT because some crucial programs on your system might still be in A.OUT format. -Kernel support for JAVA binaries +Kernel support for JAVA binaries (obsolete) CONFIG_BINFMT_JAVA - This option is obsolete. Use binfmt_misc instead. It is more - flexible. + JAVA(tm) is an object oriented programming language developed by + SUN; JAVA programs are compiled into "JAVA bytecode" binaries which + can then be interpreted by run time systems on many different + operating systems. These JAVA binaries are becoming a universal + executable format. If you want to execute JAVA binaries, read the + Java on Linux HOWTO, available via ftp (user: anonymous) at + sunsite.unc.edu:/pub/Linux/docs/HOWTO. You will then need to install + the run time system contained in the Java Developers Kit (JDK) as + described in the HOWTO. This is completely independent of the Linux + kernel and you do NOT need to say Y here for this to work. + Saying Y here allows you to execute a JAVA bytecode binary just like + any other Linux program: by simply typing in its name. (You also + need to have the JDK installed for this to work). As more and more + Java programs become available, the use for this will gradually + increase. You can even execute HTML files containing JAVA applets (= + JAVA binaries) if those files start with the string + "<!--applet-->". If you want to use this, say Y here and read + Documentation/java.txt. If you disable this option it will reduce + your kernel by about 4kB. This is not much and by itself does not + warrant removing support. However its removal is a good idea if you + do not have the JDK installed. You may answer M for module support + and later load the module when you install the JDK or find an + interesting Java program that you can't live without. The module + will be called binfmt_java.o. + The complete functionality of this Java support is also provided by + the more general option "Kernel support for MISC binaries", + below. This option is therefore considered obsolete and you probably + want to say N here and Y to "Kernel support for MISC binaries" if + you're interested in Java. Kernel support for Linux/Intel ELF binaries CONFIG_BINFMT_EM86 Say Y here if you want to be able to execute Linux/Intel ELF - binaries just like native Alpha binaries on your machine. For this - to work, you need to have the emulator /usr/bin/em86 in place. You - may answer M to compile the emulation support as a module and later - load the module when you want to use a Linux/Intel binary. The + binaries just like native Alpha binaries on your Alpha machine. For + this to work, you need to have the emulator /usr/bin/em86 in place. + You may answer M to compile the emulation support as a module and + later load the module when you want to use a Linux/Intel binary. The module will be called binfmt_em86.o. If unsure, say Y. Kernel support for MISC binaries @@ -933,6 +1136,15 @@ CONFIG_BINFMT_MISC you have use for it. If you don't know what to answer at this point, say Y. +Solaris binary emulation +CONFIG_SOLARIS_EMUL + This is experimental code which will enable you to run (many) + Solaris binaries on your Sparc Linux machine. This code is also + available as a module ( = code which can be inserted in and removed + from the running kernel whenever you want). The module will be + called solaris.o. If you want to compile it as a module, say M here + and read Documentation/modules.txt. + Processor family CONFIG_M386 This is the processor type of your CPU. This information is used for @@ -942,7 +1154,11 @@ CONFIG_M386 then the kernel will run on all of these CPUs: 486 and Pentium (=586) and Pentium Pro (=686). In rare cases, it can make sense to specify "Pentium" even if running on a 486: the kernel will be - smaller but slower. If you don't know what to do, say "386". + smaller but slower. + If you have a multiple processor machine and want Linux to use all + the processors in parallel, set the SMP variable in the toplevel + kernel Makefile. + If you don't know what to do, say "386". Video mode selection support CONFIG_VIDEO_SELECT @@ -964,23 +1180,40 @@ CONFIG_PARPORT If you want to use devices connected to your parallel port (the connector at the computers with 25 holes), e.g. printer, Zip drive, PLIP link etc., then you need to enable this option; please read - Documentation/parport.txt and drivers/misc/BUGS-parport. It - is possible to share a single parallel port among several devices - and it is safe to compile all the corresponding drivers into the - kernel. If you want to compile parallel port support as a module ( = - code which can be inserted in and removed from the running kernel - whenever you want), say M here and read - Documentation/modules.txt. The module will be called parport.o. If - you have more than one parallel port and want to specify which port - and IRQ to use by this driver at module load time, read - Documentation/networking/net-modules.txt. + Documentation/parport.txt and drivers/misc/BUGS-parport. For + extensive information about drivers for many devices attaching to + the parallel port see http://www.torque.net/linux-pp.html on the WWW + (To browse the WWW, you need to have access to a machine on the + Internet that has a programs like lynx or netscape). It is possible + to share a single parallel port among several devices and it is safe + to compile all the corresponding drivers into the kernel. If you + want to compile parallel port support as a module ( = code which can + be inserted in and removed from the running kernel whenever you + want), say M here and read Documentation/modules.txt. The module + will be called parport.o. If you have more than one parallel port + and want to specify which port and IRQ to use by this driver at + module load time, read Documentation/networking/net-modules.txt. PC-style hardware CONFIG_PARPORT_PC You should enable this option if you have a PC-style parallel port. All IBM PC compatible computers and some Alphas have PC-style - parallel ports. This driver is also available as a module which - will be called parport_pc.o. + parallel ports. This code is also available as a module. If you + want to it as a module ( = code which can be inserted in and removed + from the running kernel whenever you want), say M here and read + Documentation/modules.txt. The module will be called parport_pc.o. + +Sun Ultra/AX-style hardware +CONFIG_PARPORT_AX + Say Y here if you need support for the parallel port hardware on Sun + Ultra/AX machines. This code is also available as a module (say M), + called parport_ax.o. If in doubt, saying N is the safe plan. + +Foreign parallel hardware +CONFIG_PARPORT_OTHER + Say Y here if you want to be able to load driver modules to support + other types of parallel port. This causes a performance loss, so most + people say N. Compile the kernel into the ELF object format CONFIG_ELF_KERNEL @@ -1016,9 +1249,9 @@ CONFIG_PNP Auto-probe for parallel devices CONFIG_PNP_PARPORT - Some IEEE-1284 conformant parallel-port devices can identify themselves - when requested. If this option is enabled the kernel will probe to see - what devices are connected at boot time. + Some IEEE-1284 conformant parallel-port devices can identify + themselves when requested. Say Y to enable this feature, or M to + compile it as a module (parport_ieee1284.o). If in doubt, say N. Plug and Play subsystem (EXPERIMENTAL) CONFIG_PNP_DRV @@ -1051,7 +1284,7 @@ CONFIG_PNP_ISA Plug and Play ISA devices. This includes full support for PnP ISA, including the I/O range check feature. -PnP ISA backwards-compatiblity support +PnP ISA backwards-compatibility support CONFIG_PNP_ISA_COMPAT This option will enable partial backwards compatibility with drivers written using older versions (up to the last 0.2.x) of the PnP driver @@ -1064,18 +1297,18 @@ CONFIG_PNP_LEGACY These cards used somewhat proprietary mechanisms for configuring IRQs, DMAs, IO addresses, and memory ranges. These devices (mainly network cards, but also some sound card) can be configured as any - other PnP device can by enabling this option, if appropriate drivers + other PnP device can by saying Y here, if appropriate drivers for these devices are available. PnP sysctl support (RECOMMENDED) CONFIG_PNP_SYSCTL This option enables support for the user-mode interface to the - kernel-mode PnP systems. It requires that you enable CONFIG_SYSCTL. - The only reason you might want to switch this off is if you aren't - going to use user-mode utilities to configure PnP, and you want to - save a couple of kilobytes of kernel space. Answer Y unless you know - what you are doing. User-mode utilities and a library for accessing - this interface may be found at + kernel-mode PnP systems. It requires that you said Y to "Sysctl + support" above. The only reason you might want to switch this off + is if you aren't going to use user-mode utilities to configure PnP, + and you want to save a couple of kilobytes of kernel space. Answer Y + unless you know what you are doing. User-mode utilities and a + library for accessing this interface may be found at http://www.lpsg.demon.co.uk/pnp-linux.html. PnP auto-configures all devices on startup @@ -1102,10 +1335,10 @@ CONFIG_MODVERSIONS kernel. Saying Y here makes it possible, and safe, to use the same modules even after compiling a new kernel; this requires the program modprobe. All the software needed for module support is in - the modules package (check the file Documentation/Changes for + the modutils package (check the file Documentation/Changes for location and latest version). NOTE: if you say Y here but don't have the program genksyms (which is also contained in the above - mentioned modules package), then the building of your kernel will + mentioned modutils package), then the building of your kernel will fail. If you are going to use modules that are generated from non-kernel sources, you would benefit from this option. Otherwise it's not that important. So, N ought to be a safe bet. @@ -1120,7 +1353,7 @@ CONFIG_KERNELD "kerneld" will also automatically unload all unused modules, so you don't have to use "rmmod" either. kerneld will also provide support for different user-level beeper and screen blanker programs later - on. The "kerneld" daemon is included in the modules package (check + on. The "kerneld" daemon is included in the modutils package (check Documentation/Changes for latest version and location). You will probably want to read the kerneld mini-HOWTO, available via ftp (user: anonymous) from @@ -1170,17 +1403,80 @@ CONFIG_IP_MULTICAST you need to have access to a machine on the Internet that has a program like lynx or netscape). Information about the multicast capabilities of the various network cards is contained in - drivers/net/README.multicast. For most people, it's safe to say N. + Documentation/networking/multicast.txt. For most people, it's safe + to say N. + +IP: advanced router +CONFIG_IP_ADVANCED_ROUTER + If you intend to run your Linux box mostly as a router, i.e. as a + computer that forwards and redistributes network packets, say Y; you + will then be presented with several options that allow more precise + control about the routing process. + The answer to this question won't directly affect the kernel: saying + N will just cause this configure script to skip all the questions + about advanced routing. + Note that your box can only act as a router if you say Y to "/proc + filesystem support" below and if you enable IP forwarding in your + kernel; you can do this from within a boot-time script like so: + echo "1" > /proc/sys/net/ipv4/ip_forwarding + after the /proc filesystem has been mounted. + If unsure, say N here. + +IP: policy routing +CONFIG_IP_MULTIPLE_TABLES + Normally, a router decides what to do with a received packet based + solely on the packet's final destination address. If you say Y here, + routing can also take into account the originating address and the + network device from which the packet reached us. + +IP: equal cost multipath +CONFIG_IP_ROUTE_MULTIPATH + Normally, the routing tables specify a single action to be taken in + a deterministic manner for a given packet. If you say Y here + however, it becomes possible to attach several actions to a packet + pattern, in effect specifying several alternative paths to travel + for those packets. The router considers all these paths to be of + equal "cost" and chooses one of them in a non-deterministic fashion + if a matching packet arrives. + +IP: use TOS value as routing key +CONFIG_IP_ROUTE_TOS + The header of every IP packet carries a TOS (Type of Service) value + with which the packet requests a certain treatment, e.g. low latency + (for interactive traffic), high throughput, or high + reliability. Normally, these values are ignored, but if you say Y + here, you will be able to specify different routes for packets with + different TOS values. + +IP: verbose route monitoring +CONFIG_IP_ROUTE_VERBOSE + If you say Y here, which is recommended, then the kernel will print + verbose messages regarding the routing, for example warnings about + received packets which look strange and could be evidence of an + attack or a misconfigured system somewhere. The information is + handled by the klogd demon which is responsible for kernel messages + ("man klogd"). + +IP: large routing tables +CONFIG_IP_ROUTE_LARGE_TABLES + If you have routing zones that grow to more than about 64 entries, + you may want to say Y here to speed up the routing process. + +IP: fast network address translation +CONFIG_IP_ROUTE_NAT + If you say Y here, your router will be able to modify source and + destination addresses of packets that pass through it. IP: optimize as router not host CONFIG_IP_ROUTER Some Linux network drivers use a technique called copy and checksum - to optimize host performance. For a machine which is forwarding most - packets to another host this is however a loss. This parameter turns - off copy and checksum from devices. It may make other changes in the - future. + to optimize host performance. For a machine which acts a router most + of the time and is forwarding most packets to another host this is + however a loss. If you say Y here, copy and checksum will be + switched off. In the future, it may make other changes which + optimize for router operation. Note that your box can only act as a router if you say Y to "/proc - filesystem support" below and you enable IP forwarding in your + filesystem support" below and if you enable IP forwarding in your kernel; you can do this from within a boot-time script like so: echo "1" > /proc/sys/net/ipv4/ip_forwarding after the /proc filesystem has been mounted. If unsure, say N here. @@ -1199,21 +1495,22 @@ CONFIG_IP_FIREWALL support" below and IP forwarding is enabled in your kernel; do this from within a boot-time script like so: echo "1" > /proc/sys/net/ipv4/ip_forwarding - after the /proc filesystem has been mounted. You need to say Y to - "IP firewalling" in order to be able to use IP masquerading - (i.e. local computers can chat with an outside host, but that - outside host is made to think that it is talking to the firewall box - -- makes the local network completely invisible and avoids the need - to allocate valid IP host addresses for the machines on the local - net) and IP packet accounting (keeping track of what is using all - your network bandwidth) and IP transparent proxying (makes the - computers on the local network think they're talking to a remote - computer, while in reality the traffic is redirected by your Linux - firewall to a local proxy server). If unsure, say N. + after the /proc filesystem has been mounted. + You need to say Y to "IP firewalling" in order to be able to use IP + masquerading (masquerading means that local computers can chat with + an outside host, but that outside host is made to think that it is + talking to the firewall box -- makes the local network completely + invisible and avoids the need to allocate valid IP host addresses + for the machines on the local net) and IP packet accounting (keeping + track of what is using all your network bandwidth) and IP + transparent proxying (makes the computers on the local network think + they're talking to a remote computer, while in reality the traffic + is redirected by your Linux firewall to a local proxy server). If + unsure, say N. IP: firewall packet netlink device CONFIG_IP_FIREWALL_NETLINK - If you say Y here and when packets hit your Linux firewall and are + If you say Y here and then packets hit your Linux firewall and are blocked, the first 128 bytes of each such packet are passed on to optional user space monitoring software that can then look for attacks and take actions such as paging the administrator of the @@ -1239,8 +1536,8 @@ CONFIG_IP_PNP of the routing table during kernel boot, based on either information supplied at the kernel command line or by BOOTP or RARP protocols. You need to say Y only for diskless machines requiring network access - to boot (see CONFIG_ROOT_NFS for more information about root volume - mounted via NFS), because all other machines configure the network in + to boot (in which case you want to say Y to "Root file system on + NFS" as well), because all other machines configure the network in their startup scripts. BOOTP support @@ -1285,18 +1582,22 @@ CONFIG_NET_IPIP IP: GRE tunnels over IP CONFIG_NET_IPGRE - Another kind of tunneling protocol - "Generic Routing Encapsulation". - It allows to tunnel any networking protocol over existing IPv4 - infrastructure. At the moment only IPv4 and IPv6 are supported. - It is useful, if another endpoint is Cisco router: it likes - GRE much more than IPIP and, particularly, allows multicasts - redistribution over GRE tunnels. + Tunneling means encapsulating data of one protocol type within + another protocol and sending it over a channel that understands the + encapsulating protocol. This particular tunneling driver implements + GRE (Generic Routing Encapsulation) and at this time allows + encapsulating of IPv4 or IPv6 over existing IPv4 + infrastructure. This driver is useful if the other endpoint is a + Cisco router: Cisco likes GRE much better than the other Linux + tunneling driver ("IP: tunneling" above). In addition, GRE allows + multicast redistribution through the tunnel. IP: broadcast GRE over IP CONFIG_NET_IPGRE_BROADCAST - One application of GRE/IP, allowing to construct broadcast LAN, - looking like ethernet network, distributed over the Internet. - It requires, that your domain supported multicast routing. + One application of GRE/IP is to construct a broadcast WAN (Wide Area + Network), which looks like a normal1 ethernet LAN (Local Area + Network), but can be distributed all over the Internet. If you want + to do that, say Y here and to "IP: multicast routing" below. IP: firewall packet logging CONFIG_IP_FIREWALL_VERBOSE @@ -1332,7 +1633,7 @@ CONFIG_IP_MASQUERADE Linux box to the Internet using SLiRP [SLiRP is a SLIP/PPP emulator that works if you have a regular dial up shell account on some UNIX computer; get it via ftp (user: anonymous) from - ftp://sunsite.unc.edu/pub/Linux/system/Network/serial/].) Details + ftp://sunsite.unc.edu/pub/Linux/system/network/serial/].) Details on how to set things up are contained in the IP Masquerading FAQ, available at http://www.indyramp.com/masq/. If you say Y here, then the modules ip_masq_ftp.o (for ftp transfers through the firewall), @@ -1344,23 +1645,27 @@ CONFIG_IP_MASQUERADE IP: ICMP masquerading CONFIG_IP_MASQUERADE_ICMP - The basic masquerade code described for CONFIG_IP_MASQUERADE only + The basic masquerade code described for "IP: masquerading" above only handles TCP or UDP packets (and ICMP errors for existing connections). This option adds additional support for masquerading ICMP packets, such as ping or the probes used by the Windows 95 tracert program. - If you want this, say Y. + If you want this, say Y. IP: ipautofw masquerade support CONFIG_IP_MASQUERADE_IPAUTOFW (Experimental) - ipautofw is a program by Richard Lynch allowing additional - support for masquerading protocols which do not (as yet) - have additional protocol helpers. - Information and source for ipautofw is available from + ipautofw is a program by Richard Lynch allowing additional support + for masquerading protocols which do not (as yet) have their own + additional protocol helpers. Information and source for ipautofw is + available via ftp (user: anonymous) from ftp://ftp.netis.com/pub/members/rlynch/ The ipautofw code is still under development and so is currently marked EXPERIMENTAL. - If you want this, say Y. + If you want this, say Y. This code is also available as a module ( = + code which can be inserted in and removed from the running kernel + whenever you want). The module will be called ip_masq_autofw.o. If + you want to compile it as a module, say M here and read + Documentation/modules.txt. IP: ipportfw masquerade support CONFIG_IP_MASQUERADE_IPPORTFW @@ -1368,10 +1673,16 @@ CONFIG_IP_MASQUERADE_IPPORTFW to allow some forwarding of packets from outside to inside a firewall on given ports. Information and source for ipportfw is available from - http://www.monmouth.demon.co.uk/ipsubs/portforwarding.html + http://www.monmouth.demon.co.uk/ipsubs/portforwarding.html (to + browse the WWW, you need to have access to a machine on the Internet + that has a program like lynx or netscape). The portfw code is still under development and so is currently marked EXPERIMENTAL. - If you want this, say Y. + If you want this, say Y. This code is also available as a module ( = + code which can be inserted in and removed from the running kernel + whenever you want). The module will be called ip_masq_portfw.o. If + you want to compile it as a module, say M here and read + Documentation/modules.txt. IP: always defragment CONFIG_IP_ALWAYS_DEFRAG @@ -1417,23 +1728,26 @@ CONFIG_IP_MROUTE audio and video broadcasts. In order to do that, you would most likely run the program mrouted. Information about the multicast capabilities of the various network cards is contained in - drivers/net/README.multicast. If you haven't heard about it, you - don't need it. + Documentation/networking/multicast.txt. If you haven't heard about + it, you don't need it. IP: PIM-SM version 1 support CONFIG_IP_PIMSM_V1 - Kernel side support for Sparse Mode PIM version 1. This multicast - routing protocol is used widely due to Cisco supports it. - You need special software to use it (pimd-v1). Press N, if - you do not want to use PIM-SM v1. Note, that Dense Mode PIM - need not this option. + Kernel side support for Sparse Mode PIM (Protocol Independent + Multicast) version 1. This multicast routing protocol is used widely + because Cisco supports it. You need special software to use it + (pimd-v1). Please see http://netweb.usc.edu/pim/ for more + information about PIM (to browse the WWW, you need to have access to + a machine on the Internet that has a program like lynx or + netscape). Say Y if you want to use PIM-SM v1. Note that you can say + N here if you just want to use Dense Mode PIM. IP: PIM-SM version 2 support CONFIG_IP_PIMSM_V2 - Kernel side support for Sparse Mode PIM version 2. You need - experimental routing daemon supporting it (pimd or gated-5). - This protocol is not used widely, so that press Y, if you - do not want play with it. + Kernel side support for Sparse Mode PIM version 2. In order to use + this, you need an experimental routing daemon supporting it (pimd or + gated-5). This routing protocol is not used widely, so say N unless + you want to play with it. PC/TCP compatibility mode CONFIG_INET_PCTCP @@ -1455,16 +1769,18 @@ CONFIG_INET_RARP rarp ("man rarp") on your box. If you actually want to use a diskless Sun 3 machine as an Xterminal to Linux, say Y here and fetch Linux-Xkernel from - ftp://sunsite.unc.edu/pub/Linux/system/Network/boot.net/. Superior + ftp://sunsite.unc.edu/pub/Linux/system/network/boot.net/. Superior solutions to the problem of booting and configuring machines over a net connection are given by the protocol BOOTP and its successor DHCP. See the DHCP FAQ - http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html for details. If - you want to compile RARP support as a module ( = code which can be - inserted in and removed from the running kernel whenever you want), - say M here and read Documentation/modules.txt. The module will be - called rarp.o. If you don't understand a word of the above, say N - and rest in peace. + http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html for details (to + browse the WWW, you need to have access to a machine on the Internet + that has a program like lynx or netscape). If you want to compile + RARP support as a module ( = code which can be inserted in and + removed from the running kernel whenever you want), say M here and + read Documentation/modules.txt. The module will be called rarp.o. + If you don't understand a word of the above, say N and rest in + peace. Assume subnets are local CONFIG_INET_SNARL @@ -1537,10 +1853,16 @@ CONFIG_SKB_LARGE Unix domain sockets CONFIG_UNIX - Y if you want Unix domain sockets. Unless you are working on an - embedded system or somthing, you probably want to say Y. If you try - building this as a module and you are running kerneld, you need to make - sure and add 'alias net-pf-1 unix' to your /etc/conf.module file. + This includes Unix domain sockets, the standard Unix mechanism for + establishing and accessing network connections. Unless you are + working on an embedded system or something, you probably want to say + Y. The socket support is also available as a module ( = code which + can be inserted in and removed from the running kernel whenever you + want). The module will be called unix.o. If you want to compile it + as a module, say M here and read Documentation/modules.txt. If you + try building this as a module and you are running kerneld, be sure + to add 'alias net-pf-1 unix' to your /etc/conf.module file. If + unsure, say Y. The IPv6 protocol CONFIG_IPV6 @@ -1548,31 +1870,35 @@ CONFIG_IPV6 Protocol IP version 6 (also called IPng "IP next generation"). Features of this new protocol include: expanded address space, authentication and privacy, and seamless - interoperability with the current version of IP. For general - information about IPv6, see - http://playground.sun.com/pub/ipng/html/ipng-main.html; for specific - information about IPv6 under Linux read the HOWTO at - http://www.terra.net/ipv6/ and the file net/ipv6/README in the - kernel source. If you want to use IPv6, please upgrade to the newest - net-tools as given in Documentation/Changes. The IPv6 support is - also available as a module ( = code which can be inserted in and - removed from the running kernel whenever you want). The module will - be called ipv6.o. If you want to compile it as a module, say M here - and read Documentation/modules.txt. It's safe to say N for now. + interoperability with the current version of IP (IP version 4). For + general information about IPv6, see + http://playground.sun.com/pub/ipng/html/ipng-main.html (to browse + the WWW, you need to have access to a machine on the Internet that + has a program like lynx or netscape); for specific information about + IPv6 under Linux read the HOWTO at http://www.terra.net/ipv6/ and + the file net/ipv6/README in the kernel source. If you want to use + IPv6, please upgrade to the newest net-tools as given in + Documentation/Changes. The IPv6 support is also available as a + module ( = code which can be inserted in and removed from the + running kernel whenever you want). The module will be called + ipv6.o. If you want to compile it as a module, say M here and read + Documentation/modules.txt. It's safe to say N for now. IPv6: enable EUI-64 token format CONFIG_IPV6_EUI64 - 6bone is moving to new aggregatable address format and new link local - address assignment (EUI-64). Say Y, if your site already upgraded, or - started upgrade. + 6bone, the network of computers using the IPv6 protocol, is moving + to a new aggregatable address format and a new link local address + assignment (EUI-64). Say Y, if your site has upgraded already, or + has started to upgrade. IPv6: disable provider based addresses CONFIG_IPV6_NO_PB - Linux tries to operate correctly, when site is moved to EUI-64 - only partially. Unfortunately, these two formats ("provider based" - and "aggregatable") are incompatible. Say Y, if your site finished - upgrade, and/or you encountered some problems caused by presense of - two link-local addresses on an interface. + Linux tries to operate correctly when your site is moved to EUI-64 + only partially. Unfortunately, the two address formats (old: + "provider based" and new: "aggregatable") are incompatible. Say Y, + if your site finished the upgrade to EUI-64, and/or you encountered + some problems caused by the presence of two link-local addresses on + an interface. The IPX protocol CONFIG_IPX @@ -1580,13 +1906,13 @@ CONFIG_IPX used for local networks of Windows machines. You need it if you want to access Novell Netware file or print servers using the Linux Novell client ncpfs (available via ftp (user: anonymous) from - sunsite.unc.edu:/pub/Linux/system/Filesystems/) or from within the + sunsite.unc.edu:/pub/Linux/system/filesystems/) or from within the Linux DOS emulator dosemu (read the DOSEMU-HOWTO, available in sunsite.unc.edu:/pub/Linux/docs/HOWTO). In order to do the former, you'll also have to say Y to "NCP filesystem support", below. To turn your Linux box into a fully featured Netware file server and IPX router, say Y here and fetch either lwared from - sunsite.unc.edu:/pub/Linux/system/Network/daemons/ or mars_nwe from + sunsite.unc.edu:/pub/Linux/system/network/daemons/ or mars_nwe from ftp.gwdg.de:/pub/linux/misc/ncpfs. For more information, read the IPX-HOWTO in sunsite.unc.edu:/pub/Linux/docs/howto. The IPX driver would enlarge your kernel by about 5 kB. This driver is also @@ -1644,21 +1970,49 @@ CONFIG_ATALK machine on the Internet that has a program like lynx or netscape). EtherTalk is the name used for appletalk over ethernet and the cheaper and slower LocalTalk is appletalk over a proprietary - apple network using serial links. Ethertalk and Localtalk is fully + apple network using serial links. Ethertalk and Localtalk are fully supported by Linux. The NET-2-HOWTO, available via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO contains valuable information as well. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you - want). The module will be called appletalk.o. If you want to compile + want). The module is called appletalk.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. I hear that the GNU boycott of Apple is over, so even politically correct people are allowed to say Y here. -IP-over-DDP support +Appletalk-IP driver support CONFIG_IPDDP This allows IP networking for users who only have Appletalk - networking available. This feature is experimental. Please see - http://www.maths.unm.edu/~bradford/ltpc.html for support software. + networking available. This feature is experimental. With this + driver, you can either encapsulate IP inside Appletalk (e.g. if your + Linux box is stuck on an appletalk only network) or decapsulate + (e.g. if you want your Linux box to act as a internet gateway for a + zoo of appletalk connected Macs). You decide which one of the two + you want in the following two questions; you can say Y to only one + of them. Please see Documentation/networking/ipddp.txt for more + information. This driver is also available as a module ( = code + which can be inserted in and removed from the running kernel + whenever you want). The module is called ipddp.o. If you want to + compile it as a module, say M here and read + Documentation/modules.txt. + +IP to Appletalk-IP Encapsulation support +CONFIG_IPDDP_ENCAP + If you say Y here, the kernel will be able to encapsulate IP packets + inside Appletalk frames; this is useful if your Linux box is stuck + on an appletalk network (which hopefully contains a decapsulator + somewhere). Please see Documentation/networking/ipddp.txt for more + information. If you say Y here, you cannot say Y to "Appletalk-IP to + IP Decapsulation support", below. + +Appletalk-IP to IP Decapsulation support +CONFIG_IPDDP_DECAP + If you say Y here, the kernel will be able to decapsulate + Appletalk-IP frames to IP packets; this is useful if you want your + Linux box to act as an Internet gateway for an appletalk + network. Please see Documentation/networking/ipddp.txt for more + information. If you say Y here, you cannot say Y to "IP to + Appletalk-IP Encapsulation support", above. Apple/Farallon LocalTalk PC card support CONFIG_LTPC @@ -1667,8 +2021,7 @@ CONFIG_LTPC If you are in doubt, this card is the one with the 65C02 chip on it. You also need version 1.3.3 or later of the netatalk package. This driver is experimental, which means that it may not work. - See README.ltpc in the drivers/net directory, and the web site - http://www.math.unm.edu/~bradford/ltpc.html + See the file Documentation/networking/ltpc.txt. COPS LocalTalk PC card support CONFIG_COPS @@ -1677,9 +2030,7 @@ CONFIG_COPS package. This driver is experimental, which means that it may not work. This driver will only work if you choose "Appletalk DDP" networking support, above. - Please read the file Documentation/networking/README.cops. See the - web site http://www.math.unm.edu/~bradford/ltpc.html for localtalk - IP tools. + Please read the file Documentation/networking/cops.txt. Dayna firmware support CONFIG_COPS_DAYNA @@ -1692,6 +2043,17 @@ CONFIG_COPS_TANGENT Support COPS compatible cards with Tangent style firmware (Tangent ATB_II, Novell NL-1000, Daystar Digital LT-200. +Amateur Radio support +CONFIG_HAMRADIO + If you want to connect your Linux computer to an amateur radio, say + Y here. You want to read http://www.tapr.org/tapr/html/pkthome.html + (to browse the WWW, you need to have access to a machine on the + Internet that has a program like lynx or netscape) and the HAM-HOWTO + and the AX25-HOWTO, both available via ftp (user: anonymous) from + sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the answer to this + question won't directly affect the kernel: saying N will just cause + this configure script to skip all the questions about amateur radio. + Amateur Radio AX.25 Level 2 CONFIG_AX25 This is the protocol used for computer communication over amateur @@ -1785,19 +2147,20 @@ CONFIG_ROSE CCITT X.25 Packet Layer CONFIG_X25 X.25 is a set of standardized network protocols, similar in scope to - frame relay; the one physical line from your box to the entry point - to the X.25 network can carry several logical point-to-point - connections (called "virtual circuits") to other computers connected - to the X.25 network. Governments, banks, and other organizations - tend to use it to connect to each other or to form Wide Area - Networks. Many countries have public X.25 networks. X.25 consists - of two protocols: the higher level Packet Layer Protocol (PLP) (say - Y here if you want that) and the lower level data link layer - protocol LAPB (say Y to "LAPB Data Link Driver" below if you want - that). You can read more about X.25 at - http://www.sangoma.com/x25.html and - http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm. - Information about X.25 for Linux is contained in the files + frame relay; the one physical line from your box to the X.25 network + entry point can carry several logical point-to-point connections + (called "virtual circuits") to other computers connected to the X.25 + network. Governments, banks, and other organizations tend to use it + to connect to each other or to form Wide Area Networks (WAN's). Many + countries have public X.25 networks. X.25 consists of two + protocols: the higher level Packet Layer Protocol (PLP) (say Y here + if you want that) and the lower level data link layer protocol LAPB + (say Y to "LAPB Data Link Driver" below if you want that). You can + read more about X.25 at http://www.sangoma.com/x25.html and + http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm + (to browse the WWW, you need to have access to a machine on the + Internet that has a program like lynx or netscape). Information + about X.25 for Linux is contained in the files Documentation/networking/x25.txt and Documentation/networking/x25-iface.txt. One connects to an X.25 network either with a dedicated network card using the X.21 protocol @@ -1833,7 +2196,7 @@ CONFIG_LAPB CONFIG_LLC This is a Logical Link Layer protocol used for X.25 connections over ethernet, using ordinary ethernet cards. - + Bridging (EXPERIMENTAL) CONFIG_BRIDGE If you say Y here, then your Linux box will be able to act as an @@ -1844,13 +2207,23 @@ CONFIG_BRIDGE algorithm. As this is a standard, Linux bridges will interwork properly with other third party bridge products. In order to use this, you'll need the bridge configuration tools available via ftp - (user: anonymous) from shadow.cabi.net. Note that if your box acts - as a bridge, it probably contains several ethernet devices, but the - kernel is not able to recognize more than one at boot time without - help; for details read the Multiple-Ethernet-mini-HOWTO, available - via ftp (user: anonymous) in - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. The Bridging code is - still in test. If unsure, say N. + (user: anonymous) from shadow.cabi.net in /pub/Linux. Note that if + your box acts as a bridge, it probably contains several ethernet + devices, but the kernel is not able to recognize more than one at + boot time without help; for details read the Ethernet-HOWTO, available + via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO/. + The Bridging code is still in test. If unsure, say N. + +Packet socket +CONFIG_PACKET + The Packet protocol is used by applications which communicate + directly with network devices without an intermediate network + protocol implemented in the kernel, e.g. tcpdump. If you want that + they work, choose Y. This driver is also available as a module + called af_packet.o ( = code which can be inserted in and removed + from the running kernel whenever you want). If you want to compile + it as a module, say M here and read Documentation/modules.txt. If + unsure, say Y. Kernel/User network link driver CONFIG_NETLINK @@ -1863,7 +2236,9 @@ CONFIG_NETLINK to "Kernel/User network link driver" further down. You also need to say Y here if you want to use arpd, a daemon that helps keep the internal ARP cache (a mapping between IP addresses and hardware - addresses on the local network) small. If unsure, say N. + addresses on the local network) small. The ethertap device, which + lets user space programs read and write raw ethernet frames, also + needs the network link driver. If unsure, say Y. Routing messages CONFIG_RTNETLINK @@ -1872,6 +2247,11 @@ CONFIG_RTNETLINK you can read some network related routing information from that file. Everything you write to that file will be discarded. +Netlink device emulation +CONFIG_NETLINK_DEV + This is a backward compatibility option, choose Y for now. + This option will be removed soon. + SCSI support? CONFIG_SCSI If you want to use a SCSI harddisk, SCSI tapedrive, SCSI CDROM or @@ -1904,7 +2284,7 @@ CONFIG_BLK_DEV_SD your root filesystem (the one containing the directory /) is located on a SCSI disk. In this case, do not compile the driver for your SCSI host adapter (below) as a module either. - + SCSI tape support CONFIG_CHR_DEV_ST If you want to use a SCSI tapedrive under Linux, say Y and read the @@ -1932,8 +2312,7 @@ CONFIG_BLK_DEV_SR_VENDOR This enables the usage of vendor specific SCSI commands. This is required to support multisession CD's on with old NEC/TOSHIBA cdrom drives (and HP Writers). If you have such a drive and get - the first session only, try to turn this on. Most drives should - work fine without this. + the first session only, try to say Y here; everybody else says N. SCSI generic support CONFIG_CHR_DEV_SG @@ -1969,6 +2348,20 @@ CONFIG_SCSI_CONSTANTS understand if you say Y here; it will enlarge your kernel by about 12KB. If in doubt, say Y. +SCSI logging facility +CONFIG_SCSI_LOGGING + This turns on a logging facility that can be used to debug a number + of problems. Normally no logging output will appear, but you can + enable logging with a shell command like: + echo "scsi log token [level]" > /proc/scsi/scsi + There are a number of things that can be used for 'token' (you can + find them in the source: drivers/scsi/scsi.c), and this allows you + to select the types of information you want, and the level allows + you to select the level of verbosity. If you say 'N' here, it may + be harder to track down some types of scsi problems. If you say 'Y' + here your kernel will be somewhat larger, but there should be no + noticeable performance impact as long as you have logging turned off. + AdvanSys SCSI support CONFIG_SCSI_ADVANSYS This is a driver for all SCSI host adapters manufactured by @@ -2003,7 +2396,7 @@ CONFIG_SCSI_AHA1542 inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called aha1542.o. - + Adaptec AHA1740 support CONFIG_SCSI_AHA1740 This is support for a SCSI host adapter. It is explained in section @@ -2045,21 +2438,22 @@ CONFIG_OVERRIDE_CMDS Maximum number of commands per LUN CONFIG_AIC7XXX_CMDS_PER_LUN - If tagged queueing is enabled, then you may want to try increasing - the number of SCSI commands per LUN to more than 2. By default, we - limit the commands per LUN to 2 with or without tagged queueing - enabled. If tagged queueing is disabled, the sequencer in the host - adapter will keep the 2nd command in the input queue until the first - one completes - so it is OK to have more than 1 command queued. If - tagged queueing is enabled, then the sequencer will attempt to send - the 2nd command block to the device while the first command block is - executing and the device is disconnected. For adapters limited to 4 - command blocks (SCB's), you may want to actually decrease the - commands per LUN to 1, if you often have more than 2 devices active - at the same time. This will ensure that there will always be a free - SCB for up to 4 devices active at the same time. When SCB paging is - enabled, set the commands per LUN to 8 or higher (see "SCB paging - support" below). If unsure, go with the default for now. + By default, we limit the commands per LUN to 2 with or without + tagged queueing enabled. If tagged queueing is enabled, the + sequencer in the host adapter will attempt to send the 2nd command + block to the device while the first command block is still executing + and the device is disconnected. If the devices don't complain, you + can thus try to increase the number of SCSI commands per LUN to more + than 2 in this case. If tagged queueing is disabled, the sequencer + in the host adapter will keep the 2nd command in its input queue + until the first one completes - so it is OK to have more than 1 + command queued. However, for host adapters limited to 4 command + blocks (SCB's), you may want to actually decrease the commands per + LUN to 1, if you often have more than 2 devices active at the same + time. This will ensure that there will always be a free SCB for up + to 4 devices active at the same time. When SCB paging is enabled, + set the commands per LUN to 8 or higher (see "SCB paging support" + below). If unsure, go with the default for now. Enable SCB paging CONFIG_AIC7XXX_PAGE_ENABLE @@ -2159,7 +2553,7 @@ CONFIG_SCSI_U14_34F want). The module will be called u14-34f.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. -enable linked commands +enable elevator sorting CONFIG_SCSI_U14_34F_LINKED_COMMANDS This is a feature of SCSI-2 which improves performance: the host adapter can send a whole list of commands to a device in one @@ -2197,7 +2591,7 @@ CONFIG_SCSI_GENERIC_NCR5380 kernel whenever you want). The module will be called g_NCR5380.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. - + Enable NCR53c400 extensions CONFIG_SCSI_GENERIC_NCR53C400 This enables certain optimizations for the NCR53c400 scsi cards. You @@ -2237,7 +2631,7 @@ CONFIG_SCSI_NCR53C7xx_FAST This will enable 10MHz FAST-SCSI transfers with your host adapter. Some systems have problems with that speed, so it's safest to say N here. - + allow DISCONNECT CONFIG_SCSI_NCR53C7xx_DISCONNECT This enables the disconnect/reconnect feature of the NCR SCSI @@ -2364,23 +2758,54 @@ CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT IBMMCA SCSI support CONFIG_SCSI_IBMMCA - If your computer sports an MCA bus system architecture (IBM PS/2) - with an SCSI harddrive, say Y here. Please read - Documentation/mca.txt. This driver is also available as a module ( = - code which can be inserted in and removed from the running kernel - whenever you want). The module will be called ibmmca.o. If you want - to compile it as a module, say M here and read - Documentation/modules.txt. - Normally, all IBM MCA SCSI adapters are automatically detected. If - that doesn't work right however, you can completely override - auto-detection by specifying "ibmmcascsi=io1,io2,..." at the boot - loader's command prompt or "io_port=io1,io2,... scsi_id=id1,id2,..." - as a parameter of insmod. "io" and "id" are the I/O base address - and the SCSI ID of each adapter, respectively. - If you want to compile this driver as a module ( = code which can be - inserted in and removed from the running kernel whenever you want), - say M here and read Documentation/modules.txt. The module will be - called ibmmca.o. + This is support for the IBM SCSI adapter found in many of the PS/2 + series. CONFIG_MCA must be set for this to work. If the adapter + isn't found during boot (a common problem for models 56, 57, 76, and + 77) you'll need to use the 'ibmmcascsi=<pun>', where <pun> is the id + of the SCSI subsystem (usually 7, but if that doesn't work check your + reference diskette). Owners of model 95 with a LED-matrix-display + can in addition activate some activity info like under OS/2, but more + informative, by setting 'ibmmcascsi=display' as additional kernel- + parameter. + +Standard SCSI-order +CONFIG_IBMMCA_SCSI_ORDER_STANDARD + In the PC-world and in most modern SCSI-BIOS-setups, SCSI-harddisks + are assigned to the driveletters, starting with the lowest SCSI-id + (physical number - pun) to be drive C:, as seen from DOS and similar + operating systems. When looking into papers, describing the + ANSI-SCSI-standard, this assignment of drives appears to be wrong. + The SCSI-standard follows a hardware-hierarchy which says, that + id 7 has the highest priority and id 0 the lowest. Therefore, the + hostadapters are still today everywhere placed as SCSI-id 7 by + default. In the SCSI-standard, the driveletters express the priority + of the disk. C: should be the harddisk or a partition on it, with the + highest priority. This must therefore be the disk with the highest + SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the + original definition of the SCSI-standard as also industrial- and + process-control-machines, like VME-CPUs running under realtime-OSs + (e.g. LynxOS, OS9) do. + If you like to run Linux on your MCA-machine with the same assignment, + of harddisks, as seen from e.g. DOS or OS/2 on your machine, which + is in addition conform to the SCSI-standard, you must say 'y' here. + This is also necessary for MCA-Linux-users who want to keep downward- + compatibility to older releases of the IBM-MCA-SCSI-driver (older than + driver-release 2.00 and older than June 1997). + If you like to have the lowest SCSI-id assigned as drive C:, as modern + SCSI-BIOS do, which is not conform to the standard, but widely spread + and common in the PC-world of today, you must say 'n' here. + +Reset SCSI-devices at boottime +CONFIG_IBMMCA_SCSI_DEV_RESET + By default, SCSI-devices are reset, when the machine is powered on. + However, some devices exist, like special-control-devices, + SCSI-CNC-machines, SCSI-printer or scanners of older type, that + do not reset, when switched on. If you say 'y' here, each device + along your SCSI-bus will get a reset-command after it has been + probed, while the kernel is booting. Say always 'n' here, if you + have no such strange SCSI-devices on your bus. If you say 'y' and + some more modern devices, like harddisks, do not like too much + resets, your system will hang when booting. Always IN2000 SCSI support CONFIG_SCSI_IN2000 @@ -2404,6 +2829,36 @@ CONFIG_SCSI_PAS16 pas16.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. +PCI2000 support +CONFIG_SCSI_PCI2000 + This is support for the PCI2000I EIDE interface card which acts as a + SCSI host adapter. Please read the SCSI-HOWTO, available via ftp + (user: anonymous) at sunsite.unc.edu:/pub/Linux/docs/HOWTO. This + driver is also available as a module called pci2000.o ( = code which + can be inserted in and removed from the running kernel whenever you + want). If you want to compile it as a module, say M here and read + Documentation/modules.txt. + +PCI2220i support +CONFIG_SCSI_PCI2220I + This is support for the PCI2220i EIDE interface card which acts as a + SCSI host adapter. Please read the SCSI-HOWTO, available via ftp + (user: anonymous) at sunsite.unc.edu:/pub/Linux/docs/HOWTO. This + driver is also available as a module called pci2220i.o ( = code + which can be inserted in and removed from the running kernel + whenever you want). If you want to compile it as a module, say M + here and read Documentation/modules.txt. + +PSI240i support +CONFIG_SCSI_PSI240I + This is support for the PSI240i EIDE interface card which acts as a + SCSI host adapter. Please read the SCSI-HOWTO, available via ftp + (user: anonymous) at sunsite.unc.edu:/pub/Linux/docs/HOWTO. This + driver is also available as a module called psi240i.o ( = code which + can be inserted in and removed from the running kernel whenever you + want). If you want to compile it as a module, say M here and read + Documentation/modules.txt. + Qlogic FAS SCSI support CONFIG_SCSI_QLOGIC_FAS This driver works only with the ISA, VLB, and PCMCIA versions of the @@ -2472,15 +2927,15 @@ CONFIG_SCSI_ULTRASTOR Documentation/modules.txt. The module will be called ultrastor.o. Note that there is also another driver for the same hardware: "UltraStor 14F/34F support", above. - + 7000FASST SCSI support CONFIG_SCSI_7000FASST - This driver supports the Western Digital 7000 SCSI host adapter. - Some information is in the source: drivers/scsi/wd7000.c. This - driver is also available as a module ( = code which can be inserted - in and removed from the running kernel whenever you want). The - module will be called wd7000.o. If you want to compile it as a - module, say M here and read Documentation/modules.txt. + This driver supports the Western Digital 7000 SCSI host adapter + family. Some information is in the source: drivers/scsi/wd7000.c. + This driver is also available as a module ( = code which can be + inserted in and removed from the running kernel whenever you + want). The module will be called wd7000.o. If you want to compile it + as a module, say M here and read Documentation/modules.txt. EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support CONFIG_SCSI_EATA @@ -2505,7 +2960,7 @@ CONFIG_SCSI_EATA_TAGGED_QUEUE previous commands haven't finished yet. Some SCSI devices don't implement this properly, so the save answer is N. -enable linked commands +enable elevator sorting CONFIG_SCSI_EATA_LINKED_COMMANDS This is a feature of SCSI-2 which improves performance: the host adapter can send a whole list of commands to a device in one @@ -2530,25 +2985,12 @@ CONFIG_SCSI_NCR53C406A and read Documentation/modules.txt. The module will be called NCR53c406.o. -Tekram DC390W/U/F (T) SCSI support -CONFIG_SCSI_DC390W - This driver supports the Tekram DC390W/U/F (T) PCI SCSI host - adapters with the NCR/Symbios 53c825/875 chips. Say Y here if you - have one of those. If however you have a DC390 (T) adaptor with the - Am53C974A chip, use the DC390(T) driver "Tekram DC390(T) (AMD - PCscsi) SCSI support", below. - If you want to compile this driver as a module ( = code which can be - inserted in and removed from the running kernel whenever you want), - say M here and read Documentation/modules.txt. The module will be - called ???.o. - Tekram DC390(T) (AMD PCscsi) SCSI support CONFIG_SCSI_DC390T This driver supports the Tekram DC390(T) PCI SCSI host adapter with the Am53C974A chip, and perhaps other cards using the same chip. - This driver does _not_ support the DC390W/U/F adaptor with the - NCR/Symbios chips; use "Tekram DC390W/U/F (T) SCSI support" for that - one. + This driver does _not_ support the DC390W/U/F adaptor with the + NCR/Symbios chips; use "NCR53C8XX SCSI support" for that one. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be @@ -2608,6 +3050,15 @@ CONFIG_SCSI_SGIWD93 This is the SCSI driver for WD33C93 / WD33C95 SCSI chips used in many SGI machines. +SCSI Debug host simulator. +CONFIG_SCSI_DEBUG + This is a host adapter simulator that can be programmed to simulate a + large number of conditions that could occur on a real bus. The advantage + is that many hard to reproduce problems can be tested in a controlled + environment where there is reduced risk of losing important data. + This is primarily of use to people trying to debug the middle and upper + layers of the scsi subsystem. If unsure, say N. + Network device support? CONFIG_NETDEVICES You can say N here in case you don't intend to connect to any other @@ -2618,20 +3069,19 @@ CONFIG_NETDEVICES shell account or a BBS, even using term (term is a program which gives you almost full Internet connectivity if you have a regular dial up shell account on some Internet connected Unix computer. Read - http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html). You'll - have to say Y if your computer contains a network card that you want - to use under linux (make sure you know its name because you will be - asked for it and read the Ethernet-HOWTO; also, if you plan to use - more than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini) or if you want to use - SLIP (Serial Line Internet Protocol is the protocol used to send - Internet traffic over telephone lines or nullmodem cables) or CSLIP - (compressed SLIP) or PPP (Point to Point Protocol, a better and - newer replacement for SLIP) or PLIP (Parallel Line Internet Protocol - is mainly used to create a mini network by connecting the parallel - ports of two local machines) or AX.25/KISS (protocol for sending - internet traffic over radio links). Make sure to read the + http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse + the WWW, you need to have access to a machine on the Internet that + has a program like lynx or netscape)). You'll have to say Y if your + computer contains a network card that you want to use under linux + (make sure you know its name because you will be asked for it and read + the Ethernet-HOWTO in sunsite.unc.edu:/pub/Linux/docs/HOWTO; or if you + want to use SLIP (Serial Line Internet Protocol is the protocol used + to send Internet traffic over telephone lines or nullmodem cables) + or CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better + and newer replacement for SLIP) or PLIP (Parallel Line Internet + Protocol is mainly used to create a mini network by connecting the + parallel ports of two local machines) or AX.25/KISS (protocol for + sending internet traffic over radio links). Make sure to read the NET-2-HOWTO. Eventually, you will have to read Olaf Kirch's excellent book "Network Administrator's Guide", to be found in sunsite.unc.edu:/pub/Linux/docs/LDP. If unsure, say Y. @@ -2653,7 +3103,7 @@ CONFIG_DUMMY want to use more than one dummy device at a time, you need to compile this driver as a module. Instead of 'dummy', the devices will then be called 'dummy0', 'dummy1' etc. - + SLIP (serial line) support CONFIG_SLIP Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to @@ -2665,7 +3115,7 @@ CONFIG_SLIP nullmodems). Normally, your access provider has to support SLIP in order for you to be able to use it, but there is now a SLIP emulator called SLiRP around (available via ftp (user: anonymous) from - sunsite.unc.edu:/pub/Linux/system/Network/serial/) which allows you + sunsite.unc.edu:/pub/Linux/system/network/serial/) which allows you to use SLIP over a regular dial up shell connection. If you plan to use SLiRP, make sure to say Y to CSLIP, below. The NET-2-HOWTO, available via ftp (user: anonymous) in @@ -2674,14 +3124,16 @@ CONFIG_SLIP term (term is a program which gives you almost full Internet connectivity if you have a regular dial up shell account on some Internet connected Unix computer. Read - http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html). SLIP - support will enlarge your kernel by about 4kB. If unsure, say N. If - you want to compile this as a module ( = code which can be inserted - in and removed from the running kernel whenever you want), say M - here and read Documentation/modules.txt as well as + http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse + the WWW, you need to have access to a machine on the Internet that + has a program like lynx or netscape)). SLIP support will enlarge + your kernel by about 4kB. If unsure, say N. If you want to compile + this as a module ( = code which can be inserted in and removed from + the running kernel whenever you want), say M here and read + Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be called slip.o. - + CSLIP compressed headers CONFIG_SLIP_COMPRESSED This protocol is faster than SLIP because it uses compression on the @@ -2689,7 +3141,7 @@ CONFIG_SLIP_COMPRESSED on both ends. Ask your access provider if you are not sure and say Y, just in case. You will still be able to use plain SLIP. If you plan to use SLiRP, the SLIP emulator (available via ftp (user: - anonymous) from sunsite.unc.edu:/pub/Linux/system/Network/serial/) + anonymous) from sunsite.unc.edu:/pub/Linux/system/network/serial/) which allows you to use SLIP over a regular dial up shell connection, you definitely want to say Y here. The NET-2-HOWTO, available via ftp (user: anonymous) in @@ -2712,27 +3164,15 @@ CONFIG_SLIP_MODE_SLIP6 end of the link as well. It's good enough, for example, to run IP over the async ports of a Camtec JNT Pad. If unsure, say N. -Radio network interfaces +Wireless LAN (non-hamradio) CONFIG_NET_RADIO - Radio based interfaces for Linux. This includes amateur radio - (AX.25), support for wireless ethernet and other systems. Note that - the answer to this question won't directly affect the kernel: saying - N will just cause this configure script to skip all the questions - about radio interfaces. Some user-level drivers for scarab devices - which don't require special kernel support are available via ftp - (user: anonymous) from shadow.cabi.net. - If unsure, say N. - -AX.25 network interfaces -CONFIG_NET_HAM - Say Y here if you want support for a device that connects your Linux - box to your amateur radio (HAM). AX.25 is the protocol used for - digital traffic over amateur radio connections. You might want to - read the HAM-HOWTO and the AX25-HOWTO, both available via ftp (user: - anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the - answer to this question won't directly affect the kernel: saying N - will just cause this configure script to skip all the questions - about amateur radio interfaces. + Support for wireless LAN's and everything having to do with radio, + but not with amateur radio. Note that the answer to this question + won't directly affect the kernel: saying N will just cause this + configure script to skip all the questions about radio + interfaces. Some user-level drivers for scarab devices which don't + require special kernel support are available via ftp (user: + anonymous) from shadow.cabi.net in /pub/Linux. PPP (point-to-point) support CONFIG_PPP @@ -2742,7 +3182,7 @@ CONFIG_PPP otherwise you can't use it (not quite true any more: the free program SLiRP can emulate a PPP line if you just have a regular dial up shell account on some UNIX computer; get it via ftp (user: - anonymous) from sunsite.unc.edu:/pub/Linux/system/Network/serial/). + anonymous) from sunsite.unc.edu:/pub/Linux/system/network/serial/). To use PPP, you need an additional program called pppd as described in Documentation/networking/ppp.txt and in the PPP-HOWTO, available from sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you upgrade from an @@ -2751,20 +3191,22 @@ CONFIG_PPP program which gives you almost full Internet connectivity if you have a regular dial up shell account on some Internet connected UNIX computer. Read - http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html). The PPP - option enlarges your kernel by about 16kB. This driver is also - available as a module ( = code which can be inserted in and removed - from the running kernel whenever you want). If you said Y to - "Version information on all symbols" above, then you cannot compile - the PPP driver into the kernel; you can then only compile it as a - module. The module will be called ppp.o. If you want to compile it - as a module, say M here and read Documentation/modules.txt as well - as Documentation/networking/net-modules.txt. Note that, no matter - what you do, the BSD compression code (used to compress the IP - packets sent over the serial line; has to be supported at the other - end as well) will always be compiled as a module; it is called - bsd_comp.o and will show up in the directory modules once you have - said "make modules". If unsure, say N. + http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse + the WWW, you need to have access to a machine on the Internet that + has a program like lynx or netscape)). The PPP option enlarges your + kernel by about 16kB. This driver is also available as a module ( = + code which can be inserted in and removed from the running kernel + whenever you want). If you said Y to "Version information on all + symbols" above, then you cannot compile the PPP driver into the + kernel; you can then only compile it as a module. The module will be + called ppp.o. If you want to compile it as a module, say M here and + read Documentation/modules.txt as well as + Documentation/networking/net-modules.txt. Note that, no matter what + you do, the BSD compression code (used to compress the IP packets + sent over the serial line; has to be supported at the other end as + well) will always be compiled as a module; it is called bsd_comp.o + and will show up in the directory modules once you have said "make + modules". If unsure, say N. Shortwave radio modem driver CONFIG_HFMODEM @@ -2790,7 +3232,9 @@ STRIP (Metricom Starmode radio IP) CONFIG_STRIP Say Y if you have a Metricom radio and intend to use Starmode Radio IP. STRIP is a radio protocol developed for the MosquitoNet project - (http://mosquitonet.stanford.edu/) to send Internet traffic using + (On the WWW at http://mosquitonet.stanford.edu/; to browse the WWW, + you need to have access to a machine on the Internet that has a + program like lynx or netscape) to send Internet traffic using Metricom radios. Metricom radios are small, battery powered, 100kbit/sec packet radio transceivers, about the size and weight of a cellular telephone. (You may also have heard them called @@ -2805,6 +3249,26 @@ CONFIG_STRIP the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called strip.o. +Radio support +CONFIG_MISC_RADIO + If you have a radio card (which enables your computer to receive + regular radio broadcasts), then you will want to say "y" here and + make a character device file (usually /dev/radio) with major number + 10 and minor 152 using mknod ("man mknod"). And then, don't forget + to pick up some useful tools to use said device (you _might_ find + something at ftp.lmh.ox.ac.uk: /users/weejock/linux/, but I haven't + written anything too useful yet...) + +AIMSlab RadioTrack card +CONFIG_RADIO_RTRACK + Choose Y here if you have one of these, and then fill in the port + address below. + +RadioTrack i/o port +CONFIG_RADIO_RTRACK_PORT + Enter either 0x30f or 0x20f here. The card default is 0x30f, if you + haven't changed the jumper setting on the card. + LAPB over Ethernet driver CONFIG_LAPBETHER This is a driver for a pseudo device (typically called /dev/lapb0) @@ -2841,36 +3305,52 @@ CONFIG_SCC running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called scc.o. +additional delay for PA0HZP OptoSCC compatible boards +CONFIG_SCC_DELAY + +support for TRX that feedback the tx signal to rx +CONFIG_SCC_TRXECHO +### +### Don't know what's going on here. +### + High-speed (DMA) SCC driver for AX.25 CONFIG_DMASCC - This is a driver for high-speed SCC boards, i.e. those supporting - DMA on one port. Currently, only Ottawa PI/PI2 boards (see - http://hydra.carleton.ca/info/pi2.html) and Gracilis PackeTwin - boards (see http://www.paccomm.com/) are supported and detected - automatically. Multiple boards are operated simultaneously. If - you compile this driver as a module, it will be called dmascc.o. - If you don't give any parameter to the driver, all possible I/O - addresses are probed. This could irritate other devices that are - currently not in use. You may specify the list of addresses to be - probed by "dmascc=addr1,addr2,..." (when compiled into the kernel - image) or "io=addr1,addr2,..." (when loaded as a module). - The network interfaces will be called dmascc0 and dmascc1 for the - board detected first, dmascc2 and dmascc3 for the second one, and - so on. Before you configure each interface with ifconfig, you MUST - set certain parameters, such as channel access timing, clock mode, - and DMA channel. This is accomplished with a small utility program - called dmascc_cfg, which is part of the ax25-utils package. - Alternatively, you may download the utility from + This is a driver for high-speed SCC boards (used to connect your + computer to your amateur radio and send internet traffic over the + radio), i.e. those supporting DMA on one port. Currently, only + Ottawa PI/PI2 boards (see http://hydra.carleton.ca/info/pi2.html) + and Gracilis PackeTwin boards (see http://www.paccomm.com/; to + browse the WWW, you need to have access to a machine on the Internet + that has a program like lynx or netscape) are supported and detected + automatically. If you have one of these cards, you can say Y here + and should read the HAM-HOWTO, available via ftp (user: anonymous) + in sunsite.unc.edu:/pub/Linux/docs/HOWTO. + This driver operates multiple boards simultaneously. If you compile + this driver as a module, it will be called dmascc.o. If you don't + give any parameter to the driver, all possible I/O addresses are + probed. This could irritate other devices that are currently not in + use. You may specify the list of addresses to be probed by + "dmascc=addr1,addr2,..." (when compiled into the kernel image) or + "io=addr1,addr2,..." (when loaded as a module). The network + interfaces will be called dmascc0 and dmascc1 for the board detected + first, dmascc2 and dmascc3 for the second one, and so on. Before you + configure each interface with ifconfig, you MUST set certain + parameters, such as channel access timing, clock mode, and DMA + channel. This is accomplished with a small utility program called + dmascc_cfg, which is part of the ax25-utils package. Alternatively, + you may download the utility from http://www.oevsv.at/~oe1kib/Linux.html. BAYCOM picpar and par96 driver for AX.25 CONFIG_BAYCOM_PAR - This is a driver for Baycom style simple amateur radio - modems that connect to a parallel interface. The driver - supports the picpar and par96 designs. To configure the - driver, use the sethdlc utility available in the standard - ax25 utilities package. For information on the modems, see - http://www.baycom.de and Documentation/networking/baycom.txt. If you + This is a driver for Baycom style simple amateur radio modems that + connect to a parallel interface. The driver supports the picpar and + par96 designs. To configure the driver, use the sethdlc utility + available in the standard ax25 utilities package. For information on + the modems, see http://www.baycom.de (to browse the WWW, you need to + have access to a machine on the Internet that has a program like + lynx or netscape) and Documentation/networking/baycom.txt. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. This is @@ -2879,45 +3359,51 @@ CONFIG_BAYCOM_PAR BAYCOM ser12 full duplex driver for AX.25 CONFIG_BAYCOM_SER_FDX This is one of two drivers for Baycom style simple amateur radio - modems that connect to a serial interface. The driver supports - the ser12 design in full duplex mode. In addition, it allows the + modems that connect to a serial interface. The driver supports the + ser12 design in full duplex mode. In addition, it allows the baudrate to be set between 300 and 4800 baud (however not all modems - support all baudrates). This is the preferred driver. baycom_ser_hdx.o - is the old driver and still provided in case this driver does not work - with your serial interface chip. To configure the driver, use the - sethdlc utility available in the standard ax25 utilities package. - For information on the modems, see http://www.baycom.de and - Documentation/networking/baycom.txt. If you want to compile - this driver as a module ( = code which can be inserted in - and removed from the running kernel whenever you want), - say M here and read Documentation/modules.txt. This is - recommended. The module will be called baycom_ser_fdx.o. + support all baudrates). This is the preferred driver. The next + driver, "BAYCOM ser12 half duplex driver for AX.25" is the old + driver and still provided in case this driver does not work with + your serial interface chip. To configure the driver, use the sethdlc + utility available in the standard ax25 utilities package. For + information on the modems, see http://www.baycom.de (to browse the + WWW, you need to have access to a machine on the Internet that has a + program like lynx or netscape) and + Documentation/networking/baycom.txt. If you want to compile this + driver as a module ( = code which can be inserted in and removed + from the running kernel whenever you want), say M here and read + Documentation/modules.txt. This is recommended. The module will be + called baycom_ser_fdx.o. BAYCOM ser12 half duplex driver for AX.25 CONFIG_BAYCOM_SER_HDX This is one of two drivers for Baycom style simple amateur radio - modems that connect to a serial interface. The driver supports - the ser12 design in full duplex mode. This is the old driver. - It is still provided in case your serial interface chip does - not work with the full duplex driver. This driver is depreciated. - To configure the driver, use the sethdlc utility available - in the standard ax25 utilities package. For information - on the modems, see http://www.baycom.de and - Documentation/networking/baycom.txt. If you want to compile - this driver as a module ( = code which can be inserted in - and removed from the running kernel whenever you want), - say M here and read Documentation/modules.txt. This is - recommended. The module will be called baycom_ser_hdx.o. + modems that connect to a serial interface. The driver supports the + ser12 design in full duplex mode. This is the old driver. It is + still provided in case your serial interface chip does not work with + the full duplex driver. This driver is depreciated. To configure + the driver, use the sethdlc utility available in the standard ax25 + utilities package. For information on the modems, see + http://www.baycom.de (to browse the WWW, you need to have access to + a machine on the Internet that has a program like lynx or netscape) + and Documentation/networking/baycom.txt. If you want to compile this + driver as a module ( = code which can be inserted in and removed + from the running kernel whenever you want), say M here and read + Documentation/modules.txt. This is recommended. The module will be + called baycom_ser_hdx.o. Soundcard modem driver for AX.25 CONFIG_SOUNDMODEM This experimental driver allows a standard SoundBlaster or WindowsSoundSystem compatible soundcard to be used as a packet radio - modem, to send digital traffic over amateur radio. To configure the - driver, use the sethdlc, smdiag and smmixer utilities available in - the standard ax25 utilities package. For information on how to key - the transmitter, see - http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html and + modem (NOT as a telephone modem!), to send digital traffic over + amateur radio. To configure the driver, use the sethdlc, smdiag and + smmixer utilities available in the standard ax25 utilities + package. For information on how to key the transmitter, see + http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html (to browse + the WWW, you need to have access to a machine on the Internet that + has a program like lynx or netscape) and Documentation/networking/soundmodem.txt. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read @@ -2999,26 +3485,6 @@ CONFIG_SOUNDMODEM_FSK9600 can only use one protocol at a time, depending on what the other end can understand). -Shortwave radio modem driver -CONFIG_HFMODEM - This experimental driver is used by a package (to be released) - that implements the shortwave radio protocols RTTY, Sitor (Amtor), - Pactor 1 and GTOR using a standard PC soundcard. If unsure, - say N. - -Shortwave radio modem driver support for SoundBlaster and compatible cards -CONFIG_HFMODEM_SBC - This option enables the hfmodem driver to use SoundBlaster and - compatible cards. It requires a 16bit capable card, i.e. - SB16 or better, or ESS1688 or newer. - -Shortwave radio modem driver support for WSS and Crystal cards -CONFIG_HFMODEM_WSS - This option enables the hfmodem driver to use WindowsSoundSystem - compatible cards. These cards feature a codec chip from either - Analog Devices (such as AD1848, AD1845, AD1812) or Crystal - Semiconductors (such as CS4248, CS423x). - Serial port KISS driver for AX.25 CONFIG_MKISS KISS is the protocol used to send IP traffic over AX.25 radio @@ -3033,28 +3499,31 @@ CONFIG_MKISS PLIP (parallel port) support CONFIG_PLIP - PLIP (Parallel Line Internet Protocol) is used to create a mini - network consisting of two (or, rarely, more) local machines. The - parallel ports (the connectors at the computers with 25 holes) are - connected using "null printer" or "Turbo Laplink" cables which can - transmit 4 bits at a time or using special PLIP cables, to be used - on bidirectional parallel ports only, which can transmit 8 bits at a - time (you can find the wiring of these cables in - drivers/net/README?.plip). The cables can be up to 15m long. This - works also if one of the machines runs DOS/Windows and has some PLIP - software installed, e.g. the Crynwr PLIP packet driver - (http://sunsite.cnam.fr/packages/Telnet/PC/msdos/misc/pktdrvr.txt) - and winsock or NCSA's telnet. If you want to use this, say Y and - read the PLIP mini-HOWTO, available via ftp (user: anonymous) in - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini as well as the - NET-2-HOWTO in sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the - PLIP protocol was changed and this PLIP driver won't work together - with the PLIP support in Linux versions 1.0.x. This option enlarges - your kernel by about 8kB. If you want to compile this as a module ( - = code which can be inserted in and removed from the running kernel - whenever you want), say M here and read Documentation/modules.txt as - well as Documentation/networking/net-modules.txt. The module will be - called plip.o. + PLIP (Parallel Line Internet Protocol) is used to create a + reasonably fast mini network consisting of two (or, rarely, more) + local machines. The PLIP driver has two modes, mode 0 and mode + 1. The parallel ports (the connectors at the computers with 25 + holes) are connected with "null printer" or "Turbo Laplink" cables + which can transmit 4 bits at a time (mode 0) or with special PLIP + cables, to be used on bidirectional parallel ports only, which can + transmit 8 bits at a time (mode 1); you can find the wiring of these + cables in Documentation/networking/PLIP.txt. The cables can be up to + 15m long. Mode 0 works also if one of the machines runs DOS/Windows + and has some PLIP software installed, e.g. the Crynwr PLIP packet + driver (http://www.kanren.net/pktdrvr-info.html; to browse the WWW, + you need to have access to a machine on the Internet that has a + program like lynx or netscape) and winsock or NCSA's telnet. If you + want to use PLIP, say Y and read the PLIP mini-HOWTO, available via + ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini + as well as the NET-2-HOWTO in + sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the PLIP protocol + was changed and this PLIP driver won't work together with the PLIP + support in Linux versions 1.0.x. This option enlarges your kernel + by about 8kB. If you want to compile this as a module (= code which + can be inserted in and removed from the running kernel whenever you + want), say M here and read Documentation/modules.txt as well as + Documentation/networking/net-modules.txt. The module will be called + plip.o. If unsure, say Y or M, in case you buy a laptop later. EQL (serial line load balancing) support CONFIG_EQUALIZER @@ -3065,11 +3534,32 @@ CONFIG_EQUALIZER like one double speed connection using this driver. Naturally, this has to be supported at the other end as well, either with a similar EQL Linux driver or with a Livingston Portmaster 2e. Say Y if you - want this and read drivers/net/README.eql. This driver is also - available as a module ( = code which can be inserted in and removed - from the running kernel whenever you want). The module will be - called eql.o. If you want to compile it as a module, say M here - and read Documentation/modules.txt. + want this and read Documentation/networking/eql.txt. This driver is + also available as a module ( = code which can be inserted in and + removed from the running kernel whenever you want). The module will + be called eql.o. If you want to compile it as a module, say M here + and read Documentation/modules.txt. If unsure, say N. + +Ethertap network tap +CONFIG_ETHERTAP + If you say Y here (and have said Y to "Kernel/User network link + driver", above) and create a character special file /dev/tap0 with + major number 36 and minor number 16 using mknod ("man mknod"), you + will be able to have a user space program read and write raw + ethernet frames from/to that special file. tap0 can be configured + with ifconfig and route like any other ethernet device but it is not + connected to any physical LAN; everything written by the user to + /dev/tap0 is treated by the kernel as if it had come in from a LAN + to the device tap0; everything the kernel wants to send out over the + device tap0 can instead be read by the user from /dev/tap0: the user + mode program replaces the LAN that would be attached to an ordinary + ethernet device. Please read the file + Documentation/networking/ethertap.txt for more information. This + driver is also available as a module ( = code which can be inserted + in and removed from the running kernel whenever you want). The + module will be called ethertap.o. If you want to compile it as a + module, say M here and read Documentation/modules.txt. If you don't + know what to use this for, you don't need it. Frame Relay (DLCI) support CONFIG_DLCI @@ -3080,16 +3570,15 @@ CONFIG_DLCI network, usually at the phone company) can carry several logical point-to-point connections to other computers connected to the frame relay network. For a general explanation of the protocol, check out - http://frame-relay.indiana.edu/4000/4000index.html on the WWW. (To - browse the WWW, you need to have access to a machine on the Internet - that has a program like lynx or netscape.) To use frame relay, you - need supporting hardware (FRAD) and certain programs from the - net-tools package as explained in - Documentation/networking/framerelay.txt. This driver is also + http://www.frforum.com/ on the WWW. (To browse the WWW, you need to + have access to a machine on the Internet that has a program like + lynx or netscape.) To use frame relay, you need supporting hardware + (FRAD) and certain programs from the net-tools package as explained + in Documentation/networking/framerelay.txt. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be - called dlci.o. If you want to compile it as a module, say M here - and read Documentation/modules.txt. + called dlci.o. If you want to compile it as a module, say M here and + read Documentation/modules.txt. Max open DLCI CONFIG_DLCI_COUNT @@ -3115,6 +3604,109 @@ CONFIG_SDLA sdla.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. +CPU is too slow to handle full bandwidth +CONFIG_CPU_IS_SLOW +### +### How to know when the CPU is too slow? +### + +QoS and/or fair queueing +CONFIG_NET_SCHED + When the kernel has several packets to send out over the network + devices, it has to make a decision which one to send first. This is + especially important if some of the network devices are real time + devices that need a certain minimum data flow rate. There are + several different algorithms how to do this "fairly"; they are + called packet schedulers. You can attach different schedulers to + different network devices. If you want to stick to the default + scheduling algorithm, say N here. If you want to experiment with a + couple of different algorithms, say Y. The available schedulers are + listed in the following questions; you can say Y to as many as you + like. If unsure, say N now. + +CBQ packet scheduler +CONFIG_NET_SCH_CBQ + Say Y here if you want to use the Class-Based Queueing (CBQ) packet + scheduling algorithm for some of your network devices. This + algorithm classifies the waiting packets into a tree-like hierarchy + of classes; the leaves of this tree are in turn scheduled by + separate algorithms (called "disciplines" in this context) which you + can choose below from among the "auxiliary disciplines". See the top + of net/sched/sch_cbq.c for references about the CBQ algorithm. + This code is also available as a + module called sch_cbq.o ( = code which can be inserted in and + removed from the running kernel whenever you want). If you want to + compile it as a module, say M here and read + Documentation/modules.txt. + +CSZ packet scheduler +CONFIG_NET_SCH_CSZ + Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet + scheduling algorithm for some of your network devices. At the + moment, this is the only algorithm that can guarantee service for + real-time applications (see the top of net/sched/sch_csz.c for + details and references about the algorithm). This code is also + available as a module called sch_csz.o ( = code which can be + inserted in and removed from the running kernel whenever you + want). If you want to compile it as a module, say M here and read + Documentation/modules.txt. + +RED queueing discipline +CONFIG_NET_SCH_RED + Say Y here if you want to use the Random Early Detection (RED) + packet scheduling algorithm for some of your network devices (see + the top of net/sched/sch_red.c for details and references about the + algorithm). This code is also available as a module called sch_red.o + ( = code which can be inserted in and removed from the running + kernel whenever you want). If you want to compile it as a module, + say M here and read Documentation/modules.txt. + +SFQ queueing discipline +CONFIG_NET_SCH_SFQ + Say Y here if you want to use the Stochastic Fairness Queueing (SFQ) + packet scheduling algorithm for some of your network devices or as a + leaf discipline for the CBQ scheduling algorithm (see the top of + net/sched/sch_sfq.c for details and references about the SFQ + algorithm). This code is also available as a module called sch_sfq.o + ( = code which can be inserted in and removed from the running + kernel whenever you want). If you want to compile it as a module, + say M here and read Documentation/modules.txt. + +auxiliary TBF queue +CONFIG_NET_SCH_TBF + Say Y here if you want to use the Simple Token Bucket Filter (TBF) + packet scheduling algorithm for some of your network devices or as a + leaf discipline for the CBQ scheduling algorithm (see the top of + net/sched/sch_tbf.c for a description of the TBF algorithm). This code + is also available as a module called sch_tbf.o ( = code which can be + inserted in and removed from the running kernel whenever you + want). If you want to compile it as a module, say M here and read + Documentation/modules.txt. + +auxiliary FIFO queue +CONFIG_NET_SCH_PFIFO + Say Y here if you want to use a simple FIFO (first in - first out) + packet "scheduler" for some of your network devices or as a leaf + discipline for the CBQ scheduling algorithm. This code is also + available as a module called sch_fifo.o ( = code which can be + inserted in and removed from the running kernel whenever you + want). If you want to compile it as a module, say M here and read + Documentation/modules.txt. + +auxiliary PRIO queue +CONFIG_NET_SCH_PRIO + Say Y here if you want to use an n-band priority queue packet + "scheduler" for some of your network devices or as a leaf discipline + for the CBQ scheduling algorithm. This code is also available as a + module called sch_prio.o ( = code which can be inserted in and + removed from the running kernel whenever you want). If you want to + compile it as a module, say M here and read + Documentation/modules.txt. +### +### what user level programs are needed to administrate these packet +### schedulers? +### + WAN Router CONFIG_WAN_ROUTER Wide Area Networks (WANs), such as X.25, frame relay and leased @@ -3122,20 +3714,19 @@ CONFIG_WAN_ROUTER distances with data transfer rates significantly higher than those achievable with commonly used asynchronous modem connections. Usually, a quite expensive external device called `WAN router' is - needed to connect to a WAN. - As an alternative, WAN routing can be built into the Linux - kernel. With relatively inexpensive WAN interface cards available - on the market, a perfectly usable router can be built for less than - half the price of an external router. If you have one of those - cards (with appropriate WAN Link Driver) and wish to use your Linux - box as a WAN router, you may say 'Y' to this option. You will also - need a wan-tools package available via FTP (user: anonymous) from + needed to connect to WAN. + As an alternative, WAN router can be build into Linux kernel. + With relatively inexpensive WAN interface cards available on the + market, a perfectly usable router can be built for less than half a + price of an external router. If you have one of those cards (with + appropriate WAN Link Driver) and wish to use your Linux box as a WAN + router, you may say 'Y' to this option. You will also need a + wan-tools package available via FTP (user: anonymous) from ftp.sangoma.com. Read Documentation/networking/wan-router.txt for more information. - WAN routing is always built as a module ( = code which can be + WAN router is always built as a module ( = code which can be inserted in and removed from the running kernel whenever you want). - The module is called wanrouter.o. For general information about - modules read Documentation/modules.txt. + For general information about modules read Documentation/modules.txt. WAN Drivers CONFIG_WAN_DRIVERS @@ -3149,46 +3740,46 @@ CONFIG_WAN_DRIVERS Sangoma WANPIPE(tm) multiprotocol cards CONFIG_VENDOR_SANGOMA WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com) - is a family of intelligent multiprotocol WAN adapters with data + is a family of intelligent multiprotocol WAN adapter with data transfer rates up to T1 (1.544 Mbps). They are also known as Synchronous Data Link Adapters (SDLA) and designated S502E(A), S503 - or S508. These cards support the X.25, Frame Relay, and PPP - protocols. If you have one or more of these cards, say 'Y' to this - option. The next questions will ask you about the protocols you - want the driver to support. The driver will be compiled as a module - ( = code which can be inserted in and removed from the running - kernel whenever you want). The module will be called wanpipe.o. - For general information about modules read - Documentation/modules.txt. + or S508. If you have one of these cards, say 'Y' to this option. + WANPIPE driver is always built as a module ( = code which can be + inserted in and removed from the running kernel whenever you want). + For general information about modules read Documentation/modules.txt. Maximum number of cards CONFIG_WANPIPE_CARDS Enter number of WANPIPE adapters installed in your machine. The - driver can support up to 8 cards. You may enter more than you + driver can support up to 8 cards. You may enter more that you actually have if you plan to add more cards in the future without re-compiling the driver, but remember that in this case you'll waste some kernel memory (about 1K per card). WANPIPE X.25 support CONFIG_WANPIPE_X25 - Say 'Y' to this option, if you are planning to connect a WANPIPE + Say 'Y' to this option, if you are planning to connect WANPIPE card to an X.25 network. If you say 'N', the X.25 support will not be included in the driver (saves about 16K of kernel memory). WANPIPE Frame Relay support CONFIG_WANPIPE_FR - Say 'Y' to this option, if you are planning to connect a WANPIPE + Say 'Y' to this option, if you are planning to connect WANPIPE card to a frame relay network. If you say 'N', the frame relay support will not be included in the driver (saves about 16K of kernel memory). WANPIPE PPP support CONFIG_WANPIPE_PPP - Say 'Y' to this option, if you are planning to connect a WANPIPE + Say 'Y' to this option, if you are planning to connect WANPIPE card to a leased line using Point-to-Point protocol (PPP). If you say 'N', the PPP support will not be included in the driver (saves about 16K of kernel memory). + + Sun LANCE Ethernet support + CONFIG_SUN_LANCE + This is support for lance ethernet cards on Sun workstations such as Sun LANCE Ethernet support CONFIG_SUN_LANCE This is support for lance ethernet cards on Sun workstations such as @@ -3224,16 +3815,11 @@ Western Digital/SMC cards CONFIG_NET_VENDOR_SMC If you have a network (ethernet) card belonging to this class, say Y and read the Ethernet-HOWTO, available via ftp (user: anonymous) in - sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you plan to use more than - one network card under linux, read the Multiple-Ethernet-mini-HOWTO, - available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. Note that - the answer to this question doesn't directly affect the kernel: + sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the + answer to this question doesn't directly affect the kernel: saying N will just cause this configure script to skip all the questions about Western Digital cards. If you say Y, you will be - asked for your specific card in the following questions. If you plan - to use more than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + asked for your specific card in the following questions. WD80*3 support CONFIG_WD80x3 @@ -3244,10 +3830,7 @@ CONFIG_WD80x3 running kernel whenever you want). The module will be called wd.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. SMC Ultra support CONFIG_ULTRA @@ -3258,39 +3841,89 @@ CONFIG_ULTRA from the running kernel whenever you want). The module will be called smc-ultra.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. Important: There have - been many reports that, with some motherboards mixing an SMC Ultra - and an Adaptec AHA1542 SCSI card causes corruption problems with - many operating systems. + Documentation/networking/net-modules.txt. + Important: There have been many reports that, with some motherboards + mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible, + such as some BusLogic models) causes corruption problems with many + operating systems. The linux smc-ultra driver has a work-around for this + but keep it in mind if you have such a SCSI card and have problems. + +SMC Ultra32 EISA support +CONFIG_ULTRA + If you have a network (ethernet) card of this type, say Y and read + the Ethernet-HOWTO, available via ftp (user: anonymous) in + sunsite.unc.edu:/pub/Linux/docs/HOWTO. This driver is also + available as a module ( = code which can be inserted in and removed + from the running kernel whenever you want). The module will be + called smc-ultra32.o. If you want to compile it as a module, say M + here and read Documentation/modules.txt as well as + Documentation/networking/net-modules.txt. SMC 9194 Support CONFIG_SMC9194 This is support for the SMC9xxx based Ethernet cards. Choose this option if you have a DELL laptop with the docking station, or another SMC9192/9194 based chipset. Say Y if you want it compiled - into the kernel, and read the the file drivers/net/README.smc9 and + into the kernel, and read the the file + Documentation/networking/smc9.txt and the Ethernet-HOWTO, available + via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. + This driver is also available as a module ( = code which can be + inserted in and removed from the running kernel whenever you + want). The module will be called smc9194.o. If you want to compile + it as a module, say M here and read Documentation/modules.txt as + well as Documentation/networking/net-modules.txt. + +Racal-Interlan (Micom) NI cards +CONFIG_NET_VENDOR_RACAL + If you have a network (ethernet) card belonging to this class, such + as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO, + available via ftp (user: anonymous) in + sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the answer + to this question doesn't directly affect the kernel: + saying N will just cause this configure script to skip all the + questions about NI cards. If you say Y, you will be asked for your + specific card in the following questions. + +NI5010 support +CONFIG_NI5010 + If you have a network (ethernet) card of this type, say Y and read the Ethernet-HOWTO, available via ftp (user: anonymous) in - sunsite.unc.edu:/pub/Linux/docs/HOWTO. This driver is also - available as a module ( = code which can be inserted in and removed - from the running kernel whenever you want). The module will be - called smc9194.o. If you want to compile it as a module, say M here - and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that this is still + experimental code. This driver is also available + as a module ( = code which can be inserted in and removed from the + running kernel whenever you want). The module will be called + ni5010.o. If you want to compile it as a module, say M here and read + Documentation/modules.txt as well as + Documentation/networking/net-modules.txt. + +NI5210 support +CONFIG_NI52 + If you have a network (ethernet) card of this type, say Y and read + the Ethernet-HOWTO, available via ftp (user: anonymous) in + sunsite.unc.edu:/pub/Linux/docs/HOWTO. This driver is also available + as a module ( = code which can be inserted in and removed from the + running kernel whenever you want). The module will be called + ni52.o. If you want to compile it as a module, say M here and read + Documentation/modules.txt as well as + Documentation/networking/net-modules.txt. + +NI6510 support +CONFIG_NI65 + If you have a network (ethernet) card of this type, say Y and read + the Ethernet-HOWTO, available via ftp (user: anonymous) in + sunsite.unc.edu:/pub/Linux/docs/HOWTO. This driver is also available + as a module ( = code which can be inserted in and removed from the + running kernel whenever you want). The module will be called + ni65.o. If you want to compile it as a module, say M here and read + Documentation/modules.txt as well as + Documentation/networking/net-modules.txt. AMD LANCE and PCnet (AT1500 and NE2100) support CONFIG_LANCE If you have a network (ethernet) card of this type, say Y and read the Ethernet-HOWTO, available via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. Some LinkSys cards are of - this type. If you plan to use more than one network card under - linux, read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + this type. 3COM cards CONFIG_NET_VENDOR_3COM @@ -3300,9 +3933,7 @@ CONFIG_NET_VENDOR_3COM this question doesn't directly affect the kernel: saying N will just cause this configure script to skip all the questions about 3COM cards. If you say Y, you will be asked for your specific card in the - following questions. If you plan to use more than one network card - under linux, read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + following questions. 3c501 support CONFIG_EL1 @@ -3316,10 +3947,7 @@ CONFIG_EL1 from the running kernel whenever you want). The module will be called 3c501.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini - and don't use 3c501s. + Documentation/networking/net-modules.txt. 3c503 support CONFIG_EL2 @@ -3330,10 +3958,7 @@ CONFIG_EL2 running kernel whenever you want). The module will be called 3c503.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. 3c505 support CONFIG_ELPLUS @@ -3345,9 +3970,7 @@ CONFIG_ELPLUS removed from the running kernel whenever you want), say M here and read Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be called - 3c505.o. If you plan to use more than one network card under linux, - read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + 3c505.o. 3c507 support CONFIG_EL16 @@ -3358,10 +3981,7 @@ CONFIG_EL16 running kernel whenever you want). The module will be called 3c507.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. 3c523 support CONFIG_ELMC @@ -3372,10 +3992,7 @@ CONFIG_ELMC running kernel whenever you want). The module will be called 3c523.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. 3c509/3c579 support CONFIG_EL3 @@ -3386,11 +4003,8 @@ CONFIG_EL3 inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be called - 3c509.o. If you plan to use more than one network card under linux, - read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. If your card is not - working you may need to use the DOS setup disk to disable Plug & - Play mode, and to select the default media type. + 3c509.o. If your card is not working you may need to use the DOS setup + disk to disable Plug & Play mode, and to select the default media type. 3c590 series (592/595/597) "Vortex" support CONFIG_VORTEX @@ -3403,9 +4017,7 @@ CONFIG_VORTEX running kernel whenever you want), say M here and read Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be called - 3c59x.o. If you plan to use more than one network card under linux, - read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini + 3c59x.o. Other ISA cards CONFIG_NET_ISA @@ -3418,9 +4030,7 @@ CONFIG_NET_ISA directly affect the kernel: saying N will just cause this configure script to skip all the remaining ISA network card questions. If you say Y, you will be asked for your specific card in the following - questions. If you plan to use more than one network card under - linux, read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + questions. Generic ARCnet support CONFIG_ARCNET @@ -3428,7 +4038,7 @@ CONFIG_ARCNET (arguably) beautiful poetry in Documentation/networking/arcnet.txt. You need both this driver, and the driver for the particular ARCnet chipset of your card. If you don't know, then it's probably a - COM90xx type card, so say Y (or M) to ARCnet COM90xx chipset support + COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset support" below. You might also want to have a look at the Ethernet-HOWTO, available via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO @@ -3437,11 +4047,8 @@ CONFIG_ARCNET from the running kernel whenever you want). The module will be called arcnet.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. - + Documentation/networking/net-modules.txt. + Enable arc0e (ARCnet "ether-encap" packet format) CONFIG_ARCNET_ETH This allows you to use "ethernet encapsulation" with your ARCnet @@ -3467,30 +4074,50 @@ CONFIG_ARCNET_1051 documentation in Documentation/networking/arcnet.txt for more information about using arc0e and arc0s. -ARCnet COM90xx chipset support +ARCnet COM90xx (normal) chipset driver CONFIG_ARCNET_COM90xx - This is the chipset driver for the standard COM90xx cards. If you always - used the old arcnet driver without knowing what type of card you had, - this is probably the one for you. + This is the chipset driver for the standard COM90xx cards. If you + have always used the old arcnet driver without knowing what type of + card you had, this is probably the one for you. This driver is also + available as a module ( = code which can be inserted in and removed + from the running kernel whenever you want). The module will be + called com90xx.o. If you want to compile it as a module, say M here + and read Documentation/modules.txt as well as + Documentation/networking/net-modules.txt. -ARCnet COM90xx IO mapped mode chipset support -CONFIG_ARCNET_COM90xxIO - This is the chipset driver for the COM90xx cards, using them in IO-mapped - mode instead of memory-mapped mode. This is slower than the normal driver. - Only use it if your card doesn't support shared memory. +ARCnet COM90xx (IO mapped) chipset driver +CONFIG_ARCNET_COM90x + This is the chipset driver for the COM90xx cards, using them in + IO-mapped mode instead of memory-mapped mode. This is slower than + the normal driver. Only use it if your card doesn't support shared + memory. This driver is also available as a module ( = code which can + be inserted in and removed from the running kernel whenever you + want). The module will be called com90io.o. If you want to compile + it as a module, say M here and read Documentation/modules.txt as + well as Documentation/networking/net-modules.txt. -ARCnet RIM I chipset support +ARCnet COM90xx (RIM I) chipset driver CONFIG_ARCNET_RIM_I - This is yet another chipset driver for the COM90xx cards, but this time - only using memory-mapped mode, and no IO ports at all. This driver is - completely untested, so if you have one of these cards, please mail - dwmw2@cam.ac.uk, especially if it works! + This is yet another chipset driver for the COM90xx cards, but this + time only using memory-mapped mode, and no IO ports at all. This + driver is completely untested, so if you have one of these cards, + please mail dwmw2@cam.ac.uk, especially if it works! + This driver is also available as a module ( = code which can be + inserted in and removed from the running kernel whenever you + want). The module will be called arc-rimi.o. If you want to compile + it as a module, say M here and read Documentation/modules.txt as + well as Documentation/networking/net-modules.txt. -ARCnet COM20020 chipset support +ARCnet COM20020 chipset driver CONFIG_ARCNET_COM20020 - This is the driver for the new COM20020 chipset. It supports such things - as promiscuous mode, so packet sniffing is possible, and extra diagnostic - information. + This is the driver for the new COM20020 chipset. It supports such + things as promiscuous mode, so packet sniffing is possible, and + extra diagnostic information. This driver is also available as a + module ( = code which can be inserted in and removed from the + running kernel whenever you want). The module will be called + com20020.o. If you want to compile it as a module, say M here and + read Documentation/modules.txt as well as + Documentation/networking/net-modules.txt. Cabletron E21xx support CONFIG_E2100 @@ -3501,10 +4128,7 @@ CONFIG_E2100 running kernel whenever you want). The module will be called e2100.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. CS89x0 support CONFIG_CS89x0 @@ -3517,9 +4141,7 @@ CONFIG_CS89x0 running kernel whenever you want), say M here and read Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be called - cs89x.o. If you plan to use more than one network card under linux, - read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + cs89x.o. DEPCA support CONFIG_DEPCA @@ -3530,32 +4152,26 @@ CONFIG_DEPCA code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be - called depca.o. If you plan to use more than one network card under - linux, read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + called depca.o. EtherWorks 3 support CONFIG_EWRK3 This driver supports the DE203, DE204 and DE205 network (ethernet) - cards. If this is for you, say Y and read drivers/net/README.ewrk3 - in the kernel source as well as the Ethernet-HOWTO, available via - ftp (user: anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO. - If you want to compile this as a module ( = code which can be - inserted in and removed from the running kernel whenever you want), - say M here and read Documentation/modules.txt as well as + cards. If this is for you, say Y and read + Documentation/networking/ewrk3.txt in the kernel source as well as + the Ethernet-HOWTO, available via ftp (user: anonymous) from + sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you want to compile this + as a module ( = code which can be inserted in and removed from the + running kernel whenever you want), say M here and read + Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be called - ewrk3.o. If you plan to use more than one network card under linux, - read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + ewrk3.o. SEEQ8005 support CONFIG_SEEQ8005 This is a driver for the SEEQ 8005 network (ethernet) card. If this is for you, read the Ethernet-HOWTO, available via ftp (user: - anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you plan - to use more than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO. AT1700 support CONFIG_AT1700 @@ -3566,9 +4182,7 @@ CONFIG_AT1700 running kernel whenever you want). If you want to compile it as a module, say M here and read Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be called - at1700.o. If you plan to use more than one network card under linux, - read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + at1700.o. FMV-181/182/183/184 support CONFIG_FMV18X @@ -3579,10 +4193,7 @@ CONFIG_FMV18X removed from the running kernel whenever you want). The module will be called fmv18x.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. If you use FMV-183 or + Documentation/networking/net-modules.txt. If you use FMV-183 or FMV-184 and it is not working, you may need to disable Plug & Play mode of the card. @@ -3596,10 +4207,7 @@ CONFIG_EEXPRESS_PRO in and removed from the running kernel whenever you want). The module will be called eepro.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. EtherExpress support CONFIG_EEXPRESS @@ -3613,43 +4221,7 @@ CONFIG_EEXPRESS running kernel whenever you want), say M here and read Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be called - eexpress.o. If you plan to use more than one network card under - linux, read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. - -NI5010 support -CONFIG_NI5010 - If you have a network (ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available via ftp (user: anonymous) in - sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you plan to use more than - one network card under linux, read the Multiple-Ethernet-mini-HOWTO, - available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. - Note that this is still experimental code. If you use this driver, - please contact the authors to join the development team. - -NI5210 support -CONFIG_NI52 - If you have a network (ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available via ftp (user: anonymous) in - sunsite.unc.edu:/pub/Linux/docs/HOWTO. This driver is also available - as a module ( = code which can be inserted in and removed from the - running kernel whenever you want). The module will be called - ni52.o. If you want to compile it as a module, say M here and read - Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more than - one network card under linux, read the Multiple-Ethernet-mini-HOWTO, - available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. - -NI6510 support -CONFIG_NI65 - If you have a network (ethernet) card of this type, say Y and read - the Ethernet-HOWTO, available via ftp (user: anonymous) in - sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you want to compile it as - a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. The module will be called - ni65.o. If you plan to use more than one network card under linux, - read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + eexpress.o. AT&T WaveLAN & DEC RoamAbout DS support CONFIG_WAVELAN @@ -3662,17 +4234,15 @@ CONFIG_WAVELAN If you want to use a card of this type under Linux, say Y and read the Ethernet-HOWTO, available via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. Some more specific - information is contained in drivers/net/README.wavelan. You will - also need the wireless tools package available from + information is contained in + Documentation/networking/wavelan.txt. You will also need the + wireless tools package available from ftp://ftp.inka.de/pub/comp/Linux/networking/NetTools/contrib/. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called wavelan.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as - well as Documentation/networking/net-modules.txt. If you plan to use - more than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + well as Documentation/networking/net-modules.txt. HP PCLAN+ (27247B and 27252A) support CONFIG_HPLAN_PLUS @@ -3683,10 +4253,7 @@ CONFIG_HPLAN_PLUS running kernel whenever you want). The module will be called hp-plus.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. HP PCLAN (27245 and other 27xxx series) support CONFIG_HPLAN @@ -3697,10 +4264,7 @@ CONFIG_HPLAN running kernel whenever you want). The module will be called hp.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. HP 10/100VG PCLAN (ISA, EISA, PCI) support CONFIG_HP100 @@ -3711,9 +4275,7 @@ CONFIG_HP100 running kernel whenever you want), say M here and read Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be called - hp100.o. If you plan to use more than one network card under linux, - read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + hp100.o. NE2000/NE1000 support CONFIG_NE2000 @@ -3725,41 +4287,31 @@ CONFIG_NE2000 from the running kernel whenever you want). The module will be called ne.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. SK_G16 support CONFIG_SK_G16 If you have a network (ethernet) card of this type, say Y and read the Ethernet-HOWTO, available via ftp (user: anonymous) in - sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you plan to use more than - one network card under linux, read the Multiple-Ethernet-mini-HOWTO, - available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + sunsite.unc.edu:/pub/Linux/docs/HOWTO. EISA, VLB, PCI and on board controllers CONFIG_NET_EISA This is another class of network cards which attach directly to the bus. If you have one of those, say Y and read the Ethernet-HOWTO, available via ftp (user: anonymous) from - sunsite.unc.edu:/pub/Linux/docs/HOWTO; if you are unsure, say - Y. Note that the answer to this question doesn't directly affect the - kernel: saying N will just cause this configure script to skip all - the questions about this class of network cards. If you say Y, you - will be asked for your specific card in the following questions. If - you plan to use more than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you are unsure, say Y. + Note that the answer to this question doesn't + directly affect the kernel: saying N will just cause this configure + script to skip all the questions about this class of network + cards. If you say Y, you will be asked for your specific card in the + following questions. AMD PCnet32 (VLB and PCI) support CONFIG_PCNET32 - if you have a PCnet32 or PCnetPCI based network (ethernet) card, say + If you have a PCnet32 or PCnetPCI based network (ethernet) card, say Y here and read the Ethernet-HOWTO, available via ftp (user: - anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you plan to - use more than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. Ansel Communications EISA 3200 support CONFIG_AC3200 @@ -3770,10 +4322,7 @@ CONFIG_AC3200 running kernel whenever you want). The module will be called ac3200.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. Racal-Interlan EISA ES3210 support CONFIG_ES3210 @@ -3784,10 +4333,7 @@ CONFIG_ES3210 running kernel whenever you want). The module will be called es3210.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. Apricot Xen-II on board ethernet CONFIG_APRICOT @@ -3798,9 +4344,7 @@ CONFIG_APRICOT running kernel whenever you want), say M here and read Documentation/modules.txt as well as Documentation/networking/net-modules.txt. The module will be called - apricot.o. If you plan to use more than one network card under - linux, read the Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + apricot.o. Generic DECchip & DIGITAL EtherWORKS PCI/EISA CONFIG_DE4X5 @@ -3809,15 +4353,12 @@ CONFIG_DE4X5 models. If you have a network card of this type, say Y and read the Ethernet-HOWTO, available via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. More specific information is - contained in drivers/net/README.de4x5. This driver is also available - as a module ( = code which can be inserted in and removed from the - running kernel whenever you want). The module will be called - de4x5.o. If you want to compile it as a module, say M here and read - Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + contained in Documentation/networking/de4x5.txt. This driver is also + available as a module ( = code which can be inserted in and removed + from the running kernel whenever you want). The module will be + called de4x5.o. If you want to compile it as a module, say M here + and read Documentation/modules.txt as well as + Documentation/networking/net-modules.txt. DECchip Tulip (dc21x4x) PCI support CONFIG_DEC_ELCP @@ -3844,15 +4385,12 @@ CONFIG_DGRS models. If you have a network card of this type, say Y and read the Ethernet-HOWTO, available via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. More specific information is - contained in drivers/net/README.dgrs. This driver is also available - as a module ( = code which can be inserted in and removed from the - running kernel whenever you want). The module will be called - dgrs.o. If you want to compile it as a module, say M here and read - Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + contained in Documentation/networking/dgrs.txt. This driver is also + available as a module ( = code which can be inserted in and removed + from the running kernel whenever you want). The module will be + called dgrs.o. If you want to compile it as a module, say M here and + read Documentation/modules.txt as well as + Documentation/networking/net-modules.txt. EtherExpressPro/100 support CONFIG_EEXPRESS_PRO100 @@ -3863,10 +4401,7 @@ CONFIG_EEXPRESS_PRO100 removed from the running kernel whenever you want). The module will be called eepro100.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. ICL EtherTeam 16i/32 support CONFIG_ETH16I @@ -3877,10 +4412,7 @@ CONFIG_ETH16I running kernel whenever you want). The module will be called eth16i.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as - Documentation/networking/net-modules.txt. If you plan to use more - than one network card under linux, read the - Multiple-Ethernet-mini-HOWTO, available from - sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + Documentation/networking/net-modules.txt. TI ThunderLAN support (EXPERIMENTAL) CONFIG_TLAN @@ -3932,33 +4464,29 @@ CONFIG_ATP D-Link DE600 pocket adapter support CONFIG_DE600 This is a network (ethernet) device which attaches to your parallel - port. Read drivers/net/README.DLINK as well as the Ethernet-HOWTO, - available via ftp (user: anonymous) from + port. Read Documentation/networking/DLINK.txt as well as the + Ethernet-HOWTO, available via ftp (user: anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO if you want to use this. It is possible to have several devices share a single parallel port and it is safe to compile the corresponding drivers into the kernel. If you want to compile this driver as a module however ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module - will be called de600.o. If you plan to use more than one network - card under linux, read the Multiple-Ethernet-mini-HOWTO, available - from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + will be called de600.o. D-Link DE620 pocket adapter support CONFIG_DE620 This is a network (ethernet) device which attaches to your parallel - port. Read drivers/net/README.DLINK as well as the Ethernet-HOWTO, - available via ftp (user: anonymous) from + port. Read Documentation/networking/DLINK.txt as well as the + Ethernet-HOWTO, available via ftp (user: anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO if you want to use this. It is possible to have several devices share a single parallel port and it is safe to compile the corresponding drivers into the kernel. If you want to compile this driver as a module however ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module - will be called de620.o. If you plan to use more than one network - card under linux, read the Multiple-Ethernet-mini-HOWTO, available - from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. - + will be called de620.o. + Token Ring driver support CONFIG_TR Token Ring is IBM's way of communication on a local network; the @@ -4019,9 +4547,9 @@ CONFIG_CD_NO_IDESCSI For each of these drivers, a file Documentation/cdrom/<driver_name> exists. Especially in cases where you do not know exactly which kind of drive you have you should read there. - Most of these drivers use a file drivers/cdrom/<driver_name>.h where - you can define your interface parameters and switch some internal - goodies. + Most of these drivers use a file drivers/cdrom/<driver_name>.h + where you can define your interface parameters and switch some + internal goodies. All these CDROM drivers are also usable as a module (= code which can be inserted in and removed from the running kernel whenever you want). If you want to compile them as module, say M instead of Y and read @@ -4037,7 +4565,7 @@ CONFIG_CDU31A will not be auto detected by the kernel at boot time; you have to provide the interface address as an option to the kernel at boot time as described in Documentation/cdrom/cdu31a or fill in your - parameters into linux/drivers/cdrom/cdu31a.c. Try "man bootparam" or + parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or see the documentation of your boot loader (lilo or loadlin) about how to pass options to the kernel. The lilo procedure is also explained in the SCSI-HOWTO. If you say Y here, you should also say @@ -4060,7 +4588,7 @@ CONFIG_MCD (PhotoCDs). There is a new driver (next question) which can do this. If you want that one, say N here. If the driver doesn't work out of the box, you might want to have a - look at linux/drivers/cdrom/mcd.h. If you say Y here, you should + look at drivers/cdrom/mcd.h. If you say Y here, you should also say Y to "ISO9660 cdrom filesystem support" below, because that's the filesystem used on CDROMs. Please also read the file Documentation/cdrom/mcd. This driver is also available as a module ( @@ -4104,7 +4632,7 @@ CONFIG_SBPCD are not sure, but can consume some time during the boot process if none of the supported drives gets found. Once your drive got found, you should enter the reported parameters - into linux/drivers/cdrom/sbpcd.h and set "DISTRIBUTION 0" there. + into drivers/cdrom/sbpcd.h and set "DISTRIBUTION 0" there. This driver can support up to four CDROM interface cards, and each card can support up to four CDROM drives; if you say Y here, you will be asked how many controllers you have. If compiled as a @@ -4123,7 +4651,7 @@ CONFIG_SBPCD2 Say Y here only if you have two CDROM controller boards of this type (usually only if you have more than four drives). You should enter the parameters for the second, third and fourth interface card into - linux/drivers/cdrom/sbpcd.h before compiling the new kernel. Read + linux/include/linux/sbpcd.h before compiling the new kernel. Read the file Documentation/cdrom/sbpcd. Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support @@ -4155,29 +4683,14 @@ Goldstar R420 CDROM support CONFIG_GSCD If this is your CDROM drive, say Y here. As described in linux/Documentation/cdrom/gscd, you might have to change a setting - in the file linux/drivers/cdrom/gscd.h before compiling the kernel. - Please read the file Documentation/cdrom/gscd. If you say Y here, - you should also say Y to "ISO9660 cdrom filesystem support" below, - because that's the filesystem used on CDROMs. This driver is also - available as a module ( = code which can be inserted in and removed - from the running kernel whenever you want). The module will be - called gscd.o. If you want to compile it as a module, say M here and - read Documentation/modules.txt. - -MicroSolutions backpack CDROM support -CONFIG_BPCD - MicroSolutions backpack CDROM is an external drive that connects to - the parallel port. This driver supports model 164550 (and perhaps - other models). Say Y if you have one of these, and read the file - Documentation/cdrom/bpcd. If you say Y here, you should also say Y - to "ISO9660 cdrom filesystem support" below, because that's the - filesystem used on CDROMs. It is possible for several devices to - share a parallel port and it is safe to compile the corresponding - drivers all into the kernel. This driver is also available as a - module ( = code which can be inserted in and removed from the - running kernel whenever you want). The module will be called - bpcd.o. If you want to compile it as a module, say M here and read - Documentation/modules.txt. + in the file linux/drivers/cdrom/gscd.h before compiling the + kernel. Please read the file Documentation/cdrom/gscd. If you say Y + here, you should also say Y to "ISO9660 cdrom filesystem support" + below, because that's the filesystem used on CDROMs. This driver is + also available as a module ( = code which can be inserted in and + removed from the running kernel whenever you want). The module will + be called gscd.o. If you want to compile it as a module, say M here + and read Documentation/modules.txt. Philips/LMS CM206 CDROM support CONFIG_CM206 @@ -4251,10 +4764,10 @@ CONFIG_QUOTA If you say Y here, you will be able to set per user limits for disk usage (also called diskquotas). Currently, it works only for the ext2 filesystem. You need additional software in order to use quota - support; it is available via ftp (user: anonymous) from - ftp.funet.fi/pub/Linux/kernel/src/subsystems/quota/. Probably the - quota support is only useful for multi user systems. If unsure, say - N. + support; for details, read the Quota mini-HOWTO, available via ftp + (user: anonymous) in + sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. Probably the quota + support is only useful for multi user systems. If unsure, say N. Online mirror support CONFIG_OMIRR @@ -4449,6 +4962,33 @@ CONFIG_EXT2_FS compiled as a module, and so this could be dangerous. Most everyone wants to say Y here. +ISO9660 cdrom filesystem support +CONFIG_ISO9660_FS + This is the standard filesystem used on CDROMs. It was previously + known as "High Sierra Filesystem" and is called "hsfs" on other Unix + systems. The so-called Rock-Ridge extensions which allow for long + Unix filenames and symbolic links are also supported by this + driver. If you have a CDROM drive and want to do more with it than + just listen to audio CDs and watch its LEDs, say Y (and read + Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available + via ftp (user: anonymous) from + sunsite.unc.edu:/pub/Linux/docs/HOWTO), thereby enlarging your + kernel by about 27 kB; otherwise say N. If you want to compile this + as a module ( = code which can be inserted in and removed from the + running kernel whenever you want), say M here and read + Documentation/modules.txt. The module will be called isofs.o. + +Microsoft Joliet cdrom extensions +CONFIG_JOLIET + Joliet is a Microsoft extension for the ISO9660 CDROM filesystem + which allows for long filenames in unicode format (unicode is the + new 16 bit character code, successor to ASCII, which encodes the + characters of almost all languages of the world; see + http://www.unicode.org for more information; to browse the WWW, you + need to have access to a machine on the Internet that has a program + like lynx or netscape). Say Y here if you want to be able to read + Joliet CDROMs under Linux. + fat fs support CONFIG_FAT_FS If you want to use one of the FAT-based filesystems (the MS-DOS, @@ -4473,7 +5013,7 @@ CONFIG_MSDOS_FS Linux, you can either use the DOS emulator DOSEMU, described in the DOSEMU-HOWTO, available via ftp (user: anonymous) at sunsite.unc.edu:/pub/Linux/docs/HOWTO, or try dmsdosfs in - sunsite.unc.edu:/pub/Linux/system/Filesystems/dosfs. If you intend + sunsite.unc.edu:/pub/Linux/system/filesystems/dosfs. If you intend to use dosemu with a non-compressed MSDOS partition, say Y here) and MSDOS floppies. This means that file access becomes transparent, i.e. the MSDOS files look and behave just like all other Unix files. @@ -4529,154 +5069,6 @@ CONFIG_UMSDOS_FS umsdos.o. Note that the filesystem of your root partition cannot be a module, so this could be dangerous. If unsure, say N. -nls: Native language codepages and Unicode support -CONFIG_NLS - This is required by the FAT filesystems and by the ISO9660 filesystem - when it is compiled with Joliet support. Joliet is a Microsoft - extension for CDROMs that supports Unicode. This allows translation - between different character sets. When dealing with the FAT based - filesystems, there are two character sets that are important. The - first is the codepage. Codepages are character sets that are used by - DOS to allow filenames to have native language characters when - character sets were limited to 256 characters. The codepage is the - character set that is used to store native language characters on - disk. The two most common codepages are 437 in the United States and - 850 in much of Europe. The second important character set is the - input/output character set. This is the character set that is - displayed on the screen. In the United States, this will almost always - be the ISO 8859-1 character set. This is the default. Linux will only - do a translation of the FAT filenames, not the contents of the files. - -nls iso8859-1 -CONFIG_NLS_ISO8859_1 - ISO8859-1 is the Latin 1 character set, and it covers most West - European languages such as Albanian, Catalan, Danish, Dutch, English, - Faeroese, Finnish, French, German, Galician, Irish, Icelandic, Italian, - Norwegian, Portuguese, Spanish, Swedish, and Valencian. - -nls iso8859-2 -CONFIG_NLS_ISO8859_2 - ISO8859-2 is the Latin 2 character set, and it works for most - Latin-written Slavic and Central European languages: Czech, German, - Hungarian, Polish, Rumanian, Croatian, Slovak, Slovene. - -nls iso8859-3 -CONFIG_NLS_ISO8859_3 - ISO8859-3 is the Latin 3 character set, and it s popular with authors - of Esperanto, Galician, Maltese, and Turkish. - -nls iso8859-4 -CONFIG_NLS_ISO8859_4 - ISO8859-4 is the Latin 4 character set, and it introduces letters - for Estonian, Latvian, and Lithuanian. It is an incomplete predecessor of - Latin 6. - -nls iso8859-5 -CONFIG_NLS_ISO8859_5 - ISO8859-5 is a Cyrillic character set, and you can type Bulgarian, - Byelorussian, Macedonian, Russian, Serbian, and Ukrainian. - Note that the charset KOI8-R is preferred in Russia. - -nls iso8859-6 -CONFIG_NLS_ISO8859_6 - ISO8859-6 is the Arabic character set. - -nls iso8859-7 -CONFIG_NLS_ISO8859_7 - ISO8859-7 is the Modern Greek character set. - -nls iso8859-8 -CONFIG_NLS_ISO8859_8 - ISO8859-8 is the Hebrew character set. - -nls iso8859-9 -CONFIG_NLS_ISO8859_9 - ISO8859-9 is the Latin 5 character set, and it replaces the rarely - needed Icelandic letters in Latin 1 with the Turkish ones. Useful in - Turkey. - -nls iso8859-10 -CONFIG_NLS_ISO8859_10 - ISO8859-10 is the Latin 6 character set, and it adds the last Inuit - (Greenlandic) and Sami (Lappish) letters that were missing in Latin 4 to - cover the entire Nordic area. - -nls koi8-r -CONFIG_NLS_KOI8_R - This is the preferred Russian character set. - -nls codepage 437 -CONFIG_NLS_CODEPAGE_437 - This is the DOS codepage that is used in the United States and parts of - Canada. - -nls codepage 737 -CONFIG_NLS_CODEPAGE_737 - This is the codepage used by DOS for Greek. - -nls codepage 775 -CONFIG_NLS_CODEPAGE_775 - This is the codepage used by DOS for the Baltic Rim Languages. - -nls codepage 850 -CONFIG_NLS_CODEPAGE_850 - This is the DOS codepage that is used in much of Europe--United Kingdom, - Germany, Spain, Italy, and [add more countries here]. It has some - characters useful to many European languages that are not part of - codepage 437. - -nls codepage 852 -CONFIG_NLS_CODEPAGE_852 - This is the Latin 2 codepage used by DOS for much of Central and - Eastern Europe. It has all the required characters for these languages: - Albanian, Croatian, Czech, English, Finnish, Hungarian, Irish, German, - Polish, Romanian, Serbian (Latin transcription), Slovak, Slovenian, and - Sorbian. - -nls codepage 855 -CONFIG_NLS_CODEPAGE_855 - This is the DOS codepage that is used for Cyrillic. - -nls codepage 857 -CONFIG_NLS_CODEPAGE_857 - This is the DOS codepage that is used for Turkish. - -nls codepage 860 -CONFIG_NLS_CODEPAGE_860 - This is the DOS codepage that is used for Portuguese. - -nls codepage 861 -CONFIG_NLS_CODEPAGE_861 - This is the DOS codepage that is used for Icelandic. - -nls codepage 862 -CONFIG_NLS_CODEPAGE_862 - This is the DOS codepage that is used for Hebrew. - -nls codepage 863 -CONFIG_NLS_CODEPAGE_863 - This is the DOS codepage that is used for Canadian French. - -nls codepage 864 -CONFIG_NLS_CODEPAGE_864 - This is the DOS codepage that is used for Arabic. - -nls codepage 865 -CONFIG_NLS_CODEPAGE_865 - This is the DOS codepage that is used in the Nordic European countries. - -nls codepage 866 -CONFIG_NLS_CODEPAGE_866 - This is the DOS codepage that is used for Cyrillic/Russian. - -nls codepage 869 -CONFIG_NLS_CODEPAGE_869 - This is the DOS codepage that is used for Greek. - -nls codepage 874 -CONFIG_NLS_CODEPAGE_874 - This is the DOS codepage that is used for Thai. - /proc filesystem support CONFIG_PROC_FS This is a virtual filesystem providing information about the status @@ -4685,16 +5077,17 @@ CONFIG_PROC_FS them. Also, you cannot read the files with less: you need to use more or cat. The filesystem is explained in the Kernel Hacker's Guide at http://www.redhat.com:8080/HyperNews/get/khg.html on the - Web, and also on the proc(8) manpage ("man 8 proc"). This option - will enlarge your kernel by about 18 kB. It's totally cool; for - example, "cat /proc/interrupts" gives information about what the - different IRQs are used for at the moment (there is a small number - of Interrupt ReQuest lines in your computer that are used by the - attached devices to gain the CPU's attention - often a source of - trouble if two devices are mistakenly configured to use the same - IRQ). Several programs depend on this, so everyone should say Y - here. - + WWW (to browse the WWW, you need to have access to a machine on the + Internet that has a program like lynx or netscape), and also on the + proc(8) manpage ("man 8 proc"). This option will enlarge your + kernel by about 18 kB. It's totally cool; for example, "cat + /proc/interrupts" gives information about what the different IRQs + are used for at the moment (there is a small number of Interrupt + ReQuest lines in your computer that are used by the attached devices + to gain the CPU's attention - often a source of trouble if two + devices are mistakenly configured to use the same IRQ). Several + programs depend on this, so everyone should say Y here. + NFS filesystem support CONFIG_NFS_FS If you are connected to some other (usually local) Unix computer @@ -4718,7 +5111,7 @@ CONFIG_NFS_FS Documentation/modules.txt. If you configure a diskless machine which will mount its root filesystem over nfs (in order to do that, check out the netboot package, available via ftp (user: anonymous) from - sunsite.unc.edu in /pub/Linux/system/Linux-boot/, extract with "tar + sunsite.unc.edu in /pub/Linux/system/boot/ethernet/, extract with "tar xzvf filename", and say Y to "Root file system on NFS" below), then you cannot compile this driver as a module. If you don't know what all this is about, say N. @@ -4747,20 +5140,28 @@ CONFIG_NFSD module, say M here and read Documentation/modules.txt. If unsure, say N. -ISO9660 cdrom filesystem support -CONFIG_ISO9660_FS - This is the standard filesystem used on CDROMs. It was previously - known as "High Sierra Filesystem" and is called "hsfs" on other Unix - systems. The so-called Rock-Ridge extensions which allow for long - Unix filenames are also supported by this driver. If you have a - CDROM drive and want to do more with it than just listen to audio - CDs and watch its LEDs, say Y (and read the CDROM-HOWTO, available - via ftp (user: anonymous) from - sunsite.unc.edu:/pub/Linux/docs/HOWTO), thereby enlarging your - kernel by about 27 kB; otherwise say N. If you want to compile this - as a module ( = code which can be inserted in and removed from the - running kernel whenever you want), say M here and read - Documentation/modules.txt. The module will be called isofs.o. +BOOTP support +CONFIG_RNFS_BOOTP + If you want your Linux box to mount its whole root filesystem from + some other computer over the net via NFS and you want the IP address + of your computer to be discovered automatically at boot time using + the BOOTP protocol (a special protocol designed for doing this job), + say Y here. In case the boot ROM of your network card was designed + for booting Linux and does BOOTP itself, providing all necessary + information on the kernel command line, you can say N here. If + unsure, say Y. Note that in case you want to use BOOTP, a BOOTP + server must be operating on your network. Read + Documentation/nfsroot.txt for details. + +RARP support +CONFIG_RNFS_RARP + If you want your Linux box to mount its whole root filesystem from + some other computer over the net via NFS and you want the IP address + of your computer to be discovered automatically at boot time using + the RARP protocol (an older protocol which is being obsoleted by + BOOTP and DHCP), say Y here. Note that in case you want to use RARP, + a RARP server must be operating on your network. Read + Documentation/nfsroot.txt for details. OS/2 HPFS filesystem support (read only) CONFIG_HPFS_FS @@ -4775,7 +5176,27 @@ CONFIG_HPFS_FS want). The module is called hpfs.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. - + +Windows NT NTFS support (read only) +CONFIG_NTFS_FS + NTFS is the file system of Microsoft Windows NT. Say Y if you want + to access partitions using this file system. The Linux NTFS driver + supports most of the mount options of the VFAT driver, see + Documentation/filesystems/ntfs.txt. Saying Y here will give you + read-only access to NTFS partitions. This code is also + available as a module ( = code which can be inserted in and removed + from the running kernel whenever you want). The module will be + called ntfs.o. If you want to compile it as a module, say M here + and read Documentation/modules.txt. + +NTFS read-write support (experimental) +CONFIG_NTFS_RW + If you say Y here, you will (hopefully) be able to write to NTFS + file systems as well as to read from them. The read-write support + in NTFS is far from being complete and is not well tested. If you + enable this, be prepared to recover the NTFS volume from tape. If + unsure, say N. + System V and Coherent filesystem support CONFIG_SYSV_FS SCO, Xenix and Coherent are commercial Unix systems for intel @@ -4793,15 +5214,15 @@ CONFIG_SYSV_FS nfs filesystem support obviously). Note that this option is generally not needed for floppies, since a good portable way to transport files and directories between unixes (and even other - operating systems) is given by the tar program ("man tar"). Note - also that this option has nothing whatsoever to do with the option - "System V IPC". Read about the System V filesystem in - Documentation/filesystems/sysv-fs.txt. This option will enlarge your - kernel by about 34 kB. If you want to compile this as a module ( = - code which can be inserted in and removed from the running kernel - whenever you want), say M here and read - Documentation/modules.txt. The module will be called sysv.o. If you - haven't heard about all of this before, it's safe to say N. + operating systems) is given by the tar program ("man tar" or + preferably "info tar"). Note also that this option has nothing + whatsoever to do with the option "System V IPC". Read about the + System V filesystem in Documentation/filesystems/sysv-fs.txt. This + option will enlarge your kernel by about 34 kB. If you want to + compile this as a module ( = code which can be inserted in and + removed from the running kernel whenever you want), say M here and + read Documentation/modules.txt. The module will be called sysv.o. If + you haven't heard about all of this before, it's safe to say N. Kernel automounter support (experimental) CONFIG_AUTOFS_FS @@ -4822,42 +5243,54 @@ BSD UFS filesystem support (read only) CONFIG_UFS_FS BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD and NeXTstep) use a filesystem called UFS. Some System V Unixes can - create and mount partitions and diskettes using this filesystem as - well. Saying Y here allows you to mount these partitions and - diskettes read-only. If you only intend to mount files from some - other Unix over the network using NFS, you don't need the UFS - filesystem support (but you need nfs filesystem support + create and mount harddisk partitions and diskettes using this + filesystem as well. Saying Y here allows you to mount these + partitions and diskettes read-only. If you only intend to mount + files from some other Unix over the network using NFS, you don't + need the UFS filesystem support (but you need nfs filesystem support obviously). Note that this option is generally not needed for floppies, since a good portable way to transport files and directories between unixes (and even other operating systems) is - given by the tar program ("man tar"). When accessing NeXTstep files, - you may need to convert them from the NeXT character set to the - Latin1 character set; use GNU recode for this purpose. Say Y to - build UFS support into your kernel. If you want to compile this as a - module ( = code which can be inserted in and removed from the - running kernel whenever you want), say M here and read - Documentation/modules.txt. The module will be called ufs.o. If you - haven't heard about all of this before, it's safe to say N. + given by the tar program ("man tar" or preferably "info tar"). When + accessing NeXTstep files, you may need to convert them from the NeXT + character set to the Latin1 character set; use the program recode + for this purpose. Say Y to build UFS read support into your + kernel. If you want to compile this as a module ( = code which can + be inserted in and removed from the running kernel whenever you + want), say M here and read Documentation/modules.txt. The module + will be called ufs.o. If you haven't heard about all of this before, + it's safe to say N. BSD disklabel (FreeBSD partition tables) support CONFIG_BSD_DISKLABEL - FreeBSD uses its own partition scheme on your PC. It requires only - one entry in the primary partition table of your disk and manages it - similarly to DOS extended partitions, putting in its first sector a - new partition table in disklabel format. Saying Y here allows you to - read these disklabels and further mount FreeBSD partitions on your - Linux box if you also have configured BSD ufs filesystem support. If - you don't know what all this is about, say N. + FreeBSD uses its own harddisk partition scheme on your PC. It + requires only one entry in the primary partition table of your disk + and manages it similarly to DOS extended partitions, putting in its + first sector a new partition table in disklabel format. Saying Y + here allows you to read these disklabels and further mount FreeBSD + partitions read-only from within Linux if you have also said Y to + "BSD ufs filesystem support", above. If you don't know what all this + is about, say N. SMD disklabel (Sun partition tables) support CONFIG_SMD_DISKLABEL - Like most systems, SunOS uses its own partition table format, - incompatible with all others. Saying Y here allows you to read these - partition tables and further mount SunOS disks on your Linux box if - you also have configured BSD ufs filesystem support. This is mainly - used to carry data from a Sparc under SunOS to your Linux box via a - removable medium like magneto-optical or ZIP drives. If you don't - know what all this is about, say N. + Like most systems, SunOS uses its own harddisk partition table + format, incompatible with all others. Saying Y here allows you to + read these partition tables and further mount SunOS disks read-only + from within Linux if you have also said Y to "BSD ufs filesystem + support", above. This is mainly used to carry data from a Sparc + under SunOS to your Linux box via a removable medium like + magneto-optical or ZIP drives; note however that a good portable way + to transport files and directories between unixes (and even other + operating systems) is given by the tar program ("man tar" or + preferably "info tar"). If you don't know what all this is about, + say N. + +Macintosh partition map support +CONFIG_MAC_PARTITION + Say Y here if you want your Linux system to be able to read + the partition tables of Macintosh hard drives, and thus use + partitions on those drives. SMB filesystem support (to mount WfW shares etc..) CONFIG_SMB_FS @@ -4873,7 +5306,7 @@ CONFIG_SMB_FS available to Windows clients (which need to have a TCP/IP stack), you don't need to say Y here; you can use the program samba (available via ftp (user: anonymous) in - sunsite.unc.edu:/pub/Linux/system/Network/samba) for that. General + sunsite.unc.edu:/pub/Linux/system/network/samba) for that. General information about how to connect Linux, Windows machines and Macs is on the WWW at http://eats.com/linux_mac_win.html (to browse the WWW, you need to have access to a machine on the Internet that has a @@ -4885,15 +5318,22 @@ CONFIG_SMB_FS Coda filesystem support CONFIG_CODA_FS - CODA is an advanced network filesystem. It has support for disconnected - operation for laptops, read/write server replication, persistent client - caches and write back caching. - By choosing this option you are compiling kernel support for Coda clients - into the Linux kernel. You will need user level code as well, both for - the client and server. Server's are currently user level, i.e. need - no kernel support. For further information see - http://www.coda.cs.cmu.edu or contact Peter Braam <braam@cs.cmu.edu>. - + CODA is an advanced network filesystem. It has support for + disconnected operation for laptops, read/write server replication, + persistent client caches and write back caching. + By saying Y here you are compiling kernel support for Coda clients + into the Linux kernel. You will need user level code as well, both + for the client and server. Servers are currently user level, + i.e. need no kernel support. For technical information, read + Documentation/filesystems/coda.txt. + If you want to compile the coda client support as a module ( = code + which can be inserted in and removed from the running kernel + whenever you want), say M here and read + Documentation/modules.txt. The module will be called coda.o. + For further information see http://www.coda.cs.cmu.edu (to browse + the WWW, you need to have access to a machine on the Internet that + has a program like lynx or netscape) or contact Peter Braam + <braam@cs.cmu.edu>. SMB Win95 bug work-around CONFIG_SMB_WIN95 @@ -4916,24 +5356,74 @@ CONFIG_NCP_FS read Documentation/modules.txt. The module will be called ncpfs.o. Say N unless you are connected to a Novell network. +Packet signatures +CONFIG_NCPFS_PACKET_SIGNING + NCP allows to sign packets for stronger security. If you want + security, say Y. Normal users can leave it off. To be able to use + packet signing you must use ncpfs > 2.0.12. + +Proprietary file locking +CONFIG_NCPFS_IOCTL_LOCKING + Allows locking of records on remote volumes. Say N unless you have special + applications which are able to utilize this locking scheme. + +Clear remove/delete inhibit when needed +CONFIG_NCPFS_STRONG + Allows manipulation of files flagged as Delete or Rename Inhibit. + To use this feature you must mount volumes with the ncpmount parameter + "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting + volumes with -f 444. + +Use NFS namespace when available +CONFIG_NCPFS_NFS_NS + Allows you to utilize NFS namespace on NetWare servers. It brings you + case sensitive filesystems. Say Y. You can disable it at mount-time with + the -N nfs parameter of ncpmount. + +Use OS2/LONG namespace when available +CONFIG_NCPFS_OS2_NS + Allows you to utilize OS2/LONG namespace on NetWare servers. Filenames + in this namespace are limited to 255 characters, they are case + insensitive, and case in names is preserved. + Say Y. You can disable it at mount time with the -N os2 parameter of + ncpmount. + +Allow mounting of volume subdirectories +CONFIG_NCPFS_MOUNT_SUBDIR + Allows you to mount not only whole servers or whole volumes, but also + subdirectory from a volume. It can be used to reexport data and so on. + There is no reason why to say N, so Y is recommended unless you count + every byte. + To utilize this feature you must use ncpfs-2.0.12 or newer. + +NDS interserver authentication domains +CONFIG_NCPFS_NDS_DOMAINS + This allows storing NDS private keys into kernel space where it can be + used to authenticate another server as interserver NDS accesses need + it. You must use ncpfs-2.0.12.1 or newer to utilize this feature. + Say Y if you are using NDS connections to NetWare servers. Do not say Y + if security is primary for you because root can read your session + key (from /proc/kcore). + Amiga FFS filesystem support CONFIG_AFFS_FS The Fast File System (FFS) is the common filesystem used on harddisks by Amiga(tm) Systems since AmigaOS Version 1.3 - (34.20). With this driver you can also mount diskfiles used by the - Un*X Amiga Emulator by Bernd Schmidt - (http://www-users.informatik.rwth-aachen.de/~crux/uae.html). If you - want to do the latter, you will also need to say Y to "Loop device - support", above. Say Y if you want to be able to read and write - files from and to an Amiga FFS partition on your harddrive. Amiga - floppies however cannot be read with this driver due to an - incompatibility of the floppy controller used in an Amiga and the - standard floppy controller in PCs and workstations. Read - Documentation/filesystems/affs.txt and fs/affs/Changes. This - filesystem is also available as a module ( = code which can be - inserted in and removed from the running kernel whenever you want). - The module is called affs.o. If you want to compile it as a module, - say M here and read Documentation/modules.txt. If unsure, say N. + (34.20). With this driver you can also mount diskfiles used by Bernd + Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/; + to browse the WWW, you need to have access to a machine on the + Internet that has a program like lynx or netscape). If you want to + do the latter, you will also need to say Y to "Loop device support", + above. Say Y if you want to be able to read and write files from and + to an Amiga FFS partition on your harddrive. Amiga floppies however + cannot be read with this driver due to an incompatibility of the + floppy controller used in an Amiga and the standard floppy + controller in PCs and workstations. Read + Documentation/filesystems/affs.txt and fs/affs/Changes. This filesystem is also + available as a module ( = code which can be inserted in and removed + from the running kernel whenever you want). The module is called + affs.o. If you want to compile it as a module, say M here and read + Documentation/modules.txt. If unsure, say N. ROM filesystem support CONFIG_ROMFS_FS @@ -4947,23 +5437,323 @@ CONFIG_ROMFS_FS and read Documentation/modules.txt. If you don't know whether you need it, then you don't need it: say N. +nls: Native language codepages and Unicode support +CONFIG_NLS + This is required by the FAT and NTFS filesystems and by the ISO9660 + filesystem when it is compiled with Joliet support. Joliet is a + Microsoft extension for CDROMs that supports Unicode. This allows + translation between different character sets. When dealing with the + FAT based filesystems, there are two character sets that are + important. The first is the codepage. Codepages are character sets + that are used by DOS to allow filenames to have native language + characters when character sets were limited to 256 characters. The + codepage is the character set that is used to store native language + characters on disk. The two most common codepages are 437 in the + United States and 850 in much of Europe. The second important + character set is the input/output character set. This is the + character set that is displayed on the screen. In the United States, + this will almost always be the ISO 8859-1 character set. This is the + default. Linux will only do a translation of the FAT filenames, not + the contents of the files. + +nls codepage 437 +CONFIG_NLS_CODEPAGE_437 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored + in so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage that is used in + the United States and parts of Canada. This is recommended. + +nls codepage 737 +CONFIG_NLS_CODEPAGE_737 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored + in so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage that is used for + Greek. If unsure, say N. + +nls codepage 775 +CONFIG_NLS_CODEPAGE_775 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored + in so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage that is used for + for the Baltic Rim Languages. If unsure, say N. + +nls codepage 850 +CONFIG_NLS_CODEPAGE_850 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored + in so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage that is used for + much of Europe--United Kingdom, Germany, Spain, Italy, and [add more + countries here]. It has some characters useful to many European + languages that are not part of the US codepage 437. If unsure, say + Y. + +nls codepage 852 +CONFIG_NLS_CODEPAGE_852 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the Latin 2 codepage used by DOS + for much of Central and Eastern Europe. It has all the required + characters for these languages: Albanian, Croatian, Czech, English, + Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin + transcription), Slovak, Slovenian, and Sorbian. + +nls codepage 855 +CONFIG_NLS_CODEPAGE_855 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Cyrillic. + +nls codepage 857 +CONFIG_NLS_CODEPAGE_857 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Turkish. + +nls codepage 860 +CONFIG_NLS_CODEPAGE_860 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Portuguese. + +nls codepage 861 +CONFIG_NLS_CODEPAGE_861 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Icelandic. + +nls codepage 862 +CONFIG_NLS_CODEPAGE_862 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Hebrew. + +nls codepage 863 +CONFIG_NLS_CODEPAGE_863 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Canadian + French. + +nls codepage 864 +CONFIG_NLS_CODEPAGE_864 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Arabic. + +nls codepage 865 +CONFIG_NLS_CODEPAGE_865 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for the Nordic + European countries. + +nls codepage 866 +CONFIG_NLS_CODEPAGE_866 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for + Cyrillic/Russian. + +nls codepage 869 +CONFIG_NLS_CODEPAGE_869 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Greek. +### +### Why do we have two codepages for Greek and Cyrillic? +### + +nls codepage 874 +CONFIG_NLS_CODEPAGE_874 + The Microsoft fat filesystem family can deal with filenames in + native language character sets. These character sets are stored in + so-called DOS codepages. You need to include the appropriate + codepage if you want to be able to read/write these filenames on + DOS/Windows partitions correctly. This does apply to the filenames + only, not to the file contents. You can include several codepages; + say Y here if you want to include the DOS codepage for Thai. + +nls iso8859-1 +CONFIG_NLS_ISO8859_1 + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 1 character + set, which covers most West European languages such as Albanian, + Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German, + Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish, + Swedish, and Valencian. It is also the default for the US. If + unsure, say Y. + +nls iso8859-2 +CONFIG_NLS_ISO8859_2 + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the the Latin 2 character + set, which works for most Latin-written Slavic and Central European + languages: Czech, German, Hungarian, Polish, Rumanian, Croatian, + Slovak, Slovene. + +nls iso8859-3 +CONFIG_NLS_ISO8859_3 + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 3 character + set, which is popular with authors of Esperanto, Galician, Maltese, + and Turkish. + +nls iso8859-4 +CONFIG_NLS_ISO8859_4 + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 4 character + set which introduces letters for Estonian, Latvian, and + Lithuanian. It is an incomplete predecessor of Latin 6. + +nls iso8859-5 +CONFIG_NLS_ISO8859_5 + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for ISO8859-5, a Cyrillic + character set with which you can type Bulgarian, Byelorussian, + Macedonian, Russian, Serbian, and Ukrainian. Note that the charset + KOI8-R is preferred in Russia. + +nls iso8859-6 +CONFIG_NLS_ISO8859_6 + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for ISO8859-6, the Arabic + character set. + +nls iso8859-7 +CONFIG_NLS_ISO8859_7 + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for ISO8859-7, the Modern + Greek character set. + +nls iso8859-8 +CONFIG_NLS_ISO8859_8 + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for ISO8859-8, the Hebrew + character set. + +nls iso8859-9 +CONFIG_NLS_ISO8859_9 + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 5 character + set, and it replaces the rarely needed Icelandic letters in Latin 1 + with the Turkish ones. Useful in Turkey. + +nls iso8859-10 +CONFIG_NLS_ISO8859_10 + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the Latin 6 character + set, which adds the last Inuit (Greenlandic) and Sami (Lappish) + letters that were missing in Latin 4 to cover the entire Nordic + area. + +nls koi8-r +CONFIG_NLS_KOI8_R + If you want to display filenames with native language characters + from the Microsoft fat filesystem family or from JOLIET CDROMs + correctly on the screen, you need to include the appropriate + input/output character sets. Say Y here for the preferred Russian + character set. + Virtual terminal CONFIG_VT - This includes support for a terminal device using display and + This includes support for a terminal device with display and keyboard devices. Only people using embedded systems want to say N - here; most everybody says Y. + here; most everybody else says Y. If unsure, say Y, or else you + won't be able to do much with your new shiny Linux system :-) -Console on virtual terminal +Support for console on virtual terminal CONFIG_VT_CONSOLE - If you enable this option, by default all kernel messages will be sent - to the device /dev/tty0 which corresponds to the virtual terminal you + If you say Y here, by default all kernel messages will be sent to + the device /dev/tty0 which corresponds to the virtual terminal you have visible on your display. You should say Y here unless you only - want to have the kernel messages output on a serial port. + want to have the kernel messages output on a serial port (in which + case you probably want to say Y to "Console on serial port", below). Software generated cursor CONFIG_SOFTCURSOR - If you enable this option, you'll be able to do lots of nice things - with your cursor -- for example to turn it into a non-blinking one. + If you say Y here, you'll be able to do lots of nice things with the + cursors of your virtual consoles -- for example to turn them into + non-blinking block cursors which are more visible on laptop screens. See Documentation/VGA-softcursor.txt for more information. Standard/generic serial support @@ -4985,14 +5775,14 @@ CONFIG_SERIAL that they can use serial mice, modems and similar devices connecting to the standard serial ports. -Console on serial port +Support for console on serial port CONFIG_SERIAL_CONSOLE - If you enable this option, it is possible to use a serial port as the - console. By default still the virtual console will be used at the - system console but you can alter that using a kernel command line - option. If you don't have a VGA card installed the kernel will - automatically use /dev/ttyS0 as system console if this option is - enabled. + If you say Y here, it is possible to use a serial port as the + console. By default still the currently visible virtual console will + be used as the system console but you can alter that using a kernel + command line option. If you don't have a VGA card installed and you + say Y here, the kernel will automatically use /dev/ttyS0 as system + console. Comtrol Rocketport support CONFIG_ROCKETPORT @@ -5044,27 +5834,29 @@ CONFIG_SPECIALIX connect more than two modems to your linux box, for instance in order to become a BBS. If you have a card like that, say Y here and read the file Documentation/specialix.txt. Also it's possible to say - M here and compile this driver as kernel loadable module. + M here and compile this driver as kernel loadable module which will + be called specialix.o. Specialix DTR/RTS pin is RTS CONFIG_SPECIALIX_RTSCTS - The Specialix card can only support either RTS or DTR. When this - option is off, the driver will use the pin as "DTR" when the tty is - in software handshake mode. When this option is on or hardware - handshake is on, it will always be RTS. Read the file - Documentation/specialix.txt for more information. + The Specialix card can only support either RTS or DTR. When you say + N here, the driver will use the pin as "DTR" when the tty is in + software handshake mode. When you say Y here or hardware handshake + is on, it will always be RTS. Read the file + Documentation/specialix.txt for more information. Cyclades async mux support CONFIG_CYCLADES This is a driver for a card that gives you many serial ports. You would need something like this to connect more than two modems to - your linux box, for instance in order to become a BBS. If you want - to compile this as a module ( = code which can be inserted in and - removed from the running kernel whenever you want), say M here and - read Documentation/modules.txt. The module will be called - cyclades.o. If you haven't heard about it, it's safe to say N. (As - of 1.3.9x kernels, this driver's minor numbers start at 0 instead of - 32.) + your linux box, for instance in order to become a BBS. For + information about the Cyclades-Z card, read + drivers/char/README.cycladesZ. If you want to compile this as a + module ( = code which can be inserted in and removed from the + running kernel whenever you want), say M here and read + Documentation/modules.txt. The module will be called cyclades.o. If + you haven't heard about it, it's safe to say N. (As of 1.3.9x + kernels, this driver's minor numbers start at 0 instead of 32.) Stallion multiport serial support CONFIG_STALDRV @@ -5074,7 +5866,7 @@ CONFIG_STALDRV asked for your specific card model in the next questions. Make sure to read drivers/char/README.stallion in this case. If you have never heard about all this, it's safe to say N. - + Stallion EasyIO or EC8/32 support CONFIG_STALLION If you have an EasyIO or EasyConnection 8/32 multiport Stallion @@ -5234,12 +6026,13 @@ CONFIG_82C710_MOUSE PC110 digitizer pad support CONFIG_PC110_PAD This drives the digitizer pad on the IBM PC110 palmtop (see - http://toy.cabi.net). It can turn the digitizer pad into a PS/2 - mouse emulation with tap gestures or into an absolute pad. If you - want to compile this as a module ( = code which can be inserted in - and removed from the running kernel whenever you want), say M here - and read Documentation/modules.txt. The module will be called - pc110pad.o. + http://toy.cabi.net; to browse the WWW, you need to have access to a + machine on the Internet that has a program like lynx or + netscape). It can turn the digitizer pad into a PS/2 mouse emulation + with tap gestures or into an absolute pad. If you want to compile + this as a module ( = code which can be inserted in and removed from + the running kernel whenever you want), say M here and read + Documentation/modules.txt. The module will be called pc110pad.o. Microsoft busmouse support CONFIG_MS_BUSMOUSE @@ -5295,97 +6088,90 @@ CONFIG_QIC02_DYNCONF Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support CONFIG_FTAPE - If you have a tape drive that is connected to your floppy - controller, say `Y' here. Some tape drives (like the Seagate "Tape + If you have a tape drive that is connected to your floppy + controller, say Y here. Some tape drives (like the Seagate "Tape Store 3200" or the Iomega "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed" controller of their own. These drives (and - their companion controllers) are also supported. - If you have a special controller (such as the CMS FC-10, FC-20, + their companion controllers) are also supported if you say Y here. + If you have a special controller (such as the CMS FC-10, FC-20, Mountain Mach-II, or any controller that is based on the Intel 82078 FDC like the high speed controllers by Seagate and Exabyte and Iomega's "Ditto Dash") you must configure it by selecting the - appropriate entries from the "Floppy tape controllers" sub-menu and - possibly modify the default values for the IRQ and DMA channel and - the IO base in ftape's configuration menu. If you want to use your - floppy tape drive on a PCI-bus based system, please read the file - `./drivers/char/ftape/README.PCI'. - The ftape kernel driver is also available as a runtime loadable + appropriate entries from the "Floppy tape controllers" sub-menu + below and possibly modify the default values for the IRQ and DMA + channel and the IO base in ftape's configuration menu. If you want + to use your floppy tape drive on a PCI-bus based system, please read + the file drivers/char/ftape/README.PCI. + The ftape kernel driver is also available as a runtime loadable module ( = code which can be inserted in and removed from the running kernel whenever you want). If you want to compile it as a - module, say `M' here and read `./Documentation/modules.txt'. - Note that the `Ftape-HOWTO' is out of date (sorry), but there is a - web page with more recent documentation at - `http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/'. This page + module, say M here and read Documentation/modules.txt. The module + will be called ftape.o. + Note that the Ftape-HOWTO is out of date (sorry) and documents the + older version 2.08 of this software but still contains useful + information. There is a web page with more recent documentation at + http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ . This page always contains the latest release of the ftape driver and useful information (backup software, ftape related patches and - documentation, FAQ). The Ftape-HOWTO still contains useful - information, though, but documents the older 2.08 version of ftape, - whereas this version of ftape is 3.04. - Note that the file system interface has changed quite a lot - compared to previous versions of ftape. Please read - `./Documentation/ftape.txt' + documentation, FAQ). (To browse the WWW, you need to have access to + a machine on the Internet that has a program like lynx or netscape.) + Note that the file system interface has changed quite a bit compared + to previous versions of ftape. Please read Documentation/ftape.txt. The file system interface for ftape CONFIG_ZFTAPE - Normally, you want to say `Y' or `M'. DON'T say `N' here or you + Normally, you want to say Y or M. DON'T say N here or you WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE. - The ftape module itself no longer contains the routines necessary + The ftape module itself no longer contains the routines necessary to interface with the kernel VFS layer (i.e. to actually write data to and read data from the tape drive). Instead the file system interface (i.e. the hardware independent part of the driver) has been moved to a separate module. - If you say `M' zftape will be compiled as as a runtime loadable + If you say M zftape will be compiled as a runtime loadable module ( = code which can be inserted in and removed from the running kernel whenever you want). In this case you should read - `./Documentation/modules.txt'. - There will also be another module called `zft-compressor.o' which - contains code to support user transparent on-the-fly compression - based on Ross William's lzrw3 algorithm. `zft-compressor.o' will be - compiled as a runtime loadable module only. If you have enabled + Documentation/modules.txt. The module will be called zftape.o. + Regardless of whether you say Y or M here, an additional runtime + loadable module called `zft-compressor.o' which contains code to + support user transparent on-the-fly compression based on Ross + William's lzrw3 algorithm will be produced. If you have enabled auto-loading of kernel modules via `kerneld' (i.e. have said `Y' to CONFIG_KERNELD) then `zft-compressor.o' will be loaded automatically by zftape when needed. - Despite of its name zftape does NOT use compression by - default. The file `./Documentation/ftape.txt' contains a short - description of the most important changes in the file system - interface compared to previous versions of ftape. The ftape home - page `http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/' - contains further information. IMPORTANT NOTE: zftape can read - archives created by previous versions of ftape and provide file mark - support (i.e. fast skipping between tape archives) but previous - version of ftape will lack file mark support when reading archives - produced by zftape. - -Builtin on-the-fly compression for zftape, based on lzrw3 -CONFIG_ZFT_COMPRESSOR - This module implements builtin on-the-fly compression for ftape's - file system interface zftape. `zft-compressor.o' is compiled as a - runtime loadable module only and will be loaded by zftape on demand - if support for auto-loading of modules via `kerneld' has been - enabled (CONFIG_KERNELD). + Despite of its name zftape does NOT use compression by default. The + file Documentation/ftape.txt contains a short description of the + most important changes in the file system interface compared to + previous versions of ftape. The ftape home page + http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains + further information (to browse the WWW, you need to have access to a + machine on the Internet that has a program like lynx or netscape). + IMPORTANT NOTE: zftape can read archives created by previous + versions of ftape and provide file mark support (i.e. fast skipping + between tape archives) but previous version of ftape will lack file + mark support when reading archives produced by zftape. Default block size for zftape CONFIG_ZFT_DFLT_BLK_SZ - If unsure leave this at its default value, i.e. 10240. Note that + If unsure leave this at its default value, i.e. 10240. Note that you specify only the default block size here. The block size can be changed at run time using the MTSETBLK tape operation with the MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the shell command line). - The probably most striking difference between zftape and previous + The probably most striking difference between zftape and previous versions of ftape is the fact that all data must be written or read in multiples of a fixed block size. The block size defaults to 10240 which is what GNU tar uses. The values for the block size should be either 1 or multiples of 1024 up to a maximum value of 63488 (i.e. 62k). If you specify `1' then zftape's builtin compression will be disabled. - Reasonable values are `10240' (GNU tar's default block size), + Reasonable values are `10240' (GNU tar's default block size), `5120' (afio's default block size), `32768' (default block size some backup programs assume for SCSI tape drives) or `1' (no restriction on block size, but disables builtin compression). Number of DMA buffers CONFIG_FT_NR_BUFFERS - Please leave this at `3"' unless you REALLY know what you are + Please leave this at `3' unless you REALLY know what you are doing. It is not necessary to change this value. Values below 3 make the proper use of ftape impossible, values greater than 3 are waste of memory. You can change the amount of DMA memory used by ftape at @@ -5395,7 +6181,7 @@ CONFIG_FT_NR_BUFFERS Procfs entry for ftape CONFIG_FT_PROC_FS - Optional. Saying `Y' will result in creation of a file + Optional. Saying `Y' will result in creation of a file `/proc/ftape' under the proc file system. This files can be viewed with your favorite pager (i.e. use "more /proc/ftape/history" or "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The @@ -5405,21 +6191,21 @@ CONFIG_FT_PROC_FS kernel driver. Saying `Y' will enlarge the size of the ftape driver by approximately 2k. WARNING: When compiling ftape as a module (i.e. saying `M' to - `CONFIG_FTAPE') it is dangerous to use ftape's proc file system + "Floppy tape drive") it is dangerous to use ftape's proc file system interface. Accessing `/proc/ftape' while the module is unloaded will result in a kernel Oops. This cannot be fixed from inside ftape. Controlling the amount of debugging output of ftape CONFIG_FT_NORMAL_DEBUG - This option controls the amount of debugging output the ftape driver + This option controls the amount of debugging output the ftape driver is ABLE to produce; it does not increase or diminish the debugging level itself. If unsure, leave this at its default setting, i.e. choose "Normal". - Ftape can print lots of debugging messages to the system console + Ftape can print lots of debugging messages to the system console resp. kernel log files. Reducing the amount of possible debugging output reduces the size of the kernel module by some kb, so it might be a good idea to use "None" for emergency boot floppies. - If you want to save memory then the following strategy is + If you want to save memory then the following strategy is recommended: leave this option at its default setting "Normal" until you know that the driver works as expected, afterwards reconfigure the kernel, this time specifying "Reduced" or "None" and recompile @@ -5427,12 +6213,12 @@ CONFIG_FT_NORMAL_DEBUG debugging output does not increase the amount of debugging output printed to the console but only makes it possible to produce "Excessive" debugging output. - Please read `./Documentation/ftape.txt' for a short description + Please read Documentation/ftape.txt for a short description how to control the amount of debugging output. The floppy drive controller for ftape CONFIG_FT_STD_FDC - Only change this setting if you have a special controller. If you + Only change this setting if you have a special controller. If you didn't plug any add-on card into your computer system but just plugged the floppy tape cable into the already existing floppy drive controller then you don't want to change the default setting, @@ -5447,115 +6233,115 @@ CONFIG_FT_STD_FDC `2'. This is necessary for any controller card that is based on Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high speed" controllers. - If you choose something other than "Standard" then please make + If you choose something other than "Standard" then please make sure that the settings for the IO base address and the IRQ and DMA channel in the configuration menus below are correct. Use the manual of your tape drive to determine the correct settings! - If you are already successfully using your tape drive with another + If you are already successfully using your tape drive with another operating system then you definitely should use the same settings for the IO base, the IRQ and DMA channel that have proven to work with that other OS. - Note that this menu lets you specify only the default setting for + Note that this menu lets you specify only the default setting for the hardware setup. The hardware configuration can be changed at boot time (when ftape is compiled into the kernel, i.e. if you - have said `Y' to `CONFIG_FTAPE') or module load time (i.e. if you - have said `M' to `CONFIG_FTAPE'). - Please read also the file `./Documentation/ftape.txt' which + have said Y to "Floppy tape drive") or module load time (i.e. if you + have said M to "Floppy tape drive"). + Please read also the file Documentation/ftape.txt which contains a short description of the parameters that can be set at boot or load time. If you want to use your floppy tape drive on a PCI-bus based system, please read the file - `./drivers/char/ftape/README.PCI'. + drivers/char/ftape/README.PCI. IO base of the floppy disk controller used with Ftape CONFIG_FT_FDC_BASE - You don't need to specify a value if the following default + You don't need to specify a value if the following default settings for the base IO address are correct: <<< MACH-2 : 0x1E0 >>> <<< FC-10/FC-20: 0x180 >>> <<< Secondary : 0x370 >>> Secondary refers to a secondary FDC controller like the "high speed" controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash. - Please make sure that the setting for the IO base address + Please make sure that the setting for the IO base address specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already successfully using the tape drive with another operating system then you definitely should use the same settings for the IO base that has proven to work with that other OS. - Note that this menu lets you specify only the default setting for + Note that this menu lets you specify only the default setting for the IO base. The hardware configuration can be changed at boot time - (when ftape is compiled into the kernel, i.e. if you specify `Y' to - `CONFIG_FTAPE') or module load time (i.e. if you have say `M' to - `CONFIG_FTAPE'). - Please read also the file `./Documentation/ftape.txt' which - contains a short description of the parameters that can be set at - boot or load time. - + (when ftape is compiled into the kernel, i.e. if you specified Y to + "Floppy tape drive") or module load time (i.e. if you have said M to + "Floppy tape drive"). + Please read also the file Documentation/ftape.txt which contains a + short description of the parameters that can be set at boot or load + time. + IRQ channel for the floppy disk controller used with Ftape CONFIG_FT_FDC_IRQ - You don't need to specify a value if the following default + You don't need to specify a value if the following default settings for the interrupt channel are correct: <<< MACH-2 : 6 >>> <<< FC-10/FC-20: 9 >>> <<< Secondary : 6 >>> Secondary refers to secondary a FDC controller like the "high speed" controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash. - Please make sure that the setting for the IO base address + Please make sure that the setting for the IO base address specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already successfully using the tape drive with another operating system then you definitely should use the same settings for the IO base that has proven to work with that other OS. - Note that this menu lets you specify only the default setting for + Note that this menu lets you specify only the default setting for the IRQ channel. The hardware configuration can be changed at boot - time (when ftape is compiled into the kernel, i.e. if you specify - `Y' to `CONFIG_FTAPE') or module load time (i.e. if you have say `M' - to `CONFIG_FTAPE'). - Please read also the file `./Documentation/ftape.txt' which - contains a short description of the parameters that can be set at - boot or load time. - + time (when ftape is compiled into the kernel, i.e. if you specified + Y to "Floppy tape drive") or module load time (i.e. if you have said M + to "Floppy tape drive"). + Please read also the file Documentation/ftape.txt which contains a + short description of the parameters that can be set at boot or load + time. + DMA channel for the floppy disk controller used with Ftape CONFIG_FT_FDC_DMA - You don't need to specify a value if the following default + You don't need to specify a value if the following default settings for the DMA channel are correct: <<< MACH-2 : 2 >>> <<< FC-10/FC-20: 3 >>> <<< Secondary : 2 >>> Secondary refers to a secondary FDC controller like the "high speed" controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash. - Please make sure that the setting for the IO base address + Please make sure that the setting for the IO base address specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already successfully using the tape drive with another operating system then you definitely should use the same settings for the IO base that has proven to work with that other OS. - Note that this menu lets you specify only the default setting for + Note that this menu lets you specify only the default setting for the DMA channel. The hardware configuration can be changed at boot - time (when ftape is compiled into the kernel, i.e. if you specify - `Y' to `CONFIG_FTAPE') or module load time (i.e. if you have say `M' - to `CONFIG_FTAPE'). - Please read also the file `./Documentation/ftape.txt' which - contains a short description of the parameters that can be set at - boot or load time. + time (when ftape is compiled into the kernel, i.e. if you specified + Y to "Floppy tape drive") or module load time (i.e. if you have said M + to "Floppy tape drive"). + Please read also the file Documentation/ftape.txt which contains a + short description of the parameters that can be set at boot or load + time. FDC FIFO Threshold before requesting DMA service CONFIG_FT_FDC_THR - Set the FIFO threshold of the FDC. If this is higher the DMA + Set the FIFO threshold of the FDC. If this is higher the DMA controller may serve the FCD after a higher latency time. If this is lower, less DMA transfers occur leading to less bus contention. - You may try to tune this if ftape annoys you with "reduced data + You may try to tune this if ftape annoys you with "reduced data rate because of excessive overrun errors" messages. However, this doesn't seem to have too much an effect. If unsure, don't touch the initial value, i.e. leave it at "8". FDC maximum data rate CONFIG_FT_FDC_MAX_RATE - With some mother board/FDC combinations ftape will not be able to + With some mother board/FDC combinations ftape will not be able to run your FDC/tape drive combination at the highest available speed. If this is the case you'll encounter "reduced data rate because of excessive overrun errors" messages and lots of retries before ftape finally decides to reduce the data rate. - In this case it might be desirable to tell ftape beforehand that + In this case it might be desirable to tell ftape beforehand that it need not try to run the tape drive at the highest available speed. If unsure, leave this disabled, i.e. leave it at 2000 bits/sec. @@ -5579,20 +6365,22 @@ CONFIG_APM USER RESUME operation, the /proc/apm device will provide battery status information, and user-space programs will receive notification of APM "events" (e.g., battery status - change). Supporting software can be gotten via ftp (user: anonymous) - from tsx-11.mit.edu/pub/linux/packages/laptops/apm/. This driver - does not spin down disk drives (see hdparm(8) for that); and it - doesn't turn off VESA-compliant "green" monitors. This driver does - not support the TI 4000M TravelMate and the ACER 486/DX4/75 because - they don't have compliant BIOSes. Many "green" desktop machines - also don't have compliant BIOSes, and this driver will cause those - machines to panic during the boot phase (typically, these machines - are using a data segment of 0040, which is reserved for the Linux - kernel). Generally, if you don't have a battery in your machine, - there isn't much point in using this driver and you should say N. - If you get random kernel OOPSes or reboots that don't seem to be - related to anything, try disabling/enabling this option. Some other - things to try when experiencing seemingly random, "weird" problems: + change). Supporting software is available; for more information, + read the Battery Powered Linux mini-HOWTO available via ftp (user: + anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. + This driver does not spin down disk drives (see hdparm(8) for that); + and it doesn't turn off VESA-compliant "green" monitors. This + driver does not support the TI 4000M TravelMate and the ACER + 486/DX4/75 because they don't have compliant BIOSes. Many "green" + desktop machines also don't have compliant BIOSes, and this driver + will cause those machines to panic during the boot phase (typically, + these machines are using a data segment of 0040, which is reserved + for the Linux kernel). Generally, if you don't have a battery in + your machine, there isn't much point in using this driver and you + should say N. If you get random kernel OOPSes or reboots that don't + seem to be related to anything, try disabling/enabling this + option. Some other things to try when experiencing seemingly random, + "weird" problems: 1) passing the "no-hlt" option to the kernel 2) passing the "no-387" option to the kernel 3) passing the "floppy=nodma" option to the kernel @@ -5648,10 +6436,22 @@ CONFIG_APM_DISPLAY_BLANK Power off on shutdown CONFIG_APM_POWER_OFF - This option will power off the computer after the Linux kernel is halted - (e.g., with the halt(8) command). As with the other APM options, this + Enable the ability to power off the computer after the Linux kernel + is halted. You will need software (e.g., a suitable version of the + halt(8) command) to cause the computer to power down. Recent + versions of the sysvinit package available from + ftp://sunsite.unc.edu/pub/Linux/system/daemons/init/ (user: + anonymous) contain support for this ("halt -p" shuts down Linux and + powers off the computer). As with the other APM options, this option may not work reliably with some APM BIOS implementations. +Ignore multiple suspend/standby events +CONFIG_APM_IGNORE_MULTIPLE_SUSPEND + This option is necessary on the Thinkpad 560, but should work on all + other laptops. When the APM BIOS returns multiple suspend or standby + events while one is already being processed they will be ignored. + Without this the Thinkpad 560 has troubles with apmd, and pcmcia-cs. + Watchdog Timer Support CONFIG_WATCHDOG If you say Y here (and to one of the following options) and create a @@ -5740,7 +6540,7 @@ CONFIG_ACQUIRE_WDT inserted in and removed from the running kernel whenever you want). The module is called pscwdt.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. Most people will say N. - + Enhanced Real Time Clock Support CONFIG_RTC If you say Y here and create a character special file /dev/rtc with @@ -5756,6 +6556,13 @@ CONFIG_RTC have a use for such a device (such as periodic data sampling), then say Y here, and go read the file Documentation/rtc.txt for details. +Tadpole ANA H8 Support +CONFIG_H8 + The Hitachi H8/337 is a microcontroller used to deal with the power + and thermal environment. If you say Y here, you will be able to + communicate with it via via a character special device. If unsure, + say N. + /dev/nvram support CONFIG_NVRAM If you say Y here and create a character special file /dev/nvram @@ -5776,18 +6583,17 @@ CONFIG_NVRAM PC joystick support CONFIG_JOYSTICK - If you have a PC compatible analog or digital joystick, you can - say Y here. If you then create a character special file under /dev - with major number 15 and minor number 0 or 1 (for the two joystick - ports) using mknod ("man mknod"), you can read the status of the - buttons and the x and y coordinates from that file. More - information, an example program and a calibration program are - contained in the joystick package which is available at: - ftp://sunsite.unc.edu/pub/Linux/kernel/patches/console - This driver is also available as a module ( = code which can be - inserted in and removed from the running kernel whenever you want). - The module will be called joystick.o. If you want to compile it as a - module, say M here and read Documentation/modules.txt. + If you have a PC compatible analog or digital joystick, you can say + Y here. If you then create a character special file under /dev with + major number 15 and minor number 0 or 1 (for the two joystick ports) + using mknod ("man mknod"), you can read the status of the buttons + and the x and y coordinates from that file. Please read the file + Documentation/joystick.txt which contains more information and the + location of the joystick package that you'll need. This driver is + also available as a module ( = code which can be inserted in and + removed from the running kernel whenever you want). The module will + be called joystick.o. If you want to compile it as a module, say M + here and read Documentation/modules.txt. ARC console time CONFIG_RTC_ARC @@ -5838,6 +6644,9 @@ CONFIG_ADLIB these cards may cause trouble (I don't currently know of any such cards, however). +Loopback MIDI device support +CONFIG_VMIDI + Gravis Ultrasound support CONFIG_GUS Say Y here for any type of Gravis Ultrasound card, including @@ -5911,14 +6720,15 @@ CONFIG_TRIX Answer Y if you have the AudioTriX Pro sound card manufactured by MediaTrix. -Support for MAD16 and/or Mozart based cards +Support for OPTi MAD16 and/or Mozart based cards CONFIG_MAD16 - Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 - (OPTi 82C928 or 82C929) audio interface chip. These chips are - currently quite common so it's possible that many no-name cards - have one of them. In addition the MAD16 chip is used in some - cards made by known manufacturers such as Turtle Beach (Tropez), - Reveal (some models) and Diamond (latest ones). + Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi + 82C928 or 82C929 or 82C931) audio interface chip. For the 82C931, + please read drivers/sound/README.C931. These chips are currently + quite common so it's possible that many no-name cards have one of + them. In addition the MAD16 chip is used in some cards made by known + manufacturers such as Turtle Beach (Tropez), Reveal (some models) + and Diamond (latest ones). Support for Crystal CS4232 based (PnP) cards CONFIG_CS4232 @@ -5954,7 +6764,7 @@ CONFIG_SUN_AUDIO SB32/AWE support CONFIG_AWE32_SYNTH Say Y here if you have a SB32 or SB AWE soundcard. See - linux/drivers/sound/lowlevel/README.awe for more info. + drivers/sound/lowlevel/README.awe for more info. Additional low level drivers CONFIG_LOWLEVEL_SOUND @@ -5976,23 +6786,23 @@ CONFIG_ACI_MIXER Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600) CONFIG_AEDSP16 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This card - can emulate an SBPro or a Microsoft Sound System card, so you should - have said Y to either "SoundBlaster (SB, SBPro, SB16, clones) + can emulate either an SBPro or a Microsoft Sound System card, so you + should have said Y to either "SoundBlaster (SB, SBPro, SB16, clones) support" or "Microsoft Sound System support", above, and you need to answer the "MSS emulation" and "SBPro emulation" questions below - accordingly. You should say Y to one and only one of these + accordingly. You should say Y to one and only one of these two questions. Read the drivers/sound/lowlevel/README.aedsp16 file and - the head of drivers/sound/lowlevel/aedsp16.c to get more - information about this driver and its configuration. This driver - supports Audio Excel DSP 16 but not the III nor Pnp versions of this - card. Read drivers/sound/lowlevel/README.aedsp16 if you want to know - something more on how to use the III version with this sound driver. + the head of drivers/sound/lowlevel/aedsp16.c to get more information + about this driver and its configuration. This driver supports Audio + Excel DSP 16 but not the III nor Pnp versions of this card. Read + drivers/sound/lowlevel/README.aedsp16 if you want to know something + more on how to use the III version with this sound driver. SC-6600 based audio cards (new Audio Excel DSP 16) CONFIG_SC6600 - The SC6600 is the new version of DSP mounted on the Audio Excel DSP 16 - cards. Find in the manual the FCC ID of your audio card and answer Y if - you have an SC6600 DSP. + The SC6600 is the new version of DSP mounted on the Audio Excel DSP + 16 cards. Find in the manual the FCC ID of your audio card and + answer Y if you have an SC6600 DSP. Audio Excel DSP 16 (MSS emulation) CONFIG_AEDSP16_MSS @@ -6014,9 +6824,10 @@ CONFIG_PROFILE read it, you need the readprofile package from sunsite.unc.edu. Its manpage gives information regarding the format of profiling data. To become a kernel hacker, you can start with the Kernel Hacker's Guide - at http://www.redhat.com:8080/HyperNews/get/khg.html. Mere mortals - say N. - + at http://www.redhat.com:8080/HyperNews/get/khg.html (to browse the + WWW, you need to have access to a machine on the Internet that has a + program like lynx or netscape). Mere mortals say N. + Profile shift count CONFIG_PROFILE_SHIFT This is used to adjust the granularity with which the addresses of @@ -6053,12 +6864,13 @@ CONFIG_ISDN emulator. Network devices support autodial, channel-bundling, callback and caller-authentication without having a daemon running. A reduced T.70 protocol is supported with tty's suitable - for German BTX. On D-Channel, the protocols EDSS1 and 1TR6 are - supported. See Documentation/isdn/README for more information. If - you want to compile the ISDN as a module ( = code which can be - inserted in and removed from the running kernel whenever you want), - say M here and read Documentation/modules.txt. The module will be - called isdn.o. If unsure, say N. + for German BTX. On D-Channel, the protocols EDSS1 (Euro-ISDN) and + 1TR6 (German style) are supported. See Documentation/isdn/README for + more information. If you want to compile the ISDN code as a module + ( = code which can be inserted in and removed from the running + kernel whenever you want), say M here and read + Documentation/modules.txt. The module will be called isdn.o. If + unsure, say N. Support synchronous PPP CONFIG_ISDN_PPP @@ -6173,7 +6985,7 @@ HiSax Support for US/NI-1 CONFIG_HISAX_NI1 You should choose the D-channel protocol your local telephone service provider uses here by saying Y or N. - + HiSax Support for German 1TR6 CONFIG_HISAX_1TR6 You should choose the D-channel protocol your local @@ -6200,21 +7012,25 @@ CONFIG_ISDN_DRV_SC can be inserted in and removed from the running kernel whenever you want, details in Documentation/modules.txt); the module will be called sc.o. See Documentation/isdn/README.sc and - http://www.spellcast.com for more information. + http://www.spellcast.com for more information (to browse the WWW, + you need to have access to a machine on the Internet that has a + program like lynx or netscape). AVM-B1 with CAPI2.0 support CONFIG_ISDN_DRV_AVMB1 This enables support for the AVM B1 ISDN networking cards. In addition, a CAPI (Common ISDN Application Programming Interface, a standard making it easy for programs to access ISDN hardware, see - http://www.capi.org/) interface for this card is provided. In order - to use this card, additional firmware is necessary, which has to be - downloaded into the card using a utility which is distributed - separately. Please read the file Documentation/isdn/README.avmb1. - This code is also available as a module ( = code which can be - inserted in and removed from the running kernel whenever you - want). The module will be called avmb1.o. If you want to compile it - as a module, say M here and read Documentation/modules.txt. + http://www.capi.org/; to browse the WWW, you need to have access to + a machine on the Internet that has a program like lynx or netscape) + interface for this card is provided. In order to use this card, + additional firmware is necessary, which has to be downloaded into + the card using a utility which is distributed separately. Please + read the file Documentation/isdn/README.avmb1. This code is also + available as a module ( = code which can be inserted in and removed + from the running kernel whenever you want). The module will be + called avmb1.o. If you want to compile it as a module, say M here + and read Documentation/modules.txt. Verbose reason code reporting (kernel size +=7K) CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON @@ -6226,8 +7042,9 @@ Support for AP1000 multicomputer CONFIG_AP1000 This enables support for a sparc based parallel multi-computer called AP1000+. For details on our efforts to port Linux to this - machine see http://cap.anu.edu.au/cap/projects/linux or mail to - hackers@cafe.anu.edu.au + machine see http://cap.anu.edu.au/cap/projects/linux (to browse the + WWW, you need to have access to a machine on the Internet that has a + program like lynx or netscape) or mail to hackers@cafe.anu.edu.au Sparc ESP SCSI support CONFIG_SCSI_SUNESP @@ -6243,123 +7060,14 @@ CONFIG_SUN_OPENPROMIO removed from the running kernel whenever you want), say M and read Documentation/modules.txt. If unsure, say Y. -Support for Cyrix processors -CONFIG_CYRIX - This enables recognition of Cyrix processors. Without it - /proc/cpuinfo will list your processor as an unknown model - of Cyrix. With it it will list the correct details. It should - be safe to say Y here regardless of what processor you are - actually using. If this option is not enabled none of the - Cyrix feature options are available. - -Enable suspend on halt power saving feature -CONFIG_CYRIX_SUSP_HLT - Suspend on halt causes the processor to enter a low power state - when the "hlt" instruction is executed. This is disabled at - power up and many BIOSs leave it that way. You probably want it - enabled since it dramatically reduces the operating temperature - of the processor. In a few rare cases there may be problems - with some bus master DMA cards if this is enabled. - -No I/O recovery delays -CONFIG_CYRIX_FAST_IO - Historically programmers used "jmp $+2" instructions to create - delays between I/O instructions. The branch prediction of 5x86 - and higher processors renders this ineffective and so a selectable - delay is implemented for I/O instructions in the processor. Linux - uses dummy I/O instructions where necessary rather than jumps - and so the extra processor imposed delay should not be necessary. - Enabling this option removes this delay. - -5x86 performance features -CONFIG_CYRIX_5X86 - The Cyrix 5x86 has several performance feature which are enabled - using on-chip registers. This code attempts to ensure that the - useful features are set to suit Linux. Read Documentation/CPU/Cyrix - before enabling this. - WARNING: If this is enabled you may find that the only way to - reboot is to power cycle the machine. Even a hard reboot seems - to fail on some systems. - -6x86 performance features -CONFIG_CYRIX_6X86 - The Cyrix 6x86 has several performance feature which are enabled - using on-chip registers. Most are normally enabled by the BIOS - however this code ensures that all the useful ones are set to - suit Linux. Read Documentation/CPU/Cyrix before enabling this. - -Avoid unnecessary locked cycles -CONFIG_CYRIX_6X86_NOLOCK - Enabling this option causes the 6x86 not to use locked bus cycles - except for page table access and interrupt acknowledge cycles. - This allows the data used by descriptor tables, xchg instructions - and instructions preceeded by the LOCK prefix to be cached leading - to improved performance. Enabling this option has no effect if - an SMP kernel is being built - SMP requires locked cycles to - guarantee processor synchronization. - -Allocate L1 cache lines on write misses -CONFIG_CYRIX_6X86_WTALLOC - If this is enabled L1 cache write misses will cause a cache line - to be allocated. This may result in increased performance. On the - other hand it may cause excessive trashing of the L1 cache when - copying or zeroing pages. In general you _probably_ win... - -Branch Target Buffer features -CONFIG_CYRIX_6X86_BTB - The Cyrix 6x86 has branch prediction logic which is normally - only set to handle short branches (as in small loops and ifs). - This code attempts on configure the branch prediction logic - appropriately. Read Documentation/CPU/Cyrix before enabling this. - -Variable sized paging mechanism (VSPM) -CONFIG_CYRIX_6X86_VSPM - Variable sized paging mechanism (VSPM) is a feature of the Cyrix - 6x86 family of processors that allows large regions of memory - to be mapped in one go, significantly reducing the amount of work - the MMU has to do compared with traditional paging. However VSPM - is known to be buggy in many 6x86 chip revisions. Please read - Documentation/CPU/Cyrix before enabling this. - WARNING: If this is enabled you may find that the only way to - reboot is to power cycle the machine. Even a hard reboot seems - to fail on some systems. - -Allocate L1 cache lines on write misses -CONFIG_AMD_K5_WTALLOC - If this is enabled L1 cache write misses will cause a cache line - to be allocated. This may result in increased performance. On the - other hand it may cause excessive trashing of the L1 cache when - copying or zeroing pages. In general you _probably_ win... - -Allocate L1 cache lines on write misses -CONFIG_AMD_K6_WTALLOC - If this is enabled L1 cache write misses will cause a cache line - to be allocated. This may result in increased performance. On the - other hand it may cause excessive trashing of the L1 cache when - copying or zeroing pages. In general you _probably_ win... - -Use write cacheability detection -CONFIG_AMD_K6_WTALLOC_WCDE - Write cacheability detection requires the system logic to assert - the cache enable bus signal during a write cycle. Some chipsets - do this and some do not. Some, such as Triton, do but not at - the appropriate point during the write cycle. Cacheability - detection is not normally useful unless you have memory mapped - devices which exist outside the 640k-1M range but within your - actual memory. (There is another option that disables write - allocate for the 15M-16M range commonly used by older VLB - video cards). You probably do not want to enable this. - -No write allocate between 15MB-16MB -CONFIG_AMD_K6_WTALLOC_WAE15M - There were a small number of cards, mainly VESA Local Bus - video cards, that were memory mapped to the 15M-16M address - range. If you have such a card you do not want write allocate - to delay or reorder writes to this space so you must enable - this option. Other memory mapped cards are either outside the - systems memory space or are in the 640k-1M range which is - not subject to write allocate so this option is not normally - required. +Mostek real time clock support +CONFIG_SUN_MOSTEK_RTC + +Siemens SAB82532 serial support +CONFIG_SAB82532 +### +### Please someone fill these in. +### # m68k-specific kernel options # Documented by Chris Lawrence <quango@themall.net> et al. @@ -6598,8 +7306,8 @@ CONFIG_BLZ1230_SCSI Fastlane SCSI support CONFIG_FASTLANE_SCSI - If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use one - in the near future, say Y to this question. Otherwise, say N. + If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use + one in the near future, say Y to this question. Otherwise, say N. Atari native SCSI support CONFIG_ATARI_SCSI @@ -6720,32 +7428,13 @@ CONFIG_ATARI_SCC whenever you want). If you want to compile it as a module, say M here and read Documentation/modules.txt. -Radio support -CONFIG_MISC_RADIO - If you have a radio card (you will probably know if you do!), then - you will want to say "y" here and make a character device file - (usually /dev/radio) with major number 10 and minor 152 using mknod - ("man mknod"). And then, don't forget to pick up some useful tools - to use said device (you _might_ find something at ftp.lmh.ox.ac.uk: - /users/weejock/linux/radio/, but I haven't written anything too - useful yet...) - -AIMSlab RadioTrack card -CONFIG_RADIO_RTRACK - Choose "y" here if you have one of these, and then fill in the port - address below. - -RadioTrack i/o port -CONFIG_RADIO_RTRACK_PORT - Enter either 0x30f or 0x20f here. The card default is 0x30f, if you - haven't changed the jumper setting on the card. - Atari SCC serial DMA support CONFIG_ATARI_SCC_DMA - This enables DMA support for receiving data on channel A of the SCC. If - you have a TT you may say Y here and read drivers/char/atari_SCC.README. - All other users should say N here, because only the TT has SCC-DMA, even - if your machine keeps claiming so at boot time. + This enables DMA support for receiving data on channel A of the + SCC. If you have a TT you may say Y here and read + drivers/char/atari_SCC.README. All other users should say N here, + because only the TT has SCC-DMA, even if your machine keeps claiming + so at boot time. Atari MIDI serial support CONFIG_ATARI_MIDI @@ -6851,7 +7540,10 @@ CONFIG_SCSI_MESH Many Power Macintoshes and clones have a MESH (Macintosh Enhanced SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the other Power Macintoshes do). Say Y to include support for this SCSI - adaptor. + adaptor. This driver is also available as a module called mesh.o ( + = code which can be inserted in and removed from the running kernel + whenever you want). If you want to compile it as a module, say M + here and read Documentation/modules.txt. Maximum synchronous transfer rate CONFIG_SCSI_MESH_SYNC_RATE @@ -6869,7 +7561,11 @@ CONFIG_SCSI_MAC53C94 On Power Macintoshes (and clones) with two SCSI buses, the external SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older machines which only have one SCSI bus, such as the 7200, also use - the 53C94. Say Y to include support for the 53C94. + the 53C94. Say Y to include support for the 53C94. This driver is + also available as a module called mac53c94.o ( = code which can be + inserted in and removed from the running kernel whenever you + want). If you want to compile it as a module, say M here and read + Documentation/modules.txt. MACE (Power Mac ethernet) support CONFIG_MACE @@ -6879,14 +7575,44 @@ CONFIG_MACE Video For Linux CONFIG_VIDEO_DEV - Support for audio/video capture and overlay devices. The exact capabilities - of each device vary. User tools for this are available from - ftp://ftp.uk.linux.org/pub/linux/video4linux + Support for audio/video capture and overlay devices. The exact + capabilities of each device vary. User tools for this are available + from ftp://ftp.uk.linux.org/pub/linux/video4linux. This driver is + also available as a module called videodev.o ( = code which can be + inserted in and removed from the running kernel whenever you + want). If you want to compile it as a module, say M here and read + Documentation/modules.txt. BT848 Video For Linux CONFIG_VIDEO_BT848 - Support for BT848 based frame grabber/overlay boards. This includes the - Miro, Hauppauge and STB boards. + Support for BT848 based frame grabber/overlay boards. This includes + the Miro, Hauppauge and STB boards. This driver is + also available as a module called bttv.o ( = code which can be + inserted in and removed from the running kernel whenever you + want). If you want to compile it as a module, say M here and read + Documentation/modules.txt. + +Quickcam BW Video For Linux +CONFIG_VIDEO_BWQCAM + Say Y have if you have such a thing. This driver is also available + as a module called bw-qcam.o ( = code which can be inserted in and + removed from the running kernel whenever you want). If you want to + compile it as a module, say M here and read + Documentation/modules.txt. + +Colour QuickCam Video For Linux +CONFIG_VIDEO_CQCAM + This is the video4linux driver for the colour version of the Connectix + Quickcam. If you have one of these cameras, say Y here, otherwise say N. + This driver does not work with the original monochrome Quickcam, + Quickcam VC or QuickClip. It is also available as a module (c-qcam.o). + +Mediavision Pro Movie Studio Video For Linux +CONFIG_VIDEO_PMS + Say Y if you have such a thing. This driver is also available as a + module called pms.o ( = code which can be inserted in and removed + from the running kernel whenever you want). If you want to compile + it as a module, say M here and read Documentation/modules.txt. # need an empty line after last entry, for sed script in Configure. @@ -7015,18 +7741,36 @@ CONFIG_VIDEO_BT848 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james -# LocalWords: caldera Preload dcache Preloading slowdowns schoebel uni -# LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS +# LocalWords: caldera Preload dcache Preloading slowdowns schoebel uni NBD nbd +# LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid # LocalWords: transname filespace adm Nodename hostname uname Kernelname bootp # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt SCB's RX # LocalWords: dataless kerneltype SYSNAME Netbeui Comtrol Rocketport palmtop # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY # LocalWords: HFMODEM shortwave Sitor Amtor Pactor GTOR hfmodem hayes TX TMOUT -# LocalWords: QIC TR CONFIG FTAPE Iomega CMS FC FDC Exabyte Iomega's DFLT -# LocalWords: tapedrive THR FCD IRQ DMA SZ PCI ftape README txt HOWTO -# LocalWords: http www rwth aachen LBFM claus FAQ mt ZFTAPE VFS -# LocalWords: zftape zft William's lzrw kerneld BLK zftape's tar's -# LocalWords: afio's MTSETBLK MTIOCTOP dev qft setblk BLKSZ NR -# LocalWords: setdrvbuffer kb NUMBUFFERS Procfs PROC FS proc resp STD -# LocalWords: Alt LocalWords +# LocalWords: IDEPCI IDEDMA idedma PDC pdc TRM trm raidtools luthien nuclecu +# LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS +# LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE +# LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM +# LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd +# LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate +# LocalWords: ipddp Decapsulation DECAP bool HAMRADIO WAN's tcpdump af CD's tx +# LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio LAN's +# LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO +# LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate +# LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched +# LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW +# LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu +# LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian +# LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ +# LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt +# LocalWords: charset Inuit Greenlandic Sami Lappish koi SOFTCURSOR softcursor +# LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's +# LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb +# LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer +# LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB +# LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax +# LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev +# LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS +# LocalWords: pms diff --git a/Documentation/IO-APIC.txt b/Documentation/IO-APIC.txt new file mode 100644 index 000000000..84ab57c19 --- /dev/null +++ b/Documentation/IO-APIC.txt @@ -0,0 +1,137 @@ + +most (all) Intel SMP boards have the so-called 'IO-APIC', which is +an enhanced interrupt controller, able to route hardware interrupts +to multiple CPUs, or to CPU groups. + +Linux supports the IO-APIC, but unfortunately there are broken boards +out there which make it unsafe to enable the IO-APIC unconditionally. +The Linux policy thus is to enable the IO-APIC only if it's 100% safe, ie.: + + - the board is on the 'whitelist' + + or - the board does not have PCI pins connected to the IO-APIC + + or - the user has overriden blacklisted settings with the + pirq= boot option line. + +Kernel messages tell you wether the board is 'safe'. If your box +boots with enabled IO-APIC IRQs, then you have nothing else to do. Your +/proc/interrupts will look like this one: + + ----------------------------> + hell:~> cat /proc/interrupts + CPU0 CPU1 + 0: 90782 0 XT PIC timer + 1: 4135 2375 IO-APIC keyboard + 2: 0 0 XT PIC cascade + 3: 851 807 IO-APIC serial + 9: 6 22 IO-APIC ncr53c8xx + 11: 307 154 IO-APIC NE2000 + 13: 4 0 XT PIC fpu + 14: 56000 30610 IO-APIC ide0 + NMI: 0 + IPI: 0 + <---------------------------- + +some interrupts will still be 'XT PIC', but this is not a problem, none +of those IRQ sources is 'heavy'. + +If one of your boot messages says 'unlisted/blacklisted board, DISABLING +IO-APIC IRQs', then you should do this to get multi-CPU IO-APIC IRQs +running: + + A) if your board is unlisted, then mail to linux-smp to get + it into either the white or the blacklist + B) if your board is blacklisted, then figure out the apropriate + pirq= option to get your system boot + + +pirq= lines look like the following in /etc/lilo.conf: + + append="pirq=15,11,10" + +the actual numbers depend on your system, on your PCI cards and on their +PCI slot position. Usually PCI slots are 'daisy chained' before they are +connected to the PCI chipset irq routing facility (the incoming PIRQ1-4 +lines): + + ,-. ,-. ,-. ,-. ,-. + PIRQ4 ----| |-. ,-| |-. ,-| |-. ,-| |--------| | + |S| \ / |S| \ / |S| \ / |S| |S| + PIRQ3 ----|l|-. `/---|l|-. `/---|l|-. `/---|l|--------|l| + |o| \/ |o| \/ |o| \/ |o| |o| + PIRQ2 ----|t|-./`----|t|-./`----|t|-./`----|t|--------|t| + |1| /\ |2| /\ |3| /\ |4| |5| + PIRQ1 ----| |- `----| |- `----| |- `----| |--------| | + `-' `-' `-' `-' `-' + +every PCI card emits a PCI IRQ, which can be INTA,INTB,INTC,INTD: + + ,-. + INTD--| | + |S| + INTC--|l| + |o| + INTB--|t| + |x| + INTA--| | + `-' + +These INTA-D PCI IRQs are always 'local to the card', their real meaning +depends on which slot they are in. If you look at the daisy chaining diagram, +a card in slot4, issuing INTA IRQ, it will end up as a signal on PIRQ2 of +the PCI chipset. Most cards issue INTA, this creates optimal distibution +between the PIRQ lines. (distributing IRQ sources properly is not a +necessity, PCI IRQs can be shared at will, but it's a good for performance +to have non shared interrupts). Slot5 should be used for videocards, they +dont use interrupts normally, thus they are not daisy chained either. + +so if you have your SCSI card (IRQ11) in Slot1, Tulip card (IRQ9) in +Slot2, then you'll have to specify this pirq= line: + + append="pirq=11,9" + +the following script tries to figure out such a default pirq= line from +your PCI configuration: + + echo -n pirq=; echo `scanpci | grep T_L | cut -c56-` | sed 's/ /,/g' + +note that this script wont work if you have skipped a few slots or if your +board does not do default daisy-chaining. (or the IO-APIC has the PIRQ pins +connected in some strange way). Eg. if in the above case you have your SCSI +card (IRQ11) in Slot3, and have Slot1 empty: + + append="pirq=0,9,11" + +[value '0' is a generic 'placeholder', reserved for empty (or non-IRQ emitting) +slots.] + +generally, it's always possible to find out the correct pirq= settings, just +permutate all IRQ numbers properly ... it will take some time though. An +'incorrect' pirq line will cause the booting process to hang, or a device +wont function properly (if it's inserted as eg. a module). + +If you have 2 PCI buses, then you can use up to 8 pirq values. Although such +boards tend to have a good configuration and will be included in the +whitelist. + +Be prepared that it might happen that you need some strange pirq line: + + append="pirq=0,0,0,0,0,0,9,11" + +use smart try-and-err techniques to find out the correct pirq line ... + + +the following pirq line can be used to force a board into the whitelist: + + append="pirq=0" + +[if your system works with no problems after this, then it should be added +to the official whitelist, contact us] + +good luck and mail to linux-smp@vger.rutgers.edu or +linux-kernel@vger.rutger.edu if you have any problems that are not covered +by this document. + +-- mingo + diff --git a/Documentation/binfmt_misc.txt b/Documentation/binfmt_misc.txt index 0adcf7185..6a8b87aff 100644 --- a/Documentation/binfmt_misc.txt +++ b/Documentation/binfmt_misc.txt @@ -54,10 +54,10 @@ A few examples (assumed you are in /proc/sys/fs/binfmt_misc): - enable support for packed DOS applications (pre-configured dosemu hdimages): echo ':DEXE:M::\x0eDEX::/usr/bin/dosexec:' > register -- enable support for DOS/Windows executables (using mzloader and dosemu/wine): - echo ':DOSWin:M::MZ::/usr/sbin/mzloader:' > register - echo ':DOScom:E::com::/usr/sbin/mzloader:' > register - echo ':DOSexe:E::exe::/usr/sbin/mzloader:' > register +- enable support for Windows executables using wine: + echo ':DOSWin:M::MZ::/usr/local/bin/wine:' > register + +For java support see Documentation/java.txt You can enable/disable binfmt_misc or one binary type by echoing 0 (to disable) @@ -68,73 +68,12 @@ You can remove one entry or all entries by echoing -1 to /proc/.../the_name or /proc/sys/fs/binfmt_misc/status. -Emulating binfmt_java: -====================== - -To emulate binfmt_java the following register-strings could be used: -for compiled Java programs use - ':Java:M::\xca\xfe\xba\xbe::/usr/local/java/bin/javawrapper:' -for simple applet support use - ':Applet:E::html::/usr/local/java/bin/appletviewer:' -for more selective applet support (like binfmt_java) use - ':Applet:M::<!--applet::/usr/local/java/bin/appletviewer:' - -Note, that for the more selective applet support you have to modify -existing html-files to contain <!--applet--> in the first line to -let this work! - -For the compiled Java programs you need a wrapper script like the -following (this is because Java is broken in case of the filename -handling): - -====================== Cut here =================== -#!/bin/bash -# /usr/local/java/bin/javawrapper - the wrapper for binfmt_misc/java -CLASS=$1 - -# if classname is a link, we follow it (this could be done easier - how?) -if [ -L "$1" ] ; then - CLASS=`ls --color=no -l $1 | tr -s '\t ' ' ' | cut -d ' ' -f 11` -fi -CLASSN=`basename $CLASS .class` -CLASSP=`dirname $CLASS` - -FOO=$PATH -PATH=$CLASSPATH -if [ -z "`type -p -a $CLASSN.class`" ] ; then - # class is not in CLASSPATH - if [ -e "$CLASSP/$CLASSN.class" ] ; then - # append dir of class to CLASSPATH - if [ -z "${CLASSPATH}" ] ; then - export CLASSPATH=$CLASSP - else - export CLASSPATH=$CLASSP:$CLASSPATH - fi - else - # uh! now we would have to create a symbolic link - really - # ugly, i.e. print a message that one has to change the setup - echo "Hey! This is not a good setup to run $1 !" - exit 1 - fi -fi -PATH=$FOO - -shift -/usr/local/java/bin/java $CLASSN $@ -====================== Cut here =================== - -To add a Java program to your path best put a symbolic link to the main -.class file into /usr/bin (or another place you like) omitting the .class -extension. The directory containing the original .class file will be -added to your CLASSPATH during execution. - - - HINTS: ====== If you want to pass special arguments to your interpreter, you can -write a wrapper script for it. +write a wrapper script for it. See Documentation/java.txt for an +example. Your interpreter should NOT look in the PATH for the filename; the kernel passes it the full filename to use. Using the PATH can cause diff --git a/Documentation/cdrom/00-INDEX b/Documentation/cdrom/00-INDEX index fee4a7e66..c8b428bf1 100644 --- a/Documentation/cdrom/00-INDEX +++ b/Documentation/cdrom/00-INDEX @@ -2,8 +2,6 @@ - this file (info on CD-ROMs and Linux) aztcd - info on Aztech/Orchid/Okano/Wearnes/Conrad/CyCDROM driver. -bpcd - - info on MicroSolutions backpack CDROM cdrom-standard.tex - LaTeX document on standardizing the CD-ROM programming interface. diff --git a/Documentation/cdrom/bpcd b/Documentation/cdrom/bpcd deleted file mode 100644 index 877d7fe05..000000000 --- a/Documentation/cdrom/bpcd +++ /dev/null @@ -1,74 +0,0 @@ -linux/Documentation/cdrom/bpcd (c) 1996 Grant R. Guenther <grant@torque.net> - -This file documents the bpcd driver for the MicroSolutions backpack CDrom, -an external parallel port device. - -There are apparently two versions of the backpack protocol. This -driver knows about the version 2 protocol - as is used in the 4x -and 6x products. There is no support for the sound hardware that -is included in some models. It should not be difficult to add -support for the ATAPI audio play functions and the corresponding -ioctls. - -The driver was developed by reverse engineering the protocol -and testing it on the backpack model 164550. This model -is actually a stock ATAPI drive packaged with a custom -ASIC that implements the IDE over parallel protocol. -I tested with a backpack that happened to contain a Goldstar -drive, but I've seen reports of Sony and Mitsumi drives as well. - -Before attempting to use the driver, you will need to -create a new device special file. The following commands will -do that for you: - - mknod /dev/bpcd b 41 0 - chown root:disk /dev/bpcd - chmod 660 /dev/bpcd - -Afterward, you can mount a disk in the usual way: - - mount -t iso9660 /dev/bpcd /cdrom - -(assuming you have made a directory /cdrom to use as a mount point). - -The driver will attempt to detect which parallel port your -backpack is connected to. If this fails for any reason, you -can override it by specifying a port on the LILO command line -(for built in drivers) or the insmod command (for drivers built -as modules). If your drive is on the port at 0x3bc, you would -use one of these commands: - - LILO: bpcd=0x3bc - - insmod: insmod bpcd bp_base=0x3bc - -The driver can detect if the parallel port supports 8-bit -transfers. If so, it will use them. You can force it to use -4-bit (nybble) mode by setting the variable bp_nybble to 1 on -an insmod command, or using the following LILO parameters: - - bpcd=0x3bc,1 - -(you must specify the correct port address if you use this method.) - -There is currently no support for EPP or ECP modes. Also, -as far as I can tell, the MicroSolutions protocol does not -support interrupts in the 4-bit and 8-bit modes. - -MicroSolutions' protocol allows for several drives to be -chained together off the same parallel port. Currently, this -driver will recognise only one of them. If you do have more -than one drive, it will choose the one with the lowest id number, -where the id number is the last two digits of the product's -serial number. - -It is not currently possible to connect a printer to the chained -port on the BackPack and expect Linux to use both devices at once. -If you need to use this driver together with a printer on the -same port, build both the bpcd and lp drivers as modules. - -Keep an eye on http://www.torque.net/bpcd.html for news and -other information about the driver. If you have any problems -with this driver, please send me, grant@torque.net, some mail -directly before posting into the newsgroups or mailing lists. - diff --git a/Documentation/cdrom/cdrom-standard.tex b/Documentation/cdrom/cdrom-standard.tex index 6f1af1c18..1db560b15 100644 --- a/Documentation/cdrom/cdrom-standard.tex +++ b/Documentation/cdrom/cdrom-standard.tex @@ -1,5 +1,5 @@ \documentclass{article} -\def\version{$Id: cdrom-standard.tex,v 1.8 1997/11/19 21:58:33 david Exp $} +\def\version{$Id: cdrom-standard.tex,v 1.9 1997/12/28 15:42:49 david Exp $} \newcommand{\newsection}[1]{\newpage\section{#1}} \evensidemargin=0pt @@ -388,46 +388,6 @@ CDS_DISC_OK& a disc is loaded and everything is fine\cr } $$ -\subsection{$Disc_status$} -\label{disc status} - -As a complement to $drive_status()$, this function can provide {\emph -{some}} information about the current disc that is inserted in the -drive. This function is now implemented internally in the \UCD, so the -low-level drivers do not need to implement this functionality anymore. - -The history of development of the CD's use as a carrier medium for -various digital information has lead to many different disc types. This -$ioctl$ makes the false assumption that CDs have {\emph {only one}} type -of data on them. While this is often the case, it is also very common -for CDs to have some tracks with data, and some tracks with audio. -Because this is an existing interface, rather than fixing this interface -by changing the assumptions it was made under, thereby breaking all user -applications that use this function, the \UCD\ implements this $ioctl$ -as follows: If the CD in question has audio tracks on it, and it has -absolutly no CD-I, XA, or data tracks on it, it will be reported as -$CDS_AUDIO$. Failing that, if the CD in question has any CD-I tracks -on it, it will be reported as $CDS_XA_2_2$. Failing that, if the CD in -question has any XA tracks on it, it will be reported as $CDS_XA_2_1$. -Finally, if the CD in question has any data tracks on it, it will be -reported as a data CD ($CDS_DATA_1$). - -This function can return: -$$ -\halign{$#$\ \hfil&$/*$ \rm# $*/$\hfil\cr -CDS_NO_INFO& no information available\cr -CDS_NO_DISC& no disc is inserted, or tray is opened\cr -CDS_AUDIO& Audio disc (2352 audio bytes/frame)\cr -CDS_DATA_1& data disc, mode 1 (2048 user bytes/frame)\cr -CDS_DATA_2& data disc, mode 2 (2336 user bytes/frame)\cr -CDS_XA_2_1& mixed data (XA), mode 2, form 1 (2048 user bytes)\cr -CDS_XA_2_2& mixed data (XA), mode 2, form 1 (2324 user bytes)\cr -} -$$ -As far as I know, data \cdrom s are always of type $CDS_DATA_1$. For -some information concerning frame layout of the various disc types, see -a recent version of \cdromh. - \subsection{$Int\ media_changed(struct\ cdrom_device_info * cdi, int\ disc_nr)$} This function is very similar to the original function in $struct\ @@ -940,8 +900,46 @@ the current flags. given. The special value $CDSL_CURRENT$ requests that information about the currently selected slot is returned. \item[CDROM_DISC_STATUS] Returns the type of the disc currently in the - drive by a call to $disc_status()$. Return values are as defined in - section~\ref{disc status}. + drive. It should be viewed as a complement to $CDROM_DRIVE_STATUS$. + This $ioctl$ can provide \emph {some} information about the current + disc that is inserted in the drive. This functionality used to be + implemented in the low level drivers, but is now carried out + entirely in \UCD. + + The history of development of the CD's use as a carrier medium for + various digital information has lead to many different disc types. + This $ioctl$ is useful only in the case that CDs have \emph {only + one} type of data on them. While this is often the case, it is + also very common for CDs to have some tracks with data, and some + tracks with audio. Because this is an existing interface, rather + than fixing this interface by changing the assumptions it was made + under, thereby breaking all user applications that use this + function, the \UCD\ implements this $ioctl$ as follows: If the CD in + question has audio tracks on it, and it has absolutly no CD-I, XA, + or data tracks on it, it will be reported as $CDS_AUDIO$. If it has + both audio and data tracks, it will return $CDS_MIXED$. If there + are no audio tracks on the disc, and if the CD in question has any + CD-I tracks on it, it will be reported as $CDS_XA_2_2$. Failing + that, if the CD in question has any XA tracks on it, it will be + reported as $CDS_XA_2_1$. Finally, if the CD in question has any + data tracks on it, it will be reported as a data CD ($CDS_DATA_1$). + + This $ioctl$ can return: + $$ + \halign{$#$\ \hfil&$/*$ \rm# $*/$\hfil\cr + CDS_NO_INFO& no information available\cr + CDS_NO_DISC& no disc is inserted, or tray is opened\cr + CDS_AUDIO& Audio disc (2352 audio bytes/frame)\cr + CDS_DATA_1& data disc, mode 1 (2048 user bytes/frame)\cr + CDS_DATA_2& data disc, mode 2 (2336 user bytes/frame)\cr + CDS_XA_2_1& mixed data (XA), mode 2, form 1 (2048 user bytes)\cr + CDS_XA_2_2& mixed data (XA), mode 2, form 1 (2324 user bytes)\cr + CDS_MIXED& mixed audio/data disc\cr + } + $$ + For some information concerning frame layout of the various disc + types, see a recent version of \cdromh. + \item[CDROM_CHANGER_NSLOTS] Returns the number of slots in a juke-box. \end{description} @@ -1021,4 +1019,3 @@ the first place. $ \version\ $ \eject \end{document} - diff --git a/Documentation/cdrom/ide-cd b/Documentation/cdrom/ide-cd index 70384d975..d6ceef8a5 100644 --- a/Documentation/cdrom/ide-cd +++ b/Documentation/cdrom/ide-cd @@ -1,12 +1,12 @@ IDE-CD driver documentation -19 May 1996 -scott snyder <snyder@fnald0.fnal.gov> +Originally by scott snyder <snyder@fnald0.fnal.gov> (19 May 1996) +Carrying on the torch is: Erik Andersen <andersee@debian.org> 1. Introduction --------------- -The ide-cd driver should work with all ATAPI 1.2 compliant cdrom -drives which attach to an IDE interface. Note that some cdrom vendors +The ide-cd driver should work with all ATAPI ver 1.2 to ATAPI 2.6 compliant +cdrom drives which attach to an IDE interface. Note that some cdrom vendors (including Mitsumi, Sony, Creative, Aztech, and Goldstar) have made both ATAPI-compliant drives and drives which use a proprietary interface. If your drive uses one of those proprietary interfaces, @@ -28,9 +28,7 @@ This driver provides the following features: - On drives which support it, reading digital audio data directly from audio tracks. The program cdda2wav can be used for this. - Note, however, that only a few drives actually support this - function; the only ones which i've heard of successes with are Sony - and Toshiba drives. + Note, however, that only some drives actually support this. - There is now support for cdrom changers which comply with the ATAPI 2.6 draft standard (such as the NEC CDR-251). This additional @@ -50,10 +48,13 @@ This driver provides the following features: driver. 1. Make sure that the ide and ide-cd drivers are compiled into the - kernel you're using. When configuring the kernel, say `yes' to the - options + kernel you're using. When configuring the kernel, in the section + entitled "Floppy, IDE, and other block devices", say either `Y' + (which will compile the support directly into the kernel) or `M' + (to compile support as a module which can be loaded and unloaded) + to the options: - Enhanced IDE/MFM/RLL disk/cdrom/tape support + Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support Include IDE/ATAPI CDROM support and `no' to @@ -74,8 +75,8 @@ This driver provides the following features: address and an IRQ number, the standard assignments being 0x170 and 14 for the primary interface and 0x1f0 and 15 for the secondary interface. Each interface can control up to two devices, - where each device can be either a hard drive, a cdrom drive, or a - tape drive. The two devices on an interface are called `master' + where each device can be a hard drive, a cdrom drive, a floppy drive, + or a tape drive. The two devices on an interface are called `master' and `slave'; this is usually selectable via a jumper on the drive. Linux names these devices as follows. The master and slave devices @@ -223,7 +224,9 @@ a. Drive is not detected during booting. - If the autoprobing is not finding your drive, you can tell the driver to assume that one exists by using a lilo option of the form `hdX=cdrom', where X is the drive letter corresponding to - where your drive is installed (see section 2). Note that if you + where your drive is installed (see section 2). This is required + for CDROM drives such as the Pioneer DR-A24X, which do not properly + identify themselves as ATAPI CDROM drives. Note that if you do this and you see a boot message like hdX: ATAPI cdrom (?) diff --git a/Documentation/cyrix.txt b/Documentation/cyrix.txt deleted file mode 100644 index 203bc8b8f..000000000 --- a/Documentation/cyrix.txt +++ /dev/null @@ -1,201 +0,0 @@ - Cyrix Processor Support - ----------------------- - -Processor Recognition ---------------------- - -Cyrix processors prior to the 6x86MX power up in a default mode -designed to avoid compatibility problems with software that -makes assumptions about processor capabilities based solely on -the apparent family of processor. Unless special handling is -provided Cyrix chips will be identified as some unknown model -of 486. - - The Cyrix processor recognition kernel build option compiles -in code that enables the CPUID instruction on Cyrix processors -and that uses the Cyrix specific DEVID feature to identify the -particular type of Cyrix chip present. - - The 6x86MX and later processors have CPUID enabled by default -however special handling is still required to read the specific -processor type using DEVID since the CPUID information gives -family 6, model 0 - i.e. an A step PPro. - - The combination of CPUID and DEVID allows all current Cyrix -processors to be recognised and listed correctly in /proc/cpuinfo. -This includes Cx486, 5x86, 6x86, Gx86 (aka MediaGx) and 6x86MX. - - Processor recognition is required for all other Cyrix specific -options. - - -Suspend on Halt Power Saving ----------------------------- - -The suspend on halt power saving feature allows the processor to -enter a low power mode when the "hlt" instruction is executed. This -results in dramatically reduced operating temperatures if you do -not spend long periods of time running processor intensive tasks. -Cyrix processors allow this feature to be enabled an disabled -through their configuration registers. The default state on reset -is disabled and many (most?) BIOSs leave it disabled hence a -kernel configuration option is provided that adds code to explicitly -enabled suspend on halt when Linux boots. - - However there appear to be a few rare cases in which the -combination of suspend on halt and some bus master DMA cards can -cause the system to lock up. If this appears to happen you may -need to leave suspend on halt in its default state. (Note that -an option to _disable_ suspend on halt is not provided. If your -BIOS enables it you have to live with it) - - -5x86 Performance Features -------------------------- - -The 5x86 contains a performance control register that allows -several performance enhancing features to be turned on. Unfortunately -many of these features do not appear to work correctly. The 5x86 -performance features kernel build option will attempt to set -the performance control register appropriately but it is -impossible to guarantee that even these conservative settings -will work on all chips. - - WARNING: If this is enabled you may find that the only way to -reboot is to power cycle the machine. Even a hard reboot seems -to fail on some systems. - - -6x86 Performance Features -------------------------- - -Like the 5x86 the 6x86 has several Cyrix specific performance -features. Normally a 6x86 aware BIOS will set these to reasonable, -if not fully optimal, settings. The 6x86 performance features -kernel build option mostly just fine tunes them. - - -6x86 Branch Prediction ----------------------- - -The 6x86 uses speculative execution coupled with several levels -of branch prediction to maximise processing speed. While the -default power up state is reasonable the branch prediction logic -is configurable and there may be some benefit in fine tuning it. - - Unfortunately Cyrix offer no documentation on how to configure -branch prediction and IBM have only partial documentation available. -Further detail and speculation is available from the 6x86opt package -by Mikael Johansson <Mikael.Johansson@helsinki.fi>. - - The initial power up state of the 6x86 configures the branch -prediction logic to handle short branches. The 6x86 branch target -buffer features kernel build option enables code that enables -handling of long branches as well. It is not clear if this will -benefit in your particular case or not. - - -6x86 Variable Sized Paging Mechanism ------------------------------------- - -The variable sized paging mechanism (VSPM) is a feature of the Cyrix -6x86 family of processors that allows large regions of memory -to be mapped using a single MMU entry rather than many individual -page sized entries. This significantly reduces the overhead in -accessing such regions. It is also ideally suited to use for the -linear mapping of physical memory to kernel memory used by Linux. - - The Cyrix documenation offers only a brief paragraph of explanation. -Unfortunately the observed behaviour of VSPM suggests that even -this little information is not entirely correct. Worse still, no one -at Cyrix is able to answer questions concerning VSPM. Given that -every revision of 6x86 has *different* VSPM bugs this is not entirely -surprising! Work arounds are in place for the known bugs in step 1, -revisions 4, 5 and 6 chips. Revision 7 is also believed to work. - - WARNING: There appears to be no way to disable a VSPM entry once -it has been created short of a hard reset (which may mean a power -cycle). Failure to clear the VSPM entries means that programs that -use virtual memory layouts different from Linux will crash unexpectedly -after Linux has been running. This includes Windows NT/95, programs -that use DOS extenders etc. - - By experiment: - - * VSPM pages must be power of two sizes. A single 24MB page fails. - This is not entirely surprising but the documentation could give - the impression that VSPM supports arbitrary sizes. - - * Documentation suggests there are 8 VSPM slots (3 bit index) but - tests show the upper four slots mirror the lower four. - - * VSPM entries appear to override traditional page table entries - so we must not overlap the start of the vmalloc region. - - The following only apply to 1 rev 6 and lower chips. 1 rev 7 and - above do not appear to have these problems. - - * With a 16MB page followed by an 8MB page I always get a write - fault on the last 4k of the 8MB page. With 8MB plus 4MB I can't - even boot. - If we have such a memory size we map the first power of two - with a VSPM entry and use traditional paging for the rest. - - * Do not try and create a mapping with dirty and accessed flags - clear - a step 1 rev 5 chip will crash. - - * The valid bit in a VSPM entry is non-functional. There is no way - to invalidate a VSPM entry once it has been written. - - * Attempting to replace a VSPM entry with one that maps a zero - sized region from 0 to 0 crashes the CPU. - - -What more could be done ------------------------ - - Disabling write allocate while we do page copies/clears will -avoid unnecessary cache trashing. However it will also reduce -the apparent memory bandwidth for the operation so it runs -slower (with write allocate the write to memory becomes delayed -and happens asynchronously). Rumour has it that disabling -write allocate for such operations is generally good on an -Intel chip. Disabling and re-enabling write allocate on a -Cyrix would take and extra 60-65 clock cycles each. - - The 6x86 allows Address regions to be set up and en/disabling -certain features for these regions. In order to optimize, we could -analyse the setup done (or not done) by the BIOS and optimize it. -However, it is worth noting that the BIOS probably has more -hardware specific details coded in it than we could ever determine -by any form of probing so if it sets something up in a particular -way the motherboard designers may have had very good reasons for -doing it. Trying to play fast and loose may not be such a good -idea for the general case. - - * Setting up regions fo the main memory: RCE, WWO, WL(?), WG - - * Setting up VGA text (0x000a0000) and graphics memory (PCI: - e.g. 0xe0000000) to RCD, WG - - * Setting up BIOS regions to RCD or RCE, WT - - * Not touching SMM space (ARR3) - - * Disabling WG for Memory Mapped IO - -(RCE/D = Region cache enable/disable, WWO = Weak Write Ordering, -WL = Weak Locking, WG = Write Gathering, WT = Write Through.) - - -Where to get information ------------------------- - - There is a databook in PDF format (6X-DBOOK.PDF), which can be down- -loaded from Cyrix' WWW server, which contains a description of the -Configuration Registers CCR0 - CCR5, the Device Identification Registers -DIR0 + DIR1 and the Address Region ARRx and Region Control -RCRx registers and an incomplete description of the VSPM mechanism. -More about CPU detection, VSPM and more undocumented features can be -found on the Pentium Compiler Group homepage (http://www.goof.com/pcg) -and by following the links found in the docs. diff --git a/Documentation/devices.tex b/Documentation/devices.tex index cbca53433..15e06fd2d 100644 --- a/Documentation/devices.tex +++ b/Documentation/devices.tex @@ -4,7 +4,7 @@ % pages to print... :-) If you're actually putting this in print, you % may wish to change these. % -% $Id: devices.tex,v 1.4 1997/12/05 01:34:21 hpa Exp $ +% $Id: devices.tex,v 1.7 1998/02/18 04:07:45 hpa Exp $ % \oddsidemargin=0in \textwidth=6.5in @@ -50,7 +50,7 @@ foo \kill}% % \title{{\bf Linux Allocated Devices}} \author{Maintained by H. Peter Anvin $<$hpa@zytor.com$>$} -\date{Last revised: December 4, 1997} +\date{Last revised: February 17, 1998} \maketitle % \noindent @@ -199,6 +199,7 @@ Your cooperation is appreciated. \major{47}{}{char }{Comtrol Rocketport serial card -- alternate devices} \major{ }{}{block}{Reserved for parallel port ATAPI disk} \major{48}{}{char }{SDL RISCom serial card} +\major{48}{--55}{block}{Reserved for Mylex DAC960 PCI RAID Controller} \major{49}{}{char }{SDL RISCom serial card -- alternate devices} \major{50}{}{char }{Reserved for GLINT} \major{51}{}{char }{Baycom radio modem} @@ -243,8 +244,10 @@ Your cooperation is appreciated. \major{93}{}{char }{IBM Smart Capture Card frame grabber} \major{94}{}{char }{miroVIDEO DC10/30 capture/playback device} \major{95}{}{char }{IP Filter} -\major{96}{}{char }{Reserved for parallel port ATAPI tape} -\major{97}{--119}{}{Unallocated} +\major{96}{}{char }{Parallel port ATAPI tape} +\major{97}{}{char }{Parallel port generic ATAPI interface} +\major{98}{}{char }{Control and Measurement Device (comedi)} +\major{99}{--119}{}{Unallocated} \major{120}{--127}{}{Local/experimental use} \major{128}{--239}{}{Unallocated} \major{240}{--254}{}{Local/experimental use} @@ -299,6 +302,11 @@ the 1st through 16th series of 16 pseudo-ttys each, and the position within the series. \end{itemize} +\noindent +In the future, it is likely that the PTY master multiplex ({\file +/dev/ptmx}) device will be used to acquire a PTY on demand. If so, +the actual PTY masters will be unnamed devices. + \begin{devicelist} \major{}{}{block}{Floppy disks} \minor{0}{/dev/fd0}{Controller 1, drive 1 autodetect} @@ -325,7 +333,7 @@ the position within the series. \minor{ 72}{/dev/fd?h1494}{5.25\tum\ 1494K in a 1200K drive} \minor{ 92}{/dev/fd?h1600}{5.25\tum\ 1600K in a 1200K drive\1} \minor{}{}{} - \minor{ 12}{/dev/fd?u360}{3.5\tum\ \num{4}{360}K Double Density} + \minor{ 12}{/dev/fd?u360}{3.5\tum\ \num{4}{360}K Double Density\2} \minor{ 16}{/dev/fd?u720}{3.5\tum\ \num{4}{720}K Double Density\1} \minor{120}{/dev/fd?u800}{3.5\tum\ \num{4}{800}K Double Density\2} \minor{ 52}{/dev/fd?u820}{3.5\tum\ \num{4}{820}K Double Density} @@ -366,7 +374,13 @@ these devices. \minor{1}{/dev/ttyp1}{Second PTY slave} \minordots \minor{255}{/dev/ttyef}{256th PTY slave} -\\ +\end{devicelist} + +\noindent +In the future, Linux may adopt the Unix98 naming scheme {\file +/dev/pts/0}, {\file /dev/pts/1}, ... + +\begin{devicelist} \major{}{}{block}{First MFM, RLL and IDE hard disk/CD-ROM interface} \minor{0}{/dev/hda}{Master: whole disk (or CD-ROM)} \minor{64}{/dev/hdb}{Slave: whole disk (or CD-ROM)} @@ -412,6 +426,7 @@ Linux. To ensure proper operation, do not mix old and new PTY devices. \major{ 5}{}{char }{Alternate TTY devices} \minor{0}{/dev/tty}{Current TTY device} \minor{1}{/dev/console}{System console} + \minor{2}{/dev/ptmx}{PTY master multiplex} \minor{64}{/dev/cua0}{Callout device corresponding to {\file ttyS0}} \minordots \minor{127}{/dev/cua63}{Callout device corresponding to {\file ttyS63}} @@ -1087,8 +1102,10 @@ networking device. \end{devicelist} \noindent -Partitions are handled the same way as for IDE disks (see major number -3). +This device is obsolete and will be removed in a future version of +Linux. It has been replaced with the parallel port IDE disk driver at +major number 45. Partitions are handled the same way as for IDE disks +(see major number 3). \begin{devicelist} \major{41}{}{char }{Yet Another Micro Monitor} @@ -1098,6 +1115,11 @@ Partitions are handled the same way as for IDE disks (see major number \minor{0}{/dev/bpcd}{BackPack CD-ROM} \end{devicelist} +\noindent +This device is obsolete and will be removed in a future version of +Linux. It has been replaced with the parallel port ATAPI CD-ROM +driver at major number 46. + \begin{devicelist} \major{42}{}{}{Demo/sample use} \end{devicelist} @@ -1163,13 +1185,30 @@ disk (same as SCSI.) \minordots \minor{191}{/dev/ippp63}{64th SyncPPP device} \minor{255}{/dev/isdninfo}{ISDN monitor interface} +\\ +\major{ }{}{block}{Parallel port IDE disk devices} + \minor{0}{/dev/pda}{First parallel port IDE disk} + \minor{16}{/dev/pdb}{Second parallel port IDE disk} + \minor{32}{/dev/pdc}{Third parallel port IDE disk} + \minor{48}{/dev/pdd}{Fourth parallel port IDE disk} \end{devicelist} +\noindent +Partitions are handled in the same way as for IDE disks (see major +number 3) except that the partition limit is 15 rather than 63 per +disk. + \begin{devicelist} \major{46}{}{char }{Comtrol Rocketport serial card} \minor{0}{/dev/ttyR0}{First Rocketport port} \minor{1}{/dev/ttyR1}{Second Rocketport port} \minordots +\\ +\major{ }{}{block}{Parallel port ATAPI CD-ROM devices} + \minor{0}{/dev/pcd0}{First parallel port ATAPI CD-ROM} + \minor{1}{/dev/pcd1}{Second parallel port ATAPI CD-ROM} + \minor{2}{/dev/pcd2}{Third parallel port ATAPI CD-ROM} + \minor{3}{/dev/pcd3}{Fourth parallel port ATAPI CD-ROM} \end{devicelist} \begin{devicelist} @@ -1177,13 +1216,25 @@ disk (same as SCSI.) \minor{0}{/dev/cur0}{Callout device corresponding to {\file ttyR0}} \minor{1}{/dev/cur1}{Callout device corresponding to {\file ttyR1}} \minordots +\\ +\major{ }{}{block}{Parallel port ATAPI disk devices} + \minor{0}{/dev/pf0}{First parallel port ATAPI disk} + \minor{1}{/dev/pf1}{Second parallel port ATAPI disk} + \minor{2}{/dev/pf2}{Third parallel port ATAPI disk} + \minor{3}{/dev/pf3}{Fourth parallel port ATAPI disk} \end{devicelist} +\noindent +This driver is intended for floppy disks and similar devices and hence +does not support partitioning. + \begin{devicelist} \major{48}{}{char }{SDL RISCom serial card} \minor{0}{/dev/ttyL0}{First RISCom port} \minor{1}{/dev/ttyL1}{Second RISCom port} \minordots +\\ +\major{ }{}{block}{Reserved for Mylex DAC960 PCI RAID Controller} \end{devicelist} \begin{devicelist} @@ -1191,10 +1242,14 @@ disk (same as SCSI.) \minor{0}{/dev/cul0}{Callout device corresponding to {\file ttyL0}} \minor{1}{/dev/cul1}{Callout device corresponding to {\file ttyL1}} \minordots +\\ +\major{ }{}{block}{Reserved for Mylex DAC960 PCI RAID Controller} \end{devicelist} \begin{devicelist} \major{50}{}{char}{Reserved for GLINT} +\\ +\major{ }{}{block}{Reserved for Mylex DAC960 PCI RAID Controller} \end{devicelist} \begin{devicelist} @@ -1202,6 +1257,8 @@ disk (same as SCSI.) \minor{0}{/dev/bc0}{First Baycom radio modem} \minor{1}{/dev/bc1}{Second Baycom radio modem} \minordots +\\ +\major{ }{}{block}{Reserved for Mylex DAC960 PCI RAID Controller} \end{devicelist} \begin{devicelist} @@ -1210,6 +1267,8 @@ disk (same as SCSI.) \minor{1}{/dev/dcbri1}{Second DataComm card} \minor{2}{/dev/dcbri2}{Third DataComm card} \minor{3}{/dev/dcbri3}{Fourth DataComm card} +\\ +\major{ }{}{block}{Reserved for Mylex DAC960 PCI RAID Controller} \end{devicelist} \begin{devicelist} @@ -1230,6 +1289,10 @@ interface. PD is the Motorola Public Domain Interface and ICD is the commercial interface by P\&E. \begin{devicelist} +\major{ }{}{block}{Reserved for Mylex DAC960 PCI RAID Controller} +\end{devicelist} + +\begin{devicelist} \major{54}{}{char }{Electrocardiognosis Holter serial card} \minor{0}{/dev/holter0}{First Holter port} \minor{1}{/dev/holter1}{Second Holter port} @@ -1242,8 +1305,14 @@ $<$mseritan@ottonel.pub.ro$>$ to transfer data from Holter 24-hour heart monitoring equipment. \begin{devicelist} +\major{ }{}{block}{Reserved for Mylex DAC960 PCI RAID Controller} +\end{devicelist} + +\begin{devicelist} \major{55}{}{char }{DSP56001 digital signal processor} \minor{0}{/dev/dsp56k}{First DSP56001} +\\ +\major{ }{}{block}{Reserved for Mylex DAC960 PCI RAID Controller} \end{devicelist} \begin{devicelist} @@ -1582,7 +1651,41 @@ on {\url http://home.pages.de/~videotext/\/}. \end{devicelist} \begin{devicelist} -\major{96}{--119}{}{Unallocated} +\major{96}{}{char }{Parallel port ATAPI tape devices} + \minor{0}{/dev/pt0}{First parallel port ATAPI tape} + \minor{1}{/dev/pt1}{Second parallel port ATAPI tape} + \minor{2}{/dev/pt2}{Third parallel port ATAPI tape} + \minor{3}{/dev/pt3}{Fourth parallel port ATAPI tape} + \minor{128}{/dev/npt0}{First parallel port ATAPI tape, no rewind} + \minor{129}{/dev/npt1}{Second parallel port ATAPI tape, no rewind} + \minor{130}{/dev/npt2}{Third parallel port ATAPI tape, no rewind} + \minor{131}{/dev/npt3}{Fourth parallel port ATAPI tape, no rewind} +\end{devicelist} + +\begin{devicelist} +\major{97}{}{char }{Parallel port generic ATAPI interface} + \minor{0}{/dev/pg0}{First parallel port ATAPI device} + \minor{1}{/dev/pg1}{Second parallel port ATAPI device} + \minor{2}{/dev/pg2}{Third parallel port ATAPI device} + \minor{3}{/dev/pg3}{Fourth parallel port ATAPI device} +\end{devicelist} + +\noindent +These devices support the same API as the generic SCSI devices. + +\begin{devicelist} +\major{98}{}{char }{Control and Mesurement Device (comedi)} + \minor{0}{/dev/comedi0}{First comedi device} + \minor{1}{/dev/comedi1}{Second comedi device} + \minordots +\end{devicelist} + +\noindent +See {\url http://stm.lbl.gov/comedi/} or {\url +http://www.llp.fu-berlin.de/}. + +\begin{devicelist} +\major{99}{--119}{}{Unallocated} \end{devicelist} \begin{devicelist} diff --git a/Documentation/devices.txt b/Documentation/devices.txt index 3f229ff41..2242044f6 100644 --- a/Documentation/devices.txt +++ b/Documentation/devices.txt @@ -1,7 +1,7 @@ LINUX ALLOCATED DEVICES Maintained by H. Peter Anvin <hpa@zytor.com> - Last revised: December 4, 1997 + Last revised: February 17, 1998 This list is the Linux Device List, the official registry of allocated device numbers and /dev directory nodes for the Linux operating @@ -91,6 +91,11 @@ Your cooperation is appreciated. the 1st through 16th series of 16 pseudo-ttys each, and * the fifth letter is one of 0123456789abcdef indicating the position within the series. + + In the future, it is likely that the PTY master + multiplex (/dev/ptmx) device will be used to acquire a + PTY on demand. If so, the actual PTY masters will be + unnamed devices. block Floppy disks 0 = /dev/fd0 First floppy disk autodetect @@ -112,9 +117,10 @@ Your cooperation is appreciated. 72 = /dev/fd?h1494 5.25" 1494K in a 1200K drive 92 = /dev/fd?h1600 5.25" 1600K in a 1200K drive(1) - 12 = /dev/fd?u360 3.5" 360K Double Density - 120 = /dev/fd?u800 3.5" 800K Double Density(1) - 52 = /dev/fd?u820 3.5" 820K Double Density(2) + 12 = /dev/fd?u360 3.5" 360K Double Density(2) + 16 = /dev/fd?u720 3.5" 720K Double Density(1) + 120 = /dev/fd?u800 3.5" 800K Double Density(2) + 52 = /dev/fd?u820 3.5" 820K Double Density 68 = /dev/fd?u830 3.5" 830K Double Density 84 = /dev/fd?u1040 3.5" 1040K Double Density(1) 88 = /dev/fd?u1120 3.5" 1120K Double Density(1) @@ -148,12 +154,15 @@ Your cooperation is appreciated. 0 = /dev/ttyp0 First PTY slave 1 = /dev/ttyp1 Second PTY slave ... - 256 = /dev/ttyef 256th PTY slave + 255 = /dev/ttyef 256th PTY slave + + In the future, Linux may adopt the Unix98 naming + scheme (/dev/pts/0, /dev/pts/1, ...) block First MFM, RLL and IDE hard disk/CD-ROM interface 0 = /dev/hda Master: whole disk (or CD-ROM) 64 = /dev/hdb Slave: whole disk (or CD-ROM) - + For partitions, add to the whole disk device number: 0 = /dev/hd? Whole disk 1 = /dev/hd?1 First partition @@ -165,7 +174,7 @@ Your cooperation is appreciated. partitions, and 5 and above are logical partitions. Other versions of Linux use partitioning schemes appropriate to their respective architectures. - + 4 char TTY devices 0 = /dev/tty0 Current virtual console @@ -192,6 +201,7 @@ Your cooperation is appreciated. 5 char Alternate TTY devices 0 = /dev/tty Current TTY device 1 = /dev/console System console + 2 = /dev/ptmx PTY master multiplex 64 = /dev/cua0 Callout device corresponding to ttyS0 ... 127 = /dev/cua63 Callout device corresponding to ttyS63 @@ -738,6 +748,9 @@ Your cooperation is appreciated. block Syquest EZ135 parallel port removable drive 0 = /dev/eza Parallel EZ135 drive, whole disk + This device is obsolete and will be removed in a + future version of Linux. It has been replaced with + the parallel port IDE disk driver at major number 45. Partitions are handled in the same way as IDE disks (see major number 3). @@ -746,6 +759,10 @@ Your cooperation is appreciated. block MicroSolutions BackPack parallel port CD-ROM 0 = /dev/bpcd BackPack CD-ROM + This device is obsolete and will be removed in a + future version of Linux. It has been replaced with + the parallel port ATAPI CD-ROM driver at major number 46. + 42 Demo/sample use This number is intended for use in sample code, as @@ -803,39 +820,66 @@ Your cooperation is appreciated. 191 = /dev/ippp63 64th SyncPPP device 255 = /dev/isdninfo ISDN monitor interface + block Parallel port IDE disk devices + 0 = /dev/pda First parallel port IDE disk + 16 = /dev/pdb Second parallel port IDE disk + 32 = /dev/pdc Third parallel port IDE disk + 48 = /dev/pdd Fourth parallel port IDE disk + + Partitions are handled in the same way as for IDE + disks (see major number 3) except that the partition + limit is 15 rather than 63 per disk. 46 char Comtrol Rocketport serial card 0 = /dev/ttyR0 First Rocketport port 1 = /dev/ttyR1 Second Rocketport port ... + block Parallel port ATAPI CD-ROM devices + 0 = /dev/pcd0 First parallel port ATAPI CD-ROM + 1 = /dev/pcd1 Second parallel port ATAPI CD-ROM + 2 = /dev/pcd2 Third parallel port ATAPI CD-ROM + 3 = /dev/pcd3 Fourth parallel port ATAPI CD-ROM 47 char Comtrol Rocketport serial card - alternate devices 0 = /dev/cur0 Callout device corresponding to ttyR0 1 = /dev/cur1 Callout device corresponding to ttyR1 ... + block Parallel port ATAPI disk devices + 0 = /dev/pf0 First parallel port ATAPI disk + 1 = /dev/pf1 Second parallel port ATAPI disk + 2 = /dev/pf2 Third parallel port ATAPI disk + 3 = /dev/pf3 Fourth parallel port ATAPI disk + + This driver is intended for floppy disks and similar + devices and hence does not support partitioning. 48 char SDL RISCom serial card 0 = /dev/ttyL0 First RISCom port 1 = /dev/ttyL1 Second RISCom port ... + block Reserved for Mylex DAC960 PCI RAID controller 49 char SDL RISCom serial card - alternate devices 0 = /dev/cul0 Callout device corresponding to ttyL0 1 = /dev/cul1 Callout device corresponding to ttyL1 ... + block Reserved for Mylex DAC960 PCI RAID controller 50 char Reserved for GLINT + block Reserved for Mylex DAC960 PCI RAID controller 51 char Baycom radio modem 0 = /dev/bc0 First Baycom radio modem 1 = /dev/bc1 Second Baycom radio modem ... + block Reserved for Mylex DAC960 PCI RAID controller 52 char Spellcaster DataComm/BRI ISDN card 0 = /dev/dcbri0 First DataComm card 1 = /dev/dcbri1 Second DataComm card 2 = /dev/dcbri2 Third DataComm card 3 = /dev/dcbri3 Fourth DataComm card + block Reserved for Mylex DAC960 PCI RAID controller 53 char BDM interface for remote debugging MC683xx microcontrollers 0 = /dev/pd_bdm0 PD BDM interface on lp0 @@ -851,6 +895,8 @@ Your cooperation is appreciated. Domain Interface and ICD is the commercial interface by P&E. + block Reserved for Mylex DAC960 PCI RAID controller + 54 char Electrocardiognosis Holter serial card 0 = /dev/holter0 First Holter port 1 = /dev/holter1 Second Holter port @@ -860,8 +906,11 @@ Your cooperation is appreciated. <mseritan@ottonel.pub.ro> to transfer data from Holter 24-hour heart monitoring equipment. + block Reserved for Mylex DAC960 PCI RAID controller + 55 char DSP56001 digital signal processor 0 = /dev/dsp56k First DSP56001 + block Reserved for Mylex DAC960 PCI RAID controller 56 char Apple Desktop Bus 0 = /dev/adb ADB bus control @@ -1116,7 +1165,33 @@ Your cooperation is appreciated. 2 = /dev/ipstate State information log file 3 = /dev/ipauth Authentication control device/log file - 96-119 UNALLOCATED + 96 char Parallel port ATAPI tape devices + 0 = /dev/pt0 First parallel port ATAPI tape + 1 = /dev/pt1 Second parallel port ATAPI tape + 2 = /dev/pt2 Third parallel port ATAPI tape + 3 = /dev/pt3 Fourth parallel port ATAPI tape + 128 = /dev/npt0 First p.p. ATAPI tape, no rewind + 129 = /dev/npt1 Second p.p. ATAPI tape, no rewind + 130 = /dev/npt2 Third p.p. ATAPI tape, no rewind + 131 = /dev/npt3 Fourth p.p. ATAPI tape, no rewind + + 97 char Parallel port generic ATAPI interface + 0 = /dev/pg0 First parallel port ATAPI device + 1 = /dev/pg1 Second parallel port ATAPI device + 2 = /dev/pg2 Third parallel port ATAPI device + 3 = /dev/pg3 Fourth parallel port ATAPI device + + These devices support the same API as the generic SCSI + devices. + + 98 char Control and Measurement Device (comedi) + 0 = /dev/comedi0 First comedi device + 1 = /dev/comedi1 Second comedi device + ... + + See http://stm.lbl.gov/comedi or http://www.llp.fu-berlin.de/. + + 99-119 UNALLOCATED 120-127 LOCAL/EXPERIMENTAL USE diff --git a/Documentation/digiboard.txt b/Documentation/digiboard.txt index 0a49a427f..ab1490ada 100644 --- a/Documentation/digiboard.txt +++ b/Documentation/digiboard.txt @@ -254,3 +254,35 @@ sh /dev/MAKEDEV digi ;; par[0-2]) ----- End Makedev patch + +----------------------------------------------------------------------------- + +Changes v1.5.5: + +The ability to use the kernel's command line to pass in the configuration for +boards. Using LILO's APPEND command, a string of comma separated identifiers +or integers can be used. The 6 values in order are: + + Enable/Disable this card, + Type of card: PC/Xi(0), PC/Xe(1), PC/Xeve(2), PC/Xem(3) + Enable/Disable alternate pin arrangement, + Number of ports on this card, + I/O Port where card is configured (in HEX if using string identifiers), + Base of memory window (in HEX if using string identifiers), + +Samples: + append="digi=E,PC/Xi,D,16,200,D0000" + append="digi=1,0,0,16,512,(whatever D0000 is in base 10 :) + +Driver's minor device numbers are conserved. This means that instead of +each board getting a block of 16 minors pre-assigned, it gets however +many it should, with the next card following directly behind it. A +system with 4 2-port PC/Xi boards will use minor numbers 0-7. +This conserves some memory, and removes a few hard coded constants. + +NOTE!! NOTE!! NOTE!! +The definition of PC/Xem as a valid board type is the BEGINNING of support +for this device. The driver does not currently recognise the board, nor +does it want to initialize it. At least not the EISA version. + +Mike McLagan <mike.mclagan@linux.org> 5, April 1996. diff --git a/Documentation/ez.txt b/Documentation/ez.txt deleted file mode 100644 index 9fb314e14..000000000 --- a/Documentation/ez.txt +++ /dev/null @@ -1,85 +0,0 @@ -linux/Documentation/ez.txt (c) 1996 Grant R. Guenther <grant@torque.net> - -This file documents the ez driver for the parallel port versions of -SyQuest's EZ135 and EZ230 removable media disk drives. - -Special thanks go to Pedro Soria-Rodriguez for his help testing -the EZFlyer 230 support. - -The drive is actually SyQuest's IDE product with a ShuttleTech -IDE <-> parallel converter chip built in. - -Before attempting to access the new driver, you will need to -create some device special files. The following commands will -do that for you: - - mknod /dev/eza b 40 0 - mknod /dev/eza1 b 40 1 - mknod /dev/eza2 b 40 2 - mknod /dev/eza3 b 40 3 - mknod /dev/eza4 b 40 4 - chown root:disk /dev/ez* - chmod 660 /dev/ez* - -You can make devices for more partitions (up to 15) if you need to. - -You can alter certain driver parameters on the LILO or LOADLIN -command line. The general syntax is - - ez=base[,irq] - -where base is the base address of the parallel port you want to use -and irq is the interrupt number for that port. By default, the -driver uses the ports at 0x378 and irq 7. You can disable the -interrupt by specifying it as 0. For example, to run the driver -on port 0x3bc without an interrupt, you would append the following -to the LILO command line: - - ez=0x3bc,0 - -If you have configured the driver as a loadable module, you can -adjust these parameters on the insmod command line using the -variables ez_base and ez_irq. For example: - - insmod ez ez_base=0x3bc - -The driver can detect if the parallel port supports 8-bit -transfers. If so, it will use them. - -The driver can be used with or without interrupts. If an IRQ -is specified the driver will use it - if it can. If the irq -number is set to 0, an alternative, polling-based, strategy -will be used. Polling consumes more CPU time, but may be more -stable on some systems. - -If you experience timeout errors while using this driver - and -you have enabled interrupts - try disabling the interrupt. I -have heard reports of some parallel ports having exceptionally -unreliable interrupts. This could happen on misconfigured -systems in which an inactive sound card shares the same IRQ with -the parallel port. (Remember that most people do not use the -parallel port interrupt for printing.) - -It would be advantageous to use multiple mode transfers, -but ShuttleTech's driver does not appear to use them, so I'm not -sure that the converter can handle it. - -It is not currently possible to connect a printer to the chained -port on an EZ drive and expect Linux to use both devices at once. -If you need to do this, build both the ez and lp drivers as modules -and load one or the other as required. - -When the EZ230 powers on, the "standby timer" is set to about 6 -minutes: if the drive is idle for that length of time, it will -put itself into a low power standby mode. It takes a couple of -seconds for the drive to come out of standby mode. So, if you -load this driver while it is in standby mode, you will notice -a "freeze" of a second or two as the driver waits for the EZ230 -to come back to life. Once loaded, this driver disables the -standby timer (until you next power up the EZ230 ...) - -Keep an eye on http://www.torque.net/ez135.html for news and -other information about the driver. If you have any problems -with this driver, please send me, grant@torque.net, some mail -directly before posting into the newsgroups or mailing lists. - diff --git a/Documentation/filesystems/affs.txt b/Documentation/filesystems/affs.txt index bc892a75b..4c5d7fa7a 100644 --- a/Documentation/filesystems/affs.txt +++ b/Documentation/filesystems/affs.txt @@ -65,6 +65,11 @@ quiet The file system will not return an error for disallowed verbose The volume name, file system type and block size will be written to the syslog when the filesystem is mounted. +mufs The filesystem is really a muFS, also it doesn't + identify itself as one. This option is neccessary if + the filesystem wasn't formatted as muFS, but is used + as one. + prefix=path Path will be prefixed to every absolute path name of symbolic links on an AFFS partition. Default = / diff --git a/Documentation/filesystems/coda.txt b/Documentation/filesystems/coda.txt index 829fd2d20..f049c02a6 100644 --- a/Documentation/filesystems/coda.txt +++ b/Documentation/filesystems/coda.txt @@ -1,3 +1,27 @@ + +NOTE: +This is one of the technical documents describing a component of +Coda -- this document describes the client kernel-Venus interface. + +For more information: + http://www.coda.cs.cmu.edu +For user level software needed to run Coda: + ftp://ftp.coda.cs.cmu.edu + +To run Coda you need to get a user level cache manager for the client, +named Venus, as well as tools to manipulate ACL's, to log in etc. The +client needs to have the Coda filesystem selected in the kernel +configuration. + +The server needs a user level server and at present does not depend on +kernel support. + + + + + + + The Venus kernel interface Peter J. Braam v1.0, Nov 9, 1997 @@ -8,103 +32,128 @@ (version 1.0) as well as improvements we envisage. ______________________________________________________________________ - Table of Contents: + Table of Contents + + + + + + + + + + + + + + + + + + + - 1. Introduction - 2. Servicing Coda filesystem calls - 3. The message layer - 3.1. Implementation details - 4. The interface at the call level - 4.1. Data structures shared by the kernel and Venus - 4.2. The pioctl interface - 4.3. root - 4.4. lookup - 4.5. getattr - 4.6. setattr - 4.7. access - 4.8. create - 4.9. mkdir - 4.10. link - 4.11. synlink - 4.12. remove - 4.13. rmdir - 4.14. readlink - 4.15. open - 4.16. close - 4.17. ioctl - 4.18. rename - 4.19. readdir - 4.20. vget - 4.21. fsync - 4.22. inactive - 4.23. rdwr - 4.24. odymount - 4.25. ody_lookup - 4.26. ody_expand - 4.27. prefetch - 4.28. signal - 5. The minicache and downcalls - 5.1. INVALIDATE - 5.2. FLUSH + 1. Introduction - 5.3. PURGEUSER + 2. Servicing Coda filesystem calls - 5.4. ZAPFILE + 3. The message layer - 5.5. ZAPDIR + 3.1 Implementation details - 5.6. ZAPVNODE + 4. The interface at the call level - 5.7. PURGEFID + 4.1 Data structures shared by the kernel and Venus + 4.2 The pioctl interface + 4.3 root + 4.4 lookup + 4.5 getattr + 4.6 setattr + 4.7 access + 4.8 create + 4.9 mkdir + 4.10 link + 4.11 symlink + 4.12 remove + 4.13 rmdir + 4.14 readlink + 4.15 open + 4.16 close + 4.17 ioctl + 4.18 rename + 4.19 readdir + 4.20 vget + 4.21 fsync + 4.22 inactive + 4.23 rdwr + 4.24 odymount + 4.25 ody_lookup + 4.26 ody_expand + 4.27 prefetch + 4.28 signal - 5.8. REPLACE + 5. The minicache and downcalls + + 5.1 INVALIDATE + 5.2 FLUSH + 5.3 PURGEUSER + 5.4 ZAPFILE + 5.5 ZAPDIR + 5.6 ZAPVNODE + 5.7 PURGEFID + 5.8 REPLACE + + 6. Initialization and cleanup + + 6.1 Requirements - 6. Initialization and cleanup - 6.1. Requirements ______________________________________________________________________ 0wpage 11.. IInnttrroodduuccttiioonn + + A key component in the Coda Distributed File System is the cache manager, _V_e_n_u_s. + When processes on a Coda enabled system access files in the Coda filesystem, requests are directed at the filesystem layer in the operating system. The operating system will communicate with Venus to @@ -168,7 +217,7 @@ the Coda FS layer, so the Coda FS driver must expose the VFS interface as applicable in the operating system. These differ very significantly among operating systems, but share features such as facilities to - read/write and create and remove object. The Coda FS layer services + read/write and create and remove objects. The Coda FS layer services such VFS requests in by invoking on or more well defined services offered by the cache manager Venus. When the replies from Venus have come back to the FS driver, servicing of the VFS call continues and @@ -176,13 +225,18 @@ returns to the process. As a result of this design a basic interface exposed by the FS driver - must allow Venus to handle manage message traffic. In particular - Venus must be able to retrieve and place messages and to be notified - of the arrival of a new message. The notification must be through a - mechanism which does not block Venus since Venus must attend to other - tasks even when no messages are waiting or being processed. + must allow Venus to manage message traffic. In particular Venus must + be able to retrieve and place messages and to be notified of the + arrival of a new message. The notification must be through a mechanism + which does not block Venus since Venus must attend to other tasks even + when no messages are waiting or being processed. + + - Interfaces of Coda FS Driver + + + + Interfaces of the Coda FS Driver Furthermore the FS layer provides for a special path of communication between a user process and Venus, called the pioctl interface. The @@ -210,8 +264,10 @@ 33.. TThhee mmeessssaaggee llaayyeerr + + At the lowest level the communication between Venus and the FS driver - proceeds through messages. The synchronization of between processes + proceeds through messages. The synchronization between processes requesting Coda file service and Venus relies on blocking and waking up processes. The Coda FS driver processes VFS- and pioctl-requests on behalf of a process P, creates messages for Venus, awaits replies @@ -256,6 +312,7 @@ namely when Venus calls sendmsg_to_kernel. At this moment the Coda FS driver looks at the contents of the message and decides if: + +o the message is a reply for a suspended thread P. If so it removes the message from the processing queue and marks the message as WRITTEN. Finally, the FS driver unblocks P (still in the kernel @@ -266,7 +323,7 @@ +o The message is a _d_o_w_n_c_a_l_l. A downcall is a request from Venus to the FS Driver. The FS driver processes the request immediately - (usually a cach eviction or replacement) and when finishes + (usually a cache eviction or replacement) and when finishes sendmsg_to_kernel returns. Now P awakes and continues processing upcall. There are some @@ -277,6 +334,12 @@ deallocate message structure and return. The FS routine can proceed with its processing. + + + + + + Sleeping and IPC arrangements In case P is woken up by a signal and not by Venus, it will first look @@ -291,6 +354,8 @@ extra field "handle_signals" could be added in the message structure to indicate points of no return have been passed.--) + + 33..11.. IImmpplleemmeennttaattiioonn ddeettaaiillss The Unix implementation of this mechanism has been through the @@ -312,11 +377,13 @@ 44.. TThhee iinntteerrffaaccee aatt tthhee ccaallll lleevveell + This section describes the upcalls a Coda FS driver can make to Venus. Each of these upcalls make use of two structures: inputArgs and outputArgs. In pseudo BNF form the structures take the following form: + struct inputArgs { u_long opcode; u_long unique; /* Keep multiple outstanding msgs distinct */ @@ -335,6 +402,8 @@ <union "out" of call dependent parts of inputArgs> }; + + Before going on let us elucidate the role of the various fields. The inputArgs start with the opcode which defines the type of service requested from Venus. There are approximately 30 upcalls at present @@ -346,8 +415,12 @@ Before delving into the specific calls we need to discuss a variety of data structures shared by the kernel and Venus. + + + 44..11.. DDaattaa ssttrruuccttuurreess sshhaarreedd bbyy tthhee kkeerrnneell aanndd VVeennuuss + The CodaCred structure defines a variety of user and group id's as they are set for the calling process. The vuid_t and guid_t are 32 bit unsigned integers. It also defines group member ship in an array. On @@ -361,10 +434,13 @@ vgid_t cr_groups[NGROUPS]; /* Group membership for caller */ }; + + NNOOTTEE It is questionable if we need CodaCreds in Venus. Finally Venus doesn't know about groups, although it does create files with the default uid/gid. Perhaps the list of group membership is superfluous. + The next item is the fundamental identifier used to identify Coda files, the ViceFid. A fid of a file uniquely defines a file or directory in the Coda filesystem within a _c_e_l_l. (-- A _c_e_l_l is a @@ -372,12 +448,15 @@ control machine or SCM. See the Coda Administration manual for a detailed description of the role of the SCM.--) + typedef struct ViceFid { VolumeId Volume; VnodeId Vnode; Unique_t Unique; } ViceFid; + + Each of the constituent fields: VolumeId, VnodeId and Unique_t are unsigned 32 bit integers. We envisage that a further field will need to be prefixed to identify the Coda cell; this will probably take the @@ -388,6 +467,23 @@ exchange information. It has room for future extensions such as support for device files (currently not present in Coda). + + + + + + + + + + + + + + + + + struct coda_vattr { enum coda_vtype va_type; /* vnode type (for create) */ u_short va_mode; /* files access mode and type */ @@ -410,9 +506,13 @@ long va_spare; /* remain quad aligned */ }; + + + 44..22.. TThhee ppiiooccttll iinntteerrffaaccee - Coda specific requests can be made by application through a pioctl + + Coda specific requests can be made by application through the pioctl interface. The pioctl is implemented as an ordinary ioctl on a ficticious file /coda/.CONTROL. The piocl call opens this file, gets a file handle and makes the ioctl call. Finally it closes the file. @@ -429,14 +529,19 @@ int follow; } data; + + where + struct ViceIoctl { caddr_t in, out; /* Data to be transferred in, or out */ short in_size; /* Size of input buffer <= 2K */ short out_size; /* Maximum size of output buffer, <= 2K */ }; + + The path must be a Coda file, otherwise the ioctl upcall will not be made. @@ -449,6 +554,7 @@ 44..33.. rroooott + AArrgguummeennttss iinn empty @@ -459,6 +565,8 @@ ViceFid VFid; } cfs_root; + + DDeessccrriippttiioonn This call is made to Venus during the initialization of the Coda filesystem. If the result is zero, the cfs_root structure contains the ViceFid of the root of the Coda filesystem. If a non-zero @@ -470,6 +578,7 @@ 44..44.. llooookkuupp + SSuummmmaarryy Find the ViceFid and type of an object in a directory if it exists. @@ -482,6 +591,8 @@ char *name; /* Place holder for data. */ } cfs_lookup; + + oouutt struct cfs_lookup_out { @@ -489,6 +600,8 @@ int vtype; } cfs_lookup; + + DDeessccrriippttiioonn This call is made to determine the ViceFid and filetype of a directory entry. The directory entry requested carries name name and Venus will search the directory identified by cfs_lookup_in.VFid. @@ -512,6 +625,7 @@ 44..55.. ggeettaattttrr + SSuummmmaarryy Get the attributes of a file. AArrgguummeennttss @@ -523,12 +637,16 @@ struct coda_vattr attr; /* XXXXX */ } cfs_getattr; + + oouutt struct cfs_getattr_out { struct coda_vattr attr; } cfs_getattr; + + DDeessccrriippttiioonn This call returns the attributes of the file identified by fid. @@ -549,6 +667,7 @@ 44..66.. sseettaattttrr + SSuummmmaarryy Set the attributes of a file. AArrgguummeennttss @@ -560,6 +679,9 @@ struct coda_vattr attr; } cfs_setattr; + + + oouutt empty @@ -577,6 +699,7 @@ 44..77.. aacccceessss + SSuummmmaarryy AArrgguummeennttss @@ -588,11 +711,13 @@ int flags; } cfs_access; + + oouutt empty DDeessccrriippttiioonn Verify if access to the object identified by VFid for - operetions described by flags is permitted. The result indicates if + operations described by flags is permitted. The result indicates if access will be granted. It is important to remember that Coda uses ACL's to enforce protection and that ultimately the servers, not the clients enforce the security of the system. The result of this call @@ -605,6 +730,7 @@ 44..88.. ccrreeaattee + SSuummmmaarryy Invoked to create a file AArrgguummeennttss @@ -619,6 +745,9 @@ char *name; /* Place holder for data. */ } cfs_create; + + + oouutt struct cfs_create_out { @@ -626,6 +755,8 @@ struct coda_vattr attr; } cfs_create; + + DDeessccrriippttiioonn This upcall is invoked to request creation of a file. The file will be created in the directory identified by VFid, its name will be name, and the mode will be mode. If excl is set an error will @@ -637,6 +768,7 @@ instantiate a vnode, inode or filehandle at kernel level for the new object. + EErrrroorrss A variety of errors can occur. Permissions may be insufficient. If the object exists and is not a file the error EISDIR is returned under Unix. @@ -657,6 +789,7 @@ 44..99.. mmkkddiirr + SSuummmmaarryy Create a new directory. AArrgguummeennttss @@ -669,6 +802,8 @@ char *name; /* Place holder for data. */ } cfs_mkdir; + + oouutt struct cfs_mkdir_out { @@ -676,6 +811,9 @@ struct coda_vattr attr; } cfs_mkdir; + + + DDeessccrriippttiioonn This call is similar to create but creates a directory. Only the mode field in the input parameters is used for creation. Upon successful creation, the attr returned contains the attributes of @@ -693,6 +831,7 @@ 44..1100.. lliinnkk + SSuummmmaarryy Create a link to an existing file. AArrgguummeennttss @@ -705,6 +844,8 @@ char *tname; /* Place holder for data. */ } cfs_link; + + oouutt empty @@ -716,7 +857,8 @@ EErrrroorrss The usual errors can occur.0wpage - 44..1111.. ssyynnlliinnkk + 44..1111.. ssyymmlliinnkk + SSuummmmaarryy create a symbolic link @@ -731,12 +873,14 @@ char *tname; } cfs_symlink; + + oouutt none DDeessccrriippttiioonn Create a symbolic link. The link is to be placed in the directory identified by VFid and named tname. It should point to the - pathname srcname. The attributes of the newly creaeted object are to + pathname srcname. The attributes of the newly created object are to be set to attr. EErrrroorrss @@ -748,6 +892,7 @@ 44..1122.. rreemmoovvee + SSuummmmaarryy Remove a file AArrgguummeennttss @@ -759,6 +904,8 @@ char *name; /* Place holder for data. */ } cfs_remove; + + oouutt none @@ -774,6 +921,7 @@ 44..1133.. rrmmddiirr + SSuummmmaarryy Remove a directory AArrgguummeennttss @@ -785,6 +933,8 @@ char *name; /* Place holder for data. */ } cfs_rmdir; + + oouutt none @@ -800,6 +950,7 @@ 44..1144.. rreeaaddlliinnkk + SSuummmmaarryy Read the value of a symbolic link. AArrgguummeennttss @@ -810,6 +961,8 @@ ViceFid VFid; } cfs_readlink; + + oouutt struct cfs_readlink_out { @@ -817,6 +970,8 @@ caddr_t data; /* Place holder for data. */ } cfs_readlink; + + DDeessccrriippttiioonn This routine reads the contents of symbolic link identified by VFid into the buffer data. The buffer data must be able to hold any name up to CFS_MAXNAMLEN (PATH or NAM??). @@ -827,6 +982,7 @@ 44..1155.. ooppeenn + SSuummmmaarryy Open a file. AArrgguummeennttss @@ -838,6 +994,8 @@ int flags; } cfs_open; + + oouutt struct cfs_open_out { @@ -845,6 +1003,8 @@ ino_t inode; } cfs_open; + + DDeessccrriippttiioonn This request asks Venus to place the file identified by VFid in its cache and to note that the calling process wishes to open it with flags as in open(2). The return value to the kernel differs @@ -852,7 +1012,6 @@ informed of the device and inode number of the container file in the fields dev and inode. For Windows the path of the container file is returned to the kernel. - EErrrroorrss NNOOTTEE Currently the cfs_open_out structure is not properly adapted to @@ -864,6 +1023,7 @@ 44..1166.. cclloossee + SSuummmmaarryy Close a file, update it on the servers. AArrgguummeennttss @@ -875,6 +1035,8 @@ int flags; } cfs_close; + + oouutt none @@ -896,6 +1058,7 @@ 44..1177.. iiooccttll + SSuummmmaarryy Do an ioctl on a file. This includes the piocl interface. AArrgguummeennttss @@ -910,13 +1073,18 @@ char *data; /* Place holder for data. */ } cfs_ioctl; + + oouutt + struct cfs_ioctl_out { int len; caddr_t data; /* Place holder for data. */ } cfs_ioctl; + + DDeessccrriippttiioonn Do an ioctl operation on a file. The command, len and data arguments are filled as usual. flags is not used by Venus. @@ -925,10 +1093,12 @@ NNOOTTEE Another bogus parameter. flags is not used. What is the business about PREFETCHING in the Venus' code? + 0wpage 44..1188.. rreennaammee + SSuummmmaarryy Rename a fid. AArrgguummeennttss @@ -942,6 +1112,8 @@ char *destname; } cfs_rename; + + oouutt none @@ -956,6 +1128,7 @@ 44..1199.. rreeaaddddiirr + SSuummmmaarryy Read directory entries. AArrgguummeennttss @@ -968,6 +1141,9 @@ int offset; } cfs_readdir; + + + oouutt struct cfs_readdir_out { @@ -975,6 +1151,8 @@ caddr_t data; /* Place holder for data. */ } cfs_readdir; + + DDeessccrriippttiioonn Read directory entries from VFid starting at offset and read at most count bytes. Returns the data into data and indicates the size returned size. @@ -989,15 +1167,18 @@ 44..2200.. vvggeett + SSuummmmaarryy instructs Venus to do an FSDB->Get. AArrgguummeennttss iinn - struct cfs_fsync_in { + struct cfs_vget_in { ViceFid VFid; - } cfs_fsync; + } cfs_vget; + + oouutt @@ -1006,6 +1187,8 @@ int vtype; } cfs_vget; + + DDeessccrriippttiioonn This upcall asks Venus to do a get operation on an fsobj labelled by VFid. @@ -1020,6 +1203,7 @@ 44..2211.. ffssyynncc + SSuummmmaarryy Tell Venus to update the RVM attributes of a file. AArrgguummeennttss @@ -1030,6 +1214,8 @@ ViceFid VFid; } cfs_fsync; + + oouutt none @@ -1045,6 +1231,7 @@ 44..2222.. iinnaaccttiivvee + SSuummmmaarryy Tell Venus a vnode is no longer in use. AArrgguummeennttss @@ -1055,6 +1242,8 @@ ViceFid VFid; } cfs_inactive; + + oouutt none @@ -1068,6 +1257,7 @@ 44..2233.. rrddwwrr + SSuummmmaarryy Read or write from a file AArrgguummeennttss @@ -1083,6 +1273,9 @@ caddr_t data; /* Place holder for data. */ } cfs_rdwr; + + + oouutt struct cfs_rdwr_out { @@ -1091,6 +1284,8 @@ caddr_t data; /* Place holder for data. */ } cfs_rdwr; + + DDeessccrriippttiioonn This upcall asks Venus to read or write from a file. EErrrroorrss @@ -1099,10 +1294,12 @@ read/write operations never reach Venus. I have been told the operation does not work. It is not currently used. + 0wpage 44..2244.. ooddyymmoouunntt + SSuummmmaarryy Allows mounting multiple Coda "filesystems" on one Unix mount point. @@ -1114,12 +1311,16 @@ char *name; /* Place holder for data. */ } ody_mount; + + oouutt struct ody_mount_out { ViceFid VFid; } ody_mount; + + DDeessccrriippttiioonn Asks Venus to return the rootfid of a Coda system named name. The fid is returned in VFid. @@ -1133,12 +1334,14 @@ 44..2255.. ooddyy__llooookkuupp + SSuummmmaarryy Looks up something. AArrgguummeennttss iinn irrelevant + oouutt irrelevant @@ -1152,6 +1355,7 @@ 44..2266.. ooddyy__eexxppaanndd + SSuummmmaarryy expands something in a dynamic set. AArrgguummeennttss @@ -1171,6 +1375,7 @@ 44..2277.. pprreeffeettcchh + SSuummmmaarryy Prefetch a dynamic set. AArrgguummeennttss @@ -1188,10 +1393,12 @@ NNOOTTEE Gut it. It isn't working and isn't used by Coda. + 0wpage 44..2288.. ssiiggnnaall + SSuummmmaarryy Send Venus a signal about an upcall. AArrgguummeennttss @@ -1219,6 +1426,7 @@ 55.. TThhee mmiinniiccaacchhee aanndd ddoowwnnccaallllss + The Coda FS Driver can cache results of lookup and access upcalls, to limit the frequency of upcalls. Upcalls carry a price since a process context switch needs to take place. The counterpart of caching the @@ -1227,8 +1435,8 @@ The kernel code generally has to maintain a structure which links the internal file handles (called vnodes in BSD, inodes in Linux and - FileHandles in Windows) with the ViceFid's which Venus maintains. - Ther reason is that frequent translations back and forth are needed in + FileHandles in Windows) with the ViceFid's which Venus maintains. The + reason is that frequent translations back and forth are needed in order to make upcalls and use the results of upcalls. Such linking objects are called ccnnooddeess. @@ -1246,7 +1454,7 @@ The lookup call in the Coda FS Driver may request the cnode of the desired object from the cache, by passing it's name, directory and the CodaCred's of the caller. The cache will return the cnode or indicate - and it cannot be found. The Coda FS Driver must be careful to + that it cannot be found. The Coda FS Driver must be careful to invalidate cache entries when it modifies or removes objects. When Venus obtains information that indicates that cache entries are @@ -1255,12 +1463,17 @@ the kind described below. The Coda FS Driver does not return an error unless the downcall data could not be read into kernel memory. + 55..11.. IINNVVAALLIIDDAATTEE + No information is available on this call. + 55..22.. FFLLUUSSHH + + AArrgguummeennttss None SSuummmmaarryy Flush the name cache entirely. @@ -1270,25 +1483,33 @@ systems allow the kernel name cache to be switched off dynamically. When this is done, this downcall is made. + 55..33.. PPUURRGGEEUUSSEERR + AArrgguummeennttss struct cfs_purgeuser_out {/* CFS_PURGEUSER is a venus->kernel call */ struct CodaCred cred; } cfs_purgeuser; + + DDeessccrriippttiioonn Remove all entries in the cache carrying the Cred. This call is issued when tokes for a user expire or are flushed. + 55..44.. ZZAAPPFFIILLEE + AArrgguummeennttss struct cfs_zapfile_out { /* CFS_ZAPFILE is a venus->kernel call */ ViceFid CodaFid; } cfs_zapfile; + + DDeessccrriippttiioonn Remove all entries which have the (dir vnode, name) pair. This is issued as a result of an invalidation of cached attributes of a vnode. @@ -1297,20 +1518,28 @@ zapfile routine takes different arguments. Linux does not implement the invalidation of attributes correctly. + + 55..55.. ZZAAPPDDIIRR + AArrgguummeennttss struct cfs_zapdir_out { /* CFS_ZAPDIR is a venus->kernel call */ ViceFid CodaFid; } cfs_zapdir; + + DDeessccrriippttiioonn Remove all entries in the cache lying in a directory CodaFid, and all children of this directory. This call is issed when - Venus receives a callback on the this directory. + Venus receives a callback on the directory. + 55..66.. ZZAAPPVVNNOODDEE + + AArrgguummeennttss struct cfs_zapvnode_out { /* CFS_ZAPVNODE is a venus->kernel call */ @@ -1318,11 +1547,15 @@ ViceFid VFid; } cfs_zapvnode; + + DDeessccrriippttiioonn Remove all entries in the cache carrying the cred and VFid as in the arguments. This downcall is probably never issued. + 55..77.. PPUURRGGEEFFIIDD + SSuummmmaarryy AArrgguummeennttss @@ -1331,12 +1564,17 @@ ViceFid CodaFid; } cfs_purgefid; + + DDeessccrriippttiioonn Flush the attribute for the file. If it is a dir (odd vnode), purge its children from the namecache remove the file from the namecache. + + 55..88.. RREEPPLLAACCEE + SSuummmmaarryy Replace the Fid's for a collection of names. AArrgguummeennttss @@ -1346,6 +1584,8 @@ ViceFid OldFid; } cfs_replace; + + DDeessccrriippttiioonn This routine replaces a ViceFid in the name cache with another. It is added to allow Venus during reintegration to replace locally allocated temp fids while disconnected with global fids even @@ -1355,11 +1595,13 @@ 66.. IInniittiiaalliizzaattiioonn aanndd cclleeaannuupp + This section gives brief hints as to desirable features for the Coda FS Driver at startup and upon shutdown or Venus failures. Before entering the discussion it is useful to repeat that the Coda FS Driver maintains the following data: + 1. message queues 2. cnodes @@ -1383,8 +1625,10 @@ Currently the _p_i_o_c_t_l passes through the VFS for Coda so we can treat these similarly. + 66..11.. RReeqquuiirreemmeennttss + The following requirements should be accomodated: 1. The message queueus should have open and close routines. On Unix @@ -1399,6 +1643,7 @@ +o Close will free all memory allocated by the message queues. + 2. At open the namecache shall be initialized to empty state. 3. Before the message queues are open, all VFS operations will fail. @@ -1425,3 +1670,5 @@ above requirements fully. For smooth operation this needs to be corrected. + + diff --git a/Documentation/filesystems/fat_cvf.txt b/Documentation/filesystems/fat_cvf.txt new file mode 100644 index 000000000..9e7062e13 --- /dev/null +++ b/Documentation/filesystems/fat_cvf.txt @@ -0,0 +1,190 @@ +This is the main documentation for the CVF-FAT filesystem extension. 31DEC1997 + + +Table of Contents: + +1. The idea of CVF-FAT +2. Restrictions +3. Mount options +4. Description of the CVF-FAT interface +5. CVF Modules + +------------------------------------------------------------------------------ + + +1. The idea of CVF-FAT +------------------------------------------------------------------------------ + +CVF-FAT is a FAT filesystem extension that provides a generic interface for +Compressed Volume Files in FAT partitions. Popular CVF software, for +example, are Microsoft's Doublespace/Drivespace and Stac's Stacker. +Using the CVF-FAT interface, it is possible to load a module that handles +all the low-level disk access that has to do with on-the-fly compression +and decompression. All other part of FAT filesystem access is still handled +by the FAT, MSDOS or VFAT or even UMSDOS driver. + +CVF access works by redirecting certain low-level routines from the FAT +driver to a loadable, CVF-format specific module. This module must fake +a normal FAT filesystem to the FAT driver while doing all the extra stuff +like compression and decompression silently. + + +2. Restrictions +------------------------------------------------------------------------------ + +- BMAP problems + + CVF filesystems cannot do bmap. It's impossible by principle. Thus + all actions that require bmap do not work (swapping, writable mmapping). + Read-only mmapping works because the FAT driver has a hack for this + situation :) Well, with some tricks writable mmapping could work, + (proof: they did under old dmsdos), but..... (hint: readpage/writepage + interface functions) ...... but the FAT driver has to support them + first without bmap :-) + + We'll see. If someone points me to an application that needs this, I + might be persuaded to implement it :). CVF-FAT is already prepared + for using readpage. + +- DOSEMU users attention + + You may have to unmount all CVF partitions before running DOSEMU depending + on your configuration. If DOSEMU is configured to use wholedisk or + partition access (this is often the case to let DOSEMU access + compressed partitions) there's a risk of destroying your compressed + partitions or crashing your system because of confused drivers. + + Note that it is always safe to redirect the compressed partitions with + lredir or emufs.sys. Refer to the DOSEMU documentation for details. + + +3. Mount options +------------------------------------------------------------------------------ + +The CVF-FAT extension currently adds the following options to the FAT +driver's standard options: + + cvf_format=xxx + Forces the driver to use the CVF module "xxx" instead of auto-detection. + This is only necessary if the CVF format is not recognized corrrectly + because of bugs or incompatibilities in the CVF modules. (It skips + the detect_cvf call.) "xxx" may be the text "none" (without the quotes) + to inhibit using any of the loaded CVF modules, just in case a CVF + module insists on mounting plain FAT filesystems by misunderstanding :) + + cvf_options=yyy + Option string passed to the CVF module. I.e. only the "yyy" is passed + (without the quotes). The documentation for each CVF module should + explain it since it is interpreted only by the CVF module. Note that + the string must not contain a comma (",") - this would lead to + misinterpretation by the FAT driver, which would recognize the text + after a comma as a FAT driver option and might get confused or print + strange error messages. The documentation for the CVF module should + offer a different seperation symbol, for example the dot ".", which + is only valid inside the string "yyy". + + +4. Description of the CVF-FAT interface +------------------------------------------------------------------------------ + +Assuming you want to write your own CVF module, you need to write a lot of +interface funtions. Most of them are covered in the kernel documentation +you can find on the net, and thus won't be described here. They have been +marked with "[...]" :-) Take a look at include/linux/fat_cvf.h. + +struct cvf_format +{ int cvf_version; + char* cvf_version_text; + unsigned long int flags; + int (*detect_cvf) (struct super_block*sb); + int (*mount_cvf) (struct super_block*sb,char*options); + int (*unmount_cvf) (struct super_block*sb); + [...] + void (*cvf_zero_cluster) (struct inode*inode,int clusternr); +} + +This structure defines the capabilities of a CVF module. It must be filled +out completely by a CVF module. Consider it as a kind of form that is used +to introduce the module to the FAT/CVF-FAT driver. + +It contains... + - cvf_version: + A version id which must be uniqe. Choose one. + - cvf_version_text: + A human readable version string that should be one short word + describing the CVF format the module implements. This text is used + for the cvf_format option. This name must also be uniqe. + - flags: + Bit coded flags, currently only used for a readpage/mmap hack that + provides both mmap and readpage functionality. If CVF_USE_READPAGE + is set, mmap is set to generic_file_mmap and readpage is caught + and redirected to the cvf_readpage function. If it is not set, + readpage is set to generic_readpage and mmap is caught and redirected + to cvf_mmap. + - detect_cvf: + A function that is called to decide whether the filesystem is a CVF of + the type the module supports. The detect_cvf function must return 0 + for "NO, I DON'T KNOW THIS GARBAGE" or anything !=0 for "YES, THIS IS + THE KIND OF CVF I SUPPORT". The function must maintain the module + usage counters for safety, i.e. do MOD_INC_USE_COUNT at the beginning + and MOD_DEC_USE_COUNT at the end. The function *must not* assume that + successful recongition would lead to a call of the mount_cvf function + later. + - mount_cvf: + A function that sets up some values or initializes something additional + to what has to be done when a CVF is mounted. This is called at the + end of fat_read_super and must return 0 on success. Definitely, this + function must increment the module usage counter by MOD_INC_USE_COUNT. + This mount_cvf function is also responsible for interpreting a CVF + module specific option string (the "yyy" from the FAT mount option + "cvf_options=yyy") which cannot contain a comma (use for example the + dot "." as option separator symbol). + - unmount_cvf: + A function that is called when the filesystem is unmounted. Most likely + it only frees up some memory and calls MOD_DEC_USE_COUNT. The return + value might be ignored (it currently is ignored). + - [...]: + All other interface functions are "caught" FAT driver functions, i.e. + are executed by the FAT driver *instead* of the original FAT driver + functions. NULL means use the original FAT driver functions instead. + If you really want "no action", write a function that does nothing and + hang it in instead. + - cvf_zero_cluster: + The cvf_zero_cluster function is called when the fat driver wants to + zero out a (new) cluster. This is important for directories (mkdir). + If it is NULL, the FAT driver defaults to overwriting the whole + cluster with zeros. Note that clusternr is absolute, not relative + to the provided inode. + +Notes: + 1. The cvf_bmap function should be ignored. It really should never + get called from somewhere. I recommend redirecting it to a panic + or fatal error message so bugs show up immediately. + 2. The cvf_writepage function is ignored. This is because the fat + driver doesn't support it. This might change in future. I recommend + setting it to NULL (i.e use default). + +int register_cvf_format(struct cvf_format*cvf_format); + If you have just set up a variable containing the above structure, + call this function to introduce your CVF format to the FAT/CVF-FAT + driver. This is usually done in init_module. Be sure to check the + return value. Zero means success, everything else causes a kernel + message printed in the syslog describing the error that occured. + Typical errors are: + - a module with the same version id is already registered or + - too many CVF formats. Hack fs/fat/cvf.c if you need more. + +int unregister_cvf_format(struct cvf_format*cvf_format); + This is usually called in cleanup_module. Return value =0 means + success. An error only occurs if you try to unregister a CVF format + that has not been previously registered. The code uses the version id + to distinguish the modules, so be sure to keep it uniqe. + +5. CVS Modules +------------------------------------------------------------------------------ + +Refer to the dmsdos module (the successor of the dmsdos filesystem) for a +sample implementation. It can currently be found at + + ftp://fb9nt.uni-duisburg.de/pub/linux/dmsdos + diff --git a/Documentation/filesystems/isofs.txt b/Documentation/filesystems/isofs.txt new file mode 100644 index 000000000..2f0a4249e --- /dev/null +++ b/Documentation/filesystems/isofs.txt @@ -0,0 +1,28 @@ +Mount options that are the same as for msdos and vfat partitions. + + gid=nnn All files in the partition will be in group nnn. + uid=nnn All files in the partition will be owned by user id nnn. + umask=nnn The permission mask (see umask(1)) for the partition. + +Mount options that are the same as vfat partitions. These are only useful +when using discs encoded using Microsoft's Joliet extensions. + iocharset=name Character set to use for converting from Unicode to + ASCII. Joliet filenames are stored in Unicode format, but + Unix for the most part doesn't know how to deal with Unicode. + There is also an option of doing UTF8 translations with the + utf8 option. + utf8 Encode Unicode names in UTF8 format. Default is no. + +Mount options that are unique to the isofs filesystem. + block=512 Set the block size for the disk to 512 bytes + block=1024 Set the block size for the disk to 1024 bytes + block=2048 Set the block size for the disk to 2048 bytes + check=relaxed Matches filenames with different cases + check=strict Matches only filenames with the exact same case + cruft Try to handle badly formatted CDs. + map=off Do not map non-rockridge filenames to lowercase + map=normal Map rockridge filenames to lowercase + mode=xxx Sets the permissions on files to xxx + nojoliet Ignore Joliet extensions if they are present. + norock Ignore rockridge extensions if they are present. + unhide Show hidden files. diff --git a/Documentation/filesystems/ntfs.txt b/Documentation/filesystems/ntfs.txt new file mode 100644 index 000000000..504408e52 --- /dev/null +++ b/Documentation/filesystems/ntfs.txt @@ -0,0 +1,30 @@ +NTFS Overview +============= + +To mount an NTFS volume, use the filesystem type 'ntfs'. The driver +currently works only in read-only mode, with no fault-tolerance +supported. If you enable the experimental write support, make sure +you can recover from a complete loss of data. For ftdisk support, +limit success was reported with volume sets on top of the md driver, +although mirror and stripe sets should work as well - if the md +driver can be talked into using the same lay-out as Windows NT. + +The ntfs driver supports the following mount options: +iocharset=name Character set to use when returning file names. + Unlike VFAT, NTFS suppresses names that contain + unconvertible characters +utf8=<bool> Use UTF-8 for converting file names +uni_xlate=<bool>,2 Use the VFAT-style encoding for file names outside + the current character set. A boolean value will + enable the feature, a value of 2 will enable the + encoding as documented in vfat.txt: + ':', (u & 0x3f), ((u>>6) & 0x3f), (u>>12), +uid= +gid= +umask= These options work as documented in mount(8). + By default, the files are owned by root and + not readable by somebody else. +posix=<bool> If enabled, the file system distinguishes between + upper and lower case. The 8.3 alias names are presented + as hard links instead of being suppressed. + diff --git a/Documentation/filesystems/smbfs.txt b/Documentation/filesystems/smbfs.txt index 04eb2e586..5fc080576 100644 --- a/Documentation/filesystems/smbfs.txt +++ b/Documentation/filesystems/smbfs.txt @@ -1,27 +1,20 @@ Smbfs is a filesystem that implements the SMB protocol, which is the protocol used by Windows for Workgroups, Windows 95 and Windows NT. -Smbfs was inspired by samba, the program written by Andrew Tridgell +Smbfs was inspired by Samba, the program written by Andrew Tridgell that turns any unix host into a file server for DOS or Windows clients. See ftp://nimbus.anu.edu.au/pub/tridge/samba/ for this interesting program suite and much more information on SMB, NetBIOS over TCP/IP, and explanations for concepts like netbios name or share. -To use smbfs, you need to install the Samba package (Samba-1.9.17p1 or -later), and you need the special mount program from the smbfs package -(smbfs-2.1.0 or later), found on +To use smbfs, you must first install the Samba package (Samba-1.9.18p1 or +later). This package includes the special smbmount utility needed to mount +smbfs volumes. Refer to the smbmount(8) and smbmnt(8) manpages for the +details regarding smbfs mounts. - ftp://ftp.gwdg.de/pub/linux/misc/smbfs/dontuse - -After downloading the smbfs package, apply the patch to the smbclient -program and recompile. Smbfs can then be mounted from the smbclient -command line, as for example: - - smb: \>mount /mnt/tmp -f 755 - -For convenience, you may wish to package the command in a script like this: - -#!/bin/sh -echo "mount /mnt/tmp -f 755" | smbclient //server/c$ -U administrator% +The smbmount utility reads the Samba smb.conf config file for some of its +options, and at least one of these is important for smbfs operation. You +should enable the TCP_NODELAY socket option, or else directory listings +will be dramatically slower (under Win NT at least). Mount-Time Options Windows 95 has several bugs that affect SMB operations, and smbfs includes @@ -37,11 +30,12 @@ to the file mode argument of the mount command for the Win 95 servers. Option Value Effect Identify Win 95 Server 1 Enables bug fixes Use Core Attributes 2 Speeds up directory scans, only mtime +Use Dir Attributes 4 Alternate way to get file attributes To apply the options, sum the values and prepend it to the file mode. For -example, to use both options with file mode 755, you would prepend 3 to 755: +example, to use options 1 and 2 with file mode 755, you would specify 3755: - cnt>mount /mnt/tmp -f 3755 + mount /mnt/tmp -f 3755 Smbfs will print a message at mount time confirming the selected options. Note that _only_ Windows 95 servers require special treatment; using the diff --git a/Documentation/filesystems/vfat.txt b/Documentation/filesystems/vfat.txt index 050a4306a..61f44a87c 100644 --- a/Documentation/filesystems/vfat.txt +++ b/Documentation/filesystems/vfat.txt @@ -43,6 +43,10 @@ nonumtail=<bool> -- When creating 8.3 aliases, normally the alias will be the short alias instead of 'longfi~1.txt'. quiet -- Stops printing certain warning messages. +check=s|r|n -- Case sensitivity checking setting. + s: strict, case sensitive + r: relaxed, case insensitive + n: normal, default setting, currently case insensitive <bool>: 0,1,yes,no,true,false diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt index e4922c3b9..0644c2e2f 100644 --- a/Documentation/filesystems/vfs.txt +++ b/Documentation/filesystems/vfs.txt @@ -8,7 +8,7 @@ I've learned while writing lofs... The VFS relatively simple, but it is nice not to have to browse through pages of code to determine what is expected when writing a filesystem. Hopefully this helps anyone attempting such a feat, as well as clearing up -a few important points/dependancies. +a few important points/dependencies. register_filesystem (struct file_system_type *fstype) diff --git a/Documentation/hayes-esp.txt b/Documentation/hayes-esp.txt index d0682999c..62a9c7451 100644 --- a/Documentation/hayes-esp.txt +++ b/Documentation/hayes-esp.txt @@ -1,14 +1,37 @@ -HAYES ESP DRIVER VERSION 1.6 +HAYES ESP DRIVER VERSION 2.0 + +A big thanks to the people at Hayes, especially Alan Adamson. Their support +has enabled me to provide enhancements to the driver. + +Please report your experiences with this driver to me (arobinso@nyx.net). I +am looking for both positive and negative feedback. + +*** IMPORTANT CHANGES FOR 2.0 *** +Support for PIO mode. Five situations will cause PIO mode to be used: +1) A multiport card is detected. PIO mode will always be used. (8 port cards +do not support DMA). +2) The DMA channel is set to an invalid value (anything other than 1 or 3). +3) The DMA buffer/channel could not be allocated. The port will revert to PIO +mode until it is reopened. +4) Less than 33 bytes need to be transferred to/from the FIFOs. PIO mode will +be used for that transfer only. +5) A port needs to do a DMA transfer and another port is already using the +DMA channel. PIO mode will be used for that transfer only. + +A patch for setserial (2.12) is included to allow the ESP enhanced mode +configuration to be viewed and changed. +*** + +This package contains the files needed to compile a module to support the Hayes +ESP card. The drivers are basically a modified version of the serial drivers. Features: - Uses the enhanced mode of the ESP card, allowing a wider range of interrupts and features than compatibilty mode -- Uses DMA to transfer data to and from the ESP's FIFOs, reducing CPU load +- Uses DMA and 16 bit PIO mode to transfer data to and from the ESP's FIFOs, + reducing CPU load - Supports primary and secondary ports -- Special version of setserial can be used to view/change the enhanced mode - configuration. The setserial patch is distributed with the standalone - driver distribution. See http://www.nyx.net/~arobinso for more information. To compile/install: @@ -47,7 +70,8 @@ be: insmod esp divisor=0,0,0,0,0,0,0x84,0 The dma= option can be used to set the DMA channel. The channel can be either -1 or 3. For example, to set the dma channel to 3, the insmod command would be: +1 or 3. Specifying any other value will force the driver to use PIO mode. +For example, to set the dma channel to 3, the insmod command would be: insmod esp dma=3 diff --git a/Documentation/ioctl-number.txt b/Documentation/ioctl-number.txt index 43b094d5c..ac2af6e3f 100644 --- a/Documentation/ioctl-number.txt +++ b/Documentation/ioctl-number.txt @@ -1,5 +1,5 @@ Ioctl Numbers -1 Sep 1997 +18 Feb 1998 Michael Chastain <mec@shout.net> @@ -86,7 +86,7 @@ Code Seq# Include File Comments 'W' 28-2F linux/iso16-relay.h in development 'Y' all linux/cyclades.h 'a' all various, see http://lrcwww.epfl.ch/linux-atm/magic.html -'b' 00-3F bit3 vme host bridge in development: +'b' 00-FF bit3 vme host bridge in development: <mailto:natalia@nikhefk.nikhef.nl> 'c' all linux/comstats.h 'f' all linux/ext2_fs.h @@ -99,6 +99,8 @@ Code Seq# Include File Comments 'n' all linux/ncp_fs.h 'p' 00-3F linux/mc146818rtc.h 'p' 40-7F linux/nvram.h +'p' 80-9F user-space parport in development: + <tim@cyberelk.demon.co.uk> 'r' all linux/msdos_fs.h 's' all linux/cdk.h 't' 00-7F linux/if_ppp.h @@ -108,6 +110,8 @@ Code Seq# Include File Comments 'w' all CERN SCI driver in development 'z' 00-3F CAN bus card in development: <mailto:hdstich@connectu.ulm.circular.de> +'z' 40-7F CAN bas card in development: + <mailto:oe@port.de> 0x89 00-0F asm-i386/sockios.h 0x89 10-DF linux/sockios.h 0x89 E0-EF linux/sockios.h SIOCPROTOPRIVATE range diff --git a/Documentation/isdn/README b/Documentation/isdn/README index 770694f2b..48dec2d83 100644 --- a/Documentation/isdn/README +++ b/Documentation/isdn/README @@ -285,7 +285,7 @@ README for the ISDN-subsystem 5. Application a) For some card-types, firmware has to be loaded into the cards, before - proceeding with device-independant setup. See README.<yourDriver> + proceeding with device-independent setup. See README.<yourDriver> for how to do that. b) If you only intend to use ttys, you are nearly ready now. diff --git a/Documentation/java.txt b/Documentation/java.txt index f5205b1a4..a5439f730 100644 --- a/Documentation/java.txt +++ b/Documentation/java.txt @@ -4,45 +4,92 @@ Linux beats them ALL! While all other OS's are TALKING about direct support of Java Binaries in the OS, Linux is doing it! -You execute Java classes as you would any other executable, after a few -small details: - - 1) You MUST FIRST install the Java Developers Kit for Linux. - The Java on Linux HOWTO gives the details on getting and - installing this. This HOWTO can be found at: - - ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/Java-HOWTO - - If you install the JDK in a location other than /usr/bin/java, - then you will need to tell the kernel where you put the Java - interpreter. - There are two ways to do this. - One, edit fs/binfmt_java.c file and make the needed change to - the _PATH_JAVA definition at the top of that file. - Two, as root, issue the command: - echo "/path/to/java/interpreter" > /proc/sys/kernel/java-interpreter - (Currently, this does not work if you're using a module for - Java support.) - - 2) You must chmod the '*.class' files you wish to execute with - the execute bit. This is not normally (till now) done with - '.class' files. - - 3) You must optionally export a CLASSPATH environment variable, - if you plan to use Java applications installed outside of - /usr/local/java/classes/*. - - 4) Either compile your kernel with Java support builtin, or - as a loadable module. If a module, load it with insmod or - kerneld. - - 5) A caveat. When executing a java file, the java interpreter is - invoked only with the class name, not with the complete file path. - Therefore it is possible that the file the shell finds with PATH - is not the same file the java interpreter finds with CLASSPATH. - The recommended solution is to make symbolic links from a directory - in PATH to the actual class file in CLASSPATH, e.g., - /usr/local/bin/myapp -> /usr/local/java/classes/myapp.class. +You can execute Java applications and Java Applets just like any +other program after you have done the following: + +1) You MUST FIRST install the Java Developers Kit for Linux. + The Java on Linux HOWTO gives the details on getting and + installing this. This HOWTO can be found at: + + ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/Java-HOWTO + + You should also set up a reasonable CLASSPATH environment + variable to use Java applications that make use of any + nonstandard classes (not included in the same directory + as the application itself). + +2) You have to compile BINFMT_MISC either as module or into + the kernel (CONFIG_BINFMT_MISC) and set it up properly. + If you choose to compile it as a module, you will have + to insert it manually with modprobe/insmod, as kerneld + can not easy be supported with binfmt_misc. + Read the file 'binfmt_misc.txt' in this directory to know + more about the configuration process. + +3) Add the following configuration items to binfmt_misc + (you should really have read binfmt_misc.txt now): + support for Java applications: + ':Java:M::\xca\xfe\xba\xbe::/usr/local/java/bin/javawrapper:' + support for Java Applets: + ':Applet:E::html::/usr/local/java/bin/appletviewer:' + or the following, if you want to be more selective: + ':Applet:M::<!--applet::/usr/local/java/bin/appletviewer:' + + Of cause you have to fix the path names, if you installed the JDK + at another place than /usr/local/java. + + Note, that for the more selective applet support you have to modify + existing html-files to contain <!--applet--> in the first line + ('<' has to be the first character!) to let this work! + + For the compiled Java programs you need a wrapper script like the + following (this is because Java is broken in case of the filename + handling), again fix the path names, both in the script and in the + above given configuration string: + +====================== Cut here =================== +#!/bin/bash +# /usr/local/java/bin/javawrapper - the wrapper for binfmt_misc/java +CLASS=$1 + +# if classname is a link, we follow it (this could be done easier - how?) +if [ -L "$1" ] ; then + CLASS=`ls --color=no -l $1 | tr -s '\t ' ' ' | cut -d ' ' -f 11` +fi +CLASSN=`basename $CLASS .class` +CLASSP=`dirname $CLASS` + +FOO=$PATH +PATH=$CLASSPATH +if [ -z "`type -p -a $CLASSN.class`" ] ; then + # class is not in CLASSPATH + if [ -e "$CLASSP/$CLASSN.class" ] ; then + # append dir of class to CLASSPATH + if [ -z "${CLASSPATH}" ] ; then + export CLASSPATH=$CLASSP + else + export CLASSPATH=$CLASSP:$CLASSPATH + fi + else + # uh! now we would have to create a symbolic link - really + # ugly, i.e. print a message that one has to change the setup + echo "Hey! This is not a good setup to run $1 !" + exit 1 + fi +fi +PATH=$FOO + +shift +/usr/local/java/bin/java $CLASSN "$@" +====================== Cut here =================== + + +Now simply chmod +x the .class and/or .html files you want to execute. +To add a Java program to your path best put a symbolic link to the main +.class file into /usr/bin (or another place you like) omitting the .class +extension. The directory containing the original .class file will be +added to your CLASSPATH during execution. + To test your new setup, enter in the following simple Java app, and name it "HelloWorld.java": @@ -53,59 +100,20 @@ it "HelloWorld.java": } } - Now compile the application with: - - /usr/local/java/bin/javac HelloWorld.java + javac HelloWorld.java Set the executable permissions of the binary file, with: - chmod 755 HelloWorld.class And then execute it: - ./HelloWorld.class -Yes, it's JUST THAT EASY! ;-) - ------------------------------------------------------------------ - -Nope, I didn't forget about Java Applets! ;-) - -While this may not be the best way to do this, it works! - -Take any html file used with the Java appletviewer (like the -demo/Blink/example1.html file), and: - - 1) Insert a new first line of: - - <!--applet--> - - Make sure the '<' is the first character in the file. This - will be treated as a valid HTML comment outside of this - Java Applet support, so the modified file can still be used - with all known browsers. - - 2) If you install the applet viewer in a location other than - /usr/bin/appletviewer, then you will need to tell the - kernel where you put the Java appletviewer. - There are two ways to do this. - One, edit fs/binfmt_java.c file and make the needed change to - the _PATH_APPLET definition at the top of that file. - Two, as root, issue the command: - echo "/path/to/java/appletviewer" > /proc/sys/kernel/java-appletviewer - (Currently, this does not work if you're using a module for - Java support.) - - 3) You must chmod the '*.html' files you wish to execute with - the execute bit. This is not normally (till now) done with - '.html' files. - - 4) And then execute it. - +To execute Java Applets, simple chmod the *.html files to include +the execution bit, then just do + ./Applet.html -Brian A. Lantz -brian@lantz.com -(/proc/sys/kernel/java-* support by Mike Shaver (shaver@ingenia.com)) +originally by Brian A. Lantz, brian@lantz.com +heavily edited for binfmt_misc by Richard Günther. diff --git a/Documentation/m68k/framebuffer.txt b/Documentation/m68k/framebuffer.txt index 490a33793..b533f0202 100644 --- a/Documentation/m68k/framebuffer.txt +++ b/Documentation/m68k/framebuffer.txt @@ -3,7 +3,7 @@ ---------------------------------- Maintained by Geert Uytterhoeven (Geert.Uytterhoeven@cs.kuleuven.ac.be) -Last revised: March 23, 1997 +Last revised: January 24, 1998 0. Introduction @@ -23,85 +23,47 @@ The device is accessed through special device nodes, usually located in the -------------------------- From the user's point of view, the frame buffer device looks just like any -other device in /dev. It's a character device using major 29, the minor is -divided into a frame buffer number in the upper 3 bits (allowing max. 8 frame -buffers simultaneously) and a resolution code in the lower 5 bits of the minor. +other device in /dev. It's a character device using major 29; the minor +specifies the frame buffer number. By convention, the following device nodes are used (numbers indicate the device minor numbers): - First frame buffer - 0 = /dev/fb0current Current resolution - 1 = /dev/fb0autodetect Default resolution - 2 = /dev/fb0predefined0 Predefined resolutions (22) - ... - 23 = /dev/fb0predefined21 - 24 = /dev/fb0user0 User defined resolutions (8) - ... - 31 = /dev/fb0user7 - - Second frame buffer - 32 = /dev/fb1current Current resolution - 33 = /dev/fb1autodetect Default resolution - 34 = /dev/fb1predefined0 Predefined resolutions (22) - ... - 55 = /dev/fb1predefined21 - 56 = /dev/fb1user0 User defined resolutions (8) - ... - 63 = /dev/fb1user7 + 0 = /dev/fb0 First frame buffer + 32 = /dev/fb1 Second frame buffer + ... + 224 = /dev/fb7 8th frame buffer -and so on... - -The device with (minor & 31) == 0 (/dev/fb?current) stands for the frame buffer -together with the currently set video parameters; (minor & 31) == 1 -(/dev/fb?autodetect) is the video mode detected at boot time. Any other minor -stands for some predefined or user defined video mode. - -The predefined entries (/dev/fb?predefined*) usually have a device dependent -name, e.g. for major 29, minor 5, we have /dev/fb0multiscan on Amiga and -/dev/fb0ttmid on Atari. These are meant to contain hardware dependent -resolutions. - -The user defined resolutions (/dev/fb?user?) are meant to be filled in by the -user. This way the user can store his favorite 8 resolutions during boot up. +For backwards compatibility, you may want to create the following symbolic +links: -Note: if you need more than 8 user defined resolutions, you can always override -the predefined resolutions by storing them in one of the predefined entries. -But this is not recommended. Similarly, if there are more than 22 predefined -resolutions, the device writer can decide to store them in the user defined -entries. + /dev/fb0current -> fb0 + /dev/fb1current -> fb1 -If the device is opened (for writing), the frame buffer driver switches to the -selected video mode. Thus, you can switch video modes by writing to a frame -buffer device, e.g. - - > /dev/fb0ttlow - -will switch your video to TT low mode. Note: if you specify a resolution which -contains a value that's not possible on your hardware, the frame buffer device -will round it up (if possible) or return an error condition. +and so on... The frame buffer devices are also `normal' memory devices, this means, you can read and write their contents. You can, for example, make a screen snapshot by - cp /dev/fb0current myfile + cp /dev/fb0 myfile There also can be more than one frame buffer at a time, e.g. if you have a graphics card in addition to the built-in hardware. The corresponding frame -buffer devices (/dev/fb0* and /dev/fb1* etc.) work independently. +buffer devices (/dev/fb0 and /dev/fb1 etc.) work independently. Application software that uses the frame buffer device (e.g. the X server) will -use /dev/fb0current by default. You can specify an alternative resolution by -setting the environment variable $FRAMEBUFFER to the path name of a frame -buffer device, e.g. (for sh/bash users): +use /dev/fb0 by default (older software uses /dev/fb0current). You can specify +an alternative frame buffer device by setting the environment variable +$FRAMEBUFFER to the path name of a frame buffer device, e.g. (for sh/bash +users): - export FRAMEBUFFER=/dev/fb0multiscan + export FRAMEBUFFER=/dev/fb1 or (for csh users): - setenv FRAMEBUFFER /dev/fb0multiscan + setenv FRAMEBUFFER /dev/fb1 -After this the X server will use the multiscan video mode. +After this the X server will use the second frame buffer. 2. Programmer's View of /dev/fb* @@ -152,23 +114,20 @@ much trouble... -------------------------------------- Frame buffer resolutions are maintained using the utility `fbset'. It allows to -change the video mode properties of the current or a user defined resolution. -It's main usage is to tune video modes and to store custom resolutions into one -of the /dev/fb?user? entries, e.g. during boot up in one of your /etc/rc.* or -/etc/init.d/* files, after which those resolutions can be used by applications. +change the video mode properties of the current resolution. It's main usage is +to change the current video mode, e.g. during boot up in one of your /etc/rc.* +or /etc/init.d/* files. Fbset uses a video mode database stored in a configuration file, so you can -easily add your own modes and refer to them with a simple identifier. The fbset -install script also creates the special device nodes for the device dependent -predefined resolutions. +easily add your own modes and refer to them with a simple identifier. 4. The X Server --------------- The X server (XF68_FBDev) is the most notable application program for the frame -buffer device. The current X server is part of the XFree86/XFree68 release 3.2 -package and has 2 modes: +buffer device. The current X server is part of the XFree86/XFree68 release +3.3.1 package and has 2 modes: - If the `Display' subsection for the `fbdev' driver in the /etc/XF86Config file contains a @@ -347,7 +306,7 @@ applications, please refer to the following documentation: - The mighty kernel sources: o linux/include/linux/fb.h o linux/drivers/char/fbmem.c - o linux/arch/m68k/*/*fb.c + o linux/drivers/video/*fb.c 8. Downloading diff --git a/Documentation/m68k/kernel-options.txt b/Documentation/m68k/kernel-options.txt index fded75017..7b611ef55 100644 --- a/Documentation/m68k/kernel-options.txt +++ b/Documentation/m68k/kernel-options.txt @@ -3,8 +3,8 @@ Command Line Options for Linux/m68k =================================== -Date: Oct 6, 1997 -Linux/m68k version: 2.0.21 +Last Update: Nov 28, 1997 +Linux/m68k version: 2.1.64 Author: Roman.Hodek@informatik.uni-erlangen.de (Roman Hodek) Update: jds@kom.auc.dk (Jes Sorensen) @@ -191,6 +191,7 @@ Devices possible for Atari: - "ser2": SCC channel B serial port ("Modem2"); parameters: 9600bps, 8N1 - "ser" : default serial port This is "ser2" for a Falcon, and "ser1" for any other machine + - "midi": The MIDI port; parameters: 31250bps, 8N1 - "par" : parallel port The printing routine for this implements a timeout for the case there's no printer connected (else the kernel would @@ -408,19 +409,7 @@ physical start, in bytes. Often, extended interval video hardware has to be activated somehow. For this, see the "sw_*" options below. -4.1.6) sw_acia, sw_snd6, sw_snd7 --------------------------------- - -This specifies the method for turning on extended internal video -hardware, like OverScan. Several methods are in use: - - sw_acia: Set RTS of the keyboard ACIA high - sw_snd6: Set bit 6 of the PSG port A - sw_snd7: Set bit 7 of the PSG port A - -These sub-options are generally only useful together with "internal:". - -4.1.7) external: +4.1.6) external: ---------------- Syntax: @@ -509,13 +498,13 @@ If you're missing a corresponding yres_virtual: the external part is legacy, therefore we don't support hardware-dependend functions like hardware-scroll, panning or blanking. -4.1.8) eclock: +4.1.7) eclock: -------------- The external pixel clock attached to the Falcon VIDEL shifter. This currently works only with the ScreenWonder! -4.1.9) monitorcap: +4.1.8) monitorcap: ------------------- Syntax: monitorcap:<vmin>;<vmax>;<hmin>;<hmax> @@ -532,7 +521,7 @@ the horizontal frequency, in kHz. The defaults for TV/SC1224/SC1435 cover both PAL and NTSC standards. -4.1.10) keep +4.1.9) keep ------------ If this option is given, the framebuffer device doesn't do any video @@ -578,7 +567,7 @@ Syntax: ataflop=<drive type>[,<trackbuffering>[,<steprateA>[,<steprateB>]]] type. The second parameter <trackbuffer> tells the kernel whether to use - track buffering (1) or not (0). The default is machine dependant: + track buffering (1) or not (0). The default is machine-dependent: no for the Medusa and yes for all others. With the two following parameters, you can change the default @@ -650,7 +639,62 @@ ignored (other aren't affected). can be performed in optimal order. Not all SCSI devices support tagged queuing (:-(). +4.6 switches= +------------- + +Syntax: switches=<list of switches> + + With this option you can switch some hardware lines that are often +used to enable/disable certain hardware extensions. Examples are +OverScan, overclocking, ... + + The <list of switches> is a comma-separated list of the following +items: + + ikbd: set RTS of the keyboard ACIA high + midi: set RTS of the MIDI ACIA high + snd6: set bit 6 of the PSG port A + snd7: set bit 6 of the PSG port A + +It doesn't make sense to mention a switch more than once (no +difference to only once), but you can give as many switches as you +want to enable different features. The switch lines are set as early +as possible during kernel initialization (even before determining the +present hardware.) + + All of the items can also be prefixed with "ov_", i.e. "ov_ikbd", +"ov_midi", ... These options are meant for switching on an OverScan +video extension. The difference to the bare option is that the +switch-on is done after video initialization, and somehow synchronized +to the HBLANK. A speciality is that ov_ikbd and ov_midi are switched +off before rebooting, so that OverScan is disabled and TOS boots +correctly. + + If you give an option both, with and without the "ov_" prefix, the +earlier initialization ("ov_"-less) takes precedence. But the +switching-off on reset still happens in this case. + +4.5) stram_swap= +---------------- +Syntax: stram_swap=<do_swap>[,<max_swap>] + + This option is available only if the kernel has been compiled with +CONFIG_STRAM_SWAP enabled. Normally, the kernel then determines +dynamically whether to actually use ST-RAM as swap space. (Currently, +the fraction of ST-RAM must be less or equal 1/3 of total memory to +enable this swapping.) You can override the kernel's decision by +specifying this option. 1 for <do_swap> means always enable the swap, +even if you have less alternate RAM. 0 stands for never swap to +ST-RAM, even if it's small enough compared to the rest of memory. + + If ST-RAM swapping is enabled, the kernel usually uses all free +ST-RAM as swap "device". (If the kernel resides in ST-RAM, the region +allocated by it is obviously never used for swapping :-) You can also +limit this amount by specifying the second parameter, <max_swap>, if +you want to use parts of ST-RAM as normal system memory. <max_swap> is +in kBytes and the number should be a multiple of 4 (otherwise: rounded +down). 5) Options for Amiga Only: ========================== diff --git a/Documentation/md.txt b/Documentation/md.txt new file mode 100644 index 000000000..0107ca5d8 --- /dev/null +++ b/Documentation/md.txt @@ -0,0 +1,37 @@ +Tools that manage md devices can be found at sweet-smoke.ufr-info-p7.ibp.fr +in public/Linux/md035.tar.gz. + + Marc ZYNGIER <zyngier@ufr-info-p7.ibp.fr> + +-- + +You can boot (if you selected boot support in the configuration) with your md +device with the following kernel command line: + +md=<md device no.>,<raid level>,<chunk size factor>,<fault level>,dev0,dev1,...,devn + +md device no. = the number of the md device ... + 0 means md0, + 1 md1, + 2 md2, + 3 md3, + 4 md4 + +raid level = -1 linear mode + 0 striped mode + other modes are currently unsupported. + +chunk size factor = (raid-0 and raid-1 only) + Set the chunk size as PAGE_SIZE << n. + +fault level = (raid-1 only) + Set the maximum fault number as n. + Currently unsupported due to lack of boot support for raid1. + +dev0-devn: e.g. /dev/hda1,/dev/hdc1,/dev/sda1,/dev/sdb1 + +my loadlin line looks like this: + +e:\loadlin\loadlin e:\zimage root=/dev/md0 md=0,0,4,0,/dev/hdb2,/dev/hdc3 ro + + Harald Hoyer <HarryH@Royal.Net> diff --git a/Documentation/modules.txt b/Documentation/modules.txt index ace34450c..b637da0a4 100644 --- a/Documentation/modules.txt +++ b/Documentation/modules.txt @@ -60,7 +60,6 @@ Here is a sample of the available modules included in the kernel sources: aztcd: Aztech,Orchid,Okano,Wearnes cm206: Philips/LMS CM206 gscd: Goldstar GCDR-420 - bpcd: MicroSolutions backpack CDrom mcd, mcdx: Mitsumi LU005, FX001 optcd: Optics Storage Dolphin 8000AT sjcd: Sanyo CDR-H94A diff --git a/Documentation/nbd.txt b/Documentation/nbd.txt index e6617f068..fc488449e 100644 --- a/Documentation/nbd.txt +++ b/Documentation/nbd.txt @@ -4,19 +4,19 @@ means, that it works on my computer, and it worked on one of school computers. - What is it: With this think compiled in kernel, linux can use remote - server as one of its block devices. So every time client computer - wants to read /dev/nd0, it will send request over TCP to server, which - will reply with data readed. This can be used for stations with - low-disk space (or even disklesses - if you boot from floppy) to - borrow disk space from other computer. Unlike NFS, it is possible to - put any filesystem on it etc. It is impossible to use NBD as root - filesystem, since it requires user-level program to start. It also + What is it: With this compiled in the kernel, linux can use a remote + server as one of its block devices. So every time the client computer + wants to read /dev/nd0, it sends a request over TCP to the server, which + will reply with the data read. This can be used for stations with + low-disk space (or even diskless - if you boot from floppy) to + borrow disk space from another computer. Unlike NFS, it is possible to + put any filesystem on it etc. It is impossible to use NBD as a root + filesystem, since it requires a user-level program to start. It also allows you to run block-device in user land (making server and client - physicaly same computer, communicating using loopback). + physically the same computer, communicating using loopback). Current state: It currently works. Network block device looks like - being pretty stable. I originaly thought that it is impossible to swap + being pretty stable. I originally thought that it is impossible to swap over TCP. It turned out not to be true - swapping over TCP now works and seems to be deadlock-free, but it requires heavy patches into Linux's network layer. @@ -30,8 +30,8 @@ brw-rw-rw- 1 root root 43, 1 Apr 11 00:28 nd1 ... Protocol: Userland program passes file handle with connected TCP - socket to actuall kernel driver. This way, kernel does not have to - care about connecting etc. Protocol is rather simple: If driver is + socket to actual kernel driver. This way, the kernel does not have to + care about connecting etc. Protocol is rather simple: If the driver is asked to read from block device, it sends packet of following form "request" (all data are in network byte order): @@ -48,7 +48,7 @@ brw-rw-rw- 1 root root 43, 1 Apr 11 00:28 nd1 structure "reply": __u32 magic; must be equal to - __u64 handle; handle copyied from request + __u64 handle; handle copied from request __u32 error; 0 = operation completed successfully, else error code ... in case of read operation with no error, diff --git a/Documentation/networking/alias.txt b/Documentation/networking/alias.txt index 6b742170a..ef0415936 100644 --- a/Documentation/networking/alias.txt +++ b/Documentation/networking/alias.txt @@ -1,32 +1,10 @@ -NET_ALIAS device aliasing v0.4x -=============================== - The main step taken in versions 0.40+ is the implementation of a - device aliasing mechanism that creates *actual* devices. - This development includes NET_ALIAS (generic aliasing) plus IP_ALIAS - (specific IP) support. -Features --------- -o ACTUAL alias devices created & inserted in dev chain -o AF_ independent: net_alias_type objects. Generic aliasing engine. -o AF_INET optimized -o hashed alias address lookup -o net_alias_type objs registration/unreg., module-ables. -o /proc/net/aliases & /proc/net/alias_types entries +IP-Aliasing: +============ -o IP alias implementation: static or runtime module. -Usage (IP aliasing) -------------------- - A very first step to test if you are running a net_alias-ed kernel - is to check /proc/net/aliases & /proc/net/alias_types entries: - # cat /proc/net/alias* - - For IP aliasing you must have IP_ALIAS support included by - static linking ('y' to 2nd question above), or runtime module - insertion ('m' to 2nd q. above): - # insmod /usr/src/linux/modules/ip_alias.o (1.3.xx) - # insmod /usr/src/ip_alias/ip_alias.o (1.2.xx) see above. +o For IP aliasing you must have IP_ALIAS support included by static + linking. o Alias creation. Alias creation is done by 'magic' iface naming: eg. to create a @@ -42,50 +20,30 @@ o Alias creation. for eth0:0) o Alias deletion. - Also done by magic naming, eg: + Also done by shutting the interface down: + + # ifconfig eth0:0 down + ~~~~~~~~~~ -> will delete alias - # ifconfig eth0:0- 0 (maybe any address) - ~~~ -> will delete alias (note '-' after dev name) - alias device is closed before deletion, so all network stuff that - points to it (routes, arp entries, ...) will be released. Alias (re-)configuring - Aliases *are* devices, so you configure and refer to them as usual (ifconfig, - route, etc). - -o Procfs entries - 2 entries are added to help fetching alias runtime configuration: - a) /proc/net/alias_types - Will show you alias_types registered (ie. address families that - can be aliased). - eg. for IP aliasing with 1 alias configured: - - # cat /proc/net/alias_types - type name n_attach - 2 ip 1 - - b) /proc/net/aliases - Will show aliased devices info, eg (same as above): - # cat /proc/net/aliases - device family address - eth0:0 2 200.1.1.1 + Aliases are no real devices, but should be able to configure and + refer to them as usual (ifconfig, route, etc). Relationship with main device ----------------------------- - - On main device closing, all aliases will be closed and freed. - - Each new alias created is inserted in dev_chain just before next - main device (aliases get 'stacked' after main_dev), eg: - lo->eth0->eth0:0->eth0:2->eth1->0 - If eth0 is unregistered, all it aliases will also be: - lo->eth1->0 + + - the main device is an alias itself like additional aliases and can + be shut down without deleting other aliases. Contact ------- Please finger or e-mail me: Juan Jose Ciarlante <jjciarla@raiz.uncu.edu.ar> - - + +Updated by Erik Schoenfelder <schoenfr@gaertner.DE> + ; local variables: ; mode: indented-text ; mode: auto-fill diff --git a/Documentation/networking/de4x5.txt b/Documentation/networking/de4x5.txt index 3e838c222..dc6a99a7a 100644 --- a/Documentation/networking/de4x5.txt +++ b/Documentation/networking/de4x5.txt @@ -11,9 +11,9 @@ Digital Semiconductor SROM Specification. The driver currently recognises the following chips: - DC21040 (no SROM) - DC21041[A] - DC21140[A] + DC21040 (no SROM) + DC21041[A] + DC21140[A] DC21142 DC21143 @@ -57,7 +57,7 @@ 1) copy de4x5.c from the /linux/drivers/net directory to your favourite temporary directory. 2) for fixed autoprobes (not recommended), edit the source code near - line 5537 to reflect the I/O address you're using, or assign these when + line 5594 to reflect the I/O address you're using, or assign these when loading by: insmod de4x5 io=0xghh where g = bus number @@ -92,6 +92,16 @@ can compile with a DEC_ONLY define, or if loading as a module, use the 'dec_only=1' parameter. + I've changed the timing routines to use the kernel timer and scheduling + functions so that the hangs and other assorted problems that occurred + while autosensing the media should be gone. A bonus for the DC21040 + auto media sense algorithm is that it can now use one that is more in + line with the rest (the DC21040 chip doesn't have a hardware timer). + The downside is the 1 'jiffies' (10ms) resolution. + + IEEE 802.3u MII interface code has been added in anticipation that some + products may use it in the future. + The SMC9332 card has a non-compliant SROM which needs fixing - I have patched this driver to detect it because the SROM format used complies to a previous DEC-STD format. @@ -133,11 +143,36 @@ is the preferred way to use this driver, since it doesn't have this limitation. - Where SROM media detection is used and full duplex is specified in the - SROM, the feature is ignored unless de4x5_full_duplex is set at compile - time OR during a module load (insmod de4x5 de4x5_full_duplex=1). This - is because there is no way to automatically detect full duplex links - except through autonegotiation. When I include the autonegotiation - feature in the SROM autoconf code, this detection will occur - automatically. - + Where SROM media detection is used and full duplex is specified in the + SROM, the feature is ignored unless lp->params.fdx is set at compile + time OR during a module load (insmod de4x5 args='eth??:fdx' [see + below]). This is because there is no way to automatically detect full + duplex links except through autonegotiation. When I include the + autonegotiation feature in the SROM autoconf code, this detection will + occur automatically for that case. + + Command line arguements are now allowed, similar to passing arguements + through LILO. This will allow a per adapter board set up of full duplex + and media. The only lexical constraints are: the board name (dev->name) + appears in the list before its parameters. The list of parameters ends + either at the end of the parameter list or with another board name. The + following parameters are allowed: + + fdx for full duplex + autosense to set the media/speed; with the following + sub-parameters: + TP, TP_NW, BNC, AUI, BNC_AUI, 100Mb, 10Mb, AUTO + + Case sensitivity is important for the sub-parameters. They *must* be + upper case. Examples: + + insmod de4x5 args='eth1:fdx autosense=BNC eth0:autosense=100Mb'. + + For a compiled in driver, in linux/drivers/net/CONFIG, place e.g. + DE4X5_OPTS = -DDE4X5_PARM='"eth0:fdx autosense=AUI eth2:autosense=TP"' + + Yes, I know full duplex isn't permissible on BNC or AUI; they're just + examples. By default, full duplex is turned off and AUTO is the default + autosense setting. In reality, I expect only the full duplex option to + be used. Note the use of single quotes in the two examples above and the + lack of commas to separate items. diff --git a/Documentation/networking/depca.txt b/Documentation/networking/depca.txt new file mode 100644 index 000000000..24c6b26e5 --- /dev/null +++ b/Documentation/networking/depca.txt @@ -0,0 +1,92 @@ + +DE10x +===== + +Memory Addresses: + + SW1 SW2 SW3 SW4 +64K on on on on d0000 dbfff + off on on on c0000 cbfff + off off on on e0000 ebfff + +32K on on off on d8000 dbfff + off on off on c8000 cbfff + off off off on e8000 ebfff + +DBR ROM on on dc000 dffff + off on cc000 cffff + off off ec000 effff + +Note that the 2K mode is set by SW3/SW4 on/off or off/off. Address +assignment is through the RBSA register. + +I/O Address: + SW5 +0x300 on +0x200 off + +Remote Boot: + SW6 +Disable on +Enable off + +Remote Boot Timeout: + SW7 +2.5min on +30s off + +IRQ: + SW8 SW9 SW10 SW11 SW12 +2 on off off off off +3 off on off off off +4 off off on off off +5 off off off on off +7 off off off off on + +DE20x +===== + +Memory Size: + + SW3 SW4 +64K on on +32K off on +2K on off +2K off off + +Start Addresses: + + SW1 SW2 SW3 SW4 +64K on on on on c0000 cffff + on off on on d0000 dffff + off on on on e0000 effff + +32K on on off off c8000 cffff + on off off off d8000 dffff + off on off off e8000 effff + +Illegal off off - - - - + +I/O Address: + SW5 +0x300 on +0x200 off + +Remote Boot: + SW6 +Disable on +Enable off + +Remote Boot Timeout: + SW7 +2.5min on +30s off + +IRQ: + SW8 SW9 SW10 SW11 SW12 +5 on off off off off +9 off on off off off +10 off off on off off +11 off off off on off +15 off off off off on + diff --git a/Documentation/networking/filter.txt b/Documentation/networking/filter.txt new file mode 100644 index 000000000..60deb1771 --- /dev/null +++ b/Documentation/networking/filter.txt @@ -0,0 +1,42 @@ +filter.txt: Linux Socket Filtering +Written by: Jay Schulist <Jay.Schulist@spacs.k12.wi.us> + +Introduction +============ + + Linux Socket Filtering is derived from the Berkeley +Packet Filter. There are some distinct differences between +the BSD and Linux Kernel Filtering. + +Linux Socket Filtering (LSF) allows a user-space program to +attach a filter onto any socket and allow or disallow certain +types of data to come through the socket. LSF follows exactly +the same filter code structure as the BSD Berkeley Packet Filter +(BPF), so refering to the BSD bpf.4 manpage is very helpful in +creating filters. + +LSF is much simpler that BPF. One does not have to worry about +devices or anything like that. You simply create your filter +code, send it to the kernel via the SO_ATTACH_FILTER ioctl and +if you filter code passes the kernel check on it, you then +immediately begin filtering data on that socket. + +You can also detach filters from your socket via the +SO_DETACH_FILTER ioctl. This will probably not be used much +since when you close a socket that has a filter on it the +filter is automagicly removed. The other less common case +may be adding a differnt filter on the same socket you had another +filter that is still running, the kernel takes care of removing +the old one and placing your new one in its place, assumming your +filter has passed the checks, otherwise if it fails the old filter +will remain on that socket. + +Examples +======== + +Ioctls- +setsockopt(sockfd, SOL_SOCKET, SO_ATTACH_FILTER, &Filter, sizeof(Filter)); +setsockopt(sockfd, SOL_SOCKET, SO_DETACH_FILTER, &value, sizeof(value)); + +See the BSD bpf.4 manpage and the BSD Packet Filter paper written by +Steven McCanne and Van Jacobson of Lawrence Berkeley Laboratory. diff --git a/Documentation/networking/ipddp.txt b/Documentation/networking/ipddp.txt new file mode 100644 index 000000000..6ed2d93f5 --- /dev/null +++ b/Documentation/networking/ipddp.txt @@ -0,0 +1,78 @@ +Text file for ipddp.c: + Appletalk-IP Decapsulation and Appletalk-IP Encapsulation + +This text file writen by Jay Schulist <Jay.Schulist@spacs.k12.wi.us> + +Introduction +------------ + +Appletalk-IP (IPDDP) is the method computers connected to Appletalk +networks can communicate via IP. Appletalk-IP is simply IP datagrams +inside Appletalk packets. + +Through this driver you can either allow your Linux box to communicate +IP over an Appletalk network or you can provide IP gatewaying functions +for you Appletalk users. + +You can currently Encapsulate or Decapsulate Appletalk-IP on LocalTalk, +EtherTalk and PPPTalk. The only limit on the protocol is that of what +the kernel Appletalk layer and drivers are available. + +Each mode requires its own user space software. + +Compiling Appletalk-IP Decapsulation/Encapsulation +================================================= + +Appletalk-IP Decapsulation needs to be compiled into your kernel. You +will need to turn on Appletalk-IP driver support. Then you will need to +select ONE of the two options; IP to Appletalk-IP Encapsulation support or +Appletalk-IP to IP Decapsulation support. If you compile the driver +staticly you will only be able to use the driver for the function you have +enabled in the kernel. If you compile the driver as a module you can +select what mode you want it to run in via a module loading param. +ipddp_mode=1 for Appletalk-IP Encapsulation and ipddp_mode=2 for +Appletalk-IP to IP Decapsulation. + +Basic instructions for user space tools +======================================= + +To enable Appletalk-IP Decapsulation/Encapsulation you will need the +proper tools. You can get the tools for Decapsulation from +http://spacs1.spacs.k12.wi.us/~jschlst/MacGate and for Encapsulation +from http://www.maths.unm.edu/~bradford/ltpc.html + +I will briefly describe the operation of the tools, but you will +need to consult the supporting documentation for each set of tools. + +Decapsulation - You will need to download a software package called +MacGate. In this distribution there will be a tool called MacRoute +which enabled you to add routes to the kernel for your Macs by hand. +Also the tool MacRegGateWay is included to register the +proper IP Gateway and IP addresses for your machine. Included in this +distribution is a patch to netatalk-1.4b2+asun2.0a17.2 (available from +ftp.u.washington.edu/pub/user-supported/asun/) this patch is optional +but it allows automatic adding and deleting of routes for Macs. (Handy +for locations with large Mac installations) + +Encapsulation - You will need to download a software daemon called ipddpd. +This software expects there to be and Appletalk-IP gateway on the network. +You will also need to add the proper routes to route your Linux box's IP +traffic out the ipddp interface. + +Common Uses of ipddp.c +---------------------- +Of course Appletalk-IP Decapsulation and Encapsulation, but specificly +Decapsulation is being used most for connecting LocalTalk networks to +IP networks. Although it has been used on EtherTalk networks to allow +Macs that are only able to tunnel IP over EtherTalk. + +Encapsulation has been used to allow a Linux box stuck on a LocalTalk +network to use IP. It should work equally well if you are stuck on an +EtherTalk only network. + +Further Assisatance +------------------- +You can contact me (Jay Schulist <Jay.Schulist@spacs.k12.wi.us>) with any +questions reguarding Decapsulation or Encapsulation. Bradford W. Johnson +<johns393@maroon.tc.umn.edu> originally wrote the ipddp.c driver for IP +encapsulation in Appletalk. diff --git a/Documentation/networking/scc.txt b/Documentation/networking/scc.txt deleted file mode 100644 index b3eb3445c..000000000 --- a/Documentation/networking/scc.txt +++ /dev/null @@ -1,23 +0,0 @@ - -You will find subset of the documentation in - - linux/Documentation/networking/z8530drv.txt - -To use this driver you MUST have the full package from: - -Internet: -========= - -1. db0bm.automation.fh-aachen.de/incoming/dl1bke/z8530drv-utils-3.0.tar.gz - -2. ftp.ucsd.edu:/hamradio/packet/tcpip/incoming/z8530drv-utils-3.0.tar.gz - If you can't find it there, try .../tcpip/linux/z8530drv-utils-3.0.tar.gz - -and various mirrors (i.e. nic.switch.ch) - -The package includes the utilities necessary to initialize and -control the driver. - -Joerg Reuter ampr-net: dl1bke@db0pra.ampr.org - AX-25 : DL1BKE @ DB0ACH.#NRW.DEU.EU - Internet: jreuter@lykos.oche.de diff --git a/Documentation/networking/wan-router.txt b/Documentation/networking/wan-router.txt index 3062f43d5..7f64cbc72 100644 --- a/Documentation/networking/wan-router.txt +++ b/Documentation/networking/wan-router.txt @@ -1,6 +1,8 @@ ------------------------------------------------------------------------------ WAN Router for Linux Operating System ------------------------------------------------------------------------------ +Version 2.0.1 - Nov 28, 1997 +Version 2.0.0 - Nov 06, 1997 Version 1.0.3 - June 3, 1997 Version 1.0.1 - January 30, 1997 Author: Jaspreet Singh <jaspreet@sangoma.com> @@ -8,6 +10,11 @@ Author: Jaspreet Singh <jaspreet@sangoma.com> Copyright (c) 1995-1997 Sangoma Technologies Inc. ------------------------------------------------------------------------------ + +WARNING: This Version of WANPIPE supports only the S508 and S508/FT1 cards. +IF YOU OWN A S502E OR A S508 CARD THEN PLEASE CONTACT SANGOMA TECHNOLOGIES FOR +AN UPGRADE. + INTRODUCTION Wide Area Networks (WANs) are used to interconnect Local Area Networks (LANs) @@ -73,10 +80,14 @@ assist WAN device driver writer by providing common services, such as: To ba able to use Linux WAN Router you will also need a WAN Tools package available from - ftp.sangoma.com/pub/linux/wantools-X.Y.Z.tgz + ftp.sangoma.com/pub/linux/vX.Y.Z/wantools-X.Y.Z.tgz + or + ftp.sangoma.com/pub/linux/vX.Y.Z/wanpipe-X.Y.Z.tgz + +where vX.Y.Z represent the linux kernel version number. For technical questions and/or comments regarding this product please e-mail -to genek@compuserve.com or dm@sangoma.com. +to jaspreet@sangoma.com or dm@sangoma.com. @@ -117,19 +128,55 @@ product. REVISION HISTORY + +2.0.1 Nov 28, 1997 - Protection of "enable_irq()" while + "disable_irq()" has been enabled from any other + routine (for Frame Relay, PPP and X25). + - Added additional Stats for Fpipemon and Ppipemon - Improved Load Sharing for multiple boards. + + +2.0.0 Nov 07, 1997 - Implemented protection of RACE conditions by + critical flags for FRAME RELAY and PPP. + - DLCI List interrupt mode implemented. + - IPX support in FRAME RELAY and PPP. + - IPX Server Support (MARS) + - More driver specific stats included in FPIPEMON + and PIPEMON. + +1.0.5 July 28, 1997 - Configurable T391,T392,N391,N392,N393 for Frame + Relay in router.conf. + - Configurable Memory Address through router.conf + for Frame Relay, PPP and X.25. (commenting this + out enables auto-detection). + - Fixed freeing up received buffers using kfree() + for Frame Relay and X.25. + - Protect sdla_peek() by calling save_flags(), + cli() and restore_flags(). + - Changed number of Trace elements from 32 to 20 + - Added DLCI specific data monitoring in FPIPEMON. + +1.0.4 July 10, 1997 - S508/FT1 monitoring capability in fpipemon and + ppipemon utilities. + - Configurable TTL for UDP packets. + - Multicast and Broadcast IP source addresses are + silently discarded. + 1.0.3 June 3, 1997 - o UDP port for multiple boards (Frame relay, PPP) - o Continuous Transmission of Configure Request Packet for PPP (this - support is only added for 508 cards) - o Connection Timeout for PPP changed from 900 to 0 - o Flow Control for multiple boards and multiple channels (Frame Relay) + - UDP port for multiple boards (Frame relay, PPP) + Continuous Transmission of Configure Request + - Packet for PPP (this support is only added for + 508 cards) + - Connection Timeout for PPP changed from 900 to 0 + - Flow Control for multiple boards and multiple + channels (Frame Relay) 1.0.1 January 30, 1997 - o Implemented user-readable status and statistics via /proc filesystem + - Implemented user-readable status and statistics + via /proc filesystem 1.0.0 December 31, 1996 - o Initial version + - Initial version >>>>>> END <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< diff --git a/Documentation/networking/wanpipe.txt b/Documentation/networking/wanpipe.txt index 9650edb73..5288c8259 100644 --- a/Documentation/networking/wanpipe.txt +++ b/Documentation/networking/wanpipe.txt @@ -1,9 +1,9 @@ ------------------------------------------------------------------------------ WANPIPE(tm) Multiprotocol WAN Driver for Linux WAN Router ------------------------------------------------------------------------------ -Release 3.1.0 -January 30, 1997 -Author: Gene Kozin <genek@compuserve.com> +Release 4.1 +November 17, 1997 +Author: Jaspreet Singh <jaspreet@sangoma.com> Copyright (c) 1995-1997 Sangoma Technologies Inc. ------------------------------------------------------------------------------ @@ -23,8 +23,13 @@ package to be able to use Linux WAN Router and WANPIPE driver. The package is available via the Internet from Sangoma Technologies' anonymous FTP server: ftp.sangoma.com/pub/linux/wantools-X.Y.Z.tgz + or + ftp.sangoma.com/pub/linux/wanpipe-X.Y.Z.tgz -For technical questions and/or comments please e-mail to genek@compuserve.com. +The name of the package differ only due to naming convention. The functionalityof wantools and wanpipe packages are the same. The latest version of WAN +Drivers is wanpipe-2.0.0. + +For technical questions and/or comments please e-mail to jaspreet@sangoma.com. For general inquiries please contact Sangoma Technologies Inc. by Hotline: 1-800-388-2475 (USA and Canada, toll free) @@ -53,10 +58,13 @@ Ave, Cambridge, MA 02139, USA. NEW IN THIS RELEASE - o Implemented as WAN Link Driver compliant with Linux WAN Router interface - o Added support for X.25 protocol - o Miscellaneous bug fixes and performance improvements - + o This Version of WANPIPE supports only the S508 and S508/FT1 cards. IF YOU + OWN A S502E OR A S508 CARD THEN PLEASE CONTACT SANGOMA TECHNOLOGIES FOR AN + UPGRADE. + o Protection of "enable_irq()" while "disable_irq()" has been enabled from + any other routine (for Frame Relay, PPP and X25). + o Added additional Stats for Fpipemon and Ppipemon. + o Improved Load Sharing for multiple boards FILE LIST @@ -64,23 +72,39 @@ FILE LIST drivers/net: README.wanpipe This file sdladrv.c SDLA support module source code - wpmain.c WANPIPE driver module main source code - wpx.c WANPIPE driver module X.25 source code - wpf.c WANPIPE driver module frame relay source code - wpp.c WANPIPE driver module PPP source code + sdla_fr.c SDLA Frame Relay source code + sdla_ppp.c SDLA PPP source code + sdla_x25.c SDLA X25 source code + sdlamain.c SDLA support source code + +include/linux: sdla_x25.h SDLA X.25 firmware API definitions sdla_fr.h SDLA frame relay firmware API definitions sdla_ppp.h SDLA PPP firmware API definitions - -include/linux: wanpipe.h WANPIPE API definitions sdladrv.h SDLA support module API definitions sdlasfm.h SDLA firmware module definitions - + router.h REVISION HISTORY +4.1 November 28, 1997 + o Protection of "enable_irq()" while "disable_irq()" has been enabled + from any other routine (for Frame Relay, PPP and X25). + o Added additional Stats for Fpipemon and Ppipemon + o Improved Load Sharing for multiple boards + + +4.0 November 06, 1997 + o Implemented better protection of RACE conditions by critical flags for + FRAME RELAY, PPP and X25. + o DLCI List interrupt mode implemented for DLCI specific CIR. + o IPX support for FRAME RELAY, PPP and X25. + o IPX Server Support (MARS) for FRAME RELAY, PPP and X25. + o More driver specific stats included. + o MULTICAST for FRAME RELAY and PPP. + 3.1.0 January 30, 1997 o Implemented IOCTL for executing adapter commands. diff --git a/Documentation/networking/z8530drv.txt b/Documentation/networking/z8530drv.txt index ac22b0b15..b566181a9 100644 --- a/Documentation/networking/z8530drv.txt +++ b/Documentation/networking/z8530drv.txt @@ -4,9 +4,9 @@ full package from: Internet: ========= -1. ftp://db0bm.automation.fh-aachen.de/incoming/z8530drv/z8530drv-utils-3.0.tar.gz +1. ftp://ftp.ccac.rwth-aachen.de/pub/jr/z8530drv-utils-3.0-1.tar.gz -2. ftp://ftp.pspt.fi/pub/ham/linux/ax25/z8530drv-utils-3.0.tar.gz +2. ftp://ftp.pspt.fi/pub/ham/linux/ax25/z8530drv-utils-3.0-1.tar.gz 3. ftp://ftp.ucsd.edu/hamradio/packet/tcpip/incoming/z8530drv-utils-3.0.tar.gz If you can't find it there, try .../tcpip/linux/z8530drv-utils-3.0.tar.gz @@ -23,7 +23,7 @@ http://www.rat.de/jr ******************************************************************** - (c) 1993,1997 by Joerg Reuter DL1BKE <jreuter@poboxes.com> + (c) 1993,1998 by Joerg Reuter DL1BKE <jreuter@poboxes.com> portions (c) 1993 Guido ten Dolle PE1NNZ diff --git a/Documentation/paride.txt b/Documentation/paride.txt new file mode 100644 index 000000000..923377cad --- /dev/null +++ b/Documentation/paride.txt @@ -0,0 +1,338 @@ + + Linux and parallel port IDE devices + +PARIDE v1.0 (c) 1997 Grant Guenther <grant@torque.net> + +1. Introduction + +Owing to the simplicity and near universality of the parallel port interface +to personal computers, many external devices such as portable hard-disk, +CD-ROM, LS-120 and tape drives use the parallel port to connect to their +host computer. While some devices (notably scanners) use ad-hoc methods +to pass commands and data through the parallel port interface, most +external devices are actually identical to an internal model, but with +a parallel-port adapter chip added in. Some of the original parallel port +adapters were little more than mechanisms for mulitplexing a SCSI bus. +(The Iomega PPA-3 adapter used in the ZIP drives is an example of this +approach). Most current designs, however, take a different approach. +The adapter chip reproduces a small ISA or IDE bus in the external device +and the communication protocol provides operations for reading and writing +device registers, as well as data block transfer functions. Sometimes, +the device being addressed via the parallel cable is a standard SCSI +controller like an NCR 5380. The "ditto" family of external tape +drives use the ISA replicator to interface a floppy disk controller, +which is then connected to a floppy-tape mechanism. The vast majority +of external parallel port devices, however, are now based on standard +IDE type devices, which require no intermediate controller. If one +were to open up a parallel port CD-ROM drive, for instance, one would +find a standard ATAPI CD-ROM drive, a power supply, and a single adapter +that interconnected a standard PC parallel port cable and a standard +IDE cable. It is usually possible to exchange the CD-ROM device with +any other device using the IDE interface. + +The document describes the support in Linux for parallel port IDE +devices. It does not cover parallel port SCSI devices, "ditto" tape +drives or scanners. Many different devices are supported by the +parallel port IDE subsystem, including: + + MicroSolutions backpack CD-ROM + MicroSolutions backpack PD/CD + MicroSolutions backpack hard-drives + SyQuest EZ-135, EZ-230 & SparQ drives + Avatar Shark + Imation Superdisk LS-120 + FreeCom Power CD + Hewlett-Packard 5GB tape drive + +as well as most of the clone and no-name products on the market. + +To support such a wide range of devices, PARIDE, the parallel port IDE +subsystem, is actually structured in three parts. There is a base +paride module which provides a registry and some common methods for +accessing the parallel ports. The second component is a set of +high-level drivers for each of the different type of supported device: + + pd IDE disk + pcd ATAPI CD-ROM + pf ATAPI disk + pt ATAPI tape + +(Support for ATAPI CD-R and CD-RW drives is not yet in development, +but this may change.) + +The high-level drivers function according to the relevant standards. +The third component of PARIDE is a set of low-level protocol drivers +for each of the parallel port IDE adapter chips. Thanks to the interest +and encouragement of Linux users from many parts of the world, +support is available for almost all known adapter protocols: + + aten ATEN EH-100 (HK) + bpck Microsolutions backpack (US) + comm DataStor (old-type) "commuter" adapter (TW) + dstr DataStor EP-2000 (TW) + epat Shuttle EPAT (UK) + epia Shuttle EPIA (UK) + frpw Freecom Power (DE) + kbic KingByte KBIC-951A and KBIC-971A (TW) + on20 OnSpec 90c20 (US) + on26 OnSpec 90c26 (US) + +(A driver for some modes of the Noveca RAP// protocol is also under +development). + + +2. Using the PARIDE subsystem + +While configuring the Linux kernel, you may choose either to build +the PARIDE drivers into your kernel, or to build them as modules. + +In either case, you will need to select "Parallel port IDE device support" +as well as at least one of the high-level drivers and at least one +of the parallel port communication protocols. If you do not know +what kind of parallel port adapter is used in your drive, you could +begin by checking the file names and any text files on your DOS +installation floppy. Alternatively, you can look at the markings on +the adapter chip itself. That's usually sufficient to identify the +correct device. + +You can actually select all the protocol modules, and allow the PARIDE +subsystem to try them all for you. + +For the "brand-name" products listed above, here are the protocol +and high-level drivers that you would use: + + Manufacturer Model Driver Protocol + + MicroSolutions CD-ROM pcd bpck + MicroSolutions PD drive pf bpck + MicroSolutions hard-drive pd bpck + SyQuest EZ, SparQ pd epat + Imation Superdisk pf epat + Avatar Shark pd epat + FreeCom CD-ROM pcd frpw + Hewlett-Packard 5GB Tape pt epat + +2.1 Configuring built-in drivers + +We recommend that you get to know how the drivers work and how to +configure them as loadable modules, before attempting to compile a +kernel with the drivers built-in. + +If you built all of your PARIDE support directly into your kernel, +and you have just a single parallel port IDE device, your kernel should +locate it automatically for you. If you have more than one device, +you may need to give some command line options to your bootloader +(eg: LILO), how to do that is beyond the scope of this document. + +The high-level drivers accept a number of command line parameters, all +of which are documented in the source files in linux/drivers/block/paride. +By default, each driver will automatically try all parallel ports it +can find, and all protocol types that have been installed, until it finds +a parallel port IDE adapter. Once it finds one, the probe stops. So, +if you have more than one device, you will need to tell the drivers +how to identify them. This requires specifying the port address, the +protocol identification number and, for some devices, the drive's +chain ID. While your system is booting, a number of messages are +displayed on the console. Like all such messages, they can be +reviewed with the 'dmesg' command. Among those messages will be +some lines like: + + paride: bpck registered as protocol 0 + paride: epat registered as protocol 1 + +The numbers will always be the same until you build a new kernel with +different protocol selections. You should note these numbers as you +will need them to identify the devices. + +If you happen to be using a MicroSolutions backpack device, you will +also need to know the unit ID number for each drive. This is usually +the last two digits of the drive's serial number (but read MicroSolution's +documentation about this). + +As an example, lets assume that you have a MicroSolutions PD/CD drive +with unit ID number 36 connected to the parallel port at 0x378, a SyQuest +EZ-135 connected to the chained port on the PD/CD drive and also an +Imation Superdisk connected to port 0x278. You could give the following +options on your boot command: + + pd.drive0=0x378,1 pf.drive0=0x278,1 pf.drive1=0x378,0,36 + +In the last option, pf.drive1 configures device /dev/pf1, the 0x378 +is the parallel port base address, the 0 is the protocol registration +number and 36 is the chain ID. + +Please note: while PARIDE will work both with and without the +PARPORT parallel port sharing system that is included by the +"Parallel port support" option, PARPORT must be included and enabled +if you want to use chains of devices on the same parallel port. + +2.2 Loading and configuring PARIDE as modules + +It is much faster and simpler to get to understand the PARIDE drivers +if you use them as loadable kernel modules. + +Note 1: using these drivers with the "kerneld" automatic module loading +system is not recommended, and is not documented here. + +Note 2: if you build PARPORT support as a loadable module, PARIDE must +also be built as loadable modules, and PARPORT must be loaded before the +PARIDE modules. + +To use PARIDE, you must begin by + + insmod paride + +this loads a base module which provides a registry for the protocols, +among other tasks. + +Then, load as many of the protocol modules as you think you might need. +As you load each module, it will register the protocols that it supports, +and print a log message to your kernel log file and your console. For +example: + + # insmod epat + paride: epat registered as protocol 0 + # insmod kbic + paride: k951 registered as protocol 1 + paride: k971 registered as protocol 2 + +Finally, you can load high-level drivers for each kind of device that +you have connected. By default, each driver will autoprobe for a single +device, but you can support up to four similar devices by giving their +individual co-ordinates when you load the driver. + +For example, if you had two no-name CD-ROM drives both using the +KingByte KBIC-951A adapter, one on port 0x378 and the other on 0x3bc +you could give the following command: + + # insmod pcd drive0=0x378,1 drive1=0x3bc,1 + +For most adapters, giving a port address and protocol number is sufficient, +but check the source files in linux/drivers/block/paride for more +information. (Hopefully someone will write some man pages one day !). + +As another example, here's what happens when PARPORT is installed, and +a SyQuest EZ-135 is attached to port 0x378: + + # insmod paride + paride: version 1.0 installed + # insmod epat + paride: epat registered as protocol 0 + # insmod pd + pd: pd version 1.0, major 45, cluster 64, nice 0 + pda: Sharing parport1 at 0x378 + pda: epat 1.0, Shuttle EPAT chip c3 at 0x378, mode 5 (EPP-32), delay 1 + pda: SyQuest EZ135A, 262144 blocks [128M], (512/16/32), removable media + pda: pda1 + +Note that the last line is the output from the generic partition table +scanner - in this case it reports that it has found a disk with one partition. + +2.3 Using a PARIDE device + +Once the drivers have been loaded, you can access PARIDE devices in the +same way as their traditional counterparts. You will probably need to +create the device "special files". Here is a simple script that you can +cut to a file and execute: + +#!/bin/bash +# +# mkd -- a script to create the device special files for the PARIDE subsystem +# +function mkdev { + mknod $1 $2 $3 $4 ; chmod 0660 $1 ; chown root:disk $1 +} +# +function pd { + D=$( printf \\$( printf "x%03x" $[ $1 + 97 ] ) ) + mkdev pd$D b 45 $[ $1 * 16 ] + for P in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 + do mkdev pd$D$P b 45 $[ $1 * 16 + $P ] + done +} +# +cd /dev +# +for u in 0 1 2 3 ; do pd $u ; done +for u in 0 1 2 3 ; do mkdev pcd$u b 46 $u ; done +for u in 0 1 2 3 ; do mkdev pf$u b 47 $u ; done +for u in 0 1 2 3 ; do mkdev pt$u c 96 $u ; done +for u in 0 1 2 3 ; do mkdev npt$u c 96 $[ $u + 128 ] ; done +# +# end of mkd + +With the device files and drivers in place, you can access PARIDE devices +like any other Linux device. For example, to mount a CD-ROM in pcd0, use: + + mount /dev/pcd0 /cdrom + +If you have a fresh Avatar Shark cartridge, and the drive is pda, you +might do something like: + + fdisk /dev/pda -- make a new partition table with + partition 1 of type 83 + + mke2fs /dev/pda1 -- to build the file system + + mkdir /shark -- make a place to mount the disk + + mount /dev/pda1 /shark + +Devices like the Imation superdisk work in the same way, except that +they do not have a partition table. For example to make a 120MB +floppy that you could share with a DOS system: + + mkdosfs /dev/pf0 + mount /dev/pf0 /mnt + + +3. Troubleshooting + +While a lot of testing has gone into these drivers to make them work +as smoothly as possible, problems will arise. If you do have problems, +please check all the obvious things first: does the drive work in +DOS with the manufacturer's drivers ? If that doesn't yield any useful +clues, then please make sure that only one drive is hooked to your system, +and that either (a) PARPORT is enabled or (b) no other device driver +is using your parallel port (check in /proc/ioports). Then, load the +appropriate drivers (you can load several protocol modules if you want) +as in: + + # insmod paride + # insmod epat + # insmod bpck + # insmod kbic + ... + # insmod pd verbose=1 + +(using the correct driver for the type of device you have, of course). +The verbose=1 parameter will cause the drivers to log a trace of their +activity as they attempt to locate your drive. + +Use 'dmesg' to capture a log of all the PARIDE messages (any messages +beginning with paride:, a protocol module's name or a driver's name) and +include that with your bug report. You can submit a bug report in one +of two ways. Either send it directly to the author of the PARIDE suite, +by e-mail to grant@torque.net, or join the linux-parport mailing list +and post your report there. + +You can join the linux-parport mailing list by sending a mail message +to + linux-parport-request@torque.net + +with the single word + + subscribe + +in the body of the mail message (not in the subject line). Please be +sure that your mail program is correctly set up when you do this, as +the list manager is a robot that will subscribe you using the reply +address in your mail headers. REMOVE any anti-spam gimmicks you may +have in your mail headers, when sending mail to the list server. + +You might also find some useful information on the linux-parport +web pages (although they are not always up to date) at + + http://www.torque.net/linux-pp.html + + diff --git a/Documentation/powerpc/00-INDEX b/Documentation/powerpc/00-INDEX index d432cd274..9e553e6c8 100644 --- a/Documentation/powerpc/00-INDEX +++ b/Documentation/powerpc/00-INDEX @@ -7,5 +7,8 @@ please mail me. - this file ppc_htab.txt - info about the Linux/PPC /proc/ppc_htab entry +smp.txt + - use and state info about Linux/PPC on MP machines sound.txt - info on sound support under Linux/PPC + diff --git a/Documentation/powerpc/smp.txt b/Documentation/powerpc/smp.txt new file mode 100644 index 000000000..932170f74 --- /dev/null +++ b/Documentation/powerpc/smp.txt @@ -0,0 +1,20 @@ + Information about Linux/PPC SMP mode +===================================================================== + +This document and the related code was written by me (Cort Dougan), please +email me (cort@cs.nmt.edu) if you have questions, comments or corrections. + +SMP support for Linux/PPC is still in its early stages and likely to +be buggy for a while. If you want to help by writing code or testing +different hardware please email me! + +1. State of Supported Hardware + + UMAX s900 + The second processor on this machine boots up just fine and + enters its idle loop. Hopefully a completely working SMP kernel + on this machine will be done shortly. + + BeBox + BeBox support hasn't been added to the 2.1.X kernels from 2.0.X + but work is being done and SMP support for BeBox is in the works. diff --git a/Documentation/riscom8.txt b/Documentation/riscom8.txt index 6157bb11d..92c20238a 100644 --- a/Documentation/riscom8.txt +++ b/Documentation/riscom8.txt @@ -1,5 +1,5 @@ This is the README for RISCom/8 multi-port serial driver - (C) 1994-1996 D.Gorodchanin (begemot@bgm.rosrpint.net) + (C) 1994-1996 D.Gorodchanin (pgmdsg@ibi.com) See file LICENSE for terms and conditions. NOTE: English is not my native language. diff --git a/Documentation/smart-config.txt b/Documentation/smart-config.txt new file mode 100644 index 000000000..eda5c3dfa --- /dev/null +++ b/Documentation/smart-config.txt @@ -0,0 +1,103 @@ +Smart CONFIG_* Dependencies +Fri 2 Dec 1997 + +Michael Chastain <mec@shout.net> +Werner Almesberger <almesber@lrc.di.epfl.ch> +Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de> + +Here is the problem: + + Suppose that drivers/net/foo.c has the following lines: + + #include <linux/config.h> + + ... + + #ifdef CONFIG_FOO_AUTOFROB + /* Code for auto-frobbing */ + #else + /* Manual frobbing only */ + #endif + + ... + + #ifdef CONFIG_FOO_MODEL_TWO + /* Code for model two */ + #endif + + Now suppose the user (the person building kernels) reconfigures the + kernel to change some unrelated setting. This will regenerate the + file include/linux/autoconf.h, which will cause include/linux/config.h + to be out of date, which will cause drivers/net/foo.c to be recompiled. + + Most kernel sources, perhaps 80% of them, have at least one CONFIG_* + dependency somewhere. So changing _any_ CONFIG_* setting requires + almost _all_ of the kernel to be recompiled. + +Here is the solution: + + We've made the dependency generator, mkdep.c, smarter. Instead of + generating this dependency: + + drivers/net/foo.c: include/linux/config.h + + It now generates these dependencies: + + drivers/net/foo.c: \ + include/config/foo_autofrob.h \ + include/config/foo_model_two.h + + So drivers/net/foo.c depends only on the CONFIG_* lines that + it actually uses. + + A new program, split-include.c, runs at the end of make config (also + make oldconfig, make menuconfig, and make xconfig). split-include + reads include/linux/autoconf.h and updates the include/linux/*.h + directory, writing one file per option. It updates only the files + that changed. + + mkdep.c also generates much better warning messages for missing + or unneeded <linux/config.h> lines. In fact, you can get these + messages without generating dependencies with the new top-level + target 'make checkconfig'. + +Flag Dependencies + + Martin Von Loewis contributed another feature to this patch: + 'flag dependencies'. The idea is that a .o file depends on + the compilation flags used to build it. The file foo.o has + its flags stored in .flags.foo.o. + + Suppose the user changes the foo driver from resident to + modular, 'make' will notice that the foo.o was not compiled + with -DMODULE and will recompile foo.c. + + Flag dependencies also work with per-source-file flags such + as those in drivers/net/CONFIG. + + All .a and .o files made from C source or with 'ld' or 'ar' + have flag dependencies. .S files do not have flag dependencies. + +Per-source-file Flags + + You can specify compilation flags for individual source files + like this: + + CFLAGS_foo.o = -DSPECIAL_FOO_DEFINE + + This helps clean up drivers/net/Makefile, drivers/scsi/Makefile, + and several other Makefiles. + +Credit + + Werner Almesberger had the original idea and wrote the first + version of this patch. + + Michael Chastain picked it up and continued development. He is + now the principal author and maintainer. Report bugs to him, + or to all three people together. + + Martin von Loewis wrote flag dependencies, with some modifications + by Michael Chastain. + + Thanks to all of the beta testers. diff --git a/Documentation/spinlocks.txt b/Documentation/spinlocks.txt new file mode 100644 index 000000000..1d749b942 --- /dev/null +++ b/Documentation/spinlocks.txt @@ -0,0 +1,186 @@ +On Fri, 2 Jan 1998, Doug Ledford wrote: +> +> I'm working on making the aic7xxx driver more SMP friendly (as well as +> importing the latest FreeBSD sequencer code to have 7895 support) and wanted +> to get some info from you. The goal here is to make the various routines +> SMP safe as well as UP safe during interrupts and other manipulating +> routines. So far, I've added a spin_lock variable to things like my queue +> structs. Now, from what I recall, there are some spin lock functions I can +> use to lock these spin locks frmo other use as oppossed to a (nasty) +> save_flags(); cli(); stuff; restore_flags(); construct. Where do I find +> these routines and go about making use of them? Do they only lock on a +> per-processor basis or can they also lock say an interrupt routine from +> mucking with a queue if the queue routine was manipulating it when the +> interrupt occured, or should I still use a cli(); based construct on that +> one? + +See <asm/spinlock.h>. The basic version is: + + spinlock_t xxx_lock = SPIN_LOCK_UNLOCKED; + + + unsigned long flags; + + spin_lock_irqsave(&xxx_lock, flags); + ... critical section here .. + spin_unlock_irqrestore(&xxx_lock, flags); + +and the above is always safe. It will disable interrupt _locally_, but the +spinlock itself will guarantee the global lock, so it will guarantee that +there is only one thread-of-control within the region(s) protected by that +lock. + +Note that it works well even under UP - the above sequence under UP +essentially is just the same as doing a + + unsigned long flags; + + save_flags(flags); cli(); + ... critical section ... + restore_flags(flags); + +so the code does _not_ need to worry about UP vs SMP issues: the spinlocks +work correctly under both (and spinlocks are actually more efficient on +architectures that allow doing the "save_flags + cli" in one go because I +don't export that interface normally). + +NOTE NOTE NOTE! The reason the spinlock is so much faster than a global +interrupt lock under SMP is exactly because it disables interrupts only on +the local CPU. The spin-lock is safe only when you _also_ use the lock +itself to do locking across CPU's, which implies that EVERYTHING that +touches a shared variable has to agree about the spinlock they want to +use. + +The above is usually pretty simple (you usually need and want only one +spinlock for most things - using more than one spinlock can make things a +lot more complex and even slower and is usually worth it only for +sequences that you _know_ need to be split up: avoid it at all cost if you +aren't sure). HOWEVER, it _does_ mean that if you have some code that does + + cli(); + .. critical section .. + sti(); + +and another sequence that does + + spin_lock_irqsave(flags); + .. critical section .. + spin_unlock_irqrestore(flags); + +then they are NOT mutually exclusive, and the critical regions can happen +at the same time on two different CPU's. That's fine per se, but the +critical regions had better be critical for different things (ie they +can't stomp on each other). + +The above is a problem mainly if you end up mixing code - for example the +routines in ll_rw_block() tend to use cli/sti to protect the atomicity of +their actions, and if a driver uses spinlocks instead then you should +think about issues like the above.. + +This is really the only really hard part about spinlocks: once you start +using spinlocks they tend to expand to areas you might not have noticed +before, because you have to make sure the spinlocks correctly protect the +shared data structures _everywhere_ they are used. The spinlocks are most +easily added to places that are completely independent of other code (ie +internal driver data structures that nobody else ever touches, for +example). + +---- + +Lesson 2: reader-writer spinlocks. + +If your data accesses have a very natural pattern where you usually tend +to mostly read from the shared variables, the reader-writer locks +(rw_lock) versions of the spinlocks are often nicer. They allow multiple +readers to be in the same critical region at once, but if somebody wants +to change the variables it has to get an exclusive write lock. The +routines look the same as above: + + rwlock_t xxx_lock = RW_LOCK_UNLOCKED; + + + unsigned long flags; + + read_lock_irqsave(&xxx_lock, flags); + .. critical section that only reads the info ... + read_unlock_irqrestore(&xxx_lock, flags); + + write_lock_irqsave(&xxx_lock, flags); + .. read and write exclusive access to the info ... + write_unlock_irqrestore(&xxx_lock, flags); + +The above kind of lock is useful for complex data structures like linked +lists etc, especially when you know that most of the work is to just +traverse the list searching for entries without changing the list itself, +for example. Then you can use the read lock for that kind of list +traversal, which allows many concurrent readers. Anything that _changes_ +the list will have to get the write lock. + +Note: you cannot "upgrade" a read-lock to a write-lock, so if you at _any_ +time need to do any changes (even if you don't do it every time), you have +to get the write-lock at the very beginning. I could fairly easily add a +primitive to create a "upgradeable" read-lock, but it hasn't been an issue +yet. Tell me if you'd want one. + +---- + +Lesson 3: spinlocks revisited. + +The single spin-lock primitives above are by no means the only ones. They +are the most safe ones, and the ones that work under all circumstances, +but partly _because_ they are safe they are also fairly slow. They are +much faster than a generic global cli/sti pair, but slower than they'd +need to be, because they do have to disable interrupts (which is just a +single instruction on a x86, but it's an expensive one - and on other +architectures it can be worse). + +If you have a case where you have to protect a data structure across +several CPU's and you want to use spinlocks you can potentially use +cheaper versions of the spinlocks. IFF you know that the spinlocks are +never used in interrupt handlers, you can use the non-irq versions: + + spin_lock(&lock); + ... + spin_unlock(&lock); + +(and the equivalent read-write versions too, of course). The spinlock will +guarantee the same kind of exclusive access, and it will be much faster. +This is useful if you know that the data in question is only ever +manipulated from a "process context", ie no interrupts involved. + +The reasons you mustn't use these versions if you have interrupts that +play with the spinlock is that you can get deadlocks: + + spin_lock(&lock); + ... + <- interrupt comes in: + spin_lock(&lock); + +where an interrupt tries to lock an already locked variable. This is ok if +the other interrupt happens on another CPU, but it is _not_ ok if the +interrupt happens on the same CPU that already holds the lock, because the +lock will obviously never be released (because the interrupt is waiting +for the lock, and the lock-holder is interrupted by the interrupt and will +not continue until the interrupt has been processed). + +(This is also the reason why the irq-versions of the spinlocks only need +to disable the _local_ interrupts - it's ok to use spinlocks in interrupts +on other CPU's, because an interrupt on another CPU doesn't interrupt the +CPU that holds the lock, so the lock-holder can continue and eventually +releases the lock). + +Note that you can be clever with read-write locks and interrupts. For +example, if you know that the interrupt only ever gets a read-lock, then +you can use a non-irq version of read locks everywhere - because they +don't block on each other (and thus there is no dead-lock wrt interrupts. +But when you do the write-lock, you have to use the irq-safe version. + +For an example of being clever with rw-locks, see the "waitqueue_lock" +handling in kernel/sched.c - nothing ever _changes_ a wait-queue from +within an interrupt, they only read the queue in order to know whom to +wake up. So read-locks are safe (which is good: they are very common +indeed), while write-locks need to protect themselves against interrupts. + + Linus + + diff --git a/Documentation/stallion.txt b/Documentation/stallion.txt index 73d31f7bd..aff00034e 100644 --- a/Documentation/stallion.txt +++ b/Documentation/stallion.txt @@ -2,10 +2,10 @@ Stallion Multiport Serial Driver Readme --------------------------------------- -Copyright (C) 1994-1997, Stallion Technologies (support@stallion.oz.au). +Copyright (C) 1994-1998, Stallion Technologies (support@stallion.com). -Version: 5.3.4 -Date: 15SEP97 +Version: 5.4.3 +Date: 04FEB98 @@ -13,32 +13,36 @@ Date: 15SEP97 There are two drivers that work with the different families of Stallion multiport serial boards. One is for the Stallion smart boards - that is -EasyIO and EasyConnection 8/32, the other for the true Stallion intelligent -multiport boards - EasyConnection 8/64, ONboard and Brumby. +EasyIO, EasyConnection 8/32 and EasyConnection 8/64-PCI, the other for +the true Stallion intelligent multiport boards - EasyConnection 8/64 +(ISA and EISA), ONboard and Brumby. If you are using any of the Stallion intelligent multiport boards (Brumby, -ONboard, EasyConnection 8/64) with Linux you will need to get the driver -utility package. This package is available at most of the Linux archive -sites (and on CD's that contain these archives). The file will be called -stallion-X.X.X.tar.gz where X.X.X will be the version number. In particular -this package contains the board embedded executable images that are -required for these boards. It also contains the downloader program. -These boards cannot be used without this. - -The following ftp sites (and their mirrors) definitely have the stallion -driver utility package: ftp.stallion.com, tsx-11.mit.edu, sunsite.unc.edu. - -ftp.stallion.com:/drivers/ata5/Linux/stallion-5.3.1.tar.gz -tsx-11.mit.edu:/pub/linux/BETA/serial/stallion/stallion-5.3.1.tar.gz -sunsite.unc.edu:/pub/Linux/kernel/patches/serial/stallion-5.3.1.tar.gz +ONboard, EasyConnection 8/64 (ISA or EISA)) with Linux you will need to +get the driver utility package. This package is available at most of the +Linux archive sites (and on CD-ROMs that contain these archives). The file +will be called stallion-X.X.X.tar.gz where X.X.X will be the version +number. In particular this package contains the board embedded executable +images that are required for these boards. It also contains the downloader +program. These boards cannot be used without this. + +The Stallion Technologies ftp site, ftp.stallion.com, will always have +the latest version of the driver utility package. Other sites that usually +have the latest version are tsx-11.mit.edu, sunsite.unc.edu and their +mirrors. + +ftp.stallion.com:/drivers/ata5/Linux/stallion-5.4.2.tar.gz +tsx-11.mit.edu:/pub/linux/packages/stallion/stallion-5.4.2.tar.gz +sunsite.unc.edu:/pub/Linux/kernel/patches/serial/stallion-5.4.2.tar.gz As of the printing of this document the latest version of the driver -utility package is 5.3.1. If a later version is now available then you +utility package is 5.4.2. If a later version is now available then you should use the latest version. -If you are using the EasyIO or EasyConnection 8/32 boards then you don't -need this package. Although it does have a handy script to create the -/dev device nodes for these boards, and a serial stats display program. +If you are using the EasyIO, EasyConnection 8/32 or EasyConnection 8/64-PCI +boards then you don't need this package. Although it does have a handy +script to create the /dev device nodes for these boards, and a serial stats +display program. If you require DIP switch settings, EISA/MCA configuration files, or any other information related to Stallion boards then have a look at Stallion's @@ -63,7 +67,7 @@ the instructions below. Both drivers can support up to 4 boards. The smart card driver (the stallion.c driver) supports any combination of EasyIO and EasyConnection 8/32 boards (up to a total of 4). The intelligent driver supports any combination of ONboards, Brumbys, Stallions and EasyConnection -8/64 boards (up to a total of 4). +8/64 (ISA and EISA) boards (up to a total of 4). To set up the driver(s) for the boards that you want to use you need to edit the appropriate driver file and add configuration entries. @@ -76,7 +80,8 @@ If using EasyIO or EasyConnection 8/32 ISA or MCA boards, do: (the comments before this structure should help) - save and exit -If using ONboard, Brumby, Stallion or EasyConnection 8/64 boards then do: +If using ONboard, Brumby, Stallion or EasyConnection 8/64 (ISA or EISA) +boards then do: vi /usr/src/linux/drivers/char/istallion.c - find the definition of the stli_brdconf array (of structures) near the top of the file @@ -114,11 +119,11 @@ do a couple of things: configuration files for *all* the EasyIO and EasyConnection 8/32 boards that are sharing interrupts. The Stallion EasyIO and EasyConnection 8/32 EISA configuration files required are supplied by Stallion Technologies - on the EASY Utilities floppy (usually supplied in the box with the board - when purchased. If not, you can pick it up from Stallion's FTP site, - ftp.stallion.com). You will need to edit the board resources to choose - level triggered interrupts, and make sure to set each board's interrupt - to the same IRQ number. + on the EASY Utilities floppy diskette (usually supplied in the box with + the board when purchased. If not, you can pick it up from Stallion's FTP + site, ftp.stallion.com). You will need to edit the board resources to + choose level triggered interrupts, and make sure to set each board's + interrupt to the same IRQ number. You must complete both the above steps for this to work. When you reboot or load the driver your EasyIO and EasyConnection 8/32 boards will be @@ -149,8 +154,8 @@ modules, or change it on the board. On EasyIO and EasyConnection 8/32 boards the IRQ is software programmable, so if there is a conflict you may need to change the IRQ used for a board in the stallion.c configuration structure. There are no interrupts to worry about for ONboard, Brumby or EasyConnection -8/64 boards. The memory region on EasyConnection 8/64 and ONboard boards is -software programmable, but not on the Brumby boards. +8/64 (ISA, EISA and MCA) boards. The memory region on EasyConnection 8/64 and +ONboard boards is software programmable, but not on the Brumby boards. diff --git a/Documentation/transname.txt b/Documentation/transname.txt index ed0a82177..d0a877141 100644 --- a/Documentation/transname.txt +++ b/Documentation/transname.txt @@ -20,7 +20,7 @@ for this task because they have to be valid in the view of mounted filesystems at all clients, not at the server. Linux transname overcomes this problem by allowing filenames -to be context-dependend. For example, if you have a file /etc/config +to be context-dependent. For example, if you have a file /etc/config that should differ on the hosts "myserver" and "myclient", you just create two different files named /etc/config#host=myserver# and /etc/config#host=myclient# . On host "myserver", the file |