summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* | Const'ify scc_driver_name.marius2013-08-022-2/+2
| |
* | - Use NULL instead of 0 for pointers.marius2013-08-024-7/+5
| | | | | | | | - Remove unnecessary __RMAN_RESOURCE_VISIBLE.
* | - Implement iclear methods for QUICC and SAB 82532. With r253161 in place,marius2013-08-023-24/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | this is is crucial at least for the latter. What happens is that attaching uart(4) to scc(4) causes the SAB 82532 to "receive" something and trigger a SER_INT_RXREADY interrupt, given that at least fast/filter interrupts are already enabled. Prior to r253161, uart_bus_ihand() was set up at this point and handled that condition, i. e. read the RX FIFO and issued a Receive Message Complete. Now, uart_bus_ihand() and uart_intr() are setup after attaching uart(4), leaving the SER_INT_RXREADY interrupt triggered during the latter to be handled by the iclear method. However, with that method not implement, this in turn causes SAB 82532 to not issue any further SER_INT_RXREADY interrupts until the RX FIFO is full again. Thus, 15 received bytes go to nowhere, given that "the other half" of the RX FIFO is used for status information. Hence, implementing sab82532_bfe_iclear() fixes things again. Potentially, the same problem exists for QUICC. - Remove unnecessary __RMAN_RESOURCE_VISIBLE. - Remove a superfluous header. - Use KOBJMETHOD_END. - Mark unused arguments as such. - Remove variables unused after initialization. Reviewed by: marcel (earlier version)
* | Add in some definitions required for later iwn(4) device support.adrian2013-08-021-5/+259
| | | | | | | | | | | | | | | | | | | | This also clarifies a few existing fields. Tested: * Intel 5100 Submitted by: Cedric GROSS <cg@gross.info>
* | Break out the iwn(4) device IDs into if_iwn_devid.h, as well as addadrian2013-08-023-48/+331
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | IDs for new devices. * Add new device IDs * Extend the ID probe code to include the newer range of bits used by later model devices Tested: * Intel 5100, STA mode TODO: * Test on Intel 4965, just to be sure Submitted by: Cedric GROSS <cg@gross.info>
* | Only receive the interrupts on the first core, to avoid duplicate interrupts.cognet2013-08-021-1/+1
| |
* | Update serf 1.2.1 -> 1.3.0 for svnpeter2013-08-0248-13346/+1802
|\ \
| * | Import serf-1.3.0peter2013-08-0247-13345/+1801
| | |
* | | Display temperature sensor data. Shows -1 if sensor notnp2013-08-021-0/+30
| | | | | | | | | | | | | | | | | | | | | available on the card. # sysctl dev.t4nex.0.temperature # sysctl dev.t5nex.0.temperature
* | | Fix previous commit (r253873). "cong" has one bit per channel but thenp2013-08-021-1/+10
| | | | | | | | | | | | | | | congestion channel map has 1 nibble per channel. So bits wxyz need to be blown up into 000w000x000y000z.
* | | Add p_candebug() check to FILEMON_SET_PID ioctl.hrs2013-08-021-1/+8
| | | | | | | | | | | | | | | Discussed with: sjg MFC after: 3 days
* | | find: Allow -delete to delete files given as arguments.jilles2013-08-022-1/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Formerly, a command like find dir1/dir2 -delete would delete everything under dir1/dir2 but not dir1/dir2 itself. When -L is not specified and "." can be opened, the fts(3) code underlying find(1) is careful to avoid following symlinks or being dropped in different locations by moving the directory fts is currently traversing. If a problematic concurrent modification is detected, fts will not enter the directory or abort. Files found in the search are returned via the current working directory and a pathname not containing a slash. For paranoia, find(1) verifies this when -delete is used. However, it is too paranoid about the root of the traversal. It is already assumed that the initial pathname does not refer to directories or symlinks that might be replaced by untrusted users; otherwise, the whole traversal would be unsafe. Therefore, it is not necessary to do the check for fts_level == FTS_ROOTLEVEL. Deleting the pathnames given as arguments can be prevented without error messages using -mindepth 1 or by changing directory and passing "." as argument to find. This works in the old as well as the new version of find. Tested by: Kurt Lidl Reviewed by: jhb
* | | Remove extra zeroing after M_ZERO allocation.glebius2013-08-021-2/+0
| | |
* | | Merge bmake-20130730sjg2013-08-0226-172/+369
| | | | | | | | | | | | | | | Main feature of interest is .MAKE.JOB.PREFIX= to suppress --- job --- tokens.
* | | Set up congestion manager context properly for T5 based cards.np2013-08-011-0/+16
| | | | | | | | | | | | MFC after: 3 days (will check with re@)
* | | Teach cxgbetool to display T5 congestion manager context.np2013-08-011-1/+12
| | |
* | | Now that conf/options knows about if_iwn.h, add it to if_iwn.c.adrian2013-08-011-0/+1
| | | | | | | | | | | | | | | This allows for IWN_DEBUG (and maybe more stuff later) to be a build time configure option.
* | | Add IWN_DEBUG as an option for if_iwn.adrian2013-08-011-0/+3
| | |
* | | iwn(4) debugging improvements.adrian2013-08-012-11/+113
| | | | | | | | | | | | | | | | | | | | | | | | * Add in some new register debugging under IWN_DEBUG_REGISTER * Make IWN_DEBUG an option now for building. I'll chase this up with a commit to 'options' soon. Submitted by: Cedric GROSS <cg@cgross.info>
* | | A number of important fixes:jfv2013-08-011-24/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - mbuf reused after an RX_COPY optimized operation can sometimes have a bogus cached address, resulting in TCP hangs. Add critical save points to the cached address. Thanks to Michael and the team at Verisign for finding this problem. - A couple more spots where the rxbuf->flags member should be cleared just to be sure no incorrect RX_COPY state is left around. Thanks to Adrian for tracking these down. - Remove the rearm_queues function from the driver, this was found to be responsible for some out-of-order packets by Verisign, and was always a bandaid, with the other fixes in this delta the bandaid can finally be removed. - In the other/link interrupt handler the entire state of the EICS register was being writen back into EICR (which clears causes and thus re-enables those interrupts), this was wrong, so now mask off the queue portion of the register value, so we only clear the other/link interrupt we intend. Marc from Verisign found this. - Make the SFP+ unsupported option tuneable now, by customer request. - Finally, just a couple of minor DEBUG string fixes. I want to call out and thank all the participants in the 10G community/Intel calls for helping track down these problems and make the driver better for everyone! MFC after: 3 days, these are critical fixes for 9.2!
* | | Fix the build of the testmain target. This target compiles a Forthmarcel2013-08-011-4/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | interpreter that can be run on the system and as such cannot be compiled against libbstand. On the one hand this means we need to include the usual headers for system interfaces that we use and on the the other hand we can only use standard system interfaces. While here, define local variables only when needed to make this WARNS=2 clean on amd64. PR: 172542 Obtained from: peterj@ Pointed out by: Jan Beich <jbeich@tormail.org>
* | | Add license for the half MD4 algorithm used in ext2_half_md4().pfg2013-08-011-5/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The htree implementation uses code derived from the RSA Data Security, Inc. MD4 Message-Digest Algorithm. Add a proper licensing statement for the code and clarify the corresponding comments. Approved by: core (hrs)
* | | Remove unused malloc type.kib2013-08-011-2/+0
| | | | | | | | | | | | | | | Requested by: alc MFC after: 1 week
* | | Micro-optimization suggested intuexen2013-08-011-4/+3
| | | | | | | | | | | | | | | | | | | | | https://bugzilla.mozilla.org/show_bug.cgi?id=898234 by pchang9. While there simplify the code. MFC after: 1 week
* | | Add identification for Cortex-A7 (R0) cores.ganbold2013-08-013-1/+5
| | | | | | | | | | | | Reviewed by: cognet@
* | | Moved clearing of vmm_initialized to avoid the casegrehan2013-08-011-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | of unloading the module while VMs existed. This would result in EBUSY, but would prevent further operations on VMs resulting in the module being impossible to unload. Submitted by: Tycho Nightingale (tycho.nightingale <at> plurisbusnetworks.com) Reviewed by: grehan, neel
* | | Include /usr/local/etc/libmap.d/ by default.jlh2013-08-012-0/+3
| | | | | | | | | | | | | | | | | | | | | PR: 180568 Reviewed by: bapt Obtained from: kib MFC after: 3 days
* | | Fix boundary check of sockaddr array.hrs2013-08-011-3/+2
| | | | | | | | | | | | Reported by: uqs
* | | Properly print arguments to vfork(2) and rfork(2).markj2013-08-012-1/+12
| | | | | | | | | | | | | | | | | | PR: 180976 Submitted by: Yuri <yuri@tsoft.com> (original patch) MFC after: 1 week
* | | Correctly maintain the CR0/CR4 shadow registers.grehan2013-08-011-11/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was exposed with AP spinup of Linux, and booting OpenBSD, where the CR0 register is unconditionally written to prior to the longjump to enter protected mode. The CR-vmexit handling was not updating CPU state which resulted in a vmentry failure with invalid guest state. A follow-on submit will fix the CPU state issue, but this fix prevents the CR-vmexit prior to entering protected mode by properly initializing and maintaining CR* state. Reviewed by: neel Reported by: Gopakumar.T @ netapp
* | | Changes to allow using BOOTP_NFSROOT and mounting an nfs root filesystemian2013-07-312-21/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | other than the one specified by the BOOTP server. This configures NFS using the BOOTP protocol while also respecting other root-path options such as setting vfs.root.mountfrom in the environment or using the RB_DFLTROOT boot option. It allows you to override the root path provided by the server, or to supply a root path when the server provides IP configuration but no root path info. This maintains the historical BOOTP_NFSROOT behavior of panicking on a failure to mount the root path provided by the server, unless you've provided an alternative via the ROOTDEVNAME kernel option or by setting vfs.root.mountfrom. The behavior of panicking when given no other options is preserved because it amounts to a bit of a retry loop that could eventually recover from a transient network or server problem. The user can now override the root path from loader(8) even if the kernel is compiled with BOOTP_NFSROOT. If vfs.root.mountfrom is set in the environment it is used unconditionally -- it always overrides the BOOTP info. If it begins with [old]nfs: then the BOOTP code uses it instead of the server-provided info. If it specifies some other filesystem then the bootp code will not panic like it used to and the code in vfs_mountroot.c will invoke the right filesystem to do the mount. If the kernel is compiled with the ROOTDEVNAME option, then that name is used by the BOOTP code if either * The server doesn't provide a pathname. * The boothowto flags include RB_DFLTROOT. The latter allows the user to compile in alternate path in ROOTDEVNAME such as ufs:/dev/da0s1a and boot from that path by setting boot_dftlroot=1 in loader(8) or using the '-r' option in boot(8). The one thing not provided here is automatic failover from a server-provided path to a compiled-in one without the user manually requesting that. The code just isn't currently structured in a way that makes that possible with a lot of rewrite. I think the ability to set vfs.root.mountfrom and to use ROOTDEVNAME automatically when the server doesn't provide a name covers the most common needs. A set of patches submitted by Lars Eggert provided the part I couldn't figure out by myself when I tried to do this last year; many thanks. Reviewed by: rodrigc
* | | Add myself as maintainer for nvme(4), nvd(4) and nvmecontrol(8).jimharris2013-07-311-0/+3
| | |
* | | Back out r253779 & r253786.obrien2013-07-3186-564/+140
| | |
* | | Adjust magic numbers to allow attachment of ath(4) modules.sbruno2013-07-311-2/+2
| | |
* | | Document net.link.bridge.allow_llz_overlap.hrs2013-07-311-9/+9
| | |
* | | device if_bridge gets me a bridge devicesbruno2013-07-311-1/+1
| | |
* | | Allocate in6_ifextra (ifp->if_afdata[AF_INET6]) only for IPv6-capablehrs2013-07-313-8/+12
| | | | | | | | | | | | | | | | | | | | | interfaces. This eliminates unnecessary IPv6 processing for non-IPv6 interfaces. MFC after: 3 days
* | | Another fix for r253823; retain the default of 1 readahead block for sendfile.scottl2013-07-311-1/+1
| | | | | | | | | | | | | | | | | | Submitted by: glebius Obtained from: Netflix MFC after: 3 days
* | | Change default behaviour of ld(1) to not recursively copy DT_NEEDEDbapt2013-07-311-1/+1
| | | | | | | | | | | | | | | This is the default behaviour of the newer binutils as well as most alternative linkers. All the ports tree has been fixed to be able to link properly with this new behaviour.
* | | Make two buffer variables static for now. It is not safe todelphij2013-07-311-1/+1
| | | | | | | | | | | | | | | | | | reference stack memory after return. MFC after: 2 weeks
* | | Resolve fflag with realpath().delphij2013-07-311-1/+3
| | | | | | | | | | | | MFC after: 2 weeks
* | | Add definitions for the Mailbox, Spinlock and PRU-ICSS devices.rpaulo2013-07-311-0/+19
| | |
* | | Cleanup the allocations when the attachment fails.rpaulo2013-07-311-5/+8
| | |
* | | Initialisation routines for the mailbox, spinlock and PRU-ICSS clocks.rpaulo2013-07-312-1/+79
| | |
* | | Display SGE tunables in the sysctl tree.np2013-07-313-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | dev.t5nex.0.fl_pktshift: payload DMA offset in rx buffer (bytes) dev.t5nex.0.fl_pad: payload pad boundary (bytes) dev.t5nex.0.spg_len: status page size (bytes) dev.t5nex.0.cong_drop: congestion drop setting Discussed with: scottl
* | | Document the -S flag to fsck_ffsscottl2013-07-311-1/+6
| | | | | | | | | | | | Obtained from: Netflix
* | | When using tcpdump -I -i wlanN and wlanN is not a monitor mode VAP,rpaulo2013-07-311-0/+23
| | | | | | | | | | | | | | | | | | tcpdump will print an error message saying rfmon is not supported. Give a concise explanation as to how one might solve this problem by creating a monitor mode VAP.
* | | Remove duplicate SRCS include block. Spotted by jmallett.jhibbits2013-07-311-5/+0
| | |
* | | Add the macio attachment for wi(4). Partially obtained from NetBSD.jhibbits2013-07-315-0/+203
| | | | | | | | | | | | | | | Reviewed by: adrian Obtained from: NetBSD (partially)
* | | Fix r253823. Some WIP patches snuck in.scottl2013-07-302-21/+7
| | | | | | | | | | | | Submitted by: zont
OpenPOWER on IntegriCloud