https://toorun.dev/tags/regulatory/Recent content in regulatory on toorun.devHugo -- gohugo.ioen-usSat, 29 Nov 2025 12:30:00 +0000https://toorun.dev/posts/linux-wifi-tx-power-regulatory-configuration/Sat, 29 Nov 2025 12:30:00 +0000https://toorun.dev/posts/linux-wifi-tx-power-regulatory-configuration/WiFi TX Power Configuration Overview WiFi configuration typically allows runtime control of parameters such as channel selection. However, TX power is not always dynamically configurable and may require configuration during driver initialization. This is done by providing a TX power configuration binary to the driver. TX Power Configuration Flow The general workflow: Generate TX power configuration binary\ Place it in firmware path\ Load driver with configuration\ Verify applied limits Generating TX Power Configuration A configuration file is used to generate a binary representation of TX power limits.https://toorun.dev/posts/embedded-red-cybersecurity-en18031/Sat, 29 Mar 2025 12:30:00 +0000https://toorun.dev/posts/embedded-red-cybersecurity-en18031/RED Cybersecurity (EN 18031) Overview The RED cybersecurity standard (EN 18031) defines requirements to ensure that radio equipment is secure and does not negatively impact networks, users, or services. It is structured around three main articles: 3.3.d: Protection of networks and prevention of service degradation 3.3.e: Protection of personal data and privacy 3.3.f: Protection against fraud Applicability Depending on the system design, not all articles may apply. Typical example: Systems without user data → privacy requirements may not apply Systems without financial interaction → fraud-related requirements may not apply Network interaction → usually relevant and must be addressed Requirements Structure Each article is divided into: