File	Date	Author	Commit
debian	2013-09-14	Philip Ashmore	[b05dc2] Version 0.1.1-01
v3c	2013-11-13	Philip Ashmore	[afa592] Version 0.1.3-01
AUTHORS	2013-09-01	Philip Ashmore	[fa0700] Version 0.1.0-01
COPYING	2013-09-01	Philip Ashmore	[fa0700] Version 0.1.0-01
COPYING.LESSER	2013-09-01	Philip Ashmore	[fa0700] Version 0.1.0-01
ChangeLog	2013-11-13	Philip Ashmore	[afa592] Version 0.1.3-01
INSTALL	2013-09-01	Philip Ashmore	[fa0700] Version 0.1.0-01
LICENSE.txt	2013-09-01	Philip Ashmore	[fa0700] Version 0.1.0-01
Makefile.am	2013-09-14	Philip Ashmore	[b05dc2] Version 0.1.1-01
NEWS	2013-11-13	Philip Ashmore	[afa592] Version 0.1.3-01
README	2013-09-29	Philip Ashmore	[9aeabe] Version 0.1.2-01
TODO	2013-09-14	Philip Ashmore	[b05dc2] Version 0.1.1-01
configure.ac.in	2013-09-14	Philip Ashmore	[b05dc2] Version 0.1.1-01
doxygen.cfg	2013-09-01	Philip Ashmore	[fa0700] Version 0.1.0-01
makefile	2013-11-13	Philip Ashmore	[afa592] Version 0.1.3-01
v3c-raspi.m4.in	2013-09-16	Philip Ashmore	[3477cf] Version 0.1.1-03
v3c-raspi.pc.in	2013-09-16	Philip Ashmore	[3477cf] Version 0.1.1-03

Read Me

Introduction
============
Initially this is just a wrapper around the Bcm2835 IO ports.

Think of IO, DMA and memory configurations in the old ISA PC system.
The device driver supplied a list of resource combinations for the system to
choose from.

So instead of a device driver, a program provides the combinations of GPIO,
DMA etc resources it needs in a configuration file.

When it starts up it asks the ConfigurationManager which configuration index it
should use, -1 means it can't use resources and should quit.

System configuration assigns priorities to each program.

The system administrator controls the system configuration and has to connect
any physical devices.

They can run test cases of combinations of programs-to-run / hardware-to-connect
and the ConfigurationManager will tell them which arrangements are possible,
if any, allowing them to make choices and assign priorities based on physical
or other constraints.


Directory structure
===================
v3c-raspi (you are here)
 |- build (everything created goes here, as far as the tools will allow)
 |   \- v3c
 |       \- examples
 \- v3c
     \- examples

Why the need for v3c?
=====================
It "boilerplates" the autotool bootstrapping phase, allowing you to focus your
attention on the task of developing your project with minimal intrusion - it's
even got GIT integration, Debian/Ubuntu package generation, doxygen integration,
with more to come.

V3c-raspi inherits capabilities provided by v3c, so you can "make debian" or
"make ubuntu" to build a debian/ubuntu packages and if you use the "git" version
control system you can "make git branch=0.1.1-03 distcheck" to run distcheck on
the git branch 0.1.1-03.

V3c-raspi provides documentation and v3c-raspi.m4 that defines an m4 macro,
ACX_V3C_RASPI for inclusion in your projects configure.ac.in.

Finally there's v3c-raspi.pc, allowing your project to specify a minimum
v3c-raspi version to build against.

Required packages
=================
On Debian/Ubuntu, apt-get is the tool de-jour.

base requirements
-----------------
    Read the v3c README file for it's requirements.
    You can get v3c from
        http://sourceforge.net/projects/v3c

Feedback
========
All feedback should be through this projects support web page
    http://sourceforge.net/projects/v3c-raspi/support.

I've added a help, open discussion and a mantis bug tracker there.

Finally, do send me an email to let me know what your thoughts are on v3c-raspi!