-
[automated] Merge in upstream-github/master
lattera committedApr 9, 2014 -
Add a function to check whether the given register can be accessed wh…
adrian authored and adrian committedApr 9, 2014 …ilst the chip is asleep. It's AR5416 and later specific; I'll add a HAL method to generalise it later. Tested: * AR5416, STA mode
-
Spell imgact_binmisc correctly
seanbruno committedApr 9, 2014 -
Bump osreldate for tracking SA-14:06
DarkHelmet433 committedApr 9, 2014
-
Another fix for r264274. Last moment cosmetic changes are evil!
amotin committedApr 8, 2014 -
sys/kern/imgact_binmisc.c -- free the right pointer mask vs magic
seanbruno committedApr 8, 2014 sys/sys/imagact_binmisc.h -- cleanup white space tabs vs spaces -- remove stray " in comment Submitted by: jmallett@ -
Also ignore files from Murcirial (.hg) and git (.git) when copying
bsdimp committedApr 8, 2014 file trees.
-
Actually, since this is what I thought I was doing, only allow the
seanbruno committedApr 8, 2014 binmisc code to be build on amd64/i386 for the kernel. Update NOTES with some indication of what this code is used for. Pointed out by jhb@ ... thanks! Submitted by: jhb@
-
Oops! Few quick fixes for r264274.
amotin committedApr 8, 2014 -
Handle single-byte reads from the bvmcons port (0x220) by returning
bsdjhb committedApr 8, 2014 0xff. Some guests may attempt to read from this port to identify psuedo-PNP ISA devices. (The ie(4) driver in FreeBSD/i386 is one example.) Reviewed by: grehan
-
Quick mdoc/whitespace/spelling pass, this needs some more work.
cbrueffer committedApr 8, 2014 -
Add support for SCSI UNMAP commands to CTL.
amotin committedApr 8, 2014 This patch adds support for three new SCSI commands: UNMAP, WRITE SAME(10) and WRITE SAME(16). WRITE SAME commands support both normal write mode and UNMAP flag. To properly report UNMAP capabilities this patch also adds support for reporting two new VPD pages: Block limits and Logical Block Provisioning. UNMAP support can be enabled per-LUN by adding "-o unmap=on" to `ctladm create` command line or "option unmap on" to lun sections of /etc/ctl.conf. At this moment UNMAP supported for ramdisks and device-backed block LUNs. It was tested to work great with ZFS ZVOLs. For file-backed LUNs UNMAP support is unfortunately missing due to absence of respective VFS KPI. Reviewed by: ken MFC after: 1 month Sponsored by: iXsystems, Inc
-
Put proper ${} around variable expansion. This fixes the build on 9.2
bsdimp committedApr 8, 2014 with fmake (which complained). Not sure why bmake didn't complain though...
-
Add Stacey Son's binary activation patches that allow remapping of
seanbruno committedApr 8, 2014 execution to a emumation program via parsing of ELF header information. With this kernel module and userland tool, poudriere is able to build ports packages via the QEMU userland tools (or another emulator program) in a different architecture chroot, e.g. TARGET=mips TARGET_ARCH=mips I'm not connecting this to GENERIC for obvious reasons, but this should allow the kernel module to be built by default and enable the building of the userland tool (which automatically loads the kernel module). Submitted by: sson@ Reviewed by: jhb@
-
(Re)connect sys/boot/amd64 to the build
emaste committedApr 8, 2014 Sponsored by: The FreeBSD Foundation
-
Fix NFS deadlock vulnerability. [SA-14:05]
delphij committedApr 8, 2014 Fix "Heartbleed" vulnerability and ECDSA Cache Side-channel Attack in OpenSSL. [SA-14:06]
-
Wakeup only one thread of added in r263978i at a time.
amotin committedApr 8, 2014 This slightly reduces lock congestion between threads. Submitted by: trasz
-
Add explicit casts to quiet warnings in libefi
emaste committedApr 8, 2014 Sponsored by: The FreeBSD Foundation
-
Revert r264132, disconnecting sys/boot/amd64 for now
emaste committedApr 8, 2014 Some 64-bit Ficl warnings broke tinderbox builds.
-
rayddteam committed
Apr 8, 2014 o Unmute terminal when done with driver replacement. o Move init fonts to early point. o Minor cleanup. MFC after: 6 days X-MFC-with: r264244 r264242 Sponsored by: The FreeBSD Foundation
-
Fix cursor color in reverse video mode.
rayddteam committedApr 8, 2014 PR: kern/188196 Submitted by: Claude Buisson <clbuisson@orange.fr> (original version) MFC after: 1 week Sponsored by: The FreeBSD Foundation
-
Distinguish between the different variants and configurations of Sunix
sparcplug committedApr 8, 2014 {MIO,SER}5xxxx chips instead of treating all of them as PUC_PORT_2S. Among others, this fixes the hang seen when trying to probe the none- existent second UART on an actually 1-port chip. Obtained from: NetBSD (BAR layouts) MFC after: 3 days Sponsored by: Bally Wulff Games & Entertainment GmbH -
Add some debugging and forcing of the BAW to match what the current
adrian authored and adrian committedApr 8, 2014 tracked BAW actually is. The net80211 code that completes a BAR will set tid->txa_start (the BAW start) to whatever value was called when sending the BAR. Now, in case there's bugs in my driver code that cause the BAW to slip along, we should make sure that the new BAW we start at is actually what we currently have it at, not what we've sent. This totally breaks the specification and so this stays a printf(). If it happens then I need to know and fix it. Whilst here, add some debugging updates: * add TID logging to places where it's useful; * use SEQNO().
-
Don't do continue inside the scheduler loop; we really need to check
adrian authored and adrian committedApr 8, 2014 if we've hit the end of the list and cycled around to the first node again. Obtained from: DragonflyBSD
-
Correct the actual definition of ath_tx_tid_filt_comp_single() to
adrian authored and adrian committedApr 8, 2014 match how it's used. This is another bug that led to aggregate traffic hanging because the BAW tracking stopped being accurate. In this instance, a filtered frame that exceeded retries would return a non-error, which would mean the caller would never remove it from the BAW. But it wouldn't be added to the filtered list, so it would be lost forever. There'd thus be a hole in the BAW that would never get transmitted and this leads to a traffic hang. Tested: * Routerstation Pro, AR9220 AP
-
Add a comment explaining the obvious.
adrian authored and adrian committedApr 8, 2014 -
Don't resume a TID on each filtered frame completion - only do it if
adrian authored and adrian committedApr 8, 2014 we did suspend it. The whole suspend/resume TID queue thing is supposed to be a matched reference count - a subsystem (eg addba negotiation, BAR transmission, filtered frames, etc) is supposed to call pause() once and then resume() once. ath_tx_tid_filt_comp_complete() is called upon the completion of any filtered frame, regardless of whether the driver had aleady seen a filtered frame and called pause(). So only call resume() if tid->isfiltered = 1, which indicates that we had called pause() once. This fixes a seemingly whacked and different problem - traffic hangs. What was actually going on: * There'd be some marginal link with crappy behaviour, causing filtered frames and BAR TXing to occur; * A BAR TX would occur, setting the new BAW (block-ack window) to seqno n; * .. and pause() would be called, blocking further transmission; * A filtered frame completion would occur from the hardware, but with tid->isfiltered = 0 which indiciates we haven't actually marked the queue yet as filtered; * ath_tx_tid_filt_comp_complete() would call resume(), continuing transmission; * Some frames would be queued to the hardware, since the TID is now no longer paused; * .. and if some make it out and ACked successfully, the new BAW may be seqno n+1 or more; * .. then the BAR TX completes and sets the new seqno back to n. At this point the BAW tracking would be loopy because the BAW start was modified but the BAW ring buffer wasn't updated in lock step. Tested: * Routerstation Pro + AR9220 AP
-
[automated] Merge in upstream-github/master
lattera committedApr 8, 2014 -
rpaulo authored and rpaulo committed
Apr 8, 2014 * Define support for the SDHCI driver, although it doesn't work yet * Fix the memory mappings for IPU [1] Reviewed by: ray [1]
-
Add a basic set of data points which count the number of sleep entries
adrian authored and adrian committedApr 8, 2014 that are being done by the OS. For now this'll match up with the "wakeups"; although I'll dig deeper into this to see if we can determine which sleep state the CPU managed to get into. Most things I've seen these days only expose up to C2 or C3 via ACPI even though the CPU goes all the way down to C6 or C7.
-
kevlo authored and kevlo committed
Apr 8, 2014