Age | Commit message (Collapse) | Author |
|
and 1. As a result rgephy(4) attaches twice. Prevent this from happening
by passing the PHY address, which is part of the device tree, down from the
bus-specific glue to the generic driver code.
|
|
IWM_CMD_* values are bit flags. The same was done 2 years ago
in Linux git commit a10229271946731959b2269370d0492d88cfab23.
|
|
de is amazing(tm). it really should be cut back and simplified a bit.
|
|
drivers that fill that field in too.
quad types are going away.
|
|
guenther is proposing the removal of u_quad_t. uint64_t is more portable.
tested on a perc5 and perc6, no functional change.
|
|
GMAC core which is used on the Allwinner A20 SoCs and later SoCs in the
Allwinner family. Since this core is very likely to show up the base of
other devices, it gets to live here in dev/ic.
Ported from NetBSD (where it is named awge(4)) by patrick@. Some further
fixes by me.
ok deraadt@
|
|
ok jsg@, patrick@
|
|
workarounds. Some of them will soon stand in the way of armv7.
Off to the attic you go.
|
|
Lets Bacula find the end of medium on LTO5 drive.
Reported & fix tested by Kor son of Rynar.
ok mikeb@ deraadt@
|
|
|
|
interface marked UP and scheduling the init task. Matches iwn(4) behaviour.
|
|
|
|
ok patrick@
|
|
Rather than performing an atomic bit clearing for every encountered
event bit set we can adjust the code to perform an atomic swap of a
single row of the events array and decrease the amount of expensive
atomic operations.
Same optimization as for Hyper-V. From FreeBSD.
|
|
Rather than performing an atomic bit clearing for every encountered
event bit set we can adjust the code to perform an atomic swap of a
single row of the events array and decrease the amount of expensive
atomic operations.
From FreeBSD.
|
|
|
|
|
|
|
|
|
|
|
|
before suspending, in order to fix suspend/resume on some newer
machines.
more cleanup and TPM 2.0 support coming later.
earlier version ok pirofti
ok deraadt
|
|
|
|
This change adds a check into the Rx ring completion routine that
schedules an interrupt task to be executed immediately after if
consumer index has already advanced itself. The benefit of doing
this compared to an additional loop after replenishing the ring
(as done in FreeBSD for example) is that first of all this goes
through the loop in the taskqueue thread with a yeild check to
prevent CPU hogging and second is that it triggers Tx completion
as well since interrupt handler runs both.
|
|
Pending event bits are located in a shared memory and are potentially
accessed by multiple CPUs running dom0 and the guest VM. It appears
that a failure to synchronize changes to this shared memory leads to
race conditions resulting in the guest missing out on notifications.
|
|
shorten and simplify code.
No intentional functional change.
|
|
|
|
|
|
UFI command sets. Probe all the LUNs a device reports instead of
assuming ATAPI and UFI devices always have 1 LUN.
Motivated by the device David Vasek reported as claiming to be
ATAPI but wanting to use >1 LUN. Committing quickly to smoke out
the inevitable device that works in the exact opposite way. All
hail USB.
ok kettenis@
|
|
ok claudio@
|
|
|
|
|
|
hw.sensors.acpials0.illuminance0=11.00 lx (ambient light sensor)
|
|
|
|
In the Netfront case it appears that by having scheduler decide when
to run the workload we don't need to involve additional mechanisms
to artificially limit resource availability to achieve better
performance under heavy load. On the contrary, by performing a
single pass through Rx and Tx completion rings and having scheduler
decide when to run the next attempt, we limit the amount of time
spent in the packet processing and achieve system responsiveness.
|
|
Handling receive and transmit for multiple networking interfaces
in a "shared interrupt" within normal interrupt vector code path
introduces too much delay from the hypervisor POV which prevents
it from injecting further completion event interrupts for Rx and
Tx queues.
Additionally, Netfront backend driver includes a mechanism to
detect Rx ring stalls and "turn the carrier off" when the guest
is not replenishing the ring (e.g. due to missing completion
interrupts) that relies on guest waking up periodically and making
sure that the Rx ring completion handling is progressing.
Having tried both task queue + timeout and interrupts + timeout
approaches, it appears that using the task queue is more flexible
and provides superior performance under heavy network load.
|
|
|
|
|
|
|
|
|
|
acpicpu(4) drivers to the right cpu(4).
ok mlarkin@, guenther@
|
|
|
|
|
|
|
|
ok patrick@
|
|
|
|
ok mikeb@
|
|
used in the fdt attach args and the device tree.
ok kettenis@
|
|
Some code paths in this driver peek at ic_htcaps and act upon it, so let's
play it safe until this driver gets its 11n support enabled on purpose.
Spotted while investigating the bug fixed in r1.35.
|
|
ok deraadt@
|
|
Repairs urtwn(4) on macppc. Problem reported by juanfra@.
ok millert@ deraadt@
|