summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Move all sound related scripts to its own 'sound' subdir.ariff2009-06-106-18/+18
| | | | Suggested by: jmallett
* Oops, fix directory name.yongari2009-06-101-1/+1
|
* Move machine dependant AFMT_* definition from sound.hariff2009-06-102-36/+29
| | | | to global soundcard.h .
* Marvell 88W8363 driver and associated firmwaresam2009-06-103-0/+242
|
* iwn does not require a license acksam2009-06-101-22/+1
|
* Fix typo.yongari2009-06-101-1/+1
|
* Add alc(4) man page and hook up ale(4) to the build.yongari2009-06-105-3/+169
| | | | Also add Xr to appropriate man pages.
* Add alc(4) to the list of supported network interface.yongari2009-06-101-0/+1
|
* Add alc(4), a driver for Atheros AR8131/AR8132 PCIe ethernetyongari2009-06-1010-0/+4732
| | | | | | | | | | | | | | | | | | | | | | | | | | | | controller. These controllers are also known as L1C(AR8131) and L2C(AR8132) respectively. These controllers resembles the first generation controller L1 but usage of different descriptor format and new register mappings over L1 register space requires a new driver. There are a couple of registers I still don't understand but the driver seems to have no critical issues for performance and stability. Currently alc(4) supports the following hardware features. o MSI o TCP Segmentation offload o Hardware VLAN tag insertion/stripping o Tx/Rx interrupt moderation o Hardware statistics counters(dev.alc.%d.stats) o Jumbo frame o WOL AR8131/AR8132 also supports Tx checksum offloading but I disabled it due to stability issues. I'm not sure this comes from broken sample boards or hardware bugs. If you know your controller works without problems you can still enable it. The controller has a silicon bug for Rx checksum offloading, so the feature was not implemented. I'd like to say big thanks to Atheros. Atheros kindly sent sample boards to me and answered several questions I had. HW donated by: Atheros Communications, Inc.
* As far as I can tell systems that have less than 4GB are more often hurtkmacy2009-06-102-0/+19
| | | | | | | by prefetched than helped. On i386 systems and systems with less than 4GB, prefetch is now disabled by default. I've added a prefetch enable tunable, to enable prefetching for those systems. The prefetch disable tunable will continue to unconditionally disable prefetching.
* Controller will dma SCB command status for a given command andyongari2009-06-101-13/+14
| | | | | | | | | driver should read updated status back after issuing a SCB command. To send a command to controller and read updated status back, driver should synchronize both memory read and write operations with device. Fix bus_dmamap_sync operation specifier used in fxp_dma_wait() by adding both memory read and memory write operations.
* We can actually remove devclass_find_driver.imp2009-06-101-21/+0
|
* These are no longer public, so remove the man page.imp2009-06-092-61/+0
|
* As discussed on arch@, restireimp2009-06-092-8/+4
| | | | | devclass_{add,delete,find,quiesce}_driver. They aren't needed or used and complicate locking newbus.
* ja_JP: AM/PM date format should be localized.edwin2009-06-092-8/+4
| | | | | | | | ja_JP.eucJP and ja_JP.SJIS fixes. PR: conf/63527 Submitted by: Yukihiro Nakai <nakai@gnome.gr.jp> MFC after: 1 week
* Fix LC_NUMERIC and LC_MONETARY for de_CH localeedwin2009-06-093-8/+21
| | | | | | | | | | | | | | | With the de_CH (swiss german) locale, numbers should look like this: numbers: 1'234.45 monetary values: Fr. 1'234.45 Previously, the thousands separator was missing for numbers, and "." for monetary values, and "," was incorrectly used as decimal point. PR: conf/75502 Submitted by: Benjamin Lutz <benlutz@datacomm.ch> MFC after: 1 week
* Fix some overflow errors: a signed allocation and an insufficiantjamie2009-06-091-4/+12
| | | | | | | | array size. Reported by: pho Tested by: pho Approved by: bz (mentor)
* opt in to flowtable on i386/amd64kmacy2009-06-092-0/+2
|
* revert to opt-in flowtablekmacy2009-06-094-6/+5
|
* Add opt_inet.h back lost with r190872.bz2009-06-091-0/+1
| | | | | This will bring back improved IPv4 SIOCSIFADDR ioctl handling not re-initializing the interface if avoidable.
* Sync struct ng_ipfw_tag description with sources.oleg2009-06-091-2/+3
| | | | Submitted by: Mikolaj Golub
* add explanatory header licensekmacy2009-06-091-0/+36
|
* Close long existed race with net.inet.ip.fw.one_pass = 0:oleg2009-06-099-105/+89
| | | | | | | | | | | | | | If packet leaves ipfw to other kernel subsystem (dummynet, netgraph, etc) it carries pointer to matching ipfw rule. If this packet then reinjected back to ipfw, ruleset processing starts from that rule. If rule was deleted meanwhile, due to existed race condition panic was possible (as well as other odd effects like parsing rules in 'reap list'). P.S. this commit changes ABI so userland ipfw related binaries should be recompiled. MFC after: 1 month Tested by: Mikolaj Golub
* make flowtable opt-outkmacy2009-06-094-4/+5
|
* remove flowtable from DEFAULTSkmacy2009-06-092-3/+0
|
* move jenkins hash to its own header in libkernkmacy2009-06-092-145/+151
|
* 1. Update the message that prints out for -U when the mtree database doesdougb2009-06-091-7/+7
| | | | | | | | | | | not exist to let the user know that it will be created for the next run. 2. Delete more stuff we're not going to use from the temproot prior to creating the mtree database to dramatically reduce its size (162K -> 37K). 3. We've been deleting the zero-size files from temproot for a long time now, so remove the spurious "-size +0" from the find command in the comparison loop, and remove what is now a really stale comment.
* Add part of NFSv4 ACL kernel support code that is required for the upcomingtrasz2009-06-091-0/+579
| | | | | | | libc changes to work. Not connected to the kernel build yet; for now, it will be compiled into libc. Reviewed by: rwatson
* - add drbr routines for accessing #qentries and conditionally dequeueingkmacy2009-06-093-20/+67
| | | | - track bytes enqueued in buf_ring
* Pass the previously returned IRQ back to arm_get_next_irq() so thatmarcel2009-06-099-10/+10
| | | | | | | | | the implementation can guarantee forward progress in the event of a stuck interrupt or interrupt storm. This is especially critical for fast interrupt handlers, as they can cause a hard hang in that case. When first called, arm_get_next_irq() is passed -1. Obtained from: Juniper Networks, Inc.
* Disable interrupts to allow booting on firmware (e.g. U-Boot) thatmarcel2009-06-091-0/+5
| | | | | | has interrupts enabled and active. Obtained from: Juniper Networks, Inc.
* Eliminate an instance of VM_PROT_READ_IS_EXEC that I overlooked in r190705.alc2009-06-091-4/+0
|
* protect callouts with the com locksam2009-06-091-5/+7
| | | | Prodded by: jhb
* add missing calls to ieee80211_dfs_attach/detachsam2009-06-091-0/+2
|
* Eliminate an unnecessary restriction on the vm object type fromalc2009-06-091-4/+2
| | | | | | vm_map_pmap_enter(). The immediate effect of this change is that automatic prefaulting by mmap() for small mappings is performed on POSIX shared memory objects just the same as it is on ordinary files.
* Correct ieee80211_gettid:sam2009-06-094-9/+12
| | | | | | | | | | o don't increment extracted tid, this was a vestige of IEEE80211_NONQOS_TID being defined as 0 (w/ real tid's +1) o handle 4-address frames (add IEEE80211_IS_DSTODS to check if an 802.11 header is DSTODS) Submitted by: cbzimmer Reviewed by: avatar
* Since vn_lock() with the LK_RETRY flag never returns an errorrmacklem2009-06-091-7/+11
| | | | | | | | | for FreeBSD-CURRENT, the code that checked for and returned the error was broken. Change it to check for VI_DOOMED set after vn_lock() and return an error for that case. I believe this should only happen for forced dismounts. Approved by: kib (mentor)
* Add support for multiple passes of the device tree during the boot-timejhb2009-06-097-15/+363
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | probe. The current device order is unchanged. This commit just adds the infrastructure and ABI changes so that it is easier to merge later changes into 8.x. - Driver attachments now have an associated pass level. Attachments are not allowed to probe or attach to drivers until the system-wide pass level is >= the attachment's pass level. By default driver attachments use the "last" pass level (BUS_PASS_DEFAULT). Driver's that wish to probe during an earlier pass use EARLY_DRIVER_MODULE() instead of DRIVER_MODULE() which accepts the pass level as an additional parameter. - A new method BUS_NEW_PASS has been added to the bus interface. This method is invoked when the system-wide pass level is changed to kick off a rescan of the device tree so that drivers that have just been made "eligible" can probe and attach. - The bus_generic_new_pass() function provides a default implementation of BUS_NEW_PASS(). It first allows drivers that were just made eligible for this pass to identify new child devices. Then it propogates the rescan to child devices that already have an attached driver by invoking their BUS_NEW_PASS() method. It also reprobes devices without a driver. - BUS_PROBE_NOMATCH() is only invoked for devices that do not have an attached driver after being scanned during the final pass. - The bus_set_pass() function is used during boot to raise the pass level. Currently it is only called once during root_bus_configure() to raise the pass level to BUS_PASS_DEFAULT. This has the effect of probing all devices in a single pass identical to previous behavior. Reviewed by: imp Approved by: re (kib)
* Rework the _BBN handling for Host-PCI bridges. Previously we only trustedjhb2009-06-091-18/+25
| | | | | | | | | | | | | | a _BBN value of 0 if it was for the first bridge encountered since some older systems returned _BBN of 0 for all bridges. However, some newer systems enumerate bridges with non-zero _BBN before bus 0 which is perfectly valid. Handle both cases by trusting the first bridge that has a _BBN of 0 and falling back to reading from non-standard config registers only for subsequent bridges with a _BBN of 0. We also only perform this check for segment (domain) 0. We assume that _BBN is always correct for segments other than 0. Tested by: Josef Moellers josef.moellers at fujitsu MFC after: 1 week
* - Remove an unnecessary memory barrier from an atomic op.jhb2009-06-091-3/+3
| | | | | - Use the per-softc mutex to protect the softc data in the callout routine rather than letting it run without any locks whatsoever.
* Revert r181651, which changed the ABI, and use a temp variable instead.des2009-06-092-2/+4
| | | | Suggested by: attilio
* For now only compile flowtable.c if both options FLOWTABLE and INETbz2009-06-091-1/+1
| | | | | are given. This will also work when we add IPv6 support as for now INET6 depends on INET.
* Each generated file should depend its own generator as well.ariff2009-06-091-3/+3
|
* Remove one INET dependency by calling the generalbz2009-06-091-1/+1
| | | | | | AF agnostic version for doing the routing lookup. Reviewed by: kmacy
* Unbreak the build for amd64 after r193814 using correct variable names.bz2009-06-091-2/+2
|
* Depend on @ machine (_ILINKS) as we do with other modules so that @bz2009-06-091-3/+3
| | | | | is there for parallel (-jN) builds. Ideally beforedepends in kmod.mk should do the right thing but it seems it does not.
* Spacing fixes. No actual change.delphij2009-06-091-2/+2
|
* Style fix.hrs2009-06-091-7/+7
| | | | Submitted by: bz
* When using i8254 as the only kernel timer source:ariff2009-06-092-14/+62
| | | | | | | | | - Interpolate stat/prof clock using clkintr() in a similar fashion to local APIC timer, since statclock usually run slower. - Liberate hardclockintr() from taking the burden of handling both stat and prof clock interrupt. Instead, send IPIs within clkintr() to handle those.
* Use new spelling of the NG_*LEN constants.imp2009-06-094-8/+8
|
OpenPOWER on IntegriCloud