Resync with latest commit.

To be clear, the point is to have an explicit panic rather than a boot hang because we end up spinning in an uninitialized trap handler?

Always open /dev/pci read-write.

I had this in D48244 as well. @mat didn't like it and @cperciva pointed out that it can be a useful quick reference for finding out when something was implemented or changed.

Add helper

Can you send ma a git patch with this change? e.g. the output of git format-patch

Fix mandoc -T lint warnings:

• Replace smart quotation mark.
• Wrap the line to 80 characters.

@ivy wrote:

no, but it is no longer supported, so we don't need to support it. it would be different if it had been downgraded to tier 3 rather than becoming entirely unsupported.

Admittedly, I don't see much difference between being demoted to T3 vs. unsupported, although it's another topic. I think we could retain 32-bit PPC support due to mass production of good quality Apple G4 hardware which is scattered around the world and is still useful as a backup boxen, NAS, etc. Another reason to keep it around: different endianness, char signness, 32-bitness force one to write well-typed, correct, sound code. And it's not affected by Y2038 problem, i.e. uses 64-bit time_t.

Adding the wider powerpc umbrella, so others can take a look as well.

But I also have one more question: one of the warnings is also about unexisting .Xr sysctl 2. As I can see, there is no sysctl(2) in FreeBSD, only sysctl(3). But the man pages talks about it in the context of syscalls, so it seems that we can't just change sysctl(2) to sysctl(3) since sysctl(3) is not a syscall. What sould we do about that?

the "extint-gpio1" check returned NULL

The type NULL checks are good. I think the whole of the changes for pmu_send() are a bit overkill. Could you test with just the one line I pointed out, and the rest reverted?

Please commit it.