GitHub - adurbin/iotools: Automatically exported from code.google.com/p/iotools

Branches Tags

Name		Name	Last commit message	Last commit date
Latest commit History 58 Commits
COPYING		COPYING
Makefile		Makefile
README		README
TODO.txt		TODO.txt
cmos_rw.c		cmos_rw.c
commands.c		commands.c
commands.h		commands.h
io_rw.c		io_rw.c
iotools.c		iotools.c
linux-i2c-dev.h		linux-i2c-dev.h
logic.c		logic.c
misc.c		misc.c
mmio_rw.c		mmio_rw.c
msr.c		msr.c
pci_rw.c		pci_rw.c
platform.h		platform.h
scom.c		scom.c
smbus_rw.c		smbus_rw.c

Repository files navigation

About

The iotools package provides a set of simple command line tools which allow
access to hardware device registers. Supported register interfaces include PCI, IO, memory mapped IO, SMBus, CPUID, and MSR. Also included are some utilities
which allow for simple arithmetic, logical, and other operations.

If you ever have to debug hardware, you could probably use these tools.

Building

iotools currently does not use an autoconf script or anything similar to build.
iotools has only been tested to run and build on Linux. Additionally, it is
assumed that gcc is being used to build. In order to build iotools, one just
has to type 'make.'

There are a few options that can be used during the build.

DEBUG - If set to 1, debugging symbols will be generated in the binaries. The
build currently turns this option on if the DEBUG variable has not been
assigned.

STATIC - If set to 1, the binary is linked statically. The build currently
turns this option on if the STATIC variable has not been assigned.

CROSS_COMPILE - This variable can be set to a path of another gcc. The build
will use the compiler pointed to by CROSS_COMPILE.

There is a 'rinstall' build target that will scp the iotools binary to a remote
system defined by the RHOST variable. RUSER can be defined to login with RUSER
to perform the copy. If RUSER is not defined, RUSER defaults to 'root.'