summaryrefslogtreecommitdiffstats
path: root/sys/dev/pci (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* regenjsg2021-01-272-2/+177
|
* add some more amdgpu devicesjsg2021-01-271-1/+36
|
* do better accounting of how many msix interrupts we want to use.dlg2021-01-271-2/+8
| | | | ok jmatthew@
* intrmap attribute missing from mcx; ok dlgderaadt2021-01-261-3/+3
|
* raise the max number of queues/interrupts to 16, up from 1.dlg2021-01-251-3/+12
| | | | | | | | | jmatthew@ has tried this before, but hrvoje popovski experienced breakage so it wasn't enabled. we've tightened the code up since then so it's time to try again. this diff has been tested by hrvoje popovski and myself ok jmatthew@
* if the rx descriptor reports the rss hash, use it for the mbuf flowid.dlg2021-01-251-2/+10
| | | | ok jmatthew@
* don't lose the M_FLOWID flag if the ipv4 cksum is ok.dlg2021-01-251-2/+2
| | | | | found while poking around with hrvoje popovski yes jmatthew@
* use an intrmap when establishing interrupts for queues.dlg2021-01-251-21/+44
| | | | | | | mcx is still hardcoded/limited to 1 queue for now, but this lets different mcx devices use different cpus for handling packets. looks good jmatthew@
* match on Intel Alder Lake and Meteor Lake I219 Ethernet idsjsg2021-01-243-3/+30
|
* regenjsg2021-01-242-2/+47
|
* add Intel Alder Lake and Meteor Lake I219 Ethernet idsjsg2021-01-241-1/+10
|
* match on Realtek RTL8168H ids for Killer E2500V2 and E2600jsg2021-01-241-1/+3
| | | | checked against linux and windows drivers
* regenjsg2021-01-242-2/+12
|
* add Realtek RTL8168H ids for Killer E2500V2 and E2600jsg2021-01-241-1/+3
| | | | checked against linux and windows drivers
* match on another Realtek RTL8168 idjsg2021-01-231-1/+2
| | | | reported and tested by John Batteen on a TP-Link TG-3468
* regenjsg2021-01-232-2/+7
|
* add another Realtek RTL8168 idjsg2021-01-231-1/+2
| | | | shows up on a TP-Link TG-3468 John Batteen has
* Check management capabilities before trying to attach temperature sensors,jmatthew2021-01-201-1/+43
| | | | | | | | avoiding an unhelpful error message if the card's firmware doesn't expose the sensor registers. tested by chris@, who saw the unhelpful error message ok dlg@
* add another iwx devicejcs2021-01-172-11/+21
| | | | ok stsp jsg
* regenjcs2021-01-172-2/+7
|
* add another ax201jcs2021-01-171-1/+2
|
* this hardware is fine with BUS_DMA_64BIT mappings.dlg2021-01-171-4/+7
| | | | | | | | this raises performance of tcpbench on an m3000 from ~3kpps and ~8MB/s to ~70kpps and ~191MB/s when transmitting, and ~10kpps and ~15MB/s to ~120kpps and 174MB/s when receiving. i also tested this on a v245 and an m4000 a while back.
* recognise Realtek ALC287jsg2021-01-161-1/+4
|
* regenjsg2021-01-162-4/+109
|
* add devices mostly from x1 nano jcs@ hasjsg2021-01-161-2/+23
|
* revert drm vmalloc changesjsg2021-01-133-126/+39
| | | | | | | It is suspected they were to blame for a machine with inteldrm running X (xterms and chromium) running out of resources after a few days. ok kettenis@
* Bring the emulated Linux memory allocation interfaces more in line withkettenis2021-01-083-39/+126
| | | | | | | | | what Linux does. Let vmalloc() use km_alloc(9) instead of malloc(9) and let kvmalloc() only use malloc(9) for small (less than a page) allocations and atomic allocations. This should reduce the pressure on the "interrupt-safe" map. ok jsg@
* the tx doorbell is next to the rx doorbell, not on top of it.dlg2021-01-041-2/+2
|
* use bus_dmamap_sync around updates to the doorbells.dlg2021-01-041-33/+69
| | | | ok jmatthew@
* Remove useless redundant call of ttyopen().jan2021-01-011-6/+1
| | | | | | Also remove dead DIALOUT macro. ok mpi@
* don't oversleep when waiting on fencesjsg2020-12-311-15/+17
| | | | original diff from and ok cheloha@
* regenkettenis2020-12-282-2/+14
|
* Add Synopsys vendor and their DesignWare PCIe bridge.kettenis2020-12-281-1/+5
|
* have mcx_process_txeof return the number of slots it processed.dlg2020-12-271-7/+8
| | | | | | | it used a pointer in an argument to communicate that back to the caller, while being a void functon. this seems more natural and brings it in line with how the rx completion function returns free slots to its caller too.
* do a bus space barrier after arming the eq.dlg2020-12-271-2/+2
| | | | ok jmatthew@
* disable timestamping a little bit harder to avoid divide by 0.dlg2020-12-271-1/+5
| | | | | hrvoje popovski reports the current code faults on some boxes. i'm working on it, but the code isn't being used right now.
* shuffle filling the rx ring so the sw prod is updated before the hw.dlg2020-12-271-24/+19
| | | | ok jmatthew@
* reuse the calculated vector as the argument to pci_intr_map_msix.dlg2020-12-261-2/+2
| | | | doing the maths again feels error prone.
* add bus_dmamap_sync ops around the eq.dlg2020-12-261-6/+27
| | | | ok jmatthew@
* add some bus_dmamap_syncs around the rq.dlg2020-12-261-2/+16
| | | | ok jmatthew@
* sprinkle some bus_dmamap_syncs around the cq handling.dlg2020-12-261-1/+14
| | | | ok jmatthew@
* sprinkle some bus_dmamap_syncs around the sq.dlg2020-12-261-2/+17
| | | | ok jmatthew@
* better manage the lifetime of the dmamem used for various rings.dlg2020-12-261-36/+65
| | | | ok jmatthew@
* expose the mcx timer as a timecounter.dlg2020-12-251-1/+30
| | | | | | | | | | this is mostly to help me better understand where i accumulate error when trying to sync the chip to the kernel clocks. ie, if im using mcx as the kernel clock source and my attempts to sync to it still produce errors, then my code is very wrong instead of slightly wrong. it's also fun and a tiny amount of code.
* match on Gemini Lake I2Cjsg2020-12-251-1/+9
| | | | | Makes touchpad work on Joel Carnat's Teclast F7 Plus laptop. Patch from James Hastings.
* Refactor klist insertion and removalvisa2020-12-251-4/+4
| | | | | | | | | | | | Rename klist_{insert,remove}() to klist_{insert,remove}_locked(). These functions assume that the caller has locked the klist. The current state of locking remains intact because the kernel lock is still used with all klists. Add new functions klist_insert() and klist_remove() that lock the klist internally. This allows some code simplification. OK mpi@
* regenjsg2020-12-242-4/+76
|
* add some NVMe devices and Intel Comet Lake host bridgesjsg2020-12-241-2/+18
|
* ramdisks do not contain WOLderaadt2020-12-241-1/+3
|
* Add Wake on LAN support to rge(4).kevlo2020-12-242-3/+86
| | | | Tested by otto@ and myself.