Tree [f266ba] master next /
 History



File Date Author Commit
 man 2014-07-01 Vasant Hegde Vasant Hegde [1b7476] lsvpd: Rename docs dir as man
 src 2016-01-22 Ankit Kumar Ankit Kumar [f266ba] Validate readlink return value to fix out of bo...
 .gitignore 2014-07-01 Janani Venkataraman Janani Venkataraman [fd2910] lsvpd: Adding .gitignore
 AUTHORS 2013-06-12 Harsh Prateek Bora Harsh Prateek Bora [85b0b0] Initial commit from internal repo
 COPYING 2014-04-08 Vasant Hegde Vasant Hegde [2fa139] License: Grant permission to link with librtas ...
 ChangeLog 2015-11-02 Vasant Hegde Vasant Hegde [34bed6] Roll out v1.7.6
 Makefile.am 2015-09-10 Vasant Hegde Vasant Hegde [9b06ba] lsvpd: Enable compilation warning
 NEWS 2013-06-12 Harsh Prateek Bora Harsh Prateek Bora [85b0b0] Initial commit from internal repo
 README 2015-09-08 Vasant Hegde Vasant Hegde [b92714] lsvpd: Update outdated README file
 bootstrap.sh 2015-07-20 Vasant Hegde Vasant Hegde [771285] lsvpd: Silence automake warning
 configure.ac 2015-11-02 Vasant Hegde Vasant Hegde [34bed6] Roll out v1.7.6
 cpu_mod_conv.conf 2013-06-12 Harsh Prateek Bora Harsh Prateek Bora [85b0b0] Initial commit from internal repo
 lsvpd.spec.in 2015-11-02 Vasant Hegde Vasant Hegde [34bed6] Roll out v1.7.6
 scsi_templates.conf 2013-06-12 Harsh Prateek Bora Harsh Prateek Bora [85b0b0] Initial commit from internal repo

Read Me

lsvpd:
-----
The lsvpd package contains all of the lsvpd, lscfg and lsmcode commands.
These commands, along with a scanning program called vpdupdate, constitute
a hardware inventory system. The lsvpd command provides Vital Product Data
(VPD) about hardware components to higher-level serviceability tools. The
lscfg command provides a more human-readable format of the VPD, as well as
some system-specific information. lsmcode lists microcode and firmware
levels. lsvio lists virtual devices.

Source:
-------
http://linux-diag.sf.net/lsvpd.html

Mailing list:
-------------
linux-diag-devel@lists.sourceforge.net
Info/subscribe : https://lists.sourceforge.net/lists/listinfo/linux-diag-devel

License:
--------
See 'COPYING' file.

Compilation dependencies:
-------------------------
- C and C++ compiler (gcc, g++)
- GNU build tools (automake, autoconf, libtool, etc)
- librtas-devel
- libvpd-devel
- sg3_utils-devel
- zlib-devel

Binary dependencies:
--------------------
- iprutils
- librtas
- libvpd
- sg3_utils
- zlib

Note:
  Package name may differ slightly between Linux distributors. Ex: RedHat and
  SLES ships development packages as "-devel" while Ubuntu ships it as "-dev"
  package. Please check your linux distribution package naming convention and
  make sure you have installed right packages.

Building:
---------
You can build on Power Linux System.

$ ./bootstrap.sh
$ ./configure [--prefix=/usr/]
$ make
$ make install

Building rpms:
--------------
To build a tarball to feed to rpmbuild, do

$ make dist-gzip

As an example, we use a command similar to the following:

$ rpmbuild -ba [--target=ppc/ppc64] <path-to-spec-file>

Hacking:
--------
All patches should be sent to the mailing list with linux-kernel style
'Signed-Off-By'. The following git commands are your friends:
- git commit -s
- git format-patch

You probably want to read the linux kernel Documentation/SubmittingPatches
as much of it applies to lsvpd.

Submitting patch:
-----------------
We use same mailing list for all Power Linux VPD and diagnostics projects
(ppc64-diag, libvpd, lsvpd, [lib]servicelog). It is common convention to
prefix your subject line with project name. This lets maintainer and other
developers more easily identify patches from patches targeted to other
projects. For example,

  Subject: [lsvpd PATCH 01/10] Summary phrase

--