Sponsored by: Netflix
Details
Details
- Reviewers
jhb manu bz - Group Reviewers
Doc Committers - Commits
- rG9478c7f5f80b: firmware: document new native file loading.
Diff Detail
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
(Sorry if some comments are confusing; I lost track of the state of the latest implementation)
| share/man/man9/firmware.9 | ||
|---|---|---|
| 95 | I keep wondering if s/native images/[plain ]firmware files/ ? | |
| 287 | s/NATIVE/PLAIN/ ? or simply "FIRMWARE FILES"? Consistently everywhere (above/below) | |
| 309 | to the full(?) pathname of the firmware file | |
| 324 | I love that example. If you want it more general s/wifi/some/g ;-) | |
| 363 | Is there a sysctl or tunable to change this? | |
| 364 | I would highly love an example on how to manually unload such firmware. Does that need the full path or imagename or ...? | |
| share/man/man9/firmware.9 | ||
|---|---|---|
| 95 | Suggestion: .Pp Firmware binary files may also be loaded directly rather than embedded into kernel modules. | |
| 287 | Presumably s/native/binary/ throughout? | |
| 327 | ||
| 328–329 | ||
| 339 | Yes | |
| 342–343 | ||
| 345–347 | I feel like there's a better word here than 'subpath' that has a well-defined meaning for the "trailing components" of a pathname but I can't think of it. I do think we at least want 'trailing' to indicate that the string match is anchored at the end of the path. | |
| 349–354 | ||
| 356–362 | ||