ƒ»m214632 119 807 807 553 140 136 144 141 142 159 129 116 137 240 124 305 227 223 166 141 478 170 164 154 115 115 109 703 479 118 327 153 118 158 186 535 213 173 252 130 810 165 212 289 211 252 122 300 202 600 550 377 358 1635 1635 258 278 278 398 552 552 507 377 1335 159 1335 1506 716 716 512 512 780 780 2521 2521 1660 1660 224 470 1361 1361 737 737 1614 1614 263 416 416 113 337 337 172 174 174 174 239 343 1292 544 557 332 332 312 135 137 116 123 170 472 114 204 484 484 129 475 139 210 329 340 287 K 10 svn:author V 8 bschmidt K 8 svn:date V 27 2010-11-01T19:04:16.255586Z K 7 svn:log V 709 MFC r214160,214162,214236 r214236 & r214160: The firmware does pad notifications to an even number of bytes (at least the association notification), the included information though always contains an elem block with an odd number of bytes. We handle the last byte as if it might contain a whole elem block, this of course is not true as one byte is not enough to hold a block, we therefore discard the complete frame. The solution here is to subtract one from the actual notification length, this is also what the Linux driver does. With this change the frame ends exactly where the last elem block ends. r214262: The firmware always sets bit 14 and 15, to get the real associd we need to clear those bits. END K 10 svn:author V 8 bschmidt K 8 svn:date V 27 2010-11-01T19:05:38.198462Z K 7 svn:log V 709 MFC r214160,214162,214236 r214236 & r214160: The firmware does pad notifications to an even number of bytes (at least the association notification), the included information though always contains an elem block with an odd number of bytes. We handle the last byte as if it might contain a whole elem block, this of course is not true as one byte is not enough to hold a block, we therefore discard the complete frame. The solution here is to subtract one from the actual notification length, this is also what the Linux driver does. With this change the frame ends exactly where the last elem block ends. r214262: The firmware always sets bit 14 and 15, to get the real associd we need to clear those bits. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T19:35:33.960100Z K 7 svn:log V 460 Merge ^/vendor/binutils/dist@214571 into contrib/binutils, which brings us up to version 2.17.50.20070703, at the last GPLv2 commit. Amongst others, this added upstream support for some FreeBSD-specific things that we previously had to manually hack in, such as the OSABI label support, and so on. There are also quite a number of new files, some for cpu's (e.g. SPU) that we may or may not be interested in, but those can be cleaned up later on, if needed. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T19:39:10.117850Z K 7 svn:log V 48 Update VERSION to 2.17.50 [FreeBSD] 2007-07-03. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T19:40:22.330092Z K 7 svn:log V 44 Update Makefile and config.h for libiberty. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T19:41:22.211943Z K 7 svn:log V 52 Update Makefile, bfd.h and config.h.bsd for libbfd. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T19:42:07.076130Z K 7 svn:log V 49 Update Makefile and config.h.bsd for libopcodes. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T19:42:29.806311Z K 7 svn:log V 50 Update Makefile and config.h.bsd for libbinutils. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T19:45:15.186619Z K 7 svn:log V 67 Add manpages under gnu/usr.bin/binutils, since they are generated. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T19:45:55.544862Z K 7 svn:log V 37 Update Makefile and config.h for as. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T19:46:18.374858Z K 7 svn:log V 24 Update config.h for ld. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T19:47:03.603293Z K 7 svn:log V 45 Update doc Makefile and texinfo config file. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T20:09:54.560171Z K 7 svn:log V 147 For stuff under gnu/usr.bin/gdb, search contrib/binutils/include before contrib/gdb/include, since that contains newer versions of the same files. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T20:17:15.919920Z K 7 svn:log V 32 Fix warnings in fbsd-threads.c. END K 10 svn:author V 3 jfv K 8 svn:date V 27 2010-11-01T20:19:25.574589Z K 7 svn:log V 212 Sync the lem code up with the vlan and other fixes in em. Delete a unneeded test from the beginning of em_xmit. CRITICAL: shared code fix for 82574, a mutex might not be released, this can cause hangs. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T20:20:31.335107Z K 7 svn:log V 134 Use new output format 'elf64-x86-64-freebsd' instead of 'elf64-x86-64', and similarly 'elf64-sparc-freebsd' instead of 'elf64-sparc'. END K 10 svn:author V 6 cognet K 8 svn:date V 27 2010-11-01T21:04:23.442148Z K 7 svn:log V 127 Try to be a little smart at guessing where _start is located in flash, instead of relying on a binutils bug. Reported by: dim END K 10 svn:author V 5 jamie K 8 svn:date V 27 2010-11-01T21:37:28.477025Z K 7 svn:log V 72 Combine check_intparams() and ip_params(), JF_CHECKINT and JF_IPPARAMS. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-01T22:11:18.968347Z K 7 svn:log V 49 Sync: merge r214353 through r214648 from ^/head. END K 10 svn:author V 5 gonzo K 8 svn:date V 27 2010-11-02T01:24:49.977424Z K 7 svn:log V 383 Fix reading of .debug_line on MIPS64, big-endian: read_initial_length detects pointer size by checking first 4 bytes of .debug_line and stores it in struct comp_unit_head * passed to it as second argument. By passing NULL to a read_initial_length we ignore actual pointer size (8 bytes) and use default (4 bytes) which results in wrong offsets of header fields. END K 10 svn:author V 5 gonzo K 8 svn:date V 27 2010-11-02T01:26:21.339138Z K 7 svn:log V 76 - Add ELF core for FreeBSD/mips - Register all known cores in init function END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2010-11-02T02:13:13.294675Z K 7 svn:log V 68 Use sysctl kern.sched.cpusetsize to retrieve size of kernel cpuset. END K 10 svn:author V 6 obrien K 8 svn:date V 27 2010-11-02T05:27:05.478641Z K 7 svn:log V 59 Give the user a hint as to what config(8) is unhappy with. END K 10 svn:author V 6 obrien K 8 svn:date V 27 2010-11-02T05:39:57.657450Z K 7 svn:log V 20 Shorten long lines. END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2010-11-02T06:11:04.570552Z K 7 svn:log V 19 create dir for me. END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2010-11-02T06:13:21.104348Z K 7 svn:log V 13 libthr work. END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2010-11-02T06:47:18.115188Z K 7 svn:log V 606 Implement userland sleep queue. The queue is used to eliminate extra context switches and system calls in condition variable use. The problem is pthread_cond_broadcast can cause thread scheduler's thundering hurd, and because a thread calls pthread_cond_signal or pthread_cond_broadcast with mutex locked, resumed thread tries to lock the mutex and is block again, this is extra context switch. The change tries to move sleeping threads from condition variable's wait queue to mutex wait queue, only when the mutex is unlocked, a sleeping thread is woken up, in ideal case, only one system call is needed. END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2010-11-02T06:58:01.262672Z K 7 svn:log V 382 For simple mutex, we don't use thread id as owner data, instead use some contants. This eliminates the need to link the mutex into thread's private list, saves some cycles. The m_owner is pointer of curthread, which is always duplicated in child process after fork(), so for atfork handler in child process which wants to unlock the mutex, it will success rather than return EPERM. END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2010-11-02T07:46:31.688796Z K 7 svn:log V 22 Add missing function. END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2010-11-02T07:49:21.459227Z K 7 svn:log V 230 Remove link field in pthread_mutex, because it can not be used in process-shared mutex, otherwise, another process can corrupt your mutex link list when you owned it. Instead, allocate mutex link entry from heap, keep it private. END K 10 svn:author V 3 avg K 8 svn:date V 27 2010-11-02T07:56:20.481427Z K 7 svn:log V 61 MFC r213737: acpi_ec: changes in communication with hardware END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2010-11-02T08:08:37.382145Z K 7 svn:log V 22 Add sleep queue file. END K 10 svn:author V 3 mav K 8 svn:date V 27 2010-11-02T09:01:08.460391Z K 7 svn:log V 66 MFC r214325: Add missing mtx_destroy() on channel attach failure. END K 10 svn:author V 3 mav K 8 svn:date V 27 2010-11-02T09:04:18.935029Z K 7 svn:log V 94 MFC r214099: Some mvs(4) style cleanup: - remove commented debugging code; - wrap long lines. END K 10 svn:author V 3 mav K 8 svn:date V 27 2010-11-02T09:05:40.375393Z K 7 svn:log V 442 MFC r214102: Workaround strange situation when EDMA_RESQIP register returns zero instead of proper value. It caused bunch of "EMPTY CRPB" messages and potentially may cause premature requests completion, which could cause data corruption. For most cases it seems enough to just reread register to get proper value. To protect against worse cases - erase processed queue entries with impossible values and ignore them if problem still happen. END K 10 svn:author V 3 mav K 8 svn:date V 27 2010-11-02T09:13:13.934195Z K 7 svn:log V 120 MFC r213047 by jchandra: Add missing byteswap, works on big endian systems now (tested on Netlogic XLS MIPS processor). END K 10 svn:author V 3 mav K 8 svn:date V 27 2010-11-02T09:14:04.293993Z K 7 svn:log V 81 MFC r213092: Add missing le32toh(), same as recently done in ata-siliconimage.c. END K 10 svn:author V 3 mav K 8 svn:date V 27 2010-11-02T09:15:27.810330Z K 7 svn:log V 159 MFC r213301: Revert r132291. Restore setting PIO/WDMA timings for VIA UDMA133 controllers. Linux disables only AST register writing there, but no all timings. END K 10 svn:author V 7 davidxu K 8 svn:date V 27 2010-11-02T09:16:41.319176Z K 7 svn:log V 34 Refetch lockword before retrying. END K 10 svn:author V 3 mav K 8 svn:date V 27 2010-11-02T09:26:12.125983Z K 7 svn:log V 717 MFC r214016: Set of legacy mode SATA enchancements: - Implement proper combined mode decoding for Intel controllers to properly identify SATA and PATA channels and associate ATA channels with SATA ports. This fixes wrong reporting and in some cases hard resets to wrong SATA ports. - Improve SATA registers support to handle hot-plug events and potentially interface errors. For ICH5/6300ESB chipsets these registers accessible via PCI config space. For later ones they may be accessible via PCI BAR(5). - For controllers not generating interrupts on hot-plug events, implement periodic status polling. Use it to detect hot-plug on Intel and VIA controllers. Same probably could also be used for Serverworks and SIS. END K 10 svn:author V 3 mav K 8 svn:date V 27 2010-11-02T09:31:24.228123Z K 7 svn:log V 73 Remove stale line, accidentally slipped into r214016. MFC after: 3 days END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-02T12:40:13.505438Z K 7 svn:log V 119 Fix a few typos and style nits in the example code. Submitted by: Arnaud Lacombe lacombar of gmail MFC after: 3 days END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-02T12:42:46.604938Z K 7 svn:log V 196 MFC: Use the 'cfg2' value for Intel chipsets to limit the number of channels for non-SATA controllers. Specifically, limit the non-AHCI ICH7, 63XXESB2, and ICHM8 controllers to a single channel. END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-02T13:00:56.886315Z K 7 svn:log V 118 Don't leak the LLE lock if the arptimer callout is pending or inactive. Reported by: David Rhodus MFC after: 1 month END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-02T13:04:25.895324Z K 7 svn:log V 159 Skip SMAP regions above 4GB on i386 since they will not fit into a long. While here, update some comments to better explain the new code flow. Tested by: dhw END K 10 svn:author V 2 ae K 8 svn:date V 27 2010-11-02T13:47:13.797566Z K 7 svn:log V 31 Add frontend to tunefs dialog. END K 10 svn:author V 7 attilio K 8 svn:date V 27 2010-11-02T14:08:21.078084Z K 7 svn:log V 203 Rename s/ifn/ifp and s/nd_nic/nd_ifp in order to have more consistent names. Additively note that nd_nic_tun is not changed because it doesn't rappresent a "struct ifnet" pointer. Requested by: rwatson END K 10 svn:author V 7 attilio K 8 svn:date V 27 2010-11-02T14:29:39.522840Z K 7 svn:log V 105 Remove the reserved use of word "none" for interface name and use a flag instead. Requested by: rwatson END K 10 svn:author V 2 ed K 8 svn:date V 27 2010-11-02T17:00:56.602484Z K 7 svn:log V 508 Add a new libc function: cfmakesane(3). I've noticed various terminal emulators that need to obtain a sane default termios structure use very complex `hacks'. Even though POSIX doesn't provide any functionality for this, extend our termios API with cfmakesane(3), which is similar to the commonly supported cfmakeraw(3), except that it fills the termios structure with sane defaults. Change all code in our base system to use this function, instead of depending on to provide TTYDEF_*. END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-02T17:56:16.495845Z K 7 svn:log V 457 Further tweaks to the ram_attach() routine: - Use > 2^32 - 1 instead of >= when checking for memory regions above 4G. - Skip SMAP entries > 4G on i386 rather than breaking out of the loop since SMAP entries are not guaranteed to be in order. - Remove 'i' and loop over 'rid' directly in the dump_avail[] case. - Only check for 4G regions in the dump_avail[] case on i386 if PAE is enabled since vm_paddr_t is 32-bit in the !PAE case. Submitted by: alc END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-02T18:34:31.815909Z K 7 svn:log V 284 Tweak the waitchannel messages for the dead lock detection kthread. Use a shorter message (userland generally only sees the first 6 to 8 characters) when waiting for the allproc lock. Use "-" when idle to math the behavior of other kthreads. Reviewed by: attilio MFC after: 1 week END K 10 svn:author V 5 dougb K 8 svn:date V 27 2010-11-02T19:33:45.441665Z K 7 svn:log V 263 For -a change to using PM_NEEDS_UPDATE for keeping track of things that have already been updated as dependencies of other ports that needed updating. In order to do the above effectively we need to preserve the (moderately hackish) space prepended to the list. END K 10 svn:author V 6 marius K 8 svn:date V 27 2010-11-02T20:06:46.644307Z K 7 svn:log V 1538 MFC: r213878 Add a NetBSD-compatible mii_attach(), which is intended to eventually replace mii_phy_probe() altogether. Compared to the latter the advantages of mii_attach() are: - intended to be called multiple times in order to attach PHYs in multiple passes (f.e. in order to only use sub-ranges of the 0 to MII_NPHY - 1 range) - being able to pass along the capability mask from the NIC to the PHY drivers - being able to specify at which address (phyloc) to probe for a PHY (instead of always probing at all addresses from 0 to MII_NPHY - 1) - being able to specify which PHY instance (offloc) to attach - being able to pass along MIIF_* flags from the NIC to the PHY drivers (f.e. as required to indicated to the PHY drivers that flow control is supported by the NIC driver, which actually is the motivation for this change). While at it, I used the opportunity to get rid of some hacks in mii(4) like miibus_probe() generally doing work besides sheer probing and the "EVIL HACK" (which will vanish entirely along with mii_phy_probe()) by passing the struct ifnet pointer via an argument of mii_attach() as well as to fix some resource leaks in mii(4) in case something fails. Commits which will update the PHY drivers to honor the MII flags passed down from the NIC drivers and take advantage of mii_attach() to get rid of certain types of hacks in NIC and PHY drivers as well as a conversion of the remaining uses of mii_phy_probe() will follow shortly. Reviewed by: jhb, yongari Obtained from: NetBSD (partially) END K 10 svn:author V 6 marius K 8 svn:date V 27 2010-11-02T20:06:49.547977Z K 7 svn:log V 1538 MFC: r213878 Add a NetBSD-compatible mii_attach(), which is intended to eventually replace mii_phy_probe() altogether. Compared to the latter the advantages of mii_attach() are: - intended to be called multiple times in order to attach PHYs in multiple passes (f.e. in order to only use sub-ranges of the 0 to MII_NPHY - 1 range) - being able to pass along the capability mask from the NIC to the PHY drivers - being able to specify at which address (phyloc) to probe for a PHY (instead of always probing at all addresses from 0 to MII_NPHY - 1) - being able to specify which PHY instance (offloc) to attach - being able to pass along MIIF_* flags from the NIC to the PHY drivers (f.e. as required to indicated to the PHY drivers that flow control is supported by the NIC driver, which actually is the motivation for this change). While at it, I used the opportunity to get rid of some hacks in mii(4) like miibus_probe() generally doing work besides sheer probing and the "EVIL HACK" (which will vanish entirely along with mii_phy_probe()) by passing the struct ifnet pointer via an argument of mii_attach() as well as to fix some resource leaks in mii(4) in case something fails. Commits which will update the PHY drivers to honor the MII flags passed down from the NIC drivers and take advantage of mii_attach() to get rid of certain types of hacks in NIC and PHY drivers as well as a conversion of the remaining uses of mii_phy_probe() will follow shortly. Reviewed by: jhb, yongari Obtained from: NetBSD (partially) END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-02T20:16:41.079197Z K 7 svn:log V 165 Cosmetic change to revert one of my earlier ones. #if __i386__ && PAE is identical to just #if PAE since PAE is only a valid option for i386. Submitted by: attilio END K 10 svn:author V 6 marius K 8 svn:date V 27 2010-11-02T21:01:15.187415Z K 7 svn:log V 182 MFC: r201430 Fix card/device names, no functional change The ADMtek AN985 is the cardbus variant of ADMtek AN983 The Netgear FA511 is just a relabled ADMtek AN985 PR: kern/50574 END K 10 svn:author V 6 marius K 8 svn:date V 27 2010-11-02T21:01:18.431317Z K 7 svn:log V 182 MFC: r201430 Fix card/device names, no functional change The ADMtek AN985 is the cardbus variant of ADMtek AN983 The Netgear FA511 is just a relabled ADMtek AN985 PR: kern/50574 END K 10 svn:author V 5 dougb K 8 svn:date V 27 2010-11-02T22:06:23.265268Z K 7 svn:log V 303 Since we're going to depend on PM_NEEDS_UPDATE to tell us what ports we can skip with -a anyway, use the same mechanism to handle multiport(). This allows me to get rid of yet another list, PM_MULTI_BUILT. While I'm here, tune up all the examples of case "$PM_NEEDS_UPDATE" to have a consistent style. END K 10 svn:author V 6 marius K 8 svn:date V 27 2010-11-02T22:12:06.499737Z K 7 svn:log V 456 MFC: r214526 Partially revert r203829 (MFC'ed to stable/7 in r205920); as it turns out what the PowerPC OFW loader did was incorrect as further down the road cons_probe() calls malloc() so the former can't be called before init_heap() has succeed. Instead just exit to the firmware in case init_heap() fails like OF_init() does when hitting a problem as we're then likely running in a very broken environment where hardly anything can be trusted to work. END K 10 svn:author V 6 marius K 8 svn:date V 27 2010-11-02T22:12:12.965561Z K 7 svn:log V 456 MFC: r214526 Partially revert r203829 (MFC'ed to stable/7 in r205921); as it turns out what the PowerPC OFW loader did was incorrect as further down the road cons_probe() calls malloc() so the former can't be called before init_heap() has succeed. Instead just exit to the firmware in case init_heap() fails like OF_init() does when hitting a problem as we're then likely running in a very broken environment where hardly anything can be trusted to work. END K 10 svn:author V 3 pjd K 8 svn:date V 27 2010-11-02T22:13:08.307977Z K 7 svn:log V 414 Send packets to remote node only via the send thread to avoid possible races - in this case a keepalive packet was send from wrong thread which lead to connection dropping, because of corrupted packet. Fix it by sending keepalive packets directly from the send thread. As a bonus we now send keepalive packets only when connection is idle. Submitted by: Mikolaj Golub MFC after: 3 days END K 10 svn:author V 3 pjd K 8 svn:date V 27 2010-11-02T22:30:19.359113Z K 7 svn:log V 284 MFC r211854: - When VFS_VGET() is not supported, switch to VOP_LOOKUP(). - We are fine by only share-locking the vnode. - Remove assertion that doesn't hold for ZFS where we cross mount points boundaries by going into .zfs/snapshot//. Reviewed by: rmacklem Reminded by: kib END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T22:44:51.448289Z K 7 svn:log V 1237 MFC r213081,213225,213280: r213081: Always show asic/chip revision in device attach phase. There are too many bge(4) controllers there and model name does not necessarily match asic/chip revision. Relying on VPD string made it hard to identify exact asic/chip revision so the first step to debug bge(4) was getting exact asic/chip information with verbose boot which may not be available on production server. r213255: Set the number of RX frames to receive after RX MBUF low watermark has reached. This reduced number of dropped frames when flow-control is enabled. Previously it dropped incoming frames once RX MBUF low watermark has reached. The value used in MAC RX MBUF low watermark is greater than or equal to 4 so receiving two more RX frames should not be a problem. Obtained from: OpenBSD r213280: After r207391, brgphy(4) passes resolved flow-control settings to parent driver. Use that information to configure flow-control. One drawback is there is no way to disable flow-control as we still don't have proper way to not advertise RX/TX pause capability to link partner. But I don't think it would cause severe problems and users can selectively disable flow-control in switch port. END K 10 svn:author V 3 pjd K 8 svn:date V 27 2010-11-02T22:48:18.765617Z K 7 svn:log V 67 MFC r211855: Update comment now that I finally committed r211854. END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T22:48:52.545593Z K 7 svn:log V 1237 MFC r213081,213225,213280: r213081: Always show asic/chip revision in device attach phase. There are too many bge(4) controllers there and model name does not necessarily match asic/chip revision. Relying on VPD string made it hard to identify exact asic/chip revision so the first step to debug bge(4) was getting exact asic/chip information with verbose boot which may not be available on production server. r213255: Set the number of RX frames to receive after RX MBUF low watermark has reached. This reduced number of dropped frames when flow-control is enabled. Previously it dropped incoming frames once RX MBUF low watermark has reached. The value used in MAC RX MBUF low watermark is greater than or equal to 4 so receiving two more RX frames should not be a problem. Obtained from: OpenBSD r213280: After r207391, brgphy(4) passes resolved flow-control settings to parent driver. Use that information to configure flow-control. One drawback is there is no way to disable flow-control as we still don't have proper way to not advertise RX/TX pause capability to link partner. But I don't think it would cause severe problems and users can selectively disable flow-control in switch port. END K 10 svn:author V 3 pjd K 8 svn:date V 27 2010-11-02T22:49:20.498973Z K 7 svn:log V 1412 MFC r214119,r214273,r214274,r214275,r214276,r214282,r214283,r214284,r214692: r214119: Use closefrom(2) instead of close(2) in a loop. r214273: Load geom_gate.ko module after parsing arguments. r214274: Plug memory leaks. Found with: valgrind r214275: Plug memory leak. r214276: Simplify code a bit. r214282: Move all NV defines into nv.c, they are not used externally thus there is no need to make then visible from outside. r214283: Implement nv_exists() function that returns true if argument of the given name exists. r214284: Before this change on first connect between primary and secondary we initialize all the data. This is huge waste of time and resources if there were no writes yet, as there is no real data to synchronize. Optimize this by sending "virgin" argument to secondary, which gives it a hint that synchronization is not needed. In the common case (where noth nodes are configured at the same time) instead of synchronizing everything, we don't synchronize at all. r214692: Send packets to remote node only via the send thread to avoid possible races - in this case a keepalive packet was send from wrong thread which lead to connection dropping, because of corrupted packet. Fix it by sending keepalive packets directly from the send thread. As a bonus we now send keepalive packets only when connection is idle. Submitted by: Mikolaj Golub END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T22:57:20.195210Z K 7 svn:log V 619 MFC r213283,213410: r213283: Implement hardware MAC statistics for BCM5705 or newer Broadcom controllers. bge(4) exported MAC statistics on controllers that maintain the statistics in the NIC's internal memory. Newer controllers require register access to fetch these values. These counters provide useful information to diagnose driver issues. r213410: Consistently use ifHCOutOctets/ifHCInOctets instead of Octets as these names are used in data sheet. Also use UnicastPkts, MulticastPkts and BroadcastPkts instead of UcastPkts, McastPkts and BcastPkts to clarify its meaning. Suggested by: bde END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T22:59:45.808390Z K 7 svn:log V 619 MFC r213283,213410: r213283: Implement hardware MAC statistics for BCM5705 or newer Broadcom controllers. bge(4) exported MAC statistics on controllers that maintain the statistics in the NIC's internal memory. Newer controllers require register access to fetch these values. These counters provide useful information to diagnose driver issues. r213410: Consistently use ifHCOutOctets/ifHCInOctets instead of Octets as these names are used in data sheet. Also use UnicastPkts, MulticastPkts and BroadcastPkts instead of UcastPkts, McastPkts and BcastPkts to clarify its meaning. Suggested by: bde END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:04:23.945875Z K 7 svn:log V 415 MFC r213316,213333-213334: r213316: Fix IFCAP_TXCSUM/IFCAP_RXCSUM handling. Previously bge(4) used IFCAP_HWCSUM to know which capability should be changed such that disabling RX checksun offloading resulted in disabling TX checksum offloading. r213333: Allow write DMA to request larger DMA burst size to get better performance on BCM5785. Obtained from: OpenBSD r213334: Remove extra semicolon. END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:07:38.625401Z K 7 svn:log V 415 MFC r213316,213333-213334: r213316: Fix IFCAP_TXCSUM/IFCAP_RXCSUM handling. Previously bge(4) used IFCAP_HWCSUM to know which capability should be changed such that disabling RX checksun offloading resulted in disabling TX checksum offloading. r213333: Allow write DMA to request larger DMA burst size to get better performance on BCM5785. Obtained from: OpenBSD r213334: Remove extra semicolon. END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:23:48.968356Z K 7 svn:log V 683 MFC r213411,213464-213465,213468: r213411: Enable fix for read DMA FIFO overruns on controllers that have this fix. Note, we still need workaround for controllers that lacks this fix and it needs more work in RX BD updating. Submitted by: davidch r213464: Separate common flags into controller specific and PHY related flags. There should be no functional changes. This change will make it easy to add more quirk/flags in future. Reviewed by: davidch r213465: Rearrange code a bit to correctly set PHY flags. This change make it easy to add more newer ASICs. Obtained from: OpenBSD r213468: Fix bge(4) build breakage when BGE_REGISTER_DEBUG is defined. END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:26:07.194375Z K 7 svn:log V 683 MFC r213411,213464-213465,213468: r213411: Enable fix for read DMA FIFO overruns on controllers that have this fix. Note, we still need workaround for controllers that lacks this fix and it needs more work in RX BD updating. Submitted by: davidch r213464: Separate common flags into controller specific and PHY related flags. There should be no functional changes. This change will make it easy to add more quirk/flags in future. Reviewed by: davidch r213465: Rearrange code a bit to correctly set PHY flags. This change make it easy to add more newer ASICs. Obtained from: OpenBSD r213468: Fix bge(4) build breakage when BGE_REGISTER_DEBUG is defined. END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:35:08.563960Z K 7 svn:log V 2423 MFC r213485,213710,213812: r213485: Overhaul MII register access routine and remove unnecessary BGE_MI_MODE register accesses. Previously bge(4) used to read BGE_MI_MODE register to detect whether it needs to disable autopolling feature or not. Because we don't touch autopolling in other part of driver there is no reason to read BGE_MI_MODE register given that we know default value in advance. In order to achieve the goal, check whether the controller has CPMU(Central Power Mangement Unit) capability. If controller has CPMU feature, use 500KHz MII management interface(mdio/mdc) frequency regardless core clock frequency. Otherwise use default MII clock. While I'm here, add CPMU register definition. In bge_miibus_readreg(), rearrange code a bit and remove goto statement. In bge_miibus_writereg(), make sure to restore autopolling even if MII write failed. The delay time inserted after accessing BGE_MI_MODE register increased from 40us to 80us. The default PHY address is now stored in softc. All PHYs supported by bge(4) currently uses PHY address 1 but it will be changed when we add newer controllers. This change will make it easier to change default PHY address depending on PHY models. Submitted by: davidch r213710: Remove one last reference of BGE_MI_MODE register for auto polling. Previously bge(4) always enabled auto polling for non-BGE_FLAG_TBI controllers. With this change, auto polling is not used anymore so polling through mii(4) was introduced. Reviewed by: davidch r213812: Fix a regression introduced in r213710. r213710 removed the use of auto polling such that it made all controllers obtain link status information from the state of the LNKRDY input signal. Broadcom recommends disabling auto polling such that driver should rely on PHY interrupts for link status change indications. Unfortunately it seems some controllers(BCM5703, BCM5704 and BCM5705) have PHY related issues so Linux took other approach to workaround it. bge(4) didn't follow that and it used to enable auto polling to workaround it. Restore this old behavior for BCM5700 family controllers and BCM5705 to use auto polling. For BCM5700 and BCM5701, it seems it does not need to enable auto polling but I restored it for safety. Special thanks to marius who tried lots of patches with patience. Reported by: marius Tested by: marius END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:36:54.651551Z K 7 svn:log V 2423 MFC r213485,213710,213812: r213485: Overhaul MII register access routine and remove unnecessary BGE_MI_MODE register accesses. Previously bge(4) used to read BGE_MI_MODE register to detect whether it needs to disable autopolling feature or not. Because we don't touch autopolling in other part of driver there is no reason to read BGE_MI_MODE register given that we know default value in advance. In order to achieve the goal, check whether the controller has CPMU(Central Power Mangement Unit) capability. If controller has CPMU feature, use 500KHz MII management interface(mdio/mdc) frequency regardless core clock frequency. Otherwise use default MII clock. While I'm here, add CPMU register definition. In bge_miibus_readreg(), rearrange code a bit and remove goto statement. In bge_miibus_writereg(), make sure to restore autopolling even if MII write failed. The delay time inserted after accessing BGE_MI_MODE register increased from 40us to 80us. The default PHY address is now stored in softc. All PHYs supported by bge(4) currently uses PHY address 1 but it will be changed when we add newer controllers. This change will make it easier to change default PHY address depending on PHY models. Submitted by: davidch r213710: Remove one last reference of BGE_MI_MODE register for auto polling. Previously bge(4) always enabled auto polling for non-BGE_FLAG_TBI controllers. With this change, auto polling is not used anymore so polling through mii(4) was introduced. Reviewed by: davidch r213812: Fix a regression introduced in r213710. r213710 removed the use of auto polling such that it made all controllers obtain link status information from the state of the LNKRDY input signal. Broadcom recommends disabling auto polling such that driver should rely on PHY interrupts for link status change indications. Unfortunately it seems some controllers(BCM5703, BCM5704 and BCM5705) have PHY related issues so Linux took other approach to workaround it. bge(4) didn't follow that and it used to enable auto polling to workaround it. Restore this old behavior for BCM5700 family controllers and BCM5705 to use auto polling. For BCM5700 and BCM5701, it seems it does not need to enable auto polling but I restored it for safety. Special thanks to marius who tried lots of patches with patience. Reported by: marius Tested by: marius END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:41:43.302495Z K 7 svn:log V 1562 MFC r213495,213742: r213495: Add more comments to rings supported by the controller. Different versions of controller support different number of ring control blocks such that adjust code a bit to access known number of send/receive ring control blocks. Previously bge(4) blindly accessed 16 send/receive RCBs. Also move initializing standard receive producer ring producer index, jumbo receive producer ring producer index and mini receive producer ring producer index to the end of each receive producer ring initialization. Do not assume mini receive producer ring is available only when controller has jumbo frame capability, instead explicitly check ASIC version BCM5700 to disable mini receive producer ring. Additionally always enable send ring 0 regardless of controller versions. Previously bge(4) didn't enable send ring 0 if controller is BGE_IS_5705_PLUS. Becase bge(4) need 1 send ring to send frames at least, I have no idea how it would have worked so far. Submitted by: davidch r213742: Fix a regression introduced in r213495. r213495 disabled mini receive producer ring only for BCM5700. It was believed that BCM5700 with external SSRAM is the only controller that supports mini ring but it seems all BCM570[0-4] requires to disable mini receive producer ring. Otherwise, it caused unexpected RX DMA error or watchdog timeouts. Reported by: marius, Steve Kargl troutmask dot apl dot washington dot edu> Tested by: marius, Steve Kargl troutmask dot apl dot washington dot edu> END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:43:27.356203Z K 7 svn:log V 1562 MFC r213495,213742: r213495: Add more comments to rings supported by the controller. Different versions of controller support different number of ring control blocks such that adjust code a bit to access known number of send/receive ring control blocks. Previously bge(4) blindly accessed 16 send/receive RCBs. Also move initializing standard receive producer ring producer index, jumbo receive producer ring producer index and mini receive producer ring producer index to the end of each receive producer ring initialization. Do not assume mini receive producer ring is available only when controller has jumbo frame capability, instead explicitly check ASIC version BCM5700 to disable mini receive producer ring. Additionally always enable send ring 0 regardless of controller versions. Previously bge(4) didn't enable send ring 0 if controller is BGE_IS_5705_PLUS. Becase bge(4) need 1 send ring to send frames at least, I have no idea how it would have worked so far. Submitted by: davidch r213742: Fix a regression introduced in r213495. r213495 disabled mini receive producer ring only for BCM5700. It was believed that BCM5700 with external SSRAM is the only controller that supports mini ring but it seems all BCM570[0-4] requires to disable mini receive producer ring. Otherwise, it caused unexpected RX DMA error or watchdog timeouts. Reported by: marius, Steve Kargl troutmask dot apl dot washington dot edu> Tested by: marius, Steve Kargl troutmask dot apl dot washington dot edu> END K 10 svn:author V 8 jmallett K 8 svn:date V 27 2010-11-02T23:43:44.861335Z K 7 svn:log V 126 Declare the CF GEOM class so that g_modevent will get called, the class will be recorded, etc. This fixes libgeom on Octeon. END K 10 svn:author V 6 jilles K 8 svn:date V 27 2010-11-02T23:44:29.683712Z K 7 svn:log V 374 sh: Fix some issues with aliases and case, by importing dash checkkwd code. This moves the function of the noaliases variable into the checkkwd variable. This way it is properly reset on errors and aliases can be used normally in the commands for each case (the case labels recognize the keyword esac but no aliases). The new code is clearer as well. Obtained from: dash END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:48:08.353305Z K 7 svn:log V 1263 MFC r213522,213587,213711: r213522: Fix a long standing bug which regarded some revisions of controller as 5788. This caused BGE_MISC_LOCAL_CTL register is used to generate link state change interrupt for non-5788 controllers. The interrupt handler may or may not detect link state attention as status block wouldn't be updated when an interrupt was generated with BGE_MISC_LOCAL_CTL register. All controllers except 5700 and 5788 should use host coalescing mode register to trigger an interrupt. r213587: Do not blindly UP the interface when interface's MTU is changed. If driver is not running there is no need to up the interface. While I'm here hold driver lock before modifying MTU as it is referenced in RX handler. r213711: The IFF_DRV_RUNNING flag is set at the end of bge_init_locked. But before setting the flag, interrupt was already enabled such that interrupt handler could be run before setting IFF_DRV_RUNNING flag. This can lose initial link state change interrupt which in turn make bge(4) think that it still does not have valid link. Fix this race by protecting the taskqueue with a driver lock. While I'm here move reenabling interrupt code after handling of link state chage. Reviewed by: davidch END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:49:48.427250Z K 7 svn:log V 1263 MFC r213522,213587,213711: r213522: Fix a long standing bug which regarded some revisions of controller as 5788. This caused BGE_MISC_LOCAL_CTL register is used to generate link state change interrupt for non-5788 controllers. The interrupt handler may or may not detect link state attention as status block wouldn't be updated when an interrupt was generated with BGE_MISC_LOCAL_CTL register. All controllers except 5700 and 5788 should use host coalescing mode register to trigger an interrupt. r213587: Do not blindly UP the interface when interface's MTU is changed. If driver is not running there is no need to up the interface. While I'm here hold driver lock before modifying MTU as it is referenced in RX handler. r213711: The IFF_DRV_RUNNING flag is set at the end of bge_init_locked. But before setting the flag, interrupt was already enabled such that interrupt handler could be run before setting IFF_DRV_RUNNING flag. This can lose initial link state change interrupt which in turn make bge(4) think that it still does not have valid link. Fix this race by protecting the taskqueue with a driver lock. While I'm here move reenabling interrupt code after handling of link state chage. Reviewed by: davidch END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:54:59.622296Z K 7 svn:log V 640 MFC r213747,213808,214216: r213747: Protect bge(4) from accessing invalid NIC internal memory regions on BCM5906. Tested by: Buganini < buganini <> gmail dot com > r213808: Add more checks for resolved link speed in bge_miibus_statchg(). Link UP state could be reported first before actual completion of auto-negotiation. This change makes bge(4) reprogram BGE_MAC_MODE, BGE_TX_MODE and BGE_RX_MODE register only after controller got a valid link. r214216: Enable TX MAC state machine lockup fix for both BCM5755 or higher and BCM5906. Publicly available data sheet just says it may happen due to corrupted TxMbuf. END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-02T23:56:35.126224Z K 7 svn:log V 640 MFC r213747,213808,214216: r213747: Protect bge(4) from accessing invalid NIC internal memory regions on BCM5906. Tested by: Buganini < buganini <> gmail dot com > r213808: Add more checks for resolved link speed in bge_miibus_statchg(). Link UP state could be reported first before actual completion of auto-negotiation. This change makes bge(4) reprogram BGE_MAC_MODE, BGE_TX_MODE and BGE_RX_MODE register only after controller got a valid link. r214216: Enable TX MAC state machine lockup fix for both BCM5755 or higher and BCM5906. Publicly available data sheet just says it may happen due to corrupted TxMbuf. END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-03T00:03:26.486380Z K 7 svn:log V 1516 MFC r214087,214219,214251,214292: r214087: Add workaround for BCM5906 controller silicon bug. If device receive two back-to-back send BDs with less than or equal to 8 total bytes then the device may hang. The two back-to-back send BDs must be in the same frame for this failure to occur. Thanks to davidch for detailed errata information. Reviewed by: davidch r214219: Add workaround for BCM5906 A1 controller silicon bug. When auto-negotiation results in half-duplex operation, excess collision on the ethernet link may cause internal chip delays that may result in subsequent valid frames being dropped due to insufficient receive buffer resources. The workaround is to choose de-pipeline method as a flow control decision for SDI. De-pipeline method allows only 1 data in TxMbuf at a time such that a request to RDMA from SDI is made only when TxMbuf is empty. Thanks for david for providing detailed errata information. r214251: Apply the same workaround for SDI flow control used on BCM5906 A1 to BCM6906 A0/A2. This should fix a long standing BCM5906 A2 lockup issues. Data sheet explicitly mentions BCM5906 A0, A1 and A2 use de-pipelined mode on these revisions. Special thanks to Buganini who tried all combinations of experimental patches for more than 10 days. Tested by: Buganini gmail dot com > r214292: Use bge_chipid to compare controller ids. r214251 incorrectly used bge_chiprev. Reported by: Buganini gmail dot com > END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-03T00:13:22.040546Z K 7 svn:log V 1516 MFC r214087,214219,214251,214292: r214087: Add workaround for BCM5906 controller silicon bug. If device receive two back-to-back send BDs with less than or equal to 8 total bytes then the device may hang. The two back-to-back send BDs must be in the same frame for this failure to occur. Thanks to davidch for detailed errata information. Reviewed by: davidch r214219: Add workaround for BCM5906 A1 controller silicon bug. When auto-negotiation results in half-duplex operation, excess collision on the ethernet link may cause internal chip delays that may result in subsequent valid frames being dropped due to insufficient receive buffer resources. The workaround is to choose de-pipeline method as a flow control decision for SDI. De-pipeline method allows only 1 data in TxMbuf at a time such that a request to RDMA from SDI is made only when TxMbuf is empty. Thanks for david for providing detailed errata information. r214251: Apply the same workaround for SDI flow control used on BCM5906 A1 to BCM6906 A0/A2. This should fix a long standing BCM5906 A2 lockup issues. Data sheet explicitly mentions BCM5906 A0, A1 and A2 use de-pipelined mode on these revisions. Special thanks to Buganini who tried all combinations of experimental patches for more than 10 days. Tested by: Buganini gmail dot com > r214292: Use bge_chipid to compare controller ids. r214251 incorrectly used bge_chiprev. Reported by: Buganini gmail dot com > END K 10 svn:author V 5 edwin K 8 svn:date V 27 2010-11-03T01:24:26.213826Z K 7 svn:log V 168 Vendor import of tzdata2010o: - Fiji will end DST 3 weeks earlier than expected - on March 6, 2011, not March 27, 2011. Obtained from: ftp://elsie.nci.nih.gov/pub/ END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-03T01:24:33.010331Z K 7 svn:log V 319 MFC r214302: Add TSO support over VLAN for i82550/i82551. Controller requires VLAN hardware tagging to make TSO work over VLAN. So if VLAN hardware tagging is disabled explicitly clear TSO over VLAN. While I'm here allow disabling VLAN TX checksum offloading. Tested by: Liudas < liudasb <> centras dot lt > END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-03T01:26:11.677695Z K 7 svn:log V 319 MFC r214302: Add TSO support over VLAN for i82550/i82551. Controller requires VLAN hardware tagging to make TSO work over VLAN. So if VLAN hardware tagging is disabled explicitly clear TSO over VLAN. While I'm here allow disabling VLAN TX checksum offloading. Tested by: Liudas < liudasb <> centras dot lt > END K 10 svn:author V 5 edwin K 8 svn:date V 27 2010-11-03T01:26:41.557172Z K 7 svn:log V 19 Tag of tzdata2010o END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-03T01:28:09.474387Z K 7 svn:log V 240 MFC r214432: Use shorten model name and add RTL8168, RTL8111 to the list of supported device. re(4) had been supported all variants of RTL8168, RTL8111 and RTL810x. I think this change will cover all controllers supported by re(4). END K 10 svn:author V 7 yongari K 8 svn:date V 27 2010-11-03T01:28:57.033309Z K 7 svn:log V 240 MFC r214432: Use shorten model name and add RTL8168, RTL8111 to the list of supported device. re(4) had been supported all variants of RTL8168, RTL8111 and RTL810x. I think this change will cover all controllers supported by re(4). END K 10 svn:author V 5 edwin K 8 svn:date V 27 2010-11-03T01:30:56.325282Z K 7 svn:log V 78 MFV of tzdata2010o, r214716 - Fiji moves to DST three weeks earlier in 2010. END K 10 svn:author V 5 edwin K 8 svn:date V 27 2010-11-03T01:32:39.061001Z K 7 svn:log V 80 MFC of r214722, tzdata2010o: - Fiji goes into DST three weeks earlier in 2011. END K 10 svn:author V 5 edwin K 8 svn:date V 27 2010-11-03T01:32:44.549483Z K 7 svn:log V 80 MFC of r214722, tzdata2010o: - Fiji goes into DST three weeks earlier in 2011. END K 10 svn:author V 5 edwin K 8 svn:date V 27 2010-11-03T01:32:50.181894Z K 7 svn:log V 80 MFC of r214722, tzdata2010o: - Fiji goes into DST three weeks earlier in 2011. END K 10 svn:author V 8 hselasky K 8 svn:date V 27 2010-11-03T07:51:33.019541Z K 7 svn:log V 141 Clean up leftover USB device ID after r213856. This fixes: options USB_VERBOSE Submitted by: Lucius Windschuh Approved by: thompsa (mentor) END K 10 svn:author V 3 kib K 8 svn:date V 27 2010-11-03T08:34:00.711097Z K 7 svn:log V 250 MFC r214049: When readdirplus() is handled on the exported filesystem that does not support VFS_VGET, like msdosfs, do not call VOP_LOOKUP() for dotdot on the root directory. Our filesystems expect that VFS handles dotdot lookups on root on its own. END K 10 svn:author V 3 kib K 8 svn:date V 27 2010-11-03T09:23:08.637881Z K 7 svn:log V 1198 If dlopen() is called for the dso that has been already loaded as a dependency, then the dso never has its DAG initialized. Empty DAG makes ref_dag() call in dlopen() a nop, and the dso refcount is off by one. Initialize the DAG on the first dlopen() call, using a boolean flag to prevent double initialization. From the PR (edited): Assume we have a library liba.so, containing a function a(), and a library libb.so, containing function b(). liba.so needs functionality from libb.so, so liba.so links in libb.so. An application doesn't know about the relation between these libraries, but needs to call a() and b(). It dlopen()s liba.so and obtains a pointer to a(), then it dlopen()s libb.so and obtains a pointer to b(). As soon as the application doesn't need a() anymore, it dlclose()s liba.so. Expected result: the pointer to b() is still valid and can be called Actual result: the pointer to b() has become invalid, even though the application did not dlclose() the handle to libb.so. On calling b(), the application crashes with a segmentation fault. PR: misc/151861 Based on patch by: jh Reviewed by: kan Tested by: Arjan van Leeuwen MFC after: 1 week END K 10 svn:author V 5 edwin K 8 svn:date V 27 2010-11-03T10:10:34.237982Z K 7 svn:log V 449 MFC of r214002, r214010 - Stylify of uudecode(1) Part of PR bin/124739. - "b64decode -r" did not handle arbitary breaks in base64 encoded data. White space should be accepted anywhere in a base64 encoded stream, not just after every chunk (4 characters). Test-scenario: VmVsb2NpdHkgUmV3YXJkcw== and VmVsb2NpdHkgUmV3YXJkcw == should both produce "Velocity Rewards" PR: bin/124739 Submitted by: Mark Andrews END K 10 svn:author V 5 edwin K 8 svn:date V 27 2010-11-03T10:12:13.267866Z K 7 svn:log V 462 MFC of r214002, r214010 - Stylify of uudecode(1) Part of PR bin/124739. - "b64decode -r" did not handle arbitary breaks in base64 encoded data. White space should be accepted anywhere in a base64 encoded stream, not just after every chunk (4 characters). Test-scenario: VmVsb2NpdHkgUmV3YXJkcw== and VmVsb2NpdHkgUmV3YXJkcw == should both produce "Velocity Rewards" PR: bin/124739 Submitted by: Mark Andrews END K 10 svn:author V 2 ed K 8 svn:date V 27 2010-11-03T10:23:06.248600Z K 7 svn:log V 240 MFC r214105: Remove setpgid() call before executing child process. Using a separate process group here is bad, since (for example) job control in the TTY layer prevents interaction with the TTY, causing the child process to hang. END K 10 svn:author V 2 ed K 8 svn:date V 27 2010-11-03T10:24:57.522371Z K 7 svn:log V 240 MFC r214105: Remove setpgid() call before executing child process. Using a separate process group here is bad, since (for example) job control in the TTY layer prevents interaction with the TTY, causing the child process to hang. END K 10 svn:author V 2 ae K 8 svn:date V 27 2010-11-03T10:34:21.280031Z K 7 svn:log V 220 Remove stale declarations. Fix a typo [1]. Add check for correctness of volume label. Construct tunefs command-line based on info given from dialog. Allow long messages for dmenu_open_errormsg. Noticed by: netchild [1] END K 10 svn:author V 6 rpaulo K 8 svn:date V 27 2010-11-03T10:43:38.538737Z K 7 svn:log V 40 Merge wpa_supplicant and hostapd 0.7.3. END K 10 svn:author V 6 rpaulo K 8 svn:date V 27 2010-11-03T10:44:25.428963Z K 7 svn:log V 42 Adapt for wpa_supplicant / hostapd 0.7.3. END K 10 svn:author V 6 rpaulo K 8 svn:date V 27 2010-11-03T10:46:39.237177Z K 7 svn:log V 21 Remove unused files. END K 10 svn:author V 2 ae K 8 svn:date V 27 2010-11-03T12:12:29.025469Z K 7 svn:log V 32 Add simple commit/undo support. END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-03T13:42:59.651320Z K 7 svn:log V 78 Delete machine/foo.h headers moved to x86/. I forgot to commit this earlier. END K 10 svn:author V 10 nwhitehorn K 8 svn:date V 27 2010-11-03T15:15:48.461105Z K 7 svn:log V 371 Clean up the user segment handling code a little more. Now that set_user_sr() itself caches the user segment VSID, there is no need for cpu_switch() to do it again. This change also unifies the 32 and 64-bit code paths for kernel faults on user pages and remaps the user SLB slot on 64-bit systems when taking a syscall to avoid some unnecessary segment exception traps. END K 10 svn:author V 10 nwhitehorn K 8 svn:date V 27 2010-11-03T15:22:09.052541Z K 7 svn:log V 14 IFC @ r214739 END K 10 svn:author V 10 nwhitehorn K 8 svn:date V 27 2010-11-03T15:24:25.958251Z K 7 svn:log V 103 MFC r214601: Add some missing parentheses so that moea_bat_mapped() actually works. Submitted by: alc END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-03T15:25:30.389726Z K 7 svn:log V 391 MFC 213672,213674,214396: - Report subcommand handler errors in mfiutil so that tools that invoke the utilities can robustly report errors. - Fix compile with -DDEBUG by using the correct mfi_pd_ref union definition in mfireg.h. - Save errno values before calling warn(3) so that errors are correctly reported. - Use powerof2() from rather than a copy and paste version. END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-03T15:25:40.620298Z K 7 svn:log V 391 MFC 213672,213674,214396: - Report subcommand handler errors in mfiutil so that tools that invoke the utilities can robustly report errors. - Fix compile with -DDEBUG by using the correct mfi_pd_ref union definition in mfireg.h. - Save errno values before calling warn(3) so that errors are correctly reported. - Use powerof2() from rather than a copy and paste version. END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-03T15:31:10.809664Z K 7 svn:log V 37 Trim unneeded mergeinfo from a file. END K 10 svn:author V 10 nwhitehorn K 8 svn:date V 27 2010-11-03T15:31:37.042792Z K 7 svn:log V 374 MFC r214349: The EHCI_CAPLENGTH and EHCI_HCIVERSION registers are actually sub-registers within the first 4 bytes of the EHCI memory space. For controllers that use big-endian MMIO, reading them with 1- and 2-byte reads would then return the wrong values. Instead, read the combined register with a 4-byte read and mask out the interesting quantities. Requested by: marius END K 10 svn:author V 3 jhb K 8 svn:date V 27 2010-11-03T15:38:52.835235Z K 7 svn:log V 47 Remove 'softclock_ih' as it is no longer used. END K 10 svn:author V 5 jamie K 8 svn:date V 27 2010-11-03T15:54:50.947006Z K 7 svn:log V 115 MFC 214434: Find a jail's type as part of jailparam_init rather than waiting until it's absolutely necessary. END K 10 svn:author V 2 jh K 8 svn:date V 27 2010-11-03T16:19:35.482920Z K 7 svn:log V 237 Extend the g_eventlock mutex coverage in one_event() to include setting of the EV_DONE flag and use the mutex to protect against losing wakeups in g_waitfor_event(). Reported by: davidxu Tested by: davidxu Discussed on: freebsd-current END K 10 svn:author V 10 nwhitehorn K 8 svn:date V 27 2010-11-03T16:21:47.613043Z K 7 svn:log V 239 Fix two mistakes on 32-bit systems. The slbmte code in syscall() is 64-bit only, and should be protected with an ifdef, and the no-execute bit in 32-bit set_user_sr() should be set before the comparison, not after, or it will never match. END K 10 svn:author V 3 dim K 8 svn:date V 27 2010-11-03T16:39:55.760580Z K 7 svn:log V 194 Simply our custom OSABI branding 'stub'. It is presently still needed for ia64, but I will integrate it into contrib/binutils/bfd/elfxx-ia64.c later on, after which it can be removed entirely. END