summaryrefslogtreecommitdiffstats
path: root/sys/modules
Commit message (Collapse)AuthorAgeFilesLines
...
* Add modules for the HCI part of USB. This is convenient when having a UHCIn_hibma2008-10-095-1/+46
| | | | controller in your laptop but inserting a (OHCI-based) Option Cardbus card.
* This is the roumored ATA modulerisation works, and it needs a little ↵sos2008-10-0931-4/+382
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | explanation. If you just config KERNEL as usual there should be no apparent changes, you'll get all chipset support code compiled in. However there is now a way to only compile in code for chipsets needed on a pr vendor basis. ATA now has the following "device" entries: atacore: ATA core functionality, always needed for any ATA setup atacard: CARDBUS support atacbus: PC98 cbus support ataisa: ISA bus support atapci: PCI bus support only generic chipset support. ataahci: AHCI support, also pulled in by some vendor modules. ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek, atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron, atamarvell, atamicron, atanational, atanetcell, atanvidia, atapromise, ataserverworks, atasiliconimage, atasis, atavia; Vendor support, ie atavia for VIA chipsets atadisk: ATA disk driver ataraid: ATA softraid driver atapicd: ATAPI cd/dvd driver atapifd: ATAPI floppy/flashdisk driver atapist: ATAPI tape driver atausb: ATA<>USB bridge atapicam: ATA<>CAM bridge This makes it possible to config a kernel with just VIA chipset support by having the following ATA lines in the kernel config file: device atacore device atapci device atavia And then you need the atadisk, atapicd etc lines in there just as usual. If you use ATA as modules loaded at boot there is few changes except the rename of the "ata" module to "atacore", things looks just as usual. However under atapci you now have a whole bunch of vendor specific drivers, that you can kldload individually depending on you needs. Drivers have the same names as used in the kernel config explained above.
* the 3945 firmware license does not require acknowledging the EULA,sam2008-10-071-1/+0
| | | | | | | | remove the sysctl ack requirement Pointed out by: Joerg Sonnenberger Reviewed by: thompsa Approved by: core
* - Add driver for Attansic L2 FastEthernet controller found onstas2008-10-032-0/+9
| | | | | | | | | Asus EeePC and some Asus mainboards. Reviewed by: yongari, rpaulo, jhb Tested by: many Approved by: kib (mentor) MFC after: 1 week
* - Remove default NIC dependency on ulp headerskmacy2008-09-241-4/+27
| | | | | | | - make toe module build dependent on kernel support Submitted by: Chelsio Inc. MFC after: 1 week
* Update cxgb include paths to not require prefixing with dev/cxgbkmacy2008-09-235-9/+14
| | | | Submitted by: Chelsio Inc.
* add ddb support (default to off unless built with the kernel)sam2008-09-151-4/+5
|
* Allow COMPAT_SVR4 to be built without COMPAT_43.ed2008-09-151-6/+1
| | | | | | | | | | | | | | It seems we only depend on COMPAT_43 to implement the send() and recv() routines. We can easily implement them using sendto() and recvfrom(), just like we do inside our very own C library. I wasn't able to really test it, apart from simple compilation testing. I've heard rumours that COMPAT_SVR4 is broken inside execve() anyway. It's still worth to fix this, because I suspect we'll get rid of COMPAT_43 somewhere in the future... Reviewed by: rdivacky Discussed with: jhb
* Connect ufoma(4) to build and,takawata2008-09-121-0/+1
| | | | disable handsfree interface that is not yet ported to newtty.
* Resurrect the sbni(4) driver. Someone finally tested the MPSAFE patches andjhb2008-09-102-1/+13
| | | | | | the driver worked ok with them. Tested by: friends of yar
* Build k8temp on i386.rpaulo2008-09-091-0/+1
|
* Per email to arch@ a little while ago (that was greeted with silence),imp2008-09-0137-66/+65
| | | | | prefer the more common > ${.TARGET} over > opt_foo.h in modules makefiles.
* opt_bus.h isn't needed here anymore. It never was really needed,imp2008-08-301-1/+1
| | | | since usb has no business including it like it did...
* Remove opt_wi.h from module and fix typo in pccarddevs.imp2008-08-271-6/+1
|
* Add uipaq. HTC smart phones use it, and it seems like a reasonableimp2008-08-241-0/+1
| | | | thing to have laying around.
* Add a very simple dpms(4) driver that uses the VESA BIOS DPMS calls tojhb2008-08-232-0/+11
| | | | | | | turn off the external display during suspend and restore it to its original state on resume. MFC after: 2 weeks
* Update drm kernel drivers.rnoland2008-08-231-1/+1
| | | | | | | | | | This is a sync to mesa/drm pre-gem, with a few fixes on top of that. It also contains one local patch supplied by kib@ that I can't apply to git.master shared code. Approved by: flz Obtained from: mesa/drm git.master MFC after: 2 weeks
* Integrate the new MPSAFE TTY layer to the FreeBSD operating system.ed2008-08-202-15/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The last half year I've been working on a replacement TTY layer for the FreeBSD kernel. The new TTY layer was designed to improve the following: - Improved driver model: The old TTY layer has a driver model that is not abstract enough to make it friendly to use. A good example is the output path, where the device drivers directly access the output buffers. This means that an in-kernel PPP implementation must always convert network buffers into TTY buffers. If a PPP implementation would be built on top of the new TTY layer (still needs a hooks layer, though), it would allow the PPP implementation to directly hand the data to the TTY driver. - Improved hotplugging: With the old TTY layer, it isn't entirely safe to destroy TTY's from the system. This implementation has a two-step destructing design, where the driver first abandons the TTY. After all threads have left the TTY, the TTY layer calls a routine in the driver, which can be used to free resources (unit numbers, etc). The pts(4) driver also implements this feature, which means posix_openpt() will now return PTY's that are created on the fly. - Improved performance: One of the major improvements is the per-TTY mutex, which is expected to improve scalability when compared to the old Giant locking. Another change is the unbuffered copying to userspace, which is both used on TTY device nodes and PTY masters. Upgrading should be quite straightforward. Unlike previous versions, existing kernel configuration files do not need to be changed, except when they reference device drivers that are listed in UPDATING. Obtained from: //depot/projects/mpsafetty/... Approved by: philip (ex-mentor) Discussed: on the lists, at BSDCan, at the DevSummit Sponsored by: Snow B.V., the Netherlands dcons(4) fixed by: kan
* Move wb driver from sys/pci to sys/dev/wb.imp2008-08-141-1/+1
|
* Move pcn driver from sys/pci to sys/dev/pcn.imp2008-08-141-1/+1
|
* Move the ste driver from sys/pci to sys/dev/ste.imp2008-08-141-1/+1
|
* Move the tl driver form sys/pci to sys/dev/tl.imp2008-08-141-1/+1
|
* Remove cxgb private lro implementation and switch to using system ↵kmacy2008-08-121-1/+1
| | | | | | | implementation. Obtained from: Chelsio Inc. MFC after: 1 week
* Connect upgt(4) to the build.weongyo2008-08-111-0/+5
|
* Add Conexant/Intersil PrismGT SoftMAC wireless USB driver - upgt(4).weongyo2008-08-111-0/+10
| | | | | | | | This driver supports GW3887 based chipsets and works on x86/powerpc/sparc64. You need upgtfw kernel module before loading upgt(4). Please see the manpage. Obtained from: OpenBSD
* Move sis to sys/dev/sis for consistency.imp2008-08-101-1/+1
|
* Move the xl driver form sys/pci to sys/dev/xl for consistency.imp2008-08-101-1/+1
|
* Add glxsb(4) driver for the Security Block in AMD Geode LX processors (asphilip2008-08-092-0/+11
| | | | | | | | | | | | | | found in Soekris hardware, for instance). The hardware supports acceleration of AES-128-CBC accessible through crypto(4) and supplies entropy to random(4). TODO: o Implement rndtest(4) support o Performance enhancements Submitted by: Patrick Lamaizière <patfbsd -at- davenulle.org> Reviewed by: jhb, sam MFC after: 1 week
* - Add cpuctl(4) pseudo-device driver to provide access to some low-levelstas2008-08-082-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | features of CPUs like reading/writing machine-specific registers, retrieving cpuid data, and updating microcode. - Add cpucontrol(8) utility, that provides userland access to the features of cpuctl(4). - Add subsequent manpages. The cpuctl(4) device operates as follows. The pseudo-device node cpuctlX is created for each cpu present in the systems. The pseudo-device minor number corresponds to the cpu number in the system. The cpuctl(4) pseudo- device allows a number of ioctl to be preformed, namely RDMSR/WRMSR/CPUID and UPDATE. The first pair alows the caller to read/write machine-specific registers from the correspondent CPU. cpuid data could be retrieved using the CPUID call, and microcode updates are applied via UPDATE. The permissions are inforced based on the pseudo-device file permissions. RDMSR/CPUID will be allowed when the caller has read access to the device node, while WRMSR/UPDATE will be granted only when the node is opened for writing. There're also a number of priv(9) checks. The cpucontrol(8) utility is intened to provide userland access to the cpuctl(4) device features. The utility also allows one to apply cpu microcode updates. Currently only Intel and AMD cpus are supported and were tested. Approved by: kib Reviewed by: rpaulo, cokane, Peter Jeremy MFC after: 1 month
* Add card_if.h and pccarddevs.himp2008-08-071-1/+1
|
* Disconnect drivers that haven't been ported to MPSAFE TTY yet.ed2008-08-033-17/+0
| | | | | | | | | | | | | As clearly mentioned on the mailing lists, there is a list of drivers that have not been ported to the MPSAFE TTY layer yet. Remove them from the kernel configuration files. This means people can now still use these drivers if they explicitly put them in their kernel configuration file, which is good. People should keep in mind that after August 10, these drivers will not work anymore. Even though owners of the hardware are capable of getting these drivers working again, I will see if I can at least get them to a compilable state (if time permits).
* Unbreak the build by creating opt_nfs.hps2008-07-311-1/+1
|
* Hook up Bluetooth SCO sockets code to the buildemax2008-07-301-1/+2
| | | | MFC after: 3 months
* Change Makefile to reflect new directory structurejfv2008-07-301-3/+5
| | | | MFC after:ASAP
* Change to build module with new directory treejfv2008-07-301-10/+4
| | | | MFC after:ASAP
* Remove a file that is not used and does not exist.antoine2008-07-281-1/+1
|
* Prefer the opt_global.h from KERNBUILDDIR if existent so we obtain allmarius2008-07-241-0/+5
| | | | macros that might be relevant.
* For sun4v ensure there is an opt_global.h with SUN4V defined included,marius2008-07-221-0/+9
| | | | even for the stand-alone build.
* Add an accept filter for TCP based DNS requests. It waits until thedwmalone2008-07-182-0/+9
| | | | whole first request is present before returning from accept.
* import vendor fixes to cxgbkmacy2008-07-181-1/+1
|
* Remove the sbsh(4) driver. No one responded to requests for testing thejhb2008-07-042-9/+0
| | | | | | | MPSAFE patches on current@ and stable@. This driver also has a fundamental issue in that it sleeps when sending commands to the card including in the if_init/if_start routines (which can be called from interrupt context). As such, the driver shouldn't be working reliably even on 4.x.
* Remove the sbni(4) driver. No one responded to calls to test it onjhb2008-07-042-13/+1
| | | | current@ and stable@.
* Remove the cnw(4) driver. No one responded to calls to test it on current@jhb2008-07-042-10/+0
| | | | | | and stable@. It also is a driver for an older non-802.11 wireless PC card that is quite slow in comparison to say, wi(4). I know Warner wants this driver axed as well.
* Remove the oltr(4) driver. No one responded to calls for testing onjhb2008-07-042-17/+1
| | | | | | | | current@ and stable@ for the locking patches. The driver can always be revived if someone tests it. This driver also sleeps in its if_init routine, so it likely doesn't really work at all anyway in modern releases.
* Remove the arl(4) driver. It is reported to not work on 6.x or laterjhb2008-07-042-18/+0
| | | | | even though the driver hasn't changed since 4.x (last known working release).
* Rework the lifetime management of the kernel implementation of POSIXjhb2008-06-271-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | semaphores. Specifically, semaphores are now represented as new file descriptor type that is set to close on exec. This removes the need for all of the manual process reference counting (and fork, exec, and exit event handlers) as the normal file descriptor operations handle all of that for us nicely. It is also suggested as one possible implementation in the spec and at least one other OS (OS X) uses this approach. Some bugs that were fixed as a result include: - References to a named semaphore whose name is removed still work after the sem_unlink() operation. Prior to this patch, if a semaphore's name was removed, valid handles from sem_open() would get EINVAL errors from sem_getvalue(), sem_post(), etc. This fixes that. - Unnamed semaphores created with sem_init() were not cleaned up when a process exited or exec'd. They were only cleaned up if the process did an explicit sem_destroy(). This could result in a leak of semaphore objects that could never be cleaned up. - On the other hand, if another process guessed the id (kernel pointer to 'struct ksem' of an unnamed semaphore (created via sem_init)) and had write access to the semaphore based on UID/GID checks, then that other process could manipulate the semaphore via sem_destroy(), sem_post(), sem_wait(), etc. - As part of the permission check (UID/GID), the umask of the proces creating the semaphore was not honored. Thus if your umask denied group read/write access but the explicit mode in the sem_init() call allowed it, the semaphore would be readable/writable by other users in the same group, for example. This includes access via the previous bug. - If the module refused to unload because there were active semaphores, then it might have deregistered one or more of the semaphore system calls before it noticed that there was a problem. I'm not sure if this actually happened as the order that modules are discovered by the kernel linker depends on how the actual .ko file is linked. One can make the order deterministic by using a single module with a mod_event handler that explicitly registers syscalls (and deregisters during unload after any checks). This also fixes a race where even if the sem_module unloaded first it would have destroyed locks that the syscalls might be trying to access if they are still executing when they are unloaded. XXX: By the way, deregistering system calls doesn't do any blocking to drain any threads from the calls. - Some minor fixes to errno values on error. For example, sem_init() isn't documented to return ENFILE or EMFILE if we run out of semaphores the way that sem_open() can. Instead, it should return ENOSPC in that case. Other changes: - Kernel semaphores now use a hash table to manage the namespace of named semaphores nearly in a similar fashion to the POSIX shared memory object file descriptors. Kernel semaphores can now also have names longer than 14 chars (up to MAXPATHLEN) and can include subdirectories in their pathname. - The UID/GID permission checks for access to a named semaphore are now done via vaccess() rather than a home-rolled set of checks. - Now that kernel semaphores have an associated file object, the various MAC checks for POSIX semaphores accept both a file credential and an active credential. There is also a new posixsem_check_stat() since it is possible to fstat() a semaphore file descriptor. - A small set of regression tests (using the ksem API directly) is present in src/tools/regression/posixsem. Reported by: kris (1) Tested by: kris Reviewed by: rwatson (lightly) MFC after: 1 month
* Remove the non-existent rt2860 subdir. Note, the ralfw module is not used inthompsa2008-06-261-1/+1
| | | | | | | the build yet. PR: kern/125015 Submitted by: Dan Cojocar
* Re-implement the client side of rpc.lockd in the kernel. This implementationdfr2008-06-261-0/+1
| | | | | | | | | | | | provides the correct semantics for flock(2) style locks which are used by the lockf(1) command line tool and the pidfile(3) library. It also implements recovery from server restarts and ensures that dirty cache blocks are written to the server before obtaining locks (allowing multiple clients to use file locking to safely share data). Sponsored by: Isilon Systems PR: 94256 MFC after: 2 weeks
* Always create opt_ah.h regardless of KERNBUILDDIR.thompsa2008-06-231-1/+1
|
* Add et(4), a port of DragonFly's Agere ET1310 10/100/Gigabitdelphij2008-06-203-1/+15
| | | | | | | | Ethernet device driver, written by sephe@ Obtained from: DragonFly Sponsored by: iXsystems MFC after: 2 weeks
OpenPOWER on IntegriCloud