- 14 Nov, 2022 3 commits
-
-
Vaibhav Gupta authored
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>
-
Vaibhav Gupta authored
If we name the group-attributes, an additional directory will be created in sysfs. And the goal of making SPEC and SVEC symmetric, will not be achieved. Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>
-
Vaibhav Gupta authored
Along with SPEC devices, we also have SVEC devices which have symmetric code. Due to kernel upgrade, SVEC started using sysfs to get the name of firmware to be loaded. Thus, to keep the code symmetric, we should do similar change in SPEC. Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>
-
- 09 Nov, 2022 10 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Vaibhav Gupta authored
Header-files and Module.symvers from fpga-mgr-backport project should only be used for the FEC-OS based on 3.10.0-957.1.3.rt56.913.el7.x86_64 CentOS kernel. And the vesrion-check should be done on the basis of kernel source (done in $(REPO_PARENT/common.mk) )and not on host's kernel version. Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>
-
Vaibhav Gupta authored
Some drivers make use of 'REPO_PARENT' and 'TOPDIR' variables and some not. Thus to keep the code uniform, use the variables for this driver too. Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>
-
Vaibhav Gupta authored
Variable name 'LINUX' is very ambiguous for its purpose in the makefile. Also, this project builds as a part of COHT project which uses another variable name 'KERNELSRC' for the same purpose. Hence, this change makes this project uniform with others. Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>
-
Vaibhav Gupta authored
Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>
-
Federico Vaga authored
Resolve "update HDL dependencies" Closes #4 See merge request be-cem-edl/fec/hardware-modules/spec!1
-
- 08 Nov, 2022 4 commits
-
-
Federico Vaga authored
Resolve "Document the CSR registers" Closes #2 See merge request be-cem-edl/fec/hardware-modules/spec!3
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
GN4124: 3.1.1 DDR: 2.0.1 Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 15 Jun, 2022 4 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 06 Apr, 2022 1 commit
-
-
Federico Vaga authored
It happened at least once that we got an invalid tx pointer. Not sure why this happened (e.g. spurious interrupt?), but it happened. With this patch, we do not prevent this from happening, but we avoid to have a kernel crash. This could help to understand the real problem. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 24 Feb, 2022 1 commit
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 23 Feb, 2022 8 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
-
Federico Vaga authored
This is not however 100% compatible with acc_py. However, we are not planning to release it in acc_py any time soon. By the time this will happen, probably acc_py will upgrade to support also this approach. And by the way there is also the old setup.py around. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Prepare this product to be delivered as RPM package. This is a perliminary work. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 22 Feb, 2022 3 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Not only the kernel depends on spec-core-fpga.h, but also the spec-firmware-version tool does. So, move the generation of that header in the include directory. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 29 Jul, 2021 6 commits
-
-
Federico Vaga authored
2.1.6 - 2021-07-29 ================== Fixed ----- - sw: improve compatibilty with newer (greater than 3.10) Linux kernel version
-
Federico Vaga authored
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Mathis MARION authored
This patch follows a change to how IRQ are handled by HTVIC. Here is a copy of the commit message for the corresponding HTVIC patch: When creating an IRQ domain, the code used to store a device struct pointer in the `of_node` field of the irq_domain struct returned by `irq_domain_add_linear`. This was done by casting to a void pointer and passing as the first argument of the function. In the SPEC repository (and supposedly other depending repositories), we would then get back the irq_domain struct by calling `irq_find_host` with again a device struct pointer casted to a void pointer as the argument. The function would compare the addresses of the 2 device structs and return the right irq_domain. This trick was most likely due to the fact that the IRQ domain API was conceived around OpenFirmware before version 4.4, and that the project should work for ACPI. A workaround for kernel 4.7 was written, which involved using a `select` function, and passing the address of the device struct as a parameter. It was particularly ugly as it would require getting around the `irq_find_host` to call immediately `irq_find_matching_fwspec` and pass in the address of the wanted device struct as a parameter in a hacky way to fit it inside two 32 bit integers. Kernel version 4.4 introduced fwnodes, which would make easier working with ACPI. Instead of repeating the hacky workaround (which would result in a kernel error on later kernels when calling irq_domain_add_linear), I allocated a fwnode_handle struct before creating a new IRQ domain. Then I used the new irq_domain_create_* API to get an irq_domain using this fwnode. I also took care of disallocating the fwnode_handle. On the other end, we can just call `irq_find_matching_fwnode` and pass dev.fwnode as a parameter. Signed-off-by: Gwenhael GOAVEC <gwenhael.goavec@femto-st.fr> Signed-off-by: Mathis MARION <mathis.marion@grenoble-inp.org>
-
Mathis MARION authored
`kallsyms_lookup_name` is no longer available from headers since kernel 5.7. This compatibility fix is described here: https://github.com/xcellerator/linux_kernel_hacking/issues/3Signed-off-by: Gwenhael GOAVEC <gwenhael.goavec@femto-st.fr> Signed-off-by: Mathis MARION <mathis.marion@grenoble-inp.org>
-
Mathis MARION authored
The signature for `debugfs_create_regset32` changed from returning a `struct dentry *` to `void`. Error checking is no longer possible. Signed-off-by: Gwenhael GOAVEC <gwenhael.goavec@femto-st.fr> Signed-off-by: Mathis MARION <mathis.marion@grenoble-inp.org>
-