summaryrefslogtreecommitdiffstats
path: root/sys/modules
Commit message (Collapse)AuthorAgeFilesLines
* Sort files alphabeticallyimp2004-09-041-1/+1
|
* Hook autofs to the build.alfred2004-09-021-0/+1
|
* Cleanup paths.alfred2004-09-011-4/+6
| | | | Submitted by: ru
* Removed -Wall from CFLAGS.ru2004-09-011-1/+1
|
* Mechanically tidy up the contents of CLEANFILES:M*.h: kmod.mkru2004-09-015-7/+3
| | | | automatically removes opt_*.h and if_*.h found in SRCS.
* bsd.kmod.mk knows how to clean up opt_*.h files automatically,ru2004-09-012-8/+1
| | | | and has the necessary magic to create empty opt_*.h files.
* General modernization of coda:brooks2004-09-012-2/+1
| | | | | | | | - Ditch NVCODA - Don't use a static major - Don't declare functions extern Reviewed by: peter
* Wrong makefile in the wrong place.alfred2004-08-311-0/+14
| | | | Pointed out by: scottl
* Make coda5 compile.scottl2004-08-311-6/+4
|
* Fixed the module build.ru2004-08-311-6/+3
|
* Enable aac(4) module build for amd64scottl2004-08-301-0/+1
|
* Only compile aac_linux.ko for i386scottl2004-08-301-0/+2
|
* Remove the HW_WDOG option; it serves no purpose.des2004-08-291-1/+0
| | | | MFC after: 3 days
* Enable more modules on AMD64:obrien2004-08-291-0/+14
| | | | ciss em ext2fs i2c ida iir ips lnc mly safe scsi_low smbfs sppp twa
* Enable sound modules.obrien2004-08-291-0/+1
|
* opt_pfil_hooks.h is no longer required.andre2004-08-271-1/+0
|
* Always compile PFIL_HOOKS into the kernel and remove the associated kernelandre2004-08-271-9/+0
| | | | | | | | | | | compile option. All FreeBSD packet filters now use the PFIL_HOOKS API and thus it becomes a standard part of the network stack. If no hooks are connected the entire packet filter hooks section and related activities are jumped over. This removes any performance impact if no hooks are active. Both OpenBSD and DragonFlyBSD have integrated PFIL_HOOKS permanently as well.
* Document how a standalone module can be built with divert(4) support.ru2004-08-261-0/+4
|
* Revert the last change to sys/modules/ipfw/Makefile and fix aru2004-08-261-5/+1
| | | | | | | standalone module build in a better way. Silence from: andre MFC after: 3 days
* Make this compile again in the standalone and the MODULES_WITH_WORLDimp2004-08-231-1/+5
| | | | | | environments. Chances are good that this doesn't produce a good module, but I leave the proper defaults to the dummy opt_* files to the author.
* opt_agp.h is not required anymore.nyan2004-08-221-1/+1
|
* Enable build of Netgraph modules on all architectures.ru2004-08-181-3/+1
| | | | Tested by: make universe
* Build a dummy opt_compat.h header since linprocfs.c now requires it.tjr2004-08-181-1/+5
|
* Convert ipfw to use PFIL_HOOKS. This is change is transparent to userlandandre2004-08-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and preserves the ipfw ABI. The ipfw core packet inspection and filtering functions have not been changed, only how ipfw is invoked is different. However there are many changes how ipfw is and its add-on's are handled: In general ipfw is now called through the PFIL_HOOKS and most associated magic, that was in ip_input() or ip_output() previously, is now done in ipfw_check_[in|out]() in the ipfw PFIL handler. IPDIVERT is entirely handled within the ipfw PFIL handlers. A packet to be diverted is checked if it is fragmented, if yes, ip_reass() gets in for reassembly. If not, or all fragments arrived and the packet is complete, divert_packet is called directly. For 'tee' no reassembly attempt is made and a copy of the packet is sent to the divert socket unmodified. The original packet continues its way through ip_input/output(). ipfw 'forward' is done via m_tag's. The ipfw PFIL handlers tag the packet with the new destination sockaddr_in. A check if the new destination is a local IP address is made and the m_flags are set appropriately. ip_input() and ip_output() have some more work to do here. For ip_input() the m_flags are checked and a packet for us is directly sent to the 'ours' section for further processing. Destination changes on the input path are only tagged and the 'srcrt' flag to ip_forward() is set to disable destination checks and ICMP replies at this stage. The tag is going to be handled on output. ip_output() again checks for m_flags and the 'ours' tag. If found, the packet will be dropped back to the IP netisr where it is going to be picked up by ip_input() again and the directly sent to the 'ours' section. When only the destination changes, the route's 'dst' is overwritten with the new destination from the forward m_tag. Then it jumps back at the route lookup again and skips the firewall check because it has been marked with M_SKIP_FIREWALL. ipfw 'forward' has to be compiled into the kernel with 'option IPFIREWALL_FORWARD' to enable it. DUMMYNET is entirely handled within the ipfw PFIL handlers. A packet for a dummynet pipe or queue is directly sent to dummynet_io(). Dummynet will then inject it back into ip_input/ip_output() after it has served its time. Dummynet packets are tagged and will continue from the next rule when they hit the ipfw PFIL handlers again after re-injection. BRIDGING and IPFW_ETHER are not changed yet and use ipfw_chk() directly as they did before. Later this will be changed to dedicated ETHER PFIL_HOOKS. More detailed changes to the code: conf/files Add netinet/ip_fw_pfil.c. conf/options Add IPFIREWALL_FORWARD option. modules/ipfw/Makefile Add ip_fw_pfil.c. net/bridge.c Disable PFIL_HOOKS if ipfw for bridging is active. Bridging ipfw is still directly invoked to handle layer2 headers and packets would get a double ipfw when run through PFIL_HOOKS as well. netinet/ip_divert.c Removed divert_clone() function. It is no longer used. netinet/ip_dummynet.[ch] Neither the route 'ro' nor the destination 'dst' need to be stored while in dummynet transit. Structure members and associated macros are removed. netinet/ip_fastfwd.c Removed all direct ipfw handling code and replace it with the new 'ipfw forward' handling code. netinet/ip_fw.h Removed 'ro' and 'dst' from struct ip_fw_args. netinet/ip_fw2.c (Re)moved some global variables and the module handling. netinet/ip_fw_pfil.c New file containing the ipfw PFIL handlers and module initialization. netinet/ip_input.c Removed all direct ipfw handling code and replace it with the new 'ipfw forward' handling code. ip_forward() does not longer require the 'next_hop' struct sockaddr_in argument. Disable early checks if 'srcrt' is set. netinet/ip_output.c Removed all direct ipfw handling code and replace it with the new 'ipfw forward' handling code. netinet/ip_var.h Add ip_reass() as general function. (Used from ipfw PFIL handlers for IPDIVERT.) netinet/raw_ip.c Directly check if ipfw and dummynet control pointers are active. netinet/tcp_input.c Rework the 'ipfw forward' to local code to work with the new way of forward tags. netinet/tcp_sack.c Remove include 'opt_ipfw.h' which is not needed here. sys/mbuf.h Remove m_claim_next() macro which was exclusively for ipfw 'forward' and is no longer needed. Approved by: re (scottl)
* Add ISA attachement files for the aic7xxx driver.gibbs2004-08-171-0/+18
| | | | | Approved by: re Reminded by: obrien
* Add an ISA attachement to the aic7xxx driver to handle 284X controllers.gibbs2004-08-172-4/+4
| | | | | | | | | | | | | | | | | | | | | The ISA probe uses an identify routine to probe all slot locations from 1 to 14 that do not conflict with other allocated resources. This required making aic7770.c part of the driver core when compiled as a module. aic7xxx.c: aic79xx.c: aic_osm_lib.c: Use aic_scb_timer_start() consistently to start the watchdog timer. This removes a few places that verbatum copied the code in aic_scb_timer_start(). During recovery processing, allow commands to still be queued to the controller. The only requirement we have is that our recovery command be queued first - something the code already guaranteed. The only other change required to make this work is to prevent timers from being started for these newly queued commands. Approved by: re
* agp_amd64.c is not needed on pc98.nyan2004-08-161-1/+4
|
* And isa_if.himp2004-08-161-1/+1
|
* Add pccbb_isa.c and pccbb_pci.cimp2004-08-161-1/+1
|
* AMD64 on-CPU GART support.obrien2004-08-162-1/+6
| | | | | | | This also applies to AMD64 HW running 'i386' OS. Submitted by: Jung-uk Kim <jkim@niksun.com> Integration by: obrien
* Connect RAID3 GEOM class to the build.pjd2004-08-161-0/+1
|
* Introduce GEOM RAID3 class, i.e. kernel module, which implements RAID3pjd2004-08-161-0/+9
| | | | | | | transformation and graid3(8) userland utility, which can be used for configuration. No manual page yet, sorry. Hardware provided by: Daniel Seuffert
* - Introduce an uart_cpu_identify() which is implemented in uart_cpu_<arch>.cmarius2004-08-141-2/+7
| | | | | | | | | | | | | | | | | and that can be used as an identify function for all kinds of busses on a certain platform. Expect for sparc64 these are only stubs right now. [1] - For sparc64, add code to its uart_cpu_identify() for registering the on- board ISA UARTs and their resources based on information obtained from Open Firmware. It would be better if this would be done in the OFW ISA code. However, due to the common FreeBSD ISA code and PNP-IDs not always being present in the properties of the ISA nodes there seems to be no good way to implement that. Therefore special casing UARTs as the sole really relevant ISA devices on sparc64 seemed reasonable. [2] Approved by: marcel Discussed with: marcel [1], tmm [2] Tested by: make universe
* Now that hme(4) is MI build its module on all platforms.marius2004-08-142-4/+6
| | | | Tested by: `make universe` and powerpc cross-build on i386
* Get rid of the RANDOM_IP_ID option and make it a sysctl. NetBSDdwmalone2004-08-142-14/+3
| | | | | | | | | | | | | | | | | | | | | have already done this, so I have styled the patch on their work: 1) introduce a ip_newid() static inline function that checks the sysctl and then decides if it should return a sequential or random IP ID. 2) named the sysctl net.inet.ip.random_id 3) IPv6 flow IDs and fragment IDs are now always random. Flow IDs and frag IDs are significantly less common in the IPv6 world (ie. rarely generated per-packet), so there should be smaller performance concerns. The sysctl defaults to 0 (sequential IP IDs). Reviewed by: andre, silby, mlaier, ume Based on: NetBSD MFC after: 2 months
* Add geom_uzip -- geom class that implements read-only compressed disks.fjoe2004-08-132-0/+10
| | | | | Currently supports cloop V2.0 disk compression format. May support more formats in future.
* - Introduce an ofw_bus kobj-interface for retrieving the OFW node and amarius2004-08-124-6/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | subset ("compatible", "device_type", "model" and "name") of the standard properties in drivers for devices on Open Firmware supported busses. The standard properties "reg", "interrupts" und "address" are not covered by this interface because they are only of interest in the respective bridge code. There's a remaining standard property "status" which is unclear how to support properly but which also isn't used in FreeBSD at present. This ofw_bus kobj-interface allows to replace the various (ebus_get_node(), ofw_pci_get_node(), etc.) and partially inconsistent (central_get_type() vs. sbus_get_device_type(), etc.) existing IVAR ones with a common one. This in turn allows to simplify and remove code-duplication in drivers for devices that can hang off of more than one OFW supported bus. - Convert the sparc64 Central, EBus, FHC, PCI and SBus bus drivers and the drivers for their children to use the ofw_bus kobj-interface. The IVAR- interfaces of the Central, EBus and FHC are entirely replaced by this. The PCI bus driver used its own kobj-interface and now also uses the ofw_bus one. The IVARs special to the SBus, e.g. for retrieving the burst size, remain. Beware: this causes an ABI-breakage for modules of drivers which used the IVAR-interfaces, i.e. esp(4), hme(4), isp(4) and uart(4), which need to be recompiled. The style-inconsistencies introduced in some of the bus drivers will be fixed by tmm@ in a generic clean-up of the respective drivers later (he requested to add the changes in the "new" style). - Convert the powerpc MacIO bus driver and the drivers for its children to use the ofw_bus kobj-interface. This invloves removing the IVARs related to the "reg" property which were unused and a leftover from the NetBSD origini of the code. There's no ABI-breakage caused by this because none of these driver are currently built as modules. There are other powerpc bus drivers which can be converted to the ofw_bus kobj-interface, e.g. the PCI bus driver, which should be done together with converting powerpc to use the OFW PCI code from sparc64. - Make the SBus and FHC front-end of zs(4) and the sparc64 eeprom(4) take advantage of the ofw_bus kobj-interface and simplify them a bit. Reviewed by: grehan, tmm Approved by: re (scottl) Discussed with: tmm Tested with: Sun AX1105, AXe, Ultra 2, Ultra 60; PPC cross-build on i386
* Add the module build stuff for the ATM call control module.harti2004-08-122-0/+18
|
* change the name of the md module, to g_md, introduce a define with thejmg2004-08-091-1/+1
| | | | name MD_MODNAME, and make mdconfig use this new define...
* Due to popular demand, hook up geom_vinum to the build.le2004-08-071-0/+1
|
* Move the source code for these two modules out of src/sys/modules.des2004-08-064-906/+4
|
* Fix module builds for i386 and amd64.markm2004-08-041-0/+3
|
* Bump WARNS to 2 for all other ACPI drivers and minor cleanup.njl2004-08-034-16/+20
|
* Making a loadable null.ko for /dev/(null|zero) proved rathermarkm2004-08-032-10/+0
| | | | | | unpopular, so remove this (mis)feature. Encouragement provided by: jhb (and others)
* Really back out rev 1.388.obrien2004-08-021-0/+1
|
* Don't build and install a mem.ko module.obrien2004-08-021-1/+0
| | | | | | | | | Currently one cannot load the mem.ko module without panicing if mem is compiled into the kernel and one cannot build a kernel w/o "device mem" right now either. Thus it is too dangerous to install mem.ko right now because if one puts 'mem_load="YES"' in /etc/loader.conf they cannot boot an "old" kernel (at the time that a kernel doesn't have to be built with "device mem).
* Break out the MI part of the /dev/[k]mem and /dev/io drivers intomarkm2004-08-013-2/+25
| | | | | | | | their own directory and module, leaving the MD parts in the MD area (the MD parts _are_ part of the modules). /dev/mem and /dev/io are now loadable modules, thus taking us one step further towards a kernel created entirely out of modules. Of course, there is nothing preventing the kernel from having these statically compiled.
* Connect GEOM_MIRROR class to the build.pjd2004-07-301-0/+1
|
* Add GEOM_MIRROR class which provide RAID1 functionality and has many usefulpjd2004-07-301-0/+9
| | | | | | | | features. The gmirror(8) utility should be used for control of this class. There is no manual page yet, but I'm working on it with keramida@. Many useful tests provided by: simon (thank you!) Some ideas from: scottl, simon, phk
* Add the ACPI Panasonic extras driver.nyan2004-07-212-1/+10
| | | | Submitted by: OGAWA Takaya <t-ogawa@triaez.kaisei.org> and nyan
OpenPOWER on IntegriCloud