Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

drv: downgrade EEPROM not found from error to warning

See merge request be-cem-edl/fec/hardware-modules/fmc!10

Even though having a working EEPROM is part of the FMC standard, it is not
strictly needed for a driver to work. Or at least, it is not needed by the FMC
framework to continue the loading process.

Hence, we forgive the lack of an EEPROM and move on. If a driver wants to read
data from the EEPROM, it will then need to fail later.

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Resolve "clean up preprocessor conditions"

Closes #14

See merge request be-cem-edl/fec/hardware-modules/fmc!9

Resolve "NULL pointer in the error handling process of add_eeprom"

Closes #13

See merge request be-cem-edl/fec/hardware-modules/fmc!8

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

The carrier device release function and the fmc_carrier_register error handling
process were freeing the IDA is twice.

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

The device release function and the fmc_carrier_add_slot error handling
process were freeing the IDA is twice. Somehow, the id triggered a NULL
pointer bug. Not clear where that comes from, but fixing the error
management fixed the NULL pointer reference as well (I think, but I do
not have time to investigate further).

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

tools: lib: fix path for installation

Closes #11

See merge request be-cem-edl/fec/hardware-modules/fmc!7

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Resolve "rebuild for debian 12 and install"

Closes #11

See merge request be-cem-edl/fec/hardware-modules/fmc!6

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

If sphinx not found, make recipe will fail and it will throw error.
Hence CI will also fail.

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Resolve "Make the root makefile uniform with other projects"

Closes #10

See merge request be-cem-edl/fec/hardware-modules/fmc!5

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Resolve "Use fec-build-sw to build FMC"

Closes #9

See merge request be-cem-edl/fec/hardware-modules/fmc!4

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

The targets were explicitly listed and had separate make commands for
each of the directories which could be combined into one. Putting the
directories in a common variable will also help to implement 'flawfinder'
and 'cppcheck' at later stages.

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>

Resolve "at24 module should be loaded before FMC probe"

Closes #8

See merge request be-cem-edl/fec/hardware-modules/fmc!3

In cases where driver modules are not built into the kernel itself, at24
module is not loaded at the desired time, and thus, can cause error when
trying to read the eeprom.

Also, listing at24 as a soft dependency doesn't solves our problem as it
does not guarantees the time at which the module will be loaded.

Hence, load the module using request_module(), and throw a kernel warning
in syslog if it fails.

Signed-off-by: Vaibhav Gupta <vaibhav.gupta@cern.ch>