- User Since
- Nov 27 2014, 10:57 AM (273 w, 19 h)
Tue, Feb 11
Mon, Feb 10
The pcie_discovery_data is device specific, move it to the softc.
Move the root memory to the softc and switch it to use bus_space.
While here create a common function to get the correct bus_space
details for a given bus/slot/func/reg combination.
Move the driver to dev/pci/controller/
what about dev/pci/controller/? linux does that.
We have a similar subdirectory for MMC drivers: dev/mmc/host/ that works well and keeps dev/mmc/ clean
Sat, Feb 8
Fri, Feb 7
move the driver by request from jhb@
Thu, Feb 6
Wed, Feb 5
Mon, Feb 3
Sat, Feb 1
Thu, Jan 30
o Address mmel's comment.
o Don't override MSI methods since Andrew has fixed a bug in the ITS driver
Include pcI_n1sdp to the build
Wed, Jan 29
Add comment for MSI/MSIx
Override MSI/MSIx pcib methods so MSI allocation fail and INTx are used.
MSI/MSIx don't work for now
Tue, Jan 28
Address Andrew's comments: use kva_alloc/pmap_enter for non-device memory
Mon, Jan 27
Fri, Jan 24
Thu, Jan 23
Rename the driver to dev/xilinx/xlnx_pcib.[ch] per request from jhb@
Jan 17 2020
Dec 30 2019
Dec 29 2019
Looks good. Thank you!
Dec 4 2019
Nov 14 2019
Nov 11 2019
Nov 4 2019
Oct 28 2019
I also have a comment from jhb@:
@br typically we only route device interrupts to a single core since interrupt handlers generally assume they are not run concurrently (interrupt filters, ithreads will be single-threaded even if the interrupt is broadcast)
as Andy noted, you want to handle interrupt binding requests, but you also need to do something for the “default” case.
Not sure what INTRNG does, but on x86 we round-robin interrupts among CPUs when they are first setup.
Oct 25 2019
Why do we need to enable interrupts for all CPUs and not only current cpu?
where an interrupt will be signaled in that case?
Oct 15 2019
Oct 14 2019
Oct 11 2019
Oct 10 2019
Oct 8 2019
Are these example of PLIC contexts?
interrupts-extended = < &cpu0_intc 0xffffffff &cpu1_intc 0xffffffff &cpu1_intc 9 &cpu2_intc 0xffffffff &cpu2_intc 9 &cpu3_intc 0xffffffff &cpu3_intc 9 &cpu4_intc 0xffffffff &cpu4_intc 9>;
- Infer the tracing device based on compiler architecture (PT on amd64, Coresight on aarch64)
- Document all the pmctrace usage flags
I was looking at Linux driver before writing this one. Why don't they do the same ?
hart ID is recorded to pcpup->pc_hart. Could it be used ? i.e. PCPU_GET(hart) or pcpu_find(cpu)->pc_hart
Oct 7 2019
Sep 27 2019
Sep 18 2019
Sep 13 2019
Sep 9 2019
Sep 7 2019
I discussed with James Clarke jrtc27, it is fine