summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Fix typo: s/LIBSERACHPATH/LIBSEARCHPATH/gmarcel2011-03-219-11/+11
|
* Change region 4 to be part of the kernel. This serves 2 purposes:marcel2011-03-215-46/+40
| | | | | | | | 1. The PBVM is in region 4, so if we want to make use of it, we need region 4 freed up. 2. Region 4 and above cannot be represented by an off_t by virtue of that type being signed. This is problematic for truss(1), ktrace(1) and other such programs.
* sh(1): Describe subshell environment, command substitution more correctly.jilles2011-03-201-7/+19
| | | | | | | | | | | POSIX does not require the shell to fork for a subshell environment, and we use that possibility in various ways (command substitutions with a single command and most subshells that are the final command of a shell process). Therefore do not tie subshells to forking in the man page. Command substitutions with expansions are a bit strange, causing a fork for $(...$(($x))...) because $x might expand to y=2; they will probably be changed later but this is how they work now.
* Use 'list scan' in favor of 'scan', as 'scan' has a different purpose.gjb2011-03-201-1/+1
| | | | | Pointed out by: bschmidt MFC after: 1 day
* Retire opt_ffs_broken_fixme.h.kib2011-03-205-8/+7
| | | | | | | | Instead of directly calling ffs_snapgone(), use UFS_SNAPGONE() with usual layering. Requested by: bde MFC after: 1 week
* index(3): Mention that index/rindex are deprecated and not specified byjilles2011-03-201-1/+14
| | | | | | POSIX.1-2008. MFC after: 1 week
* Disable a check I added a while ago to ensure the initial NF cal completed.adrian2011-03-201-5/+24
| | | | | | | | | | Give it a good go (32 attempts) and then print out a warning that's going to occur whether HAL debugging is enabled or not. Then don't abort the radio setup; just continue merrily along. This should fix the issue that users were having where scanning would occasionally fail on the active channel, causing traffic to cease until the radio scanned again.
* Update a comment. The sending process has not mapped the buffer pagesalc2011-03-201-3/+3
| | | | | | since before r127501. Strictly speaking, the buffer pages are not "wired". They remain in the paging queues. However, they are pinned in memory using vm_page_hold().
* Add a file with some remarks for setting up a zfs boot environmentmr2011-03-201-0/+35
|
* - Add script for preparing disks in GPT/ZFS boot environmentmr2011-03-202-0/+64
| | | | - Add merge script for integrating amd64 slice into i386 disk image
* Cave in and disable the ADC DC gain/offset calibrations if they'readrian2011-03-201-3/+6
| | | | | | | | | | | | | | not needed. These calibrations are only applicable if the chip operating mode engages both interleaved RX ADCs (ie, it's compensating for the differences in DC gain and DC offset -between- the two ADCs.) Otherwise the chip reads values of 0x0 for the secondary ADC (as I guess it's not enabled here) and thus writes potentially bogus info into the chip. I've tested this on the AR9160 and AR9280; both behave themselves in 11g mode with these calibrations disabled.
* * Remove a not-needed check in the AR5416+ caseadrian2011-03-201-6/+6
| | | | | * Restore the chip default of the DCU backoff threshold to 0x2, mirroring what ath9k does.
* Bring over a copy of the AR5212 TX queue reset and setup routines, in ↵adrian2011-03-203-0/+344
| | | | | | | | | preparation for fixing them based on the ath9k related TXQ fixes. I've done this so people can go over the history of the diffs to the original AR5212 routines (which AR5416 and later chips use) to see what's changed.
* Remove dead code.dchagin2011-03-201-17/+0
| | | | MFC after: 1 Week
* Add a PSPOLL queue type, in preparation for (eventually) portingadrian2011-03-201-0/+1
| | | | | over the TX queue setup code from ath9k for the AR5416 and later chips.
* Add support for checking out ports and doc trees from a CVS repository,nwhitehorn2011-03-191-7/+17
| | | | | | in addition to CVSUP, and add support for alternate SVN roots for src. Requested by: jhb
* Correct broadcast frame handling. Setting bit6 of MCR0 registeryongari2011-03-192-3/+4
| | | | | | | | | enables broadcast filtering. Make sure to clear the bit to receive broadcast frames. While I'm here rename the bit definition to reflect reality. Reported by: brad@OpenBSD MFC after: 1 week
* ouch, newrt is used on the return path, my fault.dchagin2011-03-191-1/+1
| | | | | | Partialy revert the previous change. MFC after: 1 Week.
* - Make a panic message better reflect the actual problem.marius2011-03-191-13/+15
| | | | | | - A closer inspection of the OpenSolaris code indicates the block store workaround is only necessary in case of BUS_DMASYNC_POSTREAD. - Mark some unused parameters as such.
* A bit rearranged rtalloc1_fib() code.dchagin2011-03-191-6/+6
| | | | | | | Initialize a variable when it is really needed. To avoid code duplication move the miss label to line up and jump on it. MFC after: 1 Week
* On Serengeti-class machines the OFW root isn't the parent of the CPUmarius2011-03-191-2/+2
| | | | nodes.
* Remove spl(9) remnants.glebius2011-03-191-3/+1
|
* In case reading PCIR_MINGNT fails don't use it for calculating themarius2011-03-191-1/+1
| | | | | latency. This is more or less a theoretical problem though as it typically indicates way bigger problems.
* Properly check for an IPv4 socket after r219579.bz2011-03-191-2/+2
| | | | | | | | | | | | | | | In some cases as udp6_connect() without an earlier bind(2) to an address, v4-mapped scokets allowed and a non mapped destination address, we can end up here with both v4 and v6 indicated: inp_vflag = (INP_IPV4|INP_IPV6|INP_IPV6PROTO) In that case however laddrp is NULL as the IPv6 path does not pass in a copy currently. Reported by: Pawel Worach (pawel.worach gmail.com) Tested by: Pawel Worach (pawel.worach gmail.com) MFC after: 6 days X-MFC with: r219579
* Remove a now unused variable.dchagin2011-03-191-2/+1
| | | | MFC after: 1 Week
* For now remove options FLOWTABLE from the remaining GENERIC kernelbz2011-03-194-5/+0
| | | | | | | | | | | | | | | configurations and make it opt-in for those who want it. LINT will still build it. While it may be a perfect win in some scenarios, it still troubles users (see PRs) in general cases. In addition we are still allocating resources even if disabled by sysctl and still leak arp/nd6 entries in case of interface destruction. Discussed with: qingli (2010-11-24, just never executed) Discussed with: juli (OCTEON1) PR: kern/148018, kern/155604, kern/144917, kern/146792 MFC after: 2 weeks
* Add in the channel survey data structures. These will be filled outadrian2011-03-191-0/+27
| | | | by the HAL at some point in the future.
* Reserve a new diagnostic code for the channel survey code I'll add soon.adrian2011-03-191-0/+1
|
* Make sure that the AR_MISC_MODE value from the initvals are properly respected.adrian2011-03-194-4/+4
| | | | | | | | | | | | | | | | | | | | | This commit really is "fix the OFDM duration calculation to match reality when running in 802.11g mode." The AR5212 init vals set AR_MISC_MODE to 0x0 and all the bits that can be set are set through code. The AR5416 and later initvals set AR_MISC_MODE to various other values (with the AR5212 AR_MISC_MODE options cleared), which include AR_PCU_CCK_SIFS_MODE . This adds 6uS to SIFS on non-CCK frames when transmitting. This fixes the issue where _DATA_ 802.11g OFDM frames were being TX'ed with the ACK duration set to 38uS, not 44uS as on the AR5212 (and other devices.) The AR5212 TX pathway obeys the software-programmed duration field in the packet, but the 11n TX pathway overrides that with a hardware-calculated duration. This was getting it wrong because of the above AR_MISC_MODE setting. I've verified that 11g data OFDM frames are now being TXed with the correct ACK+SIFS duration programmed in.
* Use the HAL method rather than directly calling ar5212ResetTxQueue().adrian2011-03-191-1/+1
| | | | | | Since ath9k does some slightly different bit fiddling when setting up the TX queues, it may that the TX queue setup/reset functions will need overriding later on.
* Add debugging messages to the AR5416 ANI code that's found in the AR5212 ANI ↵adrian2011-03-191-0/+6
| | | | code.
* A cut and paste here was wrong also.jfv2011-03-191-1/+1
|
* Correct broken definejfv2011-03-191-1/+1
|
* - Build disk image (for USB sticks) and iso imagemr2011-03-183-11/+29
| | | | | | | - Change name to reflect this - Install all kernel modules - Choose image size that i386 and amd64 can be combined into one image - Mount tmpfs over /boot/zfs for zpool imports
* o Move the IVT and supporting functions to the front of the textmarcel2011-03-184-55/+100
| | | | | | | segment so that it's always mapped by the loader. o Change the alternate fault handlers to account for PBVM. Since currently the region is handled by the VHPT, no alternate faults will be generated for it.
* Remove inclusion of unneeded bootinfo.h header.marcel2011-03-181-1/+0
|
* This delta updates the em driver to version 7.2.2 which hasjfv2011-03-189-341/+404
| | | | | | | | | | | | | been undergoing test for some weeks. This improves the RX mbuf handling to avoid system hang due to depletion. Thanks to all those who have been testing the code, and to Beezar Liu for the design changes. Next the igb driver is updated for similar RX changes, but also to add new features support for our upcoming i350 family of adapters. MFC after a week
* Use VM_MAXUSER_ADDRESS rather than VM_MAX_ADDRESS when we talk aboutmarcel2011-03-186-26/+26
| | | | | the bounds of user space. Redefine VM_MAX_ADDRESS as ~0UL, even though it's not used anywhere in the source tree.
* Partially revert previous change. Drop the quirk to disable MSI for HTjhb2011-03-181-19/+2
| | | | | | | | chipsets that do not have an HT slave at 0:0:0:0. The Linux quirk is actually specific to Nvidia chipsets and the check I had added was in the wrong place. Prodded by: nathanw
* Use resolvconf(8) to update /etc/resolv.conf.ume2011-03-181-25/+46
| | | | | If you don't want to use resolvconf(8) to update /etc/resolv.conf, you can put resolvconf_enable="NO" into /etc/dhclient-enter-hooks.
* Add resolvconf(8) which manages resolv.conf.ume2011-03-183-0/+40
|
* Fix a few issues with HyperTransport devices and MSI interrupts:jhb2011-03-182-4/+44
| | | | | | | | | | | | | | | - Always enable the HyperTransport MSI mapping window for HyperTransport to PCI bridges (these show up as HyperTransport slave devices). The mapping windows in PCI-PCI bridges are enabled by existing code in the PCI-PCI bridge driver as MSI requests propagate up the device tree, but Host-PCI bridges don't really show up in that tree. - If the PCI device at domain 0 bus 0 slot 0 function 0 is not a HyperTransport device, then blacklist MSI on any other HT devices in the system. Linux has a similar quirk. PR: kern/155442 Tested by: Zack Dannar zdannar of gmail MFC after: 1 week
* Import openresolv from vendor branch, actually.ume2011-03-1812-0/+1727
|\ | | | | | | Helped by: jhb
| * Import openresolv-3.4.1.ume2011-03-1812-0/+1727
|
* Remove contrib/openresolv.ume2011-03-180-0/+0
| | | | Helped by: jhb
* Add myself to calendar.freebsd.sbz2011-03-181-0/+1
| | | | Approved by: miwi@ (mentor)
* Add an entry for myself to committers-ports.dot.sbz2011-03-181-0/+3
| | | | Approved by: miwi@ (mentor)
* In vm_daemon(), when iterating over all processes in the system, skip thosetrasz2011-03-181-0/+4
| | | | | | | | | | | which are not yet fully initialized (i.e. ones with p_state == PRS_NEW). Without it, we could panic in _thread_lock_flags(). Note that there may be other instances of FOREACH_PROC_IN_SYSTEM() that require similar fix. Reported by: pho, keramida Discussed with: kib
* Formatting fix.gjb2011-03-171-1/+1
| | | | | Submitted by: arundel (via doc@) MFC after: 3 days
* Preserve errno in an error case.jhb2011-03-171-1/+2
| | | | Submitted by: gcooper
OpenPOWER on IntegriCloud