Don't throw exceptions from top-level bindings, even if we can't talk to xen

Instead we raise the exception when the user calls {wait,after}, i.e.
when they actually want to use event channels. The user application can
catch the Failure exception and perform some diagnostics.

Signed-off-by: David Scott <dave.scott@eu.citrix.com>
Merge pull request #7 from djs55/dont-fail-on-startup

Dont fail on startup
Update README.md

Signed-off-by: David Scott <dave.scott@citrix.com>
Update to 1.0.2, correct license spec

Signed-off-by: David Scott <dave.scott@citrix.com>
Update CHANGES

Signed-off-by: David Scott <dave.scott@citrix.com>
Regenerate OASIS

Signed-off-by: David Scott <dave.scott@citrix.com>
Merge pull request #10 from djs55/1.0.2

Update to 1.0.2
xen-evtchn.unix should depend on xen-evtchn

Without this we get intermittent link failures in downstream projects

Signed-off-by: David Scott <dave.scott@citrix.com>
Regenerate OASIS

Signed-off-by: David Scott <dave.scott@citrix.com>
Merge pull request #11 from djs55/fix-depends

Add missing dependency
Update to 1.0.3

Signed-off-by: David Scott <dave.scott@citrix.com>
Merge pull request #12 from djs55/fix-depends

Update to 1.0.3
xen-evtchn.unix.activations needs to depend on xen-evtchn

This is because the Unix_activations module depends on Eventchn and
Generation.

Signed-off-by: David Scott <dave.scott@eu.citrix.com>
Regenerate OASIS

Signed-off-by: David Scott <dave.scott@eu.citrix.com>