| Age | Commit message (Collapse) | Author | Files | Lines |
|
methods are present. Should fix the panic that occurs on older ThinkPads
(such as the x201) when you press the ThinkLight key.
|
|
Based on a diff from Mathieu <naabed AT poolp DOT org>.
|
|
|
|
found via key dump diff, run by Bryan Vyhmeister
also remove 3 temperature keys which likely do not return useful values
verified with help from macbook pro output of tb (4,1 and 5,5),
kettenis (12,1), and Cristoph R. Murauer (9,1) via misc@
|
|
encountered via key dump diff, run by Bryan Vyhmeister
|
|
hint from kettenis
|
|
machines that have both the keyboard backlight and the thinklight (x230, t430)
quite right yet.
ok jung@ (for a slightly different version of this diff)
|
|
Adds support for HT MCS 0-7 (theoretical limit 65 Mbit/s) and the
reception of A-MSDU and A-MPDU aggregated frames.
None of the optional 11n features are supported for now.
MIMO, 40Mhz channels, short guard interval, etc. are left for future work.
And we're not sending A-MSDU or A-MPDU frames yet either.
Tested with various 11a/b/g/n access points. With some APs I'm seeing
a noticable increase in throughput, especially on 5Ghz.
Also, fix automatic rate selection by using the current Tx rate selected
by AMRR as the upper bound for the firmware's rate table and updating the
firmware's table whenever AMRR switches Tx rate, rather than setting the
table just once after association and ignoring AMRR updates.
ok mpi@ krw@ (earlier version), ok jasper@
|
|
|
|
For now this only supports the true ThinkLight. Support for the keyboard
backlight found on the most recent ThinkPads will follow soon.
ok jung@
|
|
|
|
|
|
mikeb@ doesn't like the Ids, "somebody else has to add them".
|
|
speedup interrupt handling on virtual machines. Unfortunately it is
broken on Xen 4.2 or older, so use the early pvbus detection to drop
the advertised x2APIC CPU feature. Xen has fixed this in late 2013,
but the problem still shows up in "the Cloud" (it doesn't seem to
affect others as they either use legacy APIC or Xen IPIs).
OK mlarkin@ mikeb@
Cvs: ----------------------------------------------------------------------
|
|
tested by Bryan Vyhmeister, krw, tb, and myself
ok krw tb
|
|
(bios, CPU, interrupt handlers, pvbus). This splits the pvbus attach
function into two parts: pvbus_identify() to scan the CPUID registers
for supported hypervisors and pvbus_attach() to attach the bus, print
information, and configure the children.
This will be needed for Xen and KVM, as discussed with mikeb@ and sf@
OK mlarkin@
|
|
tested by Bryan Vyhmeister, krw, tb, and myself
ok jcs krw tb
|
|
|
|
|
|
command and propagate the result
|
|
similar to config_defer(9).
ok mikeb@, deraadt@
|
|
|
|
|
|
Do not set the "Port Number", "Hub Address" and "Split Completion Mask"
fields in Isochronous Queue Heads for high-speed devices.
These fields should be ignored by the host controller unless the EPS
field indicates a full- or low-speed device, but that's not the case
with Nvidia controllers.
From NetBSD via miod@
|
|
accelerator drivers. No longer used by anything. ok sthen@ mikeb@
|
|
|
|
tweak it to use ifq_restart so ifq_clr_oactive is serialised with start.
ok jmatthew@
|
|
Apparently length values returned by XenStore depend on which
operation has been requested: for instance XS_READ will always
return an strlen() result without accounting for the trailing
NUL character, however XS_LIST will return length that includes
it. While staying within our data buffer limit (xsm_dlen) we
can readjust the length of the resulting string accordingly.
|
|
this is handled in audio(4) layer. From
Alexey Suslikov <alexey.suslikov at gmail.com>
|
|
|
|
|
|
|
|
also some KNF and whitespace cleanup while here
initial diff from William Orr with some tweaks by me
ok jcs mpi
|
|
(HBR2) for Broadwell and non-ULX Haswell DisplayPort. This enables
support for 3840x2160 60Hz SST.
Initial patch from and tested by Scot Doyle.
drm/i915: Enable 5.4Ghz (HBR2) link rate for Displayport 1.2-capable devices
from Todd Previte
06ea66b6bb445043dc25a9626254d5c130093199
drm/i915: don't try DP_LINK_BW_5_4 on HSW ULX
from Paulo Zanoni
9bbfd20abe5025adbb0ac75160bd2e41158a9e83
drm/i915/dp: add missing \n in the TPS3 debug message
from Jani Nikula
f8d8a672f9370278ae2c9752ad3021662dbc42fd
drm/i915/dp: only use training pattern 3 on platforms that support it
from Jani Nikula
7809a61176b385ebb3299ea43c58b1bb31ffb8c0
|
|
work is represented by struct task.
the start routine is now wrapped by a task which is serialised by the
infrastructure. if_start_barrier has been renamed to ifq_barrier and
is now implemented as a task that gets serialised with the start
routine.
this also adds an ifq_restart() function. it serialises a call to
ifq_clr_oactive and calls the start routine again. it exists to
avoid a race that kettenis@ identified in between when a start
routine discovers theres no space left on a ring, and when it calls
ifq_set_oactive. if the txeof side of the driver empties the ring
and calls ifq_clr_oactive in between the above calls in start, the
queue will be marked oactive and the stack will never call the start
routine again.
by serialising the ifq_set_oactive call in the start routine and
ifq_clr_oactive calls we avoid that race.
tested on various nics
ok mpi@
|
|
|
|
|
|
Discussed with deraadt@, kettenis@, mpi@, OK mlarkin, mpi
|
|
network interface) in order to attach a paravirtualized drivers
(such as Xen Netfront).
OK mlarkin
|
|
XenStore provides a hierarchical storage for Xen configuration
in a style of an OpenFirmware. Itself it's an interrupt driven
producer/consumer interface with two 1kb rings for input and
output.
It's required in order to do virtual device discovery and device
configuration (fetch MAC address, various parameters).
With input from and OK mlarkin, reyk
|
|
This is a simple driver for the virtual PCI device with only one
purpose: to allocate the interrupt vector and communicate that
to the Hypervisor in case the IDT callback method was not available.
With input from and OK deraadt, mlarkin, reyk, mpi
|
|
channel ports.
During boot, Xen will use polling mode, but once the system
enables interrupts after cpu_configure(), xen_intr_enable
will be called from the mountrook hook to unmask event ports.
OK mlarkin, mpi, reyk
|
|
OK mlarkin, reyk
|
|
This page provides a matrix of pending events and some other
information like hypervisor timecounter.
OK mlarkin, reyk
|
|
This page provides a matrix of pending events and some other
information like hypervisor timecounter.
OK mlarkin, reyk
|
|
and implements functions to fetch extended version and features.
OK mlarkin
|
|
and implements functions to fetch extended version and features.
OK mlarkin
|
|
With input from and OK mpi, mlarkin, reyk
|
|
With input from and OK mpi, mlarkin, reyk
|
|
prevent it from moving off-channel during association. The firmware issues
interrupts at beginning and end of the time event. The driver tried detecting
the beginning with a tsleep() in the newstate task followed by a wakeup()
from the interrupt handler. However, sometimes the newstate task did not get
scheduled until the time event had already passed, and association was aborted.
In rare cases the newstate task would even sleep forever and the iwm(4)
interface would stop working until reboot.
Fix these issues by issuing the time event and continuing association without
checking for a "go" from the firmware. Our kernel does not provide the
scheduling guarantees required for such precise synchronization so
association is more likely to fail with the additional check than without.
ok mpi@ tedu@
|