summaryrefslogtreecommitdiffstats
path: root/sys/conf
Commit message (Collapse)AuthorAgeFilesLines
* iwn(4) update. Notable changes:rpaulo2009-12-291-2/+30
| | | | | | | | | | | | | | | | | | | | * new firmware * untested support for 1000 and 6000 series * bgscan support * remove unnecessary RXON changes * allow setting of country/regdomain by enforcing channel flags read from the EEPROM * suspend/resume fixes * RF kill switch fixes * LED adjustments * several bus_dma*() related fixes * addressed some LORs * many other bug fixes Submitted by: Bernhard Schmidt <bschmidt at techwires.net> Obtained from: Brandon Gooch <jamesbrandongooch at gmail dot com> (LED related changes), Benjamin Kaduk <kaduk at mit dot edu> (LOR fixes), OpenBSD
* Add a driver for the `Fire' JBus to PCIe bridges found in at leastmarius2009-12-271-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | the Sun Fire V215/V245 and Sun Ultra 25/45 machines. This driver also already includes all the code to support the `Oberon' Uranus to PCIe bridges found in the Fujitsu-Siemens based Mx000 machines but due to lack of access to such a system for testing, probing of these bridges is currently disabled. Unfortunately, the event queue mechanism of these bridges for MSIs/ MSI-Xs matches our current MD and MI interrupt frameworks like square pegs fit into round holes so for now we are generous and use one event queue per MSI, which limits us to 35 MSIs/MSI-Xs per Host-PCIe-bridge (we use one event queue for the PCIe error messages). This seems tolerable as long as most devices just use one MSI/MSI-X anyway. Adding knowledge about MSIs/MSI-Xs to the MD interrupt code should allow us to decouple the 1:1 mapping at the cost of no longer being able to bind MSIs/MSI-Xs to specific CPUs as we currently have no reliable way to quiesce a device during the transition of its MSIs/ MSI-Xs to another event queue. This would still require the problem of interrupt storms generated by devices which have no one-shot behavior or can't/don't mask interrupts while the filter/handler is executed (like the older PCIe NICs supported by bge(4)) to be solved though. Committed from: 26C3
* SYnc with amd64:marcel2009-12-261-2/+0
| | | | De-support adv_isa.c and aic_isa.c
* Add hwpmc_arm.crpaulo2009-12-231-0/+1
|
* Hook ebus(4) and isa(4) up to the sun4v LINT build in order tomarius2009-12-231-0/+4
| | | | | ensure that their compilation doesn't break as they are expected to work as-is now (but aren't actually run-time tested).
* - Create a separate section in in the MI NOTES file for PCI wireless NICjhb2009-12-181-1/+22
| | | | | | | drivers and move bwi(4) there from the PCI Ethernet NIC section. - Move ath(4) and ral(4) to the MI NOTES file. Reviewed by: rpaulo
* Add entries to NOTES for the modular phy support so that these options arejhb2009-12-161-4/+37
| | | | | | | documented. PR: docs/141358 Submitted by: Bruce Cran
* more splitting of ip_fw2.c, now extract the 'table' routinesluigi2009-12-151-0/+2
| | | | | | | | | | | | and the sockopt routines (the upper half of the kernel). Whoever is the author of the 'table' code (Ruslan/glebius/oleg ?) please change the attribution in ip_fw_table.c. I have copied the copyright line from ip_fw2.c but it carries my name and I have neither written nor designed the feature so I don't deserve the credit. MFC after: 1 month
* Start splitting ip_fw2.c and ip_fw.h into smaller components.luigi2009-12-151-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At this time we pull out from ip_fw2.c the logging functions, and support for dynamic rules, and move kernel-only stuff into netinet/ipfw/ip_fw_private.h No ABI change involved in this commit, unless I made some mistake. ip_fw.h has changed, though not in the userland-visible part. Files touched by this commit: conf/files now references the two new source files netinet/ip_fw.h remove kernel-only definitions gone into netinet/ipfw/ip_fw_private.h. netinet/ipfw/ip_fw_private.h new file with kernel-specific ipfw definitions netinet/ipfw/ip_fw_log.c ipfw_log and related functions netinet/ipfw/ip_fw_dynamic.c code related to dynamic rules netinet/ipfw/ip_fw2.c removed the pieces that goes in the new files netinet/ipfw/ip_fw_nat.c minor rearrangement to remove LOOKUP_NAT from the main headers. This require a new function pointer. A bunch of other kernel files that included netinet/ip_fw.h now require netinet/ipfw/ip_fw_private.h as well. Not 100% sure i caught all of them. MFC after: 1 month
* MFp4:mav2009-12-062-0/+7
| | | | | | | | | | | | | | | | | | Introduce ATA_CAM kernel option, turning ata(4) controller drivers into cam(4) interface modules. When enabled, this options deprecates all ata(4) peripheral drivers (ad, acd, ...) and interfaces and allows cam(4) drivers (ada, cd, ...) and interfaces to be natively used instead. As side effect of this, ata(4) mode setting code was completely rewritten to make controller API more strict and permit above change. While doing this, SATA revision was separated from PATA mode. It allows DMA-incapable SATA devices to operate and makes hw.ata.atapi_dma tunable work again. Also allow ata(4) controller drivers (except some specific or broken ones) to handle larger data transfers. Previous constraint of 64K was artificial and is not really required by PCI ATA BM specification or hardware. Submitted by: nwitehorn (powerpc part)
* Remove extra parantheses from usb_ethernet.c and usb_serial.c lines.jhb2009-11-301-4/+7
| | | | | | | | | | config(8) doesn't parse parantheses and instead treated them as being part of the device driver name (e.g. '(u3g' vs 'u3g'). While here, fix the style of these long lines to match the wrapping used for other long lines in this file. Submitted by: Brett Glass MFC after: 1 week
* amdsbwd: new driver for AMD SB600/SB7xx watchdog timeravg2009-11-302-0/+2
| | | | | | | | | | | | The hardware is compliant with WDRT specification, so I originally considered including generic WDRT watchdog support, but decided against it, because I couldn't find anyone to the code for me. WDRT seems to be not very popular. Besides, generic WDRT porbably requires a slightly different driver approach. Reviewed by: des, gavin, rpaulo MFC after: 3 weeks
* Drop USB mass storage devices support from ata(4). It is out of the build asmav2009-11-261-1/+0
| | | | | | | | long as I remember, and completely superseded by better maintained umass(4). It's main idea was to optionally avoid CAM dependency for such devices, but with move ATA to CAM, it is not actual any more. No objections: hselasky@, thompsa@, arch@
* Tune CAM ATA kernel options a bit. Move PMP support from da to scbus andmav2009-11-191-2/+2
| | | | add ada device option, according to man page.
* Merge ACPICA 20091112.jkim2009-11-161-101/+102
|
* Convert syscons on i386 to TERM=xterm.ed2009-11-132-2/+0
| | | | | TEKEN_XTERM is now gone. Because we always use xterm mode now, we only need a TEKEN_CONS25 switch to go back to cons25.
* Switch the default terminal emulation style to xterm for most platforms.ed2009-11-132-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Right now syscons(4) uses a cons25-style terminal emulator. The disadvantages of that are: - Little compatibility with embedded devices with serial interfaces. - Bad bandwidth efficiency, mainly because of the lack of scrolling regions. - A very hard transition path to support for modern character sets like UTF-8. Our terminal emulation library, libteken, has been supporting xterm-style terminal emulation for months, so flip the switch and make everyone use an xterm-style console driver. I still have to enable this on i386. Right now pc98 and i386 share the same /etc/ttys file. I'm not going to switch pc98, because it uses its own Kanji-capable cons25 emulator. IMPORTANT: What to do if things go wrong (i.e. graphical artifacts): - Run the application inside script(1), try to reduce the problem and send me the log file. - In the mean time, you can run `vidcontrol -T cons25' and `export TERM=cons25' so you can run applications the same way you did before. You can also build your kernel with `options TEKEN_CONS25' to make all virtual terminals use the cons25 emulator by default. Discussed on: current@
* Move inet_aton() (specular to inet_ntoa(), already present in libkern)attilio2009-11-121-0/+1
| | | | | | | | into libkern in order to made it usable by other modules than alias_proxy. Obtained from: Sandvine Incorporated Sponsored by: Sandvine Incorporated MFC: 1 week
* Added option NETGRAPH_VLAN.ru2009-11-113-0/+3
| | | | Submitted by: pluknet
* Add ixgb(4) to NOTES.jhb2009-11-101-0/+1
| | | | Approved by: jfv
* Driver for the Apple Touchpad present on MacBook (non-Pro & Pro).rpaulo2009-11-091-0/+1
| | | | | Submitted by: Rohit Grover <rgrover1 at gmail.com> MFC after: 2 months
* Introduce define and kernel option ATA_REQUEST_TIMEOUT to control ATA(4)mav2009-11-082-0/+4
| | | | | | command timeout. Submitted by: keramida
* Reimplement the lazy FP context switching:marcel2009-10-311-0/+1
| | | | | | | | | | | | | | | | | | | o Move all code into a single file for easier maintenance. o Use a single global lock to avoid having to handle either multiple locks or race conditions. o Make sure to disable the high FP registers after saving or dropping them. o use msleep() to wait for the other CPU to save the high FP registers. This change fixes the high FP inconsistency panics. A single global lock typically serializes too much, which may be noticable when a lot of threads use the high FP registers, but in that case it's probably better to switch the high FP context synchronuously. Put differently: cpu_switch() should switch the high FP registers if the incoming and outgoing threads both use the high FP registers.
* Add missing ATA kernel options dependencies.mav2009-10-291-2/+2
| | | | MFC after: 3 days
* Update some comments regarding ktr(4).ru2009-10-291-6/+5
|
* Document new modularised ATA kernel options.mav2009-10-261-0/+37
| | | | | PR: kern/133162 MFC after: 3 days
* Update firmware images according to the latest iwn updated.rpaulo2009-10-251-10/+38
| | | | | "device iwnfw" includes all firmware images, but you can pick just one by using the model number, e.g.: "device iwn4965fw".
* MFp4:mav2009-10-231-0/+1
| | | | | Move Port Multiplier support code out of ATA XPT into pmp periph driver. This is convinient, as PMP itself is a bus target and has own state.
* - Introduce new option BCE_JUMBO_HDRSPLIT that allows user to enable headerstas2009-10-212-0/+7
| | | | | | | | splitting in bce(4) instead of (ab)using ZERO_COPY_SOCKETS that was not propagated into if_bce.c anyway. It is disabled by default. Approved by: davidch MFC after: 3 days
* Remove the newly added uch341 driver, it will be merged into uchcom instead.thompsa2009-10-191-2/+1
| | | | | Suggested by: takawata Submitted by: HPS
* Rewrite x86bios and update its dependent drivers.jkim2009-10-192-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Do not map entire real mode memory (1MB). Instead, we map IVT/BDA and ROM area separately. Most notably, ROM area is mapped as device memory (uncacheable) as it should be. User memory is dynamically allocated and free'ed with contigmalloc(9) and contigfree(9). Remove now redundant and potentially dangerous x86bios_alloc.c. If this emulator ever grows to support non-PC hardware, we may implement it with rman(9) later. - Move all host-specific initializations from x86emu_util.c to x86bios.c and remove now unnecessary x86emu_util.c. Currently, non-PC hardware is not supported. We may use bus_space(9) later when the KPI is fixed. - Replace all bzero() calls for emulated registers with more obviously named x86bios_init_regs(). This function also initializes DS and SS properly. - Add x86bios_get_intr(). This function checks if the interrupt vector is available for the platform. It is not necessary for PC-compatible hardware but it may be needed later. ;-) - Do not try turning off monitor if DPMS does not support the state. - Allocate stable memory for VESA OEM strings instead of just holding pointers to them. They may or may not be accessible always. Fix a memory leak of video mode table while I am here. - Add (experimental) BIOS POST call for vesa(4). This function calls VGA BIOS POST code from the current VGA option ROM. Some video controllers cannot save and restore the state properly even if it is claimed to be supported. Usually the symptom is blank display after resuming from suspend state. If the video mode does not match the previous mode after restoring, we try BIOS POST and force the known good initial state. Some magic was taken from NetBSD (and it was taken from vbetool, I believe.) - Add a loader tunable for vgapci(4) to give a hint to dpms(4) and vesa(4) to identify who owns the VESA BIOS. This is very useful for multi-display adapter setup. By default, the POST video controller is automatically probed and the tunable "hw.pci.default_vgapci_unit" is set to corresponding vgapci unit number. You may override it from loader but it is very unlikely to be necessary. Unfortunately only AGP/PCI/PCI-E controllers can be matched because ISA controller does not have necessary device IDs. - Fix a long standing bug in state save/restore function. The state buffer pointer should be ES:BX, not ES:DI according to VBE 3.0. If it ever worked, that's because BX was always zero. :-) - Clean up register initializations more clearer per VBE 3.0. - Fix a lot of style issues with vesa(4).
* Scan for option ROMs on i386 and amd64 only.marcel2009-10-113-1/+2
|
* cxgb(4) updates, including:np2009-10-051-0/+2
| | | | | | | | | | - support for the new Gen-2, BT, and LP-CR cards. - T3 firmware 7.7.0 - shared "common code" updates. Approved by: gnn (mentor) Obtained from: Chelsio MFC after: 1 month
* Fix build nfscl and/or nfsd.nyan2009-10-021-6/+6
| | | | MFC after: 3 days
* Add support for ChipHead 341 serial port adapter.thompsa2009-09-281-1/+2
| | | | Submitted by: Hans Petter Selasky
* lindev(4) [1] is supposed to be a collection of linux-specific pseudobz2009-09-263-0/+6
| | | | | | | | | | | | | | | | | | | devices that we also support, just not by default (thus only LINT or module builds by default). While currently there is only "/dev/full" [2], we are planning to see more in the future. We may decide to change the module/dependency logic in the future should the list grow too long. This is not part of linux.ko as also non-linux binaries like kFreeBSD userland or ports can make use of this as well. Suggested by: rwatson [1] (name) Submitted by: ed [2] Discussed with: markm, ed, rwatson, kib (weeks ago) Reviewed by: rwatson, brueffer (prev. version) PR: kern/68961 MFC after: 6 weeks
* r197444 unnecessarily changed positions of these files. Re-sort.jkim2009-09-242-4/+4
|
* Move sys/dev/x86bios to sys/compat/x86bios.jkim2009-09-232-5/+4
| | | | | | It may not be optimal but it is clearly better than the old place. OK'ed by: delphij, paradox (ddkprog yahoo com)
* Improve on r197334:mlaier2009-09-231-2/+9
| | | | | | | | | Find the most recently merged svn revision, too. If we get a svn revision that matches HEAD use rXXX=GIT otherwise use rXXX+GIT. Submitted by: avg MFC after: 3 days X-MFC: not stable/8 before 8.0
* Add per-process osrel node to the procfs, to allow read and set p_osrelkib2009-09-231-0/+1
| | | | | | | value for the process. Approved by: des (procfs maintainer) MFC after: 3 weeks
* Don't build ufs_gjournal.c at all if UFS_GJOURNAL option is not givenrdivacky2009-09-221-1/+1
| | | | | | | instead of building an almost empty C file. Approved by: pjd Approved by: ed (mentor, implicit)
* Add pieces of infrastructure required for NFSv4 ACL support in UFS.trasz2009-09-221-0/+1
| | | | Reviewed by: rwatson
* Hide x86bios stuff in i386/amd64 specific files as atkbdc would getdelphij2009-09-223-5/+15
| | | | these stuff into build.
* Build x86bios only for i386/amd64 for now. More work is requireddelphij2009-09-211-2/+0
| | | | | | | to make these functional on other architectures, and the current code breaks sparc64 and powerpc. Spotted by: tinderbox via des
* Allow atkbd to obtain keyboard repeat rate from BIOS on amd64.delphij2009-09-211-4/+4
| | | | Submitted by: swell.k at gmail.com
* Collapase interrupt supporting functions to a new module, and switch fromdelphij2009-09-213-4/+6
| | | | | | | | | | x86emu to this new module. This changeset also brings a fix for bugs introduced with the initial x86emu commit, which prevents the user from using some display mode or cause instant reboots during mode switch. Submitted by: paradox <ddkprog yahoo com>
* Revert part that should not be in my previous commit.delphij2009-09-211-29/+0
| | | | Pointy hat to: delphij
* Automatically depend on x86emu when vesa or dpms is being built intodelphij2009-09-213-8/+37
| | | | | | | kernel. With this change the user no longer need to remember building this option. Submitted by: swell.k at gmail.com
* Enable s3pci on amd64 which works on top of VESA, and allowdelphij2009-09-212-0/+2
| | | | | | static building it into kernel on i386 and amd64. Submitted by: swell.k at gmail.com
* Extract version information from git repositories. Try to find amlaier2009-09-191-9/+28
| | | | | | | | | corresponding svn version if this is a git-svn clone'ed repo. This prefers svn version information over git in case a working directory has both .svn and .git directories. MFC after: 3 days X-MFC: not stable/8 before 8.0
OpenPOWER on IntegriCloud