Age | Commit message (Collapse) | Author |
|
to include that than rdnvar.h. ok deraadt dlg
|
|
is unique; as done by hme(4).
ok deraadt@
|
|
internal speaker, line input and hp output. Tested on i386/amd64.
hints/help & ok ratchov@
|
|
1. Always unmask the slot context for the "Set Address" command.
2. Use the right spl when submitting a transfer to prevent from
setting up a timer on an already completed xfer.
Analyzed with and ok jsg@
|
|
PROT_NONE, PROT_READ, PROT_WRITE, and PROT_EXEC from mman.h.
PROT_MASK is introduced as the one true way of extracting those bits.
Remove UVM_ADV_* wrapper, using the standard names.
ok doug guenther kettenis
|
|
for NS Saturn based boards.
From NetBSD
ok deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
Since there's now no way to select maximum receive unit size the
hardware is programmed to accept frame sizes up to 9216 which is
now the maximum (down from 15.5K since this is supposed to work
in all advanced configurations and gives slightly better flow
control watermark ranges) and split all frames larger 2K into
multiple fragments (code was already there but wasn't enabled).
Tested on 82599 (SFP+) and X540 (10GBaseT).
With input from dlg@.
|
|
changed. This saves a lot of I/O when attaching/detaching devices
and might help with some timing related problems.
Has been in snap for ten days, committing now so that people testing
xhci(4) test the same thing w/ snapshots and their own kernel.
|
|
bugs that panic the kernel and it's unclear if any such device works at all.
Anyone in possession of a working AR9300 device that stops working with this
commit please talk to me. I've only seen evidence of this code not working.
ok kirby@ mpi@ phessler@ dcoppa@
|
|
the second "Set Address" command is issued. This would lead the
HC to reprocess TRBs corresponding to completed transfers.
This was the cause of the "xhci0: NULL xfer pointer" message that
could be seen after attaching a device and reported by naddy@.
|
|
|
|
|
|
This change fixes up SFP+ module detection during "ifconfig up"
after the machine has been booted without the modules plugged in.
|
|
since most of them can't be retrieved otherwise. This
comes with a slight but measurable performance increase
as well.
Also since the hardware has a single counter for missed
packets including those caused by the insufficient DMA
buffers available, this makes it hard to decipher actual
errors when used with Rx ring length limiting mechanisms
like if_rxr or mclgeti.
|
|
|
|
|
|
This code is violating various layers of abstraction, just like ehci(4)
does. Transaction translators need a bit more love.
|
|
|
|
Some Low/Full speed devices do not like to get a SET_ADDRESS command
before we have read (some bits of) their device descriptor. So change
the attach logic to issue two "Device Address" command with a BSR dance.
This should fix the "device problem, disabling port" error seen on root
hubs with some Low/Full speed devices, reported by miod@.
|
|
to the way USB buses are discovered.
|
|
context, not the whole array of endpoints. Yeah, pointers are hard.
Fix a panic reported by Dimitris Papastamos on tech@
|
|
sleep. This prevents accidental lid flex or slight opening in a backpack
from waking the machine up and leaving it resumed (powered on).
ok deraadt@
|
|
xHCI specification r1.1 are handled in this implementation. This is a
bit tricky because our bus interface is pipe-oriented. Hopefully this
will help other people squash the remaining bugs in this area.
|
|
protection.
Fix a panic reported by Patrick Wildt.
|
|
Without knowing their depth, hubs couldn't find the bits correspdonding
to their downstream port in the route-string. Now USB 3.0 devices just
work(tm) anywhere in your hub chain.
This commit would not have been possible without the cheese provided by
miod@ at #HAMoween.
|
|
ok mlarkin@
|
|
struct vga_pci_softc in vga_pcivar.h
Original diff from guenther@ changed to incorporate feedback
from kettenis@ and myself.
|
|
the i218 which is used in many modern laptops like the X240. This
seems to stop the watchdog timeouts triggered by heavy traffic on
such systems.
Tested by myself, phessler, blambert and Donovan Watteau
OK deraadt, brad
|
|
ok deraadt@
"Even though I admire the chutzpah of return(void), I agree". ok krw@
|
|
when the caller fills the entry.
|
|
to to the completion queue head doorbell instead of the submission queue
tail doorbell.
this lets us submit more than one command to the chip.
|
|
newer Yukon chipsets.
Pointed out by jsg@
|
|
work with xhci(4).
|
|
|
|
anything with it and it simplifies this mess in order to implement
warm reset.
|
|
|
|
|
|
|
|
might be NULL. Prevent from crashing in this case 8)
|
|
|
|
|
|
|
|
Even if it's very handy to know where a thread is sleeping in order to
debug HC drivers, users might not like to have to restart their machine
if a transfer timed and nothing will wakeup the discovery thread.
Note that I still haven't seen any hardware timeout in all my tests.
|
|
ok miod@
|
|
Prodded by a comment from stsp@.
|