ath(4): Remove MIPS AHB frontend and join PCI one w/ main support again

[marius]

Summary

Following the removal of general MIPS support, there's no longer a need
to have the AHB bus-frontend in place, which according to Linux sources
also isn't used with any non-MIPS SoCs. For simplicity, PCI bus support
is only made conditional on the main one again, i. e. device ath_pci is
removed, and built into the main module, i. e. if_ath_pci.ko obsoleted,
respectively.
Effectively, this reverts the following commits and associated changes:
dba9c8597747c6c9bf3d2ec68f7eb90552878dc7
e849bb3ecbb1963344a22ae77fc96f89fbebf40c

[adrian]

Hi! I know this is a long shot, but if someone wants to do AR9271/AR7010 support (which is USB) it'll need this bus abstraction still.

[marius]

Well, the bus abstraction as such deliberately is left in place, build-wise the PCI bus front-end just is coupled with the core support again (but as for the kernel, also only if has PCI support in the first place as usual). Generally, we consider PCI default enough that there are no seperate modules and devices for PCI bus front-ends even if support for additional busses exists. Currently, ath(4) and ath_pci(4) respectively are one of the very few odd ones out in this regard (I think virtio_pci(4) is the only other offender). Also, with all support for the very resource constraint platforms already gone, even if code for said USB chips would be added today, I believe the few bytes for the bus glue won't matter. The ARMv7 if_ath_pci.o currently is 25 KB and ARMv6 support also already on its way out ...

[adrian]

fiiine :-P

[marius]

Thanks!

[jlduran_gmail.com]

share/man/man4/Makefile

625

This line was missed.

[ehem_freebsd_m5p.com]

Latest build attempt failed. This is my current suspect.

share/man/man4/Makefile

625

I don't yet have a successful build, but this could explain my latest build failure.

[jlduran_gmail.com]

share/man/man4/Makefile

625

It was fixed in 9cb4ee9a6439a8fd3f4e6a692b7a70a61d5ca3a6

[ehem_freebsd_m5p.com]

Missed it when looking for a fix in recent history. Most recent build succeeded, so looks like this was the fix.