summaryrefslogtreecommitdiffstats
path: root/sys/modules
Commit message (Collapse)AuthorAgeFilesLines
* i386->amd64 syncpeter2005-06-301-0/+2
| | | | | | Add ath_hal and ichwd modules Approved by: re (blanked i386<->amd64 sync)
* Backout the change I made before 5.4-R since I wasn't aware that it was onlydwhite2005-06-241-1/+1
| | | | | | | | | | | | | a problem with one particular switch module. Create a kernel option BGE_FAKE_AUTONEG that restores the 5.4 behavior, which should make the DNLK switch module work. IBM/Intel blades with Intel or AD switch modules should work without patching or kernel options with this commit. Hardware for testing provided by several folks, including Danny Braniss <danny@cs.huji.ac.il>, Achim Patzner <ap@bnc.net>, and OffMyServer. Approved by: re
* Buid reiserifs.ko on every platforms, not only i386 and pc98.dumbbell2005-06-211-2/+1
| | | | | Reviewed by: mux (mentor) Approved by: re (dougb)
* Don't compile legacy libalias support into kernel.glebius2005-06-201-1/+1
| | | | Approved by: re (dwhite)
* Moving reiserfs from sys/gnu to sys/gnu/fs. This was discussed on arch@.dumbbell2005-06-181-1/+1
| | | | | Reviewed by: mux (mentor) Approved by: re (scottl)
* Move ext2fs from src/gnu to src/gnu/fs.rodrigc2005-06-151-1/+1
| | | | | | | Discussed on arch@. Reviewed by: kan Approved by: re (blanket), kan
* Attach ng_tcpmss to the build.glebius2005-06-102-0/+7
|
* MFP4:jkoshy2005-06-091-5/+27
| | | | | | | | | | | | | | | | - Implement sampling modes and logging support in hwpmc(4). - Separate MI and MD parts of hwpmc(4) and allow sharing of PMC implementations across different architectures. Add support for P4 (EMT64) style PMCs to the amd64 code. - New pmcstat(8) options: -E (exit time counts) -W (counts every context switch), -R (print log file). - pmc(3) API changes, improve our ability to keep ABI compatibility in the future. Add more 'alias' names for commonly used events. - bug fixes & documentation.
* Hook ichsmb to build.takawata2005-06-051-1/+1
|
* Make ichsmb loadable.takawata2005-06-051-0/+8
| | | | | PR: kern/81912 Submitted by: nork
* Let kmod.mk create an empty .h file.ru2005-06-051-3/+1
|
* Fix deprecated name, and let kmod.mk create an empty .h file.ru2005-06-051-3/+1
|
* Connect if_bridge to the build.thompsa2005-06-052-0/+18
| | | | Approved by: mlaier (mentor)
* Move MAINTAINER documentation to MAINTAINERSimp2005-06-041-2/+0
|
* Release n_hibma's maintainership due to his ENOTIME.schweikh2005-06-0411-32/+11
| | | | Discussed with, okayed, authorized, requested by, on behalf of: n_hibma (MAINTAINER)
* Fix module build.glebius2005-06-041-1/+1
| | | | MFC after: 3 days
* Update to reflect takawata-san's changes to MAINTAINERSimp2005-06-031-2/+0
|
* Fix standalone module build.ru2005-06-031-0/+6
| | | | Reported by: Boris Samorodov <bsam@ipt.ru>
* Remove myself as maintainer of the OSF/1 compat code. I haven't hadgallatin2005-06-031-2/+0
| | | | | an alpha booting -current since my xp1000 died over a year ago, and I don't think I touched the osf1 code since long before then.
* Connect the ReiserFS filesystem to the modules build (i386 only).dumbbell2005-05-242-0/+13
| | | | Approved by: mux (mentor)
* - Try to not leak resources in the attach functions of the esp(4) SBusmarius2005-05-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | front-end and the LSI64854 and NCR53C9x code in case one of these functions fails. Add detach functions to these parts and make esp(4) detachable. - Revert rev. 1.7 of esp_sbus.c, since rev. 1.34 of sbus.c the clockfreq IVAR defaults to the per-child values. - Merge ncr53c9x.c rev. 1.111 from NetBSD (partial): On reset, clear state flags and the msgout queue. In NetBSD code to notify the upper layer (i.e. CAM in FreeBSD) on reset was also added with this revision. This is believed to be not necessary in FreeBSD and was not merged. This makes ncr53c9x.c to be in sync with NetBSD up to rev. 1.114. - Conditionalize the LSI64854 support on sbus(4) only instead of sbus(4) and esp(4) as it's also required for the 'dma', 'espdma' and 'ledma' busses/devices as well as the 'SUNW,bpp' device (printer port) which all hang off of sbus(4). - Add a driver for the 'dma', 'espdma' and 'ledma' (pseudo-)busses/ devices. These busses and devices actually represent the LSI64854 DMA engines for the ESP SCSI and LANCE Ethernet controllers found on the SBus of Ultra 1 and SBus add-on cards. With 'espdma' and 'ledma' the 'esp' and 'le' devices hang off of the respective DMA bus instead of directly from the SBus. The 'dma' devices are either also used in this manner or on some add-on cards also as a companion device to an 'esp' device which also hangs off directly from the SBus. With the latter variant it's a bit tricky to glue the DMA engine to the core logic of the respective 'esp' device. With rev. 1.35 of sbus.c we are however guaranteed that such a 'dma' device is probed before the respective 'esp' device which simplifies things a lot. [1] - In the esp(4) SBus front-end read the part-unique ID code of Fast-SCSI capable chips the right way. This fixes erroneously detecting some chips as FAS366 when in fact they are not. Add explicit checks for the FAS100A, FAS216 and FAS236 variants instead treating all of these as ESP200. That way we can correctly set the respective Fast-SCSI config bits instead of driving them out of specs. This includes adding the FAS100A and FAS236 variants to the NCR53C9x core code. We probably still subsume some chip variants as ESP200 while in fact they are another variant which however shouldn't really matter as this will only happen when these chips are driven at 25MHz or less which implies not being able to run Fast-SCSI. [3] - Add a workaround to the NCR53C9x interrupt handler which ignores the stray interrupt generated by FAS100A when doing path inquiry during boot and which otherwiese would trigger a panic. - Add support for the 'esp' devices hanging off of a 'dma' or 'espdma' busses or which are companions of 'dma' devices to esp(4). In case of the variants that hang off of a DMA device this is a bit hackish as esp(4) then directly uses the softc of the respective parent to talk to the DMA engine. It might make sense to add an interface for this in order to implement this in a cleaner way however it's not yet clear how the requirements for the LANCE Ethernet controllers are and the hack works for now. [2] This effectively adds support for the onboard SCSI controller in Ultra 1 as well as most of the ESP-based SBus add-on cards to esp(4). With this the code for supporting the Performance Technologies SBS430 SBus SCSI add-on cards is also largely in place the remaining bits were however omitted as it's unclear from the NetBSD how to couple the DMA engine and the core logic together for these cards. Obtained from: OpenBSD [1] Obtained from: NetBSD [2] Clue from: BSD/OS [3] Reviewed by: scottl (earlier version) Tested with: FSBE/S add-on card (FAS236), SSHA add-on card (ESP100A), Ultra 1 (onboard FAS100A), Ultra 2 (onboard FAS366)
* Make NETGRAPH_DEBUG a kernel option, so that it can't be turned offglebius2005-05-161-0/+2
| | | | | | without hacking source. In collaboration with: ru, julian
* Change a directory layout for pc98.nyan2005-05-103-4/+4
| | | | | | | | | - Move MD files into <arch>/<arch>. - Move bus dependent files into <arch>/<bus>. Rename some files to more suitable names. Repo-copied by: peter Discussed with: imp
* Fix separate module build.marks2005-05-091-0/+5
| | | | Submitted by: njl
* Attach ng_nat and libalias to build.glebius2005-05-062-0/+2
|
* ng_nat - a netgraph(4) node, which does NATglebius2005-05-051-0/+6
|
* libalias is now buildable as kernel moduleglebius2005-05-051-0/+33
|
* Introduce MAC Framework and MAC Policy entry points to label and controlrwatson2005-05-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | access to POSIX Semaphores: mac_init_posix_sem() Initialize label for POSIX semaphore mac_create_posix_sem() Create POSIX semaphore mac_destroy_posix_sem() Destroy POSIX semaphore mac_check_posix_sem_destroy() Check whether semaphore may be destroyed mac_check_posix_sem_getvalue() Check whether semaphore may be queried mac_check_possix_sem_open() Check whether semaphore may be opened mac_check_posix_sem_post() Check whether semaphore may be posted to mac_check_posix_sem_unlink() Check whether semaphore may be unlinked mac_check_posix_sem_wait() Check whether may wait on semaphore Update Biba, MLS, Stub, and Test policies to implement these entry points. For information flow policies, most semaphore operations are effectively read/write. Submitted by: Dandekar Hrishikesh <rishi_dandekar at sbcglobal dot net> Sponsored by: DARPA, McAfee, SPARTA Obtained from: TrustedBSD Project
* Use the new path (post repo-copy) to our sources.jkoshy2005-04-281-1/+1
|
* new files and compile defines to build new ipfilterdarrenr2005-04-251-2/+3
|
* Throw the switch on the new driver generation/loading mechanism. Fromwpaul2005-04-242-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | here on in, if_ndis.ko will be pre-built as a module, and can be built into a static kernel (though it's not part of GENERIC). Drivers are created using the new ndisgen(8) script, which uses ndiscvt(8) under the covers, along with a few other tools. The result is a driver module that can be kldloaded into the kernel. A driver with foo.inf and foo.sys files will be converted into foo_sys.ko (and foo_sys.o, for those who want/need to make static kernels). This module contains all of the necessary info from the .INF file and the driver binary image, converted into an ELF module. You can kldload this module (or add it to /boot/loader.conf) to have it loaded automatically. Any required firmware files can be bundled into the module as well (or converted/loaded separately). Also, add a workaround for a problem in NdisMSleep(). During system bootstrap (cold == 1), msleep() always returns 0 without actually sleeping. The Intel 2200BG driver uses NdisMSleep() to wait for the NIC's firmware to come to life, and fails to load if NdisMSleep() doesn't actually delay. As a workaround, if msleep() (and hence ndis_thsuspend()) returns 0, use a hard DELAY() to sleep instead). This is not really the right thing to do, but we can't really do much else. At the very least, this makes the Intel driver happy. There are probably other drivers that fail in this way during bootstrap. Unfortunately, the only workaround for those is to avoid pre-loading them and kldload them once the system is running instead.
* Pick up the selectors to use for various kernel segments from assym.siedowse2005-04-221-2/+2
| | | | | | | | instead of assuming fixed offsets within the GDT. The hard-coded values here have been incorrect since Peter's GDT rearranging around 10 days ago, causing ACPI resume problems. Reviewed by: peter
* Add sio and puc to i386 build.imp2005-04-221-1/+4
| | | | Remove ray from ia64 build since it hasn't been tested there.
* Create a puc module. Not connected to the build until I can test it onimp2005-04-221-0/+10
| | | | more machines.
* Revert previous commit: build hwpmc(4) on all architectures.marcel2005-04-201-3/+1
| | | | Ok'd by: jkoshy@
* Rename from apm_bioscall.s to apm_bioscall.S for removing a special rulenyan2005-04-201-6/+1
| | | | | | to build a module. A repo-copy is not done because it has no important logs. Pointed out by: ru
* Only compile for the hwpmc module for supported architectures.jkoshy2005-04-201-1/+3
| | | | Submitted by: grehan
* Add a driver for SMI-based SpeedStep. The hardware supports two frequencynjl2005-04-191-0/+4
| | | | | | | | | | settings and is an older version of the same design used for ICH SpeedStep. It is only known to be available on PIIX4 chipsets. Many thanks to Bruno Ducrot for writing the driver and Jon Noack for testing. Submitted by: Bruno Ducrot
* Bring a working snapshot of hwpmc(4), its associated libraries, userland ↵jkoshy2005-04-192-0/+22
| | | | | | | | | | utilities and documentation into -CURRENT. Bump FreeBSD_version. Reviewed by: alc, jhb (kernel changes)
* Initial import of ipw, iwi, ral and ural drivers:damien2005-04-185-0/+37
| | | | | | | | | ipw - Intel PRO/Wireless 2100 iwi - Intel PRO/Wireless 2200BG/2225BG/2915ABG ral - Ralink Technology RT2500 ural - Ralink Technology RT2500USB Approved by: silby (mentor)
* Fix the apm module on pc98.nyan2005-04-171-2/+13
| | | | | Pointed out by: Kuwamura Shinya <kuwa at lares dot dti dot ne dot jp> MFC after: 1 day
* Update to DRM CVS as of 2005-04-12, bringing many changes:anholt2005-04-163-1/+42
| | | | | | | | | | | | | | | | | | | | - Split core DRM routines back into their own module, rather than using the nasty templated system like before. - Development-class R300 support in radeon driver (requires userland pieces, of course). - Mach64 driver (haven't tested in a while -- my mach64s no longer fit in the testbox). Covers Rage Pros, Rage Mobility P/M, Rage XL, and some others. - i915 driver files, which just need to get drm_drv.c fixed to allow attachment to the drmsub device. Covers i830 through i915 integrated graphics. - savage driver files, which should require minimal changes to work. Covers the Savage3D, Savage IX/MX, Savage 4, ProSavage. - Support for color and texture tiling and HyperZ features of Radeon. Thanks to: scottl (much p4 handholding) Jung-uk Kim (helpful prodding) PR: [1] kern/76879, [2] kern/72548 Submitted by: [1] Alex, lesha at intercaf dot ru [2] Shaun Jurrens, shaun at shamz dot net
* Build cpufreq on ia64. The upcoming Montecito processor supports themarcel2005-04-131-0/+1
| | | | | | | | Enhanced SpeedStep (that is, a follow-up of it called Foxton). Until we actually have support for that, we build to catch regressions in the framework. Triggered by: njl
* The latest release of the FreeBSD driver (twa) forvkashyap2005-04-121-5/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3ware's 9xxx series controllers. This corresponds to the 9.2 release (for FreeBSD 5.2.1) on the 3ware website. Highlights of this release are: 1. The driver has been re-architected to use a "Common Layer" (all tw_cl* files), which is a consolidation of all OS-independent parts of the driver. The FreeBSD OS specific portions of the driver go into an "OS Layer" (all tw_osl* files). This re-architecture is to achieve better maintainability, consistency of behavior across OS's, and better portability to new OS's (drivers for new OS's can be written by just adding an OS Layer that's specific to the OS, by complying to a "Common Layer Programming Interface" API. 2. The driver takes advantage of multiple processors. 3. The driver has a new firmware image bundled, the new features of which include Online Capacity Expansion and multi-lun support, among others. More details about 3ware's 9.2 release can be found here: http://www.3ware.com/download/Escalade9000Series/9.2/9.2_Release_Notes_Web.pdf Since the Common Layer is used across OS's, the FreeBSD specific include path for header files (/sys/dev/twa) is not part of the #include pre-processor directive in any of the source files. For being able to integrate twa into the kernel despite this, Makefile.<arch> has been changed to add the include path to CFLAGS. Reviewed by: scottl
* Create new i386 windows/bsd thunking layer, similar to the amd64 thunkingwpaul2005-04-111-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | layer, but with a twist. The twist has to do with the fact that Microsoft supports structured exception handling in kernel mode. On the i386 arch, exception handling is implemented by hanging an exception registration list off the Thread Environment Block (TEB), and the TEB is accessed via the %fs register. The problem is, we use %fs as a pointer to the pcpu stucture, which means any driver that tries to write through %fs:0 will overwrite the curthread pointer and make a serious mess of things. To get around this, Project Evil now creates a special entry in the GDT on each processor. When we call into Windows code, a context switch routine will fix up %fs so it points to our new descriptor, which in turn points to a fake TEB. When the Windows code returns, or calls out to an external routine, we swap %fs back again. Currently, Project Evil makes use of GDT slot 7, which is all 0s by default. I fully expect someone to jump up and say I can't do that, but I couldn't find any code that makes use of this entry anywhere. Sadly, this was the only method I could come up with that worked on both UP and SMP. (Modifying the LDT works on UP, but becomes incredibly complicated on SMP.) If necessary, the context switching stuff can be yanked out while preserving the convention calling wrappers. (Fortunately, it looks like Microsoft uses some special epilog/prolog code on amd64 to implement exception handling, so the same nastiness won't be necessary on that arch.) The advantages are: - Any driver that uses %fs as though it were a TEB pointer won't clobber pcpu. - All the __stdcall/__fastcall/__regparm stuff that's specific to gcc goes away. Also, while I'm here, switch NdisGetSystemUpTime() back to using nanouptime() again. It turns out nanouptime() is way more accurate than just using ticks(). On slower machines, the Atheros drivers I tested seem to take a long time to associate due to the loss in accuracy.
* Connect the atapicam module to the build.scottl2005-04-051-1/+1
|
* Add a Makefile for atapi-cam.scottl2005-04-051-0/+9
|
* Add support for _PDC/_OSC by advertising that we support direct access tonjl2005-04-041-6/+5
| | | | | the PERF_CTL/STS MSRs via the new acpi_get_features() method. This should allow newer systems to use SpeedStep.
* Don't build arcmsr on pc98. The card either won't fit/work in theimp2005-04-011-1/+1
| | | | | | | pc98 machines because (a) it is PCIe or PCI-X (b) there's a BIOS that must run at boot which assumes IBM-AT compatible boot environment. Noticed by: scottl
* Glue the arcmsr driver into the tree.scottl2005-03-311-0/+3
|
OpenPOWER on IntegriCloud