Also in the loop for erbest the search was fixed if the first port
which is elected as ebest by default is not valid.

Since the portnumber is a 16bit value, memcp is not given to be correct
on all architectures depending on the endines

msg: reset ext_specific flags in the announce to zero when either no TLV is appended or the TLV is not a WR TLV

The flags was not set to any value when no TLV was appended or a wrong TLV was appended, in that
case the RAM content was wrongly propagated as WR flags which may caused that a node is going into
a wrong state.

For the dataset comparisment all known foreign masters have to be qualified
so the worst is found. Once aged out it will be removed so the qualification is
not relevant in this check.

The UTC leap flags are propagated to the system (unix) so the leap second is correctly handled at midnight
so the UTC time is always correct.

the variance is now set according to the servo state, the source and timescale
are set according to the clock classes set

Added clock accuracy constants and aligned the chaning of the clock class
with the accuracy

The clock class is now decreased and increased based on the servo state,
this only has an effect for wrs and wrpc since the contain a servo loop.

The clock class goes only to 6 if realy in gm mode, so not even passive
The variance was changed back to 0x8000 until computed

We don't compute the variance so the default value shall be 0xFFFF

bmc & default dataset: Handle passive for loopbacke frames correctly, take Clockid only from MAC of Port1

The switsch was getting the Clockid for the default datset for each port which has a different MAC on each port, this is wrong, now the Clockid is always fetched only from Port1 for all other ports.

Leap seconds are now also fetched from the system in case we are a grandmaster
A reset of the locking procedure was added so a locked switch can get master again

The audit portings changed the timely behaviour of the ppsi which cause wrong behaviours,
the timeout scheme was changed to only reset timeouts where needed and in all non PTP
states. UTC offset is now fetched from the system where supported, link up/down is now
considered in the BMC, also some state changes where cleaned up to be out of the BMC, e.g.
state changes based on timeouts between PreMaster and Master or between Uncalibrated and Slave.

Passive handling is actualy done differently, its integrated into
the bmc as a precheck.

Most of them were already ported, added a check before returning next delay if
a timeout for a (p)delay request has to be taken into account

Now everywhere the packet buffer is a void *buf and the lenght is int len

Only the patches ragrding the flag from the current master was
taken over, the other falgs are still needed and used.

Streamlined length naming, other parts were already ported

No real porting was required only some clarifying, the rest was ported already

The patches from the audit chapter 2.4.1 were ported, some of the
changes were not ported due to previous changes or different
foreign master handling, eg.g announce unpacking is still done since
this seems more streamline with other message handling and is actually
still used for field extraction for the foreign master data set

For the announce receipt timeout the datasets shall be updated depending on the other ports states, only if no other in slave update parent dataset.
when a link was connected it runs through initializing which was wrongly updating the parent dataset which caused a short masterchange condition an resyncing.

changed peer delay handling so p2p messages are only answered when in this mode
added p2p messages to some states where it was missing

Message handling for the case of received back frames changed and timeouts for announces reset according to standard

The calibration handshake is now started on the slave state base
Announce messages from the same device are handled differnetly for a BC

A hook was added that handles the wr states, so that they don't get overwritten by bmc decisions.
The extension stays in the white rabbit states until a calibration is done.

The FSM order was changed in order to leave the fsm on a state change and re-enter the fsm directly afterward,
this makes sure no state decision is overwritten by the state handling and each state dicision is handled at least once,
There seems to be an issue with htons on unaligned addresses, which is the case for stepsRemoved in an announce,
a workaround of a manual 16bit conversion was added.

Merged uncalibrated and slave state, added event handling to the individual states,
changed in all states the frame handling to table driven handling,
moved common handling from common to slave since it is actually not common,
fixed state passive to be according to standard,
added uncalibrated handling,
fixed listening and master frame handling,

BMC fixed to be called periodically and data sets comparisments fixed
also changed the foreign master table adding and agging and some
minor adpatations in state pre-master

This reverts commit a72f6bdc.

Remove warning that HAS_ABSCAL is redefined
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>