summaryrefslogtreecommitdiffstats
path: root/sys/conf
Commit message (Collapse)AuthorAgeFilesLines
* Add sysctl variables for the Linuxulator. These reside under `compat.linux' asmarcel1999-08-271-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | discussed on current. The following variables are defined (for now): osname (defaults to "Linux") Allow users to change the name of the OS as returned by uname(2), specially added for all those Linux Netscape users and statistics maniacs :-) We now have what we all wanted! osrelease (defaults to "2.2.5") Allow users to change the version of the OS as returned by uname(2). Since -current supports glibc2.1 now, change the default to 2.2.5 (was 2.0.36). oss_version (defaults to 198144 [0x030600]) This one will be used by the OSS_GETVERSION ioctl (PR 12917) which I can commit now that we have the MIB. The default version number is the lowest version possible with the current 'encoding'. A note about imprisoned processes (see jail(2)): These variables are copy-on-write (as suggested by phk). This means that imprisoned processes will use the system wide value unless it is written/set by the process. From that moment on, a copy local to the prison will be used. A note about the implementation: I choose to add a single pointer to struct prison, because I didn't like the idea of changing struct prison every time I come up with a new variable. As a side effect, the extra storage is only needed when a variable is set from within the prison. This also minimizes kernel bloat when the Linuxulator is not used; both compiled in or as a module. Reviewed by: bde (first version only) and phk
* Add miibus drivers for the ThunderLAN internal PHY and the Micro Linearwpaul1999-08-271-0/+2
| | | | | | | | | ML6692 PHY. The Micro Linear driver is my own; the ThunderLAN driver is a port of the NetBSD driver with various hacks. The ML driver is necessary to support the Olicom OC-2326 ThunderLAN-based NIC. Also regenerated miidevs.h to pick up the proper 'obtained from' revision string.
* Merge from sys/i386/conf/options.i386 revision .1.20.kato1999-08-231-2/+1
|
* This commit adds device driver support for the Sundance Technologies ST201wpaul1999-08-212-1/+6
| | | | | | | | | | | | | PCI fast ethernet controller. Currently, the only card I know that uses this chip is the D-Link DFE-550TX. (Don't ask me where to buy these: the only cards I have are samples sent to me by D-Link.) This driver is the first to make use of the miibus code once I'm sure it all works together nicely, I'll start converting the other drivers. The Sundance chip is a clone of the 3Com 3c90x Etherlink XL design only with its own register layout. Support is provided for ifmedia, hardware multicast filtering, bridging and promiscuous mode.
* This commit adds support for the NetBSD MII abstraction layer andwpaul1999-08-212-1/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MII-compliant PHY drivers. Many 10/100 ethernet NICs available today either use an MII transceiver or have built-in transceivers that can be programmed using an MII interface. It makes sense then to separate this support out into common code instead of duplicating it in all of the NIC drivers. The mii code also handles all of the media detection, selection and reporting via the ifmedia interface. This is basically the same code from NetBSD's /sys/dev/mii, except it's been adapted to FreeBSD's bus architecture. The advantage to this is that it automatically allows everything to be turned into a loadable module. There are some common functions for use in drivers once an miibus has been attached (mii_mediachg(), mii_pollstat(), mii_tick()) as well as individual PHY drivers. There is also a generic driver for all PHYs that aren't handled by a specific driver. It's possible to do this because all 10/100 PHYs implement the same general register set in addition to their vendor-specific register sets, so for the most part you can use one driver for pretty much any PHY. There are a couple of oddball exceptions though, hence the need to have specific drivers. There are two layers: the generic "miibus" layer and the PHY driver layer. The drivers are child devices of "miibus" and the "miibus" is a child of a given NIC driver. The "miibus" code and the PHY drivers can actually be compiled and kldoaded as completely separate modules or compiled together into one module. For the moment I'm using the latter approach since the code is relatively small. Currently there are only three PHY drivers here: the generic driver, the built-in 3Com XL driver and the NS DP83840 driver. I'll be adding others later as I convert various NIC drivers to use this code. I realize that I'm cvs adding this stuff instead of importing it onto a separate vendor branch, but in my opinion the import approach doesn't really offer any significant advantage: I'm going to be maintaining this stuff and writing my own PHY drivers one way or the other.
* Implement a new generic mechanism for attaching handler functions tomsmith1999-08-211-0/+1
| | | | | | | | | | | | | events, in order to pave the way for removing a number of the ad-hoc implementations currently in use. Retire the at_shutdown family of functions and replace them with new event handler lists. Rework kern_shutdown.c to take greater advantage of the use of event handlers. Reviewed by: green
* Fix short timeout problems with the pt(4) driver:ken1999-08-202-3/+10
| | | | | | | | | | | | | - increase the default timeout from 10 seconds to 60 seconds - add a new kernel option, SCSI_PT_DEFAULT_TIMEOUT, that lets users specify the default timeout for the pt driver to use - add two new ioctls, one to get the timeout for a given pt device, the other to set the timeout for a given pt device. The idea is that userland applications using the device can set the timeout to suit their purposes. The ioctls are defined in a new header file, sys/ptio.h PR: 10266 Reviewed by: gibbs, joerg
* Extract the next runnable process selection out of cpu_switch() into apeter1999-08-191-0/+1
| | | | | | | fairly machine independent C routine. gcc actually does a pretty good job of this. Reviewed by: msmith (in principle)
* The "LINUX" option isn't actually used or referenced anywhere. The stuffpeter1999-08-181-2/+1
| | | | | | | that goes to opt_dontuse.h is so an opt_*.h file doesn't get created even though an option may be used for bringing stuff in via files[.*]. Pointed out by: bde
* Merge from sys/i386/conf/files.i386 revision 1.259.kato1999-08-181-2/+4
|
* Create callable (non-inline) versions of the atomic_OP_TYPE functionsalc1999-08-181-1/+3
| | | | | | | | | | | | that are linked into the kernel. The KLD compilation options are changed to call these functions, rather than in-lining the atomic operations. This approach makes atomic operations from KLDs significantly faster on UP systems (though somewhat slower on SMP systems). PR: i386/13111 Submitted by: peter.jeremy@alcatel.com.au
* Add CAM_DEBUG_DELAY option.gibbs1999-08-161-1/+2
|
* Give if_tun the "almost clone" makeover.phk1999-08-151-2/+2
|
* Give BPF the "almost-clone" update. If you need more of them, makephk1999-08-151-2/+2
| | | | | more entries in /dev and be happy you don't need to recompile your kernel.
* Reserve bdev/cdev entries for i2o driver.jkh1999-08-111-1/+3
| | | | Requested by: Simon Shapiro
* Re-order list.des1999-08-101-4/+4
|
* Merge the cons.c and cons.h to the best of my ability. alpha may orphk1999-08-094-6/+4
| | | | may not compile, I can't test it.
* Make the pty driver as close to a cloning device as we can get for now,phk1999-08-081-3/+3
| | | | | | | | | we create the pty on the fly when it is first opened. If you run out of ptys now, just MAKEDEV some more. This also demonstrate the use of dev_t->si_tty_tty and dev_t->si_drv1 in a device driver.
* Fix a reference to `st' by replacing it with `sa'.chris1999-08-081-2/+2
|
* Sync with sys/i386/conf/options.i386 revision 1.119.kato1999-08-081-2/+7
|
* Sync with sys/i386/conf/files.i386 revision 1.257.kato1999-08-081-16/+19
|
* Add vinumraid5.c to the files for Vinum. This allows (deprecated)grog1999-08-081-0/+1
| | | | | | kernel builds with Vinum. Linted-by: phk
* The following simplifies newvers.sh somewhat and makes what(1) work withjkh1999-08-081-8/+10
| | | | | | | | | kernels again, now that we're using EGCS/GCC 2.9+. This "here" file is compatible with the Bourne shell and the Korn shell (incl. pdksh and KSH93 from AT&T, which I do have), so it doesn't make newvers.sh unportable, but makes it easier to modify in the future/read now. Submitted by: green
* Re-delete the (meaningless) device-driver tokens that came back in 1.256peter1999-08-071-29/+29
| | | | | | after having been removed in 1.253 and turned into a warning. Noticed by: bde
* Add driver support for M-systems DiskOnChip Products.phk1999-08-061-1/+4
| | | | Sponsored by: M-systems Inc. http://www.m-sys.com
* updating isdn4bsd to beta version 0.83hm1999-08-063-30/+50
|
* The ARLA folks don't need a bdev after all - remove it.jkh1999-08-041-2/+1
|
* Correction: "ans" -> "and."green1999-08-041-2/+2
|
* Add variable INSTALLFLAGS_EDIT used to remove arbitrary INSTALLFLAGS.hoek1999-07-311-2/+7
| | | | | | | | | | | | | | | Specifically intended for removing -fschg ("INSTALLFLAGS_EDIT=:S/schg/uchg/") this makes the NOFSCHG flag redundant. NOFSCHG will still be honoured by bsd.lib.mk but is valid for buildworld only. NOFSCHG is still implemented in the old way (ie. _not_ ".if NOFSCHG then { INSTALLFLAGS_EDIT+=:S/schg/,/ }" to emphasize the fact that NOFSCHG is only supported in a limited fashion and for buildworld. The interface and implementation are such that future use of flags such as sappnd can also be easily removed or altered (perhaps to uappnd). This commit brought to you by the letters B, D, and E, and the numbers six, one, thirteen, and three.
* Reserve majors for arla.jkh1999-07-311-1/+3
|
* Removed apm_setup.s.kato1999-07-301-2/+1
|
* Major update to the kernel's BIOS-calling ability.msmith1999-07-291-2/+1
| | | | | | | | | - Add support for calling 32-bit code in other segments - Add support for calling 16-bit protected mode code Update APM to use this facility. Submitted by: jlemon
* Sync with sys/i386/conf/files.i386 revision 1.254.kato1999-07-261-2/+7
|
* Pave the way for the fla driver.phk1999-07-261-2/+7
|
* Various formatting fixes on my FPE trapcode commit.cracauer1999-07-261-6/+4
| | | | Submitted by: BDE
* On FPU exceptions, pass a useful error code (one of the FPE_...cracauer1999-07-251-8/+14
| | | | | | | | | | | | | | | | macros) to the signal handler, for old-style BSD signal handlers as the second (int) argument, for SA_SIGINFO signal handlers as siginfo_t->si_code. This is source-compatible with Solaris, except that we have no <siginfo.h> (which isn't even mentioned in POSIX 1003.1b). An rather complete example program is at http://www3.cons.org/cracauer/freebsd-signal.c This will be added to the regression tests in src/. This commit also adds code to disable the (hardware) FPU from userconfig, so that you can use a software FP emulator on a machine that has hardware floating point. See LINT.
* This commit adds device driver support for Adaptec Duralink PCI fastwpaul1999-07-252-1/+9
| | | | | | | | | | | | | | | | | | | | | ethernet controllers based on the AIC-6915 "Starfire" controller chip. There are single port, dual port and quad port cards, plus one 100baseFX card. All are 64-bit PCI devices, except one single port model. The Starfire would be a very nice chip were it not for the fact that receive buffers have to be longword aligned. This requires buffer copying in order to achieve proper payload alignment on the alpha. Payload alignment is enforced on both the alpha and x86 platforms. The Starfire has several different DMA descriptor formats and transfer mechanisms. This driver uses frame descriptors for transmission which can address up to 14 packet fragments, and a single fragment descriptor for receive. It also uses the producer/consumer model and completion queues for both transmit and receive. The transmit ring has 128 descriptors and the receive ring has 256. This driver supports both FreeBSD/i386 and FreeBSD/alpha, and uses newbus so that it can be compiled as a loadable kernel module. Support for BPF and hardware multicast filtering is included.
* Removed device-dirver flags.kato1999-07-091-215/+215
|
* This commit adds driver support for the SysKonnect SK-984x serieswpaul1999-07-092-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gigabit ethernet adapters. This includes two single port cards (single mode and multimode fiber) and two dual port cards (also single mode and multimode fiber). SysKonnect is currently the only vendor with a dual port gigabit ethernet NIC. The ports on dual port adapters are treated as separate network interfaces. Thus, if you have an SK-9844 dual port SX card, you should have both sk0 and sk1 interfaces attached. Dual port cards are implemented using two XMAC II chips connected to a single SysKonnect GEnesis controller. Hence, dual port cards are really one PCI device, as opposed to two separate PCI devices connected through a PCI to PCI bridge. Note that SysKonnect's drivers use the two ports for failover purposes rather that as two separate interfaces, plus they don't support jumbo frames. This applies to their Linux driver too. :) Support is provided for hardware multicast filtering, BPF and jumbo frames. The SysKonnect cards support TCP checksum offload however this feature is not currently enabled (hopefully it will be once we get checksum offload support). There are still a few things that need to be implemeted, like the ability to communicate with the on-board LM80 voltage/temperature monitor, but I wanted to get the driver under CVS control and into -current so people could bang on it. A big thanks for SysKonnect for making all their programming info for these cards (and for their FDDI and token ring cards) available without NDA (see www.syskonnect.com).
* Implement support for hardware debug registers on the i386.jlemon1999-07-091-0/+1
| | | | Submitted by: Brian Dean <brdean@unx.sas.com>
* Sync with sys/i386/conf/Makefile.i386 revision 1.158.kato1999-07-081-5/+1
|
* Rename bpfilter to bpf.des1999-07-062-6/+6
|
* add another ISP optionmjacob1999-07-051-1/+2
|
* The IDA driver is 'ida', not 'id'msmith1999-07-051-3/+3
|
* Move the initialisation/tuning of nmbclusters from param.c/machdep.cmsmith1999-07-051-17/+1
| | | | | | | | | | | | | | | into uipc_mbuf.c. This reduces three sets of identical tunable code to one set, and puts the initialisation with the mbuf code proper. Make NMBUFs tunable as well. Move the nmbclusters sysctl here as well. Move the initialisation of maxsockets from param.c to uipc_socket2.c, next to its corresponding sysctl. Use the new tunable macros for the kern.vm.kmem.size tunable (this should have been in a separate commit, whoops).
* Update comment for new location of soft-updates sources.jdp1999-07-031-2/+2
|
* Eliminate a bunch of #include "pci.h" and #if NPCI > 0 around entirepeter1999-07-031-21/+21
| | | | files. config will leave the whole file out if configured to do so.
* Delete the 'device-driver' suffix. It's been meaningless for a long time.peter1999-07-036-415/+403
| | | | | | On the VAX, it used to be used for special compilation to avoid the optimizer which would mess with memory mapped devices etc. These days we use 'volatile'.
* Only have the pci component compiled if pci is specified at config.peter1999-07-031-3/+3
| | | | Remove #if NPCI > 0 as a result.
* Move bt_isa.c to the cpu-independent isa section.peter1999-07-032-3/+3
|
OpenPOWER on IntegriCloud