Herman BRULE
The leader of this project
Can teach to the novice user
User space.
The software/command used to set the gpon/epon settings, in C to have low memory footprint
Linux kernel driver. Where the performance matter.
It's the control the specific port where is connected the optical module, in C
PCB. Better and better hardware.
How the PCB part, connect the wifi chip, the ethernet, the xPON port, and what do you need. In KiCad.
Dev platform + test cases. Accelerate closed to open source.
And as BONUS help greatly to detect backdoor/security problem. Most of ONU ported to open source into few weeks. So many industrial secret... Accelerated reverse engineering. 200k of code lines. What I prefer: be paid to open source or be paid to keep closed sources...
Ported devices
Every device below has been declared for this work. Each carries a dated certificate recording what was measured on a live GPON line against a real operator OLT, and how many of the suite's cases it passed and failed; a port still in progress is listed with whatever it has measured so far, so the work in flight is visible.
| Device | Cases passed | Benchmarks passed | Document |
|---|---|---|---|
| X111W HSGQ · RTL9602C | — | - | certificate (PDF) · ES · stock vs OpenWrt |
| X400AXF HSGQ · RTL9607F | 165 | 42 | certificate (PDF) · ES · stock vs OpenWrt |
Every device declared on the bench appears here, whether or not it has been measured yet; a device with no run shows a dash rather than a number, never a zero. The counts are read from the run's own artifact, never typed. They count different things and neither contains the other: cases passed is the number of named tests the issued certificate records as passing, while benchmarks passed counts the individual throughput points measured on this device under OpenWrt -- one per configuration, frame size and direction. The document column links this device's certificate -- which prints its own passed and failed counts on its first page -- and this device's stock-vs-OpenWrt comparison.