diff options
| author | Ralf Baechle <ralf@linux-mips.org> | 2000-01-29 01:41:54 +0000 |
|---|---|---|
| committer | Ralf Baechle <ralf@linux-mips.org> | 2000-01-29 01:41:54 +0000 |
| commit | f969d69ba9f952e5bdd38278e25e26a3e4a61a70 (patch) | |
| tree | b3530d803df59d726afaabebc6626987dee1ca05 /Documentation | |
| parent | a10ce7ef2066b455d69187643ddf2073bfc4db24 (diff) | |
Merge with 2.3.27.
Diffstat (limited to 'Documentation')
41 files changed, 545 insertions, 151 deletions
diff --git a/Documentation/Changes b/Documentation/Changes index a1c994b2a..a883b8d5d 100644 --- a/Documentation/Changes +++ b/Documentation/Changes @@ -45,7 +45,7 @@ running, the suggested command should tell you. - Kernel modutils 2.3.6 ; insmod -V - Gnu C 2.7.2.3 ; gcc --version -- Binutils 2.8.1.0.23 ; ld -v +- Binutils 2.9.1.0.7 ; ld -v - Linux libc5 C Library 5.4.46 ; ls -l /lib/libc* - Linux libc6 C Library 2.0.7pre6 ; ls -l /lib/libc* - Dynamic Linker (ld.so) 1.9.9 ; ldd --version or ldd -v @@ -63,6 +63,7 @@ running, the suggested command should tell you. - Pcmcia-cs 3.1.2 ; cardmgr -V - PPP 2.3.9 ; pppd --version - Util-linux 2.9i ; chsh -v +- isdn4k-utils v3.1beta7 ; isdnctrl 2>&1|grep version Upgrade notes ************* @@ -183,13 +184,10 @@ Binutils to find out the proper way to upgrade it. No, the instruction to "rm `which encaps`" is not a joke. - The last public release of the binutils 2.8.x series was 2.8.1.0.23. -Binutils 2.8.1.0.25 to 2.9.1.0.2 are beta releases, and are known to be -very buggy. Binutils 2.9.1 (note the absence of a suffix) from the FSF -should work, and binutils 2.9.1.0.7 and later releases are also good. -Either use binutils-2.8.1.0.23 or binutils-2.9.1.0.7 or later. Glibc2 -users should especially try to use the 2.9.1.0.x releases, as they -resolve known issues with glibc2 and binutils-2.8.x releases. + You must use binutils 2.9.1.0.7 or later. Latest release is 2.9.1.0.25. +Beware that binutils 2.9.1 (note the absence of a suffix) from the FSF +does not work. If you are upgrading from earlier versions, you should +consider upgrading to the latest 2.9.5.0.x release. Gnu C ===== @@ -248,9 +246,6 @@ modules) are currently distributed separately: see DHCP clients for 2.0 do not work with the new networking code in the 2.2 kernel. You will need to upgrade your dhcpcd / dhcpclient. - The ISDN code in the stock 2.2 kernel may not work for you. If it -doesn't, look in ftp://ftp.suse.com/pub/isdn4linux for updated versions. - In 2.0.x the kernel could be configured to drop source routed IP packets via a compile time configuration option. In 2.2.x, this has been replaced by a sysctl. See Documentation/networking/ip-sysctl.txt @@ -497,29 +492,31 @@ config.h file needs to so be sure to check that when you recompile. +ISDN4Linux +========== +Since 2.3.27 here is a new length of the phonenumber field, old utils +have to recompile, a upgrade to isdn4k-utils.v3.1beta7 or later is +recomented. +Older isdn4k-utils versions don't support EXTRAVERSION into kernel version +string. + + Where to get the files ********************** Binutils ======== -The 2.8.1.0.23 release: -ftp://tsx-11.mit.edu/pub/linux/packages/GCC/binutils-2.8.1.0.23.bin.tar.gz -ftp://metalab.unc.edu/pub/Linux/GCC/binutils-2.8.1.0.23.bin.tar.gz +The 2.9.1.0.25 release: +ftp://ftp.varesearch.com/pub/support/hjl/binutils/2.9.1/binutils-2.9.1.0.25-glibc.x86.tar.gz +ftp://ftp.varesearch.com/pub/support/hjl/binutils/2.9.1/binutils-2.9.1.0.25.tar.gz Installation notes: -ftp://tsx-11.mit.edu/pub/linux/packages/GCC/release.binutils-2.8.1.0.23 -ftp://metalab.unc.edu/pub/Linux/GCC/release.binutils-2.8.1.0.23 - -The 2.9.1.0.15 release: -ftp://tsx-11.mit.edu/pub/linux/packages/GCC/binutils-2.9.1.0.15-glibc.x86.tar.gz -ftp://tsx-11.mit.edu/pub/linux/packages/GCC/binutils-2.9.1.0.15-libc5.x86.tar.gz -ftp://tsx-11.mit.edu/pub/linux/packages/GCC/binutils-2.9.1.0.15.tar.gz -ftp://metalab.unc.edu/pub/Linux/GCC/binutils-2.9.1.0.15-glibc.x86.tar.gz -ftp://metalab.unc.edu/pub/Linux/GCC/binutils-2.9.1.0.15-libc5.x86.tar.gz -ftp://metalab.unc.edu/pub/Linux/GCC/binutils-2.9.1.0.15.tar.gz +ftp://ftp.varesearch.com/pub/support/hjl/binutils/2.9.1/release.binutils-2.9.1.0.25 + +The 2.9.5.0.16 release: +ftp://ftp.varesearch.com/pub/support/hjl/binutils/binutils-2.9.5.0.16.tar.bz2 Installation notes: -ftp://tsx-11.mit.edu/pub/linux/packages/GCC/release.binutils-2.9.1.0.15 -ftp://metalab.unc.edu/pub/Linux/GCC/release.binutils-2.9.1.0.15 +ftp://ftp.varesearch.com/pub/support/hjl/binutils/release.binutils-2.9.5.0.16 Gnu C ===== @@ -785,6 +782,11 @@ Patch The 2.5 release: ftp://ftp.gnu.org/gnu/patch/patch-2.5.tar.gz +ISDN4Linux +========== +The v3.1beta7 release: +ftp://ftp.isdn4linux.de/pub/isdn4linux/utils/testing/isdn4k-utils.v3.1beta7.tar.gz + Other Info ========== diff --git a/Documentation/Configure.help b/Documentation/Configure.help index 1bb6e8607..4de02e1ff 100644 --- a/Documentation/Configure.help +++ b/Documentation/Configure.help @@ -1774,6 +1774,29 @@ CONFIG_HUB6 Say Y here to enable support in the dumb serial driver to support the HUB6 card. +PCMCIA serial device support +CONFIG_PCMCIA_SERIAL_CS + Say Y here to enable support for 16-bit PCMCIA serial devices, + including serial port cards, modems, and the modem functions of + multifunction ethernet/modem cards. + + 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 serial_cs.o. If you want to compile it as a + module, say M here and read Documentation/modules.txt. If unsure, + say N. + +CardBus serial device support +CONFIG_PCMCIA_SERIAL_CB + Say Y here to enable support for CardBus serial devices, including + the modem functions of multifunction ethernet/modem devices. + + 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 serial_cb.o. If you want to compile it as a + module, say M here and read Documentation/modules.txt. If unsure, + say N. + PCI support CONFIG_PCI Find out whether you have a PCI motherboard. PCI is the name of a @@ -2006,6 +2029,23 @@ CONFIG_SYSCTL building a kernel for install/rescue disks or your system is very limited in memory. +Kernel core (/proc/kcore) format +CONFIG_KCORE_ELF + If you enabled support for /proc filesystem then the file /proc/kcore + will contain the kernel core image. This can be used in gdb: + + $ cd /usr/src/linux ; gdb vmlinux /proc/kcore + + Selecting ELF will make /proc/kcore appear in ELF core format as defined + by the Executable and Linking Format specification. Selecting A.OUT will + choose the old "a.out" format which may be necessary for some old versions + of binutils or on some architectures. + + This is especially useful if you have compiled the kernel with "-g" option + to preserve debugging information. It is mainly used for examining kernel + data structures on the live kernel so if you don't understand what this + means or are not a kernel hacker, just leave it at its default value ELF. + Kernel support for ELF binaries CONFIG_BINFMT_ELF ELF (Executable and Linkable Format) is a format for libraries and @@ -3070,7 +3110,7 @@ CONFIG_UNIX here and read Documentation/modules.txt. The module will be called unix.o. If you try building this as a module and you have said Y to "Kernel module loader support" above, be sure to add 'alias net-pf-1 - unix' to your /etc/conf.modules file. Note that several important + unix' to your /etc/modules.conf file. Note that several important services won't work correctly if you say M here and then neglect to load the module. @@ -3794,7 +3834,7 @@ CONFIG_PACKET whenever you want). If you want to compile it as a module, say M here and read Documentation/modules.txt; if you use modprobe or kmod, you may also want to add "alias net-pf-17 af_packet" to - /etc/conf.modules. + /etc/modules.conf. If unsure, say Y. @@ -5684,6 +5724,36 @@ CONFIG_PCMCIA_XIRC2PS module, say M here and read Documentation/modules.txt. If unsure, say N. +3Com 3c575 CardBus support +CONFIG_PCMCIA_3C575 + This driver supports the 3Com 3c575 series of CardBus Fast Ethernet + adapters. + + This driver can only 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 3c575_cb.o. If you want to do that, say M + here and read Documentation/modules.txt. If unsure, say N. + +DEC Tulip CardBus support +CONFIG_PCMCIA_TULIP + This driver supports CardBus Fast Ethernet adapters based on DEC + Tulip and compatible chipsets. + + This driver can only 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 tulip_cb.o. If you want to do that, say M + here and read Documentation/modules.txt. If unsure, say N. + +SMC EPIC CardBus support +CONFIG_PCMCIA_EPIC100 + This driver supports CardBus Fast Ethernet adapters based on the SMC + EPIC chipset. + + This driver can only 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 epic100_cb.o. If you want to do that, say + M here and read Documentation/modules.txt. If unsure, say N. + Aviator/Raytheon 2.4MHz wireless support CONFIG_PCMCIA_RAYCS Say Y here if you intend to attach an Aviator/Raytheon PCMCIA @@ -7935,6 +8005,18 @@ CONFIG_USB_CPIA The module will be called cpia.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. +USB Kodak DC-2xx Camera support +CONFIG_USB_DC2XX + Say Y here if you want to connect this type of still camera to + your computer's USB port. See drivers/usb/README.dc2xx for more + information; some non-Kodak cameras may also work with this + driver, given application support (such as www.gPhoto.org). + + 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 dc2xx.o. If you want to compile it as a + module, say M here and read Documentation/modules.txt. + USB SCSI Support CONFIG_USB_SCSI Say Y here if you want to connect SCSI devices to your computer's @@ -7984,24 +8066,12 @@ CONFIG_USB_PROC Note that you must say Y to "/proc filesystem support" below for this to work. -Generic ACPI support +ACPI support CONFIG_ACPI Advanced Configuration and Power Interface (ACPI) is an interface specification to support power management of peripherals. If your system supports it, say Y here. - 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 acpi.o. If you want to compile it as a - module, say M here and read Documentation/modules.txt. - -PIIX4 ACPI support -CONFIG_PIIX4_ACPI - If you have a PIIX4 based motherboard (PCI ISA IDE Xcelerator - (PIIX4) is a multi-function PCI device) and you want support for - Advanced Configuration and Power Interface (ACPI) to support power - management of peripherals, say Y here. - Minix fs support CONFIG_MINIX_FS Minix is a simple operating system used in many classes about OS's. @@ -8064,6 +8134,23 @@ CONFIG_EXT2_FS compiled as a module, and so this could be dangerous. Most everyone wants to say Y here. +SCO UnixWare BFS Support +CONFIG_BFS_FS + Boot Filesystem (BFS) is a filesystem used under SCO UnixWare to + allow bootloader access the kernel image and other important files + during the boot process. It is usually mounted under /stand and + corresponds to the slice marked as "STAND" in the UnixWare + partition. This is useful if you want to access files on your /stand + slice from Linux. More information on this filesystem can be found in + Documentation/filesystems/bfs.txt file. If you do not know what it is, + 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 bfs.o. Note that the filesystem of your root partition (the + one containing the directory /) cannot be compiled as a module. + ISO 9660 CDROM filesystem support CONFIG_ISO9660_FS This is the standard filesystem used on CDROMs. It was previously @@ -8081,7 +8168,7 @@ CONFIG_ISO9660_FS say M here and read Documentation/modules.txt. The module will be called isofs.o. -Microsoft Joliet cdrom extensions +Microsoft Joliet CDROM extensions CONFIG_JOLIET Joliet is a Microsoft extension for the ISO 9660 CDROM filesystem which allows for long filenames in unicode format (unicode is the @@ -8090,7 +8177,7 @@ CONFIG_JOLIET http://www.unicode.org for more information). Say Y here if you want to be able to read Joliet CDROMs under Linux. -UDF Filesystem support +UDF Filesystem support (read only) CONFIG_UDF_FS This is the new filesystem used by some CDROMS and DVD drivers. Say Y if you intend to mount DVD discs or CDRW's written in packet mode, @@ -8104,13 +8191,13 @@ CONFIG_UDF_FS If unsure, say N. -UDF read-write support (EXPERIMENTAL) +UDF write support (DANGEROUS) CONFIG_UDF_RW Say Y if you want to test write support for UDF filesystems. Due to lack of support for writing to CDR/CDRW's, this option is only supported for Hard Discs, DVD-RAM, and loopback files. -fat fs support +DOS FAT fs support CONFIG_FAT_FS If you want to use one of the FAT-based filesystems (the MS-DOS, VFAT (Windows 95) and UMSDOS (used to run Linux on top of an @@ -8146,7 +8233,7 @@ CONFIG_FAT_FS module, so don't say M here if you intend to use UMSDOS as your root filesystem. -msdos fs support +MSDOS fs support CONFIG_MSDOS_FS This allows you to mount MSDOS partitions of your hard drive (unless they are compressed; to access compressed MSDOS partitions under @@ -8175,7 +8262,7 @@ CONFIG_MSDOS_FS want), say M here and read Documentation/modules.txt. The module will be called msdos.o. -vfat fs support +VFAT (Windows-95) fs support CONFIG_VFAT_FS This option provides support for normal Windows filesystems with long filenames. That includes non-compressed FAT-based filesystems @@ -8196,7 +8283,7 @@ CONFIG_VFAT_FS say M here and read Documentation/modules.txt. The module will be called vfat.o. -umsdos: Unix like fs on top of std MSDOS fs +UMSDOS: Unix-like filesystem on top of standard MSDOS filesystem CONFIG_UMSDOS_FS Say Y here if you want to run Linux from within an existing DOS partition of your hard drive. The advantage of this is that you can @@ -8288,7 +8375,7 @@ CONFIG_ROOT_NFS Most people say N here. -NFS server support +NFS server support (EXPERIMENTAL) CONFIG_NFSD If you want your Linux box to act as a NFS *server*, so that other computers on your local network which support NFS can access certain @@ -8310,7 +8397,7 @@ CONFIG_NFSD The module is called nfsd.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say N. -Emulate Sun NFS daemon +Emulate SUN NFS server CONFIG_NFSD_SUN If you would like for the server to allow clients to access directories that are mount points on the local filesystem (this is @@ -8353,11 +8440,11 @@ CONFIG_NTFS_RW If unsure, say N. -System V and Coherent filesystem support +System V and Coherent filesystem support (read only) CONFIG_SYSV_FS SCO, Xenix and Coherent are commercial Unix systems for Intel - machines. Saying Y here would allow you to read to and write from - their floppies and hard disk partitions. + machines. Saying Y here would allow you to read from their floppies + and hard disk partitions. If you have floppies or hard disk partitions like that, it is likely that they contain binaries from those other Unix systems; in order @@ -8387,6 +8474,15 @@ CONFIG_SYSV_FS If you haven't heard about all of this before, it's safe to say N. +SYSV filesystem write support (DANGEROUS) +CONFIG_SYSV_FS_WRITE + If you say Y here, you will (hopefully) be able to write to System V + and Coherent file systems as well as read from them. The read-write + support in SYSV is not well tested yet. If you enable this, back up + your SYSV/Coherent volumes first since they may get damaged. + + If unsure, say N. + Amiga FFS filesystem support CONFIG_AFFS_FS The Fast File System (FFS) is the common filesystem used on hard @@ -8472,7 +8568,7 @@ CONFIG_AUTOFS_FS If you are not a part of a fairly large, distributed network, you probably do not need an automounter, and can say N here. -EFS filesystem support (EXPERIMENTAL) +EFS filesystem support (read only) (EXPERIMENTAL) CONFIG_EFS_FS EFS is an older filesystem used for non-ISO9660 CDROMs and hard disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer uses @@ -8492,7 +8588,7 @@ CONFIG_SGI_DISKLABEL Say Y to this only if you plan on mounting disks with SGI disklabels. This is not required to mount EFS-format CDROMs. -UFS filesystem support +UFS filesystem support (read only) CONFIG_UFS_FS BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, OpenBSD and NeXTstep) use a filesystem called UFS. Some System V @@ -8522,7 +8618,7 @@ CONFIG_UFS_FS If you haven't heard about all of this before, it's safe to say N. -UFS filesystem write support (EXPERIMENTAL) +UFS filesystem write support (DANGEROUS) CONFIG_UFS_FS_WRITE Say Y here if you want to try writing to UFS partitions. This is experimental, so you should back up your UFS partitions beforehand. @@ -8642,7 +8738,7 @@ CONFIG_UNIXWARE_DISKLABEL If you don't know what all this is about, say N. -SMB filesystem support (to mount Windows shares etc...) +SMB filesystem support (to mount Windows shares etc.) CONFIG_SMB_FS SMB (Server Message Block) is the protocol Windows for Workgroups (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share @@ -8668,7 +8764,7 @@ CONFIG_SMB_FS want), say M here and read Documentation/modules.txt. The module will be called smbfs.o. Most people say N, however. -Coda filesystem support +Coda filesystem support (advanced network fs) CONFIG_CODA_FS Coda is an advanced network filesystem, similar to NFS in that it enables you to mount filesystems of a remote server and access them @@ -9975,7 +10071,7 @@ CONFIG_MTRR lead to all sorts of problems. You can safely say Y even if your machine doesn't have MTRRs, you'll - just add about 3k to your kernel. + just add about 9K to your kernel. See Documentation/mtrr.txt for more information. @@ -10032,9 +10128,15 @@ CONFIG_APM APM is a BIOS specification for saving power using several different techniques. This is mostly useful for battery powered laptops with APM compliant BIOSes. If you say Y here, the system time will be - reset after a 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). + reset after a 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). + + If you select "Y" here, you can disable actual use of the APM + BIOS by passing the "apm=off" option to the kernel at boot time. + + Note that the APM support is almost completely disabled for + machines with more than one CPU. Supporting software is available; for more information, read the Battery Powered Linux mini-HOWTO, available from @@ -10047,9 +10149,7 @@ CONFIG_APM 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). + may cause those machines to panic during the boot phase. If you are running Linux on a laptop, you may also want to read the Linux Laptop home page on the WWW at @@ -12760,13 +12860,6 @@ CONFIG_NSC_FIR the ACTiSYS IR2000B ISA card and supports SIR, MIR and FIR (4Mbps) speeds. -Sharp UIRCC IrDA Device Driver -CONFIG_SHARP_FIR - Say Y here if you want to build support for the Sharp UIRCC IrDA - chipset. If you want to compile it as a module, say M here and - read Documentation/modules.txt. This chipset is used by the Toshiba - Tecra laptops. - Toshiba Type-O IR Port Device Driver CONFIG_TOSHIBA_FIR Say Y here if you want to build support for the Toshiba Type-O IR @@ -13134,7 +13227,7 @@ CONFIG_KHTTPD # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SKTR SNA -# LocalWords: SysKonnect sktr sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX +# LocalWords: SysKonnect tms380tr sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs diff --git a/Documentation/acpi.txt b/Documentation/acpi.txt new file mode 100644 index 000000000..9629eb29e --- /dev/null +++ b/Documentation/acpi.txt @@ -0,0 +1,125 @@ +ACPI Driver Interface +--------------------- + +Overview: +1) Register each instance of a device with "acpi_register" +2) Call "acpi_access" before accessing the hardware. + (this will ensure that the hardware is awake and ready) +3) "acpi_transition" callback is called before entering D1-D3 + or after entering D0 +4) Call "acpi_dev_idle" when the device is not being used + (not required by will improve idle detection) +5) When unloaded, unregister the device with "acpi_unregister" + +/* + * Description: Register a device with the ACPI subsystem + * + * Parameters: + * info - static device information + * type - device type + * hid - PnP identifier (or 0 if unknown) + * trans - device state transition callback + * adr - bus number and address or unique id + * + * Returns: Registered ACPI device or NULL on error + * + * Details: The device type, bus number, and bus address should be + * enough information to reconstruct the device tree and + * identify device dependencies + * + * Examples: + * struct acpi_dev_info info = {ACPI_SYS_DEV, ACPI_VGA_HID, vga_trans}; + * dev = acpi_register(&info, 0); + * + * struct pci_dev *pci_dev = pci_find_dev(...); + * struct acpi_dev_info info = {ACPI_PCI_DEV, 0, trans}; + * dev = acpi_register(&info, ACPI_PCI_ADR(pci_dev)); + */ +struct acpi_dev *acpi_register(struct acpi_dev_info *info, unsigned long adr); + +/* + * Description: Unregister a device with ACPI + * + * Parameters: + * dev - ACPI device previously returned from acpi_register + */ +void acpi_unregister(struct acpi_dev *dev); + +/* + * Device idle/use detection + * + * In general, drivers for all devices should call "acpi_access" + * before accessing the hardware (ie. before reading or modifying + * a hardware register). Request or packet-driven drivers should + * additionally call "acpi_idle" when a device is not being used. + * + * Examples: + * 1) A keyboard driver would call acpi_access whenever a key is pressed + * 2) A network driver would call acpi_access before submitting + * a packet for transmit or receive and acpi_idle when its + * transfer and receive queues are empty. + * 3) A VGA driver would call acpi_access before it accesses any + * of the video controller registers + * + * Ultimately, the ACPI policy manager uses the access and idle + * information to decide when to transition devices between + * device states. + */ + +/* + * Description: Update device access time and wake up device, if necessary + * + * Parameters: + * dev - ACPI device previously returned from acpi_register + * + * Details: If called from an interrupt handler acpi_access updates + * access time but should never need to wake up the device + * (if device is generating interrupts, it should be awake + * already) This is important as we can not wake up + * devices (run AML, etc.) from an interrupt handler. + */ +void acpi_access(struct acpi_dev *dev); + +/* + * Description: Identify device as currently being idle + * + * Parameters: + * dev - ACPI device previously returned from acpi_register + * + * Details: A call to acpi_idle might signal to the policy manager + * to put a device to sleep. If a new device request arrives + * between the call to acpi_idle and the acpi_transition + * callback, the driver should fail the acpi_transition request. + */ +void acpi_dev_idle(struct acpi_dev *dev); + +/* + * Transition function + * + * Parameters: + * dev - ACPI device previously returned from acpi_register + * state - the device state being entered + * + * Returns: 0 if the state transition is possible and context saved + * EINVAL if the requested device state is not supported + * EBUSY if the device is now busy and can not transition + * ENOMEM if the device was unable to save context (out of memory) + * + * Details: The device state transition function will be called + * before the device is transitioned into the D1-D3 states + * or after the device is transitioned into the D0 state. + * The device driver should save (D1-D3) or restore (D0) + * device context when the transition function is called. + * + * For system devices, the ACPI subsystem will perform + * the actual hardware state transition itself. For bus + * devices, after the driver's acpi_transition function + * is called, the bus driver's acpi_transition function + * is called to perform the actual hardware state transition. + * + * Once a driver returns 0 (success) from a transition + * to D1-3 request, it should not process any further + * requests or access the device hardware until a + * call to "acpi_access" is made. + */ +typedef int (*acpi_transition)(struct acpi_dev *dev, acpi_dstate_t state); diff --git a/Documentation/computone.txt b/Documentation/computone.txt index c1577ec21..9d39a878a 100644 --- a/Documentation/computone.txt +++ b/Documentation/computone.txt @@ -59,7 +59,7 @@ d) Run "make config" or "make menuconfig" or "make xconfig" e) Set address on ISA cards then: edit /usr/src/linux/drivers/char/ip2/ip2.h if needed or - edit /etc/conf.modules (or /etc/modules.conf) if needed (module). + edit /etc/modules.conf if needed (module). or both to match this setting. f) Run "make dep" g) Run "make modules" diff --git a/Documentation/digiboard.txt b/Documentation/digiboard.txt index cb63042c2..eee81a0cf 100644 --- a/Documentation/digiboard.txt +++ b/Documentation/digiboard.txt @@ -29,7 +29,7 @@ The driver can be built direct into the kernel or as a module. The pcxx driver can be configured using the command line feature while loading the kernel with LILO or LOADLIN or, if built as a module, with arguments to insmod and modprobe or with parameters in -/etc/conf.modules for modprobe and kerneld. +/etc/modules.conf for modprobe and kerneld. After configuring the driver you need to create the device special files as described in "Device file creation:" below and set the appropriate @@ -96,13 +96,13 @@ devices following that board, you can empty the io-value for that board: The remaining board still uses ttyD8-ttyD15 and cud8-cud15. -Example line for /etc/conf.modules for use with kerneld and as default +Example line for /etc/modules.conf for use with kerneld and as default parameters for modprobe: options pcxx io=0x200 numports=8 For kerneld to work you will likely need to add these two lines to your -/etc/conf.modules: +/etc/modules.conf: alias char-major-22 pcxx alias char-major-23 pcxx diff --git a/Documentation/filesystems/00-INDEX b/Documentation/filesystems/00-INDEX index b481c8a67..b4ffac022 100644 --- a/Documentation/filesystems/00-INDEX +++ b/Documentation/filesystems/00-INDEX @@ -4,6 +4,8 @@ adfs.txt - info and mount options for the Acorn Advanced Disc Filing System. affs.txt - info and mount options for the Amiga Fast File System. +bfs.txt + - info for the SCO UnixWare Boot Filesystem (BFS). coda.txt - description of the CODA filesystem. fat_cvf.txt diff --git a/Documentation/filesystems/bfs.txt b/Documentation/filesystems/bfs.txt new file mode 100644 index 000000000..a6179cad9 --- /dev/null +++ b/Documentation/filesystems/bfs.txt @@ -0,0 +1,59 @@ +The BFS filesystem is used on SCO UnixWare machines for /stand slice. +By default, if you attempt to mount it read-write it will be automatically +mounted read-only. If you want to enable (limited) write support, you need +to select "BFS write support" when configuring the kernel. The write support +at this stage is limited to the blocks preallocated for a given inode. +This means that writes beyond the value of inode->iu_eblock will fail with EIO. +In particular, this means you can create empty files but not write data to them +or you can write data to the existing files and increase their size but not the +number of blocks allocated to them. I am currently working on removing this +limitation, i.e. ability to migrate inodes within BFS filesystem. + +In order to access /stand partition under Linux you obviously need to +know the partition number and the kernel must support UnixWare disk slices +(CONFIG_UNIXWARE_DISKLABEL config option). However BFS support does not +depend on having UnixWare disklabel support because one can also mount +BFS filesystem via loopback: + +# losetup /dev/loop0 stand.img +# mount -t bfs /dev/loop0 /mnt/stand + +where stand.img is a file containing the image of BFS filesystem. +When you have finished using it and umounted you need to also deallocate +/dev/loop0 device by: + +# losetup -d /dev/loop0 + +You can simplify mounting by just typing: + +# mount -t bfs -o loop stand.img /mnt/stand + +this will allocate the first available loopback device (and load loop.o +kernel module if necessary) automatically. Beware that umount will not +deallocate /dev/loopN device if /etc/mtab file on your system is a +symbolic link to /proc/mounts. You will need to do it manually using +"-d" switch of losetup(8). Read losetup(8) manpage for more info. + +To create the BFS image under UnixWare you need to find out first which +slice contains it. The command prtvtoc(1M) is your friend: + +# prtvtoc /dev/rdsk/c0b0t0d0s0 + +(assuming your root disk is on target=0, lun=0, bus=0, controller=0). Then you +look for the slice with tag "STAND", which is usually slice 10. With this +information you can use dd(1) to create the BFS image: + +# umount /stand +# dd if=/dev/rdsk/c0b0t0d0sa of=stand.img bs=512 + +Just in case, you can verify that you have done the right thing by checking +the magic number: + +# od -Ad -tx4 stand.img | more + +The first 4 bytes should be 0x1BADFACE. + +If you have any questions or suggestions regarding this BFS implementation +please contact me: + +Tigran A. Aivazian <tigran@ocston.org>. diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt index a17c05b0f..fef3bb743 100644 --- a/Documentation/filesystems/proc.txt +++ b/Documentation/filesystems/proc.txt @@ -190,7 +190,7 @@ Table 1-3: Kernel info in /proc ide Directory containing info about the IDE subsystem interrupts Interrupt usage ioports I/O port usage - kcore Kernel core image + kcore Kernel core image (can be ELF or A.OUT) kmsg Kernel messages ksyms Kernel symbol table loadavg Load average diff --git a/Documentation/ftape.txt b/Documentation/ftape.txt index 7de46c2e0..525df9f89 100644 --- a/Documentation/ftape.txt +++ b/Documentation/ftape.txt @@ -244,14 +244,14 @@ C. Boot and load time configuration insmod ftape.o ft_tracing=4 - or by editing the file `/etc/conf.modules' in which case they take + or by editing the file `/etc/modules.conf' in which case they take effect each time when the module is loaded with `modprobe' (please refer to the modules documentation, i.e. `modules.txt' and the respective manual pages). Thus, you should add a line options ftape ft_tracing=4 - to `/etc/conf.modules` if you intend to increase the debugging + to `/etc/modules.conf` if you intend to increase the debugging output of the driver. @@ -299,7 +299,7 @@ C. Boot and load time configuration 5. Example module parameter setting ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To do the same, but with ftape compiled as a loadable kernel - module, add the following line to `/etc/conf.modules': + module, add the following line to `/etc/modules.conf': options ftape ft_probe_fc10=1 ft_tracing=4 diff --git a/Documentation/hayes-esp.txt b/Documentation/hayes-esp.txt index e0a570185..85885da94 100644 --- a/Documentation/hayes-esp.txt +++ b/Documentation/hayes-esp.txt @@ -109,7 +109,7 @@ option with a space. For example: insmod esp dma=3 trigger=512 The esp module can be automatically loaded when needed. To cause this to -happen, add the following lines to /etc/conf.modules (replacing the last line +happen, add the following lines to /etc/modules.conf (replacing the last line with options for your configuration): alias char-major-57 esp diff --git a/Documentation/ide.txt b/Documentation/ide.txt index 866a3a909..df417541d 100644 --- a/Documentation/ide.txt +++ b/Documentation/ide.txt @@ -245,7 +245,7 @@ When using ide.c/ide-tape.c as modules in combination with kerneld, add: alias block-major-3 ide-probe alias char-major-37 ide-tape -respectively to /etc/conf.modules. +respectively to /etc/modules.conf. When ide.c is used as a module, you can pass command line parameters to the driver using the "options=" keyword to insmod, while replacing any ',' with diff --git a/Documentation/isdn/00-INDEX b/Documentation/isdn/00-INDEX index 919af9057..b7161af1a 100644 --- a/Documentation/isdn/00-INDEX +++ b/Documentation/isdn/00-INDEX @@ -6,12 +6,18 @@ INTERFACE - description of Linklevel and Hardwarelevel ISDN interface. README - general info on what you need and what to do for Linux ISDN. +README.FAQ + - general info for FAQ. README.audio - info for running audio over ISDN. +README.fax + - info for using Fax over ISDN. README.icn - info on the ICN-ISDN-card and its driver. README.HiSax - info on the HiSax driver which replaces the old teles. +README.hfc-pci + - info on hfc-pci based cards. README.pcbit - info on the PCBIT-D ISDN adapter and driver. README.syncppp @@ -22,8 +28,12 @@ README.avmb1 - info on driver for AVM-B1 ISDN card. README.act2000 - info on driver for IBM ACT-2000 card. +README.eicon + - info on driver for Eicon active cards. README.concap - info on "CONCAP" ecapsulation protocol interface used for X.25. +README.diversion + - info on module for isdn diversion services. README.sc - info on driver for Spellcaster cards. README.x25 diff --git a/Documentation/isdn/CREDITS b/Documentation/isdn/CREDITS index 31da77e3b..beef990ba 100644 --- a/Documentation/isdn/CREDITS +++ b/Documentation/isdn/CREDITS @@ -15,8 +15,11 @@ Volker Götz (volker@oops.franken.de) For contribution of man-pages, the imontty-tool and a perfect maintaining of the mailing-list at hub-wue. +Matthias Hessler (hessler@isdn4linux.de) + For creating and maintaining the FAQ. + Bernhard Hailer (Bernhard.Hailer@lrz.uni-muenchen.de) - For maintaining the FAQ. + For creating the FAQ, and the leafsite HOWTO. Michael 'Ghandi' Herold (michael@abadonna.franken.de) For contribution of the vbox answering machine. diff --git a/Documentation/isdn/README b/Documentation/isdn/README index dcd14151e..3cf623d48 100644 --- a/Documentation/isdn/README +++ b/Documentation/isdn/README @@ -11,7 +11,7 @@ README for the ISDN-subsystem necessary. Those programs and some contributed utilities are available at - ftp.franken.de + ftp.isdn4linux.de /pub/isdn4linux/isdn4k-utils-<VersionNumber>.tar.gz @@ -22,19 +22,23 @@ README for the ISDN-subsystem reasons, the mailing-list's primary language is german. However mails written in english have been welcome all the time. - to subscribe: write a email to majordomo@hub-wue.franken.de, + to subscribe: write a email to majordomo@listserv.isdn4linux.de, Subject irrelevant, in the message body: subscribe isdn4linux <your_email_address> - To write to the mailing-list, write to isdn4linux@hub-wue.franken.de + To write to the mailing-list, write to isdn4linux@listserv.isdn4linux.de This mailinglist is bidirectionally gated to the newsgroup de.alt.comm.isdn4linux - There is also a well maintained FAQ (both english and german) available - at ftp.franken.de in /pub/isdn4linux/FAQ/ - This FAQ is also available at http://www.lrz-muenchen.de/~ui161ab/www/isdn/ + There is also a well maintained FAQ in English available at + http://www.mhessler.de/i4lfaq/ + It can be viewed online, or downloaded in sgml/text/html format. + The FAQ can also be viewed online at + http://www.isdn4inux.de/faq/ + or downloaded from + ftp://ftp.isdn4linux.de/pub/isdn4linux/FAQ/ 1.1 Technical details @@ -266,6 +270,8 @@ README for the ISDN-subsystem 23 0 Bit coded register: Bit 0: 0 = Add CPN to RING message off 1 = Add CPN to RING message on + Bit 1: 0 = Add CPN to FCON message off + 1 = Add CPN to FCON message on Last but not least a (at the moment fairly primitive) device to request the line-status (/dev/isdninfo) is made available. @@ -581,7 +587,7 @@ README for the ISDN-subsystem If other drivers will not be affected, I will include the changes in the next release. For developers only, there is a second mailing-list. Write to me - (fritz@wuemaus.franken.de), if you want to join that list. + (fritz@isdn4linux.de), if you want to join that list. Have fun! diff --git a/Documentation/isdn/README.FAQ b/Documentation/isdn/README.FAQ new file mode 100644 index 000000000..356f79446 --- /dev/null +++ b/Documentation/isdn/README.FAQ @@ -0,0 +1,26 @@ + +The FAQ for isdn4linux +====================== + +Please note that there is a big FAQ available in the isdn4k-utils. +You find it in: + isdn4k-utils/FAQ/i4lfaq.sgml + +In case you just want to see the FAQ online, or download the newest version, +you can have a look at my website: +http://www.mhessler.de/i4lfaq/ (view + download) +or: +http://www.isdn4linux.de/faq/ (view) + +As the extension tells, the FAQ is in SGML format, and you can convert it +into text/html/... format by using the sgml2txt/sgml2html/... tools. +Alternatively, you can also do a 'configure; make all' in the FAQ directory. + + +Please have a look at the FAQ before posting anything in the Mailinglist, +or the newsgroup! + + +Matthias Hessler +hessler@isdn4linux.de + diff --git a/Documentation/isdn/README.HiSax b/Documentation/isdn/README.HiSax index 7faff4a34..ee95d85f4 100644 --- a/Documentation/isdn/README.HiSax +++ b/Documentation/isdn/README.HiSax @@ -63,6 +63,7 @@ Berkom Telekom A4T Scitel Quadro Gazel ISDN cards HFC-PCI based cards +Winbond W6692 based cards Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet @@ -182,6 +183,7 @@ Card types: 34 Gazel ISDN cards (ISA) irq,io 34 Gazel ISDN cards (PCI) none 35 HFC 2BDS0 PCI none + 36 W6692 based PCI cards none At the moment IRQ sharing is only possible with PCI cards. Please make sure @@ -285,6 +287,7 @@ type 34 Gazel ISDN cards (ISA) pa=irq, pb=io 34 Gazel ISDN cards (PCI) no parameter 35 HFC 2BDS0 PCI no parameter + 36 W6692 based PCI cards none Running the driver ------------------ @@ -425,6 +428,7 @@ Special thanks to: Klaus Lichtenwalder (Klaus.Lichtenwalder@WebForum.DE), for ELSA PCMCIA support Enrik Berkhan (enrik@starfleet.inka.de) for S0BOX specific stuff Ton van Rosmalen for Teles PCI + Petr Novak <petr.novak@i.cz> for Winbond W6692 support and more people who are hunting bugs. (If I forgot somebody, please send me a mail). diff --git a/Documentation/isdn/README.avmb1 b/Documentation/isdn/README.avmb1 index 34eee2125..6fa9406df 100644 --- a/Documentation/isdn/README.avmb1 +++ b/Documentation/isdn/README.avmb1 @@ -169,7 +169,7 @@ capi20 Questions --------- -Check out the FAQ (ftp.franken.de) or subscribe to the +Check out the FAQ (ftp.isdn4linux.de) or subscribe to the linux-avmb1@calle.in-berlin.de mailing list by sending a mail to majordomo@calle.in-berlin.de with subscribe linux-avmb1 diff --git a/Documentation/isdn/README.eicon b/Documentation/isdn/README.eicon index d55cc14ad..b40e1ecd2 100644 --- a/Documentation/isdn/README.eicon +++ b/Documentation/isdn/README.eicon @@ -1,6 +1,6 @@ -$Id: README.eicon,v 1.4 1999/07/11 17:17:30 armin Exp $ +$Id: README.eicon,v 1.5 1999/10/11 18:13:25 armin Exp $ -(c) 1999 Cytronics & Melware +(c) 1999 Cytronics & Melware (info@melware.de) This document describes the eicon driver for the Eicon.Diehl active ISDN cards. @@ -24,17 +24,26 @@ It is meant to be used with isdn4linux, an ISDN link-level module for Linux. Supported Cards ---------------- +=============== +Old ISA type +------------ - S-Card ISA - SX-Card ISA - SXn-Card ISA - SCOM-Card ISA - Quadro-Card ISA - S2M-Card ISA + +DIVA Server family +------------------ - DIVA Server BRI/PCI 2M - DIVA Server PRI/PCI 2M (9M 23M 30M) - (Only analog modem functions of the DSPs are currently implemented) + supported functions of onboard DSPs: + - analog modem + - fax group 2/3 (Fax Class 2 commands) + - DTMF detection + ISDN D-Channel Protocols ------------------------ @@ -76,6 +85,10 @@ Example for loading and starting a PRI card with E-DSS1 Protocol. Details about using the eiconctrl utility are in 'man eiconctrl' or will be printed by starting eiconctrl without any parameters. +Thanks to + Deutsche Mailbox Saar-Lor-Lux GmbH + for sponsoring and testing fax + capabilities with Diva Server cards. Any reports about bugs, errors and even wishes are welcome. diff --git a/Documentation/isdn/README.fax b/Documentation/isdn/README.fax index 897abd0ef..eeff9ce9f 100644 --- a/Documentation/isdn/README.fax +++ b/Documentation/isdn/README.fax @@ -9,7 +9,7 @@ This only makes sense under the following conditions : - You need the commands as dummy, because you are using hylafax (with patch) for AVM capi. -- You want to use the fax capabillities of your isdn-card. +- You want to use the fax capabilities of your isdn-card. (supported cards are listed below) @@ -21,8 +21,12 @@ NOTE: This implementation does *not* support fax with passive Supported ISDN-Cards -------------------- -Eicon DIVA Server BRI/PCI (will be ready soon) -Eicon DIVA Server PRI/PCI (will be ready soon) +Eicon DIVA Server BRI/PCI + - full support with both B-channels. + +Eicon DIVA Server PRI/PCI + - full support on amount of B-channels + depending on DSPs on board. diff --git a/Documentation/isdn/README.hfc-pci b/Documentation/isdn/README.hfc-pci index 94e0d4352..6cc311e35 100644 --- a/Documentation/isdn/README.hfc-pci +++ b/Documentation/isdn/README.hfc-pci @@ -20,6 +20,21 @@ This enables the echo mode. If Hex logging is activated the isdnctrlx devices show a output with a line beginning of HEX: for the providers exchange and ECHO: for isdn devices sending to the provider. +If more than one HFC-PCI cards are installed, a specific card may be selected +at the hisax module load command line. Supply the load command with the desired +IO-address of the desired card. +Example: +There tree cards installed in your machine at IO-base addresses 0xd000, 0xd400 +and 0xdc00 +If you want to use the card at 0xd400 standalone you should supply the insmod +or depmod with type=35 io=0xd400. +If you want to use all three cards, but the order needs to be at 0xdc00,0xd400, +0xd000 you may give the parameters type=35,35,35 io=0xdc00,0xd400,0xd00 +Then the desired card will be the initialised in the desired order. +If the io parameter is used the io addresses of all used cards should be +supplied else the parameter is assumed 0 and a auto search for a free card is +invoked which may not give the wanted result. + Comments and reports to werner@isdn4linux.de or werner@titro.de . diff --git a/Documentation/isdn/README.pcbit b/Documentation/isdn/README.pcbit index fb696422f..512500228 100644 --- a/Documentation/isdn/README.pcbit +++ b/Documentation/isdn/README.pcbit @@ -32,7 +32,7 @@ allow normal operation. Plans for the future include cooperation with the manufacturer in order to solve this problem. Information/hints/help can be obtained in the linux isdn -mailing list (isdn4linux@hub-wue.franken.de) or directly from me. +mailing list (isdn4linux@listserv.isdn4linux.de) or directly from me. regards, Pedro. diff --git a/Documentation/joystick-parport.txt b/Documentation/joystick-parport.txt index 6bf2cd9c2..880150b9e 100644 --- a/Documentation/joystick-parport.txt +++ b/Documentation/joystick-parport.txt @@ -1,5 +1,5 @@ Linux Joystick parport drivers v1.2 BETA - (c) 1998 Vojtech Pavlik <vojtech@ucw.cz> + (c) 1998 Vojtech Pavlik <vojtech@suse.cz> (c) 1998 Andree Borrmann <a.borrmann@tu-bs.de> ---------------------------------------------------------------------------- diff --git a/Documentation/joystick.txt b/Documentation/joystick.txt index 9e3a2320a..ab8a454a2 100644 --- a/Documentation/joystick.txt +++ b/Documentation/joystick.txt @@ -1,5 +1,5 @@ Linux Joystick driver v1.2.13 - (c) 1996-1998 Vojtech Pavlik <vojtech@ucw.cz> + (c) 1996-1998 Vojtech Pavlik <vojtech@suse.cz> ---------------------------------------------------------------------------- 0. Disclaimer @@ -19,7 +19,7 @@ with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Should you need to contact me, the author, you can do so either by e-mail -- mail your message to <vojtech@ucw.cz>, or by paper mail: Vojtech Pavlik, +- mail your message to <vojtech@suse.cz>, or by paper mail: Vojtech Pavlik, Ucitelska 1576, Prague 8, 182 00 Czech Republic For your convenience, the GNU General Public License version 2 is included @@ -58,20 +58,20 @@ them. Bug reports and success stories are also welcome. The joystick package is available at the following FTP sites: ftp://atrey.karlin.mff.cuni.cz/pub/linux/joystick/ - ftp://artax.karlin.mff.cuni.cz/pub/linux/joystick/ - The joystick driver is also included in the Linux 2.1 kernels: + The joystick driver is also included in the Linux 2.1+ kernels: - ftp://linux.kernel.org/pub/linux/kernel/v2.1/ + ftp://linux.kernel.org/pub/linux/kernel/ And a homepage of the driver is at: - http://atrey.karlin.mff.cuni.cz/~vojtech/joystick/ - http://artax.karlin.mff.cuni.cz/~vojtech/joystick/ + http://www.suse.cz/development/joystick/ - A mirror of the homepage is at: + Mirrors of the homepage are at: + http://atrey.karlin.mff.cuni.cz/~vojtech/joystick/ http://www.trylinux.com/projects/joystick/ + http://www.linuxgames.com/joystick/ There is also a mailing list for the driver at: diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index dc57ee651..e88c7c150 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -11,7 +11,7 @@ restrictions on the kernel for the said kernel parameter to be valid. The restrictions referred to are that the relevant option is valid if: APIC APIC support is enabled. - APM Automatic Power Management support is enabled. + APM Advanced Power Management support is enabled. AX25 Appropriate AX.25 support is enabled. CD Appropriate CD support is enabled. EIDE EIDE/ATAPI support is enabled. @@ -20,6 +20,7 @@ restrictions referred to are that the relevant option is valid if: ISDN Appropriate ISDN support is enabled. JOY Appropriate joystick support is enabled. LP Printer support is enabled. + LOOP Loopback device support is enabled. MCA MCA bus support is enabled. MDA The MDA console is enabled. MOUSE Appropriate mouse support is enabled. @@ -65,7 +66,7 @@ running once the system is up. AM53C974= [HW,SCSI] - apm= [APM] Automatic Power Management. + apm= [APM] Advanced Power Management. arcrimi= [HW,NET] @@ -208,6 +209,9 @@ or lp=auto driver. 'lp=reset' (which can be specified in mac5380= [HW,SCSI] + max_loop=[0-255] [LOOP] States the maximum number of loopback devices + that can be mounted. + maxcpus= [SMP] States the maximum number of processors that an SMP kernel should make use of. diff --git a/Documentation/modules.txt b/Documentation/modules.txt index cf8b42214..e7e371945 100644 --- a/Documentation/modules.txt +++ b/Documentation/modules.txt @@ -117,7 +117,7 @@ Using the modprobe utility, you can load any module like this: without paying much attention to which kernel you are running, or what other modules this module depends on. -With the help of the modprobe configuration file: "/etc/conf.modules" +With the help of the modprobe configuration file: "/etc/modules.conf" you can tune the behaviour of modprobe in many ways, including an automatic setting of insmod options for each module. And, yes, there _are_ man-pages for all this... @@ -164,10 +164,10 @@ This is what happens: fits this symbolic description. - modprobe looks into its internal "alias" translation table to see if there is a match. This table can be reconfigured - and expanded by having "alias" lines in "/etc/conf.modules". + and expanded by having "alias" lines in "/etc/modules.conf". - insmod is then asked to insert the module(s) that modprobe has decided that the kernel needs. Every module will be - configured according to the "options" lines in "/etc/conf.modules". + configured according to the "options" lines in "/etc/modules.conf". - modprobe exits and kerneld tells the kernel that the request succeeded (or failed...) - The kernel uses the freshly installed feature just as if it @@ -191,7 +191,7 @@ for maintainers of distributions. To use kerneld with the least amount of "hassle", you need modprobe from a release that can be considered "recent" w.r.t. your kernel, and also -a configuration file for modprobe ("/etc/conf.modules"). +a configuration file for modprobe ("/etc/modules.conf"). Since modprobe already knows about most modules, the minimal configuration file could look something like this: @@ -208,10 +208,6 @@ You could add these lines as well, but they are only "cosmetic": alias net-pf-4 off # if you don't use the ipx module alias net-pf-5 off # if you don't use the appletalk module -Finally, for the "purists": -You can name the modprobe configuration either "/etc/conf.modules" or -"/etc/modules.conf", since modprobe knows what to do in each case... - Written by: Jacques Gelinas <jacques@solucorp.qc.ca> diff --git a/Documentation/networking/arcnet-hardware.txt b/Documentation/networking/arcnet-hardware.txt index 638bb8abf..b84cdc4d6 100644 --- a/Documentation/networking/arcnet-hardware.txt +++ b/Documentation/networking/arcnet-hardware.txt @@ -78,7 +78,7 @@ CABLING ARCNET NETWORKS ----------------------- This section was rewritten by - Vojtech Pavlik <Vojtech.Pavlik@st.mff.cuni.cz> + Vojtech Pavlik <vojtech@suse.cz> using information from several people, including: Avery Pennraun <apenwarr@worldvisions.ca> Stephen A. Wood <saw@hallc1.cebaf.gov> @@ -270,7 +270,7 @@ All ARCnet cards should have a total of four or five different settings: that IRQ2 is the same as IRQ9, as far as Linux is concerned. You can "cat /proc/interrupts" for a somewhat complete list of which ones are in use at any given time. Here is a list of common usages from Vojtech - Pavlik <Vojtech.Pavlik@st.mff.cuni.cz>: + Pavlik <vojtech@suse.cz>: ("Not on bus" means there is no way for a card to generate this interrupt) IRQ 0 - Timer 0 (Not on bus) @@ -347,8 +347,7 @@ All ARCnet cards should have a total of four or five different settings: network. Also, on many cards (not mine, though) there are red and green LED's. -Vojtech Pavlik <Vojtech.Pavlik@st.mff.cuni.cz> tells me this is what they -mean: +Vojtech Pavlik <vojtech@suse.cz> tells me this is what they mean: GREEN RED Status ----- --- ------ OFF OFF Power off @@ -1735,11 +1734,11 @@ JP 6 : IRQ set (ONLY ONE jumper on 1-5 for IRQ 2-6) ** Acer ** 8-bit card, Model 5210-003 -------------------------- - - from Vojtech Pavlik <Vojtech.Pavlik@st.mff.cuni.cz> using portions of - the existing arcnet-hardware file. + - from Vojtech Pavlik <vojtech@suse.cz> using portions of the existing + arcnet-hardware file. -This is a 90C26 based card. Its configuration seems similar to -the SMC PC100, but has some additional jumpers I don't know. +This is a 90C26 based card. Its configuration seems similar to the SMC +PC100, but has some additional jumpers I don't know the meaning of. __ | | @@ -1903,7 +1902,7 @@ guess the purpose. ** Datapoint? ** LAN-ARC-8, an 8-bit card ------------------------ - - from Vojtech Pavlik <Vojtech.Pavlik@st.mff.cuni.cz> + - from Vojtech Pavlik <vojtech@suse.cz> This is another SMC 90C65-based ARCnet card. I couldn't identify the manufacturer, but it might be DataPoint, because the card has the @@ -2043,7 +2042,7 @@ parameters. These two switches are normally left in the OFF position. ** Topware ** 8-bit card, TA-ARC/10 ------------------------- - - from Vojtech Pavlik <Vojtech.Pavlik@st.mff.cuni.cz> + - from Vojtech Pavlik <vojtech@suse.cz> This is another very similar 90C65 card. Most of the switches and jumpers are the same as on other clones. @@ -2752,7 +2751,7 @@ Setting the Timeouts ** No Name ** 8-bit cards ("Made in Taiwan R.O.C.") ----------- - - from Vojtech Pavlik <Vojtech.Pavlik@st.mff.cuni.cz> + - from Vojtech Pavlik <vojtech@suse.cz> I have named this ARCnet card "NONAME", since I got only the card with no manual at all and the only text identifying the manufacturer is diff --git a/Documentation/networking/baycom.txt b/Documentation/networking/baycom.txt index 71e0c76df..b9d58fe2f 100644 --- a/Documentation/networking/baycom.txt +++ b/Documentation/networking/baycom.txt @@ -93,7 +93,7 @@ Every time a driver is inserted into the kernel, it has to know which modems it should access at which ports. This can be done with the setbaycom utility. If you are only using one modem, you can also configure the driver from the insmod command line (or by means of an option line in -/etc/conf.modules). +/etc/modules.conf). Examples: insmod baycom_ser_fdx mode="ser12*" iobase=0x3f8 irq=4 diff --git a/Documentation/networking/ltpc.txt b/Documentation/networking/ltpc.txt index ed9983f07..b93585b95 100644 --- a/Documentation/networking/ltpc.txt +++ b/Documentation/networking/ltpc.txt @@ -25,7 +25,7 @@ the driver will try to determine them itself. If you load the driver as a module, you can pass the parameters "io=", "irq=", and "dma=" on the command line with insmod or modprobe, or add -them as options in /etc/conf.modules: +them as options in /etc/modules.conf: alias lt0 ltpc # autoload the module when the interface is configured options ltpc io=0x240 irq=9 dma=1 diff --git a/Documentation/networking/soundmodem.txt b/Documentation/networking/soundmodem.txt index 202101d18..f6d49e9af 100644 --- a/Documentation/networking/soundmodem.txt +++ b/Documentation/networking/soundmodem.txt @@ -39,7 +39,7 @@ Every time the driver is inserted into the kernel, it has to know which modems it should access at which ports. This can be done with the setbaycom utility. If you are only using one modem, you can also configure the driver from the insmod command line (or by means of an option line in -/etc/conf.modules). +/etc/modules.conf). Examples: insmod soundmodem mode="sbc:afsk1200" iobase=0x220 irq=5 dma=1 diff --git a/Documentation/oops-tracing.txt b/Documentation/oops-tracing.txt index 9673a46e7..4263c68d5 100644 --- a/Documentation/oops-tracing.txt +++ b/Documentation/oops-tracing.txt @@ -16,6 +16,37 @@ If you are totally stumped as to whom to send the report, send it to linux-kernel@vger.rutgers.edu. Thanks for your help in making Linux as stable as humanly possible. +Where is the_oops.txt? +---------------------- + +Normally the Oops text is read from the kernel buffers by klogd and +handed to syslogd which writes it to a syslog file, typically +/var/log/messages (depends on /etc/syslog.conf). Sometimes klogd dies, +in which case you can run dmesg > file to read the data from the kernel +buffers and save it. Or you can cat /proc/kmsg > file, however you +have to break in to stop the transfer, kmsg is a "never ending file". +If the machine has crashed so badly that you cannot enter commands or +the disk is not available then you have three options :- + +(1) Hand copy the text from the screen and type it in after the machine + has restarted. Messy but it is the only option if you have not + planned for a crash. + +(2) Boot with a serial console (see Documentation/serial-console.txt), + run a null modem to a second machine and capture the output there + using your favourite communication program. Minicom works well. + +(3) Patch the kernel with one of the crash dump patches. These save + data to a floppy disk or video rom or a swap partition. None of + these are standard kernel patches so you have to find and apply + them yourself. Search kernel archives for kmsgdump, lkcd and + oops+smram. + +No matter how you capture the log output, feed the resulting file to +ksymoops along with /proc/ksyms and /proc/modules that applied at the +time of the crash. /var/log/ksymoops can be useful to capture the +latter, man ksymoops for details. + Full Information ---------------- diff --git a/Documentation/parport.txt b/Documentation/parport.txt index c932216df..db0c13e0b 100644 --- a/Documentation/parport.txt +++ b/Documentation/parport.txt @@ -35,7 +35,7 @@ auto-detected IRQ. Currently, PC-style (parport_pc), Sun Ultra/AX KMod ---- -If you use kmod, you will find it useful to edit /etc/conf.modules. +If you use kmod, you will find it useful to edit /etc/modules.conf. Here is an example of the lines that need to be added: post-install parport modprobe -k parport_pc diff --git a/Documentation/pci.txt b/Documentation/pci.txt index 86d0a58c4..07572a696 100644 --- a/Documentation/pci.txt +++ b/Documentation/pci.txt @@ -4,7 +4,7 @@ "What should you avoid when writing PCI drivers" - by Martin Mares <mj@atrey.karlin.mff.cuni.cz> on 09-Oct-1999 + by Martin Mares <mj@atrey.karlin.mff.cuni.cz> on 03-Nov-1999 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -73,6 +73,8 @@ corresponding register block for you. config space. You should use the values in the pci_dev structure as they might have been remapped by the kernel. + See Documentation/IO-mapping.txt for how to access device memory. + 5. Other interesting functions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ pci_find_slot() Find pci_dev corresponding to given bus and diff --git a/Documentation/sound/AWE32 b/Documentation/sound/AWE32 index edc0b880e..a0f18d640 100644 --- a/Documentation/sound/AWE32 +++ b/Documentation/sound/AWE32 @@ -83,7 +83,7 @@ Compile it. Copy sfxload program to /usr/bin. To enable AWE general midi synthesis you should also get the sound bank file for general midi from http://members.xoom.com/yar/synthgm.sbk.gz. Copy it to /usr and gunzip it there. -7) Edit /etc/conf.modules, inserting at the end of the file: +7) Edit /etc/modules.conf, inserting at the end of the file: alias midi awe_wave post-install awe_wave /usr/bin/sfxload /usr/synthfm.sbk diff --git a/Documentation/sound/AudioExcelDSP16 b/Documentation/sound/AudioExcelDSP16 index 855ee59de..f4ffd9d0c 100644 --- a/Documentation/sound/AudioExcelDSP16 +++ b/Documentation/sound/AudioExcelDSP16 @@ -41,7 +41,7 @@ mpu_base I/O base address for activate MPU-401 mode (0x300, 0x310, 0x320 or 0x330) mpu_irq MPU-401 irq line (5, 7, 9, 10 or 0) -The /etc/conf.modules will have lines like this: +The /etc/modules.conf will have lines like this: options opl3 io=0x388 options ad1848 io=0x530 irq=11 dma=3 @@ -51,7 +51,7 @@ Where the aedsp16 options are the options for this driver while opl3 and ad1848 are the corresponding options for the MSS and OPL3 modules. Loading MSS and OPL3 needs to pre load the aedsp16 module to set up correctly -the sound card. Installation dependencies must be written in the conf.modules +the sound card. Installation dependencies must be written in the modules.conf file: pre-install ad1848 modprobe aedsp16 diff --git a/Documentation/sound/CMI8330 b/Documentation/sound/CMI8330 index fca15f606..a12bed1d2 100644 --- a/Documentation/sound/CMI8330 +++ b/Documentation/sound/CMI8330 @@ -88,7 +88,7 @@ CONFIG_SOUND_MSS=m -Alma Chao <elysian@ethereal.torsion.org> suggests the following /etc/conf.modules: +Alma Chao <elysian@ethereal.torsion.org> suggests the following /etc/modules.conf: alias sound ad1848 alias synth0 opl3 diff --git a/Documentation/sound/Introduction b/Documentation/sound/Introduction index f33121e0c..0e9bbc865 100644 --- a/Documentation/sound/Introduction +++ b/Documentation/sound/Introduction @@ -145,7 +145,7 @@ MODPROBE: ========= If loading via modprobe, these common files are automatically loaded -when requested by modprobe. For example, my /etc/conf.modules contains: +when requested by modprobe. For example, my /etc/modules.conf contains: alias sound sb options sb io=0x240 irq=9 dma=3 dma16=5 mpu_io=0x300 @@ -205,7 +205,7 @@ http://www.opensound.com. Before loading the commercial sound driver, you should do the following: 1. remove sound modules (detailed above) -2. remove the sound modules from /etc/conf.modules +2. remove the sound modules from /etc/modules.conf 3. move the sound modules from /lib/modules/<kernel>/misc (for example, I make a /lib/modules/<kernel>/misc/tmp directory and copy the sound module files to that @@ -241,7 +241,7 @@ twice, you need to do the following: sb.o could be copied (or symlinked) to sb1.o for the second SoundBlasster. -2. Make a second entry in /etc/conf.modules, for example, +2. Make a second entry in /etc/modules.conf, for example, sound1 or sb1. This second entry should refer to the new module names for example sb1, and should include the I/O, etc. for the second sound card. @@ -333,7 +333,7 @@ There are several ways of configuring your sound: 2) On the command line when using insmod or in a bash script using command line calls to load sound. -3) In /etc/conf.modules when using modprobe. +3) In /etc/modules.conf when using modprobe. 4) Via Red Hat's /usr/sbin/sndconfig program (text based). diff --git a/Documentation/sound/OPL3-SA2 b/Documentation/sound/OPL3-SA2 index a51a4aebb..e6bca7089 100644 --- a/Documentation/sound/OPL3-SA2 +++ b/Documentation/sound/OPL3-SA2 @@ -125,7 +125,7 @@ and I'll try my best to help. Lastly, if you're using modules and want to set up automatic module loading with kmod, the kernel module loader, here is the section I -currently use in my conf.modules file: +currently use in my modules.conf file: # Sound alias char-major-14 opl3sa2 diff --git a/Documentation/sound/Opti b/Documentation/sound/Opti index 34b0f4331..07318d243 100644 --- a/Documentation/sound/Opti +++ b/Documentation/sound/Opti @@ -18,7 +18,7 @@ force the card into a mode in which it can be programmed. If you have another OS installed on your computer it is recommended that Linux and the other OS use the same resources. -Also, it is recommended that resources specified in /etc/conf.modules +Also, it is recommended that resources specified in /etc/modules.conf and resources specified in /etc/isapnp.conf agree. Compiling the sound driver @@ -68,9 +68,9 @@ address is hard-coded into the driver. Using kmod and autoloading the sound driver ------------------------------------------- Comment: as of linux-2.1.90 kmod is replacing kerneld. -The config file '/etc/conf.modules' is used as before. +The config file '/etc/modules.conf' is used as before. -This is the sound part of my /etc/conf.modules file. +This is the sound part of my /etc/modules.conf file. Following that I will explain each line. alias mixer0 mad16 diff --git a/Documentation/sound/README.modules b/Documentation/sound/README.modules index 91d044586..9cc30a3ac 100644 --- a/Documentation/sound/README.modules +++ b/Documentation/sound/README.modules @@ -26,7 +26,7 @@ Note that it is no longer necessary or possible to configure sound in the drivers/sound dir. Now one simply configures and makes one's kernel and modules in the usual way. - Then, add to your /etc/modules.conf or /etc/conf.modules something like: + Then, add to your /etc/modules.conf something like: alias char-major-14 sb post-install sb /sbin/modprobe "-k" "adlib_card" @@ -82,7 +82,7 @@ wasteful of RAM, but it guarantees that sound always works. To make the sound driver use persistent DMA buffers we need to pass the sound.o module a "dmabuf=1" command-line argument. This is normally done -in /etc/conf.modules (or the more proper /etc/modules.conf) like so: +in /etc/modules.conf like so: options sound dmabuf=1 diff --git a/Documentation/sound/Wavefront b/Documentation/sound/Wavefront index 66501a566..f1dcf975f 100644 --- a/Documentation/sound/Wavefront +++ b/Documentation/sound/Wavefront @@ -190,7 +190,7 @@ Here's my autoconf.h SOUND section: 6) How do I configure my card ? ************************************************************ -You need to edit /etc/conf.modules. Here's mine (edited to show the +You need to edit /etc/modules.conf. Here's mine (edited to show the relevant details): # Sound system diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt index ab8676faf..c17774865 100644 --- a/Documentation/sysrq.txt +++ b/Documentation/sysrq.txt @@ -33,7 +33,7 @@ On other - If you know of the key combos for other architectures, please 'b' - Will immediately reboot the system without syncing or unmounting your disks. -'o' - Will shut your system off via APM (if configured and supported). +'o' - Will shut your system off (if configured and supported). 's' - Will attempt to sync all mounted filesystems. |