version information is stored in constant libipmi_version_s
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

version information is stored in constant libsdbfs_version_s
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 the build.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

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

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

Changes in the buildsystem.

Also change its name.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Get rid of warnings:

ipmi.c: In function ‘ipmi_common_header_write’:
ipmi.c:68:6: warning: variable ‘ret’ set but not used
[-Wunused-but-set-variable]
  int ret;
      ^
ipmi.c: In function ‘ipmi_board_info_area_write’:
ipmi.c:119:6: warning: variable ‘ret’ set but not used
[-Wunused-but-set-variable]
  int ret;
      ^
ipmi.c: In function ‘ipmi_dc_load_record_write’:
ipmi.c:198:6: warning: variable ‘ret’ set but not used
[-Wunused-but-set-variable]
  int ret;
      ^
ipmi.c: In function ‘ipmi_dc_output_record_write’:
ipmi.c:228:6: warning: variable ‘ret’ set but not used
[-Wunused-but-set-variable]
  int ret;
      ^
ipmi.c: In function ‘ipmi_oem_record_write’:
ipmi.c:258:6: warning: variable ‘ret’ set but not used
[-Wunused-but-set-variable]
  int ret;
      ^
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

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

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>

FMC bus is part of the recent kernel versions, so we may have conflicts
between this version and the one in the kernel.

With this patch we force the compilation proceed to ignore the kernel
header for FMC and use the local ones.
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>

Driver cannot call fmc_sdb_dump() anymore. (acctually they can but the
operation is not supported, so it will print an error message)
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

This gave us more freedom to change/add/remove operations without
recompiling all device driver.

Typically, Carrier board implement the fmc operations, so they will not
use this helpers.
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

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

Sometimes (expecially in cross-compilation context) t is necessary to use
different environments. Instead of complicate this makefile, include
an external one with user code.

Create a local file named Makefile.specific, and write here your code.
Bear in mind that Makefile.specific will run before the Makefile.
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

src point to the source code. Obj point to the object. Sometimes they
live toghether but users can decide to build the object outside the
source tree (e.g. O=/output/path/).
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
Acked-by: Alessandro Rubini <rubini@gnudd.com>

Remove binaries on clean
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
Acked-by: Alessandro Rubini <rubini@gnudd.com>

The main reason to introduce this EXTRACFLAGS variable is to allow people
to cross compile on x86 architectures over 32bits and 64bits

    make EXTRACFLAGS="-m32"
    make EXTRACFLAGS="-m64"
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
Acked-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This completes the show_sdb_tree functionality, with the
new informative fields.  The output for a verbose module is now
like this (long lines are unavoidable):

 SDB: 00000651:e6a542c9 WB4-Crossbar-GSI
 SDB: 0000ce42:00000601 WB-DMA.Control      (00001000-0000103f)
 SDB: 0000ce42:779c5443 WB-OneWire-Master   (00001100-000011ff)
 SDB: 0000ce42:00000603 WB-SPEC-CSR         (00001200-0000121f)
 SDB: 0000ce42:00000013 WB-VIC-Int.Control  (00001300-000013ff)
 SDB: 0000ce42:d5735ab4 WB-DMA.EIC          (00001400-0000140f)
 SDB: 00000651:eef0b198 WB4-Bridge-GSI      (bridge: 00002000)
 SDB:    00000651:e6a542c9 WB4-Crossbar-GSI
 SDB:    0000ce42:123c5443 WB-I2C-Master       (00003000-000030ff)
 SDB:    0000ce42:e503947e WB-SPI.Control      (00003100-0000311f)
 SDB:    0000ce42:123c5443 WB-I2C-Master       (00003200-000032ff)
 SDB:    0000ce42:00000608 WB-FMC-ADC-Core     (00003300-0000337f)
 SDB:    0000ce42:779c5443 WB-OneWire-Master   (00003400-000034ff)
 SDB:    0000ce42:26ec6086 WB-FMC-ADC.EIC      (00003500-0000350f)
 SDB:    0000ce42:00000604 WB-Timetag-Core     (00003600-0000367f)
 SDB: Synthesis repository: git://ohwr.org/fmc-projects/fmc-adc-100m14b4cha.git
 SDB: Bitstream 'spec_top_fmc_adcmc-projects/fmc-adc-100m14b4cha.git' \
         synthesized 20140116 by mcattin (ISE version 133), commit f0a539dffe6d
Signed-off-by: Tomasz Wlostowski <tomasz.wlostowski@cern.ch>
Acked-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This allows easier modification to the eeprom than loading the
fmc-write-eeprom module.  The carrier driver will likely refuse
writing if the FPGA is not running the golden gateware image.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This 444 should have been octal.
Signed-off-by: Joe Perches <joe@perches.com>

The code reported wrong addresses in the sdb dumps.  All sdb addresses
are relative, but the code was adding the base address twice.  Bug
exposed by a gateware image with two bridge levels.
Reported-by: Juan David Gonzalez Cobas <dcobas@cern.ch>
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

At registration and unregistration time, I was checking fmc->flags
for FMC_DEVICE_NO_MEZZANINE, to skip initialization and cleanup for
empty slots.  But the check was wrong (see previous commit) and
the conditional was never triggered.

I think we should register slots with no mezzanines, because the
carrier may offer some support anyways (the SPEC does), so the commit
removes the conditionals instead of fixing them.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The flag must be checked with "&", not "==".  When I tested
it was the only flag, so I didn't notice.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The call to kzalloc() wasn't checked.
The dev_info() message dereferenced freed memory on error.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

If we don't allocate "arr" then the cleanup path will dereference it and
oops.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

The use of the 'readl' and 'writel' identifiers here causes build errors on
architectures where those are macros. This renames the fields to read32/write32
to avoid the problem.
Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

For traceability purposes, we include commit descriptions
as MODULE_VERSION information in drivers that are deployed
in CERN control system.

Ideally, the commit description should be added to all the
binary blobs installed, but the kernel module is critical
in this connection, as it is crucial to trace back quickly
the whereabouts of installed .ko sources.