Please prepend a blank comment line for conformance with style guides and consistency with C style comments.

I know we have widespread usage of this, but if you read mdoc(7), it is wrong.

i dont know the international expectations, but in the US i think firewire would be a much more common and expected search term

tag renders really bad, please use bullet

please no macros in width fields

The how the spec spell it : https://damien.douxchamps.net/ieee1394/libdc1394/iidc/IIDC_1.31.pdf

Write : IIDC over firewire in google, and you get Gemini explaining you IIDC 1394-based digital camera

When i asked AI if we have such driver, it searched "FreeBSD IIDC 1394-based digital camera driver 2025 2026"

In the driver messages i used firewire.

The cameras I have tested so far don't need any bus reset recovery IIDC state is re-established through post_explore.

I left the empty stub as scaffolding so the hook isn't forgotten when I get hardware that does need it (some cameras require re-negotiation after reset).

Happy to remove it and track in my notes if you'd prefer it gone.

It's fine leaving it in here as scaffolding! thanks.

i want humans to be able to search the manual to find what they need. the Nd field contains the search keywords.

fair!

So i put both ?

here too

both is fine with me, although i dont know how to word that elegantly. compare with the other firewire device driver in the tree, https://man.freebsd.org/fwohci

can it only be set in loader.conf and not at runtime? we separate these out usually into SYSCTLS and TUNABLES, which (from ux standpoint) are the same except tunables can only be set at boot time through loader.conf or the loader prompt, whereas you can do that with sysctls but they can also be turned during runtime.