summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Named normally cannot be started chrooted inside a jail. Thus treatbz2009-02-071-5/+23
| | | | | | | | | | the jail case specifically. In case we find a proper pre-seeded devfs in the chroot path (mounted from the base system) permit starting chrooted else give proper warn/error messages. PR: conf/103489 Reviewed by: dougb MFC after: 5 days
* Fix build, sigh.thompsa2009-02-071-1/+1
|
* Move the comment to it's correct place.wkoszek2009-02-071-5/+5
|
* Remove leftover of alpha support for config(8)--we have MAP_FAILEDwkoszek2009-02-071-3/+0
| | | | globally defined.
* Don't forget to create opt_agp.h on ia64, which also uses agp(4).wkoszek2009-02-072-0/+6
|
* Dont hold the lock over the controller init, we are still attaching.thompsa2009-02-073-28/+13
|
* C99 TC2 now wants FP_FAST_FMA* to be defined to 1, if the macros aredas2009-02-071-3/+3
| | | | defined at all. See also: defect report #223.
* count stuck beacon eventssam2009-02-071-0/+1
|
* fix building w/o CFI_ARMEDANDDANGEROUSsam2009-02-071-4/+5
|
* expand CFI_ARMEDANDDANGEROUS to include writing the user segmentsam2009-02-071-3/+12
| | | | | of the PR; this register is actually write-once so deserves the safety-belt as much as the PLR
* si_cmdname() is defined only when SI_DEBUG is enabled, thuswkoszek2009-02-071-2/+2
| | | | | using this function in simple printf() causes compile-time problems. Use conditionally enabled DPRINT() macro instead.
* fix 11n channel constructionsam2009-02-071-6/+6
|
* add macro for future regulatory modssam2009-02-071-0/+5
|
* Rearrange this code slightly to pass softcs around instead of device_t,nwhitehorn2009-02-076-57/+85
| | | | | | | | solving a possible panic when snd_ai2s is loaded at boot time. Also change the device setup to indicate to the pcm layer that the device is MPSAFE. Submitted by: Marco Trillo Suggestions by: Ariff Abdullah
* Regulatory fixups:sam2009-02-073-66/+140
| | | | | | | | | | | | o add missing channel flags for ECM, indoor, and outdoor constraints o use HT capabilities to short-circuit HT20/HT40 channel construction o rewrite 1/2 and 1/4 width channel handling yet again; previously we assumed there was a full-width version of the channel in the calibration table but that's not always true (e.g. for the Public Safety Band), now we first check the calibration table for the exact channel we want then fall back to the heuristics we used before o fix HT channel construction; wasn't adjusting band edges for HT40 channel bandwidth requirements
* Tidy NOTES a bit:wkoszek2009-02-071-3/+14
| | | | | | | | | | | | - ath(4) is the last listed device, so make it's comment last as well - since we have hints for le(4), bring it back by inserting commented out line until I check, if it can be safely enabled. - bring snc(4) explanation - put pmtimer comment together with other drivers' comments in a block - bring comments for canbus, canbepm, pmc olpt comment has been left blank, since I don't know how does this driver differ from other printer drivers.
* Tidy NOTES a bit:wkoszek2009-02-071-3/+3
| | | | | | - leave pmtimer comment that is common to other architectures. - bring pbio explanation to the block comment relating to other drivers in the same block.
* Tidy NOTES a bit:wkoszek2009-02-071-3/+6
| | | | | | | | | | - remove misleading nve/nfe comments, which make it hard to distinguish those two at a first glance - bring pbio documentation to the block comment together with other drivers I also brought commented out line responsible for si(4), since it seems to compile and already has respective comment in this file.
* Add rudimentary support for symbolic links on UDF. Links are stored as ajhb2009-02-062-3/+124
| | | | | | | | sequence of pathname components. We walk the list building a string in the caller's passed in buffer. Currently this only handles path names in CS8 (character set 8) as that is what mkisofs generates for UDF images. MFC after: 1 month
* Comment about ural(4) isn't approprate here, since the driver is present inwkoszek2009-02-061-3/+0
| | | | | | | | | | global NOTES file. cx(4) driver isn't present in this file, though it could be. However, cx(4) seems to be more or less dead -- it hasn't been linked to the modules build, and after TTY-ng transformations it doesn't compile. Remove it until cx(4) is broken.
* ural(4) is already present in global NOTES, thus there is nowkoszek2009-02-061-2/+0
| | | | | | | | | need to explicitly list it here once again. This removes: WARNING: duplicate option `DEV_URAL' encountered. WARNING: duplicate device `ural' encountered. Warnings when compiling LINT on amd64.
* Fix AGP debugging code:wkoszek2009-02-067-3/+22
| | | | | | | | | | | | - correct format strings - fill opt_agp.h if AGP_DEBUG is defined - bring AGP_DEBUG to LINT by mentioning it in NOTES This should hopefully fix a warning that was... Found by: Coverity Prevent(tm) CID: 3676 Tested on: amd64, i386
* Add support for fifos to UDF:jhb2009-02-063-0/+64
| | | | | | | | | - Add a separate set of vnode operations that inherits from the fifo ops and use it for fifo nodes. - Add a VOP_SETATTR() method that allows setting the size (by silently ignoring the requests) of fifos. This is to allow O_TRUNC opens of fifo devices (e.g. I/O redirection in shells using ">"). - Add a VOP_PRINT() handler while I'm here.
* Tweak the output of VOP_PRINT/vn_printf() some.jhb2009-02-064-4/+5
| | | | | | | | - Align the fifo output in fifo_print() with other vn_printf() output. - Remove the leading space from lockmgr_printinfo() so its output lines up in vn_printf(). - lockmgr_printinfo() now ends with a newline, so remove an extra newline from vn_printf().
* Add KASSERTs to make it easier to debug problems like the one fixedtrasz2009-02-062-0/+2
| | | | | | | | | in r188141. Reviewed by: kib,attilio Approved by: rwatson (mentor) Tested by: pho Sponsored by: FreeBSD Foundation
* When a device containing mounted UFS filesystem disappears, the typetrasz2009-02-061-4/+4
| | | | | | | | | | | | | | | of devvp becomes VBAD, which UFS incorrectly interprets as snapshot vnode, which in turns causes panic. Fix it by replacing '!= VCHR' with '== VREG'. With this fix in place, you should no longer be able to panic the system by removing a device with an UFS filesystem mounted from it - assuming you don't use softupdates. Reviewed by: kib Tested by: pho Approved by: rwatson (mentor) Sponsored by: FreeBSD Foundation
* In urtw_init() call urtw_stop(ifp, 0) rather than urtw_stop(ifp, 1)kevlo2009-02-061-1/+1
| | | | to stop the device.
* Note that the slave address passed to smb(4) commands must be left-justifiedjhb2009-02-061-1/+4
| | | | | (LSB is 0). The iic(4) manpage probably needs similar language to describe the format it expects.
* Regenkevlo2009-02-062-2/+9
|
* Add the Buffalo WLI-U2-SG54HGkevlo2009-02-064-0/+4
|
* Add a note to document that ichsmb(4) now uses left-justified SMBus slavejhb2009-02-061-0/+7
| | | | addresses.
* Expand the scope of the sysctllock sx lock to protect the sysctl tree itself.jhb2009-02-064-25/+112
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Back in 1.1 of kern_sysctl.c the sysctl() routine wired the "old" userland buffer for most sysctls (everything except kern.vnode.*). I think to prevent issues with wiring too much memory it used a 'memlock' to serialize all sysctl(2) invocations, meaning that only one user buffer could be wired at a time. In 5.0 the 'memlock' was converted to an sx lock and renamed to 'sysctl lock'. However, it still only served the purpose of serializing sysctls to avoid wiring too much memory and didn't actually protect the sysctl tree as its name suggested. These changes expand the lock to actually protect the tree. Later on in 5.0, sysctl was changed to not wire buffers for requests by default (sysctl_handle_opaque() will still wire buffers larger than a single page, however). As a result, user buffers are no longer wired as often. However, many sysctl handlers still wire user buffers, so it is still desirable to serialize userland sysctl requests. Kernel sysctl requests are allowed to run in parallel, however. - Expose sysctl_lock()/sysctl_unlock() routines to exclusively lock the sysctl tree for a few places outside of kern_sysctl.c that manipulate the sysctl tree directly including the kernel linker and vfs_register(). - sysctl_register() and sysctl_unregister() require the caller to lock the sysctl lock using sysctl_lock() and sysctl_unlock(). The rest of the public sysctl API manage the locking internally. - Add a locked variant of sysctl_remove_oid() for internal use so that external uses of the API do not need to be aware of locking requirements. - The kernel linker no longer needs Giant when manipulating the sysctl tree. - Add a missing break to the loop in vfs_register() so that we stop looking at the sysctl MIB once we have changed it. MFC after: 1 month
* Consistently use <TAB> instead of spaces as option name and filewkoszek2009-02-062-9/+9
| | | | separator.
* fix spelling errorimp2009-02-061-1/+1
| | | | Submitted by: trasz
* Store the entire funce for disk type functions (eg CF cards and theimp2009-02-062-1/+20
| | | | like).
* Set NFSMNT_ACDIRMAX flag in fallback_mount() function.rodrigc2009-02-061-0/+1
|
* Set NFSMNT_ACREGMIN, NFSMNT_ACREGMAX, and NFSMNT_ACDIRMIN flagsrodrigc2009-02-061-0/+9
| | | | | | | | in fallback_mount() function. Add a comment to indicate that the fallback_mount() function should eventually go away. Submitted by: Jaakko Heinonen <jh saunalahti fi>
* Remove unused variable.wkoszek2009-02-061-2/+0
| | | | | Found with: Coverity Prevent(tm) CID: 4138
* Make config -x <kernel> only return non-zero characters,wkoszek2009-02-061-2/+13
| | | | | | | | | | so that: config -x <kernel> | grep <something> just works. Reported by: Danny Braniss <danny@cs.huji.ac.il>
* add PSB channels to the calibration listsam2009-02-061-3/+12
|
* Bring consistent debugging output for all values that are supposedwkoszek2009-02-052-31/+31
| | | | | | | to be printed in a hexadecimal format. Otherwise, '270' doesn't say much. Reviewed by: imp
* for adhoc and ahdemo modes try to find the "bss node": use the bssidsam2009-02-051-1/+10
| | | | | | unless it's not setup or zero's; this may not work as the bssid of the ibss isn't certain to the "right mac address" but for many cases it is
* Drop the kernel linker lock while running SYSUNINIT routines and removingjhb2009-02-051-0/+3
| | | | | | | | | sysctls during a linker file unload. We drop the lock when doing similar operations during a linker file load. To close races, clear the LINKED flag before dropping the lock so that the linker file is no longer visible to userland. MFC after: 1 week
* make -o handling like athstatssam2009-02-051-9/+30
|
* unbreak -osam2009-02-051-2/+1
|
* halt APs on rebootkmacy2009-02-051-1/+1
|
* reboot instance on resetkmacy2009-02-051-1/+4
|
* fix non-witness compilekmacy2009-02-051-0/+1
|
* eliminate gainFCorrection; just have ar5212GetGainFCorrection returnsam2009-02-052-11/+12
| | | | the calculated value as it's only used in one place
* add new stats and missing tx_raw statsam2009-02-051-2/+12
|
OpenPOWER on IntegriCloud