Add a comment out all these warnings we see.
As I was told it has to do with the usual -1 so in case someone
gives 0 it does not become negative.
Still annoying.
Adjust the register table to our memory layout with BAR0 and BAR1
but not spelt out here to avoid conflicts on #defines with the
(initial) reference solution.
Add an optional IP protocol field to make it easier to generate
OSPF packets.
This was used for testing initial assignments before understanding
how to modify scapy packets after they were created.
Adjust to our two-BAR memory layout split between registers and tables.
This was done in order to reduce differences to the reference solution.
Add a workaround for one of the multiple cases when the framework would
say PASS on a clear FAIL.  In this case it was if there were no
values received at all.

This was submitted as git pull request #54 on the NetFPGA repository.
Add the code used to understand how to modify a scapy packet
after creation to not lose the samples.
Split the registers into BAR0 and BAR1.

Finding this TCL file is magic.  Documentation should be added to the wiki.
Add the new files to the .pao file and add the to the repository.
At this time the register interfaces are working, the pipe-line work
is in progress, the statistics counters need to be hooked up along
with the pipeline work, and finally the ether src/dst, IPv4 TTL/Csum
need to be updated if not sent to CPU.
Add test case for the non-learning switch with statistics counters
to zero and read.

Add test case for the register interface (counters and tables),
writing them (were possible) and reading them back, and an update
test.
Commit the (otherwise generated) register files for the software
development (python test cases and C user space code) given that
this interface is stable and tested.
Merge branch 'master' of ssh://127.1:2222/Users/bz/Documents/Cambridge/CL/P33/P33.github
Add a bitfile that passed timing after the register/table interfaces
were finalised and tested.
The packet passing logic is not existent in this bitfile and it is
unclear what will happen if packets are encountered.