summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Refactor the test/ Makefiles after recent changes to bsd.test.mk (r289158) andngie2015-10-12121-321/+69
| | | | | | | | | | | | netbsd-tests.test.mk (r289151) - Eliminate explicit OBJTOP/SRCTOP setting - Convert all ad hoc NetBSD test integration over to netbsd-tests.test.mk - Remove unnecessary TESTSDIR setting - Use SRCTOP where possible for clarity MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Divison
* net80211 drivers: eliminate any references to sc_rxtap_len/sc_txtap_len ↵adrian2015-10-1214-31/+2
| | | | | | | (never used here) Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3776
* urtwn(4): split *reg and *var parts (no functional change).adrian2015-10-124-192/+208
| | | | | Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3775
* net80211: move ieee80211_free_node() call on error from ic_raw_xmit() to ↵adrian2015-10-1223-70/+11
| | | | | | | | | | ieee80211_raw_output(). This doesn't free the mbuf upon error; the driver ic_raw_xmit method is still doing that. Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3774
* net80211: free node reference in the ieee80211_parent_xmitpkt() when error ↵adrian2015-10-128-39/+19
| | | | | | | | | | happened. Move error handling into ieee80211_parent_xmitpkt() instead of spreading it between functions. Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3772
* wpi(4): add support for TX fragmentation.adrian2015-10-123-28/+96
| | | | | | | | Tested: * Tested with Intel 3945BG, HOSTAP and STA modes Differential Revision: https://reviews.freebsd.org/D3770
* net80211: separate mbuf cleanup from ieee80211_fragment()adrian2015-10-127-52/+31
| | | | | | | | | | | | * Create ieee80211_free_mbuf() which frees a list of mbufs. * Use it in the fragment transmit path and ath / uath transmit paths. * Call it in xmit_pkt() if the transmission fails; otherwise fragments may be leaked. This should be a big no-op. Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3769
* Revert r289150:pfg2015-10-121-1/+0
| | | | | | | | Correct handling of enum attributes with g++ It is causing issues on some platforms. Reported by: sbruno (through adrian)
* sh: Make struct arglist an array instead of a linked list.jilles2015-10-116-215/+136
| | | | | | | | | | | This simplifies the code (e.g. allowing use of qsort(3) instead of a hand-rolled mergesort) and should have better cache properties. The waste of unused args arrays after resizes is approximately the same as the savings from getting rid of the next pointers. At the same time, remove a piece of global state and move some duplicated code into a function.
* Default TESTSDIR to /usr/tests/${RELDIR:H}ngie2015-10-112-4/+9
| | | | | | | | | | | | | | | When run from bin/ls/tests, for example, the value of TESTSDIR would be ${TESTSBASE}/${RELDIR:H} -> /usr/tests/bin/ls/tests/.. -> /usr/tests/bin/ls Document the new behavior in bsd.README. While here, also document TESTSBASE Relnotes: yes Differential Revision: D1022 MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
* NTB: MFV c336acd3: memcpy lockup workaroundcem2015-10-111-2/+3
| | | | | | | | | | The system will appear to lockup for long periods of time due to the NTB driver spending too much time in memcpy. Avoid this by reducing the number of packets that can be serviced on a given interrupt. Authored by: Jon Mason Obtained from: Linux Sponsored by: EMC / Isilon Storage Division
* NTB: MFV c9d534c8: Correctly handle receive buffers of the minimal sizecem2015-10-111-3/+5
| | | | | | | | | | | The ring logic of the NTB receive buffer/transmit memory window requires there to be at least 2 payload sized allotments. For the minimal size case, split the buffer into two and set the transport_mtu to the appropriate size. Authored by: Jon Mason Obtained from: Linux Sponsored by: EMC / Isilon Storage Division
* NTB: MFV 90f9e934: reset tx_index on link togglecem2015-10-111-2/+1
| | | | | | | | | | | If the NTB link toggles, the driver could stop receiving due to the tx_index not being set to 0 on the transmitting size on a link-up event. This is due to the driver expecting the incoming data to start at the beginning of the receive buffer and not at a random place. Authored by: Jon Mason Obtained from: Linux Sponsored by: EMC / Isilon Storage Division
* NTB: MFV b77b2637: Link toggle memory leakcem2015-10-111-0/+8
| | | | | | | | | | | | Each link-up will allocate a new NTB receive buffer when the NTB properties are negotiated with the remote system. These allocations did not check for existing buffers and thus did not free them. Now, the driver will check for an existing buffer and free it if not of the correct size, before trying to alloc a new one. Authored by: Jon Mason Obtained from: Linux Sponsored by: EMC / Isilon Storage Division
* NTB: MFV 113fc505: Handle 64bit BAR sizescem2015-10-111-34/+65
| | | | | | | | | | | | 64bit BAR sizes are permissible with an NTB device. To support them various modifications and clean-ups were required, most significantly using 2 32bit scratch pad registers for each BAR. Also, modify the driver to allow more than 2 Memory Windows. Authored by: Jon Mason Obtained from: Linux Sponsored by: EMC / Isilon Storage Division
* NTB: MFV cc0f868d: fix pointer math issuescem2015-10-111-2/+2
| | | | | | | | | ->remote_rx_info and ->rx_info are struct ntb_rx_info pointers. If we add sizeof(struct ntb_rx_info) then it goes too far. Authored by: Dan Carpenter Obtained from: Linux Sponsored by: EMC / Isilon Storage Division
* Simplify netbsd-tests.test.mkngie2015-10-111-8/+4
| | | | | | | | | | | | | - projects/bmake and subsequent commits provide SRCTOP; there's no need to manually specify it now. - Compute a sane default for OBJTOP based on .OBJDIR and RELDIR. Manually specifying this is probably no longer needed, but it persists just in case (supporting commits will need to be made to move it out of some of the meta .mk files). - Compute a sane default for TESTSRC. Error out if the path cannot be found. MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
* Correct handling of enum attributes with g++pfg2015-10-111-0/+1
| | | | | | | | | | | | | From OpenBSD's commit log: This was responsible for memory corruption with recent versions of Mesa where c and c++ code share a header with a packed enum type. Reference: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39219 Obtained from: OpenBSD (CVS rev. 1.2) MFC after: 1 week
* Use existing CONFDIR instead of adding a new CONFIGDIRbapt2015-10-113-3/+2
| | | | Reported by: jbeich
* Correct flash layout (this is a 4M flash unit).sbruno2015-10-111-22/+15
| | | | | Remove "rootfs" entry and assign the 800K or so to the kernel partition as this unit boots from usb mass storage.
* Make delete method set via kern.cam.da.X.delete_method persistent.mav2015-10-112-48/+55
| | | | | | | | | This allows to set delete method via tunable, before device capabilities are known. Also allow ZERO method for devices not reporting LBP, if user explicitly requests it -- it may be useful if storage supports compression and WRITE SAME, but does not support UNMAP. MFC after: 2 weeks
* Fix build with gcc 4.2bapt2015-10-113-3/+3
|
* Remove legacy CHS geometry from dmesg and unify capacity outputs.mav2015-10-113-17/+11
|
* Remove compatibility shims for legacy ATA device names.mav2015-10-1123-141/+11
| | | | | We got new ATA stack in FreeBSD 8.x, switched to it at 9.x, completely removed old stack at 10.x, so at 11.x it is time to remove compat shims.
* Remove lock upgrade attempt from ctl_be_block_open_file().mav2015-10-111-15/+0
| | | | | | | | I am not sure what for it was done. Now open routine should automatically fall back to read-only if open for writing is impossible. In such case attempt to upgrade to write sounds strange. MFC after: 1 week
* Use machine specific values cleaned from openwrt for the mac addresssbruno2015-10-111-1/+3
| | | | location on the TP link mr3020
* wpi(4): do not count failures twice for ic_raw_xmit().adrian2015-10-111-10/+3
| | | | | | | | | Tested: * Tested with Intel 3945BG, STA mode Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3768
* wpi(4): move error handling upper (wpi_tx_data()/wpi_cmd2() -> ↵adrian2015-10-111-30/+31
| | | | | | | | | | | wpi_raw_xmit()/wpi_transmit()). Tested: * Tested with Intel 3945BG, STA mode Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3767
* wpi(4): fix possible race between TX/RX threads.adrian2015-10-111-0/+2
| | | | | | | | | Tested: * Tested with Intel 3945BG, STA mode Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3766
* wpi(4): do not allocate space for unused rings.adrian2015-10-112-14/+4
| | | | | | | | | Tested: * Tested with Intel 3945BG, STA mode Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3765
* wpi(4): do not override iv_recv_mgmt() in non-adhoc modes.adrian2015-10-111-6/+7
| | | | | | | | | Tested: * Tested with Intel 3945BG, IBSS and STA modes Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3764
* wpi(4): use more correct types.adrian2015-10-113-55/+67
| | | | | | | | | This change fixes some amount of -Wsign-conversion and -Wconversion warnings and sets correct sizes for some variables (as a result, some loop counters were touched too). Submitted by: <s3erios@gmail.com> Differential Revision: https://reviews.freebsd.org/D3763
* Update Dragonfly Mail Agent to v0.10bapt2015-10-1039-1171/+114
|
* Replace a local sx lock that allowed only one client at a time to accessian2015-10-101-12/+11
| | | | | an eeprom device with iicbus_request/release_bus(), which achieves the same effect and also keeps other i2c slave drivers from clashing on the bus.
* There's no way a fbsd install + kernel will fit into 4MB of flash.sbruno2015-10-101-13/+3
| | | | | Assume and enforce the fact that this will always boot a rootfs from usb.
* Remove a double "as well as"phk2015-10-101-3/+3
|
* Fix installing config files as non rootbapt2015-10-101-1/+3
| | | | Reported by: adrian
* Install bsd.confs.mkbapt2015-10-105-4/+5
| | | | Rename ETCDIR into CONFIGDIR to avoid conflicts with the ports tree
* Add 'p' postfix to mdconfig(8).trasz2015-10-102-6/+9
| | | | | MFC after: 1 month Sponsored by: The FreeBSD Foundation
* Change the default setting of kern.ipc.shm_allow_removed from 0 to 1.trasz2015-10-102-5/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This removes the need for manually changing this flag for Google Chrome users. It also improves compatibility with Linux applications running under Linuxulator compatibility layer, and possibly also helps in porting software from Linux. Generally speaking, the flag allows applications to create the shared memory segment, attach it, remove it, and then continue to use it and to reattach it later. This means that the kernel will automatically "clean up" after the application exits. It could be argued that it's against POSIX. However, SUSv3 says this about IPC_RMID: "Remove the shared memory identifier specified by shmid from the system and destroy the shared memory segment and shmid_ds data structure associated with it." From my reading, we break it in any case by deferring removal of the segment until it's detached; we won't break it any more by also deferring removal of the identifier. This is the behaviour exhibited by Linux since... probably always, and also by OpenBSD since the following commit: revision 1.54 date: 2011/10/27 07:56:28; author: robert; state: Exp; lines: +3 -8; Allow segments to be used even after they were marked for deletion with the IPC_RMID flag. This is permitted as an extension beyond the standards and this is similar to what other operating systems like linux do. MFC after: 1 month Relnotes: yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D3603
* Provide better debug message on kernel module name clash.trasz2015-10-101-6/+2
| | | | | | Reviewed by: kib@ MFC after: 1 month Sponsored by: The FreeBSD Foundation
* Make geom_nop(4) collect statistics on all types of BIOs, not justtrasz2015-10-103-4/+47
| | | | | | | | | | reads and writes. PR: kern/198405 Submitted by: Matthew D. Fuller <fullermd at over-yonder dot net> MFC after: 1 month Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D3679
* drm/i915: Remove "Attempting to unbind pinned buffer" messagedumbbell2015-10-101-3/+1
| | | | | | | | This error message is removed in later versions of Linux and currently, it spams users. PR: 200712 MFC after: 1 week
* Update the AP135 reference design flash layout to be more useful.adrian2015-10-101-17/+28
| | | | | | | | | | | | | | | | | | | * Shuffle the kernel to be at the beginning * Give the kernel 2mb, the rootfs 6mb, and 'mib0' the rest * put the cfg parition just before the ART calibration data for the wifi part in the SoC * .. and make sure ART points to the right 64k region. I've updated the freebsd-wifi-build wiki the instructions on using this. If someone has an AP135 with 8MB SPI flash then this won't work; everything minus the big mib0 partition is just a bit over 8MB. Come see me if this ever happens (you'll likely just have to shrink the rootfs and the kernel a little in order to make it fit.) Tested: * AP135 reference board.
* Translate iic hardware layer status values to errno return values.ian2015-10-101-3/+9
|
* Add a short name, IIC_INTRWAIT, for the common case (IIC_INTR | IIC_WAIT).ian2015-10-101-0/+1
|
* iw_cxgbe: fix for page fault in cm_close_handler().np2015-10-101-8/+14
| | | | | | | | | | | | | | | | | | | | This is roughly the iw_cxgbe equivalent of https://github.com/torvalds/linux/commit/be13b2dff8c4e41846477b22cc5c164ea5a6ac2e ----------------- RDMA/cxgb4: Connect_request_upcall fixes When processing an MPA Start Request, if the listening endpoint is DEAD, then abort the connection. If the IWCM returns an error, then we must abort the connection and release resources. Also abort_connection() should not post a CLOSE event, so clean that up too. Signed-off-by: Steve Wise <swise@opengridcomputing.com> Signed-off-by: Roland Dreier <roland@purestorage.com> ----------------- Submitted by: Krishnamraju Eraparaju at chelsio dot com.
* Remove all of the syncsngie2015-10-101-10/+0
| | | | | | They're unnecessary as shown by further testing on my VM Requested by: jhb
* Flip on fast frames support for AR5416 and AR9300 series NICs.adrian2015-10-102-8/+2
| | | | | | | | | | | | | | | | | | | This was off because the net80211 aggregation code was using the same state pointers for both fast frames and ampdu tx support which led to some pretty unfortunate panic-y behaviour. Now that net80211 doesn't panic, let's flip this back on. It doesn't (yet) do the horrific sounding thing of A-MPDU aggregates of fast frames; that'll come next. It's a pre-requisite to supporting AMSDU + AMPDU anyway, which actually speeds things up quite considerably (think packing lots of little ACK frames into a single AMSDU.) Tested: * QCA955x SoC, AP mode * AR5416, STA mode * AR9170, STA mode (with local fast frame patches)
* Fix more cases of iicbus-layer functions that must return IIC_Exxxx values.ian2015-10-101-2/+2
|
OpenPOWER on IntegriCloud