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

version information is stored in constant libipmi_version_s
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>

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: 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>

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>

The example files and configuration matches what is current in
the fdelay driver, to be released soon after this very package.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

fru-dump includes local headers, where recent commit changed fru_alloc
to correctly receive size_t.  fru-dump has it's own local implementation,
which was still receiving an "int" argument. Thus build failed in 64-bit
(and I wonder why my compiler doesn't even warn in 32 bits.

But reported and fix suggested by Michel Vincent, in private email.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

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

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

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

This addes command line support and environment support to specify the
values to be set in the EEPROM. Removes the dumping function
(tools/fru-dump will soon be there), removes generation of the fake
internal use area and supports the soon-to-be-documented defaults.

It is still missing a lot (i.e., power consumption is still hardwired)
but it can be used for the initial work on eeprom images.

Again, thanks to Manohar Vanga and Matthieu Cattin for libipmi and
this tools.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

unlike in pts, here fmc_eeprom.py is in a subdir, relative to the
fru-generator main program, so fix stuff accordingly.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This fixes a bug in the code we imported from PTS, the fix
in PTS is carried out separately.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The contents of this commit are part of the "fmcadc100m14b4cha" branch
of the "pts" project (Python Test Suite) on ohwr, commit 1564157 (Nov
13 2012).

Files are renamed like this:

 test/fmceeprom/python/fmc_eeprom_example.py  -> tools/fru-generator
 test/fmceeprom/python/libipmi/               -> tools/libipmi/
 test/fmceeprom/python/fmc_eeprom.py          -> tools/libipmi/fmc_eeprom.py

The rationale is that tools/fru-generator will be called by our users,
while fmc_eeprom.py is part of the library.

Later commits in fmc-bus change the files (now copied literally) to fit
the different use case.

Matthieu is the author of this code with Manohar Vanga, but neither is
reposnsible for this commit. The committer marked Matthieu as author
so "git blame" will show him not me.

It is lifted here (and renamed) unchanged before being customized.