| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| common/ | 04-Jul-2025 | - | 4,672 | 3,022 | ||
| crypto_toolbox/ | 04-Jul-2025 | - | 2,035 | 1,426 | ||
| docs/architecture/ | 04-Jul-2025 | - | 314 | 248 | ||
| fuzz/ | 04-Jul-2025 | - | 147 | 90 | ||
| hal/ | 04-Jul-2025 | - | 9,824 | 7,011 | ||
| hci/ | 04-Jul-2025 | - | 38,933 | 30,759 | ||
| lpp/ | 04-Jul-2025 | - | 306 | 143 | ||
| metrics/ | 04-Jul-2025 | - | 2,714 | 2,027 | ||
| os/ | 04-Jul-2025 | - | 8,958 | 5,969 | ||
| packet/ | 04-Jul-2025 | - | 14,646 | 10,045 | ||
| proto/ | 04-Jul-2025 | - | 76 | 66 | ||
| rust/ | 04-Jul-2025 | - | 54,816 | 43,604 | ||
| storage/ | 04-Jul-2025 | - | 4,794 | 3,462 | ||
| sysprops/ | 04-Jul-2025 | - | 346 | 236 | ||
| .gitignore | D | 04-Jul-2025 | 48 | 4 | 3 | |
| Android.bp | D | 04-Jul-2025 | 17.2 KiB | 626 | 612 | |
| AndroidTestTemplate.xml | D | 04-Jul-2025 | 2.3 KiB | 46 | 29 | |
| BUILD.gn | D | 04-Jul-2025 | 1.9 KiB | 73 | 63 | |
| README.md | D | 04-Jul-2025 | 865 | 27 | 16 | |
| benchmark.cc | D | 04-Jul-2025 | 852 | 26 | 8 | |
| fuzz_test.cc | D | 04-Jul-2025 | 848 | 26 | 7 | |
| module.cc | D | 04-Jul-2025 | 6.8 KiB | 190 | 134 | |
| module.h | D | 04-Jul-2025 | 6.6 KiB | 240 | 154 | |
| module_unittest.cc | D | 04-Jul-2025 | 7.6 KiB | 238 | 160 |
README.md
1### Why is gabeldorsche plural? 2 3Please see this [informative video we've prepared](https://www.youtube.com/watch?v=vLRyJ0dawjM). 4 5### Architecture 6 7Guidelines for developing the Gabeldorsche (GD) stack 8 9* [Architecture](./docs/architecture/architecture.md) 10 11### Testing 12 13Gabeldorsche (GD) was built with test driven development in mind. Three types of 14tests are used in ensuring Gabeldorsche stack's stability, correctness and free 15from regression. 16 17If you are verifying something is glued or hooked up correctly inside the stack, 18use a unit test. 19 20* [GTest Unit Test](./docs/testing/gtest.md) 21 22If you are verifying correct behavior (especially interop problems) **DO NOT** 23write a unit test as this not a good use of your time. Write a [cert test](./cert_test.md) instead 24so it applies to any stack. 25 26* [GD Certification Tests](./docs/testing/cert_test.md) 27