summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Implement a rudimentary suspend/resume methods for PCI P2P bridge.jkim2009-12-102-57/+200
| | | | Reviewed by: jhb, imp
* Fix the posix_memalign() changes in r196861 to actually return a NULL pointerjasone2009-12-101-0/+1
| | | | | | as intended. PR: standards/138307
* Add my birthday.gavin2009-12-091-0/+1
| | | | Approved by: ed (mentor)
* For some buses, devices may have active resources assigned even though theyjhb2009-12-093-64/+188
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | are not allocated by the device driver. These resources should still appear allocated from the system's perspective so that their assigned ranges are not reused by other resource requests. The PCI bus driver has used a hack to effect this for a while now where it uses rman_set_device() to assign devices to the PCI bus when they are first encountered and later assigns them to the actual device when a driver allocates a BAR. A few downsides of this approach is that it results in somewhat confusing devinfo -r output as well as not being very easily portable to other bus drivers. This commit adds generic support for "reserved" resources to the resource list API used by many bus drivers to manage the resources of child devices. A resource may be reserved via resource_list_reserve(). This will allocate the resource from the bus' parent without activating it. resource_list_alloc() recognizes an attempt to allocate a reserved resource. When this happens it activates the resource (if requested) and then returns the reserved resource. Similarly, when a reserved resource is released via resource_list_release(), it is deactivated (if it is active) and the resource is then marked reserved again, but is left allocated from the bus' parent. To completely remove a reserved resource, a bus driver may use resource_list_unreserve(). A bus driver may use resource_list_busy() to determine if a reserved resource is allocated by a child device or if it can be unreserved. The PCI bus driver has been changed to use this framework instead of abusing rman_set_device() to keep track of reserved vs allocated resources. Submitted by: imp (an older version many moons ago) MFC after: 1 month
* Add myself, and show ed@ as my mentor.gavin2009-12-091-0/+2
| | | | Approved by: ed (mentor)
* Add missing relation between philip and I.ed2009-12-091-0/+1
| | | | It seems I forgot this when I became a committer last year.
* Fix a confusing typo in the EDD packet structure used in gptboot andjhb2009-12-092-6/+6
| | | | | | | | gptzfsboot. I got the segment and offset fields reversed in the structure, but I also succeeded in crossing the assignments so the actual EDD packet ended up correct. MFC after: 1 week
* - Port bios_getmem() from libi386 to {gpt,}zfsboot() and use it tojhb2009-12-092-21/+112
| | | | | | | | | | safely allocate a heap region above 1MB. This enables {gpt,}zfsboot() to allocate much larger buffers than before. - Use a larger buffer (1MB instead of 128K) for temporary ZFS buffers. This allows more reliable reading of compressed files in a raidz/raidz2 pool. Submitted by: Matt Reimer mattjreimer of gmail MFC after: 1 week
* Fix hardware issue with FTDI chips: avoid sending a zero length packet due tothompsa2009-12-091-1/+1
| | | | | | | hardware sending garbage on ZLPs. Reported by: Corey Smith Submitted by: HPS
* Fix dwSignature for NCM mode and add extra debug output.thompsa2009-12-091-6/+17
| | | | Submitted by: HPS
* Add new device ids.thompsa2009-12-093-0/+4
| | | | | PR: usb/140951, usb/140923 Submitted by: Romain Tartiere, Brett Glass
* Correct name, 82801IJ -> 82801JIthompsa2009-12-092-8/+8
| | | | Submitted by: mitya_cabletv.dp.ua
* If the ID byte is non zero then we allow descriptors having multiple sizes.thompsa2009-12-091-3/+12
| | | | | Submitted by: HPS Reported by: daichi
* Port lastlogin(1) to libulog.ed2009-12-092-43/+21
| | | | | Just use ulog_getutxuser() to obtain lastlog records or ulog_getutxent() to browse through all of them.
* Don't let sysinstall depend on <utmp.h>.ed2009-12-091-4/+3
| | | | | Looking at the other entries, I suspect we must also reserve one terminating byte, so I'm using UNAME_FIELD_LEN - 1, not UNAME_FIELD_LEN.
* when calling ldd, use the cross libraries and not the host versionluigi2009-12-091-4/+4
| | | | MFC after: 3 days
* use default HZluigi2009-12-091-1/+1
|
* add -lulog, the program "less" and a commentluigi2009-12-091-1/+4
|
* Clear result before requesting XPT_PATH_INQ.mav2009-12-091-0/+1
| | | | Many SIMs doesn't fill maxio field yet.
* Increase Max Read Request Size for PCIe chips from 512 to 1024 bytes.mav2009-12-091-1/+14
| | | | It gives those beasts additional 10% of write bandwidth.
* The default balance algorithm has changed from "split" toru2009-12-091-2/+2
| | | | (the improved version of) "load".
* make PV core dump actually dump memory - still need to fix program header ↵kmacy2009-12-092-0/+7
| | | | initialization
* Allow using IPv6 in nfsrvd_sentcache() callback.delphij2009-12-081-2/+3
| | | | | | | PR: kern/141289 Submitted by: Petr Lampa <lampa fit vutbr cz> Approved by: rmacklem MFC after: 1 week
* Change gmirror default balance algorithm from "split" to "load".mav2009-12-081-1/+1
| | | | | | | | | | | "split" is very ineffective for devices with rotating media as HDDs. To be effective, it needs that transfer time reduction due to block splitting was bigger then access time increase due to non-sequential access. For modern HDDs I was able to reproduce it only with read sizes of 2MB and above, which is almost not applicable in real life. "load" algorithm same time is more universal and effective now. Reviewed by: pjd
* Simplify a macro not to generate unncessary symbols.jkim2009-12-081-14/+1
|
* Fix the build.mav2009-12-081-2/+13
|
* sem_init(3): document process shared semaphores and their restrictionsjilles2009-12-081-18/+9
|
* Don't add VAPPEND if the file is not being opened for writing. Note that thistrasz2009-12-082-2/+2
| | | | | | | only affects cases where open(2) is being used improperly - i.e. when the user specifies O_APPEND without O_WRONLY or O_RDWR. Reviewed by: rwatson
* Add additional checks of the kernel stack addresses in order tomarius2009-12-082-6/+22
| | | | | | ensure we don't overrun the end of the call chain. MFC after: 1 week
* What we have in base system is actually OpenBSD 4.5's netcat,delphij2009-12-081-1/+1
| | | | update this file to reflect the fact.
* Remove phantom line of code that somehow slippedjfv2009-12-081-1/+0
| | | | into the checkin.
* Create sysctl node(dev.bge.%d.focred_collapse) instead ofyongari2009-12-082-21/+25
| | | | | | | | | hw.bge.forced_collapse. hw.bge.forced_collapse affects all bge(4) controllers on system which may not desirable behavior of the sysctl node. Also allow the sysctl node could be modified at any time. Reviewed by: bde (initial version)
* Add ID for NetMos NM9820 Serial Port chip, found on CardBus serial adapter.mav2009-12-081-0/+1
|
* MFi386: revision 200219nyan2009-12-082-8/+25
| | | | | | | Improve the algorithm the loader uses to choose a memory range for its heap when using a range above 1MB. MFC after: 1 week
* MFi386: Use real mode instead of v86 mode.nyan2009-12-081-410/+361
| | | | MFC after: 1 week
* MFi386: revision 200216nyan2009-12-082-3/+2
| | | | Various small whitespace and style fixes.
* - Try pre-allocating all FIBs upfront. Previously we tried pre-allocatingjkim2009-12-083-10/+6
| | | | | | | | | | | 128 FIBs first and allocated more later if necessary. Remove now unused definitions from the header file[1]. - Force sequential bus scanning. It seems parallel scanning is in fact slower and causes more harm than good[1]. Adjust a comment to reflect that. PR: kern/141269 Submitted by: Alexander Sack (asack at niksun dot com)[1] Reviewed by: scottl
* Partially revert r200228. For mini RCB case, bge(4) still have toyongari2009-12-081-7/+5
| | | | | | | disable mini ring withtout regard to mini ring support. Reported by: marcel Tested by: marcel
* Resync with Intel versions of both the em and igbjfv2009-12-0822-1798/+3148
| | | | | | | | | | | drivers. These add new hardware support, most importantly the pch (i5 chipset) in the em driver. Also, both drivers now have the simplified (and I hope improved) watchdog code. The igb driver uses the new RX cleanup that I first implemented in ixgbe. em - version 6.9.24 igb - version 1.8.4
* Fix typo in commentrpaulo2009-12-081-1/+1
| | | | Submitted by: Paul B Mahol <onemda at gmail.com>
* Improve response to multi-touch taps.rpaulo2009-12-081-48/+117
| | | | Submitted by: Rohit Grover <rgrover1 at gmail.com>
* In exception_save, write-back ar.rnat after switching the backing-marcel2009-12-081-14/+13
| | | | | | | store. Writing to ar.bspstore is defined to leave ar.rnat undefined. PR: ia64/120315 MFC after: 3 days
* Update driver to Intel version 2.0.7:jfv2009-12-0712-1269/+2510
| | | | | | | | | | | | | | | | | | | | | This adds new feature support for the 82599, a hardware assist to LRO, doing this required a large revamp to the RX cleanup code because the descriptor ring may not be processed out of order, this necessitated the elimination of global pointers. Additionally, the RX routine now does not refresh mbufs on every descriptor, rather it will do a range, and then update the hardware pointer at that time. These are performance oriented changes. The TX side now has a cleaner simpler watchdog algorithm as well, in TX cleanup a read of ticks is stored, that can then be compared in local_timer to determine if there is a hang. Various other cleanups along the way, thanks to all who have provided input and testing.
* Revert r200231. It was already taken cared by jhb long ago.jkim2009-12-071-16/+3
| | | | | Pointed out by: jhb Pointy hat: jkim
* Make mfi(4) little bit less chatty.jkim2009-12-071-3/+16
|
* Add support for the NetMos NM9865 family of Serial/Parallel ports.marcel2009-12-072-3/+40
| | | | | Obtained from: NetMos MCS9865 v1.0.0.1 driver MFC after: 3 days
* Don't access jumbo frame related registers if controller lacks theyongari2009-12-071-8/+14
| | | | | | | | | feature. These registers are reserved on controllers that have no support for jumbo frame. Only BCM5700 has mini ring so do not poke mini ring related registers if controller is not BCM5700. Reviewed by: marius
* Remove PHY isolate/power down code in bge_stop(). The isolationyongari2009-12-071-27/+0
| | | | | | | | | | | handler in brgphy(4) does not exist and brgphy(4) just resets the PHY and returns EINVAL as it has no isolation handler. I also agree on Marius's opinion that stop handler of every NIC driver seems to be the wrong place for implementing PHY isolate/power down. If we need PHY isolate/power down it should be implemented in brgphy(4) and users should administratively down the PHY. Reviewed by: marius
* Explicitly acknowledge MSI completion, as required by SiI3124 datasheet.mav2009-12-072-3/+14
| | | | | | It makes MSI working there. Later (and cheaper) PCIe chips (3132/3531) still randomly crashing system in few seconds of high MSI rates, generating something inaporopriate, like NMI or "Fatal trap 30".
* Improve the algorithm the loader uses to choose a memory range for itsjhb2009-12-073-8/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | heap when using a range above 1MB. Previously the loader would always use the last 3MB in the first memory range above 1MB for the heap. However, this memory range is also where the kernel and any modules are loaded. If this memory range is "small", then using the high 3MB for the heap may not leave enough room for the kernel and modules. Now the loader will use any range below 4GB for the heap, and the logic to choose the "high" heap region has moved into biosmem.c. It sets two variables that the loader can use for a high heap if it desires. When a high heap is enabled (BZIP2, FireWire, GPT, or ZFS), then the following memory ranges are preferred for the heap in order from best to worst: - The largest memory region in the SMAP with a start address greater than 1MB. The memory region must be at least 3MB in length. This leaves the region starting at 1MB purely for use by the kernel and modules. - The last 3MB of the memory region starting at 1MB if it is at least 3MB in size. This matches the current behavior except that the current loader would break horribly if the first region was not at least 3MB in size. - The memory range from the end of the loader up to the 640k window. This is the range the loader uses when none of the high-heap-requesting options are enabled. Tested by: hrs MFC after: 1 week
OpenPOWER on IntegriCloud