Change Details

For all manuals in man4/man4.$arch/ directories, use the arch specifier in their document title. Note that this does not include many pages in these directories because they are already done this way, this is part of the spec and I can not imagine this will introduce any regressions. We have a problem in the HW relnotes where we can't keep track of what is for specific architectures. HW relnotes draws from the manuals, and the framework is already all existing in the manual subsystem, it's in the spec, these manuals are in according folders, and ~30% of them are already done. We need to double down on it a bit. The next step will be to get the HW relnotes to show this somehow. Maybe in the HW relnotes e.g. it could say armv8crypto(4aarch64)? Eventually I want to clean up the Makefiles and get the things that are only built for certain arches into these folders, someone else could do that and tag me as a reviewer if they want. Note that arch specific s4 manuals are currently all built for every arch. Also tagging riscv developers because we do not have a man4.riscv and we should. MFC after: 3 days (any reason why not?)

Use the mdoc(7) arch specifier in the document title for (afaik) all remaining manuals reflecting drivers which are only for one architecture. These display at the top of the manual [0] without taking up any extra space and are useful in any case, however I am hoping to use these in the Hardware Release Notes, where architecture specificity is currently unclear. Also tagging riscv developers because we do not have a `/man4/man4.riscv/` and we should. All manuals are built for all architectures, but this helps make things more understandable. [0] Example: https://man-dev.freebsd.org/boot MFC after: 3 days (any reason why not?)

For all manuals in man4/man4.$arch/ directories, use the arch specifier in their document title. Note that this does not include many pages in these directories because they are already done this way, this is part of the spec and I can not imagine this will introduce any regressionsUse the mdoc(7) arch specifier in the document title for (afaik) all remaining manuals reflecting drivers which are only for one architecture. We have a problem in the HW relnotes where we can't keep track of what is for specific architectures. HW relnotes draws from the manuals, and the framework is already all existing in the manual subsystem, it's in the spec, these manuals are in according foldersThese display at the top of the manual [0] without taking up any extra space and are useful in any case, and ~30% ofhowever I am hoping to use these in them are already done. Hardware Release Notes, We need to double down on it a bitwhere architecture specificity is currently unclear. The next step will be to get the HW relnotes to show this somehow. Maybe in the HW relnotes e.g.Also tagging riscv developers because we do not have a `/man4/man4.riscv/` and we should. All manuals are built for all architectures, it could say armv8crypto(4aarch64)?but this helps make things more understandable. Eventually I want to clean up the Makefiles and get the things that are only built for certain arches into these folders, someone else could do that and tag me as a reviewer if they want. Note that arch specific s4 manuals are currently all built for every arch. Also tagging riscv developers because we do not have a man4.riscv and we should.[0] Example: https://man-dev.freebsd.org/boot MFC after: 3 days (any reason why not?)