obu-firmware builds against vanetza-idf from microbu-esp32c5/external, but that tree was gitignored, so a clone of this repository could not build the firmware it ships. It is now committed here as ordinary files in its own folder, microbu-esp32c5/: the colleague's commit cf4b99f plus the V2X2MAP bridge's signature verification (--trust) used on the bench. Nothing is fetched from or pushed to the colleague's repository; this repository and its remotes carry everything. The folder's own .gitignore keeps build output, downloaded components and private key material out, as it did there; the committed file set is identical to that repository's tracked files. The ESP32-C5 is still flashed from obu-firmware/, which only takes vanetza-idf from microbu-esp32c5/, so the two stay separate folders. FLASHING.md says how to take a newer version of the colleague's tree (copy it over the folder, rebuild, test, commit).
36 lines
714 B
C++
36 lines
714 B
C++
#include "limeric_transmit_rate_control.hpp"
|
|
#include <vanetza/common/runtime.hpp>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace dcc
|
|
{
|
|
|
|
LimericTransmitRateControl::LimericTransmitRateControl(const Runtime& rt, const Limeric& limeric) :
|
|
m_budget(limeric, rt)
|
|
{
|
|
}
|
|
|
|
Clock::duration LimericTransmitRateControl::delay(const Transmission&)
|
|
{
|
|
return m_budget.delay();
|
|
}
|
|
|
|
Clock::duration LimericTransmitRateControl::interval(const Transmission&)
|
|
{
|
|
return m_budget.interval();
|
|
}
|
|
|
|
void LimericTransmitRateControl::notify(const Transmission& transmission)
|
|
{
|
|
m_budget.notify(transmission.channel_occupancy());
|
|
}
|
|
|
|
void LimericTransmitRateControl::update()
|
|
{
|
|
m_budget.update();
|
|
}
|
|
|
|
} // namespace dcc
|
|
} // namespace vanetza
|