This directory contains some utilities:

x2y that translate an alliance format in an other alliance format
    for the physical or structural views.

    ex: x2y vst edi somefile
    would produce the somefile.edi file from somefile.vst

xnf that drives a xnf format compatible (as far as I've tested, ie not
    much) file from an alliance structural format.
    Some important issues:
    the xnf files has ibuf, obuf or tbuf on all its external output: this
    means that this is a complete design, not a hierarchy.
    This means that it is to be used at the end of a design only.
    the design flow is as follows: 
       you have a design that instanciates structural and behaviral
       files, so you have to synthesize, let say on the xilib library,
       all you vbe cells.
       After that you have a hierarchy of vst files intanciation the
       leaf cells of the xilib library.
       You want to translate all that in a single xnf file, so you do:
       `xnf -r higher_level_of_hierarchy', and this produces the
       appropriate xnf file.
       THe -r stands for `flatten the netlist so it instanciates only
       the leaf cells'.
       If the design is a single hierarchy (directly instanciating the
       leaf cells, then the -r is no necessary).

xilib : a small xilinx library, containing only the most common leaf
        cells.
        Note that logic cannot map a sequential design when only the
        `dff' is available: it is too complex for it to set the '0'
        and '1' values correctly.
