obu-firmware builds against the vanetza-idf C-ITS library, which until now came from the colleague's microbu-esp32c5 tree beside the repository and was not tracked here, so a clone of this repository could not build the firmware it ships. The library alone is now part of obu-firmware, as obu-firmware/external/vanetza-idf: their external/vanetza-idf at commit cf4b99f, unchanged (9775 files; see its PROVENANCE.md). CMake takes it from there by default; -DVANETZA_IDF_DIR still points the build elsewhere. The rest of the colleague's tree (their own VAM firmware, PKI tooling, station-link Python tools, the V2X2MAP bridge) stays out of this repository and gitignored; nothing is pushed to their repository. NOTES.md, docs/06, TODO.md and the pcap verifier's usage line point at the new location.
36 lines
675 B
C++
36 lines
675 B
C++
#pragma once
|
|
#include <vanetza/access/access_category.hpp>
|
|
#include <cstdint>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace access
|
|
{
|
|
|
|
/**
|
|
* \brief map access category to PPPP for C-V2X
|
|
*
|
|
* Mapping is according to EN 303 613 V1.1.1 Table B.7
|
|
*
|
|
* \param ac access category from 802.11
|
|
* \return matching PPPP value
|
|
*/
|
|
constexpr std::uint8_t pppp_from_ac(AccessCategory ac)
|
|
{
|
|
switch (ac) {
|
|
case AccessCategory::VO:
|
|
return 2;
|
|
case AccessCategory::VI:
|
|
return 4;
|
|
case AccessCategory::BE:
|
|
return 5;
|
|
case AccessCategory::BK:
|
|
default:
|
|
return 7;
|
|
}
|
|
}
|
|
|
|
} // namespace access
|
|
} // namespace vanetza
|
|
|