summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Convert mount_smbfs to use nmount().rodrigc2005-11-164-261/+68
| | | | Reviewed by: bp (smbfs maintainer)
* - Add errmsg to the list of smbfs mount options.rodrigc2005-11-161-7/+23
| | | | | | - Use vfs_mount_error() to propagate smbfs mount errors back to userspace. Reviewed by: bp (smbfs maintainer)
* Do not pass noauto to nmount() or external mount program.rodrigc2005-11-161-1/+10
| | | | Noticed by: maxim
* Catch up with loader_color -> loader_logo and document beastie_disable.ru2005-11-152-5/+12
|
* Revise hcsecd(8) and sdpd(8) rc.d scripts.emax2005-11-152-6/+22
| | | | | | | | | | - Have both scripts automatically kldload ng_btsocket(4). I did not want to do it, but its easier for users and it seems other scripts do similar things; - Assign few variables after load_rc_config, so the /etc/rc.conf overrides actually work; MFC after: 1 week
* Provide a link to the documentation of the I/O APIC at Intel.andre2005-11-151-0/+4
|
* Add geometry of SiliconSystems 4GB CF cardphk2005-11-151-0/+13
|
* Add some initial bits (currently unused) for upcoming AMRR support.damien2005-11-151-0/+10
| | | | | | | AMRR = Adaptive Multi Rate Retry algorithm More information: http://www-sop.inria.fr/rapports/sophia/RR-5208.html More to come.
* Add some initial bits (currently unused) for upcoming AMRR support.damien2005-11-151-0/+77
| | | | | AMRR = Adaptive Multi Rate Retry algorithm More information: http://www-sop.inria.fr/rapports/sophia/RR-5208.html
* Optimize and clean TX time computation.damien2005-11-152-44/+14
| | | | | | Avoid a test and a modulus operation. MFC after: 2 weeks
* Add BCM5752 to HARDWARE section.glebius2005-11-151-1/+3
|
* Recognize Broadcom BCM5752 chip, that can be found in HP DC7600.glebius2005-11-152-2/+7
| | | | | PR: kern/88940 Submitted by: Alexander Hausner
* Some whitespace and style cleanup.glebius2005-11-152-89/+88
|
* Update ieee80211_mhz2ieee to understand public safety bands and spectrumsam2005-11-152-9/+24
| | | | | | | that can potentially be mapped to negative ieee #'s. NB: before operation on the latter can be supported we need to cleanup various code that assumes ieee channel #'s are >= 0
* nuke special handling to extend cts when bursting; it was race pronesam2005-11-153-65/+2
| | | | MFC after: 7 days
* bandaid inconsistent state handling: the rate index map may besam2005-11-151-0/+5
| | | | | | stale when called to reset rate control state causing us to pickup an invalid index, check for this and skip 'em (things will eventually get fixed up so this is not harmful)
* Unbreak kernel builds.kan2005-11-151-2/+2
| | | | Submitted by: arr
* The KAME's getipnodebyaddr() code honor the MULTI_PTRS_ARE_ALIASESume2005-11-151-0/+1
| | | | | | | | | define also, but res_config.h was not included into libc/net/name6.c. So getipnodebyaddr() ignored the multiple PTRs. PR: kern/88241 Submitted by: Dan Lukes <dan__at__obluda.cz> MFC after: 3 days
* Keep track of volumes in non-optimal state and expose a simple countkan2005-11-152-0/+13
| | | | | | | of volumes that might need administrator attention through device specific sysctl to simplify device monitoring. Submitted by: Deomid Ryabkov <myself at rojer dot pp dot ru>
* Add a new configuration variable, ipv4_addrs_<ifn>, which adds one orbrooks2005-11-144-5/+84
| | | | | | | | | | | more IPv4 address from a ranged list in CIRD notation: ipv4_addrs_ed0="192.168.0.1/24 192.168.1.1-5/28" In the process move alias processing into new ipv4_up/down functions to more toward a less IPv4 centric world. Submitted by: Philipp Wuensche <cryx dash freebsd at h3q dot com>
* Briefly document the use of kern.elf32.can_exec_dyn.cognet2005-11-141-0/+4
| | | | MFC after: 3 days
* Add a new sysctl, kern.elf[32|64].can_exec_dyn. When set to 1, one cancognet2005-11-141-1/+7
| | | | | | | | | execute a ET_DYN binary (shared object). This does not make much sense, but some linux scripts expect to be able to execute /lib/ld-linux.so.2 (ldd comes to mind). The sysctl defaults to 0. MFC after: 3 days
* 0xb1881106 seems to be an AGP bridge and some BIOSes incorrectly handlejkim2005-11-142-32/+144
| | | | | the bridge. Therefore, we give the same treatment as we did for nForce3-250 and ULi chipsets. VIA AGPv3 code was copied from agp_via.c.
* Listen to jhb, and remove bogus claim of support of DE425.wilko2005-11-141-1/+1
| | | | Obtained from: jhb
* In ktr_getrequest(), acquire ktrace_mtx earlier -- while the racerwatson2005-11-141-2/+3
| | | | | | | | | | currently present is minor and offers no real semantic issues, it also doesn't make sense since an earlier lockless check has already occurred. Also hold the mutex longer, over a manipulation of per-process ktrace state, which requires synchronization. MFC after: 1 month Pointed out by: jhb
* Update my email address, so people know where the exact /ariff2005-11-143-7/+7
| | | | | | proper / correct place to bug me. Approved by: netchild (mentor)
* Add Intel ICH7.joel2005-11-141-1/+3
|
* From luigi:ariff2005-11-141-35/+71
| | | | | | | | | | | | | This one simply tries to simplify the logic to select the buffer sizes. I am not sure it is necessary but the code seems a bit more readable to me. And at least i have tried to document how the buffer sizes are computed. Thanks to luigi for deciphering one of the most cryptic part of sound driver. Submitted by: luigi Approved by: netchild (mentor)
* From luigi:ariff2005-11-141-2/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | In SNDCTL_DSP_SETFRAGMENT, if you specify both read and write channels, the existing code first acts on the read channel, but as a side effect it updates the arguments (maxfrags, fragsz) passed by the caller according to acceptable values for the read channel, and then uses the modified values to act on the write channel. The problem with this approach is that, given a (maxfrags, fragsz) user-specified value, the actual values computed by the read and write channels may differ: e.g. the read channel might want to allocate more fragments than what the user specified because it has no side-effects on the delay and it helps in case of slow readers, whereas the write channel needs to use as few fragments as possible to keep the audio latency low (very important with telephony apps). This patch stores the values computed by the read channel into temproary variables so the write channel will use the actual arguments of the ioctl. This patch is very helpful with telephony apps such as asterisk. Submitted by: luigi Approved by: netchild (mentor)
* Unlike the rest of the world, NDIS code can access "structru2005-11-141-1/+2
| | | | | ifnet" before is has been fully initialized by if_attach(). Account for that to avoid a null pointer dereference.
* ac97.c:ariff2005-11-142-2/+3
| | | | | | | | | | | | | | - Added new codec id for CX20468-21 and VIA1617A. Submitted by: Chen Lihong <lihong.chen@gmail.com> - Re-enable SOUND_MIXER_IGAIN, but set the default level as 0 (mute) Suggested by: luigi mixer.c: - Set default value for SOUND_MIXER_IGAIN as 0 (mute) to avoid feedback problems on some laptops (was disabled by jhb during ac97.c revision 1.42). Approved by: netchild (mentor)
* Fix a long standing unhandled interrupt bug which can causeariff2005-11-141-2/+2
| | | | | | | | | erratic system slowdown (beaten to a pulp) and possible panic. This issue has bugged me for as long as I could remember, until I realized that it is possible for register base offset to hold zero value which is definitely a "FALSE". Approved by: netchild (mentor)
* - Added few more Intel HDA ids (ICH 6/7) which does have backwardariff2005-11-141-104/+154
| | | | | | | | | | | | | | | | | | | | | | | | | | compatible AC97 codec. - As the driver supports so many variants, create a table ids for ease of probing and maintenance. Submitted by: yongari Reviewed/Tested by: multimedia@ - From luigi: The code to compute fragment sizes in the ich driver almost invariably ends up using the full buffer available, no matter how the user specifies fragment size and number. With audio telephony (8khz, 16bit-stereo) and the 16k buffer size this results in an unbearable 500ms delay. This patch makes sure that we never use more than 4 fragments, (i don't think we need more unless there are huge interrupt servicing latencies), and obey to the requested fragment size, so that latency is acceptable. Based on this (and after much regression tests), I can conclude that this driver works best with 2 fragments, thus solving various long standing issues of ICH driver not capable to flush or play short files perfectly. Suggested by: luigi (the idea of smaller fragments) - MPSAFE conversion. Approved by: netchild (mentor)
* Use both (enabled by default) DAC1 and DAC2 to provide 2ariff2005-11-141-105/+473
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | distinct hardware playback channels. DAC configuration can be accessed through kernel hint - hint.pcm.<unit>.dac="val" with following possible values: 0 = Enable both DACs (default) 1 = Enable single DAC (DAC1) 2 = Enable single DAC (DAC2) 3 = Enable both DACs, swap position (DAC2 comes first instead of DAC1) Special case for ES1370: Unlike ES1371,2,3/CT5880, volume for each DAC 1 and 2 can be controlled indepedently (synth for DAC1, pcm for DAC2). It is possible that user will confuse by this behaviour, since both DACs are enabled by default. Thus, provide a knob through sysctl hw.snd.pcm<unit>.single_pcm_mixer: 0 = each DACs will be controlled separately (synth/pcm). 1 = combine both DACs volume mixer controller into a single "pcm" (default) As a side note, fixed rate operation (provided by previous commit) is not a mandatory if the configuration space does not involve DAC2 (perhaps disabled by user through the above kernel hint). Unlike DAC2, DAC1 has its own register / control space, not affected by the speed settings of ADC. Tested by: multimedia@ Approved by: netchild (mentor)
* Fix left/right channel mixed-up during recording by splitting recdevariff2005-11-141-13/+22
| | | | | | | mask to recdev_l and recdev_r, since each have its own unique mask. Submitted by: Watanabe Kazuhiro <CQG00620@nifty.ne.jp> Approved by: netchild (mentor)
* In build_iovec(), if passed in len is -1, check to see ifrodrigc2005-11-141-3/+6
| | | | | | val is NULL before doing strlen() to calculate new len. Submitted by: maxim
* o Style: restore tab indentation mangled in the previous delta.maxim2005-11-141-5/+5
|
* Eliminate coredump problem introduced by last commit.rodrigc2005-11-141-2/+8
| | | | Noticed by: Guido van Rooij <guido at gvr dot org>
* Use the new syntax for GENERIC.des2005-11-141-1/+1
|
* Build a PAE kernel if a PAE config exists.des2005-11-141-0/+1
|
* Add support for the += operator, which appends to a multiple-value variable.des2005-11-142-6/+19
|
* Add support for building other kernels than LINT and GENERIC.des2005-11-142-15/+39
|
* Unbreak for !INET6 case.ru2005-11-141-1/+1
|
* Eliminate build breakage due to warnings about const.rodrigc2005-11-141-3/+3
|
* Reuse delete_and_clear() template helper.bland2005-11-141-5/+1
| | | | Approved by: imp
* Fix misspelling.imp2005-11-141-2/+2
| | | | Submitted by: thompsa
* Provide a dummy NO_XBOX option that lives in opt_xbox.h for pc98.imp2005-11-144-6/+4
| | | | This allows us to eliminate a three ifdef PC98 instances.
* Add xbox associated options/devices to LINT.imp2005-11-141-0/+17
| | | | Submitted by: Rink P.W. Springer
* Update to match geom_gpt:1.35marcel2005-11-131-3/+5
| | | | | | | o Change the result of gctl(001) now that a bogus verb still requires a valid geom, o Insert gctl(024) to test for an appropriate error when a bogus verb is given that does have a proper geom parameter.
* o Slightly refactor the ctlreq code to maximize code sharing betweenmarcel2005-11-131-67/+127
| | | | | | | | | | | | | | verbs. Only the create verb operates on a provider. All other verbs operate on a GPT geom. Also, the GPT entry oriented verbs require a non-downgraded GPT. o Have all verbs take an optional flags parameter. The flags parameter is a string of single-letter flags. The typical use of these flags is to enable certain behaviour in support fo the gpt(8) tool. o Add dummy implementations for the destroy and recover verbs. This change causes test 2 of the GPT regression test suite to fail. The presence of a geom parameter is now required even for unknown verbs.
OpenPOWER on IntegriCloud