An error occurred while fetching the assigned milestone of the selected merge_request.
Making libs more versatile for Altera/Modelsim
- Jun 22, 2022
-
-
David Belohrad authored
components purely dependent of xilinx libraries are not compiled in if target differs from xilinx
7f6c088b -
David Belohrad authored083bca62
-
David Belohrad authored79ed0932
-
- Aug 23, 2021
-
-
Federico Vaga authored8649d40d
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
4cea3a03 -
Mathis MARION authored
dev.fwnode was not set to NULL after deallocation which could wrong memory accesses. Signed-off-by: Mathis MARION <mathis.marion@grenoble-inp.org>
0b4bc246
-
- Jul 29, 2021
-
-
Federico Vaga authored
1.1.2 - 2021-07-29 ================== https://www.ohwr.org/project/general-cores/tags/v1.1.2 Fixed ----- - sw: improve compatibility with newer (> 3.10) Linux kernel versions
16b7b936 -
Federico Vaga authored21f2e94e
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
0184795d -
Mathis MARION authored
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>
49dfe034 -
Mathis MARION authored
`i2c_new_device` disappeared in kernel 5.2 and onwards. It is now required to use `i2c_new_client_device`, which works the same way except for error checking. Signed-off-by: Mathis MARION <mathis.marion@grenoble-inp.org>
30c5b080 -
Mathis MARION authored
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>
7152194b -
Mathis MARION authored
`i2c_new_device` disappeared in kernel 5.2 and onwards. It is now required to use `i2c_new_client_device`, which works the same way except for error checking. Signed-off-by: Mathis MARION <mathis.marion@grenoble-inp.org>
85bfb868
-
- Oct 22, 2020
-
-
Federico Vaga authored844cc49d
-
Mamta Shukla authored
Adding condition to warn about 0 divider value. It was observed while accessing svec-flash, if frequency for flash is not defined correctly i.e in operation range of chip and host(i.e vme or pci), divider value 0 doesn't allow flash transfers. Signed-off-by Mamta Shukla <mamta.ramendra.shukla@cern.ch> Suggested-by: Federico Vaga <federico.vaga@cern.ch>
e57a80e9
-
- Sep 14, 2020
-
-
Federico Vaga authored
1.1.1 - 2020-09-14 ================== Fixed ----- - sw: fix SPI driver to update the spi_message->actual_length
abaab958
-