summaryrefslogtreecommitdiffstats
path: root/sys/modules
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|
* Additions to .PATH are cumulative so referencing $.PATH is not helpful.njl2005-03-311-1/+1
| | | | Informed by: ru
* Add the Areca SATA RAID driver (arcmsr). This supports the ARC-11xx and 12xxscottl2005-03-311-0/+10
| | | | | | | | | series of controllers. Areca provides a CLI and HTTP management tool for FreeBSD/i386 and FreeBSD/amd64 on their website. Many thanks to Areca for their support of FreeBSD. Thanks also to Mike Tansca and Sentex Communications for donating hardware. Obtained from: Erich Chen <erich at areca com tw>
* This is the much rumoured ATA mkIII update that I've been working on.sos2005-03-3014-0/+117
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | o ATA is now fully newbus'd and split into modules. This means that on a modern system you just load "atapci and ata" to get the base support, and then one or more of the device subdrivers "atadisk atapicd atapifd atapist ataraid". All can be loaded/unloaded anytime, but for obvious reasons you dont want to unload atadisk when you have mounted filesystems. o The device identify part of the probe has been rewritten to fix the problems with odd devices the old had, and to try to remove so of the long delays some HW could provoke. Also probing is done without the need for interrupts, making earlier probing possible. o SATA devices can be hot inserted/removed and devices will be created/ removed in /dev accordingly. NOTE: only supported on controllers that has this feature: Promise and Silicon Image for now. On other controllers the usual atacontrol detach/attach dance is still needed. o Support for "atomic" composite ATA requests used for RAID. o ATA RAID support has been rewritten and and now supports these metadata formats: "Adaptec HostRAID" "Highpoint V2 RocketRAID" "Highpoint V3 RocketRAID" "Intel MatrixRAID" "Integrated Technology Express" "LSILogic V2 MegaRAID" "LSILogic V3 MegaRAID" "Promise FastTrak" "Silicon Image Medley" "FreeBSD PseudoRAID" o Update the ioctl API to match new RAID levels etc. o Update atacontrol to know about the new RAID levels etc NOTE: you need to recompile atacontrol with the new sys/ata.h, make world will take care of that. NOTE2: that rebuild is done differently from the old system as the rebuild is now done piggybacked on read requests to the array, so atacontrol simply starts a background "dd" to rebuild the array. o The reinit code has been worked over to be much more robust. o The timeout code has been overhauled for races. o Support of new chipsets. o Lots of fixes for bugs found while doing the modulerization and reviewing the old code. Missing or changed features from current ATA: o atapi-cd no longer has support for ATAPI changers. Todays its much cheaper and alot faster to copy those CD images to disk and serve them from there. Besides they dont seem to be made anymore, maybe for that exact reason. o ATA RAID can only read metadata from all the above metadata formats, not write all of them (Promise and Highpoint V2 so far). This means that arrays can be picked up from the BIOS, but they cannot be created from FreeBSD. There is more to it than just the missing write metadata support, those formats are not unique to a given controller like Promise and Highpoint formats, instead they exist for several types, and even worse, some controllers can have different formats and its impossible to tell which one. The outcome is that we cannot reliably create the metadata of those formats and be sure the controller BIOS will understand it. However write support is needed to update/fail/rebuild the arrays properly so it sits fairly high on the TODO list. o So far atapicam is not supported with these changes. When/if this will change is up to the maintainer of atapi-cam so go there for questions. HW donated by: Webveveriet AS HW donated by: Frode Nordahl HW donated by: Yahoo! HW donated by: Sentex Patience by: Vife and my boys (and even the cats)
* - Fix the hpfs build, hpfs_hash.c was removed from the repository.jeff2005-03-281-1/+1
|
* Fix module build on amd64. There may be a cleaner way to do the .PATHnjl2005-03-281-0/+1
|
* Hook powernow up to the build for i386 and amd64.njl2005-03-271-1/+5
|
* Unbreak buildworld on i386 when MODULES_WITH_WORLD is defined.cognet2005-03-231-0/+4
|
* Add USB Communication Device Class Ethernet driver. Originally written forsobomax2005-03-222-0/+11
| | | | | | | | | | FreeBSD based on aue(4) it was picked by OpenBSD, then from OpenBSD ported to NetBSD and finally NetBSD version merged with original one goes into FreeBSD. Obtained from: http://www.gank.org/freebsd/cdce/ NetBSD OpenBSD
* Add acpi_fujitsu for handling acpi-controlled buttons on Fujitsu laptops.philip2005-03-182-1/+11
| | | | | | Submitted by: Anish Mistry <mistry.7 -at- osu.edu> Reviewed by: njl X-MFC after: 5.4-RELEASE
* eisa attachment is safe to be in this module, both on eisa andimp2005-03-171-1/+1
| | | | non-eisa configured kernels.
* Add PSEUDOFS_TRACE option.des2005-03-141-0/+1
|
* Use vfs_hash() instead of home-rolledphk2005-03-141-1/+1
|
* Remove ufs_ihash.c here as well.phk2005-03-141-1/+1
|
* Don't build the nve on pc98.nyan2005-03-121-1/+1
|
* Due to a CVS misfire, I ended up committing the wrong version of this.obrien2005-03-121-3/+7
|
* FreeBSD consumer bits of the nForce MCP NIC binary blob.obrien2005-03-122-0/+18
| | | | | | | Demanded by: DES Encouraged by: scottl Obtained from: q@onthenet.com.au (partially) KNF'ed by: obrien
* reorder ath_rate_onoe to after ath_rate_sample so it gets used as thesam2005-03-111-1/+1
| | | | | default rate control algorithm; this should be done differently but for now use this simple solution
* just use crypto/rijndael, and nuke opencrypto/rindael.[ch].ume2005-03-111-2/+3
| | | | | | the two became almost identical since latest KAME merge. Discussed with: sam
* SampleRate rate control algorithm for the ath driversam2005-03-112-0/+49
| | | | Submitted by: John Bicket
* connect wlan_acl to the buildsam2005-03-091-0/+1
| | | | Submitted by: Alexey Zelkin
* Move all of the hptmv files to /sys/dev/hptmv so that they won't be mistakenscottl2005-03-021-2/+2
| | | | for being on a CVS vendor branch. The files were moved via a repo-copy.
* The chip specific functions have been split out in their ownharti2005-02-251-1/+1
| | | | | C files to simplify adding of new PHY chips. Include the split out .c files in the module build too.
OpenPOWER on IntegriCloud