In 3.10.0-957.1.3.rt56.913.el7.x86_64, vmebus CRCs change,
and this takes care of this fact

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

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Ignore temporary files created during build.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Remove following warning when comparing variables:
In file included from include/linux/cache.h:4:0,
                 from include/linux/time.h:4,
                 from include/linux/stat.h:18,
                 from include/linux/sysfs.h:20,
                 from include/linux/kobject.h:21,
                 from include/linux/device.h:17,
                 from
/nfs/cs-ccr-nfsdev/vol1/u1/awujek/coht/fmc/svec-sw/kernel/svec-sysfs.c:11:
/nfs/cs-ccr-nfsdev/vol1/u1/awujek/coht/fmc/svec-sw/kernel/svec-sysfs.c:
In function ‘__next_token’:
include/linux/kernel.h:724:17: warning: comparison of distinct pointer
types lacks a cast [enabled by default]
  (void) (&_min1 == &_min2);  \
                 ^
/nfs/cs-ccr-nfsdev/vol1/u1/awujek/coht/fmc/svec-sw/kernel/svec-sysfs.c:297:8:
note: in expansion of macro ‘min’
  len = min(p - tok + 1, buf_length - 1);
        ^
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Use _ABS in Makefiles wherever possible.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

FMC_BUS_ABS is passed to Kbuild, which uses different current directory.
It is not trivial to handle FMC_BUS to be absolute or relative path.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

This allows parallel build.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Rename Module.symvers.vme to Module.symvers.vmebus.

update content of Module.symvers.* with CRC's.
CRC's are needed for kernels with enabled CONFIG_MODVERSIONS.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

symvers are under kernel directory
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Include parent_common.mk from up directory. Which may contain various
environment definitions such compiler, linker, etc. If such file is not
present it will not affect build.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@gmail.com>

Signed-off-by: Federico Vaga <federico.vaga@gmail.com>

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>

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

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

When possible, avoid statement-scope variable for a better maintanability
of the code.
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

If there are no reasons for a *_free() function to return an error, change
the return type to void
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

The irq_lock is a SVEC spinlock, but we must protect VIC variables. In order
to make the VIC code independent, use a dedicated VIC spinlock
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Make the VIC code indipendently as much as possible
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Use the specular name: we used init, we should use exit
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

On spec driver remove, do not clean-up VIC stuff. The VIC should be cleaned
by the mezzanine driver when it release all its handlers (see patch a628fa3).
Just leave a reminder for driver developer when something goes wrong.

Moreove, we do not need to user sver_irq_exit() any more. If the mezzanine
driver is properly written it will clear all its interrupts, and thanks to
patch a628fa3 we can safely assume that everything was cleared.
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

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

Interrupt resources are not properly released. Mainly two problems:

  1. on IRQ free the driver was using the IRQ number instead of the the
     component base address. So, the component IRQ handlers were never
     released

  2. on IRQ free, supposing that the first problem was not there, when
     all component's IRQ handlers were released the PCI IRQ handler (VIC
     dispatcher) should have released, but it was not. In consequence of this
     even if the driver was removed an interrupt can be handled by a
     ghost handler.
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

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

The patch 355e1019 move two fields in the spec_dev structure, but other
drivers may include this header and use this structure, so it breakes
all the fields's offset.

Revert this modification in order to make the modification more backward
compatible. It will not fix all the situations (sizeof) but some of them
yes.
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>