From 6d8bdc65446a704d0750217efd05532fc641ea7d Mon Sep 17 00:00:00 2001 From: Jacob McDonnell Date: Sat, 25 Apr 2026 14:02:27 -0400 Subject: docs: OpenBSD Man Pages Added --- static/openbsd/man4/Makefile | 782 +++++++++++++ static/openbsd/man4/aac.4 | 77 ++ static/openbsd/man4/abcrtc.4 | 45 + static/openbsd/man4/abl.4 | 49 + static/openbsd/man4/ac97.4 | 76 ++ static/openbsd/man4/acphy.4 | 56 + static/openbsd/man4/acpi.4 | 186 +++ static/openbsd/man4/acpiac.4 | 55 + static/openbsd/man4/acpials.4 | 50 + static/openbsd/man4/acpiasus.4 | 45 + static/openbsd/man4/acpibat.4 | 57 + static/openbsd/man4/acpibtn.4 | 91 ++ static/openbsd/man4/acpicbkbd.4 | 47 + static/openbsd/man4/acpicmos.4 | 36 + static/openbsd/man4/acpicpu.4 | 75 ++ static/openbsd/man4/acpidock.4 | 63 + static/openbsd/man4/acpiec.4 | 54 + static/openbsd/man4/acpige.4 | 42 + static/openbsd/man4/acpihid.4 | 42 + static/openbsd/man4/acpihpet.4 | 46 + static/openbsd/man4/acpihve.4 | 37 + static/openbsd/man4/acpimadt.4 | 45 + static/openbsd/man4/acpimcfg.4 | 44 + static/openbsd/man4/acpipci.4 | 45 + static/openbsd/man4/acpiprt.4 | 48 + static/openbsd/man4/acpipwrres.4 | 45 + static/openbsd/man4/acpisbs.4 | 56 + static/openbsd/man4/acpisony.4 | 43 + static/openbsd/man4/acpisurface.4 | 47 + static/openbsd/man4/acpithinkpad.4 | 51 + static/openbsd/man4/acpitimer.4 | 46 + static/openbsd/man4/acpitoshiba.4 | 49 + static/openbsd/man4/acpitz.4 | 56 + static/openbsd/man4/acpivideo.4 | 56 + static/openbsd/man4/acpivout.4 | 49 + static/openbsd/man4/acpiwmi.4 | 37 + static/openbsd/man4/acrtc.4 | 45 + static/openbsd/man4/acx.4 | 209 ++++ static/openbsd/man4/adc.4 | 50 + static/openbsd/man4/addcom.4 | 87 ++ static/openbsd/man4/adl.4 | 48 + static/openbsd/man4/admcts.4 | 50 + static/openbsd/man4/admlc.4 | 50 + static/openbsd/man4/admtemp.4 | 55 + static/openbsd/man4/admtm.4 | 50 + static/openbsd/man4/admtmp.4 | 50 + static/openbsd/man4/admtt.4 | 50 + static/openbsd/man4/adt.4 | 53 + static/openbsd/man4/adtfsm.4 | 49 + static/openbsd/man4/adv.4 | 125 ++ static/openbsd/man4/age.4 | 83 ++ static/openbsd/man4/aggr.4 | 102 ++ static/openbsd/man4/agp.4 | 49 + static/openbsd/man4/ahc.4 | 301 +++++ static/openbsd/man4/ahci.4 | 65 ++ static/openbsd/man4/ahd.4 | 156 +++ static/openbsd/man4/aibs.4 | 183 +++ static/openbsd/man4/aic.4 | 92 ++ static/openbsd/man4/akbd.4 | 169 +++ static/openbsd/man4/alc.4 | 83 ++ static/openbsd/man4/ale.4 | 84 ++ static/openbsd/man4/alipm.4 | 50 + static/openbsd/man4/amas.4 | 86 ++ static/openbsd/man4/amdgpio.4 | 49 + static/openbsd/man4/amdiic.4 | 50 + static/openbsd/man4/amdpm.4 | 64 + static/openbsd/man4/amdpmc.4 | 44 + static/openbsd/man4/ami.4 | 136 +++ static/openbsd/man4/amlclock.4 | 42 + static/openbsd/man4/amldwusb.4 | 46 + static/openbsd/man4/amliic.4 | 44 + static/openbsd/man4/amlmmc.4 | 51 + static/openbsd/man4/amlpciephy.4 | 43 + static/openbsd/man4/amlpinctrl.4 | 42 + static/openbsd/man4/amlpwm.4 | 42 + static/openbsd/man4/amlreset.4 | 42 + static/openbsd/man4/amlrng.4 | 47 + static/openbsd/man4/amlsm.4 | 45 + static/openbsd/man4/amltemp.4 | 48 + static/openbsd/man4/amluart.4 | 42 + static/openbsd/man4/amlusbphy.4 | 43 + static/openbsd/man4/amphy.4 | 45 + static/openbsd/man4/ams.4 | 69 ++ static/openbsd/man4/an.4 | 190 +++ static/openbsd/man4/andl.4 | 54 + static/openbsd/man4/aplgpio.4 | 50 + static/openbsd/man4/aps.4 | 70 ++ static/openbsd/man4/aq.4 | 71 ++ static/openbsd/man4/arc.4 | 147 +++ static/openbsd/man4/arcofi.4 | 101 ++ static/openbsd/man4/asbtm.4 | 45 + static/openbsd/man4/asmc.4 | 65 ++ static/openbsd/man4/ast.4 | 129 +++ static/openbsd/man4/atapiscsi.4 | 100 ++ static/openbsd/man4/ath.4 | 353 ++++++ static/openbsd/man4/athn.4 | 274 +++++ static/openbsd/man4/atphy.4 | 34 + static/openbsd/man4/atu.4 | 209 ++++ static/openbsd/man4/atw.4 | 238 ++++ static/openbsd/man4/auacer.4 | 55 + static/openbsd/man4/audio.4 | 520 +++++++++ static/openbsd/man4/aue.4 | 214 ++++ static/openbsd/man4/auglx.4 | 40 + static/openbsd/man4/auich.4 | 81 ++ static/openbsd/man4/auixp.4 | 58 + static/openbsd/man4/autri.4 | 56 + static/openbsd/man4/auvia.4 | 58 + static/openbsd/man4/axe.4 | 175 +++ static/openbsd/man4/axen.4 | 89 ++ static/openbsd/man4/axppmic.4 | 51 + static/openbsd/man4/azalia.4 | 269 +++++ static/openbsd/man4/bce.4 | 91 ++ static/openbsd/man4/bcmaux.4 | 42 + static/openbsd/man4/bcmbsc.4 | 46 + static/openbsd/man4/bcmclock.4 | 44 + static/openbsd/man4/bcmdmac.4 | 55 + static/openbsd/man4/bcmdog.4 | 44 + static/openbsd/man4/bcmgpio.4 | 46 + static/openbsd/man4/bcmirng.4 | 47 + static/openbsd/man4/bcmmbox.4 | 44 + static/openbsd/man4/bcmpcie.4 | 44 + static/openbsd/man4/bcmrng.4 | 47 + static/openbsd/man4/bcmsdhost.4 | 63 + static/openbsd/man4/bcmstbgpio.4 | 46 + static/openbsd/man4/bcmstbintc.4 | 44 + static/openbsd/man4/bcmstbpinctrl.4 | 47 + static/openbsd/man4/bcmstbrescal.4 | 47 + static/openbsd/man4/bcmstbreset.4 | 46 + static/openbsd/man4/bcmtemp.4 | 48 + static/openbsd/man4/bcmtmon.4 | 48 + static/openbsd/man4/bdpmic.4 | 43 + static/openbsd/man4/berkwdt.4 | 53 + static/openbsd/man4/bge.4 | 202 ++++ static/openbsd/man4/bgw.4 | 49 + static/openbsd/man4/bio.4 | 180 +++ static/openbsd/man4/bktr.4 | 477 ++++++++ static/openbsd/man4/bmtphy.4 | 48 + static/openbsd/man4/bnx.4 | 181 +++ static/openbsd/man4/bnxt.4 | 75 ++ static/openbsd/man4/boca.4 | 107 ++ static/openbsd/man4/bpe.4 | 160 +++ static/openbsd/man4/bpf.4 | 1119 ++++++++++++++++++ static/openbsd/man4/brgphy.4 | 46 + static/openbsd/man4/bridge.4 | 703 +++++++++++ static/openbsd/man4/brswphy.4 | 46 + static/openbsd/man4/bse.4 | 81 ++ static/openbsd/man4/bwfm.4 | 164 +++ static/openbsd/man4/bwi.4 | 170 +++ static/openbsd/man4/bytgpio.4 | 46 + static/openbsd/man4/cac.4 | 91 ++ static/openbsd/man4/cad.4 | 73 ++ static/openbsd/man4/cardbus.4 | 113 ++ static/openbsd/man4/carp.4 | 288 +++++ static/openbsd/man4/cas.4 | 105 ++ static/openbsd/man4/ccp.4 | 51 + static/openbsd/man4/ccpmic.4 | 51 + static/openbsd/man4/cd.4 | 347 ++++++ static/openbsd/man4/cdce.4 | 151 +++ static/openbsd/man4/cdpcie.4 | 44 + static/openbsd/man4/cdsdhc.4 | 40 + static/openbsd/man4/cduart.4 | 36 + static/openbsd/man4/cfxga.4 | 55 + static/openbsd/man4/ch.4 | 90 ++ static/openbsd/man4/chvgpio.4 | 46 + static/openbsd/man4/ciphy.4 | 34 + static/openbsd/man4/ciss.4 | 68 ++ static/openbsd/man4/clcs.4 | 61 + static/openbsd/man4/clct.4 | 52 + static/openbsd/man4/cmpci.4 | 70 ++ static/openbsd/man4/com.4 | 165 +++ static/openbsd/man4/cue.4 | 102 ++ static/openbsd/man4/cwfg.4 | 49 + static/openbsd/man4/cy.4 | 93 ++ static/openbsd/man4/cz.4 | 134 +++ static/openbsd/man4/dapmic.4 | 45 + static/openbsd/man4/dc.4 | 393 +++++++ static/openbsd/man4/dcphy.4 | 23 + static/openbsd/man4/ddb.4 | 1303 +++++++++++++++++++++ static/openbsd/man4/de.4 | 131 +++ static/openbsd/man4/diskmap.4 | 58 + static/openbsd/man4/divert.4 | 210 ++++ static/openbsd/man4/drm.4 | 93 ++ static/openbsd/man4/dsxrtc.4 | 44 + static/openbsd/man4/dt.4 | 158 +++ static/openbsd/man4/dwctwo.4 | 43 + static/openbsd/man4/dwdog.4 | 44 + static/openbsd/man4/dwge.4 | 83 ++ static/openbsd/man4/dwgpio.4 | 45 + static/openbsd/man4/dwiic.4 | 55 + static/openbsd/man4/dwmmc.4 | 53 + static/openbsd/man4/dwmshc.4 | 55 + static/openbsd/man4/dwpcie.4 | 44 + static/openbsd/man4/dwqe.4 | 65 ++ static/openbsd/man4/dwxe.4 | 71 ++ static/openbsd/man4/eap.4 | 58 + static/openbsd/man4/ec.4 | 87 ++ static/openbsd/man4/eephy.4 | 45 + static/openbsd/man4/ef.4 | 93 ++ static/openbsd/man4/efi.4 | 102 ++ static/openbsd/man4/eg.4 | 65 ++ static/openbsd/man4/ehci.4 | 75 ++ static/openbsd/man4/eisa.4 | 111 ++ static/openbsd/man4/el.4 | 65 ++ static/openbsd/man4/em.4 | 228 ++++ static/openbsd/man4/emc.4 | 46 + static/openbsd/man4/emu.4 | 110 ++ static/openbsd/man4/enc.4 | 161 +++ static/openbsd/man4/endrun.4 | 82 ++ static/openbsd/man4/envy.4 | 132 +++ static/openbsd/man4/eoip.4 | 209 ++++ static/openbsd/man4/ep.4 | 152 +++ static/openbsd/man4/epic.4 | 105 ++ static/openbsd/man4/erspan.4 | 226 ++++ static/openbsd/man4/esa.4 | 61 + static/openbsd/man4/escodec.4 | 47 + static/openbsd/man4/eso.4 | 71 ++ static/openbsd/man4/ess.4 | 83 ++ static/openbsd/man4/et.4 | 71 ++ static/openbsd/man4/etherip.4 | 186 +++ static/openbsd/man4/etphy.4 | 51 + static/openbsd/man4/ex.4 | 52 + static/openbsd/man4/exphy.4 | 49 + static/openbsd/man4/exrtc.4 | 41 + static/openbsd/man4/fanpwr.4 | 43 + static/openbsd/man4/fd.4 | 97 ++ static/openbsd/man4/fdc.4 | 125 ++ static/openbsd/man4/fec.4 | 45 + static/openbsd/man4/fido.4 | 55 + static/openbsd/man4/fins.4 | 70 ++ static/openbsd/man4/fintek.4 | 66 ++ static/openbsd/man4/fms.4 | 67 ++ static/openbsd/man4/frame.4 | 244 ++++ static/openbsd/man4/fusbtc.4 | 46 + static/openbsd/man4/fuse.4 | 47 + static/openbsd/man4/fxp.4 | 144 +++ static/openbsd/man4/gcu.4 | 57 + static/openbsd/man4/gdt.4 | 149 +++ static/openbsd/man4/gem.4 | 106 ++ static/openbsd/man4/gentbi.4 | 49 + static/openbsd/man4/gfrtc.4 | 34 + static/openbsd/man4/gif.4 | 131 +++ static/openbsd/man4/glenv.4 | 52 + static/openbsd/man4/glkgpio.4 | 50 + static/openbsd/man4/gpio.4 | 219 ++++ static/openbsd/man4/gpiocharger.4 | 51 + static/openbsd/man4/gpiodcf.4 | 99 ++ static/openbsd/man4/gpioiic.4 | 80 ++ static/openbsd/man4/gpiokeys.4 | 50 + static/openbsd/man4/gpioleds.4 | 45 + static/openbsd/man4/gpioow.4 | 66 ++ static/openbsd/man4/graphaudio.4 | 49 + static/openbsd/man4/gre.4 | 797 +++++++++++++ static/openbsd/man4/gscsio.4 | 61 + static/openbsd/man4/hds.4 | 46 + static/openbsd/man4/hiclock.4 | 42 + static/openbsd/man4/hidwusb.4 | 44 + static/openbsd/man4/hil.4 | 80 ++ static/openbsd/man4/hilid.4 | 46 + static/openbsd/man4/hilkbd.4 | 106 ++ static/openbsd/man4/hilms.4 | 47 + static/openbsd/man4/hireset.4 | 42 + static/openbsd/man4/hitemp.4 | 48 + static/openbsd/man4/hme.4 | 100 ++ static/openbsd/man4/hotplug.4 | 104 ++ static/openbsd/man4/hsq.4 | 103 ++ static/openbsd/man4/hvn.4 | 61 + static/openbsd/man4/hvs.4 | 50 + static/openbsd/man4/hyperv.4 | 73 ++ static/openbsd/man4/iasuskbd.4 | 51 + static/openbsd/man4/iatp.4 | 46 + static/openbsd/man4/iavf.4 | 49 + static/openbsd/man4/icc.4 | 48 + static/openbsd/man4/ice.4 | 83 ++ static/openbsd/man4/ichiic.4 | 58 + static/openbsd/man4/ichwdt.4 | 57 + static/openbsd/man4/icmp.4 | 185 +++ static/openbsd/man4/icmp6.4 | 257 +++++ static/openbsd/man4/icsphy.4 | 50 + static/openbsd/man4/ietp.4 | 47 + static/openbsd/man4/ifmedia.4 | 573 +++++++++ static/openbsd/man4/igc.4 | 50 + static/openbsd/man4/iha.4 | 80 ++ static/openbsd/man4/ihidev.4 | 41 + static/openbsd/man4/iic.4 | 307 +++++ static/openbsd/man4/iicmux.4 | 44 + static/openbsd/man4/ikbd.4 | 40 + static/openbsd/man4/ims.4 | 46 + static/openbsd/man4/imt.4 | 47 + static/openbsd/man4/imxanatop.4 | 42 + static/openbsd/man4/imxdog.4 | 44 + static/openbsd/man4/imxesdhc.4 | 48 + static/openbsd/man4/imxgpc.4 | 43 + static/openbsd/man4/imxgpio.4 | 43 + static/openbsd/man4/imxiic.4 | 44 + static/openbsd/man4/imxpciephy.4 | 42 + static/openbsd/man4/imxpwm.4 | 42 + static/openbsd/man4/imxrtc.4 | 42 + static/openbsd/man4/imxspi.4 | 41 + static/openbsd/man4/imxsrc.4 | 43 + static/openbsd/man4/imxtmu.4 | 48 + static/openbsd/man4/imxuart.4 | 42 + static/openbsd/man4/inet.4 | 182 +++ static/openbsd/man4/inet6.4 | 222 ++++ static/openbsd/man4/inphy.4 | 50 + static/openbsd/man4/intelpmc.4 | 44 + static/openbsd/man4/inthid.4 | 42 + static/openbsd/man4/iophy.4 | 49 + static/openbsd/man4/iosf.4 | 50 + static/openbsd/man4/ip.4 | 619 ++++++++++ static/openbsd/man4/ip6.4 | 659 +++++++++++ static/openbsd/man4/ipcomp.4 | 124 ++ static/openbsd/man4/ipgphy.4 | 34 + static/openbsd/man4/ipmi.4 | 180 +++ static/openbsd/man4/ips.4 | 87 ++ static/openbsd/man4/ipsec.4 | 430 +++++++ static/openbsd/man4/ipw.4 | 162 +++ static/openbsd/man4/isa.4 | 226 ++++ static/openbsd/man4/isagpio.4 | 59 + static/openbsd/man4/isapnp.4 | 140 +++ static/openbsd/man4/islrtc.4 | 44 + static/openbsd/man4/ispi.4 | 38 + static/openbsd/man4/it.4 | 98 ++ static/openbsd/man4/itherm.4 | 69 ++ static/openbsd/man4/iwi.4 | 162 +++ static/openbsd/man4/iwm.4 | 169 +++ static/openbsd/man4/iwn.4 | 216 ++++ static/openbsd/man4/iwx.4 | 177 +++ static/openbsd/man4/ix.4 | 106 ++ static/openbsd/man4/ixgb.4 | 118 ++ static/openbsd/man4/ixl.4 | 62 + static/openbsd/man4/ixv.4 | 61 + static/openbsd/man4/jmb.4 | 55 + static/openbsd/man4/jme.4 | 81 ++ static/openbsd/man4/jmphy.4 | 51 + static/openbsd/man4/kate.4 | 98 ++ static/openbsd/man4/kcov.4 | 206 ++++ static/openbsd/man4/km.4 | 77 ++ static/openbsd/man4/ksmn.4 | 49 + static/openbsd/man4/kstat.4 | 210 ++++ static/openbsd/man4/ksyms.4 | 91 ++ static/openbsd/man4/kubsan.4 | 108 ++ static/openbsd/man4/kue.4 | 137 +++ static/openbsd/man4/lc.4 | 84 ++ static/openbsd/man4/lge.4 | 135 +++ static/openbsd/man4/lii.4 | 115 ++ static/openbsd/man4/lisa.4 | 71 ++ static/openbsd/man4/lm.4 | 147 +++ static/openbsd/man4/lmenv.4 | 62 + static/openbsd/man4/lmn.4 | 49 + static/openbsd/man4/lmtemp.4 | 45 + static/openbsd/man4/lo.4 | 85 ++ static/openbsd/man4/lpt.4 | 81 ++ static/openbsd/man4/luphy.4 | 33 + static/openbsd/man4/lxtphy.4 | 50 + static/openbsd/man4/maestro.4 | 77 ++ static/openbsd/man4/mainbus.4 | 36 + static/openbsd/man4/malo.4 | 168 +++ static/openbsd/man4/man4.alpha/Makefile | 20 + static/openbsd/man4/man4.alpha/apecs.4 | 49 + static/openbsd/man4/man4.alpha/asc.4 | 29 + static/openbsd/man4/man4.alpha/autoconf.4 | 53 + static/openbsd/man4/man4.alpha/bba.4 | 53 + static/openbsd/man4/man4.alpha/cia.4 | 49 + static/openbsd/man4/man4.alpha/intro.4 | 420 +++++++ static/openbsd/man4/man4.alpha/ioasic.4 | 87 ++ static/openbsd/man4/man4.alpha/irongate.4 | 48 + static/openbsd/man4/man4.alpha/lca.4 | 47 + static/openbsd/man4/man4.alpha/le.4 | 28 + static/openbsd/man4/man4.alpha/mcbus.4 | 62 + static/openbsd/man4/man4.alpha/mcpcia.4 | 48 + static/openbsd/man4/man4.alpha/mem.4 | 85 ++ static/openbsd/man4/man4.alpha/tcasic.4 | 48 + static/openbsd/man4/man4.alpha/tga.4 | 74 ++ static/openbsd/man4/man4.alpha/tsc.4 | 63 + static/openbsd/man4/man4.alpha/tsciic.4 | 48 + static/openbsd/man4/man4.alpha/zs.4 | 108 ++ static/openbsd/man4/man4.amd64/Makefile | 19 + static/openbsd/man4/man4.amd64/amdpcib.4 | 33 + static/openbsd/man4/man4.amd64/apm.4 | 167 +++ static/openbsd/man4/man4.amd64/autoconf.4 | 52 + static/openbsd/man4/man4.amd64/bios.4 | 51 + static/openbsd/man4/man4.amd64/cpu.4 | 78 ++ static/openbsd/man4/man4.amd64/efifb.4 | 47 + static/openbsd/man4/man4.amd64/intro.4 | 122 ++ static/openbsd/man4/man4.amd64/ioapic.4 | 46 + static/openbsd/man4/man4.amd64/mem.4 | 87 ++ static/openbsd/man4/man4.amd64/mpbios.4 | 58 + static/openbsd/man4/man4.amd64/mtrr.4 | 146 +++ static/openbsd/man4/man4.amd64/nvram.4 | 52 + static/openbsd/man4/man4.amd64/pctr.4 | 234 ++++ static/openbsd/man4/man4.amd64/skgpio.4 | 57 + static/openbsd/man4/man4.amd64/tcpcib.4 | 71 ++ static/openbsd/man4/man4.amd64/vmm.4 | 122 ++ static/openbsd/man4/man4.arm64/Makefile | 38 + static/openbsd/man4/man4.arm64/agintc.4 | 36 + static/openbsd/man4/man4.arm64/agtimer.4 | 33 + static/openbsd/man4/man4.arm64/ampchwm.4 | 48 + static/openbsd/man4/man4.arm64/ampintc.4 | 36 + static/openbsd/man4/man4.arm64/aplaudio.4 | 48 + static/openbsd/man4/man4.arm64/aplcpu.4 | 50 + static/openbsd/man4/man4.arm64/apldart.4 | 42 + static/openbsd/man4/man4.arm64/apldcp.4 | 51 + static/openbsd/man4/man4.arm64/apldma.4 | 47 + static/openbsd/man4/man4.arm64/apldog.4 | 42 + static/openbsd/man4/man4.arm64/apldrm.4 | 52 + static/openbsd/man4/man4.arm64/aplefuse.4 | 42 + static/openbsd/man4/man4.arm64/aplhidev.4 | 50 + static/openbsd/man4/man4.arm64/apliic.4 | 42 + static/openbsd/man4/man4.arm64/aplintc.4 | 42 + static/openbsd/man4/man4.arm64/aplmbox.4 | 42 + static/openbsd/man4/man4.arm64/aplmca.4 | 47 + static/openbsd/man4/man4.arm64/aplnco.4 | 43 + static/openbsd/man4/man4.arm64/aplns.4 | 38 + static/openbsd/man4/man4.arm64/aplpcie.4 | 44 + static/openbsd/man4/man4.arm64/aplpinctrl.4 | 42 + static/openbsd/man4/man4.arm64/aplpmgr.4 | 42 + static/openbsd/man4/man4.arm64/aplpmu.4 | 43 + static/openbsd/man4/man4.arm64/aplpwm.4 | 42 + static/openbsd/man4/man4.arm64/aplsart.4 | 42 + static/openbsd/man4/man4.arm64/aplsmc.4 | 50 + static/openbsd/man4/man4.arm64/aplspi.4 | 42 + static/openbsd/man4/man4.arm64/aplspmi.4 | 44 + static/openbsd/man4/man4.arm64/apm.4 | 178 +++ static/openbsd/man4/man4.arm64/intro.4 | 117 ++ static/openbsd/man4/man4.arm64/rpiclock.4 | 44 + static/openbsd/man4/man4.arm64/rpipwm.4 | 44 + static/openbsd/man4/man4.arm64/rpirtc.4 | 42 + static/openbsd/man4/man4.arm64/rpone.4 | 49 + static/openbsd/man4/man4.arm64/smbios.4 | 36 + static/openbsd/man4/man4.armv7/Makefile | 35 + static/openbsd/man4/man4.armv7/agtimer.4 | 33 + static/openbsd/man4/man4.armv7/amdisplay.4 | 76 ++ static/openbsd/man4/man4.armv7/ampintc.4 | 36 + static/openbsd/man4/man4.armv7/amptimer.4 | 30 + static/openbsd/man4/man4.armv7/armliicc.4 | 34 + static/openbsd/man4/man4.armv7/cortex.4 | 28 + static/openbsd/man4/man4.armv7/cpsw.4 | 49 + static/openbsd/man4/man4.armv7/dmtimer.4 | 38 + static/openbsd/man4/man4.armv7/edma.4 | 38 + static/openbsd/man4/man4.armv7/gptimer.4 | 38 + static/openbsd/man4/man4.armv7/imxtemp.4 | 50 + static/openbsd/man4/man4.armv7/intc.4 | 38 + static/openbsd/man4/man4.armv7/intro.4 | 117 ++ static/openbsd/man4/man4.armv7/mvodog.4 | 44 + static/openbsd/man4/man4.armv7/mvortc.4 | 41 + static/openbsd/man4/man4.armv7/omap.4 | 49 + static/openbsd/man4/man4.armv7/omclock.4 | 43 + static/openbsd/man4/man4.armv7/omcm.4 | 43 + static/openbsd/man4/man4.armv7/omdog.4 | 38 + static/openbsd/man4/man4.armv7/omgpio.4 | 50 + static/openbsd/man4/man4.armv7/ommmc.4 | 51 + static/openbsd/man4/man4.armv7/omrng.4 | 47 + static/openbsd/man4/man4.armv7/omsysc.4 | 42 + static/openbsd/man4/man4.armv7/omwugen.4 | 30 + static/openbsd/man4/man4.armv7/prcm.4 | 38 + static/openbsd/man4/man4.armv7/sxie.4 | 41 + static/openbsd/man4/man4.armv7/sxiintc.4 | 34 + static/openbsd/man4/man4.armv7/sxitimer.4 | 34 + static/openbsd/man4/man4.armv7/sxits.4 | 48 + static/openbsd/man4/man4.armv7/sysreg.4 | 36 + static/openbsd/man4/man4.armv7/zqclock.4 | 37 + static/openbsd/man4/man4.armv7/zqreset.4 | 37 + static/openbsd/man4/man4.hppa/Makefile | 25 + static/openbsd/man4/man4.hppa/asp.4 | 97 ++ static/openbsd/man4/man4.hppa/astro.4 | 43 + static/openbsd/man4/man4.hppa/cpu.4 | 243 ++++ static/openbsd/man4/man4.hppa/dino.4 | 74 ++ static/openbsd/man4/man4.hppa/elroy.4 | 39 + static/openbsd/man4/man4.hppa/gecko.4 | 38 + static/openbsd/man4/man4.hppa/gsc.4 | 113 ++ static/openbsd/man4/man4.hppa/gsckbc.4 | 52 + static/openbsd/man4/man4.hppa/harmony.4 | 89 ++ static/openbsd/man4/man4.hppa/ie.4 | 90 ++ static/openbsd/man4/man4.hppa/intro.4 | 228 ++++ static/openbsd/man4/man4.hppa/io.4 | 166 +++ static/openbsd/man4/man4.hppa/lasi.4 | 134 +++ static/openbsd/man4/man4.hppa/lcd.4 | 44 + static/openbsd/man4/man4.hppa/mem.4 | 87 ++ static/openbsd/man4/man4.hppa/mongoose.4 | 56 + static/openbsd/man4/man4.hppa/pdc.4 | 732 ++++++++++++ static/openbsd/man4/man4.hppa/phantomas.4 | 69 ++ static/openbsd/man4/man4.hppa/power.4 | 84 ++ static/openbsd/man4/man4.hppa/runway.4 | 65 ++ static/openbsd/man4/man4.hppa/ssio.4 | 51 + static/openbsd/man4/man4.hppa/uturn.4 | 65 ++ static/openbsd/man4/man4.hppa/wax.4 | 105 ++ static/openbsd/man4/man4.i386/Makefile | 38 + static/openbsd/man4/man4.i386/amdmsr.4 | 59 + static/openbsd/man4/man4.i386/amdpcib.4 | 33 + static/openbsd/man4/man4.i386/apm.4 | 221 ++++ static/openbsd/man4/man4.i386/autoconf.4 | 52 + static/openbsd/man4/man4.i386/bios.4 | 95 ++ static/openbsd/man4/man4.i386/cpu.4 | 99 ++ static/openbsd/man4/man4.i386/esm.4 | 89 ++ static/openbsd/man4/man4.i386/geodesc.4 | 49 + static/openbsd/man4/man4.i386/glxpcib.4 | 46 + static/openbsd/man4/man4.i386/glxsb.4 | 57 + static/openbsd/man4/man4.i386/gscpcib.4 | 65 ++ static/openbsd/man4/man4.i386/gscpm.4 | 43 + static/openbsd/man4/man4.i386/gus.4 | 100 ++ static/openbsd/man4/man4.i386/ichpcib.4 | 89 ++ static/openbsd/man4/man4.i386/ie.4 | 60 + static/openbsd/man4/man4.i386/intro.4 | 127 ++ static/openbsd/man4/man4.i386/ioapic.4 | 46 + static/openbsd/man4/man4.i386/joy.4 | 152 +++ static/openbsd/man4/man4.i386/le.4 | 58 + static/openbsd/man4/man4.i386/lms.4 | 57 + static/openbsd/man4/man4.i386/mem.4 | 87 ++ static/openbsd/man4/man4.i386/mms.4 | 57 + static/openbsd/man4/man4.i386/mpbios.4 | 59 + static/openbsd/man4/man4.i386/mtrr.4 | 147 +++ static/openbsd/man4/man4.i386/npx.4 | 63 + static/openbsd/man4/man4.i386/nvram.4 | 52 + static/openbsd/man4/man4.i386/pas.4 | 45 + static/openbsd/man4/man4.i386/pcibios.4 | 180 +++ static/openbsd/man4/man4.i386/pctr.4 | 281 +++++ static/openbsd/man4/man4.i386/sb.4 | 96 ++ static/openbsd/man4/man4.i386/skgpio.4 | 57 + static/openbsd/man4/man4.i386/tcpcib.4 | 71 ++ static/openbsd/man4/man4.i386/uha.4 | 55 + static/openbsd/man4/man4.i386/wds.4 | 61 + static/openbsd/man4/man4.i386/wdt.4 | 68 ++ static/openbsd/man4/man4.landisk/Makefile | 8 + static/openbsd/man4/man4.landisk/intro.4 | 139 +++ static/openbsd/man4/man4.landisk/mem.4 | 81 ++ static/openbsd/man4/man4.landisk/obio.4 | 68 ++ static/openbsd/man4/man4.landisk/power.4 | 50 + static/openbsd/man4/man4.landisk/shpcic.4 | 38 + static/openbsd/man4/man4.loongson/Makefile | 18 + static/openbsd/man4/man4.loongson/apm.4 | 211 ++++ static/openbsd/man4/man4.loongson/autoconf.4 | 53 + static/openbsd/man4/man4.loongson/bonito.4 | 48 + static/openbsd/man4/man4.loongson/gdiumiic.4 | 52 + static/openbsd/man4/man4.loongson/glxclk.4 | 43 + static/openbsd/man4/man4.loongson/glxpcib.4 | 51 + static/openbsd/man4/man4.loongson/htb.4 | 42 + static/openbsd/man4/man4.loongson/intro.4 | 109 ++ static/openbsd/man4/man4.loongson/leioc.4 | 68 ++ static/openbsd/man4/man4.loongson/mem.4 | 111 ++ static/openbsd/man4/man4.loongson/sisfb.4 | 47 + static/openbsd/man4/man4.loongson/smfb.4 | 47 + static/openbsd/man4/man4.loongson/stsec.4 | 42 + static/openbsd/man4/man4.loongson/voyager.4 | 81 ++ static/openbsd/man4/man4.loongson/ykbec.4 | 54 + static/openbsd/man4/man4.luna88k/Makefile | 12 + static/openbsd/man4/man4.luna88k/autoconf.4 | 53 + static/openbsd/man4/man4.luna88k/cbus.4 | 50 + static/openbsd/man4/man4.luna88k/intro.4 | 119 ++ static/openbsd/man4/man4.luna88k/lcd.4 | 81 ++ static/openbsd/man4/man4.luna88k/le.4 | 59 + static/openbsd/man4/man4.luna88k/mem.4 | 85 ++ static/openbsd/man4/man4.luna88k/necsb.4 | 41 + static/openbsd/man4/man4.luna88k/pcexmem.4 | 76 ++ static/openbsd/man4/man4.luna88k/spc.4 | 54 + static/openbsd/man4/man4.luna88k/xp.4 | 73 ++ static/openbsd/man4/man4.macppc/Makefile | 36 + static/openbsd/man4/man4.macppc/abtn.4 | 55 + static/openbsd/man4/man4.macppc/adb.4 | 112 ++ static/openbsd/man4/man4.macppc/aoa.4 | 78 ++ static/openbsd/man4/man4.macppc/apm.4 | 220 ++++ static/openbsd/man4/man4.macppc/asms.4 | 68 ++ static/openbsd/man4/man4.macppc/autoconf.4 | 52 + static/openbsd/man4/man4.macppc/awacs.4 | 82 ++ static/openbsd/man4/man4.macppc/bm.4 | 64 + static/openbsd/man4/man4.macppc/daca.4 | 74 ++ static/openbsd/man4/man4.macppc/dfs.4 | 53 + static/openbsd/man4/man4.macppc/fcu.4 | 45 + static/openbsd/man4/man4.macppc/hpb.4 | 40 + static/openbsd/man4/man4.macppc/ht.4 | 48 + static/openbsd/man4/man4.macppc/intro.4 | 120 ++ static/openbsd/man4/man4.macppc/kauaiata.4 | 51 + static/openbsd/man4/man4.macppc/kiic.4 | 51 + static/openbsd/man4/man4.macppc/macgpio.4 | 45 + static/openbsd/man4/man4.macppc/macobio.4 | 86 ++ static/openbsd/man4/man4.macppc/mc.4 | 71 ++ static/openbsd/man4/man4.macppc/mediabay.4 | 51 + static/openbsd/man4/man4.macppc/mem.4 | 85 ++ static/openbsd/man4/man4.macppc/memc.4 | 42 + static/openbsd/man4/man4.macppc/mpcpcibr.4 | 42 + static/openbsd/man4/man4.macppc/onyx.4 | 64 + static/openbsd/man4/man4.macppc/openpic.4 | 39 + static/openbsd/man4/man4.macppc/pgs.4 | 49 + static/openbsd/man4/man4.macppc/piic.4 | 47 + static/openbsd/man4/man4.macppc/smu.4 | 50 + static/openbsd/man4/man4.macppc/snapper.4 | 105 ++ static/openbsd/man4/man4.macppc/sysbutton.4 | 41 + static/openbsd/man4/man4.macppc/tumbler.4 | 82 ++ static/openbsd/man4/man4.macppc/xlights.4 | 41 + static/openbsd/man4/man4.macppc/zs.4 | 71 ++ static/openbsd/man4/man4.octeon/Makefile | 26 + static/openbsd/man4/man4.octeon/amdcf.4 | 55 + static/openbsd/man4/man4.octeon/cnmac.4 | 86 ++ static/openbsd/man4/man4.octeon/intro.4 | 111 ++ static/openbsd/man4/man4.octeon/octboot.4 | 62 + static/openbsd/man4/man4.octeon/octcf.4 | 39 + static/openbsd/man4/man4.octeon/octcib.4 | 38 + static/openbsd/man4/man4.octeon/octcit.4 | 48 + static/openbsd/man4/man4.octeon/octciu.4 | 50 + static/openbsd/man4/man4.octeon/octcrypto.4 | 61 + static/openbsd/man4/man4.octeon/octgmx.4 | 38 + static/openbsd/man4/man4.octeon/octgpio.4 | 37 + static/openbsd/man4/man4.octeon/octiic.4 | 40 + static/openbsd/man4/man4.octeon/octmmc.4 | 41 + static/openbsd/man4/man4.octeon/octpcie.4 | 50 + static/openbsd/man4/man4.octeon/octpip.4 | 37 + static/openbsd/man4/man4.octeon/octrng.4 | 50 + static/openbsd/man4/man4.octeon/octrtc.4 | 62 + static/openbsd/man4/man4.octeon/octsctl.4 | 37 + static/openbsd/man4/man4.octeon/octsmi.4 | 38 + static/openbsd/man4/man4.octeon/octuctl.4 | 48 + static/openbsd/man4/man4.octeon/octxctl.4 | 37 + static/openbsd/man4/man4.octeon/ogx.4 | 46 + static/openbsd/man4/man4.octeon/ogxnexus.4 | 45 + static/openbsd/man4/man4.powerpc64/Makefile | 12 + static/openbsd/man4/man4.powerpc64/astfb.4 | 55 + static/openbsd/man4/man4.powerpc64/intro.4 | 109 ++ static/openbsd/man4/man4.powerpc64/opal.4 | 43 + static/openbsd/man4/man4.powerpc64/opalcons.4 | 47 + static/openbsd/man4/man4.powerpc64/opalsens.4 | 43 + static/openbsd/man4/man4.powerpc64/phb.4 | 44 + static/openbsd/man4/man4.powerpc64/xicp.4 | 44 + static/openbsd/man4/man4.powerpc64/xics.4 | 44 + static/openbsd/man4/man4.powerpc64/xive.4 | 44 + static/openbsd/man4/man4.riscv64/Makefile | 25 + static/openbsd/man4/man4.riscv64/intro.4 | 113 ++ static/openbsd/man4/man4.riscv64/mpfclock.4 | 37 + static/openbsd/man4/man4.riscv64/mpfgpio.4 | 55 + static/openbsd/man4/man4.riscv64/mpfiic.4 | 40 + static/openbsd/man4/man4.riscv64/plic.4 | 28 + static/openbsd/man4/man4.riscv64/sfcc.4 | 28 + static/openbsd/man4/man4.riscv64/sfclock.4 | 28 + static/openbsd/man4/man4.riscv64/sfgpio.4 | 43 + static/openbsd/man4/man4.riscv64/sfuart.4 | 30 + static/openbsd/man4/man4.riscv64/sgmsi.4 | 42 + static/openbsd/man4/man4.riscv64/smtclock.4 | 42 + static/openbsd/man4/man4.riscv64/smtcomphy.4 | 43 + static/openbsd/man4/man4.riscv64/smte.4 | 76 ++ static/openbsd/man4/man4.riscv64/smtgpio.4 | 43 + static/openbsd/man4/man4.riscv64/smtiic.4 | 47 + static/openbsd/man4/man4.riscv64/smtpinctrl.4 | 42 + static/openbsd/man4/man4.riscv64/smtpmic.4 | 45 + static/openbsd/man4/man4.riscv64/stfclock.4 | 42 + static/openbsd/man4/man4.riscv64/stfpcie.4 | 45 + static/openbsd/man4/man4.riscv64/stfpciephy.4 | 43 + static/openbsd/man4/man4.riscv64/stfpinctrl.4 | 42 + static/openbsd/man4/man4.riscv64/stfrng.4 | 47 + static/openbsd/man4/man4.sparc64/Makefile | 78 ++ static/openbsd/man4/man4.sparc64/agten.4 | 57 + static/openbsd/man4/man4.sparc64/apio.4 | 63 + static/openbsd/man4/man4.sparc64/asio.4 | 63 + static/openbsd/man4/man4.sparc64/audioce.4 | 125 ++ static/openbsd/man4/man4.sparc64/audiocs.4 | 60 + static/openbsd/man4/man4.sparc64/autoconf.4 | 52 + static/openbsd/man4/man4.sparc64/auxio.4 | 53 + static/openbsd/man4/man4.sparc64/bbc.4 | 49 + static/openbsd/man4/man4.sparc64/be.4 | 72 ++ static/openbsd/man4/man4.sparc64/beeper.4 | 56 + static/openbsd/man4/man4.sparc64/bpp.4 | 47 + static/openbsd/man4/man4.sparc64/bwtwo.4 | 54 + static/openbsd/man4/man4.sparc64/cbus.4 | 60 + static/openbsd/man4/man4.sparc64/central.4 | 55 + static/openbsd/man4/man4.sparc64/cgsix.4 | 154 +++ static/openbsd/man4/man4.sparc64/cgthree.4 | 100 ++ static/openbsd/man4/man4.sparc64/cgtwelve.4 | 62 + static/openbsd/man4/man4.sparc64/clkbrd.4 | 57 + static/openbsd/man4/man4.sparc64/clock.4 | 75 ++ static/openbsd/man4/man4.sparc64/cmp.4 | 46 + static/openbsd/man4/man4.sparc64/comkbd.4 | 58 + static/openbsd/man4/man4.sparc64/comms.4 | 36 + static/openbsd/man4/man4.sparc64/core.4 | 45 + static/openbsd/man4/man4.sparc64/creator.4 | 69 ++ static/openbsd/man4/man4.sparc64/ebus.4 | 103 ++ static/openbsd/man4/man4.sparc64/ecadc.4 | 57 + static/openbsd/man4/man4.sparc64/environ.4 | 47 + static/openbsd/man4/man4.sparc64/esp.4 | 54 + static/openbsd/man4/man4.sparc64/fhc.4 | 77 ++ static/openbsd/man4/man4.sparc64/gfxp.4 | 46 + static/openbsd/man4/man4.sparc64/ifb.4 | 102 ++ static/openbsd/man4/man4.sparc64/intro.4 | 121 ++ static/openbsd/man4/man4.sparc64/le.4 | 101 ++ static/openbsd/man4/man4.sparc64/led.4 | 50 + static/openbsd/man4/man4.sparc64/lom.4 | 64 + static/openbsd/man4/man4.sparc64/machfb.4 | 47 + static/openbsd/man4/man4.sparc64/magma.4 | 114 ++ static/openbsd/man4/man4.sparc64/mem.4 | 87 ++ static/openbsd/man4/man4.sparc64/mgx.4 | 93 ++ static/openbsd/man4/man4.sparc64/pcons.4 | 70 ++ static/openbsd/man4/man4.sparc64/pmc.4 | 47 + static/openbsd/man4/man4.sparc64/power.4 | 62 + static/openbsd/man4/man4.sparc64/ppm.4 | 51 + static/openbsd/man4/man4.sparc64/prtc.4 | 42 + static/openbsd/man4/man4.sparc64/psycho.4 | 55 + static/openbsd/man4/man4.sparc64/pyro.4 | 59 + static/openbsd/man4/man4.sparc64/qe.4 | 60 + static/openbsd/man4/man4.sparc64/qec.4 | 58 + static/openbsd/man4/man4.sparc64/radeonfb.4 | 46 + static/openbsd/man4/man4.sparc64/raptor.4 | 47 + static/openbsd/man4/man4.sparc64/rfx.4 | 106 ++ static/openbsd/man4/man4.sparc64/sab.4 | 80 ++ static/openbsd/man4/man4.sparc64/sbbc.4 | 43 + static/openbsd/man4/man4.sparc64/schizo.4 | 54 + static/openbsd/man4/man4.sparc64/spif.4 | 103 ++ static/openbsd/man4/man4.sparc64/ssm.4 | 43 + static/openbsd/man4/man4.sparc64/tda.4 | 47 + static/openbsd/man4/man4.sparc64/tvtwo.4 | 82 ++ static/openbsd/man4/man4.sparc64/upa.4 | 51 + static/openbsd/man4/man4.sparc64/uperf.4 | 242 ++++ static/openbsd/man4/man4.sparc64/vbus.4 | 55 + static/openbsd/man4/man4.sparc64/vcc.4 | 53 + static/openbsd/man4/man4.sparc64/vcons.4 | 47 + static/openbsd/man4/man4.sparc64/vds.4 | 57 + static/openbsd/man4/man4.sparc64/vdsk.4 | 49 + static/openbsd/man4/man4.sparc64/vigra.4 | 108 ++ static/openbsd/man4/man4.sparc64/vldc.4 | 46 + static/openbsd/man4/man4.sparc64/vnet.4 | 69 ++ static/openbsd/man4/man4.sparc64/vpci.4 | 43 + static/openbsd/man4/man4.sparc64/vrng.4 | 55 + static/openbsd/man4/man4.sparc64/vrtc.4 | 42 + static/openbsd/man4/man4.sparc64/vsw.4 | 58 + static/openbsd/man4/man4.sparc64/xbox.4 | 50 + static/openbsd/man4/man4.sparc64/zs.4 | 183 +++ static/openbsd/man4/man4.sparc64/zx.4 | 95 ++ static/openbsd/man4/maxds.4 | 49 + static/openbsd/man4/maxrtc.4 | 45 + static/openbsd/man4/maxtmp.4 | 51 + static/openbsd/man4/mbg.4 | 104 ++ static/openbsd/man4/mcprtc.4 | 43 + static/openbsd/man4/mcx.4 | 66 ++ static/openbsd/man4/mfi.4 | 103 ++ static/openbsd/man4/mfii.4 | 81 ++ static/openbsd/man4/mfokrtc.4 | 31 + static/openbsd/man4/midi.4 | 272 +++++ static/openbsd/man4/mii.4 | 107 ++ static/openbsd/man4/mlphy.4 | 43 + static/openbsd/man4/mos.4 | 126 ++ static/openbsd/man4/moscom.4 | 52 + static/openbsd/man4/mpath.4 | 53 + static/openbsd/man4/mpe.4 | 81 ++ static/openbsd/man4/mpi.4 | 144 +++ static/openbsd/man4/mpii.4 | 107 ++ static/openbsd/man4/mpip.4 | 103 ++ static/openbsd/man4/mpu.4 | 60 + static/openbsd/man4/mpw.4 | 135 +++ static/openbsd/man4/msk.4 | 178 +++ static/openbsd/man4/msts.4 | 95 ++ static/openbsd/man4/mtd.4 | 70 ++ static/openbsd/man4/mtdphy.4 | 44 + static/openbsd/man4/mtintc.4 | 46 + static/openbsd/man4/mtio.4 | 111 ++ static/openbsd/man4/mtrng.4 | 47 + static/openbsd/man4/mtw.4 | 160 +++ static/openbsd/man4/mtxhci.4 | 49 + static/openbsd/man4/mue.4 | 59 + static/openbsd/man4/multicast.4 | 888 ++++++++++++++ static/openbsd/man4/mvclock.4 | 41 + static/openbsd/man4/mvdog.4 | 44 + static/openbsd/man4/mvgicp.4 | 42 + static/openbsd/man4/mvgpio.4 | 43 + static/openbsd/man4/mvicu.4 | 46 + static/openbsd/man4/mviic.4 | 43 + static/openbsd/man4/mvkpcie.4 | 44 + static/openbsd/man4/mvneta.4 | 48 + static/openbsd/man4/mvpinctrl.4 | 44 + static/openbsd/man4/mvpp.4 | 48 + static/openbsd/man4/mvrng.4 | 47 + static/openbsd/man4/mvrtc.4 | 41 + static/openbsd/man4/mvspi.4 | 41 + static/openbsd/man4/mvsw.4 | 43 + static/openbsd/man4/mvtemp.4 | 48 + static/openbsd/man4/mvuart.4 | 42 + static/openbsd/man4/myx.4 | 81 ++ static/openbsd/man4/ne.4 | 154 +++ static/openbsd/man4/neo.4 | 67 ++ static/openbsd/man4/nep.4 | 84 ++ static/openbsd/man4/netintro.4 | 549 +++++++++ static/openbsd/man4/nfe.4 | 101 ++ static/openbsd/man4/ngbe.4 | 79 ++ static/openbsd/man4/nge.4 | 166 +++ static/openbsd/man4/nhi.4 | 48 + static/openbsd/man4/nmea.4 | 121 ++ static/openbsd/man4/nsclpcsio.4 | 96 ++ static/openbsd/man4/nsgphy.4 | 33 + static/openbsd/man4/nsphy.4 | 50 + static/openbsd/man4/nsphyter.4 | 49 + static/openbsd/man4/null.4 | 61 + static/openbsd/man4/nviic.4 | 51 + static/openbsd/man4/nvme.4 | 56 + static/openbsd/man4/nvt.4 | 50 + static/openbsd/man4/oce.4 | 68 ++ static/openbsd/man4/ociic.4 | 44 + static/openbsd/man4/ohci.4 | 65 ++ static/openbsd/man4/onewire.4 | 75 ++ static/openbsd/man4/oosiop.4 | 111 ++ static/openbsd/man4/openprom.4 | 169 +++ static/openbsd/man4/options.4 | 551 +++++++++ static/openbsd/man4/osiop.4 | 113 ++ static/openbsd/man4/otus.4 | 177 +++ static/openbsd/man4/owctr.4 | 57 + static/openbsd/man4/owid.4 | 54 + static/openbsd/man4/owsbm.4 | 65 ++ static/openbsd/man4/owtemp.4 | 56 + static/openbsd/man4/pair.4 | 110 ++ static/openbsd/man4/pcagpio.4 | 52 + static/openbsd/man4/pcaled.4 | 46 + static/openbsd/man4/pcamux.4 | 46 + static/openbsd/man4/pcdisplay.4 | 64 + static/openbsd/man4/pcfadc.4 | 50 + static/openbsd/man4/pcfiic.4 | 48 + static/openbsd/man4/pcfrtc.4 | 43 + static/openbsd/man4/pchb.4 | 62 + static/openbsd/man4/pchgpio.4 | 47 + static/openbsd/man4/pchtemp.4 | 53 + static/openbsd/man4/pci.4 | 627 ++++++++++ static/openbsd/man4/pcib.4 | 37 + static/openbsd/man4/pciide.4 | 188 +++ static/openbsd/man4/pckbc.4 | 79 ++ static/openbsd/man4/pckbd.4 | 226 ++++ static/openbsd/man4/pcmcia.4 | 159 +++ static/openbsd/man4/pcn.4 | 112 ++ static/openbsd/man4/pcppi.4 | 66 ++ static/openbsd/man4/pcscp.4 | 63 + static/openbsd/man4/pcxrtc.4 | 43 + static/openbsd/man4/pcyrtc.4 | 43 + static/openbsd/man4/pf.4 | 1126 ++++++++++++++++++ static/openbsd/man4/pflog.4 | 111 ++ static/openbsd/man4/pflow.4 | 136 +++ static/openbsd/man4/pfsync.4 | 260 +++++ static/openbsd/man4/pgt.4 | 201 ++++ static/openbsd/man4/piixpm.4 | 72 ++ static/openbsd/man4/pijuice.4 | 53 + static/openbsd/man4/pinctrl.4 | 42 + static/openbsd/man4/pipex.4 | 269 +++++ static/openbsd/man4/plgpio.4 | 47 + static/openbsd/man4/plrtc.4 | 37 + static/openbsd/man4/pluart.4 | 40 + static/openbsd/man4/pms.4 | 74 ++ static/openbsd/man4/ppb.4 | 44 + static/openbsd/man4/ppp.4 | 82 ++ static/openbsd/man4/pppoe.4 | 248 ++++ static/openbsd/man4/pppx.4 | 86 ++ static/openbsd/man4/psci.4 | 34 + static/openbsd/man4/psp.4 | 373 ++++++ static/openbsd/man4/pty.4 | 311 +++++ static/openbsd/man4/puc.4 | 215 ++++ static/openbsd/man4/pvbus.4 | 170 +++ static/openbsd/man4/pvclock.4 | 45 + static/openbsd/man4/pwdog.4 | 58 + static/openbsd/man4/pwmbl.4 | 42 + static/openbsd/man4/pwmfan.4 | 41 + static/openbsd/man4/pwmleds.4 | 45 + static/openbsd/man4/pwmreg.4 | 42 + static/openbsd/man4/qccpu.4 | 50 + static/openbsd/man4/qccpucp.4 | 44 + static/openbsd/man4/qcdpc.4 | 46 + static/openbsd/man4/qcdrm.4 | 48 + static/openbsd/man4/qcdwusb.4 | 44 + static/openbsd/man4/qcgpio.4 | 46 + static/openbsd/man4/qciic.4 | 46 + static/openbsd/man4/qcpdc.4 | 43 + static/openbsd/man4/qcpmic.4 | 53 + static/openbsd/man4/qcpmicgpio.4 | 45 + static/openbsd/man4/qcpon.4 | 44 + static/openbsd/man4/qcpwm.4 | 43 + static/openbsd/man4/qcrng.4 | 51 + static/openbsd/man4/qcrtc.4 | 43 + static/openbsd/man4/qcspmi.4 | 44 + static/openbsd/man4/qcuart.4 | 42 + static/openbsd/man4/qla.4 | 52 + static/openbsd/man4/qle.4 | 50 + static/openbsd/man4/qlw.4 | 57 + static/openbsd/man4/qsphy.4 | 49 + static/openbsd/man4/qwx.4 | 145 +++ static/openbsd/man4/radio.4 | 249 ++++ static/openbsd/man4/ral.4 | 369 ++++++ static/openbsd/man4/random.4 | 92 ++ static/openbsd/man4/rd.4 | 30 + static/openbsd/man4/rdac.4 | 46 + static/openbsd/man4/rdcphy.4 | 33 + static/openbsd/man4/rdomain.4 | 161 +++ static/openbsd/man4/re.4 | 221 ++++ static/openbsd/man4/rge.4 | 75 ++ static/openbsd/man4/rgephy.4 | 34 + static/openbsd/man4/ricohrtc.4 | 42 + static/openbsd/man4/rkanxdp.4 | 52 + static/openbsd/man4/rkclock.4 | 41 + static/openbsd/man4/rkcomphy.4 | 49 + static/openbsd/man4/rkdrm.4 | 54 + static/openbsd/man4/rkdwhdmi.4 | 52 + static/openbsd/man4/rkdwusb.4 | 44 + static/openbsd/man4/rkemmcphy.4 | 41 + static/openbsd/man4/rkgpio.4 | 43 + static/openbsd/man4/rkgrf.4 | 42 + static/openbsd/man4/rkiic.4 | 44 + static/openbsd/man4/rkiis.4 | 48 + static/openbsd/man4/rkiovd.4 | 45 + static/openbsd/man4/rkpcie.4 | 44 + static/openbsd/man4/rkpciephy.4 | 41 + static/openbsd/man4/rkpinctrl.4 | 42 + static/openbsd/man4/rkpmic.4 | 44 + static/openbsd/man4/rkpwm.4 | 42 + static/openbsd/man4/rkrng.4 | 47 + static/openbsd/man4/rkspi.4 | 43 + static/openbsd/man4/rktcphy.4 | 47 + static/openbsd/man4/rktemp.4 | 50 + static/openbsd/man4/rkusbphy.4 | 42 + static/openbsd/man4/rkvop.4 | 52 + static/openbsd/man4/rl.4 | 222 ++++ static/openbsd/man4/rlphy.4 | 50 + static/openbsd/man4/route.4 | 518 +++++++++ static/openbsd/man4/rport.4 | 85 ++ static/openbsd/man4/rsu.4 | 158 +++ static/openbsd/man4/rtsx.4 | 45 + static/openbsd/man4/rtw.4 | 186 +++ static/openbsd/man4/rtwn.4 | 154 +++ static/openbsd/man4/rum.4 | 226 ++++ static/openbsd/man4/run.4 | 243 ++++ static/openbsd/man4/safte.4 | 68 ++ static/openbsd/man4/sbus.4 | 156 +++ static/openbsd/man4/schsio.4 | 95 ++ static/openbsd/man4/scmi.4 | 45 + static/openbsd/man4/scsi.4 | 183 +++ static/openbsd/man4/sd.4 | 225 ++++ static/openbsd/man4/sdhc.4 | 39 + static/openbsd/man4/sdmmc.4 | 66 ++ static/openbsd/man4/sdtemp.4 | 69 ++ static/openbsd/man4/se.4 | 162 +++ static/openbsd/man4/sec.4 | 156 +++ static/openbsd/man4/ses.4 | 84 ++ static/openbsd/man4/sf.4 | 185 +++ static/openbsd/man4/sili.4 | 51 + static/openbsd/man4/simpleamp.4 | 40 + static/openbsd/man4/simpleaudio.4 | 45 + static/openbsd/man4/simplefb.4 | 44 + static/openbsd/man4/simplepanel.4 | 44 + static/openbsd/man4/siop.4 | 140 +++ static/openbsd/man4/sis.4 | 172 +++ static/openbsd/man4/sk.4 | 210 ++++ static/openbsd/man4/sm.4 | 121 ++ static/openbsd/man4/smsc.4 | 66 ++ static/openbsd/man4/sncodec.4 | 42 + static/openbsd/man4/softraid.4 | 273 +++++ static/openbsd/man4/spdmem.4 | 55 + static/openbsd/man4/speaker.4 | 231 ++++ static/openbsd/man4/sppp.4 | 308 +++++ static/openbsd/man4/sqphy.4 | 52 + static/openbsd/man4/ssdfb.4 | 50 + static/openbsd/man4/st.4 | 308 +++++ static/openbsd/man4/ste.4 | 154 +++ static/openbsd/man4/stge.4 | 90 ++ static/openbsd/man4/sti.4 | 275 +++++ static/openbsd/man4/stp.4 | 52 + static/openbsd/man4/sv.4 | 73 ++ static/openbsd/man4/sxiccmu.4 | 35 + static/openbsd/man4/sxidog.4 | 34 + static/openbsd/man4/sximmc.4 | 55 + static/openbsd/man4/sxipio.4 | 44 + static/openbsd/man4/sxipwm.4 | 42 + static/openbsd/man4/sxirintc.4 | 42 + static/openbsd/man4/sxirsb.4 | 48 + static/openbsd/man4/sxirtc.4 | 35 + static/openbsd/man4/sxisid.4 | 44 + static/openbsd/man4/sxisyscon.4 | 42 + static/openbsd/man4/sxitemp.4 | 48 + static/openbsd/man4/sxitwi.4 | 38 + static/openbsd/man4/sym.4 | 47 + static/openbsd/man4/sypwr.4 | 42 + static/openbsd/man4/syscon.4 | 45 + static/openbsd/man4/tascodec.4 | 42 + static/openbsd/man4/tcic.4 | 56 + static/openbsd/man4/tcp.4 | 251 ++++ static/openbsd/man4/tcpci.4 | 46 + static/openbsd/man4/termios.4 | 1539 +++++++++++++++++++++++++ static/openbsd/man4/thmc.4 | 49 + static/openbsd/man4/tht.4 | 73 ++ static/openbsd/man4/ti.4 | 210 ++++ static/openbsd/man4/tipd.4 | 46 + static/openbsd/man4/tipmic.4 | 51 + static/openbsd/man4/titmp.4 | 50 + static/openbsd/man4/tl.4 | 142 +++ static/openbsd/man4/tlphy.4 | 50 + static/openbsd/man4/tpm.4 | 64 + static/openbsd/man4/tpmr.4 | 162 +++ static/openbsd/man4/tqphy.4 | 49 + static/openbsd/man4/trm.4 | 77 ++ static/openbsd/man4/trunk.4 | 147 +++ static/openbsd/man4/tsl.4 | 53 + static/openbsd/man4/tty.4 | 511 ++++++++ static/openbsd/man4/tun.4 | 337 ++++++ static/openbsd/man4/twe.4 | 89 ++ static/openbsd/man4/txp.4 | 122 ++ static/openbsd/man4/txphy.4 | 44 + static/openbsd/man4/uaq.4 | 74 ++ static/openbsd/man4/uark.4 | 61 + static/openbsd/man4/uath.4 | 186 +++ static/openbsd/man4/uaudio.4 | 53 + static/openbsd/man4/ubcmtp.4 | 59 + static/openbsd/man4/uberry.4 | 44 + static/openbsd/man4/ubsa.4 | 82 ++ static/openbsd/man4/ucc.4 | 45 + static/openbsd/man4/uchcom.4 | 53 + static/openbsd/man4/ucom.4 | 96 ++ static/openbsd/man4/ucrcom.4 | 45 + static/openbsd/man4/ucycom.4 | 71 ++ static/openbsd/man4/udav.4 | 109 ++ static/openbsd/man4/udcf.4 | 101 ++ static/openbsd/man4/udl.4 | 79 ++ static/openbsd/man4/udp.4 | 143 +++ static/openbsd/man4/udsbr.4 | 60 + static/openbsd/man4/ufshci.4 | 49 + static/openbsd/man4/uftdi.4 | 64 + static/openbsd/man4/ugen.4 | 294 +++++ static/openbsd/man4/ugl.4 | 55 + static/openbsd/man4/ugold.4 | 80 ++ static/openbsd/man4/uguru.4 | 52 + static/openbsd/man4/uhci.4 | 60 + static/openbsd/man4/uhid.4 | 181 +++ static/openbsd/man4/uhidev.4 | 102 ++ static/openbsd/man4/uhidpp.4 | 48 + static/openbsd/man4/uipaq.4 | 73 ++ static/openbsd/man4/ujoy.4 | 53 + static/openbsd/man4/uk.4 | 76 ++ static/openbsd/man4/ukbd.4 | 270 +++++ static/openbsd/man4/ukphy.4 | 53 + static/openbsd/man4/ukspan.4 | 45 + static/openbsd/man4/ulpt.4 | 86 ++ static/openbsd/man4/umass.4 | 56 + static/openbsd/man4/umb.4 | 95 ++ static/openbsd/man4/umbg.4 | 81 ++ static/openbsd/man4/umcs.4 | 48 + static/openbsd/man4/umct.4 | 73 ++ static/openbsd/man4/umidi.4 | 72 ++ static/openbsd/man4/umodem.4 | 72 ++ static/openbsd/man4/ums.4 | 75 ++ static/openbsd/man4/umsm.4 | 248 ++++ static/openbsd/man4/umstc.4 | 44 + static/openbsd/man4/umt.4 | 47 + static/openbsd/man4/unix.4 | 171 +++ static/openbsd/man4/uoaklux.4 | 60 + static/openbsd/man4/uoakrh.4 | 56 + static/openbsd/man4/uoakv.4 | 61 + static/openbsd/man4/uonerng.4 | 71 ++ static/openbsd/man4/uow.4 | 49 + static/openbsd/man4/upd.4 | 101 ++ static/openbsd/man4/upgt.4 | 193 ++++ static/openbsd/man4/upl.4 | 88 ++ static/openbsd/man4/uplcom.4 | 102 ++ static/openbsd/man4/ural.4 | 199 ++++ static/openbsd/man4/ure.4 | 77 ++ static/openbsd/man4/url.4 | 99 ++ static/openbsd/man4/urlphy.4 | 35 + static/openbsd/man4/urndis.4 | 72 ++ static/openbsd/man4/urng.4 | 59 + static/openbsd/man4/urtw.4 | 132 +++ static/openbsd/man4/urtwn.4 | 204 ++++ static/openbsd/man4/usb.4 | 704 +++++++++++ static/openbsd/man4/uscom.4 | 49 + static/openbsd/man4/uslcom.4 | 84 ++ static/openbsd/man4/uslhcom.4 | 46 + static/openbsd/man4/usps.4 | 46 + static/openbsd/man4/uthum.4 | 63 + static/openbsd/man4/uticom.4 | 78 ++ static/openbsd/man4/utpms.4 | 59 + static/openbsd/man4/utrh.4 | 45 + static/openbsd/man4/uts.4 | 72 ++ static/openbsd/man4/utvfu.4 | 58 + static/openbsd/man4/utwitch.4 | 55 + static/openbsd/man4/uvideo.4 | 152 +++ static/openbsd/man4/uvisor.4 | 63 + static/openbsd/man4/uvscom.4 | 63 + static/openbsd/man4/uwacom.4 | 70 ++ static/openbsd/man4/uxrcom.4 | 45 + static/openbsd/man4/veb.4 | 180 +++ static/openbsd/man4/vether.4 | 60 + static/openbsd/man4/vga.4 | 134 +++ static/openbsd/man4/vgafb.4 | 54 + static/openbsd/man4/vge.4 | 152 +++ static/openbsd/man4/viapm.4 | 103 ++ static/openbsd/man4/viasio.4 | 77 ++ static/openbsd/man4/vic.4 | 106 ++ static/openbsd/man4/video.4 | 510 ++++++++ static/openbsd/man4/vio.4 | 62 + static/openbsd/man4/vioblk.4 | 49 + static/openbsd/man4/viocon.4 | 59 + static/openbsd/man4/viogpu.4 | 49 + static/openbsd/man4/viomb.4 | 73 ++ static/openbsd/man4/viornd.4 | 60 + static/openbsd/man4/vioscsi.4 | 46 + static/openbsd/man4/virtio.4 | 86 ++ static/openbsd/man4/vlan.4 | 213 ++++ static/openbsd/man4/vmmci.4 | 57 + static/openbsd/man4/vmt.4 | 66 ++ static/openbsd/man4/vmwpvs.4 | 52 + static/openbsd/man4/vmx.4 | 116 ++ static/openbsd/man4/vnd.4 | 165 +++ static/openbsd/man4/vr.4 | 187 +++ static/openbsd/man4/vscsi.4 | 126 ++ static/openbsd/man4/vte.4 | 82 ++ static/openbsd/man4/vxlan.4 | 245 ++++ static/openbsd/man4/watchdog.4 | 96 ++ static/openbsd/man4/wb.4 | 157 +++ static/openbsd/man4/wbenv.4 | 53 + static/openbsd/man4/wbng.4 | 49 + static/openbsd/man4/wbsd.4 | 53 + static/openbsd/man4/wbsio.4 | 48 + static/openbsd/man4/wd.4 | 75 ++ static/openbsd/man4/wdc.4 | 88 ++ static/openbsd/man4/we.4 | 117 ++ static/openbsd/man4/wg.4 | 226 ++++ static/openbsd/man4/wi.4 | 393 +++++++ static/openbsd/man4/witness.4 | 95 ++ static/openbsd/man4/wpi.4 | 168 +++ static/openbsd/man4/wscons.4 | 251 ++++ static/openbsd/man4/wsdisplay.4 | 713 ++++++++++++ static/openbsd/man4/wskbd.4 | 274 +++++ static/openbsd/man4/wsmouse.4 | 233 ++++ static/openbsd/man4/wsmux.4 | 146 +++ static/openbsd/man4/xbf.4 | 57 + static/openbsd/man4/xe.4 | 62 + static/openbsd/man4/xen.4 | 77 ++ static/openbsd/man4/xf86.4 | 119 ++ static/openbsd/man4/xge.4 | 97 ++ static/openbsd/man4/xhci.4 | 52 + static/openbsd/man4/xl.4 | 209 ++++ static/openbsd/man4/xmphy.4 | 45 + static/openbsd/man4/xnf.4 | 52 + static/openbsd/man4/xspd.4 | 50 + static/openbsd/man4/yds.4 | 73 ++ static/openbsd/man4/ytphy.4 | 44 + static/openbsd/man4/zero.4 | 44 + static/openbsd/man4/zyd.4 | 217 ++++ 1130 files changed, 105616 insertions(+) create mode 100644 static/openbsd/man4/Makefile create mode 100644 static/openbsd/man4/aac.4 create mode 100644 static/openbsd/man4/abcrtc.4 create mode 100644 static/openbsd/man4/abl.4 create mode 100644 static/openbsd/man4/ac97.4 create mode 100644 static/openbsd/man4/acphy.4 create mode 100644 static/openbsd/man4/acpi.4 create mode 100644 static/openbsd/man4/acpiac.4 create mode 100644 static/openbsd/man4/acpials.4 create mode 100644 static/openbsd/man4/acpiasus.4 create mode 100644 static/openbsd/man4/acpibat.4 create mode 100644 static/openbsd/man4/acpibtn.4 create mode 100644 static/openbsd/man4/acpicbkbd.4 create mode 100644 static/openbsd/man4/acpicmos.4 create mode 100644 static/openbsd/man4/acpicpu.4 create mode 100644 static/openbsd/man4/acpidock.4 create mode 100644 static/openbsd/man4/acpiec.4 create mode 100644 static/openbsd/man4/acpige.4 create mode 100644 static/openbsd/man4/acpihid.4 create mode 100644 static/openbsd/man4/acpihpet.4 create mode 100644 static/openbsd/man4/acpihve.4 create mode 100644 static/openbsd/man4/acpimadt.4 create mode 100644 static/openbsd/man4/acpimcfg.4 create mode 100644 static/openbsd/man4/acpipci.4 create mode 100644 static/openbsd/man4/acpiprt.4 create mode 100644 static/openbsd/man4/acpipwrres.4 create mode 100644 static/openbsd/man4/acpisbs.4 create mode 100644 static/openbsd/man4/acpisony.4 create mode 100644 static/openbsd/man4/acpisurface.4 create mode 100644 static/openbsd/man4/acpithinkpad.4 create mode 100644 static/openbsd/man4/acpitimer.4 create mode 100644 static/openbsd/man4/acpitoshiba.4 create mode 100644 static/openbsd/man4/acpitz.4 create mode 100644 static/openbsd/man4/acpivideo.4 create mode 100644 static/openbsd/man4/acpivout.4 create mode 100644 static/openbsd/man4/acpiwmi.4 create mode 100644 static/openbsd/man4/acrtc.4 create mode 100644 static/openbsd/man4/acx.4 create mode 100644 static/openbsd/man4/adc.4 create mode 100644 static/openbsd/man4/addcom.4 create mode 100644 static/openbsd/man4/adl.4 create mode 100644 static/openbsd/man4/admcts.4 create mode 100644 static/openbsd/man4/admlc.4 create mode 100644 static/openbsd/man4/admtemp.4 create mode 100644 static/openbsd/man4/admtm.4 create mode 100644 static/openbsd/man4/admtmp.4 create mode 100644 static/openbsd/man4/admtt.4 create mode 100644 static/openbsd/man4/adt.4 create mode 100644 static/openbsd/man4/adtfsm.4 create mode 100644 static/openbsd/man4/adv.4 create mode 100644 static/openbsd/man4/age.4 create mode 100644 static/openbsd/man4/aggr.4 create mode 100644 static/openbsd/man4/agp.4 create mode 100644 static/openbsd/man4/ahc.4 create mode 100644 static/openbsd/man4/ahci.4 create mode 100644 static/openbsd/man4/ahd.4 create mode 100644 static/openbsd/man4/aibs.4 create mode 100644 static/openbsd/man4/aic.4 create mode 100644 static/openbsd/man4/akbd.4 create mode 100644 static/openbsd/man4/alc.4 create mode 100644 static/openbsd/man4/ale.4 create mode 100644 static/openbsd/man4/alipm.4 create mode 100644 static/openbsd/man4/amas.4 create mode 100644 static/openbsd/man4/amdgpio.4 create mode 100644 static/openbsd/man4/amdiic.4 create mode 100644 static/openbsd/man4/amdpm.4 create mode 100644 static/openbsd/man4/amdpmc.4 create mode 100644 static/openbsd/man4/ami.4 create mode 100644 static/openbsd/man4/amlclock.4 create mode 100644 static/openbsd/man4/amldwusb.4 create mode 100644 static/openbsd/man4/amliic.4 create mode 100644 static/openbsd/man4/amlmmc.4 create mode 100644 static/openbsd/man4/amlpciephy.4 create mode 100644 static/openbsd/man4/amlpinctrl.4 create mode 100644 static/openbsd/man4/amlpwm.4 create mode 100644 static/openbsd/man4/amlreset.4 create mode 100644 static/openbsd/man4/amlrng.4 create mode 100644 static/openbsd/man4/amlsm.4 create mode 100644 static/openbsd/man4/amltemp.4 create mode 100644 static/openbsd/man4/amluart.4 create mode 100644 static/openbsd/man4/amlusbphy.4 create mode 100644 static/openbsd/man4/amphy.4 create mode 100644 static/openbsd/man4/ams.4 create mode 100644 static/openbsd/man4/an.4 create mode 100644 static/openbsd/man4/andl.4 create mode 100644 static/openbsd/man4/aplgpio.4 create mode 100644 static/openbsd/man4/aps.4 create mode 100644 static/openbsd/man4/aq.4 create mode 100644 static/openbsd/man4/arc.4 create mode 100644 static/openbsd/man4/arcofi.4 create mode 100644 static/openbsd/man4/asbtm.4 create mode 100644 static/openbsd/man4/asmc.4 create mode 100644 static/openbsd/man4/ast.4 create mode 100644 static/openbsd/man4/atapiscsi.4 create mode 100644 static/openbsd/man4/ath.4 create mode 100644 static/openbsd/man4/athn.4 create mode 100644 static/openbsd/man4/atphy.4 create mode 100644 static/openbsd/man4/atu.4 create mode 100644 static/openbsd/man4/atw.4 create mode 100644 static/openbsd/man4/auacer.4 create mode 100644 static/openbsd/man4/audio.4 create mode 100644 static/openbsd/man4/aue.4 create mode 100644 static/openbsd/man4/auglx.4 create mode 100644 static/openbsd/man4/auich.4 create mode 100644 static/openbsd/man4/auixp.4 create mode 100644 static/openbsd/man4/autri.4 create mode 100644 static/openbsd/man4/auvia.4 create mode 100644 static/openbsd/man4/axe.4 create mode 100644 static/openbsd/man4/axen.4 create mode 100644 static/openbsd/man4/axppmic.4 create mode 100644 static/openbsd/man4/azalia.4 create mode 100644 static/openbsd/man4/bce.4 create mode 100644 static/openbsd/man4/bcmaux.4 create mode 100644 static/openbsd/man4/bcmbsc.4 create mode 100644 static/openbsd/man4/bcmclock.4 create mode 100644 static/openbsd/man4/bcmdmac.4 create mode 100644 static/openbsd/man4/bcmdog.4 create mode 100644 static/openbsd/man4/bcmgpio.4 create mode 100644 static/openbsd/man4/bcmirng.4 create mode 100644 static/openbsd/man4/bcmmbox.4 create mode 100644 static/openbsd/man4/bcmpcie.4 create mode 100644 static/openbsd/man4/bcmrng.4 create mode 100644 static/openbsd/man4/bcmsdhost.4 create mode 100644 static/openbsd/man4/bcmstbgpio.4 create mode 100644 static/openbsd/man4/bcmstbintc.4 create mode 100644 static/openbsd/man4/bcmstbpinctrl.4 create mode 100644 static/openbsd/man4/bcmstbrescal.4 create mode 100644 static/openbsd/man4/bcmstbreset.4 create mode 100644 static/openbsd/man4/bcmtemp.4 create mode 100644 static/openbsd/man4/bcmtmon.4 create mode 100644 static/openbsd/man4/bdpmic.4 create mode 100644 static/openbsd/man4/berkwdt.4 create mode 100644 static/openbsd/man4/bge.4 create mode 100644 static/openbsd/man4/bgw.4 create mode 100644 static/openbsd/man4/bio.4 create mode 100644 static/openbsd/man4/bktr.4 create mode 100644 static/openbsd/man4/bmtphy.4 create mode 100644 static/openbsd/man4/bnx.4 create mode 100644 static/openbsd/man4/bnxt.4 create mode 100644 static/openbsd/man4/boca.4 create mode 100644 static/openbsd/man4/bpe.4 create mode 100644 static/openbsd/man4/bpf.4 create mode 100644 static/openbsd/man4/brgphy.4 create mode 100644 static/openbsd/man4/bridge.4 create mode 100644 static/openbsd/man4/brswphy.4 create mode 100644 static/openbsd/man4/bse.4 create mode 100644 static/openbsd/man4/bwfm.4 create mode 100644 static/openbsd/man4/bwi.4 create mode 100644 static/openbsd/man4/bytgpio.4 create mode 100644 static/openbsd/man4/cac.4 create mode 100644 static/openbsd/man4/cad.4 create mode 100644 static/openbsd/man4/cardbus.4 create mode 100644 static/openbsd/man4/carp.4 create mode 100644 static/openbsd/man4/cas.4 create mode 100644 static/openbsd/man4/ccp.4 create mode 100644 static/openbsd/man4/ccpmic.4 create mode 100644 static/openbsd/man4/cd.4 create mode 100644 static/openbsd/man4/cdce.4 create mode 100644 static/openbsd/man4/cdpcie.4 create mode 100644 static/openbsd/man4/cdsdhc.4 create mode 100644 static/openbsd/man4/cduart.4 create mode 100644 static/openbsd/man4/cfxga.4 create mode 100644 static/openbsd/man4/ch.4 create mode 100644 static/openbsd/man4/chvgpio.4 create mode 100644 static/openbsd/man4/ciphy.4 create mode 100644 static/openbsd/man4/ciss.4 create mode 100644 static/openbsd/man4/clcs.4 create mode 100644 static/openbsd/man4/clct.4 create mode 100644 static/openbsd/man4/cmpci.4 create mode 100644 static/openbsd/man4/com.4 create mode 100644 static/openbsd/man4/cue.4 create mode 100644 static/openbsd/man4/cwfg.4 create mode 100644 static/openbsd/man4/cy.4 create mode 100644 static/openbsd/man4/cz.4 create mode 100644 static/openbsd/man4/dapmic.4 create mode 100644 static/openbsd/man4/dc.4 create mode 100644 static/openbsd/man4/dcphy.4 create mode 100644 static/openbsd/man4/ddb.4 create mode 100644 static/openbsd/man4/de.4 create mode 100644 static/openbsd/man4/diskmap.4 create mode 100644 static/openbsd/man4/divert.4 create mode 100644 static/openbsd/man4/drm.4 create mode 100644 static/openbsd/man4/dsxrtc.4 create mode 100644 static/openbsd/man4/dt.4 create mode 100644 static/openbsd/man4/dwctwo.4 create mode 100644 static/openbsd/man4/dwdog.4 create mode 100644 static/openbsd/man4/dwge.4 create mode 100644 static/openbsd/man4/dwgpio.4 create mode 100644 static/openbsd/man4/dwiic.4 create mode 100644 static/openbsd/man4/dwmmc.4 create mode 100644 static/openbsd/man4/dwmshc.4 create mode 100644 static/openbsd/man4/dwpcie.4 create mode 100644 static/openbsd/man4/dwqe.4 create mode 100644 static/openbsd/man4/dwxe.4 create mode 100644 static/openbsd/man4/eap.4 create mode 100644 static/openbsd/man4/ec.4 create mode 100644 static/openbsd/man4/eephy.4 create mode 100644 static/openbsd/man4/ef.4 create mode 100644 static/openbsd/man4/efi.4 create mode 100644 static/openbsd/man4/eg.4 create mode 100644 static/openbsd/man4/ehci.4 create mode 100644 static/openbsd/man4/eisa.4 create mode 100644 static/openbsd/man4/el.4 create mode 100644 static/openbsd/man4/em.4 create mode 100644 static/openbsd/man4/emc.4 create mode 100644 static/openbsd/man4/emu.4 create mode 100644 static/openbsd/man4/enc.4 create mode 100644 static/openbsd/man4/endrun.4 create mode 100644 static/openbsd/man4/envy.4 create mode 100644 static/openbsd/man4/eoip.4 create mode 100644 static/openbsd/man4/ep.4 create mode 100644 static/openbsd/man4/epic.4 create mode 100644 static/openbsd/man4/erspan.4 create mode 100644 static/openbsd/man4/esa.4 create mode 100644 static/openbsd/man4/escodec.4 create mode 100644 static/openbsd/man4/eso.4 create mode 100644 static/openbsd/man4/ess.4 create mode 100644 static/openbsd/man4/et.4 create mode 100644 static/openbsd/man4/etherip.4 create mode 100644 static/openbsd/man4/etphy.4 create mode 100644 static/openbsd/man4/ex.4 create mode 100644 static/openbsd/man4/exphy.4 create mode 100644 static/openbsd/man4/exrtc.4 create mode 100644 static/openbsd/man4/fanpwr.4 create mode 100644 static/openbsd/man4/fd.4 create mode 100644 static/openbsd/man4/fdc.4 create mode 100644 static/openbsd/man4/fec.4 create mode 100644 static/openbsd/man4/fido.4 create mode 100644 static/openbsd/man4/fins.4 create mode 100644 static/openbsd/man4/fintek.4 create mode 100644 static/openbsd/man4/fms.4 create mode 100644 static/openbsd/man4/frame.4 create mode 100644 static/openbsd/man4/fusbtc.4 create mode 100644 static/openbsd/man4/fuse.4 create mode 100644 static/openbsd/man4/fxp.4 create mode 100644 static/openbsd/man4/gcu.4 create mode 100644 static/openbsd/man4/gdt.4 create mode 100644 static/openbsd/man4/gem.4 create mode 100644 static/openbsd/man4/gentbi.4 create mode 100644 static/openbsd/man4/gfrtc.4 create mode 100644 static/openbsd/man4/gif.4 create mode 100644 static/openbsd/man4/glenv.4 create mode 100644 static/openbsd/man4/glkgpio.4 create mode 100644 static/openbsd/man4/gpio.4 create mode 100644 static/openbsd/man4/gpiocharger.4 create mode 100644 static/openbsd/man4/gpiodcf.4 create mode 100644 static/openbsd/man4/gpioiic.4 create mode 100644 static/openbsd/man4/gpiokeys.4 create mode 100644 static/openbsd/man4/gpioleds.4 create mode 100644 static/openbsd/man4/gpioow.4 create mode 100644 static/openbsd/man4/graphaudio.4 create mode 100644 static/openbsd/man4/gre.4 create mode 100644 static/openbsd/man4/gscsio.4 create mode 100644 static/openbsd/man4/hds.4 create mode 100644 static/openbsd/man4/hiclock.4 create mode 100644 static/openbsd/man4/hidwusb.4 create mode 100644 static/openbsd/man4/hil.4 create mode 100644 static/openbsd/man4/hilid.4 create mode 100644 static/openbsd/man4/hilkbd.4 create mode 100644 static/openbsd/man4/hilms.4 create mode 100644 static/openbsd/man4/hireset.4 create mode 100644 static/openbsd/man4/hitemp.4 create mode 100644 static/openbsd/man4/hme.4 create mode 100644 static/openbsd/man4/hotplug.4 create mode 100644 static/openbsd/man4/hsq.4 create mode 100644 static/openbsd/man4/hvn.4 create mode 100644 static/openbsd/man4/hvs.4 create mode 100644 static/openbsd/man4/hyperv.4 create mode 100644 static/openbsd/man4/iasuskbd.4 create mode 100644 static/openbsd/man4/iatp.4 create mode 100644 static/openbsd/man4/iavf.4 create mode 100644 static/openbsd/man4/icc.4 create mode 100644 static/openbsd/man4/ice.4 create mode 100644 static/openbsd/man4/ichiic.4 create mode 100644 static/openbsd/man4/ichwdt.4 create mode 100644 static/openbsd/man4/icmp.4 create mode 100644 static/openbsd/man4/icmp6.4 create mode 100644 static/openbsd/man4/icsphy.4 create mode 100644 static/openbsd/man4/ietp.4 create mode 100644 static/openbsd/man4/ifmedia.4 create mode 100644 static/openbsd/man4/igc.4 create mode 100644 static/openbsd/man4/iha.4 create mode 100644 static/openbsd/man4/ihidev.4 create mode 100644 static/openbsd/man4/iic.4 create mode 100644 static/openbsd/man4/iicmux.4 create mode 100644 static/openbsd/man4/ikbd.4 create mode 100644 static/openbsd/man4/ims.4 create mode 100644 static/openbsd/man4/imt.4 create mode 100644 static/openbsd/man4/imxanatop.4 create mode 100644 static/openbsd/man4/imxdog.4 create mode 100644 static/openbsd/man4/imxesdhc.4 create mode 100644 static/openbsd/man4/imxgpc.4 create mode 100644 static/openbsd/man4/imxgpio.4 create mode 100644 static/openbsd/man4/imxiic.4 create mode 100644 static/openbsd/man4/imxpciephy.4 create mode 100644 static/openbsd/man4/imxpwm.4 create mode 100644 static/openbsd/man4/imxrtc.4 create mode 100644 static/openbsd/man4/imxspi.4 create mode 100644 static/openbsd/man4/imxsrc.4 create mode 100644 static/openbsd/man4/imxtmu.4 create mode 100644 static/openbsd/man4/imxuart.4 create mode 100644 static/openbsd/man4/inet.4 create mode 100644 static/openbsd/man4/inet6.4 create mode 100644 static/openbsd/man4/inphy.4 create mode 100644 static/openbsd/man4/intelpmc.4 create mode 100644 static/openbsd/man4/inthid.4 create mode 100644 static/openbsd/man4/iophy.4 create mode 100644 static/openbsd/man4/iosf.4 create mode 100644 static/openbsd/man4/ip.4 create mode 100644 static/openbsd/man4/ip6.4 create mode 100644 static/openbsd/man4/ipcomp.4 create mode 100644 static/openbsd/man4/ipgphy.4 create mode 100644 static/openbsd/man4/ipmi.4 create mode 100644 static/openbsd/man4/ips.4 create mode 100644 static/openbsd/man4/ipsec.4 create mode 100644 static/openbsd/man4/ipw.4 create mode 100644 static/openbsd/man4/isa.4 create mode 100644 static/openbsd/man4/isagpio.4 create mode 100644 static/openbsd/man4/isapnp.4 create mode 100644 static/openbsd/man4/islrtc.4 create mode 100644 static/openbsd/man4/ispi.4 create mode 100644 static/openbsd/man4/it.4 create mode 100644 static/openbsd/man4/itherm.4 create mode 100644 static/openbsd/man4/iwi.4 create mode 100644 static/openbsd/man4/iwm.4 create mode 100644 static/openbsd/man4/iwn.4 create mode 100644 static/openbsd/man4/iwx.4 create mode 100644 static/openbsd/man4/ix.4 create mode 100644 static/openbsd/man4/ixgb.4 create mode 100644 static/openbsd/man4/ixl.4 create mode 100644 static/openbsd/man4/ixv.4 create mode 100644 static/openbsd/man4/jmb.4 create mode 100644 static/openbsd/man4/jme.4 create mode 100644 static/openbsd/man4/jmphy.4 create mode 100644 static/openbsd/man4/kate.4 create mode 100644 static/openbsd/man4/kcov.4 create mode 100644 static/openbsd/man4/km.4 create mode 100644 static/openbsd/man4/ksmn.4 create mode 100644 static/openbsd/man4/kstat.4 create mode 100644 static/openbsd/man4/ksyms.4 create mode 100644 static/openbsd/man4/kubsan.4 create mode 100644 static/openbsd/man4/kue.4 create mode 100644 static/openbsd/man4/lc.4 create mode 100644 static/openbsd/man4/lge.4 create mode 100644 static/openbsd/man4/lii.4 create mode 100644 static/openbsd/man4/lisa.4 create mode 100644 static/openbsd/man4/lm.4 create mode 100644 static/openbsd/man4/lmenv.4 create mode 100644 static/openbsd/man4/lmn.4 create mode 100644 static/openbsd/man4/lmtemp.4 create mode 100644 static/openbsd/man4/lo.4 create mode 100644 static/openbsd/man4/lpt.4 create mode 100644 static/openbsd/man4/luphy.4 create mode 100644 static/openbsd/man4/lxtphy.4 create mode 100644 static/openbsd/man4/maestro.4 create mode 100644 static/openbsd/man4/mainbus.4 create mode 100644 static/openbsd/man4/malo.4 create mode 100644 static/openbsd/man4/man4.alpha/Makefile create mode 100644 static/openbsd/man4/man4.alpha/apecs.4 create mode 100644 static/openbsd/man4/man4.alpha/asc.4 create mode 100644 static/openbsd/man4/man4.alpha/autoconf.4 create mode 100644 static/openbsd/man4/man4.alpha/bba.4 create mode 100644 static/openbsd/man4/man4.alpha/cia.4 create mode 100644 static/openbsd/man4/man4.alpha/intro.4 create mode 100644 static/openbsd/man4/man4.alpha/ioasic.4 create mode 100644 static/openbsd/man4/man4.alpha/irongate.4 create mode 100644 static/openbsd/man4/man4.alpha/lca.4 create mode 100644 static/openbsd/man4/man4.alpha/le.4 create mode 100644 static/openbsd/man4/man4.alpha/mcbus.4 create mode 100644 static/openbsd/man4/man4.alpha/mcpcia.4 create mode 100644 static/openbsd/man4/man4.alpha/mem.4 create mode 100644 static/openbsd/man4/man4.alpha/tcasic.4 create mode 100644 static/openbsd/man4/man4.alpha/tga.4 create mode 100644 static/openbsd/man4/man4.alpha/tsc.4 create mode 100644 static/openbsd/man4/man4.alpha/tsciic.4 create mode 100644 static/openbsd/man4/man4.alpha/zs.4 create mode 100644 static/openbsd/man4/man4.amd64/Makefile create mode 100644 static/openbsd/man4/man4.amd64/amdpcib.4 create mode 100644 static/openbsd/man4/man4.amd64/apm.4 create mode 100644 static/openbsd/man4/man4.amd64/autoconf.4 create mode 100644 static/openbsd/man4/man4.amd64/bios.4 create mode 100644 static/openbsd/man4/man4.amd64/cpu.4 create mode 100644 static/openbsd/man4/man4.amd64/efifb.4 create mode 100644 static/openbsd/man4/man4.amd64/intro.4 create mode 100644 static/openbsd/man4/man4.amd64/ioapic.4 create mode 100644 static/openbsd/man4/man4.amd64/mem.4 create mode 100644 static/openbsd/man4/man4.amd64/mpbios.4 create mode 100644 static/openbsd/man4/man4.amd64/mtrr.4 create mode 100644 static/openbsd/man4/man4.amd64/nvram.4 create mode 100644 static/openbsd/man4/man4.amd64/pctr.4 create mode 100644 static/openbsd/man4/man4.amd64/skgpio.4 create mode 100644 static/openbsd/man4/man4.amd64/tcpcib.4 create mode 100644 static/openbsd/man4/man4.amd64/vmm.4 create mode 100644 static/openbsd/man4/man4.arm64/Makefile create mode 100644 static/openbsd/man4/man4.arm64/agintc.4 create mode 100644 static/openbsd/man4/man4.arm64/agtimer.4 create mode 100644 static/openbsd/man4/man4.arm64/ampchwm.4 create mode 100644 static/openbsd/man4/man4.arm64/ampintc.4 create mode 100644 static/openbsd/man4/man4.arm64/aplaudio.4 create mode 100644 static/openbsd/man4/man4.arm64/aplcpu.4 create mode 100644 static/openbsd/man4/man4.arm64/apldart.4 create mode 100644 static/openbsd/man4/man4.arm64/apldcp.4 create mode 100644 static/openbsd/man4/man4.arm64/apldma.4 create mode 100644 static/openbsd/man4/man4.arm64/apldog.4 create mode 100644 static/openbsd/man4/man4.arm64/apldrm.4 create mode 100644 static/openbsd/man4/man4.arm64/aplefuse.4 create mode 100644 static/openbsd/man4/man4.arm64/aplhidev.4 create mode 100644 static/openbsd/man4/man4.arm64/apliic.4 create mode 100644 static/openbsd/man4/man4.arm64/aplintc.4 create mode 100644 static/openbsd/man4/man4.arm64/aplmbox.4 create mode 100644 static/openbsd/man4/man4.arm64/aplmca.4 create mode 100644 static/openbsd/man4/man4.arm64/aplnco.4 create mode 100644 static/openbsd/man4/man4.arm64/aplns.4 create mode 100644 static/openbsd/man4/man4.arm64/aplpcie.4 create mode 100644 static/openbsd/man4/man4.arm64/aplpinctrl.4 create mode 100644 static/openbsd/man4/man4.arm64/aplpmgr.4 create mode 100644 static/openbsd/man4/man4.arm64/aplpmu.4 create mode 100644 static/openbsd/man4/man4.arm64/aplpwm.4 create mode 100644 static/openbsd/man4/man4.arm64/aplsart.4 create mode 100644 static/openbsd/man4/man4.arm64/aplsmc.4 create mode 100644 static/openbsd/man4/man4.arm64/aplspi.4 create mode 100644 static/openbsd/man4/man4.arm64/aplspmi.4 create mode 100644 static/openbsd/man4/man4.arm64/apm.4 create mode 100644 static/openbsd/man4/man4.arm64/intro.4 create mode 100644 static/openbsd/man4/man4.arm64/rpiclock.4 create mode 100644 static/openbsd/man4/man4.arm64/rpipwm.4 create mode 100644 static/openbsd/man4/man4.arm64/rpirtc.4 create mode 100644 static/openbsd/man4/man4.arm64/rpone.4 create mode 100644 static/openbsd/man4/man4.arm64/smbios.4 create mode 100644 static/openbsd/man4/man4.armv7/Makefile create mode 100644 static/openbsd/man4/man4.armv7/agtimer.4 create mode 100644 static/openbsd/man4/man4.armv7/amdisplay.4 create mode 100644 static/openbsd/man4/man4.armv7/ampintc.4 create mode 100644 static/openbsd/man4/man4.armv7/amptimer.4 create mode 100644 static/openbsd/man4/man4.armv7/armliicc.4 create mode 100644 static/openbsd/man4/man4.armv7/cortex.4 create mode 100644 static/openbsd/man4/man4.armv7/cpsw.4 create mode 100644 static/openbsd/man4/man4.armv7/dmtimer.4 create mode 100644 static/openbsd/man4/man4.armv7/edma.4 create mode 100644 static/openbsd/man4/man4.armv7/gptimer.4 create mode 100644 static/openbsd/man4/man4.armv7/imxtemp.4 create mode 100644 static/openbsd/man4/man4.armv7/intc.4 create mode 100644 static/openbsd/man4/man4.armv7/intro.4 create mode 100644 static/openbsd/man4/man4.armv7/mvodog.4 create mode 100644 static/openbsd/man4/man4.armv7/mvortc.4 create mode 100644 static/openbsd/man4/man4.armv7/omap.4 create mode 100644 static/openbsd/man4/man4.armv7/omclock.4 create mode 100644 static/openbsd/man4/man4.armv7/omcm.4 create mode 100644 static/openbsd/man4/man4.armv7/omdog.4 create mode 100644 static/openbsd/man4/man4.armv7/omgpio.4 create mode 100644 static/openbsd/man4/man4.armv7/ommmc.4 create mode 100644 static/openbsd/man4/man4.armv7/omrng.4 create mode 100644 static/openbsd/man4/man4.armv7/omsysc.4 create mode 100644 static/openbsd/man4/man4.armv7/omwugen.4 create mode 100644 static/openbsd/man4/man4.armv7/prcm.4 create mode 100644 static/openbsd/man4/man4.armv7/sxie.4 create mode 100644 static/openbsd/man4/man4.armv7/sxiintc.4 create mode 100644 static/openbsd/man4/man4.armv7/sxitimer.4 create mode 100644 static/openbsd/man4/man4.armv7/sxits.4 create mode 100644 static/openbsd/man4/man4.armv7/sysreg.4 create mode 100644 static/openbsd/man4/man4.armv7/zqclock.4 create mode 100644 static/openbsd/man4/man4.armv7/zqreset.4 create mode 100644 static/openbsd/man4/man4.hppa/Makefile create mode 100644 static/openbsd/man4/man4.hppa/asp.4 create mode 100644 static/openbsd/man4/man4.hppa/astro.4 create mode 100644 static/openbsd/man4/man4.hppa/cpu.4 create mode 100644 static/openbsd/man4/man4.hppa/dino.4 create mode 100644 static/openbsd/man4/man4.hppa/elroy.4 create mode 100644 static/openbsd/man4/man4.hppa/gecko.4 create mode 100644 static/openbsd/man4/man4.hppa/gsc.4 create mode 100644 static/openbsd/man4/man4.hppa/gsckbc.4 create mode 100644 static/openbsd/man4/man4.hppa/harmony.4 create mode 100644 static/openbsd/man4/man4.hppa/ie.4 create mode 100644 static/openbsd/man4/man4.hppa/intro.4 create mode 100644 static/openbsd/man4/man4.hppa/io.4 create mode 100644 static/openbsd/man4/man4.hppa/lasi.4 create mode 100644 static/openbsd/man4/man4.hppa/lcd.4 create mode 100644 static/openbsd/man4/man4.hppa/mem.4 create mode 100644 static/openbsd/man4/man4.hppa/mongoose.4 create mode 100644 static/openbsd/man4/man4.hppa/pdc.4 create mode 100644 static/openbsd/man4/man4.hppa/phantomas.4 create mode 100644 static/openbsd/man4/man4.hppa/power.4 create mode 100644 static/openbsd/man4/man4.hppa/runway.4 create mode 100644 static/openbsd/man4/man4.hppa/ssio.4 create mode 100644 static/openbsd/man4/man4.hppa/uturn.4 create mode 100644 static/openbsd/man4/man4.hppa/wax.4 create mode 100644 static/openbsd/man4/man4.i386/Makefile create mode 100644 static/openbsd/man4/man4.i386/amdmsr.4 create mode 100644 static/openbsd/man4/man4.i386/amdpcib.4 create mode 100644 static/openbsd/man4/man4.i386/apm.4 create mode 100644 static/openbsd/man4/man4.i386/autoconf.4 create mode 100644 static/openbsd/man4/man4.i386/bios.4 create mode 100644 static/openbsd/man4/man4.i386/cpu.4 create mode 100644 static/openbsd/man4/man4.i386/esm.4 create mode 100644 static/openbsd/man4/man4.i386/geodesc.4 create mode 100644 static/openbsd/man4/man4.i386/glxpcib.4 create mode 100644 static/openbsd/man4/man4.i386/glxsb.4 create mode 100644 static/openbsd/man4/man4.i386/gscpcib.4 create mode 100644 static/openbsd/man4/man4.i386/gscpm.4 create mode 100644 static/openbsd/man4/man4.i386/gus.4 create mode 100644 static/openbsd/man4/man4.i386/ichpcib.4 create mode 100644 static/openbsd/man4/man4.i386/ie.4 create mode 100644 static/openbsd/man4/man4.i386/intro.4 create mode 100644 static/openbsd/man4/man4.i386/ioapic.4 create mode 100644 static/openbsd/man4/man4.i386/joy.4 create mode 100644 static/openbsd/man4/man4.i386/le.4 create mode 100644 static/openbsd/man4/man4.i386/lms.4 create mode 100644 static/openbsd/man4/man4.i386/mem.4 create mode 100644 static/openbsd/man4/man4.i386/mms.4 create mode 100644 static/openbsd/man4/man4.i386/mpbios.4 create mode 100644 static/openbsd/man4/man4.i386/mtrr.4 create mode 100644 static/openbsd/man4/man4.i386/npx.4 create mode 100644 static/openbsd/man4/man4.i386/nvram.4 create mode 100644 static/openbsd/man4/man4.i386/pas.4 create mode 100644 static/openbsd/man4/man4.i386/pcibios.4 create mode 100644 static/openbsd/man4/man4.i386/pctr.4 create mode 100644 static/openbsd/man4/man4.i386/sb.4 create mode 100644 static/openbsd/man4/man4.i386/skgpio.4 create mode 100644 static/openbsd/man4/man4.i386/tcpcib.4 create mode 100644 static/openbsd/man4/man4.i386/uha.4 create mode 100644 static/openbsd/man4/man4.i386/wds.4 create mode 100644 static/openbsd/man4/man4.i386/wdt.4 create mode 100644 static/openbsd/man4/man4.landisk/Makefile create mode 100644 static/openbsd/man4/man4.landisk/intro.4 create mode 100644 static/openbsd/man4/man4.landisk/mem.4 create mode 100644 static/openbsd/man4/man4.landisk/obio.4 create mode 100644 static/openbsd/man4/man4.landisk/power.4 create mode 100644 static/openbsd/man4/man4.landisk/shpcic.4 create mode 100644 static/openbsd/man4/man4.loongson/Makefile create mode 100644 static/openbsd/man4/man4.loongson/apm.4 create mode 100644 static/openbsd/man4/man4.loongson/autoconf.4 create mode 100644 static/openbsd/man4/man4.loongson/bonito.4 create mode 100644 static/openbsd/man4/man4.loongson/gdiumiic.4 create mode 100644 static/openbsd/man4/man4.loongson/glxclk.4 create mode 100644 static/openbsd/man4/man4.loongson/glxpcib.4 create mode 100644 static/openbsd/man4/man4.loongson/htb.4 create mode 100644 static/openbsd/man4/man4.loongson/intro.4 create mode 100644 static/openbsd/man4/man4.loongson/leioc.4 create mode 100644 static/openbsd/man4/man4.loongson/mem.4 create mode 100644 static/openbsd/man4/man4.loongson/sisfb.4 create mode 100644 static/openbsd/man4/man4.loongson/smfb.4 create mode 100644 static/openbsd/man4/man4.loongson/stsec.4 create mode 100644 static/openbsd/man4/man4.loongson/voyager.4 create mode 100644 static/openbsd/man4/man4.loongson/ykbec.4 create mode 100644 static/openbsd/man4/man4.luna88k/Makefile create mode 100644 static/openbsd/man4/man4.luna88k/autoconf.4 create mode 100644 static/openbsd/man4/man4.luna88k/cbus.4 create mode 100644 static/openbsd/man4/man4.luna88k/intro.4 create mode 100644 static/openbsd/man4/man4.luna88k/lcd.4 create mode 100644 static/openbsd/man4/man4.luna88k/le.4 create mode 100644 static/openbsd/man4/man4.luna88k/mem.4 create mode 100644 static/openbsd/man4/man4.luna88k/necsb.4 create mode 100644 static/openbsd/man4/man4.luna88k/pcexmem.4 create mode 100644 static/openbsd/man4/man4.luna88k/spc.4 create mode 100644 static/openbsd/man4/man4.luna88k/xp.4 create mode 100644 static/openbsd/man4/man4.macppc/Makefile create mode 100644 static/openbsd/man4/man4.macppc/abtn.4 create mode 100644 static/openbsd/man4/man4.macppc/adb.4 create mode 100644 static/openbsd/man4/man4.macppc/aoa.4 create mode 100644 static/openbsd/man4/man4.macppc/apm.4 create mode 100644 static/openbsd/man4/man4.macppc/asms.4 create mode 100644 static/openbsd/man4/man4.macppc/autoconf.4 create mode 100644 static/openbsd/man4/man4.macppc/awacs.4 create mode 100644 static/openbsd/man4/man4.macppc/bm.4 create mode 100644 static/openbsd/man4/man4.macppc/daca.4 create mode 100644 static/openbsd/man4/man4.macppc/dfs.4 create mode 100644 static/openbsd/man4/man4.macppc/fcu.4 create mode 100644 static/openbsd/man4/man4.macppc/hpb.4 create mode 100644 static/openbsd/man4/man4.macppc/ht.4 create mode 100644 static/openbsd/man4/man4.macppc/intro.4 create mode 100644 static/openbsd/man4/man4.macppc/kauaiata.4 create mode 100644 static/openbsd/man4/man4.macppc/kiic.4 create mode 100644 static/openbsd/man4/man4.macppc/macgpio.4 create mode 100644 static/openbsd/man4/man4.macppc/macobio.4 create mode 100644 static/openbsd/man4/man4.macppc/mc.4 create mode 100644 static/openbsd/man4/man4.macppc/mediabay.4 create mode 100644 static/openbsd/man4/man4.macppc/mem.4 create mode 100644 static/openbsd/man4/man4.macppc/memc.4 create mode 100644 static/openbsd/man4/man4.macppc/mpcpcibr.4 create mode 100644 static/openbsd/man4/man4.macppc/onyx.4 create mode 100644 static/openbsd/man4/man4.macppc/openpic.4 create mode 100644 static/openbsd/man4/man4.macppc/pgs.4 create mode 100644 static/openbsd/man4/man4.macppc/piic.4 create mode 100644 static/openbsd/man4/man4.macppc/smu.4 create mode 100644 static/openbsd/man4/man4.macppc/snapper.4 create mode 100644 static/openbsd/man4/man4.macppc/sysbutton.4 create mode 100644 static/openbsd/man4/man4.macppc/tumbler.4 create mode 100644 static/openbsd/man4/man4.macppc/xlights.4 create mode 100644 static/openbsd/man4/man4.macppc/zs.4 create mode 100644 static/openbsd/man4/man4.octeon/Makefile create mode 100644 static/openbsd/man4/man4.octeon/amdcf.4 create mode 100644 static/openbsd/man4/man4.octeon/cnmac.4 create mode 100644 static/openbsd/man4/man4.octeon/intro.4 create mode 100644 static/openbsd/man4/man4.octeon/octboot.4 create mode 100644 static/openbsd/man4/man4.octeon/octcf.4 create mode 100644 static/openbsd/man4/man4.octeon/octcib.4 create mode 100644 static/openbsd/man4/man4.octeon/octcit.4 create mode 100644 static/openbsd/man4/man4.octeon/octciu.4 create mode 100644 static/openbsd/man4/man4.octeon/octcrypto.4 create mode 100644 static/openbsd/man4/man4.octeon/octgmx.4 create mode 100644 static/openbsd/man4/man4.octeon/octgpio.4 create mode 100644 static/openbsd/man4/man4.octeon/octiic.4 create mode 100644 static/openbsd/man4/man4.octeon/octmmc.4 create mode 100644 static/openbsd/man4/man4.octeon/octpcie.4 create mode 100644 static/openbsd/man4/man4.octeon/octpip.4 create mode 100644 static/openbsd/man4/man4.octeon/octrng.4 create mode 100644 static/openbsd/man4/man4.octeon/octrtc.4 create mode 100644 static/openbsd/man4/man4.octeon/octsctl.4 create mode 100644 static/openbsd/man4/man4.octeon/octsmi.4 create mode 100644 static/openbsd/man4/man4.octeon/octuctl.4 create mode 100644 static/openbsd/man4/man4.octeon/octxctl.4 create mode 100644 static/openbsd/man4/man4.octeon/ogx.4 create mode 100644 static/openbsd/man4/man4.octeon/ogxnexus.4 create mode 100644 static/openbsd/man4/man4.powerpc64/Makefile create mode 100644 static/openbsd/man4/man4.powerpc64/astfb.4 create mode 100644 static/openbsd/man4/man4.powerpc64/intro.4 create mode 100644 static/openbsd/man4/man4.powerpc64/opal.4 create mode 100644 static/openbsd/man4/man4.powerpc64/opalcons.4 create mode 100644 static/openbsd/man4/man4.powerpc64/opalsens.4 create mode 100644 static/openbsd/man4/man4.powerpc64/phb.4 create mode 100644 static/openbsd/man4/man4.powerpc64/xicp.4 create mode 100644 static/openbsd/man4/man4.powerpc64/xics.4 create mode 100644 static/openbsd/man4/man4.powerpc64/xive.4 create mode 100644 static/openbsd/man4/man4.riscv64/Makefile create mode 100644 static/openbsd/man4/man4.riscv64/intro.4 create mode 100644 static/openbsd/man4/man4.riscv64/mpfclock.4 create mode 100644 static/openbsd/man4/man4.riscv64/mpfgpio.4 create mode 100644 static/openbsd/man4/man4.riscv64/mpfiic.4 create mode 100644 static/openbsd/man4/man4.riscv64/plic.4 create mode 100644 static/openbsd/man4/man4.riscv64/sfcc.4 create mode 100644 static/openbsd/man4/man4.riscv64/sfclock.4 create mode 100644 static/openbsd/man4/man4.riscv64/sfgpio.4 create mode 100644 static/openbsd/man4/man4.riscv64/sfuart.4 create mode 100644 static/openbsd/man4/man4.riscv64/sgmsi.4 create mode 100644 static/openbsd/man4/man4.riscv64/smtclock.4 create mode 100644 static/openbsd/man4/man4.riscv64/smtcomphy.4 create mode 100644 static/openbsd/man4/man4.riscv64/smte.4 create mode 100644 static/openbsd/man4/man4.riscv64/smtgpio.4 create mode 100644 static/openbsd/man4/man4.riscv64/smtiic.4 create mode 100644 static/openbsd/man4/man4.riscv64/smtpinctrl.4 create mode 100644 static/openbsd/man4/man4.riscv64/smtpmic.4 create mode 100644 static/openbsd/man4/man4.riscv64/stfclock.4 create mode 100644 static/openbsd/man4/man4.riscv64/stfpcie.4 create mode 100644 static/openbsd/man4/man4.riscv64/stfpciephy.4 create mode 100644 static/openbsd/man4/man4.riscv64/stfpinctrl.4 create mode 100644 static/openbsd/man4/man4.riscv64/stfrng.4 create mode 100644 static/openbsd/man4/man4.sparc64/Makefile create mode 100644 static/openbsd/man4/man4.sparc64/agten.4 create mode 100644 static/openbsd/man4/man4.sparc64/apio.4 create mode 100644 static/openbsd/man4/man4.sparc64/asio.4 create mode 100644 static/openbsd/man4/man4.sparc64/audioce.4 create mode 100644 static/openbsd/man4/man4.sparc64/audiocs.4 create mode 100644 static/openbsd/man4/man4.sparc64/autoconf.4 create mode 100644 static/openbsd/man4/man4.sparc64/auxio.4 create mode 100644 static/openbsd/man4/man4.sparc64/bbc.4 create mode 100644 static/openbsd/man4/man4.sparc64/be.4 create mode 100644 static/openbsd/man4/man4.sparc64/beeper.4 create mode 100644 static/openbsd/man4/man4.sparc64/bpp.4 create mode 100644 static/openbsd/man4/man4.sparc64/bwtwo.4 create mode 100644 static/openbsd/man4/man4.sparc64/cbus.4 create mode 100644 static/openbsd/man4/man4.sparc64/central.4 create mode 100644 static/openbsd/man4/man4.sparc64/cgsix.4 create mode 100644 static/openbsd/man4/man4.sparc64/cgthree.4 create mode 100644 static/openbsd/man4/man4.sparc64/cgtwelve.4 create mode 100644 static/openbsd/man4/man4.sparc64/clkbrd.4 create mode 100644 static/openbsd/man4/man4.sparc64/clock.4 create mode 100644 static/openbsd/man4/man4.sparc64/cmp.4 create mode 100644 static/openbsd/man4/man4.sparc64/comkbd.4 create mode 100644 static/openbsd/man4/man4.sparc64/comms.4 create mode 100644 static/openbsd/man4/man4.sparc64/core.4 create mode 100644 static/openbsd/man4/man4.sparc64/creator.4 create mode 100644 static/openbsd/man4/man4.sparc64/ebus.4 create mode 100644 static/openbsd/man4/man4.sparc64/ecadc.4 create mode 100644 static/openbsd/man4/man4.sparc64/environ.4 create mode 100644 static/openbsd/man4/man4.sparc64/esp.4 create mode 100644 static/openbsd/man4/man4.sparc64/fhc.4 create mode 100644 static/openbsd/man4/man4.sparc64/gfxp.4 create mode 100644 static/openbsd/man4/man4.sparc64/ifb.4 create mode 100644 static/openbsd/man4/man4.sparc64/intro.4 create mode 100644 static/openbsd/man4/man4.sparc64/le.4 create mode 100644 static/openbsd/man4/man4.sparc64/led.4 create mode 100644 static/openbsd/man4/man4.sparc64/lom.4 create mode 100644 static/openbsd/man4/man4.sparc64/machfb.4 create mode 100644 static/openbsd/man4/man4.sparc64/magma.4 create mode 100644 static/openbsd/man4/man4.sparc64/mem.4 create mode 100644 static/openbsd/man4/man4.sparc64/mgx.4 create mode 100644 static/openbsd/man4/man4.sparc64/pcons.4 create mode 100644 static/openbsd/man4/man4.sparc64/pmc.4 create mode 100644 static/openbsd/man4/man4.sparc64/power.4 create mode 100644 static/openbsd/man4/man4.sparc64/ppm.4 create mode 100644 static/openbsd/man4/man4.sparc64/prtc.4 create mode 100644 static/openbsd/man4/man4.sparc64/psycho.4 create mode 100644 static/openbsd/man4/man4.sparc64/pyro.4 create mode 100644 static/openbsd/man4/man4.sparc64/qe.4 create mode 100644 static/openbsd/man4/man4.sparc64/qec.4 create mode 100644 static/openbsd/man4/man4.sparc64/radeonfb.4 create mode 100644 static/openbsd/man4/man4.sparc64/raptor.4 create mode 100644 static/openbsd/man4/man4.sparc64/rfx.4 create mode 100644 static/openbsd/man4/man4.sparc64/sab.4 create mode 100644 static/openbsd/man4/man4.sparc64/sbbc.4 create mode 100644 static/openbsd/man4/man4.sparc64/schizo.4 create mode 100644 static/openbsd/man4/man4.sparc64/spif.4 create mode 100644 static/openbsd/man4/man4.sparc64/ssm.4 create mode 100644 static/openbsd/man4/man4.sparc64/tda.4 create mode 100644 static/openbsd/man4/man4.sparc64/tvtwo.4 create mode 100644 static/openbsd/man4/man4.sparc64/upa.4 create mode 100644 static/openbsd/man4/man4.sparc64/uperf.4 create mode 100644 static/openbsd/man4/man4.sparc64/vbus.4 create mode 100644 static/openbsd/man4/man4.sparc64/vcc.4 create mode 100644 static/openbsd/man4/man4.sparc64/vcons.4 create mode 100644 static/openbsd/man4/man4.sparc64/vds.4 create mode 100644 static/openbsd/man4/man4.sparc64/vdsk.4 create mode 100644 static/openbsd/man4/man4.sparc64/vigra.4 create mode 100644 static/openbsd/man4/man4.sparc64/vldc.4 create mode 100644 static/openbsd/man4/man4.sparc64/vnet.4 create mode 100644 static/openbsd/man4/man4.sparc64/vpci.4 create mode 100644 static/openbsd/man4/man4.sparc64/vrng.4 create mode 100644 static/openbsd/man4/man4.sparc64/vrtc.4 create mode 100644 static/openbsd/man4/man4.sparc64/vsw.4 create mode 100644 static/openbsd/man4/man4.sparc64/xbox.4 create mode 100644 static/openbsd/man4/man4.sparc64/zs.4 create mode 100644 static/openbsd/man4/man4.sparc64/zx.4 create mode 100644 static/openbsd/man4/maxds.4 create mode 100644 static/openbsd/man4/maxrtc.4 create mode 100644 static/openbsd/man4/maxtmp.4 create mode 100644 static/openbsd/man4/mbg.4 create mode 100644 static/openbsd/man4/mcprtc.4 create mode 100644 static/openbsd/man4/mcx.4 create mode 100644 static/openbsd/man4/mfi.4 create mode 100644 static/openbsd/man4/mfii.4 create mode 100644 static/openbsd/man4/mfokrtc.4 create mode 100644 static/openbsd/man4/midi.4 create mode 100644 static/openbsd/man4/mii.4 create mode 100644 static/openbsd/man4/mlphy.4 create mode 100644 static/openbsd/man4/mos.4 create mode 100644 static/openbsd/man4/moscom.4 create mode 100644 static/openbsd/man4/mpath.4 create mode 100644 static/openbsd/man4/mpe.4 create mode 100644 static/openbsd/man4/mpi.4 create mode 100644 static/openbsd/man4/mpii.4 create mode 100644 static/openbsd/man4/mpip.4 create mode 100644 static/openbsd/man4/mpu.4 create mode 100644 static/openbsd/man4/mpw.4 create mode 100644 static/openbsd/man4/msk.4 create mode 100644 static/openbsd/man4/msts.4 create mode 100644 static/openbsd/man4/mtd.4 create mode 100644 static/openbsd/man4/mtdphy.4 create mode 100644 static/openbsd/man4/mtintc.4 create mode 100644 static/openbsd/man4/mtio.4 create mode 100644 static/openbsd/man4/mtrng.4 create mode 100644 static/openbsd/man4/mtw.4 create mode 100644 static/openbsd/man4/mtxhci.4 create mode 100644 static/openbsd/man4/mue.4 create mode 100644 static/openbsd/man4/multicast.4 create mode 100644 static/openbsd/man4/mvclock.4 create mode 100644 static/openbsd/man4/mvdog.4 create mode 100644 static/openbsd/man4/mvgicp.4 create mode 100644 static/openbsd/man4/mvgpio.4 create mode 100644 static/openbsd/man4/mvicu.4 create mode 100644 static/openbsd/man4/mviic.4 create mode 100644 static/openbsd/man4/mvkpcie.4 create mode 100644 static/openbsd/man4/mvneta.4 create mode 100644 static/openbsd/man4/mvpinctrl.4 create mode 100644 static/openbsd/man4/mvpp.4 create mode 100644 static/openbsd/man4/mvrng.4 create mode 100644 static/openbsd/man4/mvrtc.4 create mode 100644 static/openbsd/man4/mvspi.4 create mode 100644 static/openbsd/man4/mvsw.4 create mode 100644 static/openbsd/man4/mvtemp.4 create mode 100644 static/openbsd/man4/mvuart.4 create mode 100644 static/openbsd/man4/myx.4 create mode 100644 static/openbsd/man4/ne.4 create mode 100644 static/openbsd/man4/neo.4 create mode 100644 static/openbsd/man4/nep.4 create mode 100644 static/openbsd/man4/netintro.4 create mode 100644 static/openbsd/man4/nfe.4 create mode 100644 static/openbsd/man4/ngbe.4 create mode 100644 static/openbsd/man4/nge.4 create mode 100644 static/openbsd/man4/nhi.4 create mode 100644 static/openbsd/man4/nmea.4 create mode 100644 static/openbsd/man4/nsclpcsio.4 create mode 100644 static/openbsd/man4/nsgphy.4 create mode 100644 static/openbsd/man4/nsphy.4 create mode 100644 static/openbsd/man4/nsphyter.4 create mode 100644 static/openbsd/man4/null.4 create mode 100644 static/openbsd/man4/nviic.4 create mode 100644 static/openbsd/man4/nvme.4 create mode 100644 static/openbsd/man4/nvt.4 create mode 100644 static/openbsd/man4/oce.4 create mode 100644 static/openbsd/man4/ociic.4 create mode 100644 static/openbsd/man4/ohci.4 create mode 100644 static/openbsd/man4/onewire.4 create mode 100644 static/openbsd/man4/oosiop.4 create mode 100644 static/openbsd/man4/openprom.4 create mode 100644 static/openbsd/man4/options.4 create mode 100644 static/openbsd/man4/osiop.4 create mode 100644 static/openbsd/man4/otus.4 create mode 100644 static/openbsd/man4/owctr.4 create mode 100644 static/openbsd/man4/owid.4 create mode 100644 static/openbsd/man4/owsbm.4 create mode 100644 static/openbsd/man4/owtemp.4 create mode 100644 static/openbsd/man4/pair.4 create mode 100644 static/openbsd/man4/pcagpio.4 create mode 100644 static/openbsd/man4/pcaled.4 create mode 100644 static/openbsd/man4/pcamux.4 create mode 100644 static/openbsd/man4/pcdisplay.4 create mode 100644 static/openbsd/man4/pcfadc.4 create mode 100644 static/openbsd/man4/pcfiic.4 create mode 100644 static/openbsd/man4/pcfrtc.4 create mode 100644 static/openbsd/man4/pchb.4 create mode 100644 static/openbsd/man4/pchgpio.4 create mode 100644 static/openbsd/man4/pchtemp.4 create mode 100644 static/openbsd/man4/pci.4 create mode 100644 static/openbsd/man4/pcib.4 create mode 100644 static/openbsd/man4/pciide.4 create mode 100644 static/openbsd/man4/pckbc.4 create mode 100644 static/openbsd/man4/pckbd.4 create mode 100644 static/openbsd/man4/pcmcia.4 create mode 100644 static/openbsd/man4/pcn.4 create mode 100644 static/openbsd/man4/pcppi.4 create mode 100644 static/openbsd/man4/pcscp.4 create mode 100644 static/openbsd/man4/pcxrtc.4 create mode 100644 static/openbsd/man4/pcyrtc.4 create mode 100644 static/openbsd/man4/pf.4 create mode 100644 static/openbsd/man4/pflog.4 create mode 100644 static/openbsd/man4/pflow.4 create mode 100644 static/openbsd/man4/pfsync.4 create mode 100644 static/openbsd/man4/pgt.4 create mode 100644 static/openbsd/man4/piixpm.4 create mode 100644 static/openbsd/man4/pijuice.4 create mode 100644 static/openbsd/man4/pinctrl.4 create mode 100644 static/openbsd/man4/pipex.4 create mode 100644 static/openbsd/man4/plgpio.4 create mode 100644 static/openbsd/man4/plrtc.4 create mode 100644 static/openbsd/man4/pluart.4 create mode 100644 static/openbsd/man4/pms.4 create mode 100644 static/openbsd/man4/ppb.4 create mode 100644 static/openbsd/man4/ppp.4 create mode 100644 static/openbsd/man4/pppoe.4 create mode 100644 static/openbsd/man4/pppx.4 create mode 100644 static/openbsd/man4/psci.4 create mode 100644 static/openbsd/man4/psp.4 create mode 100644 static/openbsd/man4/pty.4 create mode 100644 static/openbsd/man4/puc.4 create mode 100644 static/openbsd/man4/pvbus.4 create mode 100644 static/openbsd/man4/pvclock.4 create mode 100644 static/openbsd/man4/pwdog.4 create mode 100644 static/openbsd/man4/pwmbl.4 create mode 100644 static/openbsd/man4/pwmfan.4 create mode 100644 static/openbsd/man4/pwmleds.4 create mode 100644 static/openbsd/man4/pwmreg.4 create mode 100644 static/openbsd/man4/qccpu.4 create mode 100644 static/openbsd/man4/qccpucp.4 create mode 100644 static/openbsd/man4/qcdpc.4 create mode 100644 static/openbsd/man4/qcdrm.4 create mode 100644 static/openbsd/man4/qcdwusb.4 create mode 100644 static/openbsd/man4/qcgpio.4 create mode 100644 static/openbsd/man4/qciic.4 create mode 100644 static/openbsd/man4/qcpdc.4 create mode 100644 static/openbsd/man4/qcpmic.4 create mode 100644 static/openbsd/man4/qcpmicgpio.4 create mode 100644 static/openbsd/man4/qcpon.4 create mode 100644 static/openbsd/man4/qcpwm.4 create mode 100644 static/openbsd/man4/qcrng.4 create mode 100644 static/openbsd/man4/qcrtc.4 create mode 100644 static/openbsd/man4/qcspmi.4 create mode 100644 static/openbsd/man4/qcuart.4 create mode 100644 static/openbsd/man4/qla.4 create mode 100644 static/openbsd/man4/qle.4 create mode 100644 static/openbsd/man4/qlw.4 create mode 100644 static/openbsd/man4/qsphy.4 create mode 100644 static/openbsd/man4/qwx.4 create mode 100644 static/openbsd/man4/radio.4 create mode 100644 static/openbsd/man4/ral.4 create mode 100644 static/openbsd/man4/random.4 create mode 100644 static/openbsd/man4/rd.4 create mode 100644 static/openbsd/man4/rdac.4 create mode 100644 static/openbsd/man4/rdcphy.4 create mode 100644 static/openbsd/man4/rdomain.4 create mode 100644 static/openbsd/man4/re.4 create mode 100644 static/openbsd/man4/rge.4 create mode 100644 static/openbsd/man4/rgephy.4 create mode 100644 static/openbsd/man4/ricohrtc.4 create mode 100644 static/openbsd/man4/rkanxdp.4 create mode 100644 static/openbsd/man4/rkclock.4 create mode 100644 static/openbsd/man4/rkcomphy.4 create mode 100644 static/openbsd/man4/rkdrm.4 create mode 100644 static/openbsd/man4/rkdwhdmi.4 create mode 100644 static/openbsd/man4/rkdwusb.4 create mode 100644 static/openbsd/man4/rkemmcphy.4 create mode 100644 static/openbsd/man4/rkgpio.4 create mode 100644 static/openbsd/man4/rkgrf.4 create mode 100644 static/openbsd/man4/rkiic.4 create mode 100644 static/openbsd/man4/rkiis.4 create mode 100644 static/openbsd/man4/rkiovd.4 create mode 100644 static/openbsd/man4/rkpcie.4 create mode 100644 static/openbsd/man4/rkpciephy.4 create mode 100644 static/openbsd/man4/rkpinctrl.4 create mode 100644 static/openbsd/man4/rkpmic.4 create mode 100644 static/openbsd/man4/rkpwm.4 create mode 100644 static/openbsd/man4/rkrng.4 create mode 100644 static/openbsd/man4/rkspi.4 create mode 100644 static/openbsd/man4/rktcphy.4 create mode 100644 static/openbsd/man4/rktemp.4 create mode 100644 static/openbsd/man4/rkusbphy.4 create mode 100644 static/openbsd/man4/rkvop.4 create mode 100644 static/openbsd/man4/rl.4 create mode 100644 static/openbsd/man4/rlphy.4 create mode 100644 static/openbsd/man4/route.4 create mode 100644 static/openbsd/man4/rport.4 create mode 100644 static/openbsd/man4/rsu.4 create mode 100644 static/openbsd/man4/rtsx.4 create mode 100644 static/openbsd/man4/rtw.4 create mode 100644 static/openbsd/man4/rtwn.4 create mode 100644 static/openbsd/man4/rum.4 create mode 100644 static/openbsd/man4/run.4 create mode 100644 static/openbsd/man4/safte.4 create mode 100644 static/openbsd/man4/sbus.4 create mode 100644 static/openbsd/man4/schsio.4 create mode 100644 static/openbsd/man4/scmi.4 create mode 100644 static/openbsd/man4/scsi.4 create mode 100644 static/openbsd/man4/sd.4 create mode 100644 static/openbsd/man4/sdhc.4 create mode 100644 static/openbsd/man4/sdmmc.4 create mode 100644 static/openbsd/man4/sdtemp.4 create mode 100644 static/openbsd/man4/se.4 create mode 100644 static/openbsd/man4/sec.4 create mode 100644 static/openbsd/man4/ses.4 create mode 100644 static/openbsd/man4/sf.4 create mode 100644 static/openbsd/man4/sili.4 create mode 100644 static/openbsd/man4/simpleamp.4 create mode 100644 static/openbsd/man4/simpleaudio.4 create mode 100644 static/openbsd/man4/simplefb.4 create mode 100644 static/openbsd/man4/simplepanel.4 create mode 100644 static/openbsd/man4/siop.4 create mode 100644 static/openbsd/man4/sis.4 create mode 100644 static/openbsd/man4/sk.4 create mode 100644 static/openbsd/man4/sm.4 create mode 100644 static/openbsd/man4/smsc.4 create mode 100644 static/openbsd/man4/sncodec.4 create mode 100644 static/openbsd/man4/softraid.4 create mode 100644 static/openbsd/man4/spdmem.4 create mode 100644 static/openbsd/man4/speaker.4 create mode 100644 static/openbsd/man4/sppp.4 create mode 100644 static/openbsd/man4/sqphy.4 create mode 100644 static/openbsd/man4/ssdfb.4 create mode 100644 static/openbsd/man4/st.4 create mode 100644 static/openbsd/man4/ste.4 create mode 100644 static/openbsd/man4/stge.4 create mode 100644 static/openbsd/man4/sti.4 create mode 100644 static/openbsd/man4/stp.4 create mode 100644 static/openbsd/man4/sv.4 create mode 100644 static/openbsd/man4/sxiccmu.4 create mode 100644 static/openbsd/man4/sxidog.4 create mode 100644 static/openbsd/man4/sximmc.4 create mode 100644 static/openbsd/man4/sxipio.4 create mode 100644 static/openbsd/man4/sxipwm.4 create mode 100644 static/openbsd/man4/sxirintc.4 create mode 100644 static/openbsd/man4/sxirsb.4 create mode 100644 static/openbsd/man4/sxirtc.4 create mode 100644 static/openbsd/man4/sxisid.4 create mode 100644 static/openbsd/man4/sxisyscon.4 create mode 100644 static/openbsd/man4/sxitemp.4 create mode 100644 static/openbsd/man4/sxitwi.4 create mode 100644 static/openbsd/man4/sym.4 create mode 100644 static/openbsd/man4/sypwr.4 create mode 100644 static/openbsd/man4/syscon.4 create mode 100644 static/openbsd/man4/tascodec.4 create mode 100644 static/openbsd/man4/tcic.4 create mode 100644 static/openbsd/man4/tcp.4 create mode 100644 static/openbsd/man4/tcpci.4 create mode 100644 static/openbsd/man4/termios.4 create mode 100644 static/openbsd/man4/thmc.4 create mode 100644 static/openbsd/man4/tht.4 create mode 100644 static/openbsd/man4/ti.4 create mode 100644 static/openbsd/man4/tipd.4 create mode 100644 static/openbsd/man4/tipmic.4 create mode 100644 static/openbsd/man4/titmp.4 create mode 100644 static/openbsd/man4/tl.4 create mode 100644 static/openbsd/man4/tlphy.4 create mode 100644 static/openbsd/man4/tpm.4 create mode 100644 static/openbsd/man4/tpmr.4 create mode 100644 static/openbsd/man4/tqphy.4 create mode 100644 static/openbsd/man4/trm.4 create mode 100644 static/openbsd/man4/trunk.4 create mode 100644 static/openbsd/man4/tsl.4 create mode 100644 static/openbsd/man4/tty.4 create mode 100644 static/openbsd/man4/tun.4 create mode 100644 static/openbsd/man4/twe.4 create mode 100644 static/openbsd/man4/txp.4 create mode 100644 static/openbsd/man4/txphy.4 create mode 100644 static/openbsd/man4/uaq.4 create mode 100644 static/openbsd/man4/uark.4 create mode 100644 static/openbsd/man4/uath.4 create mode 100644 static/openbsd/man4/uaudio.4 create mode 100644 static/openbsd/man4/ubcmtp.4 create mode 100644 static/openbsd/man4/uberry.4 create mode 100644 static/openbsd/man4/ubsa.4 create mode 100644 static/openbsd/man4/ucc.4 create mode 100644 static/openbsd/man4/uchcom.4 create mode 100644 static/openbsd/man4/ucom.4 create mode 100644 static/openbsd/man4/ucrcom.4 create mode 100644 static/openbsd/man4/ucycom.4 create mode 100644 static/openbsd/man4/udav.4 create mode 100644 static/openbsd/man4/udcf.4 create mode 100644 static/openbsd/man4/udl.4 create mode 100644 static/openbsd/man4/udp.4 create mode 100644 static/openbsd/man4/udsbr.4 create mode 100644 static/openbsd/man4/ufshci.4 create mode 100644 static/openbsd/man4/uftdi.4 create mode 100644 static/openbsd/man4/ugen.4 create mode 100644 static/openbsd/man4/ugl.4 create mode 100644 static/openbsd/man4/ugold.4 create mode 100644 static/openbsd/man4/uguru.4 create mode 100644 static/openbsd/man4/uhci.4 create mode 100644 static/openbsd/man4/uhid.4 create mode 100644 static/openbsd/man4/uhidev.4 create mode 100644 static/openbsd/man4/uhidpp.4 create mode 100644 static/openbsd/man4/uipaq.4 create mode 100644 static/openbsd/man4/ujoy.4 create mode 100644 static/openbsd/man4/uk.4 create mode 100644 static/openbsd/man4/ukbd.4 create mode 100644 static/openbsd/man4/ukphy.4 create mode 100644 static/openbsd/man4/ukspan.4 create mode 100644 static/openbsd/man4/ulpt.4 create mode 100644 static/openbsd/man4/umass.4 create mode 100644 static/openbsd/man4/umb.4 create mode 100644 static/openbsd/man4/umbg.4 create mode 100644 static/openbsd/man4/umcs.4 create mode 100644 static/openbsd/man4/umct.4 create mode 100644 static/openbsd/man4/umidi.4 create mode 100644 static/openbsd/man4/umodem.4 create mode 100644 static/openbsd/man4/ums.4 create mode 100644 static/openbsd/man4/umsm.4 create mode 100644 static/openbsd/man4/umstc.4 create mode 100644 static/openbsd/man4/umt.4 create mode 100644 static/openbsd/man4/unix.4 create mode 100644 static/openbsd/man4/uoaklux.4 create mode 100644 static/openbsd/man4/uoakrh.4 create mode 100644 static/openbsd/man4/uoakv.4 create mode 100644 static/openbsd/man4/uonerng.4 create mode 100644 static/openbsd/man4/uow.4 create mode 100644 static/openbsd/man4/upd.4 create mode 100644 static/openbsd/man4/upgt.4 create mode 100644 static/openbsd/man4/upl.4 create mode 100644 static/openbsd/man4/uplcom.4 create mode 100644 static/openbsd/man4/ural.4 create mode 100644 static/openbsd/man4/ure.4 create mode 100644 static/openbsd/man4/url.4 create mode 100644 static/openbsd/man4/urlphy.4 create mode 100644 static/openbsd/man4/urndis.4 create mode 100644 static/openbsd/man4/urng.4 create mode 100644 static/openbsd/man4/urtw.4 create mode 100644 static/openbsd/man4/urtwn.4 create mode 100644 static/openbsd/man4/usb.4 create mode 100644 static/openbsd/man4/uscom.4 create mode 100644 static/openbsd/man4/uslcom.4 create mode 100644 static/openbsd/man4/uslhcom.4 create mode 100644 static/openbsd/man4/usps.4 create mode 100644 static/openbsd/man4/uthum.4 create mode 100644 static/openbsd/man4/uticom.4 create mode 100644 static/openbsd/man4/utpms.4 create mode 100644 static/openbsd/man4/utrh.4 create mode 100644 static/openbsd/man4/uts.4 create mode 100644 static/openbsd/man4/utvfu.4 create mode 100644 static/openbsd/man4/utwitch.4 create mode 100644 static/openbsd/man4/uvideo.4 create mode 100644 static/openbsd/man4/uvisor.4 create mode 100644 static/openbsd/man4/uvscom.4 create mode 100644 static/openbsd/man4/uwacom.4 create mode 100644 static/openbsd/man4/uxrcom.4 create mode 100644 static/openbsd/man4/veb.4 create mode 100644 static/openbsd/man4/vether.4 create mode 100644 static/openbsd/man4/vga.4 create mode 100644 static/openbsd/man4/vgafb.4 create mode 100644 static/openbsd/man4/vge.4 create mode 100644 static/openbsd/man4/viapm.4 create mode 100644 static/openbsd/man4/viasio.4 create mode 100644 static/openbsd/man4/vic.4 create mode 100644 static/openbsd/man4/video.4 create mode 100644 static/openbsd/man4/vio.4 create mode 100644 static/openbsd/man4/vioblk.4 create mode 100644 static/openbsd/man4/viocon.4 create mode 100644 static/openbsd/man4/viogpu.4 create mode 100644 static/openbsd/man4/viomb.4 create mode 100644 static/openbsd/man4/viornd.4 create mode 100644 static/openbsd/man4/vioscsi.4 create mode 100644 static/openbsd/man4/virtio.4 create mode 100644 static/openbsd/man4/vlan.4 create mode 100644 static/openbsd/man4/vmmci.4 create mode 100644 static/openbsd/man4/vmt.4 create mode 100644 static/openbsd/man4/vmwpvs.4 create mode 100644 static/openbsd/man4/vmx.4 create mode 100644 static/openbsd/man4/vnd.4 create mode 100644 static/openbsd/man4/vr.4 create mode 100644 static/openbsd/man4/vscsi.4 create mode 100644 static/openbsd/man4/vte.4 create mode 100644 static/openbsd/man4/vxlan.4 create mode 100644 static/openbsd/man4/watchdog.4 create mode 100644 static/openbsd/man4/wb.4 create mode 100644 static/openbsd/man4/wbenv.4 create mode 100644 static/openbsd/man4/wbng.4 create mode 100644 static/openbsd/man4/wbsd.4 create mode 100644 static/openbsd/man4/wbsio.4 create mode 100644 static/openbsd/man4/wd.4 create mode 100644 static/openbsd/man4/wdc.4 create mode 100644 static/openbsd/man4/we.4 create mode 100644 static/openbsd/man4/wg.4 create mode 100644 static/openbsd/man4/wi.4 create mode 100644 static/openbsd/man4/witness.4 create mode 100644 static/openbsd/man4/wpi.4 create mode 100644 static/openbsd/man4/wscons.4 create mode 100644 static/openbsd/man4/wsdisplay.4 create mode 100644 static/openbsd/man4/wskbd.4 create mode 100644 static/openbsd/man4/wsmouse.4 create mode 100644 static/openbsd/man4/wsmux.4 create mode 100644 static/openbsd/man4/xbf.4 create mode 100644 static/openbsd/man4/xe.4 create mode 100644 static/openbsd/man4/xen.4 create mode 100644 static/openbsd/man4/xf86.4 create mode 100644 static/openbsd/man4/xge.4 create mode 100644 static/openbsd/man4/xhci.4 create mode 100644 static/openbsd/man4/xl.4 create mode 100644 static/openbsd/man4/xmphy.4 create mode 100644 static/openbsd/man4/xnf.4 create mode 100644 static/openbsd/man4/xspd.4 create mode 100644 static/openbsd/man4/yds.4 create mode 100644 static/openbsd/man4/ytphy.4 create mode 100644 static/openbsd/man4/zero.4 create mode 100644 static/openbsd/man4/zyd.4 (limited to 'static/openbsd/man4') diff --git a/static/openbsd/man4/Makefile b/static/openbsd/man4/Makefile new file mode 100644 index 00000000..3a338ec0 --- /dev/null +++ b/static/openbsd/man4/Makefile @@ -0,0 +1,782 @@ +MAN = aac.4 \ + abcrtc.4 \ + abl.4 \ + ac97.4 \ + acphy.4 \ + acpi.4 \ + acpiac.4 \ + acpials.4 \ + acpiasus.4 \ + acpibat.4 \ + acpibtn.4 \ + acpicbkbd.4 \ + acpicmos.4 \ + acpicpu.4 \ + acpidock.4 \ + acpiec.4 \ + acpige.4 \ + acpihid.4 \ + acpihpet.4 \ + acpihve.4 \ + acpimadt.4 \ + acpimcfg.4 \ + acpipci.4 \ + acpiprt.4 \ + acpipwrres.4 \ + acpisbs.4 \ + acpisony.4 \ + acpisurface.4 \ + acpithinkpad.4 \ + acpitimer.4 \ + acpitoshiba.4 \ + acpitz.4 \ + acpivideo.4 \ + acpivout.4 \ + acpiwmi.4 \ + acrtc.4 \ + acx.4 \ + adc.4 \ + addcom.4 \ + adl.4 \ + admcts.4 \ + admlc.4 \ + admtemp.4 \ + admtm.4 \ + admtmp.4 \ + admtt.4 \ + adt.4 \ + adtfsm.4 \ + adv.4 \ + age.4 \ + aggr.4 \ + agp.4 \ + ahc.4 \ + ahci.4 \ + ahd.4 \ + aibs.4 \ + aic.4 \ + akbd.4 \ + alc.4 \ + ale.4 \ + alipm.4 \ + amas.4 \ + amdgpio.4 \ + amdiic.4 \ + amdpm.4 \ + amdpmc.4 \ + ami.4 \ + amlclock.4 \ + amldwusb.4 \ + amliic.4 \ + amlmmc.4 \ + amlpciephy.4 \ + amlpinctrl.4 \ + amlpwm.4 \ + amlreset.4 \ + amlrng.4 \ + amlsm.4 \ + amltemp.4 \ + amluart.4 \ + amlusbphy.4 \ + amphy.4 \ + ams.4 \ + an.4 \ + andl.4 \ + aplgpio.4 \ + aps.4 \ + aq.4 \ + arc.4 \ + arcofi.4 \ + asbtm.4 \ + asmc.4 \ + ast.4 \ + atapiscsi.4 \ + ath.4 \ + athn.4 \ + atphy.4 \ + atu.4 \ + atw.4 \ + auacer.4 \ + audio.4 \ + aue.4 \ + auglx.4 \ + auich.4 \ + auixp.4 \ + autri.4 \ + auvia.4 \ + axe.4 \ + axen.4 \ + axppmic.4 \ + azalia.4 \ + bce.4 \ + bcmaux.4 \ + bcmbsc.4 \ + bcmclock.4 \ + bcmdmac.4 \ + bcmdog.4 \ + bcmgpio.4 \ + bcmirng.4 \ + bcmmbox.4 \ + bcmpcie.4 \ + bcmrng.4 \ + bcmsdhost.4 \ + bcmstbgpio.4 \ + bcmstbintc.4 \ + bcmstbpinctrl.4 \ + bcmstbrescal.4 \ + bcmstbreset.4 \ + bcmtemp.4 \ + bcmtmon.4 \ + bdpmic.4 \ + berkwdt.4 \ + bge.4 \ + bgw.4 \ + bio.4 \ + bktr.4 \ + bmtphy.4 \ + bnx.4 \ + bnxt.4 \ + boca.4 \ + bpe.4 \ + bpf.4 \ + brgphy.4 \ + bridge.4 \ + brswphy.4 \ + bse.4 \ + bwfm.4 \ + bwi.4 \ + bytgpio.4 \ + cac.4 \ + cad.4 \ + cardbus.4 \ + carp.4 \ + cas.4 \ + ccp.4 \ + ccpmic.4 \ + cd.4 \ + cdce.4 \ + cdpcie.4 \ + cdsdhc.4 \ + cduart.4 \ + cfxga.4 \ + ch.4 \ + chvgpio.4 \ + ciphy.4 \ + ciss.4 \ + clcs.4 \ + clct.4 \ + cmpci.4 \ + com.4 \ + cue.4 \ + cwfg.4 \ + cy.4 \ + cz.4 \ + dapmic.4 \ + dc.4 \ + dcphy.4 \ + ddb.4 \ + de.4 \ + diskmap.4 \ + divert.4 \ + drm.4 \ + dsxrtc.4 \ + dt.4 \ + dwctwo.4 \ + dwdog.4 \ + dwge.4 \ + dwgpio.4 \ + dwiic.4 \ + dwmmc.4 \ + dwmshc.4 \ + dwpcie.4 \ + dwqe.4 \ + dwxe.4 \ + eap.4 \ + ec.4 \ + eephy.4 \ + ef.4 \ + efi.4 \ + eg.4 \ + ehci.4 \ + eisa.4 \ + el.4 \ + em.4 \ + emc.4 \ + emu.4 \ + enc.4 \ + endrun.4 \ + envy.4 \ + eoip.4 \ + ep.4 \ + epic.4 \ + erspan.4 \ + esa.4 \ + escodec.4 \ + eso.4 \ + ess.4 \ + et.4 \ + etherip.4 \ + etphy.4 \ + ex.4 \ + exphy.4 \ + exrtc.4 \ + fanpwr.4 \ + fd.4 \ + fdc.4 \ + fec.4 \ + fido.4 \ + fins.4 \ + fintek.4 \ + fms.4 \ + frame.4 \ + fusbtc.4 \ + fuse.4 \ + fxp.4 \ + gcu.4 \ + gdt.4 \ + gem.4 \ + gentbi.4 \ + gfrtc.4 \ + gif.4 \ + glenv.4 \ + glkgpio.4 \ + gpio.4 \ + gpiocharger.4 \ + gpiodcf.4 \ + gpioiic.4 \ + gpiokeys.4 \ + gpioleds.4 \ + gpioow.4 \ + graphaudio.4 \ + gre.4 \ + gscsio.4 \ + hds.4 \ + hiclock.4 \ + hidwusb.4 \ + hil.4 \ + hilid.4 \ + hilkbd.4 \ + hilms.4 \ + hireset.4 \ + hitemp.4 \ + hme.4 \ + hotplug.4 \ + hsq.4 \ + hvn.4 \ + hvs.4 \ + hyperv.4 \ + iasuskbd.4 \ + iatp.4 \ + iavf.4 \ + icc.4 \ + ice.4 \ + ichiic.4 \ + ichwdt.4 \ + icmp.4 \ + icmp6.4 \ + icsphy.4 \ + ietp.4 \ + ifmedia.4 \ + igc.4 \ + iha.4 \ + ihidev.4 \ + iic.4 \ + iicmux.4 \ + ikbd.4 \ + ims.4 \ + imt.4 \ + imxanatop.4 \ + imxdog.4 \ + imxesdhc.4 \ + imxgpc.4 \ + imxgpio.4 \ + imxiic.4 \ + imxpciephy.4 \ + imxpwm.4 \ + imxrtc.4 \ + imxspi.4 \ + imxsrc.4 \ + imxtmu.4 \ + imxuart.4 \ + inet.4 \ + inet6.4 \ + inphy.4 \ + intelpmc.4 \ + inthid.4 \ + iophy.4 \ + iosf.4 \ + ip.4 \ + ip6.4 \ + ipcomp.4 \ + ipgphy.4 \ + ipmi.4 \ + ips.4 \ + ipsec.4 \ + ipw.4 \ + isa.4 \ + isagpio.4 \ + isapnp.4 \ + islrtc.4 \ + ispi.4 \ + it.4 \ + itherm.4 \ + iwi.4 \ + iwm.4 \ + iwn.4 \ + iwx.4 \ + ix.4 \ + ixgb.4 \ + ixl.4 \ + ixv.4 \ + jmb.4 \ + jme.4 \ + jmphy.4 \ + kate.4 \ + kcov.4 \ + km.4 \ + ksmn.4 \ + kstat.4 \ + ksyms.4 \ + kubsan.4 \ + kue.4 \ + lc.4 \ + lge.4 \ + lii.4 \ + lisa.4 \ + lm.4 \ + lmenv.4 \ + lmn.4 \ + lmtemp.4 \ + lo.4 \ + lpt.4 \ + luphy.4 \ + lxtphy.4 \ + maestro.4 \ + mainbus.4 \ + malo.4 \ + maxds.4 \ + maxrtc.4 \ + maxtmp.4 \ + mbg.4 \ + mcprtc.4 \ + mcx.4 \ + mfi.4 \ + mfii.4 \ + mfokrtc.4 \ + midi.4 \ + mii.4 \ + mlphy.4 \ + mos.4 \ + moscom.4 \ + mpath.4 \ + mpe.4 \ + mpi.4 \ + mpii.4 \ + mpip.4 \ + mpu.4 \ + mpw.4 \ + msk.4 \ + msts.4 \ + mtd.4 \ + mtdphy.4 \ + mtintc.4 \ + mtio.4 \ + mtrng.4 \ + mtw.4 \ + mtxhci.4 \ + mue.4 \ + multicast.4 \ + mvclock.4 \ + mvdog.4 \ + mvgicp.4 \ + mvgpio.4 \ + mvicu.4 \ + mviic.4 \ + mvkpcie.4 \ + mvneta.4 \ + mvpinctrl.4 \ + mvpp.4 \ + mvrng.4 \ + mvrtc.4 \ + mvspi.4 \ + mvsw.4 \ + mvtemp.4 \ + mvuart.4 \ + myx.4 \ + ne.4 \ + neo.4 \ + nep.4 \ + netintro.4 \ + nfe.4 \ + ngbe.4 \ + nge.4 \ + nhi.4 \ + nmea.4 \ + nsclpcsio.4 \ + nsgphy.4 \ + nsphy.4 \ + nsphyter.4 \ + null.4 \ + nviic.4 \ + nvme.4 \ + nvt.4 \ + oce.4 \ + ociic.4 \ + ohci.4 \ + onewire.4 \ + oosiop.4 \ + openprom.4 \ + options.4 \ + osiop.4 \ + otus.4 \ + owctr.4 \ + owid.4 \ + owsbm.4 \ + owtemp.4 \ + pair.4 \ + pcagpio.4 \ + pcaled.4 \ + pcamux.4 \ + pcdisplay.4 \ + pcfadc.4 \ + pcfiic.4 \ + pcfrtc.4 \ + pchb.4 \ + pchgpio.4 \ + pchtemp.4 \ + pci.4 \ + pcib.4 \ + pciide.4 \ + pckbc.4 \ + pckbd.4 \ + pcmcia.4 \ + pcn.4 \ + pcppi.4 \ + pcscp.4 \ + pcxrtc.4 \ + pcyrtc.4 \ + pf.4 \ + pflog.4 \ + pflow.4 \ + pfsync.4 \ + pgt.4 \ + piixpm.4 \ + pijuice.4 \ + pinctrl.4 \ + pipex.4 \ + plgpio.4 \ + plrtc.4 \ + pluart.4 \ + pms.4 \ + ppb.4 \ + ppp.4 \ + pppoe.4 \ + pppx.4 \ + psci.4 \ + psp.4 \ + pty.4 \ + puc.4 \ + pvbus.4 \ + pvclock.4 \ + pwdog.4 \ + pwmbl.4 \ + pwmfan.4 \ + pwmleds.4 \ + pwmreg.4 \ + qccpu.4 \ + qccpucp.4 \ + qcdpc.4 \ + qcdrm.4 \ + qcdwusb.4 \ + qcgpio.4 \ + qciic.4 \ + qcpdc.4 \ + qcpmic.4 \ + qcpmicgpio.4 \ + qcpon.4 \ + qcpwm.4 \ + qcrng.4 \ + qcrtc.4 \ + qcspmi.4 \ + qcuart.4 \ + qla.4 \ + qle.4 \ + qlw.4 \ + qsphy.4 \ + qwx.4 \ + radio.4 \ + ral.4 \ + random.4 \ + rd.4 \ + rdac.4 \ + rdcphy.4 \ + rdomain.4 \ + re.4 \ + rge.4 \ + rgephy.4 \ + ricohrtc.4 \ + rkanxdp.4 \ + rkclock.4 \ + rkcomphy.4 \ + rkdrm.4 \ + rkdwhdmi.4 \ + rkdwusb.4 \ + rkemmcphy.4 \ + rkgpio.4 \ + rkgrf.4 \ + rkiic.4 \ + rkiis.4 \ + rkiovd.4 \ + rkpcie.4 \ + rkpciephy.4 \ + rkpinctrl.4 \ + rkpmic.4 \ + rkpwm.4 \ + rkrng.4 \ + rkspi.4 \ + rktcphy.4 \ + rktemp.4 \ + rkusbphy.4 \ + rkvop.4 \ + rl.4 \ + rlphy.4 \ + route.4 \ + rport.4 \ + rsu.4 \ + rtsx.4 \ + rtw.4 \ + rtwn.4 \ + rum.4 \ + run.4 \ + safte.4 \ + sbus.4 \ + schsio.4 \ + scmi.4 \ + scsi.4 \ + sd.4 \ + sdhc.4 \ + sdmmc.4 \ + sdtemp.4 \ + se.4 \ + sec.4 \ + ses.4 \ + sf.4 \ + sili.4 \ + simpleamp.4 \ + simpleaudio.4 \ + simplefb.4 \ + simplepanel.4 \ + siop.4 \ + sis.4 \ + sk.4 \ + sm.4 \ + smsc.4 \ + sncodec.4 \ + softraid.4 \ + spdmem.4 \ + speaker.4 \ + sppp.4 \ + sqphy.4 \ + ssdfb.4 \ + st.4 \ + ste.4 \ + stge.4 \ + sti.4 \ + stp.4 \ + sv.4 \ + sxiccmu.4 \ + sxidog.4 \ + sximmc.4 \ + sxipio.4 \ + sxipwm.4 \ + sxirintc.4 \ + sxirsb.4 \ + sxirtc.4 \ + sxisid.4 \ + sxisyscon.4 \ + sxitemp.4 \ + sxitwi.4 \ + sym.4 \ + sypwr.4 \ + syscon.4 \ + tascodec.4 \ + tcic.4 \ + tcp.4 \ + tcpci.4 \ + termios.4 \ + thmc.4 \ + tht.4 \ + ti.4 \ + tipd.4 \ + tipmic.4 \ + titmp.4 \ + tl.4 \ + tlphy.4 \ + tpm.4 \ + tpmr.4 \ + tqphy.4 \ + trm.4 \ + trunk.4 \ + tsl.4 \ + tty.4 \ + tun.4 \ + twe.4 \ + txp.4 \ + txphy.4 \ + uaq.4 \ + uark.4 \ + uath.4 \ + uaudio.4 \ + ubcmtp.4 \ + uberry.4 \ + ubsa.4 \ + ucc.4 \ + uchcom.4 \ + ucom.4 \ + ucrcom.4 \ + ucycom.4 \ + udav.4 \ + udcf.4 \ + udl.4 \ + udp.4 \ + udsbr.4 \ + ufshci.4 \ + uftdi.4 \ + ugen.4 \ + ugl.4 \ + ugold.4 \ + uguru.4 \ + uhci.4 \ + uhid.4 \ + uhidev.4 \ + uhidpp.4 \ + uipaq.4 \ + ujoy.4 \ + uk.4 \ + ukbd.4 \ + ukphy.4 \ + ukspan.4 \ + ulpt.4 \ + umass.4 \ + umb.4 \ + umbg.4 \ + umcs.4 \ + umct.4 \ + umidi.4 \ + umodem.4 \ + ums.4 \ + umsm.4 \ + umstc.4 \ + umt.4 \ + unix.4 \ + uoaklux.4 \ + uoakrh.4 \ + uoakv.4 \ + uonerng.4 \ + uow.4 \ + upd.4 \ + upgt.4 \ + upl.4 \ + uplcom.4 \ + ural.4 \ + ure.4 \ + url.4 \ + urlphy.4 \ + urndis.4 \ + urng.4 \ + urtw.4 \ + urtwn.4 \ + usb.4 \ + uscom.4 \ + uslcom.4 \ + uslhcom.4 \ + usps.4 \ + uthum.4 \ + uticom.4 \ + utpms.4 \ + utrh.4 \ + uts.4 \ + utvfu.4 \ + utwitch.4 \ + uvideo.4 \ + uvisor.4 \ + uvscom.4 \ + uwacom.4 \ + uxrcom.4 \ + veb.4 \ + vether.4 \ + vga.4 \ + vgafb.4 \ + vge.4 \ + viapm.4 \ + viasio.4 \ + vic.4 \ + video.4 \ + vio.4 \ + vioblk.4 \ + viocon.4 \ + viogpu.4 \ + viomb.4 \ + viornd.4 \ + vioscsi.4 \ + virtio.4 \ + vlan.4 \ + vmmci.4 \ + vmt.4 \ + vmwpvs.4 \ + vmx.4 \ + vnd.4 \ + vr.4 \ + vscsi.4 \ + vte.4 \ + vxlan.4 \ + watchdog.4 \ + wb.4 \ + wbenv.4 \ + wbng.4 \ + wbsd.4 \ + wbsio.4 \ + wd.4 \ + wdc.4 \ + we.4 \ + wg.4 \ + wi.4 \ + witness.4 \ + wpi.4 \ + wscons.4 \ + wsdisplay.4 \ + wskbd.4 \ + wsmouse.4 \ + wsmux.4 \ + xbf.4 \ + xe.4 \ + xen.4 \ + xf86.4 \ + xge.4 \ + xhci.4 \ + xl.4 \ + xmphy.4 \ + xnf.4 \ + xspd.4 \ + yds.4 \ + ytphy.4 \ + zero.4 \ + zyd.4 + +SUBDIRS = man4.alpha \ + man4.amd64 \ + man4.arm64 \ + man4.armv7 \ + man4.hppa \ + man4.i386 \ + man4.landisk \ + man4.loongson \ + man4.luna88k \ + man4.macppc \ + man4.octeon \ + man4.powerpc64 \ + man4.riscv64 \ + man4.sparc64 + +include ../../mandoc.mk + diff --git a/static/openbsd/man4/aac.4 b/static/openbsd/man4/aac.4 new file mode 100644 index 00000000..cfc7b117 --- /dev/null +++ b/static/openbsd/man4/aac.4 @@ -0,0 +1,77 @@ +.\" $OpenBSD: aac.4,v 1.27 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2000 Michael Smith +.\" Copyright (c) 2000 BSDi +.\" Copyright (c) 2000 Niklas Hallqvist +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt AAC 4 +.Os +.Sh NAME +.Nm aac +.Nd Adaptec SAS/SATA/SCSI RAID controller +.Sh SYNOPSIS +.Cd "aac* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Adaptec's "FSA" family of RAID controllers, +including: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Adaptec AAC-2622, AAC-364, AAC-3642 +.It Adaptec 2130S, 2200S, 2230SLP, 2410SA, 2610SA, 2810SA, 21610SA +.It Dell CERC-SATA, PERC 320/DC +.It Dell PERC 2/QC, PERC 2/Si, PERC 3/Si, PERC 3/Di +.It HP NetRaid-4M +.It IBM ServeRAID-8i/8k/8s +.El +.Pp +All the RAID set volume management is done via the card BIOS. +.Pp +This driver makes drives and/or RAID sets appear as +.Xr sd 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr scsi 4 , +.Xr sd 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Niklas Hallqvist Aq Mt niklas@openbsd.org , +inspired by the +.Fx +driver by +.An Mike Smith Aq Mt msmith@freebsd.org . +.Sh BUGS +The card provides a mechanism to do online RAID set management, +unfortunately the protocol is not public. diff --git a/static/openbsd/man4/abcrtc.4 b/static/openbsd/man4/abcrtc.4 new file mode 100644 index 00000000..53b64415 --- /dev/null +++ b/static/openbsd/man4/abcrtc.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: abcrtc.4,v 1.3 2023/12/23 02:42:51 jsg Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt +.\" Copyright (c) 2018 Mark Kettenis +.\" Copyright (c) 2018 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 23 2023 $ +.Dt ABCRTC 4 +.Os +.Sh NAME +.Nm abcrtc +.Nd Abracon AB1805 real-time clock +.Sh SYNOPSIS +.Cd "abcrtc* at iic? addr 0x69" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Abracon AB1805 real-time clock chip +and similar variants. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/abl.4 b/static/openbsd/man4/abl.4 new file mode 100644 index 00000000..fc4eaf4f --- /dev/null +++ b/static/openbsd/man4/abl.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: abl.4,v 1.3 2020/10/25 08:35:11 mglocker Exp $ +.\" +.\" Copyright (c) 2020 Marcus Glocker +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: October 25 2020 $ +.Dt ABL 4 +.Os +.Sh NAME +.Nm abl +.Nd Apple backlight support +.Sh SYNOPSIS +.Cd "abl* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver enables access to the backlight found in Intel based Apple iMac +computers. +It provides brightness control using the +.Xr wsconsctl 8 +variable +.Va display.brightness . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr wsconsctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marcus Glocker Aq Mt mglocker@openbsd.org . diff --git a/static/openbsd/man4/ac97.4 b/static/openbsd/man4/ac97.4 new file mode 100644 index 00000000..1725db9c --- /dev/null +++ b/static/openbsd/man4/ac97.4 @@ -0,0 +1,76 @@ +.\" $OpenBSD: ac97.4,v 1.18 2010/02/26 14:14:14 sobrado Exp $ +.\" +.\" Copyright (c) 1999, 2000 Constantine Sapuntzakis +.\" +.\" Author: Constantine Sapuntzakis +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote +.\" products derived from this software without specific prior written +.\" permission. +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHORS ``AS IS'' AND ANY EXPRESS +.\" OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE +.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT +.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR +.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF +.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE +.\" USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH +.\" DAMAGE. +.\" +.Dd $Mdocdate: February 26 2010 $ +.Dt AC97 4 +.Os +.Sh NAME +.Nm ac97 +.Nd generic AC'97 codec driver +.Sh DESCRIPTION +AC'97 codecs contain the analog to digital (A/D), digital to analog +(D/A), and mixing circuitry of many modern sound cards. +AC'97 codecs, for the most part, do not talk to host buses like the PCI bus +directly. +Instead, they communicate through an interface chip, called +the host controller. +The Ensoniq AudioPCI 97 (see +.Xr eap 4 ) +is an example of such a host controller. +.Pp +Unlike many drivers, the +.Nm +driver does not appear in the configuration file. +Instead, the driver is automatically attached by the drivers that require it. +.Sh SEE ALSO +.Xr auacer 4 , +.Xr auich 4 , +.Xr auixp 4 , +.Xr autri 4 , +.Xr auvia 4 , +.Xr clcs 4 , +.Xr clct 4 , +.Xr eap 4 , +.Xr emu 4 , +.Xr esa 4 , +.Xr fms 4 , +.Xr maestro 4 , +.Xr neo 4 , +.Xr yds 4 +.Sh BUGS +The +.Nm +driver does not keep track of the current user settings and instead +relies on the hardware to do this. +.Pp +The +.Nm +driver could do more to detect mixer channels that don't work and cull +them from the list. diff --git a/static/openbsd/man4/acphy.4 b/static/openbsd/man4/acphy.4 new file mode 100644 index 00000000..cd4ae6df --- /dev/null +++ b/static/openbsd/man4/acphy.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: acphy.4,v 1.7 2007/05/31 19:19:48 jmc Exp $ +.\" $NetBSD: acphy.4,v 1.3 2003/01/17 06:23:53 gendalia Exp $ +.\" +.\" Copyright 2001 Wasabi Systems, Inc. +.\" All rights reserved. +.\" +.\" Written by Jason R. Thorpe for Wasabi Systems, Inc. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed for the NetBSD Project by +.\" Wasabi Systems, Inc. +.\" 4. The name of Wasabi Systems, Inc. may not be used to endorse +.\" or promote products derived from this software without specific prior +.\" written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY WASABI SYSTEMS, INC. ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL WASABI SYSTEMS, INC +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt ACPHY 4 +.Os +.Sh NAME +.Nm acphy +.Nd Altima AC101 and AC101L 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "acphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Altima AC101 and AC101L +10/100 Ethernet PHYs. +These PHYs are often found on low-power Ethernet interfaces, +such as Mini PCI interfaces found in laptops and embedded systems. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/acpi.4 b/static/openbsd/man4/acpi.4 new file mode 100644 index 00000000..736d936c --- /dev/null +++ b/static/openbsd/man4/acpi.4 @@ -0,0 +1,186 @@ +.\" $OpenBSD: acpi.4,v 1.80 2026/04/13 01:09:07 jsg Exp $ +.\" +.\" Copyright (c) 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 13 2026 $ +.Dt ACPI 4 +.Os +.Sh NAME +.Nm acpi +.Nd Advanced Configuration and Power Interface +.Sh SYNOPSIS +.Cd "acpi0 at bios?" +.Sh DESCRIPTION +The +.Nm +driver provides basic support for ACPI including loading ACPI tables from +the firmware, parsing and interpreting AML code, event handling, +suspending and powering off, and attaching device drivers. +Userland may access +.Nm +by using the +.Xr apm 4 +device. +.Pp +The following devices can attach to +.Nm : +.Pp +.Bl -tag -width "acpithinkpad(4)XXX" -offset indent -compact +.It Xr abl 4 +Apple backlight support +.It Xr acpiac 4 +ACPI AC adapter +.It Xr acpials 4 +ACPI ambient light sensor +.It Xr acpiasus 4 +ASUS ACPI hotkeys +.It Xr acpibat 4 +ACPI control method battery +.It Xr acpibtn 4 +ACPI button +.It Xr acpicbkbd 4 +Chromebook keyboard backlight +.It Xr acpicmos 4 +CMOS memory manager +.It Xr acpicpu 4 +ACPI processor power and performance state +.It Xr acpidock 4 +ACPI docking station +.It Xr acpiec 4 +ACPI embedded controller +.It Xr acpige 4 +ACPI generic event device +.It Xr acpihid 4 +ACPI HID event and 5-button array +.It Xr acpihpet 4 +ACPI high precision event timer +.It Xr acpihve 4 +Hyper-V entropy +.It Xr acpimadt 4 +ACPI APIC configuration +.It Xr acpimcfg 4 +ACPI PCI Express configuration space +.It Xr acpipci 4 +ACPI PCI host bridge +.It Xr acpiprt 4 +ACPI PCI routing table configuration +.It Xr acpipwrres 4 +ACPI power resources +.It Xr acpisbs 4 +ACPI Smart Battery subsystem +.It Xr acpisony 4 +Sony ACPI control +.It Xr acpisurface 4 +Microsoft Surface Book ACPI support +.It Xr acpithinkpad 4 +IBM/Lenovo ThinkPad ACPI support +.It Xr acpitimer 4 +ACPI power management timer +.It Xr acpitoshiba 4 +Toshiba ACPI support +.It Xr acpitz 4 +ACPI thermal zone +.It Xr acpivideo 4 +ACPI video +.It Xr acpivout 4 +ACPI video output +.It Xr acpiwmi 4 +ACPI WMI interface +.It Xr ahci 4 +Advanced Host Controller Interface for Serial ATA +.It Xr aibs 4 +ASUSTeK AI Booster ACPI ATK0110 temperature, voltage, and fan sensor +.It Xr amdgpio 4 +AMD GPIO controller +.It Xr amdpmc 4 +AMD power management controller +.It Xr ampchwm 4 +Ampere Altra fine-grained power telemetry +.It Xr aplgpio 4 +Intel Apollo Lake GPIO controller +.It Xr asmc 4 +Apple System Management Controller (SMC) +.It Xr bse 4 +Broadcom GENET 10/100/1Gb Ethernet device +.It Xr bytgpio 4 +Intel Bay Trail GPIO controller +.It Xr ccp 4 +AMD cryptographic co-processor +.It Xr chvgpio 4 +Intel Cherry View GPIO controller +.It Xr dwgpio 4 +Synopsys DesignWare GPIO controller +.It Xr dwiic 4 +Synopsys DesignWare I2C controller +.It Xr glkgpio 4 +Intel Gemini Lake GPIO controller +.It Xr imxiic 4 +i.MX onboard I2C controller +.It Xr intelpmc 4 +Intel power management controller +.It Xr inthid 4 +Intel HID event and 5-button array devices +.It Xr iosf 4 +Intel OnChip System Fabric device +.It Xr ipmi 4 +Intelligent Platform Management Interface driver +.It Xr ispi 4 +Intel LPSS SPI controller +.It Xr pchgpio 4 +Intel PCH GPIO controller +.It Xr pckbc 4 +Keyboard controller +.It Xr pluart 4 +ARM PrimeCell PL011 UART +.It Xr qcgpio 4 +Qualcomm Snapdragon GPIO controller +.It Xr qciic 4 +Qualcomm Snapdragon GENI I2C controller +.It Xr sdhc 4 +SD Host Controller +.It Xr tpm 4 +Trusted Platform Module device +.It Xr ufshci 4 +Universal Flash Storage Host Controller Interface +.El +.Sh FILES +.Bl -tag -width "/dev/apmctlXXX" +.It /dev/apm +Power management data device. +May only be opened read-only. +May be opened by multiple concurrent users. +.It /dev/apmctl +Power management control device. +May be opened read-write or write-only. +May only be opened by one user at a time. +An attempt to open the file when in use will fail, returning +.Er EBUSY . +.El +.Sh SEE ALSO +.Xr apm 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Thorsten Lockert Aq Mt tholo@sigmasoft.com +and +.An Jordan Hargrave Aq Mt jordan@openbsd.org . diff --git a/static/openbsd/man4/acpiac.4 b/static/openbsd/man4/acpiac.4 new file mode 100644 index 00000000..86404585 --- /dev/null +++ b/static/openbsd/man4/acpiac.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: acpiac.4,v 1.7 2014/12/10 07:36:38 jmc Exp $ +.\" +.\" Copyright (c) 2006 Dmitri Alenitchev +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 10 2014 $ +.Dt ACPIAC 4 +.Os +.Sh NAME +.Nm acpiac +.Nd ACPI AC adapter +.Sh SYNOPSIS +.Cd "acpiac* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver supports ACPI AC Adapters. +Information about AC power source status (connected or disconnected) is +available through this driver as a sensor. +AC power source status is updated +via an event when a change happens, +if the implementation supports it. +The sensors provided by +.Nm +can be monitored using +.Xr sysctl 8 +or +.Xr sensorsd 8 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marco Peereboom Aq Mt marco@openbsd.org . diff --git a/static/openbsd/man4/acpials.4 b/static/openbsd/man4/acpials.4 new file mode 100644 index 00000000..55d8d7f7 --- /dev/null +++ b/static/openbsd/man4/acpials.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: acpials.4,v 1.1 2016/07/30 16:25:04 jcs Exp $ +.\" +.\" Copyright (c) 2016 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 30 2016 $ +.Dt ACPIALS 4 +.Os +.Sh NAME +.Nm acpials +.Nd ACPI ambient light sensor +.Sh SYNOPSIS +.Cd "acpials* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver supports ACPI ambient light sensor devices and provides +information about the ambient light environment in which the system is +currently operating. +Ambient light illuminance is read every second and can be monitored +using +.Xr sysctl 8 +or +.Xr sensorsd 8 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . diff --git a/static/openbsd/man4/acpiasus.4 b/static/openbsd/man4/acpiasus.4 new file mode 100644 index 00000000..b8136d54 --- /dev/null +++ b/static/openbsd/man4/acpiasus.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: acpiasus.4,v 1.2 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Joel Sing (jsing@openbsd.org) +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ACPIASUS 4 +.Os +.Sh NAME +.Nm acpiasus +.Nd ASUS ACPI hotkeys +.Sh SYNOPSIS +.Cd "acpiasus* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ACPI based hotkeys found in many ASUS laptops, +including the ASUS EeePC. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by Jared D. McNeill and was ported to +.Ox +by +.An Joel Sing Aq Mt jsing@openbsd.org . diff --git a/static/openbsd/man4/acpibat.4 b/static/openbsd/man4/acpibat.4 new file mode 100644 index 00000000..52155a70 --- /dev/null +++ b/static/openbsd/man4/acpibat.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: acpibat.4,v 1.8 2017/03/30 16:04:36 jcs Exp $ +.\" +.\" Copyright (c) 2006 Dmitri Alenitchev +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 30 2017 $ +.Dt ACPIBAT 4 +.Os +.Sh NAME +.Nm acpibat +.Nd ACPI control method battery +.Sh SYNOPSIS +.Cd "acpibat* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver supports the ACPI Control Method Battery interface between the +battery and the host. +Information about the battery, such as capacity, recharge rate, voltage, +and serial number, is available through this driver. +Battery status is updated through an event triggered when a battery +changes state (such as starting to charge) and, as a failsafe if the +system does not support passing such events, every 10 seconds. +Battery status can be monitored using +.Xr sysctl 8 +or +.Xr sensorsd 8 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr acpisbs 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marco Peereboom Aq Mt marco@openbsd.org . +.Sh BUGS +Some systems do not propagate battery insertion up to the driver. diff --git a/static/openbsd/man4/acpibtn.4 b/static/openbsd/man4/acpibtn.4 new file mode 100644 index 00000000..55049022 --- /dev/null +++ b/static/openbsd/man4/acpibtn.4 @@ -0,0 +1,91 @@ +.\" $OpenBSD: acpibtn.4,v 1.6 2021/09/03 12:11:15 kn Exp $ +.\" +.\" Copyright (c) 2006 Michael Knudsen +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 3 2021 $ +.Dt ACPIBTN 4 +.Os +.Sh NAME +.Nm acpibtn +.Nd ACPI button +.Sh SYNOPSIS +.Cd "acpibtn* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver handles events triggered by ACPI buttons. +Currently, only power button, sleep button and lid status events are supported. +.Pp +The power button event is handled according to the +.Va machdep.pwraction +.Xr sysctl 8 . +Valid values are: +.Pp +.Bl -tag -width 3n -offset indent -compact +.It 0 +Do nothing. +.It 1 +Perform a regular system shutdown and power off the machine if the +.Va hw.allowpowerdown +sysctl is set to 1. +.It 2 +Put the system into suspend (deep sleep) state. +.El +.Pp +The sleep button event puts the system into suspend (deep sleep) state. +.Pp +The lid status event is handled according to the +.Va machdep.lidaction +sysctl. +Valid values are: +.Pp +.Bl -tag -width 3n -offset indent -compact +.It 0 +Do nothing. +.It 1 +Put the system into suspend (deep sleep) state. +.It 2 +Put the system into hibernation. +System memory is saved to disk (swap space) +and the machine is powered down. +For machines supporting the +.Xr acpi 4 +style hibernate functionality, on resume a full kernel +boot will occur, followed by the reading of the saved +memory image. +The image will then be unpacked and the system resumed +at the point immediately after the hibernation request. +.El +.Pp +The lid status is set up as a sensor and can be monitored using +.Xr sysctl 8 +or +.Xr sensorsd 8 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marco Peereboom Aq Mt marco@openbsd.org . diff --git a/static/openbsd/man4/acpicbkbd.4 b/static/openbsd/man4/acpicbkbd.4 new file mode 100644 index 00000000..6abb8526 --- /dev/null +++ b/static/openbsd/man4/acpicbkbd.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: acpicbkbd.4,v 1.1 2016/08/23 18:39:08 jcs Exp $ +.\" +.\" Copyright (c) 2016 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 23 2016 $ +.Dt ACPICBKBD 4 +.Os +.Sh NAME +.Nm acpicbkbd +.Nd Chromebook keyboard backlight +.Sh SYNOPSIS +.Cd "acpicbkbd* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver enables adjustment of the keyboard backlight level on Chromebook +laptops with supported hardware. +Backlight levels can be retrieved and modified with the +.Xr wsconsctl 8 +variable +.Va keyboard.backlight . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr wsconsctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . diff --git a/static/openbsd/man4/acpicmos.4 b/static/openbsd/man4/acpicmos.4 new file mode 100644 index 00000000..8314aa22 --- /dev/null +++ b/static/openbsd/man4/acpicmos.4 @@ -0,0 +1,36 @@ +.\" $OpenBSD: acpicmos.4,v 1.1 2024/11/05 11:12:48 miod Exp $ +.\" +.\" Copyright (c) 2024, Miodrag Vallat. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 5 2024 $ +.Dt ACPICMOS 4 +.Os +.Sh NAME +.Nm acpicmos +.Nd CMOS memory manager +.Sh SYNOPSIS +.Cd "acpicmos* at acpi?" Pq "i386 and amd64" +.Sh DESCRIPTION +The +.Nm +driver handles CMOS memory access requests for all ACPI operations. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . diff --git a/static/openbsd/man4/acpicpu.4 b/static/openbsd/man4/acpicpu.4 new file mode 100644 index 00000000..e7e68682 --- /dev/null +++ b/static/openbsd/man4/acpicpu.4 @@ -0,0 +1,75 @@ +.\" $OpenBSD: acpicpu.4,v 1.10 2022/10/21 04:02:16 guenther Exp $ +.\" +.\" Copyright (c) 2006 Michael Knudsen +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 21 2022 $ +.Dt ACPICPU 4 +.Os +.Sh NAME +.Nm acpicpu +.Nd ACPI processor power and performance state +.Sh SYNOPSIS +.Cd "acpicpu* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for extracting processor power and performance +levels from ACPI tables. +This information is used to enter deeper CPU power states when idle, +and can be used to throttle processor speed to reduce +power usage and extend battery life through the +.Va hw.setperf +.Xr sysctl 2 +mechanism. +.Pp +.Nm +reports the C-states offered by ACPI using the format +.Dl C%d(%d@%d %s.%x@%#x) +where the respective fields are the ACPI state, +the reported power consumption, +the reported latency, +the method, +the flags on the method, +and the address for the method. +Inapplicable or unspecified fields are elided. +If the state won't be used for any reason then the entry will have a +.Sq !\& +prefix. +If the state is the fallback state used when no valid C-state entries were +found then flags will be a +.Sq !\& . +For the +.Va mwait +method the address is the hints value for the instruction. +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr acpi 4 , +.Xr cpu 4 , +.Xr intro 4 , +.Xr apmd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marco Peereboom Aq Mt marco@openbsd.org . +CPU power state (C-state) support was added by +.An Philip Guenther Aq Mt guenther@openbsd.org . diff --git a/static/openbsd/man4/acpidock.4 b/static/openbsd/man4/acpidock.4 new file mode 100644 index 00000000..b2254dfb --- /dev/null +++ b/static/openbsd/man4/acpidock.4 @@ -0,0 +1,63 @@ +.\" $OpenBSD: acpidock.4,v 1.5 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2007 Michael Knudsen +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ACPIDOCK 4 +.Os +.Sh NAME +.Nm acpidock +.Nd ACPI docking station +.Sh SYNOPSIS +.Cd "acpidock* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver supports ACPI docking stations. +Docking stations are units that, for example, laptops may attach to in +order to expose a number of additional hardware devices. +The +.Nm +driver handles docking and undocking machines to gracefully detach +external devices. +.Pp +When docking and undocking, an event is passed to the driver which is +then reacted upon. +For undocking, this event is usually triggered by pressing a button on +the docking station or using a special keyboard combination; for docking, +the machine usually just has to be inserted. +.Pp +The +.Nm +driver sets up a sensor that indicates docking state that can be +used with +.Xr sensorsd 8 +to perform events when docking or undocking. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr sensorsd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Michael Knudsen Aq Mt mk@openbsd.org . diff --git a/static/openbsd/man4/acpiec.4 b/static/openbsd/man4/acpiec.4 new file mode 100644 index 00000000..651177d2 --- /dev/null +++ b/static/openbsd/man4/acpiec.4 @@ -0,0 +1,54 @@ +.\" $OpenBSD: acpiec.4,v 1.5 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Dmitri Alenitchev +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ACPIEC 4 +.Os +.Sh NAME +.Nm acpiec +.Nd ACPI embedded controller +.Sh SYNOPSIS +.Cd "acpiec* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver supports ACPI Embedded Controllers. +It provides embedded controller access for other ACPI devices. +On many systems +which have an +.Nm +device, other ACPI devices such as +.Xr acpiac 4 , +.Xr acpibat 4 , +and +.Xr acpitz 4 +implicitly depend on the +.Nm +device. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Can Erkin Acar Aq Mt canacar@openbsd.org . diff --git a/static/openbsd/man4/acpige.4 b/static/openbsd/man4/acpige.4 new file mode 100644 index 00000000..98268b50 --- /dev/null +++ b/static/openbsd/man4/acpige.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: acpige.4,v 1.1 2020/11/15 18:04:10 patrick Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 15 2020 $ +.Dt ACPIGE 4 +.Os +.Sh NAME +.Nm acpige +.Nd ACPI generic event device +.Sh SYNOPSIS +.Cd "acpige* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver reacts to external events and notifies the corresponding handler. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/acpihid.4 b/static/openbsd/man4/acpihid.4 new file mode 100644 index 00000000..85eeb737 --- /dev/null +++ b/static/openbsd/man4/acpihid.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: acpihid.4,v 1.4 2026/01/10 16:20:42 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 10 2026 $ +.Dt ACPIHID 4 +.Os +.Sh NAME +.Nm acpihid +.Nd ACPI generic buttons device +.Sh SYNOPSIS +.Cd "acpihid* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver handles events triggered by the ACPI generic buttons device. +Currently only power button events are supported. +.Sh SEE ALSO +.Xr acpi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/acpihpet.4 b/static/openbsd/man4/acpihpet.4 new file mode 100644 index 00000000..b03fde77 --- /dev/null +++ b/static/openbsd/man4/acpihpet.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: acpihpet.4,v 1.6 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ACPIHPET 4 +.Os +.Sh NAME +.Nm acpihpet +.Nd ACPI high precision event timer +.Sh SYNOPSIS +.Cd "acpihpet* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the high precision event timer to be used +as a timecounter for the +.Xr tc_init 9 +framework. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr tc_init 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Thorsten Lockert Aq Mt tholo@sigmasoft.com . diff --git a/static/openbsd/man4/acpihve.4 b/static/openbsd/man4/acpihve.4 new file mode 100644 index 00000000..d251e212 --- /dev/null +++ b/static/openbsd/man4/acpihve.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: acpihve.4,v 1.2 2018/04/28 15:44:59 jasper Exp $ +.\" +.\" Copyright (c) 2017 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 28 2018 $ +.Dt ACPIHVE 4 +.Os +.Sh NAME +.Nm acpihve +.Nd Hyper-V entropy +.Sh SYNOPSIS +.Cd "acpihve* at acpi?" +.Sh DESCRIPTION +Hyper-V hosts make entropy available to guests in the OEM0 ACPI table. +The +.Nm +driver feeds this entropy into the kernel's entropy pool. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr enqueue_randomness 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . diff --git a/static/openbsd/man4/acpimadt.4 b/static/openbsd/man4/acpimadt.4 new file mode 100644 index 00000000..f13d26c8 --- /dev/null +++ b/static/openbsd/man4/acpimadt.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: acpimadt.4,v 1.5 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Michael Knudsen +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ACPIMADT 4 +.Os +.Sh NAME +.Nm acpimadt +.Nd ACPI APIC configuration +.Sh SYNOPSIS +.Cd "acpimadt* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver configures system processors and I/O APICs based on information +extracted from the ACPI APIC table. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr cpu 4 , +.Xr intro 4 , +.Xr ioapic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/acpimcfg.4 b/static/openbsd/man4/acpimcfg.4 new file mode 100644 index 00000000..e4f052a3 --- /dev/null +++ b/static/openbsd/man4/acpimcfg.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: acpimcfg.4,v 1.1 2014/02/02 10:18:36 kettenis Exp $ +.\" +.\" Copyright (c) 2014 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 2 2014 $ +.Dt ACPIMCFG 4 +.Os +.Sh NAME +.Nm acpimcfg +.Nd ACPI PCI Express configuration space +.Sh SYNOPSIS +.Cd "acpimcfg* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver configures access to PCI Express configuration space based on +information extracted from the ACPI MCFG table. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/acpipci.4 b/static/openbsd/man4/acpipci.4 new file mode 100644 index 00000000..5f71ce45 --- /dev/null +++ b/static/openbsd/man4/acpipci.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: acpipci.4,v 1.2 2019/04/02 19:39:32 jmc Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 2 2019 $ +.Dt ACPIPCI 4 +.Os +.Sh NAME +.Nm acpipci +.Nd ACPI PCI host bridge +.Sh SYNOPSIS +.Cd "acpipci* at acpi?" +.Cd "pci* at acpipci?" Pq arm64 +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI host bridges based on the information +extracted from the ACPI DSDT and SSDT tables. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/acpiprt.4 b/static/openbsd/man4/acpiprt.4 new file mode 100644 index 00000000..fa8c38fe --- /dev/null +++ b/static/openbsd/man4/acpiprt.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: acpiprt.4,v 1.5 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2007 Michael Knudsen +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ACPIPRT 4 +.Os +.Sh NAME +.Nm acpiprt +.Nd ACPI PCI routing table configuration +.Sh SYNOPSIS +.Cd "acpiprt* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides interrupt mapping information for PCI devices based on +information from ACPI PCI Routing Table objects. +Typically there is one PCI Routing Table object for every PCI bus in +the system, each handled by a separate +.Nm +device. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/acpipwrres.4 b/static/openbsd/man4/acpipwrres.4 new file mode 100644 index 00000000..4e022bb3 --- /dev/null +++ b/static/openbsd/man4/acpipwrres.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: acpipwrres.4,v 1.3 2020/04/06 00:01:08 pirofti Exp $ +.\" +.\" Copyright (c) 2009 Paul Irofti +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: April 6 2020 $ +.Dt ACPIPWRRES 4 +.Os +.Sh NAME +.Nm acpipwrres +.Nd ACPI power resources +.Sh SYNOPSIS +.Cd "acpipwrres* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ACPI power resources management. +A power resource refers to a software-controllable power plane, clock plane or +other resource upon which an integrated ACPI power-managed device might rely. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Paul Irofti Aq Mt paul@irofti.net . diff --git a/static/openbsd/man4/acpisbs.4 b/static/openbsd/man4/acpisbs.4 new file mode 100644 index 00000000..7c7d4151 --- /dev/null +++ b/static/openbsd/man4/acpisbs.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: acpisbs.4,v 1.1 2017/03/30 16:04:36 jcs Exp $ +.\" +.\" Copyright (c) 2017 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 30 2017 $ +.Dt ACPISBS 4 +.Os +.Sh NAME +.Nm acpisbs +.Nd ACPI Smart Battery subsystem +.Sh SYNOPSIS +.Cd "acpisbs* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver supports the ACPI Smart Battery subsystem and provides +information about the Smart Battery devices contained within it. +Battery status is updated every 30 seconds, as well as in response +to events from the subsystem. +Battery status can be monitored using +.Xr sysctl 8 +or +.Xr sensorsd 8 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr acpibat 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . +.Sh CAVEATS +The +.Nm +driver does not currently support more than one battery. diff --git a/static/openbsd/man4/acpisony.4 b/static/openbsd/man4/acpisony.4 new file mode 100644 index 00000000..c56479b0 --- /dev/null +++ b/static/openbsd/man4/acpisony.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: acpisony.4,v 1.5 2020/04/06 00:01:08 pirofti Exp $ +.\" +.\" Copyright (c) 2010 Paul Irofti +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: April 6 2020 $ +.Dt ACPISONY 4 +.Os +.Sh NAME +.Nm acpisony +.Nd Sony ACPI control +.Sh SYNOPSIS +.Cd "acpisony* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ACPI based hotkeys found in many Sony laptops. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Paul Irofti Aq Mt paul@irofti.net . diff --git a/static/openbsd/man4/acpisurface.4 b/static/openbsd/man4/acpisurface.4 new file mode 100644 index 00000000..801c3fbd --- /dev/null +++ b/static/openbsd/man4/acpisurface.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: acpisurface.4,v 1.2 2018/07/01 05:47:16 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mike Larkin +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 1 2018 $ +.Dt ACPISURFACE 4 +.Os +.Sh NAME +.Nm acpisurface +.Nd Microsoft Surface Book ACPI support +.Sh SYNOPSIS +.Cd "acpisurface* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides ACPI support for Microsoft Surface Book laptops. +It responds to various button presses such as volume up/down and power +buttons, all of which are located on the top of the tablet/detachable display. +It does not provide support for the hotkeys in the keyboard/base unit. +.Pp +Volume up/down button presses are routed to the master system mixer via the +.Xr wscons 4 +subsystem. +Power button presses result in a soft power off request being queued by the +.Xr acpi 4 +subsystem. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr audio 4 , +.Xr wscons 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . diff --git a/static/openbsd/man4/acpithinkpad.4 b/static/openbsd/man4/acpithinkpad.4 new file mode 100644 index 00000000..8faba7b8 --- /dev/null +++ b/static/openbsd/man4/acpithinkpad.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: acpithinkpad.4,v 1.5 2018/05/22 06:29:53 jmc Exp $ +.\" +.\" Copyright (c) 2008 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 22 2018 $ +.Dt ACPITHINKPAD 4 +.Os +.Sh NAME +.Nm acpithinkpad +.Nd IBM/Lenovo ThinkPad ACPI support +.Sh SYNOPSIS +.Cd "acpithinkpad* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides ACPI support for IBM/Lenovo ThinkPad laptops. +It responds to various hotkey button presses such as the brightness adjustment +and wireless toggle keys. +.Pp +The +.Nm +driver sets up various sensors that indicate the current state of +certain hardware devices present on ThinkPad laptops. +These include temperature sensors and fan rotational speed sensors, as well as a +sensor indicating the current state of the port replicator device. +These sensors can be used with +.Xr sensorsd 8 +to perform events on sensor state changes. +Note that the port replicator indicator will report a state of UNKNOWN +until the first port replicator connect/disconnect event is received. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr sensorsd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . diff --git a/static/openbsd/man4/acpitimer.4 b/static/openbsd/man4/acpitimer.4 new file mode 100644 index 00000000..4e00f687 --- /dev/null +++ b/static/openbsd/man4/acpitimer.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: acpitimer.4,v 1.7 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ACPITIMER 4 +.Os +.Sh NAME +.Nm acpitimer +.Nd ACPI power management timer +.Sh SYNOPSIS +.Cd "acpitimer* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver allows access to a power management timer through ACPI. +The timer is used as a timecounter for the +.Xr tc_init 9 +framework. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr tc_init 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Thorsten Lockert Aq Mt tholo@sigmasoft.com . diff --git a/static/openbsd/man4/acpitoshiba.4 b/static/openbsd/man4/acpitoshiba.4 new file mode 100644 index 00000000..870242bf --- /dev/null +++ b/static/openbsd/man4/acpitoshiba.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: acpitoshiba.4,v 1.4 2020/04/06 00:01:08 pirofti Exp $ +.\" +.\" Copyright (c) 2011 Paul Irofti +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: April 6 2020 $ +.Dt ACPITOSHIBA 4 +.Os +.Sh NAME +.Nm acpitoshiba +.Nd Toshiba ACPI support +.Sh SYNOPSIS +.Cd "acpitoshiba* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides ACPI support for Toshiba laptops. +It supports output switching and brightness adjustment. +Brightness can be adjusted either using a brightness hotkey or the +.Xr wsconsctl 8 +variable +.Va display.brightness , +while output switching is achieved only through the hotkey. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Hiroyuki Aizu Aq Mt aizu@navi.org . diff --git a/static/openbsd/man4/acpitz.4 b/static/openbsd/man4/acpitz.4 new file mode 100644 index 00000000..c1148241 --- /dev/null +++ b/static/openbsd/man4/acpitz.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: acpitz.4,v 1.6 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Dmitri Alenitchev +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ACPITZ 4 +.Os +.Sh NAME +.Nm acpitz +.Nd ACPI thermal zone +.Sh SYNOPSIS +.Cd "acpitz* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver supports ACPI Thermal Zones. +Temperature information is available through this driver as a sensor +which is updated every 10 seconds or, if the implementation supports it, +via an event. +If the temperature exceeds the +.Sq critical +temperature threshold, the system will be shut down and powered off. +The sensor provided by +.Nm +can be monitored using +.Xr sysctl 8 +or +.Xr sensorsd 8 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Can Erkin Acar Aq Mt canacar@openbsd.org . diff --git a/static/openbsd/man4/acpivideo.4 b/static/openbsd/man4/acpivideo.4 new file mode 100644 index 00000000..92d75cae --- /dev/null +++ b/static/openbsd/man4/acpivideo.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: acpivideo.4,v 1.6 2020/04/06 00:01:08 pirofti Exp $ +.\" +.\" Copyright (c) 2009 Paul Irofti +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: April 6 2020 $ +.Dt ACPIVIDEO 4 +.Os +.Sh NAME +.Nm acpivideo +.Nd ACPI video +.Sh SYNOPSIS +.Cd "acpivideo* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver supports ACPI display output switching and brightness control. +Output displays can take the form of CRTs, LCDs, TV-OUTs or any similar devices +that may be connected to the machine. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr acpithinkpad 4 , +.Xr acpitoshiba 4 , +.Xr acpivout 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Federico G. Schwindt Aq Mt fgsch@openbsd.org +and +.An Paul Irofti Aq Mt paul@irofti.net . +.Sh CAVEATS +On IBM and Lenovo ThinkPad systems, +.Nm +functionality is handled by the +.Xr acpithinkpad 4 +driver. diff --git a/static/openbsd/man4/acpivout.4 b/static/openbsd/man4/acpivout.4 new file mode 100644 index 00000000..46fc3e1a --- /dev/null +++ b/static/openbsd/man4/acpivout.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: acpivout.4,v 1.5 2020/04/06 00:01:08 pirofti Exp $ +.\" +.\" Copyright (c) 2009 Paul Irofti +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: April 6 2020 $ +.Dt ACPIVOUT 4 +.Os +.Sh NAME +.Nm acpivout +.Nd ACPI video output +.Sh SYNOPSIS +.Cd "acpivout* at acpivideo?" +.Sh DESCRIPTION +The +.Nm +driver supports brightness adjustment. +It allows brightness to be adjusted either using a brightness hotkey or the +.Xr wsconsctl 8 +variable +.Dq display.brightness . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr acpivideo 4 , +.Xr intro 4 , +.Xr wsconsctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Paul Irofti Aq Mt paul@irofti.net . diff --git a/static/openbsd/man4/acpiwmi.4 b/static/openbsd/man4/acpiwmi.4 new file mode 100644 index 00000000..86b0b957 --- /dev/null +++ b/static/openbsd/man4/acpiwmi.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: acpiwmi.4,v 1.1 2025/05/19 19:56:33 tedu Exp $ +.\" +.\" Copyright (c) 2025 Ted Unangst +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 19 2025 $ +.Dt ACPIWMI 4 +.Os +.Sh NAME +.Nm acpiwmi +.Nd ACPI WMI interface +.Sh SYNOPSIS +.Cd "acpiwmi* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Windows Management Instrumentation, or WMI. +Currently hotkeys found on some ASUS machines are supported. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.8 . diff --git a/static/openbsd/man4/acrtc.4 b/static/openbsd/man4/acrtc.4 new file mode 100644 index 00000000..2e9cf95e --- /dev/null +++ b/static/openbsd/man4/acrtc.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: acrtc.4,v 1.3 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" Copyright (c) 2017 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt ACRTC 4 +.Os +.Sh NAME +.Nm acrtc +.Nd X-Powers AC100 audio codec and real-time clock +.Sh SYNOPSIS +.Cd "acrtc* at rsb?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the X-Powers AC100 audio codec and RTC +subsystem. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sxirsb 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +.Sh BUGS +Support for the audio codec functionality is missing. diff --git a/static/openbsd/man4/acx.4 b/static/openbsd/man4/acx.4 new file mode 100644 index 00000000..4dee8ea9 --- /dev/null +++ b/static/openbsd/man4/acx.4 @@ -0,0 +1,209 @@ +.\" $OpenBSD: acx.4,v 1.50 2022/01/05 17:39:24 jmc Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt. +.\" Copyright (c) 2006 The DragonFly Project. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in +.\" the documentation and/or other materials provided with the +.\" distribution. +.\" 3. Neither the name of The DragonFly Project nor the names of its +.\" contributors may be used to endorse or promote products derived +.\" from this software without specific, prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +.\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE +.\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT +.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 5 2022 $ +.Dt ACX 4 +.Os +.Sh NAME +.Nm acx +.Nd TI ACX100/ACX111 IEEE 802.11a/b/g wireless network device +.Sh SYNOPSIS +.Cd "acx* at cardbus?" +.Cd "acx* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for TI TNETW1100/TNETW1100B (ACX100) and +TNETW1130 (ACX111) based PCI/CardBus network adapters. +.Pp +The ACX100A and ACX100B are first generation 802.11b devices +from TI. +The ACX111 is a second generation device which supports 802.11b/g +and in some cases 802.11a. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.It Host AP +In this mode the driver acts as an access point (base station) +for other cards. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) +in software for ACX111 +or in hardware for ACX100. +It is strongly recommended that WEP +not be used as the sole mechanism +to secure wireless communication, +due to serious weaknesses in it. +.Pp +The transmit speed is user-selectable or can be adapted automatically by the +driver depending on the number of hardware transmission retries. +.Pp +In Host AP mode, +the driver is compatible with clients using powersave. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs a set of firmware files which are loaded when +an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/tiacx100 +.It Pa /etc/firmware/tiacx100r0D +.It Pa /etc/firmware/tiacx100r11 +.It Pa /etc/firmware/tiacx111 +.It Pa /etc/firmware/tiacx111c16 +.It Pa /etc/firmware/tiacx111r16 +.El +.Pp +These firmware files are not free because TI refuses +to grant distribution rights. +In fact they have rebuffed thousands +of attempts to start a dialogue on this issue. +As a result, even though +.Ox +includes the driver, the firmware files cannot be included and +users have to download these files on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh HARDWARE +The following cards are among those supported by the +.Nm +driver: +.Bl -column "Microcom Travelcard" "ACX111" "CardBus" "Standard" -offset 6n +.It Em Card Ta Em Chip Ta Em Bus Ta Em Standard +.It "D-Link DWL-520+" Ta ACX100 Ta PCI Ta b +.It "D-Link DWL-650+" Ta ACX100 Ta CardBus Ta b +.It "D-Link DWL-G520+" Ta ACX111 Ta PCI Ta b/g +.It "D-Link DWL-G630+" Ta ACX111 Ta CardBus Ta b/g +.It "D-Link DWL-G650+" Ta ACX111 Ta CardBus Ta b/g +.It "Digitus DN-7001G" Ta ACX111 Ta CardBus Ta b/g +.It "Ergenic ERG WL-003" Ta ACX100 Ta CardBus Ta b +.It "Hamlet HNWP254" Ta ACX111 Ta CardBus Ta b/g +.It "Hawking HWP54G" Ta ACX111 Ta PCI Ta b/g +.It "Linksys WPC54Gv2" Ta ACX111 Ta CardBus Ta b/g +.It "Microcom Travelcard" Ta ACX111 Ta CardBus Ta b/g +.It "Netgear WG311v2" Ta ACX111 Ta PCI Ta b/g +.It "Sceptre SC254W+" Ta ACX111 Ta CardBus Ta b/g +.It "Tornado/ADT 211g" Ta ACX111 Ta PCI Ta b/g +.It "USR USR5410" Ta ACX111 Ta CardBus Ta b/g +.It "USR USR5416" Ta ACX111 Ta PCI Ta b/g +.It "ZyXEL G-160" Ta ACX111 Ta CardBus Ta b/g +.It "ZyXEL G-360 EE" Ta ACX111 Ta PCI Ta b/g +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig acx0 scan +.Pp +The following +.Xr hostname.if 5 +example configures acx0 to join network +.Dq mynwid , +using WEP key +.Dq mywepkey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +nwid mynwid nwkey mywepkey +inet autoconf +.Ed +.Pp +The following +.Xr hostname.if 5 +example creates a host-based access point on boot: +.Bd -literal -offset indent +mediaopt hostap +nwid mynwid nwkey mywepkey +inet 192.168.1.1 255.255.255.0 +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr cardbus 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr hostapd 8 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Sepherosa Ziehau . +The manual page was written by +.An Sascha Wildner . +Both are based on the +.Lk http://wlan.kewl.org +project team's original code. +.Pp +The hardware specification was reverse engineered by the good folks at +.Lk http://acx100.sourceforge.net . +Without them this driver would not have been possible. diff --git a/static/openbsd/man4/adc.4 b/static/openbsd/man4/adc.4 new file mode 100644 index 00000000..bfd5eec6 --- /dev/null +++ b/static/openbsd/man4/adc.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: adc.4,v 1.5 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ADC 4 +.Os +.Sh NAME +.Nm adc +.Nd Analog Devices AD7416/AD7417/7418 temperature sensor +.Sh SYNOPSIS +.Cd "adc* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Analog Devices AD7416/AD7417/7418 +temperature sensor. +The sensor possesses at least an internal temperature sensor. +The AD7417 and 7418 also contain 4 additional ADC converters. +These values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/addcom.4 b/static/openbsd/man4/addcom.4 new file mode 100644 index 00000000..8140591a --- /dev/null +++ b/static/openbsd/man4/addcom.4 @@ -0,0 +1,87 @@ +.\" $OpenBSD: addcom.4,v 1.8 2008/05/21 19:05:51 kettenis Exp $ +.\" +.\" Copyright (c) 2001 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: May 21 2008 $ +.Dt ADDCOM 4 +.Os +.Sh NAME +.Nm addcom +.Nd multiplexing serial communications interface +.Sh SYNOPSIS +.Cd "addcom0 at isa? port 0x108 irq 5" +.Cd "com* at addcom?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Addonics FlexPort 8/S (and probably FlexPort 4/S) +boards that multiplex together up to eight (or four) +.Tn EIA +.Tn RS-232C +.Pf ( Tn CCITT +.Tn V.28 ) +communications interfaces. +.Pp +Each +.Nm +device is the master device for up to eight +.Nm com +devices. +The kernel configuration specifies these +.Nm com +devices as slave devices of the +.Nm +device, as shown in +.Sx SYNOPSIS . +The slave ID given for each +.Nm com +device determines which bit in the interrupt multiplexing register is +tested to find interrupts for that device. +The +.Tn port +specification for the +.Nm +device is used to compute the base addresses for the +.Nm com +subdevices. +The port for the interrupt multiplexing register is fixed, +so it is doubtful that more than one +.Nm +can be used in a machine. +.Sh FILES +.Bl -tag -width Pa +.It Pa /dev/tty?? +.El +.Sh SEE ALSO +.Xr com 4 , +.Xr intro 4 , +.Xr isa 4 +.Sh HISTORY +.Ox +support for +.Nm +devices first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/adl.4 b/static/openbsd/man4/adl.4 new file mode 100644 index 00000000..4983ea30 --- /dev/null +++ b/static/openbsd/man4/adl.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: adl.4,v 1.2 2012/07/12 20:12:02 jasper Exp $ +.\" +.\" Copyright (c) 2007 Mike Belopuhov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 12 2012 $ +.Dt ADL 4 +.Os +.Sh NAME +.Nm adl +.Nd Andigilog aSC7621 temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "adl* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Andigilog aSC7621 sensors. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mike Belopuhov . diff --git a/static/openbsd/man4/admcts.4 b/static/openbsd/man4/admcts.4 new file mode 100644 index 00000000..81367c10 --- /dev/null +++ b/static/openbsd/man4/admcts.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: admcts.4,v 1.3 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ADMCTS 4 +.Os +.Sh NAME +.Nm admcts +.Nd Analog Devices ADM1026 temperature and voltage sensor +.Sh SYNOPSIS +.Cd "admcts* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Analog Devices ADM1026 +temperature sensor. +The device possesses internal and external temperature sensors, +a variety of voltage sensors, plus fan RPM sensors. +These values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/admlc.4 b/static/openbsd/man4/admlc.4 new file mode 100644 index 00000000..0a840d85 --- /dev/null +++ b/static/openbsd/man4/admlc.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: admlc.4,v 1.3 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ADMLC 4 +.Os +.Sh NAME +.Nm admlc +.Nd Analog Devices ADM1024 temperature and voltage sensor +.Sh SYNOPSIS +.Cd "admlc* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Analog Devices ADM1024 +temperature sensor. +The device possesses internal and external temperature sensors, +a variety of voltage sensors, plus two fan RPM monitors. +These values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/admtemp.4 b/static/openbsd/man4/admtemp.4 new file mode 100644 index 00000000..8944b989 --- /dev/null +++ b/static/openbsd/man4/admtemp.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: admtemp.4,v 1.11 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ADMTEMP 4 +.Os +.Sh NAME +.Nm admtemp +.Nd Analog Devices ADM1021 temperature sensor +.Sh SYNOPSIS +.Cd "admtemp* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Analog Devices ADM1021, +Analog Devices ADM1023, Analog Devices ADM1032, Genesys Logic GL523SM, +Global Mixed-mode Technology G781, Maxim 1617, NXP SA56004x, +and Xeon embedded temperature sensors. +The device possesses internal and external temperature sensors. +These values are made available through the +.Xr sysctl 8 +interface. +.Pp +On i386 machines, this driver also supports the Xeon embedded +I2C temperature probes. +In this case, however, only one temperature value is provided. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/admtm.4 b/static/openbsd/man4/admtm.4 new file mode 100644 index 00000000..af589438 --- /dev/null +++ b/static/openbsd/man4/admtm.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: admtm.4,v 1.6 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ADMTM 4 +.Os +.Sh NAME +.Nm admtm +.Nd Analog Devices ADM1025 temperature and voltage sensor +.Sh SYNOPSIS +.Cd "admtm* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Analog Devices ADM1025, +SMSC 47m192, and Philips NE1619 temperature sensor. +The device possesses internal and external temperature sensors, +plus a variety of voltage sensors. +These values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/admtmp.4 b/static/openbsd/man4/admtmp.4 new file mode 100644 index 00000000..9fd7b1cc --- /dev/null +++ b/static/openbsd/man4/admtmp.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: admtmp.4,v 1.5 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ADMTMP 4 +.Os +.Sh NAME +.Nm admtmp +.Nd Analog Devices ADM1030 temperature sensor +.Sh SYNOPSIS +.Cd "admtmp* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Analog Devices ADM1030 +temperature sensor. +The device possesses internal and external temperature sensors, +plus a fan RPM monitor. +These values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/admtt.4 b/static/openbsd/man4/admtt.4 new file mode 100644 index 00000000..690ee25c --- /dev/null +++ b/static/openbsd/man4/admtt.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: admtt.4,v 1.6 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ADMTT 4 +.Os +.Sh NAME +.Nm admtt +.Nd Analog Devices ADM1031 temperature sensor +.Sh SYNOPSIS +.Cd "admtt* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Analog Devices ADM1031 +temperature sensor. +The device possesses an internal and two external temperature sensors, +plus two fan RPM monitors. +These values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/adt.4 b/static/openbsd/man4/adt.4 new file mode 100644 index 00000000..63e2b896 --- /dev/null +++ b/static/openbsd/man4/adt.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: adt.4,v 1.15 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ADT 4 +.Os +.Sh NAME +.Nm adt +.Nd Analog Devices ADT7460 temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "adt* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Analog Devices ADT7460, +Analog Devices ADT7465, Analog Devices ADT7475, +Analog Devices ADT7476, Analog Devices ADT7477, +Analog Devices ADM1027, National Semiconductor LM85, +National Semiconductor LM96000, SMSC EMC6D10x, +SMSC SCH5017 and SMC SCH5027 temperature sensors. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/adtfsm.4 b/static/openbsd/man4/adtfsm.4 new file mode 100644 index 00000000..ac800ee1 --- /dev/null +++ b/static/openbsd/man4/adtfsm.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: adtfsm.4,v 1.3 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ADTFSM 4 +.Os +.Sh NAME +.Nm adtfsm +.Nd Analog Devices ADT7462 temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "adtfsm* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Analog Devices ADT7462, +and family. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/adv.4 b/static/openbsd/man4/adv.4 new file mode 100644 index 00000000..31de1076 --- /dev/null +++ b/static/openbsd/man4/adv.4 @@ -0,0 +1,125 @@ +.\" $OpenBSD: adv.4,v 1.28 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 1998, Jason Downs. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt ADV 4 +.Os +.Sh NAME +.Nm adv , adw +.Nd AdvanSys PCI SCSI interface +.Sh SYNOPSIS +.Cd "adv* at pci?" +.Cd "adw* at pci?" +.Sh DESCRIPTION +The +.Nm adv +and +.Nm adw +drivers support most AdvanSys PCI SCSI host adapters, as shown in this +table: +.Bl -column "ABP-960U (2)" "ASB3940U2W-00" -offset indent +.It Sy adv Ta Sy adw +.It "ABP-920" Ta ABP-940UW +.It "ABP-930 (1)" Ta ABP-940UWD +.It "ABP-930U" Ta ABP-970UW +.It "ABP-930UA" Ta ASB-3940UW-00 +.It "ABP-940" Ta ASB-3940U2W-00 +.It "ABP-940U" Ta ASB-3950U160 +.It "ABP-940UA" Ta "" +.It "ABP-950" Ta "" +.It "ABP-960 (2)" Ta "" +.It "ABP-960U (2)" Ta "" +.It "ABP-970" Ta "" +.It "ABP-970U" Ta "" +.It "ABP-980" Ta "" +.It "ABP-980U" Ta "" +.El +.Pp +.Bl -enum -compact +.It +This board has been sold by SIIG as the Fast SCSI Pro PCI. +.It +This board has been sold by Iomega as a Jaz Jet PCI adapter. +.El +.Pp +The +.Nm adw +driver will log some host adapter errors with general messages such as +.Bd -literal -offset indent +adw0:0:0: host adapter error 0x12. See adw(4). +adw0:0:0: host adapter error 0x12, resetting bus. See adw(4). +.Ed +.Pp +Some further information on the meaning of such errors can be obtained +from the following table derived from the source code provided by +ConnectCom. +.Bl -column "Error" "QHSTA_M_SCSI_BUS_RESET_UNSOL" "Comment" +.It Em "Error" Ta Em "Define Name" Ta Em "Comment" +.It 0x12 Ta QHSTA_M_SXFR_XFR_OFLW Ta "SXFR_STATUS Transfer Overflow" +.It 0x13 Ta QHSTA_M_UNEXPECTED_BUS_FREE Ta "" +.It 0x15 Ta QHSTA_M_QUEUE_ABORTED Ta "" +.It 0x16 Ta QHSTA_M_SXFR_SDMA_ERR Ta "SXFR_STATUS SCSI DMA Error" +.It 0x17 Ta QHSTA_M_SXFR_SXFR_PERR Ta "SXFR_STATUS SCSI Bus Parity Error" +.It 0x18 Ta QHSTA_M_RDMA_PERR Ta "RISC PCI DMA parity error" +.It 0x19 Ta QHSTA_M_SXFR_OFF_UFLW Ta "SXFR_STATUS Offset Underflow" +.It 0x20 Ta QHSTA_M_SXFR_OFF_OFLW Ta "SXFR_STATUS Offset Overflow" +.It 0x21 Ta QHSTA_M_SXFR_WD_TMO Ta "SXFR_STATUS Watchdog Timeout" +.It 0x22 Ta QHSTA_M_SXFR_DESELECTED Ta "SXFR_STATUS Deselected" +.It 0x24 Ta QHSTA_M_SXFR_XFR_PH_ERR Ta "SXFR_STATUS Transfer Phase Error" +.It 0x25 Ta QHSTA_M_SXFR_UNKNOWN_ERROR Ta "SXFR_STATUS Unknown Error" +.It 0x30 Ta QHSTA_M_SCSI_BUS_RESET Ta "Request aborted from SBR" +.It 0x31 Ta QHSTA_M_SCSI_BUS_RESET_UNSOL Ta "Request aborted from unsolicited SBR" +.It 0x32 Ta QHSTA_M_BUS_DEVICE_RESET Ta "Request aborted from BDR" +.It 0x35 Ta QHSTA_M_DIRECTION_ERR Ta "Data Phase mismatch" +.It 0x36 Ta QHSTA_M_DIRECTION_ERR_HUNG Ta "Data Phase mismatch and bus hang" +.It 0x41 Ta QHSTA_M_WTM_TIMEOUT Ta "" +.It 0x42 Ta QHSTA_M_BAD_CMPL_STATUS_IN Ta "" +.It 0x43 Ta QHSTA_M_NO_AUTO_REQ_SENSE Ta "" +.It 0x44 Ta QHSTA_M_AUTO_REQ_SENSE_FAIL Ta "" +.It 0x45 Ta QHSTA_M_INVALID_DEVICE Ta "Bad target ID" +.It 0x46 Ta QHSTA_M_FROZEN_TIDQ Ta "TID Queue frozen" +.It 0x47 Ta QHSTA_M_SGBACKUP_ERROR Ta "Scatter-Gather backup error" +.El +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 +.Sh AUTHORS +The +.Nm adv +and +.Nm adw +drivers were originally written by +.An Baldassare Dante Profeta +for +.Nx , +based on Linux drivers written by Advanced System Products, +Inc., which is now ConnectCom Solutions, Inc. diff --git a/static/openbsd/man4/age.4 b/static/openbsd/man4/age.4 new file mode 100644 index 00000000..e4e43fae --- /dev/null +++ b/static/openbsd/man4/age.4 @@ -0,0 +1,83 @@ +.\" $OpenBSD: age.4,v 1.4 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2009 Kevin Lo +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt AGE 4 +.Os +.Sh NAME +.Nm age +.Nd Attansic L1 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "age* at pci?" +.Cd "atphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Ethernet interfaces based on the +Attansic L1 Ethernet chipset. +.Pp +The +.Nm +driver supports IPv4 receive IP/TCP/UDP checksum offload and VLAN +tag insertion and stripping. +.Pp +The following +.Ar media +types are supported: +.Pp +.Bl -tag -width autoselect -compact +.It Cm autoselect +Enable autoselection of the media type and options. +.It Cm 10baseT +Set 10Mbps operation. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.It Cm 1000baseT +Set 1000Mbps (Gigabit Ethernet) operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by the card, try +.Ic ifconfig media . +For example, +.Ic ifconfig age0 media . +.Sh SEE ALSO +.Xr arp 4 , +.Xr atphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Pyun YongHyeon +for +.Fx +and ported to +.Ox +by +.An Kevin Lo Aq Mt kevlo@openbsd.org . diff --git a/static/openbsd/man4/aggr.4 b/static/openbsd/man4/aggr.4 new file mode 100644 index 00000000..96a7c45b --- /dev/null +++ b/static/openbsd/man4/aggr.4 @@ -0,0 +1,102 @@ +.\" $OpenBSD: aggr.4,v 1.5 2026/03/17 05:18:29 deraadt Exp $ +.\" +.\" Copyright (c) 2019 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 17 2026 $ +.Dt AGGR 4 +.Os +.Sh NAME +.Nm aggr +.Nd IEEE 802.1AX Link Aggregation (LACP) network interface +.Sh SYNOPSIS +.Cd "pseudo-device aggr" +.Sh DESCRIPTION +The +.Nm +driver implements IEEE 802.1AX (formerly 802.3ad) Link Aggregation +for combining one or more Ethernet interfaces into a single logical +interface. +The Link Aggregation Control Protocol +.Va ( LACP ) +is used to negotiate the +aggregation of member interfaces with a partner device. +.Pp +.Nm +interfaces must be configured to use one or more Ethernet interfaces +as ports, and communicate with a partner device over those +ports using +.Va LACP . +Member interfaces that negotiate with a partner device are +aggregated into a single logical link. +Packets transmitted through an +.Nm +interface select an aggregated interface for transmission. +Packets received by an aggregated device appear to be received +by the +.Nm +interface it is a member of. +.Pp +.Nm +interfaces can be created at runtime using the +.Ic ifconfig aggr Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The interface itself can be configured with +.Xr ifconfig 8 ; +see its manual page for more information. +.Pp +A random MAC address is generated when an +.Nm +interface is created. +A specific MAC address can be assigned using the +.Xr ifconfig 8 +command +.Cm lladdr Ar etheraddr . +.\" document the ioctls? +.Pp +Other forms of aggregation of Ethernet interfaces are available +using the +.Xr trunk 4 +driver. +.Sh EXAMPLES +Create an +.Nm +virtual interface on top of two physical interfaces: +.Bd -literal -offset indent +# ifconfig aggr0 create +# ifconfig aggr0 trunkport em0 +# ifconfig aggr0 trunkport em1 +# ifconfig aggr0 10.1.1.100/24 +# ifconfig aggr0 up +.Ed +.Sh SEE ALSO +.Xr inet 4 , +.Xr ip 4 , +.Xr netintro 4 , +.Xr trunk 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh STANDARDS +.Rs +.%T IEEE 802.1AX Link Aggregation +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . diff --git a/static/openbsd/man4/agp.4 b/static/openbsd/man4/agp.4 new file mode 100644 index 00000000..00c837f6 --- /dev/null +++ b/static/openbsd/man4/agp.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: agp.4,v 1.6 2014/03/14 23:57:03 kettenis Exp $ +.\" Copyright (c) Owain Ainsworth +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: March 14 2014 $ +.Dt AGP 4 +.Os +.Sh NAME +.Nm agp +.Nd accelerated graphics port driver +.Sh SYNOPSIS +.Cd "agp* at vga?" +.Sh DESCRIPTION +The +.Nm +driver provides support for programming the AGP GART. +This support is used by +.Xr drm 4 +kernel drivers. +.Sh SEE ALSO +.Xr drm 4 , +.Xr inteldrm 4 , +.Xr radeondrm 4 , +.Xr vga 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Fx 4.1 . +It was adopted in +.Nx 1.6 . +The driver was then ported in parts to +.Ox , +and fully integrated in +.Ox 4.3 . +The userland +.Xr ioctl 2 +interface was removed in +.Ox 5.6 . diff --git a/static/openbsd/man4/ahc.4 b/static/openbsd/man4/ahc.4 new file mode 100644 index 00000000..18f97bc1 --- /dev/null +++ b/static/openbsd/man4/ahc.4 @@ -0,0 +1,301 @@ +.\" $OpenBSD: ahc.4,v 1.39 2012/08/14 01:08:19 dlg Exp $ +.\" $NetBSD: ahc.4,v 1.1.2.1 1996/08/25 17:22:14 thorpej Exp $ +.\" +.\" Copyright (c) 1995, 1996 +.\" Justin T. Gibbs. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: August 14 2012 $ +.Dt AHC 4 +.Os +.Sh NAME +.Nm ahc +.Nd Adaptec VL/EISA/PCI SCSI interface +.Sh SYNOPSIS +.Cd "ahc0 at isa? " Pq VL +.Cd "ahc* at eisa? " Pq EISA +.Cd "ahc* at pci? " Pq PCI +.Cd "option AHC_ALLOW_MEMIO" +.Cd "option AHC_TMODE_ENABLE" +.Sh DESCRIPTION +This driver provides access to the +.Tn SCSI +bus(es) connected to Adaptec +.Tn AIC7770 , +.Tn AIC7850 , +.Tn AIC7860 , +.Tn AIC7870 , +.Tn AIC7880 , +.Tn AIC7890 , +.Tn AIC7891 , +.Tn AIC7892 , +.Tn AIC7895 , +.Tn AIC7896 , +.Tn AIC7897 +and +.Tn AIC7899 +host adapter chips. +These chips are found on many motherboards as well as the following +Adaptec SCSI controller cards: +.Tn 274X(W) , +.Tn 274X(T) , +.Tn 284X , +.Tn 2910 , +.Tn 2915 , +.Tn 2920 , +.Tn 2930C , +.Tn 2930U2 , +.Tn 2940 , +.Tn 2940J , +.Tn 2940N , +.Tn 2940U , +.Tn 2940AU , +.Tn 2940UW , +.Tn 2940UW Dual , +.Tn 2940UW Pro , +.Tn 2940U2W , +.Tn 2940U2B , +.Tn 2950U2W , +.Tn 2950U2B , +.Tn 19160B , +.Tn 29160B , +.Tn 29160N , +.Tn 3940 , +.Tn 3940U , +.Tn 3940AU , +.Tn 3940UW , +.Tn 3940AUW , +.Tn 3940U2W , +.Tn 3950U2 , +.Tn 3960 , +.Tn 39160 , +.Tn 3985 , +and +.Tn 4944UW . +.Pp +Driver features include support for twin and wide buses, +fast, ultra, ultra2 and ultra160 synchronous transfers depending on +controller type, tagged queuing, and SCB paging, and target mode. +.Pp +Memory mapped I/O can be enabled for PCI devices with the +.Dq Dv AHC_ALLOW_MEMIO +configuration option. +Memory mapped I/O is more efficient than the alternative, programmed I/O. +Most PCI BIOSes will map devices so that either technique for communicating +with the card is available. +In some cases, +usually when the PCI device is sitting behind a PCI->PCI bridge, +the BIOS may fail to properly initialize the chip for memory mapped I/O. +The typical symptom of this problem is a system hang if memory mapped I/O +is attempted. +Most modern motherboards perform the initialization correctly and work fine +with this option enabled. +This is the default mode of operation on every architecture except i386. +.Pp +Individual controllers may be configured to operate in the target role through +the +.Dq Dv AHC_TMODE_ENABLE +configuration option. +The value assigned to this option should be a bitmap of all units where target +mode is desired. +For example, a value of 0x25, would enable target mode on units 0, 2, and 5. +A value of 0x8a enables it for units 1, 3, and 7. +.Pp +Per target configuration performed in the +.Tn SCSI-Select +menu, accessible at boot +in +.No non- Ns Tn EISA +models, +or through an +.Tn EISA +configuration utility for +.Tn EISA +models, +is honored by this driver. +This includes synchronous/asynchronous transfers, +maximum synchronous negotiation rate, +wide transfers, +disconnection, +the host adapter's SCSI ID, +and, +in the case of +.Tn EISA +Twin Channel controllers, +the primary channel selection. +For systems that store non-volatile settings in a system specific manner +rather than a serial eeprom directly connected to the aic7xxx controller, +the +.Tn BIOS +must be enabled for the driver to access this information. +This restriction applies to all +.Tn EISA +and many motherboard configurations. +.Pp +Note that I/O addresses are determined automatically by the probe routines, +but care should be taken when using a 284x +.Pq Tn VESA No local bus controller +in an +.Tn EISA +system. +The jumpers setting the I/O area for the 284x should match the +.Tn EISA +slot into which the card is inserted to prevent conflicts with other +.Tn EISA +cards. +.Pp +Performance and feature sets vary throughout the aic7xxx product line. +The following table provides a comparison of the different chips supported by +the +.Nm +driver. +Note that wide and twin channel features, although always supported by a +particular chip, may be disabled in a particular motherboard or card design. +.Bd -literal +.Em "Chip MIPS Bus MaxSync MaxWidth SCBs Features" +aic7770 10 EISA/VL 10MHz 16Bit 4 1 +aic7850 10 PCI/32 10MHz 8Bit 3 +aic7860 10 PCI/32 20MHz 8Bit 3 +aic7870 10 PCI/32 10MHz 16Bit 16 +aic7880 10 PCI/32 20MHz 16Bit 16 +aic7890 20 PCI/32 40MHz 16Bit 16 3 4 5 6 7 8 +aic7891 20 PCI/64 40MHz 16Bit 16 3 4 5 6 7 8 +aic7892 20 PCI/64 80MHz 16Bit 16 3 4 5 6 7 8 +aic7895 15 PCI/32 20MHz 16Bit 16 2 3 4 5 +aic7895C 15 PCI/32 20MHz 16Bit 16 2 3 4 5 8 +aic7896 20 PCI/32 40MHz 16Bit 16 2 3 4 5 6 7 8 +aic7897 20 PCI/64 40MHz 16Bit 16 2 3 4 5 6 7 8 +aic7899 20 PCI/64 80MHz 16Bit 16 2 3 4 5 6 7 8 +.Ed +.Pp +.Bl -enum -compact +.It +Multiplexed Twin Channel Device - One controller servicing two buses. +.It +Multi-function Twin Channel Device - Two controllers on one chip. +.It +Command Channel Secondary DMA Engine - Allows scatter gather list and +SCB prefetch. +.It +64 Byte SCB Support - SCSI CDB is embedded in the SCB to eliminate an extra DMA. +.It +Block Move Instruction Support - Doubles the speed of certain sequencer +operations. +.It +.Sq Bayonet +style Scatter Gather Engine - Improves S/G prefetch performance. +.It +Queuing Registers - Allows queuing of new transactions without pausing the +sequencer. +.It +Ultra160 support. +.It +Multiple Target IDs - Allows the controller to respond to selection as a target +on multiple SCSI IDs. +.El +.Sh SCSI CONTROL BLOCKS (SCBs) +Every transaction sent to a device on the SCSI bus is assigned a +.Sq SCSI Control Block +(SCB). +The SCB contains all of the information required by the controller to process a +transaction. +The chip feature table lists the number of SCBs that can be stored in on-chip +memory. +All chips with model numbers greater than or equal to 7870 allow for the +on-chip SCB space to be augmented with external SRAM up to a maximum of 255 +SCBs. +Very few Adaptec controller configurations have external SRAM. +.Pp +If external SRAM is not available, +SCBs are a limited resource. +Using the SCBs in a straight forward manner would only allow the driver to +handle as many concurrent transactions as there are physical SCBs. +To fully utilize the SCSI bus and the devices on it, +requires much more concurrency. +The solution to this problem is +.Em SCB Paging , +a concept similar to memory paging. +SCB paging takes advantage of the fact that devices usually disconnect from the +SCSI bus for long periods of time without talking to the controller. +The SCBs for disconnected transactions are only of use to the controller when +the transfer is resumed. +When the host queues another transaction for the controller to execute, +the controller firmware will use a free SCB if one is available. +Otherwise, the state of the most recently disconnected (and therefore most +likely to stay disconnected) SCB is saved, via DMA, to host memory, +and the local SCB reused to start the new transaction. +This allows the controller to queue up to 255 transactions regardless of the +amount of SCB space. +Since the local SCB space serves as a cache for disconnected transactions, +the more SCB space available, the less host bus traffic consumed saving and +restoring SCB data. +.Sh SEE ALSO +.Xr ahd 4 , +.Xr cd 4 , +.Xr ch 4 , +.Xr eisa 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 +.Sh AUTHORS +The core +.Nm +driver, the +.Tn AIC7xxx +sequencer-code assembler, and the firmware running on the aic7xxx chips +were written by +.An Justin T. Gibbs . +.Pp +The +.Ox +platform dependent code was written by Steve P. Murphree, Jr and Kenneth +R. Westerback. +.Sh BUGS +Some Quantum drives (at least the Empire 2100 and 1080s) will not run on an +.Tn AIC7870 +Rev B in synchronous mode at 10MHz. +Controllers with this problem have a 42 MHz clock crystal on them and run +slightly above 10MHz. +This confuses the drive and hangs the bus. +Setting a maximum synchronous negotiation rate of 8MHz in the +.Tn SCSI-Select +utility will allow normal operation. +.Pp +Although the Ultra2 and Ultra160 products have sufficient instruction RAM space +to support both the initiator and target roles concurrently, +this configuration is disabled in favor of allowing the target role to respond +on multiple target ids. +A method for configuring dual role mode should be provided. +.Pp +Tagged Queuing is not supported in target mode. +.Pp +Reselection in target mode fails to function correctly on all high voltage +differential boards as shipped by Adaptec. +Information on how to modify HVD board to work correctly in target mode is +available from Adaptec. diff --git a/static/openbsd/man4/ahci.4 b/static/openbsd/man4/ahci.4 new file mode 100644 index 00000000..f2a354e9 --- /dev/null +++ b/static/openbsd/man4/ahci.4 @@ -0,0 +1,65 @@ +.\" $OpenBSD: ahci.4,v 1.13 2018/07/02 15:39:33 kettenis Exp $ +.\" +.\" Copyright (c) 2006 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 2 2018 $ +.Dt AHCI 4 +.Os +.Sh NAME +.Nm ahci +.Nd Advanced Host Controller Interface for Serial ATA +.Sh SYNOPSIS +.Cd "ahci* at acpi?" +.Cd "ahci* at fdt?" +.Cd "ahci* at pci?" +.Cd "ahci* at jmb?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Serial ATA controllers conforming to the +Advanced Host Controller Interface specification. +.Pp +Several AHCI capable controllers also provide a compatibility mode that +causes them to appear as a traditional ATA controller supported by +.Xr pciide 4 . +.Pp +Although +.Nm +controllers are actual ATA controllers, the driver emulates SCSI via a +translation layer. +.Pp +Setting the lowest bit (0x1) of the driver flags forces +.Nm +to negotiate SATA 1 (1.5 Gb/s) transfer speeds only. +It may be useful where higher speeds are unstable. +.Sh SEE ALSO +.Xr intro 4 , +.Xr jmb 4 , +.Xr pci 4 , +.Xr pciide 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org +and +.An Christopher Pascoe Aq Mt pascoe@openbsd.org . diff --git a/static/openbsd/man4/ahd.4 b/static/openbsd/man4/ahd.4 new file mode 100644 index 00000000..b02fbb4e --- /dev/null +++ b/static/openbsd/man4/ahd.4 @@ -0,0 +1,156 @@ +.\" $OpenBSD: ahd.4,v 1.18 2012/08/14 01:08:19 dlg Exp $ +.\" +.\" Copyright (c) 1995, 1996, 1997, 1998, 2000 +.\" Justin T. Gibbs. All rights reserved. +.\" Copyright (c) 2002 +.\" Scott Long. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ahd.4,v 1.5 2004/07/04 14:17:41 simon Exp $ +.\" +.Dd $Mdocdate: August 14 2012 $ +.Dt AHD 4 +.Os +.Sh NAME +.Nm ahd +.Nd Adaptec PCI/PCI-X AIC79xx-based Ultra320 SCSI interface +.Sh SYNOPSIS +.Cd "ahd* at pci?" +.Sh DESCRIPTION +.Nm +provides access to the +.Tn SCSI +bus(es) connected to Adaptec +.Tn AIC79xx +host adapter chips. +.Pp +.Nm +supports narrow and wide buses; synchronous and +asynchronous operation; fast, ultra, ultra2, ultra160, and ultra320 +(packetized) transfers; tagged queuing and 512 SCBs. +.Pp +.Nm +does not support target mode operation. +.Pp +The +.Nm +driver supports the following: +.Pp +.Bl -bullet -compact -offset indent +.It +Adaptec +.Tn AIC7901 +host adapter chip +.It +Adaptec +.Tn AIC7901A +host adapter chip +.It +Adaptec +.Tn AIC7902 +host adapter chip +.It +Adaptec +.Tn 29320 +host adapter +.It +Adaptec +.Tn 39320 +host adapter +.It +Many motherboards with on-board +.Tn SCSI +support +.El +.Pp +To compile in debugging code: +.Bd -ragged -offset indent +.Cd option AHD_DEBUG +.Cd option AHD_DEBUG_OPTS= +.Ed +.Pp +The +.Dv AHD_DEBUG_OPTS +option is used to control which diagnostic messages are printed to the +console when +.Dv AHD_DEBUG +is enabled. +Logically OR the following bits together: +.Bl -column "0x0001" "Function" -offset indent +.It Em Value Ta Em Function +.It 0x0001 Ta "Show miscellaneous information" +.It 0x0002 Ta "Show sense data" +.It 0x0004 Ta "Show Serial EEPROM contents" +.It 0x0008 Ta "Show bus termination settings" +.It 0x0010 Ta "Show host memory usage" +.It 0x0020 Ta "Show SCSI protocol messages" +.It 0x0040 Ta "Show mode pointer of the chip register window" +.It 0x0080 Ta "Show selection timeouts" +.It 0x0100 Ta "Show FIFO usage messages" +.It 0x0200 Ta "Show Queue Full status" +.It 0x0400 Ta "Show SCB queue status" +.It 0x0800 Ta "Show inbound packet information" +.It 0x1000 Ta "Show S/G list information" +.It 0x2000 Ta "Enable extra diagnostic code in the firmware" +.El +.Pp +Per target configuration performed in the +.Tn SCSI-Select +menu, accessible at boot, +is honored by this driver. +This includes synchronous/asynchronous transfers, +maximum synchronous negotiation rate, +wide transfers, +disconnection, +and the host adapters +.Tn SCSI +ID. +.Sh SEE ALSO +.Xr ahc 4 , +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 +.Sh HISTORY +The +.Nm +driver was ported from +.Fx 4.7 +and first appeared in +.Ox 3.6 . +.Sh AUTHORS +The +.Nm +driver, the +.Tn AIC7xxx +sequencer-code assembler, +and the firmware running on the aic79xx chips was written by +.An Justin T. Gibbs . +.Pp +.Ox +port by Milos Urbanek, Kenneth R. Westerback & Marco Peereboom. diff --git a/static/openbsd/man4/aibs.4 b/static/openbsd/man4/aibs.4 new file mode 100644 index 00000000..a2f6d2f4 --- /dev/null +++ b/static/openbsd/man4/aibs.4 @@ -0,0 +1,183 @@ +.\" $OpenBSD: aibs.4,v 1.7 2018/01/12 04:36:44 deraadt Exp $ +.\" +.\" Copyright (c) 2009 Constantine A. Murenin +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 12 2018 $ +.Dt AIBS 4 +.Os +.Sh NAME +.Nm aibs +.Nd ASUSTeK AI Booster ACPI ATK0110 temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "aibs* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the voltage, temperature and fan sensors +available through the +ATK0110 +ACPI +device +on ASUSTeK motherboards. +The number of sensors of each type, +as well as the description of each sensor, +varies according to the motherboard. +.Pp +The driver supports an arbitrary set of sensors, +provides a description regarding what each sensor is used for, +and reports whether each sensor is within the specifications +as defined by the motherboard manufacturer through ACPI. +.Pp +The +.Nm +driver supports sensor states as follows: +temperature sensors can have a state of +.Dv OK , +.Dv WARN , +.Dv CRIT +or +.Dv UNKNOWN ; +fan and voltage sensors can have a state of +.Dv OK +or +.Dv WARN +only. +Temperature sensors that have a reading of 0 +are marked as invalid and their state is set to +.Dv UNKNOWN , +whereas all other sensors are always assumed valid. +Temperature sensors have two upper limits +.Dv ( WARN +and +.Dv CRIT ) , +fan sensors have either only the lower limit, or +one lower and one upper limit, +and voltage sensors always have a lower and an upper limit. +.Pp +Sensor values are made available through the +.Dv HW_SENSORS +.Xr sysctl 2 +interface, +and can be monitored with the +.Xr systat 1 +.Ar sensors +view, +.Xr sensorsd 8 , +or +.Xr sysctl 8 +.Ar hw.sensors . +For example, on an Asus Stricker Extreme motherboard: +.Bd -literal -offset indent +$ sysctl hw.sensors.aibs0 +hw.sensors.aibs0.temp0=31.00 degC (CPU Temperature), OK +hw.sensors.aibs0.temp1=43.00 degC (MB Temperature), OK +hw.sensors.aibs0.fan0=2490 RPM (CPU FAN Speed), OK +hw.sensors.aibs0.fan1=0 RPM (CHASSIS FAN Speed), WARNING +hw.sensors.aibs0.fan2=0 RPM (OPT1 FAN Speed), WARNING +hw.sensors.aibs0.fan3=0 RPM (OPT2 FAN Speed), WARNING +hw.sensors.aibs0.fan4=0 RPM (OPT3 FAN Speed), WARNING +hw.sensors.aibs0.fan5=0 RPM (OPT4 FAN Speed), WARNING +hw.sensors.aibs0.fan6=0 RPM (OPT5 FAN Speed), WARNING +hw.sensors.aibs0.fan7=0 RPM (PWR FAN Speed), WARNING +hw.sensors.aibs0.volt0=1.26 VDC (Vcore Voltage), OK +hw.sensors.aibs0.volt1=3.25 VDC ( +3.3 Voltage), OK +hw.sensors.aibs0.volt2=4.95 VDC ( +5.0 Voltage), OK +hw.sensors.aibs0.volt3=11.78 VDC (+12.0 Voltage), OK +hw.sensors.aibs0.volt4=1.23 VDC (1.2VHT Voltage), OK +hw.sensors.aibs0.volt5=1.50 VDC (SB CORE Voltage), OK +hw.sensors.aibs0.volt6=1.25 VDC (CPU VTT Voltage), OK +hw.sensors.aibs0.volt7=0.93 VDC (DDR2 TERM Voltage), OK +hw.sensors.aibs0.volt8=1.23 VDC (NB CORE Voltage), OK +hw.sensors.aibs0.volt9=1.87 VDC (MEMORY Voltage), OK +.Ed +.Pp +Generally, sensors provided by the +.Nm +driver may also be supported by a variety of other drivers, +such as +.Xr lm 4 +or +.Xr it 4 . +The precise collection of +.Nm +sensors is comprised of the sensors +specifically utilised in the motherboard +design, which may be supported through +a combination of one or more physical hardware monitoring chips. +.Pp +The +.Nm +driver, however, provides the following advantages +when compared to the native hardware monitoring drivers: +.Bl -bullet +.It +Sensor values from +.Nm +are expected to be more reliable. +For example, voltage sensors in many hardware monitoring chips +can only sense voltage from 0 to 2 or 4 volts, and the excessive +voltage is removed by the resistors, which may vary with the motherboard +and with the voltage that is being sensed. +In +.Nm , +the required resistor factors are provided by +the motherboard manufacturer through ACPI; +in the native drivers, the resistor factors +are encoded into the driver based on the chip manufacturer's recommendations. +In essence, sensor values from +.Nm +are very likely to be identical to the readings from the +Hardware Monitor screen in the BIOS. +.It +Sensor descriptions from +.Nm +are more likely to match the markings on the motherboard. +.It +Sensor status is supported by +.Nm . +The status is reported based on the acceptable range of values +for each individual sensor as suggested by the motherboard manufacturer. +For example, the threshold for the CPU temperature sensor is likely +to be significantly higher than that for the chassis temperature sensor. +.It +Support for newer chips in +.Nm . +Newer chips may miss a native driver, +but should be supported through +.Nm +regardless. +.El +.Pp +As a result, sensor readings from the actual +native hardware monitoring drivers +may be ignored as appropriate. +.Sh SEE ALSO +.Xr systat 1 , +.Xr sysctl 2 , +.Xr acpi 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Constantine A. Murenin Aq Mt cnst@openbsd.org , +University of Waterloo. diff --git a/static/openbsd/man4/aic.4 b/static/openbsd/man4/aic.4 new file mode 100644 index 00000000..f8a47913 --- /dev/null +++ b/static/openbsd/man4/aic.4 @@ -0,0 +1,92 @@ +.\" $OpenBSD: aic.4,v 1.8 2012/08/14 01:08:19 dlg Exp $ +.\" $NetBSD: aic.4,v 1.5 1998/06/07 09:08:45 enami Exp $ +.\" +.\" Copyright (c) 1997 Jason R. Thorpe. All rights reserved. +.\" Copyright (c) 1994 James A. Jegers +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: August 14 2012 $ +.Dt AIC 4 +.Os +.Sh NAME +.Nm aic +.Nd Adaptec AIC-6260 and AIC-6360 SCSI interface +.Sh SYNOPSIS +.Cd "aic0 at isa? port 0x340 irq 11" +.Cd "aic* at isapnp?" +.Cd "aic* at pcmcia?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Tn Adaptec +AIC-6260 and AIC-6360 +.Tn SCSI +controller chips. +.Pp +The +.Tn ISA +attachment of the +.Nm +driver supports the +.Tn Adaptec +152x, the +.Tn "Creative Labs" +SoundBlaster +.Tn SCSI +host adapter, and compatibles. +Many +.Tn ISA +cards that use this chip do not have boot ROMs, and therefore cannot +be used to connect the boot device. +.Pp +The +.Tn "ISA Plug-and-Play" +attachment of the +.Nm +driver supports the +.Tn Adaptec +AHA-1520B host adapter. +.Pp +The +.Tn PCMCIA +attachment of the +.Nm +driver supports the +.Tn Adaptec +APA-14[56]0. +These +.Tn SCSI +host adapters do not include boot ROMs and therefore cannot be used +to connect the boot device. +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr isapnp 4 , +.Xr pcmcia 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 diff --git a/static/openbsd/man4/akbd.4 b/static/openbsd/man4/akbd.4 new file mode 100644 index 00000000..5aab63c4 --- /dev/null +++ b/static/openbsd/man4/akbd.4 @@ -0,0 +1,169 @@ +.\" +.\" Copyright (c) 2001 Peter Philipp +.\" Copyright (c) 1997 Colin Wood +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Colin Wood +.\" for the NetBSD Project. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $OpenBSD: akbd.4,v 1.6 2022/02/20 15:21:15 jsg Exp $ +.\" $NetBSD: adb.4,v 1.1 1997/07/18 02:13:42 ender Exp $ +.\" +.Dd $Mdocdate: February 20 2022 $ +.Dt AKBD 4 +.Os +.Sh NAME +.Nm akbd +.Nd Apple Keyboard Device +.Sh SYNOPSIS +.Cd "akbd* at adb?" +.Cd "wskbd* at akbd? mux 1" +.Cd "option AKBD_LAYOUT=XXX" +.Sh DESCRIPTION +This driver supports ADB keyboards within the +.Xr wscons 4 +console framework. +It doesn't provide direct device driver entry points but makes its +functions available via the internal +.Xr wskbd 4 +interface. +.Pp +The following is a partial list of supported +.Tn AKBD +devices: +.Bd -filled -offset indent +.Bl -item -compact +.It +Apple Standard Keyboard +.It +Apple Extended Keyboard +.It +Apple Keyboard II +.It +Apple PowerBook Keyboard +.It +Apple Adjustable Keyboard +.It +Apple PowerBook extended Keyboard +.It +Apple PowerBook G3 Keyboard +.It +Apple PowerBook G4 Keyboard +.It +Apple iBook Keyboard +.It +.El +.Ed +.Pp +The +.Nm +driver supports a number of different key mappings which +can be chosen from with the kernel option +.Dq AKBD_LAYOUT +at compile time or with the utility +.Xr wsconsctl 8 +(variable: +.Dq keyboard.encoding ) +at runtime. +Other mappings can be used if the whole keymap is replaced by means of +.Xr wsconsctl 8 . +The built-in mappings are at this time: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It KB_DE +.Pq de +German with +.Dq dead accents . +.It KB_ES +.Pq es +Spanish. +.It KB_FR +.Pq fr +French. +.It KB_JP +.Pq jp +Japanese. +.It KB_PT +.Pq pt +Portuguese. +.It KB_SF +.Pq sf +Swiss French with +.Dq dead accents . +.It KB_SG +.Pq sg +Swiss German with +.Dq dead accents . +.It KB_SV +.Pq sv +Swedish with +.Dq dead accents . +.It KB_UK +.Pq uk +British. +.It KB_US +.Pq us +English/US keyboard mapping (default). +.El +.Pp +The KB_DE, KB_FR, KB_SG and KB_SV mappings can be used in the KB_NODEAD +.Pq .nodead +variant. +This switches off the +.Dq dead accents . +.Sh EXAMPLES +To set a German keyboard layout without +.Dq dead accents , +use +.Ic wsconsctl keyboard.encoding=de.nodead . +To set it at kernel build time, add +the following to the kernel configuration file: +.Bd -literal -offset indent +option AKBD_LAYOUT="KB_DE|KB_NODEAD" +.Ed +.Sh SEE ALSO +.Xr adb 4 , +.Xr intro 4 , +.Xr ukbd 4 , +.Xr wskbd 4 , +.Xr wsconsctl 8 +.Sh HISTORY +The +.Nm +interface first appeared in +.Nx 0.9 . +It has been under development ever since. +.Sh AUTHORS +.An -nosplit +.An Bradley A. Grantham +wrote the original +.Nm +driver, including the MRG support. +The hardware direct interface was written by +.An John P. Wittkoski . +.Sh BUGS +The list of built-in mappings doesn't follow any logic. +It grew as people submitted what they needed. diff --git a/static/openbsd/man4/alc.4 b/static/openbsd/man4/alc.4 new file mode 100644 index 00000000..9e7a3c87 --- /dev/null +++ b/static/openbsd/man4/alc.4 @@ -0,0 +1,83 @@ +.\" $OpenBSD: alc.4,v 1.6 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2009 Kevin Lo +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt ALC 4 +.Os +.Sh NAME +.Nm alc +.Nd Atheros AR813x/AR815x/AR816x/AR817x 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "alc* at pci?" +.Cd "atphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Ethernet interfaces based on the +Atheros AR813x/AR815x/AR816x/AR817x Ethernet chipset. +.Pp +The +.Nm +driver supports IPv4 receive IP/TCP/UDP checksum offload and VLAN +tag insertion and stripping. +.Pp +The following +.Ar media +types are supported: +.Pp +.Bl -tag -width autoselect -compact +.It Cm autoselect +Enable autoselection of the media type and options. +.It Cm 10baseT +Set 10Mbps operation. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.It Cm 1000baseT +Set 1000Mbps (Gigabit Ethernet) operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by the card, try +.Ic ifconfig media . +For example, +.Ic ifconfig alc0 media . +.Sh SEE ALSO +.Xr arp 4 , +.Xr atphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Pyun YongHyeon +for +.Fx +and ported to +.Ox +by +.An Kevin Lo Aq Mt kevlo@openbsd.org . diff --git a/static/openbsd/man4/ale.4 b/static/openbsd/man4/ale.4 new file mode 100644 index 00000000..3ccb49fd --- /dev/null +++ b/static/openbsd/man4/ale.4 @@ -0,0 +1,84 @@ +.\" $OpenBSD: ale.4,v 1.5 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2009 Kevin Lo +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt ALE 4 +.Os +.Sh NAME +.Nm ale +.Nd Atheros AR8121/AR8113/AR8114 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "ale* at pci?" +.Cd "atphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Ethernet interfaces based on the +Atheros AR8121 Gigabit Ethernet chipset and the AR8113/AR8114 +Fast Ethernet chipsets, also known as the Attansic L1E. +.Pp +The +.Nm +driver supports IPv4 receive IP/TCP/UDP checksum offload and VLAN +tag insertion and stripping. +.Pp +The following +.Ar media +types are supported: +.Pp +.Bl -tag -width autoselect -compact +.It Cm autoselect +Enable autoselection of the media type and options. +.It Cm 10baseT +Set 10Mbps operation. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.It Cm 1000baseT +Set 1000Mbps (Gigabit Ethernet) operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by the card, try +.Ic ifconfig media . +For example, +.Ic ifconfig ale0 media . +.Sh SEE ALSO +.Xr arp 4 , +.Xr atphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Pyun YongHyeon +for +.Fx +and ported to +.Ox +by +.An Kevin Lo Aq Mt kevlo@openbsd.org . diff --git a/static/openbsd/man4/alipm.4 b/static/openbsd/man4/alipm.4 new file mode 100644 index 00000000..54ea6883 --- /dev/null +++ b/static/openbsd/man4/alipm.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: alipm.4,v 1.6 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ALIPM 4 +.Os +.Sh NAME +.Nm alipm +.Nd Acer Labs M7101 SMBus controller +.Sh SYNOPSIS +.Cd "alipm* at pci?" +.Cd "iic* at alipm?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Acer Labs M7101 Power Management +controller. +Only the SMBus host interface is supported and can be used with the +.Xr iic 4 +framework. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +.Sh BUGS +The driver doesn't support commands with a data buffer size of more +than 2 bytes. diff --git a/static/openbsd/man4/amas.4 b/static/openbsd/man4/amas.4 new file mode 100644 index 00000000..e7704dbf --- /dev/null +++ b/static/openbsd/man4/amas.4 @@ -0,0 +1,86 @@ +.\" $OpenBSD: amas.4,v 1.4 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Ariane van der Steldt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt AMAS 4 +.Os +.Sh NAME +.Nm amas +.Nd AMD memory address map +.Sh SYNOPSIS +.Cd "amas* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides read access to the AMD memory map, which describes +the location of physical memory. +.Pp +One instance of this device is shared between all cores on a chip. +This device is present on AMD processors of the 0Fh, 10h and 11h family. +.Pp +The +.Nm +device can run in either interleaved mode or in non-interleaved mode. +In interleaved mode, the physical memory addresses are rotated across +each chip. +.Nm +sits between the CPU cores, the DRAM controller and the HyperTransport bus. +When a CPU requests a memory page, +.Nm +decides if the request is serviced from memory local to the chip, +in which case it normalizes the address and passes it on to the dram +controller. +If the request refers to memory present on a different chip, +the request is forwarded to the correct chip using the hypertransport bus. +.Pp +The +.Nm +device is configured by the BIOS and kernel startup routines. +If multiple instances of this device are available, +all should contain the same information. +.Sh SEE ALSO +.Xr pci 4 +.Rs +.%T "BIOS and Kernel Developer's Guide for AMD Athlon 64 and AMD Opteron Processors" +.%D February 2006 +.%R Publication # 26094 +.%P pp. 66\(en80 +.\" .%U http://support.amd.com/us/Processor_TechDocs/26094.PDF +.Re +.Rs +.%T "BIOS and Kernel Developer's Guide (BKDG) For AMD Family 10h Processors" +.%D March 2008 +.%R Publication # 31116 +.%P pp. 158\(en167 +.\" .%U http://support.amd.com/us/Processor_TechDocs/31116.pdf +.Re +.Rs +.%T "BIOS and Kernel Developer's Guide (BKDG) For AMD Family 11h Processors" +.%D July 2008 +.%R Publication # 41256 +.%P pp. 109\(en114 +.\" .%U http://support.amd.com/us/Processor_TechDocs/41256.pdf +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Ariane van der Steldt Aq Mt ariane@stack.nl . diff --git a/static/openbsd/man4/amdgpio.4 b/static/openbsd/man4/amdgpio.4 new file mode 100644 index 00000000..4f380f46 --- /dev/null +++ b/static/openbsd/man4/amdgpio.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: amdgpio.4,v 1.2 2020/01/07 13:30:43 jmc Exp $ +.\" +.\" Copyright (c) 2019 James Hastings +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 7 2020 $ +.Dt AMDGPIO 4 +.Os +.Sh NAME +.Nm amdgpio +.Nd AMD GPIO controller +.Sh SYNOPSIS +.Cd "amdgpio* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO controller found on AMD chipsets. +It does not provide direct device driver entry points but makes its +functions available to +.Xr acpi 4 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An James Hastings +based on the +.Xr bytgpio 4 +driver by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amdiic.4 b/static/openbsd/man4/amdiic.4 new file mode 100644 index 00000000..7c9acba0 --- /dev/null +++ b/static/openbsd/man4/amdiic.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: amdiic.4,v 1.4 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt AMDIIC 4 +.Os +.Sh NAME +.Nm amdiic +.Nd AMD-8111 SMBus controller +.Sh SYNOPSIS +.Cd "amdiic* at pci?" +.Cd "iic* at amdiic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the AMD-8111 SMBus host interface to be +used with the +.Xr iic 4 +framework. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . +.Sh BUGS +The driver doesn't support I2C commands with a data buffer size of more +than 2 bytes. diff --git a/static/openbsd/man4/amdpm.4 b/static/openbsd/man4/amdpm.4 new file mode 100644 index 00000000..0d37aae5 --- /dev/null +++ b/static/openbsd/man4/amdpm.4 @@ -0,0 +1,64 @@ +.\" $OpenBSD: amdpm.4,v 1.10 2007/05/31 19:19:49 jmc Exp $ +.\" +.\" Copyright (c) 2002 Michael Shalayeff +.\" All rights reserved +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, USE, DATA, OR PROFITS; OR +.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, +.\" WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR +.\" OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF +.\" ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt AMDPM 4 +.Os +.Sh NAME +.Nm amdpm +.Nd AMD-756/766/768/8111 Power Management and SMBus controller +.Sh SYNOPSIS +.Cd "amdpm* at pci?" +.Cd "iic* at amdpm?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +AMD-756/766/768/8111 Power Management controller. +.Pp +The RNG function of the AMD-768/8111 Power Management controller +is supported. +Data generated by the RNG get fed into the pool of the +.Xr random 4 +device. +.Pp +The SMBus host interface of the AMD-756/766/768/8111 Power Management controller +and NVIDIA nForce 1 chipset are also supported. +The SMBus host interface can be used with the +.Xr iic 4 +framework. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr random 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 3.2 . +SMBus host interface support was added in +.Ox 3.9 . diff --git a/static/openbsd/man4/amdpmc.4 b/static/openbsd/man4/amdpmc.4 new file mode 100644 index 00000000..5072ad84 --- /dev/null +++ b/static/openbsd/man4/amdpmc.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: amdpmc.4,v 1.1 2025/08/03 09:26:57 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 3 2025 $ +.Dt AMDPMC 4 +.Os +.Sh NAME +.Nm amdpmc +.Nd AMD power management controller +.Sh SYNOPSIS +.Cd "amdpmc* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver implements support for the power management controller found on +AMD SoCs. +It provides support for entering low power idle states of the SoC. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/ami.4 b/static/openbsd/man4/ami.4 new file mode 100644 index 00000000..936b7a18 --- /dev/null +++ b/static/openbsd/man4/ami.4 @@ -0,0 +1,136 @@ +.\" $OpenBSD: ami.4,v 1.45 2022/02/19 23:45:51 jsg Exp $ +.\" +.\" Michael Shalayeff, 2001. Public Domain. +.\" +.Dd $Mdocdate: February 19 2022 $ +.Dt AMI 4 +.Os +.Sh NAME +.Nm ami +.Nd American Megatrends Inc. MegaRAID PATA/SATA/SCSI RAID controller +.Sh SYNOPSIS +.Cd "ami* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the MegaRAID family of RAID controllers, +including: +.Pp +.Bl -dash -offset indent -compact +.It +ACER MegaRAID ROMB-2E +.It +Apple Xserve G5 PCI Hardware RAID Card +.It +Dell CERC-PATA, +PERC 2/DC, +PERC 2/SC, +PERC 3/DC, +PERC 3/DCL, +PERC 3/QC, +PERC 3/SC, +PERC 4/DC, +PERC 4/Di, +PERC 4/SC, +PERC 4e/DC, +PERC 4e/Di, +PERC 4e/SC, +PERC 4e/Si +.It +FSC MegaRAID PCI Express ROMB +.It +Hewlett-Packard 438, +466, +T[567] +.It +Intel RAID Controller SRCS16, +SRCS28X, +SRCU41L, +SRCU42E, +SRCU42X, +SROMBU42E, +SRCZCRX +.It +LSI Logic/AMI/Symbios MegaRAID, +523 SATA, +i4 133 RAID, +ATA 133-2 +Elite 1400, +Elite 1600, +Elite 1650, +Enterprise 1200, +Enterprise 1300, +Enterprise 1400, +Enterprise 1500, +Enterprise 1600, +Express 100, +Express 200, +Express 300, +Express 500, +Series 418, +SCSI 320-0, +SCSI 320-0X, +SCSI 320-1, +SCSI 320-1E, +SCSI 320-1LP, +SCSI 320-2, +SCSI 320-2E, +SCSI 320-2X, +SCSI 320-4X, +SATA 150-4, +SATA 150-6, +SATA 300-4X, +SATA 300-8ELP, +SATA 300-8X, +SATA 300-8XLP +.It +NEC MegaRAID PCI Express ROMB +.El +.Pp +These controllers support RAID 0, RAID 1, RAID 5, JBOD, +and superpositions of those configurations. +.Pp +Although the controllers are actual RAID controllers, +the driver makes them look just like SCSI controllers. +All RAID configuration is done through the controllers' BIOSes. +.Pp +RAID management is done through the +.Xr bio 4 +device with the +.Xr bioctl 8 +command. +Logical disk status is exposed under the +.Va hw.sensors +.Xr sysctl 8 +and can be monitored using +.Xr sensorsd 8 . +For example: +.Bd -literal -offset indent +$ sysctl hw.sensors.ami0 +hw.sensors.ami0.drive0=online (sd0), OK +hw.sensors.ami0.drive1=degraded (sd1), WARNING +hw.sensors.ami0.drive2=failed (sd2), CRITICAL +.Ed +.Sh SEE ALSO +.Xr bio 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr bioctl 8 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Michael Shalayeff Aq Mt mickey@openbsd.org . +.Pp +Management functions were implemented by +.An Marco Peereboom Aq Mt marco@openbsd.org . diff --git a/static/openbsd/man4/amlclock.4 b/static/openbsd/man4/amlclock.4 new file mode 100644 index 00000000..663955f1 --- /dev/null +++ b/static/openbsd/man4/amlclock.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: amlclock.4,v 1.1 2019/08/27 09:05:57 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 27 2019 $ +.Dt AMLCLOCK 4 +.Os +.Sh NAME +.Nm amlclock +.Nd Amlogic clock controller +.Sh SYNOPSIS +.Cd "amlclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the clock signals for integrated components of Amlogic SoCs. +.Sh SEE ALSO +.Xr amlreset 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amldwusb.4 b/static/openbsd/man4/amldwusb.4 new file mode 100644 index 00000000..774d2d8b --- /dev/null +++ b/static/openbsd/man4/amldwusb.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: amldwusb.4,v 1.1 2019/08/29 17:40:57 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 29 2019 $ +.Dt AMLDWUSB 4 +.Os +.Sh NAME +.Nm amldwusb +.Nd Amlogic USB 3.0 glue logic +.Sh SYNOPSIS +.Cd "amldwusb* at fdt?" +.Cd "xhci* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the interface logic for the Synopsys DesignWare USB +3.0 controller on Amlogic SoCs. +.Sh SEE ALSO +.Xr amlpciephy 4 , +.Xr amlusbphy 4 , +.Xr intro 4 , +.Xr xhci 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amliic.4 b/static/openbsd/man4/amliic.4 new file mode 100644 index 00000000..9ac441a3 --- /dev/null +++ b/static/openbsd/man4/amliic.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: amliic.4,v 1.1 2019/10/07 18:56:59 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 7 2019 $ +.Dt AMLIIC 4 +.Os +.Sh NAME +.Nm amliic +.Nd Amlogic I2C controller +.Sh SYNOPSIS +.Cd "amliic* at fdt?" +.Cd "iic* at amliic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the I2C controller integrated in various +Amlogic SoCs. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amlmmc.4 b/static/openbsd/man4/amlmmc.4 new file mode 100644 index 00000000..32a91582 --- /dev/null +++ b/static/openbsd/man4/amlmmc.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: amlmmc.4,v 1.1 2019/09/03 21:02:51 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 3 2019 $ +.Dt AMLMMC 4 +.Os +.Sh NAME +.Nm amlmmc +.Nd Amlogic MMC/SD/SDIO controller +.Sh SYNOPSIS +.Cd "amlmmc* at fdt?" +.Cd "sdmmc* at amlmmc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various MMC/SD/SDIO controllers integrated +on various Amlogic SoCs. +.Pp +The +.Xr sdmmc 4 +subsystem performs SD/MMC transactions to communicate with whatever +MMC/SD/SDIO devices are inserted into the card slot or directly +connected to the controller. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sdmmc 4 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amlpciephy.4 b/static/openbsd/man4/amlpciephy.4 new file mode 100644 index 00000000..9540b36d --- /dev/null +++ b/static/openbsd/man4/amlpciephy.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: amlpciephy.4,v 1.2 2020/12/27 19:33:32 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 27 2020 $ +.Dt AMLPCIEPHY 4 +.Os +.Sh NAME +.Nm amlpciephy +.Nd Amlogic PCIe 2.0 and USB 3.0 PHY +.Sh SYNOPSIS +.Cd "amlpciephy* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the PCIe 2.0 and USB 3.0 PHY integrated on Amlogic SoCs. +.Sh SEE ALSO +.Xr amldwusb 4 , +.Xr amlusbphy 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amlpinctrl.4 b/static/openbsd/man4/amlpinctrl.4 new file mode 100644 index 00000000..5bcd21c2 --- /dev/null +++ b/static/openbsd/man4/amlpinctrl.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: amlpinctrl.4,v 1.1 2019/08/28 09:46:32 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 28 2019 $ +.Dt AMLPINCTRL 4 +.Os +.Sh NAME +.Nm amlpinctrl +.Nd Amlogic pin multiplexing +.Sh SYNOPSIS +.Cd "amlpinctrl* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver uses pin control data from the device tree to select one of +multiple possible roles available for pins on Amlogic SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amlpwm.4 b/static/openbsd/man4/amlpwm.4 new file mode 100644 index 00000000..cea50edb --- /dev/null +++ b/static/openbsd/man4/amlpwm.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: amlpwm.4,v 1.2 2019/09/30 20:59:22 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 30 2019 $ +.Dt AMLPWM 4 +.Os +.Sh NAME +.Nm amlpwm +.Nd Amlogic PWM controller +.Sh SYNOPSIS +.Cd "amlpwm* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PWM controllers integrated on various +Amlogic SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amlreset.4 b/static/openbsd/man4/amlreset.4 new file mode 100644 index 00000000..44e0f973 --- /dev/null +++ b/static/openbsd/man4/amlreset.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: amlreset.4,v 1.2 2019/08/27 08:24:37 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 27 2019 $ +.Dt AMLRESET 4 +.Os +.Sh NAME +.Nm amlreset +.Nd Amlogic reset controller +.Sh SYNOPSIS +.Cd "amlreset* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the reset signals for integrated components of Amlogic SoCs. +.Sh SEE ALSO +.Xr amlclock 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amlrng.4 b/static/openbsd/man4/amlrng.4 new file mode 100644 index 00000000..6a53c3b2 --- /dev/null +++ b/static/openbsd/man4/amlrng.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: amlrng.4,v 1.2 2019/08/28 06:11:36 naddy Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 28 2019 $ +.Dt AMLRNG 4 +.Os +.Sh NAME +.Nm amlrng +.Nd Amlogic random number generator +.Sh SYNOPSIS +.Cd "amlrng* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the random number generator found on the +Amlogic SoCs. +.Pp +It feeds the random subsystem's entropy pool with 32 bits of random +data every second. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amlsm.4 b/static/openbsd/man4/amlsm.4 new file mode 100644 index 00000000..92581e0d --- /dev/null +++ b/static/openbsd/man4/amlsm.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: amlsm.4,v 1.2 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt AMLSM 4 +.Os +.Sh NAME +.Nm amlsm +.Nd Amlogic secure monitor +.Sh SYNOPSIS +.Cd "amlsm* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the secure monitor firmware interface on +various Amlogic SOCs. +It uses this interface to read the chip ID of the SoC and feeds it to +the random subsystem's entropy pool. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amltemp.4 b/static/openbsd/man4/amltemp.4 new file mode 100644 index 00000000..75cc6336 --- /dev/null +++ b/static/openbsd/man4/amltemp.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: amltemp.4,v 1.2 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt AMLTEMP 4 +.Os +.Sh NAME +.Nm amltemp +.Nd Amlogic temperature sensor +.Sh SYNOPSIS +.Cd "amltemp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor found on various +Amlogic SoCs. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amluart.4 b/static/openbsd/man4/amluart.4 new file mode 100644 index 00000000..af832ff7 --- /dev/null +++ b/static/openbsd/man4/amluart.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: amluart.4,v 1.2 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt AMLUART 4 +.Os +.Sh NAME +.Nm amluart +.Nd Amlogic Universal Asynchronous Receiver/Transmitter +.Sh SYNOPSIS +.Cd "amluart* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the Amlogic Universal Asynchronous +Receiver/Transmitter (UART). +.Sh SEE ALSO +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amlusbphy.4 b/static/openbsd/man4/amlusbphy.4 new file mode 100644 index 00000000..8770b10d --- /dev/null +++ b/static/openbsd/man4/amlusbphy.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: amlusbphy.4,v 1.1 2019/08/29 17:40:57 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 29 2019 $ +.Dt AMLUSBPHY 4 +.Os +.Sh NAME +.Nm amlusbphy +.Nd Amlogic USB 2.0 PHY +.Sh SYNOPSIS +.Cd "amlusbphy* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the USB 2.0 PHY integrated on Amlogic SoCs. +.Sh SEE ALSO +.Xr amldwusb 4 , +.Xr amlpciephy 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/amphy.4 b/static/openbsd/man4/amphy.4 new file mode 100644 index 00000000..4dde7fee --- /dev/null +++ b/static/openbsd/man4/amphy.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: amphy.4,v 1.10 2007/05/31 19:19:49 jmc Exp $ +.\" +.\" Copyright (c) 2000 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt AMPHY 4 +.Os +.Sh NAME +.Nm amphy +.Nd AMD AM79c873 Ethernet PHY +.Sh SYNOPSIS +.Cd "amphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports AMD AM79c873 Ethernet PHYs, and the Davicom DM9101, +DM9102, and DM9601 integrated Ethernet PHY. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/ams.4 b/static/openbsd/man4/ams.4 new file mode 100644 index 00000000..c9b5df20 --- /dev/null +++ b/static/openbsd/man4/ams.4 @@ -0,0 +1,69 @@ +.\" $OpenBSD: ams.4,v 1.3 2014/02/13 08:35:00 schwarze Exp $ +.\" +.\" Copyright (c) 2001 Peter Philipp +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 13 2014 $ +.Dt AMS 4 +.Os +.Sh NAME +.Nm ams +.Nd Apple Mouse Support +.Sh SYNOPSIS +.Cd "ams* at adb?" +.Cd "wsmouse at ams? mux 0" +.Sh DESCRIPTION +The +.Nm +driver supports a series of +.Xr adb 4 +mice, trackballs, trackpads and tablets. +.Pp +.Bl -bullet -compact +.It +Extended Mouse Protocol +.It +Mouse Systems A3 Mouse +.It +MicroSpeed Mouse Deluxe +.It +Contour mouse +.It +Kensington Turbo Mouse +.It +Logitech non-EMP Mouseman +.It +TrackMan trackball +.El +.Sh SEE ALSO +.Xr adb 4 , +.Xr intro 4 , +.Xr ums 4 , +.Xr wsmouse 4 +.Sh AUTHORS +The +.Nm +driver was written by +.An Colin Wood . diff --git a/static/openbsd/man4/an.4 b/static/openbsd/man4/an.4 new file mode 100644 index 00000000..46a6b0ed --- /dev/null +++ b/static/openbsd/man4/an.4 @@ -0,0 +1,190 @@ +.\" $OpenBSD: an.4,v 1.46 2021/10/24 12:32:42 kn Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/an.4,v 1.5 2000/03/02 14:53:45 sheldonh Exp $ +.\" +.Dd $Mdocdate: October 24 2021 $ +.Dt AN 4 +.Os +.Sh NAME +.Nm an +.Nd Aironet Communications 4500/4800 IEEE 802.11FH/b wireless network device +.Sh SYNOPSIS +.Cd "an* at pcmcia?" +.Cd "an* at pci?" +.Cd "an* at isapnp?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Aironet Communications 4500, 4800 +(aka Cisco 340), and Cisco 350 +IEEE 802.11 wireless network adapters. +This includes the ISA, PCI, and PCMCIA varieties. +The 4500 series adapters operate at 1 and 2Mbps (FH) while +the 4800 and 350 series can operate at 1, 2, 5.5, and 11Mbps (DS). +The ISA, PCI, +and PCMCIA devices are all based on the same core PCMCIA modules +and all have the same programming interface. +However, unlike the +Lucent WaveLAN/IEEE cards, the ISA and PCI cards appear to the +host as normal ISA and PCI devices and do not require any PCMCIA +support. +.Pp +ISA cards can either be configured to use ISA Plug and Play +or to use a particular I/O address and IRQ +by properly setting the DIP switches on the board. +(The default switch setting is for plug and play.) +The +.Nm +driver has Plug and Play support and will work in either configuration, +however when using a hard-wired I/O address and IRQ, the driver +configuration and the NIC's switch settings must agree. +PCI cards +require no switch settings of any kind and will be automatically +probed and attached. +.Pp +All host/device interaction with the Aironet cards is via programmed I/O. +The +.Nm +driver encapsulates all IP and ARP traffic as 802.11 frames, though +it can receive either 802.11 or 802.3 frames. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use hardware +Wired Equivalent Privacy (WEP). +It is strongly recommended that WEP +not be used as the sole mechanism +to secure wireless communication, +due to serious weaknesses in it. +.Pp +In BSS mode, +the driver supports powersave mode, +which can be enabled via +.Xr ifconfig 8 . +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh EXAMPLES +The following +.Xr hostname.if 5 +example configures an0 to join network +.Dq mynwid , +using WEP key +.Dq mywepkey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid nwkey mywepkey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "an0: failed to allocate N bytes on NIC" +The driver was unable to allocate memory for transmit frames in the +NIC's on-board RAM. +.It "an0: device timeout" +The Aironet card failed to generate an interrupt to acknowledge a transmit +command. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isapnp 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr pcmcia 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 4.0 . +.Ox +support was added in +.Ox 2.7 . +A version of the driver based on the one in +.Nx +was added in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ee.columbia.edu +and ported to +.Ox +by +.An Michael Shalayeff Aq Mt mickey@openbsd.org . +Later the +.Nx +version of the driver by +.An Atsushi Onoe +was subsequently ported to +.Ox +by +.An Jonathan Gray Aq Mt jsg@openbsd.org . +.Sh CAVEATS +Scanning for access points is not currently supported. diff --git a/static/openbsd/man4/andl.4 b/static/openbsd/man4/andl.4 new file mode 100644 index 00000000..90ce849d --- /dev/null +++ b/static/openbsd/man4/andl.4 @@ -0,0 +1,54 @@ +.\" $OpenBSD: andl.4,v 1.5 2022/02/18 02:11:56 jsg Exp $ +.\" +.\" Copyright (c) 2008 Constantine A. Murenin +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt ANDL 4 +.Os +.Sh NAME +.Nm andl +.Nd Andigilog aSC7611 temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "andl* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Andigilog aSC7611 hardware monitor. +The device provides 3 temperature sensors, +5 voltage sensors and 4 fan sensors. +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Rs +.%T Andigilog aSC7611 Hardware Monitor with Integrated Fan Control +.%D October 2006 +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Constantine A. Murenin Aq Mt cnst@openbsd.org +whilst at the University of Waterloo. diff --git a/static/openbsd/man4/aplgpio.4 b/static/openbsd/man4/aplgpio.4 new file mode 100644 index 00000000..c2f4a258 --- /dev/null +++ b/static/openbsd/man4/aplgpio.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: aplgpio.4,v 1.1 2019/06/17 18:28:17 patrick Exp $ +.\" +.\" Copyright (c) 2019 James Hastings +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 17 2019 $ +.Dt APLGPIO 4 +.Os +.Sh NAME +.Nm aplgpio +.Nd Intel Apollo Lake GPIO controller +.Sh SYNOPSIS +.Cd "aplgpio* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO controllers found on Intel's Apollo +Lake SoC. +It does not provide direct device driver entry points but makes its +functions available to +.Xr acpi 4 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An James Hastings +based on the +.Xr bytgpio 4 +driver by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/aps.4 b/static/openbsd/man4/aps.4 new file mode 100644 index 00000000..d6cab321 --- /dev/null +++ b/static/openbsd/man4/aps.4 @@ -0,0 +1,70 @@ +.\" $OpenBSD: aps.4,v 1.10 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt APS 4 +.Os +.Sh NAME +.Nm aps +.Nd ThinkPad Active Protection System accelerometer +.Sh SYNOPSIS +.Cd "aps0 at isa? port 0x1600" +.Sh DESCRIPTION +The +.Nm +driver provides support for several sensors found in some ThinkPad laptops. +.Pp +The sensors currently exposed via the +.Xr sysctl 8 +interface are: +.Bl -column "Keyboard Active" "Unknown" "Typical Use" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical Use" +.It Li "X_ACCEL" Ta "Unknown" Ta "X Acceleration" +.It Li "Y_ACCEL" Ta "Unknown" Ta "Y Acceleration" +.It Li "X_VAR" Ta "Unknown" Ta "Weighted X Acceleration?" +.It Li "Y_VAR" Ta "Unknown" Ta "Weighted Y Acceleration?" +.It Li "Temp1" Ta "uK" Ta "Unknown" +.It Li "Temp2" Ta "uK" Ta "Unknown" +.It Li "Keyboard Active" Ta "boolean" Ta "Keyboard activity" +.It Li "Mouse Active" Ta "boolean" Ta "Mouse activity" +.It Li "Lid Open" Ta "boolean" Ta "Lid state" +.El +.Sh SEE ALSO +.Xr isa 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Jonathan Gray Aq Mt jsg@openbsd.org . +.Sh CAVEATS +The +.Nm +driver does not yet maintain state and subsequently does not take +evasive action when it thinks the hard drive is in danger. +.Pp +The Y axis on X40 and possibly other models seems to be inverted. +It is unknown how to distinguish between different versions of the +accelerometer to compensate for this in the driver at this time. +.Pp +As IBM provides no documentation, it is not known what all the available +sensors are used for. diff --git a/static/openbsd/man4/aq.4 b/static/openbsd/man4/aq.4 new file mode 100644 index 00000000..28351cdb --- /dev/null +++ b/static/openbsd/man4/aq.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: aq.4,v 1.4 2022/03/31 21:43:38 jmc Exp $ +.\" +.\" Copyright (c) 2021 Mike Larkin +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt AQ 4 +.Os +.Sh NAME +.Nm aq +.Nd Aquantia AQC1xx 1Gb/2.5Gb/5Gb/10Gb PCIe Ethernet device +.Sh SYNOPSIS +.Cd "aq* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Aquantia AQC1xx family of Ethernet adapters. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width autoselect -offset indent +.It autoselect +Enables auto-negotiation for speed and duplex. +.It 100baseTX Cm mediaopt No full-duplex +Sets 100Mbps operation. +.It 1000baseT +Sets 1000Mbps operation. +.It 2500baseT +Sets 2.5Gbps operation. +.It 5000baseT +Sets 5Gbps operation. +.It 10GbaseT +Sets 10Gbps operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mike Larkin Aq Mt mlarkin@openbsd.org +and +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . +.Sh BUGS +This driver only supports devices using Aquantia firmware version 2. diff --git a/static/openbsd/man4/arc.4 b/static/openbsd/man4/arc.4 new file mode 100644 index 00000000..4a07b875 --- /dev/null +++ b/static/openbsd/man4/arc.4 @@ -0,0 +1,147 @@ +.\" $OpenBSD: arc.4,v 1.16 2014/01/24 18:32:27 chris Exp $ +.\" +.\" Copyright (c) 2006 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 24 2014 $ +.Dt ARC 4 +.Os +.Sh NAME +.Nm arc +.Nd Areca Technology Corporation SAS/SATA RAID controller +.Sh SYNOPSIS +.Cd "arc* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PCI-X and PCI Express RAID controllers from +Areca Technology Corporation: +.Pp +.Bl -dash -offset indent -compact +.It +ARC-1110 PCI-X 4 Port SATA RAID Controller +.It +ARC-1110ML PCI-X 4 Port SATA RAID Controller +.It +ARC-1120 PCI-X 8 Port SATA RAID Controller +.It +ARC-1120ML PCI-X 8 Port SATA RAID Controller +.It +ARC-1130 PCI-X 12 Port SATA RAID Controller +.It +ARC-1130ML PCI-X 12 Port SATA RAID Controller +.It +ARC-1160 PCI-X 16 Port SATA RAID Controller +.It +ARC-1160ML PCI-X 16 Port SATA RAID Controller +.It +ARC-1170 PCI-X 24 Port SATA RAID Controller +.It +ARC-1200 Rev A PCI Express 2 Port SATA RAID Controller +.It +ARC-1202 PCI Express 2 Port SATA RAID Controller +.It +ARC-1210 PCI Express 4 Port SATA RAID Controller +.It +ARC-1212 PCI Express 4 Port SATA RAID Controller +.It +ARC-1213 PCI Express 4 Port SATA RAID Controller +.It +ARC-1214 PCI Express 4 Port SATA RAID Controller +.It +ARC-1220 PCI Express 8 Port SATA RAID Controller +.It +ARC-1222 PCI Express 8 Port SATA RAID Controller +.It +ARC-1223 PCI Express 8 Port SATA RAID Controller +.It +ARC-1224 PCI Express 8 Port SATA RAID Controller +.It +ARC-1230 PCI Express 12 Port SATA RAID Controller +.It +ARC-1230ML PCI Express 12 Port SATA RAID Controller +.It +ARC-1231ML PCI Express 12 Port SATA RAID Controller +.It +ARC-1260 PCI Express 16 Port SATA RAID Controller +.It +ARC-1260ML PCI Express 16 Port SATA RAID Controller +.It +ARC-1261ML PCI Express 16 Port SATA RAID Controller +.It +ARC-1264il-12 PCI Express 12 Port SATA RAID Controller +.It +ARC-1264il-16 PCI Express 16 Port SATA RAID Controller +.It +ARC-1280 PCI Express 24 Port SATA RAID Controller +.It +ARC-1280ML PCI Express 24 Port SATA RAID Controller +.It +ARC-1284ML-24 PCI Express 24 Port SATA RAID Controller +.It +ARC-1680 PCI Express 8 Port SAS RAID Controller +.It +ARC-1680LP PCI Express 8 Port SAS RAID Controller +.It +ARC-1680i PCI Express 8 Port SAS RAID Controller +.It +ARC-1680x PCI Express 8 Port SAS RAID Controller +.It +ARC-1681 PCI-X 8 Port SAS RAID Controller +.It +ARC-1880ixl-8 PCI Express 12 Port SAS RAID Controller +.It +ARC-1880ixl-12 PCI Express 16 Port SAS RAID Controller +.It +ARC-1882i PCI Express 8 Port SAS RAID Controller +.It +ARC-1882x PCI Express 8 Port SAS RAID Controller +.It +ARC-1882LP PCI Express 8 Port SAS RAID Controller +.It +ARC-1882ix-12 PCI Express 16 Port SAS RAID Controller +.It +ARC-1882ix-16 PCI Express 20 Port SAS RAID Controller +.It +ARC-1882ix-24 PCI Express 28 Port SAS RAID Controller +.It +ARC-1883X PCI Express 16 Port SAS RAID Controller +.El +.Pp +These controllers can support RAID levels 0, 1, 1E, 3, 5, 6, and JBOD. +.Pp +.Nm +supports alarm control and monitoring of volumes configured on the +controllers via the +.Xr bio 4 +interface and the +.Xr bioctl 8 +utility. +.Sh SEE ALSO +.Xr bio 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr bioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/arcofi.4 b/static/openbsd/man4/arcofi.4 new file mode 100644 index 00000000..83527133 --- /dev/null +++ b/static/openbsd/man4/arcofi.4 @@ -0,0 +1,101 @@ +.\" $OpenBSD: arcofi.4,v 1.8 2020/04/22 05:37:00 jmc Exp $ +.\" +.\" +.\" Copyright (c) 2011 Miodrag Vallat. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 22 2020 $ +.Dt ARCOFI 4 +.Os +.Sh NAME +.Nm arcofi +.Nd Siemens PSB2160 audio codec +.Sh SYNOPSIS +.Cd "arcofi* at gsc?" +.Cd "audio* at arcofi?" +.Sh DESCRIPTION +The +.Nm +driver supports the HP +.Dq Audio1 +audio devices, based upon the Siemens PSB2160 +.Dq ARCOFI +codec, to implement the audio device interface described in +.Xr audio 4 . +.Pp +This device is found onboard HP 9000 workstations models 425e, 705 and 710. +.Pp +The +.Nm +is limited to a mono, 8000 KHz sound, either with 8-bit phone-quality mu-law or +a-law samples, or 16-bit signed linear samples in big-endian byte order. +.Ss AUDIOCTL SETTINGS +The following encodings are supported: +.Pp +.Bl -tag -width AUDIO_ENCODING_SLINEAR_BE -offset indent -compact +.It Li AUDIO_ENCODING_ULAW +.It Li AUDIO_ENCODING_ALAW +.It Li AUDIO_ENCODING_SLINEAR_BE +Natively supported. +.Pp +.It Li AUDIO_ENCODING_SLINEAR +Software converted to +.Li AUDIO_ENCODING_ULAW +encoding. +.Pp +.It Li AUDIO_ENCODING_SLINEAR_LE +.It Li AUDIO_ENCODING_ULINEAR_LE +.It Li AUDIO_ENCODING_ULINEAR_BE +Software converted to +.Li AUDIO_ENCODING_SLINEAR_BE +encoding. +.El +.Ss MIXERCTL SETTINGS +The +.Nm +has three audio ports: +.Pp +.Bl -tag -width "outputs.lineXXX" -offset indent -compact +.It Cm inputs.line +The +.Sq line in +jack connector. +.It Cm outputs.line +The +.Sq line out +jack connector. +.It Cm outputs.spkr +The built-in speaker. +.El +.Pp +Each port has a volume control, and can be muted. +.Pp +The +.Cm outputs.line +and +.Cm outputs.spkr +volume settings are tied to the same hardware setting. +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr audio 4 , +.Xr gsc 4 , +.Xr intro 4 , +.Xr audioctl 8 , +.Xr mixerctl 8 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 5.1 . diff --git a/static/openbsd/man4/asbtm.4 b/static/openbsd/man4/asbtm.4 new file mode 100644 index 00000000..a722adba --- /dev/null +++ b/static/openbsd/man4/asbtm.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: asbtm.4,v 1.5 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Damien Miller +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ASBTM 4 +.Os +.Sh NAME +.Nm asbtm +.Nd Asus ASB 100 temperature sensor +.Sh SYNOPSIS +.Cd "asbtm* at iic?" +.Sh DESCRIPTION +The +.Nm +driver supports the Asus ASB 100 temperature sensor, making its sensor +readings available through a +.Xr sysctl 8 +interface. +.Pp +The driver reads seven voltage (A/D) inputs, three fan inputs, two on-chip +temperature sensors and up to two satellite temperature sensors. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Damien Miller Aq Mt djm@openbsd.org . diff --git a/static/openbsd/man4/asmc.4 b/static/openbsd/man4/asmc.4 new file mode 100644 index 00000000..a13a898c --- /dev/null +++ b/static/openbsd/man4/asmc.4 @@ -0,0 +1,65 @@ +.\" $OpenBSD: asmc.4,v 1.5 2020/09/13 10:43:40 jmc Exp $ +.\" +.\" Copyright (c) 2015 Joerg Jung +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 13 2020 $ +.Dt ASMC 4 +.Os +.Sh NAME +.Nm asmc +.Nd Apple System Management Controller (SMC) +.Sh SYNOPSIS +.Cd "asmc0 at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Apple System Management Controller (SMC), as +found in Intel based Apple devices. +.Pp +The driver possesses a collection of temperature, fan, light, and acceleration +sensor values which are made available through the +.Xr sysctl 8 +interface. +.Pp +If available, the keyboard backlight is enabled by the driver and can be +adjusted using the +.Xr wsconsctl 8 +variable +.Va keyboard.backlight . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 , +.Xr wsconsctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Joerg Jung Aq Mt jung@openbsd.org . +.Sh CAVEATS +Light sensor values may not be available on older products. +.Pp +Acceleration sensors are not available and the associated interrupt handling is +not implemented. +.Pp +Besides the sensors, the huge amount of other functions and information +available from the SMC is not supported. diff --git a/static/openbsd/man4/ast.4 b/static/openbsd/man4/ast.4 new file mode 100644 index 00000000..d327a997 --- /dev/null +++ b/static/openbsd/man4/ast.4 @@ -0,0 +1,129 @@ +.\" $OpenBSD: ast.4,v 1.13 2008/05/21 19:05:51 kettenis Exp $ +.\" $NetBSD: ast.4,v 1.7 1996/03/16 00:07:07 thorpej Exp $ +.\" +.\" Copyright (c) 1990, 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)dca.4 5.2 (Berkeley) 3/27/91 +.\" from: Id: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp +.\" +.Dd $Mdocdate: May 21 2008 $ +.Dt AST 4 +.Os +.Sh NAME +.Nm ast +.Nd multiplexing serial communications interface +.Sh SYNOPSIS +.Cd "ast0 at isa? port 0x1a0 irq 5" +.Cd "ast1 at isa? port 0x2a0 irq 6" +.Cd "com* at ast?" +.Sh DESCRIPTION +The +.Nm +driver provides support for boards that multiplex together up to four +.Tn EIA +.Tn RS-232C +.Pf ( Tn CCITT +.Tn V.28 ) +communications interfaces. +Apparently the original master of hardware using this multiplexing protocol +was AST. +.Pp +Each +.Nm +device is the master device for up to four +.Nm com +devices. +The kernel configuration specifies these +.Nm com +devices as slave devices of the +.Nm +device, as shown in +.Sx SYNOPSIS . +The slave ID given for each +.Nm com +device determines which bit in the interrupt multiplexing register is +tested to find interrupts for that device. +The +.Tn port +specification for the +.Nm +device is used to compute the base addresses for the +.Nm com +subdevices and the port for the interrupt multiplexing register. +.Pp +On a real AST card, the jumpers are as follows: +.Bl -tag -width xxxxx +.It SW1-1 +Turn ON for irq 2. +Default is OFF. +.It SW1-2 +Turn ON for irq 3. +Default is OFF. +.It SW1-3 +Turn ON for irq 4. +Default is OFF. +.It SW2-1 +Turn ON for irq 5. +This is ON for the first card, OFF otherwise. +.It SW2-2 +Turn ON for irq 6. +This is ON for the second card, OFF otherwise. +.It SW2-3 +Turn ON for irq 7. +Default is OFF. +.It SW3-1 +.Dq Compatible mode . +The +.Nm ast +driver needs extended mode, so leave this OFF. +.It SW3-2 +I/O Address. +In extended mode, this should be OFF for the first card at +0x1a0-0x1a7 and ON for the second card at 0x2a0-0x2a7. +.It SW3-3 +Interrupt sharing. +Default is OFF. +.It SW3-4 +Reserved, must be OFF. +.El +.Sh FILES +.Bl -tag -width Pa +.It Pa /dev/tty0? +.El +.Sh SEE ALSO +.Xr com 4 , +.Xr intro 4 , +.Xr isa 4 +.Sh HISTORY +The +.Nm +driver was written by Roland McGrath and placed into the public +domain. diff --git a/static/openbsd/man4/atapiscsi.4 b/static/openbsd/man4/atapiscsi.4 new file mode 100644 index 00000000..4c1ed8e9 --- /dev/null +++ b/static/openbsd/man4/atapiscsi.4 @@ -0,0 +1,100 @@ +.\" $OpenBSD: atapiscsi.4,v 1.12 2012/08/14 01:08:19 dlg Exp $ +.\" +.\" Copyright (c) 1999 Constantine Sapuntzakis. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 4. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 14 2012 $ +.Dt ATAPISCSI 4 +.Os +.Sh NAME +.Nm atapiscsi +.Nd ATAPI<->SCSI adapter +.Sh SYNOPSIS +.Cd "atapiscsi* at wdc? flags 0x0000" +.Cd "atapiscsi* at pciide? flags 0x0000" +.Sh DESCRIPTION +The +.Nm +driver supports ATAPI (also called IDE) devices such as CD-ROMs, ZIP +drives, LS-120 floppy drives, and tape drives. +All ATAPI devices talk a subset of the SCSI protocol. +.Pp +The +.Nm +driver acts like a SCSI adapter. +Thus, the ATAPI devices connected to the system will appear as SCSI devices. +ATAPI CD-ROMs will appear as +.Xr cd 4 +devices, ATAPI tape drives as +.Xr st 4 +devices, and ATAPI floppies as +.Xr sd 4 +devices. +.Pp +For performance reasons, one should avoid putting an ATAPI device and +a hard disk on the same cable. +The driver does not support bus release and, even if it did, many ATAPI +devices do not support it. +There is only one command outstanding on a cable at a time. +For example, if a hard disk and a CD drive are placed on the same cable, +the hard disk requests may get queued behind slower CD operations. +.Pp +The +.Cm flags +are used only with controllers that support DMA operations and +mode settings (like some +.Xr pciide 4 +controllers). +The lowest order (rightmost) nibble of the +.Cm flags +define the PIO mode to use. +The next four bits indicate the DMA mode and the third nibble the UltraDMA +mode. +.Pp +For each set of four bits, the 3 lower bits define the mode to use +and the last bit must be set to 1 for this setting to be used. +For DMA and UltraDMA, 0xf (1111) means +.Dq disable . +For example, a +.Cm flags +value of 0x0fac (1111 1010 1100) +means +.Do +use PIO mode 4, DMA mode 2, disable UltraDMA +.Dc . +The special setting 0x0000 means +.Dq use whatever the drive claims to support . +.Sh SEE ALSO +.Xr cd 4 , +.Xr intro 4 , +.Xr pciide 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr wdc 4 +.Sh BUGS +Slow devices, like tape drives, could do a better job of sharing the channel. +For now, we recommend you put the tape device on its own channel. diff --git a/static/openbsd/man4/ath.4 b/static/openbsd/man4/ath.4 new file mode 100644 index 00000000..76642ff3 --- /dev/null +++ b/static/openbsd/man4/ath.4 @@ -0,0 +1,353 @@ +.\" $OpenBSD: ath.4,v 1.70 2025/03/27 10:21:53 jmc Exp $ +.\" $NetBSD: ath.4,v 1.5 2004/07/03 16:58:18 mycroft Exp $ +.\" +.\" Copyright (c) 2002, 2003 Sam Leffler, Errno Consulting +.\" All rights reserved. +.\"" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer, +.\" without modification. +.\" 2. Redistributions in binary form must reproduce at minimum a disclaimer +.\" similar to the "NO WARRANTY" disclaimer below ("Disclaimer") and any +.\" redistribution must be conditioned upon including a substantially +.\" similar Disclaimer requirement for further binary redistribution. +.\" 3. Neither the names of the above-listed copyright holders nor the names +.\" of any contributors may be used to endorse or promote products derived +.\" from this software without specific prior written permission. +.\" +.\" NO WARRANTY +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +.\" LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTIBILITY +.\" AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL +.\" THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR SPECIAL, EXEMPLARY, +.\" OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER +.\" IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGES. +.\" +.\" +.\" Note: This man page was taken by Perry Metzger almost entirely +.\" from the "ath" and "ath_hal" man pages in FreeBSD. I claim no +.\" copyright because there was nearly no original work performed in +.\" doing so. Maintainers should check the FreeBSD originals for +.\" updates against the following two revisions and incorporate them +.\" if needed: +.\" +.\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ath.4,v 1.16 2004/02/18 08:30:08 maxim Exp $ +.\" parts from $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ath_hal.4,v 1.7 2004/01/07 20:49:51 blackend Exp $ +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt ATH 4 +.Os +.Sh NAME +.Nm ath +.Nd Atheros IEEE 802.11a/b/g wireless network device with GPIO +.Sh SYNOPSIS +.Cd "ath* at pci? dev ? function ?" +.Cd "ath* at cardbus? dev ? function ?" +.Cd "gpio* at ath?" +.Sh DESCRIPTION +The +.Nm +driver provides support for wireless network devices based on +the Atheros AR5210, AR5211, and AR5212 chips. +.Pp +All host/device interaction is via DMA. +The +.Nm +driver encapsulates all IP and ARP traffic as 802.11 frames, though +it can receive either 802.11 or 802.3 frames. +Transmit speed and operating mode is selectable and +depends on the specific chipset. +.Pp +Support for the various devices is as follows: +.Bl -tag -width "ARxxxx" +.It AR5210 +These devices support 802.11a operation with transmit speeds +of 6 Mbps, 9 Mbps, 12 Mbps, 18 Mbps, 24 Mbps, 36 Mbps, 48 Mbps, and 54 Mbps. +.It AR5211 +These devices support 802.11a and 802.11b operation with +transmit speeds as above for 802.11a and +1Mbps, 2Mbps, 5.5 Mbps, and 11Mbps for 802.11b operation. +.It AR5212 +These devices support 802.11a, 802.11b, and 802.11g operation with +transmit speeds as above for 802.11a, 802.11b, and 802.11g operation +(802.11g speeds are the same as for 802.11a speeds). +.El +.Pp +The actual transmit speed used is dependent on signal quality and the +.Dq rate control +algorithm employed by the driver. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.It Host AP +In this mode the adapter acts as an access point (base station) +for other cards. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +.Pp +AR5211 and AR5212 support the AES, TKIP, and Michael cryptographic +operations required for WPA in hardware but at this time the driver +does not support them. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh HARDWARE +Devices supported by the +.Nm +driver come in either CardBus or Mini PCI packages. +Wireless cards in CardBus slots may be inserted and ejected on the fly. +.Pp +The following cards are among those supported by the +.Nm +driver: +.Bl -column "Proxim Skyline 4030" "AR5212" "Mini PCI" "Standard" -offset 6n +.It Em Card Ta Em Chip Ta Em Bus Ta Em Standard +.It "3Com 3CRPAG175" Ta AR5212 Ta CardBus Ta a/b/g +.\"It "Aztech WL830PC" Ta AR5212 Ta CardBus Ta b/g +.It "Cisco AIR-CB21AG" Ta AR5212 Ta CardBus Ta a/b/g +.It "D-Link DWL-A650" Ta AR5210 Ta CardBus Ta a +.It "D-Link DWL-AB650" Ta AR5211 Ta CardBus Ta a/b +.It "D-Link DWL-A520" Ta AR5210 Ta PCI Ta a +.\"It "D-Link DWL-AG520" Ta AR5212 Ta PCI Ta a/b/g +.\"It "D-Link DWL-AG650" Ta AR5212 Ta CardBus Ta a/b/g +.\"It "D-Link DWL-G520" Ta AR5212 Ta PCI Ta b/g +.\"It "D-Link DWL-G650B" Ta AR5212 Ta CardBus Ta b/g +.\"It "Elecom LD-WL54AG" Ta AR5212 Ta CardBus Ta a/b/g +.It "Elecom LD-WL54" Ta AR5211 Ta CardBus Ta a +.\"It "Fujitsu E5454" Ta AR5212 Ta CardBus Ta a/b/g +.\"It "Fujitsu FMV-JW481" Ta AR5212 Ta CardBus Ta a/b/g +.\"It "Fujitsu E5454" Ta AR5212 Ta CardBus Ta a/b/g +.\"It "HP NC4000" Ta AR5212 Ta PCI Ta a/b/g +.It "IBM 11ABG WL LAN" Ta AR5212 Ta Mini PCI Ta a/b/g +.\"It "I/O Data WN-AB" Ta AR5212 Ta CardBus Ta a/b +.\"It "I/O Data WN-AG" Ta AR5212 Ta CardBus Ta a/b/g +.\"It "I/O Data WN-A54" Ta AR5212 Ta CardBus Ta a +.\"It "Linksys WMP55AG" Ta AR5212 Ta PCI Ta a/b/g +.It "Linksys WPC51AB" Ta AR5211 Ta CardBus Ta a/b +.\"It "Linksys WPC55AG" Ta AR5212 Ta CardBus Ta a/b/g +.\"It "NEC PA-WL/54AG" Ta AR5212 Ta CardBus Ta a/b/g +.\"It "Netgear WAG311" Ta AR5212 Ta PCI Ta a/b/g +.It "Netgear WAB501" Ta AR5211 Ta CardBus Ta a/b +.\"It "Netgear WAG511" Ta AR5212 Ta CardBus Ta a/b/g +.\"It "Netgear WG311 rev1" Ta AR5212 Ta PCI Ta b/g +.\"It "Netgear WG511T" Ta AR5212 Ta CardBus Ta b/g +.\"It "Orinoco 8480" Ta AR5212 Ta CardBus Ta a/b/g +.\"It "Orinoco 8470WD" Ta AR5212 Ta CardBus Ta a/b/g +.It "Planet WL-3560" Ta AR5211 Ta CardBus Ta a/b/g +.It "Proxim Skyline 4030" Ta AR5210 Ta CardBus Ta a +.It "Proxim Skyline 4032" Ta AR5210 Ta PCI Ta a +.\"It "Samsung SWL-5200N" Ta AR5212 Ta CardBus Ta a/b/g +.It "Senao NL-5354MP" Ta AR5212 Ta Mini PCI Ta a/b/g +.It "SMC SMC2735W" Ta AR5210 Ta CardBus Ta a +.\"It "Sony PCWA-C700" Ta AR5212 Ta CardBus Ta a/b +.\"It "Sony PCWA-C300S" Ta AR5212 Ta CardBus Ta b/g +.It "Sony PCWA-C500" Ta AR5210 Ta CardBus Ta a +.It "Wistron CM9" Ta AR5212 Ta Mini PCI Ta a/b/g +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig ath0 scan +.Pp +The following +.Xr hostname.if 5 +example configures ath0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +nwid mynwid wpakey mywpakey +inet autoconf +.Ed +.Pp +The following +.Xr hostname.if 5 +example creates a host-based access point on boot: +.Bd -literal -offset indent +mediaopt hostap +nwid mynwid wpakey mywpakey +inet 192.168.1.1 255.255.255.0 +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "ath0: unable to attach hardware; HAL status N" +The Hardware Access Layer was unable to configure the hardware +as requested. +The status code is explained in the HAL include file +.Pa sys/dev/ic/ar5xxx.h . +.It "ath0: failed to allocate descriptors: N" +The driver was unable to allocate contiguous memory for the transmit +and receive descriptors. +This usually indicates system memory is scarce and/or fragmented. +.It "ath0: unable to setup a data xmit queue!" +The request to the HAL to set up the transmit queue for normal +data frames failed. +This should not happen. +.It "ath0: unable to setup a beacon xmit queue!" +The request to the HAL to set up the transmit queue for 802.11 beacon frames +failed. +This should not happen. +.It "ath0: hardware error; resetting" +An unrecoverable error in the hardware occurred. +Errors of this sort include unrecoverable DMA errors. +The driver will reset the hardware and continue. +.It "ath0: rx FIFO overrun; resetting" +The receive FIFO in the hardware overflowed before the data could be +transferred to the host. +This typically occurs because the hardware ran short of receive +descriptors and had no place to transfer received data. +The driver will reset the hardware and continue. +.It "ath0: unable to reset hardware; hal status N" +The Hardware Access Layer was unable to reset the hardware +as requested. +The status code is explained in the HAL include file +.Pa /sys/dev/ic/ar5xxx.h . +This should not happen. +.It "ath0: unable to initialize the key cache" +The driver was unable to initialize the hardware key cache. +This should not happen. +.It "ath0: unable to start recv logic" +The driver was unable to restart frame reception. +This should not happen. +.It "ath0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware and continue. +This should not happen. +.It "ath0: bogus xmit rate 0xNNNN" +An invalid transmit rate was specified for an outgoing frame. +The frame is discarded. +This should not happen. +.It "ath0: ath_chan_set: unable to reset channel N (X MHz)" +The Hardware Access Layer was unable to reset the hardware +when switching channels during scanning. +This should not happen. +.It "ath0: unable to allocate channel table" +The driver was unable to allocate memory for the table used to hold +the set of available channels. +.It "ath0: unable to collect channel list from hal" +A problem occurred while querying the HAL to find the set of available +channels for the device. +This should not happen. +.It "ath0: failed to enable memory mapping" +The driver was unable to enable memory-mapped I/O to the PCI device registers. +This should not happen. +.It "ath0: failed to enable bus mastering" +The driver was unable to enable the device as a PCI bus master for doing DMA. +This should not happen. +.It "ath0: cannot map register space" +The driver was unable to map the device registers into the host address space. +This should not happen. +.It "ath0: could not map interrupt" +The driver was unable to allocate an IRQ for the device interrupt. +This should not happen. +.It "ath0: could not establish interrupt" +The driver was unable to install the device interrupt handler. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr cardbus 4 , +.Xr gpio 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr gpioctl 8 , +.Xr hostapd 8 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 5.2 +using a binary-only HAL module which was ported to +.Nx 2.0 . +The driver using a free HAL-replacement first appeared in +.Ox 3.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Sam Leffler , +and was ported to +.Ox +by +.An Reyk Floeter Aq Mt reyk@openbsd.org +who also wrote a free replacement of the binary-only HAL. +.Sh CAVEATS +Different regulatory domains may not be able to communicate with each +other with 802.11a as different regulatory domains do not necessarily +have overlapping channels. +.Pp +Host AP mode doesn't support power saving. +Clients attempting to use power saving mode may experience significant +packet loss (disabling power saving on the client will fix this). +.Sh BUGS +Performance in lossy environments is suboptimal. +The algorithm used to select the rate for transmitted packets is +very simplistic. +There is no software retransmit; only hardware retransmit is used. +Contributors are encouraged to replace the existing rate control algorithm +with a better one. +.Pp +The driver does not fully enable power-save operation of the chip; +consequently power use is suboptimal. +.Pp +Operation in the 2GHz band is restricted to 11b mode because the driver +does not support running the hardware in 11g mode. diff --git a/static/openbsd/man4/athn.4 b/static/openbsd/man4/athn.4 new file mode 100644 index 00000000..6a19e6cf --- /dev/null +++ b/static/openbsd/man4/athn.4 @@ -0,0 +1,274 @@ +.\" $OpenBSD: athn.4,v 1.45 2025/03/27 10:21:53 jmc Exp $ +.\" +.\" Copyright (c) 2009 Damien Bergamini . +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt ATHN 4 +.Os +.Sh NAME +.Nm athn +.Nd Atheros IEEE 802.11a/b/g/n wireless network device +.Sh SYNOPSIS +.Cd "athn* at cardbus?" +.Cd "athn* at pci?" +.Cd "athn* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver provides support for a wide variety of +Atheros 802.11n devices, ranging from the AR5008 up to the AR9287. +.Pp +The AR5008 (codenamed Owl) is the first generation of +Atheros 802.11n solutions. +It consists of two chips, a MAC/Baseband Processor and a Radio-on-a-Chip. +The MAC/Baseband Processor can be an AR5416 (PCI and CardBus form factors) +or an AR5418 (PCIe Mini Card form factor). +The radio can be an AR2122, AR2133, AR5122 or an AR5133 chip. +The AR2122 chip operates in the 2GHz spectrum and supports up to 2 +transmit paths and 2 receiver paths (2T2R). +The AR2133 chip operates in the 2GHz spectrum and supports up to 3 +transmit paths and 3 receiver paths (3T3R). +The AR5122 chip operates in the 2GHz and 5GHz spectra and supports +up to 2 transmit paths and 2 receiver paths (2T2R). +The AR5133 chip operates in the 2GHz and 5GHz spectra and supports +up to 3 transmit paths and 3 receiver paths (3T3R). +.Pp +The AR9001 (codenamed Sowl) is a Mini-PCI 802.11n solution. +It consists of two chips, an AR9160 MAC/Baseband Processor and an +AR9103 or AR9106 Radio-on-a-Chip. +The AR9103 chip operates in the 2GHz spectrum and supports up to 3 +transmit paths and 3 receiver paths (3T3R). +The AR9106 chip operates in the 2GHz and 5GHz spectra and supports +up to 3 transmit paths and 3 receiver paths (3T3R). +.Pp +The AR9220, AR9223 and AR9280 (codenamed Merlin) are the +first generation of +Atheros single-chip 802.11n solutions. +The AR9220 and AR9223 exist in PCI and Mini-PCI form factors. +The AR9280 exists in PCIe (DT92), PCIe Mini Card (XB92), +half Mini Card (HB92) and USB 2.0 (AR9280+AR7010) form factors. +The AR9220 and AR9280 operate in the 2GHz and 5GHz spectra and +support 2 transmit paths and 2 receiver paths (2T2R). +The AR9223 operates in the 2GHz spectrum and supports 2 +transmit paths and 2 receiver paths (2T2R). +.Pp +The AR9281 is a single-chip PCIe 802.11n solution. +It exists in PCIe Mini Card (XB91) and half Mini Card (HB91) form +factors. +It operates in the 2GHz spectrum and supports 1 transmit path and +2 receiver paths (1T2R). +.Pp +The AR9285 (codenamed Kite) is a single-chip PCIe 802.11n solution that +targets the value PC market. +It exists in PCIe half Mini Card (HB95) form factor only. +It operates in the 2GHz spectrum and supports a single stream (1T1R). +It can be combined with the AR3011 chip to form a combo WiFi/Bluetooth +device (WB195). +.Pp +The AR9271 is a single-chip USB 2.0 802.11n solution. +It operates in the 2GHz spectrum and supports a single stream (1T1R). +.Pp +The AR2427 is a single-chip PCIe 802.11b/g solution similar to the other +AR9280 solutions but with 802.11n capabilities removed. +It exists in PCIe Mini Card form factor only. +It operates in the 2GHz spectrum. +.Pp +The AR9227 and AR9287 are single-chip 802.11n solutions that +target mid-tier PCs. +The AR9227 exists in PCI and Mini-PCI form factors. +The AR9287 exists in PCIe half Mini Card (HB97) +and USB 2.0 (AR9287+AR7010) form factors. +They operate in the 2GHz spectrum and support 2 transmit paths and 2 +receiver paths (2T2R). +.Pp +The following table summarizes the supported chips and their capabilities. +.Bl -column "AR9001-3NX2 (AR9160+AR9106)" "2GHz/5GHz" "3x3:3" "PCI/CardBus" -offset 6n +.It Em Chipset Ta Em Spectrum Ta Em TxR:S Ta Em Bus +.It "AR5008-2NG (AR5416+AR2122)" Ta 2GHz Ta 2x2:2 Ta PCI/CardBus +.It "AR5008-3NG (AR5416+AR2133)" Ta 2GHz Ta 3x3:2 Ta PCI/CardBus +.It "AR5008-2NX (AR5416+AR5122)" Ta 2GHz/5GHz Ta 2x2:2 Ta PCI/CardBus +.It "AR5008-3NX (AR5416+AR5133)" Ta 2GHz/5GHz Ta 3x3:2 Ta PCI/CardBus +.It "AR5008E-2NG (AR5418+AR2122)" Ta 2GHz Ta 2x2:2 Ta PCIe +.It "AR5008E-3NG (AR5418+AR2133)" Ta 2GHz Ta 3x3:2 Ta PCIe +.It "AR5008E-2NX (AR5418+AR5122)" Ta 2GHz/5GHz Ta 2x2:2 Ta PCIe +.It "AR5008E-3NX (AR5418+AR5133)" Ta 2GHz/5GHz Ta 3x3:2 Ta PCIe +.It "AR9001-2NG (AR9160+AR9103)" Ta 2GHz Ta 2x2:2 Ta PCI +.It "AR9001-3NG (AR9160+AR9103)" Ta 2GHz Ta 3x3:2 Ta PCI +.It "AR9001-3NX2 (AR9160+AR9106)" Ta 2GHz/5GHz Ta 3x3:2 Ta PCI +.It "AR9220" Ta 2GHz/5GHz Ta 2x2:2 Ta PCI +.It "AR9223" Ta 2GHz Ta 2x2:2 Ta PCI +.It "AR9280" Ta 2GHz/5GHz Ta 2x2:2 Ta PCIe +.It "AR9280+AR7010" Ta 2GHz/5GHz Ta 2x2:2 Ta USB 2.0 +.It "AR9281" Ta 2GHz Ta 1x2:2 Ta PCIe +.It "AR9285" Ta 2GHz Ta 1x1:1 Ta PCIe +.It "AR9271" Ta 2GHz Ta 1x1:1 Ta USB 2.0 +.It "AR2427" Ta 2GHz Ta 1x1:1 Ta PCIe +.It "AR9227" Ta 2GHz Ta 2x2:2 Ta PCI +.It "AR9287" Ta 2GHz Ta 2x2:2 Ta PCIe +.It "AR9287+AR7010" Ta 2GHz Ta 2x2:2 Ta USB 2.0 +.El +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It Host AP +In this mode the driver acts as an access point (base station) +for other cards. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver offloads both encryption and decryption to the hardware for the +CCMP cipher. +.Pp +The transmit speed is user-selectable or can be adapted automatically by the +driver depending on the number of hardware transmission retries. +.Pp +In Host AP mode, +the driver is compatible with clients using powersave, except on AR7010 +and AR9287 USB devices. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +For USB devices, the driver needs at least version 1.1p4 of the following +firmware files, which are loaded when an interface is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/athn-open-ar7010 +.It Pa /etc/firmware/athn-open-ar9271 +.El +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +Firmware source code is available under a mix of BSD and GPLv2 licences. +A port which cross-compiles the firmware can be found in +.Pa /usr/ports/devel/open-ath9k-htc-firmware . +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig athn0 scan +.Pp +The following +.Xr hostname.if 5 +example configures athn0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +nwid mynwid wpakey mywpakey +inet autoconf +.Ed +.Pp +The following +.Xr hostname.if 5 +example creates a host-based access point on boot: +.Bd -literal -offset indent +mediaopt hostap +nwid mynwid wpakey mywpakey +inet 192.168.1.1 255.255.255.0 +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "athn0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.It "athn0: radio is disabled by hardware switch" +The radio transmitter is off and thus no packet can go out. +The driver will reset the hardware. +Make sure the laptop radio switch is on. +.It "athn0: radio switch turned off" +The radio switch has been turned off while the interface was up and running. +The driver will turn the interface down. +.It "athn0: error N, could not read firmware ..." +For some reason, the driver was unable to read the firmware file from the +filesystem. +The file might be missing or corrupted. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr cardbus 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.7 . +Support for USB 2.0 devices first appeared in +.Ox 4.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr +based on source code licensed under the ISC released in 2008 by +Atheros Communications for Linux. +.An Anthony J. Bentley Aq Mt bentley@openbsd.org +added the open source USB firmware and its cross-compiler to the ports tree. +.An Stefan Sperling Aq Mt stsp@openbsd.org +implemented driver support for the open source USB firmware. +.Sh CAVEATS +Support for 802.11n 40MHz channels and Tx aggregation is not yet implemented. +Additional work is required in +.Xr ieee80211 9 +before those features can be supported. +.Pp +On USB devices, Host AP mode is limited to 7 concurrent clients and does +not support power saving. +Clients attempting to use power saving mode may experience significant +packet loss. diff --git a/static/openbsd/man4/atphy.4 b/static/openbsd/man4/atphy.4 new file mode 100644 index 00000000..26539626 --- /dev/null +++ b/static/openbsd/man4/atphy.4 @@ -0,0 +1,34 @@ +.\" $OpenBSD: atphy.4,v 1.5 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2008 Brad Smith +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt ATPHY 4 +.Os +.Sh NAME +.Nm atphy +.Nd Attansic Technology F1/F2 10/100/1Gb Ethernet PHY +.Sh SYNOPSIS +.Cd "atphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Attansic Technology F1 10/100/1Gb Ethernet PHY and +F2 10/100 Ethernet PHY. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/atu.4 b/static/openbsd/man4/atu.4 new file mode 100644 index 00000000..a81d7d84 --- /dev/null +++ b/static/openbsd/man4/atu.4 @@ -0,0 +1,209 @@ +.\" $OpenBSD: atu.4,v 1.41 2021/10/24 12:32:42 kn Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: October 24 2021 $ +.Dt ATU 4 +.Os +.Sh NAME +.Nm atu +.Nd Atmel AT76C50x USB IEEE 802.11b wireless network device +.Sh SYNOPSIS +.Cd "atu* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver provides support for wireless network adapters based around +the Atmel AT76C503, AT76C503A, AT76C505, and AT76C505A USB chipsets and four +companion radio chipsets. +.Pp +The +.Nm +driver encapsulates all IP and ARP traffic as 802.11 frames, +though it can receive either 802.11 or 802.3 frames. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.El +.Pp +The +.Nm +driver can be configured to use hardware +Wired Equivalent Privacy (WEP). +It is strongly recommended that WEP +not be used as the sole mechanism +to secure wireless communication, +due to serious weaknesses in it. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The adapter needs some firmware files, which are loaded on demand by the +driver when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/atu-at76c503-i3863-int +.It Pa /etc/firmware/atu-at76c503-i3863-ext +.It Pa /etc/firmware/atu-at76c503-rfmd-acc-int +.It Pa /etc/firmware/atu-at76c503-rfmd-acc-ext +.It Pa /etc/firmware/atu-at76c505-rfmd-int +.It Pa /etc/firmware/atu-at76c505-rfmd-ext +.It Pa /etc/firmware/atu-intersil-int +.It Pa /etc/firmware/atu-intersil-ext +.It Pa /etc/firmware/atu-rfmd-int +.It Pa /etc/firmware/atu-rfmd-ext +.It Pa /etc/firmware/atu-rfmd2958-int +.It Pa /etc/firmware/atu-rfmd2958-ext +.It Pa /etc/firmware/atu-rfmd2958smc-int +.It Pa /etc/firmware/atu-rfmd2958smc-ext +.El +.Sh HARDWARE +The following devices are known to be supported by the +.Nm +driver: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Tn 3Com 3CRSHEW696 +.It Tn AboCom BWU613 +.It Tn Accton 2664W +.It Tn Acer Peripherals AWL300 +.It Tn Acer Peripherals AWL400 +.It Tn Actiontec 802UAT1 +.It Tn Addtron AWU120 +.It Tn Aincomm AWU2000B +.It Tn Askey Computer Voyager 1010 +.It Tn Askey Computer WLL013 (Intersil Radio) +.It Tn Askey Computer WLL013 (RFMD Radio) +.It Tn Atmel AT76C503 (Intersil Radio) +.It Tn Atmel AT76C503 (RFMD Radio) +.It Tn Atmel AT76C505 (RFMD Radio) +.It Tn Atmel AT76C505 (RFMD 2958 Radio) +.It Tn Atmel AT76C505A (RFMD 2958 Radio) +.It Tn Atmel AT76C505AS (RFMD 2958 Radio) +.It Tn Belkin F5D6050 +.It Tn Bluetake BW002 +.It Tn Compaq iPAQ h54xx/h55xx Internal WLAN +.It Tn Conceptronic C11U +.It Tn Conceptronic WL210 +.It Tn Corega WLAN USB Stick 11 +.It Tn Dick Smith Electronics CHUSB 611G +.It Tn Dick Smith Electronics WL200U +.It Tn Dick Smith Electronics WL240U +.It Tn Dick Smith Electronics XH1153 +.It Tn D-Link DWL-120 rev E +.It Tn Geowave GW-US11S +.It Tn Gigabyte GN-WLBM101 +.It Tn Gigaset WLAN +.It Tn Hewlett-Packard HN210W +.It Tn Intel AP310 AnyPoint II +.It Tn I/O DATA USB WN-B11 +.It Tn Lexar 2662W-AR +.It Tn Linksys WUSB11 802.11b +.It Tn Linksys WUSB11 802.11b v2.8 +.It Tn MSI WLAN +.It Tn Netgear MA101 +.It Tn Netgear MA101 rev B +.It Tn OQO model 01 WiFi +.It Tn Ovislink AirLive WL-1120USB +.It Tn OvisLink AirLive WL-1130USB +.It Tn Planex Communications GW-US11S +.It Tn Samsung SWL2100W +.It Tn Siemens WLL013 +.It Tn SMC EZ Connect 11Mbps (SMC2662w) +.It Tn SMC EZ Connect 11Mbps v2 (SMC2662wV2) +.It Tn Tekram U-300C +.It Tn TRENDnet TEW-229UB +.It Tn W-Buddie WN210 +.It Tn Z-Com M4Y-750 +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig atu0 scan +.Pp +The following +.Xr hostname.if 5 +example configures atu0 to join network +.Dq mynwid , +using WEP key +.Dq mywepkey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid nwkey mywepkey +inet autoconf +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Daan Vreeken +and ported to +.Ox +by +.An Theo de Raadt +and +.An David Gwynne . +.Sh CAVEATS +The +.Nm +driver does not support a lot of the functionality available in the hardware. +More work is required to properly support the IBSS, power management, +and selectable transmission rate features. diff --git a/static/openbsd/man4/atw.4 b/static/openbsd/man4/atw.4 new file mode 100644 index 00000000..98db8baf --- /dev/null +++ b/static/openbsd/man4/atw.4 @@ -0,0 +1,238 @@ +.\" $OpenBSD: atw.4,v 1.41 2025/03/27 10:21:53 jmc Exp $ +.\" $NetBSD: atw.4,v 1.8 2004/06/06 04:05:49 wiz Exp $ +.\" +.\" Copyright (c) 2003 +.\" David Young . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY David Young AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL David Young +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt ATW 4 +.Os +.Sh NAME +.Nm atw +.Nd ADMtek ADM8211 IEEE 802.11b wireless network device +.Sh SYNOPSIS +.Cd "atw* at cardbus?" +.Cd "atw* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports PCI/CardBus 802.11b wireless adapters based on the +ADMtek ADM8211. +.Pp +The ADM8211 is a bus-mastering 802.11 Media Access Controller (MAC) +which is derived from ADMtek's DEC/Intel 21143 clones (see +.Xr dc 4 +for more information). +It supports contention-free traffic (with an 802.11 Point Coordinator). +The ADM8211 integrates an RF3000 baseband processor (BBP) by RF +Microdevices. +.Pp +In a typical application, the ADM8211 is coupled with an RF front-end +by RFMD and a Silicon Laboratories Si4126 RF/IF synthesizer. +.Pp +With the ADM8211, the division of labor between the host and NIC +is different than with firmware-based NICs such as +.Xr an 4 +and +.Xr wi 4 . +The ADM8211 is still responsible for real-time 802.11 functions +such as sending ACK/RTS/CTS/ATIM frames, sending beacons, and +answering CF polls from the access point, but the host takes +responsibility for providing 802.11 functions such as scanning, +association, and authentication. +The host is also responsible for programming both the BBP and the +RF/IF synthesizer. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.El +.Pp +The +.Nm +driver can be configured to use hardware +Wired Equivalent Privacy (WEP) +(though see +.Sx BUGS , +below). +It is strongly recommended that WEP +not be used as the sole mechanism +to secure wireless communication, +due to serious weaknesses in it. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh HARDWARE +The +.Nm +driver supports PCI and CardBus cards using revisions 0x11 and 0x15 +of the ADM8211 (aka ADM8211A) and revision 0x20 (aka ADM8211B). +This includes: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It 3Com OfficeConnect 3CRSHPW796 CardBus +.It Belkin F5D6001 PCI (version 2 only) +.It Blitz NetWave Point CardBus +.It D-Link DWL-650 Rev. \&L1 CardBus +.It D-Link DWL-520 Rev. \&C1 PCI +.It LanReady WP2000 PCI +.It SMC 2635W CardBus (version 1 only) +.It TRENDnet TEW-221PC CardBus +.It Xterasys XN2511B PCI +.El +.Pp +The +.Nm +driver does not yet support cards using revision 0x30 (ADM8211C). +.\"This includes: +.\".Pp +.\".Bl -tag -width Ds -offset indent -compact +.\".El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig atw0 scan +.Pp +The following +.Xr hostname.if 5 +example configures atw0 to join network +.Dq mynwid , +using WEP key +.Dq mywepkey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid nwkey mywepkey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "atw0: failed to tune channel N" +The driver failed to tune the radio to a new channel. +The radio remains tuned to the old channel. +.It "atw0: atw_si4136_write wrote XXXX, SYNCTL still busy" +The driver waited 100ms without seeing an indication that the +ADM8211 had finished writing a register on the Si4126 RF/IF +synthesizer. +.It "atw0: device timeout" +The ADM8211 failed to generate an interrupt to acknowledge a transmit +command. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr cardbus 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T Silicon Laboratories +.%U https://www.silabs.com +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Young Aq Mt dyoung@NetBSD.org . +For features which the ADM8211 has in common with the DECchip 21x4x, +code was liberally borrowed from the +.Nx +tlp driver by +.An Jason Thorpe Aq Mt thorpej@NetBSD.org . +.Sh BUGS +The author does not fully understand what processing the duration +fields for the PLCP header and the 802.11 header undergo before +they are applied to a transmitted frame. +If the duration fields in transmitted frames are incorrect, +network performance may suffer. +.Pp +The driver does not provide rate control when the media type is +set to autoselect. +.Pp +The driver will sometimes complain that it cannot re-tune the radio +because the transmit process has not gone idle. +The author is investigating. +.Pp +Many features are still missing, especially WEP decryption and +802.11 power-saving. +.Pp +The ad-hoc mode has not been rigorously tested. +IBSSs with the same SSID may not coalesce, but this should not +matter for most applications. +.Pp +The driver is untested in the ad-hoc demo mode of Lucent WaveLAN +cards. +.Pp +The ADM8211 supports 802.11 power-saving; however, +.Nm +does not support it yet. +For time-bounded service, the ADM8211 will interoperate with an +access point which implements the 802.11 Point Coordination Function; +however, this is also not supported. +.Pp +Combinations of an ADM8211 with either an Intersil or a Marvell RF +front-end are not supported. +.Pp +.Nm +contains incomplete support for the ADM8211's WEP encryption/decryption +engine. +.Nm +does not yet support hardware WEP decryption; however, it will use +the ADM8211's crypto engine to encrypt transmitted frames. +Documentation from ADMtek claims that, in addition to the 4 104-bit +shared WEP keys, the ADM8211 will store WEP key pairs for up to 20 +peers. +The documentation provides no details, hence +.Nm +does not support the 20 key-pairs. diff --git a/static/openbsd/man4/auacer.4 b/static/openbsd/man4/auacer.4 new file mode 100644 index 00000000..fb07e1b1 --- /dev/null +++ b/static/openbsd/man4/auacer.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: auacer.4,v 1.3 2008/12/10 04:46:49 brad Exp $ +.\" $NetBSD: auacer.4,v 1.3.20.1 2008/06/02 13:21:34 mjf Exp $ +.\" +.\" Copyright (c) 2004 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 10 2008 $ +.Dt AUACER 4 +.Os +.Sh NAME +.Nm auacer +.Nd Acer Labs I/O Controller Hub integrated AC'97 audio device driver +.Sh SYNOPSIS +.Cd "auacer* at pci?" +.Cd "audio* at auacer?" +.Sh DESCRIPTION +The +.Nm +device driver supports the M5455 integrated AC'97 audio controller +of some Acer Labs I/O Controller Hub. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 4.5 . +.Sh BUGS +No support for recording or S/PDIF. diff --git a/static/openbsd/man4/audio.4 b/static/openbsd/man4/audio.4 new file mode 100644 index 00000000..ebcd3be3 --- /dev/null +++ b/static/openbsd/man4/audio.4 @@ -0,0 +1,520 @@ +.\" $OpenBSD: audio.4,v 1.87 2022/03/31 17:27:20 naddy Exp $ +.\" $NetBSD: audio.4,v 1.20 1998/05/28 17:27:15 augustss Exp $ +.\" +.\" Copyright (c) 1996 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by John T. Kohl. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt AUDIO 4 +.Os +.Sh NAME +.Nm audio , +.Nm audioctl +.Nd device-independent audio driver layer +.Sh SYNOPSIS +.Cd "audio* at ..." +.Pp +.In sys/types.h +.In sys/ioctl.h +.In sys/audioio.h +.In string.h +.Sh DESCRIPTION +The +.Nm audio +driver provides support for various audio peripherals. +It provides a uniform programming interface layer above different +underlying audio hardware drivers. +.Pp +In addition to hardware mixer controls like those +documented in +.Xr azalia 4 , +the +.Nm +driver exposes the +.Va record.enable +control. +The superuser can change it with +.Xr mixerctl 8 . +It accepts the following values: +.Pp +.Bl -tag -offset indent -width "sysctl" -compact +.It Cm on +Recording is enabled. +.It Cm off +Silence is returned instead of the recorded samples. +.It Cm sysctl +Behavior is controlled by the +.Va kern.audio.record +.Xr sysctl 2 +variable. +This is the default. +.El +.Pp +There are two types of device files available for audio operation: +.Bl -dash -offset indent +.It +Audio devices are used for recording or playback of digital samples. +.It +Control devices are used to manipulate audio device +parameters like volume or recording source. +They can also read certain +.Nm +driver variables while it is in use. +.El +.Sh AUDIO DEVICES +When audio devices are opened, +they attempt to maintain the previous audio sample format and record/playback mode. +In addition, if one is opened read-only +(write-only) the device is set to record-only (play-only) mode with +recording (playing) unpaused. +.Pp +If a writing process does not call +.Xr write 2 +frequently enough to provide samples at the pace the hardware +consumes them, silence is inserted. +If a reading process does not call +.Xr read 2 +frequently enough, it will simply miss samples. +.Pp +The following +.Xr ioctl 2 +commands are supported on the sample devices: +.Pp +.Bl -tag -width Ds -compact +.It Dv AUDIO_GETDEV Fa "audio_device_t *" +This command fetches the current hardware device information into the +.Vt audio_device_t * +argument. +.Bd -literal +typedef struct audio_device { + char name[MAX_AUDIO_DEV_LEN]; + char version[MAX_AUDIO_DEV_LEN]; + char config[MAX_AUDIO_DEV_LEN]; +} audio_device_t; +.Ed +.Pp +.It Dv AUDIO_SETPAR Fa "struct audio_swpar *" +.It Dv AUDIO_GETPAR Fa "struct audio_swpar *" +Set or get audio parameters as encoded in the +.Vt audio_swpar +structure. +.Bd -literal +struct audio_swpar { + unsigned int sig; /* if 1, encoding is signed */ + unsigned int le; /* if 1, encoding is little-endian */ + unsigned int bits; /* bits per sample */ + unsigned int bps; /* bytes per sample */ + unsigned int msb; /* if 1, bits are msb-aligned */ + unsigned int rate; /* common play & rec sample rate */ + unsigned int pchan; /* play channels */ + unsigned int rchan; /* rec channels */ + unsigned int nblks; /* number of blocks in play buffer */ + unsigned int round; /* common frames per block */ +}; +.Ed +.Pp +When setting the device parameters with +.Dv AUDIO_SETPAR , +the +.Vt audio_swpar +structure should first be initialized with +.Bd -literal +struct audio_swpar ap; + +AUDIO_INITPAR(&ap); +.Ed +.Pp +and then only the values to be changed should be set. +This ensures that the software will work with future versions +of the driver. +The driver will attempt to set the given parameters; if the +device doesn't support them, it will choose other parameters. +Then the software must call +.Dv AUDIO_GETPAR +to obtain the parameters in use. +.Pp +The parameters are as follows: +.Bl -tag -width "round" +.It Va bits +Number of bits per sample: must be between 1 and 32. +.It Va bps +Bytes per sample; if specified, it must be large enough to hold all bits. +By default it's set to the smallest power of two large enough to hold +.Va bits . +.It Va sig +If set (i.e. non-zero) then the samples are signed; +otherwise they are unsigned. +.It Va le +If set then the byte order is little endian; +if not, it is big endian. +It is meaningful only if +.Va bps +> 1. +.It Va msb +If set, then the +.Va bits +are aligned in the packet to the most significant bit +(i.e. lower bits are padded), +otherwise to the least significant bit +(i.e. higher bits are padded). +It's meaningful only if +.Va bits +< +.Va bps +* 8. +.It Va rchan +The number of recorded channels; meaningful only if the +device is opened for reading. +.It Va pchan +The number of channels playing; meaningful only if +the device is opened for writing. +.It Va rate +The sampling frequency in Hz. +.It Va nblks +The number of blocks in the play buffer. +.It Va round +The audio block size. +.El +.Pp +.It Dv AUDIO_START +Start playback and/or recording immediately. +If the device is open for writing (playback), then +the play buffer must be filled with the +.Xr write 2 +syscall. +The buffer size is obtained by multiplying +the +.Va nblks , +.Va round , +and +.Va bps +parameters obtained with +.Dv AUDIO_GETPAR . +.Pp +.It Dv AUDIO_STOP +Stop playback and recording immediately. +.Pp +.It Dv AUDIO_GETPOS Fa "struct audio_pos *" +Fetch an atomic snapshot of device timing information in the +.Vt audio_pos +structure. +.Bd -literal +struct audio_pos { + unsigned int play_pos; /* total bytes played */ + unsigned int play_xrun; /* bytes of silence inserted */ + unsigned int rec_pos; /* total bytes recorded */ + unsigned int rec_xrun; /* bytes dropped */ +}; +.Ed +.Pp +The properties have the following meaning: +.Bl -tag -width "play_xrun" +.It Va play_pos +Total number of bytes played by the device since playback started +(a.k.a the device wall clock). +.It Va play_xrun +The number of bytes corresponding to silence played because +.Xr write 2 +wasn't called fast enough. +.It Va rec_pos +Total number of bytes recorded by the device since recording started +(a.k.a the device wall clock). +.It Va rec_xrun +The number of bytes dropped because +.Xr read 2 +wasn't called fast enough. +.El +.Pp +.It Dv AUDIO_GETSTATUS Fa "struct audio_status *" +Fetch the current device status from the audio driver in the +.Vt audio_status +structure. +This +.Xr ioctl 2 +is intended for use with diagnostic tools +and is of no use to audio programs. +.Bd -literal +struct audio_status { +#define AUMODE_PLAY 0x01 +#define AUMODE_RECORD 0x02 + int mode; /* current mode */ + int pause; /* not started yet */ + int active; /* playing/recording in progress */ +}; +.Ed +.Pp +The properties have the following meaning: +.Bl -tag -width "active" +.It Va mode +The current mode determined by +.Xr open 2 +flags. +.It Va pause +If set, indicates that +.Dv AUDIO_STOP +was called, and the device is not attempting to start. +.It Va active +If set, indicates that the device is playing and/or recording. +.El +.El +.Sh CONTROL DEVICES +Control devices support the following +.Xr ioctl 2 +commands: +.Pp +.Bl -tag -width Ds -compact +.It Dv AUDIO_GETDEV Fa "audio_device_t *" +.It Dv AUDIO_GETPOS Fa "struct audio_pos *" +.It Dv AUDIO_GETSTATUS Fa "struct audio_status *" +.It Dv AUDIO_GETPAR Fa "struct audio_swpar *" +.It Dv AUDIO_SETPAR Fa "struct audio_swpar *" +These commands are the same as described above for the audio devices. +While the audio device is open, +.Dv AUDIO_SETPAR +may not be used. +.Pp +.It Dv AUDIO_MIXER_READ Fa "mixer_ctrl_t *" +.It Dv AUDIO_MIXER_WRITE Fa "mixer_ctrl_t *" +These commands read the current mixer state or set new mixer state for +the specified device +.Va dev . +.Va type +identifies which type of value is supplied in the +.Vt mixer_ctrl_t * +argument. +.Bd -literal +#define AUDIO_MIXER_CLASS 0 +#define AUDIO_MIXER_ENUM 1 +#define AUDIO_MIXER_SET 2 +#define AUDIO_MIXER_VALUE 3 +typedef struct mixer_ctrl { + int dev; /* input: nth device */ + int type; + union { + int ord; /* enum */ + int mask; /* set */ + mixer_level_t value; /* value */ + } un; +} mixer_ctrl_t; + +#define AUDIO_MIN_GAIN 0 +#define AUDIO_MAX_GAIN 255 +typedef struct mixer_level { + int num_channels; + u_char level[8]; /* [num_channels] */ +} mixer_level_t; +#define AUDIO_MIXER_LEVEL_MONO 0 +#define AUDIO_MIXER_LEVEL_LEFT 0 +#define AUDIO_MIXER_LEVEL_RIGHT 1 +.Ed +.Pp +For a mixer value, the +.Va value +field specifies both the number of channels and the values for each +channel. +If the channel count does not match the current channel count, the +attempt to change the setting may fail (depending on the hardware +device driver implementation). +For an enumeration value, the +.Va ord +field should be set to one of the possible values as returned by a prior +.Dv AUDIO_MIXER_DEVINFO +command. +The type +.Dv AUDIO_MIXER_CLASS +is only used for classifying particular +.Nm mixer +device types and is not used for +.Dv AUDIO_MIXER_READ +or +.Dv AUDIO_MIXER_WRITE . +.Pp +.It Dv AUDIO_MIXER_DEVINFO Fa "mixer_devinfo_t *" +This command is used iteratively to fetch audio +.Nm mixer +device information into the input/output +.Vt mixer_devinfo_t * +argument. +To query all the supported devices, start with an index field of +0 and continue with successive devices (1, 2, ...) until the +command returns an error. +.Bd -literal +typedef struct mixer_devinfo { + int index; /* input: nth mixer device */ + audio_mixer_name_t label; + int type; + int mixer_class; + int next, prev; +#define AUDIO_MIXER_LAST -1 + union { + struct audio_mixer_enum { + int num_mem; + struct { + audio_mixer_name_t label; + int ord; + } member[32]; + } e; + struct audio_mixer_set { + int num_mem; + struct { + audio_mixer_name_t label; + int mask; + } member[32]; + } s; + struct audio_mixer_value { + audio_mixer_name_t units; + int num_channels; + int delta; + } v; + } un; +} mixer_devinfo_t; +.Ed +.Pp +The +.Va label +field identifies the name of this particular mixer control. +The +.Va index +field may be used as the +.Va dev +field in +.Dv AUDIO_MIXER_READ +and +.Dv AUDIO_MIXER_WRITE +commands. +The +.Va type +field identifies the type of this mixer control. +Enumeration types are typically used for on/off style controls (e.g., a +mute control) or for input/output device selection (e.g., select +recording input source from CD, line in, or microphone). +Set types are similar to enumeration types but any combination +of the mask bits can be used. +.Pp +The +.Va mixer_class +field identifies what class of control this is. +This value is set to the index value used to query the class itself. +The +.Pq arbitrary +value set by the hardware driver may be determined by examining the +.Va mixer_class +field of the class itself, +a mixer of type +.Dv AUDIO_MIXER_CLASS . +For example, a mixer level controlling the input gain on the +.Dq line in +circuit would have a +.Va mixer_class +that matches an input class device with the name +.Dq inputs +.Dv ( AudioCinputs ) +and would have a +.Va label +of +.Dq line +.Dv ( AudioNline ) . +Mixer controls which control audio circuitry for a particular audio +source (e.g., line-in, CD in, DAC output) are collected under the input class, +while those which control all audio sources (e.g., master volume, +equalization controls) are under the output class. +Hardware devices capable of recording typically also have a record class, +for controls that only affect recording, +and also a monitor class. +.Pp +The +.Va next +and +.Va prev +may be used by the hardware device driver to provide hints for the next +and previous devices in a related set (for example, the line in level +control would have the line in mute as its +.Dq next +value). +If there is no relevant next or previous value, +.Dv AUDIO_MIXER_LAST +is specified. +.Pp +For +.Dv AUDIO_MIXER_ENUM +mixer control types, +the enumeration values and their corresponding names are filled in. +For example, a mute control would return appropriate values paired with +.Dv AudioNon +and +.Dv AudioNoff . +For the +.Dv AUDIO_MIXER_VALUE +and +.Dv AUDIO_MIXER_SET +mixer control types, the channel count is +returned; the units name specifies what the level controls (typical +values are +.Dv AudioNvolume , +.Dv AudioNtreble , +and +.Dv AudioNbass ) . +.\" For AUDIO_MIXER_SET mixer control types, what is what? +.El +.Pp +A process may read the control device to get notifications about +mixer changes. +Whenever a control changes, the +.Xr read 2 +function fetches an integer identifying the control. +It may be used in the +.Va dev +field of the +.Va mixer_ctrl +structure to call +.Dv AUDIO_MIXER_READ . +.Pp +In contrast to audio devices, which have the exclusive open property, +control devices can be opened at any time in write-only mode. +Only one reader is allowed at a time. +.Sh FILES +.Bl -tag -width /dev/audioctlN -compact +.It Pa /dev/audio Ns Ar N +Audio device. +.It Pa /dev/audioctl Ns Ar N +Control device. +.El +.Sh SEE ALSO +.Xr aucat 1 , +.Xr cdio 1 , +.Xr sndioctl 1 , +.Xr ioctl 2 , +.Xr sio_open 3 , +.Xr sioctl_open 3 , +.Xr ac97 4 , +.Xr uaudio 4 , +.Xr sndio 7 , +.Xr audioctl 8 , +.Xr mixerctl 8 , +.Xr sndiod 8 , +.Xr audio 9 +.\" .Sh BUGS diff --git a/static/openbsd/man4/aue.4 b/static/openbsd/man4/aue.4 new file mode 100644 index 00000000..1e22820a --- /dev/null +++ b/static/openbsd/man4/aue.4 @@ -0,0 +1,214 @@ +.\" $OpenBSD: aue.4,v 1.39 2022/02/17 12:24:08 jsg Exp $ +.\" $NetBSD: aue.4,v 1.9 2002/07/11 00:23:31 rh Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/aue.4,v 1.2 2000/01/07 22:18:47 wpaul Exp $ +.\" +.Dd $Mdocdate: February 17 2022 $ +.Dt AUE 4 +.Os +.Sh NAME +.Nm aue +.Nd ADMtek AN986/ADM8511 Pegasus family 10/100 USB Ethernet device +.Sh SYNOPSIS +.Cd "aue* at uhub?" +.Cd "acphy* at mii?" +.Cd "bmtphy* at mii?" +.Cd "sqphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Ethernet adapters based on the ADMtek +AN986 ("Pegasus") and ADM8511 ("Pegasus II") chipsets. +This includes the following adapters: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Tn 3Com 3c460b +.It Tn Abocom UFE1000 +.It Tn Abocom DSB650TX +.It Tn Accton USB320-EC +.It Tn Accton SpeedStream Ethernet +.It Tn Admtek Pegasus +.It Tn Admtek Pegasus II +.It Tn AEI USB Fast Ethernet +.It Tn Allied Telesyn AT-USB100 +.It Tn ATEN UC-110T +.It Tn Belkin F5D5050 +.It Tn Billionton Systems USB100 +.It Tn Billionton Systems USB100EL +.It Tn Billionton Systems USB100LP +.It Tn Billionton Systems USBE100 +.It Tn Corega FEther USB-TX +.It Tn Corega FEther USB-TXS +.It Tn D-Link DSB-650 +.It Tn D-Link DSB-650TX +.It Tn D-Link DSB-650TX-PNA +.It Tn ELCON Systemtechnik Goldpfeil P-LAN +.It Tn Elecom LD-USB/TX +.It Tn Elecom LD-USB20 +.It Tn Elecom LD-USBL/TX +.It Tn Elsa Microlink USB2Ethernet +.It Tn GIGABYTE GN-BR402W +.It Tn Hawking UF100 +.It Tn HP HN210E +.It Tn I/O DATA USB ET/TX +.It Tn I/O DATA USB ET/TX-S +.It Tn I/O DATA ETX-US2 +.It Tn Kingston KNU101TX +.It Tn Laneed LD-USBL/TX +.It Tn Linksys USB100TX +.It Tn Linksys USB100H1 +.It Tn Linksys USB10T +.It Tn Linksys USB10TA +.It Tn Linksys USB10TX +.It Tn Logitec LAN-TX/U1H2 +.It Tn Melco Inc. LUA-TX +.It Tn Melco Inc. LUA2-TX +.It Tn Microsoft MN110 +.It Tn Mobility EasiDock Ethernet +.It Tn Netgear FA101 +.It Tn Omnidirectional Control Technology USB TO Ethernet +.It Tn Siemens SpeedStream USB +.It Tn Smartbridges smartNIC 2 +.It Tn SMC 2202USB/ETH +.It Tn SMC 2206USB/ETH +.It Tn SOHOware NUB100 +.It Tn SOHOware NUB110 +.El +.Pp +The Pegasus family of chipsets contain a 10/100 +.Tn Ethernet +MAC with an MII interface and are designed to work with both +.Tn Ethernet +and HomePNA transceivers. +Although the chipsets are designed to interface with +100Mbps peripherals, the USB 1.x standards specify a maximum +transfer speed of 12Mbps. +Users should therefore not expect to actually +achieve 100Mbps speeds with these devices. +.Pp +The Pegasus chipsets support a 64-bit multicast hash table, single perfect +filter entry for the station address and promiscuous mode. +Packets are +received and transmitted over separate USB bulk transfer endpoints. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width tenletters +.It autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +The +.Ar mediaopt +option can also be used to enable +.Ar full-duplex +operation. +Not specifying +.Ar full duplex +implies +.Ar half-duplex +mode. +.It 100baseTX +Set 100Mbps (Fast +.Tn Ethernet ) +operation. +The +.Ar mediaopt +option can also be used to enable +.Ar full-duplex +operation. +Not specifying +.Ar full duplex +implies +.Ar half-duplex +mode. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width tenletters +.It full-duplex +Force full duplex operation. +The interface will operate in +half duplex mode if this media option is not specified. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "aue0: watchdog timeout" +A packet was queued for transmission and a transmit command was +issued, however the device failed to acknowledge the transmission +before a timeout expired. +.It "aue0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.El +.Sh SEE ALSO +.Xr acphy 4 , +.Xr arp 4 , +.Xr bmtphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr sqphy 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T ADMtek AN986 and ADM8511 data sheets +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 4.0 . +.Ox +support was added in +.Ox 2.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ee.columbia.edu +and ported to +.Ox +by +.An Aaron Campbell Aq Mt aaron@openbsd.org . diff --git a/static/openbsd/man4/auglx.4 b/static/openbsd/man4/auglx.4 new file mode 100644 index 00000000..654cd734 --- /dev/null +++ b/static/openbsd/man4/auglx.4 @@ -0,0 +1,40 @@ +.\" $OpenBSD: auglx.4,v 1.2 2010/02/25 00:18:12 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Marc Balmer +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 25 2010 $ +.Dt AUGLX 4 +.Os +.Sh NAME +.Nm auglx +.Nd AMD Geode LX CS5536 integrated AC'97 audio device +.Sh SYNOPSIS +.Cd "auglx* at pci?" +.Cd "audio* at auglx?" +.Sh DESCRIPTION +The +.Nm +device driver supports the integrated AC'97 audio controller +of the AMD Geode LX CS5536 companion chip. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.4 . diff --git a/static/openbsd/man4/auich.4 b/static/openbsd/man4/auich.4 new file mode 100644 index 00000000..6762a363 --- /dev/null +++ b/static/openbsd/man4/auich.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: auich.4,v 1.25 2010/02/25 00:18:01 sthen Exp $ +.\" +.\" Copyright (c) 2000-2001 Michael Shalayeff +.\" All rights reserved +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, USE, DATA, OR PROFITS; OR +.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, +.\" WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR +.\" OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF +.\" ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 25 2010 $ +.Dt AUICH 4 +.Os +.Sh NAME +.Nm auich +.Nd Intel ICH integrated AC'97 audio device +.Sh SYNOPSIS +.Cd "auich* at pci? flags 0x0000" +.Cd "audio* at auich?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the integrated AC'97 audio controller present +on the Intel ICH I/O controller hub and compatible chipsets. +.Pp +Supported chipsets: +.Pp +.Bl -bullet -compact -offset indent +.It +AMD 768, 8111 +.It +Intel 6300ESB/6321ESB +.It +Intel 82440MX +.It +Intel 82801 (ICH, ICH0, ICH2, ICH3, ICH4, ICH5, ICH6, ICH7) +.It +NVIDIA nForce, nForce2, nForce3, nForce4 +.It +SiS 7012 +.El +.Pp +The +.Nm +DMA engine supports full-duplex operation and has separate channels +for line input and microphone. +Unfortunately, simultaneous recording from both line and microphone inputs +is not supported due to the current +.Xr ac97 4 +design. +Setting +.Ar flags +to 0x0001 will compensate for machines that have reversed stereo. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.8 . +.Sh CAVEATS +Some hardware implementations only support 48kHz sampling rates. diff --git a/static/openbsd/man4/auixp.4 b/static/openbsd/man4/auixp.4 new file mode 100644 index 00000000..cf97f41d --- /dev/null +++ b/static/openbsd/man4/auixp.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: auixp.4,v 1.11 2010/09/19 12:41:23 jmc Exp $ +.\" $NetBSD: auixp.4,v 1.4 2005/06/22 04:19:09 kent Exp $ +.\" +.\" Copyright (c) 2004, 2005 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Reinoud Zandijk. +.\" +.\" Manual page template from auich.4 by Jason Thorpe +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 19 2010 $ +.Dt AUIXP 4 +.Os +.Sh NAME +.Nm auixp +.Nd ATI SB200/SB300/SB400/SB600 integrated AC'97 audio device +.Sh SYNOPSIS +.Cd "auixp* at pci?" +.Cd "audio* at auixp?" +.Sh DESCRIPTION +The +.Nm +device driver supports the integrated AC'97 audio controller +of the ATI SB200/SB300/SB400/SB600 I/O controller hub. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 3.8 . +.Sh BUGS +S/PDIF support is not fully implemented. diff --git a/static/openbsd/man4/autri.4 b/static/openbsd/man4/autri.4 new file mode 100644 index 00000000..4b581cea --- /dev/null +++ b/static/openbsd/man4/autri.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: autri.4,v 1.8 2007/05/31 19:19:49 jmc Exp $ +.\" $NetBSD: autri.4,v 1.1 2001/11/18 16:46:49 augustss Exp $ +.\" +.\" Copyright (c) 2001 SOMEYA Yoshihiko and KUROSAWA Takahiro. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt AUTRI 4 +.Os +.Sh NAME +.Nm autri +.Nd Trident 4DWAVE-DX/NX, SiS 7018, ALi M5451 audio device +.Sh SYNOPSIS +.Cd "autri* at pci? flags 0x0000" +.Cd "audio* at autri?" +.Cd "midi* at autri?" +.Sh DESCRIPTION +The +.Nm +device driver supports the AC'97 audio controller found in +Trident 4DWAVE-DX/NX, SiS 7018 and ALi M5451. +.Nm +typically has reversed stereo channels. +The driver compensates for this, but the compensation can be turned off +by setting flags to 0x0001. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr midi 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 3.1 . diff --git a/static/openbsd/man4/auvia.4 b/static/openbsd/man4/auvia.4 new file mode 100644 index 00000000..50fbc216 --- /dev/null +++ b/static/openbsd/man4/auvia.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: auvia.4,v 1.12 2009/03/16 22:47:45 sobrado Exp $ +.\" $NetBSD: auvia.4,v 1.1 2000/03/31 05:49:59 tsarna Exp $ +.\" +.\" Copyright (c) 2000 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Tyler C. Sarna +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 16 2009 $ +.Dt AUVIA 4 +.Os +.Sh NAME +.Nm auvia +.Nd VIA VT82C686A/VT8233/VT8235/VT8237 integrated AC'97 audio device +.Sh SYNOPSIS +.Cd "auvia* at pci?" +.Cd "audio* at auvia?" +.Sh DESCRIPTION +The +.Nm +device driver supports the integrated AC'97 audio controller +of the +.Tn VIA Technologies VT82C686A +Southbridge, +.Tn VIA Technologies VT8233, VT8235, VT8237 +chips found on some motherboards. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.8 . diff --git a/static/openbsd/man4/axe.4 b/static/openbsd/man4/axe.4 new file mode 100644 index 00000000..62f455a6 --- /dev/null +++ b/static/openbsd/man4/axe.4 @@ -0,0 +1,175 @@ +.\" Copyright (c) 1997, 1998, 1999, 2000-2003 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/axe.4,v 1.3 2003/05/29 21:28:35 ru Exp $ +.\" $OpenBSD: axe.4,v 1.48 2022/02/18 10:24:32 jsg Exp $ +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt AXE 4 +.Os +.Sh NAME +.Nm axe +.Nd ASIX Electronics AX88172/AX88178/AX88772 10/100/1Gb USB Ethernet device +.Sh SYNOPSIS +.Cd "axe* at uhub?" +.Cd "rgephy* at mii?" +.Cd "rlphy* at mii?" +.Cd "eephy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Ethernet adapters based on the ASIX +Electronics AX88172, AX88178, and AX88772 USB 2.0 chipsets, including the +following: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Apple USB Ethernet Adapter A1277 +.It ATEN UC-210T +.It BAFO BF-320 +.It Billionton Systems USB2AR +.It Buffalo(MELCO) LUA-U2-GT +.It Buffalo(MELCO) LUA-U2-KTX +.It Corega FEther USB2-TX +.It D-Link DUB-E100 +.It Delock Gigabit USB 2.0 Ethernet Adapter +.It Good Way GWUSB2E +.It Hawking UF200 +.It Intellinet USB 2.0 to Ethernet (rev A) +.It IO-Data ETG-US2 +.It JVC MP-PRX1 +.It Konig CMP-NWUSB20 +.It Lenovo USB 2.0 Ethernet +.It Level One USB-0200 +.It Level One USB-0301 +.It Linksys USB200M +.It Linksys USB1000 +.It Logitec LAN-GTJ/U2 +.It Netgear FA120 +.It Nintendo Wii USB Lan Ethernet Adapter RVL-015 +.It OQO model 01+ Ethernet +.It Sitecom LN-029 +.It SMC 2209USB/ETH +.It SnapPort USB 2.0 LAN Adapter +.It ST Lab USB 2.0 Fast Ethernet +.It Surecom EP-1427X-2 +.It System TALKS SGC-X2UL +.It TRENDnet TU2-ET100 +.It Z-TEK ZK-R01-2 +.El +.Pp +The AX88172, AX88178, and AX88772 are USB 2.0 devices designed to work with +either Ethernet or HomePNA transceivers. +The AX88172 and AX88772 contain 10/100 Ethernet MACs with MII interfaces. +The AX88178 contains a 10/100/1Gb Ethernet MAC with a GMII/MII +interface. +All adapters will operate with either USB 1.x or USB 2.0 controllers, however +performance with 1.x controllers will be limited since the USB 1.x standard +specifies a maximum transfer speed of 12Mbps. +Users with USB 1.x controllers should therefore not expect to actually +achieve 100Mbps speeds with these devices. +.Pp +A 64-bit multicast hash table is supported, +single perfect filter entry for the station address, +all-multicast mode, and promiscuous mode. +Packets are +received and transmitted over separate USB bulk transfer endpoints. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width "autoselect" +.It autoselect +Enable autoselection of the media type and options (this is the default). +The user can manually override the autoselected mode by adding media +options to the appropriate +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.It 1000baseT +Set 1000Mbps (Gigabit Ethernet) operation (AX88178 only). +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width "full-duplex" +.It full-duplex +Force full-duplex operation. +.It half-duplex +Force half-duplex operation. +.El +.Pp +The interface will operate in +half-duplex mode if no media option is specified. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "axe0: watchdog timeout" +A packet was queued for transmission and a transmit command was +issued, however the device failed to acknowledge the transmission +before a timeout expired. +.It "axe0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr eephy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr rgephy 4 , +.Xr rlphy 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T "ASIX AX88172 data sheet" +.%U https://www.asix.com.tw +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@windriver.com +and ported to +.Ox +by +.An Greg Taleck Aq Mt taleck@oz.net . diff --git a/static/openbsd/man4/axen.4 b/static/openbsd/man4/axen.4 new file mode 100644 index 00000000..5fb1ad0a --- /dev/null +++ b/static/openbsd/man4/axen.4 @@ -0,0 +1,89 @@ +.\" $OpenBSD: axen.4,v 1.11 2024/10/07 07:35:40 kevlo Exp $ +.\" +.\" Copyright (c) 2013 Yojiro UO +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 7 2024 $ +.Dt AXEN 4 +.Os +.Sh NAME +.Nm axen +.Nd ASIX Electronics AX88179/AX88179A/AX88772D 10/100/1Gb USB Ethernet device +.Sh SYNOPSIS +.Cd "axen* at uhub?" +.Cd "rgephy* at mii?" +.Cd "ukphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Ethernet adapters based on the ASIX +Electronics AX88179/AX88179A/AX88772D chipset, including the following: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It D-Link DUB-1312 +.It Kuroutoshikou GbE-USB3.0 +.It Logitec LAN-GTJU3 +.It Sitecom LN-032 +.It StarTech USB31000S +.It TP-LINK UE300C v2 +.It TP-Link UE306 +.It Ugreen CM650-15632 +.El +.Pp +The AX88772D is a USB 2.0 device which supports both +10 and 100Mbps speeds in either full or half duplex. +The AX88179 and AX88179A are USB 3.0 devices, which contain +a 10/100/1Gb Ethernet MAC with a GMII/MII interface. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width "autoselect" +.It autoselect +Enable autoselection of the media type and options (this is the default). +The user can manually override the autoselected mode by adding media +options to the appropriate +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.It 1000baseT +Set 1000Mbps (Gigabit Ethernet) operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr rgephy 4 , +.Xr ukphy 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Yojiro UO Aq Mt yuo@nui.org . diff --git a/static/openbsd/man4/axppmic.4 b/static/openbsd/man4/axppmic.4 new file mode 100644 index 00000000..a3a58211 --- /dev/null +++ b/static/openbsd/man4/axppmic.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: axppmic.4,v 1.3 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt AXPPMIC 4 +.Os +.Sh NAME +.Nm axppmic +.Nd X-Powers AXP Power Management IC +.Sh SYNOPSIS +.Cd "axppmic* at iic?" +.Cd "axppmic* at rsb?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the X-Powers AXP Power Management ICs. +Depending on the model, these devices have temperature, voltage and +current sensors and power indicators. +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sxirsb 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/azalia.4 b/static/openbsd/man4/azalia.4 new file mode 100644 index 00000000..818d4dd9 --- /dev/null +++ b/static/openbsd/man4/azalia.4 @@ -0,0 +1,269 @@ +.\" $OpenBSD: azalia.4,v 1.28 2025/05/04 23:45:28 tedu Exp $ +.\" $NetBSD: azalia.4,v 1.2 2005/06/22 04:19:09 kent Exp $ +.\" +.\" Copyright (c) 2005 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by TAMURA Kent +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 4 2025 $ +.Dt AZALIA 4 +.Os +.Sh NAME +.Nm azalia +.Nd generic High Definition Audio device +.Sh SYNOPSIS +.Cd "azalia* at pci?" +.Cd "audio* at azalia?" +.Sh DESCRIPTION +The +.Nm +device driver is expected to support any PCI device which is +compliant with the High Definition Audio Specification 1.0. +.Pp +The High Definition Audio (HDA) specification describes a flexible and +extensible infrastructure to support high quality audio. +HDA supports sample rates up to 192 kHz, bit rates of up to 32 bits per +sample, and up to 16 channels in audio streams. +It also supports S/PDIF input/output as well as jack retasking and sensing. +The HDA specification defines a controller register set and a codec +architecture. +.Sh MIXER INTERFACE +The codec is the main audio processor. +Configuration of the device, such as selecting playback sample rate +or decreasing the volume, is handled by the codec. +Codecs are comprised of interconnected widgets. +Common examples of widgets include DACs (digital to analog converter), +ADCs (analog to digital converter), selectors, mixers, and pin +complexes (input/output jacks). +Widgets may have fixed or controllable properties. +Some of these properties include source selection, amplifier gain, +mute, and operational direction. +.Pp +The mixer interface for +.Nm +is designed to allow the user to control most properties of the widgets. +When +.Nm +first attaches and configures the device, it will set all widgets to +unmuted, moderate volume, and configure connections such that stereo +playback and recording will work with the expected input/output pins. +.Pp +There are a wide range of HDA codecs. +Some have only a few widgets that don't have many controllable +properties, and some may have many, very controllable widgets. +The mixer interface on one +.Nm +may be very different than the mixer interface on another. +.Pp +Mixer item names describe the widget and property being controlled. +Names take the following form: +.Bd -literal +.[][_] +.Ed +.Pp +The mixer class gives a hint as to the purpose of the control. +The widget type enumerator is used to distinguish different widgets +of the same type. +The enumeration starts at 2: the first widget of each type is not +enumerated. +The enumeration order is meaningless. +The property is optional. +Generally, if there is no property, the mixer item is an amplifier gain +control. +.Pp +The following are the widget type names used in mixer control names: +.Bl -tag -width "SPDIF-in" +.It Cm dac +Digital to analog converter, usually used for playback. +The audio stream channels these widgets will convert are encoded into +their name in the form of :. +For example, +.Cm dac-0:1 +converts channels 0 and 1 (stereo). +However, a dac that is connected to built-in speakers or front +panel headphone jacks by default will convert audio stream channels +starting at 0 if the dac would otherwise not be converting any channels. +For example, if +.Cm dac-2:3 +is the default dac for the built-in speakers in a laptop, +.Cm dac-2:3 +will convert channels 0 and 1 when a stereo audio stream is being played. +This is to allow simultaneous stereo playback on both the built-in speakers +and a line or headphone jack. +.It Cm dig-dac +Digital output converter, usually an S/PDIF transmitter. +The audio stream channels these widgets will convert are encoded into +their name in the form of :. +For example, +.Cm dig-dac-0:1 +converts channels 0 and 1 (stereo). +.It Cm adc +Analog to digital converter, usually used for recording. +The audio stream channels these widgets will convert are encoded into +their name in the form of :. +For example, +.Cm adc-0:1 +converts channels 0 and 1 (stereo). +.It Cm dig-adc +Digital input converter, usually an S/PDIF receiver. +The audio stream channels these widgets will convert are encoded into +their name in the form of :. +For example, +.Cm dig-adc-0:1 +converts channels 0 and 1 (stereo). +.It Cm mix +Sums multiple audio sources into a single stream, but +sometimes only used for amplifier or mute properties. +The property part of a mix widget mixer control name may be +the name of another widget. +Such a mixer item controls the input level from the widget in the +property part of the name. +.It Cm sel +Selects a single audio source, but sometimes used only for amplifier +or mute properties. +.It Cm pow +Controls power state for a group of widgets. +.It Cm volume +Interprets data from external controls, such as a volume knob. +.It Cm beep +Creates a tone at a certain frequency. +.It Cm line +Pin complex for a line-level jack that is normally used for analog audio +output. +The name may also be appended with a color abbreviation such as -grn (green), +-blk (black), -org (orange), or -gry (grey), to help differentiate jacks. +.It Cm spkr +Pin complex for a speaker, often built into the machine. +.It Cm hp +Pin complex for a jack that is normally used for output to a headphone. +.It Cm cd +Pin complex for analog audio input from a CD device. +.It Cm SPDIF +Pin complex for an S/PDIF output connector. +.It Cm line-in +Pin complex for a line-level jack that is normally used for analog audio input. +.It Cm aux +Pin complex for an auxiliary analog audio input. +.It Cm mic +Pin complex for analog audio input from a microphone, either a jack or built +into the machine. +.It Cm SPDIF-in +Pin complex for an S/PDIF input connector. +.It Cm beep +Pin complex for analog audio input from a beep generator. +.El +.Pp +The following are the property names used in mixer control names: +.Bl -tag -width "source" +.It Cm mute +Mutes input or output audio stream. +.It Cm source +Selects input source. +Can either select a single source or multiple sources. +Sometimes these controls may only have a single choice, but they are +provided to show how audio streams move through the codec. +.It Cm dir +Selects pin direction and input VRef signal. +VRef is represented in percent of the analog voltage rail. +For example, 'input-vr80' means input direction with 80% VRef. +.It Cm boost +Enables/disables low impedance amplifier, usually for use with headphones. +.It Cm eapd +Powers on/off external amplifier circuitry. +.It Cm sense +Reports current jack sense state. +.El +.Pp +There are also some special mixer controls that don't directly +correspond to properties of the widgets, but control aspects +of the driver or other mixer controls. +The following describes these special controls: +.Bl -tag -width "outputsXmasterXslaves" +.It Cm outputs.spkr_muters +List of pins that can mute a built-in speaker. +A pin mutes the speaker by sending a signal when it senses that something +has been plugged into its jack. +If a pin supports both input and output operation, the pin will only mute +the speaker when plugged into if that pin is configured for output. +.It Cm outputs.master.slaves +List of widgets with amplifier gain or mute controls that are configured +with the parameters used for +.Cm outputs.master +and +.Cm outputs.master.mute . +For example, if +.Cm dac +is in the list and has an input amplifier gain control, setting +.Cm outputs.master +to 200 will set +.Cm inputs.dac +to 200. +.It Cm outputs.master +Amplifier gain control for widgets listed in +.Cm outputs.master.slaves . +.It Cm outputs.master.mute +Mute control for widgets listed in +.Cm outputs.master.slaves . +.It Cm record.volume.slaves +List of widgets with amplifier gain or mute controls that are configured +with the parameters used for +.Cm record.volume +and +.Cm record.volume.mute . +For example, if +.Cm adc +is in the list and has an input amplifier gain control, setting +.Cm record.volume +to 200 will set +.Cm record.adc +to 200. +.It Cm record.volume +Amplifier gain control for widgets listed in +.Cm record.volume.slaves . +.It Cm record.volume.mute +Mute control for widgets listed in +.Cm record.volume.slaves . +.It Cm outputs.mode +Controls whether the digital or analog converters and pins will be +used for playback. +.It Cm record.mode +Controls whether the digital or analog converters and pins will be +used for recording. +.El +.Sh SEE ALSO +.Xr audio 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Nx 3.0 . +.Ox +support first appeared in +.Ox 4.0 . +.Sh BUGS +This driver does not support codecs that are intended for HDMI or +DisplayPort connectivity. diff --git a/static/openbsd/man4/bce.4 b/static/openbsd/man4/bce.4 new file mode 100644 index 00000000..fd380fb6 --- /dev/null +++ b/static/openbsd/man4/bce.4 @@ -0,0 +1,91 @@ +.\" $OpenBSD: bce.4,v 1.16 2013/07/16 16:05:48 schwarze Exp $ +.\" $NetBSD: bce.4,v 1.2 2003/10/05 11:58:36 wiz Exp $ +.\" +.\" Copyright (c) 2003 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Thomas Klausner. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt BCE 4 +.Os +.Sh NAME +.Nm bce +.Nd Broadcom BCM4401 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "bce* at pci?" +.Cd "bmtphy* at mii?" +.Sh DESCRIPTION +The +.Nm +provides support for the Broadcom BCM4401 10/100 Ethernet card. +.Pp +The following media types and options (as given to +.Xr ifconfig 8 ) +are supported: +.Bl -tag -width xxx -offset indent +.It Cm media No autoselect +Enable autoselection of the media type and options (default). +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Set 100Mbps (Fast Ethernet) operation and force full-duplex mode. +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Set 100Mbps (Fast Ethernet) operation and force half-duplex mode. +.It Cm media No 10baseT Cm mediaopt No full-duplex +Set 10Mbps operation and force full-duplex. +.It Cm media No 10baseT Cm mediaopt No half-duplex +Set 10Mbps operation and force half-duplex. +.El +.Pp +If no media options are present, the +.Nm +driver places the card into autoselect mode. +.Sh SEE ALSO +.Xr arp 4 , +.Xr bmtphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver appeared in +.Nx 1.6.2 . +.Ox +support was added in +.Ox 3.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Cliff Wright Aq Mt cliff@snipe444.org +and ported to +.Ox +by +.An Nathan L. Binkert Aq Mt binkertn@umich.edu . diff --git a/static/openbsd/man4/bcmaux.4 b/static/openbsd/man4/bcmaux.4 new file mode 100644 index 00000000..6facb27b --- /dev/null +++ b/static/openbsd/man4/bcmaux.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: bcmaux.4,v 1.1 2018/04/01 09:03:25 jsg Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 1 2018 $ +.Dt BCMAUX 4 +.Os +.Sh NAME +.Nm bcmaux +.Nd Broadcom BCM283x auxiliary peripherals +.Sh SYNOPSIS +.Cd "bcmaux* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver handles clock gating and interrupts for the auxiliary peripherals in the +Broadcom BCM2835, BCM2836 and BCM2837 SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmbsc.4 b/static/openbsd/man4/bcmbsc.4 new file mode 100644 index 00000000..cc7f7933 --- /dev/null +++ b/static/openbsd/man4/bcmbsc.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: bcmbsc.4,v 1.1 2020/04/25 23:00:11 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 25 2020 $ +.Dt BCMBSC 4 +.Os +.Sh NAME +.Nm bcmbsc +.Nd Broadcom Serial Control controller +.Sh SYNOPSIS +.Cd "bcmbsc* at fdt?" +.Cd "iic* at bcmbsc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Broadcom Serial Control controller +integrated on Broadcom BCM283x and BCM2711 SoCs. +The Broadcom Serial Controller bus is compatible with the I2C bus and +can be used to connect standard I2C slave devices. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmclock.4 b/static/openbsd/man4/bcmclock.4 new file mode 100644 index 00000000..5301746f --- /dev/null +++ b/static/openbsd/man4/bcmclock.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: bcmclock.4,v 1.1 2020/04/19 16:09:45 tobhe Exp $ +.\" +.\" Copyright (c) 2020 Tobias Heider +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 19 2020 $ +.Dt BCMCLOCK 4 +.Os +.Sh NAME +.Nm bcmclock +.Nd Broadcom BCM283x CPRMAN clock controller +.Sh SYNOPSIS +.Cd "bcmclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the CPRMAN clock controller of the Broadcom +BCM2835, BCM2836 and BCM2837 SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Neil Ashford Aq Mt ashfordneil0@gmail.com +and +.An Tobias Heider Aq Mt tobhe@openbsd.org . diff --git a/static/openbsd/man4/bcmdmac.4 b/static/openbsd/man4/bcmdmac.4 new file mode 100644 index 00000000..70cfa8ed --- /dev/null +++ b/static/openbsd/man4/bcmdmac.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: bcmdmac.4,v 1.2 2020/04/22 11:35:03 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 22 2020 $ +.Dt BCMDMAC 4 +.Os +.Sh NAME +.Nm bcmdmac +.Nd Broadcom BCM238x DMA controller +.Sh SYNOPSIS +.Cd "bcmdmac* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the DMA controller integrated on Broadcom +BCM283x and BCM2711 SoCs. +.Pp +The controller is used to support DMA for devices that don't provide a +DMA controller of their own. +.Sh SEE ALSO +.Xr bcmsdhost 4 , +.Xr intro 4 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared D. McNeill +for +.Nx +and ported to +.Ox +by +.An Neil Ashford Aq Mt ashfordneil0@gmail.com +and +.An Tobias Heider Aq Mt tobhe@openbsd.org . diff --git a/static/openbsd/man4/bcmdog.4 b/static/openbsd/man4/bcmdog.4 new file mode 100644 index 00000000..c0168a6a --- /dev/null +++ b/static/openbsd/man4/bcmdog.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: bcmdog.4,v 1.1 2018/04/01 09:03:25 jsg Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 1 2018 $ +.Dt BCMDOG 4 +.Os +.Sh NAME +.Nm bcmdog +.Nd Broadcom BCM283x watchdog timer +.Sh SYNOPSIS +.Cd "bcmdog* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the integrated watchdog timer in the Broadcom +BCM2835, BCM2836 and BCM2837 SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr watchdog 4 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/bcmgpio.4 b/static/openbsd/man4/bcmgpio.4 new file mode 100644 index 00000000..2e46ff4b --- /dev/null +++ b/static/openbsd/man4/bcmgpio.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: bcmgpio.4,v 1.2 2020/05/16 17:58:55 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 16 2020 $ +.Dt BCMGPIO 4 +.Os +.Sh NAME +.Nm bcmgpio +.Nd Broadcom BCM283x GPIO controller +.Sh SYNOPSIS +.Cd "bcmgpio* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver uses pin control data from the device tree to select one of +multiple possible roles available for pins on Broadcom BCM283x and +BCM2711 SoCs. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmirng.4 b/static/openbsd/man4/bcmirng.4 new file mode 100644 index 00000000..3186bd57 --- /dev/null +++ b/static/openbsd/man4/bcmirng.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: bcmirng.4,v 1.2 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt BCMIRNG 4 +.Os +.Sh NAME +.Nm bcmirng +.Nd Broadcom RNG200 random number generator +.Sh SYNOPSIS +.Cd "bcmirng* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the RNG200 random number generator found +on the Broadcom BCM2711 SoC. +.Pp +It feeds the random subsystem's entropy pool with up to 128 bits of +random data every second. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmmbox.4 b/static/openbsd/man4/bcmmbox.4 new file mode 100644 index 00000000..e7f7649d --- /dev/null +++ b/static/openbsd/man4/bcmmbox.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: bcmmbox.4,v 1.1 2020/04/19 16:09:45 tobhe Exp $ +.\" +.\" Copyright (c) 2020 Tobias Heider +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 19 2020 $ +.Dt BCMMBOX 4 +.Os +.Sh NAME +.Nm bcmmbox +.Nd Broadcom BCM283x VideoCore Mailboxes +.Sh SYNOPSIS +.Cd "bcmmbox* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver handles communication with the VideoCore on Broadcom BCM2835, BCM2836 +and BCM2837 SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Neil Ashford Aq Mt ashfordneil0@gmail.com +and +.An Tobias Heider Aq Mt tobhe@openbsd.org . diff --git a/static/openbsd/man4/bcmpcie.4 b/static/openbsd/man4/bcmpcie.4 new file mode 100644 index 00000000..7728f139 --- /dev/null +++ b/static/openbsd/man4/bcmpcie.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: bcmpcie.4,v 1.2 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECI`AL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt BCMPCIE 4 +.Os +.Sh NAME +.Nm bcmpcie +.Nd Broadcom BCM2711 Host/PCIe bridge +.Sh SYNOPSIS +.Cd "bcmpcie* at fdt?" +.Cd "pci* at bcmpcie?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PCIe controller found on the +Broadcom BCM2711 SoC that is used in the Raspberry Pi 4. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmrng.4 b/static/openbsd/man4/bcmrng.4 new file mode 100644 index 00000000..7688624a --- /dev/null +++ b/static/openbsd/man4/bcmrng.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: bcmrng.4,v 1.2 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt BCMRNG 4 +.Os +.Sh NAME +.Nm bcmrng +.Nd Broadcom BCM2835/BCM2836/BCM2837 random number generator +.Sh SYNOPSIS +.Cd "bcmrng* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the random number generator found on the +Broadcom BCM2835/BCM2836/BCM2837 SoC. +.Pp +It feeds the random subsystem's entropy pool with up to 128 bits of +random data every second. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmsdhost.4 b/static/openbsd/man4/bcmsdhost.4 new file mode 100644 index 00000000..55917746 --- /dev/null +++ b/static/openbsd/man4/bcmsdhost.4 @@ -0,0 +1,63 @@ +.\" $OpenBSD: bcmsdhost.4,v 1.2 2020/04/22 11:35:03 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 22 2020 $ +.Dt BCMSDHOST 4 +.Os +.Sh NAME +.Nm bcmsdhost +.Nd Broadcom BCM238x SD controller +.Sh SYNOPSIS +.Cd "bcmsdhost* at fdt?" +.Cd "sdmmc* at bcmsdhost?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SD controllers integrated on Broadcom +BCM283x and BCM2711 SoCs. +The driver uses the +.Xr bcmdmac 4 +DMA controller to provide DMA support. +.Pp +The +.Xr sdmmc 4 +subsystem performs SD/MMC transactions to communicate with whatever SD +devices are inserted into the card slot or directly connected to the +controller. +.Sh SEE ALSO +.Xr bcmdmac 4 , +.Xr intro 4 , +.Xr sdmmc 4 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared D. McNeill +for +.Nx +and ported to +.Ox +by +.An Neil Ashford Aq Mt ashfordneil0@gmail.com +and +.An Tobias Heider Aq Mt tobhe@openbsd.org . diff --git a/static/openbsd/man4/bcmstbgpio.4 b/static/openbsd/man4/bcmstbgpio.4 new file mode 100644 index 00000000..9a81d354 --- /dev/null +++ b/static/openbsd/man4/bcmstbgpio.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: bcmstbgpio.4,v 1.1 2025/08/09 21:12:23 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 9 2025 $ +.Dt BCMSTBGPIO 4 +.Os +.Sh NAME +.Nm bcmstbgpio +.Nd Broadcom Set-top Box GPIO controller +.Sh SYNOPSIS +.Cd "bcmstbgpio* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO ports found on Broadcom Set-top +Box SoCs. +This includes the Broadcom BCM2712 SoC that is used in the Raspberry +Pi 5. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmstbintc.4 b/static/openbsd/man4/bcmstbintc.4 new file mode 100644 index 00000000..b4d40624 --- /dev/null +++ b/static/openbsd/man4/bcmstbintc.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: bcmstbintc.4,v 1.1 2025/09/08 19:44:45 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2025 $ +.Dt BCMSTBINTC 4 +.Os +.Sh NAME +.Nm bcmstbintc +.Nd Broadcom Set-to Box interrupt controller +.Sh SYNOPSIS +.Cd "bcmstbintc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the L2 interrupt controller +integrated on Broadcom Set-top Box SoCs. +This includes the Broadcom BCM2712 SoC that is used in the Raspberry +Pi 5. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmstbpinctrl.4 b/static/openbsd/man4/bcmstbpinctrl.4 new file mode 100644 index 00000000..bcdcf780 --- /dev/null +++ b/static/openbsd/man4/bcmstbpinctrl.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: bcmstbpinctrl.4,v 1.1 2025/08/19 11:58:31 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 19 2025 $ +.Dt BCMSTBPINCTRL 4 +.Os +.Sh NAME +.Nm bcmstbpinctrl +.Nd Broadcom Set-top Box pin multiplexing +.Sh SYNOPSIS +.Cd "bcmstbpinctrl* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver uses pin control data from the device tree to select one of +multiple possible roles available for pins on Broadcom Set-top Box +SoCs. +This includes the Broadcom BCM2712 SoC that is used in the Raspberry +Pi 5. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmstbrescal.4 b/static/openbsd/man4/bcmstbrescal.4 new file mode 100644 index 00000000..ee283c75 --- /dev/null +++ b/static/openbsd/man4/bcmstbrescal.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: bcmstbrescal.4,v 1.1 2025/08/20 13:13:03 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 20 2025 $ +.Dt BCMSTBRESCAL 4 +.Os +.Sh NAME +.Nm bcmstbrescal +.Nd Broadcom Set-top Box reset calibration controller +.Sh SYNOPSIS +.Cd "bcmstbrescal* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the reset calibration controller for the integrated +PCIe/SATA components of Broadcom Set-top Box SoCs. +This includes the Broadcom BCM2712 SoC that is used in the Raspberry +Pi 5. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr bcmpcie 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmstbreset.4 b/static/openbsd/man4/bcmstbreset.4 new file mode 100644 index 00000000..beb3b846 --- /dev/null +++ b/static/openbsd/man4/bcmstbreset.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: bcmstbreset.4,v 1.1 2025/08/20 12:14:21 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 20 2025 $ +.Dt BCMSTBRESET 4 +.Os +.Sh NAME +.Nm bcmstbreset +.Nd Broadcom Set-top Box reset controller +.Sh SYNOPSIS +.Cd "bcmstbreset* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the reset signals for integrated components of +Broadcom Set-top Box SoCs. +This includes the Broadcom BCM2712 SoC that is used in the Raspberry +Pi 5. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmtemp.4 b/static/openbsd/man4/bcmtemp.4 new file mode 100644 index 00000000..2724d70d --- /dev/null +++ b/static/openbsd/man4/bcmtemp.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: bcmtemp.4,v 1.3 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt BCMTEMP 4 +.Os +.Sh NAME +.Nm bcmtemp +.Nd Broadcom BCM2835/BCM2836/BCM2837 temperature monitor +.Sh SYNOPSIS +.Cd "bcmtemp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor found on the +Broadcom BCM2835/BCM2836/BCM2837 SoC. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bcmtmon.4 b/static/openbsd/man4/bcmtmon.4 new file mode 100644 index 00000000..c52e65b2 --- /dev/null +++ b/static/openbsd/man4/bcmtmon.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: bcmtmon.4,v 1.3 2025/09/15 16:16:20 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 15 2025 $ +.Dt BCMTMON 4 +.Os +.Sh NAME +.Nm bcmtmon +.Nd Broadcom BCM2711/BCM2712 temperature monitor +.Sh SYNOPSIS +.Cd "bcmtmon* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor found on the +Broadcom BCM2711/BCM2712 SoC that is used in the Raspberry Pi 4/5. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alastair Poole Aq Mt netstar@gmail.com . diff --git a/static/openbsd/man4/bdpmic.4 b/static/openbsd/man4/bdpmic.4 new file mode 100644 index 00000000..1c399c38 --- /dev/null +++ b/static/openbsd/man4/bdpmic.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: bdpmic.4,v 1.1 2020/03/20 09:25:42 patrick Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 20 2020 $ +.Dt BDPMIC 4 +.Os +.Sh NAME +.Nm bdpmic +.Nd ROHM BD718x7 Power Management IC +.Sh SYNOPSIS +.Cd "bdpmic* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the voltage regulators in the ROHM BD71837 +and BD71847 Power Management ICs. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/berkwdt.4 b/static/openbsd/man4/berkwdt.4 new file mode 100644 index 00000000..a737b2c6 --- /dev/null +++ b/static/openbsd/man4/berkwdt.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: berkwdt.4,v 1.4 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Michael Knudsen +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: July 16 2013 $ +.Dt BERKWDT 4 +.Os +.Sh NAME +.Nm berkwdt +.Nd Berkshire Products watchdog timer device +.Sh SYNOPSIS +.Cd "berkwdt0 at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Berkshire Products PCI PC Watchdog. +These devices contain a watchdog timer and general purpose digital inputs +and outputs, but currently only the watchdog timer is supported. +.Pp +.Nm +provides the standard +.Xr watchdog 4 +interface and may be used with +.Xr watchdogd 8 . +The watchdog timer may be configured to a value from 1 second to 18 +hours. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr watchdog 4 , +.Xr sysctl 8 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Wim Van Sebroeck Aq Mt wim@iguana.be . diff --git a/static/openbsd/man4/bge.4 b/static/openbsd/man4/bge.4 new file mode 100644 index 00000000..34e96016 --- /dev/null +++ b/static/openbsd/man4/bge.4 @@ -0,0 +1,202 @@ +.\" $OpenBSD: bge.4,v 1.67 2022/09/10 10:06:08 jsg Exp $ +.\" Copyright (c) 2001 Wind River Systems +.\" Copyright (c) 1997, 1998, 1999, 2000, 2001 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 10 2022 $ +.Dt BGE 4 +.Os +.Sh NAME +.Nm bge +.Nd Broadcom BCM57xx/BCM590x 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "bge* at pci?" +.Cd "brgphy* at mii?" +.Cd "rgephy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various NICs based on the Broadcom BCM570x, +571x, 572x, 575x, 576x, 578x, 5776x and 5778x Gigabit Ethernet controller +chips and the 590x and 5779x Fast Ethernet controller chips, +including the following: +.Pp +.Bl -bullet -compact +.It +3Com 3c996-T (10/100/1000baseT) +.It +3Com 3c996-SX (1000baseSX) +.It +3Com 3c996B-T (10/100/1000baseT) +.It +Allied-Telesis AT-2972LX10/LC +.It +Fujitsu PW0G8GE1U (1000baseSX) +.It +Fujitsu PW0G8GE2U (10/100/1000baseT) +.It +Fujitsu PW008GE4 (1000baseSX) +.It +Fujitsu PW008GE5 (10/100/1000baseT) +.It +Fujitsu PW008QG1U (10/100/1000baseT) +.It +HP ProLiant NC320T PCI-E Gigabit NIC (10/100/1000baseT) +.It +HP ProLiant NC320m PCI-E Gigabit NIC (10/100/1000baseT) +.It +HP ProLiant NC370F PCI-X Gigabit NIC (1000baseSX) +.It +HP ProLiant NC370T PCI-X Gigabit NIC (10/100/1000baseT) +.It +HP ProLiant NC1020 PCI Gigabit NIC (10/100/1000baseT) +.It +HP ProLiant NC6770 PCI-X Gigabit NIC (1000baseSX) +.It +HP ProLiant NC7760 embedded PCI Gigabit NIC (10/100/1000baseT) +.It +HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseT) +.It +HP ProLiant NC7771 PCI-X Gigabit NIC (10/100/1000baseT) +.It +HP ProLiant NC7780 embedded PCI-X Gigabit NIC (10/100/1000baseT) +.It +HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseT) +.It +HP ProLiant NC7782 embedded PCI-X Gigabit NIC (10/100/1000baseT) +.It +Netgear GA302T (10/100/1000baseT) +.It +SysKonnect SK-9D21 (10/100/1000baseT) +.It +SysKonnect SK-9D41 (1000baseSX) +.El +.Pp +The +.Nm +driver supports IPv4 receive IP/TCP/UDP checksum offload and transmit IP/TCP +checksum offload, VLAN tag insertion and stripping, +as well as a 256-bit multicast hash filter. +The BCM5717, BCM5718, BCM5723, BCM5754, BCM5755, BCM5761, BCM5764, BCM5784, +BCM5785, BCM5787 and BCM577xx chips also support IPv6 receive TCP/UDP +checksum offload. +.Pp +The BCM5700, BCM5701, BCM5703, BCM5704, BCM5714, BCM5717, BCM5719, BCM5720, +BCM5762, BCM5780, BCM57765 and BCM57766 +chips are capable of supporting jumbo frames. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width 1000baseSX +.It Cm autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It Cm 10baseT +Set 10Mbps operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 1000baseT +Set 1000baseT operation over twisted pair. +Both +.Cm full-duplex +and +.Cm half-duplex +modes are supported. +.It Cm 1000baseSX +Set 1000Mbps (Gigabit Ethernet) operation. +Both +.Cm full-duplex +and +.Cm half-duplex +modes are supported. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It Cm full-duplex +Force full duplex operation. +.It Cm half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "bge0: can't find mem space" +A fatal initialization error has occurred. +.It "bge0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "bge0: watchdog timeout -- resetting" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr brgphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr rgephy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@windriver.com . diff --git a/static/openbsd/man4/bgw.4 b/static/openbsd/man4/bgw.4 new file mode 100644 index 00000000..2cb6f9e0 --- /dev/null +++ b/static/openbsd/man4/bgw.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: bgw.4,v 1.1 2017/11/30 15:06:35 kettenis Exp $ +.\" +.\" Copyright (c) 2017 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 30 2017 $ +.Dt BGW 4 +.Os +.Sh NAME +.Nm bgw +.Nd Bosch motion sensor +.Sh SYNOPSIS +.Cd "bgw* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Bosch BMC150, BMI055, BMA222E, +BMA250E, BMA255 and BMA280 motion sensors. +The acceleration data as well as the chip temperature are made +available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bio.4 b/static/openbsd/man4/bio.4 new file mode 100644 index 00000000..46564cdb --- /dev/null +++ b/static/openbsd/man4/bio.4 @@ -0,0 +1,180 @@ +.\" $OpenBSD: bio.4,v 1.35 2024/07/13 15:28:42 krw Exp $ +.\" +.\" Copyright (c) 2002 Niklas Hallqvist +.\" Copyright (c) 2006 Marco Peereboom +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 13 2024 $ +.Dt BIO 4 +.Os +.Sh NAME +.Nm bio +.Nd block I/O ioctl tunnel pseudo-device +.Sh SYNOPSIS +.Cd "pseudo-device bio" Op Ar count +.Sh DESCRIPTION +The +.Nm +driver provides userland applications +.Xr ioctl 2 +access to devices otherwise not found as +.Pa /dev +nodes. +The +.Pa /dev/bio +device node operates by delegating ioctl +calls to a requested device driver. +Only drivers which have registered with the +.Nm +device can be accessed via this interface. +.Pp +If +.Ar count +is given in the specification, and is greater than 0, a maximum of one +.Nm bio +device is created. +.Pp +The following device drivers register with +.Nm +for volume management: +.Pp +.Bl -tag -width softraid(4)XX -offset indent -compact +.It Xr ami 4 +American Megatrends Inc. MegaRAID PATA/SATA/SCSI RAID controller +.It Xr arc 4 +Areca Technology Corporation SAS/SATA RAID controller +.It Xr cac 4 +Compaq Smart Array 2/3/4 SCSI RAID controller +.It Xr ciss 4 +Compaq Smart Array SAS/SATA/SCSI RAID controller +.It Xr gdt 4 +ICP-Vortex and Intel GDT SATA/SCSI RAID controller +.It Xr ips 4 +IBM SATA/SCSI ServeRAID controller +.It Xr mfi 4 +LSI Logic & Dell MegaRAID SAS RAID controller +.It Xr mfii 4 +LSI Logic MegaRAID SAS Fusion RAID controller +.It Xr mpi 4 +LSI Logic Fusion-MPT Message Passing Interface +.It Xr mpii 4 +LSI Logic Fusion-MPT Message Passing Interface II +.It Xr nvme 4 +NVMe storage controllers +.It Xr softraid 4 +Software RAID +.El +.Pp +The following device drivers register with +.Nm +to provide enclosure management: +.Pp +.Bl -tag -width safte($)XX -offset indent -compact +.It Xr safte 4 +SCSI Accessed Fault-Tolerant Enclosure +.It Xr ses 4 +SCSI Enclosure Services +.El +.Pp +The following ioctl calls apply to the +.Nm +device: +.Bl -tag -width Ds +.It Dv BIOCLOCATE Fa "struct bio_locate *" +Locate a named device and give back a cookie to the application +for subsequent ioctl calls. +The cookie is used to tunnel further ioctls to the right device. +.It Dv BIOCINQ Fa "struct bioc_inq *" +Retrieve number of volumes and physical disks for a specific device. +.It Dv BIOCDISK Fa "struct bioc_disk *" +Retrieve detailed information for the specified physical disk. +Information returned can include status, size, channel, target, lun, +vendor name, serial number and processor device (ses or safte). +.It Dv BIOCVOL Fa "struct bioc_vol *" +Retrieve detailed information for the specified volume. +Information returned can include status, size, RAID level, number of disks, +device name association (sd?) and vendor name. +.It Dv BIOCALARM Fa "struct bioc_alarm *" +Control the alarm beeper on the device. +Supported states are: disable alarm, enable alarm, silence alarm, status and +test alarm. +.Pp +Note: These options might not be supported on all hardware. +.It Dv BIOCBLINK Fa "struct bioc_blink *" +Blink an LED of the specified physical disk. +Supported blink states are: blink LED, unblink LED and blink alarm LED. +.Pp +Note: This option is only supported if the disk is governed by +.Xr ses 4 +or +.Xr safte 4 +and the hardware supports hardware blinking. +.It Dv BIOCSETSTATE Fa "struct bioc_setstate *" +Alter the state of specified physical disk. +Supported states are: create hot-spare, online disk and offline disk. +.El +.Pp +The following ioctl calls apply to the +.Nm +device only when talking to a +.Xr softraid 4 +device: +.Bl -tag -width Ds +.It Dv BIOCCREATERAID Fa "struct bioc_createraid *" +Create a new volume or assemble an existing volume. +The volume will be attached as a system disk, if this capability is supported +by the volume discipline. +.It Dv BIOCDELETERAID Fa "struct bioc_deleteraid *" +Remove system disk (if present) and disassemble the +.Xr softraid 4 +volume. +.It Dv BIOCDISCIPLINE Fa "struct bioc_discipline *" +Dispatch a discipline specific ioctl. +.It Dv BIOCINSTALLBOOT Fa "struct bioc_installboot *" +Install a boot loader. +.El +.Sh FILES +.Bl -tag -width /dev/bio -compact +.It Pa /dev/bio +ioctl tunnel device +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr softraid 4 , +.Xr bioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Niklas Hallqvist Aq Mt niklas@openbsd.org . +The API was written by +.An Marco Peereboom Aq Mt marco@openbsd.org . diff --git a/static/openbsd/man4/bktr.4 b/static/openbsd/man4/bktr.4 new file mode 100644 index 00000000..3ab98bf0 --- /dev/null +++ b/static/openbsd/man4/bktr.4 @@ -0,0 +1,477 @@ +.\" +.\" Copyright (c) 1998 Amancio Hasty and Roger Hardiman +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Amancio Hasty and +.\" Roger Hardiman. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $OpenBSD: bktr.4,v 1.30 2024/09/01 05:33:29 jsg Exp $ +.\" $FreeBSD: /c/ncvs/src/share/man/man4/bktr.4,v 1.9.2.5 2001/03/06 19:08:09 ru Exp $ +.\" +.Dd $Mdocdate: September 1 2024 $ +.Dt BKTR 4 +.Os +.Sh NAME +.Nm bktr +.Nd Brooktree Bt848/849/878/879 PCI TV tuners and video capture boards +.Sh SYNOPSIS +.Cd "bktr* at pci?" +.Cd "radio* at bktr?" +.Pp +.In dev/ic/bt8xx.h +.Pp +.Cd "option BKTR_ALLOC_PAGES=nnn" +.Cd "option BKTR_SYSTEM_DEFAULT=XXX" +.Cd "option BKTR_OVERRIDE_CARD=nnn" +.Cd "option BKTR_OVERRIDE_MSP=n" +.Cd "option BKTR_OVERRIDE_TUNER=nnn" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI video capture and VBI capture on low cost, +high performance boards. +This should support most video cards based on the +Brooktree Bt848/849/878/879 Video Capture Chip. +The driver also supports FM Radio if the Tuner supports it. +.Pp +Specifically, the following cards are known to work: +.Bd -unfilled -offset indent +Animation Technologies FlyVideo +AOpen VA1000 +Askey/Dynalink Magic TView +ATI TV-Wonder and Wonder/VE +AverMedia cards +Hauppauge Wincast TV and WinTV/PCI +IMS TV Turbo +Intel Smart Video Recorder III +I/O DATA GV-BCTV2/PCI +I/O DATA GV-BCTV3/PCI +KISS TV/FM PCI +Leadtek Winfast TV 2000 +Leadtek Winfast TV 2000 XP +Miro PC TV +MMAC Osprey +NEC PK-UG-X017 +STB TV PCI Television Tuner +Terratec TerraTVplus +Video Highway XTreme +VideoLogic Captivator PCI +Zoltrix TV and Genie TV/FM +.Ed +.Pp +The driver currently supports the following features: +.Bd -unfilled -offset indent +PCI to PCI DMA transfer +clipping +yuv +rgb16 +rgb24 +rgb32 +.Ed +.Pp +On these cards, tuners and other components are interconnected with an I2C bus. +The Brooktree848 chips act as a master device on the bus to control them. +.Sh VIDEO CAPTURE INTERFACE +The video capture interface to +.Nm +is accessed through +.Pa /dev/bktrN +devices. +The following +.Xr ioctl 2 +commands are supported on the Brooktree848 video capture interface: +.Bl -tag -width Ds +.It Dv METEORSFMT Fa "unsigned long *" +This command sets the video format, also sometimes referred to as the +video norm. +The supported formats are: +.Pp +.Bl -tag -compact -width 28n +.It Dv METEOR_FMT_NTSC +NTSC +.It Dv METEOR_FMT_PAL +PAL +.It Dv METEOR_FMT_SECAM +SECAM +.It Dv METEOR_FMT_AUTOMODE +hardware default +.El +.It Dv METEORGFMT Fa "unsigned long *" +This command retrieves the current video format to the +.Vt unsigned long * +argument. +.It Dv METEORSETGEO Fa "struct meteor_geomet *" +This command sets the video properties that affect the bit size of +a frame through the +.Vt meteor_geomet * +argument. +.Bd -literal +struct meteor_geomet { + u_short rows; /* height in pixels*/ + u_short columns; /* width in pixels */ + u_short frames; + u_long oformat; +} +.Ed +.Pp +The +.Va frames +field is the number of frames to buffer. +Currently only 1 frame is supported for most operations. +.Pp +The +.Va oformat +field is a bit-field describing the output pixel format +type and which video fields to capture. +The following are supported pixel format types: +.Pp +.Bl -tag -compact -width 28n +.It Dv METEOR_GEO_RGB16 +16-bit RGB +.It Dv METEOR_GEO_RGB24 +24-bit RGB in 32 bits +.It Dv METEOR_GEO_YUV_PACKED +16-bit 4:2:2 YUV +.It Dv METEOR_GEO_YUV_PLANAR +16-bit 4:2:2 YUV +.It Dv METEOR_GEO_YUV_UNSIGNED +unsigned UV +.It Dv METEOR_GEO_YUV_422 +.It Dv METEOR_GEO_YUV_12 +.It Dv METEOR_GEO_YUV_9 +.El +.Pp +The following are supported field capture modes: +.Pp +.Bl -tag -compact -width 28n +.It Dv METEOR_GEO_ODD_ONLY +only odd fields +.It Dv METEOR_GEO_EVEN_ONLY +only even fields +.El +.Pp +By default, frames will consist of both the odd and even fields. +.It Dv METEORGSUPPIXFMT Fa "struct meteor_pixfmt *" +This command is used iteratively to fetch descriptions of supported +output pixel formats into the +.Vt meteor_pixfmt * +argument. +.Bd -literal +struct meteor_pixfmt { + u_int index; + METEOR_PIXTYPE type; + u_int Bpp; /* bytes per pixel */ + u_long masks[3]; /* YUV bit masks */ + unsigned swap_bytes :1; + unsigned swap_shorts:1; +}; +.Ed +.Pp +To query all the supported formats, start with an index field of 0 and +continue with successive encodings (1, 2, ...) until the command returns +an error. +.It Dv METEORSACTPIXFMT Fa "int *" +This command sets the active pixel format. +The +.Vt int * +argument is the index of the pixel format as returned by +.Dv METEORGSUPPIXFMT . +.It Dv METEORGACTPIXFMT Fa "int *" +This command fetches the active pixel format index into the +.Vt int * +argument. +.It Dv METEORSINPUT Fa "unsigned long *" +This command sets the input port of the Brooktree848 device. +The following are supported input ports: +.Pp +.Bl -tag -compact -width 28n +.It Dv METEOR_INPUT_DEV0 +composite (RCA) +.It Dv METEOR_INPUT_DEV1 +tuner +.It Dv METEOR_INPUT_DEV2 +composite S-video +.It Dv METEOR_INPUT_DEV3 +mystery device +.It Dv METEOR_INPUT_DEV_RGB +rgb meteor +.It Dv METEOR_INPUT_DEV_SVIDEO +S-Video +.El +.Pp +Not all devices built with Brooktree848 chips support the +full list of input ports. +.It Dv METEORGINPUT Fa "unsigned long *" +This command retrieves the current input port to the +.Vt unsigned long * +argument. +.It Dv METEORSFPS Fa "unsigned short *" +This command sets the number of frames to grab each second. +Valid frame rates are integers from 0 to 30. +.It Dv METEORGFPS Fa "unsigned short *" +This command fetches the number of frames to grab each second into the +.Vt unsigned short * +argument. +.It Dv METEORCAPTUR Fa "int *" +This command controls capturing of video data. +The following are valid arguments: +.Pp +.Bl -tag -compact -width 28n +.It Dv METEOR_CAP_SINGLE +capture one frame +.It Dv METEOR_CAP_CONTINOUS +continuously capture +.It Dv METEOR_CAP_STOP_CONT +stop continuous capture +.El +.It Dv METEORSSIGNAL Fa "unsigned int *" +This command controls the signal emission properties of +.Nm . +If the +.Vt unsigned int * +argument is a valid signal, then that signal will be emitted +when either a frame or field capture has completed. +To select between frame or field signalling, the following arguments +are used: +.Pp +.Bl -tag -compact -width 28n +.It Dv METEOR_SIG_FRAME +signal every frame +.It Dv METEOR_SIG_FIELD +signal every field +.El +.Pp +By default, signals will be generated for every frame. +Generation of signals is terminated with the +.Dv METEOR_SIG_MODE_MASK +argument. +.El +.Sh TUNER INTERFACE +Most cards supported by this driver feature a hardware television tuner +on the I2C bus. +The tuner interface to +.Nm +is accessed through +.Pa /dev/tunerN +devices. +The following +.Xr ioctl 2 +commands are supported on the tuner interface: +.Bl -tag -width Ds +.It Dv TVTUNER_SETTYPE Fa "unsigned int *" +This command sets the tuner's TV channel set, also sometimes called the TV +channel band. +This setting is used to calculate the proper tuning frequencies. +The desired channel set must be selected before attempting to set the tuner +channel or frequency. +The following is a list of valid channel sets: +.Pp +.Bl -tag -compact -width 28n +.It Dv CHNLSET_NABCST +North America broadcast +.It Dv CHNLSET_CABLEIRC +North America IRC cable +.It Dv CHNLSET_CABLEHRC +North America HRC cable +.It Dv CHNLSET_WEUROPE +Western Europe +.It Dv CHNLSET_JPNBCST +Japan broadcast +.It Dv CHNLSET_JPNCABLE +Japan cable +.It Dv CHNLSET_XUSSR +Russia +.It Dv CHNLSET_AUSTRALIA +Australia +.It Dv CHNLSET_FRANCE +France +.El +.It Dv TVTUNER_GETTYPE Fa "unsigned int *" +This command fetches the tuner's current channel set to the +.Vt unsigned int * +argument. +.It Dv TVTUNER_SETCHNL Fa "unsigned int *" +This command sets the tuner's frequency to a specified channel in the +current channel set. +.It Dv TVTUNER_GETCHNL Fa "unsigned int *" +This command fetches the last selected channel. +Note that it is not necessarily the current channel. +In particular, changing the tuner's frequency by a command other than +.Dv TVTUNER_SETCHNL +will not update this setting, and it defaults to 0 on driver +initialization. +.It Dv TVTUNER_SETFREQ Fa "unsigned int *" +This command sets the tuner's frequency to 1/16th the value of the +.Vt unsigned int * +argument, in MHz. +Note that the current channelset is used to determine frequency +offsets when this command is executed. +.It Dv TVTUNER_GETFREQ Fa "unsigned int *" +This command fetches the tuner's current frequency to the +.Vt unsigned int * +argument. +Note that this value is 16 times the actual tuner frequency, in MHz. +.It Dv BT848_SAUDIO Fa "int *" +This command controls the audio input port and mute state. +The following is a list of valid arguments: +.Pp +.Bl -tag -compact -width 18n +.It Dv AUDIO_TUNER +tuner audio port +.It Dv AUDIO_EXTERN +external audio port +.It Dv AUDIO_INTERN +internal audio port +.It Dv AUDIO_MUTE +mute audio +.It Dv AUDIO_UNMUTE +unmute audio +.El +.It Dv BT848_GAUDIO Fa "int *" +This command fetches the audio input and mute state bits to the +.Vt int * +argument. +.El +.Sh KERNEL OPTIONS +The following kernel configuration options are available: +.Bl -tag -width xxxxxxxx +.It Cd option BKTR_ALLOC_PAGES=nnn +Specifies the number of contiguous pages to allocate when successfully +probed. +The default number of pages allocated by the kernel is 216. +This means that there are (216*4096) bytes available for use. +.It Cd option BKTR_SYSTEM_DEFAULT="(BROOKTREE_PAL | BROOKTREE_NTSC)" +One of these options can be used to set the default video format for the driver. +This fixed random hangs and lockups with the VideoLogic Captivator PCI card. +.It Cd option BKTR_OVERRIDE_CARD=nnn +Select a specific card (overrides autodetection). +`nnn' is set to one of the names listed and explained below. +.Pp +.Bl -tag -width "CARD_ASKEY_DYNALINK_MAGIC_TVIEW" -compact +.It CARD_ASKEY_DYNALINK_MAGIC_TVIEW +Askey/Dynalink Magic TView +.It CARD_AVER_MEDIA +AverMedia +.It CARD_FLYVIDEO +Animation Technologies FlyVideo +.It CARD_AOPEN_VA1000 +AOpen VA1000 +.It CARD_TVWONDER +ATI TV-Wonder/VE +.It CARD_HAUPPAUGE +Hauppauge Wincast TV and WinTV +.It CARD_IMS_TURBO +IMS TV Turbo +.It CARD_INTEL +Intel Smart Video Recorder III +.It CARD_IO_GV +I/O DATA GV-BCTV2/PCI +.It CARD_IO_BCTV3 +I/O DATA GV-BCTV3/PCI +.It CARD_KISS +KISS TV/FM PCI +.It CARD_LEADTEK +Leadtek Winfast TV 2000 +.It CARD_LEADTEK_XP +Leadtek Winfast TV 2000 XP +.It CARD_MIRO +Miro PC TV +.It CARD_OSPREY +MMAC Osprey +.It CARD_NEC_PK +NEC PK-UG-X017 +.It CARD_STB +STB TV PCI Television Tuner +.It CARD_TERRATVPLUS +Terratec TerraTVplus +.It CARD_VIDEO_HIGHWAY_XTREME +Video Highway XTreme +.It CARD_ZOLTRIX +Zoltrix TV +.It CARD_ZOLTRIX_GENIE_FM +Zoltrix Genie TV/FM +.El +.It Cd option BKTR_OVERRIDE_MSP=n +Specifies whether the MSP3400C chip is present (overrides autodetection). +.It Cd option BKTR_OVERRIDE_TUNER=nnn +Select a specific tuner (overrides autodetection). +`nnn' is set to one of the names listed and explained below. +.Pp +.Bl -tag -compact -width 28n +.It TEMIC_NTSC +Temic 4032FY5 +.It TEMIC_PAL +Temic 4002FH5 +.It TEMIC_SECAM +Temic 4002FN5 +.It PHILIPS_NTSC +Philips FI1236 +.It PHILIPS_PAL +Philips FM1216 +.It PHILIPS_SECAM +Philips FI1216MF +.It TEMIC_PALI +Temic 4062FY5 +.It PHILIPS_PALI +Philips FI1246 +.It PHILIPS_FR1236_NTSC +Philips FR1236 MK2 +.It PHILIPS_FR1216_PAL +Philips FM1216 +.It PHILIPS_FR1236_SECAM +Philips FM1216MF +.It ALPS_TSCH5 +Alps TSCH5 NTSC +.It ALPS_TSBH1 +Alps TSBH1 NTSC +.It TIVISION_TVF5533 +Tivision TVF5533-MF NTSC +.El +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr radio 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Fx 2.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver is based on the work of +.An Jim Lowe Aq Mt james@miller.cs.uwm.edu , +.An Mark Tinguely Aq Mt tinguely@plains.nodak.edu , +.An Amancio Hasty Aq Mt hasty@star\-gate.com , +.An Roger Hardiman Aq Mt roger@FreeBSD.org +and a bunch of other people. +.Sh CAVEATS +On big-endian architectures it is not possible to program the +card to perform proper byte swapping in 24 bit modes, +therefore only 16 and 32 bit modes are supported. diff --git a/static/openbsd/man4/bmtphy.4 b/static/openbsd/man4/bmtphy.4 new file mode 100644 index 00000000..2eae8d0a --- /dev/null +++ b/static/openbsd/man4/bmtphy.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: bmtphy.4,v 1.10 2020/01/24 05:08:02 jsg Exp $ +.\" +.\" Copyright (c) 2000 Theo de Raadt +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 24 2020 $ +.Dt BMTPHY 4 +.Os +.Sh NAME +.Nm bmtphy +.Nd Broadcom Mini-Theta Ethernet PHY +.Sh SYNOPSIS +.Cd "bmtphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Broadcom Mini-Theta BCM5201 and BCM5202 10/100 +Ethernet PHYs and their derivatives such as BCM4401, BCM5214, and BCM522x. +It also supports the internal PHY on the 3Com 3C905C-TX 10/100 Ethernet +interface, and the internal PHY on some 3Com 3C905B-TX 10/100 Ethernet +interfaces. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/bnx.4 b/static/openbsd/man4/bnx.4 new file mode 100644 index 00000000..26130eae --- /dev/null +++ b/static/openbsd/man4/bnx.4 @@ -0,0 +1,181 @@ +.\" $OpenBSD: bnx.4,v 1.32 2021/09/08 20:29:21 jmc Exp $ +.\" +.\"Copyright (c) 2006 Broadcom Corporation +.\" David Christensen . All rights reserved. +.\" +.\"Redistribution and use in source and binary forms, with or without +.\"modification, are permitted provided that the following conditions +.\"are met: +.\" +.\"1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\"2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\"3. Neither the name of Broadcom Corporation nor the name of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written consent. +.\" +.\"THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS' +.\"AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\"IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\"ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS +.\"BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\"CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\"SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\"INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\"CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\"ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\"THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/bce.4,v 1.2 2006/04/10 20:12:17 brueffer Exp $ +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt BNX 4 +.Os +.Sh NAME +.Nm bnx +.Nd Broadcom NetXtreme II 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "bnx* at pci?" +.Cd "brgphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports Broadcom's NetXtreme II product family which is made up of +the BCM5706, BCM5708, BCM5709, and BCM5716 Ethernet controller chips. +Products using these controller chips include: +.Pp +.Bl -bullet -compact +.It +HP NC370F PCI-X Multifunction Gigabit server adapter (1000baseSX) +.It +HP NC370T PCI-X Multifunction Gigabit server adapter (10/100/1000baseT) +.It +HP Dual NC370i Multifunction Gigabit embedded server adapter (10/100/1000baseT) +.It +HP NC373F PCI Express Multifunction Gigabit server adapter (1000baseSX) +.It +HP NC373i PCI Express Multifunction Gigabit embedded server adapter (10/100/1000baseT) +.It +HP NC374m PCI Express Multifunction Gigabit embedded server adapter (10/100/1000baseT) +.It +HP NC373T PCI Express Multifunction Gigabit server adapter (10/100/1000baseT) +.It +HP NC380T PCI Express Dual Port Multifunction Gigabit server adapter (10/100/1000baseT) +.It +HP NC382T PCI Express Dual Port server adapter (10/100/1000baseT) +.El +.Pp +The NetXtreme II product family is composed of various Converged NIC (or CNIC) +Ethernet controllers which support a TCP Offload Engine (TOE), +Remote DMA (RDMA), and iSCSI acceleration, +in addition to standard L2 Ethernet traffic, +all on the same controller. +The following features are supported in the +.Nm +driver under +.Ox : +.Bd -literal -offset indent +IPv4 receive IP/TCP/UDP checksum offload +IPv4 transmit TCP/UDP checksum offload +.\"jumbo frames +VLAN tag insertion and stripping +interrupt coalescing +10/100/1000Mbps operation in full-duplex mode +10/100Mbps operation in half-duplex mode +.Ed +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width "10baseT/UTP" +.It Cm autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode via +.Xr ifconfig 8 . +.It Cm 10baseT/UTP +Set 10Mbps operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 1000baseT +Set 1000baseT operation over twisted pair. +Only +.Cm full-duplex +mode is supported. +.It Cm 1000baseSX +Set 1000Mbps (Gigabit Ethernet) operation. +Only +.Cm full-duplex +mode is supported. +.It Cm 2500baseSX +Set 2500Mbps operation. +Only +.Cm full-duplex +mode is supported. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width "full-duplex" +.It Cm full-duplex +Force full duplex operation. +.It Cm half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh FILES +The adapter needs firmware files to run, which are loaded on demand by the +driver when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/bnx-b06 +.It Pa /etc/firmware/bnx-b09 +.It Pa /etc/firmware/bnx-rv2p +.It Pa /etc/firmware/bnx-xi-rv2p +.It Pa /etc/firmware/bnx-xi90-rv2p +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr brgphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Christensen Aq Mt davidch@broadcom.com +and ported to +.Ox +by +.An Brad Smith Aq Mt brad@openbsd.org . diff --git a/static/openbsd/man4/bnxt.4 b/static/openbsd/man4/bnxt.4 new file mode 100644 index 00000000..8399217d --- /dev/null +++ b/static/openbsd/man4/bnxt.4 @@ -0,0 +1,75 @@ +.\" $OpenBSD: bnxt.4,v 1.5 2026/03/12 23:15:47 jmatthew Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Matthew +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 12 2026 $ +.Dt BNXT 4 +.Os +.Sh NAME +.Nm bnxt +.Nd Broadcom NetXtreme-C/E 10Gb/25Gb/40Gb/50/100Gb Ethernet device +.Sh SYNOPSIS +.Cd "bnxt* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports the Broadcom NetXtreme-C/E PCI Express Ethernet +adapters based on the Broadcom BCM573xx, BCM574xx and BCM575xx chipsets, +including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +Broadcom P150c Adapter (10/25/40/50Gb QSFP28) +.It +Broadcom P150p Adapter (10/25/40/50Gb QSFP28) +.It +Broadcom P210c Adapter (10Gb SFP+) +.It +Broadcom P210p Adapter (10Gb SFP+) +.It +Broadcom P210tp Adapter (10GBASE-T) +.It +Broadcom P225c Adapter (10/25Gb QSFP28) +.It +Broadcom P225p Adapter (10/25Gb SFP28) +.It +Broadcom P425p Adapter (10/25Gb SFP28) +.It +Broadcom P1200G Adapter (10/25/40/50/100Gb QSFP56) +.It +Broadcom P2100G Adapter (10/25/40/50/100Gb QSFP56) +.El +.Pp +Adapters based on these chipsets are also available as LOM/Mezzanine +options for Dell, Lenovo, HPE and Supermicro servers. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . diff --git a/static/openbsd/man4/boca.4 b/static/openbsd/man4/boca.4 new file mode 100644 index 00000000..9ad05d60 --- /dev/null +++ b/static/openbsd/man4/boca.4 @@ -0,0 +1,107 @@ +.\" $OpenBSD: boca.4,v 1.12 2014/02/20 17:56:35 schwarze Exp $ +.\" +.\" Copyright (c) 1990, 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)dca.4 5.2 (Berkeley) 3/27/91 +.\" from: Id: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp +.\" +.Dd $Mdocdate: February 20 2014 $ +.Dt BOCA 4 +.Os +.Sh NAME +.Nm boca +.Nd multiplexing serial communications interface +.Sh SYNOPSIS +For 4-port BB1004 boards and 8-port BB1008 boards: +.Pp +.Cd "boca0 at isa? port 0x100 irq 5" +.Cd "com* at boca?" +.Pp +For 16-port BB2016 boards: +.Pp +.Cd "boca0 at isa? port 0x100 irq 5" +.Cd "boca1 at isa? port 0x140 irq 5" +.Cd "com* at boca?" +.Pp +(The BB2016 is functionally equivalent to two BB1008 boards, +and is configured as such.) +.Sh DESCRIPTION +The +.Nm +driver provides support for BOCA Research BB1004, BB1008, and BB2016 +boards that multiplex together up to four, eight, or sixteen +.Tn EIA +.Tn RS-232C +.Pq Tn CCITT V.28 +communications interfaces. +.Pp +Each +.Nm +device is the master device for up to eight +.Nm com +devices. +The kernel configuration specifies these +.Nm com +devices as slave devices of the +.Nm +device, as shown in +.Sx SYNOPSIS . +The slave ID given for each +.Nm com +device determines which bit in the interrupt multiplexing register is +tested to find interrupts for that device. +The +.Cd port +specification for the +.Nm +device is used to compute the base addresses for the +.Nm com +subdevices and the port for the interrupt multiplexing register. +.Sh FILES +.Bl -tag -width Pa +.It Pa /dev/tty?? +.El +.Sh SEE ALSO +.Xr com 4 , +.Xr intro 4 , +.Xr isa 4 +.Sh HISTORY +The +.Nm +driver was written by +.An Charles Hannum , +based on the +.Nm ast +driver and source code from +.An David Muir Sharnoff . +David wishes to acknowledge the assistance of +.An Jason Venner +in determining how to use the BOCA boards. diff --git a/static/openbsd/man4/bpe.4 b/static/openbsd/man4/bpe.4 new file mode 100644 index 00000000..4bea103f --- /dev/null +++ b/static/openbsd/man4/bpe.4 @@ -0,0 +1,160 @@ +.\" $OpenBSD: bpe.4,v 1.6 2022/09/12 09:15:29 jsg Exp $ +.\" +.\" Copyright (c) 2018 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 12 2022 $ +.Dt BPE 4 +.Os +.Sh NAME +.Nm bpe +.Nd Backbone Provider Edge pseudo-device +.Sh SYNOPSIS +.Cd "pseudo-device bpe" +.Sh DESCRIPTION +The +.Nm bpe +driver creates IEEE 802.1Q Provider Backbone Bridge (PBB) networks +by acting as a Backbone Edge Bridge (BEB). +PBB, also known as mac-in-mac, was originally specified in +IEEE 802.1ah-2008 and became part of IEEE 802.1Q-2011. +.Pp +A Provider Backbone Bridge Network (PBBN) consists of BEBs +interconnected by Backbone Core Bridges (BCBs) to form an Ethernet +network for the transport of encapsulated Ethernet packets. +Where VLAN and SVLAN protocols add a shim to differentiate Ethernet +packets for different networks but retain the Ethernet addresses +of encapsulated traffic, PBB completely encapsulates Ethernet packets +for transmission between BEBs on a PBBN. +This removes the need for intermediate BCB devices on the backbone +network to learn the Ethernet addresses of devices on the encapsulated +network, but requires each BEB to maintain a mapping of addresses +on the encapsulated network to peer BEBs. +.Pp +A PBB packet consists of another Ethernet frame containing Ethernet +addresses for BEBs and the PBB Ethernet protocol type (0x88e7), a +32-bit Backbone Service Instance Tag (I-TAG), followed by the +encapsulated Ethernet frame. +The I-TAG contains a 24-bit Backbone Service Instance Identifier +(I-SID) to differentiate different PBBNs on the same backbone network +.Pp +IEEE 802.1Q describes customer VLANs being encapsulated by PBB, +which in turn uses an S-VLAN service. +This can be implemented with +.Xr vlan 4 +using a +.Nm bpe +interface as the parent, +and with the +.Nm bpe +interface using +.Xr svlan 4 +as the parent. +.Nm bpe +itself does not require this topology, therefore allowing flexible +deployment and network topologies. +.Pp +The +.Nm bpe +driver implements a learning bridge on each interface. +The driver will learn the mapping of BEPs to encapsulated Ethernet +address based on traffic received from other devices on the backbone +network. +Traffic sent to broadcast, multicast, or unknown unicast Ethernet +addresses will be flooded to a multicast address on the backbone network. +The multicast address used for each PBB Service Instance +will begin with 01:1e:83 as the first three octets, with the I-SID +as the last three octets. +For example, a +.Nm bpe +interface with a vnetid of 1024 (0x400 in hex) will have a multicast +group address of 01:1e:83:00:04:00. +The address learning in +.Nm bpe +only uses the Ethernet addresses of encapsulated traffic for its +forwarding decisions; it does not use VLAN or S-VLAN tags to +differentiate services. +.Pp +.Nm bpe +interfaces can be created at runtime using the +.Ic ifconfig bpe Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The interface itself can be configured with +.Xr ifconfig 8 ; +see its manual page for more information. +.Pp +.Nm bpe +interfaces must be configured with a parent Ethernet interface to +operate, and a virtual network identifier for use as the I-SID. +.Pp +The I-TAG includes a priority field. +By default, the value of the priority field in a transmitted packet +is based on the priority of packets sent over the interface, which +may be altered via +.Xr pf.conf 5 ; +see the +.Cm prio +option for more information. +Alternatively, +.Cm txprio +can set a specific priority for transmitted packets. +.Pp +.Nm bpe +interfaces support the following +.Xr ioctl 2 Ns s : +.Bl -tag -width indent -offset 3n +.It Dv SIOCSIFPARENT Fa "struct if_parent *" +Set the parent interface. +The parent may only be configured while the virtual interface is +administratively down. +.It Dv SIOCGIFPARENT Fa "struct if_parent *" +Get the currently configured parent interface. +.It Dv SIOCDIFPARENT Fa "struct ifreq *" +Delete the parent interface configuration. +The parent may only be removed while the virtual interface is +administratively down. +.It Dv SIOCSVNETID Fa "struct ifreq *" +Set the virtual network identifier. +Valid identifiers are 24-bit values in the range 0 to 16777215. +.It Dv SIOCGVNETID Fa "struct ifreq *" +Get the currently configured virtual network identifier. +.El +.Sh SEE ALSO +.Xr bridge 4 , +.Xr inet 4 , +.Xr ip 4 , +.Xr netintro 4 , +.Xr vlan 4 , +.Xr hostname.if 5 , +.Xr pf.conf 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Rs +.%T IEEE 802.1Q standard +.%U https://standards.ieee.org/standard/802_1Q-2018.html +.Re +.Rs +.%Q Provider Backbone Bridges +.%T IEEE 802.1ah standard +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.5 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/bpf.4 b/static/openbsd/man4/bpf.4 new file mode 100644 index 00000000..05e55c7a --- /dev/null +++ b/static/openbsd/man4/bpf.4 @@ -0,0 +1,1119 @@ +.\" $OpenBSD: bpf.4,v 1.51 2025/11/21 14:48:34 schwarze Exp $ +.\" $NetBSD: bpf.4,v 1.7 1995/09/27 18:31:50 thorpej Exp $ +.\" +.\" Copyright (c) 1990 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that: (1) source code distributions +.\" retain the above copyright notice and this paragraph in its entirety, (2) +.\" distributions including binary code include the above copyright notice and +.\" this paragraph in its entirety in the documentation or other materials +.\" provided with the distribution, and (3) all advertising materials mentioning +.\" features or use of this software display the following acknowledgement: +.\" ``This product includes software developed by the University of California, +.\" Lawrence Berkeley Laboratory and its contributors.'' Neither the name of +.\" the University nor the names of its contributors may be used to endorse +.\" or promote products derived from this software without specific prior +.\" written permission. +.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED +.\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. +.\" +.\" This document is derived in part from the enet man page (enet.4) +.\" distributed with 4.3BSD Unix. +.\" +.Dd $Mdocdate: November 21 2025 $ +.Dt BPF 4 +.Os +.Sh NAME +.Nm bpf +.Nd Berkeley Packet Filter +.Sh SYNOPSIS +.Cd "pseudo-device bpfilter" +.Sh DESCRIPTION +The Berkeley Packet Filter provides a raw interface to data link layers in +a protocol-independent fashion. +All packets on the network, even those destined for other hosts, are +accessible through this mechanism. +.Pp +The packet filter appears as a character special device, +.Pa /dev/bpf . +After opening the device, the file descriptor must be bound to a specific +network interface with the +.Dv BIOCSETIF +.Xr ioctl 2 . +A given interface can be shared between multiple listeners, and the filter +underlying each descriptor will see an identical packet stream. +.Pp +Associated with each open instance of a +.Nm +file is a user-settable +packet filter. +Whenever a packet is received by an interface, all file descriptors +listening on that interface apply their filter. +Each descriptor that accepts the packet receives its own copy. +.Pp +Reads from these files return the next group of packets that have matched +the filter. +To improve performance, the buffer passed to read must be the same size as +the buffers used internally by +.Nm bpf . +This size is returned by the +.Dv BIOCGBLEN +.Xr ioctl 2 +and can be set with +.Dv BIOCSBLEN . +Note that an individual packet larger than this size is necessarily truncated. +.Pp +A packet can be sent out on the network by writing to a +.Nm +file descriptor. +Each descriptor can also have a user-settable filter +for controlling the writes. +Only packets matching the filter are sent out of the interface. +The writes are unbuffered, meaning only one packet can be processed per write. +.Pp +Once a descriptor is configured, further changes to the configuration +can be prevented using the +.Dv BIOCLOCK +.Xr ioctl 2 . +.Sh IOCTL INTERFACE +The +.Xr ioctl 2 +command codes below are defined in +.In net/bpf.h . +All commands require these includes: +.Pp +.nr nS 1 +.In sys/types.h +.In sys/time.h +.In sys/ioctl.h +.In net/bpf.h +.nr nS 0 +.Pp +Additionally, +.Dv BIOCGETIF +and +.Dv BIOCSETIF +require +.In sys/socket.h +and +.In net/if.h . +.Pp +The (third) argument to the +.Xr ioctl 2 +call should be a pointer to the type indicated. +.Pp +.Bl -tag -width Ds -compact +.It Dv BIOCGBLEN Fa "u_int *" +Returns the required buffer length for reads on +.Nm +files. +.Pp +.It Dv BIOCSBLEN Fa "u_int *" +Sets the buffer length for reads on +.Nm +files. +The buffer must be set before the file is attached to an interface with +.Dv BIOCSETIF . +If the requested buffer size cannot be accommodated, the closest allowable +size will be set and returned in the argument. +A read call will result in +.Er EINVAL +if it is passed a buffer that is not this size. +.Pp +.It Dv BIOCGDLT Fa "u_int *" +Returns the type of the data link layer underlying the attached interface. +.Er EINVAL +is returned if no interface has been specified. +The device types, prefixed with +.Dq DLT_ , +are defined in +.In net/bpf.h . +.Pp +.It Dv BIOCGDLTLIST Fa "struct bpf_dltlist *" +Returns an array of the available types of the data link layer +underlying the attached interface: +.Bd -literal -offset indent +struct bpf_dltlist { + u_int bfl_len; + u_int *bfl_list; +}; +.Ed +.Pp +The available types are returned in the array pointed to by the +.Va bfl_list +field while their length in +.Vt u_int +is supplied to the +.Va bfl_len +field. +.Er ENOMEM +is returned if there is not enough buffer space and +.Er EFAULT +is returned if a bad address is encountered. +The +.Va bfl_len +field is modified on return to indicate the actual length in +.Vt u_int +of the array returned. +If +.Va bfl_list +is +.Dv NULL , +the +.Va bfl_len +field is set to indicate the required length of the array in +.Vt u_int . +.Pp +.It Dv BIOCSDLT Fa "u_int *" +Changes the type of the data link layer underlying the attached interface. +.Er EINVAL +is returned if no interface has been specified or the specified +type is not available for the interface. +.Pp +.It Dv BIOCPROMISC +Forces the interface into promiscuous mode. +All packets, not just those destined for the local host, are processed. +Since more than one file can be listening on a given interface, a listener +that opened its interface non-promiscuously may receive packets promiscuously. +This problem can be remedied with an appropriate filter. +.Pp +The interface remains in promiscuous mode until all files listening +promiscuously are closed. +.Pp +.It Dv BIOCFLUSH +Flushes the buffer of incoming packets and resets the statistics that are +returned by +.Dv BIOCGSTATS . +.Pp +.It Dv BIOCLOCK +Prevents further changes to the configuration of the +.Nm +descriptor by only permitting a set of +.Dq known safe +ioctls: +.Dv BIOCFLUSH , +.Dv BIOCGBLEN , +.Dv BIOCGDIRFILT , +.Dv BIOCGDLT , +.Dv BIOCGDIRFILT , +.Dv BIOCGDLTLIST , +.Dv BIOCGETIF , +.Dv BIOCGHDRCMPLT , +.Dv BIOCGRSIG , +.Dv BIOCGRTIMEOUT , +.Dv BIOCGSTATS , +.Dv BIOCIMMEDIATE , +.Dv BIOCLOCK , +.Dv BIOCSRTIMEOUT , +.Dv BIOCSWTIMEOUT , +.Dv BIOCDWTIMEOUT , +.Dv BIOCVERSION , +.Dv TIOCGPGRP , +and +.Dv FIONREAD . +All other ioctl operations will be denied with +.Er EPERM . +.Pp +The purpose of this mechanism is that a privileged program can open a +.Nm +device, drop privileges, set the interface, provide filters and modes, +and then lock it with +.Dv BIOCLOCK . +If the device is opened with write, +.Dv BIOCLOCK +does not prevent writes, so a write filter is probably needed. +If applied correctly, a bug in a program will not result in the ability to +see or send unfiltered traffic to the network interface. +.Pp +.It Dv BIOCGETIF Fa "struct ifreq *" +Returns the name of the hardware interface that the file is listening on. +The name is returned in the +.Fa ifr_name +field of the +.Vt struct ifreq . +All other fields are undefined. +.Pp +.It Dv BIOCSETIF Fa "struct ifreq *" +Sets the hardware interface associated with the file. +This command must be performed before any packets can be read. +The device is indicated by name using the +.Fa ifr_name +field of the +.Vt struct ifreq . +Additionally, performs the actions of +.Dv BIOCFLUSH . +.Pp +.It Dv BIOCSRTIMEOUT Fa "struct timeval *" +.It Dv BIOCGRTIMEOUT Fa "struct timeval *" +Sets or gets the read timeout parameter. +The +.Ar timeval +specifies the length of time to wait before timing out on a read request. +This parameter is initialized to zero by +.Xr open 2 , +indicating no timeout. +.Pp +.It Dv BIOCGSTATS Fa "struct bpf_stat *" +Returns the following structure of packet statistics: +.Bd -literal -offset indent +struct bpf_stat { + u_int bs_recv; + u_int bs_drop; +}; +.Ed +.Pp +The fields are: +.Bl -tag -width bs_recv +.It Fa bs_recv +Number of packets received by the descriptor since opened or reset (including +any buffered since the last read call). +.It Fa bs_drop +Number of packets which were accepted by the filter but dropped by the kernel +because of buffer overflows (i.e., the application's reads aren't keeping up +with the packet traffic). +.El +.Pp +.It Dv BIOCIMMEDIATE Fa "u_int *" +Enables or disables +.Dq immediate mode , +based on the truth value of the argument. +When immediate mode is enabled, reads return immediately upon packet reception. +Otherwise, a read will block until either the kernel buffer becomes full or a +timeout occurs. +This is useful for programs like +.Xr rarpd 8 , +which must respond to messages in real time. +The default for a new file is off. +.Pp +.It Dv BIOCSWTIMEOUT Fa "struct timeval *" +.It Dv BIOCGWTIMEOUT Fa "struct timeval *" +.It Dv BIOCDWTIMEOUT +Sets, gets, or deletes (resets) the wait timeout parameter. +The +.Ar timeval +specifies the length of time to wait between receiving a packet and +the kernel buffer becoming readable. +By default, or when reset, the wait timeout is infinite, meaning +the age of packets in the kernel buffer does not make the buffer +readable. +The maximum wait time that can be set is 5 minutes (300 seconds). +.Pp +.It Dv BIOCSETF Fa "struct bpf_program *" +.It Dv BIOCSETFNR Fa "struct bpf_program *" +Sets the filter program used by the kernel to discard uninteresting packets. +An array of instructions and its length are passed in using the following +structure: +.Bd -literal -offset indent +struct bpf_program { + u_int bf_len; + struct bpf_insn *bf_insns; +}; +.Ed +.Pp +The filter program is pointed to by the +.Fa bf_insns +field, while its length in units of +.Vt struct bpf_insn +is given by the +.Fa bf_len +field. +If +.Dv BIOCSETF +is used, the actions of +.Dv BIOCFLUSH +are also performed. +.Pp +See section +.Sx FILTER MACHINE +for an explanation of the filter language. +.Pp +.It Dv BIOCSETWF Fa "struct bpf_program *" +Sets the filter program used by the kernel to filter the packets +written to the descriptor before the packets are sent out on the +network. +See +.Dv BIOCSETF +for a description of the filter program. +.Pp +Note that the filter operates on the packet data written to the descriptor. +If the +.Dq header complete +flag is not set, the kernel sets the link-layer source address +of the packet after filtering. +.Pp +.It Dv BIOCVERSION Fa "struct bpf_version *" +Returns the major and minor version numbers of the filter language currently +recognized by the kernel. +Before installing a filter, applications must check that the current version +is compatible with the running kernel. +Version numbers are compatible if the major numbers match and the application +minor is less than or equal to the kernel minor. +The kernel version number is returned in the following structure: +.Bd -literal -offset indent +struct bpf_version { + u_short bv_major; + u_short bv_minor; +}; +.Ed +.Pp +The current version numbers are given by +.Dv BPF_MAJOR_VERSION +and +.Dv BPF_MINOR_VERSION +from +.In net/bpf.h . +An incompatible filter may result in undefined behavior (most likely, an +error returned by +.Xr ioctl 2 +or haphazard packet matching). +.Pp +.It Dv BIOCSRSIG Fa "u_int *" +.It Dv BIOCGRSIG Fa "u_int *" +Sets or gets the receive signal. +This signal will be sent to the process or process group specified by +.Dv FIOSETOWN . +It defaults to +.Dv SIGIO . +.Pp +.It Dv BIOCSHDRCMPLT Fa "u_int *" +.It Dv BIOCGHDRCMPLT Fa "u_int *" +Sets or gets the status of the +.Dq header complete +flag. +Set to zero if the link level source address should be filled in +automatically by the interface output routine. +Set to one if the link level source address will be written, +as provided, to the wire. +This flag is initialized to zero by default. +.Pp +.It Dv BIOCSFILDROP Fa "u_int *" +.It Dv BIOCGFILDROP Fa "u_int *" +Sets or gets the +.Dq filter drop +action. +The supported actions for packets matching the filter are: +.Pp +.Bl -tag -width "BPF_FILDROP_CAPTURE" -compact +.It Dv BPF_FILDROP_PASS +Accept and capture +.It Dv BPF_FILDROP_CAPTURE +Drop and capture +.It Dv BPF_FILDROP_DROP +Drop and do not capture +.El +.Pp +Packets matching any filter configured to drop packets will be +reported to the associated interface so that they can be dropped. +The default action is +.Dv BPF_FILDROP_PASS . +.Pp +.It Dv BIOCSDIRFILT Fa "u_int *" +.It Dv BIOCGDIRFILT Fa "u_int *" +Sets or gets the status of the +.Dq direction filter +flag. +If non-zero, packets matching the specified direction (either +.Dv BPF_DIRECTION_IN +or +.Dv BPF_DIRECTION_OUT ) +will be ignored. +.El +.Ss Standard ioctls +.Nm +now supports several standard ioctls which allow the user to do asynchronous +and/or non-blocking I/O to an open +.Nm +file descriptor. +.Pp +.Bl -tag -width Ds -compact +.It Dv FIONREAD Fa "int *" +Returns the number of bytes that are immediately available for reading. +.Pp +.It Dv FIONBIO Fa "int *" +Sets or clears non-blocking I/O. +If the argument is non-zero, enable non-blocking I/O. +If the argument is zero, disable non-blocking I/O. +If non-blocking I/O is enabled, the return value of a read while no data +is available will be 0. +The non-blocking read behavior is different from performing non-blocking +reads on other file descriptors, which will return \-1 and set +.Va errno +to +.Er EAGAIN +if no data is available. +Note: setting this overrides the timeout set by +.Dv BIOCSRTIMEOUT . +.Pp +.It Dv FIOASYNC Fa "int *" +Enables or disables asynchronous I/O. +When enabled (argument is non-zero), the process or process group specified +by +.Dv FIOSETOWN +will start receiving +.Dv SIGIO +signals when packets arrive. +Note that you must perform an +.Dv FIOSETOWN +command in order for this to take effect, as the system will not do it by +default. +The signal may be changed via +.Dv BIOCSRSIG . +.Pp +.It Dv FIOSETOWN Fa "int *" +.It Dv FIOGETOWN Fa "int *" +Sets or gets the process or process group (if negative) that should receive +.Dv SIGIO +when packets are available. +The signal may be changed using +.Dv BIOCSRSIG +(see above). +.El +.Ss BPF header +The following structure is prepended to each packet returned by +.Xr read 2 : +.Bd -literal -offset indent +struct bpf_hdr { + struct bpf_timeval bh_tstamp; + u_int32_t bh_caplen; + u_int32_t bh_datalen; + u_int16_t bh_hdrlen; +}; +.Ed +.Pp +The fields, stored in host order, are as follows: +.Bl -tag -width Ds +.It Fa bh_tstamp +Time at which the packet was processed by the packet filter. +.It Fa bh_caplen +Length of the captured portion of the packet. +This is the minimum of the truncation amount specified by the filter and the +length of the packet. +.It Fa bh_datalen +Length of the packet off the wire. +This value is independent of the truncation amount specified by the filter. +.It Fa bh_hdrlen +Length of the BPF header, which may not be equal to +.Li sizeof(struct bpf_hdr) . +.El +.Pp +The +.Fa bh_hdrlen +field exists to account for padding between the header and the link level +protocol. +The purpose here is to guarantee proper alignment of the packet data +structures, which is required on alignment-sensitive architectures and +improves performance on many other architectures. +The packet filter ensures that the +.Fa bpf_hdr +and the network layer header will be word aligned. +Suitable precautions must be taken when accessing the link layer protocol +fields on alignment restricted machines. +(This isn't a problem on an Ethernet, since the type field is a +.Vt short +falling on an even offset, and the addresses are probably accessed in a +bytewise fashion). +.Pp +Additionally, individual packets are padded so that each starts on a +word boundary. +This requires that an application has some knowledge of how to get from packet +to packet. +The macro +.Dv BPF_WORDALIGN +is defined in +.In net/bpf.h +to facilitate this process. +It rounds up its argument to the nearest word aligned value (where a word is +.Dv BPF_ALIGNMENT +bytes wide). +For example, if +.Va p +points to the start of a packet, this expression will advance it to the +next packet: +.Pp +.Dl p = (char *)p + BPF_WORDALIGN(p->bh_hdrlen + p->bh_caplen); +.Pp +For the alignment mechanisms to work properly, the buffer passed to +.Xr read 2 +must itself be word aligned. +.Xr malloc 3 +will always return an aligned buffer. +.Ss Filter machine +A filter program is an array of instructions with all branches forwardly +directed, terminated by a +.Dq return +instruction. +Each instruction performs some action on the pseudo-machine state, which +consists of an accumulator, index register, scratch memory store, and +implicit program counter. +.Pp +The following structure defines the instruction format: +.Bd -literal -offset indent +struct bpf_insn { + u_int16_t code; + u_char jt; + u_char jf; + u_int32_t k; +}; +.Ed +.Pp +The +.Fa k +field is used in different ways by different instructions, and the +.Fa jt +and +.Fa jf +fields are used as offsets by the branch instructions. +The opcodes are encoded in a semi-hierarchical fashion. +There are eight classes of instructions: +.Dv BPF_LD , +.Dv BPF_LDX , +.Dv BPF_ST , +.Dv BPF_STX , +.Dv BPF_ALU , +.Dv BPF_JMP , +.Dv BPF_RET , +and +.Dv BPF_MISC . +Various other mode and operator bits are logically OR'd into the class to +give the actual instructions. +The classes and modes are defined in +.In net/bpf.h . +Below are the semantics for each defined +.Nm +instruction. +We use the convention that A is the accumulator, X is the index register, +P[] packet data, and M[] scratch memory store. +P[i:n] gives the data at byte offset +.Dq i +in the packet, interpreted as a word (n=4), unsigned halfword (n=2), or +unsigned byte (n=1). +M[i] gives the i'th word in the scratch memory store, which is only addressed +in word units. +The memory store is indexed from 0 to +.Dv BPF_MEMWORDS Ns \-1 . +.Fa k , +.Fa jt , +and +.Fa jf +are the corresponding fields in the instruction definition. +.Dq len +refers to the length of the packet. +.Bl -tag -width Ds +.It Dv BPF_LD +These instructions copy a value into the accumulator. +The type of the source operand is specified by an +.Dq addressing mode +and can be a constant +.Pf ( Dv BPF_IMM ) , +packet data at a fixed offset +.Pf ( Dv BPF_ABS ) , +packet data at a variable offset +.Pf ( Dv BPF_IND ) , +the packet length +.Pf ( Dv BPF_LEN ) , +a random number +.Pf ( Dv BPF_RND ) , +or a word in the scratch memory store +.Pf ( Dv BPF_MEM ) . +For +.Dv BPF_IND +and +.Dv BPF_ABS , +the data size must be specified as a word +.Pf ( Dv BPF_W ) , +halfword +.Pf ( Dv BPF_H ) , +or byte +.Pf ( Dv BPF_B ) . +The semantics of all recognized +.Dv BPF_LD +instructions follow. +.Pp +.Bl -tag -width 32n -compact +.Sm off +.It Xo Dv BPF_LD No + Dv BPF_W No + +.Dv BPF_ABS +.Xc +.Sm on +A <- P[k:4] +.Sm off +.It Xo Dv BPF_LD No + Dv BPF_H No + +.Dv BPF_ABS +.Xc +.Sm on +A <- P[k:2] +.Sm off +.It Xo Dv BPF_LD No + Dv BPF_B No + +.Dv BPF_ABS +.Xc +.Sm on +A <- P[k:1] +.Sm off +.It Xo Dv BPF_LD No + Dv BPF_W No + +.Dv BPF_IND +.Xc +.Sm on +A <- P[X+k:4] +.Sm off +.It Xo Dv BPF_LD No + Dv BPF_H No + +.Dv BPF_IND +.Xc +.Sm on +A <- P[X+k:2] +.Sm off +.It Xo Dv BPF_LD No + Dv BPF_B No + +.Dv BPF_IND +.Xc +.Sm on +A <- P[X+k:1] +.Sm off +.It Xo Dv BPF_LD No + Dv BPF_W No + +.Dv BPF_LEN +.Xc +.Sm on +A <- len +.Sm off +.It Xo Dv BPF_LD No + Dv BPF_W No + +.Dv BPF_RND +.Xc +.Sm on +A <- arc4random() +.Sm off +.It Dv BPF_LD No + Dv BPF_IMM +.Sm on +A <- k +.Sm off +.It Dv BPF_LD No + Dv BPF_MEM +.Sm on +A <- M[k] +.El +.It Dv BPF_LDX +These instructions load a value into the index register. +Note that the addressing modes are more restricted than those of the +accumulator loads, but they include +.Dv BPF_MSH , +a hack for efficiently loading the IP header length. +.Pp +.Bl -tag -width 32n -compact +.Sm off +.It Xo Dv BPF_LDX No + Dv BPF_W No + +.Dv BPF_IMM +.Xc +.Sm on +X <- k +.Sm off +.It Xo Dv BPF_LDX No + Dv BPF_W No + +.Dv BPF_MEM +.Xc +.Sm on +X <- M[k] +.Sm off +.It Xo Dv BPF_LDX No + Dv BPF_W No + +.Dv BPF_LEN +.Xc +.Sm on +X <- len +.Sm off +.It Xo Dv BPF_LDX No + Dv BPF_B No + +.Dv BPF_MSH +.Xc +.Sm on +X <- 4*(P[k:1]&0xf) +.El +.It Dv BPF_ST +This instruction stores the accumulator into the scratch memory. +We do not need an addressing mode since there is only one possibility for +the destination. +.Pp +.Bl -tag -width 32n -compact +.It Dv BPF_ST +M[k] <- A +.El +.It Dv BPF_STX +This instruction stores the index register in the scratch memory store. +.Pp +.Bl -tag -width 32n -compact +.It Dv BPF_STX +M[k] <- X +.El +.It Dv BPF_ALU +The ALU instructions perform operations between the accumulator and index +register or constant, and store the result back in the accumulator. +For binary operations, a source mode is required +.Pf ( Dv BPF_K +or +.Dv BPF_X ) . +.Pp +.Bl -tag -width 32n -compact +.Sm off +.It Xo Dv BPF_ALU No + BPF_ADD No + +.Dv BPF_K +.Xc +.Sm on +A <- A + k +.Sm off +.It Xo Dv BPF_ALU No + BPF_SUB No + +.Dv BPF_K +.Xc +.Sm on +A <- A - k +.Sm off +.It Xo Dv BPF_ALU No + BPF_MUL No + +.Dv BPF_K +.Xc +.Sm on +A <- A * k +.Sm off +.It Xo Dv BPF_ALU No + BPF_DIV No + +.Dv BPF_K +.Xc +.Sm on +A <- A / k +.Sm off +.It Xo Dv BPF_ALU No + BPF_MOD No + +.Dv BPF_K +.Xc +.Sm on +A <- A % k +.Sm off +.It Xo Dv BPF_ALU No + BPF_AND No + +.Dv BPF_K +.Xc +.Sm on +A <- A & k +.Sm off +.It Xo Dv BPF_ALU No + BPF_OR No + +.Dv BPF_K +.Xc +.Sm on +A <- A | k +.Sm off +.It Xo Dv BPF_ALU No + BPF_XOR No + +.Dv BPF_K +.Xc +.Sm on +A <- A ^ k +.Sm off +.It Xo Dv BPF_ALU No + BPF_LSH No + +.Dv BPF_K +.Xc +.Sm on +A <- A << k +.Sm off +.It Xo Dv BPF_ALU No + BPF_RSH No + +.Dv BPF_K +.Xc +.Sm on +A <- A >> k +.Sm off +.It Xo Dv BPF_ALU No + BPF_ADD No + +.Dv BPF_X +.Xc +.Sm on +A <- A + X +.Sm off +.It Xo Dv BPF_ALU No + BPF_SUB No + +.Dv BPF_X +.Xc +.Sm on +A <- A - X +.Sm off +.It Xo Dv BPF_ALU No + BPF_MUL No + +.Dv BPF_X +.Xc +.Sm on +A <- A * X +.Sm off +.It Xo Dv BPF_ALU No + BPF_DIV No + +.Dv BPF_X +.Xc +.Sm on +A <- A / X +.Sm off +.It Xo Dv BPF_ALU No + BPF_MOD No + +.Dv BPF_X +.Xc +.Sm on +A <- A % X +.Sm off +.It Xo Dv BPF_ALU No + BPF_AND No + +.Dv BPF_X +.Xc +.Sm on +A <- A & X +.Sm off +.It Xo Dv BPF_ALU No + BPF_OR No + +.Dv BPF_X +.Xc +.Sm on +A <- A | X +.Sm off +.It Xo Dv BPF_ALU No + BPF_XOR No + +.Dv BPF_X +.Xc +.Sm on +A <- A ^ X +.Sm off +.It Xo Dv BPF_ALU No + BPF_LSH No + +.Dv BPF_X +.Xc +.Sm on +A <- A << X +.Sm off +.It Xo Dv BPF_ALU No + BPF_RSH No + +.Dv BPF_X +.Xc +.Sm on +A <- A >> X +.Sm off +.It Dv BPF_ALU No + BPF_NEG +.Sm on +A <- -A +.El +.It Dv BPF_JMP +The jump instructions alter flow of control. +Conditional jumps compare the accumulator against a constant +.Pf ( Dv BPF_K ) +or the index register +.Pf ( Dv BPF_X ) . +If the result is true (or non-zero), the true branch is taken, otherwise the +false branch is taken. +Jump offsets are encoded in 8 bits so the longest jump is 256 instructions. +However, the jump always +.Pf ( Dv BPF_JA ) +opcode uses the 32-bit +.Fa k +field as the offset, allowing arbitrarily distant destinations. +All conditionals use unsigned comparison conventions. +.Pp +.Bl -tag -width 32n -compact +.Sm off +.It Dv BPF_JMP No + BPF_JA +pc += k +.Sm on +.Sm off +.It Xo Dv BPF_JMP No + BPF_JGT No + +.Dv BPF_K +.Xc +.Sm on +pc += (A > k) ? jt : jf +.Sm off +.It Xo Dv BPF_JMP No + BPF_JGE No + +.Dv BPF_K +.Xc +.Sm on +pc += (A >= k) ? jt : jf +.Sm off +.It Xo Dv BPF_JMP No + BPF_JEQ No + +.Dv BPF_K +.Xc +.Sm on +pc += (A == k) ? jt : jf +.Sm off +.It Xo Dv BPF_JMP No + BPF_JSET No + +.Dv BPF_K +.Xc +.Sm on +pc += (A & k) ? jt : jf +.Sm off +.It Xo Dv BPF_JMP No + BPF_JGT No + +.Dv BPF_X +.Xc +.Sm on +pc += (A > X) ? jt : jf +.Sm off +.It Xo Dv BPF_JMP No + BPF_JGE No + +.Dv BPF_X +.Xc +.Sm on +pc += (A >= X) ? jt : jf +.Sm off +.It Xo Dv BPF_JMP No + BPF_JEQ No + +.Dv BPF_X +.Xc +.Sm on +pc += (A == X) ? jt : jf +.Sm off +.It Xo Dv BPF_JMP No + BPF_JSET No + +.Dv BPF_X +.Xc +.Sm on +pc += (A & X) ? jt : jf +.El +.It Dv BPF_RET +The return instructions terminate the filter program and specify the +amount of packet to accept (i.e., they return the truncation amount) +or, for the write filter, the maximum acceptable size for the packet +(i.e., the packet is dropped if it is larger than the returned +amount). +A return value of zero indicates that the packet should be ignored/dropped. +The return value is either a constant +.Pf ( Dv BPF_K ) +or the accumulator +.Pf ( Dv BPF_A ) . +.Pp +.Bl -tag -width 32n -compact +.It Dv BPF_RET No + Dv BPF_A +Accept A bytes. +.It Dv BPF_RET No + Dv BPF_K +Accept k bytes. +.El +.It Dv BPF_MISC +The miscellaneous category was created for anything that doesn't fit into +the above classes, and for any new instructions that might need to be added. +Currently, these are the register transfer instructions that copy the index +register to the accumulator or vice versa. +.Pp +.Bl -tag -width 32n -compact +.Sm off +.It Dv BPF_MISC No + Dv BPF_TAX +.Sm on +X <- A +.Sm off +.It Dv BPF_MISC No + Dv BPF_TXA +.Sm on +A <- X +.El +.El +.Pp +The +.Nm +interface provides the following macros to facilitate array initializers: +.Bd -filled -offset indent +.Dv BPF_STMT ( Ns Ar opcode , +.Ar operand ) +.Pp +.Dv BPF_JUMP ( Ns Ar opcode , +.Ar operand , +.Ar true_offset , +.Ar false_offset ) +.Ed +.Sh FILES +.Bl -tag -width /dev/bpf -compact +.It Pa /dev/bpf +.Nm +device +.El +.Sh EXAMPLES +The following filter is taken from the Reverse ARP daemon. +It accepts only Reverse ARP requests. +.Bd -literal -offset indent +struct bpf_insn insns[] = { + BPF_STMT(BPF_LD+BPF_H+BPF_ABS, 12), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, ETHERTYPE_REVARP, 0, 3), + BPF_STMT(BPF_LD+BPF_H+BPF_ABS, 20), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, REVARP_REQUEST, 0, 1), + BPF_STMT(BPF_RET+BPF_K, sizeof(struct ether_arp) + + sizeof(struct ether_header)), + BPF_STMT(BPF_RET+BPF_K, 0), +}; +.Ed +.Pp +This filter accepts only IP packets between host 128.3.112.15 and +128.3.112.35. +.Bd -literal -offset indent +struct bpf_insn insns[] = { + BPF_STMT(BPF_LD+BPF_H+BPF_ABS, 12), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, ETHERTYPE_IP, 0, 8), + BPF_STMT(BPF_LD+BPF_W+BPF_ABS, 26), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 0x8003700f, 0, 2), + BPF_STMT(BPF_LD+BPF_W+BPF_ABS, 30), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 0x80037023, 3, 4), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 0x80037023, 0, 3), + BPF_STMT(BPF_LD+BPF_W+BPF_ABS, 30), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 0x8003700f, 0, 1), + BPF_STMT(BPF_RET+BPF_K, (u_int)-1), + BPF_STMT(BPF_RET+BPF_K, 0), +}; +.Ed +.Pp +Finally, this filter returns only TCP finger packets. +We must parse the IP header to reach the TCP header. +The +.Dv BPF_JSET +instruction checks that the IP fragment offset is 0 so we are sure that we +have a TCP header. +.Bd -literal -offset indent +struct bpf_insn insns[] = { + BPF_STMT(BPF_LD+BPF_H+BPF_ABS, 12), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, ETHERTYPE_IP, 0, 10), + BPF_STMT(BPF_LD+BPF_B+BPF_ABS, 23), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, IPPROTO_TCP, 0, 8), + BPF_STMT(BPF_LD+BPF_H+BPF_ABS, 20), + BPF_JUMP(BPF_JMP+BPF_JSET+BPF_K, 0x1fff, 6, 0), + BPF_STMT(BPF_LDX+BPF_B+BPF_MSH, 14), + BPF_STMT(BPF_LD+BPF_H+BPF_IND, 14), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 79, 2, 0), + BPF_STMT(BPF_LD+BPF_H+BPF_IND, 16), + BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, 79, 0, 1), + BPF_STMT(BPF_RET+BPF_K, (u_int)-1), + BPF_STMT(BPF_RET+BPF_K, 0), +}; +.Ed +.Sh ERRORS +If the +.Xr ioctl 2 +call fails, +.Xr errno 2 +is set to one of the following values: +.Bl -tag -width Er +.It Bq Er EINVAL +The timeout used in a +.Dv BIOCSRTIMEOUT +request is negative. +.It Bq Er EINVAL +The timeout used in a +.Dv BIOCSRTIMEOUT +request specified a microsecond value less than zero or +greater than or equal to 1 million. +.It Bq Er EOVERFLOW +The timeout used in a +.Dv BIOCSRTIMEOUT +request is too large to be represented by an +.Vt int . +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr read 2 , +.Xr select 2 , +.Xr signal 3 , +.Xr MAKEDEV 8 , +.Xr tcpdump 8 , +.Xr arc4random 9 +.Rs +.%A McCanne, S. +.%A Jacobson, V. +.%D January 1993 +.%J 1993 Winter USENIX Conference +.%T The BSD Packet Filter: A New Architecture for User-level Packet Capture +.Re +.Sh HISTORY +The Enet packet filter was created in 1980 by Mike Accetta and Rick Rashid +at Carnegie-Mellon University. +Jeffrey Mogul, at Stanford, ported the code to +.Bx +and continued its +development from 1983 on. +Since then, it has evolved into the Ultrix Packet Filter at DEC, a STREAMS +NIT module under SunOS 4.1, and BPF. +.Sh AUTHORS +.An -nosplit +.An Steve McCanne +of Lawrence Berkeley Laboratory implemented BPF in Summer 1990. +Much of the design is due to +.An Van Jacobson . +.Sh BUGS +The read buffer must be of a fixed size (returned by the +.Dv BIOCGBLEN +ioctl). +.Pp +A file that does not request promiscuous mode may receive promiscuously +received packets as a side effect of another file requesting this mode on +the same hardware interface. +This could be fixed in the kernel with additional processing overhead. +However, we favor the model where all files must assume that the interface +is promiscuous, and if so desired, must utilize a filter to reject foreign +packets. diff --git a/static/openbsd/man4/brgphy.4 b/static/openbsd/man4/brgphy.4 new file mode 100644 index 00000000..548fa97d --- /dev/null +++ b/static/openbsd/man4/brgphy.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: brgphy.4,v 1.25 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2000 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt BRGPHY 4 +.Os +.Sh NAME +.Nm brgphy +.Nd Broadcom BCM54xx/BCM57xx 10/100/1Gb/2.5Gb Ethernet PHY +.Sh SYNOPSIS +.Cd "brgphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports Broadcom BCM5400 100/1000TX Ethernet PHY interfaces, as well +as the BCM5401, BCM541x, BCM5421, BCM54K2, BCM5462, BCM546x, BCM570x, BCM5714, +BCM5722, BCM575x, BCM5761, BCM578x, BCM5906 and BCM57780 10/100/1000baseT +Ethernet PHY interfaces, and BCM5708S Gigabit/2500 Ethernet PHY interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/bridge.4 b/static/openbsd/man4/bridge.4 new file mode 100644 index 00000000..58e6c1aa --- /dev/null +++ b/static/openbsd/man4/bridge.4 @@ -0,0 +1,703 @@ +.\" $OpenBSD: bridge.4,v 1.83 2022/03/31 17:27:20 naddy Exp $ +.\" +.\" Copyright (c) 1999-2001 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt BRIDGE 4 +.Os +.Sh NAME +.Nm bridge +.Nd Ethernet bridge interface +.Sh SYNOPSIS +.Cd "pseudo-device bridge" +.Pp +.In sys/types.h +.In net/if.h +.In netinet/in.h +.In netinet/if_ether.h +.In net/if_bridge.h +.Sh DESCRIPTION +The +.Nm +device creates a logical link between two or more Ethernet interfaces or +encapsulation interfaces (see +.Xr etherip 4 ) . +This link between the interfaces selectively forwards frames from +each interface on the bridge to every other interface on the bridge. +A bridge can serve several services, including isolation of traffic between +sets of machines so that traffic local to one set of machines is not +available on the wire of another set of machines, and it can act as +a transparent filter for +.Xr ip 4 +datagrams. +.Pp +A +.Nm +interface can be created at runtime using the +.Ic ifconfig bridge Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +.Pp +The bridges provided by this interface are learning bridges with +filtering; see +.Xr pf 4 . +In general a bridge works like a hub, forwarding traffic from one interface +to another. +It differs from a hub in that it will "learn" which machines +are on each of its attached segments by actively listening to +incoming traffic and examining the headers of each frame. +A table is built containing the MAC address and segment to which the +MAC address is attached. +This allows a bridge to be more selective about what it forwards, +which can be used to reduce traffic on a set of segments and also to provide +an IP firewall without changing the topology of the network. +.Pp +The algorithm works as follows by default, but can be modified via +.Xr ioctl 2 +or the utility +.Xr ifconfig 8 . +When a frame comes in, the origin segment and the source address are +recorded. +If the bridge has no knowledge about where the destination is to be found, +the bridge will forward the frame to all attached segments. +If the destination is known to be on a different segment from its origin, the +bridge will forward the packet only to the destination segment. +If the destination is on the same segment as the origin segment, the bridge +will drop the packet because the receiver has already had a chance to see +the frame. +Before forwarding a frame, the bridge will check to see if the packet +contains an +.Xr ip 4 +or +.Xr ip6 4 +datagram; if so, the datagram is run through the +pf interface so that it can be filtered. +See the +.Sx NOTES +section for details. +.Sh SPANNING TREE +The bridge has support for 802.1D-2004 Spanning Tree Protocol (STP), +which can be used to detect and remove loops in a network topology. +Using the +.Cm stp +or +.Cm -stp +commands +to +.Nm , +STP can be enabled or disabled on each port. +.Pp +The bridge will use the Rapid Spanning Tree Protocol (RSTP) by default +to allow rapid transitions to the forwarding state. +The +.Cm proto +command to +.Nm +can be used to force operation in the common Spanning Tree Protocol +without rapid state transitions. +Note that RSTP will be compatible with remote bridges running common STP. +.Sh SPAN PORTS +The bridge can have interfaces added to it as span ports. +Span ports transmit a copy of every frame received by the bridge. +This is most useful for snooping a bridged network passively on +another host connected to one of the span ports of the bridge. +Span ports cannot be bridge members; instead, the +.Cm addspan +and +.Cm delspan +commands are used to add and delete span ports to and from a bridge. +.Sh IOCTLS +A +.Nm +interface responds to all of the +.Xr ioctl 2 +calls specific to other interfaces listed in +.Xr netintro 4 . +The following +.Xr ioctl 2 +calls are specific to +.Nm +devices. +They are defined in +.In sys/sockio.h . +Some +.Xr ioctl 2 +calls are used by +.Xr veb 4 +and +.Xr tpmr 4 +as well. +.Bl -tag -width Ds +.It Dv SIOCBRDGIFS Fa "struct ifbifconf *" +Retrieve member interface list from a bridge. +This request takes an +.Vt ifbifconf +structure (see below) as a value-result parameter. +The +.Va ifbic_len +field should be initially set to the size of the buffer +pointed to by +.Va ifbic_buf . +On return it will contain the length, in bytes, of the configuration +list. +.Pp +Alternatively, if the +.Va ifbic_len +passed in is set to 0, +.Dv SIOCBRDGIFS +will set +.Va ifbic_len +to the size that +.Va ifbic_buf +needs to be to fit the entire configuration list, +and will not fill in the other parameters. +This is useful for determining the exact size that +.Va ifbic_buf +needs to be in advance. +.Pp +The argument structure is defined as follows: +.Bd -literal +struct ifbreq { + char ifbr_name[IFNAMSIZ]; /* bridge ifs name */ + char ifbr_ifsname[IFNAMSIZ];/* member ifs name */ + u_int32_t ifbr_ifsflags; /* member ifs flags */ + u_int8_t ifbr_state; /* member stp state */ + u_int8_t ifbr_priority; /* member stp priority */ + u_int32_t ifbr_portno; /* member port number */ + u_int32_t ifbr_path_cost; /* member stp path cost */ +}; + +/* ifbr_ifsflags flags about interfaces */ +#define IFBIF_LEARNING 0x0001 /* ifs can learn */ +#define IFBIF_DISCOVER 0x0002 /* sends packets w/unknown dst */ +#define IFBIF_BLOCKNONIP 0x0004 /* ifs blocks non-IP/ARP in/out */ +#define IFBIF_STP 0x0008 /* participate in spanning tree*/ +#define IFBIF_SPAN 0x0100 /* ifs is a span port (ro) */ +#define IFBIF_RO_MASK 0xff00 /* read only bits */ + +struct ifbifconf { + char ifbic_name[IFNAMSIZ]; /* bridge ifs name */ + u_int32_t ifbic_len; /* buffer size */ + union { + caddr_t ifbicu_buf; + struct ifbreq *ifbicu_req; + } ifbic_ifbicu; +#define ifbic_buf ifbic_ifbicu.ifbicu_buf +#define ifbic_req ifbic_ifbicu.ifbicu_req +}; +.Ed +.It Dv SIOCBRDGADD Fa "struct ifbreq *" +Add the interface named in +.Va ifbr_ifsname +to the bridge named in +.Va ifbr_name . +.It Dv SIOCBRDGDEL Fa "struct ifbreq *" +Delete the interface named in +.Va ifbr_ifsname +from the bridge named in +.Va ifbr_name . +.It Dv SIOCBRDGADDS Fa "struct ifbreq *" +Add the interface named in +.Va ifbr_ifsname +as a span port to the bridge named in +.Va ifbr_name . +.It Dv SIOCBRDGDELS Fa "struct ifbreq *" +Delete the interface named in +.Va ifbr_ifsname +from the list of span ports of the bridge named in +.Va ifbr_name . +.It Dv SIOCBRDGSIFFLGS Fa "struct ifbreq *" +Set the bridge member interface flags for the interface named in +.Va ifbr_ifsname +attached to the bridge +.Va ifbr_name . +If the flag +.Dv IFBIF_LEARNING +is set on an interface, source addresses from frames received on the +interface are recorded in the address cache. +If the flag +.Dv IFBIF_DISCOVER +is set, the interface will receive packets destined for unknown +destinations, otherwise a frame that has a destination not found +in the address cache is not forwarded to this interface. +The default for newly added interfaces has both flags set. +If the flag +.Dv IFBIF_BLOCKNONIP +is set, only +.Xr ip 4 , +.Xr ip6 4 , +.Xr arp 4 , +and +Reverse ARP packets will be bridged from and to the interface. +.It Dv SIOCBRDGGIFFLGS Fa "struct ifbreq *" +Retrieve the bridge member interface flags for the interface named in +.Va ifbr_ifsname +attached to the bridge +.Va ifbr_name . +.It Dv SIOCBRDGRTS Fa "struct ifbaconf *" +Retrieve the address cache of the bridge named in +.Va ifbac_name . +This request takes an +.Vt ifbaconf +structure (see below) as a value-result parameter. +The +.Va ifbac_len +field should be initially set to the size of the buffer pointed to by +.Va ifbac_buf . +On return, it will contain the length, in bytes, of the configuration list. +.Pp +Alternatively, if the +.Va ifbac_len +passed in is set to 0, +.Dv SIOCBRDGRTS +will set it to the size that +.Va ifbac_buf +needs to be to fit the entire configuration list, and will not fill in the other +parameters. +As with +.Dv SIOCBRDGIFS , +this is useful for determining the exact size that +.Va ifbac_buf +needs to be in advance. +.Pp +The argument structure is defined as follows: +.Bd -literal +struct ifbareq { + char ifba_name[IFNAMSIZ]; /* bridge name */ + char ifba_ifsname[IFNAMSIZ];/* destination ifs */ + u_int8_t ifba_age; /* address age */ + u_int8_t ifba_flags; /* address flags */ + struct ether_addr ifba_dst; /* destination addr */ +}; + +#define IFBAF_TYPEMASK 0x03 /* address type mask */ +#define IFBAF_DYNAMIC 0x00 /* dynamically learned */ +#define IFBAF_STATIC 0x01 /* static address */ + +struct ifbaconf { + char ifbac_name[IFNAMSIZ]; /* bridge ifs name */ + u_int32_t ifbac_len; /* buffer size */ + union { + caddr_t ifbacu_buf; /* buffer */ + struct ifbareq *ifbacu_req; /* request pointer */ + } ifbac_ifbacu; +#define ifbac_buf ifbac_ifbacu.ifbacu_buf +#define ifbac_req ifbac_ifbacu.ifbacu_req +}; +.Ed +.Pp +Address cache entries with the type set to +.Dv IFBAF_DYNAMIC +in +.Va ifba_flags +are entries learned by the bridge. +Entries with the type set to +.Dv IFBAF_STATIC +are manually added entries. +.It Dv SIOCBRDGSADDR Fa "struct ifbareq *" +Add an entry, manually, to the address cache for the bridge named in +.Va ifba_name . +The address and its associated interface and flags are set in the +.Va ifba_dst , +.Va ifba_ifsname , +and +.Va ifba_flags +fields, respectively. +.It Dv SIOCBRDGDADDR Fa "struct ifbareq *" +Delete an entry from the address cache of the bridge named in +.Va ifba_name . +Entries are deleted strictly based on the address field +.Va ifba_dst . +.It Dv SIOCBRDGFLUSH Fa "struct ifbreq *" +Flush addresses from the cache. +.Va ifbr_name +contains the name of the bridge device, and +.Va ifbr_ifsflags +should be set to +.Dv IFBF_FLUSHALL +to flush all addresses from the cache or +.Dv IFBF_FLUSHDYN +to flush only the dynamically learned addresses from the cache. +.It Dv SIOCBRDGSCACHE Fa "struct ifbrparam *" +Set the maximum address cache size for the bridge named in +.Va ifbrp_name +to +.Va ifbrp_csize +entries. +.Pp +The argument structure is as follows: +.Bd -literal +struct ifbrparam { + char ifbrp_name[IFNAMSIZ]; + union { + u_int32_t ifbrpu_csize; /* cache size */ + int ifbrpu_ctime; /* cache time */ + u_int16_t ifbrpu_prio; /* bridge priority */ + u_int8_t ifbrpu_hellotime; /* hello time */ + u_int8_t ifbrpu_fwddelay; /* fwd delay */ + u_int8_t ifbrpu_maxage; /* max age */ + u_int64_t ifbrpu_datapath; /* datapath-id */ + u_int32_t ifbrpu_maxgroup; /* group size */ + } ifbrp_ifbrpu; +}; +#define ifbrp_csize ifbrp_ifbrpu.ifbrpu_csize +#define ifbrp_ctime ifbrp_ifbrpu.ifbrpu_ctime +#define ifbrp_prio ifbrp_ifbrpu.ifbrpu_prio +#define ifbrp_hellotime ifbrp_ifbrpu.ifbrpu_hellotime +#define ifbrp_fwddelay ifbrp_ifbrpu.ifbrpu_fwddelay +#define ifbrp_maxage ifbrp_ifbrpu.ifbrpu_maxage +.Ed +.Pp +Note that the +.Va ifbrp_ctime , ifbrp_hellotime , ifbrp_fwddelay +and +.Va ifbrp_maxage +fields are in seconds. +.It Dv SIOCBRDGGCACHE Fa "struct ifbrparam *" +Retrieve the maximum size of the address cache for the bridge +.Va ifbrp_name . +.It Dv SIOCBRDGSTO Fa "struct ifbrparam *" +Set the time, in seconds, for how long addresses which have not been +seen on the network (i.e., have not transmitted a packet) will remain in +the cache to the value +.Va ifbrp_ctime . +If the time is set to zero, no aging is performed on the address cache. +.It Dv SIOCBRDGGTO Fa "struct ifbrparam *" +Retrieve the address cache expiration time (see above). +.It Dv SIOCBRDGARL Fa "struct ifbrlreq *" +Add an Ethernet address filtering rule to the bridge on a specific interface. +.Va ifbr_name +contains the name of the bridge device, and +.Va ifbr_ifsname +contains the name of the bridge member interface. +.Pp +Rules are applied in the order in which they were added to the bridge, +and the first matching rule's action parameter determines the fate of +the packet. +The +.Va ifbr_action +field is one of +.Dv BRL_ACTION_PASS +or +.Dv BRL_ACTION_BLOCK , +to pass or block matching frames, respectively. +The +.Va ifbr_flags +field specifies whether the rule should match on input, output, or both +by using the flags +.Dv BRL_FLAG_IN +and +.Dv BRL_FLAG_OUT . +At least one of these flags must be set. +.Pp +The +.Va ifbr_flags +field +also specifies whether either (or both) of the source and destination +addresses should be matched by using the +.Dv BRL_FLAG_SRCVALID +and +.Dv BRL_FLAG_DSTVALID +flags. +The +.Va ifbr_src +field is the source address that triggers the rule (only considered if +.Va ifbr_flags +has the +.Dv BRL_FLAG_SRCVALID +bit set). +The +.Va ifbr_src +field is the destination address that triggers the rule (only considered if +.Va ifbr_flags +has the +.Dv BRL_FLAG_DSTVALID +bit set). +If neither bit is set, the rule matches all frames. +.Pp +The argument structure is as follows: +.Bd -literal +struct ifbrlreq { + char ifbr_name[IFNAMSIZ]; /* bridge ifs name */ + char ifbr_ifsname[IFNAMSIZ]; /* member ifs name */ + u_int8_t ifbr_action; /* disposition */ + u_int8_t ifbr_flags; /* flags */ + struct ether_addr ifbr_src; /* source mac */ + struct ether_addr ifbr_dst; /* destination mac */ + char ifbr_tagname[PF_TAG_NAME_SIZE]; /* pf tagname */ +}; +#define BRL_ACTION_BLOCK 0x01 /* block frame */ +#define BRL_ACTION_PASS 0x02 /* pass frame */ +#define BRL_FLAG_IN 0x08 /* input rule */ +#define BRL_FLAG_OUT 0x04 /* output rule */ +#define BRL_FLAG_SRCVALID 0x02 /* src valid */ +#define BRL_FLAG_DSTVALID 0x01 /* dst valid */ +.Ed +.It Dv SIOCBRDGFRL Fa "struct ifbrlreq *" +Remove all filtering rules from a bridge interface member. +.Va ifbr_name +contains the name of the bridge device, and +.Va ifbr_ifsname +contains the name of the bridge member interface. +.It Dv SIOCBRDGGRL Fa "struct ifbrlconf *" +Retrieve all of the rules from the bridge, +.Va ifbrl_name , +for the member interface, +.Va ifbrl_ifsname . +This request takes an +.Vt ifbrlconf +structure (see below) as a value-result parameter. +The +.Va ifbrl_len +field should be initially set to the size of the buffer pointed to by +.Va ifbrl_buf . +On return, it will contain the length, in bytes, of the configuration list. +.Pp +Alternatively, if the +.Va ifbrl_len +passed in is set to 0, +.Dv SIOCBRDGGRL +will set it to the size that +.Va ifbrl_buf +needs to be to fit the entire configuration list, and will not fill in the other +parameters. +As with +.Dv SIOCBRDGIFS , +this is useful for determining the exact size that +.Va ifbrl_buf +needs to be in advance. +.Pp +The argument structure is defined as follows: +.Bd -literal +struct ifbrlconf { + char ifbrl_name[IFNAMSIZ]; /* bridge ifs name */ + char ifbrl_ifsname[IFNAMSIZ]; /* member ifs name */ + u_int32_t ifbrl_len; /* buffer size */ + union { + caddr_t ifbrlu_buf; + struct ifbrlreq *ifbrlu_req; + } ifbrl_ifbrlu; +#define ifbrl_buf ifbrl_ifbrlu.ifbrlu_buf +#define ifbrl_req ifbrl_ifbrlu.ifbrlu_req +}; +.Ed +.It Dv SIOCBRDGGPRI Fa "struct ifbrparam *" +Retrieve the Spanning Tree Protocol (STP) priority parameter of the bridge into +the +.Va ifbrp_prio +field. +.It Dv SIOCBRDGSPRI Fa "struct ifbrparam *" +Set the STP priority parameter of the bridge to the value in +.Va ifbrp_prio . +.It Dv SIOCBRDGGHT Fa "struct ifbrparam *" +Retrieve the STP hello time parameter, in seconds, of the bridge into the +.Va ifbrp_hellotime +field. +.It Dv SIOCBRDGSHT Fa "struct ifbrparam *" +Set the STP hello time parameter, in seconds, of the bridge to the value in +.Va ifbrp_hellotime . +The value in +.Va ifbrp_hellotime +cannot be zero. +.It Dv SIOCBRDGGFD Fa "struct ifbrparam *" +Retrieve the STP forward delay parameter, in seconds, of the bridge into the +.Va ifbrp_fwddelay +field. +.It Dv SIOCBRDGSFD Fa "struct ifbrparam *" +Set the STP forward delay parameter, in seconds, of the bridge to the value in +.Va ifbrp_fwddelay . +The value in +.Va ifbrp_fwddelay +cannot be zero. +.It Dv SIOCBRDGGMA Fa "struct ifbrparam *" +Retrieve the STP maximum age parameter, in seconds, of the bridge into the +.Va ifbrp_maxage +field. +.It Dv SIOCBRDGSMA Fa "struct ifbrparam *" +Set the STP maximum age parameter, in seconds, of the bridge to the value in +.Va ifbrp_maxage . +The value in +.Va ifbrp_maxage +cannot be zero. +.It Dv SIOCBRDGSIFPRIO Fa "struct ifbreq *" +Set the STP priority parameter of the interface named in +.Va ifbr_ifsname +to the value in +.Va ifbr_priority . +.It Dv SIOCBRDGSIFCOST Fa "struct ifbreq *" +Set the STP cost parameter of the interface named in +.Va ifbr_ifsname +to the value in +.Va ifbr_path_cost . +The value in +.Va ifbr_path_cost +must be greater than or equal to one. +.It Dv SIOCBRDGSIFPROT Fa "struct ifbreq *" +Set the protection domain membership of the interface named in +.Va ifbr_ifsname +to the value in +.Va ifbr_protected . +.El +.Sh ERRORS +If the +.Xr ioctl 2 +call fails, +.Xr errno 2 +is set to one of the following values: +.Bl -tag -width Er +.It Bq Er ENOENT +For an add request, this means that the named interface is not configured +into the system. +For a delete operation, it means that the named interface is not a member +of the bridge. +For an address cache deletion, the address was not found in the table. +.It Bq Er ENOMEM +Memory could not be allocated for an interface or cache entry +to be added to the bridge. +.It Bq Er EEXIST +The named interface is already a member of the bridge. +.It Bq Er EBUSY +The named interface is already a member of another bridge. +.It Bq Er EINVAL +The named interface is not an Ethernet interface, or an invalid ioctl +was performed on the bridge. +.It Bq Er ENETDOWN +Address cache operation (flush, add, or delete) on a bridge that is +in the down state. +.It Bq Er EPERM +Super-user privilege is required to add and delete interfaces to and from +bridges and to set the bridge interface flags. +.It Bq Er EFAULT +The buffer used in a +.Dv SIOCBRDGIFS +or +.Dv SIOCBRDGRTS +request points outside of the process's allocated address space. +.It Bq Er ESRCH +No such member interface in the bridge. +.El +.Sh NOTES +Bridged packets pass through +.Xr pf 4 +filters once as input on the receiving interface and once +as output on all interfaces on which they are forwarded. +In order to pass through the bridge, packets must pass +any +.Ar in +rules on the input and any +.Ar out +rules on the output interface. +Packets may be blocked either entering or leaving the bridge. +.Pp +Return packets generated by pf itself are not routed using the +kernel routing table. +Instead, pf will send these replies back to the same Ethernet +address that the original packet came from. +This applies to rules with +.Ic return , +.Ic return-rst , +.Ic return-icmp , +.Ic return-icmp6 , +or +.Ic synproxy +defined. +At the moment, only +.Ic return-rst +on IPv4 is implemented and the other packet generating rules +are unsupported. +.Pp +If an IP packet is too large for the outgoing interface, the bridge +will perform IP fragmentation. +This can happen when bridge members +have different MTUs or when IP fragments are reassembled by pf. +Non-IP packets which are too large for the outgoing interface will be +dropped. +.Pp +If the +.Dv IFF_LINK2 +flag is set on the +.Nm +interface, the bridge will also perform transparent +.Xr ipsec 4 +processing on the packets (encrypt or decrypt them), according to the +policies set with the +.Xr ipsecctl 8 +command by the administrator. +If appropriate security associations (SAs) do not exist, any key +management daemons such as +.Xr isakmpd 8 +that are running on the bridge will be invoked to establish the +necessary SAs. +These daemons have to be configured as if they were running on the +host whose traffic they are protecting (i.e., they need to have the +appropriate authentication and authorization material, such as keys +and certificates, to impersonate the protected host(s)). +.Sh SEE ALSO +.Xr errno 2 , +.Xr ioctl 2 , +.Xr arp 4 , +.Xr etherip 4 , +.Xr ip 4 , +.Xr ip6 4 , +.Xr ipsec 4 , +.Xr netintro 4 , +.Xr pf 4 , +.Xr tpmr 4 , +.Xr vether 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr ipsecctl 8 , +.Xr isakmpd 8 , +.Xr netstart 8 +.Sh HISTORY +The +.Nm +kernel interface first appeared in +.Ox 2.5 . +.Sh AUTHORS +The +.Nm +kernel interface was written by +.An Jason L. Wright Aq Mt jason@thought.net +as part of an undergraduate independent study at the +University of North Carolina at Greensboro. +.Pp +Support for rapid spanning tree reconfigurations (RSTP) was added by +.An Andrew Thompson Aq Mt thompsa@freebsd.org +and ported to +.Ox +by +.An Reyk Floeter Aq Mt reyk@openbsd.org . +.Sh BUGS +There are some rather special network interface chipsets which will +not work in a bridge configuration. +Some chipsets have serious flaws when running in promiscuous mode, like the +TI ThunderLAN (see +.Xr tl 4 ) , +which receives its own transmissions (this renders the address learning +cache useless). +Most other chipsets work fine though. diff --git a/static/openbsd/man4/brswphy.4 b/static/openbsd/man4/brswphy.4 new file mode 100644 index 00000000..a3cd4aa0 --- /dev/null +++ b/static/openbsd/man4/brswphy.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: brswphy.4,v 1.2 2020/04/06 00:01:08 pirofti Exp $ +.\" +.\" Copyright (c) 2014 Paul Irofti +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: April 6 2020 $ +.Dt BRSWPHY 4 +.Os +.Sh NAME +.Nm brswphy +.Nd Broadcom BCM53xx 10/100/1000TX Ethernet PHY +.Sh SYNOPSIS +.Cd "brswphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports Broadcom BCM53115 10/100/1000TX Ethernet PHY interfaces found +on some of the octeon models. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Paul Irofti Aq Mt paul@irofti.net . diff --git a/static/openbsd/man4/bse.4 b/static/openbsd/man4/bse.4 new file mode 100644 index 00000000..35267429 --- /dev/null +++ b/static/openbsd/man4/bse.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: bse.4,v 1.6 2022/03/21 14:56:16 miod Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 21 2022 $ +.Dt BSE 4 +.Os +.Sh NAME +.Nm bse +.Nd Broadcom GENET 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "bse* at acpi?" +.Cd "bse* at fdt?" +.Cd "brgphy*" at mii? +.Sh DESCRIPTION +The +.Nm +driver provides support for the Broadcom GENET controller found on the +Raspberry Pi4. +.Pp +The +.Nm +driver supports several media types, which are selected via the +.Xr ifconfig 8 +command. +The supported media types are: +.Bl -tag -width "media" -offset indent +.It Cm media No autoselect +Attempt to autoselect the media type (default) +.It Cm media No 1000baseT Cm mediaopt No full-duplex +Use 1000baseT on copper, full duplex +.It Cm media No 1000baseT Cm mediaopt No half-duplex +Use 1000baseT on copper, half duplex +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Use 100baseTX, full duplex +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Use 100baseTX, half duplex +.It Cm media No 10baseT Cm mediaopt No full-duplex +Use 10baseT, full duplex +.It Cm media No 10baseT Cm mediaopt No half-duplex +Use 10baseT, half duplex +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr brgphy 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared D. McNeill +for +.Nx +and ported to +.Ox +by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/bwfm.4 b/static/openbsd/man4/bwfm.4 new file mode 100644 index 00000000..4a2d1f00 --- /dev/null +++ b/static/openbsd/man4/bwfm.4 @@ -0,0 +1,164 @@ +.\" $OpenBSD: bwfm.4,v 1.23 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2017 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt BWFM 4 +.Os +.Sh NAME +.Nm bwfm +.Nd Broadcom and Cypress IEEE 802.11a/ac/ax/b/g/n wireless network device +.Sh SYNOPSIS +.Cd "bwfm* at pci?" +.Cd "bwfm* at sdmmc?" +.Cd "bwfm* at usb?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Broadcom and Cypress FullMAC wireless network +adapters. +.Pp +The following table summarizes supported chipsets and their capabilities, +as well as the bus attachments recognized by the +.Nm +driver: +.Bl -column BCM43236 2GHz/5GHz Type MIMO SDMMC/USB -offset 6n +.It Em Chipset Ta Em Spectrum Ta Em Type Ta Em MIMO Ta Em Bus +.It BCM43143 Ta 2GHz Ta 11n Ta 1x1 Ta SDMMC/USB +.It BCM43236 Ta 2GHz/5GHz Ta 11n Ta 2x2 Ta USB +.It BCM4324 Ta 2GHz/5GHz Ta 11n Ta 2x2 Ta SDMMC +.It BCM43242 Ta 2GHz/5GHz Ta 11n Ta 2x2 Ta USB +.It BCM4329 Ta 2GHz/5GHz Ta 11n Ta 2x2 Ta SDMMC +.It BCM4330 Ta 2GHz/5GHz Ta 11n Ta 2x2 Ta SDMMC +.It BCM4334 Ta 2GHz/5GHz Ta 11n Ta 2x2 Ta SDMMC +.It BCM43340 Ta 2GHz/5GHz Ta 11n Ta 1x1 Ta SDMMC +.It BCM43341 Ta 2GHz/5GHz Ta 11n Ta 1x1 Ta SDMMC +.It BCM4335 Ta 2GHz/5GHz Ta 11ac Ta 1x1 Ta SDMMC +.It BCM43362 Ta 2GHz Ta 11n Ta 1x1 Ta SDMMC +.It BCM43364 Ta 2GHz Ta 11n Ta 1x1 Ta SDMMC +.It BCM4339 Ta 2GHz/5GHz Ta 11ac Ta 1x1 Ta SDMMC +.It BCM43430 Ta 2GHz Ta 11n Ta 1x1 Ta SDMMC +.It BCM43455 Ta 2GHz/5GHz Ta 11ac Ta 1x1 Ta SDMMC +.It BCM43456 Ta 2GHz/5GHz Ta 11ac Ta 2x2 Ta SDMMC +.It BCM4350 Ta 2GHz/5GHz Ta 11ac Ta 2x2 Ta PCI +.It BCM4354 Ta 2GHz/5GHz Ta 11ac Ta 2x2 Ta SDMMC +.It BCM4356 Ta 2GHz/5GHz Ta 11ac Ta 2x2 Ta PCI/SDMMC +.It BCM43569 Ta 2GHz/5GHz Ta 11ac Ta 2x2 Ta USB +.It BCM43602 Ta 2GHz/5GHz Ta 11ac Ta 3x3 Ta PCI +.It BCM4371 Ta 2GHz/5GHz Ta 11ac Ta 2x2 Ta PCI +.It BCM4378 Ta 2GHz/5GHz Ta 11ax Ta 2x2 Ta PCI +.It BCM4387 Ta 2GHz/5GHz Ta 11ax Ta 2x2 Ta PCI +.El +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It Host AP +In this mode the driver acts as an access point (base station) +for other cards. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver relies on the software 802.11 stack for the WPA handshake. +Both encryption and decryption of data frames are handled by the +firmware. +.Pp +The firmware automatically selects the transmit speed and the channel +depending on the received signal strength. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs a firmware file which is loaded when the driver +attaches. +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig bwfm0 scan +.Pp +The following +.Xr hostname.if 5 +example configures bwfm0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +nwid mynwid wpakey mywpakey +inet autoconf +.Ed +.Pp +The following +.Xr hostname.if 5 +example creates a host-based access point on boot: +.Bd -literal -offset indent +mediaopt hostap +nwid mynwid wpakey mywpakey +inet 192.168.1.1 255.255.255.0 +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . +.Sh CAVEATS +The firmware is outdated and contains known vulnerabilities. diff --git a/static/openbsd/man4/bwi.4 b/static/openbsd/man4/bwi.4 new file mode 100644 index 00000000..7f49dfb7 --- /dev/null +++ b/static/openbsd/man4/bwi.4 @@ -0,0 +1,170 @@ +.\" $OpenBSD: bwi.4,v 1.49 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2007 Marcus Glocker +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt BWI 4 +.Os +.Sh NAME +.Nm bwi +.Nd Broadcom AirForce IEEE 802.11b/g wireless network device +.Sh SYNOPSIS +.Cd "bwi* at cardbus?" +.Cd "bwi* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Broadcom AirForce based +PCI/Cardbus network adapters. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver relies on the software 802.11 stack for both encryption and decryption +of data frames. +.Pp +The transmit speed is user-selectable or can be adapted automatically by the +driver depending on the received signal strength and on the number of hardware +transmission retries. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs a firmware file which is loaded when an interface is +brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/bwi-airforce +.El +.\".Pp +.\"These firmware files are not free because Broadcom refuses +.\"to grant distribution rights. +.\"As a result, even though +.\".Ox +.\"includes the driver, the firmware files cannot be included and +.\"users have to download these files on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh HARDWARE +The following cards are among those supported by the +.Nm +driver: +.Bl -column "TRENDnet TEW-401PCplus" "BCM4306" "CardBus" "Standard" -offset 6n +.It Em Card Ta Em Chip Ta Em Bus Ta Em Standard +.It "Apple Airport Extreme" Ta BCM4306 Ta PCI Ta b/g +.It "Apple Airport Extreme" Ta BCM4318 Ta PCI Ta b/g +.It "ASUS WL-138g" Ta BCM4318 Ta PCI Ta b/g +.It "Buffalo WLI-CB-G54" Ta BCM4306 Ta CardBus Ta b/g +.It "Compaq R4035 onboard" Ta BCM4306 Ta PCI Ta b/g +.It "HP nx6125" Ta BCM4319 Ta PCI Ta b/g +.It "Linksys WPC54G Ver 3" Ta BCM4318 Ta CardBus Ta b/g +.It "Linksys WPC54GS Ver 2" Ta BCM4318 Ta CardBus Ta b/g +.It "TRENDnet TEW-401PCplus" Ta BCM4306 Ta CardBus Ta b/g +.It "US Robotics 5411" Ta BCM4318 Ta CardBus Ta b/g +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig bwi0 scan +.Pp +The following +.Xr hostname.if 5 +example configures bwi0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr cardbus 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.\".Xr hostapd 8 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written for +.Dx +by +.An Sepherosa Ziehau +and ported to +.Ox +by +.An Jonathan Gray +and +.An Marcus Glocker . +.Sh CAVEATS +Some chips are incorrectly calibrated due to the lack of documentation, +which can slow the amount of traffic to the point of being unusable. +Furthermore this driver only supports firmware version 3. +.Pp +The BCM4331 chip isn't supported by this driver but the driver disables +the chip if detected, since some buggy EFI revisions found in 2011-2012 +Macs leave the chip enabled, causing it to emit spurious interrupts when +the shared interrupt line is enabled. diff --git a/static/openbsd/man4/bytgpio.4 b/static/openbsd/man4/bytgpio.4 new file mode 100644 index 00000000..0b1ccc13 --- /dev/null +++ b/static/openbsd/man4/bytgpio.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: bytgpio.4,v 1.3 2016/08/15 17:49:43 mglocker Exp $ +.\" +.\" Copyright (c) 2016 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 15 2016 $ +.Dt BYTGPIO 4 +.Os +.Sh NAME +.Nm bytgpio +.Nd Intel Bay Trail GPIO controller +.Sh SYNOPSIS +.Cd "bytgpio* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO controllers found on Intel's Bay +Trail SoC. +It does not provide direct device driver entry points but makes its +functions available to +.Xr acpi 4 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/cac.4 b/static/openbsd/man4/cac.4 new file mode 100644 index 00000000..8aea373a --- /dev/null +++ b/static/openbsd/man4/cac.4 @@ -0,0 +1,91 @@ +.\" $OpenBSD: cac.4,v 1.26 2022/03/31 17:27:20 naddy Exp $ +.\" +.\" Michael Shalayeff, 2000. Public Domain. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt CAC 4 +.Os +.Sh NAME +.Nm cac +.Nd Compaq Smart Array 2/3/4 SCSI RAID controller +.Sh SYNOPSIS +.Cd "cac* at pci?" +.Cd "cac* at eisa?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the following RAID controllers: +.Pp +.Bl -bullet -offset indent -compact +.It +Compaq Integrated Array +.It +Compaq IAES +.It +Compaq IDA +.It +Compaq IDA-2 +.It +Compaq RAID LC2 +.It +Compaq Smart Array 221 +.It +Compaq Smart Array 3100ES +.It +Compaq Smart Array 3200 +.It +Compaq Smart Array 4200 +.It +Compaq Smart Array 4250ES +.It +Compaq Smart Array 431 +.It +Compaq SMART +.It +Compaq SMART-2/E +.It +Compaq SMART-2/P +.It +Compaq SMART-2DH +.It +Compaq SMART-2SL +.El +.Pp +All the RAID set volume management is done via the card BIOS. +.Pp +Although the controllers are actual RAID controllers, the driver makes them +look just like SCSI controllers. +All RAID configuration is done through the controllers' BIOSes. +.Pp +Monitoring status for the volume and drives in it is done through the +.Xr bioctl 8 +utility; +the current status is provided by the +.Xr sysctl 8 +variable +.Va hw.sensors . +.Sh SEE ALSO +.Xr bio 4 , +.Xr eisa 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr bioctl 8 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Michael Shalayeff Aq Mt mickey@openbsd.org , +inspired by the +.Nx +driver by +.An Andrew Doran Aq Mt ad@netbsd.org . diff --git a/static/openbsd/man4/cad.4 b/static/openbsd/man4/cad.4 new file mode 100644 index 00000000..fcf84c45 --- /dev/null +++ b/static/openbsd/man4/cad.4 @@ -0,0 +1,73 @@ +.\" $OpenBSD: cad.4,v 1.4 2022/01/27 17:36:22 visa Exp $ +.\" +.\" Copyright (c) 2021 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 27 2022 $ +.Dt CAD 4 +.Os +.Sh NAME +.Nm cad +.Nd Cadence 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "cad* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the Cadence Gigabit Ethernet MAC core found on some SoCs, +including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +Microchip PolarFire SoC +.It +SiFive FU740-C000 +.It +Xilinx Zynq-7000 +.El +.Pp +The +.Nm +driver supports IPv4 receive IP/TCP/UDP checksum offload, +and IPv6 receive TCP/UDP checksum offload. +.Pp +The following media types and options are supported, +as given to +.Xr ifconfig 8 : +.Bl -tag -width autoselect -offset indent +.It media autoselect +Use auto-negotiation for speed and duplex (default). +.It media 1000baseT mediaopt full-duplex +Use 1000baseT on copper, full duplex. +.It media 100baseTX mediaopt full-duplex +Use 100baseTX on copper, full duplex. +.It media 100baseTX mediaopt half-duplex +Use 100baseTX on copper, half duplex. +.It media 10baseT mediaopt full-duplex +Use 10baseT on copper, full duplex. +.It media 10baseT mediaopt half-duplex +Use 10baseT on copper, half duplex. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 diff --git a/static/openbsd/man4/cardbus.4 b/static/openbsd/man4/cardbus.4 new file mode 100644 index 00000000..35570551 --- /dev/null +++ b/static/openbsd/man4/cardbus.4 @@ -0,0 +1,113 @@ +.\" $OpenBSD: cardbus.4,v 1.72 2021/09/08 20:29:21 jmc Exp $ +.\" $NetBSD: cardbus.4,v 1.4 2000/02/02 19:57:17 augustss Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt CARDBUS 4 +.Os +.Sh NAME +.Nm cardbus , +.Nm cbb +.Nd introduction to CardBus support +.Sh SYNOPSIS +.Cd "cbb* at pci?" +.Cd "cardslot* at cbb?" +.Cd "cardbus* at cardslot?" +.Cd "pcmcia* at cardslot?" +.Sh DESCRIPTION +.Ox +provides machine-independent bus support and drivers for CardBus devices. +.Pp +.Ox +provides support for the following devices. +Note that not all architectures support all devices. +.Ss Wired network interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr dc 4 +DEC/Intel 21140/21142/21143/21145 and clones 10/100 Ethernet device +.It Xr fxp 4 +Intel EtherExpress PRO/100 10/100 Ethernet device +.It Xr re 4 +Realtek 8139C+/8169/816xS/811xS/8168/810xE 10/100/1Gb Ethernet device +.It Xr rl 4 +Realtek 8129/8139 10/100 Ethernet device +.It Xr xl 4 +3Com EtherLink XL and Fast EtherLink XL 10/100 Ethernet device +.El +.Ss Wireless network interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr acx 4 +TI ACX100/ACX111 IEEE 802.11a/b/g wireless network device +.It Xr ath 4 +Atheros IEEE 802.11a/b/g wireless network device with GPIO +.It Xr athn 4 +Atheros IEEE 802.11a/b/g/n wireless network device +.It Xr atw 4 +ADMtek ADM8211 IEEE 802.11b wireless network device +.It Xr bwi 4 +Broadcom AirForce IEEE 802.11b/g wireless network device +.It Xr malo 4 +Marvell Libertas IEEE 802.11b/g wireless network device +.It Xr pgt 4 +Conexant/Intersil Prism GT Full-MAC IEEE 802.11a/b/g wireless network device +.It Xr ral 4 +Ralink Technology/MediaTek IEEE 802.11a/b/g/n wireless network device +.It Xr rtw 4 +Realtek RTL8180L IEEE 802.11b wireless network device +.El +.Ss Serial interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr com 4 +serial communications interface +.It Xr puc 4 +PCI +.Dq universal +communications card driver +.El +.Ss Miscellaneous devices +.Bl -tag -width 12n -offset ind -compact +.It Xr ehci 4 +USB Enhanced Host Controller Interface +.It Xr ohci 4 +USB Open Host Controller Interface +.It Xr uhci 4 +USB Universal Host Controller Interface +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr pcibios 4 , +.Xr pcmcia 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx 1.5 . +.Ox +support was added in +.Ox 2.7 . diff --git a/static/openbsd/man4/carp.4 b/static/openbsd/man4/carp.4 new file mode 100644 index 00000000..600fd1b5 --- /dev/null +++ b/static/openbsd/man4/carp.4 @@ -0,0 +1,288 @@ +.\" $OpenBSD: carp.4,v 1.42 2022/03/31 17:27:20 naddy Exp $ +.\" +.\" Copyright (c) 2003, Ryan McBride. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt CARP 4 +.Os +.Sh NAME +.Nm carp +.Nd Common Address Redundancy Protocol +.Sh SYNOPSIS +.Cd "pseudo-device carp" +.Sh DESCRIPTION +The +.Nm +interface is a pseudo-device which implements and controls the +CARP protocol. +.Nm +allows multiple hosts on the same local network to share a set of IP addresses. +Its primary purpose is to ensure that these +addresses are always available, but in some configurations +.Nm +can also provide load balancing functionality. +.Pp +A +.Nm +interface can be created at runtime using the +.Ic ifconfig carp Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +.Pp +To use +.Nm , +the administrator needs to configure at minimum +a common virtual host ID (VHID) and +virtual host IP address on each machine which is to take part in the virtual +group. +Additional parameters can also be set on a per-interface basis: +.Cm advbase +and +.Cm advskew , +which are used to control how frequently the host sends advertisements when it +is the master for a virtual host, and +.Cm pass +which is used to authenticate carp advertisements. +Finally +.Cm carpdev +is used to specify which interface the +.Nm +device attaches to. +These configurations can be done using +.Xr ifconfig 8 , +or through the +.Dv SIOCSVH +ioctl. +.Pp +.Nm +can also be used in conjunction with +.Xr ifstated 8 +to respond to changes in CARP state; +however, for most uses this will not be necessary. +See the manual page for +.Xr ifstated 8 +for more information. +.Pp +Additionally, there are a number of global parameters which can be set using +.Xr sysctl 8 : +.Bl -tag -width xxxxxxxxxxxxxxxxxxxxxxxxxx +.It net.inet.carp.allow +Accept incoming +.Nm +packets. +Enabled by default. +.It net.inet.carp.preempt +Allow virtual hosts to preempt each other. +Disabled by default. +.It net.inet.carp.log +Make +.Nm +log state changes, bad packets, and other errors. +May be a value between 0 and 7 corresponding with +.Xr syslog 3 +priorities. +The default value is 2, which limits logging to changes in CARP state. +.El +.Sh LOAD BALANCING +.Nm +uses IP balancing to load balance incoming traffic +over a group of +.Nm +hosts. +IP balancing is not dependent on ARP and therefore works +for traffic that comes over a router. +However it requires the traffic that is destined towards +the load balanced IP addresses to be received by all +.Nm +hosts. +While this is always the case when connected to a hub, +it has to play some tricks in switched networks, which +will result in a higher network load. +.Pp +To configure load balancing one has to specify multiple +carp nodes using the +.Cm carpnodes +option. +Each node in a load balancing cluster is represented +by at least one +.Qq Cm vhid : Ns Cm advskew +pair in a comma separated list. +.Nm +tries to distribute the incoming network load over all configured carpnodes. +The following example +creates a load balancing group consisting of three nodes, +using vhids 3, 4 and 6: +.Bd -literal -offset indent +# ifconfig carp0 carpnodes 3:0,4:0,6:100 +.Ed +.Pp +The advskew value of the last node is set to 100, +so that this node is designated to the BACKUP state. +It will only become MASTER if all nodes with a lower advskew value have failed. +By varying this value throughout the machines in the cluster +it is possible to decide which share of the network load each node receives. +Therefore, all carp interfaces in the cluster are configured identically, except +for a different +.Cm advskew +value within the carpnodes specification. +.Pp +IP balancing works by utilizing the network itself to distribute +incoming traffic to all +.Nm +nodes in the cluster. +Each packet is filtered on the incoming +.Nm +interface so that only one node in the cluster accepts the +packet. +All the other nodes will just silently drop it. +The filtering function uses a hash over the source and destination +address of the IPv4 or IPv6 packet and compares the result against the +state of the carpnode. +.Pp +IP balancing is activated by setting the balancing mode to +.Cm ip . +This is the recommended default setting. +In this mode, carp uses a multicast MAC address, so that a switch +sends incoming traffic towards all nodes. +.Pp +However, there are a few OS and routers that do not accept a multicast +MAC address being mapped to a unicast IP. +This can be resolved by using one of the following unicast options. +For scenarios where a hub is used it is not necessary to use a multicast MAC +and it is safe to use the +.Cm ip-unicast +mode. +Manageable switches can usually be tricked into forwarding unicast +traffic to all cluster nodes ports by configuring them into some +sort of monitoring mode. +If this is not possible, using the +.Cm ip-stealth +mode is another option, which should work on most switches. +In this mode +.Nm +never sends packets with its virtual MAC address as source. +Stealth mode prevents a switch from learning the virtual MAC +address, so that it has to flood the traffic to all its ports. +Activating stealth mode on a +.Nm +interface that has already been running might not work instantly. +As a workaround the VHID of the first carpnode can be changed to a +previously unused one, or just wait until the MAC table entry in the +switch times out. +Some layer 3 switches do port learning based on ARP packets. +Therefore the stealth mode cannot hide the virtual MAC address +from these kind of devices. +.Pp +If IP balancing is being used on a firewall, it is recommended to +configure the +.Cm carpnodes +in a symmetrical manner. +This is achieved by simply using the same +.Cm carpnodes +list on all sides of the firewall. +This ensures that packets of one connection will pass in and out +on the same host and are not routed asymmetrically. +.Sh EXAMPLES +For most scenarios it is desirable to have a well-defined master, +achieved by enabling the +.Cm preempt +option. +Enable it on both host A and B: +.Pp +.Dl # sysctl net.inet.carp.preempt=1 +.Pp +Assume that host A is the preferred master and carp should run on the physical +interfaces em0 with the network 192.168.1.0/24 and em1 with network +192.168.2.0/24. +This is the setup for host A: +.Bd -literal -offset indent +# ifconfig carp0 192.168.1.1/24 carpdev em0 vhid 1 +# ifconfig carp1 192.168.2.1/24 carpdev em1 vhid 2 +.Ed +.Pp +The setup for host B is identical, but it has a higher +.Cm advskew : +.Bd -literal -offset indent +# ifconfig carp0 192.168.1.1/24 carpdev em0 vhid 1 advskew 100 +# ifconfig carp1 192.168.2.1/24 carpdev em1 vhid 2 advskew 100 +.Ed +.Ss LOAD BALANCING +In order to set up a load balanced virtual host, it is necessary to configure +one +.Cm carpnodes +entry for each physical host. +In the following example, two physical hosts are configured to +provide balancing and failover for the IP address 192.168.1.10. +.Pp +First the +.Nm +interface on Host A is configured. +The +.Cm advskew +of 100 on the second carpnode entry means that its advertisements will be sent +out slightly less frequently and will therefore become the designated backup. +.Bd -literal -offset indent +# ifconfig carp0 192.168.1.10 carpdev em0 carpnodes 1:0,2:100 \e + balancing ip +.Ed +.Pp +The configuration for host B is identical, except the skew is on +the carpnode entry with virtual host 1 rather than virtual host 2. +.Bd -literal -offset indent +# ifconfig carp0 192.168.1.10 carpdev em0 carpnodes 1:100,2:0 \e + balancing ip +.Ed +.Pp +If a different mode of load balancing is desired, the +.Cm balancing +mode can be adjusted accordingly. +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr inet 4 , +.Xr pfsync 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr ifstated 8 , +.Xr netstart 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 3.5 . +.Sh BUGS +If load balancing is used in setups where the carpdev does not share +an IP in the same subnet as +.Nm , +it is not possible to use the IP of the +.Nm +interface for self originated traffic. +This is because the return packets are also subject to load balancing +and might end up on any other node in the cluster. +.Pp +If an IPv6 load balanced carp interface is taken down manually, +it will accept all incoming packets for its address. +This will lead to duplicated packets. diff --git a/static/openbsd/man4/cas.4 b/static/openbsd/man4/cas.4 new file mode 100644 index 00000000..bb2947cd --- /dev/null +++ b/static/openbsd/man4/cas.4 @@ -0,0 +1,105 @@ +.\" $OpenBSD: cas.4,v 1.10 2022/03/21 14:56:16 miod Exp $ +.\" +.\" Copyright (c) 2007 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 21 2022 $ +.Dt CAS 4 +.Os +.Sh NAME +.Nm cas +.Nd Sun Cassini 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "cas* at pci?" +.Cd "brgphy* at mii?" +.Cd "gentbi* at mii?" +.Cd "nsgphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various NICs based on the Sun +Cassini/Cassini+ and National Semiconductor Saturn Ethernet controller +chips, including the following: +.Pp +.Bl -bullet -compact -offset indent +.It +Sun GigaSwift Ethernet Adapter (10/100/1000baseT) +.It +Sun GigaSwift Ethernet MMF Adapter (1000baseSX) +.It +Sun Quad GigaSwift Ethernet UTP Adapter (10/100/1000baseT) +.It +Sun Quad GigaSwift PCI-X Adapter (10/100/1000baseT) +.It +Sun Dual Gigabit Ethernet and Dual SCSI/P Adapter (10/100/1000baseT) +.El +.Pp +It uses an internal or external PHY or an external 10-bit interface. +.Pp +The +.Nm +driver supports several media types, which are selected via the +.Xr ifconfig 8 +command. +The supported media types are: +.Bl -tag -width "media" -offset indent +.It Cm media No autoselect +Attempt to autoselect the media type (default) +.It Cm media No 1000baseT Cm mediaopt No full-duplex +Use 1000baseT on copper, full duplex +.It Cm media No 1000baseT Cm mediaopt No half-duplex +Use 1000baseT on copper, half duplex +.It Cm media No 1000baseSX Cm mediaopt No full-duplex +Use 1000baseSX on fiber, full duplex +.It Cm media No 1000baseSX Cm mediaopt No half-duplex +Use 1000baseSX on fiber, half duplex +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Use 100baseTX, full duplex +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Use 100baseTX, half duplex +.It Cm media No 10baseT Cm mediaopt No full-duplex +Use 10baseT, full duplex +.It Cm media No 10baseT Cm mediaopt No half-duplex +Use 10baseT, half duplex +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr brgphy 4 , +.Xr gentbi 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr nsgphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 4.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org +based on the +.Xr gem 4 +driver. +.Sh BUGS +The +.Nm +driver does not yet use many of the advanced features the Cassini chip +offers. diff --git a/static/openbsd/man4/ccp.4 b/static/openbsd/man4/ccp.4 new file mode 100644 index 00000000..3b33596d --- /dev/null +++ b/static/openbsd/man4/ccp.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: ccp.4,v 1.6 2024/09/04 11:12:53 jsg Exp $ +.\" +.\" Copyright (c) 2018 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 4 2024 $ +.Dt CCP 4 +.Os +.Sh NAME +.Nm ccp +.Nd AMD cryptographic co-processor +.Sh SYNOPSIS +.Cd "ccp* at acpi?" +.Cd "ccp* at fdt?" +.Cd "ccp* at pci?" +.Sh DESCRIPTION +AMD cryptographic co-processor devices provide offload for various +cryptographic algorithms, offload of zlib compression and decompression, +and a random number generator. +.Pp +The +.Nm +driver supports feeding output of the random number generator into +the kernel entropy pool. +.Sh SEE ALSO +.Xr intro 4 , +.Xr psp 4 , +.Xr random 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/ccpmic.4 b/static/openbsd/man4/ccpmic.4 new file mode 100644 index 00000000..b8dfaadb --- /dev/null +++ b/static/openbsd/man4/ccpmic.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: ccpmic.4,v 1.2 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt CCPMIC 4 +.Os +.Sh NAME +.Nm ccpmic +.Nd Intel Crystal Cove Power Management IC +.Sh SYNOPSIS +.Cd "ccpmic* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Dq Intel +Crystal Cove Power Management ICs. +These devices have temperature and voltage sensors and provide power +management functionality. +Sensor values are made available to +.Xr acpi 4 +to support Thermal Zones. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr acpitz 4 , +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/cd.4 b/static/openbsd/man4/cd.4 new file mode 100644 index 00000000..73a214f5 --- /dev/null +++ b/static/openbsd/man4/cd.4 @@ -0,0 +1,347 @@ +.\" $OpenBSD: cd.4,v 1.26 2024/12/21 01:00:31 jsg Exp $ +.\" $NetBSD: cd.4,v 1.3 1996/10/20 23:15:21 explorer Exp $ +.\" +.\" Copyright (c) 1996 +.\" Julian Elischer . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 21 2024 $ +.Dt CD 4 +.Os +.Sh NAME +.Nm cd +.Nd ATAPI and SCSI CD-ROM driver +.Sh SYNOPSIS +.Cd "cd* at scsibus?" +.Cd "#cd0 at scsibus0 target 6 lun 0" Pq fixed-configuration example +.Sh DESCRIPTION +The +.Nm +driver provides support for ATAPI and SCSI CD-ROM +.Pq Compact Disc Read-Only Memory +drives, via +.Xr scsibus 4 . +In an attempt to look like a regular disk, the +.Nm +driver synthesizes a partition table, with one partition covering the entire +CD-ROM. +It is possible to modify this partition table using +.Xr disklabel 8 , +but it will only last until the CD-ROM is unmounted. +In general the interfaces are similar to those described by +.Xr wd 4 +and +.Xr sd 4 . +.Pp +As the SCSI adapter is probed during boot, the SCSI bus is scanned for devices. +Any devices found which answer as +.Dq Read-only +and +.Dq removable +CD-ROM or WORM devices will be +.Dq attached +to the +.Nm +driver. +.Pp +The system utility +.Xr disklabel 8 +may be used to read the synthesized +disk label +structure, which will contain correct figures for the size of the +CD-ROM should that information be required. +.Sh IOCTLS +The following +.Xr ioctl 2 +calls which apply to CD-ROM drives are defined in the header files +.In sys/cdio.h +and +.In sys/dkio.h . +.Bl -tag -width Ds +.It Dv DIOCGDINFO , DIOCSDINFO Fa "struct disklabel *" +Read or write the in-core copy of the disklabel for the drive. +The disklabel is initialized with information read from the SCSI inquiry +commands, and should be the same as the information printed at boot. +This structure is defined in +.Xr disklabel 5 . +.\".It Dv CDIOCCAPABILITY +.\".Pq Li "struct ioc_capability" +.\"Retrieve information from the drive on what features it supports. The +.\"information is returned in the following structure: +.\".Bd -literal -offset indent +.\"struct ioc_capability { +.\" u_long play_function; +.\"#define CDDOPLAYTRK 0x00000001 +.\" /* Can play tracks/index */ +.\"#define CDDOPLAYMSF 0x00000002 +.\" /* Can play msf to msf */ +.\"#define CDDOPLAYBLOCKS 0x00000004 +.\" /* Can play range of blocks */ +.\"#define CDDOPAUSE 0x00000100 +.\" /* Output can be paused */ +.\"#define CDDORESUME 0x00000200 +.\" /* Output can be resumed */ +.\"#define CDDORESET 0x00000400 +.\" /* Drive can be completely reset */ +.\"#define CDDOSTART 0x00000800 +.\" /* Audio can be started */ +.\"#define CDDOSTOP 0x00001000 +.\" /* Audio can be stopped */ +.\"#define CDDOPITCH 0x00002000 +.\" /* Audio pitch can be changed */ +.\" +.\" u_long routing_function; +.\"#define CDREADVOLUME 0x00000001 +.\" /* Volume settings can be read */ +.\"#define CDSETVOLUME 0x00000002 +.\" /* Volume settings can be set */ +.\"#define CDSETMONO 0x00000100 +.\" /* Output can be set to mono */ +.\"#define CDSETSTEREO 0x00000200 +.\" /* Output can be set to stereo (def) */ +.\"#define CDSETLEFT 0x00000400 +.\" /* Output can be set to left only */ +.\"#define CDSETRIGHT 0x00000800 +.\" /* Output can be set to right only */ +.\"#define CDSETMUTE 0x00001000 +.\" /* Output can be muted */ +.\"#define CDSETPATCH 0x00008000 +.\" /* Direct routing control allowed */ +.\" +.\" u_long special_function; +.\"#define CDDOEJECT 0x00000001 +.\" /* The tray can be opened */ +.\"#define CDDOCLOSE 0x00000002 +.\" /* The tray can be closed */ +.\"#define CDDOLOCK 0x00000004 +.\" /* The tray can be locked */ +.\"#define CDREADHEADER 0x00000100 +.\" /* Can read Table of Contents */ +.\"#define CDREADENTRIES 0x00000200 +.\" /* Can read TOC Entries */ +.\"#define CDREADSUBQ 0x00000200 +.\" /* Can read Subchannel info */ +.\"#define CDREADRW 0x00000400 +.\" /* Can read subcodes R-W */ +.\"#define CDHASDEBUG 0x00004000 +.\" /* The tray has dynamic debugging */ +.\"}; +.\".Ed +.It Dv CDIOCPLAYTRACKS Fa "struct ioc_play_track *" +Start audio playback given a track address and length. +The structure is defined as follows: +.Bd -literal -offset indent +struct ioc_play_track { + u_char start_track; + u_char start_index; + u_char end_track; + u_char end_index; +}; +.Ed +.It Dv CDIOCPLAYBLOCKS Fa "struct ioc_play_blocks *" +Start audio playback given a block address and length. +The structure is defined as follows: +.Bd -literal -offset indent +struct ioc_play_blocks { + int blk; + int len; +}; +.Ed +.It Dv CDIOCPLAYMSF Fa "struct ioc_play_msf *" +Start audio playback given a +.Dq minutes-seconds-frames +address and length. +The structure is defined as follows: +.Bd -literal -offset indent +struct ioc_play_msf { + u_char start_m; + u_char start_s; + u_char start_f; + u_char end_m; + u_char end_s; + u_char end_f; +}; +.Ed +.It Dv CDIOCREADSUBCHANNEL Fa "struct ioc_read_subchannel *" +Read information from the subchannel at the location specified by this +structure: +.Bd -literal -offset indent +struct ioc_read_subchannel { + u_char address_format; +#define CD_LBA_FORMAT 1 +#define CD_MSF_FORMAT 2 + u_char data_format; +#define CD_SUBQ_DATA 0 +#define CD_CURRENT_POSITION 1 +#define CD_MEDIA_CATALOG 2 +#define CD_TRACK_INFO 3 + u_char track; + int data_len; + struct cd_sub_channel_info *data; +}; +.Ed +.It Dv CDIOREADTOCHEADER Fa "struct ioc_toc_header *" +Return summary information about the table of contents for the +mounted CD-ROM. +The information is returned into the following structure: +.Bd -literal -offset indent +struct ioc_toc_header { + u_short len; + u_char starting_track; + u_char ending_track; +}; +.Ed +.It Dv CDIOREADTOCENTRIES Fa "struct ioc_read_toc_entry *" +Return information from the table of contents entries mentioned. +The argument structure is defined as follows: +.Bd -literal -offset indent +struct ioc_read_toc_entry { + u_char address_format; + u_char starting_track; + u_short data_len; + struct cd_toc_entry *data; +}; +.Ed +.Pp +The requested data is written into an area of size +.Li data_len +and pointed to by +.Li data . +.It Dv CDIOCSETPATCH Fa "struct ioc_patch *" +Attach various audio channels to various output channels. +The argument structure is defined thusly: +.Bd -literal -offset indent +struct ioc_patch { + u_char patch[4]; + /* one for each channel */ +}; +.Ed +.It Dv CDIOCGETVOL , CDIOCSETVOL Fa "struct ioc_vol *" +Get (set) information about the volume settings of the output channels. +The argument structure is as follows: +.Bd -literal -offset indent +struct ioc_vol { + u_char vol[4]; + /* one for each channel */ +}; +.Ed +.It Dv CDIOCSETMONO +Patch all output channels to all source channels. +.It Dv CDIOCSETSTEREO +Patch left source channel to the left output channel and the right +source channel to the right output channel. +.It Dv CDIOCSETMUTE +Mute output without changing the volume settings. +.It Dv CDIOCSETLEFT , CDIOCSETRIGHT +Attach both output channels to the left (right) source channel. +.It Dv CDIOCSETDEBUG , CDIOCCLRDEBUG +Turn on (off) debugging for the appropriate device. +.It Dv CDIOCPAUSE , CDIOCRESUME +Pause (resume) audio play, without resetting the location of the read-head. +.It Dv CDIOCRESET +Reset the drive. +.It Dv CDIOCSTART , CDIOCSTOP +Tell the drive to spin-up (-down) the CD-ROM. +.It Dv CDIOCALLOW , CDIOCPREVENT +Tell the drive to allow (prevent) manual ejection of the CD-ROM disc. +Not all drives support this feature. +.It Dv CDIOCEJECT +Eject the CD-ROM. +.\".It Dv CDIOCCLOSE +.\"Tell the drive to close its door and load the media. Not all drives +.\"support this feature. +.\" +.\".It Dv CDIOCPITCH +.\".Pq Li "struct ioc_pitch" +.\"For drives that support it, this command instructs the drive to play +.\"the audio at a faster or slower rate than normal. Values of +.\".Li speed +.\"between -32767 and -1 result in slower playback; a zero value +.\"indicates normal speed; and values from 1 to 32767 give faster +.\"playback. Drives with less than 16 bits of resolution will silently +.\"ignore less-significant bits. The structure is defined thusly: +.\".Bd -literal -offset indent +.\"struct ioc_pitch { +.\" short speed; +.\"}; +.\".Ed +.El +.Pp +In addition the general +.Xr scsi 4 +ioctls may be used with the +.Nm +driver, if used against the `whole disk' partition (i.e., +.Pa /dev/rcd0c ) . +.Sh NOTES +When a CD-ROM is changed in a drive controlled by the +.Nm +driver, then the act of changing the media will invalidate the +disklabel and information held within the kernel. +To stop corruption, all accesses to the device will be discarded until +there are no more open file descriptors referencing the device. +During this period, all new open attempts will be rejected. +When no more open file descriptors reference the device, the first next open +will load a new set of parameters (including disklabel) for the drive. +.Pp +The audio code in the +.Nm +driver only supports SCSI-2 standard audio commands. +Because many CD-ROM manufacturers have not followed the standard, there are +many CD-ROM drives for which audio will not work. +Some work is planned to support some of the more common +.Dq broken +CD-ROM drives; however, this is not yet under way. +.Sh FILES +.Bl -tag -width /dev/rcd[0-9][a-p] -compact +.It Pa /dev/cd[0-9][a-p] +block mode CD-ROM devices +.It Pa /dev/rcd[0-9][a-p] +raw mode CD-ROM devices +.El +.Sh DIAGNOSTICS +None. +.Sh SEE ALSO +.Xr cdio 1 , +.Xr eject 1 , +.Xr ioctl 2 , +.Xr intro 4 , +.Xr scsi 4 , +.Xr scsibus 4 , +.Xr sd 4 , +.Xr wd 4 , +.Xr disklabel 5 , +.Xr disklabel 8 +.Sh HISTORY +.An Julian Elischer +wrote +.Nm +for Mach 2.5 and ported it to 386BSD. +.Sh BUGS +The names of the structures used for the third argument to +.Fn ioctl +were poorly chosen, and a number of spelling errors have survived in +the names of the +.Fn ioctl +commands. diff --git a/static/openbsd/man4/cdce.4 b/static/openbsd/man4/cdce.4 new file mode 100644 index 00000000..86f2c97a --- /dev/null +++ b/static/openbsd/man4/cdce.4 @@ -0,0 +1,151 @@ +.\" Copyright (c) 2004 Daniel Hartmeier +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" +.\" - Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" - Redistributions in binary form must reproduce the above +.\" copyright notice, this list of conditions and the following +.\" disclaimer in the documentation and/or other materials provided +.\" with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +.\" "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +.\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE +.\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER +.\" CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $OpenBSD: cdce.4,v 1.27 2022/09/10 10:10:29 jsg Exp $ +.\" +.Dd $Mdocdate: September 10 2022 $ +.Dt CDCE 4 +.Os +.Sh NAME +.Nm cdce +.Nd USB Communication Device Class Ethernet device +.Sh SYNOPSIS +.Cd "cdce* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Host-to-Host (aka USB-to-USB) bridges +based on the USB Communication Device Class (CDC) and Ethernet subclass, +including the following: +.Pp +.Bl -bullet -compact -offset indent +.It +Acer Labs USB 2.0 Data Link +.It +Dell Wireless 5530 +.It +Dell Wireless 5540 +.It +FRITZ!Box Fon ata 1020 +.It +G.Mate YP3X00 +.It +Lenovo ThinkPad USB 3.0 Ethernet adapter (FRU 03X6903) +.It +Motorola USBNET +.It +NetChip EthernetGadget +.It +Prolific PL-2501 +.It +Sony Ericsson K610i +.It +Sony Ericsson F3705g +.It +Yota LU156 +.It +ZTE MF831 LTE USB modem +.It +ZTE MF920V portable LTE WiFi router +.It +Zyxel P-971M +.El +.Pp +The USB bridge appears as a regular network interface on both sides, +transporting Ethernet frames. +USB 1.x bridges support speeds of up to 12Mbps, and USB 2.0 speeds of +up to 480Mbps. +Packets are +received and transmitted over separate USB bulk transfer endpoints. +.Pp +The +.Nm +driver does not support different media types or options. +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "cdce0: extra ethernet descriptor" +There is more than one Ethernet descriptor. +.It "cdce0: no data interface" +The data interface announced by the union descriptor cannot be found. +.It "cdce0: no descriptor for interrupt endpoint N" +.It "cdce0: interface alternate setting N failed" +.It "cdce0: no descriptor for bulk endpoint N" +.It "cdce0: could not find data bulk in/out" +For a manually added USB vendor/product, these errors indicate +that the bridge is not compatible with the driver. +.It "cdce0: watchdog timeout" +A packet was queued for transmission and a transmit command was +issued, however the device failed to acknowledge the transmission +before a timeout expired. +.It "cdce0: no memory for rx list -- packet dropped!" +Memory allocation through MGETHDR or MCLGET failed, the system +is running low on mbufs. +.It "cdce0: abort/close rx/tx/interrupt pipe failed" +.It "cdce0: rx/tx list init failed" +.It "cdce0: open rx/tx/interrupt pipe failed" +.It "cdce0: usb error on rx/tx" +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T "Universal Serial Bus Class Definitions for Communication Devices" +.%U https://www.usb.org/document-library/class-definitions-communication-devices-12 +.Re +.Rs +.%T "Data sheet Prolific PL-2501 Host-to-Host Bridge/Network Controller" +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Craig Boston Aq Mt craig@tobuj.gank.org +based on the +.Xr aue 4 +driver written by +.An Bill Paul Aq Mt wpaul@windriver.com +and ported to +.Ox +by +.An Daniel Hartmeier Aq Mt dhartmei@openbsd.org . +.Sh CAVEATS +Many USB devices notoriously fail to report their class and interfaces +correctly. +Undetected products might work flawlessly when their vendor and product IDs +are added to the driver manually. diff --git a/static/openbsd/man4/cdpcie.4 b/static/openbsd/man4/cdpcie.4 new file mode 100644 index 00000000..d04bf1f0 --- /dev/null +++ b/static/openbsd/man4/cdpcie.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: cdpcie.4,v 1.1 2025/12/07 23:05:17 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 7 2025 $ +.Dt CDPCIE 4 +.Os +.Sh NAME +.Nm cdpcie +.Nd Cadence Host/PCIe bridge +.Sh SYNOPSIS +.Cd "cdpcie* at fdt?" +.Cd "pci* at cdpcie?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Cadence PCIe controller, which is +built into various SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/cdsdhc.4 b/static/openbsd/man4/cdsdhc.4 new file mode 100644 index 00000000..9203eff4 --- /dev/null +++ b/static/openbsd/man4/cdsdhc.4 @@ -0,0 +1,40 @@ +.\" $OpenBSD: cdsdhc.4,v 1.1 2022/01/18 07:53:39 visa Exp $ +.\" +.\" Copyright (c) 2022 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 18 2022 $ +.Dt CDSDHC 4 +.Os +.Sh NAME +.Nm cdsdhc +.Nd Cadence SD/SDIO/eMMC host controller +.Sh SYNOPSIS +.Cd "cdsdhc* at fdt?" +.Cd "sdmmc* at cdsdhc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Cadence SD/SDIO/eMMC host controller, +which provides an interface to the +.Xr sdmmc 4 +bus. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sdmmc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . diff --git a/static/openbsd/man4/cduart.4 b/static/openbsd/man4/cduart.4 new file mode 100644 index 00000000..9d330d26 --- /dev/null +++ b/static/openbsd/man4/cduart.4 @@ -0,0 +1,36 @@ +.\" $OpenBSD: cduart.4,v 1.1 2021/04/24 07:49:11 visa Exp $ +.\" +.\" Copyright (c) 2021 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 24 2021 $ +.Dt CDUART 4 +.Os +.Sh NAME +.Nm cduart +.Nd Cadence Universal Asynchronous Receiver/Transmitter +.Sh SYNOPSIS +.Cd "cduart* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the Cadence Universal Asynchronous +Receiver/Transmitter (UART). +.Sh SEE ALSO +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . diff --git a/static/openbsd/man4/cfxga.4 b/static/openbsd/man4/cfxga.4 new file mode 100644 index 00000000..dc131fb0 --- /dev/null +++ b/static/openbsd/man4/cfxga.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: cfxga.4,v 1.2 2007/05/31 19:19:49 jmc Exp $ +.\" +.\" Copyright (c) 2005, Miodrag Vallat. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt CFXGA 4 +.Os +.Sh NAME +.Nm cfxga +.Nd Colorgraphic VoyagerVGA video card driver +.Sh SYNOPSIS +.Cd "cfxga* at pcmcia?" +.Cd "wsdisplay* at cfxga?" +.Sh DESCRIPTION +The Colorgraphic VoyagerVGA card is a CompactFlash removable video card. +The +.Nm +driver allows its use under +.Ox +within the +.Xr wscons 4 +console framework. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pcmcia 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh BUGS +The +.Nm +driver forces the card into a 16bpp, 640x480, 72Hz mode on the VGA output +connector. +It is not possible yet to select a different video mode, or use the S-Video +output. diff --git a/static/openbsd/man4/ch.4 b/static/openbsd/man4/ch.4 new file mode 100644 index 00000000..9cceb529 --- /dev/null +++ b/static/openbsd/man4/ch.4 @@ -0,0 +1,90 @@ +.\" $OpenBSD: ch.4,v 1.12 2011/10/06 20:17:22 sobrado Exp $ +.\" +.\" Copyright (c) 1996 +.\" Julian Elischer . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: October 6 2011 $ +.Dt CH 4 +.Os +.Sh NAME +.Nm ch +.Nd SCSI media-changer (juke box) driver +.Sh SYNOPSIS +.Cd "ch? at scsibus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for SCSI juke boxes. +It allows many slots of media to be multiplexed between a number of drives. +.Pp +A SCSI adapter and a logical scsibus must also be separately configured +into the system before a SCSI changer can be configured. +.Pp +As the SCSI adapter is probed during boot, the SCSI bus is scanned for devices. +Any devices found which answer as +.Qq Changer +type devices will be +.Dq attached +to the +.Nm +driver. +The first device found will be attached as +.Em ch0 +and the next +.Em ch1 , +etc. +It is also possible to specify what +.Nm +unit a device should come on-line as; refer to +.Xr scsi 4 +for details on kernel configuration. +.\" .Sh IOCTLS +.\" The following +.\" .Xr ioctl 2 +.\" call applies to the changer. +.\" It is defined in the header file +.\" .Aq Pa sys/chio.h . +.\" .Bl -tag -width DIOCSDINFO +.\" .It Dv CHIOOP +.\" This appears to be a +.\" .Dq do-everything +.\" call. +.\" .El +.Sh FILES +.Bl -tag -width /dev/ch[0-9] -compact +.It Pa /dev/ch[0-9] +device entries +.El +.Sh SEE ALSO +.Xr chio 1 , +.Xr cd 4 , +.Xr intro 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 +.Sh HISTORY +The +.Nm +driver appeared in 386BSD 0.1. diff --git a/static/openbsd/man4/chvgpio.4 b/static/openbsd/man4/chvgpio.4 new file mode 100644 index 00000000..ef0caecc --- /dev/null +++ b/static/openbsd/man4/chvgpio.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: chvgpio.4,v 1.2 2016/05/08 06:11:40 jmc Exp $ +.\" +.\" Copyright (c) 2016 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 8 2016 $ +.Dt CHVGPIO 4 +.Os +.Sh NAME +.Nm chvgpio +.Nd Intel Cherry View GPIO controller +.Sh SYNOPSIS +.Cd "chvgpio* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO controllers found on Intel's +Cherry View SoC. +It does not provide direct device driver entry points but makes its +functions available to +.Xr acpi 4 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/ciphy.4 b/static/openbsd/man4/ciphy.4 new file mode 100644 index 00000000..2f5fe847 --- /dev/null +++ b/static/openbsd/man4/ciphy.4 @@ -0,0 +1,34 @@ +.\" $OpenBSD: ciphy.4,v 1.10 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2004 Peter Valchev +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt CIPHY 4 +.Os +.Sh NAME +.Nm ciphy +.Nd Cicada/Vitesse CS82xx/VSC8211/VSC8601 10/100/1Gb Ethernet PHY +.Sh SYNOPSIS +.Cd "ciphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Cicada CS8201/CS8204/VSC8211/CS8244 and Vitesse VSC8601 +10/100/1Gb copper PHY. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/ciss.4 b/static/openbsd/man4/ciss.4 new file mode 100644 index 00000000..18ef7895 --- /dev/null +++ b/static/openbsd/man4/ciss.4 @@ -0,0 +1,68 @@ +.\" $OpenBSD: ciss.4,v 1.19 2017/07/21 12:28:15 mikeb Exp $ +.\" +.\" Michael Shalayeff, 2005. Public Domain. +.\" +.Dd $Mdocdate: July 21 2017 $ +.Dt CISS 4 +.Os +.Sh NAME +.Nm ciss +.Nd Compaq Smart Array SAS/SATA/SCSI RAID controller +.Sh SYNOPSIS +.Cd "ciss* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Compaq Smart Array SAS/SATA/SCSI +RAID controllers, including: +.Pp +.Bl -bullet -offset indent -compact +.It +Compaq 532, 5300, 5312, 5i +.It +Compaq 641, 642, 6400, 6400EM, 6422 +.It +Hewlett-Packard 6i, E200, E200i, E500, H240, H240ar, H240tr, H241, H244br, +P212, P220i, P222, P224br, P230i, P240tr, P246br, P400, P400i, P410, P410i, +P411, P420, P420i, P421, P430, P430i, P431, P440, P440ar, P441, P530, P531, +P542t, P600, P700m, P711m, P712m, P721m, P731m, P741m, P800, P812, P822, P830, +P830i, P840, P841, V100 +.El +.Pp +These controllers support RAID 0, RAID 1, RAID 5, JBOD, +and superpositions of those configurations. +.Pp +Although the controllers are actual RAID controllers, +the driver makes them look just like SCSI controllers. +All RAID configuration is done through the controllers' BIOSes. +.Pp +Monitoring status for the volume and drives in it is done through the +.Xr bioctl 8 +utility; +the current status is provided by the +.Xr sysctl 8 +variable +.Va hw.sensors . +.Sh SEE ALSO +.Xr bio 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr bioctl 8 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Michael Shalayeff Aq Mt mickey@openbsd.org . +.Sh CAVEATS +For purposes of status monitoring, +the current code only supports one logical +volume per controller. diff --git a/static/openbsd/man4/clcs.4 b/static/openbsd/man4/clcs.4 new file mode 100644 index 00000000..698e5a34 --- /dev/null +++ b/static/openbsd/man4/clcs.4 @@ -0,0 +1,61 @@ +.\" $OpenBSD: clcs.4,v 1.9 2008/06/26 05:42:06 ray Exp $ +.\" $NetBSD: clcs.4,v 1.1 1999/12/11 23:10:15 augustss Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt CLCS 4 +.Os +.Sh NAME +.Nm clcs +.Nd Cirrus Logic CS4280/CS4610/CS4615 audio device +.Sh SYNOPSIS +.Cd "clcs* at pci?" +.Cd "audio* at clcs?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Cirrus Logic CS4280 chip, as well as +for CS461x. +.Sh FILES +The driver needs a firmware file, +which is loaded on demand when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/cs4280 +.El +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.8 . diff --git a/static/openbsd/man4/clct.4 b/static/openbsd/man4/clct.4 new file mode 100644 index 00000000..7640397d --- /dev/null +++ b/static/openbsd/man4/clct.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: clct.4,v 1.7 2008/06/26 05:42:06 ray Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Tatoku Ogaito +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt CLCT 4 +.Os +.Sh NAME +.Nm clct +.Nd Cirrus Logic CS4281 audio device +.Sh SYNOPSIS +.Cd "clct* at pci?" +.Cd "audio* at clct?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Cirrus Logic CS4281 chip. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.9 . diff --git a/static/openbsd/man4/cmpci.4 b/static/openbsd/man4/cmpci.4 new file mode 100644 index 00000000..bae365fa --- /dev/null +++ b/static/openbsd/man4/cmpci.4 @@ -0,0 +1,70 @@ +.\" $OpenBSD: cmpci.4,v 1.16 2010/07/31 08:33:20 ratchov Exp $ +.\" +.\" Copyright (c) 2000 Takuya SHIOZAKI +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 31 2010 $ +.Dt CMPCI 4 +.Os +.Sh NAME +.Nm cmpci +.Nd C-Media CMI8338/CMI8738/CMI8768 PCI audio device +.Sh SYNOPSIS +.Cd "cmpci* at pci?" +.Cd "audio* at cmpci?" +.Sh DESCRIPTION +The +.Nm +driver supports the C-Media CMI8338A, CMI8338B, CMI8738, CMI8738B +and CMI8768 sound chips present in some PCI sound cards and some +integrated PC motherboard chipsets (such as the SiS 530). +.Pp +Hardware features: +.Bl -bullet -offset indent +.It +Supports 8 common sample rates from 5512 Hz to 48000 Hz +.It +Hardware full-duplex support enables simultaneous record and playback +.It +Some CMI8738 versions support 4 and 6 channel playback +.It +CMI8768 chips support 4, 6, and 8 channel playback +.It +CMI8768 chips can only record sample rates of 44100 Hz or 48000 Hz +.It +Hardware copying of front to rear for playing stereo input on 4 speakers +.It +S/PDIF input and output +.El +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.7 . +.Sh BUGS +The Joystick port is not supported. diff --git a/static/openbsd/man4/com.4 b/static/openbsd/man4/com.4 new file mode 100644 index 00000000..ea5ec937 --- /dev/null +++ b/static/openbsd/man4/com.4 @@ -0,0 +1,165 @@ +.\" $OpenBSD: com.4,v 1.49 2021/12/16 08:03:17 anton Exp $ +.\" $NetBSD: com.4,v 1.5 1996/03/16 00:07:08 thorpej Exp $ +.\" +.\" Copyright (c) 1990, 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)dca.4 5.2 (Berkeley) 3/27/91 +.\" +.Dd $Mdocdate: December 16 2021 $ +.Dt COM 4 +.Os +.Sh NAME +.Nm com +.Nd serial communications interface +.Sh SYNOPSIS +.Cd "# com attachments" +.Cd "#" +.Cd "# i386" +.Cd "com0 at isa? port 0x3f8 irq 4" +.Cd "com1 at isa? port 0x2f8 irq 3" +.Cd "com2 at isa? port 0x3e8 irq 5" +.Cd "com3 at isa? port 0x2e8 irq 9" +.Cd "com* at isapnp?" +.Cd "com* at pcmcia?" +.Cd "com* at puc?" +.Cd "com* at cardbus?" +.Pp +.Cd "com* at addcom?" +.Cd "com* at ast?" +.Cd "com* at boca?" +.Cd "com* at hsq?" +.Pp +.Cd "# alpha and amd64" +.Cd "com0 at isa? port 0x3f8 irq 4" +.Cd "com1 at isa? port 0x2f8 irq 3" +.Pp +.Cd "# amd64 and arm64" +.Cd "com* at acpi?" +.Pp +.Cd "# arm64 and armv7" +.Cd "com* at fdt?" +.Pp +.Cd "# hppa" +.Cd "com0 at gsc? offset 0x5000 irq 5" +.Cd "com0 at gsc? offset 0x823000 irq 5" +.Cd "com1 at gsc? offset 0x822000 irq 6" +.Cd "com2 at gsc? irq 13" +.Cd "com1 at dino? irq 11" +.Cd "com0 at ssio? irq 4" +.Cd "com1 at ssio? irq 3" +.Pp +.Cd "# loongson" +.Cd "com* at leioc?" +.Pp +.Cd "# macppc" +.Cd "com* at puc?" +.Cd "com* at pcmcia?" +.Cd "com* at cardbus?" +.Pp +.Cd "# octeon" +.Cd "com* at fdt?" +.Pp +.Cd "# riscv64" +.Cd "com* at fdt?" +.Pp +.Cd "# sparc64" +.Cd "com* at asio?" +.Cd "com* at ebus?" +.Cd "com* at puc?" +.Sh DESCRIPTION +The +.Nm com +driver provides support for NS8250-, NS16450-, NS16550-, ST16650-, +ST16C654-, and TI16750-based +.\" XR16850- +.Tn EIA +.Tn RS-232C +.Pf ( Tn CCITT +.Tn V.28 ) +communications interfaces. +.Pp +The NS8250 and NS16450 have single +character buffers, the NS16550 has a 16 character buffer, while +the ST16650 has a 32 character buffer, and the TI16750 has a 64 character +buffer. +.\" The XR16850 has a 128 character buffer. +.Pp +Input and output for each line may be set to one of following baud rates; +50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600, +19200, 38400, 57600, or 115200, or any other baud rate which is a factor +of 115200. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/tty00 +.It Pa /dev/tty01 +.It Pa /dev/cua00 +.It Pa /dev/cua01 +.El +.Sh DIAGNOSTICS +.Bl -diag +.It com0: N silo overflows +The input +.Dq silo +has overflowed and incoming data has been lost. +.It com0: weird interrupt: iir=XXXX +The device has generated an unexpected interrupt +with the code listed. +.El +.Sh SEE ALSO +.Xr addcom 4 , +.Xr asio 4 , +.Xr ast 4 , +.Xr boca 4 , +.Xr cardbus 4 , +.Xr dino 4 , +.Xr ebus 4 , +.Xr gsc 4 , +.Xr hsq 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr isapnp 4 , +.Xr pcmcia 4 , +.Xr puc 4 , +.Xr ssio 4 , +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver was originally derived from the +.Nm HP9000/300 +.Nm dca +driver. +.Sh BUGS +Data loss is possible on busy systems with unbuffered UARTs at high speed. +.Pp +The name of this driver and the constants which define the locations +of the various serial ports are holdovers from +.Nm DOS . diff --git a/static/openbsd/man4/cue.4 b/static/openbsd/man4/cue.4 new file mode 100644 index 00000000..104f3bf9 --- /dev/null +++ b/static/openbsd/man4/cue.4 @@ -0,0 +1,102 @@ +.\" $OpenBSD: cue.4,v 1.15 2013/07/16 16:05:48 schwarze Exp $ +.\" $NetBSD: cue.4,v 1.2 2000/01/16 13:54:39 augustss Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999, 2000 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/cue.4,v 1.1 2000/01/14 03:14:47 wpaul Exp $ +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt CUE 4 +.Os +.Sh NAME +.Nm cue +.Nd CATC USB-EL1201A USB Ethernet device +.Sh SYNOPSIS +.Cd "cue* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Ethernet adapters based on the Computer +Access Technology Corporation's USB-EL1202A chipset. +This includes the following adapters: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Tn Belkin F5U111 +.It Tn CATC Netmate +.It Tn CATC Netmate II +.It Tn SmartBridges SmartLink +.El +.Pp +The USB-EL1202A supports a 512-bit multicast hash filter, single perfect +filter entry for the station address and promiscuous mode. +Packets are +received and transmitted over separate USB bulk transfer endpoints. +.Pp +The CATC adapter supports only 10Mbps half-duplex mode, hence there are no +.Xr ifmedia 4 +modes to select. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "cue0: watchdog timeout" +A packet was queued for transmission and a transmit command was +issued, however the device failed to acknowledge the transmission +before a timeout expired. +.It "cue0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 4.0 . +.Ox +support was added in +.Ox 2.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ee.columbia.edu +and ported to +.Ox +by +.An Aaron Campbell Aq Mt aaron@openbsd.org . diff --git a/static/openbsd/man4/cwfg.4 b/static/openbsd/man4/cwfg.4 new file mode 100644 index 00000000..77b48ba6 --- /dev/null +++ b/static/openbsd/man4/cwfg.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: cwfg.4,v 1.1 2020/06/10 17:58:57 patrick Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 10 2020 $ +.Dt CWFG 4 +.Os +.Sh NAME +.Nm cwfg +.Nd CellWise CW201x fuel gauge +.Sh SYNOPSIS +.Cd "cwfg* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the CellWise CW201x fuel gauge. +It reads the current battery voltage, capacity and remaining minutes and +provides the information to the user via the sensors framework. +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared McNeill Aq Mt jmcneill@invisible.ca +for +.Nx +and ported to +.Ox +by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/cy.4 b/static/openbsd/man4/cy.4 new file mode 100644 index 00000000..d2c001a2 --- /dev/null +++ b/static/openbsd/man4/cy.4 @@ -0,0 +1,93 @@ +.\" $OpenBSD: cy.4,v 1.17 2020/07/23 22:33:29 jan Exp $ +.\" +.\" Copyright (c) 1993 Andrew Herbert. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name Andrew Herbert may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 23 2020 $ +.Dt CY 4 +.Os +.Sh NAME +.Nm cy +.Nd Cyclades Cyclom-{4, 8, 16}Y asynchronous comms board device driver +.Sh SYNOPSIS +.Cd "cy0 at isa? iomem 0xd4000 irq 12" +.Cd "cy* at pci?" +.Sh DESCRIPTION +This driver provides an interface to Cyclades Cyclom-4Y, Cyclom-8Y and +Cyclom-16Y asynchronous multiport serial boards. +These boards are based around Cirrus Logic CD1400 communication controllers. +.Pp +The device minor numbers for this driver are encoded as follows: +.Bd -literal + d c c u u u u u - bits in the minor device number + + bits meaning + ---- ------- + uuuuu physical serial line (i.e., unit) to use + 0-7 on a cyclom-8Y, 0-15 on a cyclom-16Y + + cc card number + + d dial-out flag +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "cy0: port 0 ibuf overrun" +Incoming characters have been discarded due to a buffer overflow. +.It "cy0: port 0 fifo overrun" +Incoming characters have been discarded due to a CD1400 channel overrun. +This is caused by interrupts not being serviced sufficiently quickly to prevent +the 12 byte receive FIFO on a serial channel from overflowing. +Reducing the value of the +.Dv RX_FIFO_THRESHOLD +#define from 6 to something smaller may help slow machines avoid this problem. +.El +.Sh SEE ALSO +.Xr com 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 , +.Xr termios 4 , +.Xr tty 4 +.Sh HISTORY +Some ideas for the architecture of this driver's two-layer processing model +were derived from the fas 2.10 driver by +.An Uwe Doering Aq Mt gemini@geminix.in-berlin.de +and the high-performance com driver by +.An Bruce Evans Aq Mt bde@kralizec.zeta.org.au . +.Pp +This work was made possible through the donation of a Cyclom-8Y board by the +manufacturer, Cyclades Corporation. +However, neither Cyclades nor the author make any warranties regarding +this software, nor guarantees of support. +.Sh AUTHORS +The driver was written by +.An Andrew Herbert Aq Mt andrew@werple.apana.org.au . +.Sh BUGS +There is currently no BREAK handling - breaks are ignored. +There is no support for bad-character reporting, except via PARMRK. +The Cyclom-[48]Y boards do not listen to the RTS signal for receiver flow +control. +FIFO overruns are only logged when the termios IGNPAR setting is enabled. diff --git a/static/openbsd/man4/cz.4 b/static/openbsd/man4/cz.4 new file mode 100644 index 00000000..e2029f7b --- /dev/null +++ b/static/openbsd/man4/cz.4 @@ -0,0 +1,134 @@ +.\" $OpenBSD: cz.4,v 1.13 2018/03/16 16:58:26 schwarze Exp $ +.\" $NetBSD: cz.4,v 1.3 2001/06/12 14:46:11 wiz Exp $ +.\" +.\" Copyright (c) 2000 Zembu Labs, Inc. +.\" All rights reserved. +.\" +.\" Author: Jason R. Thorpe +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Zembu Labs, Inc. +.\" 4. Neither the name of Zembu Labs nor the names of its employees may +.\" be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY ZEMBU LABS, INC. ``AS IS'' AND ANY EXPRESS +.\" OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WAR- +.\" RANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DIS- +.\" CLAIMED. IN NO EVENT SHALL ZEMBU LABS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 16 2018 $ +.Dt CZ 4 +.Os +.Sh NAME +.Nm cz +.Nd Cyclades-Z series multi-port serial adapter device +.Sh SYNOPSIS +.Cd "cz* at pci?" +.Sh DESCRIPTION +The +.Nm +device driver supports the Cyclades-Z series of multi-port serial adapters. +The Cyclades-Z is an intelligent serial controller comprising: +.Bl -bullet -offset indent +.It +PLX9060ES PCI bus interface +.It +Xilinx XC5204 FPGA +.It +IDT R3052 MIPS CPU +.El +.Pp +The MIPS CPU runs firmware provided by the device driver. +Communication with the MIPS is performed by modifying data structures located +in board local RAM or host RAM. +.Pp +The Cyclades-Z comes in three basic flavors: +.Bl -bullet -offset indent +.It +Cyclades-8Zo rev. 1 \(em This is an older 8-port board with no FPGA. +The serial ports are provided by an octopus cable. +.It +Cyclades-8Zo rev. 2 \(em This is the newer 8-port board. +The serial ports are provided by an octopus cable. +.It +Cyclades-Ze \(em This is the expandable version of the Cyclades-Z. +It uses an HD-50 SCSI cable to connect the board to a 1U rack mountable serial +expansion box. +Each box has 16 RJ45 serial ports, and up to 4 boxes may be chained together, +for a total of 64 ports. +Boxes 3 and 4 require their own external power supply, otherwise the firmware +will refuse to start (as it cannot communicate with the UARTs in those boxes). +.El +.Pp +The Cyclades-Z has several features to improve performance under +high serial I/O load: +.Bl -bullet -offset indent +.It +The board may operate in interrupt-driven mode or polled mode to reduce +interrupt load. +.It +Each channel has a large input and output buffer. +.It +Each channel may be programmed to generate an interrupt based on +reception of a specific character, e.g. a PPP End-Of-Frame character. +.It +The MIPS CPU on the board performs all flow-control handling. +.El +.Sh FILES +.Bl -tag -width XXXXXXXXXXX -compact +.It Pa /dev/ttyZ?? +dial-in (normal) TTY device +.It Pa /dev/cuaZ?? +dial-out TTY device +.El +.\" .Sh DIAGNOSTICS +.\" XXX to be done. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr termios 4 , +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jason R. Thorpe Aq Mt thorpej@zembu.com +and +.An Bill Studenmund Aq Mt wrstuden@zembu.com +of Zembu Labs, Inc. +.Sh BUGS +The +.Nm +driver does not currently implement communication via host RAM. +While this may improve performance by reducing the number of PCI memory +space read/write cycles, it is not straightforward to implement with +the current +.Xr bus_dma 9 +API. +.Pp +Interrupt mode has not been tested. +.Pp +There is no support for reading or writing the EEPROM connected to +the PLX PCI bus controller. diff --git a/static/openbsd/man4/dapmic.4 b/static/openbsd/man4/dapmic.4 new file mode 100644 index 00000000..338fb65e --- /dev/null +++ b/static/openbsd/man4/dapmic.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: dapmic.4,v 1.1 2021/06/16 13:56:46 kettenis Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 16 2021 $ +.Dt DAPMIC 4 +.Os +.Sh NAME +.Nm dapmic +.Nd Dialog DA9063 Power Management IC +.Sh SYNOPSIS +.Cd "dapmic* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the real-time clock in the Dialog DA9063 +Power Management IC. +It also provides a way to reset or shutdown some machines that do not +implement this functionality in their firmware. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/dc.4 b/static/openbsd/man4/dc.4 new file mode 100644 index 00000000..fed1cf06 --- /dev/null +++ b/static/openbsd/man4/dc.4 @@ -0,0 +1,393 @@ +.\" $OpenBSD: dc.4,v 1.54 2022/02/18 10:24:32 jsg Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/dc.4,v 1.1 1999/12/04 17:41:24 wpaul Exp $ +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt DC 4 +.Os +.Sh NAME +.Nm dc +.Nd DEC/Intel 21140/21142/21143/21145 and clones 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "dc* at pci?" +.Cd "dc* at cardbus?" +.Cd "amphy* at mii?" +.Cd "bmtphy* at mii?" +.Cd "dcphy* at mii?" +.Cd "icsphy* at mii?" +.Cd "lxtphy* at mii?" +.Cd "mtdphy* at mii?" +.Cd "nsphy* at mii?" +.Cd "nsphyter* at mii?" +.Cd "sqphy* at mii?" +.Cd "tqphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for several PCI, Mini PCI, and CardBus Fast Ethernet +adapters and embedded controllers based on the following chipsets: +.Pp +.Bl -bullet -compact -offset indent +.It +DEC 21140 PCI +.It +DEC/Intel 21143 PCI and CardBus +.It +Intel 21145 PCI +.It +Macronix 98713, 98713A, 98715, 98715A, 98725, 98727 and 98732 +.It +Davicom DM9100, DM9102, and DM9102A +.It +ASIX Electronics AX88140A and AX88141 +.It +ADMtek AL981 Comet, AN983 Centaur-P and ADM9511/ADM9513 Centaur-II PCI +.It +ADMtek AN985 Centaur-C CardBus +.It +Lite-On 82c168 and 82c169 PNIC +.It +Lite-On/Macronix 82c115 PNIC II +.It +Xircom X3201-based CardBus +.El +.Pp +All of these chips have the same general register layout, DMA +descriptor format and method of operation. +All of the clone chips are based on the 21143 design with +various modifications. +(The 21140 is an older version of the 21143.) +The 21143 itself has support for 10baseT, BNC, AUI, MII and symbol +media attachments, 10 and 100Mbps speeds in full or half duplex, +and built-in NWAY autonegotiation. +The 21143 also offers several receive filter programming options including +perfect filtering, inverse perfect filtering and hash table filtering. +The 21145 seems to be 10Mbps only and has an additional (unsupported) +HomePNA PHY. +.Pp +Some clone chips duplicate the 21143 fairly closely while others +only maintain superficial similarities. +Some support only MII media attachments. +Others use different receiver filter programming mechanisms. +At least one supports only chained DMA descriptors +(most support both chained descriptors and contiguously allocated +fixed size rings). +Some chips (especially the PNIC) also have peculiar bugs. +The +.Nm +driver does its best to provide generalized support for all +of these chipsets in order to keep special case code to a minimum. +.Pp +These chips are used by many vendors, which makes it +difficult to provide a complete list of all supported cards. +The following NICs are known to work with the +.Nm +driver at this time: +.Pp +.Bl -bullet -compact -offset indent +.It +Digital DE500-BA 10/100 (21143, non-MII) +.It +Built-in DE500-BA on DEC Alpha workstations (21143, non-MII) +.It +Built-in Ethernet on Linksys EtherFast 10/100 Instant GigaDrive (DM9102, MII) +.It +Kingston KNE100TX (21143, MII) +.It +D-Link DFE-570TX (21143, MII, quad port) +.It +NDC SOHOware SFA110A (98713A) +.It +NDC SOHOware SFA110A Rev B4 (98715AEC-C) +.It +SVEC PN102-TX (98713) +.It +CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715) +.It +Compex RL100-TX (98713 or 98713A) +.It +Linksys LNE100TX (PNIC 82c168, 82c169) +.It +NetGear FA310-TX Rev. D1, D2 or D3 (PNIC 82c169) +.It +Matrox FastNIC 10/100 (PNIC 82c168, 82c169) +.It +Kingston KNE110TX (PNIC 82c169) +.It +Linksys LNE100TX v2.0 (PNIC II 82c115) +.It +Jaton XpressNet (Davicom DM9102) +.It +Alfa Inc GFC2204 (ASIX AX88140A) +.It +CNet Pro110B (ASIX AX88140A) +.It +Linksys LNE100TX v4.x (ADMtek AN983 Centaur-P) +.It +Xircom CardBus, including RealPort models (Xircom X3201) +.It +IBM EtherJet 10/100 CardBus (Intel 21143) +.It +Accton EN1217 (98715) and EN2242 (ADMtek Centaur) +.It +Mototech ME316 (ADMtek Centaur) +.It +Conexant LANfinity RS7112 Mini PCI +.El +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the +.Xr hostname.if 5 +file. +.Pp +Note: the built-in NWAY autonegotiation on the original PNIC 82c168 +chip is horribly broken and is not supported by the +.Nm +driver at this time: the chip will operate in any speed or duplex +mode, however these must be set manually. +The original 82c168 appears on very early revisions of the Linksys LNE100TX +and Matrox FastNIC. +.It 10baseT +Set 10Mbps operation. +The +.Ar mediaopt +option can also be used to enable +.Ar full-duplex +operation. +Not specifying +.Ar full duplex +implies +.Ar half-duplex +mode. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Ar mediaopt +option can also be used to enable +.Ar full-duplex +operation. +Not specifying +.Ar full duplex +implies +.Ar half-duplex +mode. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation. +The interface will operate in half duplex mode if this media option +is not specified. +.El +.Pp +Note that the 100baseTX media type may not be available on certain +Intel 21143 adapters which support 10Mbps media attachments only. +The Intel 21145 supports 10Mbps half-duplex only. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "dc0: couldn't map ports/memory" +A fatal initialization error has occurred. +.It "dc0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "dc0: watchdog timeout" +A packet was queued for transmission and a transmit command was +issued, however the device failed to acknowledge the transmission +before a timeout expired. +This can happen if the device is unable to deliver interrupts for some +reason, or if there is a problem with the network connection (cable). +.It "dc0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.It "dc0: TX underrun -- increasing TX threshold" +The device generated a transmit underrun error while attempting to +DMA and transmit a packet. +This happens if the host is not able to DMA the packet data into the NIC's +FIFO fast enough. +The driver will dynamically increase the transmit start threshold so that +more data must be DMAed into the FIFO before the NIC will start +transmitting it onto the wire. +.It "dc0: TX underrun -- using store and forward mode" +The device continued to generate transmit underruns even after all +possible transmit start threshold settings had been tried, so the +driver programmed the chip for store and forward mode. +In this mode, the NIC will not begin transmission until the entire packet +has been transferred into its FIFO memory. +.El +.Sh SEE ALSO +.Xr amphy 4 , +.Xr arp 4 , +.Xr bmtphy 4 , +.Xr cardbus 4 , +.Xr dcphy 4 , +.Xr icsphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr lxtphy 4 , +.Xr mtdphy 4 , +.Xr netintro 4 , +.Xr nsphy 4 , +.Xr nsphyter 4 , +.Xr pci 4 , +.Xr sqphy 4 , +.Xr tqphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T ADMtek AL981 and AL983 data sheets +.Re +.Rs +.%T ASIX Electronics AX88140A and AX88141 data sheets +.%U https://www.asix.com.tw +.Re +.Rs +.%T Davicom DM9102 data sheet +.Re +.Rs +.%T Intel 21143 Hardware Reference Manual +.%U http://developer.intel.com +.Re +.Rs +.%T Macronix 98713/A, 98715/A and 98725 data sheets +.%U https://www.macronix.com +.Re +.Rs +.%T Macronix 98713/A and 98715/A app notes +.%U https://www.macronix.com +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 4.0 . +.Ox +support was added in +.Ox 2.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ee.columbia.edu +and ported to +.Ox +by +.An Aaron Campbell Aq Mt aaron@openbsd.org . +.Sh BUGS +The Macronix application notes claim that in order to put the +chips in normal operation, the driver must write a certain magic +number into the CSR16 register. +The numbers are documented in the app notes, but the exact meaning of the +bits is not. +.Pp +The 98713A seems to have a problem with 10Mbps full duplex mode. +The transmitter works but the receiver tends to produce many +unexplained errors leading to very poor overall performance. +The 98715A does not exhibit this problem. +All other modes on the 98713A seem to work correctly. +.Pp +The original 82c168 PNIC chip has built-in NWAY support which is +used on certain early Linksys LNE100TX and Matrox FastNIC cards, +however it is horribly broken and difficult to use reliably. +Consequently, autonegotiation is not currently supported for this +chipset: the driver defaults the NIC to 10baseT half duplex, and it's +up to the operator to manually select a different mode if necessary. +(Later cards use an external MII transceiver to implement NWAY +autonegotiation and work correctly.) +.Pp +The +.Nm +driver programs 82c168 and 82c169 PNIC chips to use the store and +forward setting for the transmit start threshold by default. +This is to work around problems with some NIC/PCI bus combinations where +the PNIC can transmit corrupt frames when operating at 100Mbps, +probably due to PCI DMA burst transfer errors. +.Pp +The 82c168 and 82c169 PNIC chips also have a receiver bug that +sometimes manifests during periods of heavy receive and transmit +activity, where the chip will improperly DMA received frames to +the host. +The chips appear to upload several kilobytes of garbage +data along with the received frame data, dirtying several RX buffers +instead of just the expected one. +The +.Nm +driver detects this condition and will salvage the frame, however +it incurs a serious performance penalty in the process. +.Pp +The PNIC chips also sometimes generate a transmit underrun error when +the driver attempts to download the receiver filter setup frame, which +can result in the receive filter being incorrectly programmed. +The +.Nm +driver will watch for this condition and requeue the setup frame until +it is transferred successfully. +.Pp +The ADMtek AL981 chip (and possibly the AN983 as well) has been observed +to sometimes wedge on transmit: this appears to happen when the driver +queues a sequence of frames which cause it to wrap from the end of +the transmit descriptor ring back to the beginning. +The +.Nm +driver attempts to avoid this condition by not queuing any frames past +the end of the transmit ring during a single invocation of the +.Fn dc_start +routine. +This workaround has a negligible impact on transmit performance. +.Pp +The +.Fn mii_tick +function does not currently run for ASIX boards, meaning cable disconnects +and reconnects can go unnoticed. +The AX88140A and AX88141 data sheets indicate that they don't have RX or TX +state registers (the bits are reserved). +Therefore, we can't seem to reliably detect when the adapter is idle. +.Pp +The Davicom interfaces require a grossly high PCI latency timer value to +function properly. +This means when a Davicom adapter is present in the machine, it is given +an unfairly high amount of bandwidth on the PCI bus, unnecessarily taking +time away from other devices. +Therefore, Davicom network cards are not recommended for use with +.Ox . +Be careful; some motherboards have Davicom interfaces built-in. diff --git a/static/openbsd/man4/dcphy.4 b/static/openbsd/man4/dcphy.4 new file mode 100644 index 00000000..8c4f1829 --- /dev/null +++ b/static/openbsd/man4/dcphy.4 @@ -0,0 +1,23 @@ +.\" $OpenBSD: dcphy.4,v 1.5 2009/07/31 14:20:29 jmc Exp $ +.\" +.\" Michael Shalayeff, 2003. Public Domain. +.\" +.Dd $Mdocdate: July 31 2009 $ +.Dt DCPHY 4 +.Os +.Sh NAME +.Nm dcphy +.Nd Pseudo-driver for media support on DEC 21143 controllers +.Sh SYNOPSIS +.Cd "dcphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver handles media selection on the +.Tn DEC 21143 +chip as it has no real MII interface. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/ddb.4 b/static/openbsd/man4/ddb.4 new file mode 100644 index 00000000..9097506e --- /dev/null +++ b/static/openbsd/man4/ddb.4 @@ -0,0 +1,1303 @@ +.\" $OpenBSD: ddb.4,v 1.111 2026/02/02 15:21:28 claudio Exp $ +.\" $NetBSD: ddb.4,v 1.5 1994/11/30 16:22:09 jtc Exp $ +.\" +.\" Mach Operating System +.\" Copyright (c) 1991,1990 Carnegie Mellon University +.\" All Rights Reserved. +.\" +.\" Permission to use, copy, modify and distribute this software and its +.\" documentation is hereby granted, provided that both the copyright +.\" notice and this permission notice appear in all copies of the +.\" software, derivative works or modified versions, and any portions +.\" thereof, and that both notices appear in supporting documentation. +.\" +.\" CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" +.\" CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR +.\" ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE. +.\" +.\" Carnegie Mellon requests users of this software to return to +.\" +.\" Software Distribution Coordinator or Software.Distribution@CS.CMU.EDU +.\" School of Computer Science +.\" Carnegie Mellon University +.\" Pittsburgh PA 15213-3890 +.\" +.\" any improvements or extensions that they make and grant Carnegie Mellon +.\" the rights to redistribute these changes. +.\" +.Dd $Mdocdate: February 2 2026 $ +.Dt DDB 4 +.Os +.Sh NAME +.Nm ddb +.Nd kernel debugger +.Sh DESCRIPTION +The +.Nm +debugger provides a means for debugging the kernel, +and analysing the kernel after a system crash ("panic"), with a +.Xr gdb 1 Ns \&-like +syntax. +.Pp +.Nm +is invoked upon a kernel panic when the +.Xr sysctl 8 +.Va ddb.panic +is set to 1. +It may be invoked from the console when the sysctl +.Va ddb.console +is set to 1, using any of the following methods: +.Bl -dash -offset 3n +.It +Using the key sequence +.Li Ctrl-Alt-Esc . +.It +Sending a +.Dv BREAK +when using a serial console. +.It +Writing to the sysctl +.Va ddb.trigger . +.It +For i386 and amd64 architectures, +using the key sequence +.Li Ctrl-Alt-Delete +when the sysctl +.Va machdep.kbdreset +is set to 2. +.El +.Pp +.Nm +prompts for commands on the console with: +.Pp +.Dl ddb> +.Pp +The general syntax of a +.Nm +command is: +.Bd -ragged -offset indent +.Ar command +.Oo Ic / Ns Ar modifiers Oc " " +.Oo Ar address Oc Ns +.Op Ic \&, Ns Ar count +.Ed +.Pp +To save typing, +.Nm +makes use of a context inferred from previous commands. +In this context, +the current location is called +.Va dot . +.\" The +.\" .Va dot +.\" is displayed with +.\" a hexadecimal format at a prompt. +The +.Ic examine , +.Ic search , +.Ic show struct , +and +.Ic write +commands update +.Va dot +to be that of the last address +examined or the last location modified, and +have intuitive effects on +.Va next +and +.Va prev . +All the other commands do not change +.Va dot , +and set +.Va next +to be the same. +(See +.Sx VARIABLES . ) +.Pp +.\" Specifying +.\" .Ar address +.\" in a command sets +.\" .Va dot . +An expression can be used in place of +.Ar address +(see +.Sx EXPRESSIONS ) . +Omitting +.Ar address +in a command uses the last value of +.Va dot . +A missing +.Ar count +is taken to be 1 for printing commands or \*(If +for stack traces. +Entering a blank line causes the last command to be repeated using +.Va next +in place of +.Ar address , +a +.Ar count +of 1, and no modifiers. +.Pp +.Nm +has a feature like +.Xr more 1 +for the output. +If the number of lines output in response to one command exceeds the number +set in the +.Va $lines +variable, it displays the message +.Ql "--db_more--" +and waits for a response. +.Pp +The valid responses are: +.Pp +.Bl -tag -width 10n -offset indent -compact +.It Aq Ic space +One more page. +.It Aq Ic return +One more line. +.It Ic q +Abort the current command, and return to the command input mode. +.El +.Pp +The following command line editing keys are provided: +.Pp +.Bl -tag -width 10n -offset indent -compact +.It Ic ^b +back one character +.It Ic ^f +forward one character +.It Ic ^a +beginning of line +.It Ic ^e +end of line +.It Ic ^w +erase word back +.It Ic ^h | Aq Ic del +erase previous character +.It Ic ^d +erase next character +.It Ic ^k +delete to end of line +.It Ic ^u +delete line +.It Ic ^p +previous in command history +.It Ic ^n +next in command history +.It Ic ^r +redraw line +.It Ic ^t +exchange the two characters to the left of the cursor +.El +.Sh COMMANDS +The following commands may be typed at the +.Ql ddb> +prompt. +Some commands consist of more than one word, and if only the first word +or words are entered, the possible alternatives to complete the command +are displayed and no other action is performed. +.Bl -tag -width 10n +.\" -------------------- +.It Ic help +List the available commands. +.\" -------------------- +.Tg examine +.It Xo +.Oo Ic e Oc Ns +.Ic x Ns Op Ic amine +.Op Cm /bhlqaAxzodurcsmiI +.Op Ar addr Ns +.Op Ic \&, Ns Ar count +.Xc +Display the contents at address +.Ar addr +according to the formats in the modifier. +If no format is specified, the last formats specified for this command +are used. +.Pp +The format characters are: +.Pp +.Bl -tag -width 4n -compact +.It Cm /b +look at by bytes (8 bits) +.It Cm /h +look at by half words (16 bits) +.It Cm /l +look at by long words (32 bits) (default) +.It Cm /q +look at by long longs (64 bits) (only available on 64-bit platforms) +.It Cm /a +print the location being displayed +.It Cm /A +print the location with a line number if possible +.It Cm /x +display in unsigned hex +.It Cm /z +display in signed hex +.It Cm /o +display in unsigned octal +.It Cm /d +display in signed decimal +.It Cm /u +display in unsigned decimal +.It Cm /r +display in current radix, signed +.It Cm /c +display low 8 bits as a character. +Non-printing characters are displayed as an octal escape code (e.g., '\e000'). +.It Cm /s +display the null-terminated string at the location. +Non-printing characters are displayed as octal escapes. +.It Cm /m +display in unsigned hex with character dump at the end of each line. +The location is also displayed in hex at the beginning of each line. +.It Cm /i +display as an instruction +.It Cm /I +display as an alternate format instruction depending on the +machine: +.Pp +.Bl -tag -width powerpc_ -compact +.It alpha +Print affected register contents for every instruction. +.It amd64 , +.It i386 +Do not skip padding to the next long word boundary for unconditional jumps. +.It m88k +Decode instructions for the opposite CPU model (e.g. m88110 when running on an +m88100 processor). +.El +.El +.Pp +The value of +.Va next +is set to the +.Ar addr +plus the size of the data examined. +.\" -------------------- +.Tg print +.It Xo +.Ic p Ns Op Ic rint +.Op Cm /axzodurc +.Op Ar addr +.Xc +Print +.Ar addr +according to the modifier character. +The valid modifiers are a subset of those from the +.Ic examine +command, and act as described there. +If no modifier is specified, the last one specified in a +previous use of +.Ic print +is used. +.Pp +For example, +.Bd -literal -offset indent +print/x $eax +.Ed +.Pp +will print something like this: +.Bd -literal -offset indent +xxxxxx +.Ed +.\" -------------------- +.Tg pprint +.It Xo +.Ic pp Ns Op Ic rint +.Op Ar addr +.Xc +Pretty-print +.Ar addr +using CTF debug symbols included in the kernel binary image. +The CTF section is normally added by running +.Xr ctfstrip 1 +as part of building a new kernel. +.\" -------------------- +.\" .It Xo Ic w Ns Op Cm /bhl +.\" .Op Ar addr +.\" .Ar expr Op expr ... +.\" .Xc +.Tg write +.It Xo +.Ic w Ns Op Ic rite +.Op Cm /bhl +.Op Ar addr +.Ar expr Op Ar expr ... +.Xc +Write the value of each +.Ar expr +expression at succeeding locations start at +.Ar addr . +The write unit size can be specified using one of the modifiers: +.Pp +.Bl -tag -width 4n -offset indent -compact +.It Cm /b +byte (8 bits) +.It Cm /h +half word (16 bits) +.It Cm /l +long word (32 bits) (default) +.El +.Pp +The value of +.Va next +is set to +.Ar addr +plus the size of values written. +.Pp +.Sy Warning : +since there is no delimiter between expressions, the +command may not parse as you expect. +It is best to enclose each expression in parentheses. +.\" -------------------- +.It Xo Ic set +.Ic $ Ns Ar name +.Op Ic = +.Ar expr +.Xc +Set the named variable or register with the value of +.Ar expr . +For valid variable names, +see +.Sx VARIABLES . +.\" -------------------- +.It Ic boot Ar how +Reboot the machine depending on +.Ar how : +.Pp +.Bl -tag -width "boot poweroff" -compact +.It Ic boot sync +Sync disks and reboot. +.It Ic boot crash +Dump core and reboot. +.It Ic boot dump +Sync disks, dump core and reboot. +.It Ic boot halt +Just halt. +.It Ic boot reboot +Just reboot. +.It Ic boot poweroff +Power down the machine whenever possible; if it fails, just halt. +.El +.\" -------------------- +.It Xo +.Ic break +.Op Ar addr Ns +.Op Ic \&, Ns Ar count +.Xc +Set a break point at +.Ar addr . +If +.Ar count +is supplied, +.Nm +allows the breakpoint to be silently hit +.Ar ( count No \- 1 ) +times before stopping at the +break point. +.\" -------------------- +.Tg delete +.It Xo +.Ic d Ns Op Ic elete +.Op Ar addr +.Xc +Delete the break point set with the +.Ic break +command. +.\" -------------------- +.\" .It Xo Ic s Ns Op Cm /p +.\" .Op Ic \&, Ns Ar count +.\" .Xc +.Tg step +.It Xo +.Ic s Ns Op Ic tep +.Op Cm /p +.Op Ic \&, Ns Ar count +.Xc +Single step +.Ar count +times. +If the +.Cm /p +modifier is specified, print each instruction at each step. +Otherwise, only print the last instruction. +.Pp +.Sy Warning : +depending on machine type, it may not be possible to +single-step through some low-level code paths. +On machines with software-emulated single-stepping (e.g., alpha), +stepping through code executed by interrupt handlers will probably +do the wrong thing. +.\" -------------------- +.It Ic call Ar name Ns Xo +.Ic \&( Ns Ar expr +.Op Ic \&, Ar expr ... +.Ic \&) +.Xc +Call the function named by +.Ar name +with the argument(s) listed in parentheses. +Parentheses may be omitted if the function takes no arguments. +The number of arguments is currently limited to 10. +.\" -------------------- +.\" .It Ic c Ns Op Cm /c +.Tg continue +.It Xo +.Ic c Ns Op Ic ontinue +.Op Cm /c +.Xc +Continue execution until a breakpoint or watchpoint. +If the +.Cm /c +modifier is given, instructions are counted while executing. +.Pp +.Sy Warning : +when counting with +.Cm /c , +.Nm +is really silently single-stepping. +This means that single-stepping on low-level code may cause strange +behavior. +.\" -------------------- +.It Xo +.Ic watch +.Ar addr +.Op Ic \&, Ns Ar size +.Xc +Set a watchpoint for the region starting at +.Ar addr . +Execution stops and control returns to +.Nm +when an attempt is made to modify a watched region. +The +.Ar size +argument defaults to 4. +.Pp +If you specify a wrong space address, the request is rejected +with an error message. +.Pp +.Sy Warning : +attempts to watch wired kernel memory +may cause an unrecoverable error on some systems (e.g., i386). +.\" -------------------- +.It Ic dwatch Ar addr +Delete the watchpoint at address +.Ar addr +that was previously set with a +.Ic watch +command. +.\" -------------------- +.It Xo +.Ic hangman +.Op Cm /s Ns Op Ic 0-9 +.Xc +This is a tiny and handy tool for random kernel hangs analysis, of which its +depth is controlled by the optional argument of the default value of five. +It uses some sophisticated heuristics to spot the global symbol that +caused the hang. +Since the discovering algorithm is a probabilistic one, +you may spend substantial time to figure the exact symbol name. +This smart thing requires a little of your attention, the input it accepts +is mostly of the same format as that of the famous +.Xr hangman 6 +game, to which it, apparently, is obliged by the name. +Hint: the +.Xr nm 1 +utility might help. +.\" -------------------- +.It Ic until Op Cm /p +Stop at the next +.Qq call +or +.Qq return +instruction. +If the +.Cm /p +modifier is specified, +.Nm +prints the call nesting depth and the +cumulative instruction count at each call or return. +Otherwise, it stays silent until the matching return is hit. +.\" -------------------- +.It Ic match Op Cm /p +Stop at the next matching return instruction. +If the +.Cm /p +modifier is specified, +.Nm +prints the call nesting depth and the +cumulative instruction count at each call or return. +Otherwise, it remains mostly quiet. +.\" -------------------- +.It Ic next Op Cm /p +The +.Ic next +command is a synonym for +.Ic match . +.\" -------------------- +.It Ic kill Ar pid +Send an uncatchable +.Dv SIGABRT +signal to the process specified by the +.Ar pid +argument. +.\" -------------------- +.It Ic stop Ar pid +Send a +.Dv SIGSTOP +signal to the process specified by the +.Ar pid +argument. +.\" -------------------- +.It Xo +.Ic trace +.Op Cm /tu +.Op Ar frameaddr Ns +.Op Ic \&, Ns Ar count +.Xc +Show the stack trace. +The +.Cm /t +modifier interprets the +.Ar frameaddr +argument as the TID of a process and shows the stack trace of +that process. +.Ar frameaddr +is subject to the radix; use the 0t prefix to enter a decimal TID. +The +.Cm /t +modifier is not supported on all platforms. +The +.Cm /u +modifier shows the stack trace of user space; +if omitted, the kernel stack is traced instead. +The +.Ar count +argument is the limit on the number of frames to be followed. +If +.Ar count +is omitted, all frames are printed. +.Pp +.Sy Warning : +user space stack trace is valid +only if the machine dependent code supports it. +.\" -------------------- +.It Xo +.Ic search +.Op Cm /bhl +.Op Ar addr +.Ar value +.Op Ar mask +.Op Ic \&, Ns Ar count +.Xc +Search memory for a value beginning at +.Ar addr . +This command might fail in interesting +ways if it doesn't find the searched-for value. +This is because +.Nm +doesn't always recover from touching bad memory. +The optional +.Ar count +argument limits the search. +The modifiers are the same as those of the +.Ic write +command. +.Pp +The +.Va next +address is set to the address where +.Ar value +is found, or just after where the search area finishes. +.\" -------------------- +.It Ic reboot +Shortcut for +.Ic boot reboot +.\" -------------------- +.It Ic show Ar what +Displays various things, depending on +.Ar what : +.Bl -tag -width 4n +.\" -------------------- +.It Ic show bcstats +Prints the buffer cache statistics. +.\" -------------------- +.It Ic show breaks +Prints a list of all breakpoints that have been set with the +.Ic break +command. +.\" -------------------- +.It Ic show buf Ar addr +Prints the +.Vt struct buf +at +.Ar addr . +.\" -------------------- +.It Ic show extents +Prints a detailed list of all extents. +.\" -------------------- +.It Ic show locks Op Ar addr +Prints the list of locks held by a thread. +If an optional address is not specified, +.Li curproc +is assumed. +The +.Cm option WITNESS +is required for this command to be available. +.\" -------------------- +.It Ic show malloc Op Ar addr +Prints malloc debugging information if available. +If an optional address is specified, only information about that address +is printed. +.\" -------------------- +.It Xo +.Ic show map +.Op Cm /f +.Ar addr +.Xc +Prints the +.Li vm_map +at +.Ar addr . +If the +.Cm /f +modifier is specified, the complete map is printed. +.\" -------------------- +.It Xo +.Ic show mbuf +.Op Cm /cp +.Ar addr +.Xc +Prints the +.Vt struct mbuf +header at +.Ar addr . +Depending on the mbuf flags +.Vt struct pkthdr +and +.Vt struct m_ext +are printed as well. +If the +.Cm /c +modifier is specified, print the mbuf chain linked with the m_next +pointer. +.Cm /p +does the same using m_nextpkt. +Both can be combined. +.\" -------------------- +.It Xo +.Ic show mount +.Op Cm /f +.Ar addr +.Xc +Prints the +.Vt struct mount +at +.Ar addr . +If the +.Cm /f +modifier is specified, prints out all +.Li vnodes +(see also +.Cm show vnode ) +and also all +.Li bufs +(see also +.Cm show buf ) +on all those vnodes. +.\" -------------------- +.It Xo +.Ic show nfsnode +.Op Cm /f +.Ar addr +.Xc +Prints the +.Vt struct nfsnode +at +.Ar addr . +If the +.Cm /f +modifier is specified, prints out additional +information as well. +.\" -------------------- +.It Xo +.Ic show nfsreq +.Op Cm /f +.Ar addr +.Xc +Prints the +.Vt struct nfsreq +at +.Ar addr . +If the +.Cm /f +modifier is specified, prints out additional +information as well. +.\" -------------------- +.It Xo +.Ic show object +.Op Cm /f +.Ar addr +.Xc +Prints the +.Li vm_object +at +.Ar addr . +If the +.Cm /f +modifier is specified, the complete object is printed. +.\" -------------------- +.It Xo +.Ic show page +.Op Cm /f +.Ar addr +.Xc +Prints the +.Li vm_page +at +.Ar addr . +If the +.Cm /f +modifier is specified, the complete page is printed. +.\" -------------------- +.It Ic show panic +Prints the panic string. +.\" -------------------- +.It Xo +.Ic show pool +.Op Cm /p +.Ar addr +.Xc +Prints the +.Li pool +at +.Ar addr . +Valid modifiers: +.Bl -tag -width xxx -compact +.It Cm /p +Print the pagelist for this pool. +.El +.\" -------------------- +.It Xo +.Ic show proc +.Op Cm /t +.Op Ar addr +.Xc +Prints the +.Vt struct proc +at +.Ar addr . +If an optional address is not specified, +.Li curproc +is assumed. +The +.Cm /t +modifier interprets the +.Ar addr +argument as the TID of a proc. +.\" -------------------- +.It Ic show registers Op Cm /u +Display the register set. +If the +.Cm /u +modifier is specified, it displays user registers (or the currently +saved registers) instead of the kernel's. +Note: The +.Cm /u +modifier is not supported on every machine, in which case +incorrect information may be displayed. +.\" -------------------- +.It Ic show route Ar addr +Prints the +.Vt struct rtentry +at +.Ar addr . +.\" -------------------- +.It Ic show socket Ar addr +Prints the +.Vt struct socket +at +.Ar addr . +If the socket is spliced, the +.Vt struct sosplice +associated with the socket is printed as well. +.\" -------------------- +.It Xo +.Ic show struct +.Ar name +.Op addr +.Xc +Prints the content of the memory at +.Ar addr +as a struct +.Ar name . +Nested structures and bit fields are not printed. +Character arrays are printed as bytes. +.\" -------------------- +.It Ic show swap +Prints a detailed list of all swaps. +.\" -------------------- +.It Xo +.Ic show tdb +.Op Cm /f +.Ar addr +.Xc +Prints the +.Vt struct tdb +at +.Ar addr . +If the +.Cm /f +modifier is specified, prints out all fields of this IPsec SA. +.\" -------------------- +.It Ic show uvmexp +Displays a selection of uvm counters and statistics. +.\" -------------------- +.It Xo +.Ic show vnode +.Op Cm /f +.Ar addr +.Xc +Prints the +.Vt struct vnode +at +.Ar addr . +If the +.Cm /f +modifier is specified, prints out all +.Li bufs +(see also +.Cm show buf ) +currently attached to this +.Li vnode . +.\" -------------------- +.It Ic show watches +Displays all watchpoints set with the +.Ic watch +command. +.\" -------------------- +.It Ic show witness Op Cm /b +Prints the current order list. +If the +.Cm /b +modifier is specified, the list of found lock order violations is printed +instead. +The +.Cm option WITNESS +is required for this command to be available. +.\" -------------------- +.It Ic show all procs Op Cm /anow +Display information on all processes. +.Pp +.Bl -tag -width foo -compact +.It Cm /n +(Default) Show process information in a +.Xr ps 1 Ns \&-like +format. +Information printed includes process ID, thread ID, parent +process ID, UID, process status, process flags, process +wait channel message and process command name. +.It Cm /a +Shows the kernel virtual addresses of each process' +proc structure, u-area, and vmspace structure. +The vmspace address is also the address of the process' +.Li vm_map +structure +and can be used in the +.Ic show map +command. +.It Cm /o +Shows non-idle threads that were on CPU when ddb was entered. +Information printed includes thread ID, process ID, UID, process flags, +thread flags, current CPU, and command name. +.It Cm /w +Shows each thread's ID, command, process group, +wait channel address, and wait channel message. +.El +.\" -------------------- +.It Ic show all bufs Op Cm /f +Display information about all buffers in the system. +.Pp +.Bl -tag -width foo -compact +.It Cm /f +For each buffer, print a more detailed output. +See the +.Ic show buf +command for more information. +.El +.\" -------------------- +.It Ic show all callout +Display the contents of the callout table. +.\" -------------------- +.It Ic show all pools Op Cm /a +Display information about all system pools in a format similar to +.Xr vmstat 8 . +.Pp +.Bl -tag -width foo -compact +.It Cm /a +Displays +.Dq interesting +address information. +.El +.\" -------------------- +.It Ic show all locks +Prints the list of locks held by all threads in the system. +The +.Cm option WITNESS +is required for this command to be available. +.\" -------------------- +.It Ic show all mounts Op Cm /f +Display information on all mounted filesystems. +.Pp +.Bl -tag -width foo -compact +.It Cm /f +For each filesystem, list all its struct vnode addresses. +These addresses can be used in the +.Ic show vnode +command. +.El +.\" -------------------- +.It Ic show all nfsnodes Op Cm /f +Display information about all nfsnodes in the system. +.Pp +.Bl -tag -width foo -compact +.It Cm /f +For each nfsnode, print a more detailed output. +See the +.Ic show nfsnode +command for more information. +.El +.\" -------------------- +.It Ic show all nfsreqs Op Cm /f +Display information for all outstanding NFS requests. +.Pp +.Bl -tag -width foo -compact +.It Cm /f +For each NFS requests, print a more detailed output. +See the +.Ic show nfsreq +command for more information. +.El +.\" -------------------- +.It Xo +.Ic show all routes +.Op Cm /iI +.Op Ar rtableid +.Op Ic \&, Ns Ar count +.Xc +Show internet routing tables. +Default for +.Ar rtableid +is 0 and +.Ar count +is 1. +.Pp +.Bl -tag -width foo -compact +.It Cm /i +Restrict to AF_INET. +.It Cm /I +Restrict to AF_INET6. +.El +.\" -------------------- +.It Ic show all tdbs Op Cm /f +Display information about all IPsec SAs in the system. +.Pp +.Bl -tag -width foo -compact +.It Cm /f +For each tdb, print a more detailed output. +See the +.Ic show tdb +command for more information. +.El +.\" -------------------- +.It Ic show all vnodes Op Cm /f +Display information about all vnodes in the system. +.Pp +.Bl -tag -width foo -compact +.It Cm /f +For each vnode, print a more detailed output. +See the +.Ic show vnode +command for more information. +.El +.El +.\" -------------------- +.It Ic callout +A synonym for the +.Ic show all callout +command. +.\" -------------------- +.It Ic ps Op Cm /anow +A synonym for +.Ic show all procs . +.\" -------------------- +.Tg machine +.It Xo +.Ic mac Ns Op Ic hine +.Ar subcommand Op Ar arg ... +.Xc +Perform a platform-specific command. +.Pp +The following commands are supported by multiprocessor kernels on +these platforms: amd64, i386, macppc, mips64, and sparc64. +.Pp +.Bl -tag -width "searchframe [addr]" -compact +.It Ic cpuinfo +Display the state of each CPU. +.It Ic ddbcpu Ar N +Stop the current CPU and start handling +.Nm +on the selected CPU. +.It Ic startcpu Op Ar N +Resume normal processing on the selected CPU, +or all CPUs if none is specified. +.It Ic stopcpu Op Ar N +Stop normal processing on the selected CPU, +or all CPUs (except the one handling +.Nm ) +if none is specified. +.El +.Pp +Other platform-specific commands: +.\" .Pp +.\" amd64: +.Pp +arm: +.Bl -tag -width "searchframe [addr]" -compact +.It Ic frame Ar addr +Display the trapframe at +.Ar addr . +.El +.Pp +i386: +.Bl -tag -width "searchframe [addr]" -compact +.\" .It Ic acpi disasm Ar ?? +.\" .It Ic acpi showval Ar ?? +.\" .It Ic acpi tree Ar ?? +.\" .It Ic acpi trace Ar ?? +.\" Evil ACPI debugging magic. +.It Ic sysregs +Display the contents of the privileged registers: +.Va IDTR , +.Va GDTR , +.Va LDTR , +.Va TR , +.Va CR0 , +.Va CR2 , +.Va CR3 , +and +.Va CR4 . +.\" (i386-only) +.El +.Pp +m88k: +.Bl -tag -width "searchframe [addr]" -compact +.It Ic ddbcpu Ar N +Stop the current CPU and start handling +.Nm +on the selected CPU. +.It Ic frame Ar addr +Display the trapframe at +.Ar addr . +.It Ic regs +Display the registers from when +.Nm +was entered. +.It Ic searchframe Op Ar addr +Search for and display stack exception frames, +starting from +.Ar addr +if given, else the address in register +.Va r31 , +and stopping at the next 8k boundary. +.It Ic where +Display where the current CPU was stopped. +.El +.Pp +mips64: +.Bl -tag -width "searchframe [addr]" -compact +.It Xo +.Ic tlb Op Cm /p Ar asid +.Op Cm /c +.Op Ar tlb +.Xc +.It Ic trap Ar ?? +.El +.Pp +sh: +.Bl -tag -width "searchframe [addr]" -compact +.It Ic cache Op Ar addr +Display the cache, starting from +.Ar addr , +defaulting to 0. +.It Ic frame +Display the switch and trap frames. +.\" .It Ic stack +.It Ic tlb +Display the TLB. +.El +.Pp +sparc64: +.Bl -tag -width "searchframe [addr]" -compact +.It Ic ctx +Display the context addresses for all threads. +.\" .It Ic dtlb Ar 0,2 +.\" .It Ic dtsb +.\" .It Ic esp +.\" .It Ic fpstate Op Ar addr +.\" .It Ic itlb Ar 0,1,2 +.\" .It Ic kmap Op Ar addr +.\" .It Ic pcb Op Ar addr +.\" .It Ic pctx Ar pid +.\" .It Ic page Ar addr +.\" .It Ic phys Op Ar addr +.\" .It Ic pmap Op Ar addr +.\" .It Ic proc Op Ar addr +.\" .It Ic prom Ar ?? +.\" .It Ic pv Ar addr +.\" .It Ic stack Op Ar addr +.\" .It Ic tf Op Ar addr +.\" .It Ic ts +.\" .It Ic traptrace Op Ar addr +.\" .It Ic watch Op Ar addr +.\" .It Ic window Op Ar winnum +.\" .It Ic xir Op Ar addr +.El +.\" -------------------- +.El +.Sh VARIABLES +.Nm +denotes registers and variables by +.Ic $ Ns Va name . +Register names can be found with the +.Ic show registers +command. +.Pp +Built-in debugger variables currently supported are: +.Bl -tag -width 10n -compact -offset indent +.It Va $radix +Input and output radix. +.It Va $maxoff +Addresses are printed as +.Ar symbol Ns Li + Ns Ar offset +unless +.Ar offset +is greater than +.Va $maxoff . +.It Va $maxwidth +The width of the displayed lines. +.It Va $lines +The number of lines to page. +This is used by the +.Dq more +feature. +.It Va $tabstops +Tab stop width. +.It Va $log +Controls whether the output of +.Nm +will also appear in the system message +buffer. +.El +.Pp +These variables can also be controlled outside +.Nm +via the +.Sq ddb +.Xr sysctl 8 +hierarchy. +.Sh EXPRESSIONS +Almost all expression operators in C are supported except for +.Ql ~ , +.Ql ^ , +and unary +.Ql & . +Special rules for expressions in +.Nm +are: +.Bl -tag -width 15n -compact -offset indent +.It Ar identifier +The name of a symbol. +It is translated to the address (or value) of the symbol. +.Ql \&. +and +.Ql \&: +can be used in the identifier. +The following can be accepted as an identifier, +if supported by an object format dependent routine: +.Bl -item -offset indent -compact +.It +.Sm off +.Oo Ar filename Li \&: Oc Ar func +.Op \&: Ar linenumber +.It +.Op Ar filename \&: +.Ar variable +.It +.Ar filename +.Op \&: Ar linenumber +.Sm on +.El +The symbol may be prefixed with +.Sq Ar symboltablename Ns :: +(e.g., +.Ql emulator::mach_msg_trap ) +to specify other than kernel symbols. +.It Ar number +The radix is determined by the first two letters: +.Ql 0x : +hex, +.Ql 0o : +octal, +.Ql 0t : +decimal, otherwise, the value of +.Va $radix +is used. +.It Li \&. +.Va dot : +the current address. +.It Li + +.Va next : +the next address. +.It Li .. +The address of the start of the last line examined. +Unlike +.Va dot +or +.Va next , +this is only changed by the +.Ic examine +or +.Ic write +command. +.It Li ' +The last address explicitly specified. +.It Li $ Ns Ar variable +The value of a register or variable. +.It Ar expr Li # Ar expr +A binary operator which rounds up the left hand side to the next +multiple of right hand side. +.It Li * Ns Ar expr +Indirection. +It may be followed by a ':' as described above with +.Ar identifier . +.El +.Sh SEE ALSO +.Xr ctfstrip 1 , +.Xr gdb 1 , +.Xr nm 1 , +.Xr witness 4 , +.Xr sysctl.conf 5 , +.Xr hangman 6 , +.Xr crash 8 , +.Xr sysctl 8 , +.Xr extent 9 , +.Xr pool 9 , +.Xr uvm_init 9 +.Sh HISTORY +This kernel facility first appeared in the Mach 3.0 operating system +developed by CMU. +Hangman (which stands for "hangs maniacal analyzer") first appeared in +.Ox 1.2 . diff --git a/static/openbsd/man4/de.4 b/static/openbsd/man4/de.4 new file mode 100644 index 00000000..cd30465c --- /dev/null +++ b/static/openbsd/man4/de.4 @@ -0,0 +1,131 @@ +.\" $OpenBSD: de.4,v 1.24 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 1997 David E. O'Brien +.\" +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt DE 4 +.Os +.Sh NAME +.Nm de +.Nd DEC DC21x4x (Tulip) 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "de* at pci?" +.Sh DESCRIPTION +The +.Nm +device driver supports Ethernet adapters based on the Digital +Equipment DC21x4x based self-contained Ethernet chips. +This includes, among others, the following models: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Asante +.It Cogent EM100FX and EM440TX +.It DEC PCI DE435, EISA DE425, DE450, DE500 +.It older Linksys 10, 10/100 +.It SMC 8432, 9332, 9334 +.It ZNYX ZX3xx +.El +.Pp +This driver may support other cards based on the 21040 and 21041 Ethernet +controllers, or the 21140[A], 21141, 21142, and 21143 Fast Ethernet +controllers. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex -offset indent +.It autoselect +Enable autoselection of the media type and options. +.It 10baseT +Set 10Mbps operation on the 10baseT port. +.It 10base2 +Set 10Mbps operation on the BNC port. +.It 10base5 +Set 10Mbps operation on the AUI port. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.It 100baseFX +Set 100Mbps operation. +.It 100baseT4 +Set 100Mbps operation (4-pair cat-3 cable). +.El +.Pp +The +.Nm +driver supports the following media options: +.Pp +.Bl -tag -width full-duplex -offset indent -compact +.It full-duplex +Set full duplex operation for UTP port. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by your card try +.Ic ifconfig media . +For example, +.Ic ifconfig de0 media . +.Pp +Note that the media types available depend on the particular card in use. +Some cards are explicitly programmed to a particular media type by a +setup utility and are not changeable. +.Pp +The old +.Dq ifconfig linkN +method of configuration is not supported. +.Sh DIAGNOSTICS +.Bl -diag +.It "de0: waking device from sleep/snooze mode" +The 21041 and 21140A chips support suspending the operation of the card. +.It "de0: error: desired IRQ of X does not match device's actual IRQ of Y" +The device probe detected that the board is configured for a different +interrupt than the one specified in the kernel configuration file. +.It "de0: not configured; limit of N reached or exceeded" +There is a limit of 32 +.Nm +devices allowed in a single machine. +.It "de0: not configured; 21040 pass 2.0 required (X.Y found)" +.It "de0: not configured; 21140 pass 1.1 required (X.Y found)" +Certain revisions of the chipset are not supported by this driver. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh AUTHORS +.An -nosplit +The +.Nm +device driver was written by +.An Matt Thomas . +This manual page was written by +.An David E. O'Brien . +.Sh CAVEATS +Since the 21040 is available on both EISA and PCI boards, one must be careful +in how one defines the 21040 in the kernel config file. diff --git a/static/openbsd/man4/diskmap.4 b/static/openbsd/man4/diskmap.4 new file mode 100644 index 00000000..6f953329 --- /dev/null +++ b/static/openbsd/man4/diskmap.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: diskmap.4,v 1.3 2015/09/10 17:55:21 schwarze Exp $ +.\" +.\" Copyright (c) 2010 Joel Sing +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt DISKMAP 4 +.Os +.Sh NAME +.Nm diskmap +.Nd disklabel UID mapping interface +.Sh SYNOPSIS +.In sys/dkio.h +.Sh DESCRIPTION +The +.Nm +driver provides userland applications with a means to map a disklabel UID to +an actual device and open that device in one atomic operation. +This is achieved via the DIOCMAP +.Xr ioctl 2 +command. +.Pp +The ability to use a disklabel UID is helpful in situations +where a disk may appear to the operating system under different device names. +For example, +plugging USB keys into differently configured systems (think sd0 or sd1), +or swapping between IDE and AHCI on a disk controller (wd0 or sd0). +Although the device names may change, +the operating system is still able to identify the disk by its UID. +.Sh FILES +.Bl -tag -width /dev/diskmap -compact +.It Pa /dev/diskmap +diskmap device +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr disklabel 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Joel Sing . diff --git a/static/openbsd/man4/divert.4 b/static/openbsd/man4/divert.4 new file mode 100644 index 00000000..c15772bc --- /dev/null +++ b/static/openbsd/man4/divert.4 @@ -0,0 +1,210 @@ +.\" $OpenBSD: divert.4,v 1.20 2022/09/10 10:22:46 jsg Exp $ +.\" +.\" Copyright (c) 2009 Michele Marchetto +.\" Copyright (c) 2012-2014 Lawrence Teo +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 10 2022 $ +.Dt DIVERT 4 +.Os +.Sh NAME +.Nm divert +.Nd kernel packet diversion mechanism +.Sh SYNOPSIS +.In sys/types.h +.In sys/socket.h +.In netinet/in.h +.Ft int +.Fn socket AF_INET SOCK_RAW IPPROTO_DIVERT +.Ft int +.Fn socket AF_INET6 SOCK_RAW IPPROTO_DIVERT +.Sh DESCRIPTION +Divert sockets are part of a mechanism completely integrated with +.Xr pf 4 +that queues raw packets from the kernel stack to userspace applications, +and vice versa. +.Pp +A divert socket must be bound to a divert port through +.Xr bind 2 , +which only the superuser can do. +Divert ports have their own number space, completely separated from +.Xr tcp 4 +and +.Xr udp 4 . +When +.Xr pf 4 +processes a packet that matches a rule with the +.Ar divert-packet +parameter +(see +.Xr pf.conf 5 +for details), it is sent to the divert socket listening on the +divert port specified in the rule. +Note that +.Ar divert-packet +should not be confused with +.Ar divert-to +or +.Ar divert-reply , +which do not use divert sockets. +If there are no divert sockets listening, the packets are dropped. +.Pp +Packets can be read via +.Xr read 2 , +.Xr recv 2 , +or +.Xr recvfrom 2 +from the divert socket. +The application that is processing the packets can then reinject them into the +kernel. +With +.Xr recvfrom 2 , +an interface IP address is passed if it is an inbound packet. +Outbound packets provide the unspecified address. +When reinjecting, use this address as argument to +.Xr sendto 2 . +This allows the kernel to guess the original incoming interface and +process it as an incoming packet. +If no interface IP address is given, the reinjected packet is treated +as an outgoing packet. +Since the userspace application could have modified the packets, upon +reinjection basic sanity checks are done to ensure that the packets are still +valid. +The packets' IPv4 and protocol checksums (TCP, UDP, ICMP, and ICMPv6) are also +recalculated. +.Pp +Writing to a divert socket can be achieved using +.Xr sendto 2 +and it will skip +.Xr pf 4 +filters to avoid loops. +Note that this means that a reinjected inbound packet will also not +run through the pf out rules after being forwarded. +A diverted packet that is not reinjected into the kernel stack is lost. +.Pp +Receive and send divert socket buffer space can be tuned through +.Xr sysctl 8 . +.Xr netstat 1 +shows information relevant to divert sockets. +Note that the default is 64k and too short to handle full sized UDP +packets. +.Sh EXAMPLES +The following PF rule queues outbound IPv4 packets to TCP port 80, +as well as the return traffic, on the em0 interface to divert port 700: +.Bd -literal -offset indent +pass out on em0 inet proto tcp to port 80 divert-packet port 700 +.Ed +.Pp +The following program reads packets on divert port 700 and reinjects them +back into the kernel. +This program does not perform any processing of the packets, +apart from discarding invalid IP packets. +.Bd -literal +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#define DIVERT_PORT 700 + +int +main(int argc, char *argv[]) +{ + int fd, s; + struct sockaddr_in sin; + socklen_t sin_len; + + fd = socket(AF_INET, SOCK_RAW, IPPROTO_DIVERT); + if (fd == -1) + err(1, "socket"); + + memset(&sin, 0, sizeof(sin)); + sin.sin_family = AF_INET; + sin.sin_port = htons(DIVERT_PORT); + sin.sin_addr.s_addr = 0; + + sin_len = sizeof(struct sockaddr_in); + + s = bind(fd, (struct sockaddr *) &sin, sin_len); + if (s == -1) + err(1, "bind"); + + for (;;) { + ssize_t n; + char packet[IP_MAXPACKET]; + struct ip *ip; + struct tcphdr *th; + int hlen; + char src[48], dst[48]; + + memset(packet, 0, sizeof(packet)); + n = recvfrom(fd, packet, sizeof(packet), 0, + (struct sockaddr *) &sin, &sin_len); + if (n == -1) { + warn("recvfrom"); + continue; + } + if (n < sizeof(struct ip)) { + warnx("packet is too short"); + continue; + } + + ip = (struct ip *) packet; + hlen = ip->ip_hl << 2; + if (hlen < sizeof(struct ip) || ntohs(ip->ip_len) < hlen || + n < ntohs(ip->ip_len)) { + warnx("invalid IPv4 packet"); + continue; + } + + th = (struct tcphdr *) (packet + hlen); + + if (inet_ntop(AF_INET, &ip->ip_src, src, + sizeof(src)) == NULL) + (void)strlcpy(src, "?", sizeof(src)); + + if (inet_ntop(AF_INET, &ip->ip_dst, dst, + sizeof(dst)) == NULL) + (void)strlcpy(dst, "?", sizeof(dst)); + + printf("%s:%u -> %s:%u\en", + src, + ntohs(th->th_sport), + dst, + ntohs(th->th_dport) + ); + + n = sendto(fd, packet, n, 0, (struct sockaddr *) &sin, + sin_len); + if (n == -1) + warn("sendto"); + } + + return 0; +} +.Ed +.Sh SEE ALSO +.Xr socket 2 , +.Xr ip 4 , +.Xr pf.conf 5 +.Sh HISTORY +The +.Nm +protocol first appeared in +.Ox 4.7 . diff --git a/static/openbsd/man4/drm.4 b/static/openbsd/man4/drm.4 new file mode 100644 index 00000000..31457af2 --- /dev/null +++ b/static/openbsd/man4/drm.4 @@ -0,0 +1,93 @@ +.\" $OpenBSD: drm.4,v 1.13 2022/01/07 00:44:17 jsg Exp $ +.\" +.\" Copyright (c) 2008 Jason McIntyre +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: January 7 2022 $ +.Dt DRM 4 +.Os +.Sh NAME +.Nm drm , +.Nm inteldrm , +.Nm radeondrm +.Nd Direct Rendering Manager device +.Sh SYNOPSIS +.Cd "# amd64" +.Cd "amdgpu* at pci?" +.Cd "drm0 at amdgpu? primary 1" +.Cd "drm* at amdgpu?" +.Cd "wsdisplay0 at amdgpu? primary 1" +.Cd "wsdisplay* at amdgpu? mux -1" +.Pp +.Cd "# arm64" +.Cd "amdgpu* at pci?" +.Cd "drm* at amdgpu?" +.Cd "wsdisplay* at amdgpu?" +.Pp +.Cd "# amd64, i386" +.Cd "inteldrm* at pci?" +.Cd "intagp* at inteldrm?" +.Cd "agp* at intagp?" +.Cd "drm0 at inteldrm? primary 1" +.Cd "drm* at inteldrm?" +.Cd "wsdisplay0 at inteldrm? primary 1" +.Cd "wsdisplay* at inteldrm? mux -1" +.Pp +.Cd "# amd64, i386" +.Cd "radeondrm* at pci?" +.Cd "drm0 at radeondrm? primary 1" +.Cd "drm* at radeondrm?" +.Cd "wsdisplay0 at radeondrm? primary 1" +.Cd "wsdisplay* at radeondrm? mux -1" +.Pp +.Cd "# arm64, loongson, macppc, powerpc64, riscv64, sparc64" +.Cd "radeondrm* at pci?" +.Cd "drm* at radeondrm?" +.Cd "wsdisplay* at radeondrm?" +.Sh DESCRIPTION +The +.Nm +driver provides support for hardware accelerated video +using the Direct Rendering Infrastructure (DRI). +.Nm +provides kernel support for DRI, +and is used in conjunction with the +.Xr X 7 +DRI module. +.Pp +Support is currently available for the following graphics cards: +.Pp +.Bl -tag -width "radeon(4)XXX" -offset indent -compact +.It Xr amdgpu 4 +AMD Radeon GPUs using the amdgpu kernel driver +.It Xr intel 4 +Intel integrated graphics chipsets +.It Xr radeon 4 +ATI/AMD Radeon video driver +.El +.Sh FILES +.Bl -tag -width "/usr/X11R6/lib/modules/dri/X_dri.so" -compact +.It Pa /dev/dri/card* +DRM primary node files. +.It Pa /dev/dri/renderD* +DRM render node files. +.It Pa /usr/X11R6/lib/modules/dri/*_dri.so +X DRI modules. +.El +.Sh SEE ALSO +.Xr vga 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . diff --git a/static/openbsd/man4/dsxrtc.4 b/static/openbsd/man4/dsxrtc.4 new file mode 100644 index 00000000..b2371e88 --- /dev/null +++ b/static/openbsd/man4/dsxrtc.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: dsxrtc.4,v 1.1 2020/04/25 15:16:00 kettenis Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 25 2020 $ +.Dt DSXRTC 4 +.Os +.Sh NAME +.Nm dsxrtc +.Nd Maxim DS3231/DS3232 real-time clock +.Sh SYNOPSIS +.Cd "dsxrtc* at iic? addr 0x68" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Maxim DS3231 and DS3232 +real-time clock chips. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/dt.4 b/static/openbsd/man4/dt.4 new file mode 100644 index 00000000..26a22b8e --- /dev/null +++ b/static/openbsd/man4/dt.4 @@ -0,0 +1,158 @@ +.\" $OpenBSD: dt.4,v 1.9 2025/10/11 00:54:55 jsg Exp $ +.\" +.\" Copyright (c) 2019 Martin Pieuchot +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 11 2025 $ +.Dt DT 4 +.Os +.Sh NAME +.Nm dt +.Nd dynamic tracer +.Sh SYNOPSIS +.Cd "pseudo-device dt" +.Sh DESCRIPTION +System and application tracing can happen in the kernel. +It has to be configured and enabled through the +.Xr ioctl 2 +interface exposed by the pseudo-device +.Pa /dev/dt . +.Pp +This device can only be opened when the +.Va kern.allowdt +.Xr sysctl 2 +variable is set. +.Sh IOCTL INTERFACE +The +.Xr ioctl 2 +command codes below are defined in +.In dev/dt/dtvar.h . +.Bl -tag -width xxxxxx +.It Dv DTIOCGPLIST Fa "struct dtioc_probe *dtpr" +Get available probe entries. +.Bd -literal +struct dtioc_probe { + size_t dtpr_size; + struct dtioc_probe_info *dtpr_probes; +}; +.Ed +.Pp +If +.Va dtpr_size +is non-zero, as many probes as possible that can fit into this size +will be copied into the supplied buffer. +On exit, +.Va dtpr_size +is always set to the total size required to hold all probe entries +(i.e., it is set to +.Li sizeof(struct dtioc_probe_info) * dt_nprobes ) . +.It Dv DTIOCGSTATS Fa "struct dtioc_stat *dtst" +Get statistics for current recording. +.Bd -literal +struct dtioc_stat { + uint64_t dtst_readevt; + uint64_t dtst_dropevt; +}; +.Ed +.It Dv DTIOCRECORD Fa "int on" +Start or stop recording. +.It Dv DTIOCPRBENABLE Fa "struct dtioc_req *dtrq" +Enable the given probe for recording. +.Bd -literal +struct dtioc_req { + uint32_t dtrq_pbn; + struct dt_filter dtrq_filter; + uint32_t dtrq_rate; + uint64_t dtrq_evtflags; +}; +.Ed +.It Dv DTIOCRDVNODE Fa "struct *dtioc_rdvn" +Resolve the instruction pointer from the traced process to the ELF object. +.Bd -literal +struct dtioc_rdvn { + pid_t dtrv_pid; + int dtrv_fd; + caddr_t dtrv_va; + caddr_t dtrv_offset; + caddr_t dtrv_start; + size_t dtrv_len; +}; +.Ed +.Pp +The caller populates +.Fa dtrv_pid +with the process ID of the traced process and +.Fa dtrv_va +with the program counter address to look up. +.Pp +On success, the remaining members are populated. +.Fa dtrv_fd +is the file descriptor to the DSO file that +.Fa dtrv_va +belongs to. +.Fa dtrv_len +is the length of the DSO file. +.Fa dtrv_offset +and +.Fa dtrv_start +are the relative offset of +.Fa dtrv_va +to the start of the text segment and the base address of that segment +respectively. +.Pp +To calculate the relative offset of +.Fa dtrv_va +in the DSO the following calculation can be used: +.Pp +.Dl iOffset = dtrv_va - dtrv_start + dtrv_offset +.Pp +The segment can be found by walking the ELF program headers and looking +for the mapping where iOffset is included in the range +[GElf_Phdr.p_offset, GElf_Phdr.p_offset + GElf_Phdr.p_filesz) +.Pp +Using the +.Vt GElf_Phdr.p_vaddr +the base address of the segment can be calculated by +.Dl lbase = dtrv_start - GElf_Phdr.p_vaddr +.Pp +For symbol lookups the offset can now be calculated as +.Dl symOffset = dtrv_va - lbase +.El +.Sh FILES +.Bl -tag -width /dev/dt -compact +.It Pa /dev/dt +dynamic tracing device. +.El +.Sh ERRORS +An open of +.Pa /dev/dt +will fail if: +.Bl -tag -width Er +.It Bq Er EPERM +the +.Va kern.allowdt +.Xr sysctl 2 +variable wasn't set. +.It Bq Er ENOMEM +not enough memory space was available. +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr bt 5 , +.Xr btrace 8 +.Sh HISTORY +The +.Nm +dynamic tracing mechanism first appeared in +.Ox 6.7 . diff --git a/static/openbsd/man4/dwctwo.4 b/static/openbsd/man4/dwctwo.4 new file mode 100644 index 00000000..7df9f908 --- /dev/null +++ b/static/openbsd/man4/dwctwo.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: dwctwo.4,v 1.4 2017/02/17 11:57:16 visa Exp $ +.\" +.\" Copyright (c) 2016 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 17 2017 $ +.Dt DWCTWO 4 +.Os +.Sh NAME +.Nm dwctwo +.Nd DesignWare HS USB 2.0 OTG controller +.Sh SYNOPSIS +.Cd "dwctwo* at fdt? " Pq "arm64, armv7" +.Cd "dwctwo0 at iobus? irq 56 " Pq "octeon" +.Cd "usb* at dwctwo?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the DesignWare High-Speed USB 2.0 On-the-Go +controller, which provides an interface to +.Xr usb 4 +devices. +.Sh SEE ALSO +.Xr ehci 4 , +.Xr ohci 4 , +.Xr usb 4 , +.Xr xhci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.8 . diff --git a/static/openbsd/man4/dwdog.4 b/static/openbsd/man4/dwdog.4 new file mode 100644 index 00000000..5aa61d41 --- /dev/null +++ b/static/openbsd/man4/dwdog.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: dwdog.4,v 1.3 2023/04/04 00:38:38 jsg Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 4 2023 $ +.Dt DWDOG 4 +.Os +.Sh NAME +.Nm dwdog +.Nd Synopsys DesignWare watchdog timer +.Sh SYNOPSIS +.Cd "dwdog* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Synopsys DesignWare watchdog timer, +which is built into various SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr watchdog 4 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/dwge.4 b/static/openbsd/man4/dwge.4 new file mode 100644 index 00000000..8aa474b2 --- /dev/null +++ b/static/openbsd/man4/dwge.4 @@ -0,0 +1,83 @@ +.\" $OpenBSD: dwge.4,v 1.7 2023/04/04 00:38:38 jsg Exp $ +.\" +.\" Copyright (c) 2016 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 4 2023 $ +.Dt DWGE 4 +.Os +.Sh NAME +.Nm dwge +.Nd Synopsys DesignWare GMAC 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "dwge* at fdt?" +.Cd "rgephy*" at mii? +.Sh DESCRIPTION +The +.Nm +driver provides support for various Ethernet controllers based on the +Synopsys DesignWare GMAC core. +These controllers are typically found on SoCs, such as the Allwinner +A20/A31 and Rockchip RK3288/RK3399 ARM SoCs. +.Pp +The +.Nm +driver supports several media types, which are selected via the +.Xr ifconfig 8 +command. +The supported media types are: +.Bl -tag -width "media" -offset indent +.It Cm media No autoselect +Attempt to autoselect the media type (default) +.It Cm media No 1000baseT Cm mediaopt No full-duplex +Use 1000baseT on copper, full duplex +.It Cm media No 1000baseT Cm mediaopt No half-duplex +Use 1000baseT on copper, half duplex +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Use 100baseTX, full duplex +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Use 100baseTX, half duplex +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr rgephy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx 7.0 . +It was ported to +.Ox 6.1 +and rewritten for +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Matt Thomas +and +.An Martin Husemann +for +.Nx +and rewritten by +.An Mark Kettenis Aq Mt kettenis@openbsd.org +and +.An Patrick Wildt Aq Mt patrick@openbsd.org . diff --git a/static/openbsd/man4/dwgpio.4 b/static/openbsd/man4/dwgpio.4 new file mode 100644 index 00000000..669ef241 --- /dev/null +++ b/static/openbsd/man4/dwgpio.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: dwgpio.4,v 1.2 2020/12/06 22:44:17 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 6 2020 $ +.Dt DWGPIO 4 +.Os +.Sh NAME +.Nm dwgpio +.Nd Synopsys DesignWare GPIO controller +.Sh SYNOPSIS +.Cd "dwgpio* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Synopsys DesignWare GPIO controller +found on, for example, the Ampere eMAG SoC. +It does not provide direct device driver entry points but makes its +functions available to +.Xr acpi 4 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/dwiic.4 b/static/openbsd/man4/dwiic.4 new file mode 100644 index 00000000..1f730de4 --- /dev/null +++ b/static/openbsd/man4/dwiic.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: dwiic.4,v 1.6 2023/08/29 12:11:08 kettenis Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 29 2023 $ +.Dt DWIIC 4 +.Os +.Sh NAME +.Nm dwiic +.Nd Synopsys DesignWare I2C controller +.Sh SYNOPSIS +.Cd "dwiic* at acpi?" +.Cd "dwiic* at fdt?" +.Cd "dwiic* at pci?" +.Cd "iic* at dwiic?" +.Sh DESCRIPTION +The +.Nm +driver supports the Synopsys DesignWare I2C controller for use +with the +.Xr iic 4 +framework. +.Pp +On systems using the Intel OnChip System Fabric, +.Nm +may need the +.Xr iosf 4 +driver to coordinate access to the I2C bus. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr iic 4 , +.Xr iosf 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . diff --git a/static/openbsd/man4/dwmmc.4 b/static/openbsd/man4/dwmmc.4 new file mode 100644 index 00000000..4a0838c9 --- /dev/null +++ b/static/openbsd/man4/dwmmc.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: dwmmc.4,v 1.2 2023/04/04 00:38:38 jsg Exp $ +.\" +.\" Copyright (c) 2017 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 4 2023 $ +.Dt DWMMC 4 +.Os +.Sh NAME +.Nm dwmmc +.Nd Synopsys DesignWare MMC/SD/SDIO controller +.Sh SYNOPSIS +.Cd "dwmmc* at fdt?" +.Cd "sdmmc* at dwmmc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various MMC/SD/SDIO controllers based on +the Synopsys DesignWare SD/eMMC core. +These controllers are typically found on SoCs, such as the Rockchip +RK3288/RK3399 and Samsung Exynos ARM SoCs. +.Pp +The +.Xr sdmmc 4 +subsystem performs SD/MMC transactions to communicate with whatever +MMC/SD/SDIO devices are inserted into the card slot or directly +connected to the controller. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sdmmc 4 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/dwmshc.4 b/static/openbsd/man4/dwmshc.4 new file mode 100644 index 00000000..74ade203 --- /dev/null +++ b/static/openbsd/man4/dwmshc.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: dwmshc.4,v 1.2 2026/04/08 08:58:28 jmatthew Exp $ +.\" +.\" Copyright (c) 2023 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 8 2026 $ +.Dt DWMSHC 4 +.Os +.Sh NAME +.Nm dwmshc +.Nd Synopsys DesignWare Mobile Storage Host Controller +.Sh SYNOPSIS +.Cd "dwmshc* at fdt?" +.Cd "sdmmc* at dwmshc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Synopsys DesignWare Mobile Storage +Host Controller core. +This core is used on the Rockchip RK3528, RK3566/RK3568 and RK3588 +SoCs as the eMMC controller. +.Pp +The Synopsys DesignWare Mobile Storage Host Controller core implements +the SD Host Controller Standard Simplified Specification, but +requires non-standard support for high clock rates. +.\" The +.\" .Nm +.\" driver is a wrapper around the +.\" .Xr sdhc 4 +.\" driver. +.Pp +The +.Xr sdmmc 4 +subsystem performs SD/MMC transactions to communicate with the +MMC/SD/SDIO devices connected to the controller. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sdhc 4 , +.Xr sdmmc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.4 . diff --git a/static/openbsd/man4/dwpcie.4 b/static/openbsd/man4/dwpcie.4 new file mode 100644 index 00000000..5b1dd208 --- /dev/null +++ b/static/openbsd/man4/dwpcie.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: dwpcie.4,v 1.3 2023/04/04 00:38:38 jsg Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 4 2023 $ +.Dt DWPCIE 4 +.Os +.Sh NAME +.Nm dwpcie +.Nd Synopsys DesignWare Host/PCIe bridge +.Sh SYNOPSIS +.Cd "dwpcie* at fdt?" +.Cd "pci* at dwpcie?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Synopsys DesignWare PCIe controller, +which is built into various SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/dwqe.4 b/static/openbsd/man4/dwqe.4 new file mode 100644 index 00000000..a07a3241 --- /dev/null +++ b/static/openbsd/man4/dwqe.4 @@ -0,0 +1,65 @@ +.\" $OpenBSD: dwqe.4,v 1.3 2023/10/11 12:57:53 stsp Exp $ +.\" +.\" Copyright (c) 2023 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 11 2023 $ +.Dt DWQE 4 +.Os +.Sh NAME +.Nm dwqe +.Nd Synopsys DesignWare Ethernet Quality-of-Service Controller +.Sh SYNOPSIS +.Cd "dwqe* at fdt?" +.Cd "dwqe* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various Ethernet controllers based on the +Synopsys DesignWare Ethernet Quality-of-Service Controller IP. +These controllers are found on Rockchip RK3566, RK3568, and RK3588 SoCs, +and on Intel Elkhart Lake SoCs. +.Pp +The +.Nm +driver supports several media types, which are selected via the +.Xr ifconfig 8 +command. +The supported media types are: +.Bl -tag -width "media" -offset indent +.It Cm media No autoselect +Attempt to autoselect the media type (default) +.It Cm media No 1000baseT Cm mediaopt No full-duplex +Use 1000baseT on copper, full duplex +.It Cm media No 1000baseT Cm mediaopt No half-duplex +Use 1000baseT on copper, half duplex +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Use 100baseTX, full duplex +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Use 100baseTX, half duplex +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 7.3 . diff --git a/static/openbsd/man4/dwxe.4 b/static/openbsd/man4/dwxe.4 new file mode 100644 index 00000000..22a887fd --- /dev/null +++ b/static/openbsd/man4/dwxe.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: dwxe.4,v 1.4 2024/08/11 08:25:12 dtucker Exp $ +.\" +.\" Copyright (c) 2016 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 11 2024 $ +.Dt DWXE 4 +.Os +.Sh NAME +.Nm dwxe +.Nd Allwinner EMAC 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "dwxe* at fdt?" +.Cd "rgephy*" at mii? +.Sh DESCRIPTION +The +.Nm +driver provides support for various Ethernet controllers based on the +Allwinner EMAC. +These controllers are found on the Allwinner A64/H3/H5/H6/H616 SoCs. +.Pp +The +.Nm +driver supports several media types, which are selected via the +.Xr ifconfig 8 +command. +The supported media types are: +.Bl -tag -width "media" -offset indent +.It Cm media No autoselect +Attempt to autoselect the media type (default) +.It Cm media No 1000baseT Cm mediaopt No full-duplex +Use 1000baseT on copper, full duplex +.It Cm media No 1000baseT Cm mediaopt No half-duplex +Use 1000baseT on copper, half duplex +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Use 100baseTX, full duplex +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Use 100baseTX, half duplex +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr rgephy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@openbsd.org . diff --git a/static/openbsd/man4/eap.4 b/static/openbsd/man4/eap.4 new file mode 100644 index 00000000..2583ae97 --- /dev/null +++ b/static/openbsd/man4/eap.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: eap.4,v 1.16 2008/06/26 05:42:06 ray Exp $ +.\" $NetBSD: eap.4,v 1.2 1998/05/06 19:14:06 augustss Exp $ +.\" +.\" Copyright (c) 1997 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt EAP 4 +.Os +.Sh NAME +.Nm eap +.Nd Ensoniq AudioPCI audio device +.Sh SYNOPSIS +.Cd "eap* at pci?" +.Cd "audio* at eap?" +.Cd "midi* at eap?" +.Sh DESCRIPTION +The +.Nm +driver supports the older Ensoniq AudioPCI and other ES1370 based +sound cards, such as the Creative Labs SoundBlaster PCI64 and PCI128. +The driver also supports many revisions of the more modern Ensoniq +AudioPCI 97 (ES1371), as well as the Ensoniq CT5880 and the Creative Labs +Ectiva 1938. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr midi 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.6 . +.Sh BUGS +The "FM" DAC is not supported. diff --git a/static/openbsd/man4/ec.4 b/static/openbsd/man4/ec.4 new file mode 100644 index 00000000..cbf64271 --- /dev/null +++ b/static/openbsd/man4/ec.4 @@ -0,0 +1,87 @@ +.\" $OpenBSD: ec.4,v 1.20 2008/09/07 06:55:34 jmc Exp $ +.\" $NetBSD: ec.4,v 1.4 1998/08/09 00:39:02 thorpej Exp $ +.\" +.\" Copyright (c) 1997 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 7 2008 $ +.Dt EC 4 +.Os +.Sh NAME +.Nm ec +.Nd 3Com EtherLink II (3c503) Ethernet device +.Sh SYNOPSIS +.Cd "ec0 at isa? port 0x250 iomem 0xd8000 irq 9" +.Sh DESCRIPTION +The +.Nm +device driver supports 3Com EtherLink II (3C503) Ethernet cards. +.Pp +The EtherLink II supports two media types on a single card. +All support the AUI media type. +The other media is either BNC or UTP behind a transceiver. +Software cannot differentiate between BNC and UTP cards. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width 10baseX -offset indent +.It 10base5 +Set 10base5 (thick-net) operation. +.It 10base2 +Set BNC (10base2/thin-net) or UTP operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by your card try +.Dq ifconfig media . +For example, +.Dq ifconfig ec0 media . +.Sh DIAGNOSTICS +.Bl -diag +.It "ec0: wildcarded IRQ is not allowed" +The IRQ was wildcarded in the kernel configuration file. +This is not supported. +.It "ec0: invalid IRQ , must be 3, 4, 5, or 9" +An IRQ other than the above listed IRQs was specified in the kernel +configuration file. +The EtherLink II hardware only supports the above listed IRQs. +.It "ec0: failed to clear shared memory at offset " +The memory test was unable to clear the interface's shared memory +region. +This often indicates that the card is configured at a conflicting +.Em iomem +address. +.El +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/eephy.4 b/static/openbsd/man4/eephy.4 new file mode 100644 index 00000000..a91d878d --- /dev/null +++ b/static/openbsd/man4/eephy.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: eephy.4,v 1.17 2019/09/24 14:39:43 visa Exp $ +.\" +.\"Copyright (c) 2001 by Parag Patel. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 24 2019 $ +.Dt EEPHY 4 +.Os +.Sh NAME +.Nm eephy +.Nd Marvell 88E1000/88E1011/88E1111/88E1545 Alaska Ethernet PHY +.Sh SYNOPSIS +.Cd "eephy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports Marvell 88E1000, 88E1011, 88E1111 and 88E1545 +10/100/1000 Ethernet PHYs. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/ef.4 b/static/openbsd/man4/ef.4 new file mode 100644 index 00000000..551a6d96 --- /dev/null +++ b/static/openbsd/man4/ef.4 @@ -0,0 +1,93 @@ +.\" $OpenBSD: ef.4,v 1.18 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 1998 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt EF 4 +.Os +.Sh NAME +.Nm ef +.Nd 3Com Fast EtherLink ISA (3c515) 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "ef* at isapnp?" +.Cd "nsphy* at mii?" +.Sh DESCRIPTION +The +.Nm +device driver supports the 3Com Fast EtherLink ISA family +of Ethernet cards, and embedded controllers based on the 3Com +.Dq corkscrew +EtherLink chips. +.Pp +The following media types and options (as given to +.Xr ifconfig 8 ) +are supported: +.Bl -tag -width xxx -offset indent +.It Cm media No autoselect +Enable autoselection of the media type and options (default). +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Set 100Mbps (Fast Ethernet) operation and force full-duplex mode. +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Set 100Mbps (Fast Ethernet) operation and force half-duplex mode. +.It Cm media No 10baseT Cm mediaopt No full-duplex +Set 10Mbps operation and force full-duplex. +.It Cm media No 10baseT Cm mediaopt No half-duplex +Set 10Mbps operation and force half-duplex. +.El +.Pp +If no media options are present, the +.Nm +driver places the card into autoselect mode. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "ef0: adapter failure (XXXX)" +A fatal error during receive or transmit has occurred. +.It "ef0: eeprom failed to come ready" +When reading/writing the EEPROM, the busy bit failed to clear. +This may indicate a hardware problem. +.It "ef0: device timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.El +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isapnp 4 , +.Xr nsphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 2.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Jason L. Wright Aq Mt jason@thought.net . diff --git a/static/openbsd/man4/efi.4 b/static/openbsd/man4/efi.4 new file mode 100644 index 00000000..f34d22e7 --- /dev/null +++ b/static/openbsd/man4/efi.4 @@ -0,0 +1,102 @@ +.\" $OpenBSD: efi.4,v 1.3 2024/05/05 19:13:13 kn Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" Copyright (c) 2024 Klemens Nanni +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 5 2024 $ +.Dt EFI 4 +.Os +.Sh NAME +.Nm efi +.Nd Unified Extensible Firmware Interface +.Sh SYNOPSIS +.Cd "# amd64" +.Cd "efi* at bios?" +.Pp +.Cd "# arm64" +.Cd "efi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for EFI runtime services offered by UEFI +firmware implementations. +It can read and write the Real Time Clock and provides userland applications +.Xr ioctl 2 +access to the System Resource Table and to read and write variables. +.Sh IOCTLS +.Nm +supports the following +.Xr ioctl 2 +commands, available through +.In dev/efi/efi.h +.In dev/efi/efiio.h : +.Bl -tag -width xxxx +.It Dv EFIIOC_GET_TABLE Fa "struct efi_get_table_ioc *" +.Bd -literal +struct efi_get_table_ioc { + void *buf; /* Pointer to userspace buffer */ + struct uuid uuid; /* UUID to look up */ + size_t table_len; /* Table size */ + size_t buf_len; /* Size of the buffer */ +}; +.Ed +.Pp +Read a table. +.It Dv EFIIOC_VAR_GET Fa "struct efi_var_ioc *" +.Bd -literal +struct efi_var_ioc { + uint16_t *name; /* User pointer to name, in UCS2 chars */ + size_t namesize; /* Number of *bytes* in the name + including terminator */ + struct uuid vendor; /* Vendor's UUID for variable */ + uint32_t attrib; /* Attributes */ + void *data; /* User pointer to value */ + size_t datasize; /* Number of *bytes* in the value */ +}; +.Ed +.Pp +Read a variable. +.It Dv EFIIOC_VAR_NEXT Fa "struct efi_var_ioc *" +Enumerate all variables. +The first command must use the empty name. +Further ones must denote the previous variable's name and UUID. +.It Dv EFIIOC_VAR_SET Fa "struct efi_var_ioc *" +Write a variable. +Delete it if +.Va datasize +is zero. +.El +.Sh FILES +.Bl -tag -width /dev/efi -compact +.It Pa /dev/efi +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared for arm64 in +.Ox 6.3 . +Support for amd64, the ESRT and EFI variables appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +Support for the ESRT and EFI variables is heavily based on work done by +.An Sergii Dmytruk Aq Mt sergii.dmytruk@3meb.com . diff --git a/static/openbsd/man4/eg.4 b/static/openbsd/man4/eg.4 new file mode 100644 index 00000000..19e053b1 --- /dev/null +++ b/static/openbsd/man4/eg.4 @@ -0,0 +1,65 @@ +.\" $OpenBSD: eg.4,v 1.10 2013/06/02 20:23:33 tedu Exp $ +.\" $NetBSD: ec.4,v 1.4 1998/08/09 00:39:02 thorpej Exp $ +.\" +.\" Copyright (c) 1997 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 2 2013 $ +.Dt EG 4 +.Os +.Sh NAME +.Nm eg +.Nd 3Com EtherLink Plus Ethernet (3c505) Ethernet device +.Sh SYNOPSIS +.Cd "eg0 at isa? port 0x310 irq 5" +.Sh DESCRIPTION +The +.Nm +device driver supports 3Com EtherLink Plus (3c505) Ethernet cards. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by your card try +.Dq ifconfig media . +For example, +.Dq ifconfig eg0 media . +.Sh DIAGNOSTICS +.Bl -diag +.It "eg0: device timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.It "eg0: invalid packet size N; dropping" +A packet of an invalid length (less than size of Ethernet header or greater +than maximum size of Ethernet frame) was received and dropped. +.El +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/ehci.4 b/static/openbsd/man4/ehci.4 new file mode 100644 index 00000000..e5094041 --- /dev/null +++ b/static/openbsd/man4/ehci.4 @@ -0,0 +1,75 @@ +.\" $OpenBSD: ehci.4,v 1.15 2021/12/29 18:44:52 patrick Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 29 2021 $ +.Dt EHCI 4 +.Os +.Sh NAME +.Nm ehci +.Nd USB Enhanced Host Controller Interface +.Sh SYNOPSIS +.Cd "ehci* at acpi?" +.Cd "ehci* at cardbus?" +.Cd "ehci* at fdt?" +.Cd "ehci* at pci?" +.Cd "usb* at ehci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the USB Enhanced Host Controller Interface, +which provides an interface to +.Xr usb 4 +devices. +.Pp +EHCI controllers are peculiar in that they can only handle the USB 2.0 +protocol. +This means that they normally have one or more companion controllers +(i.e., +.Xr ohci 4 +or +.Xr uhci 4 ) +or an internal rate-matching hub to handle USB 1.x devices. +.Pp +If at least one companion controller is present, each USB connector is +electrically connected to two USB controllers. +The handling of this is totally automatic, +but can be noticed since USB 1.x and USB 2.0 devices plugged in to the same +connector appear to connect to different USB buses. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr cardbus 4 , +.Xr ohci 4 , +.Xr pci 4 , +.Xr uhci 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver has been available since +.Ox 3.6 . diff --git a/static/openbsd/man4/eisa.4 b/static/openbsd/man4/eisa.4 new file mode 100644 index 00000000..43568e4a --- /dev/null +++ b/static/openbsd/man4/eisa.4 @@ -0,0 +1,111 @@ +.\" $OpenBSD: eisa.4,v 1.23 2020/01/10 01:13:19 jsg Exp $ +.\" $NetBSD: eisa.4,v 1.10 2001/09/11 22:52:52 wiz Exp $ +.\" +.\" Copyright (c) 1997 Jonathan Stone +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgements: +.\" This product includes software developed by Jonathan Stone +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 10 2020 $ +.Dt EISA 4 +.Os +.Sh NAME +.Nm eisa +.Nd introduction to EISA bus support +.Sh SYNOPSIS +Machine-dependent; depends on the bus topology and +.Tn EISA +bus interface of your system. +Typical +.Tn EISA +buses are either connected directly +to the main system bus, or via an +.Tn PCI +to +.Tn EISA +bridge. +See the +.Xr intro 4 +documentation for your system for details. +.Sh DESCRIPTION +.Ox +includes a machine-independent +.Tn EISA +bus subsystem and several machine-independent +.Tn EISA +device drivers. +.Pp +.Ox +provides support for the following devices. +Note that not all architectures support all devices. +.Ss Disk and tape controllers +.Bl -tag -width 12n -offset ind -compact +.It Xr cac 4 +Compaq Smart Array 2/3/4 SCSI RAID controller +.El +.Ss SCSI interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr ahc 4 +Adaptec VL/EISA/PCI SCSI interface +.It Xr uha 4 +Ultrastor SCSI interface +.El +.Ss Network interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr ep 4 +3Com EtherLink III and Fast EtherLink III 10/100 Ethernet device +.\" .It Xr le 4 +.\" Digital DE422 +.\" .Tn Ethernet +.\" interfaces. +.\" .It Xr tlp 4 +.\" Digital DE425 +.\" .Tn Ethernet +.\" interfaces. +.El +.Pp +Note that most or all +.Tn EISA +devices also have +.Tn PCI +or +.Tn ISA +equivalents. +These are listed in +.Xr pci 4 , +.Xr isa 4 , +or +.Xr isapnp 4 , +respectively. +The manual pages for each individual driver also lists the +supported bus variants. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The machine-independent +.Tn EISA +subsystem appeared in +.Ox 1.2 . diff --git a/static/openbsd/man4/el.4 b/static/openbsd/man4/el.4 new file mode 100644 index 00000000..7e4d8edc --- /dev/null +++ b/static/openbsd/man4/el.4 @@ -0,0 +1,65 @@ +.\" $OpenBSD: el.4,v 1.10 2013/06/02 20:23:33 tedu Exp $ +.\" $NetBSD: ec.4,v 1.4 1998/08/09 00:39:02 thorpej Exp $ +.\" +.\" Copyright (c) 1997 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 2 2013 $ +.Dt EL 4 +.Os +.Sh NAME +.Nm el +.Nd 3Com EtherLink (3C501) Ethernet device +.Sh SYNOPSIS +.Cd "el0 at isa? port 0x300 irq 9" +.Sh DESCRIPTION +The +.Nm +device driver supports 3Com EtherLink (3C501) Ethernet cards. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by your card try +.Dq ifconfig media . +For example, +.Dq ifconfig el0 media . +.Sh DIAGNOSTICS +.Bl -diag +.It "el0: device timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.It "el0: invalid packet size N; dropping" +A packet of an invalid length (less than size of Ethernet header or greater +than maximum size of Ethernet frame) was received and dropped. +.El +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/em.4 b/static/openbsd/man4/em.4 new file mode 100644 index 00000000..487e0584 --- /dev/null +++ b/static/openbsd/man4/em.4 @@ -0,0 +1,228 @@ +.\" $OpenBSD: em.4,v 1.55 2021/09/08 20:29:21 jmc Exp $ +.\" Copyright (c) 2002 Intel Corporation +.\" All rights reserved. +.\" Redistribution and use in source and binary forms of the Software, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code of the Software may retain the above +.\" copyright notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form of the Software may reproduce the +.\" above copyright notice, this list of conditions and the following +.\" disclaimer in the documentation and/or other materials provided with the +.\" distribution. +.\" 3. Neither the name of the Intel Corporation nor the names of its contributors +.\" shall be used to endorse or promote products derived from this Software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" +.\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE INTEL OR ITS CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER +.\" CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE +.\" USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" * Other names and brands may be claimed as the property of others. +.\" +.\" $FreeBSD: em.4,v 1.18 2005/01/30 12:29:06 yar Exp $ +.Dd $Mdocdate: September 8 2021 $ +.Dt EM 4 +.Os +.Sh NAME +.Nm em +.Nd Intel PRO/1000 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "em* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI, PCI-X and PCI Express Gigabit Ethernet adapters +based on the Intel 82540EM, 82540EP, 82541EI, 82541ER, 82541GI, 82541PI, 82542, +82543GC, 82544EI, 82544GC, 82545EM, 82545GM, 82546EB, 82546GB, 82547EI, 82547GI, +82562V, 82563EB, 82564EB, 82566DC, 82566DM, 82571EB, 82571GB, 82572EI, 82572GI, +82573E, 82573L, 82573V, 82574L, 82575EB, 82575GB, 82576EB, 82577LC, 82577LM, +82578DC, 82578DM, 82579LM, 82579V, 82580DB, 82580EB, 82583V, I210, I211, I217, +I218, I219, I350, I354 +Ethernet controller chips and the embedded chips found on EP80579 platform, +including the following: +.Pp +.Bl -item -offset indent -compact +.It +Axiomtek NA-200 EP80579 based board +.It +HP ProLiant NC110T PCI Express Gigabit NIC +.It +HP ProLiant NC112T PCI Express Gigabit NIC +.It +HP ProLiant NC310F PCI-X Gigabit NIC (SX Fiber) +.It +HP ProLiant NC340T PCI-X Quad Port Gigabit NIC +.It +HP ProLiant NC360T PCI Express Dual Port Gigabit NIC +.It +HP ProLiant NC364T PCI Express Quad Port Gigabit NIC +.It +HP ProLiant NC365T PCI Express Quad Port Gigabit NIC +.It +HP ProLiant NC6132 Upgrade Module (SX Fiber) +.It +HP ProLiant NC6133 Upgrade Module (LX Fiber) +.It +HP ProLiant NC6134 PCI Gigabit NIC (SX Fiber) +.It +HP ProLiant NC6136 PCI Gigabit NIC (SX Fiber) +.It +HP ProLiant NC6170 PCI-X Gigabit NIC (SX Fiber) +.It +HP ProLiant NC7131 PCI Gigabit NIC +.It +HP ProLiant NC7132 Upgrade Module +.It +HP ProLiant NC7170 PCI-X Dual Port Gigabit NIC +.It +HP ProLiant NC7170LP PCI-X Dual Port Gigabit NIC +.It +Intel PRO/1000 Gigabit Server Adapter (SX Fiber) (PWLA8490) +.It +Intel PRO/1000F Gigabit Server Adapter (SX Fiber) (PWLA8490SX) +.It +Intel PRO/1000T Server Adapter (PWLA8490T) +.It +Intel PRO/1000XT Server Adapter (PWLA8490XT) +.It +Intel PRO/1000XS Server Adapter (SX Fiber) (PWLA8490XF) +.It +Intel PRO/1000T Desktop Adapter (PWLA8390T) +.It +Intel PRO/1000XTL Low Profile PCI Server (PWLA8490XTL) +.It +Intel PRO/1000MT Desktop Adapter (PWLA8390MT) +.It +Intel PRO/1000MT Server Adapter (PWLA8490MT) +.It +Intel PRO/1000MT Dual Port Server Adapter (PWLA8492MT) +.It +Intel PRO/1000MF Server Adapter (SX Fiber) (PWLA8490MF) +.It +Intel PRO/1000MF Dual Port Server Adapter (SX Fiber) (PWLA8492MF) +.It +Intel PRO/1000MF Server Adapter (LX Fiber) (PWLA8490LX) +.It +Intel PRO/1000MT Quad PCI-X Adapter (PWLA8494MT) +.It +Intel PRO/1000GT Quad PCI-X Adapter (PWLA8494GT) +.It +Intel PRO/1000PT Desktop Adapter +.It +Intel PRO/1000PT Server Adapter +.It +Intel PRO/1000PT Dual Port Server Adapter +.It +Intel PRO/1000PT Quad Port Server Adapter +.It +Intel PRO/1000PF Server Adapter (SX Fiber) +.It +Intel PRO/1000PF Dual Port Server Adapter (SX Fiber) +.It +Intel PRO/1000ET Dual Port Server Adapter +.It +Intel PRO/1000ET Quad Port Server Adapter +.It +Intel PRO/1000EF Quad Port Server Adapter (SX Fiber) +.It +Intel I340-T4 PCI Express Quad Port Gigabit NIC +.It +Intel I350-T2 PCI Express Dual Port Gigabit NIC +.It +Intel I350-T4 PCI Express Quad Port Gigabit NIC +.It +Soekris Engineering lan1841 +.It +Sun PCI-E Dual Gigabit Ethernet LP UTP Adapter +.It +Sun PCI-E Dual Gigabit Ethernet LP MMF Adapter +.It +Sun PCI-E Dual Gigabit Ethernet EM UTP Adapter +.It +Sun PCI-E Dual Gigabit Ethernet EM MMF Adapter +.It +Sun PCI-E Dual Gigabit Ethernet ExpressModule +.It +Sun x4 PCI-E Quad Gigabit Ethernet LP UTP Adapter +.It +Sun x4 PCI-E Quad Gigabit Ethernet ExpressModule +.It +Sun x8 PCI-E Quad Gigabit Ethernet ExpressModule +.It +Supermicro AOC-SG-i2 Dual Port Server Adapter +.It +Supermicro AOC-PG-I2+ Dual Port Server Adapter +.El +.Pp +The +.Nm +driver supports IPv4 receive IP/TCP/UDP checksum offload and transmit TCP/UDP +checksum offload on all but 82542-based adapters, VLAN tag insertion and +stripping, and jumbo frames on all but 82562V, 82566DC/82566DM and +82573E/82573L/82573V-based adapters. +The 82562V Ethernet controller chip only supports 10/100 media types. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width autoselect -offset indent +.It autoselect +Enables auto-negotiation for speed and duplex. +.It 10baseT Cm mediaopt No full-duplex +Sets 10Mbps operation. +.It 100baseTX Cm mediaopt No full-duplex +Sets 100Mbps operation. +.It 1000baseLX +Sets 1000Mbps operation. +Only full-duplex mode is supported at this speed. +.It 1000baseSX +Sets 1000Mbps operation. +Only full-duplex mode is supported at this speed. +.It 1000baseT +Sets 1000Mbps operation. +Only full-duplex mode is supported at this speed. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr gcu 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Intel Corporation . +.Sh BUGS +There are known performance issues with this driver when running UDP traffic +with jumbo frames. +.Pp +There is a known compatibility issue where time to link is slow or link is not +established between 82541/82547 controllers and some switches. +Known switches include: +.Pp +.Bl -item -offset indent -compact +.It +I-O Data ETG-SH8 +.It +Planex FXG-08TE +.El diff --git a/static/openbsd/man4/emc.4 b/static/openbsd/man4/emc.4 new file mode 100644 index 00000000..3876d209 --- /dev/null +++ b/static/openbsd/man4/emc.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: emc.4,v 1.2 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2011 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt EMC 4 +.Os +.Sh NAME +.Nm emc +.Nd EMC CLARiiON AX/CX-series SCSI devices +.Sh SYNOPSIS +.Cd "emc* at scsibus?" +.Sh DESCRIPTION +The +.Nm +driver attaches to EMC CLARiiON AX/CX-series SCSI logical units. +Each path to an active service processor attached to by +.Nm +is presented to +.Xr mpath 4 +which uses it as a backend to the logical unit attached to its own +.Xr scsibus 4 . +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr intro 4 , +.Xr mpath 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.0 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/emu.4 b/static/openbsd/man4/emu.4 new file mode 100644 index 00000000..2cb76453 --- /dev/null +++ b/static/openbsd/man4/emu.4 @@ -0,0 +1,110 @@ +.\" $OpenBSD: emu.4,v 1.18 2013/07/16 16:05:48 schwarze Exp $ +.\" $NetBSD: emuxki.4,v 1.1 2001/10/18 18:40:16 jdolecek Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt EMU 4 +.Os +.Sh NAME +.Nm emu +.Nd Creative Labs SBLive!, PCI 512, and Audigy audio device +.Sh SYNOPSIS +.Cd "emu* at pci?" +.Cd "audio* at emu?" +.Sh DESCRIPTION +The +.Nm +device driver supports Creative Labs SoundBlaster Live!, +Sound Blaster PCI 512, +and SoundBlaster Audigy cards. +.Pp +These Environmental Audio cards are based upon the programmable EMU10K1 +digital-processing chip. +.Pp +Hardware features: +.Bl -bullet -offset indent +.It +E-mu Systems, Inc. EMU10K1 music synthesis engine +.It +64-voice hardware polyphony with E-mu's patented 8-point interpolation +technology +.It +Up to 1024-voice polyphony with multi-timbre capability +.It +Support for real-time digital effects like reverb, chorus, flanger, pitch +shifter, or distortion across any audio source +.It +User-selectable settings are optimized for headphones, two or four speakers +.It +Processes sample rates from 5kHz to 48kHz +.It +Creative Multi Speaker Surround (CMSS) places any mono or stereo sound +source in a 360 degree audio space +.It +Hardware full-duplex support enables simultaneous record and playback +at 8 standard sample rates +.It +Allows multiple audio sources playback on the same speaker system +.El +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr joy 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 3.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Yannick Montulet Aq Mt yannick.montulet@epitech.net +and ported to +.Ox 3.1 +by +.An Michael Shalayeff Aq Mt mickey@openbsd.org . +.Sh CAVEATS +ATTENTION! +.Pp +The hardware interface of this card contains registers not used +for normal operation, but potentially dangerous +and not possible to disable. +Potential damage ranges from frying the card to frying +motherboard or external equipment connected to its outputs. +.Sh BUGS +Currently this driver does not support MIDI, joystick input, +or the multi-voice capability. +.Pp +There is currently no way to control the volume of the DAC for +SoundBlaster Audigy cards. +.Pp +S-PDIF digital output does not work for +SoundBlaster Live! and +SoundBlaster Audigy cards. diff --git a/static/openbsd/man4/enc.4 b/static/openbsd/man4/enc.4 new file mode 100644 index 00000000..66a58e32 --- /dev/null +++ b/static/openbsd/man4/enc.4 @@ -0,0 +1,161 @@ +.\" $OpenBSD: enc.4,v 1.30 2020/02/15 22:19:51 kn Exp $ +.\" +.\" Copyright (c) 2006 Jason McIntyre +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 15 2020 $ +.Dt ENC 4 +.Os +.Sh NAME +.Nm enc +.Nd encapsulating interface +.Sh SYNOPSIS +.Cd "pseudo-device enc" +.Sh DESCRIPTION +The +.Nm +interface is a virtual interface for +.Xr ipsec 4 +traffic. +It allows packet filtering using +.Xr pf 4 ; +prior to encapsulation and after decapsulation, +packets may be monitored using +.Xr tcpdump 8 . +.Pp +An +.Nm +interface can be created at runtime using the +.Ic ifconfig enc Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The +.Nm enc0 +interface will always exist and cannot be destroyed using +.Xr ifconfig 8 . +.Pp +Packet filtering is documented in greater detail in +.Xr pf.conf 5 , +however some details relevant to filtering on the +.Nm +interface are documented below. +.Pp +Firstly, +.Xr pf 4 +is a stateful packet filter, +which means it can track the state of a connection. +It does this +.Em automatically . +States are normally +.Em floating , +which means they can match packets on any interface. +However this is a potential problem for filtering IPsec traffic: +states need to be interface bound, +to avoid permitting unencrypted traffic +should the SAs expire and not be replaced. +Therefore all rules on the +.Nm +interface should explicitly set +.Dq keep state (if-bound) . +For example: +.Bd -literal -offset indent +pass in on enc0 proto ipencap from 172.25.0.45 to 1.2.3.4 \e + keep state (if-bound) +.Ed +.Pp +Secondly, the +.Nm +interface does not directly support bandwidth control via +.Xr pf 4 +queueing. +Instead, IPsec packets must be tagged and the tagged packets +are assigned to queues. +.Xr ipsec.conf 5 +provides an example of tag-based queueing +and further information on packet tagging. +.Pp +Finally, +the use of translation rules to map and redirect network traffic +requires some care. +Packets destined to be IPsec processed are seen by the +filter/translation engine twice, +both before and after being IPsec processed. +If a packet's translated address +on the way back fails to match an existing IPsec flow, +from the translated address to the original source address, +it will be discarded by the filter. +It is best to avoid this situation where possible, +though a flow may be explicitly created to work around it. +.Pp +As noted above, +.Xr tcpdump 8 +may be invoked on the +.Nm +interface to see packets prior to encapsulation and after decapsulation. +For example: +.Bd -literal -offset 3n +# tcpdump -envps 1500 -i enc0 -l | grep 10.0.0.33 +tcpdump: listening on enc0, link-type ENC +15:05:08.934708 (authentic,confidential): SPI 0x6bcac587: \e + 172.25.0.45 > 1.2.3.4: 10.9.9.28.7001 > 10.0.0.33.7000: \e + [udp sum ok] udp 52 (ttl 64, id 5672, len 80) \e + (ttl 64, id 30009, len 100, bad cksum 0!) +15:05:09.063517 (authentic,confidential): SPI 0x4b70c05a: \e + 1.2.3.4 > 172.25.0.45: 10.0.0.33.7000 > 10.9.9.28.7001: \e + [udp sum ok] udp 156 (ttl 63, id 14880, len 184) \e + (ttl 51, id 19689, len 204) +.Ed +.Pp +The packets above show (for each direction): +date, ESP (not AH), SPI, direction, and encapsulated part. +The first packet is headed from 172.25.0.45 to 1.2.3.4 +and the encapsulated part from 10.9.9.28 to 10.0.0.33. +.Pp +Negotiations can be watched on the physical interface too: +.Bd -literal -offset 3n +# tcpdump -envps 1500 -i wi0 port 500 or port 4500 +tcpdump: listening on wi0, link-type EN10MB +15:15:58.188747 0:2:6f:3a:3f:3e 0:10:f3:3:bd:8a 0800 226: \e + 172.25.0.45.500 > 1.2.3.4.500: [udp sum ok] \e +[...] + attribute ENCRYPTION_ALGORITHM = AES_CBC + attribute HASH_ALGORITHM = SHA + attribute AUTHENTICATION_METHOD = RSA_SIG + attribute GROUP_DESCRIPTION = MODP_1024 + attribute LIFE_TYPE = SECONDS + attribute LIFE_DURATION = 3600 + attribute KEY_LENGTH = 128 +[...] +15:15:59.080058 0:10:f3:3:bd:8a 0:2:6f:3a:3f:3e 0800 226: \e + 1.2.3.4.500 > 172.25.0.45.500: [udp sum ok] \e +[...] + attribute ENCRYPTION_ALGORITHM = AES_CBC + attribute HASH_ALGORITHM = SHA + attribute AUTHENTICATION_METHOD = RSA_SIG + attribute GROUP_DESCRIPTION = MODP_1024 + attribute LIFE_TYPE = SECONDS + attribute LIFE_DURATION = 3600 + attribute KEY_LENGTH = 128 +[...] +.Ed +.Pp +The attribute lines for the negotiation must match. +.Sh SEE ALSO +.Xr ipsec 4 , +.Xr pf 4 , +.Xr ipsec.conf 5 , +.Xr pf.conf 5 , +.Xr tcpdump 8 diff --git a/static/openbsd/man4/endrun.4 b/static/openbsd/man4/endrun.4 new file mode 100644 index 00000000..daf2d47e --- /dev/null +++ b/static/openbsd/man4/endrun.4 @@ -0,0 +1,82 @@ +.\" $OpenBSD: endrun.4,v 1.3 2015/01/15 00:48:10 deraadt Exp $ +.\" +.\" Copyright (c) 2008 Marc Balmer +.\" Copyright (c) 2009 Kevin Steves +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt ENDRUN 4 +.Os +.Sh NAME +.Nm endrun +.Nd EndRun Technologies native time-of-day message timedelta sensor +.Sh SYNOPSIS +.Cd "pseudo-device endrun" Op Ar count +.Sh DESCRIPTION +This line discipline interfaces serial EndRun Technologies devices. +.Pp +The line discipline is enabled by the following sequence: +.Bd -literal -offset indent +#include +int ldisc = ENDRUNDISC, fildes; ... +ioctl(fildes, TIOCSETD, &ldisc); +.Ed +.Pp +The byte stream is unaltered by the line discipline which +maintains a timedelta sensor using the EndRun data. +The timedelta sensor will appear as endrun* in the list of sensors and the delta +(in nanoseconds) between the received time information and the local time can +be accessed through the +.Xr sysctl 8 +interface. +.Sh SENSOR STATES +The quality of the timedelta is reported as the sensor status: +.Bl -tag -width "CRITICALXX" -offset indent +.It OK +The time information is valid. +The timedelta is safe to use for applications like +.Xr ntpd 8 . +.It WARN +The attached receiver has been indicating a warning condition +for at least the last ten minutes. +The timedelta should be used with care. +.It CRITICAL +tty timestamping has been turned on but there is no PPS signal present or the +receiver indicated a warning condition for at least the last twenty minutes. +Check your hardware. +.El +.Pp +The status of a second sensor is used to report the status of the +device itself using the Time Figure Of Merit (TFOM) character: +.Bl -tag -width "CRITICALXX" -offset indent +.It OK +The clock is synchronized. +TFOM is 6-8. +.It WARN +The clock is synchronized and the time error is greater +than 10ms or the clock is in the unsynchronized state. +TFOM is 9. +.It CRITICAL +The TFOM is invalid. +.El +.Sh SEE ALSO +.Xr tty 4 , +.Xr ldattach 8 , +.Xr ntpd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +interface first appeared in +.Ox 4.6 . diff --git a/static/openbsd/man4/envy.4 b/static/openbsd/man4/envy.4 new file mode 100644 index 00000000..95c2c75d --- /dev/null +++ b/static/openbsd/man4/envy.4 @@ -0,0 +1,132 @@ +.\" $OpenBSD: envy.4,v 1.17 2020/05/17 05:48:39 ratchov Exp $ +.\" +.\" Copyright (c) 2007 Alexandre Ratchov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 17 2020 $ +.Dt ENVY 4 +.Os +.Sh NAME +.Nm envy +.Nd VIA Envy24 audio device +.Sh SYNOPSIS +.Cd "envy* at pci?" +.Cd "audio* at envy?" +.Cd "midi* at envy?" +.Sh DESCRIPTION +The +.Nm +driver supports sound cards based on VIA Envy24 and Envy24HT PCI chips. +The following sound cards are currently supported: +.Pp +.Bl -bullet -compact -offset indent +.It +Dynex DX-SC51 +.It +ESI Julia +.It +M-Audio Delta 1010, 1010LT, 66 and 44 +.It +M-Audio Audiophile 2496 +.It +M-Audio Revolution 5.1 +.It +M-Audio Audiophile 192k +.It +Terratec EWX 24/96 +.It +VIA Tremor 5.1 +.El +.Ss Mixer device +The chip features a digital mixer that routes and mixes the +streams below as follows: +.Bl -tag -width playback +.It Dv inputs +There are 8 streams corresponding to data received by the +device from the codecs. +They are labelled +.Va line0 +\(en +.Va line7 . +.It Dv outputs +There are 8 streams corresponding to data sent by the device to the codecs. +They are labelled +.Va line0 +\(en +.Va line7 . +Each of them can be individually configured to use any of +the external inputs or its corresponding playback stream as source. +Additionally, outputs +.Va line0 +and +.Va line1 +can be configured to use +.Va mon0 +or +.Va mon1 +as sources. +.It Dv monitor +There are 2 streams that can be configured to contain any linear +superposition of any of the 10 playback and 10 external input streams. +They are labelled +.Va mon0 +and +.Va mon1 . +From the mixer's point of view they are input streams, +so they can be used as sources of output streams. +This feature is specific to Envy24 based cards. +.It Dv playback +There are 10 streams corresponding to samples transferred +from the host to the device. +They are labelled +.Va play0 +\(en +.Va play9 . +From the mixer's point of view they are input streams, +so they are usable as sources of output streams. +.It Dv record +There are 12 streams corresponding to samples transferred +from the device to the host. +They are not controllable by the mixer. +Streams 0 to 7 are hardwired to external inputs +.Va line0 +\(en +.Va line7 +and streams 10 and 11 are hardwired to +.Va mon0 +and +.Va mon1 . +.El +.Ss Playback and record data formats +Both playback and record use linear encoding. +Samples are represented by 32-bit signed numbers in little endian order. +Only the first 24 most significant bits are used. +On Envy24-based cards, playback uses 10 channels and record uses 12 channels, +while on Envy24HT-based cards the number of streams depend on the +number of codecs physically present on the card. +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 , +.Xr midi 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh BUGS +S/PDIF transmitter/receiver is not supported. +.Pp +Ring buffer sizes are limited to 64kB, +which can be limiting at high sample rates. diff --git a/static/openbsd/man4/eoip.4 b/static/openbsd/man4/eoip.4 new file mode 100644 index 00000000..30d0462a --- /dev/null +++ b/static/openbsd/man4/eoip.4 @@ -0,0 +1,209 @@ +.\" $OpenBSD: eoip.4,v 1.8 2023/07/26 20:23:22 jmc Exp $ +.\" $NetBSD: gre.4,v 1.10 1999/12/22 14:55:49 kleink Exp $ +.\" +.\" Copyright 1998 (c) The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Heiko W. Rupp +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 26 2023 $ +.Dt EOIP 4 +.Os +.Sh NAME +.Nm eoip +.Nd MikroTik Ethernet over IP tunnel network device +.Sh SYNOPSIS +.Cd "pseudo-device gre" +.Sh DESCRIPTION +The +.Nm +interface provides tunnelling of Ethernet frames across +IPv4 and IPv6 networks using the +MikroTik Ethernet over IP (EoIP) encapsulation protocol. +.Pp +The protocol is based on the Generic Routing and Encapsulation (GRE) +protocol. +GRE datagrams (IP protocol number 47) consist of a GRE header +and an outer IP header for encapsulating another protocol's datagram. +The GRE header specifies a version and the type of the encapsulated datagram, +allowing for the tunnelling of multiple protocols. +EoIP uses GRE version 1, its own protocol identifier (0x6400) +for Ethernet, and has its own keepalive semantics, +making it distinct from the Ethernet over GRE version 0 protocol +supported by +.Xr egre 4 . +However, it is implemented as part of the same driver providing +.Xr egre 4 . +.Pp +Different tunnels between the same endpoints are distinguished +by a 16-bit tunnel identifier field in the header. +.Pp +All GRE packet processing in the system is allowed or denied by setting the +.Va net.inet.gre.allow +.Xr sysctl 8 +variable. +To allow GRE packet processing, set +.Va net.inet.gre.allow +to 1. +.Pp +.Nm +interfaces can be created at runtime using the +.Ic ifconfig eoip Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +.Pp +For correct operation, encapsulated traffic must not be routed +over the interface itself. +This can be implemented by adding a distinct or a more specific +route to the tunnel destination than the hosts or networks routed +via the tunnel interface. +Alternatively, the tunnel traffic may be configured in a separate +routing table to the encapsulated traffic. +.Ss Programming Interface +.Nm +interfaces support the following +.Xr ioctl 2 +calls for configuring tunnel options: +.Bl -tag -width indent -offset 3n +.It Dv SIOCSLIFPHYADDR Fa "struct if_laddrreq *" +Set the unicast IPv4 or IPv6 addresses for the encapsulating IP packets. +The addresses may only be configured while the interface is down. +.It Dv SIOCGLIFPHYADDR Fa "struct if_laddrreq *" +Get the addresses used for the encapsulating IP packets. +.It Dv SIOCDIFPHYADDR Fa "struct ifreq *" +Clear the addresses used for the encapsulating IP packets. +The addresses may only be cleared while the interface is down. +.It Dv SIOCSVNETID Fa "struct ifreq *" +Configure a virtual network identifier for use as the Tunnel Identifier. +The virtual network identifier may only be configured while the +interface is down. +The Tunnel Identifier is a 16-bit value. +.It Dv SIOCGVNETID Fa "struct ifreq *" +Get the virtual network identifier used in the GRE Key header. +.It Dv SIOCSLIFPHYRTABLE Fa "struct ifreq *" +Set the routing table the tunnel traffic operates in. +The routing table may only be configured while the interface is down. +.It Dv SIOCGLIFPHYRTABLE Fa "struct ifreq *" +Get the routing table the tunnel traffic operates in. +.It Dv SIOCSLIFPHYTTL Fa "struct ifreq *" +Set the Time-To-Live field in IPv4 encapsulation headers, or the +Hop Limit field in IPv6 encapsulation headers. +.It Dv SIOCGLIFPHYTTL Fa "struct ifreq *" +Get the value used in the Time-To-Live field in an IPv4 encapsulation +header or the Hop Limit field in an IPv6 encapsulation header. +.It Dv SIOCSLIFPHYDF Fa "struct ifreq *" +Configure whether the tunnel traffic sent by the interface can be +fragmented or not. +This sets the Don't Fragment (DF) bit on IPv4 packets, +and disables fragmentation of IPv6 packets. +.It Dv SIOCGLIFPHYDF Fa "struct ifreq *" +Get whether the tunnel traffic sent by the interface can be fragmented +or not. +.It Dv SIOCSTXHPRIO Fa "struct ifreq *" +Set the priority value used in the Type of Service field in IPv4 +headers, or the Traffic Class field in IPv6 headers. +Values may be from 0 to 7, or +.Dv IF_HDRPRIO_PACKET +to specify that the current priority of a packet should be used. +.It Dv SIOCGTXHPRIO Fa "struct ifreq *" +Get the priority value used in the Type of Service field in IPv4 +headers, or the Traffic Class field in IPv6 headers. +.It Dv SIOCSETKALIVE Fa "struct ifkalivereq *" +Enable the transmission of keepalive packets to detect tunnel failure. +Keepalives may only be configured while the interface is down. +.Pp +Setting the keepalive period or count to 0 disables keepalives on +the tunnel. +.It Dv SIOCGETKALIVE Fa "struct ifkalivereq *" +Get the configuration of keepalive packets. +.El +.Ss Security Considerations +EoIP does not provide any integrated security features. +It should only be deployed on trusted private networks, +or protected with IPsec to add authentication and encryption for +confidentiality. +IPsec is especially recommended when transporting EoIP over the +public internet. +.Pp +The Packet Filter +.Xr pf 4 +can be used to filter tunnel traffic with endpoint policies +.Xr pf.conf 5 . +.Pp +The Time-to-Live (TTL) value of a tunnel can be set to 1 or a low +value to restrict the traffic to the local network: +.Bd -literal -offset indent +# ifconfig eoipN tunnelttl 1 +.Ed +.Sh EXAMPLES +.Bd -literal +Host X ---- Host A ------------ tunnel ----------- MikroTik D --- Host E + \e / + \e / + +------ Host B ------ Host C ------+ +.Ed +.Pp +On Host A +.Pq Ox : +.Bd -literal -offset indent +# route add default B +# ifconfig eoipN create +# ifconfig eoipN tunnel A D +# ifconfig eoipN up +# route add E D +.Ed +.Pp +On Host D (MikroTik): +.Bd -literal -offset indent +[admin@MikroTik] > interface eoip +[admin@MikroTik] /interface eoip> add name="eoipN" \e +\e... local-address=D remote-address=A +[admin@MikroTik] /interface eoip> enable eoipN +.Ed +.Sh SEE ALSO +.Xr egre 4 , +.Xr inet 4 , +.Xr ip 4 , +.Xr netintro 4 , +.Xr options 4 , +.Xr hostname.if 5 , +.Xr protocols 5 , +.Xr ifconfig 8 , +.Xr netstart 8 , +.Xr sysctl 8 +.Sh STANDARDS +.Rs +.%A S. Hanks +.%A "T. Li" +.%A D. Farinacci +.%A P. Traina +.%D October 1994 +.%R RFC 1701 +.%T Generic Routing Encapsulation (GRE) +.Re +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org diff --git a/static/openbsd/man4/ep.4 b/static/openbsd/man4/ep.4 new file mode 100644 index 00000000..40516bf3 --- /dev/null +++ b/static/openbsd/man4/ep.4 @@ -0,0 +1,152 @@ +.\" $OpenBSD: ep.4,v 1.35 2013/08/14 06:32:34 jmc Exp $ +.\" +.\" Copyright (c) 1994 Herb Peyerl +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Herb Peyerl +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 14 2013 $ +.Dt EP 4 +.Os +.Sh NAME +.Nm ep +.Nd 3Com EtherLink III and Fast EtherLink III 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "ep* at eisa?" +.Cd "ep* at isa?" +.Cd "ep* at pci?" +.Cd "ep* at pcmcia?" +.Cd "ep* at isapnp?" +.Cd "tqphy* at mii?" +.Sh DESCRIPTION +The +.Nm +device driver supports the 3Com EtherLink III and Fast EtherLink III family +of Ethernet cards. +This includes, among others, the following models: +.Pp +.Bl -tag -width 3CXXXX -offset indent -compact +.It 3C509 +EtherLink III ISA +.It 3C509B +EtherLink III ISA (Plug-and-Play) +.It 3C556 +EtherLink III LAN+Modem PC Card (PCMCIA) +.It 3C562 +EtherLink III LAN+33.6K Modem PC Card (PCMCIA) +.It 3C574 +Fast EtherLink III 10/100 LAN PC Card (PCMCIA) +.It 3C579 +EtherLink III EISA +.It 3C589 +EtherLink III LAN PC Card (PCMCIA) +.It 3C590 +Fast EtherLink III PCI +.It 3C592 +EtherLink III EISA Bus Master +.It 3C595 +Fast EtherLink III PCI 10/100 +.It 3C597 +Fast EtherLink III EISA 10/100 +.El +.Pp +Category 3, 4 or 5 unshielded twisted-pair (UTP) cable should be used for +RJ-45 (10baseT), thick Ethernet coaxial (RG59 B/U, 50 ohm) for AUI/DIX, and +thin Ethernet coaxial (RG58 A/U or C/U, 50 ohm +/- 4) for BNC (10base2). +Some 3Com NICs also support MII connectors (switchable 10/100Mbps UTP). +.Pp +The following media types and options (as given to +.Xr ifconfig 8 ) +are supported: +.Bl -tag -width xxx -offset indent +.It Cm media No autoselect +Enable autoselection of media type and options. +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Set 100Mbps (Fast Ethernet) operation and force full-duplex mode. +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Set 100Mbps (Fast Ethernet) operation and force half-duplex mode. +.It Cm media No 10baseT Cm mediaopt No full-duplex +Set 10baseT (UTP) operation and force full-duplex mode. +.It Cm media No 10baseT Cm mediaopt No half-duplex +Set 10baseT (UTP) operation and force half-duplex mode. +.It Cm media No 10base5 +Set 10base5 (thick-net) operation (half-duplex only). +.It Cm media No 10base2 +Set 10base2 (thin-net) operation (half-duplex only). +.El +.Pp +Note that the 100baseTX media type is only available if supported by the +adapter. +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by your card try +.Dq ifconfig media . +For example, +.Dq ifconfig ep0 media . +.Pp +If more than one of the supported cards is installed, they are probed for +in the following order: +.Pp +.Bl -enum -offset indent -compact +.It +PCI cards based on PCI function number order. +.It +EISA cards based on EISA slot number order. +.It +ISA cards based on increasing Ethernet address order. +.It +Any ISA cards in Plug-and-Play mode, in Plug-and-Play order. +.El +.Pp +You may specify the port and IRQ numbers where the cards are expected to +be found, but it is not necessary. +The cards are intelligent enough to let us know where they live on the bus. +.Sh DIAGNOSTICS +.Bl -diag +.It ep0: reset (status: %x) +The driver has encountered a FIFO underrun or overrun. +The driver will reset the card and the packet will be lost. +This is not fatal. +.It ep0: eeprom failed to come ready +The EEPROM failed to come ready. +This probably means the card is wedged. +.It ep0: erase pencil mark, or disable PnP mode! +This means that someone has scribbled with pencil in the test area on the +card. +Erase the pencil mark and reboot. +(This is not a joke). +.El +.Sh SEE ALSO +.Xr eisa 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr isapnp 4 , +.Xr pci 4 , +.Xr pcmcia 4 , +.Xr tqphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/epic.4 b/static/openbsd/man4/epic.4 new file mode 100644 index 00000000..69cd340d --- /dev/null +++ b/static/openbsd/man4/epic.4 @@ -0,0 +1,105 @@ +.\" $OpenBSD: epic.4,v 1.10 2022/03/21 14:56:16 miod Exp $ +.\" +.\" Copyright (c) 1998 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 21 2022 $ +.Dt EPIC 4 +.Os +.Sh NAME +.Nm epic +.Nd SMC 83C170 (EPIC/100) 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "epic* at pci?" +.Cd "acphy* at mii?" +.Cd "lxtphy* at mii?" +.Cd "qsphy* at mii?" +.Sh DESCRIPTION +The +.Nm +interface provides access to the 10Mb/s and 100Mb/s Ethernet networks via the +.Tn SMC +.Tn EPIC +chipset. +This driver provides support for the +.Tn SMC +.Tn EtherPower II 10/100 +Ethernet cards. +.Pp +The +.Nm +supports several media types, which are selected via the +.Xr ifconfig 8 +command. +The supported media types are: +.Bl -tag -width 6n -offset indent +.It Cm media No autoselect +Attempt to autoselect the media type (default) +.It Cm media No 100baseFX Cm mediaopt No full-duplex +Use 100baseFX (fiber), full duplex +.It Cm media No 100baseFX Cm mediaopt No half-duplex +Use 100baseFX (fiber), half duplex +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Use 100baseTX, full duplex +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Use 100baseTX, half duplex +.It Cm media No 100baseTX Cm mediaopt No loopback +Put the interface into loopback mode +.It Cm media No 10baseT Cm mediaopt No full-duplex +Use 10baseT, full duplex +.It Cm media No 10baseT Cm mediaopt No half-duplex +Use 10baseT, half duplex +.It Cm media No 10baseT Cm mediaopt No loopback +Put the interface into loopback mode +.El +.Sh SEE ALSO +.Xr acphy 4 , +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr lxtphy 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr qsphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Nx 1.4 . +.Ox +support was added in +.Ox 3.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jason R. Thorpe Aq Mt thorpej@wasabisystems.com +and ported to +.Ox +by +.An Brad Smith Aq Mt brad@openbsd.org . diff --git a/static/openbsd/man4/erspan.4 b/static/openbsd/man4/erspan.4 new file mode 100644 index 00000000..59a058a9 --- /dev/null +++ b/static/openbsd/man4/erspan.4 @@ -0,0 +1,226 @@ +.\" $OpenBSD: erspan.4,v 1.3 2025/05/18 23:01:43 dlg Exp $ +.\" $NetBSD: gre.4,v 1.10 1999/12/22 14:55:49 kleink Exp $ +.\" +.\" Copyright 1998 (c) The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Heiko W. Rupp +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 18 2025 $ +.Dt ERSPAN 4 +.Os +.Sh NAME +.Nm erspan +.Nd ERSPAN Type II tunnel network device +.Sh SYNOPSIS +.Cd "pseudo-device gre" +.Sh DESCRIPTION +The +.Nm +interface provides tunnelling of Ethernet frames across +IPv4 and IPv6 networks using the +.\" Cisco Systems' +Encapsulated Remote Switch Port Analyzer (ERSPAN) Type II protocol. +.Pp +ERSPAN is intended as a network based packet capture format +rather than a tunnelling protocol. +However, ERSPAN Type II is implemented as a network interface driver +in +.Ox +to allow existing infrastructure such as +.Xr bpf 4 +and tools such as +.Xr bpflogd 8 +and +.Xr tcpdump 8 +to store and analyse the received packets. +.Nm +interfaces support packet transmission so they can be used as span ports +on +.Xr veb 4 +and +.Xr bridge 4 +configurations. +.Pp +The protocol is based on the Generic Routing and Encapsulation (GRE) +protocol. +GRE datagrams (IP protocol number 47) consist of a GRE header +and an outer IP header for encapsulating another protocol's datagram. +The GRE header specifies a version and the type of the encapsulated datagram, +allowing for the tunnelling of multiple protocols. +ERSPAN Type II uses GRE version 0, sequence numbers, protocol +identifier (0x88be), and a custom header before the Ethernet payload, +making it distinct from the Ethernet over GRE encapsulation supported +by +.Xr egre 4 . +However, it is implemented as part of the same driver providing +.Xr egre 4 . +.Pp +Distinct tunnels between the same endpoints are distinguished +by a 10-bit tunnel identifier field in the header. +.Pp +.Nm +supports the capture of the encapsulated Ethernet packets via +.Xr bpf 4 +using the +.Dv DLT_EN10MB +data link type, +and the encapsulating ERSPAN, GRE, and IP headers using the +.Dv DLT_LOOP +data link type. +.Pp +.Nm +interfaces are configured in monitor mode by default, preventing +the processing of received packets from entering the network stack. +.Pp +All GRE packet processing in the system is allowed or denied by setting the +.Va net.inet.gre.allow +.Xr sysctl 8 +variable. +To allow GRE packet processing, set +.Va net.inet.gre.allow +to 1. +.Pp +.Nm +interfaces can be created at runtime using the +.Ic ifconfig erspan Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +.Pp +For correct operation, encapsulated traffic must not be routed +over the interface itself. +This can be implemented by adding a distinct or a more specific +route to the tunnel destination than the hosts or networks routed +via the tunnel interface. +Alternatively, the tunnel traffic may be configured in a separate +routing table to the encapsulated traffic. +.Ss Programming Interface +.Nm +interfaces support the following +.Xr ioctl 2 +calls for configuring tunnel options: +.Bl -tag -width indent -offset 3n +.It Dv SIOCSLIFPHYADDR Fa "struct if_laddrreq *" +Set the unicast IPv4 or IPv6 addresses for the encapsulating IP packets. +The destination address may be left unspecified if the interface +is used as a collector for ERSPAN sessions. +The addresses may only be configured while the interface is down. +.It Dv SIOCGLIFPHYADDR Fa "struct if_laddrreq *" +Get the addresses used for the encapsulating IP packets. +.It Dv SIOCDIFPHYADDR Fa "struct ifreq *" +Clear the addresses used for the encapsulating IP packets. +The addresses may only be cleared while the interface is down. +.It Dv SIOCSVNETID Fa "struct ifreq *" +Configure a virtual network identifier for use as the Session ID +in the ERSPAN Type II header. +The virtual network identifier may only be configured while the +interface is down. +The Session ID is a 10-bit value. +.It Dv SIOCGVNETID Fa "struct ifreq *" +Get the virtual network identifier used as the Session ID in the +ERSPAN Type II header. +.It Dv SIOCDVNETID Fa "struct ifreq *" +Clear the virtual as the Session ID in the ERSPAN Type II header. +If the Session ID and tunnel destination address are unspecified, the +interface will accept packets with any Session ID. +.It Dv SIOCSLIFPHYRTABLE Fa "struct ifreq *" +Set the routing table the tunnel traffic operates in. +The routing table may only be configured while the interface is down. +.It Dv SIOCGLIFPHYRTABLE Fa "struct ifreq *" +Get the routing table the tunnel traffic operates in. +.It Dv SIOCSLIFPHYTTL Fa "struct ifreq *" +Set the Time-To-Live field in IPv4 encapsulation headers, or the +Hop Limit field in IPv6 encapsulation headers. +.It Dv SIOCGLIFPHYTTL Fa "struct ifreq *" +Get the value used in the Time-To-Live field in an IPv4 encapsulation +header or the Hop Limit field in an IPv6 encapsulation header. +.It Dv SIOCSLIFPHYDF Fa "struct ifreq *" +Configure whether the tunnel traffic sent by the interface can be +fragmented or not. +This sets the Don't Fragment (DF) bit on IPv4 packets, +and disables fragmentation of IPv6 packets. +.It Dv SIOCGLIFPHYDF Fa "struct ifreq *" +Get whether the tunnel traffic sent by the interface can be fragmented +or not. +.It Dv SIOCSTXHPRIO Fa "struct ifreq *" +Set the priority value used in the Type of Service field in IPv4 +headers, or the Traffic Class field in IPv6 headers. +Values may be from 0 to 7, or +.Dv IF_HDRPRIO_PACKET +to specify that the current priority of a packet should be used. +.It Dv SIOCGTXHPRIO Fa "struct ifreq *" +Get the priority value used in the Type of Service field in IPv4 +headers, or the Traffic Class field in IPv6 headers. +.El +.Ss Security Considerations +ERSPAN does not provide any integrated security features. +It should only be deployed on trusted private networks, +or protected with IPsec to add authentication and encryption for +confidentiality. +An encrypted transport is especially recommended when using ERSPAN +over a public network. +.Pp +The Packet Filter +.Xr pf 4 +can be used to filter tunnel traffic with endpoint policies +.Xr pf.conf 5 . +.Pp +The Time-to-Live (TTL) value of a tunnel can be set to 1 or a low +value to restrict the traffic to the local network: +.Bd -literal -offset indent +# ifconfig erspanN tunnelttl 1 +.Ed +.Sh SEE ALSO +.Xr egre 4 , +.Xr inet 4 , +.Xr ip 4 , +.Xr netintro 4 , +.Xr options 4 , +.Xr hostname.if 5 , +.Xr protocols 5 , +.Xr bpflogd 8 , +.Xr ifconfig 8 , +.Xr netstart 8 , +.Xr sysctl 8 , +.Xr tcpdump 8 +.Sh STANDARDS +.Rs +.%A S. Hanks +.%A "T. Li" +.%A D. Farinacci +.%A P. Traina +.%D October 1994 +.%R RFC 1701 +.%T Generic Routing Encapsulation (GRE) +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org diff --git a/static/openbsd/man4/esa.4 b/static/openbsd/man4/esa.4 new file mode 100644 index 00000000..26739bec --- /dev/null +++ b/static/openbsd/man4/esa.4 @@ -0,0 +1,61 @@ +.\" $OpenBSD: esa.4,v 1.9 2013/07/16 16:05:48 schwarze Exp $ +.\" $NetBSD: esa.4,v 1.4 2002/01/24 22:24:19 he Exp $ +.\" +.\" Copyright (c) 2001, 2002 Jared D. McNeill +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Neither the name of the author nor the names of any +.\" contributors may be used to endorse or promote products derived +.\" from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ESA 4 +.Os +.Sh NAME +.Nm esa +.Nd ESS Technology Allegro-1/Maestro-3 family audio device +.Sh SYNOPSIS +.Cd "esa* at pci?" +.Cd "audio* at esa?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ESS Allegro-1 and Maestro-3 audio devices +on the PCI bus. +These devices are popular in laptop systems. +.Pp +The Allegro-1 and the Maestro-3 are full-duplex devices that allow +independent playback and recording at sample rates between 8000Hz and +48000Hz and are capable of playback at 8 and 16 bit in mono and stereo. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr maestro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 3.1 . +.Sh AUTHORS +.An Jared D. McNeill Aq Mt jmcneill@invisible.ca +.Sh BUGS +Hardware volume control is not yet supported by this driver. diff --git a/static/openbsd/man4/escodec.4 b/static/openbsd/man4/escodec.4 new file mode 100644 index 00000000..aff1b90b --- /dev/null +++ b/static/openbsd/man4/escodec.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: escodec.4,v 1.2 2022/02/20 15:39:55 jsg Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 20 2022 $ +.Dt ESCODEC 4 +.Os +.Sh NAME +.Nm escodec +.Nd Everest Semiconductor ES8316 audio codec +.Sh SYNOPSIS +.Cd "escodec* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Everest Semiconductor ES8316 audio codec. +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared McNeill Aq Mt jmcneill@invisible.ca +for +.Nx +and ported to +.Ox +by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/eso.4 b/static/openbsd/man4/eso.4 new file mode 100644 index 00000000..8f7d70cb --- /dev/null +++ b/static/openbsd/man4/eso.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: eso.4,v 1.10 2010/07/31 08:33:20 ratchov Exp $ +.\" $NetBSD: eso.4,v 1.2 1999/08/02 17:43:52 augustss Exp $ +.\" +.\" Copyright (c) 1999 Klaus J. Klein +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 31 2010 $ +.Dt ESO 4 +.Os +.Sh NAME +.Nm eso +.Nd ESS Technology Solo-1 PCI AudioDrive audio device +.Sh SYNOPSIS +.Cd "eso* at pci?" +.Cd "audio* at eso?" +.\" .Cd "mpu* at eso?" +.Sh DESCRIPTION +The +.Nm +device driver supports sound cards based on ESS Technology Solo-1 +PCI AudioDrive chips (ES1938 and ES1946), +e.g. the TerraTec 128i PCI card. +.Sh DIAGNOSTICS +.Bl -diag +.It "eso0: can't map Audio 1 DMA into I/O space" +PCI autoconfiguration did not map the first audio channel DMA controller into +I/O space at a suitable address, and the driver was not able map it by itself. +In that case only playback functionality will be available. +.It "eso0: reset timeout" +The device failed to acknowledge being reset. +.It "eso0: RDR timeout" +The driver timed out reading data from a controller register. +.It "eso0: WDR timeout" +The driver timed out waiting to send a command or writing to a controller +register. +.El +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 , +.\" .Xr mpu 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.5 . +.Sh BUGS +The game port and MIDI port are not supported. diff --git a/static/openbsd/man4/ess.4 b/static/openbsd/man4/ess.4 new file mode 100644 index 00000000..bbcdda14 --- /dev/null +++ b/static/openbsd/man4/ess.4 @@ -0,0 +1,83 @@ +.\" $OpenBSD: ess.4,v 1.12 2022/03/31 17:27:20 naddy Exp $ +.\" $NetBSD: ess.4,v 1.6 1999/04/13 20:25:29 augustss Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt ESS 4 +.Os +.Sh NAME +.Nm ess +.Nd ESS Technology AudioDrive family audio device +.Sh SYNOPSIS +.\" .Cd "ess0 at isa? port 0x220 irq 5 drq 1 drq2 5" +.Cd "ess* at isapnp?" +.\" .Cd "ess* at ofisa?" +.Cd "audio* at ess?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ESS 1788, 1888, 1887, and 888 AudioDrive +audio devices. +.Pp +The AudioDrive 1788 is a half-duplex device, while the 1888, 1887, and +888 are full-duplex. +All are capable of 8- and 16-bit audio sample recording and playback +at rates up to 44.1kHz. +.Pp +The AudioDrive takes 16 I/O ports. +The I/O port range, IRQ, and DRQ channels are set by the driver +to the values specified in the configuration file (or for isapnp or ofisa, +the values assigned from the firmware). +The I/O port base must be one of 0x220, 0x230, 0x240, +0x250. +The IRQ must be one of 5, 7, 9, 10 (or 15 on the 1887 only). +The first DRQ channel must be selected from 0, 1, 3. +The second DRQ channel (used for playback by the full-duplex 1888/1887, ignored +by the 1788) can additionally be set to 5. +If both DRQ channels are used, they must be different. +.Pp +The joystick interface (if enabled) is handled by the +.Xr joy 4 +driver. +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 , +.\" .Xr isa 4 , +.Xr isapnp 4 , +.Xr joy 4 , +.Xr sb 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.2 . +.Sh BUGS +The AudioDrive devices have a SoundBlaster compatibility mode, and may +be detected by the SoundBlaster driver (see +.Xr sb 4 ) +rather than the AudioDrive driver. +The workaround is to remove or disable the SoundBlaster driver from the kernel +configuration. diff --git a/static/openbsd/man4/et.4 b/static/openbsd/man4/et.4 new file mode 100644 index 00000000..87800cc8 --- /dev/null +++ b/static/openbsd/man4/et.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: et.4,v 1.5 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2007 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt ET 4 +.Os +.Sh NAME +.Nm et +.Nd Agere/LSI ET1310 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "et* at pci?" +.Cd "etphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports PCI Express Ethernet adapters based on the Agere/LSI +ET1310 integrated MAC/PHY. +.Pp +The following +.Ar media +types are supported: +.Pp +.Bl -tag -width autoselect -compact +.It Cm autoselect +Enable autoselection of the media type and options. +.It Cm 10baseT +Set 10Mbps operation. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.It Cm 1000baseT +Set 1000Mbps (Gigabit Ethernet) operation (some models only). +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr etphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Sepherosa Ziehau +for +.Dx +and ported to +.Ox +by +.An Jonathan Gray Aq Mt jsg@openbsd.org . diff --git a/static/openbsd/man4/etherip.4 b/static/openbsd/man4/etherip.4 new file mode 100644 index 00000000..7d3dfadb --- /dev/null +++ b/static/openbsd/man4/etherip.4 @@ -0,0 +1,186 @@ +.\" $OpenBSD: etherip.4,v 1.10 2024/08/30 20:08:05 jmc Exp $ +.\" +.\" Copyright (c) 2015 YASUOKA Masahiko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" The following requests are required for all man pages. +.\" +.Dd $Mdocdate: August 30 2024 $ +.Dt ETHERIP 4 +.Os +.Sh NAME +.Nm etherip +.Nd EtherIP tunnel interface +.Sh SYNOPSIS +.Cd "pseudo-device etherip" +.Sh DESCRIPTION +The +.Nm +driver provides point-to-point tunnel interfaces for carrying +Ethernet frames across IPv4 and IPv6 networks using RFC 3378 EtherIP +encapsulation. +.Pp +An +.Nm +interface can be created using the +.Ic ifconfig etherip Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +It must be configured with the addresses used for the outer header. +This can be done using +.Xr ifconfig 8 Ns 's +.Ic tunnel +command (which uses the +.Dv SIOCSLIFPHYADDR +ioctl). +The +.Xr sysctl 2 +variable +.Dv net.inet.etherip.allow +must be set to 1, unless +.Xr ipsec 4 +is being used to protect the traffic. +.Pp +.Nm +interfaces can configured as part of an Ethernet bridge, such as +.Xr veb 4 , +.Xr tpmr 4 , +and +.Xr bridge 4 , +to extend the connectivity of Ethernet networks across IP networks, +possibly across the Internet. +.Pp +The EtherIP protocol does not provide any integrated security +features. +EtherIP should only be deployed on trusted private networks, or +protected with IPsec to add authentication and encryption for +confidentiality. +IPsec is especially recommended when transporting EtherIP over the +public Internet. +EtherIP encapsulated packets may be protected with IPsec by specifying +the appropriate IPsec flows between the two endpoints. +To only protect the encapsulated EtherIP traffic between the tunnel +endpoints, the IP transport protocol 97 (etherip) selector may be used +in +.Xr ipsec.conf 5 +or +.Xr iked.conf 5 . +.Sh EXAMPLES +Given two physically separate Ethernet networks, +.Nm +can be used as follows to make them appear as the same local area +network. +If host gw1 has the external IP address 192.0.2.10 and is connected +to network1 on em1, and host gw2 has the external IP address +198.51.100.14 and is connected to network2 on ix1, the following +configuration can be used to bridge network1 and network2. +.Pp +First create a bridge using a +.Xr veb 4 +interface, +adding the +.Nm +interface and internal Ethernet interface to the bridge. +.Pp +On gw1: +.Bd -literal -offset indent +gw1# ifconfig etherip0 create tunnel 192.0.2.10 198.51.100.14 +gw1# ifconfig veb0 create add etherip0 add em1 +.Ed +.Pp +On gw2: +.Bd -literal -offset indent +gw2# ifconfig etherip0 create tunnel 198.51.100.14 192.0.2.10 +gw2# ifconfig veb0 create add etherip0 add ix1 +.Ed +.Pp +Create Security Associations (SAs) between the external IP address of each +bridge and matching ingress flows by using the following +.Xr ipsec.conf 5 +file on gw1: +.Bd -literal -offset indent +esp from 198.51.100.14 to 192.0.2.10 spi 0x4242:0x4243 \e + authkey file "auth1:auth2" enckey file "enc1:enc2" +flow esp proto etherip from 198.51.100.14 to 192.0.2.10 +.Ed +.Pp +Now load these rules into the kernel by issuing the +.Xr ipsecctl 8 +command: +.Bd -literal -offset indent +gw1# ipsecctl -f ipsec.conf +.Ed +.Pp +Appropriate +.Xr ipsec.conf 5 +for gw2: +.Bd -literal -offset indent +esp from 198.51.100.14 to 192.0.2.10 spi 0x4243:0x4242 \e + authkey file "auth2:auth1" enckey file "enc2:enc1" +flow esp proto etherip from 198.51.100.14 to 192.0.2.10 +.Ed +.Pp +And load them: +.Bd -literal -offset indent +gw2# ipsecctl -f ipsec.conf +.Ed +.Pp +Finally, bring all the interfaces up (if not already up). +.Pp +On gw1: +.Bd -literal -offset indent +gw1# ifconfig em1 up +gw1# ifconfig etherip0 up +gw1# ifconfig veb0 up +.Ed +.Pp +On gw2: +.Bd -literal -offset indent +gw1# ifconfig ix1 up +gw1# ifconfig etherip0 up +gw1# ifconfig veb0 up +.Ed +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr bridge 4 , +.Xr inet 4 , +.Xr inet6 4 , +.Xr ipsec 4 , +.Xr tpmr 4 , +.Xr veb 4 , +.Xr hostname.if 5 , +.Xr iked.conf 5 , +.Xr ipsec.conf 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh STANDARDS +.Rs +.%A R. Housley +.%A S. Hollenbeck +.%D September 2002 +.%R RFC 3378 +.%T EtherIP: Tunneling Ethernet Frames in IP Datagrams +.Re +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 5.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Kazuya Goda Aq Mt goda@openbsd.org . diff --git a/static/openbsd/man4/etphy.4 b/static/openbsd/man4/etphy.4 new file mode 100644 index 00000000..566dae62 --- /dev/null +++ b/static/openbsd/man4/etphy.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: etphy.4,v 1.4 2013/08/14 23:08:30 schwarze Exp $ +.\" +.\" Copyright (c) 2007 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 14 2013 $ +.Dt ETPHY 4 +.Os +.Sh NAME +.Nm etphy +.Nd Agere/LSI ET1011 TruePHY Gigabit Ethernet PHY +.Sh SYNOPSIS +.Cd "etphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Agere/LSI ET1011 TruePHY 10/100/1000 Ethernet PHYs +including the integrated TruePHY in ET1310 based adapters. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Sepherosa Ziehau +for +.Dx +and ported to +.Ox +by +.An Jonathan Gray Aq Mt jsg@openbsd.org . diff --git a/static/openbsd/man4/ex.4 b/static/openbsd/man4/ex.4 new file mode 100644 index 00000000..44409109 --- /dev/null +++ b/static/openbsd/man4/ex.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: ex.4,v 1.1 2007/10/23 23:43:24 deraadt Exp $ +.\" +.\" Copyright (c) 1997 David E. O'Brien +.\" +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.Dd $Mdocdate: October 23 2007 $ +.Dt EX 4 +.Os +.Sh NAME +.Nm ex +.Nd Intel EtherExpress Pro/10 and Pro/10+ Ethernet device +.Sh SYNOPSIS +.Cd "ex0 at isa? port 0x320 irq 5" +.Sh DESCRIPTION +The +.Nm +interface provides access to a 10 Mb/s Ethernet network via the +Intel i82595 Ethernet chips. +This includes the following models: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Intel EtherExpress Pro/10 ISA +.It Intel EtherExpress Pro/10+ ISA +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/exphy.4 b/static/openbsd/man4/exphy.4 new file mode 100644 index 00000000..d1197871 --- /dev/null +++ b/static/openbsd/man4/exphy.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: exphy.4,v 1.15 2009/07/31 14:20:29 jmc Exp $ +.\" $NetBSD: exphy.4,v 1.1 1998/11/04 05:53:58 thorpej Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 31 2009 $ +.Dt EXPHY 4 +.Os +.Sh NAME +.Nm exphy +.Nd 3Com 3C905B-TX internal Ethernet PHY +.Sh SYNOPSIS +.Cd "exphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the internal PHY on 3Com 3C905B-TX 10/100 Ethernet +interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/exrtc.4 b/static/openbsd/man4/exrtc.4 new file mode 100644 index 00000000..5689cb89 --- /dev/null +++ b/static/openbsd/man4/exrtc.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: exrtc.4,v 1.2 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt EXRTC 4 +.Os +.Sh NAME +.Nm exrtc +.Nd Samsung Exynos real-time clock +.Sh SYNOPSIS +.Cd "exrtc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the real-time clock found in Samsung Exynos SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/fanpwr.4 b/static/openbsd/man4/fanpwr.4 new file mode 100644 index 00000000..362f50c4 --- /dev/null +++ b/static/openbsd/man4/fanpwr.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: fanpwr.4,v 1.2 2023/02/13 19:18:23 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 13 2023 $ +.Dt FANPWR 4 +.Os +.Sh NAME +.Nm fanpwr +.Nd Fairchild FAN53555 voltage regulator +.Sh SYNOPSIS +.Cd "fanpwr* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Fairchild FAN53555, Silergy SYR827/828 +and Tang Cheng TCS4525 voltage regulators. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/fd.4 b/static/openbsd/man4/fd.4 new file mode 100644 index 00000000..6f986692 --- /dev/null +++ b/static/openbsd/man4/fd.4 @@ -0,0 +1,97 @@ +.\" $OpenBSD: fd.4,v 1.7 2007/05/31 19:19:50 jmc Exp $ +.\" $NetBSD: fd.4,v 1.3 1994/11/30 16:22:13 jtc Exp $ +.\" +.\" Copyright (c) 1990, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)fd.4 8.1 (Berkeley) 6/9/93 +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt FD 4 +.Os +.Sh NAME +.Nm fd , +.Nm stdin , +.Nm stdout , +.Nm stderr +.Nd file descriptor files +.Sh DESCRIPTION +The files +.Pa /dev/fd/0 +through +.Pa /dev/fd/# +refer to file descriptors which can be accessed through the file system. +If the file descriptor is open and the mode the file is being opened +with is a subset of the mode of the existing descriptor, the call: +.Bd -literal -offset indent +fd = open("/dev/fd/0", mode); +.Ed +.Pp +and the call: +.Bd -literal -offset indent +fd = fcntl(0, F_DUPFD, 0); +.Ed +.Pp +are equivalent. +.Pp +Opening the files +.Pa /dev/stdin , +.Pa /dev/stdout , +and +.Pa /dev/stderr +is equivalent to the following calls: +.Bd -literal -offset indent +fd = fcntl(STDIN_FILENO, F_DUPFD, 0); +fd = fcntl(STDOUT_FILENO, F_DUPFD, 0); +fd = fcntl(STDERR_FILENO, F_DUPFD, 0); +.Ed +.Pp +Flags to the +.Xr open 2 +call other than +.Dv O_RDONLY , +.Dv O_WRONLY , +and +.Dv O_RDWR +are ignored. +.Pp +These devices may not be opened by processes which are tainted +as a result of setuid or setgid behaviours, as documented in +.Xr issetugid 2 . +In those cases, an error return will occur with +.Va errno +set to +.Dv EPERM . +.Sh FILES +.Bl -tag -width /dev/stderr -compact +.It Pa /dev/fd/# +.It Pa /dev/stdin +.It Pa /dev/stdout +.It Pa /dev/stderr +.El +.Sh SEE ALSO +.Xr tty 4 diff --git a/static/openbsd/man4/fdc.4 b/static/openbsd/man4/fdc.4 new file mode 100644 index 00000000..d0d78fe4 --- /dev/null +++ b/static/openbsd/man4/fdc.4 @@ -0,0 +1,125 @@ +.\" $OpenBSD: fdc.4,v 1.16 2016/09/01 12:24:56 jmc Exp $ +.\" $NetBSD: fdc.4,v 1.6 1996/03/22 01:55:14 andrew Exp $ +.\" +.\" Copyright (c) 1996 Andrew C. Wheadon +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)fdc.4 8.1 (Berkeley) 3/22/96 +.\" +.Dd $Mdocdate: September 1 2016 $ +.Dt FDC 4 +.Os +.Sh NAME +.Nm fdc +.Nd NEC765 compatible floppy disk driver +.Sh SYNOPSIS +.Cd "fdc0 at isa? port 0x3f0 irq 6 drq 2 " Pq alpha, amd64, i386 +.Cd "fdc* at sbus? " Pq sparc64 +.\" .Cd "fdc* at ebus? " Pq sparc64 +.Cd "fd* at fdc? flags 0x00" +.Sh DESCRIPTION +The +.Nm +driver supports the standard AT floppy disk controllers. +These include standard IDE, MFM, RLL, +EIDE, ESDI and SCSI controllers with floppy attachment, +commonly encountered on many isa bus machines, +as well as the on-board floppy controller found on most +UltraSPARC workstations. +.Pp +The standard names of a floppy drive will take the form +.Pa /dev/fd{0,1,2,3}{,B,C,D,E,F,G,H}[a-p] . +.Pp +The first component of this path is the unit number, permitting +a total of 4 floppy drives. +The next component is missing for the default geometry (it +would be A, but it is omitted for simplicity) and B-H for the +other 7 geometry types the floppy driver supports. +The last component of the path is the 16 partitions that a floppy +disk can support. +.Pp +The additional geometry types are as follows: +.Pp +.Bl -tag -width xxxxxx -offset indent -compact +.It `B' 1.44MB +.It `C' 1.2MB +.It `D' 360KB/AT (360KB disk in a 1.2 MB drive) +.It `E' 360KB/PC (360KB drive) +.It `F' 720KB +.It `G' 720KB/x (720KB in a 1.2 MB drive) +.It `H' 360KB/x (360KB in a 720KB drive) +.El +.Pp +The default geometry is the format specified in the BIOS, and +is typically the largest supported format. +.Pp +Some isa floppy controllers do not respond correctly to probes, and +the configuration file +.Cm flags +field can be used to specify a particular drive type, overriding the +probed type. +If the 0x10 bit is on, the low order three bits of the +.Cm flags +field encode the drive type, as follows: +.Pp +.Bl -tag -width 2.88MB -offset indent -compact +.It 1 2.88MB +.It 2 1.44MB +.It 3 1.2MB +.It 4 720K +.It 5 360K +.It 6 1.2 MB Japanese format +.El +.Pp +If the 0x20 bit is on, the drive will be attached even +if it was not found by the probe routine. +These flags are ignored on +.Nm +controllers not connected to an +.Xr isa 4 +bus. +.Sh SEE ALSO +.Xr eject 1 , +.Xr fdformat 1 , +.Xr ebus 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr sbus 4 +.Sh BUGS +The +.Nm +driver can interfere with other +.Xr isa 4 +controllers, namely some WD/SMC +network controllers fail to work when the probing mechanism +in the +.Nm +driver probes for a missing second floppy drive. +In this case you should try recompiling the kernel +replacing the relevant line with +.Cd "fd0 at fdc?" . diff --git a/static/openbsd/man4/fec.4 b/static/openbsd/man4/fec.4 new file mode 100644 index 00000000..defb223b --- /dev/null +++ b/static/openbsd/man4/fec.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: fec.4,v 1.3 2018/04/07 13:31:05 jmc Exp $ +.\" Copyright (c) 2014 Sylvestre Gallon +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 7 2018 $ +.Dt FEC 4 +.Os +.Sh NAME +.Nm fec +.Nd Freescale i.MX Ethernet device +.Sh SYNOPSIS +.Cd "fec* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Freescale i.MX 6 and i.MX 8 Ethernet device. +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr mii 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/fido.4 b/static/openbsd/man4/fido.4 new file mode 100644 index 00000000..534ab6e9 --- /dev/null +++ b/static/openbsd/man4/fido.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: fido.4,v 1.4 2020/08/21 19:02:46 mglocker Exp $ +.\" +.\" Copyright (c) 2019 Reyk Floeter +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 21 2020 $ +.Dt FIDO 4 +.Os +.Sh NAME +.Nm fido +.Nd FIDO/U2F security keys +.Sh SYNOPSIS +.Cd "fido* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for FIDO/U2F-compatible USB security keys. +They are Human Interface Devices (HID) which can be accessed via the +.Pa /dev/fido/N +interface. +.Pp +The driver is compatible with the +.Xr read 2 , +.Xr write 2 , +and +.Xr ioctl 2 +operations of the generic +.Xr uhid 4 +device but only accepts the optional HID +.Xr ioctl 2 +calls from root. +.Sh FILES +.Bl -tag -width /dev/fido/* -compact +.It Pa /dev/fido/* +.El +.Sh SEE ALSO +.Xr uhid 4 , +.Xr uhidev 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . diff --git a/static/openbsd/man4/fins.4 b/static/openbsd/man4/fins.4 new file mode 100644 index 00000000..70ced49e --- /dev/null +++ b/static/openbsd/man4/fins.4 @@ -0,0 +1,70 @@ +.\" $OpenBSD: fins.4,v 1.6 2009/03/30 00:37:45 deraadt Exp $ +.\" +.\" Copyright (c) 2005 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 30 2009 $ +.Dt FINS 4 +.Os +.Sh NAME +.Nm fins +.Nd Fintek F71805F LPC Super I/O +.Sh SYNOPSIS +.Cd "fins0 at isa? port 0x4e" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Fintek F71805F, F71806, F71862, +and F71882 LPC Super I/O ICs. +.Pp +The hardware monitor provides hardware monitoring capabilities +to be used with the +.Xr sysctl 8 +interface. +.Pp +The F71805F hardware monitor supports 15 sensors: +.Bl -column "Sensor" "Units" "Typical" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical Use" +.It Li "IN0" Ta "uV DC" Ta "Internal 3.3Vcc" +.It Li "IN1" Ta "uV DC" Ta "Memory Vtt" +.It Li "IN2" Ta "uV DC" Ta "RAM Vcc" +.It Li "IN3" Ta "uV DC" Ta "Chipset V" +.It Li "IN4" Ta "uV DC" Ta "+5V" +.It Li "IN5" Ta "uV DC" Ta "+12V" +.It Li "IN6" Ta "uV DC" Ta "Vcc 1.5V" +.It Li "IN7" Ta "uV DC" Ta "Vcore" +.It Li "IN8" Ta "uV DC" Ta "Vsb" +.It Li "IN9" Ta "uV DC" Ta "Vbat (optional)" +.It Li "Temp1" Ta "uK" Ta "CPU Temperature" +.It Li "Temp2" Ta "uK" Ta "Motherboard Temperature" +.It Li "Temp3" Ta "uK" Ta "(undefined)" +.It Li "Fan0" Ta "RPM" Ta "CPU Fan" +.It Li "Fan1" Ta "RPM" Ta "User Fan1" +.It Li "Fan2" Ta "RPM" Ta "User Fan2" +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Geoff Steckel . diff --git a/static/openbsd/man4/fintek.4 b/static/openbsd/man4/fintek.4 new file mode 100644 index 00000000..82ebe205 --- /dev/null +++ b/static/openbsd/man4/fintek.4 @@ -0,0 +1,66 @@ +.\" $OpenBSD: fintek.4,v 1.7 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt FINTEK 4 +.Os +.Sh NAME +.Nm fintek +.Nd Fintek F75375 temperature sensor +.Sh SYNOPSIS +.Cd "fintek* at iic? flags 0x0000" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Fintek F75375 temperature sensor +and fan controller. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface: +.Bd -literal -offset indent +$ sysctl hw.sensors.fintek0 +hw.sensors.fintek0.temp0=31.00 degC +hw.sensors.fintek0.temp1=29.00 degC +hw.sensors.fintek0.fan0=0 RPM +hw.sensors.fintek0.fan1=0 RPM +hw.sensors.fintek0.volt0=1.72 V DC (VCC) +hw.sensors.fintek0.volt1=1.34 V DC +hw.sensors.fintek0.volt2=1.73 V DC +hw.sensors.fintek0.volt3=0.90 V DC +.Ed +.Pp +On some machines the fans will not function properly with the chip in +default mode. +Setting +.Cm flags +to 0x0001 will make the fans run at full speed to prevent overheating. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@openbsd.org . diff --git a/static/openbsd/man4/fms.4 b/static/openbsd/man4/fms.4 new file mode 100644 index 00000000..0ac4ffac --- /dev/null +++ b/static/openbsd/man4/fms.4 @@ -0,0 +1,67 @@ +.\" $OpenBSD: fms.4,v 1.9 2007/05/31 19:19:50 jmc Exp $ +.\" $NetBSD: fms.4,v 1.2 1999/12/15 22:07:32 abs Exp $ +.\" +.\" Copyright (c) 1999 Klaus J. Klein +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt FMS 4 +.Os +.Sh NAME +.Nm fms +.Nd Forte Media FM801 audio device +.Sh SYNOPSIS +.Cd "fms* at pci?" +.Cd "audio* at fms?" +.\" .Cd "mpu* at fms?" +.\" .Cd "opl* at fms?" +.Cd "radio* at fms?" +.Sh DESCRIPTION +The +.Nm +device driver supports the Forte Media FM801 sound card and various FM tuners +attached to the sound card. +.Sh RADIO +Right now the +.Nm +driver supports MediaForte's +.Tn SoundForte RadioLink SF64-PCR FM +tuner and tuners on MediaForte's +.Tn SoundForte Quad X-treme SF256-PCP-R +and +.Tn SoundForte Theatre X-treme 5.1 SF256-PCS +sound cards. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr radio 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.8 . diff --git a/static/openbsd/man4/frame.4 b/static/openbsd/man4/frame.4 new file mode 100644 index 00000000..87d78dda --- /dev/null +++ b/static/openbsd/man4/frame.4 @@ -0,0 +1,244 @@ +.\" $OpenBSD: frame.4,v 1.3 2025/05/16 02:50:12 dlg Exp $ +.\" +.\" Copyright (c) 2024 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 16 2025 $ +.Dt FRAME 4 +.Os +.Sh NAME +.Nm frame +.Nd frame protocol family +.Sh SYNOPSIS +.Cd "pseudo-device af_frame" +.Pp +.In sys/types.h +.In net/frame.h +.Sh DESCRIPTION +The +.Nm +protocol family provides an interface for sending and receiving low +level network interface frames through the normal +.Xr socket 2 +mechanisms. +.Pp +The +.Nm +protocol family supports the +.Dv SOCK_DGRAM +socket type. +Only root may create +.Nm +protocol family sockets. +.Pp +.Nm +protocol family sockets are designed as an alternative to +.Xr bpf 4 +for handling low data and packet rate communication protocols. +Rather than filtering every frame entering the system before the +network stack, like +.Xr bpf 4 , +processing of the +.Nm +protocol family runs after the built in protocol handlers in the kernel, +thus avoiding the overhead. +For this reason, it is not possible to handle IPv4 or IPv6 packets +with +.Nm +protocol sockets because the kernel network stack consumes them +before the receive handling for +.Nm +sockets is run. +.Pp +Sockets can be created in the +.Nm +protocol family by using +.Dv AF_FRAME +as the +.Fa domain +argument to +.Xr socket 2 . +The type of interface, as per +.In net/if_types.h , +is specified as the socket +.Fa protocol . +Currently only Ethernet interfaces are supported. +.Pp +Sockets bound to the +.Nm +family use the following address structure: +.Bd -literal -offset indent +#define FRAME_ADDRLEN 8 +#define FRAME_DATALEN 32 + +struct sockaddr_frame { + uint8_t sfrm_len; + uint8_t sfrm_family; + uint16_t sfrm_proto; + unsigned int sfrm_ifindex; + uint8_t sfrm_addr[FRAME_ADDRLEN]; + char sfrm_ifname[IFNAMSIZ]; + uint8_t sfrm_data[FRAME_DATALEN]; +}; +.Ed +.Pp +The interface used for transmitting or receiving frames with a +.Nm +domain socket may be specified by using an interface index with +.Fa sfrm_ifindex , +or by name with +.Fa sfrm_ifname . +The use of other +.Vt struct sockaddr_frame +fields depends on the type of interface. +.Ss Ethernet frame sockets +A +.Nm +socket for use with Ethernet interfaces can be created using +.Dv IFT_ETHER +as the +.Fa protocol +argument to +.Xr socket 2 : +.Bd -literal -offset indent +int sock = socket(AF_FRAME, SOCK_DGRAM, IFT_ETHER); +.Ed +.Pp +The Ethernet protocol is specified with +.Fa sfrm_proto +in network byte order. +Ethernet addresses are specified using the first 6 bytes of +.Fa sfrm_addr . +.Pp +Ethernet +.Nm +sockets may receive frames on all interfaces by specifying 0 for +.Va sfrm_ifindex +when using +.Xr bind 2 . +Similarly, a +.Dq wildcard +local address of all zeros can be specified in +.Fa sfrm_addr . +.Pp +An interface and address must be specified when sending Ethernet frames. +.Pp +Ethernet sockets support the following +.Nm +socket options +using +.Dv IFT_ETHER +as the +.Fa level +argument with +.Xr setsockopt 2 +and +.Xr getsockopt 2 : +.Bl -tag -width Ds +.It Dv FRAME_RECVDSTADDR Ft int +Enable or disable the reception of the Ethernet destination address as a +.Vt struct ether_addr +control message for frames received with +.Xr recvmsg 2 . +.It Dv FRAME_RECVPRIO Ft int +Enable or disable the reception of the mbuf packet priority field as an +.Vt int +sized control message for frames received with +.Xr recvmsg 2 . +.It Dv FRAME_ADD_MEMBERSHIP Ft struct frame_mreq +Configure an Ethernet interface to enable reception of +frames destined to the specified multicast Ethernet address. +.Bd -literal -offset indent +struct frame_mreq { + unsigned int fmr_ifindex; + uint8_t fmr_addr[FRAME_ADDRLEN]; + char fmr_ifname[IFNAMSIZ]; +}; +.Ed +.Pp +An interface must be specified using either +.Fa fmr_ifindex +or +.Fa fmr_ifname . +The multicast Ethernet address is specified in the first 6 bytes of +.Fa fmr_addr . +.It Dv FRAME_DEL_MEMBERSHIP Ft struct frame_mreq +Configure an Ethernet interface to disable reception of frames destined +to the specified multicast Ethernet address. +.It Dv FRAME_SENDPRIO Ft int +Specify an mbuf priority value between +.Dv IF_HDRPRIO_MIN +.Pq 0 +and +.Dv IF_HDRPRIO_MAX +.Pq 7 +for frames sent with the Ethernet +.Nm +socket, or +.Dv IF_HDRPRIO_PACKET +to use the existing mbuf priority value. +The default is +.Dv IF_HDRPRIO_PACKET . +.El +.Sh EXAMPLES +To receive LLDP frames on the em0 Ethernet interface: +.Bd -literal -offset indent +struct sockaddr_frame sfrm = { + .sfrm_family = AF_FRAME, + .sfrm_ifname = "em0", + .sfrm_proto = htons(ETHERTYPE_LLDP), +}; +struct frame_mreq fmr = { + .fmr_ifname = "em0", + .fmr_addr = { 0x01, 0x80, 0xc2, 0x00, 0x00, 0x0e }, +}; +int sock; + +sock = socket(AF_FRAME, SOCK_DGRAM, IFT_ETHER); +if (sock == -1) + err(1, "ethernet frame socket"); +if (bind(sock, (struct sockaddr *)&sfrm, sizeof(sfrm)) == -1) + err(1, "bind"); +if (setsockopt(sock, IFT_ETHER, FRAME_ADD_MEMBERSHIP, + &fmr, sizeof(fmr)) == -1) + err(1, "join lldp multicast group"); + +for (;;) { + socklen_t sfrmlen = sizeof(sfrm); + uint8_t frame[2048]; + ssize_t rv; + + rv = recvfrom(sock, frame, sizeof(frame), 0, + (struct sockaddr *)&sfrm, &sfrmlen); + if (rv == -1) + err(1, "lldp recv"); + printf("received %zd bytes from %s", rv, + ether_ntoa((struct ether_addr *)sfrm.sfrm_addr)); +} +.Ed +.Sh SEE ALSO +.Xr socket 2 , +.Xr netintro 4 +.Sh HISTORY +.Nm +domain sockets appeared in +.Ox 7.7 . +.\" The +.\" .Ox +.\" implementation was influenced by the Linux +.\" .Dv AF_PACKET +.\" .Dq packet interface on device level +.\" socket interface, but is not compatible with it. +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/fusbtc.4 b/static/openbsd/man4/fusbtc.4 new file mode 100644 index 00000000..46cd80c6 --- /dev/null +++ b/static/openbsd/man4/fusbtc.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: fusbtc.4,v 1.2 2019/05/12 08:56:10 jmc Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 12 2019 $ +.Dt FUSBTC 4 +.Os +.Sh NAME +.Nm fusbtc +.Nd Fairchild FUSB302 USB Type-C Port controller +.Sh SYNOPSIS +.Cd "fusbtc* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Fairchild FUSB302 USB Type-C port controller. +It takes care of plug and unplug events on the USB Type-C port and discovers +the orientation of the plug so that the USB SuperSpeed pins can be routed +correctly. +Additionally it enables power on the USB Type-C port when a sink +is connected to power attached devices. +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/fuse.4 b/static/openbsd/man4/fuse.4 new file mode 100644 index 00000000..ea79a34e --- /dev/null +++ b/static/openbsd/man4/fuse.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: fuse.4,v 1.12 2016/05/16 17:55:57 jmc Exp $ +.\" +.\" Copyright (c) 2013 Sylvestre Gallon +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 16 2016 $ +.Dt FUSE 4 +.Os +.Sh NAME +.Nm fuse +.Nd file system in userland +.Sh SYNOPSIS +.Cd "option FUSE" +.Cd "pseudo-device fuse" +.Sh DESCRIPTION +The +.Nm +device provides a FUSE interface for implementing a file system in userland. +.Pp +This device does not support partial reads and writes. +.Sh FILES +.Bl -tag -width /dev/fuse* -compact +.It Pa /dev/fuse0 +.Nm +device special file +.El +.Sh SEE ALSO +.Xr fuse_main 3 , +.Xr intro 4 , +.Xr fb_setup 9 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Ox 5.4 . diff --git a/static/openbsd/man4/fxp.4 b/static/openbsd/man4/fxp.4 new file mode 100644 index 00000000..f2cff63c --- /dev/null +++ b/static/openbsd/man4/fxp.4 @@ -0,0 +1,144 @@ +.\" $OpenBSD: fxp.4,v 1.45 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 1997 David E. O'Brien +.\" +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt FXP 4 +.Os +.Sh NAME +.Nm fxp +.Nd Intel EtherExpress PRO/100 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "fxp* at pci?" +.Cd "fxp* at cardbus?" +.Cd "icsphy* at mii?" +.Cd "inphy* at mii?" +.Cd "iophy* at mii?" +.Cd "nsphy* at mii?" +.Sh DESCRIPTION +The +.Nm +device driver supports the Intel EtherExpress 100 family of Ethernet cards +based on various revisions of the i82557, i82558, i82559, i82559S, +i82550, i82551, and i82562 chipsets, including the following: +.Pp +.Bl -item -offset indent -compact +.It +Intel EtherExpress PRO/100 PCI +.It +Intel EtherExpress PRO/100B PCI +.It +Intel EtherExpress PRO/100+ PCI +.It +Intel EtherExpress PRO/100 Dual-Port PCI +.It +Intel PRO/100 CardBus II PC Card +.It +Intel PRO/100 VE +.It +Intel PRO/100 VM +.It +Intel PRO/100 M +.It +Intel PRO/100 S +.El +.Pp +The following media types and options (as given to +.Xr ifconfig 8 ) +are supported: +.Bl -tag -width xxx -offset indent +.It Cm media No autoselect +Enable autoselection of the media type and options (default). +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Set 100Mbps (Fast Ethernet) operation and force full-duplex mode. +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Set 100Mbps (Fast Ethernet) operation and force half-duplex mode. +.It Cm media No 10baseT Cm mediaopt No full-duplex +Set 10Mbps operation and force full-duplex. +.It Cm media No 10baseT Cm mediaopt No half-duplex +Set 10Mbps operation and force half-duplex. +.El +.Pp +If no media options are present, the +.Nm +driver places the card into autoselect mode. +.Sh FILES +Some devices are able to do interrupt coalescing but it requires firmware +updating. +The following firmware files are potentially loaded on demand when an +interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/fxp-d101a +.It Pa /etc/firmware/fxp-d101b0 +.It Pa /etc/firmware/fxp-d101ma +.It Pa /etc/firmware/fxp-d101s +.It Pa /etc/firmware/fxp-d102 +.It Pa /etc/firmware/fxp-d102c +.It Pa /etc/firmware/fxp-d102e +.El +.Pp +If a file is missing, the driver attempts to operate anyway. +.Sh DIAGNOSTICS +.Bl -diag +.It "fxp0: couldn't map memory" +A fatal initialization error has occurred. +.It "fxp0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "fxp0: Failed to malloc memory" +There are not enough mbufs available for allocation. +.It "fxp0: device timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.It "fxp0: error N, could not read firmware ..." +The device is able to do interrupt coalescing but required firmware file +is missing. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr cardbus 4 , +.Xr icsphy 4 , +.Xr ifmedia 4 , +.Xr inphy 4 , +.Xr intro 4 , +.Xr iophy 4 , +.Xr netintro 4 , +.Xr nsphy 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 2.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +device driver was written by +.An David Greenman . +This manual page was written by +.An David E. O'Brien . diff --git a/static/openbsd/man4/gcu.4 b/static/openbsd/man4/gcu.4 new file mode 100644 index 00000000..0be65044 --- /dev/null +++ b/static/openbsd/man4/gcu.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: gcu.4,v 1.5 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Dariusz Swiderski +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt GCU 4 +.Os +.Sh NAME +.Nm gcu +.Nd Intel EP80579 Global Configuration Unit +.Sh SYNOPSIS +.Cd "gcu* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides access to the miibus that is hidden behind the GCU device. +It is used to control PHYs on embedded designs utilizing Intel's EP80579 +chips. +.Pp +The GCU also provides access to CAN, SSP and TDM signal strength drivers, +but since they are not supported by +.Ox +the driver does not provide any +functionality related to them. +.Sh SEE ALSO +.Xr em 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 +.Pp +Intel's EP80579 Datasheet: +.Lk http://download.intel.com/design/intarch/ep80579/320066.pdf +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Dariusz Swiderski Aq Mt dms@openbsd.org , +partially based on the +.Fx +driver released by Intel under the ISC license. diff --git a/static/openbsd/man4/gdt.4 b/static/openbsd/man4/gdt.4 new file mode 100644 index 00000000..c3e2f802 --- /dev/null +++ b/static/openbsd/man4/gdt.4 @@ -0,0 +1,149 @@ +.\" $OpenBSD: gdt.4,v 1.34 2023/04/12 09:55:22 jsg Exp $ +.\" +.\" Copyright (c) 2000 Niklas Hallqvist +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 12 2023 $ +.Dt GDT 4 +.Os +.Sh NAME +.Nm gdt +.Nd ICP-Vortex and Intel GDT SATA/SCSI RAID controller +.Sh SYNOPSIS +.Cd "gdt* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for ICP-Vortex adapters such as: +.Pp +.Tn GDT4x13RZ , +.Tn GDT4x23RZ , +.Tn GDT6000/6020/6050 , +.Tn GDT6000B/6010 , +.Tn GDT6110/6510 , +.Tn GDT6120/6520 , +.Tn GDT6513RS , +.Tn GDT6518RS , +.Tn GDT6523RS , +.Tn GDT6530 , +.Tn GDT6535 , +.Tn GDT6537 , +.Tn GDT6537RP , +.Tn GDT6537RP1 , +.Tn GDT6537RP2 , +.Tn GDT6550 , +.Tn GDT6555 , +.Tn GDT6557 , +.Tn GDT6557RP , +.Tn GDT6557RP1 , +.Tn GDT6557RP2 , +.Tn GDT6x11RP , +.Tn GDT6x11RP1 , +.Tn GDT6x11RP2 , +.Tn GDT6x15 , +.Tn GDT6x17 , +.Tn GDT6x17RP , +.Tn GDT6x17RP1 , +.Tn GDT6x17RP2 , +.Tn GDT6x18RD , +.Tn GDT6x19RD , +.Tn GDT6x21RP , +.Tn GDT6x21RP1 , +.Tn GDT6x21RP2 , +.Tn GDT6x25 , +.Tn GDT6x27 , +.Tn GDT6x27RP , +.Tn GDT6x27RP1 , +.Tn GDT6x27RP2 , +.Tn GDT6x28RD , +.Tn GDT6x28RS , +.Tn GDT6x29RD , +.Tn GDT6x33RS , +.Tn GDT6x38RD , +.Tn GDT6x38RS , +.Tn GDT6x43RS , +.Tn GDT6x53RS , +.Tn GDT6x58RD , +.Tn GDT6x58RS , +.Tn GDT6x63RS , +.Tn GDT7x13RN , +.Tn GDT7x18RN , +.Tn GDT7x19RN , +.Tn GDT7x23RN , +.Tn GDT7x28RN , +.Tn GDT7x29RN , +.Tn GDT7x38RN , +.Tn GDT7x43RN , +.Tn GDT7x53RN , +.Tn GDT7x58RN , +.Tn GDT7x63RN , +.Tn GDT8x00RZ , +.Tn GDT8x13RZ , +.Tn GDT8x14RZ , +.Tn GDT8x22RZ , +.Tn GDT8x23RZ , +.Tn GDT8x24RZ , +.Tn GDT8x33RZ , +.Tn GDT8x43RZ , +.Tn GDT8x46RZ , +.Tn GDT8x53RZ , +.Tn GDT8x63RZ , +and +.Tn GDT8x86RZ . +.Pp +As well as Intel adapters such as: +.Pp +.Tn SRCU42L , +.Tn SRCU32 , +.Tn SRCZCR , +and +.Tn SRCS14L . +.Pp +Although the controllers are actual RAID controllers, +the driver makes them look just like SCSI controllers. +All RAID configuration is done through the controllers' BIOSes. +.Sh DIAGNOSTICS +.Bl -diag +.It "pci_mem_find: expected mem type 00000000, found 00000002" +This message occurs during autoconfiguration if jumper J4 is set to map +the controller memory below 1MB in physical memory. +The driver primarily wants this jumper to be set the other way round, +but it will work with it in any setting. +If the diagnostic is considered a nuisance, alter jumper J4's setting. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Niklas Hallqvist Aq Mt niklas@openbsd.org , +inspired by the Linux driver by +.An Achim Luebner Aq Mt achim@vortex.de . +.Sh BUGS +An ISA & EISA front-end is needed. +.Pp +The driver does not support transparent raw SCSI mode. +.Pp +It would be nice to configure the RAID units after boot +but the information on how to do that is not public. diff --git a/static/openbsd/man4/gem.4 b/static/openbsd/man4/gem.4 new file mode 100644 index 00000000..619a0d59 --- /dev/null +++ b/static/openbsd/man4/gem.4 @@ -0,0 +1,106 @@ +.\" $OpenBSD: gem.4,v 1.20 2022/03/21 14:56:16 miod Exp $ +.\" +.\" Copyright (c) 2001 Miodrag Vallat. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistribution of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: March 21 2022 $ +.Dt GEM 4 +.Os +.Sh NAME +.Nm gem +.Nd GEM 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "gem* at pci?" +.Cd "gem* at sbus?" +.Cd "bmtphy* at mii?" +.Cd "brgphy* at mii?" +.Cd "eephy* at mii?" +.Cd "gentbi* at mii?" +.Cd "luphy* at mii?" +.Cd "lxtphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various NICs based on the GEM Ethernet controller +chips, including the following: +.Pp +.Bl -bullet -compact -offset indent +.It +Apple GMAC (10/100/1000baseT) +.It +Sun ERI (10/100baseT) +.It +Sun GEM (10/100/1000baseT) +.It +Sun GEM (1000baseSX) +.El +.Pp +It uses an external PHY or an external 10-bit interface. +.Pp +The +.Nm +driver supports several media types, which are selected via the +.Xr ifconfig 8 +command. +The supported media types are: +.Bl -tag -width "media" -offset indent +.It Cm media No autoselect +Attempt to autoselect the media type (default) +.It Cm media No 1000baseT Cm mediaopt No full-duplex +Use 1000baseT on copper, full duplex +.It Cm media No 1000baseT Cm mediaopt No half-duplex +Use 1000baseT on copper, half duplex +.It Cm media No 1000baseSX Cm mediaopt No full-duplex +Use 1000baseSX on fiber, full duplex +.It Cm media No 1000baseSX Cm mediaopt No half-duplex +Use 1000baseSX on fiber, half duplex +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Use 100baseTX, full duplex +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Use 100baseTX, half duplex +.It Cm media No 10baseT Cm mediaopt No full-duplex +Use 10baseT, full duplex +.It Cm media No 10baseT Cm mediaopt No half-duplex +Use 10baseT, half duplex +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr bmtphy 4 , +.Xr brgphy 4 , +.Xr eephy 4 , +.Xr gentbi 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr luphy 4 , +.Xr lxtphy 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/gentbi.4 b/static/openbsd/man4/gentbi.4 new file mode 100644 index 00000000..aae911e5 --- /dev/null +++ b/static/openbsd/man4/gentbi.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: gentbi.4,v 1.3 2008/06/26 05:42:06 ray Exp $ +.\" $NetBSD: gentbi.4,v 1.1 2001/07/25 22:07:12 thorpej Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt GENTBI 4 +.Os +.Sh NAME +.Nm gentbi +.Nd Driver for generic 1000BASE-X ten-bit interfaces +.Sh SYNOPSIS +.Cd "gentbi* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports generic ten-bit interfaces that implement the 1000BASE-X +protocol, including 1000BASE-SX, 1000BASE-LX, and 1000BASE-CX. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/gfrtc.4 b/static/openbsd/man4/gfrtc.4 new file mode 100644 index 00000000..0bcc3bbc --- /dev/null +++ b/static/openbsd/man4/gfrtc.4 @@ -0,0 +1,34 @@ +.\" $OpenBSD: gfrtc.4,v 1.1 2021/04/24 05:16:27 jsg Exp $ +.\" +.\" Copyright (c) 2021 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 24 2021 $ +.Dt GFRTC 4 +.Os +.Sh NAME +.Nm gfrtc +.Nd Google Goldfish real-time clock +.Sh SYNOPSIS +.Cd "gfrtc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the real-time clock interface of Google's Goldfish +Android virtual hardware platform. +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . diff --git a/static/openbsd/man4/gif.4 b/static/openbsd/man4/gif.4 new file mode 100644 index 00000000..fb083135 --- /dev/null +++ b/static/openbsd/man4/gif.4 @@ -0,0 +1,131 @@ +.\" $OpenBSD: gif.4,v 1.33 2018/07/11 06:16:50 jmc Exp $ +.\" $KAME: gif.4,v 1.15 2000/04/19 09:39:42 itojun Exp $ +.\" +.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the project nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 11 2018 $ +.Dt GIF 4 +.Os +.Sh NAME +.Nm gif +.Nd generic tunnel interface +.Sh SYNOPSIS +.Cd "pseudo-device gif" +.Sh DESCRIPTION +The +.Nm +interface is a generic tunnelling pseudo-device. +It can tunnel IPv4, IPv6, and MPLS over IPv4 and IPv6, +with behavior mainly based on RFC 4213 IPv6-over-IPv4. +.Pp +A +.Nm +interface can be created at runtime using the +.Ic ifconfig gif Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +.Pp +The +.Nm +interface must be configured with the +addresses used for the outer header. +This can be done by using +.Xr ifconfig 8 Ns 's +.Ic tunnel +command (which uses the +.Dv SIOCSLIFPHYADDR +ioctl). +.Pp +The addresses of the inner header must be configured by using +.Xr ifconfig 8 +in the normal way. +The routing table can be used to direct packets toward the +.Nm +interface. +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr etherip 4 , +.Xr gre 4 , +.Xr inet 4 , +.Xr inet6 4 , +.Xr ipsec 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh STANDARDS +.Rs +.%A E. Nordmark +.%A R. Gilligan +.%D October 2005 +.%R RFC 4213 +.%T Basic Transition Mechanisms for IPv6 Hosts and Routers +.Re +.Pp +.Rs +.%A T. Worster +.%A Y. Rekhter +.%A E. Rosen +.%D March 2005 +.%R RFC 4023 +.%T Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE) +.Re +.Sh HISTORY +The +.Nm +device first appeared in WIDE hydrangea IPv6 kit. +.Pp +Previously, +.Nm +supported RFC 3378 EtherIP tunnels over +.Xr bridge 4 +interfaces. +This is now handled by +.Xr etherip 4 . +.Sh BUGS +There are many tunnelling protocol specifications, +defined differently from each other. +.Nm +may not interoperate with peers which are based on different specifications, +and are picky about outer header fields. +For example, you cannot usually use +.Nm +to talk with IPsec devices that use IPsec tunnel mode. +.Pp +The current code does not check if the ingress address +.Pq outer source address +configured to +.Nm +makes sense. +Make sure to configure an address which belongs to your node. +Otherwise, your node will not be able to receive packets from the peer, +and your node will generate packets with a spoofed source address. +.Pp +If the outer protocol is IPv6, path MTU discovery for encapsulated packet +may affect communication over the interface. diff --git a/static/openbsd/man4/glenv.4 b/static/openbsd/man4/glenv.4 new file mode 100644 index 00000000..47def43b --- /dev/null +++ b/static/openbsd/man4/glenv.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: glenv.4,v 1.5 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt GLENV 4 +.Os +.Sh NAME +.Nm glenv +.Nd Genesys Logic GL518SM temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "glenv* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Tn Genesys Logic +GL518SM hardware monitor to be used with +the +.Xr sysctl 8 +interface. +.Pp +The GL518SM possesses a voltage sensor, a temperature sensor and two +fan speed sensors. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/glkgpio.4 b/static/openbsd/man4/glkgpio.4 new file mode 100644 index 00000000..aca91d3b --- /dev/null +++ b/static/openbsd/man4/glkgpio.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: glkgpio.4,v 1.1 2019/06/24 21:33:27 kettenis Exp $ +.\" +.\" Copyright (c) 2019 James Hastings +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 24 2019 $ +.Dt GLKGPIO 4 +.Os +.Sh NAME +.Nm glkgpio +.Nd Intel Gemini Lake GPIO controller +.Sh SYNOPSIS +.Cd "glkgpio* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO controllers found on Intel's Gemini +Lake SoC. +It does not provide direct device driver entry points but makes its +functions available to +.Xr acpi 4 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An James Hastings +based on the +.Xr bytgpio 4 +driver by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/gpio.4 b/static/openbsd/man4/gpio.4 new file mode 100644 index 00000000..ebabe04f --- /dev/null +++ b/static/openbsd/man4/gpio.4 @@ -0,0 +1,219 @@ +.\" $OpenBSD: gpio.4,v 1.30 2026/04/21 19:58:21 jca Exp $ +.\" +.\" Copyright (c) 2004 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 21 2026 $ +.Dt GPIO 4 +.Os +.Sh NAME +.Nm gpio +.Nd General Purpose Input/Output +.Sh SYNOPSIS +.Cd "gpio* at ath?" +.Cd "gpio* at bcmgpio?" Pq arm64, armv7 +.Cd "gpio* at glxpcib?" Pq i386 +.Cd "gpio* at gscpcib?" Pq i386 +.Cd "gpio* at isagpio?" +.Cd "gpio* at mpfgpio?" Pq riscv64 +.Cd "gpio* at nsclpcsio?" +.Cd "gpio* at omgpio?" Pq armv7 +.Cd "gpio* at pcagpio?" +.Cd "gpio* at pcaled?" +.Cd "gpio* at sfgpio?" Pq riscv64 +.Cd "gpio* at skgpio?" Pq amd64, i386 +.Cd "gpio* at smtgpio?" Pq riscv64 +.Cd "gpio* at sxipio?" Pq arm64, armv7 +.Cd "gpio0 at voyager?" Pq loongson +.Pp +.In sys/types.h +.In sys/gpio.h +.In sys/ioctl.h +.Sh DESCRIPTION +The +.Nm +device attaches to the GPIO +controller and provides a uniform programming interface to its pins. +.Pp +Each GPIO controller with an attached +.Nm +device has an associated device file under the +.Pa /dev +directory, e.g.\& +.Pa /dev/gpio0 . +Access from userland is performed through +.Xr ioctl 2 +calls on these devices. +.Pp +The layout of the GPIO device is defined at securelevel 0, i.e. typically +during system boot, and cannot be changed later. +GPIO pins can be configured and given a symbolic name and device drivers +that use GPIO pins can be attached to the +.Nm +device at securelevel 0. +All other pins will not be accessible once the runlevel has been raised. +.Sh IOCTL INTERFACE +The following structures and constants are defined in the +.In sys/gpio.h +header file: +.Bl -tag -width XXXX +.It Dv GPIOINFO Fa "struct gpio_info" +Returns information about the GPIO +controller in the +.Fa gpio_info +structure: +.Bd -literal +struct gpio_info { + int gpio_npins; /* total number of pins available */ +}; +.Ed +.It Dv GPIOPINREAD Fa "struct gpio_pin_op" +Returns the input pin value in the +.Fa gpio_pin_op +structure: +.Bd -literal +#define GPIOPINMAXNAME 64 + +struct gpio_pin_op { + char gp_name[GPIOPINMAXNAME]; /* pin name */ + int gp_pin; /* pin number */ + int gp_value; /* value */ +}; +.Ed +.Pp +The +.Fa gp_name +or +.Fa gp_pin +field must be set before calling. +.It Dv GPIOPINWRITE Fa "struct gpio_pin_op" +Writes the output value to the pin. +The value set in the +.Fa gp_value +field must be either +.Dv GPIO_PIN_LOW +(logical 0) or +.Dv GPIO_PIN_HIGH +(logical 1). +On return, the +.Fa gp_value +field contains the old pin state. +.It Dv GPIOPINTOGGLE Fa "struct gpio_pin_op" +Toggles the pin output value, i.e. changes it to the opposite. +.Fa gp_value +field is ignored and on return contains the old pin state. +.It Dv GPIOPINSET Fa "struct gpio_pin_set" +Changes pin configuration flags with the new ones provided in the +.Fa gpio_pin_set +structure: +.Bd -literal +#define GPIOPINMAXNAME 64 + +struct gpio_pin_set { + char gp_name[GPIOPINMAXNAME]; /* pin name */ + int gp_pin; /* pin number */ + int gp_caps; /* pin capabilities (ro) */ + int gp_flags; /* pin configuration flags */ + char gp_name2[GPIOPINMAXNAME]; /* new name */ +}; +.Ed +.Pp +The +.Fa gp_flags +field is a combination of the following flags: +.Pp +.Bl -tag -width GPIO_PIN_OPENDRAIN -compact +.It Dv GPIO_PIN_INPUT +input direction +.It Dv GPIO_PIN_OUTPUT +output direction +.It Dv GPIO_PIN_INOUT +bi-directional +.It Dv GPIO_PIN_OPENDRAIN +open-drain output +.It Dv GPIO_PIN_PUSHPULL +push-pull output +.It Dv GPIO_PIN_TRISTATE +output disabled +.It Dv GPIO_PIN_PULLUP +internal pull-up enabled +.It Dv GPIO_PIN_PULLDOWN +internal pull-down enabled +.It Dv GPIO_PIN_INVIN +invert input +.It Dv GPIO_PIN_INVOUT +invert output +.El +.Pp +Note that the GPIO controller +may not support all of these flags. +On return the +.Fa gp_caps +field contains flags that are supported. +If no flags are specified, the pin configuration stays unchanged. +.Pp +Only GPIO pins that have been set using +.Ar GPIOPINSET +will be accessible at securelevels greater than 0. +.It Dv GPIOPINUNSET Fa "struct gpio_pin_set" +Unset the specified pin, i.e. clear its name and make it inaccessible +at securelevels greater than 0. +.It Dv GPIOATTACH Fa "struct gpio_attach" +Attach the device described in the +.Fa gpio_attach +structure on this gpio device. +.Bd -literal +struct gpio_attach { + char ga_dvname[16]; /* device name */ + int ga_offset; /* pin number */ + u_int32_t ga_mask; /* binary mask */ +}; +.Ed +.It Dv GPIODETACH Fa "struct gpio_attach" +Detach a device from this gpio device that was previously attached using the +.Dv GPIOATTACH +.Xr ioctl 2 . +The +.Fa ga_offset +and +.Fa ga_mask +fields of the +.Fa gpio_attach +structure are ignored. +.El +.Sh FILES +.Bl -tag -width "/dev/gpiou" -compact +.It /dev/gpio Ns Ar u +GPIO device unit +.Ar u +file. +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 3.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . +Runtime device attachment was added by +.An Marc Balmer Aq Mt mbalmer@openbsd.org . +.Sh BUGS +Event capabilities are not supported. diff --git a/static/openbsd/man4/gpiocharger.4 b/static/openbsd/man4/gpiocharger.4 new file mode 100644 index 00000000..061b6995 --- /dev/null +++ b/static/openbsd/man4/gpiocharger.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: gpiocharger.4,v 1.1 2021/09/25 18:40:07 kn Exp $ +.\" +.\" Copyright (c) 2021 Klemens Nanni +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 25 2021 $ +.Dt GPIOCHARGER 4 +.Os +.Sh NAME +.Nm gpiocharger +.Nd GPIO battery charger +.Sh SYNOPSIS +.Cd "gpiocharger* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for battery chargers connected to GPIO pins. +Currently, only power supply status events are supported. +.Pp +The power supply status (connected or disconnected) is set up as a sensor +and can be monitored using +.Xr sysctl 8 +or +.Xr sensorsd 8 . +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Klemens Nanni Aq Mt kn@openbsd.org . diff --git a/static/openbsd/man4/gpiodcf.4 b/static/openbsd/man4/gpiodcf.4 new file mode 100644 index 00000000..80971206 --- /dev/null +++ b/static/openbsd/man4/gpiodcf.4 @@ -0,0 +1,99 @@ +.\" $OpenBSD: gpiodcf.4,v 1.5 2015/06/07 20:13:13 claudio Exp $ +.\" +.\" Copyright (c) 2008 Marc Balmer +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 7 2015 $ +.Dt GPIODCF 4 +.Os +.Sh NAME +.Nm gpiodcf +.Nd DCF77 timedelta sensor through GPIO pin +.Sh SYNOPSIS +.Cd "gpiodcf* at gpio? offset 0 mask 0x1" +.Cd "gpiodcf* at gpio?" +.Sh DESCRIPTION +The +.Nm +driver decodes the DCF77 time signal code using one GPIO pin. +The pin is used as a data signal. +The GPIO pin must be able to read an input. +.Pp +The pin number can be specified in the kernel configuration with the +.Ar offset +locator. +The +.Ar mask +locator should always be 0x1 in this case. +The +.Ar offset +and +.Ar mask +can also be specified when +.Nm +is attached at runtime using the +.Dv GPIOATTACH +.Xr ioctl 2 +on the +.Xr gpio 4 +device. +.Pp +.Nm +implements a timedelta sensor and the delta (in nanoseconds) between the +received time information and the local time can be accessed through the +.Xr sysctl 8 +interface. +The clock type is indicated in the sensor description: +.Bl -tag -width "CRITICALXX" -offset indent +.It DCF77 +German DCF77 time signal station +(77.5 kHz longwave transmitter located in Mainflingen near Frankfurt). +.El +.Pp +The quality of the timedelta is reported as the sensor status: +.Bl -tag -width "CRITICALXX" -offset indent +.It UNKNOWN +No valid time information has been received yet. +.It OK +The time information is valid and the timedelta is safe to use for +applications like +.Xr ntpd 8 . +.It WARN +The time information is still valid, but no new time information has been +decoded for at least 5 minutes due to a reception or parity error. +The timedelta should be used with care. +.It CRITICAL +No valid time information has been received for more than 15 minutes since +the sensor state degraded from OK to WARN. +This is an indication that hardware should be checked +to see if it is still functional. +The timedelta will eventually degrade to a lie +as all computer internal clocks have a drift. +.El +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 , +.Xr ntpd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marc Balmer Aq Mt mbalmer@openbsd.org . diff --git a/static/openbsd/man4/gpioiic.4 b/static/openbsd/man4/gpioiic.4 new file mode 100644 index 00000000..382c8913 --- /dev/null +++ b/static/openbsd/man4/gpioiic.4 @@ -0,0 +1,80 @@ +.\" $OpenBSD: gpioiic.4,v 1.8 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt GPIOIIC 4 +.Os +.Sh NAME +.Nm gpioiic +.Nd GPIO I2C controller +.Sh SYNOPSIS +.Cd "gpioiic* at gpio? offset 0 mask 0x3 flag 0x0" +.Cd "gpioiic* at gpio?" +.Cd "iic* at gpioiic?" +.Sh DESCRIPTION +The +.Nm +driver allows bit-banging an I2C bus as a master using two GPIO pins. +By default the first pin is used as a serial data (SDA) signal and the +second as a serial clock (SCL). +If the flag locator is set to 0x01, the order of the SDA and SCL signals +is reversed. +Both GPIO pins must be able to drive an output and the SDA pin must be +also able to read an input. +.Pp +The pins can be specified in the kernel configuration with the +.Ar offset +and the +.Ar mask +locators. +The +.Ar offset +and +.Ar mask +can also be specified when +.Nm +is attached at runtime using the +.Dv GPIOATTACH +.Xr ioctl 2 +on the +.Xr gpio 4 +device. +Each bit in the +.Ar mask +locator defines one pin; the pin number is calculated as an addition of +the bit position and the +.Ar offset +locator. +For example, +.Ar offset 17 +and +.Ar mask 0x5 +defines pin numbers 17 and 19. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/gpiokeys.4 b/static/openbsd/man4/gpiokeys.4 new file mode 100644 index 00000000..839b3abb --- /dev/null +++ b/static/openbsd/man4/gpiokeys.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: gpiokeys.4,v 1.1 2021/11/09 16:16:11 kn Exp $ +.\" +.\" Copyright (c) 2021 Klemens Nanni +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 9 2021 $ +.Dt GPIOKEYS 4 +.Os +.Sh NAME +.Nm gpiokeys +.Nd GPIO keys +.Sh SYNOPSIS +.Cd "gpiokeys* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver handles events triggered by GPIO keys. +Currently, only lid status events are supported. +.Pp +The lid status is set up as a sensor and can be monitored using +.Xr sysctl 8 +or +.Xr sensorsd 8 . +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Klemens Nanni Aq Mt kn@openbsd.org . diff --git a/static/openbsd/man4/gpioleds.4 b/static/openbsd/man4/gpioleds.4 new file mode 100644 index 00000000..30f5bad7 --- /dev/null +++ b/static/openbsd/man4/gpioleds.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: gpioleds.4,v 1.1 2021/09/25 10:43:23 kn Exp $ +.\" +.\" Copyright (c) 2021 Klemens Nanni +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 25 2021 $ +.Dt GPIOLEDS 4 +.Os +.Sh NAME +.Nm gpioleds +.Nd GPIO LEDs +.Sh SYNOPSIS +.Cd "gpioleds* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for LEDs connected to GPIO pins. +.Pp +Currently, LEDs are only set to their default state, +e.g. to indicate the power status of the system. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Klemens Nanni Aq Mt kn@openbsd.org . diff --git a/static/openbsd/man4/gpioow.4 b/static/openbsd/man4/gpioow.4 new file mode 100644 index 00000000..8c888745 --- /dev/null +++ b/static/openbsd/man4/gpioow.4 @@ -0,0 +1,66 @@ +.\" $OpenBSD: gpioow.4,v 1.7 2013/07/16 16:05:48 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt GPIOOW 4 +.Os +.Sh NAME +.Nm gpioow +.Nd 1-Wire bus bit-banging through GPIO pin +.Sh SYNOPSIS +.Cd "gpioow* at gpio? offset 0 mask 0x1" +.Cd "gpioow* at gpio?" +.Cd "onewire* at gpioow?" +.Sh DESCRIPTION +The +.Nm +driver allows bit-banging a 1-Wire bus as a master using one GPIO pin. +The pin is used as a data signal. +The GPIO pin must be able to drive an output and read an input. +.Pp +The pin number can be specified in the kernel configuration with the +.Ar offset +locator. +The +.Ar mask +locator should always be 0x1 in this case. +The +.Ar offset +and +.Ar mask +can also be specified when +.Nm +is attached at runtime using the +.Dv GPIOATTACH +.Xr ioctl 2 +on the +.Xr gpio 4 +device. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 , +.Xr onewire 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/graphaudio.4 b/static/openbsd/man4/graphaudio.4 new file mode 100644 index 00000000..24cbcf1c --- /dev/null +++ b/static/openbsd/man4/graphaudio.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: graphaudio.4,v 1.2 2021/04/08 11:52:27 jmc Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 8 2021 $ +.Dt GRAPHAUDIO 4 +.Os +.Sh NAME +.Nm graphaudio +.Nd audio graph card +.Sh SYNOPSIS +.Cd "graphaudio* at fdt?" +.Cd "audio* at graphaudio?" +.Sh DESCRIPTION +.Nm +is a generic driver for audio cards. +It represents the logical connection of audio components like I2S +controllers and codecs. +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 , +.Xr simpleaudio 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org +based on the +.Xr simpleaudio 4 +driver by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/gre.4 b/static/openbsd/man4/gre.4 new file mode 100644 index 00000000..131a3a28 --- /dev/null +++ b/static/openbsd/man4/gre.4 @@ -0,0 +1,797 @@ +.\" $OpenBSD: gre.4,v 1.86 2025/11/24 02:32:54 jsg Exp $ +.\" $NetBSD: gre.4,v 1.10 1999/12/22 14:55:49 kleink Exp $ +.\" +.\" Copyright 1998 (c) The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Heiko W. Rupp +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 24 2025 $ +.Dt GRE 4 +.Os +.Sh NAME +.Nm gre , +.Nm mgre , +.Nm egre , +.Nm nvgre +.Nd Generic Routing Encapsulation network device +.Sh SYNOPSIS +.Cd "pseudo-device gre" +.Sh DESCRIPTION +The +.Nm gre +pseudo-device provides interfaces for tunnelling protocols across +IPv4 and IPv6 networks using the Generic Routing Encapsulation (GRE) +encapsulation protocol. +.Pp +GRE datagrams (IP protocol number 47) consist of a GRE header +and an outer IP header for encapsulating another protocol's datagram. +The GRE header specifies the type of the encapsulated datagram, +allowing for the tunnelling of multiple protocols. +.Pp +Different tunnels between the same endpoints may be distinguished +by an optional Key field in the GRE header. +The Key field may be partitioned to carry flow information about the +encapsulated traffic to allow better use of multipath links. +.Pp +This pseudo driver provides the clonable network interfaces: +.Bl -tag -width nvgreX +.It Nm gre +Point-to-point Layer 3 tunnel interfaces. +.It Nm mgre +Point-to-multipoint Layer 3 tunnel interfaces. +.It Nm egre +Point-to-point Ethernet tunnel interfaces. +.It Nm nvgre +Network Virtualization using Generic Routing Encapsulation +(NVGRE) overlay Ethernet network interfaces. +.It Nm eoip +MikroTik Ethernet over IP tunnel interfaces. +.El +.Pp +See +.Xr eoip 4 +for information regarding MikroTik Ethernet over IP interfaces. +.Pp +All GRE packet processing in the system is allowed or denied by setting the +.Va net.inet.gre.allow +.Xr sysctl 8 +variable. +To allow GRE packet processing, set +.Va net.inet.gre.allow +to 1. +.Pp +.Nm gre , +.Nm mgre , +.Nm egre , +and +.Nm nvgre +interfaces can be created at runtime using the +.Ic ifconfig iface Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +.Pp +For correct operation, encapsulated traffic must not be routed +over the interface itself. +This can be implemented by adding a distinct or a more specific +route to the tunnel destination than the hosts or networks routed +via the tunnel interface. +Alternatively, the tunnel traffic may be configured in a separate +routing table to the encapsulated traffic. +.Ss Point-to-Point Layer 3 GRE tunnel interfaces (gre) +A +.Nm gre +tunnel can encapsulate IPv4, IPv6, and MPLS packets. +The MTU is set to 1476 by default to match the value used by Cisco +routers. +.Pp +.Nm gre +supports sending keepalive packets to the remote endpoint which +allows tunnel failure to be detected. +To return keepalives, the remote host must be configured to forward +IP packets received from inside the tunnel back to the address of +the local tunnel endpoint. +.Pp +.Nm gre +interfaces may be configured to receive IPv4 packets in +Web Cache Communication Protocol (WCCP) +encapsulation by setting the +.Cm link0 +flag on the interface. +WCCP reception may be enabled globally by setting the +.Va net.inet.gre.wccp +sysctl value to 1. +Some magic with the packet filter configuration +and a caching proxy like squid are needed +to do anything useful with these packets. +This sysctl requires +.Va net.inet.gre.allow +to also be set. +.Ss Point-to-Multipoint Layer 3 GRE tunnel interfaces (mgre) +.Nm mgre +interfaces can encapsulate IPv4, IPv6, and MPLS packets. +Unlike a point-to-point interface, +.Nm mgre +interfaces are configured with an address on an IP subnet. +Peers on that subnet are mapped to the addresses of multiple tunnel +endpoints. +.Pp +The MTU is set to 1476 by default to match the value used by Cisco +routers. +.Ss Point-to-Point Ethernet over GRE tunnel interfaces (egre) +An +.Nm egre +tunnel interface carries Ethernet over GRE (EoGRE). +Ethernet traffic is encapsulated using Transparent Ethernet (0x6558) +as the protocol identifier in the GRE header, as per RFC 1701. +The MTU is set to 1500 by default. +.Ss Network Virtualization using GRE interfaces (nvgre) +.Nm nvgre +interfaces allow construction of virtual overlay Ethernet networks +on top of an IPv4 or IPv6 underlay network as per RFC 7637. +Ethernet traffic is encapsulated using Transparent Ethernet (0x6558) +as the protocol identifier in the GRE header, a 24-bit Virtual +Subnet ID (VSID), and an 8-bit FlowID. +.Pp +By default the MTU of an +.Nm nvgre +interface is set to 1500, and the Don't Fragment flag is set. +The MTU on the network interfaces carrying underlay network traffic +must be raised to accommodate this and the overhead of the NVGRE +encapsulation, or the +.Nm nvgre +interface must be reconfigured for less capable underlays. +.Pp +The underlay network parameters on a +.Nm nvgre +interface are a unicast tunnel source address, +a multicast tunnel destination address, +and a parent network interface. +The unicast source address is used as the NVE Provider Address (PA) +on the underlay network. +The parent interface is used to identify which interface the multicast +group should be joined to. +.Pp +The multicast group is used to transport broadcast and multicast +traffic from the overlay to other participating NVGRE endpoints. +It is also used to flood unicast traffic to Ethernet addresses in +the overlay with an unknown association to a NVGRE endpoint. +Traffic received from other NVGRE endpoints, +either to the Provider Address or via the multicast group, +is used to learn associations between Ethernet addresses in the +overlay network and the Provider Addresses of NVGRE endpoints in +the underlay. +.Ss Programming Interface +.Nm gre , +.Nm mgre , +.Nm egre , +and +.Nm nvgre +interfaces support the following +.Xr ioctl 2 +calls for configuring tunnel options: +.Bl -tag -width indent -offset 3n +.It Dv SIOCSLIFPHYADDR Fa "struct if_laddrreq *" +Set the IPv4 or IPv6 addresses for the encapsulating IP packets. +The addresses may only be configured while the interface is down. +.Pp +.Nm gre +and +.Nm egre +interfaces support configuration of unicast IP addresses as the +tunnel endpoints. +.Pp +.Nm mgre +interfaces support configuration of a unicast local IP address, +and require an +.Dv AF_UNSPEC +destination address. +.Pp +.Nm nvgre +interfaces support configuration of a unicast IP address as the +local endpoint and a multicast group address as the destination +address. +.It Dv SIOCGLIFPHYADDR Fa "struct if_laddrreq *" +Get the addresses used for the encapsulating IP packets. +.It Dv SIOCDIFPHYADDR Fa "struct ifreq *" +Clear the addresses used for the encapsulating IP packets. +The addresses may only be cleared while the interface is down. +.It Dv SIOCSVNETID Fa "struct ifreq *" +Configure a virtual network identifier for use in the GRE Key header. +The virtual network identifier may only be configured while the +interface is down. +.Pp +.Nm gre , +.Nm mgre , +and +.Nm egre +interfaces configured with a virtual network identifier will enable +the use of the GRE Key header. +The Key is a 32-bit value by default, or a 24-bit value when the +virtual network flow identifier is enabled. +.Pp +.Nm nvgre +interfaces use the virtual network identifier in the 24-bit +Virtual Subnet Identifier (VSID) +aka +Tenant Network Identifier (TNI) +field in of the GRE Key header. +.It Dv SIOCGVNETID Fa "struct ifreq *" +Get the virtual network identifier used in the GRE Key header. +.It Dv SIOCDVNETID Fa "struct ifreq *" +Disable the use of the virtual network identifier. +The virtual network identifier may only be disabled while the interface +is down. +.Pp +When the virtual network identifier is disabled on +.Nm gre , +.Nm mgre , +and +.Nm egre +interfaces, it disables the use of the GRE Key header. +.Pp +.Nm nvgre +interfaces do not support this ioctl as a +Virtual Subnet Identifier +is required by the protocol. +.It Dv SIOCSLIFPHYRTABLE Fa "struct ifreq *" +Set the routing table the tunnel traffic operates in. +The routing table may only be configured while the interface is down. +.It Dv SIOCGLIFPHYRTABLE Fa "struct ifreq *" +Get the routing table the tunnel traffic operates in. +.It Dv SIOCSLIFPHYTTL Fa "struct ifreq *" +Set the Time-To-Live field in IPv4 encapsulation headers, or the +Hop Limit field in IPv6 encapsulation headers. +.Pp +.Nm gre +and +.Nm mgre +interfaces configured with a TTL of -1 will copy the TTL in and out +of the encapsulated protocol headers. +.It Dv SIOCGLIFPHYTTL Fa "struct ifreq *" +Get the value used in the Time-To-Live field in an IPv4 encapsulation +header or the Hop Limit field in an IPv6 encapsulation header. +.It Dv SIOCSLIFPHYDF Fa "struct ifreq *" +Configure whether the tunnel traffic sent by the interface can be +fragmented or not. +This sets the Don't Fragment (DF) bit on IPv4 packets, +and disables fragmentation of IPv6 packets. +.It Dv SIOCGLIFPHYDF Fa "struct ifreq *" +Get whether the tunnel traffic sent by the interface can be fragmented +or not. +.It Dv SIOCSTXHPRIO Fa "struct ifreq *" +Set the priority value used in the Type of Service field in IPv4 +headers, or the Traffic Class field in IPv6 headers. +Values may be from 0 to 7, or +.Dv IF_HDRPRIO_PACKET +to specify that the current priority of a packet should be used. +.Pp +.Nm gre +and +.Nm mgre +interfaces configured with a value of +.Dv IF_HDRPRIO_PAYLOAD +will copy the priority from encapsulated protocol headers. +.It Dv SIOCGTXHPRIO Fa "struct ifreq *" +Get the priority value used in the Type of Service field in IPv4 +headers, or the Traffic Class field in IPv6 headers. +.El +.Pp +.Nm gre , +.Nm mgre , +and +.Nm egre +interfaces support the following +.Xr ioctl 2 +calls: +.Bl -tag -width indent -offset 3n +.It Dv SIOCSVNETFLOWID Fa "struct ifreq *" +Enable or disable the partitioning of the optional GRE Key header +into a 24-bit virtual network identifier and an 8-bit flow +identifier. +.Pp +The interface +must already be configured with a virtual network identifier before +enabling flow identifiers in the GRE Key header. +The configured virtual network identify must also fit into 24 bits. +.It Dv SIOCDVNETFLOWID Fa "struct ifreq *" +Get the status of the partitioning of the GRE key. +.El +.Pp +.Nm gre +interfaces support the following +.Xr ioctl 2 +calls: +.Bl -tag -width indent -offset 3n +.It Dv SIOCSETKALIVE Fa "struct ifkalivereq *" +Enable the transmission of keepalive packets to detect tunnel failure. +.\" Keepalives may only be configured while the interface is down. +.Pp +Setting the keepalive period or count to 0 disables keepalives on +the tunnel. +.It Dv SIOCGETKALIVE Fa "struct ifkalivereq *" +Get the configuration of keepalive packets. +.El +.Pp +.Nm nvgre +interfaces support the following +.Xr ioctl 2 +calls: +.Bl -tag -width indent -offset 3n +.It Dv SIOCSIFPARENT Fa "struct if_parent *" +Configure which interface will be joined to the multicast group +specified by the tunnel destination address. +The parent interface may only be configured while the interface is +down. +.It Dv SIOCGIFPARENT Fa "struct if_parent *" +Get the name of the interface used for multicast communication. +.It Dv SIOCDIFPARENT Fa "struct ifreq *" +Remove the configuration of the interface used for multicast +communication. +.\" bridge(4) ioctls should go here too. +.El +.Ss Security Considerations +The GRE protocol in all its flavours does not provide any integrated +security features. +GRE should only be deployed on trusted private networks, +or protected with IPsec to add authentication and encryption for +confidentiality. +IPsec is especially recommended when transporting GRE over the +public internet. +.Pp +The Packet Filter +.Xr pf 4 +can be used to filter tunnel traffic with endpoint policies +.Xr pf.conf 5 . +.Pp +The Time-to-Live (TTL) value of a tunnel can be set to 1 or a low +value to restrict the traffic to the local network: +.Bd -literal -offset indent +# ifconfig gre0 tunnelttl 1 +.Ed +.Sh EXAMPLES +.Ss Point-to-Point Layer 3 GRE tunnel interfaces (gre) example +.Bd -literal +Host X ---- Host A ------------ tunnel ------------ Cisco D ---- Host E + \e / + \e / + +------ Host B ------ Host C ------+ +.Ed +.Pp +On Host A +.Pq Ox : +.Bd -literal -offset indent +# route add default B +# ifconfig greN create +# ifconfig greN A D netmask 0xffffffff up +# ifconfig greN tunnel A D +# route add E D +.Ed +.Pp +On Host D (Cisco): +.Bd -literal -offset indent +Interface TunnelX + ip unnumbered D ! e.g. address from Ethernet interface + tunnel source D ! e.g. address from Ethernet interface + tunnel destination A +ip route C +ip route A mask C +ip route X mask tunnelX +.Ed +.Pp +OR +.Pp +On Host D +.Pq Ox : +.Bd -literal -offset indent +# route add default C +# ifconfig greN create +# ifconfig greN D A +# ifconfig greN tunnel D A +.Ed +.Pp +To reach Host A over the tunnel (from Host D), there has to be an +alias on Host A for the Ethernet interface: +.Pp +.Dl # ifconfig alias Y +.Pp +and on the Cisco: +.Pp +.Dl ip route Y mask tunnelX +.Pp +.Nm gre +keepalive packets may be enabled with +.Xr ifconfig 8 +like this: +.Bd -literal -offset indent +# ifconfig greN keepalive period count +.Ed +.Pp +This will send a keepalive packet every +.Ar period +seconds. +If no response is received in +.Ar count +* +.Ar period +seconds, the link is considered down. +To return keepalives, the remote host must be configured to forward packets: +.Bd -literal -offset indent +# sysctl net.inet.ip.forwarding=1 +.Ed +.Pp +If +.Xr pf 4 +is enabled then it is necessary to add a pass rule specific for the keepalive +packets. +The rule must use +.Cm no state +because the keepalive packet is entering the network stack multiple times. +In most cases the following should work: +.Bd -literal -offset indent +pass quick on gre proto gre no state +.Ed +.Ss Point-to-Multipoint Layer 3 GRE tunnel interfaces (mgre) example +.Nm mgre +can be used to build a point-to-multipoint tunnel network to several +hosts using a single +.Nm mgre +interface. +.Pp +In this example the host A has an outer IP of 198.51.100.12, host +B has 203.0.113.27, and host C has 203.0.113.254. +.Pp +Addressing within the tunnel is done using 192.0.2.0/24: +.Bd -literal + +--- Host B + / + / +Host A --- tunnel ---+ + \e + \e + +--- Host C +.Ed +.Pp +On Host A: +.Bd -literal -offset indent +# ifconfig mgreN create +# ifconfig mgreN tunneladdr 198.51.100.12 +# ifconfig mgreN inet 192.0.2.1 netmask 0xffffff00 up +.Ed +.Pp +On Host B: +.Bd -literal -offset indent +# ifconfig mgreN create +# ifconfig mgreN tunneladdr 203.0.113.27 +# ifconfig mgreN inet 192.0.2.2 netmask 0xffffff00 up +.Ed +.Pp +On Host C: +.Bd -literal -offset indent +# ifconfig mgreN create +# ifconfig mgreN tunneladdr 203.0.113.254 +# ifconfig mgreN inet 192.0.2.3 netmask 0xffffff00 up +.Ed +.Pp +To reach Host B over the tunnel (from Host A), there has to be a +route on Host A specifying the next-hop: +.Pp +.Dl # route add -host 192.0.2.2 203.0.113.27 -iface -ifp mgreN +.Pp +Similarly, to reach Host A over the tunnel from Host B, a route must +be present on B with A's outer IP as next-hop: +.Pp +.Dl # route add -host 192.0.2.1 198.51.100.12 -iface -ifp mgreN +.Pp +The same tunnel interface can then be used between host B and C by +adding the appropriate routes, making the network any-to-any instead +of hub-and-spoke: +.Pp +On Host B: +.Dl # route add -host 192.0.2.3 203.0.113.254 -iface -ifp mgreN +.Pp +On Host C: +.Dl # route add -host 192.0.2.2 203.0.113.27 -iface -ifp mgreN +.Ss Point-to-Point Ethernet over GRE tunnel interfaces (egre) example +.Nm egre +can be used to carry Ethernet traffic between two endpoints over +an IP network, including the public internet. +This can also be achieved using +.Xr etherip 4 , +but +.Nm egre +offers the ability to carry different Ethernet networks between the +same endpoints by using virtual network identifiers to distinguish +between them. +.Pp +For example, a pair of routers separated by the internet could +bridge several Ethernet networks using +.Nm egre +and +.Xr veb 4 . +.Pp +In this example the first router has a public IP of 192.0.2.1, and +the second router has 203.0.113.2. +They are connecting the Ethernet networks on two +.Xr vlan 4 +interfaces over the internet. +A separate +.Nm egre +tunnel is created for each VLAN and given different virtual network +identifiers so the routers can tell which network the encapsulated +traffic is for. +The +.Nm egre +interfaces are explicitly configured to provide the same MTU as the +.Xr vlan 4 +interfaces (1500 bytes) with fragmentation enabled so they can be +carried over the internet, which has the same or lower MTU. +.Pp +At the first site: +.Bd -literal -offset indent +# ifconfig vlan0 vnetid 100 +# ifconfig egre0 create +# ifconfig egre0 tunnel 192.0.2.1 203.0.113.2 +# ifconfig egre0 vnetid 100 +# ifconfig egre0 mtu 1500 -tunneldf +# ifconfig egre0 up +# ifconfig veb0 add vlan0 add egre0 up +# ifconfig vlan1 vnetid 200 +# ifconfig egre1 create +# ifconfig egre1 tunnel 192.0.2.1 203.0.113.2 +# ifconfig egre1 vnetid 200 +# ifconfig egre1 mtu 1500 -tunneldf +# ifconfig egre1 up +# ifconfig veb1 add vlan1 add egre1 up +.Ed +.Pp +At the second site: +.Bd -literal -offset indent +# ifconfig vlan0 vnetid 100 +# ifconfig egre0 create +# ifconfig egre0 tunnel 203.0.113.2 192.0.2.1 +# ifconfig egre0 vnetid 100 +# ifconfig egre0 mtu 1500 -tunneldf +# ifconfig egre0 up +# ifconfig veb0 add vlan0 add egre0 up +# ifconfig vlan1 vnetid 200 +# ifconfig egre1 create +# ifconfig egre1 tunnel 203.0.113.2 192.0.2.1 +# ifconfig egre1 vnetid 200 +# ifconfig egre1 mtu 1500 -tunneldf +# ifconfig egre1 up +# ifconfig veb1 add vlan1 add egre1 up +.Ed +.Ss Network Virtualization using GRE interfaces (nvgre) example +NVGRE can be used to build a distinct logical Ethernet network +on top of another network. +.Nm nvgre +is therefore like a +.Xr vlan 4 +interface configured on top of a physical Ethernet interface, +except it can sit on any IP network capable of multicast. +.Pp +The following shows a basic +.Nm nvgre +configuration and an equivalent +.Xr vlan 4 +configuration. +In the examples, 192.168.0.1/24 will be the network configured on +the relevant virtual interfaces. +The NVGRE underlay network will be configured on 100.64.10.0/24, +and will use 239.1.1.100 as the multicast group address. +.Pp +The +.Xr vlan 4 +interface only relies on Ethernet, it does not rely on IP configuration +on the parent interface: +.Bd -literal -offset indent +# ifconfig em0 up +# ifconfig vlan0 create +# ifconfig vlan0 parent em0 +# ifconfig vlan0 vnetid 10 +# ifconfig vlan0 inet 192.168.0.1/24 +# ifconfig vlan0 up +.Ed +.Pp +.Nm nvgre +relies on IP configuration on the parent interface, and an MTU large +enough to carry the encapsulated traffic: +.Bd -literal -offset indent +# ifconfig em0 mtu 1600 +# ifconfig em0 inet 100.64.10.1/24 +# ifconfig em0 up +# ifconfig nvgre0 create +# ifconfig nvgre0 parent em0 tunnel 100.64.10.1 239.1.1.100 +# ifconfig nvgre0 vnetid 10010 +# ifconfig nvgre0 inet 192.168.0.1/24 +# ifconfig nvgre0 up +.Ed +.Pp +NVGRE is intended for use in a multitenant datacentre environment to +provide each customer with distinct Ethernet networks as needed, +but without running into the limit on the number of VLAN tags, and +without requiring reconfiguration of the underlying Ethernet +infrastructure. +Another way to look at it is NVGRE can be used to construct multipoint +Ethernet VPNs across an IP core. +.Pp +For example, if a customer has multiple virtual machines running in +.Xr vmm 4 +on distinct physical hosts, +.Nm nvgre +and +.Xr veb 4 +can be used to provide network connectivity between the +.Xr tap 4 +interfaces connected to the virtual machines. +If there are 3 virtual machines, all using tap0 on each hosts, and +those hosts are connected to the same network described above, +.Nm nvgre +with a distinct virtual network identifier and multicast group can +be created for them. +The following assumes nvgre1 and veb1 have already been created +on each host, and em0 has had the MTU raised: +.Pp +On physical host 1: +.Bd -literal -offset indent +# ifconfig em0 inet 100.64.10.10/24 +# ifconfig nvgre1 parent em0 tunnel 100.64.10.10 239.1.1.111 +# ifconfig nvgre1 vnetid 10011 +# ifconfig veb1 add nvgre1 add tap0 up +.Ed +.Pp +On physical host 2: +.Bd -literal -offset indent +# ifconfig em0 inet 100.64.10.11/24 +# ifconfig nvgre1 parent em0 tunnel 100.64.10.11 239.1.1.111 +# ifconfig nvgre1 vnetid 10011 +# ifconfig veb1 add nvgre1 add tap0 up +.Ed +.Pp +On physical host 3: +.Bd -literal -offset indent +# ifconfig em0 inet 100.64.10.12/24 +# ifconfig nvgre1 parent em0 tunnel 100.64.10.12 239.1.1.111 +# ifconfig nvgre1 vnetid 10011 +# ifconfig veb1 add nvgre1 add tap0 up +.Ed +.Pp +Being able to carry working multicast and jumbo frames over the +public internet is unlikely, which makes it difficult to use NVGRE +to extended Ethernet VPNs between different sites. +.Nm nvgre +and +.Nm egre +can be bridged together to provide such connectivity. +See the +.Nm egre +section for an example. +.Sh SEE ALSO +.Xr eoip 4 , +.Xr inet 4 , +.Xr ip 4 , +.Xr netintro 4 , +.Xr options 4 , +.Xr hostname.if 5 , +.Xr protocols 5 , +.Xr ifconfig 8 , +.Xr netstart 8 , +.Xr sysctl 8 +.Sh STANDARDS +.Rs +.%A S. Hanks +.%A "T. Li" +.%A D. Farinacci +.%A P. Traina +.%D October 1994 +.%R RFC 1701 +.%T Generic Routing Encapsulation (GRE) +.Re +.Pp +.Rs +.%A S. Hanks +.%A "T. Li" +.%A D. Farinacci +.%A P. Traina +.%D October 1994 +.%R RFC 1702 +.%T Generic Routing Encapsulation over IPv4 networks +.Re +.Pp +.Rs +.%A D. Farinacci +.%A "T. Li" +.%A S. Hanks +.%A D. Meyer +.%A P. Traina +.%D March 2000 +.%R RFC 2784 +.%T Generic Routing Encapsulation (GRE) +.Re +.Pp +.Rs +.%A G. Dommety +.%D September 2000 +.%R RFC 2890 +.%T Key and Sequence Number Extensions to GRE +.Re +.Pp +.Rs +.%A T. Worster +.%A Y. Rekhter +.%A E. Rosen +.%D March 2005 +.%R RFC 4023 +.%T Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE) +.Re +.Pp +.Rs +.%A P. Garg +.%A Y. Wang +.%D September 2015 +.%R RFC 7637 +.%T NVGRE: Network Virtualization Using Generic Routing Encapsulation +.Re +.Pp +.Rs +.%U https://tools.ietf.org/html/draft-ietf-wrec-web-pro-00.txt +.%T Web Cache Coordination Protocol V1.0 +.Re +.Pp +.Rs +.%U https://tools.ietf.org/html/draft-wilson-wrec-wccp-v2-00.txt +.%T Web Cache Coordination Protocol V2.0 +.Re +.Sh AUTHORS +.An Heiko W. Rupp Aq Mt hwr@pilhuhn.de +.Sh CAVEATS +RFC 1701 and RFC 2890 describe a variety of optional GRE header +fields in the protocol that are not implemented in the +.Nm gre +and +.Nm egre +interface drivers. +The only optional field the drivers implement support for is the +Key header. +.Pp +.Nm gre +interfaces skip the redirect header in WCCPv2 GRE encapsulated packets. +.Pp +The NVGRE RFC specifies VSIDs 0 (0x0) to 4095 (0xfff) as reserved +for future use, and VSID 16777215 (0xffffff) for use for vendor-specific +endpoint communication. +The NVGRE RFC also explicitly states encapsulated Ethernet packets +must not contain IEEE 802.1Q (VLAN) tags. +The +.Nm nvgre +driver does not restrict the use of these VSIDs, and does not prevent +the configuration of child +.Xr vlan 4 +interfaces or the bridging of VLAN tagged traffic across the tunnel. +These non-restrictions allow non-compliant tunnels to be configured +which may not interoperate with other vendors. diff --git a/static/openbsd/man4/gscsio.4 b/static/openbsd/man4/gscsio.4 new file mode 100644 index 00000000..a4b3fc0b --- /dev/null +++ b/static/openbsd/man4/gscsio.4 @@ -0,0 +1,61 @@ +.\" $OpenBSD: gscsio.4,v 1.6 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2004 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt GSCSIO 4 +.Os +.Sh NAME +.Nm gscsio +.Nd National Semiconductor Geode SC1100 I2C controller +.Sh SYNOPSIS +.Cd "gscsio* at isa?" +.Cd "iic* at gscsio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the National Semiconductor Geode SC1100 +System-on-Chip Super I/O module. +The Super I/O (SIO) module incorporates one serial port, an infrared +communication port, two ACCESS.bus interface (ACB) ports, system wakeup +control (SWC), and a real-time clock (RTC). +Only the ACCESS.bus interface is currently supported. +.Pp +ACB is a two-wire synchronous serial interface compatible with the +Philips' +.Tn I2C +bus, and can be accessed through the +.Xr iic 4 +framework. +The +.Nm +driver +programs the ACB port to work with a standard +.Tn I2C +frequency 100kHz. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr isa 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/hds.4 b/static/openbsd/man4/hds.4 new file mode 100644 index 00000000..877c1bd1 --- /dev/null +++ b/static/openbsd/man4/hds.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: hds.4,v 1.2 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2011 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt HDS 4 +.Os +.Sh NAME +.Nm hds +.Nd Hitachi Modular Storage SCSI devices +.Sh SYNOPSIS +.Cd "hds* at scsibus?" +.Sh DESCRIPTION +The +.Nm +driver attaches to Hitachi Modular Storage logical units. +Each path to an active service processor attached to by +.Nm +is presented to +.Xr mpath 4 +which uses it as a backend to the logical unit attached to its own +.Xr scsibus 4 . +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr intro 4 , +.Xr mpath 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.0 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/hiclock.4 b/static/openbsd/man4/hiclock.4 new file mode 100644 index 00000000..e41882c8 --- /dev/null +++ b/static/openbsd/man4/hiclock.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: hiclock.4,v 1.2 2018/08/27 20:36:49 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 27 2018 $ +.Dt HICLOCK 4 +.Os +.Sh NAME +.Nm hiclock +.Nd HiSilicon clock controller +.Sh SYNOPSIS +.Cd "hiclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the clock signals for integrated components of HiSilicon SoCs. +.Sh SEE ALSO +.Xr hireset 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/hidwusb.4 b/static/openbsd/man4/hidwusb.4 new file mode 100644 index 00000000..64537f19 --- /dev/null +++ b/static/openbsd/man4/hidwusb.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: hidwusb.4,v 1.1 2018/08/27 20:05:56 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 27 2018 $ +.Dt HIDWUSB 4 +.Os +.Sh NAME +.Nm hidwusb +.Nd HiSilicon USB 3.0 glue logic +.Sh SYNOPSIS +.Cd "hidwusb* at fdt?" +.Cd "xhci* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the interface logic for the Synopsys DesignWare USB +3.0 controller on HiSilicon SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr xhci 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/hil.4 b/static/openbsd/man4/hil.4 new file mode 100644 index 00000000..ef77599b --- /dev/null +++ b/static/openbsd/man4/hil.4 @@ -0,0 +1,80 @@ +.\" $OpenBSD: hil.4,v 1.11 2014/03/18 22:36:31 miod Exp $ +.\" +.\" Copyright (c) 2003 Miodrag Vallat. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistribution of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: March 18 2014 $ +.Dt HIL 4 +.Os +.Sh NAME +.Nm hil +.Nd introduction to HP-HIL support +.Sh SYNOPSIS +.Cd "hil* at gsc? irq 1 " Pq hppa +.Pp +.Cd "hilkbd* at hil?" +.Cd "hilms* at hil?" +.Cd "hilid* at hil?" +.Sh DESCRIPTION +The +.Nm +interface provides access to the +.Dq Human Interface Loop +controller found on many +.Tn HP +workstations. +.Pp +It provides generic HIL management and interfaces for child devices, +such as keyboards, button boxes, mice, graphics tablet, and ID modules. +.\".Pp +.\"hil devices: +.\"HP 45911A HP-HIL Graphics Tablet +.\"HP 46020A HP-HIL Keyboard +.\"HP 46021A HP-HIL Keyboard +.\"HP 46060A HP-HIL Mouse +.\"HP 46060B HP-HIL 3-Button Mouse +.\"HP 46083A HP-HIL Knob +.\"HP 46085A HP-HIL Control Dial Module +.\"HP 46086A HP-HIL 32-Button Box +.\"HP 46087A HP-HIL A-Size Digitizer +.\"HP 46088A HP-HIL B-Size Digitizer +.\"HP 46089A HP-HIL 4-Button Cursor for the HP 46087/88A Tablets +.\"HP 46094A HP-HIL Quadrature Box +.\"HP 46095A HP-HIL Quadrature 3-Button Mouse +.\"HP 80409A HP-HIL 3-Button Track Ball +.Pp +.Ox +provides support for the following devices: +.Pp +.Bl -tag -width "hilkbd(4)XX" -offset 3n -compact +.It Xr hilid 4 +HIL ID module device +.It Xr hilkbd 4 +HIL keyboard device +.It Xr hilms 4 +HIL mouse and graphics tablet device +.El +.Sh SEE ALSO +.Xr gsc 4 , +.Xr intro 4 diff --git a/static/openbsd/man4/hilid.4 b/static/openbsd/man4/hilid.4 new file mode 100644 index 00000000..e2827fc8 --- /dev/null +++ b/static/openbsd/man4/hilid.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: hilid.4,v 1.5 2007/05/31 19:19:50 jmc Exp $ +.\" +.\" Copyright (c) 2003 Miodrag Vallat. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistribution of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt HILID 4 +.Os +.Sh NAME +.Nm hilid +.Nd HIL ID module device +.Sh SYNOPSIS +.Cd "hilid* at hil?" +.Sh DESCRIPTION +This driver recognizes the HIL +.Dq ID module +device. +The only purpose of this device is to provide a small, unique, +bitstring. +.Sh SEE ALSO +.Xr hil 4 , +.Xr intro 4 +.Sh BUGS +There is currently no way to communicate the ID module bitstring to +userland applications. diff --git a/static/openbsd/man4/hilkbd.4 b/static/openbsd/man4/hilkbd.4 new file mode 100644 index 00000000..b18245db --- /dev/null +++ b/static/openbsd/man4/hilkbd.4 @@ -0,0 +1,106 @@ +.\" $OpenBSD: hilkbd.4,v 1.13 2011/01/30 07:53:57 jmc Exp $ +.\" +.\" Copyright (c) 2003 Miodrag Vallat. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistribution of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: January 30 2011 $ +.Dt HILKBD 4 +.Os +.Sh NAME +.Nm hilkbd +.Nd HIL keyboard device +.Sh SYNOPSIS +.Cd "hilkbd* at hil?" +.Cd "wskbd* at hilkbd?" +.Cd "option HILKBD_LAYOUT=XXX" +.Sh DESCRIPTION +This driver supports HIL keyboards within the +.Xr wscons 4 +framework. +It doesn't provide direct device driver entry points, but makes its +functions available through the internal +.Xr wskbd 4 +interface. +.Pp +The +.Nm +driver supports a number of different key mappings. +By default, the layout corresponding to the keyboard model as probed +by the +.Nm +driver will be used. +A different layout can be chosen either with the kernel option +.Dq HILKBD_LAYOUT +at compile time, or with the +.Xr wsconsctl 8 +utility (variable: +.Dq keyboard.encoding ) +at runtime. +.Pp +The supported key mappings are at this time: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It KB_DE +.Pq de +German with +.Dq dead accents . +.It KB_FR +.Pq fr +French with +.Dq dead accents . +.It KB_SV +.Pq sv +Swedish. +.It KB_UK +.Pq uk +British. +.It KB_US +.Pq us +English/US keyboard mapping. +.El +.Pp +The KB_DE mapping can be used in the KB_NODEAD +.Pq .nodead +variant. +This switches off the +.Dq dead accents . +.Sh EXAMPLES +To set a Swedish keyboard mapping, use +.Ic wsconsctl keyboard.encoding=sv . +To set it at kernel build time, regardless of what keyboard is plugged, add +the following to the kernel configuration file: +.Bd -literal -offset indent +option HILKBD_LAYOUT="KB_SV" +.Ed +.Sh SEE ALSO +.Xr hil 4 , +.Xr intro 4 , +.Xr wskbd 4 , +.Xr wsconsctl 8 +.Sh BUGS +The list of built-in mappings is incomplete and has grown as people submitted +information about their particular layout. +.Pp +The Swedish and British layout have been reconstructed from tables in the old +HIL code present in the hp300 port, and have not been tested. diff --git a/static/openbsd/man4/hilms.4 b/static/openbsd/man4/hilms.4 new file mode 100644 index 00000000..de37628d --- /dev/null +++ b/static/openbsd/man4/hilms.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: hilms.4,v 1.7 2007/05/31 19:19:50 jmc Exp $ +.\" +.\" Copyright (c) 2003 Miodrag Vallat. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistribution of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt HILMS 4 +.Os +.Sh NAME +.Nm hilms +.Nd HIL mouse and graphics tablet device +.Sh SYNOPSIS +.Cd "hilms* at hil?" +.Cd "wsmouse* at hilms? mux 0" +.Sh DESCRIPTION +This driver supports HIL mice and graphics tablet within the +.Xr wscons 4 +framework. +It doesn't provide direct device driver entry points, but makes its +functions available through the internal +.Xr wsmouse 4 +interface. +.Sh SEE ALSO +.Xr hil 4 , +.Xr intro 4 , +.Xr wsmouse 4 diff --git a/static/openbsd/man4/hireset.4 b/static/openbsd/man4/hireset.4 new file mode 100644 index 00000000..5e40c9fc --- /dev/null +++ b/static/openbsd/man4/hireset.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: hireset.4,v 1.2 2018/08/27 20:36:49 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 27 2018 $ +.Dt HIRESET 4 +.Os +.Sh NAME +.Nm hireset +.Nd HiSilicon reset controller +.Sh SYNOPSIS +.Cd "hireset* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the reset signals for integrated components of HiSilicon SoCs. +.Sh SEE ALSO +.Xr hiclock 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/hitemp.4 b/static/openbsd/man4/hitemp.4 new file mode 100644 index 00000000..ee5aaf3f --- /dev/null +++ b/static/openbsd/man4/hitemp.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: hitemp.4,v 1.2 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt HITEMP 4 +.Os +.Sh NAME +.Nm hitemp +.Nd HiSilicon temperature monitor +.Sh SYNOPSIS +.Cd "hitemp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensors found on the +HiSilicon Hi3660 and Hi3670 SoCs. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/hme.4 b/static/openbsd/man4/hme.4 new file mode 100644 index 00000000..e54f375d --- /dev/null +++ b/static/openbsd/man4/hme.4 @@ -0,0 +1,100 @@ +.\" $OpenBSD: hme.4,v 1.16 2019/11/05 07:53:58 jmc Exp $ +.\" +.\" Copyright (c) 1998 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 5 2019 $ +.Dt HME 4 +.Os +.Sh NAME +.Nm hme +.Nd Sun Happy Meal 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "hme* at pci?" +.Cd "hme* at sbus?" +.Cd "luphy* at mii?" +.Cd "nsphy* at mii?" +.Cd "qsphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various NICs based on the Sun Happy Meal Ethernet +controller chips, including the following: +.Pp +.Bl -bullet -compact -offset indent +.It +Sun FastEthernet PCI +.It +Sun FastEthernet SBus +.It +Sun Quad FastEthernet PCI +.It +Sun Quad FastEthernet SBus +.It +Sun SunSwift PCI +.It +Sun SunSwift SBus +.El +.Pp +The +.Nm +driver supports several media types, which are selected via the +.Xr ifconfig 8 +command. +The supported media types are: +.Bl -tag -width "media autoselect" -offset indent +.It media autoselect +Attempt to autoselect the media type (default) +.It media 100baseTX mediaopt full-duplex +Use 100baseTX, full duplex +.It media 100baseTX +Use 100baseTX, half duplex +.It media 10baseT mediaopt full-duplex +Use 10baseT, full duplex +.It media 10baseT +Use 10baseT, half duplex +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr luphy 4 , +.Xr netintro 4 , +.Xr nsphy 4 , +.Xr qsphy 4 , +.Xr sbus 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T "STP2002QFP Fast Ethernet, Parallel Port, SCSI (FEPS) User's Guide" +.%D April 1996 +.%A Sun Microelectronics +.Re +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 2.4 . diff --git a/static/openbsd/man4/hotplug.4 b/static/openbsd/man4/hotplug.4 new file mode 100644 index 00000000..9f37e17b --- /dev/null +++ b/static/openbsd/man4/hotplug.4 @@ -0,0 +1,104 @@ +.\" $OpenBSD: hotplug.4,v 1.6 2015/09/14 17:09:26 schwarze Exp $ +.\" +.\" Copyright (c) 2004 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 14 2015 $ +.Dt HOTPLUG 4 +.Os +.Sh NAME +.Nm hotplug +.Nd devices hot plugging +.Sh SYNOPSIS +.Cd "pseudo-device hotplug 1" +.Pp +.In sys/types.h +.In sys/device.h +.In sys/hotplug.h +.Sh DESCRIPTION +The +.Nm +pseudo-device passes device attachment and detachment events to +userland. +When a device attaches or detaches, the corresponding event is queued. +The events can then be obtained from the queue through the +.Xr read 2 +call on the +.Pa /dev/hotplug +device file. +Once an event has been read, it's deleted from the queue. +The event queue has a limited size and if it's full all new events will be +dropped. +Each event is described with the following structure declared in the +.In sys/hotplug.h +header file: +.Bd -literal -offset indent +struct hotplug_event { + int he_type; /* event type */ + enum devclass he_devclass; /* device class */ + char he_devname[16]; /* device name */ +}; + +.Ed +The +.Va he_type +field describes the event type and can be either +.Dv HOTPLUG_DEVAT +for device attachment or +.Dv HOTPLUG_DEVDT +for detachment. +The +.Va he_devclass +field describes the device class. +All device classes can be found in the +.In sys/device.h +header file: +.Bd -literal -offset indent +enum devclass { + DV_DULL, /* generic, no special info */ + DV_CPU, /* CPU (carries resource utilization) */ + DV_DISK, /* disk drive (label, etc) */ + DV_IFNET, /* network interface */ + DV_TAPE, /* tape device */ + DV_TTY /* serial line interface */ +}; + +.Ed +The +.Va he_devname +is a device name including unit number, e.g.\& +.Pa sd1 . +.Pp +Only one structure can be read per call. +If there are no events in the queue, the +.Xr read 2 +call will block until an event appears. +.Sh DIAGNOSTICS +.Bl -diag +.It "hotplug: event lost, queue full" +New events will be dropped until all pending events have been read. +.El +.Sh SEE ALSO +.Xr read 2 , +.Xr hotplugd 8 +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 3.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/hsq.4 b/static/openbsd/man4/hsq.4 new file mode 100644 index 00000000..100e58fb --- /dev/null +++ b/static/openbsd/man4/hsq.4 @@ -0,0 +1,103 @@ +.\" $OpenBSD: hsq.4,v 1.18 2018/01/03 08:43:09 bentley Exp $ +.\" from: OpenBSD: ast.4,v 1.5 1999/07/09 13:35:43 aaron Exp +.\" from: NetBSD: ast.4,v 1.7 1996/03/16 00:07:07 thorpej Exp +.\" +.\" Copyright (c) 1990, 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)dca.4 5.2 (Berkeley) 3/27/91 +.\" from: Id: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp +.\" +.Dd $Mdocdate: January 3 2018 $ +.Dt HSQ 4 +.Os +.Sh NAME +.Nm hsq +.Nd multiplexing serial communications interface +.Sh SYNOPSIS +.Cd "hsq0 at isa? port 0x140 irq 10" +.Cd "com* at hsq?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Hostess +.Pq Lk https://www.comtrol.com/ "Comtrol Corporation" +and compatible boards that multiplex together up to four +.Tn EIA +.Tn RS-232C +.Pq Tn CCITT V.28 +communications interfaces. +.Pp +Each +.Nm +device is the master device for up to four +.Nm com +devices. +The kernel configuration specifies these +.Nm com +devices as slave devices of the +.Nm +device, as shown in +.Sx SYNOPSIS . +The slave ID given for each +.Nm com +device determines which bit in the interrupt multiplexing register is +tested to find interrupts for that device. +The +.Cd port +specification for the +.Nm +device is used to compute the base addresses for the +.Nm com +subdevices (they are equal to port + ID * 8) and the port for +the interrupt multiplexing register (it is equal to port + 7). +More technical details on how the driver works can be found in +the big comment at the beginning of the driver's source code. +.Pp +Information on setup of card's configuration switches should be taken +from Comtrol Corporation's web site, since the author wrote and tested +the driver only with Hostess-compatible cards. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/tty0? +.It Pa /dev/cua0? +.El +.Sh SEE ALSO +.Xr com 4 , +.Xr intro 4 , +.Xr isa 4 +.Sh HISTORY +The +.Nm +driver was written by +.An Denis A. Doroshenko +based on the +.Xr ast 4 +driver. diff --git a/static/openbsd/man4/hvn.4 b/static/openbsd/man4/hvn.4 new file mode 100644 index 00000000..3f8cbda9 --- /dev/null +++ b/static/openbsd/man4/hvn.4 @@ -0,0 +1,61 @@ +.\" $OpenBSD: hvn.4,v 1.5 2016/10/07 14:42:27 jmc Exp $ +.\" +.\" Copyright (c) 2016 Mike Belopuhov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 7 2016 $ +.Dt HVN 4 +.Os +.Sh NAME +.Nm hvn +.Nd Hyper-V networking interface +.Sh SYNOPSIS +.Cd "hvn* at hyperv?" +.Sh DESCRIPTION +The +.Nm +driver provides support for a Network Virtual Service Client (NetVSC), +a virtual networking interface that relays device requests to the Virtual +Service Provider (VSP) in the management operating system via the VMBus. +.Pp +NetVSC emulates an RNDIS 1.0 compliant device on top of a custom NVS +protocol operating over the VMBus channel ring. +.Pp +Individual networking interfaces can be renamed by issuing a +.Cm Rename-VMNetworkAdapter +PowerShell command in the management domain. +In order to enable sending and receiving of IEEE 802.1q (VLAN) frames, +the virtual port needs to be put into +.Em Trunk +mode with the +.Cm Set-VMNetworkAdapterVlan +command. +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr hyperv 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mike Belopuhov Aq Mt mikeb@openbsd.org +based on the +.Fx +driver by the Microsoft BSD Integration Services Team +.Aq Mt bsdic@microsoft.com . diff --git a/static/openbsd/man4/hvs.4 b/static/openbsd/man4/hvs.4 new file mode 100644 index 00000000..b48e7110 --- /dev/null +++ b/static/openbsd/man4/hvs.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: hvs.4,v 1.1 2017/06/14 10:34:41 mikeb Exp $ +.\" +.\" Copyright (c) 2017 Mike Belopuhov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 14 2017 $ +.Dt HVS 4 +.Os +.Sh NAME +.Nm hvs +.Nd Hyper-V virtual disk +.Sh SYNOPSIS +.Cd "hvs* at hyperv?" +.Sh DESCRIPTION +The +.Nm +driver provides support for a Storage Virtual Service Client (StorVSC), +a virtual disk interface that relays device requests to the Virtual +Service Provider (VSP) in the management operating system via the VMBus. +.Pp +StorVSC provides a unified interface to emulated IDE and SCSI devices. +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr hyperv 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mike Belopuhov Aq Mt mikeb@openbsd.org +based on the +.Fx +driver by the Microsoft BSD Integration Services Team +.Aq Mt bsdic@microsoft.com . diff --git a/static/openbsd/man4/hyperv.4 b/static/openbsd/man4/hyperv.4 new file mode 100644 index 00000000..f7489a69 --- /dev/null +++ b/static/openbsd/man4/hyperv.4 @@ -0,0 +1,73 @@ +.\" $OpenBSD: hyperv.4,v 1.5 2017/09/18 19:45:52 mikeb Exp $ +.\" +.\" Copyright (c) 2016 Mike Belopuhov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 18 2017 $ +.Dt HYPERV 4 +.Os +.Sh NAME +.Nm hyperv +.Nd Hyper-V guest nexus device +.Sh SYNOPSIS +.Cd "hyperv0 at pvbus?" +.Sh DESCRIPTION +.Nm +driver performs Synthetic Interrupt Controller initialization, +sets up hypercalls, +and provides access to VMBus services required by paravirtualized +devices such as disk and network interfaces. +.Pp +An access is also provided to the Key-Value Pair exchange interface +via +.Xr pvbus 4 . +All keys are associated to one of several key pools: +.Em Auto , +.Em Guest , +.Em External +or +.Em Guest/Parameters . +It's possible to modify values of keys in the +.Em Auto +pool as well as +set new keys in the +.Em Guest +pool with +.Xr hostctl 8 . +The Host provides its read-only keys in +.Em External +and +.Em Guest/Parameters +pools. +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr intro 4 , +.Xr pvbus 4 , +.Xr hostctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mike Belopuhov Aq Mt mikeb@openbsd.org +based on the +.Fx +driver by the Microsoft BSD Integration Services Team +.Aq Mt bsdic@microsoft.com . +.Sh CAVEATS +Generation 2 Virtual Machines are currently not supported. diff --git a/static/openbsd/man4/iasuskbd.4 b/static/openbsd/man4/iasuskbd.4 new file mode 100644 index 00000000..4e9d2c89 --- /dev/null +++ b/static/openbsd/man4/iasuskbd.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: iasuskbd.4,v 1.2 2025/11/23 21:30:36 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 23 2025 $ +.Dt IASUSKBD 4 +.Os +.Sh NAME +.Nm iasuskbd +.Nd ASUS I2C HID keyboard support +.Sh SYNOPSIS +.Cd "iasuskbd* at ihidev?" +.Cd "wskbd* at iasuskbd? mux 1" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ASUS-specific features of I2C HID +keyboards found on some ASUS laptops. +It enables adjustment of the keyboard backlight level on +these laptops. +Backlight levels can be retrieved and modified with the +.Xr wsconsctl 8 +variable +.Va keyboard.backlight . +.Sh SEE ALSO +.Xr ihidev 4 , +.Xr wskbd 4 , +.Xr wsconsctl 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/iatp.4 b/static/openbsd/man4/iatp.4 new file mode 100644 index 00000000..a527f16f --- /dev/null +++ b/static/openbsd/man4/iatp.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: iatp.4,v 1.2 2016/09/01 10:37:50 jmc Exp $ +.\" +.\" Copyright (c) 2016 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 1 2016 $ +.Dt IATP 4 +.Os +.Sh NAME +.Nm iatp +.Nd Atmel maXTouch touchpad and touchscreen +.Sh SYNOPSIS +.Cd "iatp* at iic?" +.Cd "wsmouse* at iatp? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides support for Atmel maXTouch touchpad and touchscreen +devices connected over Inter-Integrated Circuit (I2C) buses. +Access to these devices is through the +.Xr wscons 4 +driver. +.Sh SEE ALSO +.Xr iic 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . diff --git a/static/openbsd/man4/iavf.4 b/static/openbsd/man4/iavf.4 new file mode 100644 index 00000000..474083c7 --- /dev/null +++ b/static/openbsd/man4/iavf.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: iavf.4,v 1.4 2024/11/03 06:42:10 jmc Exp $ +.\" +.\" Copyright (c) 2019 Jonathan Matthew +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 3 2024 $ +.Dt IAVF 4 +.Os +.Sh NAME +.Nm iavf +.Nd Intel Ethernet adaptive virtual function device +.Sh SYNOPSIS +.Cd "iavf* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports the SR-IOV virtual functions of Intel 700 series Ethernet +controller devices, and newer product families. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org +and +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . diff --git a/static/openbsd/man4/icc.4 b/static/openbsd/man4/icc.4 new file mode 100644 index 00000000..872af4f4 --- /dev/null +++ b/static/openbsd/man4/icc.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: icc.4,v 1.2 2022/11/11 21:41:45 jmc Exp $ +.\" +.\" Copyright (c) 2021 Anton Lindqvist +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 11 2022 $ +.Dt ICC 4 +.Os +.Sh NAME +.Nm icc +.Nd Consumer Control keyboards +.Sh SYNOPSIS +.Cd "icc* at ihidev?" +.Cd "wsbkd* at icc? mux 1" +.Sh DESCRIPTION +The +.Nm +driver provides support for Consumer Control pseudo keyboards, often used to +expose screen brightness control. +.Sh SEE ALSO +.Xr ihidev 4 , +.Xr intro 4 , +.Xr ucc 4 , +.Xr umstc 4 , +.Xr wskbd 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Anton Lindqvist Aq Mt anton@openbsd.org +and +.An Matthieu Herrb Aq Mt matthieu@openbsd.org . diff --git a/static/openbsd/man4/ice.4 b/static/openbsd/man4/ice.4 new file mode 100644 index 00000000..3eb11e8a --- /dev/null +++ b/static/openbsd/man4/ice.4 @@ -0,0 +1,83 @@ +.\" $OpenBSD: ice.4,v 1.5 2025/07/17 09:25:11 stsp Exp $ +.\" +.\" Copyright (c) 2024 Stefan Sperling +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 17 2025 $ +.Dt ICE 4 +.Os +.Sh NAME +.Nm ice +.Nd Intel Ethernet 800 series PCI Express 1Gb/10Gb/25Gb/50Gb/100Gb Ethernet device +.Sh SYNOPSIS +.Cd "ice* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports Intel 800 series controllers based on the +Intel E810 and E823 Ethernet chipsets, including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +Intel E810-C SFP/QSFP +.It +Intel E810-XXV SFP/QSFP +.It +Intel E823-L SFP/QSFP +.It +Intel E823-L 10G/1G +.El +.Sh FILES +Intel 800 series controllers contain basic firmware which allows the +device to be used with single Tx/Rx queues and without any hardware +offloading features enabled. +For full functionality, the device needs the following firmware file, +which is loaded by the driver when the system boots: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/ice-ddp +.El +.Pp +This firmware file is not free because Intel refuses to grant +distribution rights without contractual obligations. +As a result, even though +.Ox +includes the driver, the firmware file cannot be included and +users have to download the file on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Fx 12.2 . +.Ox +support was added in +.Ox 7.7 . +.Sh AUTHORS +The +.Nm +driver was written by Intel and ported to +.Ox +by +.An Stefan Sperling Aq Mt stsp@openbsd.org . diff --git a/static/openbsd/man4/ichiic.4 b/static/openbsd/man4/ichiic.4 new file mode 100644 index 00000000..99079cd4 --- /dev/null +++ b/static/openbsd/man4/ichiic.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: ichiic.4,v 1.14 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ICHIIC 4 +.Os +.Sh NAME +.Nm ichiic +.Nd Intel ICH SMBus controller +.Sh SYNOPSIS +.Cd "ichiic* at pci?" +.Cd "iic* at ichiic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Intel ICH SMBus host interface to be +used with the +.Xr iic 4 +framework. +.Pp +Supported chipsets: +.Pp +.Bl -bullet -compact -offset indent +.It +Intel ICH, ICH2, ICH3, ICH4, ICH4-M, ICH5, ICH5R, ICH6, ICH6-M, ICH6R, ICH7, +ICH8, ICH9, ICH10, C-ICH, PCH, 6300ESB and 6321ESB. +.El +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . +.Sh BUGS +The driver doesn't support I2C commands with a data buffer size of more +than 2 bytes. diff --git a/static/openbsd/man4/ichwdt.4 b/static/openbsd/man4/ichwdt.4 new file mode 100644 index 00000000..5c389b95 --- /dev/null +++ b/static/openbsd/man4/ichwdt.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: ichwdt.4,v 1.8 2014/11/15 14:41:02 bentley Exp $ +.\" +.\" Copyright (c) 2005 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 15 2014 $ +.Dt ICHWDT 4 +.Os +.Sh NAME +.Nm ichwdt +.Nd Intel 6300ESB ICH watchdog timer device +.Sh SYNOPSIS +.Cd "ichwdt* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports the watchdog timer of the Intel 6300ESB I/O Controller Hub. +.Pp +.Nm +provides the standard +.Xr watchdog 4 +interface and may be used with +.Xr watchdogd 8 . +The watchdog timer can be configured via +.Xr sysctl 8 . +.Pp +Once the watchdog timer resets the CPU, the driver reports it on the +next boot displaying the +.Dq reboot on timeout +message in the dmesg. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr watchdog 4 , +.Xr sysctl 8 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 3.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/icmp.4 b/static/openbsd/man4/icmp.4 new file mode 100644 index 00000000..0c7e43e2 --- /dev/null +++ b/static/openbsd/man4/icmp.4 @@ -0,0 +1,185 @@ +.\" $OpenBSD: icmp.4,v 1.14 2015/09/10 17:55:21 schwarze Exp $ +.\" $NetBSD: icmp.4,v 1.3 1994/11/30 16:22:14 jtc Exp $ +.\" +.\" Copyright (c) 1986, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)icmp.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt ICMP 4 +.Os +.Sh NAME +.Nm icmp +.Nd Internet Control Message Protocol +.Sh SYNOPSIS +.In sys/socket.h +.In netinet/in.h +.Ft int +.Fn socket AF_INET SOCK_RAW proto +.Sh DESCRIPTION +.Tn ICMP +is the error and control message protocol used +by +.Tn IP +and the Internet protocol family. +It may be accessed through a +.Dq raw socket +for network monitoring +and diagnostic functions. +The +.Fa proto +parameter to the socket call to create an +.Tn ICMP +socket +is obtained from +.Xr getprotobyname 3 . +.Tn ICMP +sockets are connectionless, +and are normally used with the +.Xr sendto 2 +and +.Xr recvfrom 2 +calls, though the +.Xr connect 2 +call may also be used to fix the destination for future +packets (in which case the +.Xr read 2 +or +.Xr recv 2 +and +.Xr write 2 +or +.Xr send 2 +system calls may be used). +.Pp +Outgoing packets automatically have an +.Tn IP +header prepended to +them (based on the destination address). +Incoming packets are received with the +.Tn IP +header and options intact. +.Ss Types +ICMP messages are classified according to the type and code fields +present in the ICMP header. +The abbreviations for the types and codes may be used in rules in +.Xr pf.conf 5 . +The following types are defined: +.Bl -column "Num" "ipv6-where" -offset indent +.It Sy Num Ta Sy "Abbrev." Ta Sy Description +.It 0 Ta echorep Ta "Echo reply" +.It 3 Ta unreach Ta "Destination unreachable" +.It 4 Ta squench Ta "Packet loss, slow down" +.It 5 Ta redir Ta "Shorter route exists" +.It 6 Ta althost Ta "Alternate host address" +.It 8 Ta echoreq Ta "Echo request" +.It 9 Ta routeradv Ta "Router advertisement" +.It 10 Ta routersol Ta "Router solicitation" +.It 11 Ta timex Ta "Time exceeded" +.It 12 Ta paramprob Ta "Invalid IP header" +.It 13 Ta timereq Ta "Timestamp request" +.It 14 Ta timerep Ta "Timestamp reply" +.It 15 Ta inforeq Ta "Information request" +.It 16 Ta inforep Ta "Information reply" +.It 17 Ta maskreq Ta "Address mask request" +.It 18 Ta maskrep Ta "Address mask reply" +.It 30 Ta trace Ta "Traceroute" +.It 31 Ta dataconv Ta "Data conversion problem" +.It 32 Ta mobredir Ta "Mobile host redirection" +.It 33 Ta ipv6-where Ta "IPv6 where-are-you" +.It 34 Ta ipv6-here Ta "IPv6 i-am-here" +.It 35 Ta mobregreq Ta "Mobile registration request" +.It 36 Ta mobregrep Ta "Mobile registration reply" +.It 39 Ta skip Ta "SKIP" +.It 40 Ta photuris Ta "Photuris" +.El +.Pp +The following codes are defined: +.Bl -column "Num" "redir-tos-host" "paramprob" "Description" -offset indent +.It Sy Num Ta Sy "Abbrev." Ta Sy Type Ta Sy Description +.It 0 Ta net-unr Ta unreach Ta "Network unreachable" +.It 1 Ta host-unr Ta unreach Ta "Host unreachable" +.It 2 Ta proto-unr Ta unreach Ta "Protocol unreachable" +.It 3 Ta port-unr Ta unreach Ta "Port unreachable" +.It 4 Ta needfrag Ta unreach Ta "Fragmentation needed but DF bit set" +.It 5 Ta srcfail Ta unreach Ta "Source routing failed" +.It 6 Ta net-unk Ta unreach Ta "Network unknown" +.It 7 Ta host-unk Ta unreach Ta "Host unknown" +.It 8 Ta isolate Ta unreach Ta "Host isolated" +.It 9 Ta net-prohib Ta unreach Ta "Network administratively prohibited" +.It 10 Ta host-prohib Ta unreach Ta "Host administratively prohibited" +.It 11 Ta net-tos Ta unreach Ta "Invalid TOS for network" +.It 12 Ta host-tos Ta unreach Ta "Invalid TOS for host" +.It 13 Ta filter-prohib Ta unreach Ta "Prohibited access" +.It 14 Ta host-preced Ta unreach Ta "Precedence violation" +.It 15 Ta cutoff-preced Ta unreach Ta "Precedence cutoff" +.It 0 Ta redir-net Ta redir Ta "Shorter route for network" +.It 1 Ta redir-host Ta redir Ta "Shorter route for host" +.It 2 Ta redir-tos-net Ta redir Ta "Shorter route for TOS and network" +.It 3 Ta redir-tos-host Ta redir Ta "Shorter route for TOS and host" +.It 0 Ta normal-adv Ta routeradv Ta "Normal advertisement" +.It 16 Ta common-adv Ta routeradv Ta "Selective advertisement" +.It 0 Ta transit Ta timex Ta "Time exceeded in transit" +.It 1 Ta reassemb Ta timex Ta "Time exceeded in reassembly" +.It 0 Ta badhead Ta paramprob Ta "Invalid option pointer" +.It 1 Ta optmiss Ta paramprob Ta "Missing option" +.It 2 Ta badlen Ta paramprob Ta "Invalid length" +.It 1 Ta unknown-ind Ta photuris Ta "Unknown security index" +.It 2 Ta auth-fail Ta photuris Ta "Authentication failed" +.It 3 Ta decrypt-fail Ta photuris Ta "Decryption failed" +.El +.Sh DIAGNOSTICS +A socket operation may fail with one of the following errors returned: +.Bl -tag -width [EADDRNOTAVAIL] +.It Bq Er EISCONN +when trying to establish a connection on a socket which +already has one, or when trying to send a datagram with the destination +address specified and the socket is already connected; +.It Bq Er ENOTCONN +when trying to send a datagram, but +no destination address is specified, and the socket hasn't been +connected; +.It Bq Er ENOBUFS +when the system runs out of memory for +an internal data structure; +.It Bq Er EADDRNOTAVAIL +when an attempt is made to create a +socket with a network address for which no network interface +exists. +.El +.Sh SEE ALSO +.Xr recv 2 , +.Xr send 2 , +.Xr inet 4 , +.Xr ip 4 , +.Xr netintro 4 +.Sh HISTORY +The +.Nm +protocol appeared in +.Bx 4.3 . diff --git a/static/openbsd/man4/icmp6.4 b/static/openbsd/man4/icmp6.4 new file mode 100644 index 00000000..d9089ce0 --- /dev/null +++ b/static/openbsd/man4/icmp6.4 @@ -0,0 +1,257 @@ +.\" $OpenBSD: icmp6.4,v 1.31 2017/08/03 17:36:06 florian Exp $ +.\" $KAME: icmp6.4,v 1.6 2004/12/27 05:30:56 itojun Exp $ +.\" +.\" Copyright (c) 1986, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.Dd $Mdocdate: August 3 2017 $ +.Dt ICMP6 4 +.Os +.Sh NAME +.Nm icmp6 +.Nd Internet Control Message Protocol for IPv6 +.Sh SYNOPSIS +.In sys/socket.h +.In netinet/in.h +.In netinet/icmp6.h +.Ft int +.Fn socket AF_INET6 SOCK_RAW IPPROTO_ICMPV6 +.Sh DESCRIPTION +ICMPv6 is the error and control message protocol used by IPv6 and the +IPv6 protocol family (see +.Xr ip6 4 +and +.Xr inet6 4 ) . +It may be accessed through a +.Dq raw socket +for network monitoring and diagnostic functions. +.Pp +The +.Fa proto +parameter to the +.Xr socket 2 +call to create an ICMPv6 socket may be obtained from +.Xr getprotobyname 3 . +ICMPv6 sockets are connectionless, and are normally used with the +.Xr sendto 2 +and +.Xr recvfrom 2 +calls, though the +.Xr connect 2 +call may also be used to fix the destination for future packets +(in which case +.Xr read 2 +or +.Xr recv 2 +and +.Xr write 2 +or +.Xr send 2 +system calls may be used). +.Pp +Outgoing packets automatically have an IPv6 header prepended to them +(based on the destination address). +Incoming packets on the socket are received with the IPv6 header and any +extension headers removed. +.Ss Types +ICMPv6 messages are classified according to the type and code fields +present in the ICMPv6 header. +The abbreviations for the types and codes may be used in rules in +.Xr pf.conf 5 . +The following types are defined: +.Bl -column "Num" "listendone" "Description" -offset indent +.It Sy Num Ta Sy "Abbrev." Ta Sy Description +.It 1 Ta unreach Ta "Destination unreachable" +.It 2 Ta toobig Ta "Packet too big" +.It 3 Ta timex Ta "Time exceeded" +.It 4 Ta paramprob Ta "Invalid IPv6 header" +.It 128 Ta echoreq Ta "Echo service request" +.It 129 Ta echorep Ta "Echo service reply" +.It 130 Ta groupqry Ta "Group membership query" +.It 130 Ta listqry Ta "Multicast listener query" +.It 131 Ta grouprep Ta "Group membership report" +.It 131 Ta listenrep Ta "Multicast listener report" +.It 132 Ta groupterm Ta "Group membership termination" +.It 132 Ta listendone Ta "Multicast listener done" +.It 133 Ta routersol Ta "Router solicitation" +.It 134 Ta routeradv Ta "Router advertisement" +.It 135 Ta neighbrsol Ta "Neighbor solicitation" +.It 136 Ta neighbradv Ta "Neighbor advertisement" +.It 137 Ta redir Ta "Shorter route exists" +.It 138 Ta routrrenum Ta "Route renumbering" +.It 139 Ta fqdnreq Ta "FQDN query" +.It 139 Ta niqry Ta "Node information query" +.It 139 Ta wrureq Ta "Who-are-you request" +.It 140 Ta fqdnrep Ta "FQDN reply" +.It 140 Ta nirep Ta "Node information reply" +.It 140 Ta wrurep Ta "Who-are-you reply" +.It 200 Ta mtraceresp Ta "mtrace response" +.It 201 Ta mtrace Ta "mtrace messages" +.El +.Pp +The following codes are defined: +.Bl -column "Num" "redironlink" "paramprob" "Description" -offset indent +.It Sy Num Ta Sy "Abbrev." Ta Sy Type Ta Sy Description +.It 0 Ta noroute-unr Ta unreach Ta "No route to destination" +.It 1 Ta admin-unr Ta unreach Ta "Administratively prohibited" +.It 2 Ta beyond-unr Ta unreach Ta "Beyond scope of source address" +.It 3 Ta addr-unr Ta unreach Ta "Address unreachable" +.It 4 Ta port-unr Ta unreach Ta "Port unreachable" +.It 0 Ta transit Ta timex Ta "Time exceeded in transit" +.It 1 Ta reassemb Ta timex Ta "Time exceeded in reassembly" +.It 0 Ta badhead Ta paramprob Ta "Erroneous header field" +.It 1 Ta nxthdr Ta paramprob Ta "Unrecognized next header" +.It 2 Ta "" Ta paramprob Ta "Unrecognized option" +.It 0 Ta redironlink Ta redir Ta "Redirection to on-link node" +.It 1 Ta redirrouter Ta redir Ta "Redirection to better router" +.El +.Ss Headers +All ICMPv6 messages are prefixed with an ICMPv6 header. +This header corresponds to the +.Vt icmp6_hdr +structure and has the following definition: +.Bd -literal -offset indent +struct icmp6_hdr { + u_int8_t icmp6_type; /* type field */ + u_int8_t icmp6_code; /* code field */ + u_int16_t icmp6_cksum; /* checksum field */ + union { + u_int32_t icmp6_un_data32[1]; /* type-specific */ + u_int16_t icmp6_un_data16[2]; /* type-specific */ + u_int8_t icmp6_un_data8[4]; /* type-specific */ + } icmp6_dataun; +} __packed; + +#define icmp6_data32 icmp6_dataun.icmp6_un_data32 +#define icmp6_data16 icmp6_dataun.icmp6_un_data16 +#define icmp6_data8 icmp6_dataun.icmp6_un_data8 +#define icmp6_pptr icmp6_data32[0] /* parameter prob */ +#define icmp6_mtu icmp6_data32[0] /* packet too big */ +#define icmp6_id icmp6_data16[0] /* echo request/reply */ +#define icmp6_seq icmp6_data16[1] /* echo request/reply */ +#define icmp6_maxdelay icmp6_data16[0] /* mcast group membership*/ +.Ed +.Pp +.Va icmp6_type +describes the type of the message. +Suitable values are defined in +.In netinet/icmp6.h . +.Va icmp6_code +describes the sub-type of the message and depends on +.Va icmp6_type . +.Va icmp6_cksum +contains the checksum for the message and is filled in by the +kernel on outgoing messages. +The other fields are used for type-specific purposes. +.Ss Filters +Because of the extra functionality of ICMPv6 in comparison to ICMPv4, +a larger number of messages may be potentially received on an ICMPv6 +socket. +Input filters may therefore be used to restrict input to a subset of the +incoming ICMPv6 messages so only interesting messages are returned by the +.Xr recv 2 +family of calls to an application. +.Pp +The +.Vt icmp6_filter +structure may be used to refine the input message set according to the +ICMPv6 type. +By default, all messages types are allowed on newly created raw ICMPv6 +sockets. +The following macros may be used to refine the input set: +.Bl -tag -width Ds +.It Fn "void ICMP6_FILTER_SETPASSALL" "struct icmp6_filter *filterp" +Allow all incoming messages. +.Va filterp +is modified to allow all message types. +.It Fn "void ICMP6_FILTER_SETBLOCKALL" "struct icmp6_filter *filterp" +Ignore all incoming messages. +.Va filterp +is modified to ignore all message types. +.It Fn "void ICMP6_FILTER_SETPASS" "int type" \ + "struct icmp6_filter *filterp" +Allow ICMPv6 messages with the given +.Fa type . +.Va filterp +is modified to allow such messages. +.It Fn "void ICMP6_FILTER_SETBLOCK" "int type" \ + "struct icmp6_filter *filterp" +Ignore ICMPv6 messages with the given +.Fa type . +.Va filterp +is modified to ignore such messages. +.It Fn "int ICMP6_FILTER_WILLPASS" "int type" \ + "const struct icmp6_filter *filterp" +Determine if the given filter will allow an ICMPv6 message of the given +type. +.It Fn "int ICMP6_FILTER_WILLBLOCK" "int type" \ + "const struct icmp6_filter *filterp" +Determine if the given filter will ignore an ICMPv6 message of the given +type. +.El +.Pp +The +.Xr getsockopt 2 +and +.Xr setsockopt 2 +calls may be used to obtain and install the filter on ICMPv6 sockets at +option level +.Dv IPPROTO_ICMPV6 +and name +.Dv ICMP6_FILTER +with a pointer to the +.Vt icmp6_filter +structure as the option value. +.Sh SEE ALSO +.Xr getsockopt 2 , +.Xr recv 2 , +.Xr send 2 , +.Xr setsockopt 2 , +.Xr socket 2 , +.Xr getprotobyname 3 , +.Xr inet6 4 , +.Xr ip6 4 , +.Xr netintro 4 +.Sh STANDARDS +.Rs +.%A W. Stevens +.%A M. Thomas +.%A E. Nordmark +.%A T. Jinmei +.%D May 2003 +.%R RFC 3542 +.%T Advanced Sockets Application Program Interface (API) for IPv6 +.Re +.Pp +.Rs +.%A A. Conta +.%A S. Deering +.%A M. Gupta +.%D March 2006 +.%R RFC 4443 +.%T "Internet Control Message Protocol (ICMPv6) for the Internet" \ + "Protocol Version 6 (IPv6) Specification" +.Re diff --git a/static/openbsd/man4/icsphy.4 b/static/openbsd/man4/icsphy.4 new file mode 100644 index 00000000..20edb7be --- /dev/null +++ b/static/openbsd/man4/icsphy.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: icsphy.4,v 1.11 2020/01/24 05:08:02 jsg Exp $ +.\" $NetBSD: icsphy.4,v 1.1 1998/11/04 05:53:58 thorpej Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 24 2020 $ +.Dt ICSPHY 4 +.Os +.Sh NAME +.Nm icsphy +.Nd Integrated Circuit Systems ICS189x 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "icsphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Integrated Circuit Systems ICS1890 10/100 Ethernet PHYs +and its successors ICS1892 and ICS1893. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/ietp.4 b/static/openbsd/man4/ietp.4 new file mode 100644 index 00000000..124366d8 --- /dev/null +++ b/static/openbsd/man4/ietp.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: ietp.4,v 1.2 2023/07/09 01:12:04 jsg Exp $ +.\" +.\" Copyright (c) 2016 joshua stein +.\" Copyright (c) 2023 vladimir serbinenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 9 2023 $ +.Dt IETP 4 +.Os +.Sh NAME +.Nm ietp +.Nd Elantech touchpad +.Sh SYNOPSIS +.Cd "ietp* at iic?" +.Cd "wsmouse* at ietp? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides support for Elantech touchpad +devices connected over Inter-Integrated Circuit (I2C) buses. +Access to these devices is through the +.Xr wscons 4 +driver. +.Sh SEE ALSO +.Xr iic 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Vladimir Serbinenko Aq Mt phcoder@gmail.com . diff --git a/static/openbsd/man4/ifmedia.4 b/static/openbsd/man4/ifmedia.4 new file mode 100644 index 00000000..5e80c42c --- /dev/null +++ b/static/openbsd/man4/ifmedia.4 @@ -0,0 +1,573 @@ +.\" $OpenBSD: ifmedia.4,v 1.30 2023/08/15 00:43:00 jsg Exp $ +.\" $NetBSD: ifmedia.4,v 1.14 2001/06/30 17:57:56 bjh21 Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 15 2023 $ +.Dt IFMEDIA 4 +.Os +.Sh NAME +.Nm ifmedia +.Nd network interface media settings +.Sh SYNOPSIS +.In sys/socket.h +.In net/if.h +.In net/if_media.h +.Sh DESCRIPTION +The +.Nm +interface provides a consistent method for querying and setting +network interface media and media options. +The media is typically set using the +.Xr ifconfig 8 +command. +.Pp +Currently these link types are supported by +.Nm ifmedia : +.Pp +.Bl -tag -offset indent -width IFM_IEEE80211 -compact +.It Dv IFM_ETHER +Ethernet +.It Dv IFM_FDDI +FDDI +.It Dv IFM_IEEE80211 +IEEE802.11 Wireless LAN +.It Dv IFM_TDM +Time Division Multiplex +.It Dv IFM_CARP +CARP +.El +.Pp +The following sections describe the possible media settings for each +link type. +Not all of these are supported by every device; refer to +your device's manual page for more information. +.Pp +The lists below provide the possible names of each media type or option. +The first name in the list is the canonical name of the media type or +option. +Additional names are acceptable aliases for the media type or option. +.Sh COMMON MEDIA TYPES AND OPTIONS +The following media types are shared by all link types: +.Pp +.Bl -tag -offset indent -width IFM_MANUAL -compact +.It Dv IFM_AUTO +Autoselect the best media. +[autoselect, auto] +.It Dv IFM_MANUAL +Jumper or switch on device selects media. +[manual] +.It Dv IFM_NONE +Deselect all media. +[none] +.El +.Pp +The following media options are shared by all link types: +.Bl -tag -offset indent -width IFM_FLAG0 +.It Dv IFM_FDX +Place the device into full-duplex mode. +This option only has meaning if the device is normally not full-duplex. +.It Dv IFM_HDX +Place the device into half-duplex mode. +This option only has meaning if the device is normally not half-duplex. +[half-duplex, hdx] +.It Dv IFM_FLOW +Enable hardware flow control on device. +.It Dv IFM_FLAG0 +Driver-defined flag. +[flag0] +.It Dv IFM_FLAG1 +Driver-defined flag. +[flag1] +.It Dv IFM_FLAG2 +Driver-defined flag. +[flag2] +.It Dv IFM_LOOP +Place the device into hardware loopback mode. +[loopback, hw-loopback, loop] +.El +.Sh MEDIA TYPES AND OPTIONS FOR ETHERNET +The following media types are defined for Ethernet: +.Bl -tag -offset indent -width IFM_10G_SFP_CU +.It Dv IFM_10_T +10BASE-T, 10Mb/s over unshielded twisted pair, RJ45 connector. +[10baseT, UTP, 10UTP] +.It Dv IFM_10_2 +10BASE2, 10Mb/s over coaxial cable, BNC connector; also called Thinnet. +[10base2, BNC, 10BNC] +.It Dv IFM_10_5 +10BASE5, 10Mb/s over 15-wire cables, DB15 connector; also called AUI. +[10base5, AUI, 10AUI] +.It Dv IFM_10_STP +10BASE-STP, 10Mb/s over shielded twisted pair, DB9 connector. +[10baseSTP, STP, 10STP] +.It Dv IFM_10_FL +10BASE-FL, 10Mb/s over fiber optic cables. +[10baseFL, FL, 10FL] +.It Dv IFM_100_TX +100BASE-TX, 100Mb/s over unshielded twisted pair, RJ45 connector. +[100baseTX, 100TX] +.It Dv IFM_100_FX +100BASE-FX, 100Mb/s over fiber optic cables. +[100baseFX, 100FX] +.It Dv IFM_100_T4 +100BASE-T4, 100Mb/s over 4-wire (category 3) unshielded twisted pair, RJ45 +connector. +[100baseT4, 100T4] +.It Dv IFM_100_T2 +100BASE-T2. +[100baseT2, 100T2] +.It Dv IFM_100_VG +100VG-AnyLAN. +[100baseVG, 100VG] +.It Dv IFM_1000_SX +1000BASE-SX, 1Gb/s over multi-mode fiber optic cables. +[1000baseSX, 1000SX] +.It Dv IFM_1000_LX +1000BASE-LX, 1Gb/s over single-mode fiber optic cables. +[1000baseLX, 1000LX] +.It Dv IFM_1000_CX +1000BASE-CX, 1Gb/s over shielded twisted pair. +[1000baseCX, 1000CX] +.It Dv IFM_1000_T +1000BASE-T, 1Gb/s over category 5 unshielded twisted pair, RJ45 connector. +[1000baseT, 1000T] +.It Dv IFM_1000_TX +Compatibility for 1000BASE-T. +[1000baseTX, 1000TX] +.It Dv IFM_2500_SX +2500BASE-SX, 2.5Gb/s over multi-mode fiber optic cables. +[2500baseSX, 2500SX] +.It Dv IFM_2500_T +2500BASE-T, 2.5Gb/s over unshielded twisted pair, RJ45 connector. +[2500baseT, 2500BASE-T] +.It Dv IFM_10G_CX4 +10GBASE-CX4, 10Gb/s over XAUI 4-lane PCS and copper cables. +[10GbaseCX4, 10GCX4, 10GBASE-CX4] +.It Dv IFM_10G_LR +10GBASE-LR, 10Gb/s over single-mode fiber optic cables. +[10GbaseLR, 10GLR, 10GBASE-LR] +.It Dv IFM_10G_SFP_CU +10GSFP+Cu, 10Gb/s over SFP+ Direct Attach cables. +[10GSFP+Cu, 10GCu] +.It Dv IFM_10G_SR +10GBASE-SR, 10Gb/s over multi-mode fiber optic cables. +[10GbaseSR, 10GSR, 10GBASE-SR] +.It Dv IFM_10G_T +10GBASE-T, 10Gb/s over unshielded twisted pair, RJ45 connector. +[10GbaseT, 10GT, 10GBASE-T] +.It Dv IFM_HPNA_1 +HomePNA 1.0, 1Mb/s over 2-wire (category 3) unshielded twisted pair +[HomePNA1, HPNA1] +.El +.Pp +The following media options are defined for Ethernet: +.Bl -tag -offset indent -width IFM_ETH_RXPAUSE +.It Dv IFM_ETH_MASTER +Configure a 1000BASE-T PHY as a MASTER PHY. +.It Dv IFM_ETH_RXPAUSE +Receive flow control is enabled on the 1000BASE-T PHY. +.It Dv IFM_ETH_TXPAUSE +Transmit flow control is enabled on the 1000BASE-T PHY. +.El +.Sh MEDIA TYPES AND OPTIONS FOR FDDI +The following media types are defined for FDDI: +.Pp +.Bl -tag -offset indent -width IFM_FDDI_SMF -compact +.It Dv IFM_FDDI_SMF +Single-mode fiber. +[Single-mode, SMF] +.It Dv IFM_FDDI_MMF +Multi-mode fiber. +[Multi-mode, MMF] +.It Dv IFM_FDDI_UTP +Unshielded twisted pair, RJ45 connector. +[UTP, CDDI] +.El +.Pp +The following media options are defined for FDDI: +.Bl -tag -offset indent -width IFM_FDDI_DA +.It Dv IFM_FDDI_DA +Dual-attached station vs. Single-attached station. +[dual-attach, das] +.El +.Sh MEDIA TYPES AND OPTIONS FOR IEEE802.11 WIRELESS LAN +The following media modes are defined for IEEE802.11 Wireless LAN: +.Pp +.Bl -tag -offset indent -width IFM_IEEE80211_11AC -compact +.It Dv IFM_IEEE80211_11A +5GHz, OFDM mode. +[11a] +.It Dv IFM_IEEE80211_11B +2GHz, DSSS/CCK mode. +[11b] +.It Dv IFM_IEEE80211_11G +2GHz, DSSS/CCK/OFDM mode. +[11g] +.It Dv IFM_IEEE80211_FH +2GHz, GFSK mode. +[fh] +.It Dv IFM_IEEE80211_11N +2GHz/5GHz, HT mode. +[11n] +.It Dv IFM_IEEE80211_11AC +5GHz, VHT mode. +[11ac] +.El +.Pp +The following media options are defined for IEEE802.11 Wireless LAN: +.Pp +.Bl -tag -offset indent -width IFM_IEEE80211_IBSSMASTER -compact +.It Dv IFM_IEEE80211_ADHOC +Ad-hoc mode. +[adhoc] +.It Dv IFM_IEEE80211_HOSTAP +Host Access Point mode. +[hostap] +.It Dv IFM_IEEE80211_IBSS +IBSS mode. +[ibss] +.It Dv IFM_IEEE80211_IBSSMASTER +IBSS master mode. +[ibssmaster] +.It Dv IFM_IEEE80211_MONITOR +Monitor mode. +[monitor] +.El +.Pp +All of the above media options are mutually exclusive. +If no media option is used, the wireless interface will try to find an +access point to connect to. +.Cm hostap +mode allows the wireless interface to act as an access point for other +802.11 devices. +.Cm ibss +mode is the standardized method of operating without an access point, with +each participating device taking on part of the role of an access point. +.Cm adhoc +mode, more accurately known as +.Em ad-hoc demo mode , +is not specified by the IEEE 802.11 standard and only works with +.Xr wi 4 +devices. +Likewise, +.Cm ibssmaster +mode only works with +.Xr wi 4 +devices. +On standard 802.11 networks the IBSS master role is assigned automatically. +.Pp +The channels detailed below are defined for IEEE802.11 Wireless LAN +in the 2.4GHz band. +The list of available frequencies is dependent on radio regulations +specified by regional authorities. +Recognized regulatory authorities include +the FCC (United States), ETSI (Europe), and Japan. +Frequencies in the table are specified in MHz. +.Bl -column "Channel " "2412" "ETSI" "Japan" -offset indent +.It Em Channel Ta Em FCC Ta Em ETSI Ta Em Japan +.It 1 Ta 2412 Ta 2412 Ta 2412 +.It 2 Ta 2417 Ta 2417 Ta 2417 +.It 3 Ta 2422 Ta 2422 Ta 2422 +.It 4 Ta 2427 Ta 2427 Ta 2427 +.It 5 Ta 2432 Ta 2432 Ta 2432 +.It 6 Ta 2437 Ta 2437 Ta 2437 +.It 7 Ta 2442 Ta 2442 Ta 2442 +.It 8 Ta 2447 Ta 2447 Ta 2447 +.It 9 Ta 2452 Ta 2452 Ta 2452 +.It 10 Ta 2457 Ta 2457 Ta 2457 +.It 11 Ta 2462 Ta 2462 Ta 2462 +.It 12 Ta - Ta 2467 Ta 2467 +.It 13 Ta - Ta 2472 Ta 2472 +.It 14 Ta - Ta - Ta 2484 +.El +.Pp +The channels do overlap; the bandwidth required for each channel is about 20MHz. +When using multiple channels in close proximity, it is suggested +that channels be separated by at least 25MHz. +In the US, this means that only channels 1, 6, and 11 may be used +simultaneously without interference. +.Pp +Channels in the 5GHz band are too numerous to list here. +Regulation of their use, particularly outdoors, varies between countries. +Users are advised to inform themselves about applicable regulations before +configuring wireless LAN devices for use in the 5GHz band. +.Pp +The following media types are defined for IEEE802.11 Wireless LAN: +.Pp +.Bl -tag -offset indent -width IFM_IEEE80211_FH1 -compact +.It Dv IFM_IEEE80211_FH1 +Frequency Hopping 1Mbps. +[FH1] +.It Dv IFM_IEEE80211_FH2 +Frequency Hopping 2Mbps. +[FH2] +.It Dv IFM_IEEE80211_DS1 +Direct Sequence 1Mbps. +[DS1] +.It Dv IFM_IEEE80211_DS2 +Direct Sequence 2Mbps. +[DS2] +.El +.Pp +The above media types were first introduced in the IEEE 802.11-1997 standard +and are used in the 2.4GHz band only. +Frequency Hopping Spread Spectrum modulation is incompatible with modern +802.11 networks. +Direct Sequence Spread Spectrum modulation (DSSS) frames can still be used if +backwards compatibility to 802.11b is enabled. +.Pp +.Bl -tag -offset indent -width IFM_IEEE80211_DS22 -compact +.It Dv IFM_IEEE80211_DS5 +Direct Sequence 5.5Mbps. +[DS5] +.It Dv IFM_IEEE80211_DS11 +Direct Sequence 11Mbps. +[DS11] +.It Dv IFM_IEEE80211_DS22 +Direct Sequence 22Mbps. +[DS22] +.El +.Pp +The above media types were first introduced in the IEEE 802.11b-1999 standard +and are used in the 2.4GHz band only. +They use Complementary Code Keying (CCK) which, compared to frames sent at +1Mbps or 2Mbps, reduces the possible distance between transmitter and receiver. +.Pp +Modern 802.11 networks remain compatible with 802.11b, even though DSSS frames +are incompatible with modern 802.11 frames using OFDM. +Co-existence with 802.11b requires OFDM transmitters to either risk frame +collisions or +.Dq reserve +the medium with a separate preceding transmission that DSSS receivers are +able to decode. +This causes additional overhead which some 802.11 deployments avoid by +deliberately disabling backwards compatibility with 802.11b. +.Pp +.Bl -tag -offset indent -width IFM_IEEE80211_VHT_MCSx -compact +.It Dv IFM_IEEE80211_OFDM6 +OFDM 6Mbps. +[OFDM6] +.It Dv IFM_IEEE80211_OFDM9 +OFDM 9Mbps. +[OFDM9] +.It Dv IFM_IEEE80211_OFDM12 +OFDM 12Mbps. +[OFDM12] +.It Dv IFM_IEEE80211_OFDM18 +OFDM 18Mbps. +[OFDM18] +.It Dv IFM_IEEE80211_OFDM24 +OFDM 24Mbps. +[OFDM24] +.It Dv IFM_IEEE80211_OFDM36 +OFDM 36Mbps. +[OFDM36] +.It Dv IFM_IEEE80211_OFDM48 +OFDM 48Mbps. +[OFDM48] +.It Dv IFM_IEEE80211_OFDM54 +OFDM 54Mbps. +[OFDM54] +.It Dv IFM_IEEE80211_OFDM72 +OFDM 72Mbps. +[OFDM72] +.El +.Pp +The above media types were first introduced in the IEEE 802.11a-1999 +standard for the 5GHz band, and in the IEEE 802.11g-2003 standard +for the 2.4GHz band. +OFDM with 72Mbps is a proprietary extension and was never standardized +by IEEE. +.Pp +Orthogonal Frequency Division Multiplexing (OFDM) is the current +standard modulation technique for 802.11. +Each 20MHz channel used by 802.11a and 802.11g provides space for +48 OFDM sub-carriers for data. +The sub-carriers use BPSK, QPSK, 16QAM, or 64QAM modulation, combined with +a particular coding rate for error correction at the receiver. +The coding rate specifies how many data bits in a frame are transmitted +without redundancy. +.Bl -column "Modulation" "Coding Rate " "Mbit/s" -offset 6n +.It Em Modulation Ta Em Coding Rate Ta Em Mbit/s +.It BPSK Ta 1/2 Ta 6 +.It BPSK Ta 3/4 Ta 9 +.It QPSK Ta 1/2 Ta 12 +.It QPSK Ta 3/4 Ta 18 +.It 16QAM Ta 1/2 Ta 24 +.It 16QAM Ta 3/4 Ta 36 +.It 64QAM Ta 1/2 Ta 48 +.It 64QAM Ta 3/4 Ta 52 +.El +.Pp +The IEEE 802.11n-2009 standard for +.Dq High Throughput +(HT) wireless LAN defines additional sub-carriers, modulations, and +coding rates. +The channel bandwidth for data frame transmissions was optionally extended +to 40MHz, with full backwards compatibility to 802.11a/b/g devices which +cannot decode 40MHz transmissions. +Several additional features were introduced, most notably MIMO (multiple-input, +multiple-output). +With MIMO, a data stream is divided across up to 4 +.Dq spatial streams , +which are transmitted in parallel by a corresponding amount of antennas. +Each spatial stream is received with a dedicated antenna, and the spatial +streams are de-multiplexed to obtain the original data stream. +.Pp +802.11n assigns a numeric identifier to all possible combinations of +modulation, coding rate, and number of spatial streams. +This results in 77 distinct modulation and coding schemes, abbreviated as +.Dq MCS . +.Pp +.Nm ifmedia +supports HT_MCS0 up to HT_MCS31: +.Pp +.Bl -tag -offset indent -width IFM_IEEE80211_VHT_MCSx -compact +.It Dv IFM_IEEE80211_HT_MCSx +HT OFDM MCS x (where x is in the range 0 - 31, inclusive). +[HT-MCSx] +.El +.Pp +In practice, only MCS-0 to MCS-32 are supported by commonly available devices. +The remaining MCS define combinations where distinct spatial streams employ +distinct modulations, a feature which was not widely implemented by hardware +vendors. +.Pp +The IEEE 802.11ac-2013 standard for +.Dq Very High Throughput +(VHT) wireless LAN operates in the 5GHz band only. +The channel bandwidth for data frame transmissions can be up to 160MHz wide. +The MCS identifiers were redefined and vastly reduced in number. +As a result, only VHT_MCS0 to VHT_MCS9 are defined for 802.11ac: +.Pp +.Bl -tag -offset indent -width IFM_IEEE80211_VHT_MCSx -compact +.It Dv IFM_IEEE80211_VHT_MCSx +VHT OFDM MCS x (where x is in the range 0 - 9, inclusive). +[VHT-MCSx] +.El +.Pp +The number of spatial streams is no longer associated with a given VHT MCS +identifier and must be specified as a separate +.Dq NSS +parameter. +This parameter is not yet implemented by +.Nm ifmedia . +.Sh MEDIA TYPES AND OPTIONS FOR TDM +The following media types are defined for TDM: +.Bl -tag -offset indent -width IFM_TDM_E1_G704_CRC4 +.It Dv IFM_TDM_E1 +E1, 2048kb/s HDB3 encoded, G.703 clearchannel serial line. +[e1] +.It Dv IFM_TDM_E1_AMI +E1, 2048kb/s AMI encoded, G.703 clearchannel serial line. +[e1-ami] +.It Dv IFM_TDM_E1_AMI_G704 +E1, 2048kb/s AMI encoded, G.704 structured serial line. +[e1-ami-g.704] +.It Dv IFM_TDM_E1_G704 +E1, 2048kb/s HDB3 encoded, G.704 structured serial line. +[e1-g.704] +.It Dv IFM_TDM_E1_G704_CRC4 +E1, 2048kb/s HDB3 encoded, G.704 structured serial line with CRC4 checksum. +[e1-g.704-crc4] +.It Dv IFM_TDM_E3 +E3, 34368kb/s HDB3 encoded, G.703 clearchannel serial line. +[e3] +.It Dv IFM_TDM_E3_G751 +E3, 34368kb/s HDB3 encoded, G.751 structured serial line. +[e3-g.751] +.It Dv IFM_TDM_E3_G832 +E3, 34368kb/s HDB3 encoded, G.832 structured serial line. +[e3-g.832] +.It Dv IFM_TDM_T1 +T1, 1536xkb/s B8ZS encoded, extended super frame (ESF) structured serial line. +[t1] +.It Dv IFM_TDM_T1_AMI +T1, 1536kb/s AMI encoded, super frame (SF) structured serial line. +[t1-ami] +.It Dv IFM_TDM_T3 +T3, 44736kb/s B3ZS, C-bit structured serial line. +[t3] +.It Dv IFM_TDM_T3_M13 +T3, 44736kb/s B3ZS, M13 structured serial line. +[t3-m13] +.El +.Pp +The following media options are defined for TDM: +.Bl -tag -offset indent -width IFM_TDM_HDLC_CRC16 +.It Dv IFM_TDM_HDLC_CRC16 +Cisco HDLC with 16-bit CRC checksum encoding. +[hdlc-crc16] +.It Dv IFM_TDM_FR_ANSI +ANSI/ITU Framerelay encoding. +[framerelay-ansi, framerelay-itu] +.It Dv IFM_TDM_FR_CISCO +Cisco Framerelay encoding. +[framerelay-cisco] +.It Dv IFM_TDM_PPP +PPP encoding. +[ppp] +.El +.Pp +By default TDM interfaces will use Cisco HDLC encoding with a 32-bit CRC +checksum. +.Pp +The following media modes are defined for TDM: +.Bl -tag -offset indent -width IFM_TDM_MASTER +.It Dv IFM_TDM_MASTER +Use local clock source as master clock. +[master] +.El +.Sh MEDIA TYPES AND OPTIONS FOR CARP +.Xr carp 4 +does not support any media types or options. +.Sh SEE ALSO +.Xr netintro 4 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +interface first appeared in +.Bsx 3.0 . +The implementation that appeared in +.Nx 1.3 +was written by Jonathan Stone and Jason R. Thorpe to be compatible with +the BSDI API. +It has since gone through several revisions which have extended the +API while maintaining backwards compatibility with the original API. +.Pp +Support for the +.Sy IEEE802.11 Wireless LAN +link type was added in +.Nx 1.5 . +.Pp +.Sy Host AP +mode was added in +.Ox 3.1 . diff --git a/static/openbsd/man4/igc.4 b/static/openbsd/man4/igc.4 new file mode 100644 index 00000000..877bedcc --- /dev/null +++ b/static/openbsd/man4/igc.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: igc.4,v 1.3 2023/03/31 13:48:34 jmc Exp $ +.\" +.\" Copyright (c) 2021 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2023 $ +.Dt IGC 4 +.Os +.Sh NAME +.Nm igc +.Nd Intel I225/I226 1Gb/2.5Gb Ethernet device +.Sh SYNOPSIS +.Cd "igc* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports Intel I225/I226 series Ethernet devices. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Intel Corporation +and ported to +.Ox +by +.An Kevin Lo Aq Mt kevlo@openbsd.org . diff --git a/static/openbsd/man4/iha.4 b/static/openbsd/man4/iha.4 new file mode 100644 index 00000000..d722dbd3 --- /dev/null +++ b/static/openbsd/man4/iha.4 @@ -0,0 +1,80 @@ +.\" $OpenBSD: iha.4,v 1.18 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 2001, Kenneth R. Westerback. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt IHA 4 +.Os +.Sh NAME +.Nm iha +.Nd Initio INIC-940/950 based PCI SCSI interface +.Sh SYNOPSIS +.Cd "iha* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports PCI SCSI host adapters based on the Initio INIC-940, +INIC-941 and INIC-950 chips, including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +DTC Domex 3194U Plus +.It +INI-9090U +.It +INI-9100U/UW +.It +Iwill 2935UW +.El +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 +.Pp +.Lk http://www.initio.com/ +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 2.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written for +.Ox +by +.An Kenneth R. Westerback , +based on a +.Fx +driver by +.An Winston Hung . +.Sh BUGS +.Nm +does not currently use tagged command queuing. diff --git a/static/openbsd/man4/ihidev.4 b/static/openbsd/man4/ihidev.4 new file mode 100644 index 00000000..97daf72f --- /dev/null +++ b/static/openbsd/man4/ihidev.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: ihidev.4,v 1.2 2016/07/30 15:44:45 jcs Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 30 2016 $ +.Dt IHIDEV 4 +.Os +.Sh NAME +.Nm ihidev +.Nd HID over I2C support +.Sh SYNOPSIS +.Cd "ihidev* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Human Interface Devices (HID) on +Inter-Integrated Circuit (I2C) buses. +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . diff --git a/static/openbsd/man4/iic.4 b/static/openbsd/man4/iic.4 new file mode 100644 index 00000000..9d7c1039 --- /dev/null +++ b/static/openbsd/man4/iic.4 @@ -0,0 +1,307 @@ +.\" $OpenBSD: iic.4,v 1.136 2026/04/21 19:58:49 jca Exp $ +.\" +.\" Copyright (c) 2004, 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 21 2026 $ +.Dt IIC 4 +.Os +.Sh NAME +.Nm iic +.Nd Inter IC (I2C) bus +.Sh SYNOPSIS +.Cd "iic* at kiic? # macppc" +.Cd "iic* at piic? # macppc" +.Cd "iic* at smu? # macppc" +.Cd "iic* at alipm? # alpha i386 sparc64 " +.Cd "iic* at amdiic? # amd64 i386" +.Cd "iic* at amdpm? # i386" +.Cd "iic* at glxpcib? # i386" +.Cd "iic* at gscsio? # i386" +.Cd "iic* at ichiic? # amd64 i386" +.Cd "iic* at iicmux? # arm64" +.Cd "iic* at nviic? # amd64 i386" +.Cd "iic* at pcamux? # arm64" +.Cd "iic* at pcfiic? # sparc64" +.Cd "iic* at piixpm? # amd64 i386" +.Cd "iic* at viapm? # amd64 i386" +.Cd "iic* at gpioiic? # i386" +.Cd "iic* at gdiumiic? # loongson" +.Cd "iic* at tsciic? # alpha" +.Cd "iic* at amliic? # arm64" +.Cd "iic* at apliic? # arm64" +.Cd "iic* at bcmbsc? # arm64 armv7" +.Cd "iic* at dwiic? # amd64 arm64" +.Cd "iic* at octiic? # octeon" +.Cd "iic* at imxiic? # arm64 armv7" +.Cd "iic* at mviic? # arm64" +.Cd "iic* at rkiic? # arm64 armv7" +.Cd "iic* at qciic? # arm64" +.Cd "iic* at sxitwi? # arm64 armv7" +.Cd "iic* at mpfiic? # riscv64" +.Cd "iic* at ociic? # riscv64" +.Cd "iic* at smtiic? # riscv64" +.Sh DESCRIPTION +I2C is a two-wire bus developed by Philips used for connecting +integrated circuits. +It is commonly used for connecting devices such as EEPROMs, +temperature sensors, fan controllers, real-time clocks, tuners, +and other types of integrated circuits. +.Pp +The +.Nm +driver provides a uniform programming interface layer between +I2C master controllers and various I2C slave devices. +Each I2C master controller attaches an +.Nm +framework; several slave devices can then be attached to the +.Nm +bus. +.Pp +All I2C slave devices are uniquely identified by the address on the bus. +The master accesses a particular slave device using its address. +Devices are found on the bus using a sophisticated scanning routine +which attempts to identify commonly available devices. +On other machines (such as sparc64 and macppc) where the machine ROM +supplies a list of I2C devices, that list is used instead. +.Pp +System Management Bus (SMBus) protocol is also supported by emulating +it with the I2C commands. +.Sh SUPPORTED MASTERS +.Bl -tag -width 13n -compact +.It Xr alipm 4 +Acer Labs M7101 SMBus controller +.It Xr amdiic 4 +AMD-8111 SMBus controller +.It Xr amdpm 4 +AMD-756/766/768/8111 Power Management and SMBus controller +.It Xr amliic 4 +Amlogic I2C controller +.It Xr apliic 4 +Apple I2C controller +.It Xr bcmbsc 4 +Broadcom Serial Control controller +.It Xr dwiic 4 +Synopsys DesignWare I2C controller +.It Xr glxpcib 4 +AMD CS5536 PCI-ISA bridge with timecounter, watchdog timer, and GPIO +.It Xr gpioiic 4 +GPIO I2C controller +.It Xr gscsio 4 +National Semiconductor Geode SC1100 I2C controller +.It Xr ichiic 4 +Intel ICH SMBus controller +.It Xr imxiic 4 +Freescale i.MX I2C controller +.It Xr kiic 4 +Apple Kauai I2C controller +.It Xr mpfiic 4 +Microchip PolarFire SoC MSS I2C controller +.It Xr mviic 4 +Marvell Armada 3700 onboard I2C controller +.It Xr nviic 4 +NVIDIA nForce2/3/4 SMBus controller +.It Xr ociic 4 +OpenCores I2C controller +.It Xr octiic 4 +OCTEON two-wire serial interface +.It Xr pcfiic 4 +Philips PCF8584 I2C controller +.It Xr piic 4 +Apple via-pmu I2C controller +.It Xr piixpm 4 +Intel PIIX SMBus controller +.It Xr rkiic 4 +Rockchip I2C controller +.It Xr qciic 4 +Qualcomm Snapdragon GENI I2C controller +.It Xr rkpmic 4 +Rockchip RK8xx Power Management IC +.It Xr smtiic 4 +SpacemiT I2C controller +.It Xr smu 4 +Apple System Management Unit +.It Xr sxitwi 4 +Allwinner Two Wire Interface controller +.It Xr tsciic 4 +DECchip 21272 and 21274 Core Logic chipset I2C controller +.It Xr viapm 4 +VIA SMBus controller +.El +.Sh SUPPORTED SLAVES +.Bl -tag -width 13n -compact +.It Xr abcrtc 4 +Abracon AB1805 real-time clock +.It Xr adc 4 +Analog Devices AD7416/AD7417/7418 temperature sensor +.It Xr adl 4 +Andigilog aSC7621 temperature, voltage, and fan sensor +.It Xr admcts 4 +Analog Devices ADM1026 temperature and voltage sensor +.It Xr admlc 4 +Analog Devices ADM1024 temperature and voltage sensor +.It Xr admtemp 4 +Analog Devices ADM1021 temperature sensor +.It Xr admtm 4 +Analog Devices ADM1025 temperature and voltage sensor +.It Xr admtmp 4 +Analog Devices ADM1030 temperature sensor +.It Xr admtt 4 +Analog Devices ADM1031 temperature sensor +.It Xr adt 4 +Analog Devices ADT7460 temperature, voltage, and fan sensor +.It Xr adtfsm 4 +Analog Devices ADT7462 temperature, voltage, and fan sensor +.It Xr andl 4 +Andigilog aSC7611 temperature, voltage, and fan sensor +.It Xr asbtm 4 +Asus ASB 100 temperature sensor +.It Xr asms 4 +Apple sudden motion sensor +.It Xr axppmic 4 +X-Powers AXP Power Management IC +.It Xr bdpmic 4 +ROHM BD718x7 Power Management IC +.It Xr bgw 4 +Bosch motion sensor +.It Xr ccpmic 4 +Intel Crystal Cove Power Management IC +.It Xr cwfg 4 +CellWise CW201x fuel gauge +.It Xr dapmic 4 +Dialog DA9063 Power Management IC +.It Xr dsxrtc 4 +Maxim DS3231/DS3232 real-time clock +.It Xr ecadc 4 +environmental monitoring subsystem temperature sensor +.It Xr escodec 4 +Everest Semiconductor ES8316 audio codec +.It Xr fanpwr 4 +Fairchild FAN53555 voltage regulator +.It Xr fcu 4 +Apple Fan Control Unit sensor device +.It Xr fintek 4 +Fintek F75375 temperature sensor +.It Xr fusbtc 4 +Fairchild FUSB302 USB Type-C Port controller +.It Xr glenv 4 +Genesys Logic GL518SM temperature, voltage, and fan sensor +.It Xr iatp 4 +Atmel maXTouch touchpad and touchscreen +.It Xr ietp 4 +Elantech touchpad +.It Xr ihidev 4 +HID over I2C support +.It Xr ipmi 4 +Intelligent Platform Management Interface driver +.It Xr islrtc 4 +Intersil ISL1208/1218 real-time clock +.It Xr lisa 4 +STMicroelectronics LIS331DL MEMS motion sensor +.It Xr lm 4 +National Semiconductor LM78/79/81 temperature, voltage, and fan sensor +.It Xr lmenv 4 +National Semiconductor LM87 temperature, voltage, and fan sensor +.It Xr lmn 4 +National Semiconductor LM93 temperature, voltage, and fan sensor +.It Xr lmtemp 4 +National Semiconductor LM75/LM76/LM77 temperature sensor +.It Xr maxds 4 +Maxim DS1624/DS1631/DS1721 temperature sensor +.It Xr maxrtc 4 +Maxim DS1307/DS1339 real-time clock +.It Xr maxtmp 4 +Maxim MAX6642/MAX6690 temperature sensor +.It Xr mcprtc 4 +Microchip MCP79400 real-time clock +.It Xr mfokrtc 4 +M41T8x real-time clock +.It Xr nvt 4 +Nuvoton W83795G/ADG temperature, voltage, and fan sensor +.It Xr pcagpio 4 +Philips PCA955[4567] GPIO controller +.It Xr pcaled 4 +Philips PCA9532/9552 GPIO LED dimmer +.It Xr pcamux 4 +Philips PCA954[678] I2C switch/mux +.It Xr pcfadc 4 +Philips PCF8591 temperature sensor +.It Xr pcfrtc 4 +NXP PCF8523 real-time clock +.It Xr pcxrtc 4 +NXP PCF8563 real-time clock +.It Xr pcyrtc 4 +NXP PCF85063A/TP real-time clock +.It Xr pijuice 4 +PiJuice HAT UPS +.It Xr ricohrtc 4 +Ricoh RS5C372 real-time clock +.It Xr rkpmic 4 +Rockchip RK8xx Power Management IC +.It Xr sdtemp 4 +SO-DIMM (JC-42.4) temperature sensor +.It Xr sncodec 4 +Texas Instruments TAS2764 digital amplifier +.It Xr spdmem 4 +Serial Presence Detect memory +.It Xr ssdfb 4 +Solomon Systech SSD1306/SSD1309 OLED display module +.It Xr stsec 4 +ST7 embedded controller +.It Xr sypwr 4 +Silergy SY8106A voltage regulator +.It Xr tascodec 4 +Texas Instruments TAS2770 digital amplifier +.It Xr tcpci 4 +USB Type-C Port Controller Interface +.It Xr tda 4 +Philips TDA8444 fan controller +.It Xr thmc 4 +TI THMC50, Analog ADM1022/1028 temperature sensor +.It Xr tipd 4 +TI USB Type-C power delivery controller +.It Xr tipmic 4 +Intel Dollar Cove TI Power Management IC +.It Xr titmp 4 +TI TMP451 temperature sensor +.It Xr tsl 4 +TAOS TSL2560/61 light sensor +.It Xr wbenv 4 +Winbond W83L784R/W83L785R/W83L785TS-L temperature, voltage, and fan sensor +.It Xr wbng 4 +Winbond W83793G temperature, voltage, and fan sensor +.El +.Sh SEE ALSO +.Xr iicmux 4 , +.Xr intro 4 , +.Xr iic 9 +.Sh HISTORY +The I2C framework first appeared in +.Nx 2.0 . +.Ox +support was added in +.Ox 3.6 . +I2C bus scanning was added in +.Ox 3.9 . +.Sh AUTHORS +The I2C framework was written by +.An Steve C. Woodford +and +.An Jason R. Thorpe +for +.Nx +and then ported to +.Ox +by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/iicmux.4 b/static/openbsd/man4/iicmux.4 new file mode 100644 index 00000000..cf9cb499 --- /dev/null +++ b/static/openbsd/man4/iicmux.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: iicmux.4,v 1.1 2021/11/21 11:10:35 kettenis Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 21 2021 $ +.Dt IICMUX 4 +.Os +.Sh NAME +.Nm iicmux +.Nd I2C mux +.Sh SYNOPSIS +.Cd "iicmux* at iic?" +.Cd "iic* at pcamux?" +.Sh DESCRIPTION +The +.Nm +driver provides support for I2C bus multiplexers that use SoC pin +multiplexing to route the I2C signals. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/ikbd.4 b/static/openbsd/man4/ikbd.4 new file mode 100644 index 00000000..56ab49ae --- /dev/null +++ b/static/openbsd/man4/ikbd.4 @@ -0,0 +1,40 @@ +.\" $OpenBSD: ikbd.4,v 1.2 2016/01/17 07:52:02 jmc Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 17 2016 $ +.Dt IKBD 4 +.Os +.Sh NAME +.Nm ikbd +.Nd I2C HID keyboard support +.Sh SYNOPSIS +.Cd "ikbd* at ihidev?" +.Cd "wskbd* at ikbd? mux 1" +.Sh DESCRIPTION +The +.Nm +driver provides support for I2C HID keyboards. +Access to these devices is through the +.Xr wscons 4 +driver. +.Sh SEE ALSO +.Xr ihidev 4 , +.Xr wskbd 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.9 . diff --git a/static/openbsd/man4/ims.4 b/static/openbsd/man4/ims.4 new file mode 100644 index 00000000..1913e253 --- /dev/null +++ b/static/openbsd/man4/ims.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: ims.4,v 1.4 2021/01/22 17:35:00 jcs Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 22 2021 $ +.Dt IMS 4 +.Os +.Sh NAME +.Nm ims +.Nd I2C HID pointing device support +.Sh SYNOPSIS +.Cd "ims* at ihidev?" +.Cd "wsmouse* at ims? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides support for I2C HID touchpads and other pointing devices. +Access to these devices is through the +.Xr wscons 4 +driver. +.Sh SEE ALSO +.Xr ihidev 4 , +.Xr imt 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . diff --git a/static/openbsd/man4/imt.4 b/static/openbsd/man4/imt.4 new file mode 100644 index 00000000..a22e25d8 --- /dev/null +++ b/static/openbsd/man4/imt.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: imt.4,v 1.2 2016/07/30 15:44:45 jcs Exp $ +.\" +.\" Copyright (c) 2016 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 30 2016 $ +.Dt IMT 4 +.Os +.Sh NAME +.Nm imt +.Nd I2C HID multitouch touchpad support +.Sh SYNOPSIS +.Cd "imt* at ihidev?" +.Cd "wsmouse* at imt? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides support for I2C HID touchpads conforming to the +Windows Precision Touchpad standard. +Access to these devices is through the +.Xr wscons 4 +driver. +.Sh SEE ALSO +.Xr ihidev 4 , +.Xr ims 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . diff --git a/static/openbsd/man4/imxanatop.4 b/static/openbsd/man4/imxanatop.4 new file mode 100644 index 00000000..42d5fce5 --- /dev/null +++ b/static/openbsd/man4/imxanatop.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: imxanatop.4,v 1.3 2018/06/16 14:32:22 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 16 2018 $ +.Dt IMXANATOP 4 +.Os +.Sh NAME +.Nm imxanatop +.Nd i.MX Anatop regulator +.Sh SYNOPSIS +.Cd "imxanatop* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Anatop voltage regulators integrated in +i.MX 6, i.MX 7 and i.MX 8 processors. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/imxdog.4 b/static/openbsd/man4/imxdog.4 new file mode 100644 index 00000000..e5bc4ce6 --- /dev/null +++ b/static/openbsd/man4/imxdog.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: imxdog.4,v 1.1 2021/05/28 12:32:24 patrick Exp $ +.\" +.\" Copyright (c) 2021 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 28 2021 $ +.Dt IMXDOG 4 +.Os +.Sh NAME +.Nm imxdog +.Nd i.MX watchdog timer +.Sh SYNOPSIS +.Cd "imxdog* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the watchdog timer integrated in +i.MX 6, i.MX 7 and i.MX 8 processors. +.Sh SEE ALSO +.Xr intro 4 , +.Xr watchdog 4 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/imxesdhc.4 b/static/openbsd/man4/imxesdhc.4 new file mode 100644 index 00000000..342e1717 --- /dev/null +++ b/static/openbsd/man4/imxesdhc.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: imxesdhc.4,v 1.4 2021/05/28 12:30:34 patrick Exp $ +.\" Copyright (c) 2014 Sylvestre Gallon +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 28 2021 $ +.Dt IMXESDHC 4 +.Os +.Sh NAME +.Nm imxesdhc +.Nd i.MX SD host controller +.Sh SYNOPSIS +.Cd "imxesdhc* at fdt?" +.Cd "sdmmc* at imxesdhc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the MMC/SD/SDIO controller integrated in +i.MX 6, i.MX 7 and i.MX 8 processors. +.Pp +The +.Xr sdmmc 4 +subsystem performs SD/MMC transactions to communicate with +MMC, SD, SDHC, or SDIO devices inserted into the SD slot. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sdmmc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/imxgpc.4 b/static/openbsd/man4/imxgpc.4 new file mode 100644 index 00000000..8aa72f90 --- /dev/null +++ b/static/openbsd/man4/imxgpc.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: imxgpc.4,v 1.2 2019/01/11 20:39:46 jmc Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 11 2019 $ +.Dt IMXGPC 4 +.Os +.Sh NAME +.Nm imxgpc +.Nd i.MX general power controller +.Sh SYNOPSIS +.Cd "imxgpc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the i.MX general power controller (GPC). +It acts as a "transparent" interrupt controller and hands interrupt handlers +to the parent interrupt controller. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/imxgpio.4 b/static/openbsd/man4/imxgpio.4 new file mode 100644 index 00000000..c0b89830 --- /dev/null +++ b/static/openbsd/man4/imxgpio.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: imxgpio.4,v 1.1 2018/04/01 09:03:25 jsg Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 1 2018 $ +.Dt IMXGPIO 4 +.Os +.Sh NAME +.Nm imxgpio +.Nd i.MX GPIO controller +.Sh SYNOPSIS +.Cd "imxgpio* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO ports found on i.MX SoCs. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/imxiic.4 b/static/openbsd/man4/imxiic.4 new file mode 100644 index 00000000..7a1cff63 --- /dev/null +++ b/static/openbsd/man4/imxiic.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: imxiic.4,v 1.5 2020/11/17 14:33:26 patrick Exp $ +.\" +.\" Copyright (c) 2014 Sylvestre Gallon +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 17 2020 $ +.Dt IMXIIC 4 +.Os +.Sh NAME +.Nm imxiic +.Nd i.MX onboard I2C controller +.Sh SYNOPSIS +.Cd "imxiic* at acpi?" +.Cd "imxiic* at fdt?" +.Cd "iic* at imxiic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the I2C controller found on the Freescale +i.MX 6, i.MX 7 and i.MX 8 processor families. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/imxpciephy.4 b/static/openbsd/man4/imxpciephy.4 new file mode 100644 index 00000000..605b8ea0 --- /dev/null +++ b/static/openbsd/man4/imxpciephy.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: imxpciephy.4,v 1.1 2020/04/26 15:11:15 patrick Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 26 2020 $ +.Dt IMXPCIEPHY 4 +.Os +.Sh NAME +.Nm imxpciephy +.Nd NXP i.MX PCIe PHY +.Sh SYNOPSIS +.Cd "imxpciephy* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PCIe PHY integrated on various +NXP i.MX SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/imxpwm.4 b/static/openbsd/man4/imxpwm.4 new file mode 100644 index 00000000..6553c270 --- /dev/null +++ b/static/openbsd/man4/imxpwm.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: imxpwm.4,v 1.1 2020/03/27 16:56:39 patrick Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2020 $ +.Dt IMXPWM 4 +.Os +.Sh NAME +.Nm imxpwm +.Nd NXP i.MX PWM controller +.Sh SYNOPSIS +.Cd "imxpwm* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PWM controllers integrated on various +NXP i.MX SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/imxrtc.4 b/static/openbsd/man4/imxrtc.4 new file mode 100644 index 00000000..f31fd4a4 --- /dev/null +++ b/static/openbsd/man4/imxrtc.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: imxrtc.4,v 1.2 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt IMXRTC 4 +.Os +.Sh NAME +.Nm imxrtc +.Nd i.MX real-time clock +.Sh SYNOPSIS +.Cd "imxrtc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the RTC integrated in Freescale i.MX7 and +i.MX8 processors. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/imxspi.4 b/static/openbsd/man4/imxspi.4 new file mode 100644 index 00000000..eb32b573 --- /dev/null +++ b/static/openbsd/man4/imxspi.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: imxspi.4,v 1.1 2019/10/07 19:43:00 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 7 2019 $ +.Dt IMXSPI 4 +.Os +.Sh NAME +.Nm imxspi +.Nd i.MX onboard SPI controller +.Sh SYNOPSIS +.Cd "imxspi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SPI controller found on the Freescale +i.MX 6, i.MX 7 and i.MX 8 processor families. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/imxsrc.4 b/static/openbsd/man4/imxsrc.4 new file mode 100644 index 00000000..5e202a15 --- /dev/null +++ b/static/openbsd/man4/imxsrc.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: imxsrc.4,v 1.2 2019/01/11 20:39:46 jmc Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 11 2019 $ +.Dt IMXSRC 4 +.Os +.Sh NAME +.Nm imxsrc +.Nd i.MX system reset controller +.Sh SYNOPSIS +.Cd "imxsrc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the i.MX system reset controller (SRC). +It registers as a reset controller so that drivers can reset devices +by asserting their reset pins. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/imxtmu.4 b/static/openbsd/man4/imxtmu.4 new file mode 100644 index 00000000..35340698 --- /dev/null +++ b/static/openbsd/man4/imxtmu.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: imxtmu.4,v 1.1 2019/08/27 12:51:57 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 27 2019 $ +.Dt IMXTMU 4 +.Os +.Sh NAME +.Nm imxtmu +.Nd i.MX temperature monitor +.Sh SYNOPSIS +.Cd "imxtmu* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor found on the +Freescale i.MX8 processors. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/imxuart.4 b/static/openbsd/man4/imxuart.4 new file mode 100644 index 00000000..3d9bbd04 --- /dev/null +++ b/static/openbsd/man4/imxuart.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: imxuart.4,v 1.1 2018/04/01 09:03:25 jsg Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 1 2018 $ +.Dt IMXUART 4 +.Os +.Sh NAME +.Nm imxuart +.Nd i.MX Universal Asynchronous Receiver/Transmitter +.Sh SYNOPSIS +.Cd "imxuart* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the i.MX Universal Asynchronous Receiver/Transmitter +(UART). +.Sh SEE ALSO +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/inet.4 b/static/openbsd/man4/inet.4 new file mode 100644 index 00000000..05a81798 --- /dev/null +++ b/static/openbsd/man4/inet.4 @@ -0,0 +1,182 @@ +.\" $OpenBSD: inet.4,v 1.20 2019/10/30 10:39:53 jmc Exp $ +.\" $NetBSD: inet.4,v 1.3 1994/11/30 16:22:18 jtc Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)inet.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: October 30 2019 $ +.Dt INET 4 +.Os +.Sh NAME +.Nm inet +.Nd Internet protocol family +.Sh SYNOPSIS +.In sys/types.h +.In netinet/in.h +.Sh DESCRIPTION +The Internet protocol family is a collection of protocols +layered atop the +.Em Internet Protocol +.Pq Tn IP +transport layer, and utilizing the Internet address format. +The Internet family provides protocol support for the +.Dv SOCK_STREAM , +.Dv SOCK_DGRAM , +and +.Dv SOCK_RAW +socket types; the +.Dv SOCK_RAW +interface provides access to the +.Tn IP +protocol. +.Sh ADDRESSING +Internet addresses are four byte quantities, stored in +network standard format. +The include file +.In netinet/in.h +defines this address as a discriminated union. +.Pp +Sockets bound to the Internet protocol family utilize +the following addressing structure, +.Bd -literal -offset indent +struct sockaddr_in { + u_int8_t sin_len; + sa_family_t sin_family; + in_port_t sin_port; + struct in_addr sin_addr; + int8_t sin_zero[8]; +}; +.Ed +.Pp +Sockets may be created with the local address +.Dv INADDR_ANY +to effect +.Dq wildcard +matching on incoming messages. +The address in a +.Xr connect 2 +or +.Xr sendto 2 +call may be given as +.Dv INADDR_ANY +to mean +.Dq this host . +The distinguished address +.Dv INADDR_BROADCAST +is allowed as a shorthand for the broadcast address on the primary +network if the first network configured supports broadcast. +.Sh PROTOCOLS +The Internet protocol family is comprised of +the +.Tn IP +transport protocol, Internet Control +Message Protocol +.Pq Tn ICMP , +Transmission Control +Protocol +.Pq Tn TCP , +and User Datagram Protocol +.Pq Tn UDP . +.Tn TCP +is used to support the +.Dv SOCK_STREAM +abstraction while +.Tn UDP +is used to support the +.Dv SOCK_DGRAM +abstraction. +A raw interface to +.Tn IP +is available +by creating an Internet socket of type +.Dv SOCK_RAW . +The +.Tn ICMP +message protocol is accessible from a raw socket. +.Pp +The 32-bit Internet address contains both network and host parts. +It is frequency-encoded; the most-significant bit is clear +in Class A addresses, in which the high-order 8 bits are the network +number. +Class B addresses use the high-order 16 bits as the network field, +and Class C addresses have a 24-bit network part. +Sites with a cluster of local networks and a connection to the +Internet may choose to use a single network number for the cluster; +this is done by using subnet addressing. +The local (host) portion of the address is further subdivided +into subnet and host parts. +Within a subnet, each subnet appears to be an individual network; +externally, the entire cluster appears to be a single, uniform +network requiring only a single routing entry. +Subnet addressing is enabled and examined by the following +.Xr ioctl 2 +commands on a datagram socket in the Internet domain; +they have the same form as the +.Dv SIOCIFADDR +command (see +.Xr netintro 4 ) . +.Bl -tag -width SIOCSIFNETMASK +.It Dv SIOCSIFNETMASK +Set interface network mask. +The network mask defines the network part of the address; +if it contains more of the address than the address type would indicate, +then subnets are in use. +.It Dv SIOCGIFNETMASK +Get interface network mask. +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr socket 2 , +.Xr inet_net_ntop 3 , +.Xr inet_ntop 3 , +.Xr icmp 4 , +.Xr ip 4 , +.Xr netintro 4 , +.Xr tcp 4 , +.Xr udp 4 +.Rs +.%T "An Introductory 4.3 BSD Interprocess Communication Tutorial" +.%B PS1 +.%N 7 +.Re +.Rs +.%T "An Advanced 4.3 BSD Interprocess Communication Tutorial" +.%B PS1 +.%N 8 +.Re +.Sh HISTORY +The +.Nm +protocol interface appeared in +.Bx 4.2 . +.Sh CAVEATS +The Internet protocol support is subject to change as +the Internet protocols develop. +Users should not depend on details of the current implementation, but rather +the services exported. diff --git a/static/openbsd/man4/inet6.4 b/static/openbsd/man4/inet6.4 new file mode 100644 index 00000000..30651cb6 --- /dev/null +++ b/static/openbsd/man4/inet6.4 @@ -0,0 +1,222 @@ +.\" $OpenBSD: inet6.4,v 1.46 2022/10/10 00:12:45 jsg Exp $ +.\" $KAME: inet6.4,v 1.19 2000/11/24 10:13:18 itojun Exp $ +.\" +.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the project nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: October 10 2022 $ +.Dt INET6 4 +.Os +.Sh NAME +.Nm inet6 +.Nd Internet protocol version 6 family +.Sh SYNOPSIS +.In sys/types.h +.In netinet/in.h +.Sh DESCRIPTION +The Internet Protocol version 6 family +is an updated version of the Internet Protocol version 4 family. +It comprises Internet Protocol version 6 +.Pq IPv6 , +Internet Control Message Protocol version 6 +.Pq ICMPv6 , +Transmission Control Protocol +.Pq TCP , +and User Datagram Protocol +.Pq UDP . +.Xr tcp 4 +is used to support the +.Dv SOCK_STREAM +abstraction while +.Xr udp 4 +is used to support the +.Dv SOCK_DGRAM +abstraction. +A raw interface to IPv6 is available by creating an Internet socket of type +.Dv SOCK_RAW . +The ICMPv6 message protocol is accessible from a raw socket. +.Pp +IPv6 addresses are 128-bit quantities, +stored in network standard byteorder. +The include file +.In netinet/in.h +defines this address +as a discriminated union. +.Pp +Sockets bound to the +.Nm +family utilize the following addressing structure: +.Bd -literal -offset indent +struct sockaddr_in6 { + u_int8_t sin6_len; + sa_family_t sin6_family; + in_port_t sin6_port; + u_int32_t sin6_flowinfo; + struct in6_addr sin6_addr; + u_int32_t sin6_scope_id; +}; +.Ed +.Pp +Sockets may be created with the local address +.Dq :: +(which is equal to IPv6 address +.Dv 0:0:0:0:0:0:0:0 ) +to effect +.Dq wildcard +matching on incoming messages. +.Pp +For security reasons, +.Ox +does not route IPv4 traffic to an +.Dv AF_INET6 +socket, +and does not support IPv4 mapped addresses, +where IPv4 traffic is seen as if it comes from an IPv6 address like +.Dq ::ffff:10.1.1.1 . +Where both IPv4 and IPv6 traffic need to be accepted, +bind and listen on two sockets. +.Pp +Global addresses utilise the first 48 bits of the address +for the routing prefix. +The next 16 bits designate the subnet, +and the final 64 bits are used as a host identifier. +.Pp +The IPv6 specification also defines link-local addresses, +which are scoped. +A scoped address is ambiguous to the kernel +if it is specified without a scope identifier. +To manipulate scoped addresses properly from userland, +programs must use the advanced API defined in RFC 3542. +A compact description of the advanced API is available in +.Xr ip6 4 . +If scoped addresses are specified without explicit scope, +the kernel may raise an error. +.Pp +KAME supports an extended numeric IPv6 address notation +for link-local addresses, +such as +.Dq fe80::1%de0 +to specify +.Dq fe80::1 +on the +.Dq de0 +interface. +This notation is supported by +.Xr getaddrinfo 3 +and +.Xr getnameinfo 3 , +as well as userland programs such as +.Xr telnet 1 +and +.Xr ftp 1 . +.Pp +Scoped addresses are handled specially in the kernel. +In kernel structures like routing tables or interface structures, +scoped addresses have their interface index embedded into the address. +Therefore +the address on some kernel structures is not the same as that on the wire. +The embedded index will be visible on +.Dv PF_ROUTE +sockets, kernel memory access via +.Xr kvm 3 , +and some other occasions. +HOWEVER, users should never use the embedded form. +.Sh IPv6 SETUP +Generally speaking, +IPv6 connectivity is achieved in a fashion similar to that for IPv4. +For native IPv6 setup, +routers attach to the network either manually or using +.Cm autoconf +to connect to an ISP; +hosts receive an address prefix from a router advertisement daemon such as +.Xr rad 8 +and use +.Cm autoconf +for stateless address configuration (SLAAC). +For setups which tunnel IPv6 over IPv4, +see +.Xr gif 4 . +.Pp +The INET6 and TUNNEL sections of +.Xr ifconfig 8 +contain information relevant to IPv6 setups; +settings can be made permanent using +.Xr hostname.if 5 +files. +Routers need to set the +.Va net.inet6.ip6.forwarding +.Xr sysctl 2 . +.Sh SEE ALSO +.Xr socket 2 , +.Xr icmp6 4 , +.Xr ip6 4 , +.Xr tcp 4 , +.Xr udp 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr rad 8 +.Sh STANDARDS +.Rs +.%A Tatsuya Jinmei +.%A Atsushi Onoe +.%D June 2000 +.%N draft-ietf-ipngwg-scopedaddr-format-02.txt +.%O work in progress material +.%R internet draft +.%T "An Extension of Format for IPv6 Scoped Addresses" +.Re +.Pp +.Rs +.%A R. Gilligan +.%A S. Thomson +.%A J. Bound +.%A J. McCann +.%A W. Stevens +.%D February 2003 +.%R RFC 3493 +.%T Basic Socket Interface Extensions for IPv6 +.Re +.Pp +.Rs +.%A W. Stevens +.%A M. Thomas +.%A E. Nordmark +.%A T. Jinmei +.%D May 2003 +.%R RFC 3542 +.%T Advanced Sockets Application Programming Interface (API) for IPv6 +.Re +.Sh HISTORY +The implementation described herein appeared in WIDE/KAME project. +.Sh CAVEATS +It is advisable to explicitly reject all packets to your network +not used by any of your interface prefixes. +Otherwise packets that have a destination address belonging to your network +may be routed back to your provider via the default route. +Set a reject route for your assigned prefix: +.Pp +.Dl # route add -net 2001:db8::/48 ::1 -reject diff --git a/static/openbsd/man4/inphy.4 b/static/openbsd/man4/inphy.4 new file mode 100644 index 00000000..b2a89333 --- /dev/null +++ b/static/openbsd/man4/inphy.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: inphy.4,v 1.11 2020/01/24 05:08:02 jsg Exp $ +.\" $NetBSD: inphy.4,v 1.1 1998/11/04 05:53:58 thorpej Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 24 2020 $ +.Dt INPHY 4 +.Os +.Sh NAME +.Nm inphy +.Nd Intel i82555/i82562 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "inphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Intel i82555, i82562EM, i82562ET and i82562G 10/100 +Ethernet PHYs. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/intelpmc.4 b/static/openbsd/man4/intelpmc.4 new file mode 100644 index 00000000..b9a6378f --- /dev/null +++ b/static/openbsd/man4/intelpmc.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: intelpmc.4,v 1.1 2024/08/04 14:21:09 kettenis Exp $ +.\" +.\" Copyright (c) 2024 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 4 2024 $ +.Dt INTELPMC 4 +.Os +.Sh NAME +.Nm intelpmc +.Nd Intel power management controller +.Sh SYNOPSIS +.Cd "intelpmc* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver implements support for the power management controller found on +Intel SoCs. +It provides support for entering low power idle states of the SoC. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/inthid.4 b/static/openbsd/man4/inthid.4 new file mode 100644 index 00000000..acbc6ec8 --- /dev/null +++ b/static/openbsd/man4/inthid.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: inthid.4,v 1.1 2025/12/27 13:01:48 kettenis Exp $ +.\" +.\" Copyright (c) 2020 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 27 2025 $ +.Dt INTHID 4 +.Os +.Sh NAME +.Nm inthid +.Nd Intel HID event and 5-button array +.Sh SYNOPSIS +.Cd "inthid* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver supports Intel HID event and 5-button array devices found on some +tablet devices. +.Sh SEE ALSO +.Xr acpi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@jcs.org . diff --git a/static/openbsd/man4/iophy.4 b/static/openbsd/man4/iophy.4 new file mode 100644 index 00000000..361d45ee --- /dev/null +++ b/static/openbsd/man4/iophy.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: iophy.4,v 1.9 2009/07/31 14:20:29 jmc Exp $ +.\" $NetBSD: iophy.4,v 1.3 1999/09/08 13:58:38 soren Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 31 2009 $ +.Dt IOPHY 4 +.Os +.Sh NAME +.Nm iophy +.Nd Intel i82553 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "iophy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Intel i82553 10/100 Ethernet PHYs found on some +Intel i82557-based Ethernet cards. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/iosf.4 b/static/openbsd/man4/iosf.4 new file mode 100644 index 00000000..29f8da75 --- /dev/null +++ b/static/openbsd/man4/iosf.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: iosf.4,v 1.1 2023/04/23 00:44:44 dlg Exp $ +.\" +.\" Copyright (c) 2023 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 23 2023 $ +.Dt IOSF 4 +.Os +.Sh NAME +.Nm iosf +.Nd Intel OnChip System Fabric device +.Sh SYNOPSIS +.Cd "iosf* at acpi?" +.Cd "iosf* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support routines for platforms using the +Intel OnChip System Fabric. +.Pp +The +.Xr dwiic 4 +driver uses the MailBox Interface (MBI) provided by +.Nm +to coordinate access to I2C devices. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr dwiic 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/ip.4 b/static/openbsd/man4/ip.4 new file mode 100644 index 00000000..bb445a42 --- /dev/null +++ b/static/openbsd/man4/ip.4 @@ -0,0 +1,619 @@ +.\" $OpenBSD: ip.4,v 1.45 2026/04/18 09:30:25 sthen Exp $ +.\" $NetBSD: ip.4,v 1.3 1994/11/30 16:22:19 jtc Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)ip.4 8.2 (Berkeley) 11/30/93 +.\" +.Dd $Mdocdate: April 18 2026 $ +.Dt IP 4 +.Os +.Sh NAME +.Nm ip +.Nd Internet Protocol +.Sh SYNOPSIS +.In sys/types.h +.In sys/socket.h +.In netinet/in.h +.Ft int +.Fn socket AF_INET SOCK_RAW proto +.Sh DESCRIPTION +.Tn IP +is the network layer protocol used +by the Internet protocol family. +Options may be set at the +.Tn IP +level +when using higher-level protocols that are based on +.Tn IP +(such as +.Tn TCP +and +.Tn UDP ) . +It may also be accessed +through a +.Dq raw socket +when developing new protocols, or +special-purpose applications. +.Pp +There are several +.Tn IP-level +.Xr setsockopt 2 Ns / Ns Xr getsockopt 2 +options. +.Dv IP_OPTIONS +may be used to provide +.Tn IP +options to be transmitted in the +.Tn IP +header of each outgoing packet +or to examine the header options on incoming packets. +.Tn IP +options may be used with any socket type in the Internet family. +The format of +.Tn IP +options to be sent is that specified by the +.Tn IP +protocol specification (RFC 791), with one exception: +the list of addresses for Source Route options must include the first-hop +gateway at the beginning of the list of gateways. +The first-hop gateway address will be extracted from the option list +and the size adjusted accordingly before use. +To disable previously specified options, +use a zero-length buffer: +.Bd -literal -offset indent +setsockopt(s, IPPROTO_IP, IP_OPTIONS, NULL, 0); +.Ed +.Pp +.Dv IP_TOS +and +.Dv IP_TTL +may be used to set the type-of-service and time-to-live +fields in the +.Tn IP +header for +.Dv SOCK_STREAM , +.Dv SOCK_DGRAM +and +.Dv SOCK_RAW +sockets. +For example, +.Bd -literal -offset indent +int tos = IPTOS_LOWDELAY; /* see */ +setsockopt(s, IPPROTO_IP, IP_TOS, &tos, sizeof(tos)); + +int ttl = 60; /* max = 255 */ +setsockopt(s, IPPROTO_IP, IP_TTL, &ttl, sizeof(ttl)); +.Ed +.Pp +.Dv IP_IPDEFTTL +can be used to retrieve the system wide default TTL. +.Pp +If the +.Dv IP_RECVDSTADDR +option is enabled on a +.Dv SOCK_DGRAM +socket, +the +.Xr recvmsg 2 +call will return the destination +.Tn IP +address for a +.Tn UDP +datagram. +The +.Va msg_control +field in the +.Vt msghdr +structure points to a buffer that contains a +.Vt cmsghdr +structure followed by the +.Tn IP +address. +The +.Vt cmsghdr +fields have the following values: +.Bd -literal -offset indent +cmsg_len = CMSG_LEN(sizeof(struct in_addr)) +cmsg_level = IPPROTO_IP +cmsg_type = IP_RECVDSTADDR +.Ed +.Pp +If the +.Dv IP_RECVDSTPORT +option is enabled on a +.Dv SOCK_DGRAM +socket, +the +.Xr recvmsg 2 +call will return the destination +port for a +.Tn UDP +datagram. +The +.Va msg_control +field in the +.Vt msghdr +structure points to a buffer that contains a +.Vt cmsghdr +structure followed by the port in 16-bit network byte order. +The +.Vt cmsghdr +fields have the following values: +.Bd -literal -offset indent +cmsg_len = CMSG_LEN(sizeof(u_int16_t)) +cmsg_level = IPPROTO_IP +cmsg_type = IP_RECVDSTPORT +.Ed +.Pp +If the +.Dv IP_RECVTTL +option is enabled on a +.Dv SOCK_DGRAM +or +.Dv SOCK_RAW +socket, the +.Xr recvmsg 2 +call will return the +.Tn TTL +of the received datagram. +The +.Va msg_control +field in the +.Vt msghdr +structure points to a buffer that contains a +.Vt cmsghdr +structure followed by the +.Tn TTL +value. +The +.Vt cmsghdr +fields have the following values: +.Bd -literal -offset indent +cmsg_len = CMSG_LEN(sizeof(u_int8_t)) +cmsg_level = IPPROTO_IP +cmsg_type = IP_RECVTTL +.Ed +.Pp +The +.Dv IP_MINTTL +option may be used on TCP and UDP sockets to discard packets with a TTL +lower than the option value. +This can be used to implement the +.Em Generalized TTL Security Mechanism (GTSM) +according to RFC 5082. +To discard all packets with a TTL lower than 255: +.Bd -literal -offset indent +int minttl = 255; +setsockopt(s, IPPROTO_IP, IP_MINTTL, &minttl, sizeof(minttl)); +.Ed +.Pp +If the +.Dv IP_RECVIF +option is enabled on a +.Dv SOCK_DGRAM +or +.Dv SOCK_RAW +socket, the +.Xr recvmsg 2 +call returns a +.Vt "struct sockaddr_dl" +corresponding to the interface on which the +packet was received. +The +.Va msg_control +field in the +.Vt msghdr +structure points to a buffer that contains a +.Vt cmsghdr +structure followed by the +.Vt "struct sockaddr_dl" . +The +.Vt cmsghdr +fields have the following values: +.Bd -literal -offset indent +cmsg_len = CMSG_LEN(sizeof(struct sockaddr_dl)) +cmsg_level = IPPROTO_IP +cmsg_type = IP_RECVIF +.Ed +.Pp +If the +.Dv IP_IPSECFLOWINFO +option is enabled on a +.Dv SOCK_DGRAM +socket, +the +.Xr recvmsg 2 +call will return information identifying the incoming +IPsec SA for a +.Tn UDP +datagram. +The +.Va msg_control +field in the +.Vt msghdr +structure points to a buffer that contains a +.Vt cmsghdr +structure followed by flow information in 32-bit network byte order. +When this information is passed to a +.Xr sendmsg 2 +call, the ID of the incoming SA will be used for looking up the +outgoing SA for the +.Tn UDP +datagram. +The +.Vt cmsghdr +fields for +.Xr recvmsg 2 +and +.Xr sendmsg 2 +have the following values: +.Bd -literal -offset indent +cmsg_len = CMSG_LEN(sizeof(u_int32_t)) +cmsg_level = IPPROTO_IP +cmsg_type = IP_IPSECFLOWINFO +.Ed +.Pp +The +.Dv IP_PORTRANGE +option causes the default allocation policy for when the kernel is asked +to choose a free port number. +Three choices are available: +.Pp +.Bl -tag -width IP_PORTRANGE_DEFAULT -compact -offset indent +.It Dv IP_PORTRANGE_DEFAULT +The regular range of non-reserved ports. +.It Dv IP_PORTRANGE_HIGH +A high range, for fun. +.It Dv IP_PORTRANGE_LOW +Reserved ports; between 600 and 1023. +.El +.Pp +If the +.Dv IP_RECVRTABLE +option is enabled on a +.Dv SOCK_DGRAM +socket, +the +.Xr recvmsg 2 +call will return the source routing domain for a +.Tn UDP +datagram. +The +.Va msg_control +field in the +.Vt msghdr +structure points to a buffer that contains a +.Vt cmsghdr +structure followed by the routing table ID. +The +.Vt cmsghdr +fields have the following values: +.Bd -literal -offset indent +cmsg_len = CMSG_LEN(sizeof(u_int)) +cmsg_level = IPPROTO_IP +cmsg_type = IP_RECVRTABLE +.Ed +.Pp +When sending on a +.Dv SOCK_DGRAM +socket with +.Xr sendmsg 2 , +the source address to be used can be passed as ancillary data +with a type code of +.Dv IP_SENDSRCADDR . +The +.Va msg_control +field in the +.Vt msghdr +structure should point to a buffer that contains a +.Vt cmsghdr +structure followed by the requested source address. +The +.Vt cmsghdr +fields should have the following values: +.Bd -literal -offset indent +cmsg_len = CMSG_LEN(sizeof(struct in_addr)) +cmsg_level = IPPROTO_IP +cmsg_type = IP_SENDSRCADDR +.Ed +.Pp +The same checks and restrictions as for +.Xr bind 2 +apply, unless the socket is bound to +.Dv INADDR_ANY . +In this case, there is no source address overlap check. +.Ss "Multicast Options" +.Tn IP +multicasting is supported only on +.Dv AF_INET +sockets of type +.Dv SOCK_DGRAM +and +.Dv SOCK_RAW , +and only on networks where the interface +driver supports multicasting. +.Pp +The +.Dv IP_MULTICAST_TTL +option changes the time-to-live (TTL) +for outgoing multicast datagrams +in order to control the scope of the multicasts: +.Bd -literal -offset indent +u_char ttl; /* range: 0 to 255, default = 1 */ +setsockopt(s, IPPROTO_IP, IP_MULTICAST_TTL, &ttl, sizeof(ttl)); +.Ed +.Pp +Datagrams with a TTL of 1 are not forwarded beyond the local network. +Multicast datagrams with a TTL of 0 will not be transmitted on any network, +but may be delivered locally if the sending host belongs to the destination +group and if multicast loopback has not been disabled on the sending socket +(see below). +Multicast datagrams with TTL greater than 1 may be forwarded +to other networks if a multicast router is attached to the local network. +.Pp +For hosts with multiple interfaces, each multicast transmission is +sent from the primary network interface. +The +.Dv IP_MULTICAST_IF +option overrides the default for +subsequent transmissions from a given socket: +.Bd -literal -offset indent +struct in_addr addr; +setsockopt(s, IPPROTO_IP, IP_MULTICAST_IF, &addr, sizeof(addr)); +.Ed +.Pp +where +.Va addr +is the local +.Tn IP +address of the desired interface or +.Dv INADDR_ANY +to specify the default interface. +An interface's local IP address and multicast capability can +be obtained via the +.Dv SIOCGIFCONF +and +.Dv SIOCGIFFLAGS +.Xr ioctl 2 Ns 's . +Normal applications should not need to use this option. +.Pp +If a multicast datagram is sent to a group to which the sending host itself +belongs (on the outgoing interface), a copy of the datagram is, by default, +looped back by the IP layer for local delivery. +The +.Dv IP_MULTICAST_LOOP +option gives the sender explicit control +over whether or not subsequent datagrams are looped back: +.Bd -literal -offset indent +u_char loop; /* 0 = disable, 1 = enable (default) */ +setsockopt(s, IPPROTO_IP, IP_MULTICAST_LOOP, &loop, sizeof(loop)); +.Ed +.Pp +This option +improves performance for applications that may have no more than one +instance on a single host (such as a router daemon), by eliminating +the overhead of receiving their own transmissions. +It should generally not +be used by applications for which there may be more than one instance on a +single host (such as a conferencing program) or for which the sender does +not belong to the destination group (such as a time querying program). +.Pp +A multicast datagram sent with an initial TTL greater than 1 may be delivered +to the sending host on a different interface from that on which it was sent, +if the host belongs to the destination group on that other interface. +The loopback control option has no effect on such delivery. +.Pp +A host must become a member of a multicast group before it can receive +datagrams sent to the group. +To join a multicast group, use the +.Dv IP_ADD_MEMBERSHIP +option: +.Bd -literal -offset indent +struct ip_mreq mreq; +setsockopt(s, IPPROTO_IP, IP_ADD_MEMBERSHIP, &mreq, sizeof(mreq)); +.Ed +.Pp +where +.Fa mreq +is either of the following structures: +.Bd -literal -offset indent +struct ip_mreq { + struct in_addr imr_multiaddr; /* multicast group to join */ + struct in_addr imr_interface; /* interface to join on */ +} + +struct ip_mreqn { + struct in_addr imr_multiaddr; /* multicast group to join */ + struct in_addr imr_address; /* local IP address of interface */ + int imr_ifindex; /* interface index to join */ +}; +.Ed +.Pp +.Va imr_interface +should +be +.Dv INADDR_ANY +to choose the default multicast interface, +or the +.Tn IP +address of a particular multicast-capable interface if +the host is multihomed. +The +.Va imr_ifindex +element of +.Va struct ip_mreqn +can be set to the interface index instead of specifying the +.Tn IP +address of a particular multicast-capable interface. +Membership is associated with a single interface; +programs running on multihomed hosts may need to +join the same group on more than one interface. +Up to +.Dv IP_MAX_MEMBERSHIPS +(currently 4095) memberships may be added on a +single socket. +.Pp +To drop a membership, use: +.Bd -literal -offset indent +struct ip_mreq mreq; +setsockopt(s, IPPROTO_IP, IP_DROP_MEMBERSHIP, &mreq, sizeof(mreq)); +.Ed +.Pp +where +.Fa mreq +contains the same values as used to add the membership. +Memberships are dropped when the socket is closed or the process exits. +.\"----------------------- +.Ss "Raw IP Sockets" +Raw +.Tn IP +sockets are connectionless, +and are normally used with the +.Xr sendto 2 +and +.Xr recvfrom 2 +calls, though the +.Xr connect 2 +call may also be used to fix the destination for future +packets (in which case the +.Xr read 2 +or +.Xr recv 2 +and +.Xr write 2 +or +.Xr send 2 +system calls may be used). +.Pp +If +.Fa proto +is 0, the default protocol +.Dv IPPROTO_RAW +is used for outgoing +packets, and only incoming packets destined for that protocol +are received. +If +.Fa proto +is non-zero, that protocol number will be used on outgoing packets +and to filter incoming packets. +.Pp +Outgoing packets automatically have an +.Tn IP +header prepended to +them (based on the destination address and the protocol +number the socket is created with), +unless the +.Dv IP_HDRINCL +option has been set. +Incoming packets are received with +.Tn IP +header and options intact. +.Pp +.Dv IP_HDRINCL +indicates the complete IP header is included with the data +and may be used only with the +.Dv SOCK_RAW +type. +.Bd -literal -offset indent +#include + +int hincl = 1; /* 1 = on, 0 = off */ +setsockopt(s, IPPROTO_IP, IP_HDRINCL, &hincl, sizeof(hincl)); +.Ed +.Pp +Unlike previous +.Bx +releases, the program must set all +the fields of the IP header, including the following: +.Bd -literal -offset indent +ip->ip_v = IPVERSION; +ip->ip_hl = hlen >> 2; +ip->ip_id = 0; /* 0 means kernel set appropriate value */ +ip->ip_off = htons(offset); +ip->ip_len = htons(len); +.Ed +.Pp +Additionally note that starting with +.Ox 2.1 , +the +.Va ip_off +and +.Va ip_len +fields are in network byte order. +If the header source address is set to +.Dv INADDR_ANY , +the kernel will choose an appropriate address. +.Sh DIAGNOSTICS +A socket operation may fail with one of the following errors returned: +.Bl -tag -width [EADDRNOTAVAIL] +.It Bq Er EISCONN +when trying to establish a connection on a socket which +already has one, or when trying to send a datagram with the destination +address specified and the socket is already connected; +.It Bq Er ENOTCONN +when trying to send a datagram, but +no destination address is specified, and the socket hasn't been +connected; +.It Bq Er ENOBUFS +when the system runs out of memory for +an internal data structure; +.It Bq Er EADDRNOTAVAIL +when an attempt is made to create a +socket with a network address for which no network interface +exists. +.It Bq Er EACCES +when an attempt is made to create +a raw IP socket by a non-privileged process. +.El +.Pp +The following errors specific to +.Tn IP +may occur when setting or getting +.Tn IP +options: +.Bl -tag -width EADDRNOTAVAILxx +.It Bq Er EINVAL +An unknown socket option name was given. +.It Bq Er EINVAL +The IP option field was improperly formed; +an option field was shorter than the minimum value +or longer than the option buffer provided. +.El +.Sh SEE ALSO +.Xr getsockopt 2 , +.Xr ioctl 2 , +.Xr recv 2 , +.Xr send 2 , +.Xr icmp 4 , +.Xr inet 4 , +.Xr netintro 4 +.Sh HISTORY +The +.Nm +protocol appeared in +.Bx 4.2 . diff --git a/static/openbsd/man4/ip6.4 b/static/openbsd/man4/ip6.4 new file mode 100644 index 00000000..8acb7a76 --- /dev/null +++ b/static/openbsd/man4/ip6.4 @@ -0,0 +1,659 @@ +.\" $OpenBSD: ip6.4,v 1.40 2016/06/28 17:32:58 jca Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.Dd $Mdocdate: June 28 2016 $ +.Dt IP6 4 +.Os +.Sh NAME +.Nm ip6 +.Nd Internet Protocol version 6 (IPv6) network layer +.Sh SYNOPSIS +.In sys/types.h +.In sys/socket.h +.In netinet/in.h +.Ft int +.Fn socket AF_INET6 SOCK_RAW proto +.Sh DESCRIPTION +The IPv6 network layer is used by the IPv6 protocol family for +transporting data. +IPv6 packets contain an IPv6 header that is not provided as part of the +payload contents when passed to an application. +IPv6 header options affect the behavior of this protocol and may be used +by high-level protocols (such as the +.Xr tcp 4 +and +.Xr udp 4 +protocols) as well as directly by +.Dq raw sockets , +which process IPv6 messages at a lower-level and may be useful for +developing new protocols and special-purpose applications. +.Ss Header +All IPv6 packets begin with an IPv6 header. +When data received by the kernel are passed to the application, this +header is not included in buffer, even when raw sockets are being used. +Likewise, when data are sent to the kernel for transmit from the +application, the buffer is not examined for an IPv6 header: +the kernel always constructs the header. +To directly access IPv6 headers from received packets and specify them +as part of the buffer passed to the kernel, link-level access +.Po +.Xr bpf 4 , +for example +.Pc +must instead be utilized. +.Pp +The header has the following definition: +.Bd -literal -offset indent +struct ip6_hdr { + union { + struct ip6_hdrctl { + u_int32_t ip6_un1_flow; /* 20 bits of flow ID */ + u_int16_t ip6_un1_plen; /* payload length */ + u_int8_t ip6_un1_nxt; /* next header */ + u_int8_t ip6_un1_hlim; /* hop limit */ + } ip6_un1; + u_int8_t ip6_un2_vfc; /* version and class */ + } ip6_ctlun; + struct in6_addr ip6_src; /* source address */ + struct in6_addr ip6_dst; /* destination address */ +} __packed; + +#define ip6_vfc ip6_ctlun.ip6_un2_vfc +#define ip6_flow ip6_ctlun.ip6_un1.ip6_un1_flow +#define ip6_plen ip6_ctlun.ip6_un1.ip6_un1_plen +#define ip6_nxt ip6_ctlun.ip6_un1.ip6_un1_nxt +#define ip6_hlim ip6_ctlun.ip6_un1.ip6_un1_hlim +#define ip6_hops ip6_ctlun.ip6_un1.ip6_un1_hlim +.Ed +.Pp +All fields are in network-byte order. +Any options specified (see +.Sx Options +below) must also be specified in network-byte order. +.Pp +.Va ip6_flow +specifies the flow ID. +.Va ip6_plen +specifies the payload length. +.Va ip6_nxt +specifies the type of the next header. +.Va ip6_hlim +specifies the hop limit. +.Pp +The top 4 bits of +.Va ip6_vfc +specify the class and the bottom 4 bits specify the version. +.Pp +.Va ip6_src +and +.Va ip6_dst +specify the source and destination addresses. +.Pp +The IPv6 header may be followed by any number of extension headers that start +with the following generic definition: +.Bd -literal -offset indent +struct ip6_ext { + u_int8_t ip6e_nxt; + u_int8_t ip6e_len; +} __packed; +.Ed +.Ss Options +IPv6 allows header options on packets to manipulate the behavior of the +protocol. +These options and other control requests are accessed with the +.Xr getsockopt 2 +and +.Xr setsockopt 2 +system calls at level +.Dv IPPROTO_IPV6 +and by using ancillary data in +.Xr recvmsg 2 +and +.Xr sendmsg 2 . +They can be used to access most of the fields in the IPv6 header and +extension headers. +.Pp +The following socket options are supported: +.Bl -tag -width Ds +.It Dv IPV6_UNICAST_HOPS Fa "int *" +Get or set the default hop limit header field for outgoing unicast +datagrams sent on this socket. +A value of \-1 resets to the default value. +.It Dv IPV6_MINHOPCOUNT Fa "int *" +Get or set the minimum hop limit header field for incoming +packets received on TCP and UDP sockets. +This can be used to implement the +.Em Generalized TTL Security Mechanism (GTSM) +according to RFC 5082. +.It Dv IPV6_MULTICAST_IF Fa "u_int *" +Get or set the interface from which multicast packets will be sent. +For hosts with multiple interfaces, each multicast transmission is sent +from the primary network interface. +The interface is specified as its index as provided by +.Xr if_nametoindex 3 . +A value of zero specifies the default interface. +.It Dv IPV6_MULTICAST_HOPS Fa "int *" +Get or set the default hop limit header field for outgoing multicast +datagrams sent on this socket. +This option controls the scope of multicast datagram transmissions. +.Pp +Datagrams with a hop limit of 1 are not forwarded beyond the local +network. +Multicast datagrams with a hop limit of zero will not be transmitted on +any network but may be delivered locally if the sending host belongs to +the destination group and if multicast loopback (see below) has not been +disabled on the sending socket. +Multicast datagrams with a hop limit greater than 1 may be forwarded to +the other networks if a multicast router (such as +.Xr mrouted 8 ) +is attached to the local network. +.It Dv IPV6_MULTICAST_LOOP Fa "u_int *" +Get or set the status of whether multicast datagrams will be looped back +for local delivery when a multicast datagram is sent to a group to which +the sending host belongs. +.Pp +This option improves performance for applications that may have no more +than one instance on a single host (such as a router daemon) by +eliminating the overhead of receiving their own transmissions. +It should generally not be used by applications for which there may be +more than one instance on a single host (such as a conferencing program) +or for which the sender does not belong to the destination group +(such as a time-querying program). +.Pp +A multicast datagram sent with an initial hop limit greater than 1 may +be delivered to the sending host on a different interface from that on +which it was sent if the host belongs to the destination group on that +other interface. +The multicast loopback control option has no effect on such delivery. +.It Dv IPV6_JOIN_GROUP Fa "struct ipv6_mreq *" +Join a multicast group. +A host must become a member of a multicast group before it can receive +datagrams sent to the group. +.Bd -literal +struct ipv6_mreq { + struct in6_addr ipv6mr_multiaddr; + unsigned int ipv6mr_interface; +}; +.Ed +.Pp +.Va ipv6mr_interface +may be set to zeroes to choose the default multicast interface or to the +index of a particular multicast-capable interface if the host is +multihomed. +Membership is associated with a single interface; programs running on +multihomed hosts may need to join the same group on more than one +interface. +.Pp +If the multicast address is unspecified (i.e., all zeroes), messages +from all multicast addresses will be accepted by this group. +Note that setting to this value requires superuser privileges. +.It Dv IPV6_LEAVE_GROUP Fa "struct ipv6_mreq *" +Drop membership from the associated multicast group. +Memberships are automatically dropped when the socket is closed or when +the process exits. +.It Dv IPV6_PORTRANGE Fa "int *" +Get or set the allocation policy of ephemeral ports for when the kernel +automatically binds a local address to this socket. +The following values are available: +.Pp +.Bl -tag -width IPV6_PORTRANGE_DEFAULT -compact +.It Dv IPV6_PORTRANGE_DEFAULT +Use the regular range of non-reserved ports (varies, see +.Xr sysctl 8 ) . +.It Dv IPV6_PORTRANGE_HIGH +Use a high range (varies, see +.Xr sysctl 8 ) . +.It Dv IPV6_PORTRANGE_LOW +Use a low, reserved range (600\-1023). +.El +.It Dv IPV6_RECVPKTINFO Fa "int *" +Get or set whether additional information about subsequent packets will +be provided as ancillary data along with the payload in subsequent +.Xr recvmsg 2 +calls. +The information is stored in the following structure in the ancillary +data returned: +.Bd -literal +struct in6_pktinfo { + struct in6_addr ipi6_addr; /* src/dst IPv6 address */ + unsigned int ipi6_ifindex; /* send/recv if index */ +}; +.Ed +.Pp +Turning this option on will result in this socket getting cmsg data of +type IPV6_PKTINFO. +.It Dv IPV6_RECVHOPLIMIT Fa "int *" +Get or set whether the hop limit header field from subsequent packets +will be provided as ancillary data along with the payload in subsequent +.Xr recvmsg 2 +calls. +The value is stored as an +.Vt int +in the ancillary data returned. +Turning this option on will result in this socket getting cmsg data of +type IPV6_HOPLIMIT. +.It Dv IPV6_RECVHOPOPTS Fa "int *" +Get or set whether the hop-by-hop options from subsequent packets will be +provided as ancillary data along with the payload in subsequent +.Xr recvmsg 2 +calls. +The option is stored in the following structure in the ancillary data +returned: +.Bd -literal +struct ip6_hbh { + u_int8_t ip6h_nxt; /* next header */ + u_int8_t ip6h_len; /* length in units of 8 octets */ +/* followed by options */ +} __packed; +.Ed +.Pp +The +.Fn inet6_opt_init +routine and family of routines may be used to manipulate this data. +.Pp +This option requires superuser privileges. +Turning this option on will result in this socket getting cmsg data of +type IPV6_HOPOPTS. +.It Dv IPV6_RECVDSTOPTS Fa "int *" +Get or set whether the destination options from subsequent packets will +be provided as ancillary data along with the payload in subsequent +.Xr recvmsg 2 +calls. +The option is stored in the following structure in the ancillary data +returned: +.Bd -literal +struct ip6_dest { + u_int8_t ip6d_nxt; /* next header */ + u_int8_t ip6d_len; /* length in units of 8 octets */ +/* followed by options */ +} __packed; +.Ed +.Pp +The +.Fn inet6_opt_init +routine and family of routines may be used to manipulate this data. +.Pp +This option requires superuser privileges. +Turning this option on will result in this socket getting cmsg data of +type IPV6_DSTOPTS. +.It Dv IPV6_TCLASS Fa "int *" +Get or set the value of the traffic class field used for outgoing datagrams +on this socket. +The value must be between \-1 and 255. +A value of \-1 resets to the default value. +.It Dv IPV6_RECVTCLASS Fa "int *" +Get or set the status of whether the traffic class header field will be +provided as ancillary data along with the payload in subsequent +.Xr recvmsg 2 +calls. +The header field is stored as a single value of type +.Vt int . +.It Dv IPV6_RECVRTHDR Fa "int *" +Get or set whether the routing header from subsequent packets will be +provided as ancillary data along with the payload in subsequent +.Xr recvmsg 2 +calls. +The header is stored in the following structure in the ancillary data +returned: +.Bd -literal +struct ip6_rthdr { + u_int8_t ip6r_nxt; /* next header */ + u_int8_t ip6r_len; /* length in units of 8 octets */ + u_int8_t ip6r_type; /* routing type */ + u_int8_t ip6r_segleft; /* segments left */ +/* followed by routing-type-specific data */ +} __packed; +.Ed +.Pp +The +.Fn inet6_rth_space +routine and family of routines may be used to manipulate this data. +.Pp +This option requires superuser privileges. +Turning this option on will result in this socket getting cmsg data of +type IPV6_RTHDR. +.It Dv IPV6_CHECKSUM Fa "int *" +Get or set the byte offset into a packet where the 16-bit checksum is +located. +When set, this byte offset is where incoming packets will be expected +to have checksums of their data stored and where outgoing packets will +have checksums of their data computed and stored by the kernel. +A value of \-1 specifies that no checksums will be checked on incoming +packets and that no checksums will be computed or stored on outgoing +packets. +The offset of the checksum for ICMPv6 sockets cannot be relocated or +turned off. +.It Dv IPV6_V6ONLY Fa "int *" +Get or set whether only IPv6 connections can be made to this socket. +For wildcard sockets, this can restrict connections to IPv6 only. +With +.Ox +IPv6 sockets are always IPv6-only, so the socket option is read-only +(not modifiable). +.It Dv IPV6_USE_MIN_MTU Fa "int *" +Get or set whether the minimal IPv6 maximum transmission unit (MTU) size +will be used to avoid fragmentation from occurring for subsequent +outgoing datagrams. +.It Dv IPV6_AUTH_LEVEL Fa "int *" +Get or set the +.Xr ipsec 4 +authentication level. +.It Dv IPV6_ESP_TRANS_LEVEL Fa "int *" +Get or set the ESP transport level. +.It Dv IPV6_ESP_NETWORK_LEVEL Fa "int *" +Get or set the ESP encapsulation level. +.It Dv IPV6_IPCOMP_LEVEL Fa "int *" +Get or set the +.Xr ipcomp 4 +level. +.It Dv IPV6_RECVDSTPORT Fa "int *" +Get or set the status of whether the destination port for a UDP datagram +will be provided as ancillary data along with the payload in subsequent +.Xr recvmsg 2 +calls. +The information is stored as a single value of type +.Vt u_int16_t +in network byte order. +.Pp +Turning this option on will result in this socket getting cmsg data of +type IPV6_RECVDSTPORT. +.El +.Pp +The +.Dv IPV6_RECVPKTINFO , +.Dv IPV6_RECVHOPLIMIT , +.Dv IPV6_RECVHOPOPTS , +.Dv IPV6_RECVDSTOPTS , +and +.Dv IPV6_RTHDR +options will return ancillary data along with payload contents in subsequent +.Xr recvmsg 2 +calls with +.Va cmsg_level +set to +.Dv IPPROTO_IPV6 +and +.Va cmsg_type +set to respective option name value (e.g., +.Dv IPV6_HOPLIMIT ) . +These options may also be used directly as ancillary +.Va cmsg_type +values in +.Xr sendmsg 2 +to set options on the packet being transmitted by the call. +The +.Va cmsg_level +value must be +.Dv IPPROTO_IPV6 . +For these options, the ancillary data object value format is the same +as the value returned as explained for each when received with +.Xr recvmsg 2 . +.Pp +Note that using +.Xr sendmsg 2 +to specify options on particular packets works only on UDP and raw sockets. +To manipulate header options for packets on TCP sockets, only the socket +options may be used. +.Pp +In some cases, there are multiple APIs defined for manipulating an IPv6 +header field. +A good example is the outgoing interface for multicast datagrams, which +can be set by the +.Dv IPV6_MULTICAST_IF +socket option, through the +.Dv IPV6_RECVPKTINFO +option, and through the +.Va sin6_scope_id +field of the socket address passed to the +.Xr sendto 2 +system call. +.Pp +Resolving these conflicts is implementation dependent. +This implementation determines the value in the following way: +options specified by using ancillary data (i.e., +.Xr sendmsg 2 ) +are considered first, +options specified by using the individual, basic, and direct socket +options (e.g., +.Dv IPV6_UNICAST_HOPS ) +are considered second, +and options specified in the socket address supplied to +.Xr sendto 2 +are the last choice. +.Ss Multicasting +IPv6 multicasting is supported only on +.Dv AF_INET6 +sockets of type +.Dv SOCK_DGRAM +and +.Dv SOCK_RAW , +and only on networks where the interface driver supports +multicasting. +Socket options (see above) that manipulate membership of +multicast groups and other multicast options include +.Dv IPV6_MULTICAST_IF , +.Dv IPV6_MULTICAST_HOPS , +.Dv IPV6_MULTICAST_LOOP , +.Dv IPV6_LEAVE_GROUP , +and +.Dv IPV6_JOIN_GROUP . +.Ss Raw Sockets +Raw IPv6 sockets are connectionless and are normally used with the +.Xr sendto 2 +and +.Xr recvfrom 2 +calls, although the +.Xr connect 2 +call may be used to fix the destination address for future outgoing +packets so that +.Xr send 2 +may instead be used and the +.Xr bind 2 +call may be used to fix the source address for future outgoing +packets instead of having the kernel choose a source address. +.Pp +By using +.Xr connect 2 +or +.Xr bind 2 , +raw socket input is constrained to only packets with their +source address matching the socket destination address if +.Xr connect 2 +was used and to packets with their destination address +matching the socket source address if +.Xr bind 2 +was used. +.Pp +If the +.Ar proto +argument to +.Xr socket 2 +is zero, the default protocol +.Pq Dv IPPROTO_RAW +is used for outgoing packets. +For incoming packets, protocols recognized by kernel are +.Sy not +passed to the application socket (e.g., +.Xr tcp 4 +and +.Xr udp 4 ) +except for some ICMPv6 messages. +The ICMPv6 messages not passed to raw sockets include echo, timestamp, +and address mask requests. +If +.Ar proto +is non-zero, only packets with this protocol will be passed to the +socket. +.Pp +IPv6 fragments are also not passed to application sockets until +they have been reassembled. +If reception of all packets is desired, link-level access (such as +.Xr bpf 4 ) +must be used instead. +.Pp +Outgoing packets automatically have an IPv6 header prepended to them +(based on the destination address and the protocol number the socket +was created with). +Incoming packets are received by an application without the IPv6 header +or any extension headers. +.Pp +Outgoing packets will be fragmented automatically by the kernel if they +are too large. +Incoming packets will be reassembled before being sent to the raw socket, +so packet fragments or fragment headers will never be seen on a raw socket. +.Sh EXAMPLES +The following determines the hop limit on the next packet received: +.Bd -literal +struct iovec iov[2]; +u_char buf[BUFSIZ]; +struct cmsghdr *cm; +struct msghdr m; +int found, optval; +u_char data[2048]; + +/* Create socket. */ + +(void)memset(&m, 0, sizeof(m)); +(void)memset(&iov, 0, sizeof(iov)); + +iov[0].iov_base = data; /* buffer for packet payload */ +iov[0].iov_len = sizeof(data); /* expected packet length */ + +m.msg_name = &from; /* sockaddr_in6 of peer */ +m.msg_namelen = sizeof(from); +m.msg_iov = iov; +m.msg_iovlen = 1; +m.msg_control = (caddr_t)buf; /* buffer for control messages */ +m.msg_controllen = sizeof(buf); + +/* + * Enable the hop limit value from received packets to be + * returned along with the payload. + */ +optval = 1; +if (setsockopt(s, IPPROTO_IPV6, IPV6_RECVHOPLIMIT, &optval, + sizeof(optval)) == -1) + err(1, "setsockopt"); + +found = 0; +while (!found) { + if (recvmsg(s, &m, 0) == -1) + err(1, "recvmsg"); + for (cm = CMSG_FIRSTHDR(&m); cm != NULL; + cm = CMSG_NXTHDR(&m, cm)) { + if (cm->cmsg_level == IPPROTO_IPV6 && + cm->cmsg_type == IPV6_HOPLIMIT && + cm->cmsg_len == CMSG_LEN(sizeof(int))) { + found = 1; + (void)printf("hop limit: %d\en", + *(int *)CMSG_DATA(cm)); + break; + } + } +} +.Ed +.Sh DIAGNOSTICS +A socket operation may fail with one of the following errors returned: +.Bl -tag -width EADDRNOTAVAILxx +.It Bq Er EISCONN +when trying to establish a connection on a socket which +already has one or when trying to send a datagram with the destination +address specified and the socket is already connected. +.It Bq Er ENOTCONN +when trying to send a datagram, but +no destination address is specified, and the socket hasn't been +connected. +.It Bq Er ENOBUFS +when the system runs out of memory for +an internal data structure. +.It Bq Er EADDRNOTAVAIL +when an attempt is made to create a +socket with a network address for which no network interface +exists. +.It Bq Er EACCES +when an attempt is made to create +a raw IPv6 socket by a non-privileged process. +.El +.Pp +The following errors specific to IPv6 may occur when setting or getting +header options: +.Bl -tag -width EADDRNOTAVAILxx +.It Bq Er EINVAL +An unknown socket option name was given. +.It Bq Er EINVAL +An ancillary data object was improperly formed. +.El +.Sh SEE ALSO +.Xr getsockopt 2 , +.Xr recv 2 , +.Xr send 2 , +.Xr setsockopt 2 , +.Xr socket 2 , +.\" .Xr inet6_opt_init 3 , +.\" .Xr inet6_rth_space 3 , +.Xr if_nametoindex 3 , +.Xr bpf 4 , +.Xr icmp6 4 , +.Xr inet6 4 , +.Xr netintro 4 , +.Xr tcp 4 , +.Xr udp 4 +.Sh STANDARDS +.Rs +.%A S. Deering +.%A R. Hinden +.%D December 1998 +.%R RFC 2460 +.%T Internet Protocol, Version 6 (IPv6) Specification +.Re +.Pp +.Rs +.%A R. Gilligan +.%A S. Thomson +.%A J. Bound +.%A J. McCann +.%A W. Stevens +.%D February 2003 +.%R RFC 3493 +.%T Basic Socket Interface Extensions for IPv6 +.Re +.Pp +.Rs +.%A W. Stevens +.%A M. Thomas +.%A E. Nordmark +.%A T. Jinmei +.%D May 2003 +.%R RFC 3542 +.%T Advanced Sockets Application Program Interface (API) for IPv6 +.Re +.Pp +The +.Dv IPV6_PORTRANGE +socket option and the conflict resolution rule are not defined in the +RFCs and should be considered implementation dependent. diff --git a/static/openbsd/man4/ipcomp.4 b/static/openbsd/man4/ipcomp.4 new file mode 100644 index 00000000..acd6f709 --- /dev/null +++ b/static/openbsd/man4/ipcomp.4 @@ -0,0 +1,124 @@ +.\" $OpenBSD: ipcomp.4,v 1.17 2022/12/23 07:16:55 jmc Exp $ +.\" +.\" Copyright (c) 2001 Jean-Jacques Bernard-Gundol +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 23 2022 $ +.Dt IPCOMP 4 +.Os +.Sh NAME +.Nm ipcomp +.Nd IP Payload Compression Protocol +.Sh DESCRIPTION +IPComp is enabled with the following +.Xr sysctl 2 +variable in +.Pa /etc/sysctl.conf : +.Bl -tag -width xxxxxxxxxxxxxxxxxxxxx -offset indent +.It net.inet.ipcomp.enable +.El +.Pp +IPComp is a protocol used to reduce the size of IP datagrams. +It can be used to enhance the communication performance between a pair +of hosts/gateways, especially on slow links, by compressing the +datagrams, provided the communicating entities have enough computational +power. +.Pp +This protocol is especially useful when encryption or authentication +is applied to IP datagrams using the IPsec protocol (see +.Xr ipsec 4 +for more information about IPsec). +Encrypting information is increasing its entropy to a point where +compression to a lower layer becomes completely useless (e.g., the +PPP Compression Control Protocol). +IPcomp is applied at the network layer before other encryption +operations are applied (except encryption protocols applied at a +higher layer such as +.Xr ssh 1 +or +.Xr ssl 8 ) . +.Pp +Just like for the other IPsec protocols, IPComp needs some parameters +for each connection, specifying how the compression should be done +between the entities. +The parameters are collected in a structure called an +IPComp Association (IPCA). +The parameters stored in an IPCA are the destination address and the +Compression Parameter Index (CPI). +An IPCA is the pendant of the SA (Security Association) for IPsec. +.Pp +Currently, IPCA can be created using the +.Xr ipsecctl 8 +tool. +Using +.Xr ipsecctl 8 +it is also possible to create IPComp flows and SA/IPCA +bundles. +Such a bundle is used to create a combination of IPsec and IPComp +flows (thus enabling compression in an IPsec protocol). +.Pp +The compression is done on the data following the IP header and an +IPComp header is inserted between the compressed data and the IP +header. +In the case of IPv6, there are extension headers which cannot be +compressed since they are modified by the router along the way to the +destination. +These extension headers are hop-by-hop, routing, and fragmentation. +.Pp +When doing compression, it is possible that the uncompressed data is +smaller in size than the compressed data. +To avoid this behaviour, a non expansion policy is used in IPComp. +If the data payload is smaller than a given threshold, it will not be +compressed. +No IPComp header will be inserted. +.Pp +IPComp uses the same policy framework as IPsec. +However unlike IPsec, only one policy is available for IPComp: +.Bl -tag -width IPSEC_LEVEL_USE +.It IPSEC_LEVEL_USE +Use IPComp for sending packets but still accept packets which are not +compressed. +.El +.Sh DIAGNOSTICS +.Xr netstat 1 +can be used to obtain some statistics about IPComp usage: +.Pp +.Dl $ netstat -s -p ipcomp +.Sh SEE ALSO +.Xr enc 4 , +.Xr inet 4 , +.Xr ip 4 , +.Xr ipsec 4 , +.Xr netintro 4 , +.Xr ipsecctl 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +protocol first appeared in +.Ox 3.0 . +.Sh AUTHORS +Support for the +.Nm +protocol was written by +.An Jean-Jacques Bernard-Gundol Aq Mt jj@wabbitt.org . diff --git a/static/openbsd/man4/ipgphy.4 b/static/openbsd/man4/ipgphy.4 new file mode 100644 index 00000000..49de4d26 --- /dev/null +++ b/static/openbsd/man4/ipgphy.4 @@ -0,0 +1,34 @@ +.\" $OpenBSD: ipgphy.4,v 1.6 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2006 Brad Smith +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt IPGPHY 4 +.Os +.Sh NAME +.Nm ipgphy +.Nd IC Plus IP1000A/IP1001 10/100/1Gb Ethernet PHY +.Sh SYNOPSIS +.Cd "ipgphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the IC Plus IP1000A/IP1001 10/100/1Gb Ethernet PHY +interface. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/ipmi.4 b/static/openbsd/man4/ipmi.4 new file mode 100644 index 00000000..4e71bac5 --- /dev/null +++ b/static/openbsd/man4/ipmi.4 @@ -0,0 +1,180 @@ +.\" $OpenBSD: ipmi.4,v 1.15 2020/03/29 11:24:53 kettenis Exp $ +.\" +.\" Copyright (c) 2005 Marco Peereboom +.\" Text was heavily borrowed from the IPMI spec V1.5 +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: March 29 2020 $ +.Dt IPMI 4 +.Os +.Sh NAME +.Nm ipmi +.Nd Intelligent Platform Management Interface driver +.Sh SYNOPSIS +.Cd "ipmi0 at mainbus0" +.Cd "ipmi0 at acpi?" +.Cd "ipmi0 at iic?" +.Cd "ipmi0 at fdt?" +.Sh DESCRIPTION +The +.Nm +term Intelligent Platform Management refers to autonomous monitoring and +recovery features implemented directly in platform management hardware and +firmware. +The key characteristics of Intelligent Platform Management is that +inventory, monitoring, logging, and recovery control functions are available +independent of the main processor, BIOS, and operating system. +.Pp +Platform status information can be obtained and recovery actions initiated +under situations where vendor "in-band" management mechanisms are unavailable. +The independent monitoring, logging, and access functions available through IPMI +provide a level of manageability built in to the platform hardware. +This can support systems where there is no systems management software +available for a particular operating system. +.Pp +At the heart of the IPMI architecture is a microcontroller called +the Baseboard Management Controller (BMC). +The BMC provides the intelligence behind Intelligent Platform Management. +The BMC manages the interface between system management software +and the platform management hardware, provides autonomous monitoring, +event logging, and recovery control and serves as the gateway +between systems management software and hardware. +.Sh IPMI MESSAGING +IPMI uses message-based interfaces for the different interfaces to the platform +management subsystems. +All IPMI messages share the same fields in the message "payload", +regardless of the interface (transport) that they're transferred over. +IPMI messaging uses a request/response protocol. +IPMI request messages are commonly referred to as commands. +The use of request/response protocol facilitates the transfer of +IPMI messages over different transports. +IPMI commands are grouped into functional command sets +using a field called network function code. +There are command sets for sensor and event related commands, +chassis commands etc. +This functional grouping makes it easier to organize and manage +the assignment and allocation of command values. +.Sh SENSOR MODEL +Access to monitored information such as temperatures, voltages, fan status +etc., is provided via the IPMI Sensor Model. +Instead of providing direct access to the monitoring hardware, +IPMI provides access by abstracted sensor commands +such as the "Get Sensor Reading" command, +implemented via a management controller. +This approach isolates the software from changes in the +platform management hardware implementation. +.Pp +Sensors are classified according to the type of readings they provide +and/or the type of events they generate. +A sensor can return either an analog or discrete reading. +Sensor events can be discrete or threshold-based. +.Sh SYSTEM EVENT LOG AND EVENT MESSAGES +The BMC provides a centralized non-volatile System Event Log, or SEL. +Having the SEL and logging functions managed by the BMC +helps ensure that post-mortem logging information is available +should a failure occur that disables the systems processor(s). +.Pp +A set of IPMI commands allows the SEL to be read and cleared +and for events to be added to the SEL. +The common request message (command) +used for adding events to the SEL is referred to as an Event Message. +.Sh SENSOR DATA RECORDS & CAPABILITIES COMMANDS +IPMI's extensibility and scalability mean that +each platform implementation can have +a different population of management controllers and sensors and +different event generation capabilities. +The design of IPMI allows system +management software to retrieve information from the platform +and automatically configure itself to the platform's capabilities. +.Pp +Information that describes the platform management capabilities +is provided via two mechanisms: +Capabilities Commands and Sensor Data Records (SDRs). +Capabilities commands are commands within the IPMI command sets that return +fields that provide information on other commands and functions the controller +can handle. +.Sh SYSTEMS INTERFACES +IPMI defines three standardized systems interfaces that systems software uses +for transferring IPMI messages to the BMC. +In order to support a variety of microcontrollers, +IPMI offers a choice of systems interfaces. +The system interfaces are similar enough so that +a single driver can handle all IPMI system interfaces. +.Bl -tag -width Ds +.It Keyboard Controller Style (KCS) +The bit definitions and operation of the registers follows that used in the +Intel 8742 Universal Peripheral Interface microcontroller. +The term "Keyboard Controller Style" reflects the fact that +the 8742 interface was used as the legacy keyboard controller interface +in PC architecture computer systems. +This interface is available built in to several commercially available +microcontrollers. +Data is transferred across the KCS interface using a per-byte handshake. +.It System Management Interface Chip (SMIC) +The SMIC interface provides an alternative +when the implementer wishes to use a microcontroller for the BMC +that does not have the built-in hardware for a KCS interface. +This interface is a three I/O port interface that can be +implemented using a simple ASIC, FPGA, or discrete logic devices. +It may also be built in to a custom-designed management controller. +Like the KCS interface, +a per-byte handshake is also used +for transferring data across the SMIC interface. +.It Block Transfer (BT) +This interface provides a higher performance system interface option. +Unlike the KCS and SMIC interfaces, +a per-block handshake is used for transferring data across the interface. +The BT interface also provides an alternative to using +a controller with a built-in KCS interface. +The BT interface has three I/O mapped ports. +A typical implementation includes hardware buffers for holding +upstream and downstream message blocks. +The BT interface can be implemented using an ASIC or FPGA +or may be built in to a custom-designed management controller. +.It SMBus System Interface (SSIF) +The SSIF interface provides access to the BMC over an SMBus interface. +.El +.Sh WATCHDOG +IPMI provides +.Xr watchdog 4 +timer functionality. +Once configured, if the watchdog is not reset within +a certain period of time, +it will timeout and the server will reset. +The reset will occur regardless of the recoverability of the hang or crash. +.Pp +Example of enabling a watchdog: +.Pp +.Dl # sysctl kern.watchdog.period=10 +.Pp +In this case if the watchdog is not reset, +it'll reboot the server after roughly 10 seconds. +.Pp +Example of disabling the watchdog: +.Pp +.Dl # sysctl kern.watchdog.period=0 +.Sh SEE ALSO +.Xr watchdog 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 +and conforms to the IPMI 1.5 specification. +.Sh AUTHORS +The +.Nm +driver was written by +.An Jordan Hargrave Aq Mt jordan@openbsd.org . diff --git a/static/openbsd/man4/ips.4 b/static/openbsd/man4/ips.4 new file mode 100644 index 00000000..2ad6c045 --- /dev/null +++ b/static/openbsd/man4/ips.4 @@ -0,0 +1,87 @@ +.\" $OpenBSD: ips.4,v 1.18 2022/02/19 23:45:51 jsg Exp $ +.\" +.\" Copyright (c) 2006, 2009 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 19 2022 $ +.Dt IPS 4 +.Os +.Sh NAME +.Nm ips +.Nd IBM SATA/SCSI ServeRAID controller +.Sh SYNOPSIS +.Cd "ips* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for IBM ServeRAID controllers, including: +.Pp +.Bl -bullet -width Ds -offset indent -compact +.It +ServeRAID 3H/3HB/3L +.It +ServeRAID 4H/4L/4Lx/4M/4Mx +.It +ServeRAID 5i/5i II +.It +ServeRAID 6i/6M +.It +ServeRAID 7k/7M/7t +.El +.Pp +Although the controllers are actual RAID controllers, +the driver makes them look just like SCSI controllers. +All RAID configuration is done through the bootable +IBM ServeRAID Support CD; +a CD image is freely available at the IBM website. +.Pp +RAID management is done through the +.Xr bio 4 +device with the +.Xr bioctl 8 +command. +Logical disk status is exposed under the +.Va hw.sensors +.Xr sysctl 8 +and can be monitored using +.Xr sensorsd 8 . +.Sh SEE ALSO +.Xr bio 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr bioctl 8 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Pp +.Lk https://www.ibm.com +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . +.Sh CAVEATS +Due to +.Xr bioctl 8 +limitations the +.Nm +driver associates all unused and hot spare drives with the first volume +but the drives can be used for rebuilding any degraded volume. diff --git a/static/openbsd/man4/ipsec.4 b/static/openbsd/man4/ipsec.4 new file mode 100644 index 00000000..f758e52d --- /dev/null +++ b/static/openbsd/man4/ipsec.4 @@ -0,0 +1,430 @@ +.\" $OpenBSD: ipsec.4,v 1.89 2022/12/23 07:16:55 jmc Exp $ +.\" +.\" Copyright 1997 Niels Provos +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Niels Provos. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" Manual page, using -mandoc macros +.\" +.Dd $Mdocdate: December 23 2022 $ +.Dt IPSEC 4 +.Os +.Sh NAME +.Nm ipsec +.Nd IP Security Protocol +.Sh DESCRIPTION +IPsec is a pair of protocols, +Encapsulating Security Payload (ESP) +and Authentication Header (AH), +which provide security services for IP datagrams. +.Pp +Both protocols may be enabled or disabled using the following +.Xr sysctl 2 +variables in +.Pa /etc/sysctl.conf . +By default, both protocols are enabled: +.Pp +.Bl -tag -width "net.inet.esp.enableXX" -offset indent -compact +.It net.inet.esp.enable +Enable the ESP IPsec protocol +.It net.inet.ah.enable +Enable the AH IPsec protocol +.El +.Pp +There are four main security properties provided by IPsec: +.Bl -inset -offset indent +.It Confidentiality +\- Ensure it is hard for anyone but the +receiver to understand what data has been communicated. +For example, ensuring the secrecy of passwords when logging +into a remote machine over the Internet. +.It Integrity +\- Guarantee that the data does not get changed +in transit. +If you are on a line carrying invoicing data, you +probably want to know that the amounts and account numbers +are correct and have not been modified by a third party. +.It Authenticity +\- Sign your data so that others can see that it +is really you that sent it. +It is clearly nice to know that documents are not forged. +.It Replay protection +\- We need ways to ensure a datagram is processed only once, regardless +of how many times it is received. +That is, it should not be possible for an attacker +to record a transaction (such as a bank account withdrawal), and then +by replaying it verbatim cause the peer to think a new message +(withdrawal request) had been received. +WARNING: as per the standard's specification, replay protection is not +performed when using manual-keyed IPsec (e.g. when using +.Xr ipsecctl 8 ) . +.El +.Ss IPsec Protocols +IPsec provides these services using two new protocols: +Authentication Header (AH), and +Encapsulating Security Payload (ESP). +.Pp +ESP can provide the properties authentication, integrity, replay protection, +and confidentiality of the data +(it secures everything in the packet that follows the IP header). +Replay protection requires authentication and +integrity (these two always go together). +Confidentiality (encryption) can be used with or without +authentication/integrity. +Similarly, one could use authentication/integrity with or without +confidentiality. +.Pp +AH provides authentication, integrity, and replay protection +(but not confidentiality). +The main difference between the authentication features of +AH and ESP is that AH also authenticates portions of the IP +header of the packet +(such as the source/destination addresses). +ESP authenticates only the packet payload. +.\".Pp +.\"A third protocol is available which is highly relevant to IPsec: IPComp. +.\"IPComp is a protocol used to reduce the size of IP datagrams +.\"(i.e. it provides compression). +.\"See +.\".Xr ipcomp 4 +.\"for further information. +.Ss Authentication Header (AH) +AH works by computing a value that depends on all of the payload +data, some of the IP header data, and a certain secret value +(the authentication key). +This value is then sent with the rest of each packet. +The receiver performs the same computation, and if the value matches, +it knows no one tampered with the data (integrity), the address information +(authenticity) or a sequence number (replay protection). +It knows this because the secret authentication key makes sure no +active attacker (man-in-the-middle) can recompute the correct value after +altering the packet. +The algorithms used to compute these values are called hash algorithms and are +parameters in the SA, just like the authentication key. +.Ss Encapsulating Security Payload (ESP) +ESP optionally does almost everything that AH does +except that it does not protect the outer IP +header but furthermore it encrypts the payload data with an encryption +algorithm using a secret encryption key. +Only the ones knowing this key can decrypt the data, thus providing +confidentiality. +Both the algorithm and the encryption key are parameters of the SA. +.Ss Security Associations (SAs) +These protocols require certain parameters for each connection, describing +exactly how the desired protection will be achieved. +These parameters are collected in an entity called a security association, +or SA for short. +Typical SA parameters include encryption algorithm, hash algorithm, +encryption key, and authentication key, to name a few. +When two peers have established matching SAs +(one at each end), +packets protected with one end's SA may be verified and/or decrypted +using the information in the other end's SA. +The only issue remaining is to ensure that both ends have matching SAs. +This may be done manually, or automatically using a key management daemon. +.Pp +Further information on manual SA establishment is described in +.Xr ipsec.conf 5 . +Information on automated key management for IKEv1 can be found in +.Xr isakmpd 8 +and for IKEv2 in +.Xr iked.conf 5 . +.Ss Security Parameter Indexes (SPIs) +In order to identify an SA, we need to have a unique name for it. +This name is a triplet, consisting of the destination address, security +parameter index (aka SPI) and the security protocol (ESP or AH). +Since the destination address is part of the name, an SA is necessarily a +unidirectional construct. +For a bidirectional communication channel, two SAs are required, one +outgoing and one incoming, where the destination address is our local +IP address. +The SPI is just a number that helps us make the name unique; +it can be arbitrarily chosen in the range 0x100 \- 0xffffffff. +The security protocol number should be 50 for ESP and 51 for AH, +as these are the protocol numbers assigned by IANA. +.Ss Modes of Operation +IPsec can operate in two modes, either tunnel or transport mode. +In transport mode the ordinary IP +header is used to deliver the packets to their endpoint; +in tunnel mode the ordinary IP +header just tells us the address of a security gateway +which knows how to verify/decrypt the payload and forward the +packet to a destination given by another IP +header contained in the protected payload. +Tunnel mode can be used for establishing virtual private networks (VPNs), +where parts of the networks can be spread out over an +unsafe public network, but security gateways at each subnet are responsible +for encrypting and decrypting the data passing over the public net. +An SA will contain information specifying +whether it is a tunnel or transport mode SA, +and for tunnels it will contain values to fill in into the outer IP header. +.Ss Lifetimes +The SA also holds a couple of other parameters, especially useful for +automatic keying, called lifetimes, which puts a limit on how much we can +use an SA for protecting our data. +These limits can be in wall-clock time or in volume of our data. +.Ss IPsec Examples +To better illustrate how IPsec works, consider a typical TCP packet: +.Pp +.Dl [IP header] [TCP header] [data...] +.Pp +If we apply ESP in transport mode to the above packet, we will get: +.Pp +.Dl [IP header] [ESP header] [TCP header] [data...] +.Pp +Everything after the ESP +header is protected by whatever services of ESP we are using +(authentication/integrity, replay protection, confidentiality). +This means the IP header itself is not protected. +.Pp +If we apply ESP in tunnel mode to the original packet, we would get: +.Pp +.Dl [IP header] [ESP header] [IP header] [TCP header] [data...] +.Pp +Again, everything after the ESP header is cryptographically protected. +Notice the insertion of an IP header between the ESP and TCP header. +This mode of operation allows us to hide who the true +source and destination addresses of a packet are +(since the protected and the unprotected IP +headers don't have to be exactly the same). +A typical application of this is in Virtual Private Networks (or VPNs), +where two firewalls use IPsec +to secure the traffic of all the hosts behind them. +For example: +.Bd -literal -offset indent +Net A <----> Firewall 1 <--- Internet ---> Firewall 2 <----> Net B +.Ed +.Pp +Firewall 1 and Firewall 2 can protect all communications between Net A +and Net B by using IPsec in tunnel mode, as illustrated above. +.Pp +This implementation makes use of a virtual interface, +.Nm enc0 , +which can be used in packet filters to specify those packets that have +been or will be processed by IPsec. +.Pp +NAT can also be applied to +.Nm enc# +interfaces, but special care should be taken because of the interactions +between NAT and the IPsec flow matching, especially on the packet output path. +Inside the TCP/IP stack, packets go through the following stages: +.Bd -literal -offset indent +UL/R -> [X] -> PF/NAT(enc0) -> IPsec -> PF/NAT(IF) -> IF +UL/R <-------- PF/NAT(enc0) <- IPsec <- PF/NAT(IF) <- IF +.Ed +.Pp +With IF being the real interface and UL/R the Upper Layer or Routing code. +The [X] +stage on the output path represents the point where the packet +is matched against the IPsec flow database (SPD) to determine if and how +the packet has to be IPsec-processed. +If, at this point, it is determined that the packet should be IPsec-processed, +it is processed by the PF/NAT code. +Unless PF drops the packet, it will then be IPsec-processed, even if the +packet has been modified by NAT. +.Pp +Security Associations can be set up manually with +.Xr ipsecctl 8 +or automatically with the +.Xr isakmpd 8 +or +.Xr iked 8 +key management daemons. +.Ss Additional Variables +A number of +.Xr sysctl 8 +variables are relevant to +.Nm . +These are generally +.Va net.inet.ah.* , +.Va net.inet.esp.* , +.Va net.inet.ip.forwarding , +.Va net.inet6.ip6.forwarding , +and +.Va net.inet.ip.ipsec-* . +Full explanations can be found in +.Xr sysctl 2 , +and variables can be set using the +.Xr sysctl 8 +interface. +.Pp +A number of kernel options are also relevant to +.Nm . +See +.Xr options 4 +for further information. +.Ss API Details +The following IP-level +.Xr setsockopt 2 +and +.Xr getsockopt 2 +options are specific to +.Nm ipsec . +A socket can specify security levels for three different categories: +.Bl -tag -width IP_ESP_NETWORK_LEVEL -offset 2n +.It IP_AUTH_LEVEL +Specifies the use of authentication for packets sent or received by the +socket. +.It IP_ESP_TRANS_LEVEL +Specifies the use of encryption in transport mode for packets sent or +received by the socket. +.It IP_ESP_NETWORK_LEVEL +Specifies the use of encryption in tunnel mode. +.El +.Pp +For each of the categories there are five possible levels which +specify the security policy to use in that category: +.Bl -tag -width IPSEC_LEVEL_REQUIRE -offset 2n +.It IPSEC_LEVEL_BYPASS +Bypass the default system security policy. +This option can only be used by privileged processes. +This level is necessary for the key management daemon, +.Xr isakmpd 8 . +.It IPSEC_LEVEL_AVAIL +If a Security Association is available, it will be used for sending packets +by that socket. +.It IPSEC_LEVEL_USE +Use IP Security for sending packets but still accept packets which are not +secured. +.It IPSEC_LEVEL_REQUIRE +Use IP Security for sending packets and also require IP Security for +received data. +.It IPSEC_LEVEL_UNIQUE +The outbound Security Association will only be used by this socket. +.El +.Pp +When a new socket is created, it is assigned the default system security +level in each category. +These levels can be queried with +.Xr getsockopt 2 . +Only a privileged process can lower the security level with a +.Xr setsockopt 2 +call. +.Pp +For example, a server process might want to accept only authenticated +connections to prevent session hijacking. +It would issue the following +.Xr setsockopt 2 +call: +.Bd -literal -offset 4n +int level = IPSEC_LEVEL_REQUIRE; +error = setsockopt(s, IPPROTO_IP, IP_AUTH_LEVEL, &level, sizeof(int)); +.Ed +.Pp +The system does guarantee that it will succeed at establishing the +required security associations. +In any case a properly configured key management daemon is required which +listens to messages from the kernel. +.Pp +A list of all security associations in the kernel tables can be +obtained using the +.Xr ipsecctl 8 +command. +.Sh DIAGNOSTICS +A socket operation may fail with one of the following errors returned: +.Bl -tag -width [EINVAL] +.It Bq Er EACCES +An attempt was made to lower the security level below the system default +by a non-privileged process. +.It Bq Er EINVAL +The length of option field did not match or an unknown security level +was given. +.El +.Pp +.Xr netstat 1 +can be used to obtain some statistics about AH or ESP usage: +.Bd -literal -offset indent +$ netstat -s -p ah +$ netstat -s -p esp +.Ed +.Pp +The +.Xr ipsecctl 8 +command can be used to display information about IPsec flows. +.Pp +.Xr vmstat 8 +displays information about memory use by IPsec with the +.Fl m +flag (look for +.Dq tdb +and +.Dq xform +allocations). +.Sh SEE ALSO +.Xr enc 4 , +.\".Xr ipcomp 4 , +.Xr options 4 , +.Xr ipsec.conf 5 , +.Xr iked 8 , +.Xr ipsecctl 8 , +.Xr isakmpd 8 , +.Xr sysctl 8 +.Sh HISTORY +IPsec was originally designed to provide security services +for Internet Protocol IPv6. +It has since been engineered to provide those services for +the original Internet Protocol, IPv4. +.Pp +The IPsec protocol design process was started in 1992 by +John Ioannidis, Phil Karn, and William Allen Simpson. +In 1995, the former wrote an implementation for +.Bsx . +Angelos D. Keromytis ported it to +.Ox +and +.Nx . +The latest transforms and new features were +implemented by Angelos D. Keromytis and Niels Provos. +.Sh AUTHORS +.An -nosplit +The authors of the IPsec code proper are +.An John Ioannidis , +.An Angelos D. Keromytis , +and +.An Niels Provos . +.Pp +.An Niklas Hallqvist +and +.An Niels Provos +are the authors of +.Xr isakmpd 8 . +.Pp +.An Eric Young Ap s +libdeslite was used in this implementation for the DES algorithm. +.Pp +.An Steve Reid Ap s +SHA-1 code was also used. +.Pp +The +.Xr setsockopt 2 Ns / Ns Xr getsockopt 2 +interface follows somewhat loosely the +draft-mcdonald-simple-ipsec-api +(since expired). +.Sh BUGS +There's a lot more to be said on this subject. +This is just a beginning. +At the moment the socket options are not fully implemented. diff --git a/static/openbsd/man4/ipw.4 b/static/openbsd/man4/ipw.4 new file mode 100644 index 00000000..3beead2e --- /dev/null +++ b/static/openbsd/man4/ipw.4 @@ -0,0 +1,162 @@ +.\" $OpenBSD: ipw.4,v 1.53 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2004 +.\" Damien Bergamini . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice unmodified, this list of conditions, and the following +.\" disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt IPW 4 +.Os +.Sh NAME +.Nm ipw +.Nd Intel PRO/Wireless 2100 IEEE 802.11b wireless network device +.Sh SYNOPSIS +.Cd "ipw* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Intel PRO/Wireless 2100 Mini PCI +network adapter. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver relies on the software 802.11 stack for both encryption and decryption +of data frames. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs at least version 1.3 of the following firmware files, +which are loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/ipw-bss +.It Pa /etc/firmware/ipw-ibss +.It Pa /etc/firmware/ipw-monitor +.El +.Pp +These firmware files are not free because Intel refuses to grant +distribution rights without contractual obligations. +As a result, even though +.Ox +includes the driver, the firmware files cannot be included and +users have to find these files on their own. +The official person to state your views to about this issue is +.Mt majid.awad@intel.com . +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig ipw0 scan +.Pp +The following +.Xr hostname.if 5 +example configures ipw0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "ipw0: device timeout" +The driver will reset the hardware. +This should not happen. +.It "ipw0: error N, could not read firmware ..." +For some reason, the driver was unable to read the firmware image from the +filesystem. +The file might be missing or corrupted. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . diff --git a/static/openbsd/man4/isa.4 b/static/openbsd/man4/isa.4 new file mode 100644 index 00000000..ea681002 --- /dev/null +++ b/static/openbsd/man4/isa.4 @@ -0,0 +1,226 @@ +.\" $OpenBSD: isa.4,v 1.82 2023/04/27 19:10:53 jmc Exp $ +.\" $NetBSD: isa.4,v 1.19 2000/03/18 16:54:37 augustss Exp $ +.\" +.\" Copyright (c) 2000 Theo de Raadt. All rights reserved. +.\" Copyright (c) 1997 Jason R. Thorpe. All rights reserved. +.\" Copyright (c) 1997 Jonathan Stone +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgements: +.\" This product includes software developed by Jonathan Stone +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: April 27 2023 $ +.Dt ISA 4 +.Os +.Sh NAME +.Nm isa , isadma +.Nd introduction to ISA bus support +.Sh SYNOPSIS +.Cd "# amd64 and i386" +.Cd "isa* at amdpcib?" +.Cd "isa0 at tcpcib?" +.Cd "isa0 at mainbus0" +.Cd "isa0 at pcib?" +.Cd "isadma0 at isa?" +.Pp +.Cd "# i386" +.Cd "isa0 at ichpcib?" +.Cd "isa* at glxpcib?" +.Cd "isa0 at gscpcib?" +.Pp +.Cd "# alpha" +.Cd "isa* at pceb?" +.Cd "isa* at sio?" +.Cd "isadma0 at isa?" +.Pp +.Cd "# loongson" +.Cd "isa* at glxpcib?" +.Sh DESCRIPTION +The system includes a machine-independent ISA bus subsystem +and several machine-independent ISA device drivers. +.Pp +Attachments are machine-dependent and depend on the bus topology and +ISA bus interface of the system. +Drivers able to use DMA attach at +.Nm isadma ; +otherwise they attach at +.Nm isa . +.Pp +Note that interrupt mappings on the i386 may require that the BIOS +be configured to reserve the interrupts for these devices as "Legacy ISA". +If such configuration is not done, the system may use those interrupts +for +.Xr pci 4 +or +.Xr isapnp 4 +devices instead. +.Pp +.Ox +provides support for the following devices. +Note that not all architectures support all devices. +.Ss SCSI controllers +.Bl -tag -width 12n -offset ind -compact +.It Xr ahc 4 +Adaptec VL/EISA/PCI SCSI interface +.It Xr aic 4 +Adaptec AIC-6260 and AIC-6360 SCSI interface +.It Xr uha 4 +Ultrastor SCSI interface +.It Xr wds 4 +WD7000 compatible ISA SCSI interface +.El +.Ss Disk and tape controllers +.Bl -tag -width 12n -offset ind -compact +.It Xr fdc 4 +NEC765 compatible floppy disk driver +.It Xr wdc 4 +Standard Western Digital type hard drive controllers: MFM, RLL, ESDI, +and IDE/ATAPI. +See also the +.Xr pciide 4 +device driver which is used instead on machines with PCI IDE controllers. +.El +.Ss Serial and parallel interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr addcom 4 +Addonics FlexPort 8S serial communication cards +.It Xr ast 4 +multiplexing serial communications interface +.It Xr boca 4 +multiplexing serial communications interface +.It Xr com 4 +serial communications interface +.It Xr cy 4 +Cyclades Cyclom-{4, 8, 16}Y asynchronous comms board device driver +.It Xr hsq 4 +multiplexing serial communications interface +.It Xr lpt 4 +parallel port driver +.El +.Ss Network interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr ec 4 +3Com EtherLink II (3c503) Ethernet device +.It Xr ef 4 +3Com Fast EtherLink ISA (3c515) 10/100 Ethernet device +.It Xr eg 4 +3Com EtherLink Plus Ethernet (3c505) Ethernet device +.It Xr el 4 +3Com EtherLink (3C501) Ethernet device +.It Xr ep 4 +3Com EtherLink III and Fast EtherLink III 10/100 Ethernet device +.It Xr ex 4 +Intel EtherExpress Pro/10 and Pro/10+ Ethernet device +.It Xr ie 4 +Intel i82586/i82596 Ethernet device +.It Xr lc 4 +DEC EtherWORKS III 10/100 Ethernet device +.It Xr le 4 +AMD LANCE Ethernet device +.It Xr ne 4 +NE2000 and compatible 10/100 Ethernet device +.It Xr sm 4 +SMC91C9x and SMC91C1xx-based 10/100 Ethernet device +.It Xr we 4 +Western Digital/SMC WD80x3, SMC Elite Ultra, and SMC EtherEZ Ethernet device +.El +.Ss Sound cards +.Bl -tag -width 12n -offset ind -compact +.It Xr ess 4 +ESS Technology AudioDrive family audio device +.It Xr gus 4 +Gravis UltraSound/UltraSound MAX audio device +.It Xr mpu 4 +Roland/Yamaha MPU401 MIDI UART device +.It Xr pas 4 +Media Vision Pro AudioSpectrum audio device +.It Xr sb 4 +SoundBlaster family audio device +.El +.Ss Hardware Sensors +.Bl -tag -width 12n -offset ind -compact +.It Xr aps 4 +ThinkPad Active Protection System accelerometer +.It Xr asmc 4 +Apple System Management Controller (SMC) +.It Xr fins 4 +Fintek F71805F LPC Super I/O +.It Xr it 4 +ITE IT87xxF and SiS SiS950 temperature, voltage, and fan sensor with +watchdog timer +.It Xr lm 4 +National Semiconductor LM78/79/81 temperature, voltage, and fan sensor +.It Xr nsclpcsio 4 +National Semiconductor PC87366 LPC Super I/O with GPIO +.It Xr schsio 4 +SMSC SCH311x LPC Super I/O +.It Xr uguru 4 +ABIT temperature, voltage and fan sensors +.It Xr viasio 4 +VIA VT1211 LPC Super I/O +.It Xr wbsio 4 +Winbond LPC Super I/O +.El +.Ss Miscellaneous devices +.Bl -tag -width 12n -offset ind -compact +.It Xr gscsio 4 +National Semiconductor Geode SC1100 I2C controller +.It Xr isagpio 4 +ISA I/O mapped as GPIO +.It Xr joy 4 +games adapter +.It Xr lms 4 +Logitech-style bus mouse driver +.It Xr mms 4 +Microsoft-style bus mouse driver +.It Xr npx 4 +Numeric Processing Extension coprocessor and emulator +.It Xr pcdisplay 4 +PC display adapter driver for wscons +.It Xr pcic 4 +ISA PCMCIA controllers +.It Xr pckbc 4 +PC (ISA) keyboard controller driver +.It Xr pcppi 4 +PC (ISA) control and timer port driver +.It Xr skgpio 4 +Soekris net6501 GPIO and LEDs driver +.It Xr tcic 4 +Databook PCMCIA controller driver +.It Xr vga 4 +VGA graphics driver for wscons +.It Xr ykbec 4 +Ene Technology KB3310B embedded controller chip +.El +.Pp +Note that some ISA devices also have newer ISA Plug-and-Play variants. +These are listed in +.Xr isapnp 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr isapnp 4 +.Sh HISTORY +The machine-independent ISA subsystem appeared in +.Ox 2.0 . diff --git a/static/openbsd/man4/isagpio.4 b/static/openbsd/man4/isagpio.4 new file mode 100644 index 00000000..5ffe1420 --- /dev/null +++ b/static/openbsd/man4/isagpio.4 @@ -0,0 +1,59 @@ +.\" $OpenBSD: isagpio.4,v 1.5 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Oleg Safiullin +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice unmodified, this list of conditions, and the following +.\" disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ISAGPIO 4 +.Os +.Sh NAME +.Nm isagpio +.Nd ISA I/O mapped as GPIO +.Sh SYNOPSIS +.Cd "isagpio0 at isa? port 0x78" +.Cd "isagpio1 at isa? port 0x80" +.Cd "gpio* at isagpio?" +.Sh DESCRIPTION +The +.Nm +driver allows access to the 8-bit ISA I/O space through the +.Xr gpio 4 +framework, thus making use of the simple GPIO devices connected directly +to the ISA bus. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Oleg Safiullin Aq Mt form@pdp-11.org.ru . diff --git a/static/openbsd/man4/isapnp.4 b/static/openbsd/man4/isapnp.4 new file mode 100644 index 00000000..9336bd8e --- /dev/null +++ b/static/openbsd/man4/isapnp.4 @@ -0,0 +1,140 @@ +.\" $OpenBSD: isapnp.4,v 1.43 2023/04/27 19:01:01 miod Exp $ +.\" $NetBSD: isapnp.4,v 1.8 1998/06/07 09:08:46 enami Exp $ +.\" +.\" Copyright (c) 1997 Jonathan Stone +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgements: +.\" This product includes software developed by Jonathan Stone +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: April 27 2023 $ +.Dt ISAPNP 4 +.Os +.Sh NAME +.Nm isapnp +.Nd introduction to ISA Plug-and-Play support +.Sh SYNOPSIS +.Cd "isapnp0 at isa?" +.Sh DESCRIPTION +An +.Nm +bus can be configured for each supported ISA bus. +.Pp +.Ox +provides machine-independent bus support and drivers for ISA +Plug-and-Play (isapnp) autoconfiguration of PnP-compatible +devices on an ISA bus. +.Sh SUPPORTED DEVICES +.Ox +includes machine-independent ISAPNP drivers, sorted by function +and driver name: +.Ss Disk controllers +.Bl -tag -width 12n -offset ind -compact +.It Xr aic 4 +Adaptec AIC-6260 and AIC-6360 SCSI interface +.It Xr wdc 4 +WD100x compatible hard disk controller driver +.El +.Ss Serial and parallel interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr com 4 +serial communications interface +.El +.Ss Network interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr an 4 +Aironet 4500/4800 IEEE 802.11FH/b wireless interfaces +.It Xr ef 4 +3Com Fast EtherLink ISA (3c515) 10/100 Ethernet device +.It Xr ep 4 +3Com EtherLink III and Fast EtherLink III 10/100 Ethernet device +.It Xr le 4 +AMD LANCE Ethernet device +.It Xr ne 4 +NE2000 and compatible 10/100 Ethernet device +.It Xr we 4 +Western Digital/SMC WD80x3, SMC Elite Ultra, and SMC EtherEZ Ethernet device +.El +.Ss Sound +.Bl -tag -width 12n -offset ind -compact +.It Xr ess 4 +ESS Technology AudioDrive family audio device +.It Xr gus 4 +Gravis UltraSound/UltraSound MAX audio device +.It Xr mpu 4 +Roland/Yamaha MPU401 MIDI UART device +.It Xr sb 4 +SoundBlaster family audio device +.El +.Ss Miscellaneous devices +.Bl -tag -width 12n -offset ind -compact +.It Xr joy 4 +games adapter +.It Xr pcic 4 +ISA PCMCIA controllers +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Nx 1.3 . +.Sh CAVEATS +From time to time an +.Nm +device will be found which the kernel does not recognize. +The kernel matches +.Nm +devices to device drivers based on identifiers which each device +provides. +For example, this device: +.Pp +joy0 at isapnp0 "Creative SB16 PnP, CTL7001, PNPB02F, Game" port 0x200/8 +.Pp +This joystick calls itself by the two names +.Dq CTL7001 +and +.Dq PNPB02F . +The latter is a standard name (which the kernel automatically recognizes), +but +.Dq CTL7001 +is a vendor-specific name which needs to be added to a table. +Unfortunately, +some devices advertise only their vendor-specific name; for instance: +.Pp +"PnP Sound Chip, @P@1001, , " at isapnp0 port 0x200/8 not configured +.Pp +Testing will show that this device is actually a joystick. +To resolve the issue, the actual name +.Dq @P@1001 +has to be entered into the database found in +.Pa /sys/dev/isa/pnpdevs +and a new kernel must be built. +Then the device will probe like this: +.Pp +joy0 at isapnp0 "PnP Sound Chip, @P@1001, , " port 0x200/8 diff --git a/static/openbsd/man4/islrtc.4 b/static/openbsd/man4/islrtc.4 new file mode 100644 index 00000000..68636e86 --- /dev/null +++ b/static/openbsd/man4/islrtc.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: islrtc.4,v 1.3 2018/11/20 09:06:08 reyk Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 20 2018 $ +.Dt ISLRTC 4 +.Os +.Sh NAME +.Nm islrtc +.Nd Intersil ISL1208/1218 real-time clock +.Sh SYNOPSIS +.Cd "islrtc* at iic? addr 0x6f" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Intersil/Renesas ISL1208 and ISL1218 +real-time clock chips. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/ispi.4 b/static/openbsd/man4/ispi.4 new file mode 100644 index 00000000..e271aaf1 --- /dev/null +++ b/static/openbsd/man4/ispi.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: ispi.4,v 1.1 2026/04/13 01:05:49 jsg Exp $ +.\" +.\" Copyright (c) 2026 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 13 2026 $ +.Dt ISPI 4 +.Os +.Sh NAME +.Nm ispi +.Nd Intel LPSS SPI controller +.Sh SYNOPSIS +.Cd "ispi* at acpi?" +.Cd "ispi* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports the Serial Peripheral Interface (SPI) controller +included in the Intel Low-Power Subsystem (LPSS). +.Sh SEE ALSO +.Xr acpi 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.9 . diff --git a/static/openbsd/man4/it.4 b/static/openbsd/man4/it.4 new file mode 100644 index 00000000..a01b9b10 --- /dev/null +++ b/static/openbsd/man4/it.4 @@ -0,0 +1,98 @@ +.\" $OpenBSD: it.4,v 1.25 2015/09/10 15:16:43 schwarze Exp $ +.\" +.\" Copyright (c) 2007-2008 Oleg Safiullin +.\" Copyright (c) 2003 Julien Bordet +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt IT 4 +.Os +.Sh NAME +.Nm it +.Nd ITE IT87xxF and SiS SiS950 temperature, voltage, and fan sensor with \ +watchdog timer +.Sh SYNOPSIS +.Cd "it* at isa? port 0x2e" +.Cd "it* at isa? port 0x4e" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +ITE IT8705F, IT8712F, IT8716F, IT8718F, IT8720F, IT8726F, IT8728F, IT8772F +and SiS SiS950 +hardware monitors and +.Xr watchdog 4 +timer to be used with the +.Xr sysctl 8 +interface. +.Pp +Most supported devices possess 17 sensors: +.Bl -column "Sensor" "Units" "Typical" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical Use" +.It Li "temp0" Ta "uK" Ta "CPU Temperature" +.It Li "temp1" Ta "uK" Ta "Motherboard Temperature" +.It Li "temp2" Ta "uK" Ta "Unused" +.It Li "fan0" Ta "RPM" Ta "CPU Fan" +.It Li "fan1" Ta "RPM" Ta "Chassis Fan" +.It Li "fan2" Ta "RPM" Ta "Power Fan" +.It Li "fan3" Ta "RPM" Ta "Unused" +.It Li "fan4" Ta "RPM" Ta "Unused" +.It Li "volt0" Ta "uV DC" Ta "Core voltage" +.It Li "volt1" Ta "uV DC" Ta "Core voltage" +.It Li "volt2" Ta "uV DC" Ta "+3.3V" +.It Li "volt3" Ta "uV DC" Ta "+5V" +.It Li "volt4" Ta "uV DC" Ta "+12V" +.It Li "volt5" Ta "uV DC" Ta "-12V" +.It Li "volt6" Ta "uV DC" Ta "-5V" +.It Li "volt7" Ta "uV DC" Ta "+5VSB" +.It Li "volt8" Ta "uV DC" Ta "VBAT" +.El +.Sh SEE ALSO +.Xr isa 4 , +.Xr watchdog 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was originally written for +.Ox 3.4 +by +.An Julien Bordet Aq Mt zejames@greyhats.org , +and completely rewritten for +.Ox 4.3 +by +.An Oleg Safiullin Aq Mt form@pdp-11.org.ru . +.Sh BUGS +Watchdog timer functionality is not supported for ITE IT8705 +or SiS SiS950 chips. +For older IT8712 chips, +watchdog timeout values of more than 255 seconds +are rounded up to the nearest minute. diff --git a/static/openbsd/man4/itherm.4 b/static/openbsd/man4/itherm.4 new file mode 100644 index 00000000..ebc49e22 --- /dev/null +++ b/static/openbsd/man4/itherm.4 @@ -0,0 +1,69 @@ +.\" $OpenBSD: itherm.4,v 1.4 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2010 Mike Larkin +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ITHERM 4 +.Os +.Sh NAME +.Nm itherm +.Nd Intel 3400 temperature sensor +.Sh SYNOPSIS +.Cd "itherm* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for several sensors found in Intel 3400 and 5 series +chipsets. +.Pp +The sensors currently exposed via the +.Xr sysctl 8 +interface are: +.Bl -column "CPU power cons." "Units" "Typical Use" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical Use" +.It Li "Thermometer" Ta "degC" Ta "Temperature" +.It Li "Core 1" Ta "degC" Ta "Temperature" +.It Li "Core 2" Ta "degC" Ta "Temperature" +.It Li "CPU power cons." Ta "Watts" Ta "Power usage" +.It Li "CPU/GPU Max" Ta "degC" Ta "Temperature" +.It Li "DIMM 1" Ta "degC" Ta "Temperature" +.It Li "DIMM 2" Ta "degC" Ta "Temperature" +.It Li "DIMM 3" Ta "degC" Ta "Temperature" +.It Li "DIMM 4" Ta "degC" Ta "Temperature" +.It Li "GPU abs." Ta "degC" Ta "Temperature" +.It Li "PCH abs." Ta "degC" Ta "Temperature" +.El +.Sh SEE ALSO +.Xr pci 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mike Larkin Aq Mt mlarkin@openbsd.org . +.Sh CAVEATS +Not all sensors are wired on every machine, so the list of +sensors shown in +.Xr sysctl 8 +may not show all the sensors listed above. +Furthermore, the +.Nm +driver will flag sensors as invalid if they report bogus data. diff --git a/static/openbsd/man4/iwi.4 b/static/openbsd/man4/iwi.4 new file mode 100644 index 00000000..13b0433c --- /dev/null +++ b/static/openbsd/man4/iwi.4 @@ -0,0 +1,162 @@ +.\" $OpenBSD: iwi.4,v 1.59 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2004 +.\" Damien Bergamini . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice unmodified, this list of conditions, and the following +.\" disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt IWI 4 +.Os +.Sh NAME +.Nm iwi +.Nd Intel PRO/Wireless 2200BG/2225BG/2915ABG IEEE 802.11a/b/g wireless network device +.Sh SYNOPSIS +.Cd "iwi* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Intel +PRO/Wireless 2200BG/2915ABG Mini PCI and 2225BG PCI network adapters. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver relies on the software 802.11 stack for both encryption and decryption +of data frames. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs at least version 3.1 of the following firmware files, +which are loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/iwi-bss +.It Pa /etc/firmware/iwi-ibss +.It Pa /etc/firmware/iwi-monitor +.El +.Pp +These firmware files are not free because Intel refuses to grant +distribution rights without contractual obligations. +As a result, even though +.Ox +includes the driver, the firmware files cannot be included and +users have to download these files on their own. +The official person to state your views to about this issue is +.Mt majid.awad@intel.com . +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig iwi0 scan +.Pp +The following +.Xr hostname.if 5 +example configures iwi0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "iwi0: device timeout" +The driver will reset the hardware. +This should not happen. +.It "iwi0: error N, could not read firmware ..." +For some reason, the driver was unable to read the firmware image from the +filesystem. +The file might be missing or corrupted. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . diff --git a/static/openbsd/man4/iwm.4 b/static/openbsd/man4/iwm.4 new file mode 100644 index 00000000..75e54ec9 --- /dev/null +++ b/static/openbsd/man4/iwm.4 @@ -0,0 +1,169 @@ +.\" $OpenBSD: iwm.4,v 1.48 2025/12/01 16:30:46 stsp Exp $ +.\" +.\" Copyright (c) 2007,2008 +.\" Damien Bergamini . All rights reserved. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 1 2025 $ +.Dt IWM 4 +.Os +.Sh NAME +.Nm iwm +.Nd Intel 7000/8000/9000 IEEE 802.11a/ac/b/g/n wireless network device +.Sh SYNOPSIS +.Cd "iwm* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Intel Wireless +7260, 7265, 3160, 3165, 3168, 8260, 8265, and 9260 +PCIe Mini Card and M.2 network adapters, +and for Intel Wireless 9560 Integrated Connectivity (CNVi) network +adapters with companion RF M.2 modules. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver offloads both encryption and decryption of unicast data frames to the +hardware for the CCMP cipher. +.Pp +The +.Nm +driver supports protected management frames (PMF) which prevents spoofing +of management frames such as deauthentication, disassociation, and block-ack +negotiation, on networks using WPA. +.Pp +In BSS mode the driver supports background scanning; +see +.Xr ifconfig 8 . +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs one of the following firmware files, +which are loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/iwm-3160-17 +.It Pa /etc/firmware/iwm-3168-29 +.It Pa /etc/firmware/iwm-7260-17 +.It Pa /etc/firmware/iwm-7265-17 +.It Pa /etc/firmware/iwm-7265D-29 +.It Pa /etc/firmware/iwm-8000C-36 +.It Pa /etc/firmware/iwm-8265-36 +.It Pa /etc/firmware/iwm-9000-46 +.It Pa /etc/firmware/iwm-9260-46 +.El +.Pp +These firmware files are not free because Intel refuses to grant +distribution rights without contractual obligations. +As a result, even though +.Ox +includes the driver, the firmware files cannot be included and +users have to download these files on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig iwm0 scan +.Pp +The following +.Xr hostname.if 5 +example configures iwm0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "iwm0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.It "iwm0: fatal firmware error" +For some reason, the firmware crashed. +The driver will reset the hardware. +This should not happen. +.It "iwm0: radio is disabled by hardware switch" +The radio transmitter is off and thus no packet can go out. +The driver will reset the hardware. +Make sure the laptop radio switch is on. +.It "iwm0: could not read firmware ... (error N)" +For some reason, the driver was unable to read the firmware image from the +filesystem. +The file might be missing or corrupted. +.It "iwm0: firmware too short: N bytes" +The firmware image is corrupted and can't be loaded into the adapter. +.It "iwm0: could not load firmware" +An attempt to load the firmware into the adapter failed. +The driver will reset the hardware. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.7 . diff --git a/static/openbsd/man4/iwn.4 b/static/openbsd/man4/iwn.4 new file mode 100644 index 00000000..64e443c7 --- /dev/null +++ b/static/openbsd/man4/iwn.4 @@ -0,0 +1,216 @@ +.\" $OpenBSD: iwn.4,v 1.63 2025/03/25 19:57:54 jmc Exp $ +.\" +.\" Copyright (c) 2007,2008 +.\" Damien Bergamini . All rights reserved. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 25 2025 $ +.Dt IWN 4 +.Os +.Sh NAME +.Nm iwn +.Nd Intel WiFi Link and Centrino IEEE 802.11a/b/g/n wireless network device +.Sh SYNOPSIS +.Cd "iwn* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Intel Wireless WiFi Link 4965/5000/1000 +and Centrino Wireless-N 1000/2000/6000 Series PCIe Mini Card network adapters. +.Pp +The Intel Wireless WiFi Link 4965AGN (codenamed Kedron) is a PCIe +Mini Card network adapter that operates in the 2GHz and 5GHz spectra. +It has 2 transmit paths and 3 receiver paths (2T3R). +It is part of the fourth-generation Centrino platform (codenamed Santa Rosa). +.Pp +The Intel WiFi Link 5000 series is a family of wireless network adapters +that operate in the 2GHz and 5GHz spectra. +They are part of the fifth-generation Centrino platform (codenamed Montevina). +These adapters are available in both PCIe Mini Card (model code ending by MMW) +and PCIe Half Mini Card (model code ending by HMW) form factor. +The +.Nm +driver provides support for the 5100 (codenamed Shirley Peak 1x2), +5150 (codenamed Echo Peak-V), 5300 (codenamed Shirley Peak 3x3) and +5350 (codenamed Echo Peak-P) adapters. +The 5100 and 5150 adapters have 1 transmit path and 2 receiver paths (1T2R). +The 5300 and 5350 adapters have 3 transmit paths and 3 receiver paths (3T3R). +.Pp +The Intel WiFi Link 1000 (codenamed Condor Peak) is a single-chip wireless +network adapter that operates in the 2GHz spectrum. +It is part of the sixth-generation Centrino platform (codenamed Calpella). +It is available in both PCIe Mini Card (model code ending by MMW) +and PCIe Half Mini Card (model code ending by HMW) form factor. +It has 1 transmit path and 2 receiver paths (1T2R). +.Pp +The Intel Centrino Ultimate-N 6300 (codenamed Puma Peak 3x3) is a single-chip +wireless network adapter that operates in the 2GHz and 5GHz spectra. +It has 3 transmit paths and 3 receiver paths (3T3R). +The Intel Centrino Advanced-N 6250 (codenamed Kilmer Peak) is a combo +WiFi/WiMAX network adapter that operates in the 2GHz and 5GHz spectra. +It has 2 transmit paths and 2 receiver paths (2T2R). +The Intel Centrino Advanced-N 6200 (codenamed Puma Peak 2x2) is +a wireless network adapter that operates in the 2GHz and 5GHz spectra. +It has 2 transmit paths and 2 receiver paths (2T2R). +These adapters are part of the sixth-generation Centrino platform +(codenamed Calpella). +.Pp +The Intel Centrino Wireless-N 2230 (codename Jackson Peak) and Intel +Centrino Wireless-N 2200 (codename Marble Peak) are wireless network +adapters that operate in the 2GHz spectrum. +These adapters have 2 transmit paths and 2 receiver paths (2T2R). +The Intel Centrino Wireless-N 135 and Intel Centrino Wireless-N 105 +(codename Canyon Peak) also operate in the 2GHz spectrum. +These adapters have 1 transmit path and 1 receiver path (1T1R). +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver offloads both encryption and decryption of unicast data frames to the +hardware for the CCMP cipher. +.Pp +In BSS mode the driver supports powersave mode +and background scanning; +see +.Xr ifconfig 8 . +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs at least version 5.6 of the following firmware files, +which are loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/iwn-4965 +.It Pa /etc/firmware/iwn-5000 +.It Pa /etc/firmware/iwn-5150 +.It Pa /etc/firmware/iwn-1000 +.It Pa /etc/firmware/iwn-6000 +.It Pa /etc/firmware/iwn-6050 +.It Pa /etc/firmware/iwn-6005 +.It Pa /etc/firmware/iwn-6030 +.It Pa /etc/firmware/iwn-2030 +.It Pa /etc/firmware/iwn-2000 +.It Pa /etc/firmware/iwn-135 +.It Pa /etc/firmware/iwn-105 +.El +.Pp +These firmware files are not free because Intel refuses to grant +distribution rights without contractual obligations. +As a result, even though +.Ox +includes the driver, the firmware files cannot be included and +users have to download these files on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig iwn0 scan +.Pp +The following +.Xr hostname.if 5 +example configures iwn0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "iwn0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.It "iwn0: fatal firmware error" +For some reason, the firmware crashed. +The driver will reset the hardware. +This should not happen. +.It "iwn0: radio is disabled by hardware switch" +The radio transmitter is off and thus no packet can go out. +The driver will reset the hardware. +Make sure the laptop radio switch is on. +.It "iwn0: could not read firmware ... (error N)" +For some reason, the driver was unable to read the firmware image from the +filesystem. +The file might be missing or corrupted. +.It "iwn0: firmware too short: N bytes" +The firmware image is corrupted and can't be loaded into the adapter. +.It "iwn0: could not load firmware" +An attempt to load the firmware into the adapter failed. +The driver will reset the hardware. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +802.11n operation is currently limited to data rates MCS 0 to MCS 7. diff --git a/static/openbsd/man4/iwx.4 b/static/openbsd/man4/iwx.4 new file mode 100644 index 00000000..ce587cee --- /dev/null +++ b/static/openbsd/man4/iwx.4 @@ -0,0 +1,177 @@ +.\" $OpenBSD: iwx.4,v 1.23 2026/03/03 17:46:54 kirill Exp $ +.\" +.\" Copyright (c) 2020 Stefan Sperling +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 3 2026 $ +.Dt IWX 4 +.Os +.Sh NAME +.Nm iwx +.Nd Intel AX200/AX201/AX210/AX211 IEEE 802.11a/ac/ax/b/g/n wireless network device +.Sh SYNOPSIS +.Cd "iwx* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Intel Wireless AX200/AX210 M.2 network adapters, +and for Intel Wireless AX201/AX211 Integrated Connectivity (CNVi) network +adapters with companion RF M.2 modules. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver offloads both encryption and decryption of unicast data frames to the +hardware for the CCMP cipher. +.Pp +The +.Nm +driver supports protected management frames (PMF) which prevents spoofing +of management frames such as deauthentication, disassociation, and block-ack +negotiation, on networks using WPA. +.Pp +In BSS mode the driver supports powersave mode and background scanning; +see +.Xr ifconfig 8 . +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs one of the following firmware files, +which are loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/iwx-cc-a0-77 +.It Pa /etc/firmware/iwx-Qu-b0-hr-b0-77 +.It Pa /etc/firmware/iwx-Qu-b0-jf-b0-77 +.It Pa /etc/firmware/iwx-Qu-c0-hr-b0-77 +.It Pa /etc/firmware/iwx-Qu-c0-jf-b0-77 +.It Pa /etc/firmware/iwx-QuZ-a0-hr-b0-77 +.It Pa /etc/firmware/iwx-QuZ-a0-jf-b0-77 +.It Pa /etc/firmware/iwx-so-a0-gf-a0-77 +.It Pa /etc/firmware/iwx-so-a0-gf4-a0-77 +.It Pa /etc/firmware/iwx-so-a0-hr-b0-77 +.It Pa /etc/firmware/iwx-so-a0-jf-b0-77 +.It Pa /etc/firmware/iwx-ty-a0-gf-a0-77 +.El +.Pp +These firmware files are not free because Intel refuses to grant +distribution rights without contractual obligations. +As a result, even though +.Ox +includes the driver, the firmware files cannot be included and +users have to download these files on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig iwx0 scan +.Pp +The following +.Xr hostname.if 5 +example configures iwx0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "iwx0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.It "iwx0: fatal firmware error" +For some reason, the firmware crashed. +The driver will reset the hardware. +This should not happen. +.It "iwx0: radio is disabled by hardware switch" +The radio transmitter is off and thus no packet can go out. +The driver will reset the hardware. +Make sure the laptop radio switch is on. +.It "iwx0: could not read firmware ... (error N)" +For some reason, the driver was unable to read the firmware image from the +filesystem. +The file might be missing or corrupted. +.It "iwx0: firmware too short: N bytes" +The firmware image is corrupted and can't be loaded into the adapter. +.It "iwx0: could not load firmware" +An attempt to load the firmware into the adapter failed. +The driver will reset the hardware. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh CAVEATS +The +.Nm +driver does not support any of the 802.11ax capabilities offered +by the adapters. +Additional work is required in +.Xr ieee80211 9 +before those features can be supported. diff --git a/static/openbsd/man4/ix.4 b/static/openbsd/man4/ix.4 new file mode 100644 index 00000000..c0563581 --- /dev/null +++ b/static/openbsd/man4/ix.4 @@ -0,0 +1,106 @@ +.\" $OpenBSD: ix.4,v 1.11 2024/11/02 06:47:03 jmc Exp $ +.\" +.\" Copyright (c) 2008 Reyk Floeter +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 2 2024 $ +.Dt IX 4 +.Os +.Sh NAME +.Nm ix +.Nd Intel 82598/82599/X540/X550 PCI Express 100/1Gb/10Gb Ethernet device +.Sh SYNOPSIS +.Cd "ix* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI Express 10Gb Ethernet adapters based +on the Intel 82598EB, 82599EB, X540 and X550 Ethernet controller chips, +including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +Intel 82598AF 10GbE Adapter (10GbaseSR) +.It +Intel 82598AF Dual Port 10GbE Adapter (10GbaseSR) +.It +Intel 82598EB 10GbE Adapter (10GbaseCX4) +.It +Intel 82598EB 10GbE Adapter (SFP+) +.It +Intel 82598EB Dual Port 10GbE Adapter (10GbaseCX4) +.It +Intel 82598EB XF 10GbE Adapter (10GbaseLR) +.It +Intel 82598AT 10GbE Adapter (10GbaseT) +.It +Intel 82598AT Dual Port 10GbE Adapter (10GbaseT) +.It +Intel 82599EB 10GbE Adapter (10GbaseCX4) +.It +Intel X520-DA2 Dual Port 10GbE Adapter (SFP+) +.It +Intel X520-SR1 10GbE Adapter (SFP+/10GbaseSR) +.It +Intel X520-SR2 Dual Port 10GbE Adapter (SFP+/10GbaseSR) +.It +Intel X520-LR1 10GbE Adapter (SFP+/10GbaseLR) +.It +Intel X520-QDA1 10GbE Adapter (QSFP) +.It +Intel X540-T 10GbE Adapter (10GbaseT/1000baseT/100baseTX) +.It +Intel X550-T 10GbE Adapter (10GbaseT/1000baseT/100baseTX) +.It +Intel X552 10GbE Adapter (SFP+) +.It +Intel Xeon-D X552/X557 embedded 10GbE Adapter (SFP+/10GbaseT) +.It +HotLava Tambora 64G4/80G4/64G6/120G6 (SFP+) +.El +.Pp +SFP+ adapters generally also support SFP type modules with their +associated 1000base-* media types. +.Pp +The networking interface should be brought down before +disconnecting fiber optics, otherwise irreversible damage might be caused +to the equipment. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr ixv 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Intel Corporation +and ported to +.Ox +by +.An Reyk Floeter Aq Mt reyk@openbsd.org . +.An Claudio Jeker Aq Mt claudio@openbsd.org +and +.An Mike Belopuhov Aq Mt mikeb@openbsd.org +have performed multiple updates since. diff --git a/static/openbsd/man4/ixgb.4 b/static/openbsd/man4/ixgb.4 new file mode 100644 index 00000000..997aeb99 --- /dev/null +++ b/static/openbsd/man4/ixgb.4 @@ -0,0 +1,118 @@ +.\" $OpenBSD: ixgb.4,v 1.14 2014/09/14 00:17:09 brad Exp $ +.\" Copyright (c) 2002 Intel Corporation +.\" All rights reserved. +.\" Redistribution and use in source and binary forms of the Software, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code of the Software may retain the above +.\" copyright notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form of the Software may reproduce the +.\" above copyright notice, this list of conditions and the following +.\" disclaimer in the documentation and/or other materials provided with the +.\" distribution. +.\" 3. Neither the name of the Intel Corporation nor the names of its contributors +.\" shall be used to endorse or promote products derived from this Software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" +.\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE INTEL OR ITS CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER +.\" CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE +.\" USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" * Other names and brands may be claimed as the property of others. +.\" +.\" $FreeBSD: em.4,v 1.18 2005/01/30 12:29:06 yar Exp $ +.Dd $Mdocdate: September 14 2014 $ +.Dt IXGB 4 +.Os +.Sh NAME +.Nm ixgb +.Nd Intel PRO/10GbE 10Gb Ethernet device +.Sh SYNOPSIS +.Cd "ixgb* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI-X 10Gb Ethernet adapters based on the +Intel 82597EX Ethernet controller chips. +The driver supports IPv4 receive IP/TCP/UDP checksum offload, VLAN tag +insertion and stripping, and jumbo frames. +This includes the following models: +.Pp +.Bl -item -offset indent -compact +.It +Intel PRO/10GbE CX4 Server Adapter (PXLA8591CX4) +.It +Intel PRO/10GbE LR Server Adapter (PXLA8591LR) +.It +Intel PRO/10GbE SR Server Adapter (PXLA8591SR) +.It +Sun 10 Gigabit Ethernet PCI-X Adapter (X5544A-4) +.El +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width autoselect -offset indent +.It autoselect +Enables auto-negotiation for speed and duplex. +.It 10GbaseLR +Sets 10Gbps operation. +Only full-duplex mode is supported at this speed. +.It 10GbaseSR +Sets 10Gbps operation. +Only full-duplex mode is supported at this speed. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Intel Corporation . +.Sh BUGS +Under small packet UDP stress tests with 10GbE driver, the +.Ox +system will drop UDP packets due to the fullness of the socket buffers. +You may want to change the driver's Flow Control variables to the minimum +value for controlling packet reception. +.Pp +Excessive CRC errors may be observed if the Intel PRO/10GbE CX4 Server +adapter is connected to a Fujitsu XENPAK CX4 module in a SmartBits chassis +using 15m/24AWG cable assemblies manufactured by Fujitsu or Leoni. +The CRC errors may be received either by the Intel PRO/10GbE CX4 Server +adapter or the SmartBits. +If this situation occurs, using a different cable assembly may resolve the +issue. +.Pp +Excessive CRC errors may be observed if the Intel PRO/10GbE CX4 Server +adapter is connected to an HP Procurve 3400cl switch port using short cables +(1m or shorter). +If this situation occurs, using a longer cable may resolve the issue. +.Pp +Excessive CRC errors may be observed using Fujitsu 24AWG cable assemblies that +are 10m or longer or where using a Leoni 15 m/24AWG cable assembly. +The CRC errors may be received either by the CX4 Server adapter +or at the switch. +If this situation occurs, using a different cable assembly +may resolve the issue. diff --git a/static/openbsd/man4/ixl.4 b/static/openbsd/man4/ixl.4 new file mode 100644 index 00000000..f7870621 --- /dev/null +++ b/static/openbsd/man4/ixl.4 @@ -0,0 +1,62 @@ +.\" $OpenBSD: ixl.4,v 1.5 2020/07/12 04:56:05 dlg Exp $ +.\" +.\" Copyright (c) 2019 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 12 2020 $ +.Dt IXL 4 +.Os +.Sh NAME +.Nm ixl +.Nd Intel Ethernet 700 series Ethernet device +.Sh SYNOPSIS +.Cd "ixl* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports Intel 700 series controllers based on the +Intel X710, XXV710, XL710, and X722 Ethernet chipsets. +.Pp +The functionality of the Intel 700 series Ethernet controllers has improved as newer versions of firmware have been released. +To ensure correct driver operation, apply the most recent +.Pq stable +firmware update for the network controller. +.Pp +The +.Nm ixl +driver supports querying pluggable transceivers for information and +diagnostics. +.\" via ifconfig ixlX sff . +This functionality is available on controllers providing API version +1.6 and higher. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org +and +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . diff --git a/static/openbsd/man4/ixv.4 b/static/openbsd/man4/ixv.4 new file mode 100644 index 00000000..ffb79875 --- /dev/null +++ b/static/openbsd/man4/ixv.4 @@ -0,0 +1,61 @@ +.\" $OpenBSD: ixv.4,v 1.5 2025/05/08 23:04:35 yasuoka Exp $ +.\" +.\" Copyright (c) 2024 YASUOKA Masahiko +.\" Copyright (c) 2019 Jonathan Matthew +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 8 2025 $ +.Dt IXV 4 +.Os +.Sh NAME +.Nm ixv +.Nd Intel 10Gb Ethernet virtual function device +.Sh SYNOPSIS +.Cd "ixv* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports the SR-IOV virtual functions of Intel 82598EB, +82599, and X540-based Ethernet controller devices. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr ix 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.7 . +.Sh AUTHORS +The +.Nm +driver was written by +Intel Corporation and ported to +.Ox +by +.An NAITO Yuichiro . +.Sh BUGS +The VF relies on +.Dq vlan-filter +to receive VLAN-tagged packets. +Because the current driver doesn't have a way to configure it, +any VLAN-tagged packets will not be passed. +Alternatively, +on the host running the primary function, +there might be a way to configure a VLAN ID. diff --git a/static/openbsd/man4/jmb.4 b/static/openbsd/man4/jmb.4 new file mode 100644 index 00000000..6d33589d --- /dev/null +++ b/static/openbsd/man4/jmb.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: jmb.4,v 1.5 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2007 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt JMB 4 +.Os +.Sh NAME +.Nm jmb +.Nd JMicron JMB36x SATA II and PATA Host Controller +.Sh SYNOPSIS +.Cd "jmb* at pci?" +.Cd "ahci* at jmb?" +.Cd "pciide* at jmb?" +.Sh DESCRIPTION +JMicron JMB36x hardware can provide support for SATA devices using the Advanced +Host Controller Interface for Serial ATA, and for PATA devices using PCI IDE +controller specification. +Since support for both SATA and PATA devices can be enabled on the same PCI +device but only one driver per PCI device can be attached, the +.Nm +driver acts as a nexus to other drivers that support the SATA and PATA +functionality. +.Xr ahci 4 +supports the SATA functionality, and +.Xr pciide 4 +support the PATA functionality on these controllers. +.Sh SEE ALSO +.Xr ahci 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr pciide 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/jme.4 b/static/openbsd/man4/jme.4 new file mode 100644 index 00000000..21f82604 --- /dev/null +++ b/static/openbsd/man4/jme.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: jme.4,v 1.8 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2008 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt JME 4 +.Os +.Sh NAME +.Nm jme +.Nd JMicron JMC25x/JMC26x 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "jme* at pci?" +.Cd "jmphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports PCI Express Ethernet adapters based on the JMicron +JMC260 10/100 and JMC250 10/100/1Gb Ethernet chips. +The Ethernet portion of the JMC261 10/100 and +JMC251 10/100/1Gb chips, +which incorporate a card reader, +is also supported. +.Pp +The +.Nm +driver supports IPv4 receive/transmit IP/TCP/UDP checksum offload, IPv6 +receive/transmit TCP/UDP checksum offload and VLAN tag insertion and +stripping. +.Pp +The following +.Ar media +types are supported: +.Pp +.Bl -tag -width autoselect -compact +.It Cm autoselect +Enable autoselection of the media type and options. +.It Cm 10baseT +Set 10Mbps operation. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.It Cm 1000baseT +Set 1000Mbps (Gigabit Ethernet) operation (some models only). +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr jmphy 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Pyun YongHyeon +for +.Fx +and ported to +.Ox +by +.An Jonathan Gray Aq Mt jsg@openbsd.org . diff --git a/static/openbsd/man4/jmphy.4 b/static/openbsd/man4/jmphy.4 new file mode 100644 index 00000000..7946b25c --- /dev/null +++ b/static/openbsd/man4/jmphy.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: jmphy.4,v 1.3 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2008 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt JMPHY 4 +.Os +.Sh NAME +.Nm jmphy +.Nd JMicron JMP202/JMP211 10/100/1Gb Ethernet PHY +.Sh SYNOPSIS +.Cd "jmphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the JMicron JMP202 10/100 and +JMP211 10/100/1Gb Ethernet PHYs. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Pyun YongHyeon +for +.Fx +and ported to +.Ox +by +.An Jonathan Gray Aq Mt jsg@openbsd.org . diff --git a/static/openbsd/man4/kate.4 b/static/openbsd/man4/kate.4 new file mode 100644 index 00000000..a1c6f5e4 --- /dev/null +++ b/static/openbsd/man4/kate.4 @@ -0,0 +1,98 @@ +.\" $OpenBSD: kate.4,v 1.6 2019/04/23 18:23:49 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Constantine A. Murenin +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 23 2019 $ +.Dt KATE 4 +.Os +.Sh NAME +.Nm kate +.Nd AMD K8 temperature sensor +.Sh SYNOPSIS +.Cd "kate* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensors available in the +AMD K8 family of processors. +.Pp +These sensors were officially introduced with +Revision F Family 0Fh processors, +and provide 1 degC accuracy. +Precision was improved in Revision G chips, +which provide two more bits for 0.25 degC steppings. +Each core may have two temperature sensors, and +there may be up to two cores per package. +.Pp +Multiprocessor systems would have one instance of +.Nm +per each chip. +In each instance, +.Va temp0 +and +.Va temp1 +sensors +correspond to the temperature sensors on the first core, +whereas +.Va temp2 +and +.Va temp3 +correspond to the temperature sensors on the second core. +As such, single core chips may have two sensors, +and dual-core dual-processor systems may have as many as 8 +temperature sensors in total. +.Pp +Since many prior revisions of the chips appear to have +valid readings for at least some temperature sensors +in the same address space as the aforementioned revisions, +the driver may also attach on such older revisions provided +that it finds some sensor readings that appear valid. +However, in such cases +.Nm +would not print the core revision information into the dmesg. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Rs +.%T "BIOS and Kernel Developer's Guide for AMD NPT Family 0Fh Processors" +.%D July 2007 +.%R Publication # 32559 +.%P pp. 21\(en23 and pp. 179\(en184 +.\" .%O http://support.amd.com/us/Processor_TechDocs/32559.pdf +.Re +.Rs +.%T "Revision Guide for AMD NPT Family 0Fh Processors" +.%D February 2008 +.%R Publication # 33610 +.\" .%O http://support.amd.com/us/Processor_TechDocs/33610.pdf +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Constantine A. Murenin Aq Mt cnst@openbsd.org +whilst at the University of Waterloo. diff --git a/static/openbsd/man4/kcov.4 b/static/openbsd/man4/kcov.4 new file mode 100644 index 00000000..9cbce9ee --- /dev/null +++ b/static/openbsd/man4/kcov.4 @@ -0,0 +1,206 @@ +.\" $OpenBSD: kcov.4,v 1.10 2021/12/30 06:55:37 anton Exp $ +.\" +.\" Copyright (c) 2018 Anton Lindqvist +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 30 2021 $ +.Dt KCOV 4 +.Os +.Sh NAME +.Nm kcov +.Nd kernel code coverage tracing +.Sh SYNOPSIS +.Cd pseudo-device kcov +.Pp +.In sys/kcov.h +.Sh DESCRIPTION +The +.Nm +driver implements collection of code coverage inside the kernel. +It can be enabled on a per thread basis from user space, +allowing the kernel program counter to be collected during syscalls triggered by +the same thread. +The collected coverage can be accessed by mapping the device +using +.Xr mmap 2 . +.Pp +By default, +.Nm +is not enabled but instead requires the following line to be present in the +kernel configuration: +.Bd -literal -offset indent +pseudo-device kcov 1 +.Ed +.Pp +The following +.Xr ioctl 2 +calls are provided: +.Bl -tag -width 4n +.It Dv KIOSETBUFSIZE Fa unsigned long *nentries +Allocate a coverage buffer with a capacity of +.Fa nentries . +The buffer can be accessed using +.Xr mmap 2 , +whereas the returned pointer must be interpreted as an array of +.Vt unsigned long +entries. +The first entry contains the number of entries in the array, +excluding the first entry. +.It Dv KIOENABLE Fa int *mode +Enable code coverage tracing for the current thread or any remote +subsystem attached using +.Dv KIOREMOTEATTACH . +The +.Fa mode +must be one of the following: +.Bl -ohang +.It Dv KCOV_MODE_TRACE_PC +Trace the kernel program counter. +.It Dv KCOV_MODE_TRACE_CMP +Trace comparison instructions and switch statements. +For switch statements, the number of traced comparison instructions is equal to +the number of switch cases. +Each traced comparison instruction is represented by 4 entries in the coverage +buffer: +.Bl -enum +.It +A mask where the least significant bit is set if one of the comparison operands +is a compile-time constant, which is always true for switch statements. +The remaining bits represents the log2 size of the operands, ranging from 0 to +3. +.It +First comparison operand. +For switch statements, this operand corresponds to the case value. +.It +Second comparison operand. +For switch statements, this operand corresponds to the value passed to switch. +.It +Kernel program counter where the comparison instruction took place. +.El +.Pp +In this mode, the first entry in the coverage buffer reflects the number of +traced comparison instructions. +Thus, the effective number of entries in the coverage buffer is given by +multiplying the first entry by 4. +.El +.It Dv KIODISABLE Fa void +Disable code coverage tracing for the current thread. +.It Dv KIOREMOTEATTACH Fa struct kio_remote_attach *remote +Attach collection of remote coverage from other kernel threads, identified +by a subsystem. +Collection of remote coverage is mutually exclusive with coverage collection +of the current thread. +The +.Va remote +argument is a pointer to the following structure: +.Bd -literal +struct kio_remote_attach { + int subsystem; + int id; +}; +.Ed +.Pp +The +.Va subsystem +field must be one of the following: +.Bl -ohang +.It Dv KCOV_REMOTE_COMMON +Collect coverage from tasks and timeouts scheduled by the current process, +see +.Xr task_add 9 +and +.Xr timeout 9 . +The +.Fa id +field is ignored. +.El +.El +.Sh FILES +.Bl -tag -width /dev/kcov -compact +.It Pa /dev/kcov +Default device node. +.El +.Sh EXAMPLES +In the following example, +the +.Xr read 2 +syscall is traced and the coverage displayed, which in turn can be passed to +.Xr addr2line 1 +in order to translate the kernel program counter into the file name and line +number it corresponds to. +.Bd -literal +#include +#include +#include + +#include +#include +#include +#include +#include + +int +main(void) +{ + unsigned long *cover, i; + unsigned long size = 1024; + int fd, mode; + + fd = open("/dev/kcov", O_RDWR); + if (fd == -1) + err(1, "open"); + + if (ioctl(fd, KIOSETBUFSIZE, &size) == -1) + err(1, "ioctl: KIOSETBUFSIZE"); + cover = mmap(NULL, size * sizeof(unsigned long), + PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); + if (cover == MAP_FAILED) + err(1, "mmap"); + + mode = KCOV_MODE_TRACE_PC; + if (ioctl(fd, KIOENABLE, &mode) == -1) + err(1, "ioctl: KIOENABLE"); + read(-1, NULL, 0); + if (ioctl(fd, KIODISABLE) == -1) + err(1, "ioctl: KIODISABLE"); + + for (i = 0; i < cover[0]; i++) + printf("%p\en", (void *)cover[i + 1]); + + if (munmap(cover, size * sizeof(unsigned long)) == -1) + err(1, "munmap"); + close(fd); + + return 0; +} +.Ed +.Sh SEE ALSO +.Xr files.conf 5 , +.Xr kcov_remote_register 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Anton Lindqvist Aq Mt anton@openbsd.org . +.Sh CAVEATS +The +.Nm +driver is limited to architectures using +.Xr clang 1 +as their default compiler. diff --git a/static/openbsd/man4/km.4 b/static/openbsd/man4/km.4 new file mode 100644 index 00000000..992183ad --- /dev/null +++ b/static/openbsd/man4/km.4 @@ -0,0 +1,77 @@ +.\" $OpenBSD: km.4,v 1.11 2019/04/23 18:23:49 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Constantine A. Murenin +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 23 2019 $ +.Dt KM 4 +.Os +.Sh NAME +.Nm km +.Nd AMD K10 temperature sensor +.Sh SYNOPSIS +.Cd "km* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensors available in the +AMD Family 10h, 11h, 14h, 15h, and 16h processors. +.Pp +Each chip reports one temperature sensor. +Multiprocessor systems have one instance of +.Nm +per chip. +The highest resolution supported by the driver is 0.125 degC. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Rs +.%T "BIOS and Kernel Developer's Guide for AMD Family 10h Processors" +.%D March 26, 2008 +.%R Publication # 31116 +.%P pp. 236\(en237 and pp. 243\(en244 +.\" .%U http://support.amd.com/us/Processor_TechDocs/31116.pdf +.Re +.Rs +.%T "BIOS and Kernel Developer's Guide for AMD Family 11h Processors" +.%D July 07, 2008 +.%R Publication # 41256 +.%P pp. 156\(en157 and pp. 159\(en160 +.\" .%U http://support.amd.com/us/Processor_TechDocs/41256.pdf +.Re +.Rs +.%T "BIOS and Kernel Developer's Guide for AMD Family 14h Models 00h-04h Processors" +.%D May 02, 2011 +.%R Publication # 43170 +.%P pp. 277\(en278 and pp. 280\(en282 +.\" .%U http://support.amd.com/us/Processor_TechDocs/43170.pdf +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Constantine A. Murenin Aq Mt cnst@openbsd.org , +University of Waterloo. diff --git a/static/openbsd/man4/ksmn.4 b/static/openbsd/man4/ksmn.4 new file mode 100644 index 00000000..f236bffe --- /dev/null +++ b/static/openbsd/man4/ksmn.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: ksmn.4,v 1.1 2019/09/26 13:09:55 brynet Exp $ +.\" +.\" Copyright (c) 2019 Bryan Steele +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 26 2019 $ +.Dt KSMN 4 +.Os +.Sh NAME +.Nm ksmn +.Nd AMD F17 temperature sensor over SMN +.Sh SYNOPSIS +.Cd "ksmn* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor available in the +AMD Family 17h processors (Zen/Zen+/Zen2). +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bryan Steele Aq Mt brynet@openbsd.org diff --git a/static/openbsd/man4/kstat.4 b/static/openbsd/man4/kstat.4 new file mode 100644 index 00000000..f7bea1ee --- /dev/null +++ b/static/openbsd/man4/kstat.4 @@ -0,0 +1,210 @@ +.\" $OpenBSD: kstat.4,v 1.8 2022/01/14 04:25:57 dlg Exp $ +.\" +.\" Copyright (c) 2022 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 14 2022 $ +.Dt KSTAT 4 +.Os +.Sh NAME +.Nm kstat +.Nd kernel statistics +.Sh SYNOPSIS +.Cd "pseudo-device kstat" +.Sh DESCRIPTION +The +.Pa /dev/kstat +device exposes kernel statistics (kstats) to userland. +.Sh IOCTLS +The kstat +.Xr ioctl 2 +calls are provided in +.In sys/kstat.h . +.Pp +With the exception of +.Dv KSTATIOC_VERSION , +the kstat +.Xr ioctl 2 +calls use the +.Vt kstat_req +structure to request or enumerate kernel +statistic data from the kernel: +.Bd -literal +struct kstat_req { + unsigned int ks_rflags; +#define KSTATIOC_F_IGNVER (1 << 0) + /* the current version of the kstat subsystem */ + unsigned int ks_version; + + uint64_t ks_id; + + char ks_provider[KSTAT_STRLEN]; + unsigned int ks_instance; + char ks_name[KSTAT_STRLEN]; + unsigned int ks_unit; + + struct timespec ks_created; + struct timespec ks_updated; + struct timespec ks_interval; + unsigned int ks_type; + unsigned int ks_state; + + void *ks_data; + size_t ks_datalen; + unsigned int ks_dataver; +}; +.Ed +.Pp +The kstat subsystem increments a version number when a kstat is added to or +removed from the subsystem so changes to the set of kstats can be detected. +The current version can be requested with a +.Dv KSTATIOC_VERSION +.Xr ioctl 2 +call. +Programs requesting a kstat with the other +.Xr ioctl 2 +calls pass the current version in +.Va ks_version , +and if the version differs an error will be returned with +.Xr errno 2 +set to +.Dv EINVAL +to indicate that the program should resynchronise with the kernel +subsystem. +This check can be disabled by setting the +.Dv KSTATIOC_F_IGNVER +flag in +.Va ks_rflags . +.Pp +A kstat is identified by a 64bit number, or the combination of a +provider name, instance number, name, and unit number. +.Pp +Unless +.Va ks_data +is +.Dv NULL , +the kstat subsystem will request an update of the statistics data +and copy up to +.Va ks_datalen +bytes of it to the specified memory. +.Pp +The kstat +.Xr ioctl 2 +calls are as follows: +.Bl -tag -width Ds +.It Dv KSTATIOC_VERSION Fa "unsigned int" +Get the current version of the set of kernel statistics. +.It Dv KSTATIOC_FIND_ID Fa "struct kstat_req" +Request the kstat identified by +.Va ks_id . +.It Dv KSTATIOC_NFIND_ID Fa "struct kstat_req" +Request a kstat with an identifier greater than or equal to +.Va ks_id . +.It Dv KSTATIOC_FIND_PROVIDER Fa "struct kstat_req" +Request the kstat identified by +.Va ks_provider , +.Va ks_instance , +.Va ks_name , +and +.Va ks_unit . +.It Dv KSTATIOC_NFIND_PROVIDER Fa "struct kstat_req" +Request the kstat or next kstat from the set of kstats ordered by +.Va ks_provider , +.Va ks_instance , +.Va ks_name , +and +.Va ks_unit . +.It Dv KSTATIOC_FIND_NAME Fa "struct kstat_req" +Request the kstat identified by +.Va ks_name , +.Va ks_unit , +.Va ks_provider , +and +.Va ks_instance . +.It Dv KSTATIOC_NFIND_NAME Fa "struct kstat_req" +Request the kstat or next kstat from the set of kstats ordered by +.Va ks_name , +.Va ks_unit , +.Va ks_provider , +and +.Va ks_instance . +.El +.Pp +Upon the successful request of a kstat, the +.Nm +driver will update the +.Vt kstat_req +structure with current information about that kstat. +Updated fields include: +.Bl -tag -width Ds +.It Va ks_version +The current version of the kstat subsystem. +.It Va ks_id +The 64bit unique identifier for the requested kstat. +A kstat can be requested using this identifier and the +.Dv KSTATIOC_FIND_ID +.Xr ioctl 2 +call. +.It Va ks_provider , Va ks_instance , Va ks_name , Va ks_unit +The fully specified identifier of the kstat. +A kstat can be requested using these identifiers with the +.Dv KSTATIOC_FIND_NAME +and +.Dv KSTATIOC_FIND_PROVIDER +.Xr ioctl 2 +calls. +Groups of kstats with the same identifier or name can be enumerated +or requested with the +.Dv KSTATIOC_NFIND_NAME +and +.Dv KSTATIOC_NFIND_PROVIDER +.Xr ioctl 2 +calls without having to fetch the entire set of kstats and filtering +them. +.It Va ks_created +The system uptime when the kstat was created and added to the kstat +subsystem. +.It Va ks_updated +The system uptime at which the kstat data payload was last updated. +A kstat provider may update data when requested, or report when +data was last updated by some other process. +.Va ks_updated +can by used by a program to identify if data has been updated, or +for calculating rates of changes of values between updates. +.It Va ks_type +The type or structure of the data payload. +Currently supported types are documented in +.Xr kstat_create 9 . +.\" .It Va ks_state +.\" The state of the kstat. create or installed iirc +.It Va ks_datalen +The amount of data the kstat provides in bytes. +When requesting kstat data, the program specifies the amount of +space available at +.Va ks_data +by setting this variable. +.El +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/kstat +.El +.Sh SEE ALSO +.\".Xr kstat 1 , +.Xr kstat_create 9 , +.Xr kstat_kv_init 9 +.Sh HISTORY +The +.Nm +device appeared in +.Ox 6.8 . diff --git a/static/openbsd/man4/ksyms.4 b/static/openbsd/man4/ksyms.4 new file mode 100644 index 00000000..dbcb8143 --- /dev/null +++ b/static/openbsd/man4/ksyms.4 @@ -0,0 +1,91 @@ +.\" $OpenBSD: ksyms.4,v 1.15 2022/03/31 17:27:21 naddy Exp $ +.\" +.\" Copyright (c) 1998 Todd C. Miller +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt KSYMS 4 +.Os +.Sh NAME +.Nm ksyms +.Nd kernel symbol table device +.Sh SYNOPSIS +.Cd "pseudo-device ksyms" Op Ar count +.Sh DESCRIPTION +The +.Pa /dev/ksyms +device masquerades as an +.Ox +native executable with the symbols from the running kernel as its symbol segment. +Use of +.Pa /dev/ksyms +requires that the boot loader preserve the kernel symbols and place +them at the end of the kernel's address space. +.Pp +The +.Pa /dev/ksyms +device is used to look up the symbol table name list from the running +kernel. +Because it represents the running kernel, it is guaranteed +to always be up to date even if the kernel file has been changed (or +is even non-existent). +It is most useful when used in conjunction with +.Xr nlist 3 +or the +.Xr kvm 3 +routines (note that +.Xr kvm_open 3 +and +.Xr kvm_openfiles 3 +will try +.Pa /dev/ksyms +automatically if the first parameter to them is the +.Dv NULL +pointer). +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/ksyms +.El +.Sh ERRORS +An open of +.Pa /dev/ksyms +will fail if: +.Bl -tag -width Er +.It Bq Er EPERM +An open was attempted with write permissions. +.It Bq Er ENXIO +No kernel symbols were saved by the boot loader (usually because +they were removed with +.Xr strip 1 ) , +or the kernel has been compiled without a +.Dq pseudo-device ksyms +line. +.El +.Sh SEE ALSO +.Xr kvm 3 , +.Xr nlist 3 +.Sh HISTORY +The +.Pa /dev/ksyms +device appeared in +.Ox 2.4 . +.Sh BUGS +It is not possible to +.Xr mmap 2 +.Pa /dev/ksyms +because the boot loader does not load the symbol table onto a page +boundary (so it is not page aligned). +If all the boot loaders were fixed, +.Xr mmap 2 +support would be trivial. diff --git a/static/openbsd/man4/kubsan.4 b/static/openbsd/man4/kubsan.4 new file mode 100644 index 00000000..db3866d2 --- /dev/null +++ b/static/openbsd/man4/kubsan.4 @@ -0,0 +1,108 @@ +.\" $OpenBSD: kubsan.4,v 1.5 2024/09/06 13:31:59 mbuhl Exp $ +.\" +.\" Copyright (c) 2019 Anton Lindqvist +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: September 6 2024 $ +.Dt KUBSAN 4 +.Os +.Sh NAME +.Nm kubsan +.Nd kernel undefined behavior sanitizer +.Sh SYNOPSIS +.Cd option KUBSAN +.Sh DESCRIPTION +.Nm +detects undefined behavior at runtime inside the kernel. +Detected undefined behavior is printed to the system console, +including the offending line in the source code. +.Pp +By default, +.Nm +is not enabled but instead requires the following line to be present in the +kernel configuration: +.Bd -literal -offset indent +option KUBSAN +.Ed +.Pp +The following undefined behavior is detected: +.Bl -tag -width 4n +.It Float cast overflow +The conversion from a floating point to an integer cannot be represented by +the destination type. +.It Integer overflow +The result of an arithmetic computation on two integer operands cannot be +represented by the destination type. +.It Negate overflow +Negation of an integer cannot be represented by the destination type. +.It Pointer overflow +Pointer arithmetic overflow. +.It Out of bounds +Array indexing out of bounds, limited to cases where the size of the array +can be statically determined. +.It Shift out of bounds +Undefined logical shift caused by: +.Bl -dash +.It +The shift amount being negative. +.It +The shift operand being negative. +.It +The shift amount exceeds the number of bits as given by the shift operand +type. +.It +The result of the shift computation cannot be represented by the destination +type. +.El +.It Non-null argument +Passing +.Dv NULL +as the value for a function argument annotated with +.Dv __nonnull__ . +.It Invalid builtin +Passing zero to a compiler builtin where not allowed. +.It Invalid load +Loading a value that cannot be represented by the destination type. +.It Type mismatch +Mismatch between pointer and value type caused by: +.Bl -dash +.It +A pointer which does not fulfill the alignment requirements of the value type. +.It +A pointer to an address which lacks sufficient space to store the value type. +.El +.It Unreachable +Execution reached passed a function annotated with +.Dv __dead . +.El +.Sh SEE ALSO +.Xr options 4 +.Sh HISTORY +The +.Nm +implementation +is derived from +.Nx +and first appeared in +.Ox 6.5 . +.Sh AUTHORS +The +.Nm +implementation was written by +.An Anton Lindqvist Aq Mt anton@openbsd.org . +.Sh CAVEATS +The +.Nm +implementation is limited to architectures using +.Xr clang 1 +as their default compiler. diff --git a/static/openbsd/man4/kue.4 b/static/openbsd/man4/kue.4 new file mode 100644 index 00000000..40322e78 --- /dev/null +++ b/static/openbsd/man4/kue.4 @@ -0,0 +1,137 @@ +.\" $OpenBSD: kue.4,v 1.21 2013/07/16 16:05:49 schwarze Exp $ +.\" $NetBSD: kue.4,v 1.5 2000/03/20 01:34:22 augustss Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999, 2000 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/kue.4,v 1.2 2000/01/07 22:18:48 wpaul Exp $ +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt KUE 4 +.Os +.Sh NAME +.Nm kue +.Nd Kawasaki LSI KL5KUSB101B USB Ethernet device +.Sh SYNOPSIS +.Cd "kue* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Ethernet adapters based on the Kawasaki +LSI KL5KLUSB101B chipset. +This includes the following adapters: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Tn 3Com 3c19250 +.It Tn 3Com 3c460 HomeConnect +.It Tn AboCom Systems URE450 Ethernet +.It Tn ADS Technologies USB-10BT +.It Tn Aox USB101 +.It Tn Asante USB to Ethernet +.It Tn ATen DSB-650C +.It Tn ATen UC10T +.It Tn Corega USB-T +.It Tn D-Link DSB-650C +.It Tn Entrega NET-USB-E45 +.It Tn I/O Data USB-ET/T +.It Tn Jaton USB XpressNet +.It Tn Kawasaki USB101 +.It Tn Kingston Ethernet +.It Tn Linksys USB10T +.It Tn Mobility Ethernet +.It Tn Netgear EA101 +.It Tn Peracom USB +.It Tn Portgear Ethernet +.It Tn Portsmith Express Ethernet +.It Tn Psion Dacom Gold Port Ethernet +.It Tn Shark Pocket Adapter +.It Tn Silicom U2E +.It Tn SMC 2102USB +.It Tn SMC 2104USB +.El +.Pp +The KL5KLUSB101B supports a 128-entry multicast filter, single perfect +filter entry for the station address and promiscuous mode. +Packets are +received and transmitted over separate USB bulk transfer endpoints. +.Pp +The Kawasaki adapter supports only 10Mbps half-duplex mode, hence there +are no +.Xr ifmedia 4 +modes to select. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh FILES +The driver needs a firmware file, +which is loaded on demand when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/kue +.El +.Sh DIAGNOSTICS +.Bl -diag +.It "kue0: watchdog timeout" +A packet was queued for transmission and a transmit command was +issued, however the device failed to acknowledge the transmission +before a timeout expired. +.It "kue0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 4.0 . +.Ox +support was added in +.Ox 2.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ee.columbia.edu +and ported to +.Ox +by +.An Aaron Campbell Aq Mt aaron@openbsd.org . +.Sh BUGS +The +.Nm +driver does not accumulate Ethernet collisions statistics because the +Kawasaki firmware does not appear to maintain any internal statistics. diff --git a/static/openbsd/man4/lc.4 b/static/openbsd/man4/lc.4 new file mode 100644 index 00000000..16c30ea0 --- /dev/null +++ b/static/openbsd/man4/lc.4 @@ -0,0 +1,84 @@ +.\" $OpenBSD: lc.4,v 1.13 2013/07/16 16:05:49 schwarze Exp $ +.\" $NetBSD: lc.4,v 1.4 1999/12/15 22:07:32 abs Exp $ +.\" +.\" Copyright (c) 1997 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt LC 4 +.Os +.Sh NAME +.Nm lc +.Nd DEC EtherWORKS III 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "lc0 at isa? port 0x200" +.Cd "lc1 at isa? port 0x280" +.Sh DESCRIPTION +The +.Nm +device driver supports DEC EtherWORKS III Ethernet interfaces, which +are based on the LEMAC Ethernet chip. +This includes the DE203, DE204, and DE205. +.Sh MEDIA SELECTION +The EtherWORKS III series supports various combinations of media, depending +on model. +Some models also support media autoselect. +Media is selected with +.Xr ifconfig 8 Ns 's +.Sq media +directive. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx 1.3 , +.Ox +support was added in +.Ox 3.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Matt Thomas Aq Mt matt@netbsd.org +and ported to +.Ox +by +.An Niklas Hallqvist Aq Mt niklas@openbsd.org +.Sh BUGS +The +.Nm +does not currently support EISA LEMAC interfaces. diff --git a/static/openbsd/man4/lge.4 b/static/openbsd/man4/lge.4 new file mode 100644 index 00000000..4fd8a198 --- /dev/null +++ b/static/openbsd/man4/lge.4 @@ -0,0 +1,135 @@ +.\" $OpenBSD: lge.4,v 1.29 2022/02/18 10:24:32 jsg Exp $ +.\" Copyright (c) 2001 Wind River Systems +.\" Copyright (c) 1997, 1998, 1999, 2000, 2001 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/lge.4,v 1.3 2001/07/06 08:34:13 ru Exp $ +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt LGE 4 +.Os +.Sh NAME +.Nm lge +.Nd Level 1 LXT1001 NetCellerator PCI 1Gb Ethernet device +.Sh SYNOPSIS +.Cd "lge* at pci?" +.Cd "xmphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various NICs based on the Level 1 LXT1001 +NetCellerator Gigabit Ethernet controller chip, including the +following: +.Pp +.Bl -bullet -compact +.It +Allied Telesis CentreCOM LA1000-PCI-SX +.It +D-Link DGE-500SX +.It +SMC TigerCard 1000 (SMC9462SX) +.El +.Pp +These NICs are capable of 1000Mbps speeds over fiber optic cable. +The LXT1001 also supports a GMII port for use with 10/100/1000 copper +PHYs, however there aren't currently any NICs on the market that use +this feature. +.Pp +The LXT1001 supports IPv4 receive IP/TCP/UDP checksum offload +as well as a 64-bit multicast hash filter. +It also supports jumbo frames. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It Cm autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It Cm 1000baseSX +Set 1000baseSX operation over fiber optic cable. +Both +.Cm full-duplex +and +.Cm half-duplex +modes are supported. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It Cm full-duplex +Force full duplex operation. +.It Cm half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "lge0: can't map i/o space" +A fatal initialization error has occurred. +.It "lge0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "lge0: no memory for jumbo buffer queue!" +The driver failed to allocate memory for jumbo frames during +initialization. +.It "lge0: watchdog timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr xmphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T Level 1 LXT1001 Programming Manual +.%U https://people.freebsd.org/~wpaul/Level1/LXT1001SRM.pdf +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Bill Paul Aq Mt william.paul@windriver.com . diff --git a/static/openbsd/man4/lii.4 b/static/openbsd/man4/lii.4 new file mode 100644 index 00000000..d3ac7490 --- /dev/null +++ b/static/openbsd/man4/lii.4 @@ -0,0 +1,115 @@ +.\" $OpenBSD: lii.4,v 1.7 2011/01/27 02:18:31 kevlo Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 27 2011 $ +.Dt LII 4 +.Os +.Sh NAME +.Nm lii +.Nd Attansic L2 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "lii* at pci?" +.Cd "atphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Ethernet interfaces based on the Attansic L2 +Ethernet chipset. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width 100baseTX +.It Cm autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It Cm 10baseT +Set 10Mbps operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It Cm full-duplex +Force full duplex operation. +.It Cm half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by the card, try +.Ic ifconfig media . +For example, +.Ic ifconfig lii0 media . +.Sh SEE ALSO +.Xr arp 4 , +.Xr atphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Quentin Garnier . diff --git a/static/openbsd/man4/lisa.4 b/static/openbsd/man4/lisa.4 new file mode 100644 index 00000000..6f63cddb --- /dev/null +++ b/static/openbsd/man4/lisa.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: lisa.4,v 1.4 2018/01/12 04:36:44 deraadt Exp $ +.\" +.\" Copyright (c) 2009 Constantine A. Murenin +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 12 2018 $ +.Dt LISA 4 +.Os +.Sh NAME +.Nm lisa +.Nd STMicroelectronics LIS331DL MEMS motion sensor +.Sh SYNOPSIS +.Cd "lisa* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ST LIS331DL +3-axis digital output accelerometer. +A total of 3 sensors are provided, one for each axis +(X, Y and Z). +Each reading from LIS331DL is represented by an +8-bit 2's complement number. +.Pp +Sensor values are made available through the +.Dv HW_SENSORS +.Xr sysctl 2 +interface, +and can be monitored with the +.Xr systat 1 +.Ar sensors +view, +.Xr sensorsd 8 +and +.Xr sysctl 8 +.Ar hw.sensors . +.Sh SEE ALSO +.Xr systat 1 , +.Xr sysctl 2 , +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Rs +.%T LIS331DL MEMS motion sensor +.%N Rev 3 +.%D April 2008 +.%I STMicroelectronics +.\" .%U http://www.stm.com/stonline/products/literature/ds/13951.pdf +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Constantine A. Murenin Aq Mt cnst@openbsd.org , +University of Waterloo. diff --git a/static/openbsd/man4/lm.4 b/static/openbsd/man4/lm.4 new file mode 100644 index 00000000..73d8212b --- /dev/null +++ b/static/openbsd/man4/lm.4 @@ -0,0 +1,147 @@ +.\" $OpenBSD: lm.4,v 1.26 2019/12/17 01:34:59 mortimer Exp $ +.\" $NetBSD: lm.4,v 1.11 2001/09/22 01:22:49 wiz Exp $ +.\" +.\" Copyright (c) 2000 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Bill Squier. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 17 2019 $ +.Dt LM 4 +.Os +.Sh NAME +.Nm lm +.Nd National Semiconductor LM78/79/81 temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "lm0 at isa? port 0x290" +.Cd "lm1 at isa? port 0x280" +.Cd "lm2 at isa? port 0x310" +.\" .Cd "lm0 at pnpbios0" +.Cd "lm* at iic?" +.Cd "lm* at wbsio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +National Semiconductor LM78/79/81 +hardware monitors and register compatible chips to be used with the +.Xr sysctl 8 +interface. +.Pp +The original LM78 hardware monitor supports 11 sensors: +.Bl -column "Sensor" "Units" "Typical" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical Use" +.It Li "IN0" Ta "uV DC" Ta "Core voltage" +.It Li "IN1" Ta "uV DC" Ta "Unknown" +.It Li "IN2" Ta "uV DC" Ta "+3.3V" +.It Li "IN3" Ta "uV DC" Ta "+5V" +.It Li "IN4" Ta "uV DC" Ta "+12V" +.It Li "IN5" Ta "uV DC" Ta "-12V" +.It Li "IN6" Ta "uV DC" Ta "-5V" +.It Li "Temp" Ta "uK" Ta "Motherboard Temperature" +.It Li "Fan0" Ta "RPM" Ta "Fan" +.It Li "Fan1" Ta "RPM" Ta "Chassis Fan" +.It Li "Fan2" Ta "RPM" Ta "Fan" +.El +.Pp +For other devices, sensors' names and numbers will be different. +.Sh HARDWARE +Chips supported by the +.Nm +driver include: +.Pp +.Bl -dash -offset indent -compact +.It +ASUS AS99127F +.It +National Semiconductor LM78 and LM78-J +.It +National Semiconductor LM79 +.It +National Semiconductor LM81 +.It +Nuvoton NCT6775F, NCT6776F, NCT6779D, NCT6791D, NCT6792D, NCT6793D, NCT6795D +.It +Winbond W83627HF, W83627THF, W83637HF and W83697HF +.It +Winbond W83627DHG, W83627UHG and W83627EHF +.It +Winbond W83781D, W83782D and W83783S +.It +Winbond W83791D, W83791SD and W83792D +.El +.Pp +Some devices can attach to both +.Xr iic 4 +and +.Xr isa 4 ; +others can only attach to either one or the other. +If the +.Nm +driver detects a device attaching to both +.Xr iic 4 +and +.Xr isa 4 , +it will detach the device from +.Xr iic 4 . +.Sh SEE ALSO +.Xr iic 4 , +.Xr isa 4 , +.Xr wbsio 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx 1.5 ; +.Ox +support was added in +.Ox 3.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Squier +and ported to +.Ox 3.4 +by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . +The driver was largely rewritten for +.Ox 3.9 +by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +.Sh CAVEATS +Some vendors connect these chips to non-standard thermal diodes and +resistors. +This will result in bogus sensor values. +.Sh BUGS +Interrupt support is unimplemented. +.Pp +There are currently no known pnpbios IDs assigned to LM chips. +.Pp +This driver attaches to the Winbond W83791SD chip even though that +chip does not have any sensors. diff --git a/static/openbsd/man4/lmenv.4 b/static/openbsd/man4/lmenv.4 new file mode 100644 index 00000000..20b9b866 --- /dev/null +++ b/static/openbsd/man4/lmenv.4 @@ -0,0 +1,62 @@ +.\" $OpenBSD: lmenv.4,v 1.13 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt LMENV 4 +.Os +.Sh NAME +.Nm lmenv +.Nd National Semiconductor LM87 temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "lmenv* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the National Semiconductor LM87, +National Semiconductor LM81, Analog Devices ADM9240, and +Dallas Semiconductor 1780 temperature sensors. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface: +.Bd -literal -offset indent +$ sysctl hw.sensors.lmenv0 +hw.sensors.lmenv0.temp0=-128.00 degC (External) +hw.sensors.lmenv0.temp1=29.00 degC (Internal) +hw.sensors.lmenv0.fan0=3220 RPM +hw.sensors.lmenv0.volt0=2.62 V DC (+2.5Vin) +hw.sensors.lmenv0.volt1=1.49 V DC (Vccp) +hw.sensors.lmenv0.volt2=3.28 V DC (+Vcc) +hw.sensors.lmenv0.volt3=5.03 V DC (+5Vin/Vcc) +hw.sensors.lmenv0.volt4=12.00 V DC (+12Vin) +hw.sensors.lmenv0.volt5=1.20 V DC (Vccp) +.Ed +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/lmn.4 b/static/openbsd/man4/lmn.4 new file mode 100644 index 00000000..dae40791 --- /dev/null +++ b/static/openbsd/man4/lmn.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: lmn.4,v 1.5 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2007 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt LMN 4 +.Os +.Sh NAME +.Nm lmn +.Nd National Semiconductor LM93 temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "lmn* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the National Semiconductor LM93 +sensors. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/lmtemp.4 b/static/openbsd/man4/lmtemp.4 new file mode 100644 index 00000000..f69e3da5 --- /dev/null +++ b/static/openbsd/man4/lmtemp.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: lmtemp.4,v 1.13 2008/04/15 20:52:58 deraadt Exp $ +.\" +.\" Copyright (c) 2004 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 15 2008 $ +.Dt LMTEMP 4 +.Os +.Sh NAME +.Nm lmtemp +.Nd National Semiconductor LM75/LM76/LM77 temperature sensor +.Sh SYNOPSIS +.Cd "lmtemp* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the National Semiconductor LM75, +National Semiconductor LM76, National Semiconductor LM77, +Dallas Semiconductor 1775, and Philips Semiconductor LM75A +temperature sensors. +The sensor possesses a single temperature value that can be accessed +through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.6 . diff --git a/static/openbsd/man4/lo.4 b/static/openbsd/man4/lo.4 new file mode 100644 index 00000000..f86c55e3 --- /dev/null +++ b/static/openbsd/man4/lo.4 @@ -0,0 +1,85 @@ +.\" $OpenBSD: lo.4,v 1.29 2018/04/29 11:49:38 schwarze Exp $ +.\" $NetBSD: lo.4,v 1.3 1994/11/30 16:22:23 jtc Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)lo.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: April 29 2018 $ +.Dt LO 4 +.Os +.Sh NAME +.Nm lo +.Nd software loopback network interface +.Sh SYNOPSIS +.Cd "pseudo-device loop" +.Sh DESCRIPTION +The +.Nm loop +interface is a software loopback mechanism which may be +used for performance analysis, software testing, and/or local +communication. +.Pp +A +.Nm loop +interface can be created at runtime using the +.Ic ifconfig lo Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The +.Nm lo0 +interface will always exist and cannot be destroyed using +.Xr ifconfig 8 . +.Pp +As with other network interfaces, the loopback interface must have +network addresses assigned for each address family with which it is to be used. +These addresses +may be set or changed with the +.Dv SIOCSIFADDR +.Xr ioctl 2 . +.Sh DIAGNOSTICS +.Bl -diag +.It lo0: can't handle afX. +The interface was handed +a message with addresses formatted in an unsuitable address +family; the packet was dropped. +.El +.Sh SEE ALSO +.Xr inet 4 , +.Xr inet6 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh HISTORY +The +.Nm +device appeared in +.Bx 4.2 . diff --git a/static/openbsd/man4/lpt.4 b/static/openbsd/man4/lpt.4 new file mode 100644 index 00000000..eae4dfd5 --- /dev/null +++ b/static/openbsd/man4/lpt.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: lpt.4,v 1.8 2017/07/07 09:15:59 fcambus Exp $ +.\" +.\" Copyright (c) 1993 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christopher G. Demetriou. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 7 2017 $ +.Dt LPT 4 +.Os +.Sh NAME +.Nm lpt +.Nd parallel port driver +.Sh SYNOPSIS +.Cd "# alpha" +.Cd "lpt* at isa? port 0x3bc irq 7" +.Pp +.Cd "# amd64" +.Cd "lpt0 at isa? port 0x378 irq 7" +.Cd "lpt* at puc?" +.Pp +.Cd "# i386" +.Cd "lpt0 at isa? port 0x378 irq 7" +.Cd "lpt1 at isa? port 0x278" +.Cd "lpt2 at isa? port 0x3bc" +.Cd "lpt* at puc?" +.Pp +.Cd "# hppa" +.Cd "lpt0 at gsc? irq 7" +.Cd "lpt0 at ssio?" +.Pp +.Cd "# sparc64" +.Cd "lpt* at apio?" +.Cd "lpt* at ebus?" +.Sh DESCRIPTION +This driver provides access to parallel ports. +.Pp +The highest bit in the minor (bit 7, or add 128) number selects +whether to do polling or wait for interrupts. +If no IRQ is specified in the kernel configuration, or the IRQ specified is +not available at attach time, only the polling device may be used. +.Pp +The next lower bit (bit 6, or add 64) indicates the driver should +avoid initializing the printer. +.Pp +The next lower bit (bit 5, or add 32) requests that the driver do +automatic LF generation when printing CRs. +.Sh FILES +.Bl -tag -width /dev/lpt0 -compact +.It Pa /dev/lpt0 +first interrupt-driven parallel port device +.It Pa /dev/lpa0 +first polled parallel port device +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr ulpt 4 diff --git a/static/openbsd/man4/luphy.4 b/static/openbsd/man4/luphy.4 new file mode 100644 index 00000000..d01b1408 --- /dev/null +++ b/static/openbsd/man4/luphy.4 @@ -0,0 +1,33 @@ +.\" $OpenBSD: luphy.4,v 1.5 2009/07/31 14:20:29 jmc Exp $ +.\" +.\" Copyright (c) 2005 Brad Smith +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 31 2009 $ +.Dt LUPHY 4 +.Os +.Sh NAME +.Nm luphy +.Nd Lucent Technologies LU6612 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "luphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Lucent Technologies LU6612 10/100 Ethernet PHY. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/lxtphy.4 b/static/openbsd/man4/lxtphy.4 new file mode 100644 index 00000000..1fa7c8d7 --- /dev/null +++ b/static/openbsd/man4/lxtphy.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: lxtphy.4,v 1.11 2020/01/24 05:08:02 jsg Exp $ +.\" $NetBSD: lxtphy.4,v 1.1 1998/11/04 05:53:59 thorpej Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 24 2020 $ +.Dt LXTPHY 4 +.Os +.Sh NAME +.Nm lxtphy +.Nd Level One LXT-970/971 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "lxtphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Level One LXT-970, LXT-970A and LXT-971 10/100 Ethernet +PHYs. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/maestro.4 b/static/openbsd/man4/maestro.4 new file mode 100644 index 00000000..28af136e --- /dev/null +++ b/static/openbsd/man4/maestro.4 @@ -0,0 +1,77 @@ +.\" $OpenBSD: maestro.4,v 1.16 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 2001 Marc Espie. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt MAESTRO 4 +.Os +.Sh NAME +.Nm maestro +.Nd ESS Maestro 1 and 2 audio device +.Sh SYNOPSIS +.Cd "maestro* at pci?" +.Cd "audio* at maestro?" +.Sh DESCRIPTION +The +.Nm +driver supports ESS maestro 1, 2 and 2E, including OEM products that +identify as NEC Versa, or NEC VersaProNX VA26D, as long as they use +an AC'97 compliant codec, which is always the case, except for very +early models. +It does not support maestro 3 cards, which are entirely different and +supported by the +.Xr esa 4 +driver. +.Pp +Maestro cards have direct support for 16 bit signed little-endian +mono and stereo, 8 bit signed and unsigned mono and stereo. +Other encodings are emulated in software. +Sampling range is 4000 - 48000 Hz, with roughly a 2 Hz resolution. +.Pp +Maestro cards have some DSP and Dolby Digital 5.1 hardware, but this driver +does not support it. +.Pp +Other functions of maestro cards (modem, joystick) are not supported. +.Pp +PCI interrupt sharing works, as long as other devices comply too. +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr esa 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +Maestro hardware information was gleaned from the +.Fx +and Linux OSS drivers. +.Sh AUTHORS +.An -nosplit +.An David Leonard +and +.An Marc Espie . +.Sh BUGS +Very old cards with a PT101 mixer component should have partial support, e.g., +the mixer does not work. +.Pp +Recording should work soon. diff --git a/static/openbsd/man4/mainbus.4 b/static/openbsd/man4/mainbus.4 new file mode 100644 index 00000000..fc5e57f1 --- /dev/null +++ b/static/openbsd/man4/mainbus.4 @@ -0,0 +1,36 @@ +.\" $OpenBSD: mainbus.4,v 1.2 2007/05/31 19:19:50 jmc Exp $ +.\" +.\" Copyright (c) 2006 Jason McIntyre +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt MAINBUS 4 +.Os +.Sh NAME +.Nm mainbus +.Nd device tree root +.Sh SYNOPSIS +.Cd "mainbus0 at root" +.Sh DESCRIPTION +.Nm +provides an abstraction for all system buses to attach to. +It is the start of the device tree and always attached. +It is not a physical device as such, +but an abstraction to which other devices may attach. +.Pp +The actual buses which attach are largely machine-dependent; +refer to the individual man pages for more information. +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr intro 4 diff --git a/static/openbsd/man4/malo.4 b/static/openbsd/man4/malo.4 new file mode 100644 index 00000000..b5aa8277 --- /dev/null +++ b/static/openbsd/man4/malo.4 @@ -0,0 +1,168 @@ +.\" $OpenBSD: malo.4,v 1.54 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in +.\" the documentation and/or other materials provided with the +.\" distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +.\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE +.\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT +.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt MALO 4 +.Os +.Sh NAME +.Nm malo +.Nd Marvell Libertas IEEE 802.11b/g wireless network device +.Sh SYNOPSIS +.Cd "malo* at cardbus?" +.Cd "malo* at pci?" +.Cd "malo* at pcmcia?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Marvell Libertas 88W8335/88W8310/88W8385 based +PCI/CardBus/PCMCIA network adapters. +The second generation 88W8335/88W8310 chipsets support 802.11b/g. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver relies on the software 802.11 stack for both encryption and decryption +of data frames. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs a set of firmware files which are loaded when +an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/malo8335-h +.It Pa /etc/firmware/malo8335-m +.It Pa /etc/firmware/malo8338 +.It Pa /etc/firmware/malo8385-h +.It Pa /etc/firmware/malo8385-m +.El +.Pp +These firmware files are not free because Marvell refuses +to grant distribution rights. +As a result, even though +.Ox +includes the driver, the firmware files cannot be included and +users have to download these files on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh HARDWARE +The following cards are among those supported by the +.Nm +driver: +.Bl -column "I-O DATA WN-G54/CF" "88W8385" "CardBus" "Standard" -offset 6n +.It Em Card Ta Em Chip Ta Em Bus Ta Em Standard +.It "Ambicom WL54CF" Ta 88W8385 Ta PCMCIA Ta b/g +.It "I-O DATA WN-G54/CF" Ta 88W8385 Ta PCMCIA Ta b/g +.It "Netgear WG511v2" Ta 88W8310 Ta CardBus Ta b/g +.It "Netgear WG311v3" Ta 88W8335 Ta PCI Ta b/g +.It "SparkLAN WCFM-100" Ta 88W8385 Ta PCMCIA Ta b/g +.It "Tenda TWL541C" Ta 88W8310 Ta CardBus Ta b/g +.It "Tenda TWL542P" Ta 88W8335 Ta PCI Ta b/g +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig malo0 scan +.Pp +The following +.Xr hostname.if 5 +example configures malo0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr cardbus 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.\".Xr hostapd 8 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Claudio Jeker +and +.An Marcus Glocker . +.Sh CAVEATS +WPA encryption is not supported for PCMCIA devices. diff --git a/static/openbsd/man4/man4.alpha/Makefile b/static/openbsd/man4/man4.alpha/Makefile new file mode 100644 index 00000000..624cb54e --- /dev/null +++ b/static/openbsd/man4/man4.alpha/Makefile @@ -0,0 +1,20 @@ +MAN = apecs.4 \ + asc.4 \ + autoconf.4 \ + bba.4 \ + cia.4 \ + intro.4 \ + ioasic.4 \ + irongate.4 \ + lca.4 \ + le.4 \ + mcbus.4 \ + mcpcia.4 \ + mem.4 \ + tcasic.4 \ + tga.4 \ + tsc.4 \ + tsciic.4 \ + zs.4 + +include ../../../mandoc.mk diff --git a/static/openbsd/man4/man4.alpha/apecs.4 b/static/openbsd/man4/man4.alpha/apecs.4 new file mode 100644 index 00000000..49fbefe3 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/apecs.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: apecs.4,v 1.4 2008/06/26 05:42:07 ray Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Gregory McGarry. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt APECS 4 alpha +.Os +.Sh NAME +.Nm apecs +.Nd DECchip 21072/21071 Core Logic chipset +.Sh SYNOPSIS +.Cd "apecs* at mainbus?" +.Cd "pci* at apecs?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the DECchip 21072/21071 Core Logic chipset +(PCI controller) found on the AlphaStation 200/250/255/400 systems, +EB64+-family systems, AlphaServer 800/1000A systems and AlphaServer +1000 systems. +.Sh SEE ALSO +.Xr intro 4 , +.\".Xr mainbus 4 , +.Xr pci 4 diff --git a/static/openbsd/man4/man4.alpha/asc.4 b/static/openbsd/man4/man4.alpha/asc.4 new file mode 100644 index 00000000..df2f26bc --- /dev/null +++ b/static/openbsd/man4/man4.alpha/asc.4 @@ -0,0 +1,29 @@ +.\" $OpenBSD: asc.4,v 1.7 2017/11/02 14:04:24 mpi Exp $ +.\" +.\" Copyright (c) 1998 The OpenBSD Project +.\" All rights reserved. +.\" +.\" +.Dd $Mdocdate: November 2 2017 $ +.Dt ASC 4 alpha +.Os +.Sh NAME +.Nm asc +.Nd NCR 53c[f]94 on-board or TURBOchannel SCSI controller +.Sh SYNOPSIS +.Cd "tcds* at tc?" +.Cd "asc* at tcds?" +.Cd "asc* at tc?" +.Sh DESCRIPTION +The +.Nm +is an on-board or TURBOchannel SCSI controller based on the +NCR 53c[f]94 chips, found on DEC 3000/[3456789]00 series Alpha workstations. +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 diff --git a/static/openbsd/man4/man4.alpha/autoconf.4 b/static/openbsd/man4/man4.alpha/autoconf.4 new file mode 100644 index 00000000..8be25108 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/autoconf.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: autoconf.4,v 1.5 2010/01/02 19:55:34 schwarze Exp $ +.\" +.\" Copyright (c) 1990, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)autoconf.4 8.1 (Berkeley) 6/9/93 +.\" +.Dd $Mdocdate: January 2 2010 $ +.Dt AUTOCONF 4 alpha +.Os +.Sh NAME +.Nm autoconf +.Nd diagnostics from the autoconfiguration code +.Sh DESCRIPTION +When +.Ox +bootstraps it probes the innards of the machine +on which it is running +and locates controllers, drives, and other devices, printing out +what it finds on the console. +This procedure is driven by a system configuration table which is processed by +.Xr config 8 +and compiled into each kernel. +Devices which exist in the machine but are not configured into the +kernel are usually not detected. +.Sh SEE ALSO +.Xr intro 4 , +.Xr boot_alpha 8 , +.Xr config 8 diff --git a/static/openbsd/man4/man4.alpha/bba.4 b/static/openbsd/man4/man4.alpha/bba.4 new file mode 100644 index 00000000..34fc0ffd --- /dev/null +++ b/static/openbsd/man4/man4.alpha/bba.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: bba.4,v 1.2 2011/09/05 06:59:08 jmc Exp $ +.\" $NetBSD: bba.4,v 1.7 2008/04/30 13:10:53 martin Exp $ +.\" +.\" Copyright (c) 2000 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 5 2011 $ +.Dt BBA 4 alpha +.Os +.Sh NAME +.Nm bba +.Nd IOASIC baseboard audio device driver +.Sh SYNOPSIS +.Cd "bba0 at ioasic?" +.Cd "audio* at bba?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the IOASIC baseboard audio found on +DEC 3000 systems. +The baseboard audio driver is based on the AMD 79c30 ISDN and audio interface. +The interface is only capable of playing and recording 8kHz mu-law audio. +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 +.\" .Xr ioasic 4 +.\" .Sh HISTORY +.\" The +.\" .Nm +.\" device driver appeared in +.\" .Nx 1.5 . +.\" The name for the driver was adopted from the same driver in ULTRIX. diff --git a/static/openbsd/man4/man4.alpha/cia.4 b/static/openbsd/man4/man4.alpha/cia.4 new file mode 100644 index 00000000..07f6d326 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/cia.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: cia.4,v 1.6 2015/09/10 15:16:43 schwarze Exp $ +.\" $NetBSD$ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Gregory McGarry. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt CIA 4 alpha +.Os +.Sh NAME +.Nm cia +.Nd DECchip 2117x Core Logic chipset +.Sh SYNOPSIS +.Cd "cia* at mainbus?" +.Cd "pci* at cia?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the DECchip 2117x Core Logic chipset (PCI +controller) found on the AlphaStation 500/600, AlphaServer 1000 and +AlphaServer 800/1000A systems. +.Sh SEE ALSO +.Xr intro 4 , +.\".Xr mainbus 4 , +.Xr pci 4 diff --git a/static/openbsd/man4/man4.alpha/intro.4 b/static/openbsd/man4/man4.alpha/intro.4 new file mode 100644 index 00000000..53e5a57c --- /dev/null +++ b/static/openbsd/man4/man4.alpha/intro.4 @@ -0,0 +1,420 @@ +.\" $OpenBSD: intro.4,v 1.46 2022/03/31 17:27:21 naddy Exp $ +.\" $NetBSD: intro.4,v 1.10 2003/05/06 07:44:54 wiz Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Gregory McGarry. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" `AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt INTRO 4 alpha +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the +Alpha +platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities in +the system probe for the device and, if found, enable the software support +for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +A list of the supported hardware and devices is given below. +.Sh SUPPORTED SYSTEMS +.Tn DEC +and +.Tn Compaq +have produced a series of the +.Tn Alpha +.Tn CPU , +some of which are listed below, along with some systems which contain them. +.Pp +.Qq EV +stands for +.Qq Extended VAX +.Po +or +.Qq Electro Vlassic +.Pc +and the number following is a reference to the +.Tn CMOS +process used to make the chips. +.Qq LCA +stands for Low Cost Alpha, and +.Qq PCA +stands for PC-architecture Alpha. +.Bl -hang -width 9n +.It 21064 +.Sy EV4 +.Po +100-200 +.Tn MHz , +0.75 micron +.Pc +.Pp +AlphaPC 64 +.Pq EB64 +.Bl -hang -width 4n +.It Avanti family +.br +Digital's lower-end PCI-based workstations. +.Pp +AlphaStation 200 4/100-166 +.Pq Mustang +.br +AlphaStation 400 4/166 +.Pq Chinet +.It Pelican family +.br +Low-end +.Tn TURBOchannel +based workstations. +.Pp +DEC 3000/300 +.Pq 150 Tn MHz +.Pq Pelican +.br +DEC 3000/300X +.Pq 175 Tn MHz +.Pq Pelican+ +.br +DEC 3000/300L +.Pq 100 Tn MHz +.Pq Pelica +.br +DEC 3000/300LX +.Pq 125 Tn MHz +.Pq Pelica+ +.It Sandpiper family +.br +High-end +.Tn TURBOchannel +based workstations. +.Pp +DEC 3000/400 +.Pq 133 Tn MHz +.Pq Sandpiper +.br +DEC 3000/600 +.Pq 175 Tn MHz +.Pq Sandpiper+ +.It Flamingo family +.br +High-end +.Tn TURBOchannel +based workstations. +.Pp +DEC 3000/500 +.Pq 150 Tn MHz +.Pq Flamingo +.br +DEC 3000/500X +.Pq 200 Tn MHz +.Pq Hot Pink +.br +DEC 3000/800 +.Pq 200 Tn MHz +.Pq Flamingo II +.El +.It 21064-A +.Sy EV45 +.Po +225-333 +.Tn MHz , +0.50 micron +.Pc +.Pp +DEC 3000/700 +.Pq 225 Tn MHz +.Pq Sandpiper45 +.br +DEC 3000/900 +.Pq 275 Tn MHz +.Pq Flamingo45 +.Bl -hang -width 4n +.It Avanti family +.br +Digital's lower-end PCI-based workstations. +.Pp +AlphaStation 200 4/233 +.Pq Mustang+ +.br +AlphaStation 205 4/133-333 +.Pq LX3 +.br +AlphaStation 250 4/300 +.Pq M3+ +.br +AlphaStation 255 4/133-333 +.Pq LX3+ +.br +AlphaStation 300 4/266 +.Pq Melmac +.br +AlphaStation 400 4/233-300 +.Pq Avanti +.El +.It 21066 +.Sy LCA4 +.Po +166-233 +.Tn MHz , +0.75 micron +.Pc +.Bl -hang -width 4n +.It NoName family +.br +Digital's lowest-end family of PCI-based systems. +.Pp +DEC AXPpci33 +.Pq NoName +.br +Universal Desktop Box AXPpci166MT +.Pq UDB/Multia +.El +.Pp +21066 evaluation motherboard +.Pq EB66 +.It 21066-A +.Sy LCA45 +.Po +233 +.Tn MHz , +0.50 micron +.Pc +.Pp +21066-A evaluation motherboard +.Pq EB66+ +.It 21068 +.Sy LCA4s +.Po +66-233 +.Tn MHz , +0.75 micron +.Pc +.Pp +Universal Desktop Box AXPpci233MT +.Pq UDB/Multia +.It 21164 +.Sy EV5 +.Po +250-366 +.Tn MHz , +0.50 micron +.Pc +.Bl -hang -width 4n +.It Mikasa family +.br +AlphaServer 1000 5/300 +.Pq Pinnacle +.It Noritake family +.br +AlphaServer 1000A 5/300 +.Pq Pinnacle +.Pp +21164 evaluation motherboard +.Pq EB164 +.El +.It 21164-A +.Sy EV56 +.Po +400-766 +.Tn MHz , +0.35 micron, BWX +.Pc +.Bl -hang -width 4n +.It Personal Workstation Pq PWS +.br +PWS 433a/433au +.Pq Miata +.br +PWS 500a/500au +.Pq Miata +.br +PWS 600a/600au +.Pq Miata +.It Mikasa family +.br +AlphaServer 1000 5/333-500 +.Pq Primo +.It Noritake family +.br +AlphaServer 1000A 5/333-500 +.Pq Primo +.br +AlphaServer 800 5/333-500 +.Pq Corelle +.It EB164 family +.br +AlphaPC 164 motherboard +.Pq EB164 +.br +AlphaPC 164LX motherboard +.Pq EB164 +.El +.Pp +DigitalServer 3300 +.Po +rebadged AlphaServer 800 for NT +.Pc +.It 21164-PC +.Sy PCA56 +.Po +400-600 +.Tn MHz , +0.35 micron, MVI, no L2 cache +.Pc +.Pp +AlphaPC 164SX motherboard +.Pq EB164 +.Pp +PWS 466au +.Pq Miata +.br +PWS 550au +.Pq Miata +.It 21264 +.Sy EV6 +.Po +450-600 +.Tn MHz , +0.35 micron +.Pc +.Pp +APi UP1000 and UP1100; +AMD 751-based EV6 systems. +.Pp +264DP, XP1000, DS10, DS20 +Tsunami-based systems. +.It 21264-A +.Sy EV67 +.Po +600-833 +.Tn MHz , +0.28 micron +.Pc +.El +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width "cardbus(4)XX" -offset 3n -compact +.It Xr eisa 4 +introduction to EISA bus support +.It Xr iic 4 +Inter IC (I2C) bus +.It Xr isa 4 +introduction to ISA bus support +.It Xr onewire 4 +1-Wire bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr usb 4 +introduction to Universal Serial Bus support +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The +Alpha +.Nm intro +first appeared in +.Ox 2.3 . diff --git a/static/openbsd/man4/man4.alpha/ioasic.4 b/static/openbsd/man4/man4.alpha/ioasic.4 new file mode 100644 index 00000000..e5ca23a2 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/ioasic.4 @@ -0,0 +1,87 @@ +.\" $OpenBSD: ioasic.4,v 1.2 2017/11/02 15:37:58 jmc Exp $ +.\" $NetBSD: ioasic.4,v 1.4 2004/05/11 22:42:47 wiz Exp $ +.\" +.\" Copyright (c) 1996, 1997 Jonathan Stone. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Jonathan Stone. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 2 2017 $ +.Dt IOASIC 4 alpha +.Os +.Sh NAME +.Nm ioasic +.Nd +baseboard IO control ASIC for DEC TURBOchannel systems +.Sh SYNOPSIS +.Cd "ioasic0 at tc? slot ? offset ?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the DEC proprietary IOCTL ASIC found on +DEC 3000 TURBOchannel machines. +.Pp +The +.Nm +provides hardware DMA channels and interrupt support for several +baseboard devices, including one +.Xr asc 4 +SCSI device with a scatter/gather DMA channel, an mc146818-compatible +.Nm mcclock , +an Am7930 audio device +.Xr bba 4 , +two +.Xr zs 4 +dual-port serial devices, and an AMD 7990 LANCE +.Xr le 4 +Ethernet interface. +.Pp +The +.Nm +is also used for the audio/ISDN hardware on +audio-equipped TURBOchannel Alphas, +where the +.Nm +hardware provides a scatter-gather DMA channel between the 16-bit +device and the 32-bit +.Nm tc +DMA address space. +.Pp +Support for scatter-gather DMA eliminates the need for additional copying. +.Sh SEE ALSO +.Xr asc 4 , +.Xr bba 4 , +.Xr intro 4 , +.Xr le 4 , +.Xr zs 4 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Nx 1.1 , +derived from DECstation boot-time configuration code in +.Bx 4.4 . diff --git a/static/openbsd/man4/man4.alpha/irongate.4 b/static/openbsd/man4/man4.alpha/irongate.4 new file mode 100644 index 00000000..4d7b36f7 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/irongate.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: irongate.4,v 1.6 2015/09/10 15:16:43 schwarze Exp $ +.\" $NetBSD$ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Gregory McGarry. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt IRONGATE 4 alpha +.Os +.Sh NAME +.Nm irongate +.Nd API UP1000 AMD751 Core Logic + AGP Chipset +.Sh SYNOPSIS +.Cd "irongate* at mainbus?" +.Cd "pci* at irongate?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the AMD751 Core Logic + AGP Chipset found on +Alpha Processor, Inc.'s UP1000 systems. +.Sh SEE ALSO +.Xr intro 4 , +.\".Xr mainbus 4 , +.Xr pci 4 diff --git a/static/openbsd/man4/man4.alpha/lca.4 b/static/openbsd/man4/man4.alpha/lca.4 new file mode 100644 index 00000000..6bcf1cb8 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/lca.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: lca.4,v 1.6 2015/09/10 15:16:43 schwarze Exp $ +.\" $NetBSD$ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Gregory McGarry. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt LCA 4 alpha +.Os +.Sh NAME +.Nm lca +.Nd DECchip 21066 Core Logic chipset +.Sh SYNOPSIS +.Cd "lca* at mainbus?" +.Cd "pci* at lca?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the DECchip 21066 Core Logic chipset. +.Sh SEE ALSO +.Xr intro 4 , +.\".Xr mainbus 4 , +.Xr pci 4 diff --git a/static/openbsd/man4/man4.alpha/le.4 b/static/openbsd/man4/man4.alpha/le.4 new file mode 100644 index 00000000..17c409a5 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/le.4 @@ -0,0 +1,28 @@ +.\" $OpenBSD: le.4,v 1.13 2007/05/31 19:19:53 jmc Exp $ +.\" +.\" Copyright (c) 1998 The OpenBSD Project +.\" All rights reserved. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt LE 4 alpha +.Os +.Sh NAME +.Nm le +.Nd AMD LANCE Ethernet device +.Sh SYNOPSIS +.Cd "le* at ioasic?" Pq "TURBOchannel Alphas" +.Cd "le* at tc?" Pq "TURBOchannel Alphas" +.Sh DESCRIPTION +The +.Nm +interface provides access to the Ethernet network via the +.Tn AMD +.Tn LANCE +Ethernet chip set. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/man4.alpha/mcbus.4 b/static/openbsd/man4/man4.alpha/mcbus.4 new file mode 100644 index 00000000..3b649a36 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/mcbus.4 @@ -0,0 +1,62 @@ +.\" $OpenBSD: mcbus.4,v 1.5 2015/11/21 08:04:20 jmc Exp $ +.\" $NetBSD: mcbus.4,v 1.1 2001/09/21 09:11:44 gmcgarry Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Gregory McGarry. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 21 2015 $ +.Dt MCBUS 4 alpha +.Os +.Sh NAME +.Nm mcbus , +.Nm mcmem +.Nd MCBUS system bus +.Sh SYNOPSIS +.Cd "mcbus* at mainbus0" +.Cd "mcmem* at mcbus? mid ?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the MCBUS system bus found on AlphaServer 4100 +and 1200 systems. +.Pp +The following devices are supported by the +.Nm +driver: +.Pp +.Bl -tag -width mcclock -offset indent -compact +.It mcmem +memory modules attached to the MCBUS main system bus. +.It mcpcia +MCPCIA MCBUS-to-PCI bus adapter +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr mainbus 4 , +.Xr mcpcia 4 +.Sh BUGS +Only one MCBUS bus can exist within the system. diff --git a/static/openbsd/man4/man4.alpha/mcpcia.4 b/static/openbsd/man4/man4.alpha/mcpcia.4 new file mode 100644 index 00000000..fa89dfb7 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/mcpcia.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: mcpcia.4,v 1.4 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: mcpcia.4,v 1.1 2001/09/21 09:11:44 gmcgarry Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Gregory McGarry. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt MCPCIA 4 alpha +.Os +.Sh NAME +.Nm mcpcia +.Nd MCPCIA MCBUS-to-PCI bus adapter +.Sh SYNOPSIS +.Cd "mcpcia* at mcbus? mid ?" +.Cd "pci* at mcpcia?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the MCPCIA MCBUS-to-PCI bus adapter found +on AlphaServer 4100 and 1200 systems. +.Sh SEE ALSO +.Xr intro 4 , +.Xr mcbus 4 , +.Xr pci 4 diff --git a/static/openbsd/man4/man4.alpha/mem.4 b/static/openbsd/man4/man4.alpha/mem.4 new file mode 100644 index 00000000..b526c575 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/mem.4 @@ -0,0 +1,85 @@ +.\" $OpenBSD: mem.4,v 1.7 2024/03/22 12:29:33 jsg Exp $ +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This software was developed by the Computer Systems Engineering group +.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and +.\" contributed to Berkeley. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)mem.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: March 22 2024 $ +.Dt MEM 4 alpha +.Os +.Sh NAME +.Nm mem , +.Nm kmem +.Nd memory files +.Sh DESCRIPTION +The file +.Pa /dev/mem +is an interface to the physical memory of the +computer. +Byte offsets in this file are interpreted as physical memory addresses. +Reading and writing this file is equivalent to reading and writing +memory itself. +An error will be returned if an attempt is made to reference +an offset outside of +.Pa /dev/mem . +.Pp +Kernel virtual memory is accessed via the file +.Pa /dev/kmem +in the same manner as +.Pa /dev/mem . +Only kernel virtual addresses that are currently mapped to memory are allowed. +.Pp +On the alpha, physical memory may be discontiguous; +kernel virtual memory begins at +.Li 0xfffffc0000230000 . +.Pp +Even with sufficient file system permissions, +these devices can only be opened when the +.Xr securelevel 7 +is insecure or when the +.Va kern.allowkmem +.Xr sysctl 2 +variable is set. +.Sh FILES +.Bl -tag -width /dev/kmem -compact +.It /dev/mem +.It /dev/kmem +.El +.Sh SEE ALSO +.Xr securelevel 7 +.Sh HISTORY +The +.Pa /dev/mem +file appeared in +.At v1 , +.Pa /dev/kmem +appeared in +.At v5 . diff --git a/static/openbsd/man4/man4.alpha/tcasic.4 b/static/openbsd/man4/man4.alpha/tcasic.4 new file mode 100644 index 00000000..2525e530 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/tcasic.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: tcasic.4,v 1.6 2015/09/10 15:16:43 schwarze Exp $ +.\" $NetBSD: tcasic.4,v 1.1 2001/09/21 09:11:44 gmcgarry Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Gregory McGarry. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt TCASIC 4 alpha +.Os +.Sh NAME +.Nm tcasic +.Nd TURBOchannel host bus support +.Sh SYNOPSIS +.Cd "tcasic* at mainbus0" +.Cd "tc* at tcasic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the TURBOchannel host bus on the baseboard +of the DEC 3000/300 and 3000/500 systems. +.Sh SEE ALSO +.Xr intro 4 +.\".Xr mainbus 4 , +.\".Xr tc 4 diff --git a/static/openbsd/man4/man4.alpha/tga.4 b/static/openbsd/man4/man4.alpha/tga.4 new file mode 100644 index 00000000..f02caa8b --- /dev/null +++ b/static/openbsd/man4/man4.alpha/tga.4 @@ -0,0 +1,74 @@ +.\" $OpenBSD: tga.4,v 1.13 2013/04/17 02:28:40 jsg Exp $ +.\" +.\" Copyright (c) 2001 Nathan L. Binkert +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 17 2013 $ +.Dt TGA 4 alpha +.Os +.Sh NAME +.Nm tga +.Nd DECchip 21030 (TGA) graphics driver +.Sh SYNOPSIS +.Cd "tga* at pci?" +.Cd "wsdisplay* at tga?" +.Sh DESCRIPTION +This driver handles DECchip 21030 (TGA) graphics hardware within the +.Xr wscons 4 +console framework. +.Pp +On TGA adapters, the resolution is set on the card and is not changed +at runtime. +On some TGA models, there are four DIP switches. +On other models, there is a rotary switch with positions 0-F. +There are also some that use jumpers. +.Ss TGA Switch Settings +.Bl -column "Setting" "Freq (MHz)" "Resolution" "Rate (MHz)" -offset indent +.It Sy Switch Ta Sy Pixel Ta Sy Monitor Ta Sy Refresh +.It Sy "Setting" Ta Sy "Freq (MHz)" Ta Sy "Resolution" Ta Sy "Rate (MHz)" +.It Li 0 Ta 130 Ta 1280x1024 Ta 72 +.It Li 1 Ta 119 Ta 1280x1024 Ta 66 +.It Li 2 Ta 108 Ta 1280x1024 Ta 60 +.It Li 3 Ta 104 Ta 1152x900 Ta 72 +.It Li 4 Ta 93 Ta 1152x900 Ta 66 +.It Li 5 Ta 75 Ta 1024x768 Ta 70 +.It Li 6 Ta 74 Ta 1024x768 Ta 72 +.It Li 7 Ta 69 Ta 1024x864 Ta 60 +.It Li 8 Ta 65 Ta 1024x768 Ta 60 +.It Li 9 Ta 50 Ta 800x600 Ta 72 +.It Li A Ta 40 Ta 800x600 Ta 60 +.It Li B Ta 32 Ta 640x480 Ta 72 +.It Li C Ta 25 Ta 640x480 Ta 60 +.El +.Pp +The settings for D, E, and F are for 1600x1200 on some cards, but +there are no guarantees. +.Pp +There are also a couple of extra jumpers on some cards. +One of these jumpers often selects the card to be the primary display. +Exactly one of the cards in your machine should have that jumper on. +If you have extra cards, they should have the jumper off. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 , +.Xr wsconscfg 8 +.Rs +.%T DECchip 21030 PCI Graphics Accelerator Reference Manual +.%N EC-N0683-72 +.Re +.Sh BUGS +There are some problems with the background randomly switching between +black and blue. diff --git a/static/openbsd/man4/man4.alpha/tsc.4 b/static/openbsd/man4/man4.alpha/tsc.4 new file mode 100644 index 00000000..10417583 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/tsc.4 @@ -0,0 +1,63 @@ +.\" $OpenBSD: tsc.4,v 1.10 2015/11/21 08:04:20 jmc Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Gregory McGarry. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 21 2015 $ +.Dt TSC 4 alpha +.Os +.Sh NAME +.Nm tsc , +.Nm tsp +.Nd DECchip 21272 and 21274 Core Logic chipset +.Sh SYNOPSIS +.Cd "tsc* at mainbus?" +.Cd "tsciic* at tsc?" +.Cd "tsp* at tsc?" +.Cd "pci* at tsp?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the DECchip 21272 (Tsunami) and +21274 (Titan) Core Logic chipsets found on most 21264-based +systems. +.Pp +The +.Nm tsp +driver attaches to it and provides support for the DECchip 21272 and 21274 +built-in PCI controller. +.Pp +DECchip 21272 provides one PCI bus, while DECchip 21274 provides two distinct +PCI buses, the second one with AGP capabilities. +.Sh SEE ALSO +.Xr intro 4 , +.\".Xr mainbus 4 , +.Xr pci 4 , +.Xr tsciic 4 +.Sh BUGS +The AGP capabilities of the second PCI bus of DECchip 21274 are not currently +supported. diff --git a/static/openbsd/man4/man4.alpha/tsciic.4 b/static/openbsd/man4/man4.alpha/tsciic.4 new file mode 100644 index 00000000..2d1379f8 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/tsciic.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: tsciic.4,v 1.1 2014/12/24 18:46:14 miod Exp $ +.\" $NetBSD: tsciic.4,v 1.1 2014/02/21 12:26:00 jdc Exp $ +.\" +.\" Copyright (c) 2013 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Julian Coleman +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 24 2014 $ +.Dt TSCIIC 4 alpha +.Os +.Sh NAME +.Nm tsciic +.Nd DECchip 21272 and 21274 Core Logic chipset I2C controller +.Sh SYNOPSIS +.Cd "tsciic* at tsc?" +.Cd "iic* at tsciic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the I2C controller on the DECchip 21272 and 21274 +Core Logic chipsets, on systems without remote management consoles. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr tsc 4 diff --git a/static/openbsd/man4/man4.alpha/zs.4 b/static/openbsd/man4/man4.alpha/zs.4 new file mode 100644 index 00000000..6861ace3 --- /dev/null +++ b/static/openbsd/man4/man4.alpha/zs.4 @@ -0,0 +1,108 @@ +.\" $OpenBSD: zs.4,v 1.2 2017/11/02 15:37:58 jmc Exp $ +.\" $NetBSD: zstty.4,v 1.14 2011/06/07 20:22:56 wiz Exp $ +.\" +.\" Copyright (c) 1997 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Gordon W. Ross. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 2 2017 $ +.Dt ZS 4 alpha +.Os +.Sh NAME +.Nm zs , +.\" .Nm zskbd , +.\" .Nm zsms , +.Nm zstty +.Nd Zilog 8530 (ZSCC) Serial Communications Controller +.Sh SYNOPSIS +.Cd "zs* at ioasic0" +.\" .Cd "lskbd* at zs1" +.\" .Cd "vsms* at zs0" +.Cd "zstty* at zs?" +.Sh DESCRIPTION +The +.Nm +driver provides TTY support for the two Zilog 8530 Dual UART chips found on +DEC 3000 systems. +On these systems, two of these serial interfaces are hardwired for use by the +keyboard and mouse. +Only the second interface of each +.Nm +controller can be used as a regular serial port. +.\" The +.\" .Nm lskbd +.\" devices connect keyboard devices to the generic keyboard driver +.\" .Nm wskbd . +.\" The +.\" .Nm vsms +.\" devices connect mice to the generic mouse driver +.\" .Xr wsmouse 4 . +The +.Nm zstty +interfaces provide RS-423 +and RS-232 serial ports for general purpose use. +.Pp +The +.Nm +driver supports all of the standard +.Xr tty 4 +ioctl calls. +The status of the DTR, RTS, CTS, and DCD signals can be queried with +the TIOCMGET command but, due to limitations in the hardware, +only the DTR and RTS signals can be modified with the TIOCMSET, TIOCMBIC, +and TIOCMBIS +.Xr ioctl 2 +commands. +.Pp +Input and output for each line may be set to any baud rate in the +range 50 to 38400. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/ttyB[01] +.It Pa /dev/cuaB[01] +.El +.Sh DIAGNOSTICS +.Bl -tag -width indent +.It zs*: fifo overflow +The on-chip +.Dq FIFO +has overflowed and incoming data has been lost. +This generally means the machine is not responding to +interrupts from the ZS chip fast enough, which can be +remedied only by using a lower baud rate. +.It zs*: ring overflow +The software input +.Qq ring +has overflowed. +This usually means input flow-control is not configured correctly +.Pq i.e. incorrect cable wiring . +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr ioasic 4 , +.Xr tty 4 +.\" .Xr wskbd 4 , +.\" .Xr wsmouse 4 diff --git a/static/openbsd/man4/man4.amd64/Makefile b/static/openbsd/man4/man4.amd64/Makefile new file mode 100644 index 00000000..ab1441b6 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/Makefile @@ -0,0 +1,19 @@ +MAN = amdpcib.4 \ + apm.4 \ + autoconf.4 \ + bios.4 \ + cpu.4 \ + efifb.4 \ + intro.4 \ + ioapic.4 \ + mem.4 \ + mpbios.4 \ + mtrr.4 \ + nvram.4 \ + pctr.4 \ + skgpio.4 \ + tcpcib.4 \ + vmm.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.amd64/amdpcib.4 b/static/openbsd/man4/man4.amd64/amdpcib.4 new file mode 100644 index 00000000..16fe36c3 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/amdpcib.4 @@ -0,0 +1,33 @@ +.\" $OpenBSD: amdpcib.4,v 1.3 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Marc Balmer, 2007. Public Domain. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt AMDPCIB 4 amd64 +.Os +.Sh NAME +.Nm amdpcib +.Nd AMD-8111 series LPC bridge and timecounter +.Sh SYNOPSIS +.Cd "amdpcib* at pci?" +.Cd "isa* at amdpcib?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the AMD-8111 LPC bridge and implements a +32/64-bit 14.3 MHz (or variable) timecounter using the HPET timer. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 , +.Xr watchdog 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Michael Shalayeff . diff --git a/static/openbsd/man4/man4.amd64/apm.4 b/static/openbsd/man4/man4.amd64/apm.4 new file mode 100644 index 00000000..8ace7400 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/apm.4 @@ -0,0 +1,167 @@ +.\" $OpenBSD: apm.4,v 1.10 2023/01/30 14:43:29 jcs Exp $ +.\" +.\" Copyright (c) 1998 Marco S. Hyman +.\" +.\" Permission to copy all or part of this material for any purpose is +.\" granted provided that the above copyright notice and this paragraph +.\" are duplicated in all copies. THIS SOFTWARE IS PROVIDED ``AS IS'' +.\" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT +.\" LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE. +.\" +.Dd $Mdocdate: January 30 2023 $ +.Dt APM 4 amd64 +.Os +.Sh NAME +.Nm apm +.Nd power management interface +.Sh SYNOPSIS +.Cd "acpi0 at mainbus?" +.Sh DESCRIPTION +The +.Nm +driver provides a user interface to the +.Xr acpi 4 +driver. +.Pp +The +.Nm +driver implements the following +.Xr ioctl 2 +calls. +They are defined in +.In machine/apmvar.h . +.Bl -tag -width Ds +.It Dv APM_IOC_REJECT +.Em Not implemented . DO NOT USE . +.It Dv APM_IOC_STANDBY +.Pq Li "no parameters" +Request +.Dq standby +mode. +.It Dv APM_IOC_SUSPEND +.Pq Li "no parameters" +Request +.Dq suspend +mode. +.It Dv APM_IOC_HIBERNATE +.Pq Li "no parameters" +Request +.Dq hibernate +mode. +.It Dv APM_IOC_GETPOWER +.Pq Li "struct apm_power_info" +Request the current power state. +The argument structure is as follows: +.Bd -literal -offset indent +struct apm_power_info { + u_char battery_state; + u_char ac_state; + u_char battery_life; + u_char spare1; + u_int minutes_left; + u_int spare2[6]; +}; +.Ed +.Pp +The following values are defined for +.Va battery_state : +.Bl -tag -width Ds +.It Dv APM_BATT_HIGH +Battery has a high state of charge. +.It Dv APM_BATT_LOW +Battery has a low state of charge. +.It Dv APM_BATT_CRITICAL +Battery has a critical state of charge. +.It Dv APM_BATT_CHARGING +Battery is not high, low, or critical and is currently charging. +.It Dv APM_BATT_UNKNOWN +Cannot read the current battery state. +.It Dv APM_BATTERY_ABSENT +No battery installed. +.El +.Pp +The following values are defined for +.Va ac_state : +.Bl -tag -width Ds +.It Dv APM_AC_OFF +External power not detected. +.It Dv APM_AC_ON +External power detected. +.It Dv APM_AC_BACKUP +Backup power in use. +.It Dv APM_AC_UNKNOWN +External power state unknown. +.El +.Pp +The +.Va battery_life +value contains the estimated percentage of battery life available. +100% indicates a full charge. +.Pp +The +.Va minutes_left +value contains the estimated number of minutes of battery life +remaining. +.It Dv APM_IOC_DEV_CTL +.Pq Li "struct apm_ctl" +Allows an application to directly set the +APM operating mode. +The argument structure is as follows: +.Bd -literal -offset indent +struct apm_ctl { + u_int dev; + u_int mode; +}; +.Ed +.Pp +.Va dev +indicates the device, typically +.Dv APM_DEV_ALLDEVS . +.Pp +.Va mode +indicates the desired operating mode. +Possible values are +.Bl -tag -width Ds -compact -offset indent +.It Dv APM_SYS_READY +.It Dv APM_SYS_STANDBY +.It Dv APM_SYS_SUSPEND +.It Dv APM_SYS_OFF +.It Dv APM_LASTREQ_INPROG +.It Dv APM_LASTREQ_REJECTED +.El +.It Dv APM_IOC_PRN_CTL +.Pq Li "int" +This +.Xr ioctl 2 +controls message output by the APM +driver when a power change event is detected. +The integer parameter is one of: +.Bl -tag -width Ds +.It Dv APM_PRINT_ON +All power change events result in a message. +This is the normal operating mode for the driver. +.It Dv APM_PRINT_OFF +Power change event messages are suppressed. +.It Dv APM_PRINT_PCT +Power change event messages are suppressed unless the estimated +battery life percentage changes. +.El +.El +.Sh FILES +.Bl -tag -width "/dev/apmctlXXX" +.It /dev/apm +Power management data device. +May only be opened read-only. +May be opened by multiple concurrent users. +.It /dev/apmctl +Power management control device. +May be opened read-write or write-only. +May only be opened by one user at a time. +An attempt to open the file when in use will fail, returning +.Er EBUSY . +.El +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr halt 8 diff --git a/static/openbsd/man4/man4.amd64/autoconf.4 b/static/openbsd/man4/man4.amd64/autoconf.4 new file mode 100644 index 00000000..7a3b6888 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/autoconf.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: autoconf.4,v 1.3 2007/05/31 19:19:53 jmc Exp $ +.\" +.\" Copyright (c) 1994 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christopher G. Demetriou. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt AUTOCONF 4 amd64 +.Os +.Sh NAME +.Nm autoconf +.Nd diagnostics from the autoconfiguration code +.Sh DESCRIPTION +When +.Ox +bootstraps it probes the innards of the machine +on which it is running +and locates controllers, drives, and other devices, printing out +what it finds on the console. +This procedure is driven by a system configuration table which is processed by +.Xr config 8 +and compiled into each kernel. +Devices which exist in the machine but are not configured into the +kernel are usually not detected. +.Sh SEE ALSO +.Xr intro 4 , +.Xr boot_amd64 8 , +.Xr config 8 diff --git a/static/openbsd/man4/man4.amd64/bios.4 b/static/openbsd/man4/man4.amd64/bios.4 new file mode 100644 index 00000000..59e70b7e --- /dev/null +++ b/static/openbsd/man4/man4.amd64/bios.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: bios.4,v 1.2 2007/05/31 19:19:53 jmc Exp $ +.\" +.\" Copyright (c) 2001 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, +.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt BIOS 4 amd64 +.Os +.Sh NAME +.Nm bios +.Nd a driver for PC Firmware, aka BIOS +.Sh SYNOPSIS +.Cd "bios0 at mainbus0" +.Sh DESCRIPTION +.Ox +provides support for a limited subset of PC firmware (aka BIOS) subsystems +on this platform. +Only SMBIOS is supported. +.Pp +SMBIOS provides detail about system hardware configuration +and is used to attach +.Xr ipmi 4 +on most systems. +.Sh SEE ALSO +.Xr intro 4 , +.Xr ipmi 4 +.Sh HISTORY +The +.Nm +driver was introduced to this platform in +.Ox 4.0 . diff --git a/static/openbsd/man4/man4.amd64/cpu.4 b/static/openbsd/man4/man4.amd64/cpu.4 new file mode 100644 index 00000000..bd480c13 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/cpu.4 @@ -0,0 +1,78 @@ +.\" $OpenBSD: cpu.4,v 1.10 2024/09/10 17:01:09 tb Exp $ +.\" +.\" Copyright (c) 2004 Ted Unangst +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 10 2024 $ +.Dt CPU 4 amd64 +.Os +.Sh NAME +.Nm cpu +.Nd Central Processing Unit +.Sh SYNOPSIS +.Cd "cpu0 at mainbus?" +.Cd "cpu* at mainbus?" +.Sh DESCRIPTION +Several processor models have additional features that extend their base +functionality, such as power and frequency control or thermal monitoring. +.Pp +The +.Xr sysctl 2 +.Va hw.cpuspeed +returns the current operating frequency of the processor, +though on some processors this value may be only an approximation. +If possible, speed may be adjusted by altering +.Va hw.setperf +from 0 to 100, +representing percentage of maximum speed. +.Pp +There are several possible implementations for speed adjustment, +all transparent to the user: +.Bl -tag -width tenletters +.It EST +Enhanced SpeedStep found on Intel and VIA processors, +offering frequency scaling with numerous positions. +.It PowerNow +Found on various AMD processors. +It currently only supports a limited set of models in the K8 families. +.El +.Pp +The presence of extended instruction sets can be determined by the sysctl +.Va machdep : +.Bl -tag -width "tenletters" +.It xcrypt +Supports the VIA AES encryption instruction set. +.El +.Pp +The sysctl +.Va hw.sensors +returns the current temperature reported by the processor. +.Sh SEE ALSO +.Xr sysctl 8 +.Sh BUGS +Due to the way in which thermal information is reported on Intel processors, +the temperature may be off by exactly +/-15 degrees C. +.Pp +For multiprocessor kernels with more than one CPU sensor, +processors report identical temperatures +since the temperature is taken from the processor running the sensors update. diff --git a/static/openbsd/man4/man4.amd64/efifb.4 b/static/openbsd/man4/man4.amd64/efifb.4 new file mode 100644 index 00000000..b1512ba8 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/efifb.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: efifb.4,v 1.2 2015/08/31 15:28:39 jmc Exp $ +.\" +.\" Copyright (c) 2015 YASUOKA Masahiko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" The following requests are required for all man pages. +.\" +.Dd $Mdocdate: August 31 2015 $ +.Dt EFIFB 4 amd64 +.Os +.Sh NAME +.Nm efifb +.Nd EFI frame buffer +.Sh SYNOPSIS +.Cd "efifb* at mainbus?" +.Cd "wsdisplay* at efifb?" +.Sh DESCRIPTION +The +.Nm +driver supports the frame buffer passed from UEFI, +the Unified Extensible Firmware Interface. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr mainbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/man4.amd64/intro.4 b/static/openbsd/man4/man4.amd64/intro.4 new file mode 100644 index 00000000..9e35f84d --- /dev/null +++ b/static/openbsd/man4/man4.amd64/intro.4 @@ -0,0 +1,122 @@ +.\" $OpenBSD: intro.4,v 1.40 2023/05/03 22:03:17 jmc Exp $ +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 3 2023 $ +.Dt INTRO 4 amd64 +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the amd64 platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width "cardbus(4)XX" -offset 3n -compact +.It Xr acpi 4 +Advanced Configuration and Power Interface +.It Xr cardbus 4 +introduction to CardBus support +.It Xr iic 4 +Inter IC (I2C) bus +.It Xr isa 4 +introduction to ISA bus support +.It Xr onewire 4 +1-Wire bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr pcmcia 4 +introduction to PCMCIA (PC Card) support +.It Xr usb 4 +introduction to Universal Serial Bus support +.It Xr virtio 4 +VirtIO support driver +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr cpu 4 , +.Xr config 8 +.Sh HISTORY +The +amd64 +.Nm intro +first appeared in +.Ox 3.5 . diff --git a/static/openbsd/man4/man4.amd64/ioapic.4 b/static/openbsd/man4/man4.amd64/ioapic.4 new file mode 100644 index 00000000..01dccda9 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/ioapic.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: ioapic.4,v 1.3 2007/05/31 19:19:53 jmc Exp $ +.\" +.\" Copyright (c) 2006 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt IOAPIC 4 amd64 +.Os +.Sh NAME +.Nm ioapic +.Nd I/O Advanced Programmable Interrupt Controller +.Sh SYNOPSIS +.Cd "ioapic0 at mainbus0" +.Sh DESCRIPTION +.Nm +is an I/O Advanced Programmable Interrupt Controller (APIC). +It provides interrupt management for systems with multiple I/O +subsystems and can distribute interrupts across multiple processors. +.Sh SEE ALSO +.Xr intro 4 +.Sh STANDARDS +.Nm +is based on +Intel's 82093AA I/O Advanced Programmable Interrupt Controller (I/O APIC) +specification. +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Bill Sommerfield . diff --git a/static/openbsd/man4/man4.amd64/mem.4 b/static/openbsd/man4/man4.amd64/mem.4 new file mode 100644 index 00000000..64135758 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/mem.4 @@ -0,0 +1,87 @@ +.\" $OpenBSD: mem.4,v 1.7 2024/03/22 12:29:33 jsg Exp $ +.\" +.\" Copyright (c) 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)mem.4 5.3 (Berkeley) 5/2/91 +.\" +.Dd $Mdocdate: March 22 2024 $ +.Dt MEM 4 amd64 +.Os +.Sh NAME +.Nm mem , +.Nm kmem +.Nd memory files +.Sh DESCRIPTION +The special file +.Pa /dev/mem +is an interface to the physical memory of the computer. +Byte offsets in this file are interpreted as physical memory addresses. +Reading and writing this file is equivalent to reading and writing +memory itself. +Only offsets within the bounds of +.Pa /dev/mem +are allowed. +.Pp +Kernel virtual memory is accessed through the interface +.Pa /dev/kmem +in the same manner as +.Pa /dev/mem . +Only kernel virtual addresses that are currently mapped to memory are allowed. +.Pp +On amd64, physical memory is discontiguous; especially, +the ISA I/O memory space covers the physical address range from +.Li 0x000a0000 +to +.Li 0x00100000 . +.Pp +The kernel virtual memory begins at address +.Li 0xffffffff80000000 . +.Pp +Even with sufficient file system permissions, +these devices can only be opened when the +.Xr securelevel 7 +is insecure or when the +.Va kern.allowkmem +.Xr sysctl 2 +variable is set. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/mem +.It Pa /dev/kmem +.El +.Sh SEE ALSO +.Xr mtrr 4 , +.Xr securelevel 7 +.Sh HISTORY +The +.Pa /dev/mem +file appeared in +.At v1 , +.Pa /dev/kmem +appeared in +.At v5 . diff --git a/static/openbsd/man4/man4.amd64/mpbios.4 b/static/openbsd/man4/man4.amd64/mpbios.4 new file mode 100644 index 00000000..69a9136f --- /dev/null +++ b/static/openbsd/man4/man4.amd64/mpbios.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: mpbios.4,v 1.1 2009/01/13 13:57:03 kettenis Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 13 2009 $ +.Dt MPBIOS 4 amd64 +.Os +.Sh NAME +.Nm mpbios +.Nd MP BIOS +.Sh SYNOPSIS +.Cd "mpbios0 at bios0" +.Sh DESCRIPTION +The +.Nm +driver extracts configuration information from the BIOS on +multiprocessor systems that conform to the Intel MultiProcessor +Specification. +This information is used to attach application processors and APICs, +and to assign interrupts to ISA, EISA and PCI devices. +.Pp +On modern systems this information is provided by ACPI through the +.Xr acpimadt 4 +device. +On such a system +.Nm +will not attach, even if the BIOS also contains the data structures +specified by the Intel MP Specification. +.Pp +The +.Nm +driver supports version 1.1 and 1.4 of the Intel MP Specification. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr acpimadt 4 , +.Xr bios 4 , +.Xr cpu 4 , +.Xr intro 4 , +.Xr ioapic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.5 , +based on code present since +.Ox 3.6 . diff --git a/static/openbsd/man4/man4.amd64/mtrr.4 b/static/openbsd/man4/man4.amd64/mtrr.4 new file mode 100644 index 00000000..4a88f4ac --- /dev/null +++ b/static/openbsd/man4/man4.amd64/mtrr.4 @@ -0,0 +1,146 @@ +.\" $OpenBSD: mtrr.4,v 1.8 2014/02/15 23:41:19 schwarze Exp $ +.\" +.\" MTRR driver for OpenBSD. +.\" Copyright 1999 Matthieu Herrb +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.Dd $Mdocdate: February 15 2014 $ +.Dt MTRR 4 amd64 +.Os +.Sh NAME +.Nm mtrr +.Nd driver for CPU memory range attributes +.Sh SYNOPSIS +.Cd "pseudo-device mtrr 1" +.Sh DESCRIPTION +The +.Nm +device provides access to the memory range attributes supported by the +MTRRs on AMD64 compatible CPUs. +.Ss IOCTL INTERFACE +Several architectures allow attributes to be associated with ranges of physical +memory. +These attributes can be manipulated via +.Fn ioctl +calls performed on +.Pa /dev/mem +or +.Pa /dev/xf86 . +Declarations and data types are to be found in +.In sys/memrange.h . +.Pp +The specific attributes, and number of programmable ranges may vary between +architectures. +The full set of supported attributes is: +.Bl -tag -width MDF_WRITECOMBINE +.It Dv MDF_UNCACHEABLE +The region is not cached. +.It Dv MDF_WRITECOMBINE +Writes to the region may be combined or performed out of order. +.It Dv MDF_WRITETHROUGH +Writes to the region are committed synchronously. +.It Dv MDF_WRITEBACK +Writes to the region are committed asynchronously. +.It Dv MDF_WRITEPROTECT +The region cannot be written to. +.El +.Pp +Memory ranges are described by +.Bd -literal -offset xxxx +struct mem_range_desc { + u_int64_t mr_base; /\(** physical base address \(**/ + u_int64_t mr_len; /\(** physical length of region \(**/ + int mr_flags; /\(** attributes of region \(**/ + char mr_owner[8]; +}; +.Ed +.Pp +In addition to the region attributes listed above, the following flags +may also be set in the +.Fa mr_flags +field: +.Bl -tag -width MDF_FIXACTIVE +.It Dv MDF_FIXBASE +The region's base address cannot be changed. +.It Dv MDF_FIXLEN +The region's length cannot be changed. +.It Dv MDF_FIRMWARE +The region is believed to have been established by the system firmware. +.It Dv MDF_ACTIVE +The region is currently active. +.It Dv MDF_BOGUS +We believe the region to be invalid or otherwise erroneous. +.It Dv MDF_FIXACTIVE +The region cannot be disabled. +.El +.Pp +Operations are performed using +.Bd -literal -offset xxxx +struct mem_range_op { + struct mem_range_desc *mo_desc; + int mo_arg[2]; +}; +.Ed +.Pp +The +.Fa MEMRANGE_GET +ioctl is used to retrieve current memory range attributes. +If +.Fa mo_arg[0] +is set to 0, it will be updated with the total number of memory range +descriptors. +If greater than 0, the array at +.Fa mo_desc +will be filled with a corresponding number of descriptor structures, +or the maximum, whichever is less. +.Pp +The +.Fa MEMRANGE_SET +ioctl is used to add, alter and remove memory range attributes. +A range with the +.Dv MDF_FIXACTIVE +flag may not be removed. +.Pp +.Fa mo_arg[0] +should be set to MEMRANGE_SET_UPDATE to update an existing +or establish a new range, or to MEMRANGE_SET_REMOVE to remove a range. +.Sh ERRORS +On +.Xr ioctl 2 +failure, +.Xr errno 2 +will be set as follows: +.Bl -tag -width Er +.It Bq Er EOPNOTSUPP +Memory range operations are not supported on this architecture. +.It Bq Er ENXIO +No memory range descriptors are available (e.g., firmware has not enabled +any). +.It Bq Er EINVAL +The memory range supplied as an argument is invalid or overlaps another +range in a fashion not supported by this architecture. +.It Bq Er EBUSY +An attempt to remove or update a range failed because the range is busy. +.It Bq Er ENOSPC +An attempt to create a new range failed due to a shortage of hardware +resources (e.g., descriptor slots). +.It Bq Er ENOENT +An attempt to remove a range failed because no range matches the descriptor +base/length supplied. +.It Bq Er EPERM +An attempt to remove a range failed because the range is permanently +enabled. +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr mem 4 , +.Xr pctr 4 , +.Xr xf86 4 , +.Xr memconfig 8 +.Sh HISTORY +.Nm +support was originally included in +.Fx 3.3 . diff --git a/static/openbsd/man4/man4.amd64/nvram.4 b/static/openbsd/man4/man4.amd64/nvram.4 new file mode 100644 index 00000000..a7655d23 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/nvram.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: nvram.4,v 1.1 2007/08/02 16:40:27 deraadt Exp $ +.\" +.\" Copyright 2004 Joshua Stein +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 2 2007 $ +.Dt NVRAM 4 amd64 +.Os +.Sh NAME +.Nm nvram +.Nd driver for reading PC NVRAM contents +.Sh SYNOPSIS +.Cd "pseudo-device nvram 1" +.Sh DESCRIPTION +The +.Nm +device provides read-only access to the non-volatile memory contained in the +MC146818 real-time clock. +.Pp +This data is provided as a seekable character device, +.Pa /dev/nvram . +Checksums of the NVRAM contents are calculated over bytes 2 to 31 and stored +in byte 32. +A valid checksum is required for the driver to initialize. +.Sh FILES +.Bl -tag -width /dev/nvram +.It Pa /dev/nvram +.El +.Sh HISTORY +.Nm +support was originally included in +.Ox 3.7 . diff --git a/static/openbsd/man4/man4.amd64/pctr.4 b/static/openbsd/man4/man4.amd64/pctr.4 new file mode 100644 index 00000000..c024acc4 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/pctr.4 @@ -0,0 +1,234 @@ +.\" $OpenBSD: pctr.4,v 1.8 2019/10/05 20:53:49 matthieu Exp $ +.\" +.\" Pentium performance counter driver for OpenBSD. +.\" Copyright 1996 David Mazieres . +.\" +.\" Modification and redistribution in source and binary forms is +.\" permitted provided that due credit is given to the author and the +.\" OpenBSD project by leaving this copyright notice intact. +.\" +.Dd $Mdocdate: October 5 2019 $ +.Dt PCTR 4 amd64 +.Os +.Sh NAME +.Nm pctr +.Nd driver for CPU performance counters +.Sh SYNOPSIS +.Cd "pseudo-device pctr 1" +.Sh DESCRIPTION +The +.Nm +device provides access to the performance counters on AMD and Intel brand +processors, and to the TSC on others. +.Pp +Intel processors have two 40-bit performance counters which can be +programmed to count events such as cache misses, branch target buffer hits, +TLB misses, dual-issues, interrupts, pipeline flushes, and more. +While AMD processors have four 48-bit counters, their precision is decreased +to 40 bits. +.Pp +There is one +.Em ioctl +call to read the status of all counters, and one +.Em ioctl +call to program the function of each counter. +All require the following includes: +.Bd -literal -offset indent +#include +#include +#include +.Ed +.Pp +The current state of all counters can be read with the +.Dv PCIOCRD +.Em ioctl , +which takes an argument of type +.Dv "struct pctrst" : +.Bd -literal -offset indent +#define PCTR_NUM 4 +struct pctrst { + u_int pctr_fn[PCTR_NUM]; + pctrval pctr_tsc; + pctrval pctr_hwc[PCTR_NUM]; +}; +.Ed +.Pp +In this structure, +.Em ctr_fn +contains the functions of the counters, as previously set by the +.Dv PCIOCS0 , +.Dv PCIOCS1 , +.Dv PCIOCS2 +and +.Dv PCIOCS3 +ioctls (see below). +.Em pctr_hwc +contains the actual value of the hardware counters. +.Em pctr_tsc +is a free-running, 64-bit cycle counter. +.Pp +The functions of the counters can be programmed with ioctls +.Dv PCIOCS0 , +.Dv PCIOCS1 , +.Dv PCIOCS2 +and +.Dv PCIOCS3 +which require a writeable file descriptor and take an argument of type +.Dv "unsigned int" . \& +The meaning of this integer is dependent on the particular CPU. +.Ss Time stamp counter +The time stamp counter is available on most of the AMD and Intel CPUs. +It is set to zero at boot time, and then increments with each cycle. +Because the counter is 64-bits wide, it does not overflow. +.Pp +The value of the time stamp counter is returned by the +.Dv PCIOCRD +.Em ioctl , +so that one can get an exact timestamp on readings of the hardware +event counters. +.Pp +The performance counters can be read directly from user-mode without +need to invoke the kernel. +The macro +.Fn rdpmc ctr +takes 0, 1, 2 or 3 as an argument to specify a counter, and returns that +counter's 40-bit value (which will be of type +.Em pctrval ) . +This is generally preferable to making a system call as it introduces +less distortion in measurements. +.Pp +Counter functions supported by these CPUs contain several parts. +The most significant byte (an 8-bit integer shifted left by +.Dv PCTR_CM_SHIFT ) +contains a +.Em "counter mask" . +If non-zero, this sets a threshold for the number of times an event +must occur in one cycle for the counter to be incremented. +The +.Em "counter mask" +can therefore be used to count cycles in which an event +occurs at least some number of times. +The next byte contains several flags: +.Bl -tag -width PCTR_EN +.It Dv PCTR_U +Enables counting of events that occur in user mode. +.It Dv PCTR_K +Enables counting of events that occur in kernel mode. +You must set at least one of +.Dv PCTR_K +and +.Dv PCTR_U +to count anything. +.It Dv PCTR_E +Counts edges rather than cycles. +For some functions this allows you +to get an estimate of the number of events rather than the number of +cycles occupied by those events. +.It Dv PCTR_EN +Enable counters. +This bit must be set in the function for counter 0 +in order for either of the counters to be enabled. +This bit should probably be set in counter 1 as well. +.It Dv PCTR_I +Inverts the sense of the +.Em "counter mask" . \& +When this bit is set, the counter only increments on cycles in which +there are no +.Em more +events than specified in the +.Em "counter mask" . +.El +.Pp +The next byte (shifted left by the +.Dv PCTR_UM_SHIFT ) +contains flags specific to the event being counted, also known as the +.Em "unit mask" . +.Pp +For events dealing with the L2 cache, the following flags are valid +on Intel brand processors: +.Bl -tag -width PCTR_UM_M +.It Dv PCTR_UM_M +Count events involving modified cache coherency state lines. +.It Dv PCTR_UM_E +Count events involving exclusive cache coherency state lines. +.It Dv PCTR_UM_S +Count events involving shared cache coherency state lines. +.It Dv PCTR_UM_I +Count events involving invalid cache coherency state lines. +.El +.Pp +To measure all L2 cache activity, all these bits should be set. +They can be set with the macro +.Dv PCTR_UM_MESI +which contains the bitwise or of all of the above. +.Pp +For event types dealing with bus transactions, there is another flag +that can be set in the +.Em "unit mask" : +.Bl -tag -width PCTR_UM_A +.It Dv PCTR_UM_A +Count all appropriate bus events, not just those initiated by the +processor. +.El +.Pp +Events marked +.Em (MESI) +require the +.Dv PCTR_UM_[MESI] +bits in the +.Em "unit mask" . \& +Events marked +.Em (A) +can take the +.Dv PCTR_UM_A +bit. +.Pp +Finally, the least significant byte of the counter function is the +event type to count. +A list of possible event functions could be obtained by running a +.Xr pctr 1 +command with +.Fl l +option. +.Sh FILES +.Bl -tag -width /dev/pctr -compact +.It Pa /dev/pctr +.El +.Sh ERRORS +.Bl -tag -width "[ENODEV]" +.It Bq Er ENODEV +An attempt was made to set the counter functions on a CPU that does +not support counters. +.It Bq Er EINVAL +An invalid counter function was provided as an argument to the +.Dv PCIOCSx +.Em ioctl . +.It Bq Er EPERM +An attempt was made to set the counter functions, but the device was +not open for writing. +.El +.Sh SEE ALSO +.Xr pctr 1 , +.Xr ioctl 2 +.Sh HISTORY +A +.Nm +device first appeared in +.Ox 2.0 . +Support for amd64 architecture appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +device was written by +.An David Mazieres Aq Mt dm@lcs.mit.edu . +Support for amd64 architecture was written by +.An Mike Belopuhov Aq Mt mikeb@openbsd.org . +.Sh BUGS +Not all counter functions are completely accurate. +Some of the functions may not make any sense at all. +Also you should be aware of the possibility of an interrupt between +invocations of +.Fn rdpmc +that can potentially decrease the accuracy of measurements. diff --git a/static/openbsd/man4/man4.amd64/skgpio.4 b/static/openbsd/man4/man4.amd64/skgpio.4 new file mode 100644 index 00000000..eaa494ea --- /dev/null +++ b/static/openbsd/man4/man4.amd64/skgpio.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: skgpio.4,v 1.2 2015/10/22 11:01:14 sobrado Exp $ +.\" +.\" Copyright (c) 2014 Matt Dainty +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 22 2015 $ +.Dt SKGPIO 4 amd64 +.Os +.Sh NAME +.Nm skgpio +.Nd Soekris net6501 GPIO and LEDs +.Sh SYNOPSIS +.Cd "skgpio0 at isa? port 0x680" +.Cd "gpio* at skgpio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO and LEDs as implemented by the Xilinx +Spartan FGPA integrated into the Soekris net6501 programmed with the default +bitstream found in the BIOS. +.Pp +Two standard +.Xr gpio 4 +interfaces are provided, one for the 16 real pins which can be configured as +either inputs or outputs and another with 2 output-only pins that map +to the error and ready LEDs respectively. +Both may be used with +.Xr gpioctl 8 . +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Matt Dainty Aq matt@bodgit-n-scarper.com . +.Sh BUGS +If the Xilinx FPGA is programmed with a different bitstream, the driver will +likely not function. diff --git a/static/openbsd/man4/man4.amd64/tcpcib.4 b/static/openbsd/man4/man4.amd64/tcpcib.4 new file mode 100644 index 00000000..327e6f19 --- /dev/null +++ b/static/openbsd/man4/man4.amd64/tcpcib.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: tcpcib.4,v 1.6 2014/11/15 14:41:02 bentley Exp $ +.\" +.\" Copyright (c) 2012 Matt Dainty +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 15 2014 $ +.Dt TCPCIB 4 amd64 +.Os +.Sh NAME +.Nm tcpcib +.Nd Intel Atom E600 series LPC bridge, timecounter and watchdog timer +.Sh SYNOPSIS +.Cd "tcpcib* at pci?" +.Cd "isa* at tcpcib?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Intel Atom E600 series LPC bridge and +implements a 64-bit 14.3 MHz timecounter using the HPET timer. +.Pp +The +.Nm +driver also provides the standard +.Xr watchdog 4 +interface to the watchdog timer and may be used with +.Xr watchdogd 8 . +The watchdog timer can be configured via +.Xr sysctl 8 . +.Pp +Once the watchdog timer resets the CPU, the driver reports it on the +next boot displaying the +.Dq reboot on timeout +message in the +.Xr dmesg 8 . +.Pp +The maximum timeout value supported by the watchdog timer is 600 +seconds. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 , +.Xr watchdog 4 , +.Xr sysctl 8 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Matt Dainty Aq Mt matt@bodgit-n-scarper.com . +.Sh BUGS +Apart from the core +.Xr pcib 4 +functionality, timecounter and the +.Xr watchdog 4 +interface, the driver doesn't support any other aspects of the hardware. diff --git a/static/openbsd/man4/man4.amd64/vmm.4 b/static/openbsd/man4/man4.amd64/vmm.4 new file mode 100644 index 00000000..cc621a8e --- /dev/null +++ b/static/openbsd/man4/man4.amd64/vmm.4 @@ -0,0 +1,122 @@ +.\" $OpenBSD: vmm.4,v 1.10 2024/11/05 15:08:46 mlarkin Exp $ +.\" +.\"Copyright (c) 2015 Mike Larkin +.\" +.\"Permission to use, copy, modify, and distribute this software for any +.\"purpose with or without fee is hereby granted, provided that the above +.\"copyright notice and this permission notice appear in all copies. +.\" +.\"THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\"WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\"MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\"ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\"WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\"ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\"OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 5 2024 $ +.Dt VMM 4 amd64 +.Os +.Sh NAME +.Nm vmm +.Nd virtual machine monitor +.Sh SYNOPSIS +.Cd "vmm0 at mainbus0" +.Pp +.In machine/vmmvar.h +.Sh DESCRIPTION +The +.Nm +driver implements a virtual machine monitor (VMM) suitable for executing +.Em virtual machines +(VMs). +A VMM runs on the +.Em host +operating system and provides facilities to execute one or more +VMs, each of which is provided with a suitable complement of +virtual hardware. +.Pp +These VMs run independently of the host, but may interact with +it as any other machine would (e.g. via network communications or +other means). +.Pp +VMs are allocated hardware resources by the VMM during creation, +including: +.Pp +.Bl -bullet -offset indent -compact +.It +Virtual CPUs +.It +Virtual network interfaces +.It +Virtual disk images +.It +Virtual serial ports +.El +.Pp +Although VMs execute independently of each other and the host, they +do consume host resources and, as such, the number of VMs (and their +configurations) should be taken into consideration when planning +host capacity. +.Pp +The +.Nm +driver requires suitable host CPU capabilities in order to provide +VM services. +The +.Nm +driver requires at least one CPU with hardware-assisted virtualization +capabilities and nested or extended paging capabilities to be +present on the host. +For more information, consult the CPU vendor's documentation. +.Pp +The following +.Xr ioctl 2 +commands are provided for managing +.Nm +guests: +.Bl -tag -width Ds -offset indent +.It Dv VMM_IOC_CREATE Fa "struct vm_create_params *" +Create a VM, initializing +.Nm +if not yet started. +(Does not start the VCPU.) +.It Dv VMM_IOC_RUN Fa "struct vm_run_params *" +Run a VCPU for a defined VM. +Return on VM-exit, when the VCPU stopped, or an error occurred. +.It Dv VMM_IOC_INFO Fa "struct vm_info_params *" +Get information about the VMs currently hosted by +.Nm . +.It Dv VMM_IOC_TERM Fa "struct vm_terminate_params *" +Terminate a given VM. +.It Dv VMM_IOC_RESETCPU Fa "struct vm_resetcpu_params *" +Reset a VCPU to power-on-init state using the provided register state. +.It Dv VMM_IOC_INTR Fa "struct vm_intr_params *" +Signal a pending interrupt for a VCPU. +.It Dv VMM_IOC_READREGS Fa "struct vm_rwregs_params *" +Read registers of a VCPU. +.It Dv VMM_IOC_WRITEREGS Fa "struct vm_rwregs_params *" +Write register values of a VCPU. +.It Dv VMM_IOC_READVMPARAMS Fa "struct vm_rwvmparams_params *" +Read paravirtualized hardware parameters (such as +.Xr pvclock 4 +version) for a VM. +.It Dv VMM_IOC_WRITEVMPARAMS Fa "struct vm_rwvmparams_params *" +Write paravirtualized hardware parameters (such as +.Xr pvclock 4 +guest physical address) for a VM. +.El +.Sh SEE ALSO +.Xr cpu 4 , +.Xr intro 4 , +.Xr virtio 4 , +.Xr vmctl 8 , +.Xr vmd 8 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 5.9 . +.Sh AUTHORS +.An Mike Larkin Aq Mt mlarkin@openbsd.org diff --git a/static/openbsd/man4/man4.arm64/Makefile b/static/openbsd/man4/man4.arm64/Makefile new file mode 100644 index 00000000..d8a0918b --- /dev/null +++ b/static/openbsd/man4/man4.arm64/Makefile @@ -0,0 +1,38 @@ +MAN = agintc.4 \ + agtimer.4 \ + ampchwm.4 \ + ampintc.4 \ + aplaudio.4 \ + aplcpu.4 \ + apldart.4 \ + apldcp.4 \ + apldma.4 \ + apldog.4 \ + apldrm.4 \ + aplefuse.4 \ + aplhidev.4 \ + apliic.4 \ + aplintc.4 \ + aplmbox.4 \ + aplmca.4 \ + aplnco.4 \ + aplns.4 \ + aplpcie.4 \ + aplpinctrl.4 \ + aplpmgr.4 \ + aplpmu.4 \ + aplpwm.4 \ + aplsart.4 \ + aplsmc.4 \ + aplspi.4 \ + aplspmi.4 \ + apm.4 \ + intro.4 \ + rpiclock.4 \ + rpipwm.4 \ + rpirtc.4 \ + rpone.4 \ + smbios.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.arm64/agintc.4 b/static/openbsd/man4/man4.arm64/agintc.4 new file mode 100644 index 00000000..cc0f235e --- /dev/null +++ b/static/openbsd/man4/man4.arm64/agintc.4 @@ -0,0 +1,36 @@ +.\" $OpenBSD: agintc.4,v 1.1 2022/10/20 08:45:39 jsg Exp $ +.\" +.\" Copyright (c) 2022 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 20 2022 $ +.Dt AGINTC 4 arm64 +.Os +.Sh NAME +.Nm agintc , +.Nm agintcmsi +.Nd Arm generic interrupt controller v3/v4 +.Sh SYNOPSIS +.Cd "agintc* at fdt?" +.Cd "agintcmsi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Arm Generic Interrupt Controller (GIC) +version 3 and version 4. +.Sh SEE ALSO +.Rs +.%T Arm Generic Interrupt Controller Architecture Specification GIC architecture version 3 and version 4 +.%N Arm IHI 0069 +.Re diff --git a/static/openbsd/man4/man4.arm64/agtimer.4 b/static/openbsd/man4/man4.arm64/agtimer.4 new file mode 100644 index 00000000..608e4119 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/agtimer.4 @@ -0,0 +1,33 @@ +.\" $OpenBSD: agtimer.4,v 1.1 2018/04/04 14:21:26 jsg Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 4 2018 $ +.Dt AGTIMER 4 arm64 +.Os +.Sh NAME +.Nm agtimer +.Nd ARM generic timer +.Sh SYNOPSIS +.Cd "agtimer* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ARM generic timer, an optional extension +to the ARM architecture. +.Sh SEE ALSO +.Rs +.%T ARM Architecture Reference Manual ARMv8, for ARMv8-A architecture profile +.Re diff --git a/static/openbsd/man4/man4.arm64/ampchwm.4 b/static/openbsd/man4/man4.arm64/ampchwm.4 new file mode 100644 index 00000000..76555eac --- /dev/null +++ b/static/openbsd/man4/man4.arm64/ampchwm.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: ampchwm.4,v 1.2 2023/12/11 15:21:15 jmc Exp $ +.\" +.\" Copyright (c) 2023 Claudio Jeker +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 11 2023 $ +.Dt AMPCHWM 4 arm64 +.Os +.Sh NAME +.Nm ampchwm +.Nd Ampere Altra fine-grained power telemetry +.Sh SYNOPSIS +.Cd "ampchwm* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the per-core power telemetry firmware interface +found on the Ampere Altra SoC. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Claudio Jeker Aq Mt claudio@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/ampintc.4 b/static/openbsd/man4/man4.arm64/ampintc.4 new file mode 100644 index 00000000..76b53251 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/ampintc.4 @@ -0,0 +1,36 @@ +.\" $OpenBSD: ampintc.4,v 1.3 2022/10/20 08:52:22 jsg Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 20 2022 $ +.Dt AMPINTC 4 arm64 +.Os +.Sh NAME +.Nm ampintc , +.Nm ampintcmsi +.Nd Arm generic interrupt controller v1/v2 +.Sh SYNOPSIS +.Cd "ampintc* at fdt?" +.Cd "ampintcmsi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Arm Generic Interrupt Controller (GIC) +version 1 and version 2. +.Sh SEE ALSO +.Rs +.%T ARM Generic Interrupt Controller Architecture Specification +.%N ARM IHI 0048 +.Re diff --git a/static/openbsd/man4/man4.arm64/aplaudio.4 b/static/openbsd/man4/man4.arm64/aplaudio.4 new file mode 100644 index 00000000..602a377c --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplaudio.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: aplaudio.4,v 1.3 2022/08/06 10:51:30 jsg Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2022 $ +.Dt APLAUDIO 4 arm64 +.Os +.Sh NAME +.Nm aplaudio +.Nd Apple audio subsystem +.Sh SYNOPSIS +.Cd "aplaudio* at fdt?" +.Cd "audio* at aplaudio?" +.Sh DESCRIPTION +.Nm +is a driver for the audio subsystem on Apple Silicon Macs. +It represents the logical connection of the DMA controller, +the MCA controller and various codecs. +.Sh SEE ALSO +.Xr apldma 4 , +.Xr aplmca 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr simpleaudio 4 , +.Xr tascodec 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplcpu.4 b/static/openbsd/man4/man4.arm64/aplcpu.4 new file mode 100644 index 00000000..217c8b06 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplcpu.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: aplcpu.4,v 1.2 2022/02/20 20:01:04 jmc Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 20 2022 $ +.Dt APLCPU 4 arm64 +.Os +.Sh NAME +.Nm aplcpu +.Nd Apple CPU power states +.Sh SYNOPSIS +.Cd "aplcpu* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for managing the CPU power states on Apple +SoCs. +These power states can be set to reduce power usage and extend battery +life through the +.Va hw.setperf +.Xr sysctl 2 +mechanism. +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr intro 4 , +.Xr apmd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/apldart.4 b/static/openbsd/man4/man4.arm64/apldart.4 new file mode 100644 index 00000000..c2ed00b4 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/apldart.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: apldart.4,v 1.2 2021/02/27 18:50:38 jmc Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 27 2021 $ +.Dt APLDART 4 arm64 +.Os +.Sh NAME +.Nm apldart +.Nd Apple DART IOMMU +.Sh SYNOPSIS +.Cd "apldart* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the DART IOMMU found on various Apple +SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/apldcp.4 b/static/openbsd/man4/man4.arm64/apldcp.4 new file mode 100644 index 00000000..c2bdcd0c --- /dev/null +++ b/static/openbsd/man4/man4.arm64/apldcp.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: apldcp.4,v 1.2 2024/01/24 14:17:37 kettenis Exp $ +.\" +.\" Copyright (c) 2024 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 24 2024 $ +.Dt APLDCP 4 arm64 +.Os +.Sh NAME +.Nm apldcp +.Nd Apple display coprocessor +.Sh SYNOPSIS +.Cd "apldcp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the display coprocessor integrated on Apple SoCs. +.Sh SEE ALSO +.Xr apldrm 4 , +.Xr drm 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alyssa Rosenzweig , +.An Janne Grunau , +.An Martin Povi\[u0161]er +and +.An Sven Peter +for Linux and ported to +.Ox +by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/apldma.4 b/static/openbsd/man4/man4.arm64/apldma.4 new file mode 100644 index 00000000..b7dabb19 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/apldma.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: apldma.4,v 1.2 2022/08/06 10:51:30 jsg Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2022 $ +.Dt APLDMA 4 arm64 +.Os +.Sh NAME +.Nm apldma +.Nd Apple DMA controller +.Sh SYNOPSIS +.Cd "apldma* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the DMA controller integrated on various +Apple SoCs. +.Pp +The controller is used to support DMA for the audio interfaces +integrated on the SoC. +.Sh SEE ALSO +.Xr aplmca 4 , +.Xr intro 4 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/apldog.4 b/static/openbsd/man4/man4.arm64/apldog.4 new file mode 100644 index 00000000..7f4fd55d --- /dev/null +++ b/static/openbsd/man4/man4.arm64/apldog.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: apldog.4,v 1.2 2021/02/22 21:58:25 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 22 2021 $ +.Dt APLDOG 4 arm64 +.Os +.Sh NAME +.Nm apldog +.Nd Apple watchdog timer +.Sh SYNOPSIS +.Cd "apldog* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the watchdog timer found on various Apple +SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/apldrm.4 b/static/openbsd/man4/man4.arm64/apldrm.4 new file mode 100644 index 00000000..b6a01f61 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/apldrm.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: apldrm.4,v 1.2 2024/01/23 05:48:47 jsg Exp $ +.\" +.\" Copyright (c) 2024 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 23 2024 $ +.Dt APLDRM 4 arm64 +.Os +.Sh NAME +.Nm apldrm +.Nd Apple DRM subsystem +.Sh SYNOPSIS +.Cd "apldrm* at fdt?" +.Cd "drm* at apldrm?" +.Cd "wsdisplay* at apldrm?" +.Sh DESCRIPTION +The +.Nm +driver provides kernel mode setting (KMS) functionality for the +graphics hardware integrated on Apple SoCs. +.Sh SEE ALSO +.Xr apldcp 4 , +.Xr drm 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alyssa Rosenzweig +and +.An Janne Grunau +for Linux and ported to +.Ox +by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplefuse.4 b/static/openbsd/man4/man4.arm64/aplefuse.4 new file mode 100644 index 00000000..922c91da --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplefuse.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: aplefuse.4,v 1.2 2022/12/17 14:53:16 jmc Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 17 2022 $ +.Dt APLEFUSE 4 arm64 +.Os +.Sh NAME +.Nm aplefuse +.Nd Apple eFuses +.Sh SYNOPSIS +.Cd "aplefuse* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for reading the on-chip eFuses integrated on +various Apple SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplhidev.4 b/static/openbsd/man4/man4.arm64/aplhidev.4 new file mode 100644 index 00000000..d91a8068 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplhidev.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: aplhidev.4,v 1.2 2021/11/01 15:23:57 jmc Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 1 2021 $ +.Dt APLHIDEV 4 arm64 +.Os +.Sh NAME +.Nm aplhidev , +.Nm aplkbd , +.Nm aplms +.Nd Apple HID over SPI support +.Sh SYNOPSIS +.Cd "aplhidev* at spi?" +.Cd "aplkbd* at aplhidev?" +.Cd "wskbd* at aplkbd? mux 1" +.Cd "aplms* at aplhidev?" +.Cd "wsmouse* at aplms? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides support for Human Interface Devices (HID) on +Serial Peripheral Interface (SPI) buses on Apple Silicon Macs. +.Sh SEE ALSO +.Xr aplspi 4 , +.Xr intro 4 , +.Xr wskbd 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/apliic.4 b/static/openbsd/man4/man4.arm64/apliic.4 new file mode 100644 index 00000000..6fb4470c --- /dev/null +++ b/static/openbsd/man4/man4.arm64/apliic.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: apliic.4,v 1.2 2021/12/24 07:05:55 jmc Exp $ +.\" +.\" Copyright (c) 2021 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 24 2021 $ +.Dt APLIIC 4 arm64 +.Os +.Sh NAME +.Nm apliic +.Nd Apple I2C controller +.Sh SYNOPSIS +.Cd "apliic* at fdt?" +.Cd "iic* at apliic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the I2C controller found on various Apple SoCs. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/man4.arm64/aplintc.4 b/static/openbsd/man4/man4.arm64/aplintc.4 new file mode 100644 index 00000000..9a2c0ce3 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplintc.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: aplintc.4,v 1.2 2021/02/24 13:36:19 jmc Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 24 2021 $ +.Dt APLINTC 4 arm64 +.Os +.Sh NAME +.Nm aplintc +.Nd Apple interrupt controller +.Sh SYNOPSIS +.Cd "aplintc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the interrupt controller found on various +Apple SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplmbox.4 b/static/openbsd/man4/man4.arm64/aplmbox.4 new file mode 100644 index 00000000..178607dc --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplmbox.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: aplmbox.4,v 1.1 2021/12/19 13:15:47 kettenis Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 19 2021 $ +.Dt APLMBOX 4 arm64 +.Os +.Sh NAME +.Nm aplmbox +.Nd Apple IOP mailboxes +.Sh SYNOPSIS +.Cd "aplmbox* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver handles communication with various coprocessors integrated on +Apple SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplmca.4 b/static/openbsd/man4/man4.arm64/aplmca.4 new file mode 100644 index 00000000..8ae9f0d3 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplmca.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: aplmca.4,v 1.3 2022/08/06 10:51:30 jsg Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2022 $ +.Dt APLMCA 4 arm64 +.Os +.Sh NAME +.Nm aplmca +.Nd Apple MCA controller +.Sh SYNOPSIS +.Cd "aplmca* at fdt?" +.Sh DESCRIPTION +.Nm +is a driver for the MCA controller integrated on +various Apple SoCs. +This controller serializes audio data streams received from the +.Xr apldma 4 +DMA controller and sends these out as I2S/TDM streams on the audio +interfaces of the SoCs. +.Sh SEE ALSO +.Xr aplaudio 4 , +.Xr apldma 4 , +.Xr aplnco 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplnco.4 b/static/openbsd/man4/man4.arm64/aplnco.4 new file mode 100644 index 00000000..e840b367 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplnco.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: aplnco.4,v 1.2 2022/08/06 10:51:30 jsg Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2022 $ +.Dt APLNCO 4 arm64 +.Os +.Sh NAME +.Nm aplnco +.Nd Apple NCO clock controller +.Sh SYNOPSIS +.Cd "aplnco* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the numerically-controlled oscillators that are used +to derive the audio clock signals for Apple SoCs. +.Sh SEE ALSO +.Xr aplmca 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplns.4 b/static/openbsd/man4/man4.arm64/aplns.4 new file mode 100644 index 00000000..40860363 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplns.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: aplns.4,v 1.2 2023/09/11 04:21:30 jsg Exp $ +.\" +.\" Copyright (c) 2021 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 11 2023 $ +.Dt APLNS 4 arm64 +.Os +.Sh NAME +.Nm aplns +.Nd Apple NVMe Storage controller +.Sh SYNOPSIS +.Cd "aplns* at fdt?" +.Cd "nvme* at aplns?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the NVMe Storage controller found on +various Apple SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr nvme 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . diff --git a/static/openbsd/man4/man4.arm64/aplpcie.4 b/static/openbsd/man4/man4.arm64/aplpcie.4 new file mode 100644 index 00000000..91245cd6 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplpcie.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: aplpcie.4,v 1.1 2021/02/27 17:15:33 kettenis Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 27 2021 $ +.Dt APLPCIE 4 arm64 +.Os +.Sh NAME +.Nm aplpcie +.Nd Apple Host/PCIe bridge +.Sh SYNOPSIS +.Cd "aplpcie* at fdt?" +.Cd "pci* at aplpcie?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PCIe controller found on various Apple +SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplpinctrl.4 b/static/openbsd/man4/man4.arm64/aplpinctrl.4 new file mode 100644 index 00000000..278126bc --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplpinctrl.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: aplpinctrl.4,v 1.1 2021/08/31 15:37:40 kettenis Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 31 2021 $ +.Dt APLPINCTRL 4 arm64 +.Os +.Sh NAME +.Nm aplpinctrl +.Nd Apple pin multiplexing +.Sh SYNOPSIS +.Cd "aplpinctrl* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver uses pin control data from the device tree to select one of +multiple possible roles available for pins on various Apple SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplpmgr.4 b/static/openbsd/man4/man4.arm64/aplpmgr.4 new file mode 100644 index 00000000..3436c3d5 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplpmgr.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: aplpmgr.4,v 1.1 2021/12/09 11:44:31 kettenis Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 9 2021 $ +.Dt APLPMGR 4 arm64 +.Os +.Sh NAME +.Nm aplpmgr +.Nd Apple power management controller +.Sh SYNOPSIS +.Cd "aplpmgr* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the power management controller found on +various Apple SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplpmu.4 b/static/openbsd/man4/man4.arm64/aplpmu.4 new file mode 100644 index 00000000..e8b34682 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplpmu.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: aplpmu.4,v 1.2 2021/05/30 12:26:04 jmc Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 30 2021 $ +.Dt APLPMU 4 arm64 +.Os +.Sh NAME +.Nm aplpmu +.Nd Apple power management unit +.Sh SYNOPSIS +.Cd "aplpmu* at aplspmi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the real-time clock embedded in the PMU +found on various Apple SoCs. +.Sh SEE ALSO +.Xr aplspmi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplpwm.4 b/static/openbsd/man4/man4.arm64/aplpwm.4 new file mode 100644 index 00000000..8280c816 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplpwm.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: aplpwm.4,v 1.1 2022/11/21 22:01:51 kettenis Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 21 2022 $ +.Dt APLPWM 4 arm64 +.Os +.Sh NAME +.Nm aplpwm +.Nd Apple PWM controller +.Sh SYNOPSIS +.Cd "aplpwm* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PWM controllers found on various +Apple SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplsart.4 b/static/openbsd/man4/man4.arm64/aplsart.4 new file mode 100644 index 00000000..89a5ddf7 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplsart.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: aplsart.4,v 1.1 2022/06/12 16:02:33 kettenis Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 12 2022 $ +.Dt APLSART 4 arm64 +.Os +.Sh NAME +.Nm aplsart +.Nd Apple SART address filter +.Sh SYNOPSIS +.Cd "aplsart* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SART address filter found on various +Apple SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplsmc.4 b/static/openbsd/man4/man4.arm64/aplsmc.4 new file mode 100644 index 00000000..c0d7d1b4 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplsmc.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: aplsmc.4,v 1.3 2023/06/22 15:29:05 tobhe Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 22 2023 $ +.Dt APLSMC 4 arm64 +.Os +.Sh NAME +.Nm aplsmc +.Nd Apple System Management Controller (SMC) +.Sh SYNOPSIS +.Cd "aplsmc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the System Management Controller (SMC) +found on various Apple SoCs. +The driver provides a collection of current, fan, power, temperature, +voltage, lid position and battery information sensors. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplspi.4 b/static/openbsd/man4/man4.arm64/aplspi.4 new file mode 100644 index 00000000..54431ce5 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplspi.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: aplspi.4,v 1.1 2021/10/31 17:47:06 kettenis Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 31 2021 $ +.Dt APLSPI 4 arm64 +.Os +.Sh NAME +.Nm aplspi +.Nd Apple SPI controller +.Sh SYNOPSIS +.Cd "aplspi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SPI controller found on various Apple +SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/aplspmi.4 b/static/openbsd/man4/man4.arm64/aplspmi.4 new file mode 100644 index 00000000..71169a29 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/aplspmi.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: aplspmi.4,v 1.2 2021/05/30 12:26:04 jmc Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 30 2021 $ +.Dt APLSPMI 4 arm64 +.Os +.Sh NAME +.Nm aplspmi +.Nd Apple SPMI controller +.Sh SYNOPSIS +.Cd "aplspmi* at fdt?" +.Cd "aplpmu* at aplspmi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SPMI controller found on various Apple +SoCs. +.Sh SEE ALSO +.Xr aplpmu 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/apm.4 b/static/openbsd/man4/man4.arm64/apm.4 new file mode 100644 index 00000000..9c00eec0 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/apm.4 @@ -0,0 +1,178 @@ +.\" $OpenBSD: apm.4,v 1.6 2023/01/30 14:43:29 jcs Exp $ +.\" +.\" Copyright (c) 1998 Marco S. Hyman +.\" +.\" Permission to copy all or part of this material for any purpose is +.\" granted provided that the above copyright notice and this paragraph +.\" are duplicated in all copies. THIS SOFTWARE IS PROVIDED ``AS IS'' +.\" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT +.\" LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE. +.\" +.Dd $Mdocdate: January 30 2023 $ +.Dt APM 4 arm64 +.Os +.Sh NAME +.Nm apm +.Nd power management interface +.Sh SYNOPSIS +.Cd "apm0 at mainbus?" +.Sh DESCRIPTION +The +.Nm +driver provides an interface which simulates the Advanced Power Management +.Pq APM +BIOS functions. +.Pp +Suspend/resume and other power events are +.Em NOT YET SUPPORTED . +.Pp +The +.Nm +driver implements the following +.Xr ioctl 2 +calls. +They are defined in +.In machine/apmvar.h . +.Bl -tag -width Ds +.It Dv APM_IOC_REJECT +.Em Not implemented . DO NOT USE . +.It Dv APM_IOC_STANDBY +.Em NOT YET SUPPORTED on arm64 . +.Pp +.Pq Li "no parameters" +Request +.Dq standby +mode. +.It Dv APM_IOC_SUSPEND +.Em NOT YET SUPPORTED on arm64 . +.Pp +.Pq Li "no parameters" +Request +.Dq suspend +mode. +.It Dv APM_IOC_HIBERNATE +.Em NOT YET SUPPORTED on arm64 . +.Pp +.Pq Li "no parameters" +Request +.Dq hibernate +mode. +.It Dv APM_IOC_GETPOWER +.Pq Li "struct apm_power_info" +Request the current power state. +The argument structure is as follows: +.Bd -literal -offset indent +struct apm_power_info { + u_char battery_state; + u_char ac_state; + u_char battery_life; + u_char spare1; + u_int minutes_left; + u_int spare2[6]; +}; +.Ed +.Pp +The following values are defined for +.Va battery_state : +.Bl -tag -width Ds +.It Dv APM_BATT_HIGH +Battery has a high state of charge. +.It Dv APM_BATT_LOW +Battery has a low state of charge. +.It Dv APM_BATT_CRITICAL +Battery has a critical state of charge. +.It Dv APM_BATT_CHARGING +Battery is not high, low, or critical and is currently charging. +.It Dv APM_BATT_UNKNOWN +Cannot read the current battery state. +.It Dv APM_BATTERY_ABSENT +No battery installed. +.El +.Pp +The following values are defined for +.Va ac_state : +.Bl -tag -width Ds +.It Dv APM_AC_OFF +External power not detected. +.It Dv APM_AC_ON +External power detected. +.It Dv APM_AC_BACKUP +Backup power in use. +.It Dv APM_AC_UNKNOWN +External power state unknown. +.El +.Pp +The +.Va battery_life +value contains the estimated percentage of battery life available. +100% indicates a full charge. +.Pp +The +.Va minutes_left +value contains the estimated number of minutes of battery life +remaining. +.It Dv APM_IOC_DEV_CTL +.Em NOT YET SUPPORTED on arm64 . +.Pp +.Pq Li "struct apm_ctl" +Allows an application to directly set the +APM operating mode. +The argument structure is as follows: +.Bd -literal -offset indent +struct apm_ctl { + u_int dev; + u_int mode; +}; +.Ed +.Pp +.Va dev +indicates the device, typically +.Dv APM_DEV_ALLDEVS . +.Pp +.Va mode +indicates the desired operating mode. +Possible values are +.Bl -tag -width Ds -compact -offset indent +.It Dv APM_SYS_READY +.It Dv APM_SYS_STANDBY +.It Dv APM_SYS_SUSPEND +.It Dv APM_SYS_OFF +.It Dv APM_LASTREQ_INPROG +.It Dv APM_LASTREQ_REJECTED +.El +.It Dv APM_IOC_PRN_CTL +.Pq Li "int" +This +.Xr ioctl 2 +controls message output by the APM +driver when a power change event is detected. +The integer parameter is one of: +.Bl -tag -width Ds +.It Dv APM_PRINT_ON +All power change events result in a message. +This is the normal operating mode for the driver. +.It Dv APM_PRINT_OFF +Power change event messages are suppressed. +.It Dv APM_PRINT_PCT +Power change event messages are suppressed unless the estimated +battery life percentage changes. +.El +.El +.Sh FILES +.Bl -tag -width "/dev/apmctlXXX" +.It /dev/apm +Power management data device. +May only be opened read-only. +May be opened by multiple concurrent users. +.It /dev/apmctl +Power management control device. +May be opened read-write or write-only. +May only be opened by one user at a time. +An attempt to open the file when in use will fail, returning +.Er EBUSY . +.El +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr halt 8 diff --git a/static/openbsd/man4/man4.arm64/intro.4 b/static/openbsd/man4/man4.arm64/intro.4 new file mode 100644 index 00000000..03ba0ef7 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/intro.4 @@ -0,0 +1,117 @@ +.\" $OpenBSD: intro.4,v 1.5 2023/05/03 22:03:17 jmc Exp $ +.\" +.\" Copyright (c) 2014 Sylvestre Gallon +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 3 2023 $ +.Dt INTRO 4 arm64 +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the arm64 +platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The configuration system is described in +.Xr autoconf 4 . +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width 8n -offset 3n -compact +.It Xr acpi 4 +Advanced Configuration and Power Interface +.It Xr iic 4 +Inter IC (I2C) bus +.It Xr onewire 4 +1-Wire bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr usb 4 +introduction to Universal Serial Bus support +.It Xr virtio 4 +VirtIO support driver +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The +arm64 +.Nm +first appeared in +.Ox 6.4 . diff --git a/static/openbsd/man4/man4.arm64/rpiclock.4 b/static/openbsd/man4/man4.arm64/rpiclock.4 new file mode 100644 index 00000000..c2570ee1 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/rpiclock.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: rpiclock.4,v 1.1 2025/09/17 10:56:34 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 17 2025 $ +.Dt RPICLOCK 4 arm64 +.Os +.Sh NAME +.Nm rpiclock +.Nd Raspberry Pi RP1 clock controller +.Sh SYNOPSIS +.Cd "rpiclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the clock signals for integrated components of the RP1 +chip found on the Raspberry Pi 5. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marcus Glocker Aq Mt mglocker@openbsd.org +and +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/rpipwm.4 b/static/openbsd/man4/man4.arm64/rpipwm.4 new file mode 100644 index 00000000..02066e54 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/rpipwm.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: rpipwm.4,v 1.1 2025/09/17 10:56:34 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 17 2025 $ +.Dt RPIPWM 4 arm64 +.Os +.Sh NAME +.Nm rpipwm +.Nd Raspberry Pi RP1 PWM controller +.Sh SYNOPSIS +.Cd "rpipwm* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PWM controllers integrated on the RP1 +chip found on the Raspberry Pi 5. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marcus Glocker Aq Mt mglocker@openbsd.org +and +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/rpirtc.4 b/static/openbsd/man4/man4.arm64/rpirtc.4 new file mode 100644 index 00000000..d052a6de --- /dev/null +++ b/static/openbsd/man4/man4.arm64/rpirtc.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: rpirtc.4,v 1.1 2025/08/24 11:06:32 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 24 2025 $ +.Dt RPIRTC 4 arm64 +.Os +.Sh NAME +.Nm rpirtc +.Nd Raspberry Pi real-time clock +.Sh SYNOPSIS +.Cd "rpirtc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the firmware-managed real-time clock found +in the Raspberry Pi 5. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/rpone.4 b/static/openbsd/man4/man4.arm64/rpone.4 new file mode 100644 index 00000000..18f40e64 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/rpone.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: rpone.4,v 1.2 2025/08/24 10:53:25 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 24 2025 $ +.Dt RPONE 4 arm64 +.Os +.Sh NAME +.Nm rpone +.Nd Raspberry Pi RP1 peripheral controller +.Sh SYNOPSIS +.Cd "rpone* at pci?" +.Cd "cad* at fdt?" +.Cd "xhci* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the Raspberry Pi RP1 peripheral controller that is +used in the Raspberry Pi 5. +The driver acts as a bridge between the PCIe bus and the peripherals +and maps peripheral interrupts onto MSI-X interrupts. +The peripherals themselves are supported by separate drivers. +.Sh SEE ALSO +.Xr cad 4 , +.Xr intro 4 , +.Xr xhci 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.arm64/smbios.4 b/static/openbsd/man4/man4.arm64/smbios.4 new file mode 100644 index 00000000..50106cb2 --- /dev/null +++ b/static/openbsd/man4/man4.arm64/smbios.4 @@ -0,0 +1,36 @@ +.\" $OpenBSD: smbios.4,v 1.1 2019/08/05 07:08:57 jsg Exp $ +.\" +.\" Copyright (c) 2019 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 5 2019 $ +.Dt SMBIOS 4 arm64 +.Os +.Sh NAME +.Nm smbios +.Nd System Management BIOS +.Sh SYNOPSIS +.Cd "smbios0 at efi?" +.Sh DESCRIPTION +System Management BIOS (SMBIOS) describes hardware components. +The +.Nm +driver retrieves information about the firmware and strings identifying the +machine. +.Sh SEE ALSO +.Xr efi 4 +.Rs +.%T System Management BIOS (SMBIOS) Reference Specification +.%N DMTF DSP0134 +.Re diff --git a/static/openbsd/man4/man4.armv7/Makefile b/static/openbsd/man4/man4.armv7/Makefile new file mode 100644 index 00000000..cbbc42c1 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/Makefile @@ -0,0 +1,35 @@ +MAN = agtimer.4 \ + amdisplay.4 \ + ampintc.4 \ + amptimer.4 \ + armliicc.4 \ + cortex.4 \ + cpsw.4 \ + dmtimer.4 \ + edma.4 \ + gptimer.4 \ + imxtemp.4 \ + intc.4 \ + intro.4 \ + mvodog.4 \ + mvortc.4 \ + omap.4 \ + omclock.4 \ + omcm.4 \ + omdog.4 \ + omgpio.4 \ + ommmc.4 \ + omrng.4 \ + omsysc.4 \ + omwugen.4 \ + prcm.4 \ + sxie.4 \ + sxiintc.4 \ + sxitimer.4 \ + sxits.4 \ + sysreg.4 \ + zqclock.4 \ + zqreset.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.armv7/agtimer.4 b/static/openbsd/man4/man4.armv7/agtimer.4 new file mode 100644 index 00000000..b1f9d307 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/agtimer.4 @@ -0,0 +1,33 @@ +.\" $OpenBSD: agtimer.4,v 1.1 2016/09/18 07:03:37 jsg Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 18 2016 $ +.Dt AGTIMER 4 armv7 +.Os +.Sh NAME +.Nm agtimer +.Nd ARM generic timer +.Sh SYNOPSIS +.Cd "agtimer* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ARM generic timer, an optional extension +to the ARM architecture. +.Sh SEE ALSO +.Rs +.%T ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition +.Re diff --git a/static/openbsd/man4/man4.armv7/amdisplay.4 b/static/openbsd/man4/man4.armv7/amdisplay.4 new file mode 100644 index 00000000..4c34a607 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/amdisplay.4 @@ -0,0 +1,76 @@ +.\" $OpenBSD: amdisplay.4,v 1.4 2019/05/29 19:37:06 fcambus Exp $ +.\" +.\" Copyright (c) 2017 Ian Sutton +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 29 2019 $ +.Dt AMDISPLAY 4 armv7 +.Os +.Sh NAME +.Nm amdisplay , +.Nm nxphdmi +.Nd Texas Instruments AM335x LCD display driver +.Sh SYNOPSIS +.Nm "amdisplay* at simplebus0" +.Nm "nxphdmi* at iic*" +.Nm "wsdisplay* at amdisplay*" +.Sh DESCRIPTION +The +.Nm +driver supports the LCD controller integrated in Texas Instruments' line of +AM335x SoCs. +The LCDC reads a framebuffer from memory via DMA and scans it out +at the proper frequency to suit a display (along with the necessary +hsync/vsync/etc. signals) to a PHY transmitter. +The BeagleBone Black uses NXP/Freescale's TDA19988 HDMI transmitter, +which is additionally supported by the +.Nm nxphdmi +driver. +.Sh SEE ALSO +.Xr intro 4 , +.Xr wsdisplay 4 , +.Xr wsfb 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Ian Sutton Aq Mt ians@openbsd.org . +The +.Nm nxphdmi +driver was written by +.An Oleksandr Tymoshenko Aq Mt gonzo@freebsd.org +and later ported to +.Ox . +.Sh CAVEATS +On the BeagleBone Black, the LCDC and onboard eMMC NAND chip share the same set +of pads such that only one can be wired and used at a time. +To boot from or use the onboard storage, disable +.Nm +via +.Xr config 8 +in the kernel. +.Pp +A display must be attached at boot time, otherwise +.Nm +will fail to configure. +.Pp +Hotplugging is not supported. +.Pp +Only 16-bit color depth is supported due to a silicon bug. diff --git a/static/openbsd/man4/man4.armv7/ampintc.4 b/static/openbsd/man4/man4.armv7/ampintc.4 new file mode 100644 index 00000000..1e1141c8 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/ampintc.4 @@ -0,0 +1,36 @@ +.\" $OpenBSD: ampintc.4,v 1.2 2022/10/20 08:52:22 jsg Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 20 2022 $ +.Dt AMPINTC 4 armv7 +.Os +.Sh NAME +.Nm ampintc , +.Nm ampintcmsi +.Nd Arm generic interrupt controller v1/v2 +.Sh SYNOPSIS +.Cd "ampintc* at fdt?" +.Cd "ampintcmsi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Arm Generic Interrupt Controller (GIC) +version 1 and version 2. +.Sh SEE ALSO +.Rs +.%T ARM Generic Interrupt Controller Architecture Specification +.%N ARM IHI 0048 +.Re diff --git a/static/openbsd/man4/man4.armv7/amptimer.4 b/static/openbsd/man4/man4.armv7/amptimer.4 new file mode 100644 index 00000000..f6edcf03 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/amptimer.4 @@ -0,0 +1,30 @@ +.\" $OpenBSD: amptimer.4,v 1.1 2016/09/18 07:03:37 jsg Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 18 2016 $ +.Dt AMPTIMER 4 armv7 +.Os +.Sh NAME +.Nm amptimer +.Nd ARM global timer +.Sh SYNOPSIS +.Cd "amptimer* at cortex?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ARM global timer on Cortex-A9. +.Sh SEE ALSO +.Xr cortex 4 diff --git a/static/openbsd/man4/man4.armv7/armliicc.4 b/static/openbsd/man4/man4.armv7/armliicc.4 new file mode 100644 index 00000000..a3dff1e5 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/armliicc.4 @@ -0,0 +1,34 @@ +.\" $OpenBSD: armliicc.4,v 1.1 2016/09/18 07:03:37 jsg Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 18 2016 $ +.Dt ARMLIICC 4 armv7 +.Os +.Sh NAME +.Nm armliicc +.Nd ARM PL310 L2 cache controller +.Sh SYNOPSIS +.Cd "armliicc* at cortex?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the ARM PL310 level two cache controller +integrated into Cortex-A9. +.Sh SEE ALSO +.Xr cortex 4 +.Rs +.%T PL310 Cache Controller Technical Reference Manual +.Re diff --git a/static/openbsd/man4/man4.armv7/cortex.4 b/static/openbsd/man4/man4.armv7/cortex.4 new file mode 100644 index 00000000..81447d09 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/cortex.4 @@ -0,0 +1,28 @@ +.\" $OpenBSD: cortex.4,v 1.1 2016/09/18 07:03:37 jsg Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 18 2016 $ +.Dt CORTEX 4 armv7 +.Os +.Sh NAME +.Nm cortex +.Nd ARM MPCore complex +.Sh SYNOPSIS +.Cd "cortex0 at mainbus?" +.Sh DESCRIPTION +The +.Nm +driver is used to group the attachment of ARM MPCore peripherals. diff --git a/static/openbsd/man4/man4.armv7/cpsw.4 b/static/openbsd/man4/man4.armv7/cpsw.4 new file mode 100644 index 00000000..00d6b7f0 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/cpsw.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: cpsw.4,v 1.3 2016/06/26 09:06:35 jsg Exp $ +.\" Copyright (c) 2013 Brandon Mercer +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 26 2016 $ +.Dt CPSW 4 armv7 +.Os +.Sh NAME +.Nm cpsw +.Nd Texas Instruments CPSW Ethernet device +.Sh SYNOPSIS +.Cd "cpsw* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Texas Instruments CPSW Ethernet device. +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr mii 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan A. Kollasch Aq Mt jakllsch@NetBSD.org +and ported to +.Ox +by +.An Brandon Mercer Aq Mt bmercer@openbsd.org . diff --git a/static/openbsd/man4/man4.armv7/dmtimer.4 b/static/openbsd/man4/man4.armv7/dmtimer.4 new file mode 100644 index 00000000..df8b6a46 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/dmtimer.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: dmtimer.4,v 1.3 2014/09/19 17:17:04 jmc Exp $ +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 19 2014 $ +.Dt DMTIMER 4 armv7 +.Os +.Sh NAME +.Nm dmtimer +.Nd Texas Instruments dual mode timer device +.Sh SYNOPSIS +.Cd "dmtimer* at omap?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the dual mode timer device integrated in +AM335X SoCs. +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@dalerahn.com . diff --git a/static/openbsd/man4/man4.armv7/edma.4 b/static/openbsd/man4/man4.armv7/edma.4 new file mode 100644 index 00000000..f841af3c --- /dev/null +++ b/static/openbsd/man4/man4.armv7/edma.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: edma.4,v 1.3 2017/03/01 04:39:57 jsg Exp $ +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 1 2017 $ +.Dt EDMA 4 armv7 +.Os +.Sh NAME +.Nm edma +.Nd Texas Instruments enhanced DMA device +.Sh SYNOPSIS +.Cd "edma* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the enhanced Direct Memory Access device integrated +in AM335X SoCs. +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Sylvestre Gallon Aq Mt syl@openbsd.org . diff --git a/static/openbsd/man4/man4.armv7/gptimer.4 b/static/openbsd/man4/man4.armv7/gptimer.4 new file mode 100644 index 00000000..c7770312 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/gptimer.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: gptimer.4,v 1.3 2014/09/19 17:17:04 jmc Exp $ +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 19 2014 $ +.Dt GPTIMER 4 armv7 +.Os +.Sh NAME +.Nm gptimer +.Nd Texas Instruments general purpose timer device +.Sh SYNOPSIS +.Cd "gptimer* at omap?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the general purpose timer device integrated in +OMAP SoCs. +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@dalerahn.com . diff --git a/static/openbsd/man4/man4.armv7/imxtemp.4 b/static/openbsd/man4/man4.armv7/imxtemp.4 new file mode 100644 index 00000000..6835b0a5 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/imxtemp.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: imxtemp.4,v 1.5 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2016 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt IMXTEMP 4 armv7 +.Os +.Sh NAME +.Nm imxtemp +.Nd i.MX6 temperature monitor +.Sh SYNOPSIS +.Cd "imxtemp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor found on the +Freescale i.MX6 SoC processors. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se +and +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.armv7/intc.4 b/static/openbsd/man4/man4.armv7/intc.4 new file mode 100644 index 00000000..e94b01dc --- /dev/null +++ b/static/openbsd/man4/man4.armv7/intc.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: intc.4,v 1.3 2016/08/06 10:07:45 jsg Exp $ +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2016 $ +.Dt INTC 4 armv7 +.Os +.Sh NAME +.Nm intc +.Nd Texas Instruments interrupt controller device +.Sh SYNOPSIS +.Cd "intc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the interrupt controller device integrated in OMAP and +AM335X SoCs. +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@dalerahn.com . diff --git a/static/openbsd/man4/man4.armv7/intro.4 b/static/openbsd/man4/man4.armv7/intro.4 new file mode 100644 index 00000000..fdad4a2a --- /dev/null +++ b/static/openbsd/man4/man4.armv7/intro.4 @@ -0,0 +1,117 @@ +.\" $OpenBSD: intro.4,v 1.7 2023/05/03 22:03:17 jmc Exp $ +.\" +.\" Copyright (c) 2014 Sylvestre Gallon +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 3 2023 $ +.Dt INTRO 4 armv7 +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the armv7 +platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The configuration system is described in +.Xr autoconf 4 . +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width 8n -offset 3n -compact +.It Xr iic 4 +Inter IC (I2C) bus +.It Xr omap 4 +omap3, omap4, am335x SoCs device bus +.It Xr onewire 4 +1-Wire bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr usb 4 +introduction to Universal Serial Bus support +.It Xr virtio 4 +VirtIO support driver +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The +armv7 +.Nm +first appeared in +.Ox 5.7 . diff --git a/static/openbsd/man4/man4.armv7/mvodog.4 b/static/openbsd/man4/man4.armv7/mvodog.4 new file mode 100644 index 00000000..103ae8b0 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/mvodog.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: mvodog.4,v 1.2 2023/03/02 11:56:25 jsg Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 2 2023 $ +.Dt MVODOG 4 armv7 +.Os +.Sh NAME +.Nm mvodog +.Nd Marvell Armada 38x watchdog timer +.Sh SYNOPSIS +.Cd "mvodog* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the integrated watchdog timer in Marvell Armada +38x SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr watchdog 4 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . diff --git a/static/openbsd/man4/man4.armv7/mvortc.4 b/static/openbsd/man4/man4.armv7/mvortc.4 new file mode 100644 index 00000000..4d23c040 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/mvortc.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: mvortc.4,v 1.2 2023/03/02 11:56:25 jsg Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 2 2023 $ +.Dt MVORTC 4 armv7 +.Os +.Sh NAME +.Nm mvortc +.Nd Marvell Armada 38x real-time clock +.Sh SYNOPSIS +.Cd "mvortc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the RTC found on Marvell Armada 38x SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . diff --git a/static/openbsd/man4/man4.armv7/omap.4 b/static/openbsd/man4/man4.armv7/omap.4 new file mode 100644 index 00000000..cee66275 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/omap.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: omap.4,v 1.8 2020/04/05 19:39:21 jmc Exp $ +.\" Copyright (c) 2014 Sylvestre Gallon +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 5 2020 $ +.Dt OMAP 4 armv7 +.Os +.Sh NAME +.Nm omap +.Nd omap3, omap4, am335x SoCs device bus +.Sh SYNOPSIS +.Cd "omap0 at mainbus?" +.Sh DESCRIPTION +The +.Nm +interface serves as an abstraction used by the autoconfiguration +system to help find and attach devices integrated on Texas Instruments SoC +processors. +.Pp +.Nm +provides support for the following devices: +.Pp +.Bl -tag -width 12n -offset indent -compact +.It Xr dmtimer 4 +Texas Instruments dual mode timer device +.It Xr gptimer 4 +Texas Instruments general purpose timer device +.It Xr prcm 4 +Texas Instruments power, reset and clock management device +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr mainbus 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . diff --git a/static/openbsd/man4/man4.armv7/omclock.4 b/static/openbsd/man4/man4.armv7/omclock.4 new file mode 100644 index 00000000..29884433 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/omclock.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: omclock.4,v 1.1 2020/04/10 22:26:46 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 10 2020 $ +.Dt OMCLOCK 4 armv7 +.Os +.Sh NAME +.Nm omclock +.Nd OMAP clock module +.Sh SYNOPSIS +.Cd "omclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the clock controllers found on TI OMAP3, +OMAP4 and AM335x SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr omcm 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.armv7/omcm.4 b/static/openbsd/man4/man4.armv7/omcm.4 new file mode 100644 index 00000000..c8ee1702 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/omcm.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: omcm.4,v 1.1 2020/04/10 22:26:46 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 10 2020 $ +.Dt OMCM 4 armv7 +.Os +.Sh NAME +.Nm omcm +.Nd OMAP clock module +.Sh SYNOPSIS +.Cd "omcm* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the clock modules found on TI OMAP3, OMAP4 +and AM335x SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr omclock 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.armv7/omdog.4 b/static/openbsd/man4/man4.armv7/omdog.4 new file mode 100644 index 00000000..3962c051 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/omdog.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: omdog.4,v 1.4 2016/06/26 05:16:33 jsg Exp $ +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 26 2016 $ +.Dt OMDOG 4 armv7 +.Os +.Sh NAME +.Nm omdog +.Nd Texas Instruments watchdog timer device +.Sh SYNOPSIS +.Cd "omdog* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the watchdog timer device integrated in OMAP and +AM335X SoCs. +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@dalerahn.com . diff --git a/static/openbsd/man4/man4.armv7/omgpio.4 b/static/openbsd/man4/man4.armv7/omgpio.4 new file mode 100644 index 00000000..0098b03b --- /dev/null +++ b/static/openbsd/man4/man4.armv7/omgpio.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: omgpio.4,v 1.3 2016/08/11 04:33:06 jsg Exp $ +.\" +.\" Copyright (c) 2013 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 11 2016 $ +.Dt OMGPIO 4 armv7 +.Os +.Sh NAME +.Nm omgpio +.Nd omap3, omap4 and am335x GPIO controller +.Sh SYNOPSIS +.Cd "omgpio* at fdt?" +.Cd "gpio* at omgpio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO controllers found on omap3, omap4 and +am335x SoCs. +The devices have 32 pins which can be configured as either inputs or outputs, +and accessed using +.Xr gpioctl 8 . +.\" Both values are made available through the +.\" .Xr sysctl 8 +.\" interface. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@dalerahn.com . diff --git a/static/openbsd/man4/man4.armv7/ommmc.4 b/static/openbsd/man4/man4.armv7/ommmc.4 new file mode 100644 index 00000000..51a70eb3 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/ommmc.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: ommmc.4,v 1.2 2016/06/18 05:59:26 jsg Exp $ +.\" Copyright (c) 2013 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.\" Uwe Stuehler, 2007. Public Domain. +.\" +.Dd $Mdocdate: June 18 2016 $ +.Dt OMMMC 4 armv7 +.Os +.Sh NAME +.Nm ommmc +.Nd MMC/SD/SDIO controller +.Sh SYNOPSIS +.Cd "ommmc* at fdt?" +.Cd "sdmmc* at ommmc?" +.Sh DESCRIPTION +The +.Nm +driver supports the MMC/SD/SDIO controller integrated in OMAP and +AM335X processors. +.Pp +The +.Xr sdmmc 4 +subsystem performs SD/MMC transactions to communicate with whatever +MMC/SD/SDIO devices are inserted into the card slot. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sdmmc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@dalerahn.com . diff --git a/static/openbsd/man4/man4.armv7/omrng.4 b/static/openbsd/man4/man4.armv7/omrng.4 new file mode 100644 index 00000000..574e710b --- /dev/null +++ b/static/openbsd/man4/man4.armv7/omrng.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: omrng.4,v 1.2 2020/04/05 19:37:55 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 5 2020 $ +.Dt OMRNG 4 armv7 +.Os +.Sh NAME +.Nm omrng +.Nd OMAP random number generator +.Sh SYNOPSIS +.Cd "omrng* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the random number generator found on TI +OMAP3, OMAP4 and AM335x SoCs. +.Pp +It feeds the random subsystem's entropy pool with 64 bits of random +data every second. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.armv7/omsysc.4 b/static/openbsd/man4/man4.armv7/omsysc.4 new file mode 100644 index 00000000..dafd60b6 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/omsysc.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: omsysc.4,v 1.1 2020/04/10 22:26:46 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 10 2020 $ +.Dt OMSYSC 4 armv7 +.Os +.Sh NAME +.Nm omsysc +.Nd OMAP interconnect target module +.Sh SYNOPSIS +.Cd "omsysc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the interconnect target modules found on +TI OMAP3, OMAP4 and AM335x SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.armv7/omwugen.4 b/static/openbsd/man4/man4.armv7/omwugen.4 new file mode 100644 index 00000000..b87a70df --- /dev/null +++ b/static/openbsd/man4/man4.armv7/omwugen.4 @@ -0,0 +1,30 @@ +.\" $OpenBSD: omwugen.4,v 1.2 2016/09/15 22:38:17 jmc Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 15 2016 $ +.Dt OMWUGEN 4 armv7 +.Os +.Sh NAME +.Nm omwugen +.Nd OMAP wake-up generator +.Sh SYNOPSIS +.Cd "omwugen* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver handles the wake-up generator logic present in OMAP4 and OMAP5 SoCs +which routes interrupts to +.Xr ampintc 4 . diff --git a/static/openbsd/man4/man4.armv7/prcm.4 b/static/openbsd/man4/man4.armv7/prcm.4 new file mode 100644 index 00000000..853835cd --- /dev/null +++ b/static/openbsd/man4/man4.armv7/prcm.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: prcm.4,v 1.2 2014/09/19 17:17:04 jmc Exp $ +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 19 2014 $ +.Dt PRCM 4 armv7 +.Os +.Sh NAME +.Nm prcm +.Nd Texas Instruments power, reset and clock management device +.Sh SYNOPSIS +.Cd "prcm* at omap?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Texas Instruments power, reset and clock +management device. +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@dalerahn.com . diff --git a/static/openbsd/man4/man4.armv7/sxie.4 b/static/openbsd/man4/man4.armv7/sxie.4 new file mode 100644 index 00000000..f97ba78d --- /dev/null +++ b/static/openbsd/man4/man4.armv7/sxie.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: sxie.4,v 1.4 2016/06/26 10:12:29 jsg Exp $ +.\" +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 26 2016 $ +.Dt SXIE 4 armv7 +.Os +.Sh NAME +.Nm sxie +.Nd A1X/A20 EMAC 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "sxie* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the EMAC 10/100 Ethernet device integrated in +Allwinner Technology A1X/A20 SoCs. +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr mii 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.5 . diff --git a/static/openbsd/man4/man4.armv7/sxiintc.4 b/static/openbsd/man4/man4.armv7/sxiintc.4 new file mode 100644 index 00000000..6abc6374 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/sxiintc.4 @@ -0,0 +1,34 @@ +.\" $OpenBSD: sxiintc.4,v 1.2 2016/08/06 00:16:50 jsg Exp $ +.\" +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2016 $ +.Dt SXIINTC 4 armv7 +.Os +.Sh NAME +.Nm sxiintc +.Nd A1X interrupt controller device +.Sh SYNOPSIS +.Cd "sxiintc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the interrupt controller device integrated in +Allwinner Technology A1X SoCs. +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.5 . diff --git a/static/openbsd/man4/man4.armv7/sxitimer.4 b/static/openbsd/man4/man4.armv7/sxitimer.4 new file mode 100644 index 00000000..e873a67d --- /dev/null +++ b/static/openbsd/man4/man4.armv7/sxitimer.4 @@ -0,0 +1,34 @@ +.\" $OpenBSD: sxitimer.4,v 1.3 2019/02/01 01:30:07 jsg Exp $ +.\" +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 1 2019 $ +.Dt SXITIMER 4 armv7 +.Os +.Sh NAME +.Nm sxitimer +.Nd A1X/A20 timer device +.Sh SYNOPSIS +.Cd "sxitimer* at fdt? early 1" +.Sh DESCRIPTION +The +.Nm +driver provides support for the timer devices integrated in Allwinner Technology +A1X/A20 SoCs. +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.5 . diff --git a/static/openbsd/man4/man4.armv7/sxits.4 b/static/openbsd/man4/man4.armv7/sxits.4 new file mode 100644 index 00000000..6a32ec08 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/sxits.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: sxits.4,v 1.3 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt SXITS 4 armv7 +.Os +.Sh NAME +.Nm sxits +.Nd Allwinner touchpad controller +.Sh SYNOPSIS +.Cd "sxits* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor found on the +touchpad controller of the Allwinner A10, A10s/A13 and A20 SoCs. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.armv7/sysreg.4 b/static/openbsd/man4/man4.armv7/sysreg.4 new file mode 100644 index 00000000..37458fc7 --- /dev/null +++ b/static/openbsd/man4/man4.armv7/sysreg.4 @@ -0,0 +1,36 @@ +.\" $OpenBSD: sysreg.4,v 1.2 2016/10/08 06:45:02 jsg Exp $ +.\" +.\" Copyright (c) 2015 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 8 2016 $ +.Dt SYSREG 4 armv7 +.Os +.Sh NAME +.Nm sysreg +.Nd ARM Motherboard Express microATX system registers +.Sh SYNOPSIS +.Cd "sysreg* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the ARM Motherboard Express microATX system registers. +.Rs +.%T ARM Motherboard Express microATX Technical Reference Manual +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.8 . diff --git a/static/openbsd/man4/man4.armv7/zqclock.4 b/static/openbsd/man4/man4.armv7/zqclock.4 new file mode 100644 index 00000000..da5754fa --- /dev/null +++ b/static/openbsd/man4/man4.armv7/zqclock.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: zqclock.4,v 1.2 2021/04/30 13:52:12 jmc Exp $ +.\" +.\" Copyright (c) 2021 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 30 2021 $ +.Dt ZQCLOCK 4 armv7 +.Os +.Sh NAME +.Nm zqclock +.Nd Xilinx Zynq-7000 clock controller +.Sh SYNOPSIS +.Cd "zqclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the clock signals for the integrated components +of Zynq-7000 SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr zqreset 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . diff --git a/static/openbsd/man4/man4.armv7/zqreset.4 b/static/openbsd/man4/man4.armv7/zqreset.4 new file mode 100644 index 00000000..ac7fde7f --- /dev/null +++ b/static/openbsd/man4/man4.armv7/zqreset.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: zqreset.4,v 1.2 2021/04/30 13:52:12 jmc Exp $ +.\" +.\" Copyright (c) 2021 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 30 2021 $ +.Dt ZQRESET 4 armv7 +.Os +.Sh NAME +.Nm zqreset +.Nd Xilinx Zynq-7000 reset controller +.Sh SYNOPSIS +.Cd "zqreset* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the reset signals for the integrated components +of Zynq-7000 SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr zqclock 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . diff --git a/static/openbsd/man4/man4.hppa/Makefile b/static/openbsd/man4/man4.hppa/Makefile new file mode 100644 index 00000000..7d0f06ab --- /dev/null +++ b/static/openbsd/man4/man4.hppa/Makefile @@ -0,0 +1,25 @@ +MAN = asp.4 \ + astro.4 \ + cpu.4 \ + dino.4 \ + elroy.4 \ + gecko.4 \ + gsc.4 \ + gsckbc.4 \ + harmony.4 \ + ie.4 \ + intro.4 \ + io.4 \ + lasi.4 \ + lcd.4 \ + mem.4 \ + mongoose.4 \ + pdc.4 \ + phantomas.4 \ + power.4 \ + runway.4 \ + ssio.4 \ + uturn.4 \ + wax.4 + +include ../../../mandoc.mk diff --git a/static/openbsd/man4/man4.hppa/asp.4 b/static/openbsd/man4/man4.hppa/asp.4 new file mode 100644 index 00000000..517ab818 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/asp.4 @@ -0,0 +1,97 @@ +.\" $OpenBSD: asp.4,v 1.18 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" +.\" Copyright (c) 1999 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt ASP 4 hppa +.Os +.Sh NAME +.Nm asp +.Nd core bus controller as present on older HP 9000/700 machines +.Sh SYNOPSIS +.Cd "asp0 at mainbus? irq 28" +.Cd "gsc* at asp?" +.Sh DESCRIPTION +The supported Core bus controllers are those present on older +.Tn PA-RISC +workstations, and include: +.Pp +.Bl -bullet -compact +.It +Core bus controller +.It +System clock +.It +Interrupt controller +.It +DMA controller +.It +Real-time clock Interface +.It +RAM and EEPROM controllers +.El +.Pp +The irq level supplied is hardwired to the CPU pin, so changing the value +would not produce any noticeable results (except lost interrupts for the whole +I/O subsystem). +.Sh MACHINES +An incomplete list of machines that use the +.Tn ASP +bus controller: +.Pp +.Bl -bullet -compact +.It +705, 710 +.It +715/{33,50,75} +.It +725/{50,75} +.It +720, 730, 750 +.It +735/* +.It +745i/{50,75} +.It +747i/{50,75} +.It +755/* +.El +.Sh SEE ALSO +.Xr gsc 4 , +.Xr intro 4 , +.Xr io 4 +.Rs +.%T "Hardball I/O Subsystem ERS" +.%N Revision 1.1 +.%D 30 September 1991 +.%Q Hewlett-Packard +.Re +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.4 . diff --git a/static/openbsd/man4/man4.hppa/astro.4 b/static/openbsd/man4/man4.hppa/astro.4 new file mode 100644 index 00000000..56fac913 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/astro.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: astro.4,v 1.3 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" Copyright (c) 2007 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt ASTRO 4 hppa +.Os +.Sh NAME +.Nm astro +.Nd Astro Memory and I/O controller +.Sh SYNOPSIS +.Cd "astro* at mainbus?" +.Cd "elroy* at astro?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Astro memory and I/O controller used +on systems with PA-8500 and later 64-bit CPUs. +It functions as a bridge from the Runway bus to +up to 8 I/O ropes that connect to Elroy chips. +Astro contains an IOMMU and provides support for cache coherent DMA. +.Sh SEE ALSO +.Xr cpu 4 , +.Xr elroy 4 , +.Xr intro 4 , +.Xr runway 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . diff --git a/static/openbsd/man4/man4.hppa/cpu.4 b/static/openbsd/man4/man4.hppa/cpu.4 new file mode 100644 index 00000000..e40e156f --- /dev/null +++ b/static/openbsd/man4/man4.hppa/cpu.4 @@ -0,0 +1,243 @@ +.\" $OpenBSD: cpu.4,v 1.1 2022/07/11 03:11:49 daniel Exp $ +.\" +.\" Copyright (c) 2002 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR OR HIS RELATIVES BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF MIND, USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING +.\" IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 11 2022 $ +.Dt CPU 4 hppa +.Os +.Sh NAME +.Nm cpu +.Nd HP PA-RISC CPU +.Sh SYNOPSIS +.Cd "cpu* at mainbus0 irq 31" +.Sh DESCRIPTION +The following table lists the +.Tn PA-RISC +CPU types and their characteristics, such as TLB, maximum +cache sizes (where the +.Sq * +character means on-chip) and +.Tn HP 9000/700 +machines they were used in (see also +.Xr intro 4 +for the reverse list). +.Bl -column "7100LC" "1.1e" "MHz max" "2048 L1D*" "TLB" "BAT" "C3650, C3700, C3750" +.It Sy CPU Ta Sy PA Ta Sy Clock Ta Sy Caches Ta Sy TLB Ta Sy BAT Ta Sy Models +.It Ta Ta MHz max Ta KB max Ta Ta Ta "" +.It 7000 Ta 1.1a Ta 66 Ta 256 L1I Ta 96I Ta 4I Ta 705, 710, 720 +.It Ta Ta Ta 256 L1D Ta 96D Ta 4D Ta 730, 750 +.It 7100 Ta 1.1b Ta 100 Ta 1024 L1I Ta 120 Ta 16 Ta 715/33/50/75 +.It Ta Ta Ta 2048 L1D Ta Ta Ta 725/50/75 +.It Ta Ta Ta Ta Ta Ta {735,755}/100 +.It Ta Ta Ta Ta Ta Ta 742i, 745i, 747i +.It 7150 Ta 1.1b Ta 125 Ta 1024 L1I Ta 120 Ta 16 Ta 735/125, 755/125 +.It Ta Ta Ta 2048 L1D Ta Ta Ta "" +.It 7100LC Ta 1.1c Ta 100 Ta 1 L1I* Ta 64 Ta 8 Ta 712/60/80/100 +.It Ta Ta Ta 1024 L2I Ta Ta Ta 715/64/80/100 +.It Ta Ta Ta 1024 L2D Ta Ta Ta 715/100XC +.It Ta Ta Ta Ta Ta Ta 725/64/100 +.It Ta Ta Ta Ta Ta Ta 743i, 748i +.It Ta Ta Ta Ta Ta Ta SAIC +.It 7200 Ta 1.1d Ta 140 Ta 2 L1* Ta 120 Ta 16 Ta C100, C110 +.It Ta Ta Ta 1024 L2I Ta Ta Ta J200, J210 +.It Ta Ta Ta 1024 L2D Ta Ta Ta "" +.It 7300LC Ta 1.1e Ta 180 Ta 64 L1I* Ta 96 Ta 8 Ta A180, A180C +.It Ta Ta Ta 64 L1D* Ta Ta Ta B132, B160, B180 +.It Ta Ta Ta 8192 L2 Ta Ta Ta C132L, C160L +.It Ta Ta Ta Ta Ta Ta 744, 745, 748 +.It Ta Ta Ta Ta Ta Ta RDI PrecisionBook +.It 8000 Ta 2.0 Ta 180 Ta 1024 L1I Ta 96 Ta Ta C160, C180 +.It Ta Ta Ta 1024 L1D Ta Ta Ta J280, J282 +.It 8200 Ta 2.0 Ta 300 Ta 2048 L1I Ta 120 Ta Ta C200, C240 +.It Ta Ta Ta 2048 L1D Ta Ta Ta J2240 +.It 8500 Ta 2.0 Ta 440 Ta 512 L1I* Ta 160 Ta Ta A400, A500, C360 +.It Ta Ta Ta 1024 L1D* Ta Ta Ta B1000, B2000, C3000 +.It Ta Ta Ta Ta Ta Ta J5000, J7000 +.It 8600 Ta 2.0 Ta 550 Ta 512 L1I* Ta 160 Ta Ta A400, A500, C3600 +.It Ta Ta Ta 1024 L1D* Ta Ta Ta B2000, B2600 +.It Ta Ta Ta Ta Ta Ta J5600, J6000, J7600 +.It 8700 Ta 2.0 Ta 875 Ta 768 L1I* Ta 240 Ta Ta A400, A500, J6700 +.It Ta Ta Ta 1536 L1D* Ta Ta Ta C3650, C3700, C3750 +.El +.Sh FLOATING-POINT COPROCESSOR +The following table summarizes available floating-point coprocessor +models for the 32-bit +.Tn PA-RISC +processors. +.Bl -column "Sterling I MIU (ROC w/Weitek)" "712/60/80/100" +.It Sy FPU Ta Sy Model +.It Indigo Ta "" +.It Sterling I MIU (TYCO) Ta "" +.It Sterling I MIU (ROC w/Weitek) Ta "" +.It FPC (w/Weitek) Ta "" +.It FPC (w/Bit) Ta "" +.It Timex-II Ta "" +.It Rolex Ta 725/50, 745i +.It HARP-I Ta "" +.It Tornado Ta J2x0,C1x0 +.It PA-50 (Hitachi) Ta "" +.It PCXL Ta 712/60/80/100 +.El +.Sh SUPERSCALAR EXECUTION +The following table summarizes the superscalar execution capabilities +of 32-bit +.Tn PA-RISC +processors. +.Bl -column "7100LC" "2 integer ALU" "4-way superscalar" +.It Sy CPU Ta Sy Units Ta Sy Bundles +.It 7100 Ta 1 integer ALU Ta load-store/fp +.It Ta 1 FP Ta int/fp +.It Ta Ta branch/* +.It 7100LC Ta 2 integer ALU Ta load-store/int +.It Ta 1 FP Ta load-store/fp +.It Ta Ta int/fp +.It Ta Ta branch/* +.It 7200 Ta 2 integer ALU Ta load-store/int +.It Ta 1 FP Ta load-store/fp +.It Ta Ta int/int +.It Ta Ta int/fp +.It Ta Ta branch/* +.It 7300LC Ta 2 integer ALU Ta load-store/int +.It Ta 1 FP Ta load-store/fp +.It Ta Ta int/fp +.It Ta Ta branch/* +.It 8x00 Ta 2 integer ALU Ta 4-way superscalar +.It Ta 2 shift/merge Ta "" +.It Ta 2 load/store Ta "" +.It Ta 2 FPU mul/add Ta "" +.It Ta 2 FPU div/sqrt Ta "" +.El +.Pp +In conclusion, all of the above CPUs are dual-issue, or 2-way superscalar, +with the exception that on CPUs with two integer ALUs only one of these +units is capable of doing shift, load/store and test operations. +Additionally, there are several kinds of restrictions placed upon the +superscalar execution: +.Pp +For the purpose of showing which instructions are allowed to proceed +together through the pipeline, they are divided into classes: +.Bl -column "fsys" "FTEST and FP status/exception" +.It Sy Class Ta Sy Description +.It flop Ta floating point operation +.It ldst Ta loads and stores +.It flex Ta integer ALU +.It mm Ta shifts, extracts and deposits +.It nul Ta might nullify successor +.It bv Ta BV, BE +.It br Ta other branches +.It fsys Ta FTEST and FP status/exception +.It sys Ta system control instructions +.El +.Pp +For CPUs with two integer ALUs (7100LC, 7200, 7300LC), the following +table lists the instructions which are allowed to be executed +concurrently: +.Bl -column "flex" "flop/ldst/flex/mm/nul/br/fsys" +.It Sy First Ta Sy Second instruction +.It flop Ta + ldst/flex/mm/nul/bv/br +.It ldst Ta + flop/flex/mm/nul/br +.It flex Ta + flop/ldst/flex/mm/nul/br/fsys +.It mm Ta + flop/ldst/flex/fsys +.It nul Ta + flop +.It sys Ta never bundled +.El +.Pp +ldst + ldst is also possible under certain circumstances, which is then +called "double word load/store". +.Pp +The following restrictions are placed upon the superscalar execution: +.Pp +.Bl -bullet -compact +.It +An instruction that modifies a register will not be bundled with another +instruction that takes this register as operand. +Exception: a flop can be bundled with an FP store of the flop's result register. +.It +An FP load to one word of a doubleword register will not be bundled with +a flop that uses the other doubleword of this register. +.It +A flop will not be bundled with an FP load if both instructions have the +same target register. +.It +An instruction that could set the carry/borrow bits will not be bundled +with an instruction that uses +carry/borrow bits. +.It +An instruction which is in the delay slot of a branch is never bundled +with other instructions. +.It +An instruction which is at an odd word address and executed as a target +of a taken branch is never bundled. +.It +An instruction which might nullify its successor is never bundled with +this successor. +Only if the successor is a flop instruction is this bundle allowed. +.El +.Sh PERFORMANCE MONITOR COPROCESSOR +The performance monitor coprocessor is an optional, +implementation-dependent coprocessor which provides a minimal common +software interface to implementation-dependent performance monitor hardware. +.Sh DEBUG SPECIAL UNIT +The debug special function unit is an optional, +architected SFU which provides hardware assistance for software debugging +using breakpoints. +The debug SFU is currently defined only for Level 0 processors. +.Sh SEE ALSO +.Xr asp 4 , +.Xr intro 4 , +.Xr lasi 4 , +.Xr mem 4 , +.Xr pdc 4 , +.Xr wax 4 +.Rs +.%T PA-RISC 1.1 Architecture and Instruction Set Reference Manual +.%A Hewlett-Packard +.%D May 15, 1996 +.Re +.Rs +.%T PA7100LC ERS +.%A Hewlett-Packard +.%D March 30 1999 +.%N Public version 1.0 +.Re +.Rs +.%T Design of the PA7200 CPU +.%A Hewlett-Packard Journal +.%D February 1996 +.Re +.Rs +.%T PA7300LC ERS +.%A Hewlett-Packard +.%D March 18 1996 +.%N Version 1.0 +.Re +.Sh HISTORY +The +.Nm +driver was written by +.An Michael Shalayeff Aq Mt mickey@openbsd.org +for the HPPA +port for +.Ox 2.5 . diff --git a/static/openbsd/man4/man4.hppa/dino.4 b/static/openbsd/man4/man4.hppa/dino.4 new file mode 100644 index 00000000..5ffc2aff --- /dev/null +++ b/static/openbsd/man4/man4.hppa/dino.4 @@ -0,0 +1,74 @@ +.\" $OpenBSD: dino.4,v 1.6 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" Copyright (c) 2003 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, +.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt DINO 4 hppa +.Os +.Sh NAME +.Nm dino +.Nd Dino and Cujo Host/PCI bridges +.Sh SYNOPSIS +.Cd "dino* at phantomas?" +.Cd "dino* at uturn?" +.Cd "com1 at dino? irq 11" +.Cd "pci* at dino?" +.Sh DESCRIPTION +This driver supports +.Tn Dino +and +.Tn Cujo +Host/PCI bridges found on the A, B, C and J-class workstations. +.Tn Cujo +is a 64 bit datapath version of +.Tn Dino . +.Pp +On some machines it may also provide an additional serial port through the +.Xr com 4 +driver, or +.Tn PS/2 +keyboard and mouse ports, though the latter are not yet supported. +.Sh SEE ALSO +.Xr com 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr phantomas 4 , +.Xr uturn 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 3.5 . +.Sh BUGS +.Nm +bridges of revision earlier than three may exhibit data corruption on DMA. +This hardware bug does not affect +.Nm cujo +or card mode +.Nm +bridges. +See HP Service Note Numbers A4190A-01 and A4191A-01 for more details. +Systems affected are those shipped before Aug 20, 1997 and +of models: B132L, B160L, C160, C180, C200, C240. diff --git a/static/openbsd/man4/man4.hppa/elroy.4 b/static/openbsd/man4/man4.hppa/elroy.4 new file mode 100644 index 00000000..cffa9aae --- /dev/null +++ b/static/openbsd/man4/man4.hppa/elroy.4 @@ -0,0 +1,39 @@ +.\" $OpenBSD: elroy.4,v 1.2 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" Copyright (c) 2007 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt ELROY 4 hppa +.Os +.Sh NAME +.Nm elroy +.Nd Elroy PCI hostbridge +.Sh SYNOPSIS +.Cd "elroy* at astro?" +.Cd "pci* at elroy?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Elroy PCI hostbridge and its embedded +I/O SAPIC interrupt controller. +.Sh SEE ALSO +.Xr astro 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . diff --git a/static/openbsd/man4/man4.hppa/gecko.4 b/static/openbsd/man4/man4.hppa/gecko.4 new file mode 100644 index 00000000..0f0b4ea5 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/gecko.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: gecko.4,v 1.2 2008/04/27 19:34:00 jmc Exp $ +.\" +.\" Copyright (c) 2007 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 27 2008 $ +.Dt GECKO 4 hppa +.Os +.Sh NAME +.Nm gecko +.Nd GeckoBOA BC GSC+ port +.Sh SYNOPSIS +.Cd "gecko* at uturn?" +.Sh DESCRIPTION +.Nm +provides support for the GeckoBOA bus converter ports connecting additional +GSC+ buses to +.Xr uturn 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr uturn 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 4.4 . diff --git a/static/openbsd/man4/man4.hppa/gsc.4 b/static/openbsd/man4/man4.hppa/gsc.4 new file mode 100644 index 00000000..b441fe05 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/gsc.4 @@ -0,0 +1,113 @@ +.\" $OpenBSD: gsc.4,v 1.27 2011/12/21 23:12:03 miod Exp $ +.\" +.\" +.\" Copyright (c) 1999 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 21 2011 $ +.Dt GSC 4 hppa +.Os +.Sh NAME +.Nm gsc +.Nd introduction to HP 9000/700 GSC bus support +.Sh SYNOPSIS +.Cd "gsc* at lasi?" +.Cd "gsc* at asp?" +.Cd "gsc* at wax?" +.Sh DESCRIPTION +The General System Connect (GSC) bus +is the core I/O bus for all HP 9000/700 workstations. +All I/O subsystems connect to this bus. +The devices can be either on separate chips, expansion +cards or on an integrated megacell, like the LASI MBA. +.Pp +The +.Tn GSC +bus is a 32-bit wide, address and data multiplexed bus. +In its "standard" implementation it has a maximum throughput of 160MB/s, +the "2x" implementation reaches up to 250MB/s. +Some HPPA CPUs directly attach to this bus, namely the PA7100LC and PA7300LC. +.Pp +As for the expansion cards, there are different form-factors, depending on +bus-speed (standard or 2x) and specific models. +The standard formfactor is the "EISA form-factor"; cards that look like +typical EISA cards with a different connector (100-pin female EBBL). +The Series 712 have their own special type +of GSC expansion cards, called the "GIO form-factor", which is quite small and +mostly has only one VLSI chip on it (in most cases LASI/WAX). +Newer systems sometimes feature the "HSC formfactor", which is a 1U-VME +card-like expansion card with a 100-pin male pin+socket connector. +Mixing cards with different speeds is supported but downgrades +the performance of the whole I/O-subsystem. +.Pp +.Ox +provides support for the following devices: +.Pp +.Bl -tag -width 12n -offset indent -compact +.It Xr arcofi 4 +Siemens PSB2160 audio codec +.It Xr com 4 +serial communications interface +.It Xr gsckbc 4 +PC-style keyboard controller +.It Xr harmony 4 +CS4215/AD1849 audio +.It Xr hil 4 +introduction to HP-HIL support +.It Xr ie 4 +Intel i82596 Ethernet device +.It Xr lpt 4 +parallel port driver +.It Xr oosiop 4 +.Tn Symbios/NCR +53C700 SCSI I/O Processor +.It Xr osiop 4 +.Tn Symbios/NCR +53C710 SCSI I/O Processor +.El +.Pp +Some of these +.Tn GSC +devices also have +.Tn PCI , +.Tn EISA , +or +.Tn ISA +equivalents. +These are listed in +.Xr pci 4 , +.Xr eisa 4 , +or +.Xr isa 4 . +.Sh SEE ALSO +.Xr asp 4 , +.Xr cpu 4 , +.Xr intro 4 , +.Xr lasi 4 , +.Xr wax 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.6 . diff --git a/static/openbsd/man4/man4.hppa/gsckbc.4 b/static/openbsd/man4/man4.hppa/gsckbc.4 new file mode 100644 index 00000000..9ba2a420 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/gsckbc.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: gsckbc.4,v 1.5 2008/07/16 16:32:08 miod Exp $ +.\" +.\" Copyright (c) 2003, Miodrag Vallat. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2008 $ +.Dt GSCKBC 4 hppa +.Os +.Sh NAME +.Nm gsckbc +.Nd PS/2-like controller driver +.Sh SYNOPSIS +.Cd "gsckbc* at gsc? irq 26" +.Cd "pckbd* at gsckbc?" +.Cd "pms* at gsckbc?" +.Sh DESCRIPTION +The +.Nm +driver handles resource allocation and device attachment for the +PS/2 input device ports. +Each +.Nm +driver provides the logical connection for one child device, either the +.Dq keyboard +port or the +.Dq mouse +port. +.Sh SEE ALSO +.Xr gsc 4 , +.Xr pckbd 4 , +.Xr pms 4 diff --git a/static/openbsd/man4/man4.hppa/harmony.4 b/static/openbsd/man4/man4.hppa/harmony.4 new file mode 100644 index 00000000..b7ccaac8 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/harmony.4 @@ -0,0 +1,89 @@ +.\" $OpenBSD: harmony.4,v 1.9 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" +.\" Copyright (c) 2003 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt HARMONY 4 hppa +.Os +.Sh NAME +.Nm harmony +.Nd CS4215/AD1849 audio device +.Sh SYNOPSIS +.Cd "harmony* at gsc? irq 13" +.Cd "audio* at harmony?" +.Sh DESCRIPTION +The +.Nm +device uses the +.Tn Crystal Semiconductor +.Tn CS4215 +16-Bit Multimedia Audio Codec +or +.Tn Analog Devices +.Tn AD1849 +.Tn SoundPort(R) Stereo Codec +chip to implement the audio device interface described in +.Xr audio 4 . +This device is found on most +.Tn HP PA-RISC +workstations. +The +.Nm +has a maximum precision of 16 bits and has a stereo input and stereo output. +.Pp +On +.Tn HP 9000/712 +models +.Nm +also provides two additional channels for an add-on +card with two fax/voice modems. +.Pp +One of the hardware registers reflects the state of the +.Tn CHI +bus that is used to communicate with the codec and thus +being sampled at a low accuracy secondary frequency +(such as +.Xr timeout 9 ) +produces poor quality random bit stream that is fed into the +entropy pool of +.Xr random 4 . +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr audio 4 , +.Xr gsc 4 , +.Xr intro 4 , +.Xr random 4 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 3.3 . +.Sh CAVEATS +To trigger entropy collection +.Tn CHI +bus has to be programmed into the data mode that happens once +a single buffer of data has been played or recorded. diff --git a/static/openbsd/man4/man4.hppa/ie.4 b/static/openbsd/man4/man4.hppa/ie.4 new file mode 100644 index 00000000..2b90625b --- /dev/null +++ b/static/openbsd/man4/man4.hppa/ie.4 @@ -0,0 +1,90 @@ +.\" $OpenBSD: ie.4,v 1.16 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" Copyright (c) 2003 Paul Weissmann +.\" All rights reserved. +.\" +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt IE 4 hppa +.Os +.Sh NAME +.Nm ie +.Nd Intel i82596 Ethernet device +.Sh SYNOPSIS +.Cd "ie0 at gsc? irq 8" +.Sh DESCRIPTION +The +.Nm +interface provides access to the 10 Mb/s +.Tn Ethernet +network via the +.Tn Intel +i82596 DX/CA 32-bit +Local Area Network Coprocessor for Ethernet. +.Pp +The i82596 comes basically in two different flavors: +.Bl -tag -width i82596DXxxx +.It i82596DX +Systems with an ASP or WAX Main Bus Adapter (MBA), e.g. 720, 735 etc. +These types of systems generally have only AUI or BNC and AUI connectors at +the back. +On the models with both you usually have to switch a big +jumper-block on the mainboard to choose which one to activate. +.It i82596CA +Systems with LASI MBA, e.g. 712/*, 715/100 have the i82596CA +integrated on the LASI macrochip. +They usually have TP and AUI +connectors and autodetect to which one the network is connected to. +.El +.Pp +By default, the system will select the media type automatically, but the +.Xr ifconfig 8 +command can be used to force the media selection. +The media types are shown below: +.Bl -tag -width "media autoselect" -offset indent +.It media autoselect +Attempt to autoselect the media type (default) +.It media 10base5 +Use the AUI connector +.It media 10baseT +Use the twisted pair connector +.It media 10base2 +Use the BNC connector +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr io 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T 82596DX AND 82596SX High-Performance 32-bit Local Area Network Coprocessor +.%Q Intel +.Re +.Rs +.%T 82596CA High-Performance 32-bit Local Area Network Coprocessor +.%Q Intel +.Re diff --git a/static/openbsd/man4/man4.hppa/intro.4 b/static/openbsd/man4/man4.hppa/intro.4 new file mode 100644 index 00000000..17d5a2c3 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/intro.4 @@ -0,0 +1,228 @@ +.\" $OpenBSD: intro.4,v 1.25 2022/03/31 17:27:21 naddy Exp $ +.\" +.\" Copyright (c) 2002,2003 Paul Weissmann +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt INTRO 4 hppa +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +This section describes the special files, related driver functions, +and networking support available in the system. +In this part of the manual, +the SYNOPSIS section of each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the +.Tn HP PA-RISC +platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Character and block devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, +enable the software support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, the system must be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +.Sh SUPPORTED SYSTEMS +A list of +.Tn HP 9000/700 +models targeted for support is listed below, including basic +system characteristics. +.Bl -column "J210XC" "200" "7300LC" "64/64(+1MB)" "Expansion" -offset left +.It Sy "Model" Ta Sy "MHz" Ta Sy "CPU" Ta Sy "Caches, KB" Ta Sy "Expansion" +.It "705" Ta "35" Ta "7000" Ta "32/64" Ta "N/A" +.It "710" Ta "50" Ta "7000" Ta "32/64" Ta "N/A" +.It "720" Ta "50" Ta "7000" Ta "128/256" Ta "EISA, GSC" +.It "730" Ta "66" Ta "7000" Ta "128/256" Ta "EISA, GSC" +.It "750" Ta "66" Ta "7000" Ta "256/256" Ta "4 EISA, 2 SGC" +.It "715" Ta "33" Ta "7100" Ta "64/64" Ta "EISA/SGC" +.It "715" Ta "50" Ta "7100" Ta "64/64" Ta "EISA/SGC" +.It "715" Ta "75" Ta "7100" Ta "256/256" Ta "EISA/SGC" +.It "725" Ta "50" Ta "7100" Ta "64/64" Ta "3 EISA, EISA/SGC" +.It "725" Ta "75" Ta "7100" Ta "256/256" Ta "3 EISA, EISA/SGC" +.It "735" Ta "100" Ta "7100" Ta "256/256" Ta "EISA, SGC" +.It "742i" Ta "50" Ta "7100" Ta "64/64" Ta "N/A" +.It "745i" Ta "50" Ta "7100" Ta "64/64" Ta "4 EISA" +.It "745i" Ta "100" Ta "7100" Ta "256/256" Ta "4 EISA" +.It "747i" Ta "50" Ta "7100" Ta "64/64" Ta "2 EISA, SGC, 6 VME" +.It "747i" Ta "100" Ta "7100" Ta "256/256" Ta "2 EISA, SGC, 6 VME" +.It "755" Ta "100" Ta "7100" Ta "256/256" Ta "4 EISA, 2 SGC" +.It "735" Ta "125" Ta "7150" Ta "256/256" Ta "EISA, SGC" +.It "755" Ta "125" Ta "7150" Ta "256/256" Ta "4 EISA, 2 SGC" +.It "712" Ta "60" Ta "7100LC" Ta "32/32" Ta "GIO, TSIO" +.It "712" Ta "80" Ta "7100LC" Ta "128/128" Ta "GIO, TSIO" +.It "712" Ta "100" Ta "7100LC" Ta "128/128" Ta "GIO, TSIO" +.It "715" Ta "64" Ta "7100LC" Ta "128/128" Ta "EISA/GSC" +.It "715" Ta "80" Ta "7100LC" Ta "128/128" Ta "EISA/GSC" +.It "715" Ta "100" Ta "7100LC" Ta "128/128" Ta "EISA/GSC" +.It "715XC" Ta "100" Ta "7100LC" Ta "512/512" Ta "EISA/GSC" +.It "725" Ta "64" Ta "7100LC" Ta "128/128" Ta "EISA, 3 EISA/GSC" +.It "725" Ta "100" Ta "7100LC" Ta "128/128" Ta "EISA, 3 EISA/GSC" +.It "743i" Ta "64" Ta "7100LC" Ta "128/128" Ta "2 GSC-M/2(4), VME" +.It "743i" Ta "100" Ta "7100LC" Ta "128/128" Ta "2 GSC-M/2(4), VME" +.It "748i" Ta "64" Ta "7100LC" Ta "128/128" Ta "2 GSC-M/2(4), 4 EISA/PCI, 6 VME" +.It "748i" Ta "100" Ta "7100LC" Ta "128/128" Ta "2 GSC-M/2(4), 4 EISA/PCI, 6 VME" +.It "SAIC" Ta "60" Ta "7100LC" Ta "32/32" Ta "GIO, TSIO, 2 PCMCIA" +.It "SAIC" Ta "80" Ta "7100LC" Ta "128/128" Ta "GIO, TSIO, 2 PCMCIA" +.It "J200" Ta "100" Ta "7200" Ta "256/256" Ta "GSC, 2 EISA, 2 EISA/GSC" +.It "J210" Ta "120" Ta "7200" Ta "256/256" Ta "GSC, 2 EISA, 2 EISA/GSC" +.It "J210XC" Ta "120" Ta "7200" Ta "1MB/1MB" Ta "GSC, 2 EISA, 2 EISA/GSC" +.It "C100" Ta "100" Ta "7200" Ta "256/256" Ta "GSC, 3 EISA/GSC" +.It "C110" Ta "120" Ta "7200" Ta "256/256" Ta "GSC, 3 EISA/GSC" +.It "744" Ta "132" Ta "7300LC" Ta "64/64" Ta "2 GSC-M/2(4), VME" +.It "744" Ta "165" Ta "7300LC" Ta "64/64+512" Ta "2 GSC-M/2(4), VME" +.It "745" Ta "132" Ta "7300LC" Ta "64/64" Ta "2 GSC-M/2(4), 4 EISA/PCI" +.It "745" Ta "165" Ta "7300LC" Ta "64/64+512" Ta "2 GSC-M/2(4), 4 EISA/PCI" +.It "748" Ta "132" Ta "7300LC" Ta "64/64" Ta "2 GSC-M/2(4), 4 EISA/PCI, 6 VME" +.It "748" Ta "165" Ta "7300LC" Ta "64/64+512" Ta "2 GSC-M/2(4), 4 EISA/PCI, 6 VME" +.It "A180" Ta "180" Ta "7300LC" Ta "64/64" Ta "2 HSC/PCI" +.It "A180C" Ta "180" Ta "7300LC" Ta "64/64+1MB" Ta "2 HSC/PCI" +.It "B132L" Ta "132" Ta "7300LC" Ta "64/64(+1MB)" Ta "GSC/PCI, GSC/PCI/EISA" +.It "B132L+" Ta "132" Ta "7300LC" Ta "64/64(+1MB)" Ta "GSC/PCI, GSC/PCI/EISA" +.It "B160L" Ta "160" Ta "7300LC" Ta "64/64(+1MB)" Ta "GSC/PCI, GSC/PCI/EISA" +.It "B180L+" Ta "180" Ta "7300LC" Ta "64/64(+1MB)" Ta "GSC/PCI, GSC/PCI/EISA" +.It "C132L" Ta "132" Ta "7300LC" Ta "64/64(+1MB)" Ta "2 GSC/PCI/EISA, 2 GSC/EISA" +.It "C160L" Ta "160" Ta "7300LC" Ta "64/64(+1MB)" Ta "2 GSC/PCI/EISA, 2 GSC/EISA" +.It "RDI" Ta "132" Ta "7300LC" Ta "64/64(+1MB)" Ta "2 CardBus" +.It "RDI" Ta "160" Ta "7300LC" Ta "64/64(+1MB)" Ta "2 CardBus" +.It "RDI" Ta "180" Ta "7300LC" Ta "64/64(+1MB)" Ta "2 CardBus" +.It "C160" Ta "160" Ta "8000" Ta "512/512" Ta "2 GSC/PCI/EISA, 2 GSC/EISA" +.It "C180" Ta "180" Ta "8000" Ta "1024/1024" Ta "2 GSC/PCI/EISA, 2 GSC/EISA" +.It "J280" Ta "180" Ta "8000" Ta "1024/1024" Ta "3 GSC/PCI, PCI, PCI/EISA" +.It "J282" Ta "180" Ta "8000" Ta "1024/1024" Ta "3 GSC/PCI, PCI, PCI/EISA" +.It "C200" Ta "200" Ta "8200" Ta "512/1024" Ta "GSC/PCI/EISA, 3 GSC/PCI" +.It "C240" Ta "240" Ta "8200" Ta "2048/2048" Ta "GSC/PCI/EISA, 3 GSC/PCI" +.It "J2240" Ta "240" Ta "8200" Ta "2048/2048" Ta "3 GSC/PCI, PCI, PCI/EISA" +.It "B1000" Ta "300" Ta "8500" Ta "512/1024" Ta "6 PCI" +.It "C360" Ta "360" Ta "8500" Ta "512/1024" Ta "GSC/PCI/EISA, 3 GSC/PCI" +.It "B2000" Ta "400" Ta "8500" Ta "512/1024" Ta "4 PCI" +.It "C3000" Ta "400" Ta "8500" Ta "512/1024" Ta "6 PCI" +.It "J5000" Ta "440" Ta "8500" Ta "512/1024" Ta "7 PCI" +.It "J7000" Ta "440" Ta "8500" Ta "512/1024" Ta "7 PCI" +.It "B2600" Ta "500" Ta "8600" Ta "512/1024" Ta "4 PCI" +.It "C3600" Ta "552" Ta "8600" Ta "512/1024" Ta "6 PCI" +.It "J5600" Ta "552" Ta "8600" Ta "512/1024" Ta "7 PCI" +.It "J6000" Ta "552" Ta "8600" Ta "512/1024" Ta "7 PCI" +.It "J7600" Ta "552" Ta "8600" Ta "512/1024" Ta "7 PCI" +.It "C3650" Ta "625" Ta "8700" Ta "768/1536" Ta "6 PCI" +.It "C3700" Ta "750" Ta "8700" Ta "768/1536" Ta "6 PCI" +.It "J6700" Ta "750" Ta "8700" Ta "768/1536" Ta "3 PCI" +.It "C3750" Ta "875" Ta "8700+" Ta "768/1536" Ta "6 PCI" +.It "J6750" Ta "875" Ta "8700+" Ta "768/1536" Ta "3 PCI" +.El +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width "cardbus(4)XX" -offset ind -compact +.It Xr cardbus 4 +introduction to CardBus support +.It Xr gsc 4 +introduction to HP 9000/700 GSC bus support +.It Xr hil 4 +introduction to HP-HIL support +.It Xr onewire 4 +1-Wire bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr pcmcia 4 +introduction to PCMCIA (PC Card) support +.It Xr usb 4 +introduction to Universal Serial Bus support +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr cpu 4 , +.Xr io 4 , +.Xr runway 4 , +.Xr config 8 +.Sh HISTORY +The +hppa +.Nm +first appeared with +.Ox 3.1 . diff --git a/static/openbsd/man4/man4.hppa/io.4 b/static/openbsd/man4/man4.hppa/io.4 new file mode 100644 index 00000000..dc91f2f2 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/io.4 @@ -0,0 +1,166 @@ +.\" $OpenBSD: io.4,v 1.15 2011/09/03 22:59:07 jmc Exp $ +.\" +.\" Copyright (c) 2003,2004 Paul Weissmann +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: September 3 2011 $ +.Dt IO 4 hppa +.Os +.Sh NAME +.Nm io +.Nd HP PA-RISC I/O subsystem reference +.Sh DESCRIPTION +The following table lists the +.Tn PA-RISC +I/O subsystems and connected devices found in the supported +.Tn HP 9000/700 +machines. +.Bl -column "715/100" "DLUW" "SE, FWD" "DX, FDDI" "[GSC/PCI]" "Misc" -offset 6n +.It Sy Model Ta Sy MBA Ta Sy SCSI Ta Sy Network Ta Sy Video Ta Sy Misc +.It "705" Ta "A" Ta "SE" Ta "DX" Ta "Timber" Ta "" +.It "710" Ta "A" Ta "SE" Ta "DX" Ta "Timber" Ta "" +.It "712" Ta "LW" Ta "SE" Ta "CA, TR" Ta "Artist" Ta "" +.It "715/33" Ta "A" Ta "SE" Ta "DX" Ta "Stinger" Ta "" +.It "715/50" Ta "A" Ta "SE" Ta "DX" Ta "Stinger" Ta "" +.It "715/64" Ta "LW" Ta "SE" Ta "CA" Ta "Artist" Ta "" +.It "715/75" Ta "A" Ta "SE" Ta "DX" Ta "Stinger" Ta "" +.It "715/80" Ta "LW" Ta "SE" Ta "CA" Ta "Artist" Ta "" +.It "715/100" Ta "LW" Ta "SE" Ta "CA" Ta "Artist" Ta "" +.It "720" Ta "A" Ta "SE" Ta "DX" Ta "[SGC]" Ta "" +.It "725/50" Ta "A" Ta "SE" Ta "DX" Ta "Stinger" Ta "" +.It "725/75" Ta "A" Ta "SE" Ta "DX" Ta "Stinger" Ta "" +.It "725/64" Ta "LW" Ta "SE" Ta "CA" Ta "Artist" Ta "" +.It "725/100" Ta "LW" Ta "SE" Ta "CA" Ta "Artist" Ta "" +.It "730" Ta "A" Ta "SE" Ta "DX" Ta "[SGC]" Ta "" +.It "735" Ta "A" Ta "SE, FWD" Ta "DX, FDDI" Ta "[SGC]" Ta "" +.It "742i" Ta "A" Ta "SE" Ta "CA" Ta "Stinger" Ta "VME" +.It "743i" Ta "DLW" Ta "SE" Ta "DX" Ta "Artist" Ta "VME" +.It "744" Ta "DLW" Ta "SE" Ta "DX" Ta "EG" Ta "VME" +.It "745" Ta "DLW" Ta "SE" Ta "DX" Ta "EG" Ta "VME" +.It "745i" Ta "A" Ta "SE" Ta "DX" Ta "Stinger" Ta "" +.It "747i" Ta "A" Ta "SE" Ta "DX" Ta "Stinger" Ta "" +.It "748" Ta "DLW" Ta "SE" Ta "DX" Ta "EG" Ta "VME" +.It "748i" Ta "DLW" Ta "SE" Ta "DX" Ta "Artist" Ta "VME" +.It "750" Ta "A" Ta "SE" Ta "DX" Ta "[SGC]" Ta "" +.It "755" Ta "A" Ta "SE, FWD" Ta "DX, FDDI" Ta "[SGC]" Ta "" +.It "A180/C" Ta "DL" Ta "SE" Ta "DC" Ta "[GSC/PCI]" Ta "" +.It "B132L" Ta "DLW" Ta "SE, FWD" Ta "CA" Ta "EG" Ta "" +.It "B160L" Ta "DLW" Ta "SE, UW" Ta "DC" Ta "EG" Ta "" +.It "B180L" Ta "DLW" Ta "SE, UW" Ta "DC" Ta "EG" Ta "" +.It "C100" Ta "LUW" Ta "SE, FWD" Ta "CA" Ta "[GSC]" Ta "" +.It "C110" Ta "LUW" Ta "SE, FWD" Ta "CA" Ta "[GSC]" Ta "" +.It "C132L" Ta "DLUW" Ta "SE, UW" Ta "DC" Ta "EG" Ta "" +.It "C160L" Ta "DLUW" Ta "SE, UW" Ta "DC" Ta "EG" Ta "" +.It "C160" Ta "DLU" Ta "SE, UW" Ta "DC" Ta "[GSC/PCI]" Ta "" +.It "C180L" Ta "DLUW" Ta "SE, UW" Ta "DC" Ta "EG" Ta "" +.It "C180" Ta "DLU" Ta "SE, UW" Ta "DC" Ta "[GSC/PCI]" Ta "" +.It "C200" Ta "DLU" Ta "SE, UW" Ta "DC" Ta "[GSC/PCI]" Ta "" +.It "C230" Ta "DLU" Ta "SE, UW" Ta "DC" Ta "[GSC/PCI]" Ta "" +.It "C240" Ta "DLU" Ta "SE, UW" Ta "DC" Ta "[GSC/PCI]" Ta "" +.It "C360" Ta "DLU" Ta "SE, UW" Ta "DC" Ta "[GSC/PCI]" Ta "" +.It "J200" Ta "LUW" Ta "SE, FWD" Ta "CA" Ta "[GSC]" Ta "" +.It "J210/XC" Ta "LUW" Ta "SE, FWD" Ta "CA" Ta "[GSC]" Ta "" +.It "J280" Ta "DLUW" Ta "SE, UW" Ta "DC" Ta "[GSC/PCI]" Ta "" +.It "J282" Ta "DLUW" Ta "SE, UW" Ta "DC" Ta "[GSC/PCI]" Ta "" +.It "J2240" Ta "DLUW" Ta "SE, UW" Ta "DC" Ta "[GSC/PCI]" Ta "" +.It "RDI" Ta "DL" Ta "SE" Ta "CA" Ta "EG" Ta "CardBus" +.It "SAIC" Ta "LW" Ta "SE" Ta "CA" Ta "Artist" Ta "PCMCIA" +.El +.Pp +The MBA column denotes the bus adapters in use: +.Pp +.Bl -tag -width XXXX -compact -offset indent +.It A +.Xr asp 4 +.It D +.Xr dino 4 +.It L +.Xr lasi 4 +.It U +.Xr uturn 4 +.It W +.Xr wax 4 +.El +.Pp +The trailing characters in the SCSI row denote the +SCSI bus configuration: +.Pp +.Bl -tag -width XXXX -compact -offset indent +.It SE +.Xr oosiop 4 +or +.Xr osiop 4 ; +.Tn Symbios/NCR +53C700/710 8-bit (fast) single-ended, +.It FWD +.Xr siop 4 ; +.Tn NCR53C720 +16-bit fast differential (HVD), +.It UW +.Xr siop 4 ; +.Tn NCR53C875 +16-bit ultra single-ended. +.El +.Pp +The trailing digits in the Network row denote the +interface speed: +.Pp +.Bl -tag -width XXXXX -compact -offset indent +.It CA +.Xr ie 4 ; +.Tn i82596CA +10 Mb/s, +.It DX +.Xr ie 4 ; +.Tn i82596DX +10 Mb/s, +.It DC +.Xr dc 4 ; +.Tn DEC 21142/3 +10/100 Mb/s, +.It FDDI +.Tn Am78830 +Formac+ FDDI. +.El +.Sh SEE ALSO +.Xr asp 4 , +.Xr dc 4 , +.Xr dino 4 , +.Xr gsc 4 , +.Xr ie 4 , +.Xr intro 4 , +.Xr lasi 4 , +.Xr oosiop 4 , +.Xr osiop 4 , +.Xr runway 4 , +.Xr siop 4 , +.Xr sti 4 , +.Xr uturn 4 , +.Xr wax 4 +.Sh HISTORY +The +hppa +.Nm +reference first appeared with +.Ox 3.3 . diff --git a/static/openbsd/man4/man4.hppa/lasi.4 b/static/openbsd/man4/man4.hppa/lasi.4 new file mode 100644 index 00000000..dca12ec0 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/lasi.4 @@ -0,0 +1,134 @@ +.\" $OpenBSD: lasi.4,v 1.27 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" +.\" Copyright (c) 1999 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt LASI 4 hppa +.Os +.Sh NAME +.Nm lasi +.Nd core bus controller and I/O subsystem as present on newer HP 9000/700 \ +workstations and single-board computers +.Sh SYNOPSIS +.Cd "lasi0 at mainbus? irq 28" +.Cd "lasi0 at phantomas? irq 28" +.Cd "lasi0 at uturn? irq 28" +.Cd "gsc* at lasi?" +.Sh DESCRIPTION +The supported Core bus controllers are those used in conjunction with +.Tn PA7100LC +and +.Tn PA7300LC +CPUs and based upon LSI's macrochip that includes: +.Pp +.Bl -bullet -compact +.It +Core bus controller +.It +System clock +.It +Interrupt controller +.It +Real-time clock Interface +.It +Power system support +.It +RAM and Flash EEPROM controllers +.It +Two PS/2 ports +.It +RS-232 and Centronics I/O ports +.It +i82596CA LAN coprocessor +.It +NCR53c710 SCSI I/O processor +.It +Serial Interface for the CS4216 audio codec +.It +Interface for the WD37C65C floppy drive controller +.It +Optional telephone interface (two fax/voice modem channels) +.El +.Sh MACHINES +An incomplete list of machines that use the +.Tn LASI +bus controller: +.Pp +.Bl -bullet -compact +.It +712/* +.It +715/{64/80/100}[XC] +.It +725/{64/80/100} +.It +743/* +.It +744/* +.It +745/* +.It +A180[C] +.It +B132L[+], B160L, B180L+ +.It +C100, C110, J200, J210[XC] +.It +RDI PrecisionBook +.It +SAIC Galaxy 1100 +.El +.Sh SEE ALSO +.Xr asp 4 , +.Xr gsc 4 , +.Xr intro 4 , +.Xr io 4 , +.Xr phantomas 4 , +.Xr power 4 , +.Xr uturn 4 , +.Xr wax 4 +.Rs +.%T "Precision I/O Architecture Reference Specification" +.%Q Hewlett-Packard +.Re +.Rs +.%T "712 I/O Subsystem ERS" +.%N Revision 1.1 +.%D 12 February 1993 +.%Q Hewlett-Packard +.%O Dwg No. A-A2263-66510-31 +.Re +.Rs +.%J Hewlett-Packard Journal +.%D April 1995 +.%V Volume 46 +.%N Number 2 +.Re +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.4 . diff --git a/static/openbsd/man4/man4.hppa/lcd.4 b/static/openbsd/man4/man4.hppa/lcd.4 new file mode 100644 index 00000000..1c42bc95 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/lcd.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: lcd.4,v 1.3 2018/01/12 04:36:44 deraadt Exp $ +.\" +.\" Copyright (c) 2007 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 12 2018 $ +.Dt LCD 4 hppa +.Os +.Sh NAME +.Nm lcd +.Nd front panel LCD display +.Sh SYNOPSIS +.Cd "lcd0 at mainbus0" +.Sh DESCRIPTION +The +.Nm +driver provides support for the front panel LCD display found on newer +HP PA-RISC workstations and servers. +This LCD can be made to show a heartbeat based on the load average by +setting the +.Xr sysctl 2 +variable +.Ar machdep.led_blink +to a non-zero value. +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr intro 4 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . diff --git a/static/openbsd/man4/man4.hppa/mem.4 b/static/openbsd/man4/man4.hppa/mem.4 new file mode 100644 index 00000000..44ab580d --- /dev/null +++ b/static/openbsd/man4/man4.hppa/mem.4 @@ -0,0 +1,87 @@ +.\" $OpenBSD: mem.4,v 1.4 2018/01/12 04:36:44 deraadt Exp $ +.\" +.\" Copyright (c) 2004, Miodrag Vallat. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 12 2018 $ +.Dt MEM 4 hppa +.Os +.Sh NAME +.Nm mem , +.Nm kmem +.Nd memory files and memory controller +.Sh SYNOPSIS +.Cd "mem* at mainbus0 flags 0x0000" +.Sh DESCRIPTION +The +.Nm +driver controls and restricts access to the systems memory +by the hardware buses and the processor. +.Pp +It also provides an interface to userland through the special files +.Pa /dev/mem +and +.Pa /dev/kmem . +Physical memory is accessed through +.Pa /dev/mem , +while kernel virtual memory is accessed through +.Pa /dev/kmem . +Access to kernel virtual addresses not currently mapped to memory will fail. +On hppa, the physical memory range is always contiguous and starts at +address 0; kernel virtual memory begins at address 0 as well. +.Pp +Even with sufficient file system permissions, +these devices can only be opened when the +.Xr securelevel 7 +is insecure or when the +.Va kern.allowkmem +.Xr sysctl 2 +variable is set. +.Sh FILES +.Bl -tag -width /dev/kmem -compact +.It Pa /dev/mem +.It Pa /dev/kmem +.El +.Sh SEE ALSO +.Xr securelevel 7 +.Sh CAVEATS +On some systems featuring a +.Dq Viper +memory controller, +.Ox +may not configure bus arbitration correctly, causing the boot process +to freeze during either +.Nm +or +.Xr cpu 4 +device probe. +.Pp +In this case, a different initialization strategy can be achieved by +setting +.Ar flags +to 0x0001 +.Po +see +.Xr boot_config 8 +for details +.Pc . diff --git a/static/openbsd/man4/man4.hppa/mongoose.4 b/static/openbsd/man4/man4.hppa/mongoose.4 new file mode 100644 index 00000000..4693ae1d --- /dev/null +++ b/static/openbsd/man4/man4.hppa/mongoose.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: mongoose.4,v 1.4 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" Copyright (c) 2004 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, +.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt MONGOOSE 4 hppa +.Os +.Sh NAME +.Nm mongoose +.Nd EISA Bus adapter +.Sh SYNOPSIS +.Cd "mongoose0 at mainbus?" +.Cd "eisa* at mongoose?" +.Sh DESCRIPTION +Provides an interface from the CPU-memory bus to EISA and ISA +devices. +Two variations exist providing the same functionality +based on +.Tn Intel i82350 +or +.Tn Texas Instruments +.\" TACT84544BPC/FBW41962 TACT84543BPP/36AEKJW TACT84541CPC/FCW421B3 +chips. +Depending on the model the bus clock is either 25 MHz or 33 MHz. +.Sh SEE ALSO +.Xr eisa 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.6 . +.Sh BUGS +Has some. diff --git a/static/openbsd/man4/man4.hppa/pdc.4 b/static/openbsd/man4/man4.hppa/pdc.4 new file mode 100644 index 00000000..4364be8a --- /dev/null +++ b/static/openbsd/man4/man4.hppa/pdc.4 @@ -0,0 +1,732 @@ +.\" $OpenBSD: pdc.4,v 1.12 2022/03/31 17:27:21 naddy Exp $ +.\" +.\" Copyright (c) 2004 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR OR HIS RELATIVES BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF MIND, USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING +.\" IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt PDC 4 hppa +.Os +.Sh NAME +.Nm pdc +.Nd Processor-Dependent Code firmware driver +.Sh SYNOPSIS +.Cd "pdc0 at mainbus?" +.Sh DESCRIPTION +The +.Nm +driver provides system console services through the PDC +and also a means for calling PDC procedures, described later. +The PDC console is used early in the kernel startup before enough kernel +subsystems have been initialized to directly use the hardware +i.e. serial ports, keyboard, and video. +.Pp +The PDC version displayed at system boot is relevant to the particular +system model and is not necessarily comparable to PDC versions +on other systems. +.\" TODO page0 description and entry points +.Sh PDC PROCEDURES +PDC procedure calls are all made through a single entry point +and assume normal C language calling conventions, with option +number in the first argument and the return data address in the +second, unless indicated otherwise. +Each call requires at most 7KB of the available stack. +Here is the list of procedures and options descriptions: +.Bl -tag -width pdc +.It Fn pdc "PDC_ADD_VALID" "PDC_ADD_VALID_DFLT" "paddr" +Perform a read operation attempt at the physical address +.Ar paddr +without causing a HPMC, in order to verify that the address is valid +and there is a device to respond to it. +The implementation may choose to call the caller's HPMC handler and +raise error conditions on the bus converters. +.It Fn pdc "PDC_ALLOC" "PDC_ALLOC_DFLT" "ptr" "size" +Allocate static storage for IODC use of +.Ar size +bytes and return the address in a word pointed to by the +.Ar ptr +argument. +There is no way of freeing the storage allocated and thus +care shall be taken to not exhaust the total allocation limit of 32KB. +.It Fn pdc "PDC_BLOCK_TLB" "PDC_BTLB_DEFAULT" "ptr" +Get block TLB parameters into the data area pointed to by the +.Ar ptr +argument. +This includes minimal and maximal entry size and number of fixed and +variable sized entries in the block TLB. +Fixed entries have size of power of two and are aligned to the size +where variable entries can have any size and base address both +aligned to a page. +.It Xo +.Fo pdc +.Fa PDC_BLOCK_TLB +.Fa PDC_BTLB_INSERT +.Fa sp +.Fa va +.Fa pa +.Fa len +.Fa acc +.Fa slot +.Fc +.Xc +Insert block TLB entry specified by the space ID +.Ar sp , +virtual address +.Ar va , +physical address +.Ar pa , +region length +.Ar len , +access rights +.Ar acc , +into the slot number +.Ar slot . +.It Fn pdc "PDC_BLOCK_TLB" "PDC_BTLB_PURGE" "sp" "va" "slot" "len" +Purge one entry from the block TLB specified by the space ID +.Ar sp , +virtual address +.Ar va , +region length +.Ar len , +from slot number +.Ar slot . +.It Fn pdc "PDC_BLOCK_TLB" "PDC_BTLB_PURGE_ALL" +Purge all entries from the block TLB. +.\" TODO .It Fn pdc "PDC_BUS_BAD" "PDC_BUS_BAD_DLFT" +.It Fn pdc "PDC_CACHE" "PDC_CACHE_DFLT" "ptr" +Retrieve cache and TLB configuration parameters into the data area +pointed to by the +.Ar ptr +argument. +The format of the data stores is as follows: +.Bl -column "0x00" "contents" -offset indent +.It Sy "addr" Ta Sy "contents" +.It "0x00" Ta "I-cache size in bytes" +.It "0x04" Ta "I-cache configuration" +.It "0x08" Ta "I-cache base for flushing" +.It "0x0c" Ta "I-cache stride for flushing" +.It "0x10" Ta "I-cache count for flushing" +.It "0x14" Ta "I-cache loop size for flushing" +.It "0x18" Ta "D-cache size in bytes" +.It "0x1c" Ta "D-cache configuration" +.It "0x20" Ta "D-cache base for flushing" +.It "0x24" Ta "D-cache stride for flushing" +.It "0x28" Ta "D-cache count for flushing" +.It "0x2c" Ta "D-cache loop size for flushing" +.It "0x30" Ta "ITLB size" +.It "0x34" Ta "ITLB configuration" +.It "0x38" Ta "ITLB space base for flushing" +.It "0x3c" Ta "ITLB space stride for flushing" +.It "0x40" Ta "ITLB space count for flushing" +.It "0x44" Ta "ITLB address base for flushing" +.It "0x48" Ta "ITLB address stride for flushing" +.It "0x4c" Ta "ITLB address count for flushing" +.It "0x50" Ta "ITLB loop size for flushing" +.It "0x54" Ta "DTLB size" +.It "0x58" Ta "DTLB configuration" +.It "0x5c" Ta "DTLB space base for flushing" +.It "0x60" Ta "DTLB space stride for flushing" +.It "0x64" Ta "DTLB space count for flushing" +.It "0x68" Ta "DTLB address base for flushing" +.It "0x6c" Ta "DTLB address stride for flushing" +.It "0x70" Ta "DTLB address count for flushing" +.It "0x74" Ta "DTLB loop size for flushing" +.El +.Pp +The cache configuration word is formatted as follows: +.Bl -column "bit" "len" "contents" -offset indent +.It Sy "bit" Ta Sy "len" Ta Sy "contents" +.It "0" Ta "12" Ta "reserved" +.It "13" Ta "3" Ta "set 1 if coherent operation supported" +.It "16" Ta "2" Ta "flush mode: 0 \(em fdc & fic; 1 \(em fdc;\ + 2 \(em fic; 3 \(em either" +.It "18" Ta "1" Ta "write-thru D-cache if set" +.It "19" Ta "2" Ta "reserved" +.It "21" Ta "3" Ta "cache line size" +.It "24" Ta "4" Ta "associativity" +.It "28" Ta "4" Ta "virtual address alias boundary" +.El +.It Fn pdc "PDC_CACHE" "PDC_CACHE_SETCS" "ptr" "i_cst" "d_cst" "it_cst" "dt_cst" +The second word in each of the +.Ar i_cst , +.Ar d_cst , +.Ar it_cst , +and +.Ar dt_cst +arguments specifies the desired coherency operation for the instructions cache, +data cache, instructions TLB, and data TLB, respectively. +The data area pointed to by the +.Ar ptr +argument receives the actual coherent operation state +after an attempted change. +The CPU does not support the requested operation change +should the corresponding words not match the arguments upon return. +The currently supported values are zero for incoherent operation, +and one for coherent operation. +.It Fn pdc "PDC_CACHE" "PDC_CACHE_GETSPIDB" "ptr" +The word pointed to by the +.Ar ptr +argument receives a mask of space ID used in hashing for cache tag. +.It Fn pdc "PDC_CHASSIS" "PDC_CHASSIS_DISP" "display" +Update the chassis display with data given in the +.Ar display +argument. +The bitfields in the word are as follows: +.Pp +.Bl -tag -width 0xfffff -compact +.It 0xe0000 +Specifies the system state. +.Bl -tag -width 0xfffff -compact +.It 0x00000 +off +.It 0x20000 +fault +.It 0x40000 +test +.It 0x60000 +initialize +.It 0x80000 +shutdown +.It 0xa0000 +warning +.It 0xc0000 +run +.It 0xe0000 +all on +.El +.It 0x10000 +Blank the chassis display. +.It 0x0f000 +This and the other lower three nibbles specify the four hex digits +to be displayed on the chassis display. +.El +.It Fn pdc "PDC_CHASSIS" "PDC_CHASSIS_WARN" "ptr" +Return the warnings from the chassis fans, temperature sensors, +batteries and power supplies. +A word of data is returned in the area pointed by the +.Ar ptr +argument and is described with bitfields: +.Pp +.Bl -tag -width 0xff -compact +.It 0xff000000 +Zero means none of the redundant chassis components has indicated any failures. +A non-zero value specifies the failing component. +.It 0x4 +Indicates the chassis battery charge is low. +.It 0x2 +The chassis temperature has exceeded the low threshold. +.It 0x1 +The chassis temperature has exceeded the middle threshold. +.El +.It Fn pdc "PDC_CHASSIS" "PDC_CHASSIS_ALL" "ptr" "display" +Both retrieves the chassis warnings into the word pointed by the +.Ar ptr +argument and sets the chassis display using data in the +.Ar display +argument. +.\" TODO .It Fn pdc "PDC_CONF" "PDC_CONFIG_DECONF" "ptr" "hpa" +.\" TODO .It Fn pdc "PDC_CONF" "PDC_CONFIG_RECONF" "ptr" "hpa" +.\" TODO .It Fn pdc "PDC_CONF" "PDC_CONFIG_INFO" "ptr" "hpa" +.It Fn pdc "PDC_COPROC" "PDC_COPROC_DFLT" "ptr" +Identify the coprocessors attached to the CPU. +The +.Ar ptr +points to a memory location where data is to be stored. +The first word provides a mask for functional coprocessors and +the second word is the mask for all present coprocessors. +.It Fn pdc "PDC_DEBUG" "PDC_DEBUG_DFLT" "ptr" +Retrieve address of the PDC debugger placed in to the word +pointed to by the +.Ar ptr +argument. +.\" TODO .It Fn pdc "PDC_INSTR" "PDC_INSTR_DFLT" +.It Fn pdc "PDC_IODC" "PDC_IODC_READ" "ptr" "hpa" "entry" "addr" "count" +Given a module +.Ar hpa , +retrieve the specified +.Ar entry +from the module's IODC into a memory area at +.Ar adr +of +.Ar count +bytes long at most. +The +.Ar entry +index is a one-byte index, with a value of zero being a special case. +For the 0th entry, an IODC header of 16 bytes is returned instead +of an actual code. +.It Fn pdc "PDC_IODC" "PDC_IODC_NINIT" "ptr" "hpa" "spa" +Non-destructively initialize the memory module specified by the +.Ar hpa +and +.Ar spa +arguments and return the module status after the init in the first word +pointed to by the +.Ar ptr +argument, followed by the SPA space size and an amount of +available memory bytes in the subsequent two words. +.It Fn pdc "PDC_IODC" "PDC_IODC_DINIT" "ptr" "hpa" "spa" +Same as +.Nm PDC_IODC_NINIT +except a destructive memory test is performed. +.It Fn pdc "PDC_IODC" "PDC_IODC_MEMERR" "ptr" "hpa" "spa" +For the memory module that is specified by +.Ar hpa +and +.Ar spa , +return the last most severe error information comprised of copies of +IO_STATUS, IO_ERR_RESP, IO_ERR_INFO, and IO_ERR_REQ registers placed +into the data area pointed to by the +.Ar ptr +argument, and clear the error status. +.It Fn pdc "PDC_IODC" "PDC_IODC_IMEMMASTER" "ptr" "hpa" +HPA for the primary memory module is returned in a word pointed to by the +.Ar ptr +argument for a memory module specified by +.Ar hpa +if it's configured as a slave module in an interleave group. +.It Fn pdc "PDC_LAN_STATION_ID" "PDC_LAN_STATION_ID_READ" "macptr" "hpa" +Retrieve the MAC address for the device at +.Ar hpa +into the data area pointed to by the +.Ar macptr +argument. +.\" TODO .It Fn pdc "PDC_MEM" "PDC_MEM_INFO" "ptr" +.\" TODO .It Fn pdc "PDC_MEM" "PDC_MEM_ADD" "ptr" "PDT" +.\" TODO .It Fn pdc "PDC_MEM" "PDC_MEM_CLR" "ptr" +.\" TODO .It Fn pdc "PDC_MEM" "PDC_MEM_READ" "ptr" "PDT" +.\" TODO .It Fn pdc "PDC_MEM" "PDC_MEM_RSTCLR" "ptr" +.\" TODO .It Fn pdc "PDC_MEM" "PDC_MEM_SETGOOD" "ptr" "good" +.It Fn pdc "PDC_MEMMAP" "PDC_MEMMAP_HPA." "ptr" "path" +Returns device HPA in the word pointed to by the +.Ar ptr +argument given the device +.Ar path +pointer. +.It Fn pdc "PDC_MODEL" "PDC_MODEL_INFO" "ptr" +Returns the System model numbers. +.It Fn pdc "PDC_MODEL" "PDC_MODEL_BOOTID" "boot_id" +Set BOOT_ID of the processor module (used during boot +process of monarch selection) to a word given in the +.Ar boot_id +argument. +.It Fn pdc "PDC_MODEL" "PDC_MODEL_COMP" "ptr" "index" +Retrieve processor component versions by issuing this procedure with +subsequent indexes in the +.Ar index +argument starting at zero. +The component version number is stored in the word pointed to by +the +.Ar ptr +argument. +.It Fn pdc "PDC_MODEL" "PDC_MODEL_MODEL" "ptr" "os_id" "mod_addr" +Return a string of 80 chars maximum stored at address +.Ar mod_addr +and conforming to the OS specified by the +.Ar os_id +16-bit integer (see +.Nm PDC_STABLE +for more information on OS ID). +A word at the +.Ar ptr +address receives the result string length. +.\" TODO .It Fn pdc "PDC_MODEL" "PDC_MODEL_ENSPEC" "ptr" +.\" TODO .It Fn pdc "PDC_MODEL" "PDC_MODEL_DISPEC" "ptr" +.It Fn pdc "PDC_MODEL" "PDC_MODEL_CPUID" "ptr" +Retrieve CPU model information. +A word stored at the address given by the +.Ar ptr +argument specifies the CPU revision in the lower 5 bits followed by 7 bits +of CPU model number. +.It Fn pdc "PDC_MODEL" "PDC_MODEL_CPBALITIES" "ptr" +Retrieve platform capabilities into the word pointed by the +.Ar ptr +argument. +Bit 0 and 1 specify that a 64- or 32-bit OS is supported, respectively. +.It Fn pdc "PDC_MODEL" "PDC_MODEL_GETBOOTOPTS" "ptr" +Retrieve the currently enabled, overall supported, and enabled by default +boot test masks respectively stored at location pointed to by +the +.Ar ptr +argument. +.It Fn pdc "PDC_MODEL" "PDC_MODEL_SETBOOTOPTS" "ptr" "disable" "enable" +Disable boot tests specified by mask in the +.Ar disable +argument and enable +boot tests specified by the mask given in the +.Ar enable +argument. +The memory location pointed to by +.Ar ptr +will contain the resulting masks as returned +by the PDC_MODEL_GETBOOTOPTS function. +If an attempt is made to enable and disable the same test in one +call, a PDC_ERR_INVAL will be returned. +.It Fn pdc "PDC_NVM" "PDC_NVM_READ" "offset" "ptr" "count" +Read contents of the NVM at +.Ar offset +into the memory area pointed to by the +.Ar ptr +argument of no more than +.Ar count +bytes. +.Pp +The format of the NVM is as follows: +.Bl -column "0x0000" "size" "contents" -offset indent +.It Sy "offset" Ta Sy "size" Ta Sy "contents" +.It "0x00" Ta "0x24" Ta "HV dependent" +.It "0x24" Ta "0x20" Ta "bootpath" +.It "0x44" Ta "0x04" Ta "ISL revision" +.It "0x48" Ta "0x04" Ta "timestamp" +.It "0x4c" Ta "0x30" Ta "LIF utility entries" +.It "0x7c" Ta "0x04" Ta "entry point" +.It "0x80" Ta "0x80" Ta "OS panic information" +.El +.It Fn pdc "PDC_NVM" "PDC_NVM_WRITE" "offset" "ptr" "count" +Write data pointed to by the +.Ar ptr +argument of +.Ar count +bytes at +.Ar address +in the NVM. +.It Fn pdc "PDC_NVM" "PDC_NVM_SIZE" "ptr" +Put the size of Non-Volatile Memory into the word pointed to by the +.Ar ptr +argument. +.It Fn pdc "PDC_NVM" "PDC_NVM_VRFY" +Verify that the contents of NVM are valid. +.It Fn pdc "PDC_NVM" "PDC_NVM_INIT" +Reset the contents of NVM to zeroes without any arguments. +.It Fn pdc "PDC_HPA" "PDC_HPA_DFLT" "ptr" +The data returned provides the monarch CPUs HPA in the word pointed to by +.Ar ptr . +.It Fn pdc "PDC_HPA" "PDC_HPA_MODULES" "ptr" +Retrieve the bit mask for devices on the CPU bus into the data location +pointed to by +.Ar ptr . +The first word is a bitmask for devices 0-31, and the second is +a bitmask for devices 32-63, where bits set to one specify that +the corresponding device number is on the same bus as the CPU. +.\" TODO .It Fn pdc "PDC_PAT_IO" "PDC_PAT_IO_GET_PCI_RTSZ" +.\" TODO .It Fn pdc "PDC_PAT_IO" "PDC_PAT_IO_GET_PCI_RT" +.It Fn pdc "PDC_PIM" "PDC_PIM_HPMC" "offset" "ptr" "count" +Get HPMC data from +.Ar offset +in Processor Internal Memory (PIM) into a +.Ar ptr +memory area of no more than +.Ar count +bytes in size. +Data provided includes (in the order it is copied into the buffer): +general registers (r0-r31), control registers (cr0-cr31), space +registers (sr0-sr7), IIA space tail, IIA offset tail, check type, +CPU state, cache check, TLB check, bus check, assist check, assist +state, path info, system responder address, system requestor address, +FPU registers (fpr0-fpr31). +.It Fn pdc "PDC_PIM" "PDC_PIM_SIZE" "ptr" +Return the amount of data available in bytes in the word pointed to by +.Ar ptr . +.It Fn pdc "PDC_PIM" "PDC_PIM_LPMC" "offset" "ptr" "count" +Get LPMC data from +.Ar offset +in PIM into a +.Ar ptr +memory area of no more than +.Ar count +bytes in size. +Data provided includes: HV dependent 0x4a words, check type, HV dependent +word, cache check, TLB check, bus check, assist check, assist state, +path info, system responder address, system requestor address, +FPU registers (fpr0-fpr31). +.It Fn pdc "PDC_PIM" "PDC_PIM_SBD" "offset" "ptr" "count" +Get Soft Boot Data from +.Ar offset +in PIM into a +.Ar ptr +memory area of no more than +.Ar count +bytes in size. +Data provided includes: general registers (r0-r31), control registers +(cr0-cr31), space registers (sr0-sr7), IIA space tail, IIA offset tail, +HV dependent word, CPU state. +.It Fn pdc "PDC_PIM" "PDC_PIM_TOC" "offset" "ptr" "count" +Get TOC (Transfer Of Control) data from +.Ar offset +in PIM into a +.Ar ptr +memory area of no more than +.Ar count +bytes in size. +Data provided includes: general registers (r0-r31), control registers +(cr0-cr31), space registers (sr0-sr7), IIA space tail, IIA offset tail, +HV dependent word, CPU state. +.It Fn pdc "PDC_POW_FAIL" "PDC_POW_FAIL_DFLT" +Prepare for power fail. +On the machines that provide power failure interrupts, this function is +to be called after the operating system has completed +.Xr shutdown 8 +to finish system-dependent tasks and power down. +This function only requires 512 bytes of stack. +.It Fn pdc "PDC_PROC" "PDC_PROC_STOP" +Stop the currently executing processor and also disable bus requestorship, +disable interrupts, and exclude the processor from cache coherency protocols. +The caller must flush any necessary data from the cache before calling this +function. +.It Fn pdc "PDC_PROC" "PDC_PROC_RENDEZVOUS" +Enter the reset rendezvous code on the current processor. +This function is only implemented on category B processors and +implementation is optional on category A processors. +.It Fn pdc "PDC_PSW" "PDC_PSW_GETMASK" "ptr" +Get the mask of default bits implemented into a word pointed to by the +.Ar ptr +argument. +The following mask values are possible: +.Pp +.Bl -tag -width 100 -compact +.It 1 +Default endianness bit is available. +.It 2 +Default word width bit is available. +.El +.It Fn pdc "PDC_PSW" "PDC_PSW_DEFAULTS" "ptr" +Retrieve the default PSW bits into the word pointed to by the +.Ar ptr +argument. +.It Fn pdc "PDC_PSW" "PDC_PSW_SETDEFAULTS" "bits" +Set the default PSW +.Ar bits . +.It Fn pdc "PDC_SOFT_POWER" "PDC_SOFT_POWER_INFO" "ptr" +Retrieve +.Dq power +register address into the word pointed to by the +.Ar ptr +argument. +Bit-0 in the +.Dq power +register address being set specifies the power button being depressed. +No dampening is required, unlike with the +.Xr lasi 4 +power circuit. +.It Fn pdc "PDC_SOFT_POWER" "PDC_SOFT_POWER_ENABLE" "ptr" "stat" +Enable (zero +.Ar stat ) +or disable (non-zero +.Ar stat ) +the soft power function, +where disable means the machine will turn immediately off +should the power get depressed. +The +.Ar ptr +argument still points to the data provided previously +by the PDC_SOFT_POWER_INFO call. +.It Fn pdc "PDC_STABLE" "PDC_STABLE_READ" "offset" "ptr" "count" +Read contents of the +.Dq Stable Storage +at +.Ar offset +into the memory area pointed to by the +.Ar ptr +argument of no more than +.Ar count +bytes. +.Pp +The format of the stable storage is as follows: +.Bl -column "offset" "0x00" "contents" -offset indent +.It Sy "offset" Ta Sy "size" Ta Sy "contents" +.It "0x0000" Ta "0x20" Ta "primary bootpath" +.It "0x0020" Ta "0x20" Ta "reserved" +.It "0x0040" Ta "0x02" Ta "OS ID" +.It "0x0042" Ta "0x16" Ta "OS dependent" +.It "0x0058" Ta "0x02" Ta "diagnostic" +.It "0x005a" Ta "0x03" Ta "reserved" +.It "0x005d" Ta "0x02" Ta "OS dependent" +.It "0x005f" Ta "0x01" Ta "fast size" +.It "0x0060" Ta "0x20" Ta "console path" +.It "0x0080" Ta "0x20" Ta "alternative boot path" +.It "0x00a0" Ta "0x20" Ta "keyboard path" +.It "0x00c0" Ta "0x20" Ta "reserved" +.It "0x00e0" Ta "size" Ta "OS dependent" +.El +.Pp +The +.Dq OS ID +field may have the following values: +.Bl -column "value" "OS" -offset indent +.It Sy "value" Ta Sy "OS" +.It "0x000" Ta "No OS-dependent info" +.It "0x001" Ta "HP-UX" +.It "0x002" Ta "MPE-iX" +.It "0x003" Ta "OSF" +.It "0x004" Ta "HP-RT" +.It "0x005" Ta "Novell Netware" +.El +.Pp +The +.Dq fast size +field is the amount of memory to be tested upon system boot +and is a power of two multiplier for 256KB. +Values of 0xe and 0xf are reserved. +.It Fn pdc "PDC_STABLE" "PDC_STABLE_WRITE" "address" "ptr" "count" +Write data pointed to by the +.Ar ptr +argument of +.Ar count +bytes at +.Ar address +in the +.Dq Stable Storage . +.It Fn pdc "PDC_STABLE" "PDC_STABLE_SIZE" "ptr" +Put the size of the +.Dq Stable Storage +into the word pointed to by the +.Ar ptr +argument. +.It Fn pdc "PDC_STABLE" "PDC_STABLE_VRFY" "ptr" +Verify that the contents of the +.Dq Stable Storage +are valid. +.It Fn pdc "PDC_STABLE" "PDC_STABLE_INIT" "ptr" +Reset the contents of the +.Dq Stable Storage +to zeroes. +.It Fn pdc "PDC_SYSMAP" "PDC_SYSMAP_FIND" "ptr" "path" "number" +Map module +.Ar number +into HPA and also provide an area size starting at HPA and a number of +additional addresses placed into the data area pointed to by the +.Ar ptr +argument words one, two, and three, respectively. +The device path is placed into the data area pointed to by the +.Ar path +argument. +.It Fn pdc "PDC_SYSMAP" "PDC_SYSMAP_ADDR" "ptr" "im" "ia" +Retrieve a list of additional addresses for the module number +.Ar im +for the address index +.Ar ia . +The result is placed into the data area pointed to by +.Ar ptr , +where the first word gives the address and the second the size of the area. +.It Fn pdc "PDC_SYSMAP" "PDC_SYSMAP_HPA" "ptr" "path_ptr" +Map device +.Ar path_ptr +into device's HPA placed into a word pointed to by the +.Ar ptr +argument. +.It Fn pdc "PDC_TLB" "PDC_TLB_INFO" "ptr" +Retrieve the hardware TLB handler parameters. +This includes a minimal and maximal size for the page table, in bytes, +stored into words zero and one, respectively, +in the data area pointed to by the +.Ar ptr +argument. +.It Fn pdc "PDC_TLB" "PDC_TLB_CONFIG" "ptr" "base" "size" "param" +Configure the hardware TLB miss handler given the same parameters fetched +previously with PDC_TLB_INFO into data area pointed to by the +.Ar ptr +and page table +.Ar base +address, page table +.Ar size , +and handler parameters +.Ar param . +The hardware TLB handler parameter bits are as follows: +.Pp +.Bl -tag -width 0xff -compact +.It 1 +Enable the hardware TLB miss handler. +The default is to load cr28 with the faulted page table entry address. +.It 4 +Pointer to the next page table entry is put into cr28. +.It 6 +Next pointer field of the page table entry is put into cr28. +.El +.Pp +Resetting the page table address and/or size without disabling +the hardware TLB miss handler is allowed. +Any changes made are immediate upon Code or Data virtual +address translation bits are set in PSW. +.It Fn pdc "PDC_TOD" "PDC_TOD_READ" "ptr" +Read the TOD, which is a UNIX Epoch time, into the data area +pointed to by the +.Ar ptr +argument. +That includes seconds in the first word and microseconds in +the second. +.It Fn pdc "PDC_TOD" "PDC_TOD_WRITE" "sec" "usec" +Write TOD with UNIX Epoch time with +.Ar sec +seconds and +.Ar usec +microseconds. +.It Fn pdc "PDC_TOD" "PDC_TOD_ITIMER" "ptr" +Get TOD and CPU timer accuracy into the data location pointed to by the +.Ar ptr +argument. +The first two words specify a double floating-point value giving +CPU timer frequency. +The next two words provide accuracy in parts per billion for the TOD and +CPU timer, respectively. +.El +.Sh FILES +.Bl -tag -width /sys/arch/hppa/dev/cpudevs -compact +.It machine/pdc.h +C header file with relevant definitions. +.It /sys/arch/hppa/dev/cpudevs +System components' version numbers. +.It /dev/console +System console device. +.El +.Sh DIAGNOSTICS +Upon successful completion all procedures return zero. +The following error codes are returned in case of failures: +.Pp +.Bl -tag -width PDC_ERR_NOPROC -compact +.It PDC_ERR_NOPROC +No such procedure +.It PDC_ERR_NOPT +No such option +.It PDC_ERR_COMPL +Unable to complete without error +.It PDC_ERR_EOD +No such device +.It PDC_ERR_INVAL +Invalid argument +.It PDC_ERR_PFAIL +Aborted by powerfail +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr io 4 , +.Xr lasi 4 +.Rs +.%T PA-RISC 1.1 Firmware Architecture Reference Specification +.%A Hewlett-Packard +.%D March 8, 1999 +.Re +.Rs +.%T PA-RISC 2.0 Firmware Architecture Reference Specification +.%A Hewlett-Packard +.%D March 7, 1999 +.Re diff --git a/static/openbsd/man4/man4.hppa/phantomas.4 b/static/openbsd/man4/man4.hppa/phantomas.4 new file mode 100644 index 00000000..36f44c18 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/phantomas.4 @@ -0,0 +1,69 @@ +.\" $OpenBSD: phantomas.4,v 1.10 2020/12/22 10:33:34 tobias Exp $ +.\" +.\" Copyright (c) 2002 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, +.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 22 2020 $ +.Dt PHANTOMAS 4 hppa +.Os +.Sh NAME +.Nm phantomas +.Nd Phantom PseudoBC GSC+ Port +.Sh SYNOPSIS +.Cd "phantomas0 at mainbus?" +.Cd "dino* at phantomas?" +.Cd "lasi* at phantomas?" +.Cd "sti* at phantomas?" +.Cd "wax* at phantomas?" +.Sh DESCRIPTION +The Phantom bus converter is used to connect +various devices and controllers +to the system bus, +where the processor +and memory are located. +Currently the following are connected: +the +.Xr sti 4 +graphics interface; +the +.Xr lasi 4 +and +.Xr wax 4 +bus host adapters for +.Xr gsc 4 ; +and the +.Xr dino 4 +PCI bridge. +.Sh SEE ALSO +.Xr dino 4 , +.Xr gsc 4 , +.Xr intro 4 , +.Xr lasi 4 , +.Xr sti 4 , +.Xr wax 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 3.3 . diff --git a/static/openbsd/man4/man4.hppa/power.4 b/static/openbsd/man4/man4.hppa/power.4 new file mode 100644 index 00000000..bd822ffa --- /dev/null +++ b/static/openbsd/man4/man4.hppa/power.4 @@ -0,0 +1,84 @@ +.\" $OpenBSD: power.4,v 1.5 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" Copyright (c) 2003 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, +.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt POWER 4 hppa +.Os +.Sh NAME +.Nm power +.Nd power button and power fail support +.Sh SYNOPSIS +.Cd "power0 at mainbus?" +.Sh DESCRIPTION +.Tn HP PA-RISC +machines support power failure detection in different forms: +.Pp +.Bl -bullet -offset indent -compact +.It +.Dq soft +power button +.It +power failure interrupt +.El +.Pp +The +.Nm +driver tries its best to determine the power failure condition +that is a result of a power button being depressed or a power supply +system failure or a similar condition. +Upon detection of any of the aforementioned conditions, it tries to gracefully +.Pq if possible +shutdown the system through a call to the +.Xr boot 9 +function. +.Pp +On systems equipped with the +.Xr lasi 4 +bus adapter, we find a +.Dq soft +power button which upon depression gives us a signal in the +.Dq power register +and thus polling periodically we detect the event. +Since that bit comes directly from the power button without any dampening, +we perform a second long delay; +thus quick transitions off and on will +.Em not +result in a shutdown. +.Pp +On modern systems, an interruption is signalled upon the power +button depression and thus this avoids polling and does not require +.Pq as does being implemented in hardware +dampening. +.Sh SEE ALSO +.Xr intro 4 , +.Xr lasi 4 , +.Xr pdc 4 , +.Xr boot 9 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 3.4 . diff --git a/static/openbsd/man4/man4.hppa/runway.4 b/static/openbsd/man4/man4.hppa/runway.4 new file mode 100644 index 00000000..b64ba6be --- /dev/null +++ b/static/openbsd/man4/man4.hppa/runway.4 @@ -0,0 +1,65 @@ +.\" $OpenBSD: runway.4,v 1.5 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" Copyright (c) 2004 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, +.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt RUNWAY 4 hppa +.Os +.Sh NAME +.Nm runway +.Nd Runway bus +.Sh SYNOPSIS +.Cd "uturn* at mainbus?" +.Sh DESCRIPTION +The +.Nm +bus is a CPU and memory bus on systems based on the PA-7200, +PA-8000, and later CPUs. +The +.Nm +bus is a 64-bit multiplexed address/data bus with support for cache +coherency and allows up to 4-way SMP system configurations. +.Pp +One or two +.Xr uturn 4 +bridges connect the +.Nm +bus to the system's +.Xr gsc 4 +or +.Xr pci 4 +buses. +.Sh SEE ALSO +.Xr cpu 4 , +.Xr dino 4 , +.Xr gsc 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr uturn 4 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Ox 3.7 . diff --git a/static/openbsd/man4/man4.hppa/ssio.4 b/static/openbsd/man4/man4.hppa/ssio.4 new file mode 100644 index 00000000..208738d2 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/ssio.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: ssio.4,v 1.4 2007/07/15 20:00:49 kettenis Exp $ +.\" +.\" Copyright (c) 2007 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 15 2007 $ +.Dt SSIO 4 hppa +.Os +.Sh NAME +.Nm ssio +.Nd National Semiconductor PC87560 Legacy IO +.Sh SYNOPSIS +.Cd "ssio* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the National Semiconductor PC87560 Legacy IO +chip on systems with PA-8500 and later 64-bit CPUs. +It configures the Programmable Interrupt Controllers integrated on the chip +to route interrupts for the integrated +.Xr ohci 4 +USB controller (which appears as a separate PCI device). +.Pp +.Ox +provides support for the following devices: +.Pp +.Bl -tag -width 12n -offset indent -compact +.It Xr com 4 +serial communications interface +.It Xr lpt 4 +parallel port driver +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . diff --git a/static/openbsd/man4/man4.hppa/uturn.4 b/static/openbsd/man4/man4.hppa/uturn.4 new file mode 100644 index 00000000..70e2195c --- /dev/null +++ b/static/openbsd/man4/man4.hppa/uturn.4 @@ -0,0 +1,65 @@ +.\" $OpenBSD: uturn.4,v 1.8 2008/04/27 19:33:39 jmc Exp $ +.\" +.\" Copyright (c) 2004 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, +.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: April 27 2008 $ +.Dt UTURN 4 hppa +.Os +.Sh NAME +.Nm uturn +.Nd U2/Uturn, Runway to GSC Bus bridge & IOA +.Sh SYNOPSIS +.Cd "uturn* at mainbus?" +.Cd "astro* at uturn?" +.Cd "dino* at uturn?" +.Cd "lasi* at uturn?" +.Cd "gecko* at uturn?" +.Cd "sti* at uturn?" +.Sh DESCRIPTION +.Nm +provides the functionality of IOA (not currently supported) as a bridge +from the Runway bus (see +.Xr runway 4 +for more information) to GSC. +Modern systems, based on the PA-8000 and later 64-bit CPUs, use the +.Nm U-Turn +version, whilst earlier systems, based on the PA-7200 CPU, used +a different version of the chip called +.Nm U2 . +.Sh SEE ALSO +.Xr astro 4 , +.Xr cpu 4 , +.Xr dino 4 , +.Xr gecko 4 , +.Xr gsc 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr runway 4 , +.Xr sti 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 3.7 . diff --git a/static/openbsd/man4/man4.hppa/wax.4 b/static/openbsd/man4/man4.hppa/wax.4 new file mode 100644 index 00000000..17ad9c76 --- /dev/null +++ b/static/openbsd/man4/man4.hppa/wax.4 @@ -0,0 +1,105 @@ +.\" $OpenBSD: wax.4,v 1.7 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" +.\" Copyright (c) 2003 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt WAX 4 hppa +.Os +.Sh NAME +.Nm wax +.Nd GSC bus controller and I/O subsystem +.Sh SYNOPSIS +.Cd "wax* at mainbus0 irq 24" +.Cd "wax* at phantomas0 irq 24" +.Cd "gsc2 at wax?" +.Sh DESCRIPTION +The +.Nm +GSC bus controller is a version of +.Xr lasi 4 +with limited functionality and no additional devices on the crystal. +It is mainly used as a GSC bus controller for additional onboard devices +(e.g. 2nd RS232 or HIL) and sometimes add-on cards (such as a TR-9000 +card for the +.Tn HP 9000/712 +models). +.Sh MACHINES +An incomplete list of machines that use the +.Nm +bus controller: +.Pp +.Bl -bullet -compact +.It +712/* add-on cards +.It +715/{64/80/100}[XC] +.It +725/{64/80/100} +.It +743/* +.It +744/* +.It +745/* +.It +A180[C] +.It +B132L[+], B160L, B180L+ +.It +C100, C110 +.It +J200, J210[XC] +.It +RDI PrecisionBook +.El +.Sh SEE ALSO +.Xr asp 4 , +.Xr gsc 4 , +.Xr intro 4 , +.Xr io 4 , +.Xr lasi 4 , +.Xr phantomas 4 +.Rs +.%T Precision I/O Architecture Reference Specification +.%Q Hewlett-Packard +.Re +.Rs +.%T 712 I/O Subsystem ERS +.%N Revision 1.1 +.%D 12 February 1993 +.%Q Hewlett-Packard +.%V Dwg No. A-A2263-66510-31 +.Re +.Rs +.%Q Hewlett-Packard Journal +.%D April 1995 +.%V Volume 46 Number 2 +.Re +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 3.4 . diff --git a/static/openbsd/man4/man4.i386/Makefile b/static/openbsd/man4/man4.i386/Makefile new file mode 100644 index 00000000..e649defc --- /dev/null +++ b/static/openbsd/man4/man4.i386/Makefile @@ -0,0 +1,38 @@ +MAN = amdmsr.4 \ + amdpcib.4 \ + apm.4 \ + autoconf.4 \ + bios.4 \ + cpu.4 \ + esm.4 \ + geodesc.4 \ + glxpcib.4 \ + glxsb.4 \ + gscpcib.4 \ + gscpm.4 \ + gus.4 \ + ichpcib.4 \ + ie.4 \ + intro.4 \ + ioapic.4 \ + joy.4 \ + le.4 \ + lms.4 \ + mem.4 \ + mms.4 \ + mpbios.4 \ + mtrr.4 \ + npx.4 \ + nvram.4 \ + pas.4 \ + pcibios.4 \ + pctr.4 \ + sb.4 \ + skgpio.4 \ + tcpcib.4 \ + uha.4 \ + wds.4 \ + wdt.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.i386/amdmsr.4 b/static/openbsd/man4/man4.i386/amdmsr.4 new file mode 100644 index 00000000..ed32faf6 --- /dev/null +++ b/static/openbsd/man4/man4.i386/amdmsr.4 @@ -0,0 +1,59 @@ +.\" $OpenBSD: amdmsr.4,v 1.6 2014/01/21 03:15:46 schwarze Exp $ +.\" +.\" MSR access driver for AMD Geode LX CPUs with graphics processor. +.\" Copyright 2008 Marc Balmer +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 21 2014 $ +.Dt AMDMSR 4 i386 +.Os +.Sh NAME +.Nm amdmsr +.Nd access MSRs on certain AMD Geode LX systems +.Sh SYNOPSIS +.Cd "amdmsr0 at mainbus?" +.Sh DESCRIPTION +The +.Nm +device provides access to the Model Specific Registers (MSRs) on systems with +an AMD Geode LX CPU and graphics processor. +.Ss IOCTL INTERFACE +MSRs can be read or written via +.Fn ioctl +calls performed on +.Pa /dev/amdmsr . +Declarations and data types are to be found in +.In machine/amdmsr.h . +.Pp +Read or write requests are performed using: +.Bd -literal -offset xxxx +struct amdmsr_req { + u_int32_t addr; /* 32-bit MSR address */ + u_int64_t val; /* 64-bit MSR value */ +}; +.Ed +.Pp +The +.Fa RDMSR +ioctl is used to read an MSR register. +.Pp +The +.Fa WRMSR +ioctl is used to write an MSR register. +.Sh SEE ALSO +.Xr ioctl 2 +.Sh HISTORY +.Nm +support was added in +.Ox 4.4 . diff --git a/static/openbsd/man4/man4.i386/amdpcib.4 b/static/openbsd/man4/man4.i386/amdpcib.4 new file mode 100644 index 00000000..8fb77c39 --- /dev/null +++ b/static/openbsd/man4/man4.i386/amdpcib.4 @@ -0,0 +1,33 @@ +.\" $OpenBSD: amdpcib.4,v 1.5 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Marc Balmer, 2007. Public Domain. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt AMDPCIB 4 i386 +.Os +.Sh NAME +.Nm amdpcib +.Nd AMD-8111 series LPC bridge and timecounter +.Sh SYNOPSIS +.Cd "amdpcib* at pci?" +.Cd "isa* at amdpcib?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the AMD-8111 LPC bridge and implements a +32/64-bit 14.3 MHz (or variable) timecounter using the HPET timer. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 , +.Xr watchdog 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Michael Shalayeff . diff --git a/static/openbsd/man4/man4.i386/apm.4 b/static/openbsd/man4/man4.i386/apm.4 new file mode 100644 index 00000000..84775dec --- /dev/null +++ b/static/openbsd/man4/man4.i386/apm.4 @@ -0,0 +1,221 @@ +.\" $OpenBSD: apm.4,v 1.36 2023/01/30 14:43:29 jcs Exp $ +.\" +.\" Copyright (c) 1998 Marco S. Hyman +.\" +.\" Permission to copy all or part of this material for any purpose is +.\" granted provided that the above copyright notice and this paragraph +.\" are duplicated in all copies. THIS SOFTWARE IS PROVIDED ``AS IS'' +.\" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT +.\" LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE. +.\" +.Dd $Mdocdate: January 30 2023 $ +.Dt APM 4 i386 +.Os +.Sh NAME +.Nm apm +.Nd advanced power management device interface +.Sh SYNOPSIS +.Cd "apm0 at bios0 flags 0x0000" +.Sh DESCRIPTION +The +.Nm +driver provides an interface to the Advanced Power Management +.Pq APM +BIOS functions. +The driver supports versions 1.0, 1.1, and 1.2 interface specifications. +.Pp +This driver also provides an interface to +.Xr acpi 4 +on some machines. +.Pp +The low two bytes of the flags specify the version of the specification +driver should conform to in binary decimal notation. +The value of 0x0101 would specify version 1.1 of the interface +specification to be used. +.Pp +The value of 0x10000 specifies whether to leave interrupts enabled +when calling APM BIOS routines. +This is needed for some +.Tn IBM +laptops, the symptoms are +hangs and freezes on suspend, stand by, and hibernation activities. +.Pp +The value of 0x20000 specifies to swap the bytes of the battery +life estimation (the DX register) as given from the APM BIOS. +This is needed for some +.Tn SONY VAIO +laptops, such as some 505 models. +.Pp +Configuration options: +.Pp +.Bl -tag -width DIAGNOSTIC -compact -offset indent +.It Dv APMDEBUG +Enable various driver status messages. +.It Dv DIAGNOSTIC +Enable debugging messages. +.It Dv DEBUG +Enable other debugging messages. +.El +.Pp +The +.Nm +driver implements the following +.Xr ioctl 2 +calls. +They are defined in +.In machine/apmvar.h . +.Bl -tag -width Ds +.It Dv APM_IOC_REJECT +.Em Not implemented . DO NOT USE . +.It Dv APM_IOC_STANDBY +.Pq Li "no parameters" +Request +.Dq standby +mode. +.It Dv APM_IOC_SUSPEND +.Pq Li "no parameters" +Request +.Dq suspend +mode. +.It Dv APM_IOC_HIBERNATE +.Pq Li "no parameters" +Request +.Dq hibernate +mode. +.It Dv APM_IOC_GETPOWER +.Pq Li "struct apm_power_info" +Request the current power state. +The argument structure is as follows: +.Bd -literal -offset indent +struct apm_power_info { + u_char battery_state; + u_char ac_state; + u_char battery_life; + u_char spare1; + u_int minutes_left; + u_int spare2[6]; +}; +.Ed +.Pp +The following values are defined for +.Va battery_state : +.Bl -tag -width Ds +.It Dv APM_BATT_HIGH +Battery has a high state of charge. +.It Dv APM_BATT_LOW +Battery has a low state of charge. +.It Dv APM_BATT_CRITICAL +Battery has a critical state of charge. +.It Dv APM_BATT_CHARGING +Battery is not high, low, or critical and is currently charging. +.It Dv APM_BATT_UNKNOWN +Cannot read the current battery state. +.It Dv APM_BATTERY_ABSENT +No battery installed. +.El +.Pp +The following values are defined for +.Va ac_state : +.Bl -tag -width Ds +.It Dv APM_AC_OFF +External power not detected. +.It Dv APM_AC_ON +External power detected. +.It Dv APM_AC_BACKUP +Backup power in use. +.It Dv APM_AC_UNKNOWN +External power state unknown. +.El +.Pp +The +.Va battery_life +value contains the estimated percentage of battery life available. +100% indicates a full charge. +.Pp +The +.Va minutes_left +value contains the estimated number of minutes of battery life +remaining. +.It Dv APM_IOC_DEV_CTL +.Pq Li "struct apm_ctl" +Allows an application to directly set the +APM operating mode. +The argument structure is as follows: +.Bd -literal -offset indent +struct apm_ctl { + u_int dev; + u_int mode; +}; +.Ed +.Pp +.Va dev +indicates the device, typically +.Dv APM_DEV_ALLDEVS . +.Pp +.Va mode +indicates the desired operating mode. +Possible values are +.Bl -tag -width Ds -compact -offset indent +.It Dv APM_SYS_READY +.It Dv APM_SYS_STANDBY +.It Dv APM_SYS_SUSPEND +.It Dv APM_SYS_OFF +.It Dv APM_LASTREQ_INPROG +.It Dv APM_LASTREQ_REJECTED +.El +.It Dv APM_IOC_PRN_CTL +.Pq Li "int" +This +.Xr ioctl 2 +controls message output by the APM +driver when a power change event is detected. +The integer parameter is one of: +.Bl -tag -width Ds +.It Dv APM_PRINT_ON +All power change events result in a message. +This is the normal operating mode for the driver. +.It Dv APM_PRINT_OFF +Power change event messages are suppressed. +.It Dv APM_PRINT_PCT +Power change event messages are suppressed unless the estimated +battery life percentage changes. +.El +.El +.Sh FILES +.Bl -tag -width "/dev/apmctlXXX" +.It /dev/apm +Power management data device. +May only be opened read-only. +May be opened by multiple concurrent users. +.It /dev/apmctl +Power management control device. +May be opened read-write or write-only. +May only be opened by one user at a time. +An attempt to open the file when in use will fail, returning +.Er EBUSY . +.El +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr apm 8 , +.Xr apmd 8 , +.Xr halt 8 +.Sh HISTORY +The +.Nm +driver source code contains these copyrights: +.Pp +.Bl -item -compact +.It +.Li Copyright (c) 1995 John T. Kohl. All rights reserved. +.It +.Li Copyright (C) 1994 by HOSOKAWA Tatsumi +.El +.Pp +\&...and has been hacked on by many others since. +.Sh BUGS +Not all the BIOSes support power down the way we are attempting +to execute it. +.Pp +Not all BIOS vendors even read the specification. diff --git a/static/openbsd/man4/man4.i386/autoconf.4 b/static/openbsd/man4/man4.i386/autoconf.4 new file mode 100644 index 00000000..e9e59aec --- /dev/null +++ b/static/openbsd/man4/man4.i386/autoconf.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: autoconf.4,v 1.7 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" Copyright (c) 1994 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christopher G. Demetriou. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt AUTOCONF 4 i386 +.Os +.Sh NAME +.Nm autoconf +.Nd diagnostics from the autoconfiguration code +.Sh DESCRIPTION +When +.Ox +bootstraps it probes the innards of the machine +on which it is running +and locates controllers, drives, and other devices, printing out +what it finds on the console. +This procedure is driven by a system configuration table which is processed by +.Xr config 8 +and compiled into each kernel. +Devices which exist in the machine but are not configured into the +kernel are usually not detected. +.Sh SEE ALSO +.Xr intro 4 , +.Xr boot_i386 8 , +.Xr config 8 diff --git a/static/openbsd/man4/man4.i386/bios.4 b/static/openbsd/man4/man4.i386/bios.4 new file mode 100644 index 00000000..d33f3548 --- /dev/null +++ b/static/openbsd/man4/man4.i386/bios.4 @@ -0,0 +1,95 @@ +.\" $OpenBSD: bios.4,v 1.11 2007/05/31 19:19:54 jmc Exp $ +.\" +.\" Copyright (c) 2001 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, +.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt BIOS 4 i386 +.Os +.Sh NAME +.Nm bios +.Nd a driver for PC Firmware, aka BIOS +.Sh SYNOPSIS +.Cd "bios0 at mainbus0 flags 0x0000" +.Cd "apm0 at bios0 flags 0x0000" +.Cd "pcibios0 at bios0 flags 0x0000" +.Sh DESCRIPTION +.Ox +provides support for PC firmware, aka BIOS and some of its functions, +currently: APM subsystem, BIOS32 extensions, PCI BIOS subsystem. +.Pp +The +.Nm +driver also identifies BIOS type (such as "AT/286+", which is +almost always used in modern machines) and BIOS image date stamp, +which is, presumably, the day the BIOS image was compiled by vendor +and could be used as a crude BIOS version identification. +The +.Nm +driver also scans the ISA memory hole at 640K-1M for optional +ROM images and reserves the space from being used by various +ISA devices, for example +.Xr pcic 4 . +.Pp +Flags is a bit mask, each bit of which specifies which functions +of the driver to disable. +.Bl -tag -width 0x0001 +.It 0x0001 +BIOS32 attachment. +.Pp +Do not probe or attach to BIOS32 extensions. +BIOS32 is one of +the interfaces to the PCI BIOS configuration tables. +.It 0x0002 +PCI BIOS attachment. +.Pp +Do not probe or attach the +.Xr pcibios 4 +device, which performs certain PCI configuration tasks. +.It 0x0004 +Do not perform the scan for ROM images in the ISA memory hole +(0xc0000 - 0xf0000 physical addresses). +.It 0x0008 +SMBIOS attachment. +.Pp +Do not probe or attach to SMBIOS. +SMBIOS provides greater detail about system hardware configuration +and is required to attach +.Xr ipmi 4 +on most systems. +.El +.Sh SEE ALSO +.Xr apm 4 , +.Xr intro 4 , +.Xr pcibios 4 , +.Xr pcmcia 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.2 . +.Sh BUGS +On some machines optional ROM images do not pass checksum check, +but it's considered better to reserve space for those anyway, +choosing lesser evil from many. diff --git a/static/openbsd/man4/man4.i386/cpu.4 b/static/openbsd/man4/man4.i386/cpu.4 new file mode 100644 index 00000000..d980f591 --- /dev/null +++ b/static/openbsd/man4/man4.i386/cpu.4 @@ -0,0 +1,99 @@ +.\" $OpenBSD: cpu.4,v 1.20 2024/09/10 17:01:09 tb Exp $ +.\" +.\" Copyright (c) 2004 Ted Unangst +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 10 2024 $ +.Dt CPU 4 i386 +.Os +.Sh NAME +.Nm cpu +.Nd Central Processing Unit +.Sh SYNOPSIS +.Cd "cpu0 at mainbus?" +.Cd "cpu* at mainbus?" +.Sh DESCRIPTION +Several processor models have additional features that extend their base +functionality, such as power and frequency control or thermal monitoring. +.Pp +The +.Xr sysctl 2 +.Va hw.cpuspeed +returns the current operating frequency of the processor, +though on some processors this value may be only an approximation. +If possible, speed may be adjusted by altering +.Va hw.setperf +from 0 to 100, +representing percentage of maximum speed. +.Pp +There are several possible implementations for speed adjustment, +all transparent to the user. +In systems with more than one control capability, they are preferred in the +order given: +.Bl -tag -width tenletters +.It LongRun +Found on Transmeta Crusoe processors, offering frequency scaling with numerous +positions. +The processor dynamically adjusts frequency in response to load; the setperf +value is interpreted as the maximum. +.It EST +Enhanced SpeedStep found on Intel Pentium M processors, +offering frequency scaling with numerous positions. +.It SpeedStep +Found on some Intel Pentium 3 and newer mobile chips, +it is capable of adjusting frequency between a low and high value. +It is only enabled on some chipsets. +.It TCC +Thermal Control Circuit found on Intel Pentium 4 and newer processors, +it can adjust processor duty cycle in 12.5 percent increments. +.It PowerNow +Found on various AMD processors. +It currently only supports a limited set of models +in the K6, K7, and K8 families. +.El +.Pp +The presence of extended instruction sets can be determined by the sysctl +.Va machdep : +.Bl -tag -width "tenletters" +.It osfxsr +Supports the fxsave instruction. +.It sse +Supports the SSE instruction set. +.It sse2 +Supports the SSE2 instruction set. +.It xcrypt +Supports the VIA AES encryption instruction set. +.El +.Pp +The sysctl +.Va hw.sensors +returns the current temperature reported by the processor. +.Sh SEE ALSO +.Xr sysctl 8 +.Sh BUGS +Due to the way in which thermal information is reported on Intel processors, +the temperature may be off by exactly +/-15 degrees C. +.Pp +For multiprocessor kernels with more than one CPU sensor, +processors report identical temperatures +since the temperature is taken from the processor running the sensors update. diff --git a/static/openbsd/man4/man4.i386/esm.4 b/static/openbsd/man4/man4.i386/esm.4 new file mode 100644 index 00000000..395ef109 --- /dev/null +++ b/static/openbsd/man4/man4.i386/esm.4 @@ -0,0 +1,89 @@ +.\" $OpenBSD: esm.4,v 1.6 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: July 16 2013 $ +.Dt ESM 4 i386 +.Os +.Sh NAME +.Nm esm +.Nd Dell Embedded Server Management +.Sh SYNOPSIS +.Cd "esm0 at mainbus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the monitoring of the environmental sensors +present in a variety of Dell servers. +The hardware monitoring is accessed via the +.Va hw.sensors +.Xr sysctl 8 +variable. +.Pp +Devices compatible with the +.Nm +driver can provide an arbitrary set of sensors which may include the +following types: +.Bl -column "temperature" "Units" -offset indent +.It Sy "Sensor" Ta Sy "Units" +.It Li "temperature" Ta "uK" +.It Li "fan" Ta "RPM" +.It Li "volts" Ta "uVDC" +.El +.Pp +Sensor data is updated every 10 seconds. +.Pp +The Embedded Server Management framework has been replaced in more recent +Dell systems with the Intelligent Platform Management Interface. +Servers using the Intelligent Platform Management Interface may be +monitored by the +.Xr ipmi 4 +driver. +.Sh WATCHDOG +ESM provides +.Xr watchdog 4 +timer functionality. +Once configured, if the watchdog is not reset within +a certain period of time, +it will timeout and the server will reset. +The reset will occur regardless of the recoverability of the hang or crash. +.Pp +Example of enabling a watchdog: +.Pp +.Dl # sysctl kern.watchdog.period=10 +.Pp +In this case if the watchdog is not reset, +it'll reboot the server after roughly 10 seconds. +.Pp +Example of disabling the watchdog: +.Pp +.Dl # sysctl kern.watchdog.period=0 +.Sh SEE ALSO +.Xr intro 4 , +.Xr ipmi 4 , +.Xr watchdog 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Jordan Hargrave Aq Mt jordan@openbsd.org +and +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/man4.i386/geodesc.4 b/static/openbsd/man4/man4.i386/geodesc.4 new file mode 100644 index 00000000..ed377952 --- /dev/null +++ b/static/openbsd/man4/man4.i386/geodesc.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: geodesc.4,v 1.10 2007/05/31 19:19:54 jmc Exp $ +.\" +.\"Copyright (c) 2003 Markus Friedl +.\" +.\"Permission to use, copy, modify, and distribute this software for any +.\"purpose with or without fee is hereby granted, provided that the above +.\"copyright notice and this permission notice appear in all copies. +.\" +.\"THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\"WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\"MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\"ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\"WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\"ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\"OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt GEODESC 4 i386 +.Os +.Sh NAME +.Nm geodesc +.Nd Geode SC1100/SCx200 IAOC watchdog timer device +.Sh SYNOPSIS +.Cd "geodesc* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports the watchdog timer of the Geode SC1100. +.Pp +The Geode SC1100/SCx200 is a member of the AMD +Information Appliance On a Chip (IAOC) family +of fully integrated x86 system chips. +.Pp +The watchdog timer may be configured via +.Xr sysctl 8 . +.Sh SEE ALSO +.Xr watchdog 4 , +.Xr sysctl 8 +.Sh HISTORY +Support for the +.Nm +was added in +.Ox 3.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Markus Friedl . diff --git a/static/openbsd/man4/man4.i386/glxpcib.4 b/static/openbsd/man4/man4.i386/glxpcib.4 new file mode 100644 index 00000000..56405bc9 --- /dev/null +++ b/static/openbsd/man4/man4.i386/glxpcib.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: glxpcib.4,v 1.11 2013/08/14 06:32:33 jmc Exp $ +.\" +.\" Michael Shalayeff, 2007. Public Domain. +.\" +.Dd $Mdocdate: August 14 2013 $ +.Dt GLXPCIB 4 i386 +.Os +.Sh NAME +.Nm glxpcib +.Nd AMD CS5536 PCI-ISA bridge with timecounter, watchdog timer, and GPIO +.Sh SYNOPSIS +.Cd "glxpcib* at pci?" +.Cd "gpio* at glxpcib?" +.Cd "iic* at glxpcib?" +.Cd "isa* at glxpcib?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the AMD Geode CS5536 Companion chip. +This device contains a number of components, including a PCI-ISA bridge. +Besides the core functionality, the +.Nm +driver implements a 32-bit 3.5 MHz timecounter, a watchdog timer device, +a GPIO device, and an SMBus interface. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr iic 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 , +.Xr pcib 4 , +.Xr watchdog 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Michael Shalayeff . +The GPIO parts were added by +.An Marc Balmer Aq Mt mbalmer@openbsd.org . diff --git a/static/openbsd/man4/man4.i386/glxsb.4 b/static/openbsd/man4/man4.i386/glxsb.4 new file mode 100644 index 00000000..8c76274a --- /dev/null +++ b/static/openbsd/man4/man4.i386/glxsb.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: glxsb.4,v 1.7 2014/08/20 11:23:41 mikeb Exp $ +.\" +.\"Copyright (c) 2006 Tom Cosgrove +.\" +.\"Permission to use, copy, modify, and distribute this software for any +.\"purpose with or without fee is hereby granted, provided that the above +.\"copyright notice and this permission notice appear in all copies. +.\" +.\"THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\"WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\"MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\"ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\"WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\"ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\"OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: August 20 2014 $ +.Dt GLXSB 4 i386 +.Os +.Sh NAME +.Nm glxsb +.Nd Geode LX Security Block crypto accelerator +.Sh SYNOPSIS +.Cd "glxsb* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports the security block of the Geode LX series processors. +The Geode LX is a member of the AMD Geode family +of integrated x86 system chips. +.Pp +Driven by periodic checks for available data from the generator, +.Nm +supplies entropy to the +.Xr random 4 +driver for common usage. +.Pp +.Nm +also supports acceleration of AES-CBC operations for +.Xr ipsec 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr ipsec 4 , +.Xr pci 4 , +.Xr random 4 , +.Xr crypto 9 +.Sh HISTORY +Support for +.Nm +was added in +.Ox 4.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Tom Cosgrove . diff --git a/static/openbsd/man4/man4.i386/gscpcib.4 b/static/openbsd/man4/man4.i386/gscpcib.4 new file mode 100644 index 00000000..76d8a705 --- /dev/null +++ b/static/openbsd/man4/man4.i386/gscpcib.4 @@ -0,0 +1,65 @@ +.\" $OpenBSD: gscpcib.4,v 1.9 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2004 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt GSCPCIB 4 i386 +.Os +.Sh NAME +.Nm gscpcib +.Nd National Semiconductor Geode SC1100 PCI-ISA bridge with GPIO +.Sh SYNOPSIS +.Cd "gscpcib* at pci?" +.Cd "isa* at gscpcib?" +.Cd "gpio* at gscpcib?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the National Semiconductor Geode SC1100 +System-on-Chip +.Tn PCI-ISA +bridge. +This device is a +.Tn PCI-ISA +bridge, but with some additional sub-devices. +Besides the core functionality, the +.Nm +driver provides support for the +.Tn GPIO +interface of this device. +.Pp +The device has 64 I/O pins which can be accessed +through the +.Xr gpio 4 +framework. +The +.Xr gpioctl 8 +program provides a convenient way to manipulate these pins from userland. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/man4.i386/gscpm.4 b/static/openbsd/man4/man4.i386/gscpm.4 new file mode 100644 index 00000000..d520ab3a --- /dev/null +++ b/static/openbsd/man4/man4.i386/gscpm.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: gscpm.4,v 1.5 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2004 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt GSCPM 4 i386 +.Os +.Sh NAME +.Nm gscpm +.Nd National Semiconductor Geode SC1100 SMI/ACPI module +.Sh SYNOPSIS +.Cd "gscpm* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the National Semiconductor Geode SC1100 +System-on-Chip SMI/ACPI module. +Only power management timer is supported for now. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/man4.i386/gus.4 b/static/openbsd/man4/man4.i386/gus.4 new file mode 100644 index 00000000..ae1e27db --- /dev/null +++ b/static/openbsd/man4/man4.i386/gus.4 @@ -0,0 +1,100 @@ +.\" $OpenBSD: gus.4,v 1.15 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: gus.4,v 1.7 1997/10/08 21:59:55 jtc Exp $ +.\" +.\" Copyright (c) 1996 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by John T. Kohl. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE +.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt GUS 4 i386 +.Os +.Sh NAME +.Nm gus +.Nd Gravis UltraSound/UltraSound MAX audio device +.Sh SYNOPSIS +.Cd "gus0 at isa? port 0x220 irq 7 drq 1 drq2 6" +.Cd "gus* at isapnp?" +.Cd "audio* at gus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Gravis UltraSound (GUS) and GUS MAX +audio cards. +Both cards have on-board memory which is used for seamless playback of samples. +They can play back 8- or 16-bit samples at up to 44.1kHz. +They can record 8-bit samples at up to 44.1kHz. +The UltraSound MAX is a full-duplex sound device, and if configured with two +DRQ channels can be used for simultaneous playback and recording. +The I/O port base is jumper-selected, and may be chosen from 0x210-0x260 in +steps of 0x10. +(The normal setting is 0x220.) +The GUS takes 16 ports at its base address and 8 ports at its base address + +0x100. +.Pp +The IRQ is software programmed, so you may select any IRQ from the set +{3,5,7,9,11,12,15}. +The DRQ lines are software programmed, and may be chosen from {1,3,5,6,7}. +The +.Dq drq2 +field in the configuration file line specifies a second DRQ line for recording. +If there is no drq2 field in the config file, the playback channel will be +used for recording DMA and only half-duplex mode will be available. +.Pp +The Gravis UltraSound MAX has an additional CODEC onboard which is +addressed with four ports at an offset of 0x10C from the base ports +(0x31C-0x36C). +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr isapnp 4 +.Sh REFERENCES +Gravis UltraSound Low-Level Toolkit, Revision 2.01, 20 May 1993, +published by Advanced Gravis and Forte Technologies. +.Pp +If you wish to use +.Xr wdc 4 +on the ISAPNP version of the card, and it comes up as DISABLED, +Gravis has a PNPCFG.EXE program which re-enables it. +.Sh HISTORY +The +.Nm +device driver appeared in +.Nx 1.1 . +.Sh BUGS +The full-duplex features of the GUS MAX have not been fully tested, and +full-duplex on the original GUS may not be possible at all. +.Pp +Only two voices on the GF1 synthesizer chip are used by this driver (for +left and right channels). +.Pp +Manipulating the mixer while audio samples are playing can lead to +device driver confusion (and maybe even a system panic). +.Pp +Manipulating the mixer device seems to create pregnant system pauses, +probably due to excessive interrupt masking. +.Pp +The joystick and MIDI port interfaces are not supported. diff --git a/static/openbsd/man4/man4.i386/ichpcib.4 b/static/openbsd/man4/man4.i386/ichpcib.4 new file mode 100644 index 00000000..cd20ca72 --- /dev/null +++ b/static/openbsd/man4/man4.i386/ichpcib.4 @@ -0,0 +1,89 @@ +.\" $OpenBSD: ichpcib.4,v 1.12 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2004 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ICHPCIB 4 i386 +.Os +.Sh NAME +.Nm ichpcib +.Nd Intel ICHx/ICHx-M LPC bridges +.Sh SYNOPSIS +.Cd "ichpcib* at pci?" +.Cd "isa* at ichpcib?" +.Sh DESCRIPTION +The +.Nm +driver supports Intel +.Tn ICH , +.Tn ICH0 , +.Tn ICH2 , +.Tn ICH2-M , +.Tn ICH3-S , +.Tn ICH3-M , +.Tn ICH4 , +.Tn ICH4-M , +.Tn ICH5 , +.Tn ICH6 , +.Tn ICH7 , +.Tn ICH7-M , +.Tn ICH8 , +.Tn ICH8-M , +.Tn ICH9 , +.Tn 6300ESB +and +.Tn 6321ESB +LPC bridges. +These devices are mostly usual +.Tn PCI-ISA +bridges but with some additional power management and monitoring +capabilities. +Besides the core functionality, the +.Nm +driver provides support for the Intel SpeedStep technology, available +for the +.Tn ICH2-M , +.Tn ICH3-M , +and +.Tn ICH4-M +chipsets, and power management timer available for all chipsets. +It allows the user to control CPU frequency with the +.Xr sysctl 8 +program. +.Sh SEE ALSO +.Xr cpu 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 , +.Xr sysctl 8 +.Sh HISTORY +Intel SpeedStep support for the ICHx-M chipsets first appeared in +.Ox 3.5 +as part of the +.Xr pcib 4 +driver. +The +.Nm +driver first appeared in +.Ox 3.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . +.Sh CAVEATS +On some old machines with the +.Tn ICH2-M +chipset, Intel SpeedStep isn't available. diff --git a/static/openbsd/man4/man4.i386/ie.4 b/static/openbsd/man4/man4.i386/ie.4 new file mode 100644 index 00000000..38d78949 --- /dev/null +++ b/static/openbsd/man4/man4.i386/ie.4 @@ -0,0 +1,60 @@ +.\" $OpenBSD: ie.4,v 1.17 2023/09/11 04:56:31 jsg Exp $ +.\" +.\" Copyright (c) 1994 James A. Jegers +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 11 2023 $ +.Dt IE 4 i386 +.Os +.Sh NAME +.Nm ie +.Nd Intel i82586 Ethernet device +.Sh SYNOPSIS +.Cd "ie0 at isa? port 0x360 irq 7 iomem 0xd0000" +.Cd "ie1 at isa? port 0x300 irq 10" +.Sh DESCRIPTION +The +.Nm +device driver supports Intel 82586-based Ethernet cards. +This includes the following network adapters: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It 3Com 3C507 +.It AT&T StarLAN 10 +.It AT&T EN100 +.It AT&T StarLAN Fiber +.It Intel EtherExpress 16 +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by your card try +.Dq ifconfig media . +For example, +.Dq ifconfig ie0 media . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/man4.i386/intro.4 b/static/openbsd/man4/man4.i386/intro.4 new file mode 100644 index 00000000..43d4d77f --- /dev/null +++ b/static/openbsd/man4/man4.i386/intro.4 @@ -0,0 +1,127 @@ +.\" $OpenBSD: intro.4,v 1.87 2023/05/03 22:03:18 jmc Exp $ +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 3 2023 $ +.Dt INTRO 4 i386 +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the i386 +(PC-clone) platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width "cardbus(4)XX" -offset 3n -compact +.It Xr acpi 4 +Advanced Configuration and Power Interface +.It Xr cardbus 4 +introduction to CardBus support +.It Xr eisa 4 +introduction to EISA bus support +.It Xr iic 4 +Inter IC (I2C) bus +.It Xr isa 4 +introduction to ISA bus support +.It Xr isapnp 4 +introduction to ISA Plug-and-Play support +.It Xr onewire 4 +1-Wire bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr pcmcia 4 +introduction to PCMCIA (PC Card) support +.It Xr usb 4 +introduction to Universal Serial Bus support +.It Xr virtio 4 +VirtIO support driver +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr cpu 4 , +.Xr config 8 +.Sh HISTORY +The +i386 +.Nm intro +first appeared in +.Nx 1.0 . diff --git a/static/openbsd/man4/man4.i386/ioapic.4 b/static/openbsd/man4/man4.i386/ioapic.4 new file mode 100644 index 00000000..ddd69119 --- /dev/null +++ b/static/openbsd/man4/man4.i386/ioapic.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: ioapic.4,v 1.3 2007/05/31 19:19:55 jmc Exp $ +.\" +.\" Copyright (c) 2006 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt IOAPIC 4 i386 +.Os +.Sh NAME +.Nm ioapic +.Nd I/O Advanced Programmable Interrupt Controller +.Sh SYNOPSIS +.Cd "ioapic0 at mainbus0" +.Sh DESCRIPTION +.Nm +is an I/O Advanced Programmable Interrupt Controller (APIC). +It provides interrupt management for systems with multiple I/O +subsystems and can distribute interrupts across multiple processors. +.Sh SEE ALSO +.Xr intro 4 +.Sh STANDARDS +.Nm +is based on +Intel's 82093AA I/O Advanced Programmable Interrupt Controller (I/O APIC) +specification. +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Bill Sommerfield . diff --git a/static/openbsd/man4/man4.i386/joy.4 b/static/openbsd/man4/man4.i386/joy.4 new file mode 100644 index 00000000..a8ebfaf9 --- /dev/null +++ b/static/openbsd/man4/man4.i386/joy.4 @@ -0,0 +1,152 @@ +.\" $OpenBSD: joy.4,v 1.15 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 1996 Matthieu Herrb +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christopher G. Demetriou. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $NetBSD: joy.4,v 1.2 1996/03/31 00:17:43 perry Exp $ +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt JOY 4 i386 +.Os +.Sh NAME +.Nm joy +.Nd games adapter +.Sh SYNOPSIS +.Cd "joy0 at isa? port 0x201" +.Cd "joy* at isapnp?" +.Sh DESCRIPTION +This driver provides access to the games adapter. +The lower bit in the minor device number selects the joystick: 0 is the first +joystick and 1 is the second. +.Pp +The game control adapter allows up to two joysticks to be attached to +the system. +The adapter plus the driver convert the present resistive value to a relative +joystick position. +On receipt of an output signal, four timing circuits are started. +By determining the time required for the circuit to time-out (a function of +the resistance), the paddle position can be determined. +The adapter could be used as a general purpose I/O card with four +analog (resistive) inputs plus four digital input points. +.Pp +Applications may call +.Fn ioctl +on a game adapter driver file descriptor +to set and get the offsets of the two potentiometers and the maximum +time-out value for the circuit. +The +.Fn ioctl +commands are listed in +.In machine/joystick.h +and currently are: +.Pp +.Bl -tag -width JOY_GET_X_OFFSET -offset indent -compact +.It JOY_SETTIMEOUT +Sets the maximum time-out for the adapter. +.It JOY_GETTIMEOUT +Returns the current maximum time-out. +.It JOY_SET_X_OFFSET +Sets an offset on X value. +.It JOY_GET_X_OFFSET +Returns the current X offset. +.It JOY_SET_Y_OFFSET +Sets an offset on Y value. +.It JOY_GET_Y_OFFSET +Returns the current Y offset. +.El +.Pp +All of these commands take an integer parameter. +.Pp +Read() on the file descriptor returns a +.Fa joystick +structure: +.Bd -literal -offset indent +struct joystick { + int x; + int y; + int b1; + int b2; +}; +.Ed +.Pp +The fields have the following functions: +.Pp +.Bl -tag -width xxx -offset indent -compact +.It Fa x +Joystick's current X coordinate (or position of paddle 1). +.It Fa y +Joystick's current Y coordinate (or position of paddle 2). +.It Fa b1 +Current state of button 1. +.It Fa b2 +Current state of button 2. +.El +.Pp +The +.Fa b1 +and +.Fa b2 +fields in struct joystick are set to 1 if the corresponding button is down, +or 0 otherwise. +.Pp +The X and Y coordinates are supposed to be between 0 and 255 for a +good joystick and a good adapter. +Unfortunately, because of the hardware hack that is used to measure the +position (by measuring the time needed to discharge an RC circuit made from +the joystick's potentiometer and a capacitor on the adapter), calibration +is needed to determine exactly what values are returned for a specific +joystick/adapter combination. +Incorrect hardware can yield negative or > 255 values. +.Pp +A typical calibration procedure uses the values returned at lower-left, +center, and upper-right positions of the joystick to compute the relative +position. +.Pp +This calibration is not part of the driver. +.Sh FILES +.Bl -tag -width /dev/joy0 -compact +.It Pa /dev/joy0 +first joystick +.It Pa /dev/joy1 +second joystick +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr intro 4 , +.Xr isa 4 , +.Xr isapnp 4 +.Sh AUTHORS +.An -nosplit +.An Jean-Marc Zucconi +wrote the +.Fx +driver. +.An Matthieu Herrb +ported it to +.Ox +and wrote this manual page. diff --git a/static/openbsd/man4/man4.i386/le.4 b/static/openbsd/man4/man4.i386/le.4 new file mode 100644 index 00000000..3654390c --- /dev/null +++ b/static/openbsd/man4/man4.i386/le.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: le.4,v 1.14 2007/05/31 19:19:55 jmc Exp $ +.\" +.\" Copyright (c) 1994 James A. Jegers +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt LE 4 i386 +.Os +.Sh NAME +.Nm le +.Nd AMD LANCE Ethernet device +.Sh SYNOPSIS +.Cd "le0 at isa? port 0x360 irq 15 drq 6" +.Cd "le* at isapnp?" +.Sh DESCRIPTION +The +.Nm +interface provides access to a 10 Mb/s Ethernet network via the +AMD LANCE Ethernet chips. +This includes the following models: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It AT&T StarLAN 10, EN100, and StarLAN Fiber +.It BICC Isolan +.It BOCALANcard +.It Digital DEPCA +.It Kingston 21xx +.It Novell NE1500T +.It Novell NE2100 +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr isapnp 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/man4.i386/lms.4 b/static/openbsd/man4/man4.i386/lms.4 new file mode 100644 index 00000000..e3fdd59b --- /dev/null +++ b/static/openbsd/man4/man4.i386/lms.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: lms.4,v 1.11 2010/09/26 20:39:08 miod Exp $ +.\" $NetBSD: lms.4,v 1.13 2000/07/05 16:13:48 msaitoh Exp $ +.\" +.\" Copyright (c) 1993 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed for the +.\" NetBSD Project. See http://www.netbsd.org/ for +.\" information about NetBSD. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" <> +.\" +.Dd $Mdocdate: September 26 2010 $ +.Dt LMS 4 i386 +.Os +.Sh NAME +.Nm lms +.Nd Logitech-style bus mouse driver +.Sh SYNOPSIS +.Cd "lms0 at isa? port 0x23c irq 5" +.Cd "lms1 at isa? port 0x238 irq 5" +.Cd "wsmouse* at lms? mux 0" +.Sh DESCRIPTION +This driver provides an interface to a Logitech-style bus mouse. +Mouse related data are accessed by +.Xr wsmouse 4 +devices. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr mms 4 , +.Xr pms 4 , +.Xr ums 4 , +.Xr wsmouse 4 diff --git a/static/openbsd/man4/man4.i386/mem.4 b/static/openbsd/man4/man4.i386/mem.4 new file mode 100644 index 00000000..9b31ab72 --- /dev/null +++ b/static/openbsd/man4/man4.i386/mem.4 @@ -0,0 +1,87 @@ +.\" $OpenBSD: mem.4,v 1.13 2024/03/22 12:29:33 jsg Exp $ +.\" +.\" Copyright (c) 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)mem.4 5.3 (Berkeley) 5/2/91 +.\" +.Dd $Mdocdate: March 22 2024 $ +.Dt MEM 4 i386 +.Os +.Sh NAME +.Nm mem , +.Nm kmem +.Nd memory files +.Sh DESCRIPTION +The special file +.Pa /dev/mem +is an interface to the physical memory of the computer. +Byte offsets in this file are interpreted as physical memory addresses. +Reading and writing this file is equivalent to reading and writing +memory itself. +Only offsets within the bounds of +.Pa /dev/mem +are allowed. +.Pp +Kernel virtual memory is accessed through the interface +.Pa /dev/kmem +in the same manner as +.Pa /dev/mem . +Only kernel virtual addresses that are currently mapped to memory are allowed. +.Pp +On ISA the I/O memory space begins at physical address +.Li 0x000a0000 +and runs to +.Li 0x00100000 . +The per-process data size for the current process is +.Dv UPAGES +long, and ends at virtual address +.Li 0xfe000000 . +.Pp +Even with sufficient file system permissions, +these devices can only be opened when the +.Xr securelevel 7 +is insecure or when the +.Va kern.allowkmem +.Xr sysctl 2 +variable is set. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/mem +.It Pa /dev/kmem +.El +.Sh SEE ALSO +.Xr mtrr 4 , +.Xr securelevel 7 +.Sh HISTORY +The +.Pa /dev/mem +file appeared in +.At v1 , +.Pa /dev/kmem +appeared in +.At v5 . diff --git a/static/openbsd/man4/man4.i386/mms.4 b/static/openbsd/man4/man4.i386/mms.4 new file mode 100644 index 00000000..5389a996 --- /dev/null +++ b/static/openbsd/man4/man4.i386/mms.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: mms.4,v 1.10 2010/09/26 20:39:08 miod Exp $ +.\" $NetBSD: mms.4,v 1.13 2000/07/05 16:13:49 msaitoh Exp $ +.\" +.\" Copyright (c) 1993 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed for the +.\" NetBSD Project. See http://www.netbsd.org/ for +.\" information about NetBSD. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" <> +.\" +.Dd $Mdocdate: September 26 2010 $ +.Dt MMS 4 i386 +.Os +.Sh NAME +.Nm mms +.Nd Microsoft-style bus mouse driver +.Sh SYNOPSIS +.Cd "mms0 at isa? port 0x23c irq 5" +.Cd "mms1 at isa? port 0x238 irq 5" +.Cd "wsmouse* at mms? mux 0" +.Sh DESCRIPTION +This driver provides an interface to a Microsoft-style bus mouse. +Mouse related data are accessed by +.Xr wsmouse 4 +devices. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr lms 4 , +.Xr pms 4 , +.Xr ums 4 , +.Xr wsmouse 4 diff --git a/static/openbsd/man4/man4.i386/mpbios.4 b/static/openbsd/man4/man4.i386/mpbios.4 new file mode 100644 index 00000000..6d16c2d2 --- /dev/null +++ b/static/openbsd/man4/man4.i386/mpbios.4 @@ -0,0 +1,59 @@ +.\" $OpenBSD: mpbios.4,v 1.1 2009/01/13 13:55:03 kettenis Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 13 2009 $ +.Dt MPBIOS 4 i386 +.Os +.Sh NAME +.Nm mpbios +.Nd MP BIOS +.Sh SYNOPSIS +.Cd "mpbios0 at bios0" +.Sh DESCRIPTION +The +.Nm +driver extracts configuration information from the BIOS on +multiprocessor systems that conform to the Intel MultiProcessor +Specification. +This information is used to attach application processors and APICs, +and to assign interrupts to ISA, EISA and PCI devices. +.Pp +On modern systems this information is provided by ACPI through the +.Xr acpimadt 4 +device. +On such a system +.Nm +will not attach, even if the BIOS also contains the data structures +specified by the Intel MP Specification. +.Pp +The +.Nm +driver supports version 1.1 and 1.4 of the Intel MP Specification. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr acpimadt 4 , +.Xr bios 4 , +.Xr cpu 4 , +.Xr intro 4 , +.Xr ioapic 4 , +.Xr pcibios 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.5 , +based on code present since +.Ox 3.6 . diff --git a/static/openbsd/man4/man4.i386/mtrr.4 b/static/openbsd/man4/man4.i386/mtrr.4 new file mode 100644 index 00000000..6636011e --- /dev/null +++ b/static/openbsd/man4/man4.i386/mtrr.4 @@ -0,0 +1,147 @@ +.\" $OpenBSD: mtrr.4,v 1.17 2014/02/15 23:41:19 schwarze Exp $ +.\" +.\" Pentium MTRR driver for OpenBSD. +.\" Copyright 1999 Matthieu Herrb +.\" +.\" Modification and redistribution in source and binary forms is +.\" permitted provided that due credit is given to the author and the +.\" OpenBSD project (for instance by leaving this copyright notice +.\" intact). +.\" +.Dd $Mdocdate: February 15 2014 $ +.Dt MTRR 4 i386 +.Os +.Sh NAME +.Nm mtrr +.Nd driver for CPU memory range attributes +.Sh SYNOPSIS +.Cd "pseudo-device mtrr 1" +.Sh DESCRIPTION +The +.Nm +device provides access to the memory range attributes supported by the +MTRRs on Pentiums. +.Ss IOCTL INTERFACE +Several architectures allow attributes to be associated with ranges of physical +memory. +These attributes can be manipulated via +.Fn ioctl +calls performed on +.Pa /dev/mem +or +.Pa /dev/xf86 . +Declarations and data types are to be found in +.In sys/memrange.h . +.Pp +The specific attributes, and number of programmable ranges may vary between +architectures. +The full set of supported attributes is: +.Bl -tag -width MDF_WRITECOMBINE +.It Dv MDF_UNCACHEABLE +The region is not cached. +.It Dv MDF_WRITECOMBINE +Writes to the region may be combined or performed out of order. +.It Dv MDF_WRITETHROUGH +Writes to the region are committed synchronously. +.It Dv MDF_WRITEBACK +Writes to the region are committed asynchronously. +.It Dv MDF_WRITEPROTECT +The region cannot be written to. +.El +.Pp +Memory ranges are described by +.Bd -literal -offset xxxx +struct mem_range_desc { + u_int64_t mr_base; /\(** physical base address \(**/ + u_int64_t mr_len; /\(** physical length of region \(**/ + int mr_flags; /\(** attributes of region \(**/ + char mr_owner[8]; +}; +.Ed +.Pp +In addition to the region attributes listed above, the following flags +may also be set in the +.Fa mr_flags +field: +.Bl -tag -width MDF_FIXACTIVE +.It Dv MDF_FIXBASE +The region's base address cannot be changed. +.It Dv MDF_FIXLEN +The region's length cannot be changed. +.It Dv MDF_FIRMWARE +The region is believed to have been established by the system firmware. +.It Dv MDF_ACTIVE +The region is currently active. +.It Dv MDF_BOGUS +We believe the region to be invalid or otherwise erroneous. +.It Dv MDF_FIXACTIVE +The region cannot be disabled. +.El +.Pp +Operations are performed using +.Bd -literal -offset xxxx +struct mem_range_op { + struct mem_range_desc *mo_desc; + int mo_arg[2]; +}; +.Ed +.Pp +The +.Fa MEMRANGE_GET +ioctl is used to retrieve current memory range attributes. +If +.Fa mo_arg[0] +is set to 0, it will be updated with the total number of memory range +descriptors. +If greater than 0, the array at +.Fa mo_desc +will be filled with a corresponding number of descriptor structures, +or the maximum, whichever is less. +.Pp +The +.Fa MEMRANGE_SET +ioctl is used to add, alter and remove memory range attributes. +A range with the +.Dv MDF_FIXACTIVE +flag may not be removed. +.Pp +.Fa mo_arg[0] +should be set to MEMRANGE_SET_UPDATE to update an existing +or establish a new range, or to MEMRANGE_SET_REMOVE to remove a range. +.Sh ERRORS +On +.Xr ioctl 2 +failure, +.Xr errno 2 +will be set as follows: +.Bl -tag -width Er +.It Bq Er EOPNOTSUPP +Memory range operations are not supported on this architecture. +.It Bq Er ENXIO +No memory range descriptors are available (e.g., firmware has not enabled +any). +.It Bq Er EINVAL +The memory range supplied as an argument is invalid or overlaps another +range in a fashion not supported by this architecture. +.It Bq Er EBUSY +An attempt to remove or update a range failed because the range is busy. +.It Bq Er ENOSPC +An attempt to create a new range failed due to a shortage of hardware +resources (e.g., descriptor slots). +.It Bq Er ENOENT +An attempt to remove a range failed because no range matches the descriptor +base/length supplied. +.It Bq Er EPERM +An attempt to remove a range failed because the range is permanently +enabled. +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr mem 4 , +.Xr pctr 4 , +.Xr xf86 4 , +.Xr memconfig 8 +.Sh HISTORY +.Nm +support was originally included in +.Fx 3.3 . diff --git a/static/openbsd/man4/man4.i386/npx.4 b/static/openbsd/man4/man4.i386/npx.4 new file mode 100644 index 00000000..2a3e6065 --- /dev/null +++ b/static/openbsd/man4/man4.i386/npx.4 @@ -0,0 +1,63 @@ +.\" $OpenBSD: npx.4,v 1.15 2007/06/20 14:11:33 jmc Exp $ +.\" +.\" Copyright (c) 1993 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christopher G. Demetriou. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 20 2007 $ +.Dt NPX 4 i386 +.Os +.Sh NAME +.Nm npx +.Nd Numeric Processing Extension coprocessor and emulator +.Sh SYNOPSIS +.\" XXX this is awful hackery to get it to work right... -- cgd +.Cd "npx0 at isa? port" \&"IO_NPX0\&" irq 13 +.Sh DESCRIPTION +The +.Nm +driver enables the use of the system's Numeric Processing Extension +coprocessor, +if one is present. +Numeric processing extensions are present in systems with +.Tn 486DX +CPUs and in systems with +.Tn 387 +or +.Tn 487SX +coprocessors. +The +.Nm +driver is required for proper system functioning regardless +of whether or not an NPX is present. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 +.Sh BUGS +There are lots of them, especially on cheap motherboards. +In particular, some motherboards do not have the interrupt lines from the NPX +to the CPU wired properly. diff --git a/static/openbsd/man4/man4.i386/nvram.4 b/static/openbsd/man4/man4.i386/nvram.4 new file mode 100644 index 00000000..8980e17e --- /dev/null +++ b/static/openbsd/man4/man4.i386/nvram.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: nvram.4,v 1.4 2007/05/31 19:19:55 jmc Exp $ +.\" +.\" Copyright 2004 Joshua Stein +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt NVRAM 4 i386 +.Os +.Sh NAME +.Nm nvram +.Nd driver for reading PC NVRAM contents +.Sh SYNOPSIS +.Cd "pseudo-device nvram 1" +.Sh DESCRIPTION +The +.Nm +device provides read-only access to the non-volatile memory contained in the +MC146818 real-time clock. +.Pp +This data is provided as a seekable character device, +.Pa /dev/nvram . +Checksums of the NVRAM contents are calculated over bytes 2 to 31 and stored +in byte 32. +A valid checksum is required for the driver to initialize. +.Sh FILES +.Bl -tag -width /dev/nvram +.It Pa /dev/nvram +.El +.Sh HISTORY +.Nm +support was originally included in +.Ox 3.7 . diff --git a/static/openbsd/man4/man4.i386/pas.4 b/static/openbsd/man4/man4.i386/pas.4 new file mode 100644 index 00000000..1f8b90d0 --- /dev/null +++ b/static/openbsd/man4/man4.i386/pas.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: pas.4,v 1.2 2007/05/31 19:19:55 jmc Exp $ +.\" +.\" Copyright (c) 2006 JASON MCINTYRE +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt PAS 4 i386 +.Os +.Sh NAME +.Nm pas +.Nd Media Vision Pro AudioSpectrum audio device +.Sh SYNOPSIS +.Cd "pas0 at isa? port 0x220 irq 7 drq 1" +.Cd "audio* at pas?" +.Sh DESCRIPTION +The +.Nm +driver provides support for second generation +Media Vision Pro AudioSpectrum +sound cards. +These cards contain an MVD101 multimedia chip. +.Pp +The following cards are supported: +.Bd -literal -offset indent +CDPC +Fusion CD +Fusion CD 16 +PAS 16 +PAS Plus +.Ed +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 , +.Xr isa 4 diff --git a/static/openbsd/man4/man4.i386/pcibios.4 b/static/openbsd/man4/man4.i386/pcibios.4 new file mode 100644 index 00000000..493bd358 --- /dev/null +++ b/static/openbsd/man4/man4.i386/pcibios.4 @@ -0,0 +1,180 @@ +.\" $OpenBSD: pcibios.4,v 1.26 2024/06/22 12:38:32 deraadt Exp $ +.\" $NetBSD: pcibios.4,v 1.7 2000/08/03 13:32:39 soda Exp $ +.\" +.\" Copyright (c) 2000 Michael Shalayeff, All rights reserved. +.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 22 2024 $ +.Dt PCIBIOS 4 i386 +.Os +.Sh NAME +.Nm pcibios +.Nd introduction to PCI BIOS support +.Sh SYNOPSIS +.Cd "pcibios0 at bios0 flags 0x0000" +.\" .Cd "#option PCIBIOS_IRQS_HINT=0x0a00 #IRQ 9,11" +.\" .Cd "#option PCIBIOS_INTR_FIXUP_FORCE" +.Sh DESCRIPTION +.Ox +provides support for setting up PCI controllers, bridges, and devices +using information extracted from the BIOS. +.Pp +Ideally, the boot firmware of a machine (a.k.a. BIOS) should set +up all PCI devices; assigning them I/O and memory addresses and +interrupts. +Alas, this does not always happen, so there is some +PC specific code that can do the initialization when +.Ox +boots. +.Pp +Flags is a bit mask each bit of which specifies a fixup procedure to +omit. +The following list specifies these procedures and gives +flags bit values to disable them in case they cause problems. +.Bl -tag -width 0x0000 +.It 0x0001 +Fixup PCI I/O and memory addresses. +.Pp +Some BIOS implementations don't allocate I/O space and +memory space for all PCI devices. +Especially, a BIOS which has +.Qq PnP OS mode +enabled shows this behavior. +Since necessary space isn't allocated, those devices +will not work without special handling. +.Pp +Without this flag force allocation of I/O space and memory space +instead of relying upon the BIOS to do so. +.Pp +If necessary space is already correctly assigned to the devices, +this option leaves the space as is. +.Pp +Although many BIOS implementations leave CardBus bridges' +space unallocated, the CardBus bridge device driver doesn't +require this option, since the driver allocates necessary space +by itself. +.It 0x0002 +Fixup PCI bus numbering; needed for many +.Xr cardbus 4 +bridges. +.Pp +Each PCI bus and CardBus should have a unique bus number. +But some BIOS implementations don't assign a bus number +for subordinate PCI buses. +And many BIOS implementations don't assign a bus number for CardBuses. +.Pp +A typical symptom of this is the following boot message: +.D1 Sy cardbus0 at cardslot0: bus 0 device 0... +This cardbus0 has a bus number +.Sq 0 , +but normally the bus number 0 is used by the machine's +primary PCI bus. +Thus, this bus number for cardbus is incorrect +.Pq not assigned . +In this situation, a device located in cardbus0 doesn't +show correct device ID, +because its bus number 0 incorrectly refers to the primary +PCI bus, and a device ID in the primary PCI bus is shown +in the boot message instead of the device's ID in the cardbus0. +.Pp +Without this flag force assignment of bus numbers for all subordinate +PCI buses and CardBuses. +.Pp +Since this procedure renumbers all PCI buses and CardBuses, +all bus numbers of subordinate buses become different +when this option is enabled. +.It 0x0004 +Fixup PCI interrupt routing. +.Pp +Some BIOS implementations don't assign an interrupt for +some devices. +.Pp +This procedure assigns an interrupt for such devices instead +of relying upon the BIOS to do so. +.Pp +If the BIOS has already assigned an interrupt to a device, this +procedure leaves the interrupt as is. +.It 0x0008 +Make PCI interrupt routing fixup work with unknown interrupt routers. +If this flag is specified and a PCI interrupt routing table entry +indicates that only one IRQ is available for the entry, the IRQ is +assumed to be already connected to the device, and the corresponding PCI +Interrupt Configuration Register will be configured accordingly. +.Pp +Without this flag, if a PCI interrupt router is not known, interrupt +configuration will not be modified. +.It 0x0010 +Be verbose when performing +.Nm +tasks. +Included in these diagnostics are: PCI device address fixup tables, +interrupt fixup reports, and other diagnostic and non-fatal messages. +.It 0x0020 +Make the PCI interrupt routing fixup procedure verbose. +.It 0x0040 +Some buggy BIOS implementations provide inconsistent information between +the PCI Interrupt Configuration Register and the PCI Interrupt Routing table. +In such cases, the PCI Interrupt Configuration Register takes precedence +by default. +If this flag is specified, the PCI Interrupt Routing table takes precedence. +.El +.Sh SEE ALSO +.Xr bios 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr pci_conf_read 9 , +.Xr pci_intr_map 9 +.Sh HISTORY +The +.Nm +code appeared in +.Nx 1.5 . +.Ox +support was added in +.Ox 2.8 . +In contrast to +.Nx +implementation +.Nm +in +.Ox +is a real device, where options control is done through the +.Nm flags +which are modifiable through the +.Xr boot_config 8 +interface. +For +.Ox 2.9 +the PCI interrupt routing establishment sequence was redone to only +fixup and route interrupts when attaching interrupts for a particular PCI +device. +.Sh BUGS +The +.Em PCIBIOS Address Fixup +option may conflict with the PCI CardBus driver's own +address fixup. diff --git a/static/openbsd/man4/man4.i386/pctr.4 b/static/openbsd/man4/man4.i386/pctr.4 new file mode 100644 index 00000000..eaa3fafd --- /dev/null +++ b/static/openbsd/man4/man4.i386/pctr.4 @@ -0,0 +1,281 @@ +.\" $OpenBSD: pctr.4,v 1.30 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Pentium performance counter driver for OpenBSD. +.\" Copyright 1996 David Mazieres . +.\" +.\" Modification and redistribution in source and binary forms is +.\" permitted provided that due credit is given to the author and the +.\" OpenBSD project by leaving this copyright notice intact. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PCTR 4 i386 +.Os +.Sh NAME +.Nm pctr +.Nd driver for CPU performance counters +.Sh SYNOPSIS +.Cd "pseudo-device pctr 1" +.Sh DESCRIPTION +The +.Nm +device provides access to the performance counters on AMD and Intel brand +processors, and to the TSC on others. +.Pp +Intel processors have two 40-bit performance counters which can be +programmed to count events such as cache misses, branch target buffer hits, +TLB misses, dual-issues, interrupts, pipeline flushes, and more. +While AMD processors have four 48-bit counters, their precision is decreased +to 40 bits. +.Pp +There is one +.Em ioctl +call to read the status of all counters, and one +.Em ioctl +call to program the function of each counter. +All require the following includes: +.Bd -literal -offset indent +#include +#include +#include +.Ed +.Pp +The current state of all counters can be read with the +.Dv PCIOCRD +.Em ioctl , +which takes an argument of type +.Dv "struct pctrst" : +.Bd -literal -offset indent +#define PCTR_NUM 4 +struct pctrst { + u_int pctr_fn[PCTR_NUM]; + pctrval pctr_tsc; + pctrval pctr_hwc[PCTR_NUM]; +}; +.Ed +.Pp +In this structure, +.Em ctr_fn +contains the functions of the counters, as previously set by the +.Dv PCIOCS0 , +.Dv PCIOCS1 , +.Dv PCIOCS2 +and +.Dv PCIOCS3 +ioctls (see below). +.Em pctr_hwc +contains the actual value of the hardware counters. +.Em pctr_tsc +is a free-running, 64-bit cycle counter. +.Pp +The functions of the counters can be programmed with ioctls +.Dv PCIOCS0 , +.Dv PCIOCS1 , +.Dv PCIOCS2 +and +.Dv PCIOCS3 +which require a writeable file descriptor and take an argument of type +.Dv "unsigned int" . \& +The meaning of this integer is dependent on the particular CPU. +.Ss Time stamp counter +The time stamp counter is available on most of the AMD K6, Intel Pentium +and higher class CPUs, as well as on some 486s and non-intel CPUs. +It is set to zero at boot time, and then increments with each cycle. +Because the counter is 64-bits wide, it does not overflow. +.Pp +The time stamp counter can be read directly from user-mode using +the +.Fn rdtsc +macro, which returns a 64-bit value of type +.Em pctrval . +The following example illustrates a simple use of +.Fn rdtsc +to measure the execution time of a hypothetical subroutine called +.Fn functionx : +.Bd -literal -offset indent +void +time_functionx(void) +{ + pctrval tsc; + + tsc = rdtsc(); + functionx(); + tsc = rdtsc() - tsc; + printf("Functionx took %llu cycles.\en", tsc); +} +.Ed +.Pp +The value of the time stamp counter is also returned by the +.Dv PCIOCRD +.Em ioctl , +so that one can get an exact timestamp on readings of the hardware +event counters. +.Ss Intel Pentium counters +The Intel Pentium counters are programmed with a 9 bit function. +The top three bits contain the following flags: +.Bl -tag -width P5CTR_C +.It Dv P5CTR_K +Enables counting of events that occur in kernel mode. +.It Dv P5CTR_U +Enables counting of events that occur in user mode. +You must set at least one of +.Dv P5CTR_U +and +.Dv P5CTR_K +to count anything. +.It Dv P5CTR_C +When this flag is set, the counter attempts to count the number of +cycles spent servicing a particular event, rather than simply the +number of occurrences of that event. +.El +.Pp +The bottom 6 bits set the particular event counted. +A list of possible event functions could be obtained by running a +.Xr pctr 1 +command with +.Fl l +option. +.Ss "Counters for AMD K6, Intel Pentium Pro and newer CPUs" +Unlike the Pentium counters, these counters can be read +directly from user-mode without need to invoke the kernel. +The macro +.Fn rdpmc ctr +takes 0, 1, 2 or 3 as an argument to specify a counter, and returns that +counter's 40-bit value (which will be of type +.Em pctrval ) . +This is generally preferable to making a system call as it introduces +less distortion in measurements. +.Pp +Counter functions supported by these CPUs contain several parts. +The most significant byte (an 8-bit integer shifted left by +.Dv PCTR_CM_SHIFT ) +contains a +.Em "counter mask" . +If non-zero, this sets a threshold for the number of times an event +must occur in one cycle for the counter to be incremented. +The +.Em "counter mask" +can therefore be used to count cycles in which an event +occurs at least some number of times. +The next byte contains several flags: +.Bl -tag -width PCTR_EN +.It Dv PCTR_U +Enables counting of events that occur in user mode. +.It Dv PCTR_K +Enables counting of events that occur in kernel mode. +You must set at least one of +.Dv PCTR_K +and +.Dv PCTR_U +to count anything. +.It Dv PCTR_E +Counts edges rather than cycles. +For some functions this allows you +to get an estimate of the number of events rather than the number of +cycles occupied by those events. +.It Dv PCTR_EN +Enable counters. +This bit must be set in the function for counter 0 +in order for either of the counters to be enabled. +This bit should probably be set in counter 1 as well. +.It Dv PCTR_I +Inverts the sense of the +.Em "counter mask" . \& +When this bit is set, the counter only increments on cycles in which +there are no +.Em more +events than specified in the +.Em "counter mask" . +.El +.Pp +The next byte (shifted left by the +.Dv PCTR_UM_SHIFT ) +contains flags specific to the event being counted, also known as the +.Em "unit mask" . +.Pp +For events dealing with the L2 cache, the following flags are valid +on Intel brand processors: +.Bl -tag -width PCTR_UM_M +.It Dv PCTR_UM_M +Count events involving modified cache coherency state lines. +.It Dv PCTR_UM_E +Count events involving exclusive cache coherency state lines. +.It Dv PCTR_UM_S +Count events involving shared cache coherency state lines. +.It Dv PCTR_UM_I +Count events involving invalid cache coherency state lines. +.El +.Pp +To measure all L2 cache activity, all these bits should be set. +They can be set with the macro +.Dv PCTR_UM_MESI +which contains the bitwise or of all of the above. +.Pp +For event types dealing with bus transactions, there is another flag +that can be set in the +.Em "unit mask" : +.Bl -tag -width PCTR_UM_A +.It Dv PCTR_UM_A +Count all appropriate bus events, not just those initiated by the +processor. +.El +.Pp +Events marked +.Em (MESI) +require the +.Dv PCTR_UM_[MESI] +bits in the +.Em "unit mask" . \& +Events marked +.Em (A) +can take the +.Dv PCTR_UM_A +bit. +.Pp +Finally, the least significant byte of the counter function is the +event type to count. +A list of possible event functions could be obtained by running a +.Xr pctr 1 +command with +.Fl l +option. +.Sh FILES +.Bl -tag -width /dev/pctr -compact +.It Pa /dev/pctr +.El +.Sh ERRORS +.Bl -tag -width "[ENODEV]" +.It Bq Er ENODEV +An attempt was made to set the counter functions on a CPU that does +not support counters. +.It Bq Er EINVAL +An invalid counter function was provided as an argument to the +.Dv PCIOCSx +.Em ioctl . +.It Bq Er EPERM +An attempt was made to set the counter functions, but the device was +not open for writing. +.El +.Sh SEE ALSO +.Xr pctr 1 , +.Xr ioctl 2 +.Sh HISTORY +A +.Nm +device first appeared in +.Ox 2.0 +but was subsequently extended to support AMD and newer Intel CPUs in +.Ox 4.3 . +.Sh AUTHORS +The +.Nm +device was written by +.An David Mazieres Aq Mt dm@lcs.mit.edu . +.Sh BUGS +Not all counter functions are completely accurate. +Some of the functions may not make any sense at all. +Also you should be aware of the possibility of an interrupt between +invocations of +.Fn rdpmc +and/or +.Fn rdtsc +that can potentially decrease the accuracy of measurements. diff --git a/static/openbsd/man4/man4.i386/sb.4 b/static/openbsd/man4/man4.i386/sb.4 new file mode 100644 index 00000000..d7131957 --- /dev/null +++ b/static/openbsd/man4/man4.i386/sb.4 @@ -0,0 +1,96 @@ +.\" $OpenBSD: sb.4,v 1.16 2016/08/31 13:54:58 jmc Exp $ +.\" $NetBSD: sb.4,v 1.13 1997/10/31 15:02:33 augustss Exp $ +.\" +.\" Copyright (c) 1996 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by John T. Kohl. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE +.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 31 2016 $ +.Dt SB 4 i386 +.Os +.Sh NAME +.Nm sb +.Nd SoundBlaster family audio device +.Sh SYNOPSIS +.Cd "sb0 at isa? port 0x220 irq 5 drq 1" +.Cd "sb1 at isa? port 0x240 irq 7 drq 1 flags 1" +.Cd "sb* at isapnp?" +.Cd "audio* at sb?" +.Cd "midi* at sb?" Pq "MPU401 port" +.Sh DESCRIPTION +The +.Nm +driver supports the +SoundBlaster 16, Jazz 16, SoundBlaster AWE 32, SoundBlaster AWE 64, +and hardware register-level compatible audio cards. +.Pp +The SoundBlaster series are half-duplex cards, capable of 8- and 16-bit +audio sample recording and playback at rates up to 44.1kHz (depending on +the particular model). +.Pp +The base I/O port address is usually jumper-selected to either 0x220 or +0x240 (newer cards may provide software configuration, but this driver +does not directly support them--you must configure the card for its I/O +addresses with other software). +The SoundBlaster takes 16 I/O ports. +For the SoundBlaster and SoundBlaster Pro, the IRQ and DRQ channels are +jumper-selected. +For the SoundBlaster 16, the IRQ and DRQ channels are set by this driver +to the values specified in the config file. +The IRQ must be selected from the set {5,7,9,10}. +.Pp +The configuration file must set the value of +.Cm flags +to 1 to enable the Jazz16 support. +This is to avoid potential conflicts with other devices when probing the +Jazz 16 because it requires use of extra I/O ports not in the base port range. +.Pp +The joystick interface (if enabled by a jumper) is handled by the +.Xr joy 4 +driver, and the optional SCSI CD-ROM interface is handled by the +.Xr aic 4 +driver. +.Sh SEE ALSO +.Xr aic 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr isapnp 4 , +.Xr joy 4 , +.Xr midi 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Nx 1.0 . +.Sh BUGS +With a SoundBlaster 16 card the device is full duplex, but it can +only sensibly handle a precision of 8 bits. +It does so by extending +the output 8 bit samples to 16 bits and using the 8 bit DMA channel +for input and the 16 bit channel for output. +.Pp +The non-SCSI CD-ROM interfaces found on some older cards are not supported. diff --git a/static/openbsd/man4/man4.i386/skgpio.4 b/static/openbsd/man4/man4.i386/skgpio.4 new file mode 100644 index 00000000..b175ae9c --- /dev/null +++ b/static/openbsd/man4/man4.i386/skgpio.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: skgpio.4,v 1.2 2015/10/22 11:01:14 sobrado Exp $ +.\" +.\" Copyright (c) 2014 Matt Dainty +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 22 2015 $ +.Dt SKGPIO 4 i386 +.Os +.Sh NAME +.Nm skgpio +.Nd Soekris net6501 GPIO and LEDs +.Sh SYNOPSIS +.Cd "skgpio0 at isa? port 0x680" +.Cd "gpio* at skgpio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO and LEDs as implemented by the Xilinx +Spartan FGPA integrated into the Soekris net6501 programmed with the default +bitstream found in the BIOS. +.Pp +Two standard +.Xr gpio 4 +interfaces are provided, one for the 16 real pins which can be configured as +either inputs or outputs and another with 2 output-only pins that map +to the error and ready LEDs respectively. +Both may be used with +.Xr gpioctl 8 . +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Matt Dainty Aq matt@bodgit-n-scarper.com . +.Sh BUGS +If the Xilinx FPGA is programmed with a different bitstream, the driver will +likely not function. diff --git a/static/openbsd/man4/man4.i386/tcpcib.4 b/static/openbsd/man4/man4.i386/tcpcib.4 new file mode 100644 index 00000000..21331b61 --- /dev/null +++ b/static/openbsd/man4/man4.i386/tcpcib.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: tcpcib.4,v 1.6 2014/11/15 14:41:02 bentley Exp $ +.\" +.\" Copyright (c) 2012 Matt Dainty +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 15 2014 $ +.Dt TCPCIB 4 i386 +.Os +.Sh NAME +.Nm tcpcib +.Nd Intel Atom E600 series LPC bridge, timecounter and watchdog timer +.Sh SYNOPSIS +.Cd "tcpcib* at pci?" +.Cd "isa* at tcpcib?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Intel Atom E600 series LPC bridge and +implements a 64-bit 14.3 MHz timecounter using the HPET timer. +.Pp +The +.Nm +driver also provides the standard +.Xr watchdog 4 +interface to the watchdog timer and may be used with +.Xr watchdogd 8 . +The watchdog timer can be configured via +.Xr sysctl 8 . +.Pp +Once the watchdog timer resets the CPU, the driver reports it on the +next boot displaying the +.Dq reboot on timeout +message in the +.Xr dmesg 8 . +.Pp +The maximum timeout value supported by the watchdog timer is 600 +seconds. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 , +.Xr watchdog 4 , +.Xr sysctl 8 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Matt Dainty Aq Mt matt@bodgit-n-scarper.com . +.Sh BUGS +Apart from the core +.Xr pcib 4 +functionality, timecounter and the +.Xr watchdog 4 +interface, the driver doesn't support any other aspects of the hardware. diff --git a/static/openbsd/man4/man4.i386/uha.4 b/static/openbsd/man4/man4.i386/uha.4 new file mode 100644 index 00000000..201721dc --- /dev/null +++ b/static/openbsd/man4/man4.i386/uha.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: uha.4,v 1.14 2012/08/14 01:08:19 dlg Exp $ +.\" +.\" Copyright (c) 1994 James A. Jegers +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: August 14 2012 $ +.Dt UHA 4 i386 +.Os +.Sh NAME +.Nm uha +.Nd Ultrastor SCSI interface +.Sh SYNOPSIS +.Cd "uha0 at isa? port 0x330" +.Cd "uha1 at isa? port 0x334" +.Cd "uha* at eisa?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the following SCSI adapters: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Ultrastor 14f +.It Ultrastor 24f +.It Ultrastor 34f +.El +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr eisa 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 diff --git a/static/openbsd/man4/man4.i386/wds.4 b/static/openbsd/man4/man4.i386/wds.4 new file mode 100644 index 00000000..195e9f80 --- /dev/null +++ b/static/openbsd/man4/man4.i386/wds.4 @@ -0,0 +1,61 @@ +.\" $OpenBSD: wds.4,v 1.6 2012/08/14 01:08:19 dlg Exp $ +.\" $NetBSD: wds.4,v 1.5 2001/09/11 23:18:55 wiz Exp $ +.\" +.\" Copyright (c) 1997 Jonathan Stone +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 14 2012 $ +.Dt WDS 4 i386 +.Os +.Sh NAME +.Nm wds +.Nd WD7000 compatible ISA SCSI interface +.Sh SYNOPSIS +.Cd "wds0 at isa? port 0x350 irq 15 drq 6 # WD7000, TMC-7000" +.Cd "wds1 at isa? port 0x358 irq 11 drq 5" +.Sh DESCRIPTION +The +.Nm +driver supports the WD7000 family of +.Tn SCSI +adapters and compatibles, including: +.Pp +.Bl -tag -width xxxxxxxxxxxxx -offset xxxx -compact +.It WD7000-ASC +Busmastering DMA controller. +.It WD7000-ASE +An ASC with floppy controller and +.Tn ESDI , +manufactured for +.Tn Apollo +workstations. +.It WD7000-FASST2 +An ASC with new firmware and scatter-gather hardware. +.El +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 diff --git a/static/openbsd/man4/man4.i386/wdt.4 b/static/openbsd/man4/man4.i386/wdt.4 new file mode 100644 index 00000000..6f99c2b8 --- /dev/null +++ b/static/openbsd/man4/man4.i386/wdt.4 @@ -0,0 +1,68 @@ +.\" Copyright (c) 1998,1999 Alex Nash +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" $OpenBSD: wdt.4,v 1.15 2007/05/31 19:19:55 jmc Exp $ +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt WDT 4 i386 +.Os +.Sh NAME +.Nm wdt +.Nd ICS PCI-WDT500/501 watchdog timer device +.Sh SYNOPSIS +.Cd "wdt0 at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Industrial Computer Source +PCI-WDT500 and PCI-WDT501 boards. +.Pp +For PCI-WDT500 boards, basic watchdog timer functionality is supported. +For PCI-WDT501 boards, the onboard buzzer will sound when the watchdog +counter expires. +The sensors are not yet supported. +.Pp +If the kernel crashes, the watchdog +timer is not reset and the system will reboot (assuming a proper connection +is made between the WDT50x and motherboard). +Alternatively, the watchdog +can be reinitialized via a userland process which ensures that process +scheduling, not just kernel timeout processing, is still taking place. +See +.Xr watchdog 4 +and +.Xr watchdogd 8 +for more information. +.Pp +The timer can be configured to have a timeout from 2 to 1800 seconds. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr watchdog 4 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.6 . diff --git a/static/openbsd/man4/man4.landisk/Makefile b/static/openbsd/man4/man4.landisk/Makefile new file mode 100644 index 00000000..049c0dbf --- /dev/null +++ b/static/openbsd/man4/man4.landisk/Makefile @@ -0,0 +1,8 @@ +MAN = intro.4 \ + mem.4 \ + obio.4 \ + power.4 \ + shpcic.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.landisk/intro.4 b/static/openbsd/man4/man4.landisk/intro.4 new file mode 100644 index 00000000..3b5077b2 --- /dev/null +++ b/static/openbsd/man4/man4.landisk/intro.4 @@ -0,0 +1,139 @@ +.\" $OpenBSD: intro.4,v 1.8 2022/03/31 17:27:22 naddy Exp $ +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt INTRO 4 landisk +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the landisk platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +A list of the supported devices is given below. +.Sh LIST OF DEVICES +The devices listed below are supported in this incarnation of +the system. +Pseudo-devices are not listed. +.\" Devices are indicated by their functional interface. +Not all supported devices are listed. +.Pp +.Bl -tag -width lotsofletters -compact -offset indent +.It Xr cd 4 +ATAPI and SCSI CD-ROM driver +.It Xr obio 4 +landisk onboard I/O bus device +.It Xr pciide 4 +PCI IDE controller driver +.It Xr power 4 +power switch +.\" cpu +.\" rsclock +.It Xr sd 4 +SCSI disk driver +.\" shb +.\" scif +.It Xr shpcic 4 +landisk SuperH PCI-Host Bridge +.It Xr wd 4 +WD100x compatible hard disk driver +.It Xr wdc 4 +WD100x compatible hard disk controller driver +.El +.Pp +A further list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width "cardbus(4)XX" -offset 3n -compact +.It Xr onewire 4 +1-Wire bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr usb 4 +introduction to Universal Serial Bus support +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The +landisk +.Nm intro +first appeared in +.Ox 4.1 . diff --git a/static/openbsd/man4/man4.landisk/mem.4 b/static/openbsd/man4/man4.landisk/mem.4 new file mode 100644 index 00000000..b87f1930 --- /dev/null +++ b/static/openbsd/man4/man4.landisk/mem.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: mem.4,v 1.5 2024/03/22 12:29:33 jsg Exp $ +.\" +.\" Copyright (c) 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)mem.4 5.3 (Berkeley) 5/2/91 +.\" +.Dd $Mdocdate: March 22 2024 $ +.Dt MEM 4 landisk +.Os +.Sh NAME +.Nm mem , +.Nm kmem +.Nd memory files +.Sh DESCRIPTION +The special file +.Pa /dev/mem +is an interface to the physical memory of the computer. +Byte offsets in this file are interpreted as physical memory addresses. +Reading and writing this file is equivalent to reading and writing +memory itself. +Only offsets within the bounds of +.Pa /dev/mem +are allowed. +.Pp +Kernel virtual memory is accessed through the interface +.Pa /dev/kmem +in the same manner as +.Pa /dev/mem . +Only kernel virtual addresses that are currently mapped to memory are allowed. +.Pp +On landisk, physical memory is contiguous. +The kernel virtual memory begins at address +.Li 0xc0000000 . +.Pp +Even with sufficient file system permissions, +these devices can only be opened when the +.Xr securelevel 7 +is insecure or when the +.Va kern.allowkmem +.Xr sysctl 2 +variable is set. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/mem +.It Pa /dev/kmem +.El +.Sh SEE ALSO +.Xr securelevel 7 +.Sh HISTORY +The +.Pa /dev/mem +file appeared in +.At v1 , +.Pa /dev/kmem +appeared in +.At v5 . diff --git a/static/openbsd/man4/man4.landisk/obio.4 b/static/openbsd/man4/man4.landisk/obio.4 new file mode 100644 index 00000000..930d1379 --- /dev/null +++ b/static/openbsd/man4/man4.landisk/obio.4 @@ -0,0 +1,68 @@ +.\" +.\" Copyright (c) 1997 Colin Wood +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Colin Wood +.\" for the NetBSD Project. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $OpenBSD: obio.4,v 1.5 2007/05/31 19:19:55 jmc Exp $ +.\" $NetBSD: obio.4,v 1.1 1997/07/18 02:13:40 ender Exp $ +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt OBIO 4 landisk +.Os +.Sh NAME +.Nm obio +.Nd landisk onboard I/O bus device +.Sh SYNOPSIS +.Cd "obio0 at mainbus?" +.Sh DESCRIPTION +The +.Nm +interface serves as an abstraction used by the autoconfiguration +system to help find and attach devices +.Pq e.g. the disk controllers +connected to the +.Tn landisk +onboard I/O bus. +.Pp +.Ox +provides support for the following devices: +.Pp +.Bl -tag -width 12n -offset indent -compact +.It Xr power 4 +power switch +.It Xr wdc 4 +WD100x compatible hard disk controller driver +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr mainbus 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . diff --git a/static/openbsd/man4/man4.landisk/power.4 b/static/openbsd/man4/man4.landisk/power.4 new file mode 100644 index 00000000..0ee69224 --- /dev/null +++ b/static/openbsd/man4/man4.landisk/power.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: power.4,v 1.5 2011/06/24 19:47:48 naddy Exp $ +.\" +.\" +.\" Copyright (c) 2007 Martin Reindl +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 24 2011 $ +.Dt POWER 4 landisk +.Os +.Sh NAME +.Nm power +.Nd power switch +.Sh SYNOPSIS +.Cd "power0 at obio?" +.Sh DESCRIPTION +Landisk models provide an interrupt when the power switch is flipped to the +Off position. +The +.Nm +driver catches that interrupt. +If the +.Va hw.allowpowerdown +.Xr sysctl 8 +is set to 1, +.Nm power +will signal +.Xr init 8 +to do a clean shutdown. +.Sh SEE ALSO +.Xr intro 4 , +.Xr obio 4 , +.Xr init 8 , +.Xr rc.shutdown 8 , +.Xr sysctl 8 +.Sh HISTORY +Support for the +.Nm +driver first appeared in +.Ox 4.1 . diff --git a/static/openbsd/man4/man4.landisk/shpcic.4 b/static/openbsd/man4/man4.landisk/shpcic.4 new file mode 100644 index 00000000..ecf5fadb --- /dev/null +++ b/static/openbsd/man4/man4.landisk/shpcic.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: shpcic.4,v 1.3 2010/09/19 12:41:23 jmc Exp $ +.\" +.\" Copyright (c) 2004 Martin Reindl +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 19 2010 $ +.Dt SHPCIC 4 landisk +.Os +.Sh NAME +.Nm shpcic +.Nd landisk SuperH PCI-Host Bridge +.Sh SYNOPSIS +.Cd "shpcic* at mainbus?" +.Cd "pci0 at shpcic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the landisk on-board PCI bus. +This device is largely transparent and provides no user accessible entry points. +.Sh SEE ALSO +.Xr mainbus 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . diff --git a/static/openbsd/man4/man4.loongson/Makefile b/static/openbsd/man4/man4.loongson/Makefile new file mode 100644 index 00000000..bf79da1a --- /dev/null +++ b/static/openbsd/man4/man4.loongson/Makefile @@ -0,0 +1,18 @@ +MAN = apm.4 \ + autoconf.4 \ + bonito.4 \ + gdiumiic.4 \ + glxclk.4 \ + glxpcib.4 \ + htb.4 \ + intro.4 \ + leioc.4 \ + mem.4 \ + sisfb.4 \ + smfb.4 \ + stsec.4 \ + voyager.4 \ + ykbec.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.loongson/apm.4 b/static/openbsd/man4/man4.loongson/apm.4 new file mode 100644 index 00000000..80a0eafb --- /dev/null +++ b/static/openbsd/man4/man4.loongson/apm.4 @@ -0,0 +1,211 @@ +.\" $OpenBSD: apm.4,v 1.8 2023/01/30 14:43:29 jcs Exp $ +.\" +.\" Copyright (c) 1999 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.\" APM description: +.\" +.\" Copyright (c) 1998 Marco S. Hyman +.\" +.\" Permission to copy all or part of this material for any purpose is +.\" granted provided that the above copyright notice and this paragraph +.\" are duplicated in all copies. THIS SOFTWARE IS PROVIDED ``AS IS'' +.\" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT +.\" LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE. +.Dd $Mdocdate: January 30 2023 $ +.Dt APM 4 loongson +.Os +.Sh NAME +.Nm apm +.Nd advanced power management device interface +.Sh SYNOPSIS +.Cd "apm0 at mainbus0" +.Sh DESCRIPTION +The +.Nm +driver provides generic power and battery control, +relying on device specific drivers to provide the actual information. +.Pp +The +.Nm +driver provides an interface which simulates the Advanced Power Management +.Pq Tn APM +BIOS functions encountered on some x86 hardware. +The BIOS functions are translated into the appropriate microcontroller requests +by the hardware specific drivers, like +.Xr ykbec 4 . +Currently only battery level, AC connection, and charging status are available +from the +.Nm +device. +Suspend/resume and other power events are not yet supported. +.Pp +The +.Nm +driver implements the following +.Xr ioctl 2 +calls. +They are defined in +.In machine/apmvar.h . +.Bl -tag -width Ds +.\" .It Dv APM_IOC_STANDBY +.\" .Em NOT YET SUPPORTED on loongson +.\" .Pq Li "no parameters" +.\" Request +.\" .Dq standby +.\" mode. +.\" .It Dv APM_IOC_SUSPEND +.\" .Em NOT YET SUPPORTED on loongson +.\" .Pq Li "no parameters" +.\" Request +.\" .Dq suspend +.\" mode. +.\" .It Dv APM_IOC_HIBERNATE +.\" .Em NOT YET SUPPORTED on loongson +.\" .Pq Li "no parameters" +.\" Request +.\" .Dq hibernate +.\" mode. +.It Dv APM_IOC_GETPOWER +.Pq Li "struct apm_power_info" +Request the current power state. +The argument structure is as follows: +.Bd -literal -offset indent +struct apm_power_info { + u_char battery_state; + u_char ac_state; + u_char battery_life; + u_char spare1; + u_int minutes_left; + u_int spare2[6]; +}; +.Ed +.Pp +The following values are defined for +.Va battery_state : +.Bl -tag -width Ds +.It Dv APM_BATT_HIGH +Battery has a high state of charge. +.It Dv APM_BATT_LOW +Battery has a low state of charge. +.It Dv APM_BATT_CRITICAL +Battery has a critical state of charge. +.It Dv APM_BATT_CHARGING +Battery is not high, low, or critical and is currently charging. +.It Dv APM_BATT_UNKNOWN +Cannot read the current battery state. +.It Dv APM_BATTERY_ABSENT +No battery installed. +.El +.Pp +The following values are defined for +.Va ac_state : +.Bl -tag -width Ds +.It Dv APM_AC_OFF +External power not detected. +.It Dv APM_AC_ON +External power detected. +.\" .It Dv APM_AC_BACKUP +.\" Backup power in use. +.\" .It Dv APM_AC_UNKNOWN +.\" External power state unknown. +.El +.Pp +The +.Va battery_life +value contains the estimated percentage of battery life available. +100% indicates a full charge. +.Pp +The +.Va minutes_left +value contains the estimated number of minutes of battery life remaining. +.\" .It Dv APM_IOC_DEV_CTL +.\" .Em NOT YET SUPPORTED on loongson +.\" .Pq Li "struct apm_ctl" +.\" Allows an application to directly set the +.\" .Tm APM +.\" operating mode. +.\" The argument structure is as follows: +.\" .Bd -literal -offset indent +.\" struct apm_ctl { +.\" u_int dev; +.\" u_int mode; +.\" }; +.\" .Ed +.\" .Pp +.\" .Va dev +.\" indicates the device, typically +.\" .Dv APM_DEV_ALLDEVS . +.\" .Pp +.\" .Va mode +.\" indicates the desired operating mode. +.\" Possible values are +.\" .Bl -tag -compact -offset indent +.\" .It Dv APM_SYS_READY +.\" .It Dv APM_SYS_STANDBY +.\" .It Dv APM_SYS_SUSPEND +.\" .It Dv APM_SYS_OFF +.\" .It Dv APM_LASTREQ_INPROG +.\" .It Dv APM_LASTREQ_REJECTED +.\" .El +.It Dv APM_IOC_PRN_CTL +.Pq Li "int" +This +.Xr ioctl 2 +controls message output by the +.Nm +driver when a power change event is detected. +The integer parameter is one of: +.Bl -tag -width Ds +.It Dv APM_PRINT_ON +All power change events result in a message. +This is the normal operating mode for the driver. +.It Dv APM_PRINT_OFF +Power change event messages are suppressed. +.It Dv APM_PRINT_PCT +Power change event messages are suppressed unless the estimated +battery life percentage changes. +.El +.El +.Sh FILES +.Bl -tag -width /dev/apmctl +.It Pa /dev/apm +APM data device. +May only be opened read-only. +May be opened by multiple concurrent users. +.It Pa /dev/apmctl +APM control device. +May be opened read-write or write-only. +May only be opened by one user at a time. +An attempt to open the file when in use will fail, returning +.Er EBUSY . +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr ykbec 4 , +.Xr apm 8 , +.Xr apmd 8 +.Sh BUGS +Suspend and resume are not supported. diff --git a/static/openbsd/man4/man4.loongson/autoconf.4 b/static/openbsd/man4/man4.loongson/autoconf.4 new file mode 100644 index 00000000..113811db --- /dev/null +++ b/static/openbsd/man4/man4.loongson/autoconf.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: autoconf.4,v 1.1 2010/02/09 19:08:39 miod Exp $ +.\" +.\" Copyright (c) 1990, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)autoconf.4 8.1 (Berkeley) 6/9/93 +.\" +.Dd $Mdocdate: February 9 2010 $ +.Dt AUTOCONF 4 loongson +.Os +.Sh NAME +.Nm autoconf +.Nd diagnostics from the autoconfiguration code +.Sh DESCRIPTION +When +.Ox +bootstraps it probes the innards of the machine +on which it is running +and locates controllers, drives, and other devices, printing out +what it finds on the console. +This procedure is driven by a system configuration table which is processed by +.Xr config 8 +and compiled into each kernel. +Devices which exist in the machine but are not configured into the +kernel are not detected. +.Sh SEE ALSO +.Xr intro 4 , +.\" .Xr boot_loongson 8 , +.Xr config 8 diff --git a/static/openbsd/man4/man4.loongson/bonito.4 b/static/openbsd/man4/man4.loongson/bonito.4 new file mode 100644 index 00000000..b6379d2d --- /dev/null +++ b/static/openbsd/man4/man4.loongson/bonito.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: bonito.4,v 1.2 2010/02/10 08:35:31 jmc Exp $ +.\" +.\" Copyright (c) 2010 Miodrag Vallat. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 10 2010 $ +.Dt BONITO 4 loongson +.Os +.Sh NAME +.Nm bonito +.Nd memory and PCI or PCI-X controller +.Sh SYNOPSIS +.Cd "bonito0 at mainbus0" +.Cd "pci0 at bonito?" +.Sh DESCRIPTION +The +.Nm +driver supports both the Algorithmics Bonito64 memory and PCI controller +on Loongson 2E-based systems, or the onboard memory and PCI-X controller +found on Loongson 2F-based systems, which is a very close design, albeit +not compatible with the original Bonito. +.Pp +Differences between the two models of controllers are hidden at the +.Nm +driver level. +.Pp +The +.Nm +driver also handles PCI interrupt routing; on systems featuring a +.Xr glxpcib 4 +PCI-ISA bridge to which legacy devices are connected, it will also +handle legacy interrupts. +.Sh SEE ALSO +.Xr glxpcib 4 , +.Xr intro 4 , +.Xr mainbus 4 , +.Xr pci 4 diff --git a/static/openbsd/man4/man4.loongson/gdiumiic.4 b/static/openbsd/man4/man4.loongson/gdiumiic.4 new file mode 100644 index 00000000..ddab5640 --- /dev/null +++ b/static/openbsd/man4/man4.loongson/gdiumiic.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: gdiumiic.4,v 1.2 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt GDIUMIIC 4 loongson +.Os +.Sh NAME +.Nm gdiumiic +.Nd Gdium specific GPIO I2C controller +.Sh SYNOPSIS +.Cd "gdiumiic0 at gpio0 offset 6 mask 0x81" +.Cd "gdiumiic0 at gpio0 offset 46 mask 0x03" +.Cd "iic0 at gdiumiic0" +.Sh DESCRIPTION +The +.Nm +driver allows bit-banging an I2C bus as a master using two GPIO pins. +The first pin is used as a serial clock (SCL) signal and the second as +a serial data (SDA). +Both GPIO pins must be able to drive an output and the SDA pin must be +also able to read an input. +.Pp +The +.Nm +driver is derived from the +.Nm gpioiic +driver, using a different pin ordering, and knowledge of the Gdium I2C bus +configuration. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr gpioiic 4 , +.Xr iic 4 , +.Xr intro 4 +.Sh AUTHORS +.An -nosplit +The original +.Nm gpioiic +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/man4.loongson/glxclk.4 b/static/openbsd/man4/man4.loongson/glxclk.4 new file mode 100644 index 00000000..f717315d --- /dev/null +++ b/static/openbsd/man4/man4.loongson/glxclk.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: glxclk.4,v 1.9 2023/08/26 11:10:05 visa Exp $ +.\" +.\" Copyright (c) 2013 Paul Irofti. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 26 2023 $ +.Dt GLXCLK 4 loongson +.Os +.Sh NAME +.Nm glxclk +.Nd AMD Geode CS5536 multi-function general purpose timer +.Sh SYNOPSIS +.Cd "glxclk* at glxpcib?" +.Sh DESCRIPTION +The +.Nm +driver enables one of the multi-function general purpose timers found on the +Geode companion chip to be used as the system clock. +.Sh SEE ALSO +.Xr glxpcib 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Paul Irofti Aq Mt paul@irofti.net . diff --git a/static/openbsd/man4/man4.loongson/glxpcib.4 b/static/openbsd/man4/man4.loongson/glxpcib.4 new file mode 100644 index 00000000..99960a57 --- /dev/null +++ b/static/openbsd/man4/man4.loongson/glxpcib.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: glxpcib.4,v 1.7 2013/11/24 12:58:17 sthen Exp $ +.\" +.\" Michael Shalayeff, 2007. Public Domain. +.\" +.Dd $Mdocdate: November 24 2013 $ +.Dt GLXPCIB 4 loongson +.Os +.Sh NAME +.Nm glxpcib +.\" .Nd AMD CS5536 PCI-ISA bridge with timecounter, watchdog timer, and GPIO +.Nd AMD CS5536 PCI-ISA bridge with timecounter +.Sh SYNOPSIS +.Cd "glxpcib* at pci?" +.\" .Cd "gpio* at glxpcib?" +.\" .Cd "iic* at glxpcib?" +.Cd "glxclk* at glxpcib?" +.Cd "isa* at glxpcib?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the AMD Geode CS5536 Companion chip. +This device contains a number of components, including a PCI-ISA bridge. +Besides the core functionality, the +.Nm +.\" driver implements a 32-bit 3.5 MHz timecounter, a watchdog timer device, +.\" a GPIO device, and an SMBus interface. +driver implements a 32-bit 3.5 MHz timecounter. +.Sh SEE ALSO +.\" .Xr gpio 4 , +.\" .Xr iic 4 , +.Xr glxclk 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 , +.Xr pcib 4 , +.\" .Xr watchdog 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 +on the i386 platform. +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Michael Shalayeff . +.\" The GPIO parts were added by +.\" .An Marc Balmer Aq Mt mbalmer@openbsd.org . diff --git a/static/openbsd/man4/man4.loongson/htb.4 b/static/openbsd/man4/man4.loongson/htb.4 new file mode 100644 index 00000000..79791b75 --- /dev/null +++ b/static/openbsd/man4/man4.loongson/htb.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: htb.4,v 1.2 2016/11/20 06:25:21 visa Exp $ +.\" +.\" Copyright (c) 2016 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 20 2016 $ +.Dt HTB 4 loongson +.Os +.Sh NAME +.Nm htb +.Nd PCI host bridge +.Sh SYNOPSIS +.Cd "htb* at mainbus0" +.Cd "pci* at htb?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Xr pci 4 +bus on Loongson 3A systems. +.Sh SEE ALSO +.Xr mainbus 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh BUGS +Add-on cards with a PCI bridge might not be fully functional because +the system firmware does not provide complete interrupt routing information. diff --git a/static/openbsd/man4/man4.loongson/intro.4 b/static/openbsd/man4/man4.loongson/intro.4 new file mode 100644 index 00000000..e841a754 --- /dev/null +++ b/static/openbsd/man4/man4.loongson/intro.4 @@ -0,0 +1,109 @@ +.\" $OpenBSD: intro.4,v 1.5 2022/03/31 17:27:22 naddy Exp $ +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)intro.4 5.2 (Berkeley) 3/27/91 +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt INTRO 4 loongson +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the +loongson platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -compact -width "pcctwo(4)" -offset 3n +.It Xr isa 4 +introduction to ISA bus support +.It Xr pci 4 +introduction to PCI bus support +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The loongson +.Nm +appeared in +.Ox 4.7 . diff --git a/static/openbsd/man4/man4.loongson/leioc.4 b/static/openbsd/man4/man4.loongson/leioc.4 new file mode 100644 index 00000000..20c2b132 --- /dev/null +++ b/static/openbsd/man4/man4.loongson/leioc.4 @@ -0,0 +1,68 @@ +.\" $OpenBSD: leioc.4,v 1.1 2016/11/17 15:06:16 visa Exp $ +.\" +.\" Copyright (c) 2016 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 17 2016 $ +.Dt LEIOC 4 loongson +.Os +.Sh NAME +.Nm leioc +.Nd Loongson 3A low-end IO controller +.Sh SYNOPSIS +.Cd "leioc* at mainbus0" +.Cd "com* at leioc?" +.Sh DESCRIPTION +The +.Nm +driver supports the low-end IO controller present in Loongson 3A CPU packages. +.Pp +The controller provides several IO interfaces: +.Pp +.Bl -dash -compact -offset indent +.It +a conventional +.Xr pci 4 +bus +.It +a Low Pin Count +.Pq LPC +bus +.It +a Serial Peripheral Interface +.Pq SPI +bus +.It +16 +.Xr gpio 4 +pins +.It +two +.Xr com 4 +interfaces +.El +.Pp +Currently, only the +.Xr com 4 +interfaces are supported by the +.Nm +driver. +.Sh SEE ALSO +.Xr com 4 , +.Xr mainbus 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . diff --git a/static/openbsd/man4/man4.loongson/mem.4 b/static/openbsd/man4/man4.loongson/mem.4 new file mode 100644 index 00000000..3e4625d3 --- /dev/null +++ b/static/openbsd/man4/man4.loongson/mem.4 @@ -0,0 +1,111 @@ +.\" $OpenBSD: mem.4,v 1.5 2024/03/22 12:29:33 jsg Exp $ +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This software was developed by the Computer Systems Engineering group +.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and +.\" contributed to Berkeley. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)mem.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: March 22 2024 $ +.Dt MEM 4 loongson +.Os +.Sh NAME +.Nm mem , +.Nm kmem +.Nd memory files +.Sh DESCRIPTION +The file +.Pa /dev/mem +is an interface to the physical memory of the +computer. +Byte offsets in this file are interpreted as physical memory addresses. +Reading and writing this file is equivalent to reading and writing +memory itself. +An error will be returned if an attempt is made to reference +an offset outside of +.Pa /dev/mem . +.Pp +Kernel virtual memory is accessed via the file +.Pa /dev/kmem +in the same manner as +.Pa /dev/mem . +Only kernel virtual addresses that are currently mapped to memory are allowed. +.Pp +On the loongson, physical memory is always contiguous, but can be accessed +from two distinct physical address windows: +.Pp +.Bl -bullet -compact +.It +From address +.Ad 0x00000000 +to +.Ad 0x0fffffff , +the lowest 256 megabytes of memory. +.It +From address +.Ad 0x80000000 +to +.Ad 0xffffffff , +the whole memory, up to 2 gigabytes. +.El +.Pp +This layout implies that a given memory location within the first 256 +megabytes may indifferently be addressed in the +.Ad 0x00000000 - +.Ad 0x0fffffff +address range or the +.Ad 0x80000000 - +.Ad 0x8fffffff +address range. +.Pp +The kernel virtual memory begins at address +.Ad 0xc000000000000000 . +.Pp +Even with sufficient file system permissions, +these devices can only be opened when the +.Xr securelevel 7 +is insecure or when the +.Va kern.allowkmem +.Xr sysctl 2 +variable is set. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/mem +.It Pa /dev/kmem +.El +.Sh SEE ALSO +.Xr securelevel 7 +.Sh HISTORY +The +.Pa /dev/mem +file appeared in +.At v1 , +.Pa /dev/kmem +appeared in +.At v5 . diff --git a/static/openbsd/man4/man4.loongson/sisfb.4 b/static/openbsd/man4/man4.loongson/sisfb.4 new file mode 100644 index 00000000..2c430437 --- /dev/null +++ b/static/openbsd/man4/man4.loongson/sisfb.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: sisfb.4,v 1.2 2010/03/02 20:54:51 miod Exp $ +.\" +.\" Copyright (c) 2010 Miodrag Vallat. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 2 2010 $ +.Dt SISFB 4 loongson +.Os +.Sh NAME +.Nm sisfb +.Nd SiS 315 Pro frame buffer +.Sh SYNOPSIS +.Cd "sisfb* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports the SiS 315 Pro frame buffer. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework, as a +.Xr wsdisplay 4 +device. +.Pp +The PMON firmware initializes the frame buffer in a VGA compatible video mode, +either with a 640x400 resolution and 8 bits per pixel on Fuloong, +or a 1360x768 resolution and 16 bits per pixel on Lynloong. +It is currently not possible to change the frame buffer resolution and +color depth. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/man4.loongson/smfb.4 b/static/openbsd/man4/man4.loongson/smfb.4 new file mode 100644 index 00000000..a8d89701 --- /dev/null +++ b/static/openbsd/man4/man4.loongson/smfb.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: smfb.4,v 1.3 2010/02/18 23:05:06 miod Exp $ +.\" +.\" Copyright (c) 2010 Miodrag Vallat. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 18 2010 $ +.Dt SMFB 4 loongson +.Os +.Sh NAME +.Nm smfb +.Nd Silicon Motion frame buffer +.Sh SYNOPSIS +.Cd "smfb* at pci?" Pq "SM712" +.Cd "smfb* at voyager?" Pq "SM502" +.Sh DESCRIPTION +The +.Nm +driver supports Silicon Motion SM502 and SM712 frame buffers in 16-bit +color mode. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework, as a +.Xr wsdisplay 4 +device. +.Pp +It is currently not possible to change the frame buffer resolution and +color depth. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr voyager 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/man4.loongson/stsec.4 b/static/openbsd/man4/man4.loongson/stsec.4 new file mode 100644 index 00000000..54a52fc2 --- /dev/null +++ b/static/openbsd/man4/man4.loongson/stsec.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: stsec.4,v 1.3 2018/01/12 04:36:44 deraadt Exp $ +.\" +.\" Copyright (c) 2010 Miodrag Vallat. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 12 2018 $ +.Dt STSEC 4 loongson +.Os +.Sh NAME +.Nm stsec +.Nd ST7 embedded controller +.Sh SYNOPSIS +.Cd "stsec* at iic?" +.Sh DESCRIPTION +The +.Nm +driver supports the ST7FOX1 embedded controller found on the Gdium Liberty +netbook. +.Pp +This chip is used to control battery charge and discharge. +It also reports the lid status, as well as the state of the power and wavelan +radio enable buttons. +.Pp +Battery status and charge information is made available through the +.Xr sysctl 2 +hardware sensor interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 diff --git a/static/openbsd/man4/man4.loongson/voyager.4 b/static/openbsd/man4/man4.loongson/voyager.4 new file mode 100644 index 00000000..852dab98 --- /dev/null +++ b/static/openbsd/man4/man4.loongson/voyager.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: voyager.4,v 1.3 2010/02/26 14:53:11 miod Exp $ +.\" +.\" Copyright (c) 2010 Miodrag Vallat. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 26 2010 $ +.Dt VOYAGER 4 loongson +.Os +.Sh NAME +.Nm voyager +.Nd Silicon Motion Mobile Multimedia Companion Chip +.Sh SYNOPSIS +.Cd "voyager* at pci?" +.Cd "gpio0 at voyager?" +.\" .Cd "iic* at voyager?" +.Cd "ohci* at voyager?" +.Cd "smfb* at voyager?" +.Sh DESCRIPTION +The +.Nm +driver supports the Silicon Motion SM502 MMCC device. +.Pp +This chip is intended to fulfill most of a modern laptop's I/O needs, and +provides: +.Pp +.Bl -dash -compact -offset indent +.It +a 2D +.Xr smfb 4 +frame buffer with analog RGB and digital LCD panel interfaces +.It +an 8-bit parallel interface +.It +a +.Xr ohci 4 +USB controller +.It +two UART or IrDA ports +.It +two Zoom Video interfaces +.It +an AC97 or I2S audio codec +.It +two Synchronous Serial Ports +.Pq SSP +.It +Pulse Width Modulation +.Pq PWM +.It +64 +.Xr gpio 4 +pins +.El +.Pp +Not all the device interfaces are supported under +.Ox . +.Pp +The +.Xr ohci 4 +component only attaches on Gdium Liberty systems with the older motherboard +artwork design, as newer systems do not have this USB port connected to +anything, causing an otherwise annoying long delay to probe the empty bus +on boot. +.Sh SEE ALSO +.\" .Xr ac97 4 , +.Xr gpio 4 , +.Xr intro 4 , +.Xr ohci 4 , +.Xr pci 4 , +.Xr smfb 4 diff --git a/static/openbsd/man4/man4.loongson/ykbec.4 b/static/openbsd/man4/man4.loongson/ykbec.4 new file mode 100644 index 00000000..c9d5735b --- /dev/null +++ b/static/openbsd/man4/man4.loongson/ykbec.4 @@ -0,0 +1,54 @@ +.\" $OpenBSD: ykbec.4,v 1.6 2018/09/26 14:58:16 visa Exp $ +.\" +.\" Copyright (c) 2010 Otto Moerbeek +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 26 2018 $ +.Dt YKBEC 4 loongson +.Os +.Sh NAME +.Nm ykbec +.Nd Ene Technology KB3310B embedded controller chip +.Sh SYNOPSIS +.Cd "ykbec0 at isa?" +.Sh DESCRIPTION +The +.Nm +driver supports the Ene Technology KB3310B embedded controller chip found +in the Lemote Yeeloong. +.Pp +This chip provides general purpose I/O and handles several +dedicated functions, including: +.Pp +.Bl -dash -compact -offset indent +.It +Fan control +.It +Battery control +.It +Button events +.It +Power management +.It +Lid state +.El +.Pp +Fan, battery, and lid information is made available via the +.Xr sysctl 2 +hardware sensor interface. +Not all the device interfaces are supported under +.Ox . +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 diff --git a/static/openbsd/man4/man4.luna88k/Makefile b/static/openbsd/man4/man4.luna88k/Makefile new file mode 100644 index 00000000..87c4e10e --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/Makefile @@ -0,0 +1,12 @@ +MAN = autoconf.4 \ + cbus.4 \ + intro.4 \ + lcd.4 \ + le.4 \ + mem.4 \ + necsb.4 \ + pcexmem.4 \ + spc.4 \ + xp.4 + +include ../../../mandoc.mk diff --git a/static/openbsd/man4/man4.luna88k/autoconf.4 b/static/openbsd/man4/man4.luna88k/autoconf.4 new file mode 100644 index 00000000..cdb8095b --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/autoconf.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: autoconf.4,v 1.4 2010/01/02 19:55:35 schwarze Exp $ +.\" +.\" Copyright (c) 1990, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)autoconf.4 8.1 (Berkeley) 6/9/93 +.\" +.Dd $Mdocdate: January 2 2010 $ +.Dt AUTOCONF 4 luna88k +.Os +.Sh NAME +.Nm autoconf +.Nd diagnostics from the autoconfiguration code +.Sh DESCRIPTION +When +.Ox +bootstraps it probes the innards of the machine +on which it is running +and locates controllers, drives, and other devices, printing out +what it finds on the console. +This procedure is driven by a system configuration table which is processed by +.Xr config 8 +and compiled into each kernel. +Devices which exist in the machine but are not configured into the +kernel are not detected. +.Sh SEE ALSO +.Xr intro 4 , +.Xr boot_luna88k 8 , +.Xr config 8 diff --git a/static/openbsd/man4/man4.luna88k/cbus.4 b/static/openbsd/man4/man4.luna88k/cbus.4 new file mode 100644 index 00000000..6187cb81 --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/cbus.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: cbus.4,v 1.5 2020/06/08 00:56:19 aoyama Exp $ +.\" +.\" Copyright (c) 2014 Kenji Aoyama. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: June 8 2020 $ +.Dt CBUS 4 luna88k +.Os +.Sh NAME +.Nm cbus +.Nd NEC PC-9801 extension board slot bus +.Sh SYNOPSIS +.Cd "cbus0 at mainbus0" +.Sh DESCRIPTION +.Nm +is a bus interface of "NEC PC-9801 extension board slot" (so-called +"C-bus" in Japan) on LUNA-88K2. +The original LUNA-88K does not have this slot. +.Sh LIST OF DEVICES +The devices currently supported on +.Nm +are: +.Pp +.Bl -tag -width 10n -offset 3n -compact +.It Xr ne 4 +Allied Telesis CentreCOM LA-98 series +.It Xr necsb 4 +NEC PC-9801-86 sound board +.It Xr pcexmem 4 +NEC PC-9801 extension board slot +.It Xr pcmcia 4 +PCMCIA (PC Card) support +.El +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +bus interface first appeared in +.Ox 5.7 . diff --git a/static/openbsd/man4/man4.luna88k/intro.4 b/static/openbsd/man4/man4.luna88k/intro.4 new file mode 100644 index 00000000..e5a79903 --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/intro.4 @@ -0,0 +1,119 @@ +.\" $OpenBSD: intro.4,v 1.10 2022/03/31 17:27:22 naddy Exp $ +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)intro.4 5.2 (Berkeley) 3/27/91 +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt INTRO 4 luna88k +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the +luna88k platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +A list of the supported devices is given below. +.Sh LIST OF DEVICES +The devices listed below are supported in this incarnation of +the system. +Pseudo-devices are not listed. +Devices are indicated by their functional interface. +Not all supported devices are listed. +.Pp +.Bl -tag -compact -width "pcctwo(4)" -offset 3n +.\".It Xr clock 4 +.\"battery-backed clock +.\".It Xr fb 4 +.\"on-board frame buffer +.It Xr lcd 4 +front panel LCD display +.It Xr le 4 +AMD LANCE Ethernet device +.\".It Xr sio 4 +.\"on-board serial ports +.It Xr spc 4 +Fujitsu MB87030/MB89352 SCSI device +.\".It Xr ws 4 +.\"on-board keyboard and mouse ports +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The luna88k +.Nm +appeared in +.Ox 3.6 . diff --git a/static/openbsd/man4/man4.luna88k/lcd.4 b/static/openbsd/man4/man4.luna88k/lcd.4 new file mode 100644 index 00000000..7167fac2 --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/lcd.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: lcd.4,v 1.4 2015/02/15 22:26:45 bentley Exp $ +.\" +.\" Copyright (c) 2007 Kenji AOYAMA +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 15 2015 $ +.Dt LCD 4 luna88k +.Os +.Sh NAME +.Nm lcd +.Nd front panel LCD display +.Sh SYNOPSIS +.Cd "lcd0 at mainbus0" +.Sh DESCRIPTION +The +.Nm +driver provides access to the front panel LCD display on LUNA-88K. +It is accessed using +.Xr write 2 +to print the characters on the LCD. +The device has a physical display area of 16 characters x 2 lines +and an internal line buffer of 40 characters x 2 lines. +.Pp +The following ioctl calls apply to the +.Nm +device: +.Bl -tag -width LCD +.It Dv LCDCLS +Clear the LCD screen, restore display area from shift and move the +cursor to upper-left position. +.It Dv LCDHOME +Restore display area from shift and move the cursor to upper-left +position. +.It Dv LCDMODE Fa "int *" +Specify cursor advance direction and display shift mode. +.It Dv LCDDISP Fa "int *" +Control display on/off, cursor on/off, and cursor blinking on/off. +.It Dv LCDMOVE Fa "int *" +Move the cursor or shift the display area. +.It Dv LCDSEEK Fa "int *" +Move the cursor to the specified position. +On the first line, the position is specified by a value between 0x00 and 0x27. +On the second line, the value is between 0x40 and 0x67. +.It Dv LCDRESTORE +Restore boot-time LCD message. +.El +.Pp +These ioctl parameters are defined in +.In machine/lcd.h . +.Sh FILES +.Bl -tag -width /dev/lcd +.It Pa /dev/lcd +.El +.Sh SEE ALSO +.Xr ioctl 2 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . diff --git a/static/openbsd/man4/man4.luna88k/le.4 b/static/openbsd/man4/man4.luna88k/le.4 new file mode 100644 index 00000000..67905693 --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/le.4 @@ -0,0 +1,59 @@ +.\" $OpenBSD: le.4,v 1.6 2015/12/08 13:35:37 tedu Exp $ +.\" +.\" Copyright (c) 1990, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)le.4 8.2 (Berkeley) 11/30/93 +.\" +.Dd $Mdocdate: December 8 2015 $ +.Dt LE 4 luna88k +.Os +.Sh NAME +.Nm le +.Nd AMD LANCE Ethernet device +.Sh SYNOPSIS +.Cd "le0 at mainbus0" +.Sh DESCRIPTION +The +.Nm le +interface provides access to a 10 Mb/s Ethernet network via the +.Tn AMD +7990 +.Tn LANCE +Ethernet chip set. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/man4.luna88k/mem.4 b/static/openbsd/man4/man4.luna88k/mem.4 new file mode 100644 index 00000000..5cf09d04 --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/mem.4 @@ -0,0 +1,85 @@ +.\" $OpenBSD: mem.4,v 1.5 2024/03/22 12:29:33 jsg Exp $ +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This software was developed by the Computer Systems Engineering group +.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and +.\" contributed to Berkeley. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)mem.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: March 22 2024 $ +.Dt MEM 4 luna88k +.Os +.Sh NAME +.Nm mem , +.Nm kmem +.Nd memory files +.Sh DESCRIPTION +The file +.Pa /dev/mem +is an interface to the physical memory of the +computer. +Byte offsets in this file are interpreted as physical memory addresses. +Reading and writing this file is equivalent to reading and writing +memory itself. +An error will be returned if an attempt is made to reference +an offset outside of +.Pa /dev/mem . +.Pp +Kernel virtual memory is accessed via the file +.Pa /dev/kmem +in the same manner as +.Pa /dev/mem . +Only kernel virtual addresses that are currently mapped to memory are allowed. +.Pp +On the luna88k, physical memory is always contiguous; +kernel virtual memory begins at +.Ad 0x00000000 . +.Pp +Even with sufficient file system permissions, +these devices can only be opened when the +.Xr securelevel 7 +is insecure or when the +.Va kern.allowkmem +.Xr sysctl 2 +variable is set. +.Sh FILES +.Bl -tag -width /dev/kmem -compact +.It Pa /dev/mem +.It Pa /dev/kmem +.El +.Sh SEE ALSO +.Xr securelevel 7 +.Sh HISTORY +The +.Pa /dev/mem +file appeared in +.At v1 , +.Pa /dev/kmem +appeared in +.At v5 . diff --git a/static/openbsd/man4/man4.luna88k/necsb.4 b/static/openbsd/man4/man4.luna88k/necsb.4 new file mode 100644 index 00000000..4b9dfe39 --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/necsb.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: necsb.4,v 1.1 2014/12/28 13:03:18 aoyama Exp $ +.\" +.\" Copyright (c) 2014 Kenji Aoyama. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: December 28 2014 $ +.Dt NECSB 4 luna88k +.Os +.Sh NAME +.Nm necsb +.Nd NEC PC-9801-86 sound board +.Sh SYNOPSIS +.Cd "necsb0 at cbus?" +.Cd "audio* at necsb?" +.Sh DESCRIPTION +The +.Nm +driver supports NEC PC-9801-86 sound board on +.Xr cbus 4 . +This board is a half-duplex device. +.Sh SEE ALSO +.Xr audio 4 , +.Xr cbus 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.7 . +.Sh BUGS +The FM synthesizer is not supported. diff --git a/static/openbsd/man4/man4.luna88k/pcexmem.4 b/static/openbsd/man4/man4.luna88k/pcexmem.4 new file mode 100644 index 00000000..d08351de --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/pcexmem.4 @@ -0,0 +1,76 @@ +.\" $OpenBSD: pcexmem.4,v 1.4 2014/12/08 13:24:04 aoyama Exp $ +.\" +.\" Copyright (c) 2014 Kenji Aoyama. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: December 8 2014 $ +.Dt PCEXMEM 4 luna88k +.Os +.Sh NAME +.Nm pcexmem , +.Nm pcexio +.Nd NEC PC-9801 extension board slot +.Sh SYNOPSIS +.Cd "pcex0 at cbus0" +.Sh DESCRIPTION +The file +.Pa /dev/pcexmem +is an +.Xr mmap 2 +capable interface to the memory area of the installed board at "NEC PC-9801 +extension board slot" on LUNA-88K2. +Byte offsets in this file are interpreted as relative memory addresses +of the installed board. +The range should be between 0x0 and 0xffffff. +.Pp +The I/O port area of the installed board is accessed via the file +.Pa /dev/pcexio +in the same manner as +.Pa /dev/pcexmem . +The range should be between 0x0 and 0xffff. +.Pp +The following +.Xr ioctl 2 +calls apply to +.Pa /dev/pcexmem +and +.Pa /dev/pcexio +in order to handle interrupts of this extension slot. +Currently 7 levels of interrupt (0 to 6) are supported. +.Bl -tag -width PCEX +.It Dv PCEXSETLEVEL Fa "u_int *" +Register the specified interrupt level with this driver to handle. +.It Dv PCEXRESETLEVEL Fa "u_int *" +Unregister the specified interrupt level with this driver. +.It Dv PCEXWAITINT Fa "u_int *" +Wait for the interrupt with the specified level. +.El +.Sh FILES +.Bl -tag -width /dev/pcexmem -compact +.It Pa /dev/pcexmem +.It Pa /dev/pcexio +.El +.Sh ERRORS +.Bl -tag -width Er +.It Bq Er EWOULDBLOCK +PCEXWAITINT timeouts (currently 1 second). +.El +.Sh SEE ALSO +.Xr ioctl 2 +.Sh HISTORY +The +.Pa /dev/pcexmem +and +.Pa /dev/pcexio +files first appeared in +.Ox 5.6 . diff --git a/static/openbsd/man4/man4.luna88k/spc.4 b/static/openbsd/man4/man4.luna88k/spc.4 new file mode 100644 index 00000000..ed3eb702 --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/spc.4 @@ -0,0 +1,54 @@ +.\" $OpenBSD: spc.4,v 1.5 2012/08/14 01:08:19 dlg Exp $ +.\" $NetBSD: spc.4,v 1.1 2003/08/01 02:36:04 tsutsui Exp $ +.\" +.\" Copyright (c) 2003 Izumi Tsutsui. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 14 2012 $ +.Dt SPC 4 luna88k +.Os +.Sh NAME +.Nm spc +.Nd Fujitsu MB87030/MB89352 SCSI device +.Sh SYNOPSIS +.Cd "spc0 at mainbus0" +.Cd "spc1 at mainbus0" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Tn Fujitsu +MB87030/MB89352 +.Tn SCSI +Protocol Controller (SPC) chips. +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 +.Sh BUGS +Synchronous data transfers are not currently supported. diff --git a/static/openbsd/man4/man4.luna88k/xp.4 b/static/openbsd/man4/man4.luna88k/xp.4 new file mode 100644 index 00000000..055ad9ad --- /dev/null +++ b/static/openbsd/man4/man4.luna88k/xp.4 @@ -0,0 +1,73 @@ +.\" $OpenBSD: xp.4,v 1.2 2017/02/11 23:08:43 jmc Exp $ +.\" +.\" Copyright (c) 2017 Kenji Aoyama. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: February 11 2017 $ +.Dt XP 4 luna88k +.Os +.Sh NAME +.Nm xp +.Nd HD647180X I/O processor +.Sh SYNOPSIS +.Cd "xp0 at mainbus0" +.Sh DESCRIPTION +The file +.Pa /dev/xp +is an +.Xr mmap 2 +capable interface to the memory area of the HD647180X I/O processor +(so-called "XP") on LUNA-88K and LUNA-88K2. +Byte offsets in this file are interpreted as relative memory addresses +of the I/O processor. +The range should be between 0x0 and 0xffff. +.Pp +The following +.Xr ioctl 2 +call applies to +.Pa /dev/xp : +.Bl -tag -width 4n +.It Dv XPIOCDOWNLD Fa "struct xp_download" +Load binary and reset I/O processor. +.Bd -literal -offset indent +struct xp_download { + u_int size; + u_char *data; +}; +.Ed +.Pp +The +.Va size +member specifies the loading binary size, in bytes. +The +.Va data +member points to the binary image. +.El +.Sh FILES +.Bl -tag -width /dev/xp -compact +.It Pa /dev/xp +.El +.Sh ERRORS +.Bl -tag -width Er +.It Bq Er EINVAL +The specified size is 0 or more than the I/O processor's memory size. +.It Bq Er ENOMEM +Memory could not be allocated for loading. +.El +.Sh SEE ALSO +.Xr ioctl 2 +.Sh HISTORY +The +.Pa /dev/xp +file first appeared in +.Ox 6.1 . diff --git a/static/openbsd/man4/man4.macppc/Makefile b/static/openbsd/man4/man4.macppc/Makefile new file mode 100644 index 00000000..fec3b08b --- /dev/null +++ b/static/openbsd/man4/man4.macppc/Makefile @@ -0,0 +1,36 @@ +MAN = abtn.4 \ + adb.4 \ + aoa.4 \ + apm.4 \ + asms.4 \ + autoconf.4 \ + awacs.4 \ + bm.4 \ + daca.4 \ + dfs.4 \ + fcu.4 \ + hpb.4 \ + ht.4 \ + intro.4 \ + kauaiata.4 \ + kiic.4 \ + macgpio.4 \ + macobio.4 \ + mc.4 \ + mediabay.4 \ + mem.4 \ + memc.4 \ + mpcpcibr.4 \ + onyx.4 \ + openpic.4 \ + pgs.4 \ + piic.4 \ + smu.4 \ + snapper.4 \ + sysbutton.4 \ + tumbler.4 \ + xlights.4 \ + zs.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.macppc/abtn.4 b/static/openbsd/man4/man4.macppc/abtn.4 new file mode 100644 index 00000000..cb4d8396 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/abtn.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: abtn.4,v 1.12 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 2001 Peter Philipp +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt ABTN 4 macppc +.Os +.Sh NAME +.Nm abtn +.Nd Apple brightness/volume/eject button control +.Sh SYNOPSIS +.Cd "abtn at adb?" +.Sh DESCRIPTION +The +.Nm +driver allows you to dim the brightness of your display, +change the volume of your speakers and eject the disc +inserted into your drive. +This driver only currently recognizes the dim, brightness, volume +and eject buttons. +Numlock is also handled by this driver but it is silently ignored. +.Sh SEE ALSO +.Xr adb 4 , +.Xr intro 4 +.Sh AUTHORS +The +.Nm +driver was written by +.An Tsubai Masanari +for +.Nx . diff --git a/static/openbsd/man4/man4.macppc/adb.4 b/static/openbsd/man4/man4.macppc/adb.4 new file mode 100644 index 00000000..abb34d12 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/adb.4 @@ -0,0 +1,112 @@ +.\" $OpenBSD: adb.4,v 1.20 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 2001 Peter Philipp +.\" Copyright (c) 1997 Colin Wood +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Colin Wood +.\" for the NetBSD Project. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt ADB 4 macppc +.Os +.Sh NAME +.Nm adb +.Nd introduction to Apple Desktop Bus support +.Sh SYNOPSIS +.Cd "adb0 at macobio?" +.Cd "abtn* at adb?" +.Cd "akbd* at adb?" +.Cd "ams* at adb?" +.Cd "apm0 at adb?" +.Cd "piic0 at adb?" +.Sh DESCRIPTION +The Apple Desktop Bus +.Pq Tn ADB +is the single-master, multiple-slave, low-speed serial bus +interface used by Macintosh computers to connect input devices +such as keyboards, mice, trackballs, and graphics tablets +to the machine. +.Pp +Originally developed for the Mac68K port, the +.Nm +driver was heavily modified when it was ported to the PowerPC architecture. +During this port it seems that the original +.Nm +event device was split into many smaller subsystems, namely: +.Pp +.Bl -enum -compact +.It +Apple Keyboard driver +.Pq Xr akbd 4 . +.It +Apple Mouse Support driver +.Pq Xr ams 4 . +.El +.Pp +New +.Nm +devices such as the Apple Brightness / Volume Control Button +.Pq Xr abtn 4 , +some energy control +.Pq Xr apm 4 , +and I2C controller +.Pq Xr piic 4 +were added to the PowerPC port later to complement the ADB system. +.Pp +.Ox +provides support for the following devices: +.Pp +.Bl -tag -width "abtn(4)XX" -offset 3n -compact +.It Xr abtn 4 +Apple brightness/volume/eject button control +.It Xr akbd 4 +Apple Keyboard Device +.It Xr ams 4 +Apple Mouse Support +.It Xr apm 4 +advanced power management device interface +.It Xr piic 4 +Apple via-pmu I2C controller +.El +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +interface first appeared in +.Nx 0.9 . +It has been under development ever since. +The original +.Nm adb +manpage was written by Colin Wood for +.Nx Ns / Ns Mac68K. +.Sh AUTHORS +.An -nosplit +Original ADB support was written by +.An Bradley A. Grantham . +The direct ADB routines were written by +.An John P. Wittkoski . diff --git a/static/openbsd/man4/man4.macppc/aoa.4 b/static/openbsd/man4/man4.macppc/aoa.4 new file mode 100644 index 00000000..fe8b2237 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/aoa.4 @@ -0,0 +1,78 @@ +.\" $OpenBSD: aoa.4,v 1.10 2020/06/06 21:01:30 gkoehler Exp $ +.\" +.\" Copyright (c) 2005 Joris Vink. +.\" Copyright (c) 2004 Dale Rahn. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: June 6 2020 $ +.Dt AOA 4 macppc +.Os +.Sh NAME +.Nm aoa +.Nd Apple "aoa" audio device +.Sh SYNOPSIS +.Cd "aoa* at macobio?" +.Cd "audio* at aoa?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the audio hardware found in some macppc machines. +These devices do not provide volume control. +.Sh HARDWARE +Machines supported by the +.Nm +driver include: +.Pp +.Bl -dash -offset indent -compact +.It +PowerMac7,3 +.It +PowerMac9,1 +.It +PowerMac10,1 +.It +PowerMac10,2 +.El +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Tsubai Masanari +and ported to +.Ox +by +.An Joris Vink . +.Sh BUGS +This driver needs more testing. +.Pp +This manual page needs more precision and detail. diff --git a/static/openbsd/man4/man4.macppc/apm.4 b/static/openbsd/man4/man4.macppc/apm.4 new file mode 100644 index 00000000..2eed4ae0 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/apm.4 @@ -0,0 +1,220 @@ +.\" $OpenBSD: apm.4,v 1.17 2023/01/30 14:43:29 jcs Exp $ +.\" +.\" Copyright (c) 1998 Marco S. Hyman +.\" +.\" Permission to copy all or part of this material for any purpose is +.\" granted provided that the above copyright notice and this paragraph +.\" are duplicated in all copies. THIS SOFTWARE IS PROVIDED ``AS IS'' +.\" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT +.\" LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE. +.\" +.Dd $Mdocdate: January 30 2023 $ +.Dt APM 4 macppc +.Os +.Sh NAME +.Nm apm +.Nd advanced power management device interface +.Sh SYNOPSIS +.Cd "apm0 at adb?" +.Sh DESCRIPTION +The +.Nm +driver provides an interface which simulates the Advanced Power Management +.Pq APM +BIOS functions. +The BIOS functions are translated into the appropriate PowerManager requests. +Currently only battery level, AC connection, and charging status is available +from the +.Nm +device. +.Pp +Suspend/resume and other power events are +.Em NOT YET SUPPORTED . +.Pp +Configuration options: +.Pp +.Bl -tag -width DIAGNOSTIC -compact -offset indent +.It Dv APMDEBUG +Enable various driver status messages. +.It Dv DIAGNOSTIC +Enable debugging messages. +.It Dv DEBUG +Enable other debugging messages. +.El +.Pp +The +.Nm +driver implements the following +.Xr ioctl 2 +calls. +They are defined in +.In machine/apmvar.h . +.Bl -tag -width Ds +.It Dv APM_IOC_REJECT +.Em Not implemented . DO NOT USE . +.It Dv APM_IOC_STANDBY +.Em NOT YET SUPPORTED on macppc . +.Pp +.Pq Li "no parameters" +Request +.Dq standby +mode. +.It Dv APM_IOC_SUSPEND +.Em NOT YET SUPPORTED on macppc . +.Pp +.Pq Li "no parameters" +Request +.Dq suspend +mode. +.\" .It Dv APM_IOC_HIBERNATE +.\" .Em NOT YET SUPPORTED on macppc . +.\" .Pp +.\" .Pq Li "no parameters" +.\" Request +.\" .Dq hibernate +.\" mode. +.It Dv APM_IOC_GETPOWER +.Pq Li "struct apm_power_info" +Request the current power state. +The argument structure is as follows: +.Bd -literal -offset indent +struct apm_power_info { + u_char battery_state; + u_char ac_state; + u_char battery_life; + u_char spare1; + u_int minutes_left; + u_int spare2[6]; +}; +.Ed +.Pp +The following values are defined for +.Va battery_state : +.Bl -tag -width Ds +.It Dv APM_BATT_HIGH +Battery has a high state of charge. +.It Dv APM_BATT_LOW +Battery has a low state of charge. +.It Dv APM_BATT_CRITICAL +Battery has a critical state of charge. +.It Dv APM_BATT_CHARGING +Battery is not high, low, or critical and is currently charging. +.It Dv APM_BATT_UNKNOWN +Cannot read the current battery state. +.It Dv APM_BATTERY_ABSENT +No battery installed. +.El +.Pp +The following values are defined for +.Va ac_state : +.Bl -tag -width Ds +.It Dv APM_AC_OFF +External power not detected. +.It Dv APM_AC_ON +External power detected. +.It Dv APM_AC_BACKUP +Backup power in use. +.It Dv APM_AC_UNKNOWN +External power state unknown. +.El +.Pp +The +.Va battery_life +value contains the estimated percentage of battery life available. +100% indicates a full charge. +.Pp +If the battery is charging, i.e. when +.Va battery_state +is equal to +.Dv APM_BATT_CHARGING , +the +.Va battery_life +value contains the estimated number of minutes until the battery will be +fully charged. +Otherwise, the +.Va minutes_left +value contains the estimated number of minutes of battery life remaining. +.It Dv APM_IOC_DEV_CTL +.Em NOT YET SUPPORTED on macppc . +.Pp +.Pq Li "struct apm_ctl" +Allows an application to directly set the +APM operating mode. +The argument structure is as follows: +.Bd -literal -offset indent +struct apm_ctl { + u_int dev; + u_int mode; +}; +.Ed +.Pp +.Va dev +indicates the device, typically +.Dv APM_DEV_ALLDEVS . +.Pp +.Va mode +indicates the desired operating mode. +Possible values are +.Bl -tag -width Ds -compact -offset indent +.It Dv APM_SYS_READY +.It Dv APM_SYS_STANDBY +.It Dv APM_SYS_SUSPEND +.It Dv APM_SYS_OFF +.It Dv APM_LASTREQ_INPROG +.It Dv APM_LASTREQ_REJECTED +.El +.It Dv APM_IOC_PRN_CTL +.Em NOT YET SUPPORTED on macppc . +.Pp +.Pq Li "int" +This +.Xr ioctl 2 +controls message output by the APM +driver when a power change event is detected. +The integer parameter is one of: +.Bl -tag -width Ds +.It Dv APM_PRINT_ON +All power change events result in a message. +This is the normal operating mode for the driver. +.It Dv APM_PRINT_OFF +Power change event messages are suppressed. +.It Dv APM_PRINT_PCT +Power change event messages are suppressed unless the estimated +battery life percentage changes. +.El +.El +.Sh FILES +.Bl -tag -width "/dev/apmctlXXX" +.It /dev/apm +Power management data device. +May only be opened read-only. +May be opened by multiple concurrent users. +.It /dev/apmctl +Power management control device. +May be opened read-write or write-only. +May only be opened by one user at a time. +An attempt to open the file when in use will fail, returning +.Er EBUSY . +.El +.Sh SEE ALSO +.Xr adb 4 , +.Xr intro 4 , +.Xr apm 8 , +.Xr apmd 8 , +.Xr halt 8 +.Sh HISTORY +The +.Nm +driver source code contains these copyrights: +.Pp +.Bl -item -compact +.It +.Li Copyright (c) 1995 John T. Kohl. All rights reserved. +.It +.Li Copyright (C) 1994 by HOSOKAWA Tatsumi +.El +.Pp +\&...and has been hacked on by many others since. +.Sh BUGS +Sleep modes and power events are not supported. diff --git a/static/openbsd/man4/man4.macppc/asms.4 b/static/openbsd/man4/man4.macppc/asms.4 new file mode 100644 index 00000000..9d1435b6 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/asms.4 @@ -0,0 +1,68 @@ +.\" $OpenBSD: asms.4,v 1.7 2013/07/17 14:43:34 martin Exp $ +.\" +.\" Copyright (c) 2005 Xavier Santolaria +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 17 2013 $ +.Dt ASMS 4 macppc +.Os +.Sh NAME +.Nm asms +.Nd Apple sudden motion sensor +.Sh SYNOPSIS +.Cd "asms* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Apple sudden motion sensor found +in some laptops. +.Pp +The sensors currently exposed via the +.Xr sysctl 8 +interface are: +.Bl -column "Sensor" "Units" "Typical" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical Use" +.It Li "X_ACCEL" Ta "Unknown" Ta "X Acceleration" +.It Li "Y_ACCEL" Ta "Unknown" Ta "Y Acceleration" +.It Li "Z_ACCEL" Ta "Unknown" Ta "Z Acceleration" +.El +.Sh HARDWARE +Machines supported by the +.Nm +driver include: +.Pp +.Bl -dash -offset indent -compact +.It +PowerBook5,6 +.It +PowerBook6,7 +.It +PowerBook6,8 +.El +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Xavier Santolaria Aq Mt xsa@openbsd.org . diff --git a/static/openbsd/man4/man4.macppc/autoconf.4 b/static/openbsd/man4/man4.macppc/autoconf.4 new file mode 100644 index 00000000..def4c60b --- /dev/null +++ b/static/openbsd/man4/man4.macppc/autoconf.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: autoconf.4,v 1.4 2007/05/31 19:19:55 jmc Exp $ +.\" +.\" Copyright (c) 1994 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christopher G. Demetriou. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt AUTOCONF 4 macppc +.Os +.Sh NAME +.Nm autoconf +.Nd diagnostics from the autoconfiguration code +.Sh DESCRIPTION +When +.Ox +bootstraps it probes the innards of the machine +on which it is running +and locates controllers, drives, and other devices, printing out +what it finds on the console. +This procedure is driven by a system configuration table which is processed by +.Xr config 8 +and compiled into each kernel. +Devices which exist in the machine but are not configured into the +kernel are usually not detected. +.Sh SEE ALSO +.Xr intro 4 , +.Xr boot_macppc 8 , +.Xr config 8 diff --git a/static/openbsd/man4/man4.macppc/awacs.4 b/static/openbsd/man4/man4.macppc/awacs.4 new file mode 100644 index 00000000..33f17293 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/awacs.4 @@ -0,0 +1,82 @@ +.\" $OpenBSD: awacs.4,v 1.13 2015/01/15 20:37:36 schwarze Exp $ +.\" $NetBSD: awacs.4,v 1.2 2001/05/09 22:16:12 he Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt AWACS 4 macppc +.Os +.Sh NAME +.Nm awacs +.Nd Apple awacs audio device +.Sh SYNOPSIS +.Cd "awacs* at macobio?" +.Cd "audio* at awacs?" +.Sh DESCRIPTION +The +.Nm +(audio waveform amplifier and converter for sound) +driver provides support for the audio hardware found in many Apple +PowerMacs. +.Sh HARDWARE +Machines supported by the +.Nm +driver include: +.Pp +.Bl -dash -offset indent -compact +.It +iMac,1 +.It +PowerBook3,2 +.It +PowerMac1,1 +.It +PowerMac2,1 +.It +PowerMac2,2 +.It +PowerMac3,1 +.It +PowerMac3,3 +.El +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Nx 1.5.1 +and was imported in +.Ox 3.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Tsubai Masanari . +.Sh BUGS +This driver needs more testing. +.Pp +This manual page needs more precision and detail. diff --git a/static/openbsd/man4/man4.macppc/bm.4 b/static/openbsd/man4/man4.macppc/bm.4 new file mode 100644 index 00000000..a27d03d8 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/bm.4 @@ -0,0 +1,64 @@ +.\" $OpenBSD: bm.4,v 1.10 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 2001 Peter Philipp +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt BM 4 macppc +.Os +.Sh NAME +.Nm bm +.Nd Apple BMAC Ethernet device +.Sh SYNOPSIS +.Cd "bm* at macobio?" +.Cd "lxtphy* at mii?" +.Sh DESCRIPTION +The +.Nm +device driver supports Apple BMAC and compatible Ethernet devices. +.Sh HARDWARE +Machines supported by the +.Nm +driver include: +.Pp +.Bl -dash -offset indent -compact +.It +PowerBook1,1 +.It +PowerMac1,1 +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr lxtphy 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh AUTHORS +The +.Nm +Ethernet driver was written by +.An Tsubai Masanari . diff --git a/static/openbsd/man4/man4.macppc/daca.4 b/static/openbsd/man4/man4.macppc/daca.4 new file mode 100644 index 00000000..610533d4 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/daca.4 @@ -0,0 +1,74 @@ +.\" $OpenBSD: daca.4,v 1.8 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Joris Vink. +.\" Copyright (c) 2004 Dale Rahn. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt DACA 4 macppc +.Os +.Sh NAME +.Nm daca +.Nd Apple "daca" audio device +.Sh SYNOPSIS +.Cd "daca* at macobio?" +.Cd "audio* at daca?" +.Sh DESCRIPTION +The +.Nm +driver provides support for audio hardware using the DAC3550A chip +found in some macppc machines. +.Sh HARDWARE +Machines supported by the +.Nm +driver include: +.Pp +.Bl -dash -offset indent -compact +.It +PowerBook2,1 +.It +PowerBook2,2 +.El +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Tsubai Masanari +and ported to +.Ox +by +.An Joris Vink . +.Sh BUGS +This driver needs more testing. +.Pp +This manual page needs more precision and detail. diff --git a/static/openbsd/man4/man4.macppc/dfs.4 b/static/openbsd/man4/man4.macppc/dfs.4 new file mode 100644 index 00000000..d4baa6dd --- /dev/null +++ b/static/openbsd/man4/man4.macppc/dfs.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: dfs.4,v 1.2 2011/05/25 18:13:54 jmc Exp $ +.\" +.\" Copyright (c) 2011 Martin Pieuchot +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 25 2011 $ +.Dt DFS 4 macppc +.Os +.Sh NAME +.Nm dfs +.Nd Dynamic Frequency Switching +.Sh SYNOPSIS +.Cd "dfs* at macgpio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Dynamic Frequency Switching +feature found on some PowerPC microprocessors. +.Pp +It conserves power by lowering the processor operating frequency. +Depending on the processor model, the processor-to-system bus ratio can +be divided by two or four. +.Sh HARDWARE +Processors supported by the +.Nm +driver are part of the PowerPC G4 family and are found on various iBook +and PowerBook machines: +.Bd -literal -offset indent +MPC7447A PowerPC 7447 "Apollo 7" +MPC7448 PowerPC 7448 "Apollo 8" +.Ed +.Sh SEE ALSO +.Xr macgpio 4 , +.Xr sysctl 8 +.Rs +.%T MPC7450 RISC Microprocessor Family Reference Manual +.Re +.Sh HISTORY +Support for the +.Nm +driver first appeared in +.Ox 5.0 . diff --git a/static/openbsd/man4/man4.macppc/fcu.4 b/static/openbsd/man4/man4.macppc/fcu.4 new file mode 100644 index 00000000..10a3f292 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/fcu.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: fcu.4,v 1.10 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt FCU 4 macppc +.Os +.Sh NAME +.Nm fcu +.Nd Apple Fan Control Unit sensor device +.Sh SYNOPSIS +.Cd "fcu* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Apple +Fan Control Unit (FCU). +The device controls and monitors fans found in some Apple +machines. +Fan speed readings and PWM settings are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/man4.macppc/hpb.4 b/static/openbsd/man4/man4.macppc/hpb.4 new file mode 100644 index 00000000..27e73c95 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/hpb.4 @@ -0,0 +1,40 @@ +.\" $OpenBSD: hpb.4,v 1.3 2022/08/06 11:03:14 jsg Exp $ +.\" +.\" Copyright (c) 2015 Martin Pieuchot +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2022 $ +.Dt HPB 4 macppc +.Os +.Sh NAME +.Nm hpb +.Nd HyperTransport-PCI bridge +.Sh SYNOPSIS +.Cd "hpb* at pci?" +.Cd "pci* at hpb?" +.Sh DESCRIPTION +The +.Nm +driver supports PCI-PCI bridges with HyperTransport Interrupt Capability +as found in the IBM CPC945. +It provides support for HyperTransport posted write interrupts. +.Sh SEE ALSO +.Xr ht 4 , +.Xr openpic 4 , +.Xr pci 4 +.Rs +.%T CPC945 Bridge and Memory Controller +.%B User Manual +.%D February 1, 2008 +.Re diff --git a/static/openbsd/man4/man4.macppc/ht.4 b/static/openbsd/man4/man4.macppc/ht.4 new file mode 100644 index 00000000..36d56d46 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/ht.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: ht.4,v 1.4 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt HT 4 macppc +.Os +.Sh NAME +.Nm ht +.Nd HyperTransport bus +.Sh SYNOPSIS +.Cd "ht* at mainbus0" +.Cd "pci* at ht?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the HyperTransport bus found on Apple +.Tn G5 +machines. +The HyperTransport bus is functionally very similar to the +.Xr pci 4 +bus. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.macppc/intro.4 b/static/openbsd/man4/man4.macppc/intro.4 new file mode 100644 index 00000000..837d836d --- /dev/null +++ b/static/openbsd/man4/man4.macppc/intro.4 @@ -0,0 +1,120 @@ +.\" $OpenBSD: intro.4,v 1.53 2022/03/31 17:27:22 naddy Exp $ +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt INTRO 4 macppc +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the MacPPC +platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The configuration system is described in +.Xr autoconf 4 . +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width "cardbus(4)XX" -offset 3n -compact +.It Xr adb 4 +introduction to Apple Desktop Bus support +.It Xr cardbus 4 +introduction to CardBus support +.It Xr iic 4 +Inter IC (I2C) bus +.It Xr macobio 4 +introduction to Apple PowerPC onboard I/O bus support +.It Xr onewire 4 +1-Wire bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr pcmcia 4 +introduction to PCMCIA (PC Card) support +.It Xr usb 4 +introduction to Universal Serial Bus support +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The +MacPPC +.Nm +first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.macppc/kauaiata.4 b/static/openbsd/man4/man4.macppc/kauaiata.4 new file mode 100644 index 00000000..38ab15e1 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/kauaiata.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: kauaiata.4,v 1.4 2007/05/31 19:19:55 jmc Exp $ +.\" +.\" Copyright (c) 2003 Dale Rahn. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt KAUAIATA 4 macppc +.Os +.Sh NAME +.Nm kauaiata +.Nd ATA100 HD controller on PCI bus +.Sh SYNOPSIS +.Cd "kauaiata* at pci?" +.Sh DESCRIPTION +The +.Nm +device serves as a bridge to wdc_obio. +The DBDMA based controller logic which was on the +.Xr macobio 4 +was copied and placed on the PCI bus. +This driver adapts the PCI configuration data into the form expected +by wdc_obio. +.Sh SEE ALSO +.Xr macobio 4 , +.Xr wdc 4 +.Sh HISTORY +The +.Nm +first appeared in +.Ox 3.4 . diff --git a/static/openbsd/man4/man4.macppc/kiic.4 b/static/openbsd/man4/man4.macppc/kiic.4 new file mode 100644 index 00000000..fc983562 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/kiic.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: kiic.4,v 1.3 2008/05/01 19:17:16 xsa Exp $ +.\" +.\" Copyright (c) 2004 Dale Rahn. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: May 1 2008 $ +.Dt KIIC 4 macppc +.Os +.Sh NAME +.Nm kiic +.Nd Apple Kauai I2C controller +.Sh SYNOPSIS +.Cd "kiic* at macobio?" +.Sh DESCRIPTION +The +.Nm +device is an interface to the Kauai I2C controller. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr macobio 4 , +.Xr memc 4 +.Sh HISTORY +The +.Nm +first appeared in +.Nx +and was imported in +.Ox +3.5. diff --git a/static/openbsd/man4/man4.macppc/macgpio.4 b/static/openbsd/man4/man4.macppc/macgpio.4 new file mode 100644 index 00000000..523ffb9a --- /dev/null +++ b/static/openbsd/man4/man4.macppc/macgpio.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: macgpio.4,v 1.8 2011/05/25 18:14:55 jmc Exp $ +.\" +.\" Copyright (c) 2007 Gordon Willem Klok +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 25 2011 $ +.Dt MACGPIO 4 macppc +.Os +.Sh NAME +.Nm macgpio +.Nd support for on-board GPIO controllers +.Sh SYNOPSIS +.Cd "macgpio* at macobio?" +.Cd "macgpio* at macgpio?" +.Sh DESCRIPTION +The +.Nm +device provides support for GPIO controllers found on many +Apple machines. +.Pp +.Ox +provides support for the following devices: +.Pp +.Bl -tag -width 14n -offset indent -compact +.It Xr dfs 4 +Dynamic Frequency Switching +.It Xr pgs 4 +programmer's switch +.It Xr sysbutton 4 +Xserve G4 and G5 front system identifier button +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr macobio 4 diff --git a/static/openbsd/man4/man4.macppc/macobio.4 b/static/openbsd/man4/man4.macppc/macobio.4 new file mode 100644 index 00000000..738f2fdf --- /dev/null +++ b/static/openbsd/man4/man4.macppc/macobio.4 @@ -0,0 +1,86 @@ +.\" $OpenBSD: macobio.4,v 1.24 2021/04/09 20:05:50 kn Exp $ +.\" +.\" Copyright (c) 2003 Dale Rahn. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: April 9 2021 $ +.Dt MACOBIO 4 macppc +.Os +.Sh NAME +.Nm macobio +.Nd introduction to Apple PowerPC onboard I/O bus support +.Sh SYNOPSIS +.Cd "macobio0 at pci?" +.Sh DESCRIPTION +The +.Nm +device serves as a bridge to many of the onboard devices; it +supports the GC, Heathrow, Intrepid, K2, Keylargo, OHare, Paddington, +Pangea, and Shasta modules. +.Pp +.Ox +provides support for the following devices: +.Pp +.Bl -tag -width 16n -offset indent -compact +.It Xr aoa 4 +Apple aoa audio device +.It Xr awacs 4 +Apple awacs audio device +.It Xr bm 4 +Apple BMAC Ethernet device +.It Xr daca 4 +Apple daca audio device +.It Xr macgpio 4 +support for on-board GPIO controllers +.It Xr mc 4 +Am79C940 (MACE) on-board Ethernet device +.It Xr mediabay 4 +ATA33 HD controller +.It Xr onyx 4 +Apple onyx audio device +.It Xr openpic 4 +OpenPIC interrupt controller +.It Xr snapper 4 +Apple snapper audio device +.It Xr tumbler 4 +Apple tumbler audio device +.It Xr wdc 4 +WD100x compatible hard disk controller driver +.It Xr wi 4 +WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b wireless network device +.It Xr xlights 4 +Xserve G4 and G5 front panel LEDs +.It Xr zs 4 +Zilog 8530 (ZSCC) serial communications driver +.El +.Sh SEE ALSO +.Xr adb 4 , +.Xr intro 4 , +.Xr kiic 4 , +.Xr memc 4 +.Sh HISTORY +The +.Nm +first appeared in +.Ox 2.8 . diff --git a/static/openbsd/man4/man4.macppc/mc.4 b/static/openbsd/man4/man4.macppc/mc.4 new file mode 100644 index 00000000..3507e7ce --- /dev/null +++ b/static/openbsd/man4/man4.macppc/mc.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: mc.4,v 1.4 2007/05/31 19:19:55 jmc Exp $ +.\" $NetBSD: mc.4,v 1.1 1997/12/18 06:22:45 ender Exp $ +.\" +.\" Copyright (c) 1997 David Huang +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt MC 4 macppc +.Os +.Sh NAME +.Nm mc +.Nd Am79C940 (MACE) on-board Ethernet device +.Sh SYNOPSIS +.Cd "mc* at macobio?" +.Sh DESCRIPTION +The +.Nm +interface provides access to a 10 Mb/s Ethernet network via the AMD Am79C940 +(MACE) Ethernet chip set. +.Pp +The +.Nm +interface supports the on-board Ethernet of most old world +Power Macintosh systems. +.Pp +Machines supported by the +.Nm +driver include: +.Pp +.Bl -dash -offset indent -compact +.It +Power Macintosh 7600, 8500, 9500 and 9600. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr macobio 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +The +.Nm +Ethernet driver was written by +.An Dave Huang . diff --git a/static/openbsd/man4/man4.macppc/mediabay.4 b/static/openbsd/man4/man4.macppc/mediabay.4 new file mode 100644 index 00000000..2ee55e8e --- /dev/null +++ b/static/openbsd/man4/man4.macppc/mediabay.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: mediabay.4,v 1.6 2015/10/22 11:03:15 sobrado Exp $ +.\" +.\" Copyright (c) 2003 Dale Rahn. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: October 22 2015 $ +.Dt MEDIABAY 4 macppc +.Os +.Sh NAME +.Nm mediabay +.Nd ATA33 HD controller +.Sh SYNOPSIS +.Cd "mediabay* at macobio?" +.Sh DESCRIPTION +The +.Nm +device allows attachment of +.Xr wdc 4 +to the removable CD on the PowerBook G3 (Pismo) machines. +.Sh SEE ALSO +.Xr intro 4 , +.Xr macobio 4 , +.Xr wdc 4 +.Sh HISTORY +The +.Nm +first appeared in +.Ox 3.6 . +It existed previously in +.Nx . diff --git a/static/openbsd/man4/man4.macppc/mem.4 b/static/openbsd/man4/man4.macppc/mem.4 new file mode 100644 index 00000000..e1f5cb52 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/mem.4 @@ -0,0 +1,85 @@ +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This software was developed by the Computer Systems Engineering group +.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and +.\" contributed to Berkeley. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)mem.4 8.1 (Berkeley) 6/5/93 +.\" $OpenBSD: mem.4,v 1.8 2024/03/22 12:29:33 jsg Exp $ +.\" $NetBSD: mem.4,v 1.1 1997/06/08 17:40:57 ender Exp $ +.\" +.Dd $Mdocdate: March 22 2024 $ +.Dt MEM 4 macppc +.Os +.Sh NAME +.Nm mem , +.Nm kmem +.Nd memory files +.Sh DESCRIPTION +The file +.Pa /dev/mem +is an interface to the physical memory of the computer. +Byte offsets in this file are interpreted as physical memory addresses. +Reading and writing this file is equivalent to reading and writing +memory itself. +An error will be returned if an attempt is made to reference +an offset outside of +.Pa /dev/mem . +.Pp +Kernel virtual memory is accessed via the file +.Pa /dev/kmem +in the same manner as +.Pa /dev/mem . +Only kernel virtual addresses that are currently mapped to memory are allowed. +.Pp +On the Macintosh, physical memory may be discontiguous; +kernel virtual memory begins at +.Ad 0x00000000 . +.Pp +Even with sufficient file system permissions, +these devices can only be opened when the +.Xr securelevel 7 +is insecure or when the +.Va kern.allowkmem +.Xr sysctl 2 +variable is set. +.Sh FILES +.Bl -tag -width /dev/kmem -compact +.It /dev/mem +.It /dev/kmem +.El +.Sh SEE ALSO +.Xr securelevel 7 +.Sh HISTORY +The +.Pa /dev/mem +file appeared in +.At v1 , +.Pa /dev/kmem +appeared in +.At v5 . diff --git a/static/openbsd/man4/man4.macppc/memc.4 b/static/openbsd/man4/man4.macppc/memc.4 new file mode 100644 index 00000000..df77af75 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/memc.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: memc.4,v 1.2 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Xavier Santolaria +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt MEMC 4 macppc +.Os +.Sh NAME +.Nm memc +.Nd UniNorth interface +.Sh SYNOPSIS +.Cd "memc* at mainbus0" +.Sh DESCRIPTION +The +.Nm +device is an interface to the UniNorth bridge chip. +.Sh SEE ALSO +.Xr intro 4 , +.Xr kiic 4 , +.Xr macobio 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Dale Rahn . diff --git a/static/openbsd/man4/man4.macppc/mpcpcibr.4 b/static/openbsd/man4/man4.macppc/mpcpcibr.4 new file mode 100644 index 00000000..c5f787c0 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/mpcpcibr.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: mpcpcibr.4,v 1.2 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Xavier Santolaria +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt MPCPCIBR 4 macppc +.Os +.Sh NAME +.Nm mpcpcibr +.Nd PCI host bridge +.Sh SYNOPSIS +.Cd "mpcpcibr* at mainbus0" +.Cd "pci* at mpcpcibr?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PCI host bridge present on PowerPC systems. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Per Fogelstrom . diff --git a/static/openbsd/man4/man4.macppc/onyx.4 b/static/openbsd/man4/man4.macppc/onyx.4 new file mode 100644 index 00000000..d1e8ae04 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/onyx.4 @@ -0,0 +1,64 @@ +.\" $OpenBSD: onyx.4,v 1.8 2013/07/20 19:35:49 martin Exp $ +.\" +.\" Copyright (c) 2005 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 20 2013 $ +.Dt ONYX 4 macppc +.Os +.Sh NAME +.Nm onyx +.Nd Apple "onyx" audio device +.Sh SYNOPSIS +.Cd "onyx* at macobio?" +.Cd "audio* at onyx?" +.Sh DESCRIPTION +The +.Nm +driver provides support for audio hardware using the PCM3052 chip +found in some macppc machines. +.Sh HARDWARE +Machines supported by the +.Nm +driver include: +.Pp +.Bl -dash -offset indent -compact +.It +PowerBook5,8 +.It +PowerBook5,9 +.It +PowerBook6,8 +.It +PowerMac11,2 +.El +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org +based on code written by Tsubai Masanari. +.Sh BUGS +The driver emits some nasty pop-noise when playback starts. +.Pp +This manual page needs more precision and detail. diff --git a/static/openbsd/man4/man4.macppc/openpic.4 b/static/openbsd/man4/man4.macppc/openpic.4 new file mode 100644 index 00000000..70eda976 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/openpic.4 @@ -0,0 +1,39 @@ +.\" $OpenBSD: openpic.4,v 1.2 2008/05/04 21:06:13 jmc Exp $ +.\" +.\" Copyright (c) 2008 Xavier Santolaria +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 4 2008 $ +.Dt OPENPIC 4 macppc +.Os +.Sh NAME +.Nm openpic +.Nd OpenPIC interrupt controller +.Sh SYNOPSIS +.Cd "openpic* at memc?" +.Cd "openpic* at macobio?" +.Sh DESCRIPTION +The +.Nm +driver manages the OpenPIC interrupt controller found on +PowerPC systems. +.Sh SEE ALSO +.Xr intro 4 , +.Xr macobio 4 , +.Xr memc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.7 . diff --git a/static/openbsd/man4/man4.macppc/pgs.4 b/static/openbsd/man4/man4.macppc/pgs.4 new file mode 100644 index 00000000..e2b8e776 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/pgs.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: pgs.4,v 1.4 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2010 Jasper Lievisse Adriaanse +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PGS 4 macppc +.Os +.Sh NAME +.Nm pgs +.Nd programmer's switch +.Sh SYNOPSIS +.Cd "pgs* at macgpio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the "Programmer's Switch" found on selected +PowerMac2,1 and newer models. +If the +.Va ddb.console +.Xr sysctl 8 +is set, pressing the button will cause the machine to enter +.Xr ddb 4 . +The "Programmers Switch" can be identified by the V-like symbol on it. +.Sh SEE ALSO +.Xr intro 4 , +.Xr macgpio 4 , +.Xr sysctl 8 +.Sh HISTORY +Support for the +.Nm +driver first appeared in +.Ox 4.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Jasper Lievisse Adriaanse Aq Mt jasper@openbsd.org . diff --git a/static/openbsd/man4/man4.macppc/piic.4 b/static/openbsd/man4/man4.macppc/piic.4 new file mode 100644 index 00000000..455f159b --- /dev/null +++ b/static/openbsd/man4/man4.macppc/piic.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: piic.4,v 1.2 2007/05/31 19:19:55 jmc Exp $ +.\" +.\" Copyright (c) 2004 Dale Rahn. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt PIIC 4 macppc +.Os +.Sh NAME +.Nm piic +.Nd Apple via-pmu I2C controller +.Sh SYNOPSIS +.Cd "piic0 at adb?" +.Sh DESCRIPTION +The +.Nm +device is an interface to the via-pmu I2C controller. +.Sh SEE ALSO +.Xr adb 4 , +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +first appeared in +.Ox 3.9 . diff --git a/static/openbsd/man4/man4.macppc/smu.4 b/static/openbsd/man4/man4.macppc/smu.4 new file mode 100644 index 00000000..540964ca --- /dev/null +++ b/static/openbsd/man4/man4.macppc/smu.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: smu.4,v 1.11 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" Copyright (c) 2005 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt SMU 4 macppc +.Os +.Sh NAME +.Nm smu +.Nd Apple System Management Unit +.Sh SYNOPSIS +.Cd "smu? at mainbus0" +.Sh DESCRIPTION +The +.Nm +driver provides support for the System Management Unit found on Apple +.Tn iMac G5 +and some +.Tn Power Mac G5 +machines. +.Pp +The System Management Unit controls the fans in these systems. +It also contains the real-time clock and an I2C controller. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis . +.Sh BUGS +Fan control is not implemented yet. diff --git a/static/openbsd/man4/man4.macppc/snapper.4 b/static/openbsd/man4/man4.macppc/snapper.4 new file mode 100644 index 00000000..357d0126 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/snapper.4 @@ -0,0 +1,105 @@ +.\" $OpenBSD: snapper.4,v 1.17 2020/06/06 21:01:30 gkoehler Exp $ +.\" +.\" Copyright (c) 2004 Dale Rahn. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: June 6 2020 $ +.Dt SNAPPER 4 macppc +.Os +.Sh NAME +.Nm snapper +.Nd Apple "snapper" audio device +.Sh SYNOPSIS +.Cd "snapper* at macobio?" +.Cd "audio* at snapper?" +.Sh DESCRIPTION +The +.Nm +driver provides support for audio hardware using the TAS3004 chip +found in some macppc machines. +.Sh HARDWARE +Machines supported by the +.Nm +driver include: +.Pp +.Bl -dash -offset indent -compact +.It +PowerBook3,4 +.It +PowerBook3,5 +.It +PowerBook4,3 +.It +PowerBook5,1 +.It +PowerBook5,2 +.It +PowerBook5,3 +.It +PowerBook5,4 +.It +PowerBook5,5 +.It +PowerBook5,6 +.It +PowerBook6,1 +.It +PowerBook6,2 +.It +PowerBook6,3 +.It +PowerBook6,4 +.It +PowerBook6,5 +.It +PowerBook6,7 +.It +PowerMac3,6 +.It +PowerMac4,4 +.El +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx +and was imported in +.Ox 3.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Tsubai Masanari +and ported to +.Ox +by +.An Dale Rahn . +.Sh BUGS +This driver needs more testing. +.Pp +This manual page needs more precision and detail. diff --git a/static/openbsd/man4/man4.macppc/sysbutton.4 b/static/openbsd/man4/man4.macppc/sysbutton.4 new file mode 100644 index 00000000..4006a80c --- /dev/null +++ b/static/openbsd/man4/man4.macppc/sysbutton.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: sysbutton.4,v 1.6 2007/05/31 19:19:55 jmc Exp $ +.\" +.\" Copyright (c) 2007 Gordon Willem Klok +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt SYSBUTTON 4 macppc +.Os +.Sh NAME +.Nm sysbutton +.Nd Xserve G4 and G5 front system identifier button +.Sh SYNOPSIS +.Cd "sysbutton* at macgpio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the system identifier button found on +the front panel of Apple G4 and G5 Xserve machines. +.Pp +If the +.Va ddb.console +.Xr sysctl 8 +is set, +pressing the system identifier +button will cause the machine to enter +.Xr ddb 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr macgpio 4 , +.Xr sysctl 8 diff --git a/static/openbsd/man4/man4.macppc/tumbler.4 b/static/openbsd/man4/man4.macppc/tumbler.4 new file mode 100644 index 00000000..0cccdb01 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/tumbler.4 @@ -0,0 +1,82 @@ +.\" $OpenBSD: tumbler.4,v 1.8 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Joris Vink. +.\" Copyright (c) 2004 Dale Rahn. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt TUMBLER 4 macppc +.Os +.Sh NAME +.Nm tumbler +.Nd Apple "tumbler" audio device +.Sh SYNOPSIS +.Cd "tumbler* at macobio?" +.Cd "audio* at tumbler?" +.Sh DESCRIPTION +The +.Nm +driver provides support for audio hardware using the TAS3001 chip +found in some macppc machines. +.Sh HARDWARE +Machines supported by the +.Nm +driver include: +.Pp +.Bl -dash -offset indent -compact +.It +PowerBook3,3 +.It +PowerBook4,1 +.It +PowerMac3,4 +.It +PowerMac3,5 +.It +PowerMac4,2 +.It +PowerMac4,5 +.El +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Tsubai Masanari +and ported to +.Ox +by +.An Brad Smith . +.Sh BUGS +This driver needs more testing. +.Pp +This manual page needs more precision and detail. diff --git a/static/openbsd/man4/man4.macppc/xlights.4 b/static/openbsd/man4/man4.macppc/xlights.4 new file mode 100644 index 00000000..1f42ccf8 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/xlights.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: xlights.4,v 1.4 2022/03/31 17:27:22 naddy Exp $ +.\" +.\" Copyright (c) 2007 Gordon Willem Klok +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt XLIGHTS 4 macppc +.Os +.Sh NAME +.Nm xlights +.Nd Xserve G4 and G5 front panel LEDs +.Sh SYNOPSIS +.Cd "xlights* at macobio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the on-board i2s virtual sound device +that drives the front panel LEDs of Apple G4 and G5 Xserve machines. +.Pp +The lights provide an indication of system load and health. +System load is indicated by three dots travelling in a ring around the sixteen +LEDs found on the front panel. +When the system is lightly loaded, these dots travel quickly and slow down +as system load increases. +System health is indicated by the absence of the dots which +means a hung machine or one that is in +.Xr ddb 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr macobio 4 diff --git a/static/openbsd/man4/man4.macppc/zs.4 b/static/openbsd/man4/man4.macppc/zs.4 new file mode 100644 index 00000000..0d7d1237 --- /dev/null +++ b/static/openbsd/man4/man4.macppc/zs.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: zs.4,v 1.8 2015/11/23 10:37:20 mpi Exp $ +.\" +.\" Copyright (c) 1998 The OpenBSD Project +.\" All rights reserved. +.\" +.\" +.Dd $Mdocdate: November 23 2015 $ +.Dt ZS 4 macppc +.Os +.Sh NAME +.Nm zs , +.Nm zstty +.Nd Zilog 8530 (ZSCC) serial communications driver +.Sh SYNOPSIS +.Cd "zs* at macobio?" +.Cd "zstty* at zs?" +.Sh DESCRIPTION +The +.Nm +is a Zilog 8530 serial interface chip used in +.Tn Sun +workstations and +.Tn Apple +Macintosh systems. +On most newer Macintosh systems, the first port +tty00 +is connected to the internal modem. +The second port is either not connected, or may be connected to +an IRDA device (untested). +It is possible to replace the internal modem on some system with +a real serial port using third party hardware adapters. +.Pp +The +.Nm +driver supports all of the standard +.Xr tty 4 +ioctl calls. +The status of the DTR, RTS, CTS, and DCD signals can be queried with +TIOCMGET command, but, due to limitations in the hardware, +only the DTR and RTS signals can be modified with TIOCMSET, TIOCMBIC, +and TIOCMBIS +.Xr ioctl 2 +commands. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/tty00 +.It Pa /dev/tty01 +.It Pa /dev/cua00 +.It Pa /dev/cua01 +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr intro 4 , +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Bx 4.4 . +Support for the TIOCM* +.Xr ioctl 2 Ns s +appeared in +.Ox 2.3 . +.Sh BUGS +The +.Nm +driver now supports cua minor devices, but with this known deficiency +in the simultaneous outgoing/incoming aspect of the driver: +The first outgoing connection succeeds, but second and subsequent +connections fail, apparently due to a getty hang. +The hung getty apparently prevents the cua device from being re-opened. diff --git a/static/openbsd/man4/man4.octeon/Makefile b/static/openbsd/man4/man4.octeon/Makefile new file mode 100644 index 00000000..2eb51593 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/Makefile @@ -0,0 +1,26 @@ +MAN = amdcf.4 \ + cnmac.4 \ + intro.4 \ + octboot.4 \ + octcf.4 \ + octcib.4 \ + octcit.4 \ + octciu.4 \ + octcrypto.4 \ + octgmx.4 \ + octgpio.4 \ + octiic.4 \ + octmmc.4 \ + octpcie.4 \ + octpip.4 \ + octrng.4 \ + octrtc.4 \ + octsctl.4 \ + octsmi.4 \ + octuctl.4 \ + octxctl.4 \ + ogx.4 \ + ogxnexus.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.octeon/amdcf.4 b/static/openbsd/man4/man4.octeon/amdcf.4 new file mode 100644 index 00000000..04e082a6 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/amdcf.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: amdcf.4,v 1.4 2020/04/06 00:01:08 pirofti Exp $ +.\" +.\" Copyright (c) 2015 Paul Irofti +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: April 6 2020 $ +.Dt AMDCF 4 octeon +.Os +.Sh NAME +.Nm amdcf +.Nd octeon AMD flash memory driver +.Sh SYNOPSIS +.Cd "amdcf* at iobus?" +.Sh DESCRIPTION +The +.Nm +driver provides access to AMD/Fujitsu flash memory devices found on +D-Link OCTEON machines. +.Pp +The driver implementation follows the CFI specification and +currently has write support disabled. +.Sh SEE ALSO +.Xr intro 4 , +.Xr octcf 4 , +.Xr sd 4 , +.Xr wd 4 , +.Xr disklabel 5 , +.Xr disklabel 8 , +.Xr fdisk 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Paul Irofti Aq Mt paul@irofti.net +with parts taken from the +.Fx +cfi driver. diff --git a/static/openbsd/man4/man4.octeon/cnmac.4 b/static/openbsd/man4/man4.octeon/cnmac.4 new file mode 100644 index 00000000..e700e1e2 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/cnmac.4 @@ -0,0 +1,86 @@ +.\" $OpenBSD: cnmac.4,v 1.11 2021/02/06 09:33:41 visa Exp $ +.\" +.\" Copyright (c) 2015 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: February 6 2021 $ +.Dt CNMAC 4 octeon +.Os +.Sh NAME +.Nm cnmac +.Nd Cavium OCTEON built-in Ethernet device +.Sh SYNOPSIS +.Cd "cnmac* at octgmx?" +.Sh DESCRIPTION +The +.Nm +driver supports built-in Ethernet ports on Cavium OCTEON CN30xx, +Cavium OCTEON Plus CN50xx, Cavium OCTEON II CN61xx, and +Cavium OCTEON III CN71xx system on chips. +Among the routers based on these chips are the following: +.Pp +.Bl -item -offset indent -compact +.It +D-Link DSR-500 +.It +Netgear ProSecure UTM25 +.It +Portwell CAM-0100 +.It +Rhino Labs Inc. SDNA Shasta +.It +Rhino Labs Inc. SDNA-7130 +.It +Ubiquiti Networks EdgeRouter +.It +Ubiquiti Networks EdgeRouter 4 +.It +Ubiquiti Networks EdgeRouter 6 +.It +Ubiquiti Networks EdgeRouter LITE +.It +Ubiquiti Networks EdgeRouter PoE +.It +Ubiquiti Networks EdgeRouter PRO +.It +Ubiquiti Networks UniFi Security Gateway +.It +Ubiquiti Networks UniFi Security Gateway PRO-4 +.El +.Pp +The +.Nm +driver supports TCP/UDP checksum offload on IPv4/IPv6 reception and +transmission, and IPv4 checksum offload on reception. +The driver additionally supports jumbo frames. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr octgmx 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Internet Initiative Japan Inc . diff --git a/static/openbsd/man4/man4.octeon/intro.4 b/static/openbsd/man4/man4.octeon/intro.4 new file mode 100644 index 00000000..6b5a3012 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/intro.4 @@ -0,0 +1,111 @@ +.\" $OpenBSD: intro.4,v 1.2 2022/03/31 17:27:22 naddy Exp $ +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt INTRO 4 octeon +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the +octeon +platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width "cardbus(4)XX" -offset 3n -compact +.It Xr onewire 4 +1-Wire bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr usb 4 +introduction to Universal Serial Bus support +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The +octeon +.Nm intro +first appeared in +.Ox 7.0 . diff --git a/static/openbsd/man4/man4.octeon/octboot.4 b/static/openbsd/man4/man4.octeon/octboot.4 new file mode 100644 index 00000000..819790fa --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octboot.4 @@ -0,0 +1,62 @@ +.\" $OpenBSD: octboot.4,v 1.2 2020/10/10 10:11:54 visa Exp $ +.\" +.\" Copyright (c) 2020 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 10 2020 $ +.Dt OCTBOOT 4 octeon +.Os +.Sh NAME +.Nm octboot +.Nd kernel boot interface +.Sh SYNOPSIS +.Cd "pseudo-device octboot" +.Sh DESCRIPTION +The +.Nm +driver provides an +.Xr ioctl 2 +interface for booting into another kernel from the currently running kernel. +.Sh IOCTL INTERFACE +.Nm +provides the following +.Xr ioctl 2 +commands, available through +.In machine/octboot.h : +.Bl -tag -width xxxx +.It Dv OBIOC_GETROOTDEV Fa "char rootdev[PATH_MAX]" +Get the name of the current root device. +.It Dv OBIOC_KEXEC "struct octboot_kexec_args *args" +Boot into the given kernel image. +.Bd -literal +struct octboot_kexec_args { + char *kimg; + size_t klen; + char *argv[OCTBOOT_MAX_ARGS]; +}; +.Ed +.El +.Sh FILES +.Bl -tag -width /dev/octboot -compact +.It Pa /dev/octboot +boot interface device. +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . diff --git a/static/openbsd/man4/man4.octeon/octcf.4 b/static/openbsd/man4/man4.octeon/octcf.4 new file mode 100644 index 00000000..97daa564 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octcf.4 @@ -0,0 +1,39 @@ +.\" $OpenBSD: octcf.4,v 1.1 2019/04/25 15:22:22 visa Exp $ +.\" +.\" Copyright (c) 2019 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 25 2019 $ +.Dt OCTCF 4 octeon +.Os +.Sh NAME +.Nm octcf +.Nd OCTEON CompactFlash memory driver +.Sh SYNOPSIS +.Cd "octcf* at iobus?" +.Sh DESCRIPTION +The +.Nm +driver provides access to CompactFlash memory devices on OCTEON boot bus. +.Sh SEE ALSO +.Xr amdcf 4 , +.Xr intro 4 , +.Xr disklabel 5 , +.Xr disklabel 8 , +.Xr fdisk 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.9 . diff --git a/static/openbsd/man4/man4.octeon/octcib.4 b/static/openbsd/man4/man4.octeon/octcib.4 new file mode 100644 index 00000000..b09c643c --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octcib.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: octcib.4,v 1.2 2017/08/06 05:49:12 visa Exp $ +.\" +.\" Copyright (c) 2017 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2017 $ +.Dt OCTCIB 4 octeon +.Os +.Sh NAME +.Nm octcib +.Nd Cavium interrupt bus widget +.Sh SYNOPSIS +.Cd "octcib* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Cavium interrupt bus (CIB) widget, +which is an auxiliary interrupt controller on the CN70xx and CN71xx +system on chips. +.Sh SEE ALSO +.Xr octcit 4 , +.Xr octciu 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . diff --git a/static/openbsd/man4/man4.octeon/octcit.4 b/static/openbsd/man4/man4.octeon/octcit.4 new file mode 100644 index 00000000..239313cd --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octcit.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: octcit.4,v 1.2 2017/08/06 05:49:12 visa Exp $ +.\" +.\" Copyright (c) 2017 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2017 $ +.Dt OCTCIT 4 octeon +.Os +.Sh NAME +.Nm octcit +.Nd OCTEON central interrupt unit version 3 +.Sh SYNOPSIS +.Cd "octcit* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON central interrupt unit version 3 (CIU3). +The CIU3 is present at least on the following system on chips: +.Pp +.Bl -item -offset indent -compact +.It +CN72xx +.It +CN73xx +.It +CN77xx +.It +CN78xx +.El +.Sh SEE ALSO +.Xr octcib 4 , +.Xr octciu 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . diff --git a/static/openbsd/man4/man4.octeon/octciu.4 b/static/openbsd/man4/man4.octeon/octciu.4 new file mode 100644 index 00000000..e44df6af --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octciu.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: octciu.4,v 1.2 2017/08/06 05:49:12 visa Exp $ +.\" +.\" Copyright (c) 2017 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2017 $ +.Dt OCTCIU 4 octeon +.Os +.Sh NAME +.Nm octciu +.Nd OCTEON central interrupt unit +.Sh SYNOPSIS +.Cd "octciu* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON central interrupt unit (CIU). +The CIU is present at least on the following system on chips: +.Pp +.Bl -item -offset indent -compact +.It +CN3xxx +.It +CN5xxx +.It +CN60xx +.It +CN61xx +.It +CN70xx +.It +CN71xx +.El +.Sh SEE ALSO +.Xr octcib 4 , +.Xr octcit 4 +.Sh HISTORY +Control code for the CIU first appeared in +.Ox 5.4 . diff --git a/static/openbsd/man4/man4.octeon/octcrypto.4 b/static/openbsd/man4/man4.octeon/octcrypto.4 new file mode 100644 index 00000000..b950c8ad --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octcrypto.4 @@ -0,0 +1,61 @@ +.\" $OpenBSD: octcrypto.4,v 1.1 2018/04/09 13:48:26 visa Exp $ +.\" +.\" Copyright (c) 2018 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 9 2018 $ +.Dt OCTCRYPTO 4 octeon +.Os +.Sh NAME +.Nm octcrypto +.Nd OCTEON cryptographic unit +.Sh SYNOPSIS +.Cd "octcrypto0 at mainbus0" +.Sh DESCRIPTION +The +.Nm +driver utilizes the OCTEON cryptographic unit to provide +a hardware-accelerated implementation of the following algorithms +for +.Xr ipsec 4 : +.Pp +.Bl -item -offset indent -compact +.It +AES-CBC +.It +AES-CTR +.It +AES-GCM +.It +AES-GMAC +.It +HMAC-MD5 +.It +HMAC-SHA1 +.It +HMAC-SHA2-256 +.It +HMAC-SHA2-384 +.It +HMAC-SHA2-512 +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr ipsec 4 , +.Xr crypto 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . diff --git a/static/openbsd/man4/man4.octeon/octgmx.4 b/static/openbsd/man4/man4.octeon/octgmx.4 new file mode 100644 index 00000000..004fe32b --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octgmx.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: octgmx.4,v 1.1 2019/09/28 22:20:45 deraadt Exp $ +.\" +.\" Copyright (c) 2019 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 28 2019 $ +.Dt OCTGMX 4 octeon +.Os +.Sh NAME +.Nm octgmx +.Nd OCTEON packet interface +.Sh SYNOPSIS +.Cd "octgmx* at octpip?" +.Cd "cnmac* at octgmx?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON packet interface. +.Sh SEE ALSO +.Xr cnmac 4 , +.Xr intro 4 , +.Xr octpip 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.4 . diff --git a/static/openbsd/man4/man4.octeon/octgpio.4 b/static/openbsd/man4/man4.octeon/octgpio.4 new file mode 100644 index 00000000..2bdf0a62 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octgpio.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: octgpio.4,v 1.1 2019/01/12 17:07:16 visa Exp $ +.\" +.\" Copyright (c) 2019 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 12 2019 $ +.Dt OCTGPIO 4 octeon +.Os +.Sh NAME +.Nm octgpio +.Nd OCTEON GPIO controller +.Sh SYNOPSIS +.Cd "octgpio* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON GPIO controller. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.5 . diff --git a/static/openbsd/man4/man4.octeon/octiic.4 b/static/openbsd/man4/man4.octeon/octiic.4 new file mode 100644 index 00000000..1059ce92 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octiic.4 @@ -0,0 +1,40 @@ +.\" $OpenBSD: octiic.4,v 1.1 2019/04/23 13:56:51 visa Exp $ +.\" +.\" Copyright (c) 2019 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 23 2019 $ +.Dt OCTIIC 4 octeon +.Os +.Sh NAME +.Nm octiic +.Nd OCTEON two-wire serial interface +.Sh SYNOPSIS +.Cd "octiic* at fdt?" +.Cd "iic* at octiic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON two-wire serial interface +for use with the +.Xr iic 4 +framework. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . diff --git a/static/openbsd/man4/man4.octeon/octmmc.4 b/static/openbsd/man4/man4.octeon/octmmc.4 new file mode 100644 index 00000000..2d2cb317 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octmmc.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: octmmc.4,v 1.3 2017/07/10 16:31:29 visa Exp $ +.\" +.\" Copyright (c) 2016 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 10 2017 $ +.Dt OCTMMC 4 octeon +.Os +.Sh NAME +.Nm octmmc +.Nd OCTEON MMC host controller +.Sh SYNOPSIS +.Cd "octmmc* at fdt?" +.Cd "sdmmc* at octmmc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON MMC host controller, +which provides an interface to the +.Xr sdmmc 4 +bus. +.Sh SEE ALSO +.Xr sdmmc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh BUGS +SDIO interrupts are not supported. diff --git a/static/openbsd/man4/man4.octeon/octpcie.4 b/static/openbsd/man4/man4.octeon/octpcie.4 new file mode 100644 index 00000000..f277df5e --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octpcie.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: octpcie.4,v 1.2 2019/10/07 14:59:59 visa Exp $ +.\" +.\" Copyright (c) 2019 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 7 2019 $ +.Dt OCTPCIE 4 octeon +.Os +.Sh NAME +.Nm octpcie +.Nd OCTEON PCIe controller +.Sh SYNOPSIS +.Cd "octpcie* at iobus?" +.Cd "pci* at octpcie?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON PCIe controller found +on OCTEON II and III. +It provides a host interface to the +.Xr pci 4 +bus. +.Sh DIAGNOSTICS +.Bl -diag +.It "octpcie0 port N: link timeout" +The PCIe link did not establish. +This happens if the PCIe slot is empty. +.It "octpcie0 port N: reset timeout" +The PCIe port failed to reset. +This can happen if the PCIe port has not been wired. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . diff --git a/static/openbsd/man4/man4.octeon/octpip.4 b/static/openbsd/man4/man4.octeon/octpip.4 new file mode 100644 index 00000000..eaa0a975 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octpip.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: octpip.4,v 1.3 2020/09/08 15:48:14 visa Exp $ +.\" +.\" Copyright (c) 2019 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2020 $ +.Dt OCTPIP 4 octeon +.Os +.Sh NAME +.Nm octpip +.Nd OCTEON packet input processing unit +.Sh SYNOPSIS +.Cd "octpip* at fdt?" +.Cd "octgmx* at octpip?" +.Sh DESCRIPTION +The +.Nm +driver provides an attachment point for OCTEON packet interfaces. +.Sh SEE ALSO +.Xr intro 4 , +.Xr octgmx 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . diff --git a/static/openbsd/man4/man4.octeon/octrng.4 b/static/openbsd/man4/man4.octeon/octrng.4 new file mode 100644 index 00000000..d7b75550 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octrng.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: octrng.4,v 1.5 2020/04/06 00:01:08 pirofti Exp $ +.\" +.\" Copyright (c) 2013 Paul Irofti +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: April 6 2020 $ +.Dt OCTRNG 4 octeon +.Os +.Sh NAME +.Nm octrng +.Nd octeon random number generator +.Sh SYNOPSIS +.Cd "octrng* at iobus?" +.Sh DESCRIPTION +The +.Nm +driver supports the random number generator found on the CN50XX chip. +.Pp +After the 5 seconds it takes for the device to be initialized, the +.Nm +driver feeds the random subsystem's entropy pool 32 bits of data every +10 milliseconds through the +.Xr enqueue_randomness 9 +API. +.Sh SEE ALSO +.Xr intro 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Paul Irofti Aq Mt paul@irofti.net . diff --git a/static/openbsd/man4/man4.octeon/octrtc.4 b/static/openbsd/man4/man4.octeon/octrtc.4 new file mode 100644 index 00000000..191b4714 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octrtc.4 @@ -0,0 +1,62 @@ +.\" $OpenBSD: octrtc.4,v 1.5 2020/06/26 18:48:31 cheloha Exp $ +.\" +.\" Copyright (c) 2014 Paul Irofti +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: June 26 2020 $ +.Dt OCTRTC 4 octeon +.Os +.Sh NAME +.Nm octrtc +.Nd time-of-day clock +.Sh SYNOPSIS +.Cd "octrtc* at mainbus?" +.Sh DESCRIPTION +The +.Nm +driver supports the low resolution DS1337 time-of-day clock found on some +of the octeon models. +The clock has a resolution of 1 second. +.Pp +The +.Nm +driver is used for getting and setting the system time. +.Sh HARDWARE +Supported models: +.Bl -tag -width Ds -offset indent -compact +.It D-Link DSR-500 +.It Portwell CAM-0100 +.El +.Pp +Known models missing a DS1377 clock: +.Bl -tag -width Ds -offset indent -compact +.It Ubiquiti Networks EdgeRouter Lite +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr gettime 9 , +.Xr inittodr 9 , +.Xr resettodr 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Paul Irofti Aq Mt paul@irofti.net . diff --git a/static/openbsd/man4/man4.octeon/octsctl.4 b/static/openbsd/man4/man4.octeon/octsctl.4 new file mode 100644 index 00000000..eabe7ede --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octsctl.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: octsctl.4,v 1.1 2017/07/28 14:56:41 visa Exp $ +.\" +.\" Copyright (c) 2017 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 28 2017 $ +.Dt OCTSCTL 4 octeon +.Os +.Sh NAME +.Nm octsctl +.Nd OCTEON SATA controller bridge +.Sh SYNOPSIS +.Cd "octsctl* at fdt?" +.Cd "ahci* at octsctl?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON SATA controller bridge. +The bridge connects the system's I/O bus and a SATA controller. +.Sh SEE ALSO +.Xr ahci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . diff --git a/static/openbsd/man4/man4.octeon/octsmi.4 b/static/openbsd/man4/man4.octeon/octsmi.4 new file mode 100644 index 00000000..6ed17728 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octsmi.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: octsmi.4,v 1.1 2019/10/01 15:44:32 visa Exp $ +.\" +.\" Copyright (c) 2019 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 1 2019 $ +.Dt OCTSMI 4 octeon +.Os +.Sh NAME +.Nm octsmi +.Nd OCTEON system management interface +.Sh SYNOPSIS +.Cd "octsmi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON system management interface. +This interface connects the OCTEON SoC with external Ethernet PHYs. +.Sh SEE ALSO +.Xr cnmac 4 , +.Xr intro 4 , +.Xr mii 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.4 . diff --git a/static/openbsd/man4/man4.octeon/octuctl.4 b/static/openbsd/man4/man4.octeon/octuctl.4 new file mode 100644 index 00000000..9c525a6d --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octuctl.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: octuctl.4,v 1.1 2016/09/18 21:20:42 schwarze Exp $ +.\" +.\" Copyright (c) 2016 Rafael Neves +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 18 2016 $ +.Dt OCTUCTL 4 octeon +.Os +.Sh NAME +.Nm octuctl +.Nd OCTEON II USB controller interface +.Sh SYNOPSIS +.Cd "octuctl0 at iobus? irq 56" +.Cd "ehci0 at octuctl?" +.Cd "ohci0 at octuctl?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON II USB controller interface, +which provides an interface to +.Xr ehci 4 +and +.Xr ohci 4 +devices. +.Sh SEE ALSO +.Xr ehci 4 , +.Xr ohci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . diff --git a/static/openbsd/man4/man4.octeon/octxctl.4 b/static/openbsd/man4/man4.octeon/octxctl.4 new file mode 100644 index 00000000..ee4782b6 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/octxctl.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: octxctl.4,v 1.1 2017/08/01 16:21:54 visa Exp $ +.\" +.\" Copyright (c) 2017 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 1 2017 $ +.Dt OCTXCTL 4 octeon +.Os +.Sh NAME +.Nm octxctl +.Nd OCTEON USB3 controller bridge +.Sh SYNOPSIS +.Cd "octxctl* at fdt?" +.Cd "xhci* at octxctl?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OCTEON USB3 controller bridge. +The bridge connects the system's I/O bus and a USB3 controller. +.Sh SEE ALSO +.Xr xhci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . diff --git a/static/openbsd/man4/man4.octeon/ogx.4 b/static/openbsd/man4/man4.octeon/ogx.4 new file mode 100644 index 00000000..b1ce6147 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/ogx.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: ogx.4,v 1.2 2020/12/31 09:57:23 visa Exp $ +.\" +.\" Copyright (c) 2019 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: December 31 2020 $ +.Dt OGX 4 octeon +.Os +.Sh NAME +.Nm ogx +.Nd OCTEON III built-in Ethernet device +.Sh SYNOPSIS +.Cd "ogx* at ogxnexus?" +.Sh DESCRIPTION +The +.Nm +driver supports built-in Ethernet ports on the OCTEON III network processor. +.Pp +The +.Nm +driver utilizes IPv4 and TCP/UDP checksum offload on transmission. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr ogxnexus 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . diff --git a/static/openbsd/man4/man4.octeon/ogxnexus.4 b/static/openbsd/man4/man4.octeon/ogxnexus.4 new file mode 100644 index 00000000..1eb18ad9 --- /dev/null +++ b/static/openbsd/man4/man4.octeon/ogxnexus.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: ogxnexus.4,v 1.1 2019/11/05 14:27:59 visa Exp $ +.\" +.\" Copyright (c) 2019 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: November 5 2019 $ +.Dt OGXNEXUS 4 octeon +.Os +.Sh NAME +.Nm ogxnexus +.Nd OCTEON III Ethernet nexus +.Sh SYNOPSIS +.Cd "ogxnexus* at fdt?" +.Cd "ogx* at ogxnexus?" +.Sh DESCRIPTION +The +.Nm +driver provides an attachment point for instances of the +.Xr ogx 4 +driver. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr ogx 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . diff --git a/static/openbsd/man4/man4.powerpc64/Makefile b/static/openbsd/man4/man4.powerpc64/Makefile new file mode 100644 index 00000000..4b0cdf07 --- /dev/null +++ b/static/openbsd/man4/man4.powerpc64/Makefile @@ -0,0 +1,12 @@ +MAN = astfb.4 \ + intro.4 \ + opal.4 \ + opalcons.4 \ + opalsens.4 \ + phb.4 \ + xicp.4 \ + xics.4 \ + xive.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.powerpc64/astfb.4 b/static/openbsd/man4/man4.powerpc64/astfb.4 new file mode 100644 index 00000000..fb1211a1 --- /dev/null +++ b/static/openbsd/man4/man4.powerpc64/astfb.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: astfb.4,v 1.2 2020/10/03 18:18:44 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 3 2020 $ +.Dt ASTFB 4 powerpc64 +.Os +.Sh NAME +.Nm astfb +.Nd Aspeed BMC frame buffer +.Sh SYNOPSIS +.Cd "astfb* at pci?" +.Cd "wsdisplay* at astfb?" +.Sh DESCRIPTION +The +.Nm +driver supports the frame buffer set up by firmware +on systems with an Aspeed Baseboard Management Controller (BMC). +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.powerpc64/intro.4 b/static/openbsd/man4/man4.powerpc64/intro.4 new file mode 100644 index 00000000..b8bc13fd --- /dev/null +++ b/static/openbsd/man4/man4.powerpc64/intro.4 @@ -0,0 +1,109 @@ +.\" $OpenBSD: intro.4,v 1.3 2022/03/31 17:27:22 naddy Exp $ +.\" +.\" Copyright (c) 2014 Sylvestre Gallon +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt INTRO 4 powerpc64 +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the powerpc64 +platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The configuration system is described in +.Xr autoconf 4 . +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width 8n -offset 3n -compact +.It Xr pci 4 +introduction to PCI bus support +.It Xr usb 4 +introduction to Universal Serial Bus support +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The +powerpc64 +.Nm +first appeared in +.Ox 6.9 . diff --git a/static/openbsd/man4/man4.powerpc64/opal.4 b/static/openbsd/man4/man4.powerpc64/opal.4 new file mode 100644 index 00000000..b556e388 --- /dev/null +++ b/static/openbsd/man4/man4.powerpc64/opal.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: opal.4,v 1.1 2020/10/03 18:27:41 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 3 2020 $ +.Dt OPAL 4 powerpc64 +.Os +.Sh NAME +.Nm opal +.Nd OPAL OpenPower Abstraction Layer +.Sh SYNOPSIS +.Cd "opal* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OPAL firmware found on PowerNV systems. +.Sh SEE ALSO +.Xr intro 4 , +.Xr opalcons 4 , +.Xr opalsens 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.powerpc64/opalcons.4 b/static/openbsd/man4/man4.powerpc64/opalcons.4 new file mode 100644 index 00000000..46ec0467 --- /dev/null +++ b/static/openbsd/man4/man4.powerpc64/opalcons.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: opalcons.4,v 1.1 2020/10/03 18:27:41 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 3 2020 $ +.Dt OPALSENS 4 powerpc64 +.Os +.Sh NAME +.Nm opalcons +.Nd OPAL console +.Sh SYNOPSIS +.Cd "opalcons* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the console provided by the OPAL firmware +found on PowerNV systems. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/opalcons0 +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr opal 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.powerpc64/opalsens.4 b/static/openbsd/man4/man4.powerpc64/opalsens.4 new file mode 100644 index 00000000..88bdc862 --- /dev/null +++ b/static/openbsd/man4/man4.powerpc64/opalsens.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: opalsens.4,v 1.1 2020/10/03 18:27:41 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 3 2020 $ +.Dt OPALSENS 4 powerpc64 +.Os +.Sh NAME +.Nm opalsens +.Nd OPAL sensor +.Sh SYNOPSIS +.Cd "opalsens* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for sensors provided by the OPAL firmware +found on PowerNV systems. +.Sh SEE ALSO +.Xr intro 4 , +.Xr opal 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.powerpc64/phb.4 b/static/openbsd/man4/man4.powerpc64/phb.4 new file mode 100644 index 00000000..78d8f88e --- /dev/null +++ b/static/openbsd/man4/man4.powerpc64/phb.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: phb.4,v 1.2 2020/10/03 22:35:32 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECI`AL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 3 2020 $ +.Dt PHB 4 powerpc64 +.Os +.Sh NAME +.Nm phb +.Nd IODA PCIe host bridge +.Sh SYNOPSIS +.Cd "phb* at fdt?" +.Cd "pci* at phb?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCIe host bridges conforming to the IODA2 +and IODA3 specifications, as found on POWER CPUs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.powerpc64/xicp.4 b/static/openbsd/man4/man4.powerpc64/xicp.4 new file mode 100644 index 00000000..5291cc8b --- /dev/null +++ b/static/openbsd/man4/man4.powerpc64/xicp.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: xicp.4,v 1.1 2020/10/03 18:17:09 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 3 2020 $ +.Dt XICP 4 powerpc64 +.Os +.Sh NAME +.Nm xicp +.Nd XICP interrupt controller presenter +.Sh SYNOPSIS +.Cd "xicp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the XICP interrupt controller presenter found +on POWER CPUs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr xics 4 , +.Xr xive 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.powerpc64/xics.4 b/static/openbsd/man4/man4.powerpc64/xics.4 new file mode 100644 index 00000000..753def7a --- /dev/null +++ b/static/openbsd/man4/man4.powerpc64/xics.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: xics.4,v 1.1 2020/10/03 18:17:09 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 3 2020 $ +.Dt XICS 4 powerpc64 +.Os +.Sh NAME +.Nm xics +.Nd XICS interrupt source controller +.Sh SYNOPSIS +.Cd "xics* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the XICS interrupt source controller found +on POWER CPUs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr xicp 4 , +.Xr xive 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.powerpc64/xive.4 b/static/openbsd/man4/man4.powerpc64/xive.4 new file mode 100644 index 00000000..8e1014de --- /dev/null +++ b/static/openbsd/man4/man4.powerpc64/xive.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: xive.4,v 1.1 2020/10/03 18:17:09 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 3 2020 $ +.Dt XIVE 4 powerpc64 +.Os +.Sh NAME +.Nm xive +.Nd XIVE interrupt controller +.Sh SYNOPSIS +.Cd "xive* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the XIVE interrupt controller found on +POWER9 CPUs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr xicp 4 , +.Xr xics 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/Makefile b/static/openbsd/man4/man4.riscv64/Makefile new file mode 100644 index 00000000..a0fd346e --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/Makefile @@ -0,0 +1,25 @@ +MAN = intro.4 \ + mpfclock.4 \ + mpfgpio.4 \ + mpfiic.4 \ + plic.4 \ + sfcc.4 \ + sfclock.4 \ + sfgpio.4 \ + sfuart.4 \ + sgmsi.4 \ + smtclock.4 \ + smtcomphy.4 \ + smte.4 \ + smtgpio.4 \ + smtiic.4 \ + smtpinctrl.4 \ + smtpmic.4 \ + stfclock.4 \ + stfpcie.4 \ + stfpciephy.4 \ + stfpinctrl.4 \ + stfrng.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.riscv64/intro.4 b/static/openbsd/man4/man4.riscv64/intro.4 new file mode 100644 index 00000000..af8baca6 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/intro.4 @@ -0,0 +1,113 @@ +.\" $OpenBSD: intro.4,v 1.3 2023/05/03 22:03:18 jmc Exp $ +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 3 2023 $ +.Dt INTRO 4 riscv64 +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the +riscv64 +platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width "cardbus(4)XX" -offset 3n -compact +.It Xr iic 4 +Inter IC (I2C) bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr usb 4 +introduction to Universal Serial Bus support +.It Xr virtio 4 +VirtIO support driver +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The +riscv64 +.Nm intro +first appeared in +.Ox 7.0 . diff --git a/static/openbsd/man4/man4.riscv64/mpfclock.4 b/static/openbsd/man4/man4.riscv64/mpfclock.4 new file mode 100644 index 00000000..d750c940 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/mpfclock.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: mpfclock.4,v 1.1 2022/01/05 03:32:43 visa Exp $ +.\" +.\" Copyright (c) 2022 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 5 2022 $ +.Dt MPFCLOCK 4 riscv64 +.Os +.Sh NAME +.Nm mpfclock +.Nd Microchip PolarFire SoC MSS clock controller +.Sh SYNOPSIS +.Cd "mpfclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the clock signals for the integrated components +of PolarFire SoCs. +The driver also provides system reset functionality. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . diff --git a/static/openbsd/man4/man4.riscv64/mpfgpio.4 b/static/openbsd/man4/man4.riscv64/mpfgpio.4 new file mode 100644 index 00000000..b3673574 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/mpfgpio.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: mpfgpio.4,v 1.1 2022/02/18 10:51:43 visa Exp $ +.\" +.\" Copyright (c) 2022 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt MPFGPIO 4 riscv64 +.Os +.Sh NAME +.Nm mpfgpio +.Nd Microchip PolarFire SoC MSS GPIO controller +.Sh SYNOPSIS +.Cd "mpfgpio* at fdt?" +.Cd "gpio* at mpfgpio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Microchip PolarFire SoC MSS GPIO controller. +.Pp +The PolarFire SoC MSS has three GPIO units: +.Dv GPIO_0 , +.Dv GPIO_1 +and +.Dv GPIO_2 . +.Dv GPIO_0 +and +.Dv GPIO_1 +control up to 14 and 24 IOs, respectively. +These IOs are routed through IOMUXes. +.Dv GPIO_2 +controls up to 32 IOs through the FPGA fabric. +.Pp +The IOs can be configured as either inputs or outputs, +and accessed using +.Xr gpioctl 8 . +.Sh SEE ALSO +.Xr gpio 4 , +.Xr intro 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . diff --git a/static/openbsd/man4/man4.riscv64/mpfiic.4 b/static/openbsd/man4/man4.riscv64/mpfiic.4 new file mode 100644 index 00000000..4f16e31a --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/mpfiic.4 @@ -0,0 +1,40 @@ +.\" $OpenBSD: mpfiic.4,v 1.1 2022/02/16 13:07:36 visa Exp $ +.\" +.\" Copyright (c) 2022 Visa Hankala +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 16 2022 $ +.Dt MPFIIC 4 riscv64 +.Os +.Sh NAME +.Nm mpfiic +.Nd Microchip PolarFire SoC MSS I2C controller +.Sh SYNOPSIS +.Cd "mpfiic* at fdt?" +.Cd "iic* at mpfiic?" +.Sh DESCRIPTION +The +.Nm +driver supports the Microchip PolarFire SoC MSS I2C controller +for use with the +.Xr iic 4 +framework. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . diff --git a/static/openbsd/man4/man4.riscv64/plic.4 b/static/openbsd/man4/man4.riscv64/plic.4 new file mode 100644 index 00000000..7a339ea4 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/plic.4 @@ -0,0 +1,28 @@ +.\" $OpenBSD: plic.4,v 1.1 2021/06/18 04:29:09 jsg Exp $ +.\" +.\" Copyright (c) 2021 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2021 $ +.Dt PLIC 4 riscv64 +.Os +.Sh NAME +.Nm plic +.Nd Platform-Level Interrupt Controller +.Sh SYNOPSIS +.Cd "plic* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the RISC-V Platform-Level Interrupt Controller (PLIC). diff --git a/static/openbsd/man4/man4.riscv64/sfcc.4 b/static/openbsd/man4/man4.riscv64/sfcc.4 new file mode 100644 index 00000000..a47c67f5 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/sfcc.4 @@ -0,0 +1,28 @@ +.\" $OpenBSD: sfcc.4,v 1.1 2021/06/18 04:29:09 jsg Exp $ +.\" +.\" Copyright (c) 2021 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2021 $ +.Dt SFCC 4 riscv64 +.Os +.Sh NAME +.Nm sfcc +.Nd SiFive L2 cache controller +.Sh SYNOPSIS +.Cd "sfcc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the SiFive level two cache controller. diff --git a/static/openbsd/man4/man4.riscv64/sfclock.4 b/static/openbsd/man4/man4.riscv64/sfclock.4 new file mode 100644 index 00000000..dc007e22 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/sfclock.4 @@ -0,0 +1,28 @@ +.\" $OpenBSD: sfclock.4,v 1.1 2021/06/18 04:29:09 jsg Exp $ +.\" +.\" Copyright (c) 2021 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2021 $ +.Dt SFCLOCK 4 riscv64 +.Os +.Sh NAME +.Nm sfclock +.Nd SiFive Clock and Reset Control +.Sh SYNOPSIS +.Cd "sfclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the SiFive Power Reset Clocking Interrupt (PRCI). diff --git a/static/openbsd/man4/man4.riscv64/sfgpio.4 b/static/openbsd/man4/man4.riscv64/sfgpio.4 new file mode 100644 index 00000000..3ff90176 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/sfgpio.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: sfgpio.4,v 1.1 2022/05/30 17:44:10 kettenis Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 30 2022 $ +.Dt SFGPIO 4 riscv64 +.Os +.Sh NAME +.Nm sfgpio +.Nd SiFive GPIO controller +.Sh SYNOPSIS +.Cd "sfgpio* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO ports found on SiFive SoCs. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/sfuart.4 b/static/openbsd/man4/man4.riscv64/sfuart.4 new file mode 100644 index 00000000..98d90b9f --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/sfuart.4 @@ -0,0 +1,30 @@ +.\" $OpenBSD: sfuart.4,v 1.3 2021/11/26 03:37:39 jsg Exp $ +.\" +.\" Copyright (c) 2021 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 26 2021 $ +.Dt SFUART 4 riscv64 +.Os +.Sh NAME +.Nm sfuart +.Nd SiFive Universal Asynchronous Receiver/Transmitter +.Sh SYNOPSIS +.Cd "sfuart* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the SiFive Universal Asynchronous Receiver/Transmitter (UART). +.Sh SEE ALSO +.Xr tty 4 diff --git a/static/openbsd/man4/man4.riscv64/sgmsi.4 b/static/openbsd/man4/man4.riscv64/sgmsi.4 new file mode 100644 index 00000000..87ddeec7 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/sgmsi.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: sgmsi.4,v 1.1 2025/12/02 20:03:19 kettenis Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 2 2025 $ +.Dt SGMSI 4 riscv64 +.Os +.Sh NAME +.Nm sgmsi +.Nd Sophgo MSI controller +.Sh SYNOPSIS +.Cd "sgmsi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the MSI implementation found on Sophgo +SG2042 SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/smtclock.4 b/static/openbsd/man4/man4.riscv64/smtclock.4 new file mode 100644 index 00000000..803dceb3 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/smtclock.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: smtclock.4,v 1.1 2026/04/06 10:42:12 kettenis Exp $ +.\" +.\" Copyright (c) 2026 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 6 2026 $ +.Dt SMTCLOCK 4 riscv64 +.Os +.Sh NAME +.Nm smtclock +.Nd SpacemiT clock controller +.Sh SYNOPSIS +.Cd "smtclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the clock signals for integrated components of +SpacemiT SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/smtcomphy.4 b/static/openbsd/man4/man4.riscv64/smtcomphy.4 new file mode 100644 index 00000000..5b9b8ef1 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/smtcomphy.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: smtcomphy.4,v 1.2 2026/04/12 09:17:04 jsg Exp $ +.\" +.\" Copyright (c) 2026 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 12 2026 $ +.Dt SMTCOMPHY 4 riscv64 +.Os +.Sh NAME +.Nm smtcomphy +.Nd SpacemiT PCIe 2.0 and USB 3.0 PHY +.Sh SYNOPSIS +.Cd "smtcomphy* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the PCIe 2.0 and USB 3.0 PHY integrated on SpacemiT +SoCs. +.Sh SEE ALSO +.Xr dwpcie 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/smte.4 b/static/openbsd/man4/man4.riscv64/smte.4 new file mode 100644 index 00000000..94887c08 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/smte.4 @@ -0,0 +1,76 @@ +.\" $OpenBSD: smte.4,v 1.1 2026/04/13 12:20:13 kettenis Exp $ +.\" +.\" Copyright (c) 2026 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 13 2026 $ +.Dt SMTE 4 riscv64 +.Os +.Sh NAME +.Nm smte +.Nd SpacemiT K1 EMAC 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "smte* at fdt?" +.Cd "rgephy*" at mii? +.Cd "ytphy*" at mii? +.Sh DESCRIPTION +The +.Nm +driver provides support the Ethernet controller found on the SpacemiT +K1 SoC. +.Pp +The +.Nm +driver supports several media types, which are selected via the +.Xr ifconfig 8 +command. +The supported media types are: +.Bl -tag -width "media" -offset indent +.It Cm media No autoselect +Attempt to autoselect the media type (default) +.It Cm media No 1000baseT Cm mediaopt No full-duplex +Use 1000baseT on copper, full duplex +.It Cm media No 1000baseT Cm mediaopt No half-duplex +Use 1000baseT on copper, half duplex +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Use 100baseTX, full duplex +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Use 100baseTX, half duplex +.It Cm media No 10baseT Cm mediaopt No full-duplex +Use 10baseT, full duplex +.It Cm media No 10baseT Cm mediaopt No half-duplex +Use 10baseT, half duplex +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr rgephy 4 , +.Xr ytphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/smtgpio.4 b/static/openbsd/man4/man4.riscv64/smtgpio.4 new file mode 100644 index 00000000..a46d6452 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/smtgpio.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: smtgpio.4,v 1.1 2026/04/04 14:12:50 kettenis Exp $ +.\" +.\" Copyright (c) 2026 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 4 2026 $ +.Dt SMTGPIO 4 riscv64 +.Os +.Sh NAME +.Nm smtgpio +.Nd SpacemiT GPIO controller +.Sh SYNOPSIS +.Cd "smtgpio* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO controller found on SpacemiT SoCs. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/smtiic.4 b/static/openbsd/man4/man4.riscv64/smtiic.4 new file mode 100644 index 00000000..011810f3 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/smtiic.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: smtiic.4,v 1.1 2026/04/06 10:46:13 kettenis Exp $ +.\" +.\" Copyright (c) 2026 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 6 2026 $ +.Dt SMTIIC 4 riscv64 +.Os +.Sh NAME +.Nm smtiic +.Nd SpacemiT I2C controller +.Sh SYNOPSIS +.Cd "smtiic* at fdt?" +.Cd "iic* at smtiic?" +.Sh DESCRIPTION +The +.Nm +driver supports the SpacemiT I2C controller for use with the +.Xr iic 4 +framework. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se +and +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/smtpinctrl.4 b/static/openbsd/man4/man4.riscv64/smtpinctrl.4 new file mode 100644 index 00000000..a8e9632a --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/smtpinctrl.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: smtpinctrl.4,v 1.1 2026/04/13 09:25:26 jsg Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 13 2026 $ +.Dt SMTPINCTRL 4 riscv64 +.Os +.Sh NAME +.Nm smtpinctrl +.Nd SpacemiT K1 pin configuration +.Sh SYNOPSIS +.Cd "smtpinctrl* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver uses pin control data from the device tree to configure +pins on the SpacemiT K1 SoC. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/smtpmic.4 b/static/openbsd/man4/man4.riscv64/smtpmic.4 new file mode 100644 index 00000000..a0c2719a --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/smtpmic.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: smtpmic.4,v 1.2 2026/04/12 09:10:03 jsg Exp $ +.\" +.\" Copyright (c) 2026 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 12 2026 $ +.Dt SMTPMIC 4 riscv64 +.Os +.Sh NAME +.Nm smtpmic +.Nd SpacemiT P1 Power Management IC +.Sh SYNOPSIS +.Cd "smtpmic* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the real-time clock in the SpacemiT P1 +Power Management IC. +It also provides a way to reset or shutdown some machines that do not +implement this functionality in their firmware. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/stfclock.4 b/static/openbsd/man4/man4.riscv64/stfclock.4 new file mode 100644 index 00000000..b0971c3f --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/stfclock.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: stfclock.4,v 1.3 2026/04/06 10:41:31 kettenis Exp $ +.\" +.\" Copyright (c) 2022 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 6 2026 $ +.Dt STFCLOCK 4 riscv64 +.Os +.Sh NAME +.Nm stfclock +.Nd StarFive JH7100/JH7110 clock controller +.Sh SYNOPSIS +.Cd "stfclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the clock signals for integrated components of the +StarFive JH7100/JH7110 SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/stfpcie.4 b/static/openbsd/man4/man4.riscv64/stfpcie.4 new file mode 100644 index 00000000..14a623ef --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/stfpcie.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: stfpcie.4,v 1.1 2023/07/08 10:18:34 kettenis Exp $ +.\" +.\" Copyright (c) 2023 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 8 2023 $ +.Dt STFPCIE 4 riscv64 +.Os +.Sh NAME +.Nm stfpcie +.Nd StarFive JH7110 Host/PCIe bridge +.Sh SYNOPSIS +.Cd "stfpcie* at fdt?" +.Cd "pci* at dwpcie?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PLDA XpressRICH-AXI PCIe controller, +which is built into the StarFive JH7110 SoC. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr stfpciephy 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/stfpciephy.4 b/static/openbsd/man4/man4.riscv64/stfpciephy.4 new file mode 100644 index 00000000..ca7cdbb7 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/stfpciephy.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: stfpciephy.4,v 1.1 2023/07/08 10:18:51 kettenis Exp $ +.\" +.\" Copyright (c) 2023 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 8 2023 $ +.Dt STFPCIEPHY 4 riscv64 +.Os +.Sh NAME +.Nm stfpciephy +.Nd StarFive JH7110 PCIe 2.0 and USB 3.0 PHY +.Sh SYNOPSIS +.Cd "stfpciephy* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the PCIe 2.0 and USB 3.0 PHY integrated on the +StarFive JH7110 SoC. +.Sh SEE ALSO +.Xr intro 4 , +.Xr stfpcie 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/stfpinctrl.4 b/static/openbsd/man4/man4.riscv64/stfpinctrl.4 new file mode 100644 index 00000000..ab383cd4 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/stfpinctrl.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: stfpinctrl.4,v 1.3 2023/07/08 10:17:35 kettenis Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 8 2023 $ +.Dt STFPINCTRL 4 riscv64 +.Os +.Sh NAME +.Nm stfpinctrl +.Nd StarFive JH7100/JH7110 pin configuration +.Sh SYNOPSIS +.Cd "stfpinctrl* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver uses pin control data from the device tree to configure +pins on the StarFive JH7100/JH7110 SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.riscv64/stfrng.4 b/static/openbsd/man4/man4.riscv64/stfrng.4 new file mode 100644 index 00000000..a8ad7c07 --- /dev/null +++ b/static/openbsd/man4/man4.riscv64/stfrng.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: stfrng.4,v 1.1 2023/09/23 19:11:00 kettenis Exp $ +.\" +.\" Copyright (c) 2023 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 23 2023 $ +.Dt STFRNG 4 riscv64 +.Os +.Sh NAME +.Nm stfrng +.Nd StarFive JH7110 random number generator +.Sh SYNOPSIS +.Cd "stfrng* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the random number generator found on the +StarFive JH7110 SoC. +.Pp +It feeds the random subsystem's entropy pool with 256 bits of random +data every second. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/Makefile b/static/openbsd/man4/man4.sparc64/Makefile new file mode 100644 index 00000000..58e2b951 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/Makefile @@ -0,0 +1,78 @@ +MAN = agten.4 \ + apio.4 \ + asio.4 \ + audioce.4 \ + audiocs.4 \ + autoconf.4 \ + auxio.4 \ + bbc.4 \ + be.4 \ + beeper.4 \ + bpp.4 \ + bwtwo.4 \ + cbus.4 \ + central.4 \ + cgsix.4 \ + cgthree.4 \ + cgtwelve.4 \ + clkbrd.4 \ + clock.4 \ + cmp.4 \ + comkbd.4 \ + comms.4 \ + core.4 \ + creator.4 \ + ebus.4 \ + ecadc.4 \ + environ.4 \ + esp.4 \ + fhc.4 \ + gfxp.4 \ + ifb.4 \ + intro.4 \ + le.4 \ + led.4 \ + lom.4 \ + machfb.4 \ + magma.4 \ + mem.4 \ + mgx.4 \ + pcons.4 \ + pmc.4 \ + power.4 \ + ppm.4 \ + prtc.4 \ + psycho.4 \ + pyro.4 \ + qe.4 \ + qec.4 \ + radeonfb.4 \ + raptor.4 \ + rfx.4 \ + sab.4 \ + sbbc.4 \ + schizo.4 \ + spif.4 \ + ssm.4 \ + tda.4 \ + tvtwo.4 \ + upa.4 \ + uperf.4 \ + vbus.4 \ + vcc.4 \ + vcons.4 \ + vds.4 \ + vdsk.4 \ + vigra.4 \ + vldc.4 \ + vnet.4 \ + vpci.4 \ + vrng.4 \ + vrtc.4 \ + vsw.4 \ + xbox.4 \ + zs.4 \ + zx.4 + +include ../../../mandoc.mk + diff --git a/static/openbsd/man4/man4.sparc64/agten.4 b/static/openbsd/man4/man4.sparc64/agten.4 new file mode 100644 index 00000000..d6c1e1fa --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/agten.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: agten.4,v 1.8 2008/03/31 08:12:22 jmc Exp $ +.\" Copyright (c) 2003 Miodrag Vallat. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2008 $ +.Dt AGTEN 4 sparc64 +.Os +.Sh NAME +.Nm agten +.Nd Fujitsu AG-10e accelerated 24-bit color frame buffer +.Sh SYNOPSIS +.Cd "agten* at sbus?" +.Cd "wsdisplay* at agten?" +.Sh DESCRIPTION +The +.Tn Fujitsu +AG-10e +is a two-slot SBus color frame buffer, with graphics acceleration +and overlay capabilities, including hardware OpenGL processing. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh CAVEATS +This driver does not support any acceleration features at the moment, and +drives the card in PROM-compatible, 8 bit, mode only. diff --git a/static/openbsd/man4/man4.sparc64/apio.4 b/static/openbsd/man4/man4.sparc64/apio.4 new file mode 100644 index 00000000..c82e5500 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/apio.4 @@ -0,0 +1,63 @@ +.\" $OpenBSD: apio.4,v 1.8 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt APIO 4 sparc64 +.Os +.Sh NAME +.Nm apio +.Nd SBus Aurora pio1 driver +.Sh SYNOPSIS +.Cd "apio* at sbus?" +.Cd "lpt* at apio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Aurora Technologies +.Tn pio1 +parallel port interface, which is basically an +.Xr lpt 4 +port with +.Xr sbus 4 +glue logic. +.Sh SEE ALSO +.Xr intro 4 , +.Xr lpt 4 , +.Xr sbus 4 +.Sh HISTORY +.Ox +support for +.Nm +was added in +.Ox 3.1 . +.Sh AUTHORS +The driver was written by +.An Jason Wright Aq Mt jason@thought.net . +.Sh BUGS +Only revision +.Tn 210sj +is known to work. +Minor work may be necessary for other revisions of this card. diff --git a/static/openbsd/man4/man4.sparc64/asio.4 b/static/openbsd/man4/man4.sparc64/asio.4 new file mode 100644 index 00000000..c3dbbe9f --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/asio.4 @@ -0,0 +1,63 @@ +.\" $OpenBSD: asio.4,v 1.8 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ASIO 4 sparc64 +.Os +.Sh NAME +.Nm asio +.Nd SBus Aurora sio2 driver +.Sh SYNOPSIS +.Cd "asio* at sbus?" +.Cd "com* at asio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Aurora Technologies +.Tn sio2 +serial interface, which is basically a pair of +.Xr com 4 +ports with +.Xr sbus 4 +glue logic. +.Sh SEE ALSO +.Xr com 4 , +.Xr intro 4 , +.Xr sbus 4 +.Sh HISTORY +.Ox +support for +.Nm +was added in +.Ox 3.1 . +.Sh AUTHORS +The driver was written by +.An Jason Wright Aq Mt jason@thought.net . +.Sh BUGS +Only revision +.Tn 210sj +is known to work. +Minor work may be necessary for other revisions of this card. diff --git a/static/openbsd/man4/man4.sparc64/audioce.4 b/static/openbsd/man4/man4.sparc64/audioce.4 new file mode 100644 index 00000000..e81d28bd --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/audioce.4 @@ -0,0 +1,125 @@ +.\" $OpenBSD: audioce.4,v 1.9 2020/05/17 05:48:39 ratchov Exp $ +.\" +.\" Copyright (c) 2001 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 17 2020 $ +.Dt AUDIOCE 4 sparc64 +.Os +.Sh NAME +.Nm audioce +.Nd SPARC64 EBus CS4231 audio device +.Sh SYNOPSIS +.Cd "audioce* at ebus?" +.Cd "audio* at audioce?" +.Sh DESCRIPTION +The +.Nm +device uses the +.Tn Crystal Semiconductor +CS4231A +Parallel Interface, Multimedia Audio Codec +chip to implement the audio device interface described in +.Xr audio 4 . +This device is found onboard on some PCI/EBus based sparc64 models. +.Pp +The +.Nm +has a maximum precision of 16 bits and has both stereo and monoaural outputs. +.Sh MIXER INTERFACE +The +.Xr audio 4 +interface for +.Nm +provides the following controls: +.Bl -tag -width "outputs.monitor.mute" +.It Cm outputs.dac +Specifies the attenuation of DAC output. +A value of +.Ql 255 +represents 0 dB attenuation. +.It Cm outputs.dac.mute +Specifies whether DAC output is muted. +.It Cm outputs.output +Specifies the set of enabled output ports. +The output ports are: +.Ql line , +the line output jack, +.Ql hp , +the low impedance headphone jack, and +.Ql spkr , +the internal speaker. +Note: Not all systems support disabling the headphone and line output ports. +.It Cm inputs.cd +Specifies the gain applied to CD audio input. +A value of +.Ql 191 +represents 0 dB. +.It Cm inputs.cd.mute +Specifies whether CD audio input is muted. +.It Cm inputs.line +Specifies the gain applied to line input. +A value of +.Ql 191 +represents 0 dB. +.It Cm inputs.line.mute +Specifies whether line input is muted. +.It Cm outputs.monitor +Specifies the attenuation of ADC to DAC output. +A value of +.Ql 255 +represents 0 dB. +.It Cm outputs.monitor.mute +Specifies whether ADC to DAC output is muted. +.It Cm record.volume +Specifies ADC input gain. +A value of +.Ql 0 +represents 0 dB. +.It Cm record.source +Specifies the active input port for the ADC. +The following are valid ADC input ports: +.Ql line , +line input, +.Ql cd , +CD input, +.Ql mic , +microphone input, and +.Ql mixerout , +post-mixer output as heard on the output ports. +.It Cm record.mic_preamp +Specifies whether an additional +20 dB gain is +applied to the ADC's microphone input. +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr audio 4 , +.Xr ebus 4 , +.Xr intro 4 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.sparc64/audiocs.4 b/static/openbsd/man4/man4.sparc64/audiocs.4 new file mode 100644 index 00000000..89a93cff --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/audiocs.4 @@ -0,0 +1,60 @@ +.\" $OpenBSD: audiocs.4,v 1.10 2008/03/31 08:12:22 jmc Exp $ +.\" +.\" Copyright (c) 2001 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2008 $ +.Dt AUDIOCS 4 sparc64 +.Os +.Sh NAME +.Nm audiocs +.Nd SPARC64 CS4231 audio device +.Sh SYNOPSIS +.Cd "audiocs* at sbus?" +.Cd "audio* at audiocs?" +.Sh DESCRIPTION +The +.Nm +device uses the +.Tn Crystal Semiconductor +CS4231A +Parallel Interface, Multimedia Audio Codec +chip to implement the audio device interface described in +.Xr audio 4 . +This device is found onboard on some SBus based sparc64 models. +The +.Nm +has a maximum precision of 16 bits and has both stereo and monoaural outputs. +The output ports are: the internal speaker, line, and headphones. +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr audio 4 , +.Xr intro 4 , +.Xr sbus 4 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.sparc64/autoconf.4 b/static/openbsd/man4/man4.sparc64/autoconf.4 new file mode 100644 index 00000000..bff37fd7 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/autoconf.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: autoconf.4,v 1.4 2007/05/31 19:19:56 jmc Exp $ +.\" +.\" Copyright (c) 1994 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christopher G. Demetriou. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt AUTOCONF 4 sparc64 +.Os +.Sh NAME +.Nm autoconf +.Nd diagnostics from the autoconfiguration code +.Sh DESCRIPTION +When +.Ox +bootstraps it probes the innards of the machine +on which it is running +and locates controllers, drives, and other devices, printing out +what it finds on the console. +This procedure is driven by a system configuration table which is processed by +.Xr config 8 +and compiled into each kernel. +Devices which exist in the machine but are not configured into the +kernel may not be detected. +.Sh SEE ALSO +.Xr intro 4 , +.Xr boot_sparc64 8 , +.Xr config 8 diff --git a/static/openbsd/man4/man4.sparc64/auxio.4 b/static/openbsd/man4/man4.sparc64/auxio.4 new file mode 100644 index 00000000..4d2777b5 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/auxio.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: auxio.4,v 1.7 2018/01/12 04:36:44 deraadt Exp $ +.\" +.\" Copyright (c) 2003 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 12 2018 $ +.Dt AUXIO 4 sparc64 +.Os +.Sh NAME +.Nm auxio +.Nd SPARC64 auxiliary I/O +.Sh SYNOPSIS +.Cd "auxio* at ebus?" +.Cd "auxio* at sbus?" +.Sh DESCRIPTION +The +.Nm +device contains miscellaneous system controls, including the front panel LED. +This LED can be made to blink based on the load average on most systems +by setting the +.Xr sysctl 2 +variable +.Ar machdep.led_blink +to a non-zero value. +Internally, various status bits for some of the onboard devices are +found in +.Nm auxio . +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr ebus 4 , +.Xr intro 4 , +.Xr sbus 4 diff --git a/static/openbsd/man4/man4.sparc64/bbc.4 b/static/openbsd/man4/man4.sparc64/bbc.4 new file mode 100644 index 00000000..b425c388 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/bbc.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: bbc.4,v 1.5 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2007 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt BBC 4 sparc64 +.Os +.Sh NAME +.Nm bbc +.Nd SPARC64 BootBus Controller +.Sh SYNOPSIS +.Cd "bbc* at ebus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the BootBus Controllers found on +UltraSPARC III systems. +.Pp +The +.Nm +driver configures the system to do a full system reset when the +watchdog timer provided by +.Xr pmc 4 +expires. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pmc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/be.4 b/static/openbsd/man4/man4.sparc64/be.4 new file mode 100644 index 00000000..41739b99 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/be.4 @@ -0,0 +1,72 @@ +.\" $OpenBSD: be.4,v 1.12 2022/03/21 14:56:16 miod Exp $ +.\" +.\" Copyright (c) 1998 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 21 2022 $ +.Dt BE 4 sparc64 +.Os +.Sh NAME +.Nm be +.Nd SPARC64 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "qec* at sbus?" +.Cd "be* at qec?" +.Sh DESCRIPTION +The +.Nm +interface provides access to the 10Mb/s and 100Mb/s (half duplex only) +Ethernet networks. +The +.Nm +is found on the Sun 10/100 Mbit Ethernet boards +(Sun part number SUNW,501-2655). +.Pp +The +.Nm +is not capable of link autonegotiation, so a media type must be specified +with +.Xr ifconfig 8 . +The supported media types are: +.Bl -tag -width xxxxxxxxxx -offset indent +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Use 100Mbps, half duplex +.It Cm media No 10baseT Cm mediaopt No half-duplex +Use 10Mbps, half duplex +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr qec 4 , +.Xr sbus 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.sparc64/beeper.4 b/static/openbsd/man4/man4.sparc64/beeper.4 new file mode 100644 index 00000000..842531b1 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/beeper.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: beeper.4,v 1.7 2015/11/21 08:04:20 jmc Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 21 2015 $ +.Dt BEEPER 4 sparc64 +.Os +.Sh NAME +.Nm beeper , +.Nm beep +.Nd console annunciator +.Sh SYNOPSIS +.Cd "beeper* at ebus?" +.Cd "beep* at ebus?" +.Sh DESCRIPTION +The +.Nm +device does exactly what it sounds like: it beeps. +In particular, this device registers itself to handle beeping for +.Xr pckbd 4 +or +.Xr ukbd 4 +devices. +.Sh SEE ALSO +.Xr ebus 4 , +.Xr intro 4 , +.Xr pckbd 4 , +.Xr ukbd 4 +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.sparc64/bpp.4 b/static/openbsd/man4/man4.sparc64/bpp.4 new file mode 100644 index 00000000..9402c68d --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/bpp.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: bpp.4,v 1.4 2014/01/21 03:15:46 schwarze Exp $ +.\" +.\" Copyright (c) 2003 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 21 2014 $ +.Dt BPP 4 sparc64 +.Os +.Sh NAME +.Nm bpp +.Nd parallel port +.Sh SYNOPSIS +.Cd "bpp0 at sbus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the built-in parallel port. +It only supports writing data to the device. +.Sh FILES +.Bl -tag -width tenletters -compact +.It Pa /dev/bpp +parallel port device +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 diff --git a/static/openbsd/man4/man4.sparc64/bwtwo.4 b/static/openbsd/man4/man4.sparc64/bwtwo.4 new file mode 100644 index 00000000..bb3573bd --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/bwtwo.4 @@ -0,0 +1,54 @@ +.\" $OpenBSD: bwtwo.4,v 1.14 2008/03/31 08:12:22 jmc Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2008 $ +.Dt BWTWO 4 sparc64 +.Os +.Sh NAME +.Nm bwtwo +.Nd monochromatic frame buffer +.Sh SYNOPSIS +.Cd "bwtwo* at sbus?" +.Cd "wsdisplay* at bwtwo?" +.Sh DESCRIPTION +The +.Nm +is an SBus monochrome frame buffer. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/man4.sparc64/cbus.4 b/static/openbsd/man4/man4.sparc64/cbus.4 new file mode 100644 index 00000000..85ad6c10 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/cbus.4 @@ -0,0 +1,60 @@ +.\" $OpenBSD: cbus.4,v 1.7 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt CBUS 4 sparc64 +.Os +.Sh NAME +.Nm cbus +.Nd channel device bus +.Sh SYNOPSIS +.Cd "cbus* at vbus?" +.Sh DESCRIPTION +The +.Nm +driver provides a virtual bus for channel devices provided by the +UltraSPARC Hypervisor as found on sun4v logical domains. +.Pp +.Ox +provides support for the following devices: +.Pp +.Bl -tag -width "vdisk(4)XX" -offset 3n -compact +.It Xr vcc 4 +virtual console concentrator +.It Xr vds 4 +virtual disk server +.It Xr vdsk 4 +virtual disk +.It Xr vldc 4 +virtual channel driver +.It Xr vnet 4 +virtual network interface +.It Xr vsw 4 +virtual network switch +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr vbus 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/central.4 b/static/openbsd/man4/man4.sparc64/central.4 new file mode 100644 index 00000000..f42f5472 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/central.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: central.4,v 1.5 2008/01/18 22:06:01 jmc Exp $ +.\" +.\" Copyright (c) 2004 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 18 2008 $ +.Dt CENTRAL 4 sparc64 +.Os +.Sh NAME +.Nm central +.Nd SPARC64 Central controller +.Sh SYNOPSIS +.Cd "central* at mainbus0" +.Sh DESCRIPTION +The +.Nm +device provides support for the +.Nm +host controller on sparc64 systems, +most often found on Sunfire, Starfire, and Wildfire +UltraSPARC systems. +It provides an attachment point for the main +.Xr fhc 4 +Firehose controller used to control board +level functions on the host. +.Sh SEE ALSO +.Xr fhc 4 , +.Xr intro 4 +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 3.7 . diff --git a/static/openbsd/man4/man4.sparc64/cgsix.4 b/static/openbsd/man4/man4.sparc64/cgsix.4 new file mode 100644 index 00000000..0e3c1529 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/cgsix.4 @@ -0,0 +1,154 @@ +.\" $OpenBSD: cgsix.4,v 1.22 2015/11/01 21:26:48 jmc Exp $ +.\" +.\" Copyright (c) 2001 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 1 2015 $ +.Dt CGSIX 4 sparc64 +.Os +.Sh NAME +.Nm cgsix +.Nd accelerated 8-bit color frame buffer +.Sh SYNOPSIS +.Cd "cgsix* at sbus? flags 0x0" +.Cd "wsdisplay* at cgsix?" +.Sh DESCRIPTION +The +.Nm +is an SBus color frame buffer with graphics acceleration, +commonly found in the non +.Sq creator +SBus UltraSPARC workstations. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Pp +Different models exist, with various memory sizes and capabilities. +The +.Nm +driver supports the four flavours: +.Bl -item -offset indent -compact +.It +GX +.It +GX+ +.It +Turbo GX (or TGX) +.It +Turbo GX+ (or TGX+) +.El +.Pp +By default hardware acceleration is used to erase the screen and +scroll text. +By setting +.Ar flags +to +.Ar 1 +(via +.Xr config 8 +or +.Xr boot_config 8 ) +this acceleration can be disabled. +.Sh DISPLAY RESOLUTION +If the +.Nm +frame buffer is used as the console display, a different resolution than the +default 1152x900 can be selected by changing the OpenPROM environment. +To change the default resolution, type the following: +.Pp +.Em \ ok +setenv +.Em output-device +screen:r1280x1024x76 +.Pp +to change to a 76Hz 1280x1024 resolution. +.Pp +If the +.Nm +frame buffer is a secondary display, or a serial console is used, the +display resolution cannot be changed without using an +.Em nvramrc +OpenPROM script. +Refer to the +.Em Sun Frame Buffer FAQ +for details. +.Pp +The +.Nm +frame buffer accepts the following resolutions: +.Pp +.Bl -tag -width screen:r1280x1024x76 -compact +.It screen:r1024x768x60 +Super VGA 1024x768, with a refresh rate of 60Hz. +Only available on TGX and TGX+. +.It screen:r1024x768x70 +Super VGA 1024x768, with a refresh rate of 70Hz. +Only available on TGX and TGX+. +.It screen:r1024x768x76 +Super VGA 1024x768, with a refresh rate of 76Hz. +Only available on TGX and TGX+. +.It screen:r1024x800x74 +1024x800, with a refresh rate of 74Hz. +Only available on TGX and TGX+. +.It screen:r1024x800x85 +1024x800, with a refresh rate of 85Hz. +Only available on GX+, TGX and TGX+. +.It screen:r1152x900x66 +Standard 1152x900, with a refresh rate of 66Hz. +.It screen:r1152x900x76 +Standard 1152x900, with a refresh rate of 76Hz. +This is the default setting on GX and TGX. +.It screen:r1280x1024x67 +High res 1280x1024, with a refresh rate of 67Hz. +Only available on GX+ and TGX+. +This is the default on GX+. +.It screen:r1280x1024x76 +High res 1280x1024, with a refresh rate of 76Hz. +Only available on TGX+, where this is the default setting. +.It screen:r1600x1280x76 +High res 1600x1280, with a refresh rate of 76Hz. +Only available on GX+ and TGX+. +.El +.Pp +The 1600x1280 resolution is not officially supported by +.Tn Sun +on the GX+. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 , +.Xr boot_config 8 , +.Xr config 8 +.Rs +.%T Sun Frame Buffer FAQ +.%U http://www.sunhelp.org/faq/FrameBuffer.html +.Re diff --git a/static/openbsd/man4/man4.sparc64/cgthree.4 b/static/openbsd/man4/man4.sparc64/cgthree.4 new file mode 100644 index 00000000..0cf466f1 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/cgthree.4 @@ -0,0 +1,100 @@ +.\" $OpenBSD: cgthree.4,v 1.23 2015/11/01 21:26:48 jmc Exp $ +.\" +.\" Copyright (c) 2001 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 1 2015 $ +.Dt CGTHREE 4 sparc64 +.Os +.Sh NAME +.Nm cgthree +.Nd 8-bit color frame buffer +.Sh SYNOPSIS +.Cd "cgthree* at sbus?" +.Cd "wsdisplay* at cgthree?" +.Sh DESCRIPTION +The +.Nm +is an SBus color frame buffer. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh DISPLAY RESOLUTION +If the +.Nm +frame buffer is used as the console display, it is possible, for some models, +to select a different resolution than the default 1152x900 or 1024x768 +by changing the OpenPROM environment. +To change the default resolution, type the following: +.Pp +.Em \ ok +setenv +.Em output-device +screen:r1152x900x66 +.Pp +to change to a 66Hz 1152x900 resolution. +.Pp +If the +.Nm +frame buffer is a secondary display, or a serial console is used, the +display resolution cannot be changed without using an +.Em nvramrc +OpenPROM script. +Refer to the +.Em Sun Frame Buffer FAQ +for details. +.Pp +The +.Nm +frame buffer accepts the following resolutions: +.Pp +.Bl -tag -width screen:r1280x1024x76 -compact +.It screen:r1024x768x77 +Super VGA 1024x768, with a refresh rate of 77Hz. +This is the default setting on model 501-2691. +.It screen:r1152x900x66 +Standard 1152x900, with a refresh rate of 66Hz. +This is the default setting on older models (501-1415 and 501-8044). +.It screen:r1152x900x76 +Standard 1152x900, with a refresh rate of 76Hz. +This is the default setting on more recent models (501-1718 and 501-1909). +.El +.Pp +Note that not all models support settings other than their default setting. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Rs +.%T Sun Frame Buffer FAQ +.%U http://www.sunhelp.org/faq/FrameBuffer.html +.Re diff --git a/static/openbsd/man4/man4.sparc64/cgtwelve.4 b/static/openbsd/man4/man4.sparc64/cgtwelve.4 new file mode 100644 index 00000000..3cc163a8 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/cgtwelve.4 @@ -0,0 +1,62 @@ +.\" $OpenBSD: cgtwelve.4,v 1.4 2008/03/31 08:12:22 jmc Exp $ +.\" +.\" Copyright (c) 2002 Miodrag Vallat. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2008 $ +.Dt CGTWELVE 4 sparc64 +.Os +.Sh NAME +.Nm cgtwelve +.Nd accelerated 24-bit color frame buffer +.Sh SYNOPSIS +.Cd "cgtwelve* at sbus?" +.Cd "wsdisplay* at cgtwelve?" +.Sh DESCRIPTION +The +.Nm +is a triple-slot SBus color frame buffer, with graphics acceleration +and overlay capabilities. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh CAVEATS +The only way to connect a +.Nm +frame buffer to an UltraSPARC is with the help of an +.Xr xbox 4 +SBus Expansion subsystem. +.Pp +This driver does not support any acceleration features. diff --git a/static/openbsd/man4/man4.sparc64/clkbrd.4 b/static/openbsd/man4/man4.sparc64/clkbrd.4 new file mode 100644 index 00000000..75d858f7 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/clkbrd.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: clkbrd.4,v 1.6 2022/02/20 15:01:03 jsg Exp $ +.\" +.\" Copyright (c) 2004 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 20 2022 $ +.Dt CLKBRD 4 sparc64 +.Os +.Sh NAME +.Nm clkbrd +.Nd SPARC64 clock board +.Sh SYNOPSIS +.Cd "clkbrd* at fhc?" +.Sh DESCRIPTION +The +.Nm +device provides support for the +clock board on Sunfire, Starfire, and Wildfire +UltraSPARC systems. +This device also controls the main front panel LED. +This LED can be made to blink based on the load average on most systems +by setting the +.Xr sysctl 2 +variable +.Ar machdep.led_blink +to a non-zero value. +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr fhc 4 , +.Xr intro 4 +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 3.7 . diff --git a/static/openbsd/man4/man4.sparc64/clock.4 b/static/openbsd/man4/man4.sparc64/clock.4 new file mode 100644 index 00000000..9ac0ac59 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/clock.4 @@ -0,0 +1,75 @@ +.\" $OpenBSD: clock.4,v 1.9 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" Copyright (c) 2004 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt CLOCK 4 sparc64 +.Os +.Sh NAME +.Nm clock , +.Nm rtc +.Nd real-time clock +.Sh SYNOPSIS +.Cd "clock* at sbus?" +.Cd "clock* at ebus?" +.Cd "clock0 at fhc0" +.Cd "rtc* at ebus?" +.Sh DESCRIPTION +The +.Nm +device provides support for the real-time clocks based +on the following chips: +.Pp +.Bl -bullet -offset indent -compact +.It +Mostek MK48T02 +.It +Mostek MK48T08 +.It +Mostek MK48T18 +.It +Mostek MK48T59 +.El +.Pp +The +.Nm rtc +device provides support for the real-time clock based +on the following chips: +.Pp +.Bl -bullet -offset indent -compact +.It +Dallas/Maxim Semiconductor DS1287 +.It +Acer Labs M5819 +.It +Acer Labs M5823 +.It +Texas Instruments BQ4802 +.El +.Sh SEE ALSO +.Xr ebus 4 , +.Xr fhc 4 , +.Xr intro 4 , +.Xr sbus 4 diff --git a/static/openbsd/man4/man4.sparc64/cmp.4 b/static/openbsd/man4/man4.sparc64/cmp.4 new file mode 100644 index 00000000..fbfda448 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/cmp.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: cmp.4,v 1.5 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt CMP 4 sparc64 +.Os +.Sh NAME +.Nm cmp +.Nd chip multi-threading processor +.Sh SYNOPSIS +.Cd "cmp* at mainbus0" +.Cd "cmp* at ssm?" +.Cd "cpu* at cmp?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the chip multi-threading processors such as the +Sun UltraSPARC IV and Fujitsu SPARC64 VI processors. +It is not a physical device as such, but an abstraction to attach +individual CPU cores. +.Sh SEE ALSO +.\".Xr cpu 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/comkbd.4 b/static/openbsd/man4/man4.sparc64/comkbd.4 new file mode 100644 index 00000000..804874a6 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/comkbd.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: comkbd.4,v 1.9 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt COMKBD 4 sparc64 +.Os +.Sh NAME +.Nm comkbd +.Nd serial keyboard driver +.Sh SYNOPSIS +.Cd "comkbd* at ebus?" +.Cd "wskbd* at comkbd?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Sun serial keyboards such as the Type 4, +Type 5, and Type 6 attached to a clone of the +.Tn NS16550 +UART (normally supported by the +.Xr com 4 +driver). +.Sh SEE ALSO +.Xr com 4 , +.Xr comms 4 , +.Xr ebus 4 , +.Xr intro 4 , +.Xr wskbd 4 +.Sh HISTORY +The +.Nm +driver was first supported in +.Ox 3.1 . +.Sh AUTHORS +The driver was written by +.An Jason Wright Aq Mt jason@thought.net . diff --git a/static/openbsd/man4/man4.sparc64/comms.4 b/static/openbsd/man4/man4.sparc64/comms.4 new file mode 100644 index 00000000..d0627798 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/comms.4 @@ -0,0 +1,36 @@ +.\" $OpenBSD: comms.4,v 1.1 2009/05/20 18:22:32 miod Exp $ +.\" +.\" Copyright (c) 2009 Miodrag Vallat. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: May 20 2009 $ +.Dt COMMS 4 sparc64 +.Os +.Sh NAME +.Nm comms +.Nd serial mouse driver +.Sh SYNOPSIS +.Cd "comms* at ebus?" +.Cd "wsmouse* at comms?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Sun serial mice, connected to +.Nm comkbd +serial keyboards. +.Sh SEE ALSO +.Xr com 4 , +.Xr comkbd 4 , +.Xr ebus 4 , +.Xr intro 4 , +.Xr wsmouse 4 diff --git a/static/openbsd/man4/man4.sparc64/core.4 b/static/openbsd/man4/man4.sparc64/core.4 new file mode 100644 index 00000000..8ae3a3f4 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/core.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: core.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt CORE 4 sparc64 +.Os +.Sh NAME +.Nm core +.Nd processor core +.Sh SYNOPSIS +.Cd "core* at cmp?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the chip multi-threading processors that have +multiple threads such as the Fujitsu SPARC64-VI processors. +It is not a physical device as such, but an abstraction to attach +individual CPU threads. +.Sh SEE ALSO +.Xr cmp 4 , +.\".Xr cpu 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/creator.4 b/static/openbsd/man4/man4.sparc64/creator.4 new file mode 100644 index 00000000..ae08dc51 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/creator.4 @@ -0,0 +1,69 @@ +.\" $OpenBSD: creator.4,v 1.24 2010/11/26 20:30:21 kettenis Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 26 2010 $ +.Dt CREATOR 4 sparc64 +.Os +.Sh NAME +.Nm creator +.Nd accelerated color frame buffer +.Sh SYNOPSIS +.Cd "creator* at mainbus0 flags 0x0" +.Cd "creator* at upa0 flags 0x0" +.Cd "wsdisplay* at creator?" +.Sh DESCRIPTION +The Creator, Creator 3D and Elite 3D +are color frame buffers, with graphics acceleration, available for most +of the UltraSPARC workstations with UPA slots. +.Pp +The +.Nm +driver interfaces those frame buffers with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points but makes its functions +available via the internal +.Xr wsdisplay 4 +interface. +.Pp +By default hardware acceleration is used to erase the screen and +scroll text. +By setting +.Ar flags +to +.Ar 1 +(via +.Xr config 8 +or +.Xr boot_config 8 ) +this acceleration can be disabled. +.Sh SEE ALSO +.Xr intro 4 , +.Xr upa 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 , +.Xr boot_config 8 , +.Xr config 8 diff --git a/static/openbsd/man4/man4.sparc64/ebus.4 b/static/openbsd/man4/man4.sparc64/ebus.4 new file mode 100644 index 00000000..3d77ef49 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/ebus.4 @@ -0,0 +1,103 @@ +.\" $OpenBSD: ebus.4,v 1.26 2020/06/18 20:39:28 jmc Exp $ +.\" $NetBSD: ebus.4,v 1.3 2002/03/13 21:42:20 wiz Exp $ +.\" +.\" Copyright (c) 1999 Matthew R. Green +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 18 2020 $ +.Dt EBUS 4 sparc64 +.Os +.Sh NAME +.Nm ebus +.Nd introduction to SPARC EBus bus support +.Sh SYNOPSIS +.Cd "ebus* at pci?" +.Cd "ebus* at mainbus0" +.Sh DESCRIPTION +The +.Nm +bus is designed to provide the ability to put ISA and traditional +Intel-style peripherals in a SPARC based system with a minimal amount +of glue logic. +Typically, it is implemented in the PCIO IC from SME, which also +implements an +.Xr hme 4 +compatible PCI network device +.Pf ( Ql network ) . +The +.Nm +has four DMA channels, similar to the DMA seen in the +.Xr esp 4 +SCSI DMA. +.Pp +.Ox +provides support for the following devices: +.Pp +.Bl -tag -width "audioce(4)XX" -offset 3n -compact +.It Xr audioce 4 +SPARC64 EBus CS4231 audio device +.It Xr auxio 4 +SPARC64 auxiliary I/O +.It Xr bbc 4 +SPARC64 BootBus Controller +.It Xr beeper 4 +console annunciator +.It Xr clock 4 +real-time clock +.It Xr com 4 +serial communications interface +.It Xr comkbd 4 +serial keyboard driver +.It Xr comms 4 +serial mouse driver +.It Xr led 4 +SPARC64 LED driver +.It Xr lom 4 +lights out management +.It Xr lpt 4 +parallel port driver +.It Xr pcfiic 4 +Philips PCF8584 I2C controller +.It Xr pckbc 4 +PC (ISA) keyboard controller driver +.It Xr pmc 4 +power management controller +.It Xr power 4 +power button +.It Xr sab 4 +Infineon SAB82532 (ESCC2) serial communications driver +.It Xr uperf 4 +performance counters driver +.It Xr wbsd 4 +Winbond W83L518D/W83L519D SD memory card interface +.El +.Sh SEE ALSO +.Xr intro 4 +.Rs +.%A Sun Microelectronics +.%B Peripheral Component Interconnect Input Output Controller +.%V Part\ No.:\ 802-7837-01 +.%D March 1997 +.%U http://www.sun.com/processors/manuals/802-7837.pdf +.Re diff --git a/static/openbsd/man4/man4.sparc64/ecadc.4 b/static/openbsd/man4/man4.sparc64/ecadc.4 new file mode 100644 index 00000000..06db3cca --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/ecadc.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: ecadc.4,v 1.4 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Damien Miller +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ECADC 4 sparc64 +.Os +.Sh NAME +.Nm ecadc +.Nd environmental monitoring subsystem temperature sensor +.Sh SYNOPSIS +.Cd "ecadc* at iic?" +.Sh DESCRIPTION +The +.Nm +driver supports the PCF8591 I2C analog to digital converter that is +part of the environmental monitoring subsystem found on the Sun +Enterprise 250 and Sun Enterprise 450 systems. +The temperature readings are made available through the +.Xr sysctl 8 +interface. +.Pp +The driver reads up to four A/D lines configured as temperature inputs. +Sensor names, type and calibration information are read from OpenFirmware. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr pcfadc 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org +based on the +.Xr pcfadc 4 +driver written by +.An Damien Miller Aq Mt djm@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/environ.4 b/static/openbsd/man4/man4.sparc64/environ.4 new file mode 100644 index 00000000..f9cd2880 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/environ.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: environ.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt ENVIRON 4 sparc64 +.Os +.Sh NAME +.Nm environ +.Nd SPARC64 temperature sensor +.Sh SYNOPSIS +.Cd "environ* at fhc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor found on the boards of +Sunfire, Starfire, and Wildfire UltraSPARC systems. +The temperature readings are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr fhc 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/esp.4 b/static/openbsd/man4/man4.sparc64/esp.4 new file mode 100644 index 00000000..41e63439 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/esp.4 @@ -0,0 +1,54 @@ +.\" $OpenBSD: esp.4,v 1.12 2015/03/30 20:34:32 miod Exp $ +.\" +.\" Copyright (c) 1998 The OpenBSD Project +.\" All rights reserved. +.\" +.\" +.Dd $Mdocdate: March 30 2015 $ +.Dt ESP 4 sparc64 +.Os +.Sh NAME +.Nm esp +.Nd ESP NCR 53c94 on-board or SBus SCSI interface +.Sh SYNOPSIS +.Cd "dma* at sbus? " Pq "SBus SCSI" +.Cd "esp* at dma? " Pq "two flavours" +.Cd "esp* at sbus? " Pq "depending on model" +.Sh DESCRIPTION +The +.Nm +is an on-board or SBus SCSI controller based on the NCR 53c94 chip, found +on some +.Tn Sun +UltraSPARC workstations. +.Sh DEVICE FLAGS +.Bl -tag -width "Bits XX-XX" -compact +.It Bits 0-15 +Disable disconnect/reselect for the corresponding target +.It Bits 16-31 +Disable synchronous negotiation for target "[bit - 16]" +.El +.Pp +The +.Nm +device flags may be OR'd together to enable any combination of +the features listed above. +Targets 4 through 7 typically have disconnect/reselect enabled on the premise +that tape devices normally have one of these targets. +Tape devices should be allowed to disconnect for the SCSI bus to operate +acceptably. +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr sbus 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.sparc64/fhc.4 b/static/openbsd/man4/man4.sparc64/fhc.4 new file mode 100644 index 00000000..281d8570 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/fhc.4 @@ -0,0 +1,77 @@ +.\" $OpenBSD: fhc.4,v 1.11 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" Copyright (c) 2004 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt FHC 4 sparc64 +.Os +.Sh NAME +.Nm fhc +.Nd SPARC64 FireHose controller +.Sh SYNOPSIS +.Cd "fhc* at central?" +.Cd "fhc* at mainbus0" +.Sh DESCRIPTION +The +.Nm +device provides support for the +FireHose controllers +found on Sunfire, Starfire, and Wildfire +UltraSPARC systems. +These devices are used for board level +functions on these systems. +This device also controls an LED for each slot. +This LED can be made to blink based on the load average on most systems +by setting the +.Xr sysctl 2 +variable +.Ar machdep.led_blink +to a non-zero value. +.Sh HARDWARE +.Ox +includes the following +.Nm +drivers, sorted by driver name: +.Pp +.Bl -tag -width environ(4) -offset ind -compact +.It Xr clkbrd 4 +SPARC64 Clock Board +.It Xr clock 4 +real-time clock +.It Xr environ 4 +SPARC64 temperature sensor +.It Xr zs 4 +Zilog 8530 (ZSCC) serial communications driver +.El +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr central 4 , +.Xr intro 4 +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 3.7 . diff --git a/static/openbsd/man4/man4.sparc64/gfxp.4 b/static/openbsd/man4/man4.sparc64/gfxp.4 new file mode 100644 index 00000000..93a2dba9 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/gfxp.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: gfxp.4,v 1.2 2009/10/27 14:02:05 kettenis Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. And +.\" I won't mind if you keep the disclaimer below. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 27 2009 $ +.Dt GFXP 4 sparc64 +.Os +.Sh NAME +.Nm gfxp +.Nd accelerated color frame buffer +.Sh SYNOPSIS +.Cd "gfxp* at pci?" +.Cd "wsdisplay* at gfxp?" +.Sh DESCRIPTION +The +.Nm +driver supports Tech Source Raptor PCI frame buffer cards based on the +3D Labs +.Sq Permedia v2 +chips, such as the +Sun PGX32 +and +Tech Source Raptor GFX-8P +boards. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/man4.sparc64/ifb.4 b/static/openbsd/man4/man4.sparc64/ifb.4 new file mode 100644 index 00000000..f2de4804 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/ifb.4 @@ -0,0 +1,102 @@ +.\" $OpenBSD: ifb.4,v 1.7 2011/09/03 22:59:07 jmc Exp $ +.\" +.\" Copyright (c) 2008 Miodrag Vallat. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. And +.\" I won't mind if you keep the disclaimer below. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 3 2011 $ +.Dt IFB 4 sparc64 +.Os +.Sh NAME +.Nm ifb +.Nd inextricable frame buffer +.Sh SYNOPSIS +.Cd "ifb* at pci?" +.Cd "wsdisplay* at ifb?" +.Sh DESCRIPTION +The +.Nm +driver attempts to support various frame buffer cards based on the +3DLabs +.Sq Wildcat +chips, such as the +Sun +Expert3D-Lite, +Expert3D, +XVR-500, +XVR-600 +and +XVR-1200 +boards. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh DISPLAY RESOLUTION +If the +.Nm +frame buffer is used as the console display, a different resolution than +the default 1152x900 can be selected by changing the OpenPROM environment. +To change the default resolution, type the following: +.Pp +.Em \ ok +setenv +.Em output-device +screen:r1280x1024x76 +.Pp +to change to a 76Hz 1280x1024 resolution. +.Pp +The +.Nm +frame buffer accepts the following resolutions: +.Bl -column "Mode identifier" "Resolution" "Rate(Hz)" "" +.It Sy "Mode" Ta Sy "Resolution" Ta Sy "Refresh" Ta "" +.It Sy "Identifier" Ta "" Ta Sy "Rate (Hz)" Ta "" +.It Li r640x480x60 Ta 640x480 Ta 60 Ta "" +.It Li r640x480x60i Ta 640x480 Ta 60 Ta "Composite sync" +.It Li r768x575x50i Ta 768x575 Ta 50 Ta "" +.It Li r1024x768x60 Ta 1024x768 Ta 60 Ta "Composite sync" +.It Li r1024x768x70 Ta 1024x768 Ta 70 Ta "" +.It Li r1024x768x75 Ta 1024x768 Ta 75 Ta "" +.It Li r1024x768x77 Ta 1024x768 Ta 77 Ta "" +.It Li r1024x800x84 Ta 1024x800 Ta 84 Ta "Composite sync" +.It Li r1152x900x66 Ta 1152x900 Ta 66 Ta "Composite sync" +.It Li r1152x900x76 Ta 1152x900 Ta 76 Ta "Composite sync" +.\" .It Li r1280x768x56 Ta 1280x768 Ta 56 Ta "" +.It Li r1280x800x76 Ta 1280x1024 Ta 76 Ta "" +.It Li r1280x1024x60 Ta 1280x1024 Ta 60 Ta "" +.It Li r1280x1024x67 Ta 1280x1024 Ta 67 Ta "Composite sync" +.It Li r1280x1024x75 Ta 1280x1024 Ta 75 Ta "" +.It Li r1280x1024x76 Ta 1280x1024 Ta 76 Ta "Composite sync" +.It Li r1280x1024x85 Ta 1280x1024 Ta 85 Ta "" +.It Li r1440x900x76 Ta 1440x900 Ta 76 Ta "Composite sync" +.It Li r1600x1000x66 Ta 1600x1000 Ta 66 Ta "" +.It Li r1600x1000x76 Ta 1600x1000 Ta 76 Ta "Composite sync" +.It Li r1600x1280x76 Ta 1600x1280 Ta 76 Ta "" +.It Li r1792x1344x75 Ta 1792x1344 Ta 75 Ta "" +.It Li r1920x1080x72 Ta 1920x1080 Ta 72 Ta "Composite sync" +.It Li r1920x1200x70 Ta 1920x1200 Ta 70 Ta "" +.It Li r1920x1200x75 Ta 1920x1200 Ta 75 Ta "" +.El +.Pp +Modes with the suffix letter +.Sq i +are interlaced. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh BUGS +The second head of XVR-1200 cards is not supported. diff --git a/static/openbsd/man4/man4.sparc64/intro.4 b/static/openbsd/man4/man4.sparc64/intro.4 new file mode 100644 index 00000000..b8fa527c --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/intro.4 @@ -0,0 +1,121 @@ +.\" $OpenBSD: intro.4,v 1.63 2022/03/31 17:27:22 naddy Exp $ +.\" +.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt INTRO 4 sparc64 +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +The manual pages in section 4 describe the special files, +related driver functions, and networking support +available in the system. +In this part of the manual, the SYNOPSIS section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the +sparc64 +platform. +Software support for these devices comes in two forms. +A hardware device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. +When the resultant system is booted, the autoconfiguration facilities +in the system probe for the device and, if found, enable the software +support for it. +If a device does not respond at autoconfiguration +time, it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system will have to be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +.Sh LIST OF DEVICES +A complete list of available devices is contained within the pages +describing the system buses and controllers. +For example, a PCI device would be listed in the +.Xr pci 4 +man page. +The following buses and controllers list these devices: +.Pp +.Bl -tag -width "cardbus(4)XX" -offset 3n -compact +.It Xr ebus 4 +introduction to SPARC EBus bus support +.It Xr iic 4 +Inter IC (I2C) bus +.It Xr onewire 4 +1-Wire bus +.It Xr pci 4 +introduction to PCI bus support +.It Xr pcmcia 4 +introduction to PCMCIA (PC Card) support +.It Xr sbus 4 +introduction to SBus bus support +.It Xr usb 4 +introduction to Universal Serial Bus support +.It Xr vbus 4 +virtual device bus +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr config 8 +.Sh HISTORY +The +sparc64 +.Nm intro +first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.sparc64/le.4 b/static/openbsd/man4/man4.sparc64/le.4 new file mode 100644 index 00000000..59a5da47 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/le.4 @@ -0,0 +1,101 @@ +.\" $OpenBSD: le.4,v 1.17 2015/11/21 08:04:20 jmc Exp $ +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This software was developed by the Computer Systems Engineering group +.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and +.\" contributed to Berkeley. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: Header: le.4,v 1.2 92/10/13 05:31:33 leres Exp +.\" from: @(#)le.4 8.1 (Berkeley) 6/9/93 +.\" +.Dd $Mdocdate: November 21 2015 $ +.Dt LE 4 sparc64 +.Os +.Sh NAME +.Nm le , +.Nm ledma , +.Nm lebuffer +.Nd AMD LANCE Ethernet device +.Sh SYNOPSIS +.Cd "ledma* at sbus? " Pq onboard +.Cd "le* at ledma* " Pq onboard +.Cd "le* at sbus? " Pq SBus +.Cd "lebuffer* at sbus? " Pq SBus +.Cd "le* at lebuffer? " Pq SBus +.Sh DESCRIPTION +The +.Nm +interface provides access to the 10 Mb/s +.Tn Ethernet +network via the +.Tn AMD +Am7990 +Local Area Network Controller for Ethernet +.Pq Tn LANCE +chip set. +.Pp +Different cards and machines have different kinds of connectors, +as follows: +.Bl -tag -width "media autoselect" +.It AUI/DIX +Standard 15 pin connector +.It 10BaseT +UTP, also known as twisted pair +.El +.Pp +By default, the system will select the media type automatically, but the +.Xr ifconfig 8 +command can be used to force the media selection. +The media types are shown below: +.Bl -tag -width "media autoselect" +.It media autoselect +Attempt to autoselect the media type (default) +.It media 10base5 +Use the AUI connector +.It media 10baseT +Use the twisted pair connector +.El +.Sh NOTES +Some SBus models, in particular the 501-1450 and 501-1881, have dip +switches which must be changed to select between the BNC and AUI modes. +For BNC, set 1-6 ON, 7-8 OFF; for AUI set 1-6 OFF, and 7-8 ON. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr sbus 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.sparc64/led.4 b/static/openbsd/man4/man4.sparc64/led.4 new file mode 100644 index 00000000..ef0188cb --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/led.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: led.4,v 1.4 2018/01/12 04:36:44 deraadt Exp $ +.\" +.\" Copyright (c) 2007 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 12 2018 $ +.Dt LED 4 sparc64 +.Os +.Sh NAME +.Nm led +.Nd SPARC64 LED driver +.Sh SYNOPSIS +.Cd "led* at ebus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the front panel alert LED. +This LED can be made to blink based on the load average on most systems +by setting the +.Xr sysctl 2 +variable +.Ar machdep.led_blink +to a non-zero value. +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr ebus 4 , +.Xr intro 4 , +.Xr sysctl 8 +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 4.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/lom.4 b/static/openbsd/man4/man4.sparc64/lom.4 new file mode 100644 index 00000000..02ac90c3 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/lom.4 @@ -0,0 +1,64 @@ +.\" $OpenBSD: lom.4,v 1.5 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt LOM 4 sparc64 +.Os +.Sh NAME +.Nm lom +.Nd lights out management +.Sh SYNOPSIS +.Cd "lom* at ebus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the LOMlite lights out management module +found on Sun Netra t1 systems and the LOMlite2 module found on Sun +Fire V100/V120 and Sun Netra X1 systems. +Temperature readings, PSU status and fan status provided by the LOM +are made available through the +.Xr sysctl 8 +interface. +The integrated +.Xr watchdog 4 +timer can be configured through the +.Xr sysctl 8 +interface as well. +The watchdog timer supports timeouts between 1 and 126 seconds. +If the watchdog is disabled, which is its default state, it will turn +on the system's fault LED after the maximum timeout of 126 seconds. +.Pp +The +.Nm +driver will update the hostname stored in the LOM whenever the +system's hostname is changed. +.Sh SEE ALSO +.Xr hostname 1 , +.Xr ebus 4 , +.Xr intro 4 , +.Xr watchdog 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/machfb.4 b/static/openbsd/man4/man4.sparc64/machfb.4 new file mode 100644 index 00000000..9118add9 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/machfb.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: machfb.4,v 1.1 2009/06/02 04:30:37 kettenis Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. And +.\" I won't mind if you keep the disclaimer below. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 2 2009 $ +.Dt MACHFB 4 sparc64 +.Os +.Sh NAME +.Nm machfb +.Nd accelerated color frame buffer +.Sh SYNOPSIS +.Cd "machfb* at pci?" +.Cd "wsdisplay* at machfb?" +.Sh DESCRIPTION +The +.Nm +driver supports Sun PCI frame buffer cards based on the +ATI +.Sq Mach64 +chips, such as the +Sun +PGX +and +PGX64 +boards. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/man4.sparc64/magma.4 b/static/openbsd/man4/man4.sparc64/magma.4 new file mode 100644 index 00000000..ce36d5f4 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/magma.4 @@ -0,0 +1,114 @@ +.\" $OpenBSD: magma.4,v 1.13 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" +.\" Copyright (c) 1998 Iain Hibbert +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt MAGMA 4 sparc64 +.Os +.Sh NAME +.Nm magma +.Nd Magma Sp Serial/Parallel board device driver +.Sh SYNOPSIS +.Cd "magma? at sbus?" +.Cd "mtty? at magma?" +.Cd "mbpp? at magma?" +.Sh DESCRIPTION +This driver provides an interface to Magma LC2+1Sp, 2+1Sp, 4+1Sp, 8+2Sp, +4Sp, 8Sp, 12Sp, 16Sp, 1P, 2P, and 2+1HS boards. +These boards are based around the Cirrus Logic CD1400 serial/parallel +communications engine and the Cirrus Logic CD1190 parallel communications +engine. +.Pp +The device minor numbers for this driver are encoded as follows: +.Bd -literal + +---+---+---+---+---+---+---+---+ + | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | + +---+---+---+---+---+---+---+---+ + | | | | | | | | + | | | | +---+---+---+---> port number + | | | | + | | | +-------------------> dial-out (on tty ports) + | | | + | | +-----------------------> unused + | | + +---+---------------------------> card number +.Ed +.Pp +Up to four cards are supported in the system. +.Pp +All tty ports have full automatic hardware (RTS/CTS) flow control available +and a 12 byte FIFO on the chip in each direction so errors should be minimal. +.Sh FILES +.Bl -tag -width /dev/bpp[0-3][0-1] -compact +.It /dev/tty[mno][0-f] +Serial ports +.It /dev/bpp[mno][0-1] +Parallel ports +.El +.Sh DIAGNOSTICS +.Bl -diag +.It "mtty0X: ring buffer overflow" +Incoming characters have been discarded due to a buffer overflow. +This is caused by the process in control of the device not reading characters +fast enough. +If need be you can make the ring buffer bigger by changing the +.Dv MAGMA_RBUF_SIZE +#define to something bigger, but it should be a multiple of two. +.It "mtty0X: fifo overflow" +Incoming characters have been discarded due to a CD1400 channel overrun. +This is caused by interrupts not being serviced sufficiently quickly to prevent +the 12 byte receive FIFO on a serial channel from overflowing. +Reducing the value of either the +.Dv MTTY_RX_FIFO_THRESHOLD +or +.Dv MTTY_RX_DTR_THRESHOLD +#define's to something smaller may help slow machines avoid this problem. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr tty 4 +.Sh HISTORY +The driver was loosely based upon the +.Xr cy 4 +Cyclades Cyclom device driver written +by Andrew Herbert and Timo Rossi. +.Sh AUTHORS +The driver was written by +.An Iain Hibbert Aq Mt plunky@skate.demon.co.uk +.Sh TODO +CD1190 parallel support. +.Pp +bpp input. +.Pp +Dial-out (cua) devices are not yet supported. +.Pp +mdmbuf is unsupported. +.Pp +Automatic XON/XOFF handshaking could be implemented fairly easily. +.Pp +It would be good if the tty port waited for the FIFO to empty before allowing +a close, so that I could turn off the channel interrupts at that time. +It can be done. diff --git a/static/openbsd/man4/man4.sparc64/mem.4 b/static/openbsd/man4/man4.sparc64/mem.4 new file mode 100644 index 00000000..d4554c7c --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/mem.4 @@ -0,0 +1,87 @@ +.\" $OpenBSD: mem.4,v 1.7 2024/03/22 12:29:33 jsg Exp $ +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This software was developed by the Computer Systems Engineering group +.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and +.\" contributed to Berkeley. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)mem.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: March 22 2024 $ +.Dt MEM 4 sparc64 +.Os +.Sh NAME +.Nm mem , +.Nm kmem +.Nd memory files +.Sh DESCRIPTION +The file +.Pa /dev/mem +is an interface to the physical memory of the +computer. +Byte offsets in this file are interpreted as physical memory addresses. +Reading and writing this file is equivalent to reading and writing +memory itself. +An error will be returned if an attempt is made to reference +an offset outside of +.Pa /dev/mem . +.Pp +Kernel virtual memory is accessed via the file +.Pa /dev/kmem +in the same manner as +.Pa /dev/mem . +Only kernel virtual addresses that are currently mapped to memory are allowed. +.Pp +On the +sparc64, +physical memory may be discontiguous; +kernel virtual memory begins at +.Li 0x001000000 . +.Pp +Even with sufficient file system permissions, +these devices can only be opened when the +.Xr securelevel 7 +is insecure or when the +.Va kern.allowkmem +.Xr sysctl 2 +variable is set. +.Sh FILES +.Bl -tag -width /dev/kmem -compact +.It /dev/mem +.It /dev/kmem +.El +.Sh SEE ALSO +.Xr securelevel 7 +.Sh HISTORY +The +.Pa /dev/mem +file appeared in +.At v1 , +.Pa /dev/kmem +appeared in +.At v5 . diff --git a/static/openbsd/man4/man4.sparc64/mgx.4 b/static/openbsd/man4/man4.sparc64/mgx.4 new file mode 100644 index 00000000..feb2c04d --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/mgx.4 @@ -0,0 +1,93 @@ +.\" $OpenBSD: mgx.4,v 1.14 2011/12/03 23:01:21 schwarze Exp $ +.\" +.\" Copyright (c) 2003, 2005 Miodrag Vallat +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 3 2011 $ +.Dt MGX 4 sparc64 +.Os +.Sh NAME +.Nm mgx +.Nd SMS MGX and MGXPlus accelerated 8/24-bit color frame buffers +.Sh SYNOPSIS +.Cd "mgx* at sbus?" +.Cd "wsdisplay* at mgx?" +.Sh DESCRIPTION +The +.Tn Southland Media Systems +.Pq now Tn "Quantum 3D" +MGX and MGXPlus are SBus color frame buffers, with graphics acceleration +capabilities. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh DISPLAY RESOLUTION +The MGX and MGXPlus frame buffers will adapt their resolution to the monitor +they are connected to. +However, when not connected to a Sun monitor, the device will default to the +.Xr cgthree 4 Ns -compatible +1152x900 resolution, with a refresh rate of 66Hz. +A different resolution can be forced using the set of DIP switches +.Pq sometimes covered by metal foil +located near the SBus connector on the board itself. +.Pp +The DIP switch settings are as follows: +.Bl -column "OFF OFF OFF OFF" "Resolution" "Refresh Rate" "Details" +.It Sy "Switches" Ta Sy "Resolution" Ta Sy "Refresh Rate" Ta Sy "Details" +.It Sy "1 2 3 4" Ta "" Ta "" Ta "" +.\" 0 +.It Li "OFF OFF OFF OFF" Ta 1024x768 Ta 77Hz Ta "" +.\" 2 +.It Li "OFF ON OFF OFF" Ta 1280x1024 Ta 76Hz Ta "" +.\" 3 (exactly the same as #7. Not a typo) +.It Li "ON ON OFF OFF" Ta 1152x900 Ta 66Hz Ta "" +.\" 4 +.It Li "OFF OFF ON OFF" Ta 1152x900 Ta 76Hz Ta "" +.\" 6 +.It Li "OFF ON ON OFF" Ta 1152x900 Ta 77Hz Ta "" +.\" 7 +.It Li "ON ON ON OFF" Ta 1152x900 Ta 66Hz Ta "cgthree compatible" +.\" 11 +.It Li "ON ON OFF ON " Ta 1152x900 Ta 66Hz Ta "cgsix compatible" +.\" 12 +.It Li "OFF OFF ON ON " Ta 1280x1024 Ta 67Hz Ta "" +.\" 15 +.It Li "ON ON ON ON " Ta probed Ta probed Ta "factory default" +.El +.Pp +All other combinations are unsupported and may damage the hardware. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh CAVEATS +This driver does not support mode switching at the moment, and +drives the card in PROM-compatible, 8 bit, mode only. diff --git a/static/openbsd/man4/man4.sparc64/pcons.4 b/static/openbsd/man4/man4.sparc64/pcons.4 new file mode 100644 index 00000000..303d22ec --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/pcons.4 @@ -0,0 +1,70 @@ +.\" $OpenBSD: pcons.4,v 1.7 2015/11/01 21:26:48 jmc Exp $ +.\" +.\" Copyright (c) 2001 Miodrag Vallat. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistribution of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: November 1 2015 $ +.Dt PCONS 4 sparc64 +.Os +.Sh NAME +.Nm pcons +.Nd SPARC64 PROM console interface +.Sh SYNOPSIS +.Cd "pcons0 at mainbus0" +.Cd "wsdisplay* at pcons?" +.Sh DESCRIPTION +The +.Nm +device provides a simple text console, using the PROM services for +input and/or output if no other driver handles this task. +It will use the PROM console devices set via the +.Dq input-device +and +.Dq output-device +variables. +.Pp +This driver is provided as a fallback console mechanism +if the real console hardware cannot be driven in +.Ox . +.Sh FILES +.Bl -tag -width /dev/console +.It Pa /dev/console +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr tty 4 +.Sh HISTORY +.Ox +support for the PROM console +first appeared in +.Ox 3.0 . +.Sh CAVEATS +If +.Nm +handles console input, the PROM will handle break (or Stop-A) sequences before +.Nm pcons . +The preferred way to enter +.Xr ddb 4 +on a ddb-enabled pcons console is then to enter the following sequence : +.Sq +++++ diff --git a/static/openbsd/man4/man4.sparc64/pmc.4 b/static/openbsd/man4/man4.sparc64/pmc.4 new file mode 100644 index 00000000..0d53a368 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/pmc.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: pmc.4,v 1.5 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2007 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PMC 4 sparc64 +.Os +.Sh NAME +.Nm pmc +.Nd power management controller +.Sh SYNOPSIS +.Cd "pmc* at ebus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the watchdog feature of the power +management device of the National Semiconductor PC87317 SuperIO chip +found on UltraSPARC III systems. +.Pp +The watchdog timer provides a standard watchdog(4) interface, +and has a granularity of 60 seconds. +.Sh SEE ALSO +.Xr bbc 4 , +.Xr intro 4 , +.Xr watchdog 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/power.4 b/static/openbsd/man4/man4.sparc64/power.4 new file mode 100644 index 00000000..40c4b461 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/power.4 @@ -0,0 +1,62 @@ +.\" $OpenBSD: power.4,v 1.6 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt POWER 4 sparc64 +.Os +.Sh NAME +.Nm power +.Nd power button +.Sh SYNOPSIS +.Cd "power* at ebus?" +.Sh DESCRIPTION +Some UltraSPARC host bridges provide an interrupt when the power button +is depressed. +The +.Nm +driver catches that interrupt. +If the +.Va hw.allowpowerdown +.Xr sysctl 8 +is set to 1, +.Nm power +will signal +.Xr init 8 +to do a clean shutdown. +.Sh SEE ALSO +.Xr ebus 4 , +.Xr intro 4 , +.Xr init 8 , +.Xr rc.shutdown 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver was first supported in +.Ox 4.0 . +.Sh AUTHORS +The driver was written by +.An Jason Wright Aq Mt jason@thought.net . diff --git a/static/openbsd/man4/man4.sparc64/ppm.4 b/static/openbsd/man4/man4.sparc64/ppm.4 new file mode 100644 index 00000000..94109c25 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/ppm.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: ppm.4,v 1.3 2018/01/12 04:36:44 deraadt Exp $ +.\" +.\" Copyright (c) 2006 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 12 2018 $ +.Dt PPM 4 sparc64 +.Os +.Sh NAME +.Nm ppm +.Nd SPARC64 PPM +.Sh SYNOPSIS +.Cd "ppm* at ebus?" +.Sh DESCRIPTION +The +.Nm +device contains miscellaneous system controls, including the front panel LED. +This LED can be made to blink based on the load average on most systems +by setting the +.Xr sysctl 2 +variable +.Ar machdep.led_blink +to a non-zero value. +Internally, various status bits for some of the onboard devices are +found in +.Nm ppm . +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr ebus 4 , +.Xr intro 4 diff --git a/static/openbsd/man4/man4.sparc64/prtc.4 b/static/openbsd/man4/man4.sparc64/prtc.4 new file mode 100644 index 00000000..0e4fdc0c --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/prtc.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: prtc.4,v 1.2 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PRTC 4 sparc64 +.Os +.Sh NAME +.Nm prtc +.Nd PROM real-time clock +.Sh SYNOPSIS +.Cd "prtc0 at mainbus0" +.Sh DESCRIPTION +The +.Nm +driver provides support for the time of day service provided by the +PROM on systems that do not have a hardware real-time clock like the +Sun Enterprise 10000, Sun Fire 12K and Sun Fire 15K. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/psycho.4 b/static/openbsd/man4/man4.sparc64/psycho.4 new file mode 100644 index 00000000..b8e9eadc --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/psycho.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: psycho.4,v 1.5 2008/03/31 08:12:22 jmc Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2008 $ +.Dt PSYCHO 4 sparc64 +.Os +.Sh NAME +.Nm psycho +.Nd SPARC64 Host/PCI bridge +.Sh SYNOPSIS +.Cd "psycho* at mainbus0" +.Cd "pci* at psycho?" +.Sh DESCRIPTION +The +.Nm +device provides support for the +.Xr pci 4 +bus on sparc64 +systems, most often found on UltraSPARC I and UltraSPARC II based systems. +It supports the +.Xr ioctl 2 +interface in +.Xr pci 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.sparc64/pyro.4 b/static/openbsd/man4/man4.sparc64/pyro.4 new file mode 100644 index 00000000..492a3a4d --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/pyro.4 @@ -0,0 +1,59 @@ +.\" $OpenBSD: pyro.4,v 1.4 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PYRO 4 sparc64 +.Os +.Sh NAME +.Nm pyro +.Nd SPARC64 Host/PCIe bridge +.Sh SYNOPSIS +.Cd "pyro* at mainbus0" +.Cd "pci* at pyro?" +.Sh DESCRIPTION +The +.Nm +device provides support for the Fire and Oberon +.Xr pci 4 +bus, as found on UltraSPARC III based sparc64 systems. +It supports the +.Xr ioctl 2 +interface in +.Xr pci 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/qe.4 b/static/openbsd/man4/man4.sparc64/qe.4 new file mode 100644 index 00000000..acadd5ca --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/qe.4 @@ -0,0 +1,60 @@ +.\" $OpenBSD: qe.4,v 1.11 2008/03/31 08:12:22 jmc Exp $ +.\" +.\" Copyright (c) 1998 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2008 $ +.Dt QE 4 sparc64 +.Os +.Sh NAME +.Nm qe +.Nd SPARC64 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "qec* at sbus?" +.Cd "qe* at qec?" +.Sh DESCRIPTION +The +.Nm +interface provides access to 10Mb/s Ethernet networks via the +.Tn AMD +Am79C940 (MACE) Ethernet controller. +The +.Nm +is found on the Sun QuadEthernet boards +(Sun part number SUNW,501-2062). +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr qec 4 , +.Xr sbus 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.sparc64/qec.4 b/static/openbsd/man4/man4.sparc64/qec.4 new file mode 100644 index 00000000..82f010d6 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/qec.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: qec.4,v 1.10 2007/05/31 19:19:57 jmc Exp $ +.\" +.\" Copyright (c) 1998 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt QEC 4 sparc64 +.Os +.Sh NAME +.Nm qec +.Nd SPARC64 Quad Ethernet Controller +.Sh SYNOPSIS +.Cd "qec* at sbus?" +.Cd "be* at qec?" +.Cd "qe* at qec?" +.Sh DESCRIPTION +The +.Nm +driver is an SBus controller that can contain either one +.Xr be 4 +Ethernet controller (Sun part number SUNW,501-2655) +or four +.Xr qe 4 +Ethernet controllers (Sun part number SUNW,501-2062). +This driver, like other buses, is not directly available to users. +In essence it is a buffering DMA controller. +.Sh SEE ALSO +.Xr be 4 , +.Xr intro 4 , +.Xr qe 4 , +.Xr sbus 4 +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/man4.sparc64/radeonfb.4 b/static/openbsd/man4/man4.sparc64/radeonfb.4 new file mode 100644 index 00000000..bea7c99b --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/radeonfb.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: radeonfb.4,v 1.2 2011/01/04 19:25:36 kettenis Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 4 2011 $ +.Dt RADEONFB 4 sparc64 +.Os +.Sh NAME +.Nm radeonfb +.Nd accelerated color frame buffer +.Sh SYNOPSIS +.Cd "radeonfb* at pci?" +.Cd "wsdisplay* at radeonfb?" +.Sh DESCRIPTION +The +.Nm +driver supports Sun PCI frame buffer cards based on the +ATI +.Sq Radeon +chips, such as the +Sun +XVR-100 +and +XVR-300 +boards. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/man4.sparc64/raptor.4 b/static/openbsd/man4/man4.sparc64/raptor.4 new file mode 100644 index 00000000..9cf210ab --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/raptor.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: raptor.4,v 1.3 2011/02/24 11:18:44 kettenis Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. And +.\" I won't mind if you keep the disclaimer below. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 24 2011 $ +.Dt RAPTOR 4 sparc64 +.Os +.Sh NAME +.Nm raptor +.Nd accelerated color frame buffer +.Sh SYNOPSIS +.Cd "raptor* at pci?" +.Cd "wsdisplay* at raptor?" +.Sh DESCRIPTION +The +.Nm +driver supports Tech Source Raptor PCI frame buffer cards based on the +Number 9 +.Sq Imagine-128 +chips, such as the +Tech Source +Raptor GFX-4M +and +Raptor GFX-8M +boards. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/man4.sparc64/rfx.4 b/static/openbsd/man4/man4.sparc64/rfx.4 new file mode 100644 index 00000000..838ba628 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/rfx.4 @@ -0,0 +1,106 @@ +.\" $OpenBSD: rfx.4,v 1.12 2015/09/10 15:53:26 schwarze Exp $ +.\" +.\" Copyright (c) 2004, Miodrag Vallat. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt RFX 4 sparc64 +.Os +.Sh NAME +.Nm rfx +.Nd Vitec/Connectware/AP&D RasterFlex framebuffer series +.Sh SYNOPSIS +.Cd "rfx* at sbus?" +.Cd "wsdisplay* at rfx?" +.Sh DESCRIPTION +The RasterFlex +series, originally manufactured by Vitec, later bought by Connectware, +then by Advanced Products & Design, are high-performance frame buffers +and frame grabber devices. +.Pp +The +.Nm +driver only supports the RasterFlex frame buffers: +.Bl -tag -width RasterFLEX-HR -offset indent -compact +.It RasterFlex-24 +.It RasterFlex-32 +.It RasterFlex-HR +.El +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh DISPLAY RESOLUTION +The RasterFlex +frame buffers will adapt their resolution to the monitor they are +connected to. +However, when not connected to a Sun +monitor, the device will default to the 1152x900 resolution, with a refresh +rate of 66Hz. +A different resolution can be forced using the jumpers J2 to J4, located +near the video connector on the board itself. +.Pp +In the following tables, left +.Pq L +and right +.Pq R +jumper positions are described looking at the board with the video connector +on top. +If the jumper position is not specified +.Pq _ , +it means it has to be removed +.Pq open . +.Ss RasterFlex-24 and RasterFlex-32 Jumper Settings: +.Bl -column "J2 J3 J4" "Resolution" "Refresh Rate" "Description" -offset indent +.It Sy "J2 J3 J4" Ta Sy "Resolution" Ta Sy "Refresh Rate" Ta Sy "Description" +.It Li "\ \&R \ \&R \ \&R" Ta 1152x900 Ta 66Hz Ta "Automatic Configuration" +.It Li "L L L " Ta 1024x768 Ta 76Hz Ta "SVGA" +.It Li "L _ _ " Ta 1152x900 Ta 66Hz Ta "" +.It Li "_ L L " Ta 1152x900 Ta 76Hz Ta "" +.El +.Ss RasterFlex-HR Jumper Settings: +.Bl -column "J2 J3 J4" "Resolution" "Refresh Rate" "Description" -offset indent +.It Sy "J2 J3 J4" Ta Sy "Resolution" Ta Sy "Refresh Rate" Ta Sy "Description" +.It Li "\ \&R \ \&R \ \&R" Ta 1152x900 Ta 66Hz Ta "Automatic Configuration" +.It Li "L L L " Ta 1024x768 Ta 76Hz Ta "SVGA" +.It Li "L _ _ " Ta 1152x900 Ta 66Hz Ta "" +.It Li "L L _ " Ta 1152x900 Ta 76Hz Ta "" +.It Li "_ L _ " Ta 1280x1024 Ta 60Hz Ta "" +.It Li "_ L L " Ta 1280x1024 Ta 67Hz Ta "" +.It Li "L _ L " Ta 1280x1024 Ta 76Hz Ta "" +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh CAVEATS +This driver does not support any acceleration features at the moment, and +drives the card in PROM-compatible, 8 bit, mode only. diff --git a/static/openbsd/man4/man4.sparc64/sab.4 b/static/openbsd/man4/man4.sparc64/sab.4 new file mode 100644 index 00000000..95649f1a --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/sab.4 @@ -0,0 +1,80 @@ +.\" $OpenBSD: sab.4,v 1.9 2015/11/21 08:04:20 jmc Exp $ +.\" +.\" Copyright (c) 2001 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 21 2015 $ +.Dt SAB 4 sparc64 +.Os +.Sh NAME +.Nm sab , +.Nm sabtty +.Nd Infineon SAB82532 (ESCC2) serial communications driver +.Sh SYNOPSIS +.Cd "sab* at ebus?" +.Cd "sabtty* at sab?" +.Sh DESCRIPTION +The +.Nm +is an +.Tn Infineon +(formerly +.Tn Siemens ) +SAB82532 (ESCC2) serial interface chip used in PCI-based UltraSPARC +.Tn Sun +workstations. +The ESCC2 provides two independent input/output channels per instance. +These chips are normally used to provide RS-423 and RS232 serial ports +for general purpose use. +.Pp +The +.Nm +driver supports all of the standard +.Xr tty 4 +ioctl calls. +The status of the DTR, RTS, CTS, and DCD signals can be queried with +TIOCMGET command, but, due to limitations in the hardware, +only the DTR and RTS signals can be modified with TIOCMSET, TIOCMBIC, +and TIOCMBIS +.Xr ioctl 2 +commands. +.Sh FILES +.Bl -tag -width /dev/ttyh[0-1] -compact +.It /dev/ttyh[0-1] +Serial ports +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr ebus 4 , +.Xr intro 4 , +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.1 . +.Sh BUGS +The +.Nm +does not support cua minor devices. diff --git a/static/openbsd/man4/man4.sparc64/sbbc.4 b/static/openbsd/man4/man4.sparc64/sbbc.4 new file mode 100644 index 00000000..34027e76 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/sbbc.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: sbbc.4,v 1.4 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt SBBC 4 sparc64 +.Os +.Sh NAME +.Nm sbbc +.Nd PCI BootBus Controller +.Sh SYNOPSIS +.Cd "sbbc* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PCI BootBus Controllers found on +Serengeti and Starcat systems. +It provides access to the system controller in these systems, +providing time of day and console services. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/schizo.4 b/static/openbsd/man4/man4.sparc64/schizo.4 new file mode 100644 index 00000000..b935f4bc --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/schizo.4 @@ -0,0 +1,54 @@ +.\" $OpenBSD: schizo.4,v 1.8 2008/07/06 09:08:21 kettenis Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 6 2008 $ +.Dt SCHIZO 4 sparc64 +.Os +.Sh NAME +.Nm schizo +.Nd SPARC64 Host/PCI bridge +.Sh SYNOPSIS +.Cd "schizo* at mainbus0" +.Cd "schizo* at ssm?" +.Cd "pci* at schizo?" +.Sh DESCRIPTION +The +.Nm +device provides support for the Schizo, Schizo+ and Tomatillo +.Xr pci 4 +bus, as found on UltraSPARC III and UltraSPARC IV based sparc64 systems. +It supports the +.Xr ioctl 2 +interface in +.Xr pci 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.2 . diff --git a/static/openbsd/man4/man4.sparc64/spif.4 b/static/openbsd/man4/man4.sparc64/spif.4 new file mode 100644 index 00000000..01d28ca4 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/spif.4 @@ -0,0 +1,103 @@ +.\" $OpenBSD: spif.4,v 1.15 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 1999-2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt SPIF 4 sparc64 +.Os +.Sh NAME +.Nm spif +.Nd SBus (spiffy) Serial/Parallel Interface +.Sh SYNOPSIS +.Cd "spif* at sbus?" +.Cd "stty* at spif?" +.Cd "sbpp* at spif?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Sun Serial/Parallel Interface card +(Sun part number 501-1931) +based around the +Cirrus Logic CD180 octal serial controller +and the +Cirrus Logic PPC2 parallel port controller. +.Pp +The device minor numbers for this driver are encoded as follows: +.Bd -literal + +---+---+---+---+---+---+---+---+ + | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | + +---+---+---+---+---+---+---+---+ + | | | | | | | | + | | | | | +---+---+---> port number + | | | | | + | | | | +---------------> unused + | | | | + | | | +-------------------> dial-out (on tty ports) + | | | + | | +-----------------------> unused + | | + +---+---------------------------> card number +.Ed +.Pp +Up to four cards are supported in the system. +.Pp +Each of the serial ports has an 8 byte FIFO for receive and transmit as +well as automatic hardware (RTS/CTS) flow control. +.Sh FILES +.Bl -tag -width /dev/tty[jkl][0-7] -compact +.It /dev/tty[jkl][0-7] +Serial ports +.It /dev/sbpp[0-3] +Parallel ports +.El +.Sh DIAGNOSTICS +.Bl -diag +.It "spif0: ccr timeout" +A timeout occurred while writing to one of the CD180 registers. +.It "stty0-N: ring overflow" +Incoming characters were discarded because the application +in control of the device did not read the input fast enough. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver was first supported in +.Ox 3.1 . +.Sh AUTHORS +.An -nosplit +The driver was written by +.An Jason Wright Aq Mt jason@thought.net , +and is heavily based on the +.Xr magma 4 +driver written by +.An Iain Hibbert Aq Mt plunky@skate.demon.co.uk . +.Sh TODO +The parallel port is not supported yet. +.Pp +Dial-out (cua) devices are not yet supported. diff --git a/static/openbsd/man4/man4.sparc64/ssm.4 b/static/openbsd/man4/man4.sparc64/ssm.4 new file mode 100644 index 00000000..0908c8ba --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/ssm.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: ssm.4,v 1.3 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt SSM 4 sparc64 +.Os +.Sh NAME +.Nm ssm +.Nd Scalable Shared Memory +.Sh SYNOPSIS +.Cd "ssm* at mainbus0" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Scalable Shared Memory devices found on +Serengeti and Starcat systems. +These devices are used to connect snoopy coherency domains together in +a coherent fashion to build systems with more than 24 CPUs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/tda.4 b/static/openbsd/man4/man4.sparc64/tda.4 new file mode 100644 index 00000000..e65a3a47 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/tda.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: tda.4,v 1.5 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Robert Nagy +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt TDA 4 sparc64 +.Os +.Sh NAME +.Nm tda +.Nd Philips TDA8444 fan controller +.Sh SYNOPSIS +.Cd "tda* at iic?" +.Sh DESCRIPTION +The +.Nm +driver supports the TDA8444 DAC to adjust the output voltage to the fans +on Sun Blade 1000/2000 machines. +.Pp +The driver watches the internal and external temperature provided by the +sensors framework and adjusts the fan speeds accordingly. +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Robert Nagy Aq Mt robert@openbsd.org +and +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/tvtwo.4 b/static/openbsd/man4/man4.sparc64/tvtwo.4 new file mode 100644 index 00000000..1fa3e002 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/tvtwo.4 @@ -0,0 +1,82 @@ +.\" $OpenBSD: tvtwo.4,v 1.11 2011/12/03 23:01:21 schwarze Exp $ +.\" Copyright (c) 2003 Miodrag Vallat. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 3 2011 $ +.Dt TVTWO 4 sparc64 +.Os +.Sh NAME +.Nm tvtwo +.Nd accelerated 24-bit color frame buffer +.Sh SYNOPSIS +.Cd "tvtwo* at sbus?" +.Cd "wsdisplay* at tvtwo?" +.Sh DESCRIPTION +The Parallax XVideo and PowerVideo frame buffers, also known as +.Sq tvtwo , +are memory based color frame buffers, with graphics acceleration +and overlay capabilities, and hardware MPEG decoding. +.Pp +The +.Nm +driver interfaces the frame buffer to the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh DISPLAY RESOLUTION +The XVideo and PowerVideo frame buffers will adapt their resolution and +refresh rate to the monitor they are connected to. +However, when not connected to a Sun monitor, the device will default to the +.Xr cgthree 4 Ns -compatible +1152x900 resolution, with a refresh rate of 67Hz. +A different resolution can be forced using the rotary switch on the edge +of the board. +.Pp +The available modes are as follows: +.Bl -column "Rotary" "Resolution" "Refresh Rate" -offset indent +.It Sy Rotary Ta Sy Resolution Ta Sy "Refresh Rate" +.It Li 0 Ta autodetect Ta autodetect +.It Li 1 Ta 1152x900 Ta 67Hz +.It Li 2 Ta 1152x900 Ta 76Hz +.It Li 3 Ta 1152x900 Ta 60Hz +.It Li 4 Ta 1024x768 Ta 77Hz +.It Li 5 Ta 640x480 Ta 60Hz +.El +.Pp +All other rotary positions will behave as position 0, except for positions +E and F. +Position E enables the board built-in debugger on the serial port, and +should not be used by end-users. +Position F selects the video mode settings stored in the cards NVRAM. +These settings cannot be modified under +.Ox . +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh CAVEATS +This driver does not support any acceleration features at the moment. diff --git a/static/openbsd/man4/man4.sparc64/upa.4 b/static/openbsd/man4/man4.sparc64/upa.4 new file mode 100644 index 00000000..572be86d --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/upa.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: upa.4,v 1.5 2007/05/31 19:19:57 jmc Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt UPA 4 sparc64 +.Os +.Sh NAME +.Nm upa +.Nd SPARC64 Host/UPA bridge +.Sh SYNOPSIS +.Cd "upa* at mainbus0" +.Cd "creator* at upa0" +.Sh DESCRIPTION +The +.Nm +device provides support for the +.Nm upa +bus on sparc64 +systems, most often found on UltraSPARC III based systems. +.Sh SEE ALSO +.Xr creator 4 , +.Xr intro 4 +.Sh HISTORY +.Ox +support for the +.Nm +first appeared in +.Ox 3.2 . diff --git a/static/openbsd/man4/man4.sparc64/uperf.4 b/static/openbsd/man4/man4.sparc64/uperf.4 new file mode 100644 index 00000000..ee158d72 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/uperf.4 @@ -0,0 +1,242 @@ +.\" $OpenBSD: uperf.4,v 1.17 2015/02/15 22:26:45 bentley Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 15 2015 $ +.Dt UPERF 4 sparc64 +.Os +.Sh NAME +.Nm uperf +.Nd performance counters driver +.Sh SYNOPSIS +.Cd "uperf* at ebus?" +.Cd "uperf* at sbus?" +.Sh DESCRIPTION +Some UltraSPARC host bridges provide performance counters on their host +bridges. +The counters are a part of the system controller chip (usc, dsc, or qsc). +On PCI machines the system controller shows up as a device on the EBus, but +on SBus machines the system controller exists in SBus space. +The +.Nm +driver provides access to these counters via +.Xr ioctl 2 . +.Sh IOCTLS +All of the ioctl calls supported by the +.Nm +driver take the following structure as an argument: +.Bd -literal -offset indent +struct uperf_io { + int cnt_flags; + int cnt_src0; + int cnt_src1; + u_int32_t cnt_val0; + u_int32_t cnt_val1; +}; +.Ed +.Pp +The +.Fa cnt_flags +field specifies which counters are being operated on and is a bit mask +of +.Fa UPERF_CNT0 +and/or +.Fa UPERF_CNT1 . +.Pp +The +.Fa cnt_src0 +and +.Fa cnt_src1 +fields specify the source for the counter. +Not all counters support monitoring all sources and specifying an invalid +source for a counter to monitor will result in an error. +The sources are specified below: +.Pp +.Bl -tag -width "UPERFSRC_TLBMISS" -offset indent -compact +.It Em UPERFSRC_SYSCK +system clock ticks +.It Em UPERFSRC_PRALL +all p-requests +.It Em UPERFSRC_PRP0 +p-requests from processor 0 +.It Em UPERFSRC_PRU2S +p-requests from the U2S +.It Em UPERFSRC_UPA128 +cycles UPA 128 bit data is busy +.It Em UPERFSRC_UPA64 +cycles UPA 64 bit data is busy +.It Em UPERFSRC_PIOS +cycles stalled during PIO +.It Em UPERFSRC_MEMRI +memory requests issued +.It Em UPERFSRC_MCBUSY +cycles memory controller is busy +.It Em UPERFSRC_PXSH +stall cycles due to pending transaction scoreboard hit +.It Em UPERFSRC_P0CWMR +coherent write miss requests, processor 0 +.It Em UPERFSRC_P1CWMR +coherent write miss requests, processor 1 +.It Em UPERFSRC_CIT +coherent intervention transactions +.It Em UPERFSRC_U2SDAT +data transactions on U2S +.It Em UPERFSRC_CRXI +coherent read transactions issued +.It Em UPERFSRC_RDP0 +read requests, processor 0 +.It Em UPERFSRC_P0CRMR +coherent read misses, processor 0 +.It Em UPERFSRC_P0PIO +PIO accesses, processor 0 +.It Em UPERFSRC_MEMRC +memory requests completed +.It Em UPERFSRC_P1RR +read requests, processor 1 +.It Em UPERFSRC_CRMP1 +coherent read misses, processor 1 +.It Em UPERFSRC_PIOP1 +PIO accesses, processor 1 +.It Em UPERFSRC_CWXI +coherent write transactions issued +.It Em UPERFSRC_RP0 +read requests, processor 0 +.It Em UPERFSRC_SDVRA +streaming DVMA read transfers, PCI bus A +.It Em UPERFSRC_SDVWA +streaming DVMA write transfers, PCI bus A +.It Em UPERFSRC_CDVRA +consistent DVMA read transfers, PCI bus A +.It Em UPERFSRC_CDVWA +consistent DVMA write transfers, PCI bus A +.It Em UPERFSRC_SBMA +streaming buffer misses, PCI bus A +.It Em UPERFSRC_DVA +DVMA cycles, PCI bus A +.It Em UPERFSRC_DVWA +words transferred via DVMA, PCI bus A +.It Em UPERFSRC_PIOA +cycles consumed by PIO, bus A +.It Em UPERFSRC_SDVRB +streaming DVMA read transfers, PCI bus B +.It Em UPERFSRC_SDVWB +streaming DVMA write transfers, PCI bus B +.It Em UPERFSRC_CDVRB +consistent DVMA read transfers, PCI bus B +.It Em UPERFSRC_CDVWB +consistent DVMA write transfers, PCI bus B +.It Em UPERFSRC_SBMB +streaming buffer misses, PCI bus B +.It Em UPERFSRC_DVB +DVMA cycles, PCI bus B +.It Em UPERFSRC_DVWB +words transferred via DVMA, PCI bus B +.It Em UPERFSRC_PIOB +cycles consumed by PIO, bus B +.It Em UPERFSRC_TLBMISS +TLB misses +.It Em UPERFSRC_NINTRS +interrupts +.It Em UPERFSRC_INACK +interrupt NACKS on UPA +.It Em UPERFSRC_PIOR +PIO read transfers +.It Em UPERFSRC_PIOW +PIO write transfers +.It Em UPERFSRC_MERGE +merge buffer transactions +.It Em UPERFSRC_TBLA +DMA requests retried due to tablewalks, PCI bus A +.It Em UPERFSRC_STCA +DMA requests retries due to STC, PCI bus A +.It Em UPERFSRC_TBLB +DMA requests retries due to tablewalks, PCI bus B +.It Em UPERFSRC_STCB +DMA requests retries due to STC, PCI bus B +.El +.Pp +The +.Fa cnt_val0 +and +.Fa cnt_val1 +contain the values fetched for the counters. +Software using this interface should be prepared to handle the counters +rolling over. +.Pp +The +.Nm +device responds to the following +.Xr ioctl 2 +calls, which are defined in +.In dev/sun/uperfio.h . +.Bl -tag -width UPIO_GCNTSRC +.It Dv UPIO_GCNTSRC +.Pq Li "struct uperf_io" +Retrieve the source the counters are monitoring. +The +.Fa cnt_flags +is a bit mask for which of the counters is to be fetched. +The result is returned in +.Fa cnt_src0 +and/or +.Fa cnt_src1 . +.It Dv UPIO_SCNTSRC +.Pq Li "struct uperf_io" +Set the source the counters should monitor. +This call also clears the current value of the counters that are set. +The +.Fa cnt_flags +is a bit mask for which of the counters is to be set. +The +.Fa cnt_src0 +and/or +.Fa cnt_src1 +fields specify the source to be set for the respective counter. +.It Dv UPIO_CLRCNT +.Pq Li "struct uperf_io" +Clear the counters specified in +.Fa cnt_flags . +.It Dv UPIO_GETCNT +.Pq Li "struct uperf_io" +Retrieve the value for the counters specified in +.Fa cnt_flags . +The values are returned in +.Fa cnt_val0 +and/or +.Fa cnt_val1 . +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr ebus 4 , +.Xr intro 4 , +.Xr sbus 4 +.Sh HISTORY +The +.Nm +driver was first supported in +.Ox 3.1 . +.Sh AUTHORS +The driver was written by +.An Jason Wright Aq Mt jason@thought.net . diff --git a/static/openbsd/man4/man4.sparc64/vbus.4 b/static/openbsd/man4/man4.sparc64/vbus.4 new file mode 100644 index 00000000..959642e1 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vbus.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: vbus.4,v 1.9 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt VBUS 4 sparc64 +.Os +.Sh NAME +.Nm vbus +.Nd virtual device bus +.Sh SYNOPSIS +.Cd "vbus0 at mainbus0" +.Sh DESCRIPTION +The +.Nm +driver provides a virtual bus for virtual devices provided by the +UltraSPARC Hypervisor as found on sun4v systems and logical domains. +.Pp +.Ox +provides support for the following devices: +.Pp +.Bl -tag -width "vcons(4)XX" -offset 3n -compact +.It Xr cbus 4 +channel device bus +.It Xr vcons 4 +virtual console interface +.It Xr vrng 4 +virtual random number generator +.It Xr vrtc 4 +virtual real-time clock +.El +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/vcc.4 b/static/openbsd/man4/man4.sparc64/vcc.4 new file mode 100644 index 00000000..95544d7e --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vcc.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: vcc.4,v 1.4 2015/11/21 08:04:20 jmc Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 21 2015 $ +.Dt VCC 4 sparc64 +.Os +.Sh NAME +.Nm vcc , +.Nm vcctty +.Nd virtual console concentrator +.Sh SYNOPSIS +.Cd "vcc* at cbus?" +.Cd "vcctty* at vcc?" +.Sh DESCRIPTION +The +.Nm +driver provides access to the consoles of guest domains from the +control domain of sun4v systems. +It provides a standard +.Xr tty 4 +interface on top of a logical domain channel provided by the +UltraSPARC Hypervisor. +.Sh FILES +.Bl -tag -width /dev/ttyV[0-9a-zA-Z] +.It /dev/ttyV[0-9a-zA-Z] +.El +.Sh SEE ALSO +.Xr cbus 4 , +.Xr intro 4 , +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/vcons.4 b/static/openbsd/man4/man4.sparc64/vcons.4 new file mode 100644 index 00000000..8657c55a --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vcons.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: vcons.4,v 1.3 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt VCONS 4 sparc64 +.Os +.Sh NAME +.Nm vcons +.Nd virtual console interface +.Sh SYNOPSIS +.Cd "vcons0 at vbus?" +.Sh DESCRIPTION +The +.Nm +driver provides a console using the services provided by the +UltraSPARC Hypervisor as found on sun4v systems. +.Sh FILES +.Bl -tag -width /dev/console +.It Pa /dev/console +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr tty 4 , +.Xr vbus 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/vds.4 b/static/openbsd/man4/man4.sparc64/vds.4 new file mode 100644 index 00000000..981f002e --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vds.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: vds.4,v 1.6 2015/11/21 08:04:20 jmc Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 21 2015 $ +.Dt VDS 4 sparc64 +.Os +.Sh NAME +.Nm vds , +.Nm vdsp +.Nd virtual disk server +.Sh SYNOPSIS +.Cd "vds* at cbus?" +.Cd "vdsp* at vds?" +.Sh DESCRIPTION +The +.Nm +driver provides a virtual disk server using the services provided by +the UltraSPARC Hypervisor as found on sun4v systems. +It provides the backing storage for virtual disks in other logical +domains through a logical domain channel provided by the UltraSPARC +Hypervisor. +The +.Nm +driver uses block devices or disk images in the form of regular files. +The name of the block device or file used for the disk image is taken from the +domain's machine description. +.Pp +The +.Nm +driver supports version 1.0 and version 1.1 of the vDisk protocol. +.Sh SEE ALSO +.Xr cbus 4 , +.Xr intro 4 , +.Xr vdsk 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/vdsk.4 b/static/openbsd/man4/man4.sparc64/vdsk.4 new file mode 100644 index 00000000..afab0447 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vdsk.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: vdsk.4,v 1.3 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt VDSK 4 sparc64 +.Os +.Sh NAME +.Nm vdsk +.Nd virtual disk +.Sh SYNOPSIS +.Cd "vdsk* at cbus?" +.Sh DESCRIPTION +The +.Nm +driver provides a virtual disk using the services provided by the +UltraSPARC Hypervisor as found on sun4v systems. +It connects to a virtual disk server (vds) device in another logical +domain using a logical domain channel provided by the hypervisor. +.Pp +The +.Nm +driver supports version 1.0 of the vDisk protocol. +.Sh SEE ALSO +.Xr cbus 4 , +.Xr intro 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/vigra.4 b/static/openbsd/man4/man4.sparc64/vigra.4 new file mode 100644 index 00000000..c8490551 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vigra.4 @@ -0,0 +1,108 @@ +.\" $OpenBSD: vigra.4,v 1.7 2011/09/03 22:59:07 jmc Exp $ +.\" Copyright (c) 2002 Miodrag Vallat. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 3 2011 $ +.Dt VIGRA 4 sparc64 +.Os +.Sh NAME +.Nm vigra +.Nd 8-bit SBus color frame buffer with VGA-compatible modes +.Sh SYNOPSIS +.Cd "vigra* at sbus?" +.Cd "wsdisplay* at vigra?" +.Sh DESCRIPTION +The +.Tn "Vigra VS10, VS11 and VS12" +are 8-bit color frame buffers with user-selectable video modes, and a +VGA-compatible connector. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Pp +The video resolution and signal synchronization modes are +selected with four DIP switches on the back of the card. +.Ss VS10 and VS12 Switch Settings: +The VS10 and VS12 support the following basic modes: +.Bl -column "Switches" "Resolution" "Refresh" +.It Sy Switches Ta Sy Resolution Ta Sy Refresh Ta Sy Description +.It Sy "1 2 3 4" Ta "" Ta Sy "Rate" Ta "" +.It Li "D D D D" Ta 640x480 Ta 60Hz Ta "Standard VGA, negative separate sync" +.It Li "U D D D" Ta 800x600 Ta 56Hz Ta "Super VGA, negative separate sync" +.It Li "D U D D" Ta 800x600 Ta 56Hz Ta "Super VGA, positive separate sync" +.It Li "U U D D" Ta 1024x768 Ta 60Hz Ta "Super VGA, negative separate sync" +.It Li "D D U D" Ta 1024x768 Ta 60Hz Ta "Super VGA, composite sync" +.It Li "U D U D" Ta 1024x768 Ta 60Hz Ta "Super VGA, sync-on-green" +.It Li "D U U D" Ta 1024x768 Ta 66Hz Ta "Sun 386i, composite sync" +.It Li "U U U D" Ta 1152x900 Ta 76Hz Ta "Sun SPARCstation, composite sync" +.It Li "D D D U" Ta 1152x900 Ta 61.5Hz Ta "NEC 4D, composite sync" +.It Li "U D D U" Ta 1152x900 Ta 66Hz Ta "Sun SPARCstation, composite sync" +.It Li "D U D U" Ta 800x600 Ta 60Hz Ta "VESA, negative separate sync" +.It Li "U U D U" Ta 800x600 Ta 72Hz Ta "VESA, negative separate sync" +.El +.Ss VS12-only Switch Settings: +The VS12 supports all of the previously listed modes, as well as a few high +resolution settings. +.Bl -column "Switches" "Resolution" "Refresh" +.It Sy Switches Ta Sy Resolution Ta Sy Refresh Ta Sy Description +.It Sy "1 2 3 4" Ta "" Ta Sy "Rate" Ta "" +.It Li "D D U U" Ta 1280x1024 Ta 60Hz Ta "NEC xD, negative separate sync" +.It Li "U D U U" Ta 1280x1024 Ta 60Hz Ta "NEC xD, composite sync" +.It Li "D U U U" Ta 1280x1024 Ta 60Hz Ta "NEC xD, sync-on-green" +.It Li "U U U U" Ta 1280x1024 Ta 67Hz Ta "Sun SPARCstation, composite sync" +.El +.Ss VS11 Switch Settings: +The VS11 supports a similar set of modes as the VS12, but with higher refresh +rates. +.Bl -column "Switches" "Resolution" "Refresh" +.It Sy Switches Ta Sy Resolution Ta Sy Refresh Ta Sy Description +.It Sy "1 2 3 4" Ta "" Ta Sy "Rate" Ta "" +.It Li "D D D D" Ta 640x480 Ta 60Hz Ta "Standard VGA, negative separate sync" +.It Li "U D D D" Ta 800x600 Ta 72Hz Ta "VESA, negative separate sync" +.It Li "D U D D" Ta 1024x768 Ta 60Hz Ta "VESA, negative separate sync" +.It Li "U U D D" Ta 1024x768 Ta 60Hz Ta "VESA, composite sync" +.It Li "D D U D" Ta 1024x768 Ta 60Hz Ta "VESA, sync-on-green" +.It Li "U D U D" Ta 1024x768 Ta 66Hz Ta "Sun 386i, composite sync" +.It Li "D U U D" Ta 1152x900 Ta 66Hz Ta "Sun SPARCstation, composite sync" +.It Li "U U U D" Ta 1152x900 Ta 76Hz Ta "Sun SPARCstation, composite sync" +.It Li "D D D U" Ta 1280x1024 Ta 67Hz Ta "Sun SPARCstation, composite sync" +.It Li "U D D U" Ta 1280x1024 Ta 60Hz Ta "NEC xFG, negative separate sync" +.It Li "D U D U" Ta 1280x1024 Ta 60Hz Ta "NEC xFG, composite sync" +.It Li "U U D U" Ta 1280x1024 Ta 60Hz Ta "NEC xFG, sync-on-green" +.It Li "D D U U" Ta 1280x1024 Ta 74Hz Ta "NEC xFG, composite sync" +.It Li "U D U U" Ta 1280x1024 Ta 74Hz Ta "NEC xFG, sync-on-green" +.It Li "D U U U" Ta 1280x1024 Ta 72Hz Ta "HP A1097, composite sync" +.It Li "U U U U" Ta 1280x1024 Ta 72Hz Ta "Special, composite sync" +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/man4.sparc64/vldc.4 b/static/openbsd/man4/man4.sparc64/vldc.4 new file mode 100644 index 00000000..1e34042e --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vldc.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: vldc.4,v 1.3 2015/11/21 08:04:20 jmc Exp $ +.\" +.\" Copyright (c) 2012 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 21 2015 $ +.Dt VLDC 4 sparc64 +.Os +.Sh NAME +.Nm vldc , +.Nm vldcp +.Nd virtual channel driver +.Sh SYNOPSIS +.Cd "vldc* at cbus?" +.Cd "vldcp* at vldc?" +.Sh DESCRIPTION +The +.Nm +driver provides access to services provided over virtual channels provided by +the UltraSPARC Hypervisor as found on sun4v systems. +Examples of such services are the Hypervisor Control Interface and the +Variable Configuration domain service. +.Sh SEE ALSO +.Xr cbus 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/vnet.4 b/static/openbsd/man4/man4.sparc64/vnet.4 new file mode 100644 index 00000000..d4597472 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vnet.4 @@ -0,0 +1,69 @@ +.\" $OpenBSD: vnet.4,v 1.4 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt VNET 4 sparc64 +.Os +.Sh NAME +.Nm vnet +.Nd virtual network interface +.Sh SYNOPSIS +.Cd "vnet* at cbus?" +.Cd "vnet* at vsw?" +.Sh DESCRIPTION +The +.Nm +driver provides a network interface using the services provided by the +UltraSPARC Hypervisor as found on sun4v systems. +It connects to a virtual switch (vsw) device or virtual network (vnet) +device in another logical domain using a logical domain channel +provided by the hypervisor. +.Pp +The +.Nm +driver supports version 1.0 of the vNet protocol. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width autoselect +.It autoselect +Enable autoselection of the media type and options. +The driver always uses the fastest available speed and the media +options provided by the underlying host of the virtual machine. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr cbus 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr vsw 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/vpci.4 b/static/openbsd/man4/man4.sparc64/vpci.4 new file mode 100644 index 00000000..ce28f1ee --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vpci.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: vpci.4,v 1.3 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt VPCI 4 sparc64 +.Os +.Sh NAME +.Nm vpci +.Nd virtual Host/PCIe bridge +.Sh SYNOPSIS +.Cd "vpci* at mainbus0" +.Cd "pci* at vpci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the virtual PCIe host bridge provided by the +UltraSPARC Hypervisor as found on sun4v systems. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/vrng.4 b/static/openbsd/man4/man4.sparc64/vrng.4 new file mode 100644 index 00000000..fd92eaab --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vrng.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: vrng.4,v 1.3 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt VRNG 4 sparc64 +.Os +.Sh NAME +.Nm vrng +.Nd virtual random number generator +.Sh SYNOPSIS +.Cd "vrng0 at vbus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the random number generation service +provided by the UltraSPARC Hypervisor as found on sun4v systems. +.Pp +Driven by periodic checks for available data from the generator, +.Nm +supplies entropy to the +.Xr random 4 +driver for common usage. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 , +.Xr vbus 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +.Sh BUGS +The +.Nm +driver should probably do periodic +.Dq health checks +when running in a Trusted Domain, but currently does not. diff --git a/static/openbsd/man4/man4.sparc64/vrtc.4 b/static/openbsd/man4/man4.sparc64/vrtc.4 new file mode 100644 index 00000000..232a9397 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vrtc.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: vrtc.4,v 1.4 2013/07/16 16:05:50 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt VRTC 4 sparc64 +.Os +.Sh NAME +.Nm vrtc +.Nd virtual real-time clock +.Sh SYNOPSIS +.Cd "vrtc0 at vbus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the time of day service provided by the +UltraSPARC Hypervisor as found on sun4v systems. +.Sh SEE ALSO +.Xr intro 4 , +.Xr vbus 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/vsw.4 b/static/openbsd/man4/man4.sparc64/vsw.4 new file mode 100644 index 00000000..7683d00a --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/vsw.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: vsw.4,v 1.4 2022/07/21 08:00:31 kn Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 21 2022 $ +.Dt VSW 4 sparc64 +.Os +.Sh NAME +.Nm vsw +.Nd virtual network switch +.Sh SYNOPSIS +.Cd "vsw* at cbus?" +.Cd "vnet* at vsw?" +.Sh DESCRIPTION +The +.Nm +driver provides a network switch using the services provided by the +UltraSPARC Hypervisor as found on sun4v systems. +It attaches a separate +.Xr vnet 4 +interface for each switch port. +These ports can be added to a +.Xr bridge 4 +or +.Xr veb 4 +to create a functional network switch. +.Pp +The +.Nm +driver supports version 1.0 of the vNet protocol. +.Sh SEE ALSO +.Xr bridge 4 , +.Xr cbus 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr veb 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/man4.sparc64/xbox.4 b/static/openbsd/man4/man4.sparc64/xbox.4 new file mode 100644 index 00000000..af8479b1 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/xbox.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: xbox.4,v 1.2 2007/05/31 19:19:57 jmc Exp $ +.\" +.\" Copyright (c) 1999 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt XBOX 4 sparc64 +.Os +.Sh NAME +.Nm xbox +.Nd SPARC SBus Expansion Subsystem +.Sh SYNOPSIS +.Cd "xbox* at sbus?" +.Cd "sbus* at xbox?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Sun SBus Expansion Subsystem. +This device consists of an SBus card and a chassis which has +three additional SBus slots. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 +.Sh BUGS +DMA support through +.Nm +is currently not implemented. +This means that SBus devices using DMA (such as SCSI and some Ethernet +controllers) will not attach correctly, and will not work. diff --git a/static/openbsd/man4/man4.sparc64/zs.4 b/static/openbsd/man4/man4.sparc64/zs.4 new file mode 100644 index 00000000..6f41ea69 --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/zs.4 @@ -0,0 +1,183 @@ +.\" $OpenBSD: zs.4,v 1.18 2015/11/21 08:04:21 jmc Exp $ +.\" +.\" Copyright (c) 1998, 2002 The OpenBSD Project +.\" All rights reserved. +.\" +.\" +.Dd $Mdocdate: November 21 2015 $ +.Dt ZS 4 sparc64 +.Os +.Sh NAME +.Nm zs , +.Nm zstty , +.Nm zskbd , +.Nm zsms +.Nd Zilog 8530 (ZSCC) serial communications driver +.Sh SYNOPSIS +.Cd "zs* at fhc?" +.Cd "zs* at sbus?" +.Cd "zstty* at zs?" +.Cd "zskbd* at zs?" +.Cd "wskbd* at zskbd?" +.Cd "zsms* at zs?" +.Cd "wsmouse* at zsms?" +.Cd "option SUNKBD_LAYOUT=XXX" +.Cd "option SUNKBD5_LAYOUT=XXX" +.Sh DESCRIPTION +The +.Nm +is a Zilog 8530 serial interface chip used in SBus-based UltraSPARC +.Tn Sun +workstations. +The Zilog 8530 provides two input/output channels per instance. +Most +.Tn Sun +workstations include two of these interfaces. +One of the interfaces is usually hardwired for use by the keyboard and mouse +attached to the workstation console. +The +.Nm zskbd +devices connect keyboard devices to the generic keyboard driver +.Nm wskbd . +The +.Nm zsms +devices connect mice to the generic mouse driver +.Xr wsmouse 4 . +The remaining additional +.Nm zs +interfaces provide RS-423 +and RS-232 serial ports for general purpose use. +.Pp +The +.Nm +driver supports all of the standard +.Xr tty 4 +ioctl calls. +The status of the DTR, RTS, CTS, and DCD signals can be queried with +TIOCMGET command, but, due to limitations in the hardware, +only the DTR and RTS signals can be modified with TIOCMSET, TIOCMBIC, +and TIOCMBIS +.Xr ioctl 2 +commands. +.Pp +The +.Nm zskbd +driver supports a number of different key mappings. +By default, the layout corresponding to the keyboard model +as probed by the +.Nm zskbd +driver will be used. +A different layout can be chosen either with the kernel options +.Dq SUNKBD_LAYOUT +(for type 4 keyboards) +and +.Dq SUNKBD5_LAYOUT +(for type 5 keyboards) +at compile time or with the utility +.Xr wsconsctl 8 +(variable: +.Dq keyboard.encoding ) +at runtime. +.Pp +Other mappings can be used if the whole keymap is replaced by means of +.Xr wsconsctl 8 . +The built-in mappings are at this time: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It KB_BE +.Pq be +Belgium French (type 4 only). +.It KB_DE +.Pq de +German. +.It KB_DK +.Pq dk +Danish. +.It KB_ES +.Pq es +Spanish. +.It KB_FR +.Pq fr +French (type 5 only). +.It KB_IT +.Pq it +Italian. +.It KB_JP +.Pq jp +Japanese (type 5 only). +.It KB_NL +.Pq \&nl +Dutch. +.It KB_NO +.Pq no +Norwegian. +.It KB_PT +.Pq pt +Portuguese. +.It KB_SF +.Pq sf +Swiss French. +.It KB_SG +.Pq sg +Swiss German. +.It KB_SV +.Pq sv +Swedish with +.Dq dead accents . +.It KB_UK +.Pq uk +British. +.It KB_US +.Pq us +English/US keyboard mapping. +.El +.Pp +The KB_SV mapping can be used in +the KB_NODEAD +.Pq .nodead +variant. +This switches off the +.Dq dead accents . +.Sh EXAMPLES +To set a German keyboard layout, use +.Ic wsconsctl keyboard.encoding=de . +To set it at kernel build time, add +the following to the kernel configuration file for a type 4 keyboard: +.Bd -literal -offset indent +option SUNKBD_LAYOUT="KB_DE" +.Ed +.Pp +For a type 5 keyboard: +.Bd -literal -offset indent +option SUNKBD5_LAYOUT="KB_DE" +.Ed +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr fhc 4 , +.Xr intro 4 , +.Xr sbus 4 , +.Xr tty 4 , +.Xr wskbd 4 , +.Xr wsmouse 4 , +.Xr wsconsctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Bx 4.4 . +Support for the TIOCM* +.Xr ioctl 2 Ns s +appeared in +.Ox 2.3 . +.Sh BUGS +The +.Nm +driver now supports cua minor devices, but with this known deficiency +in the simultaneous outgoing/incoming aspect of the driver: +The first outgoing connection succeeds, but second and subsequent +connections fail, apparently due to a getty hang. +The hung getty apparently prevents the cua device from being re-opened. +.Pp +The kernel does not provide a keyboard layout for all manufactured +.Tn Sun +keyboard models. diff --git a/static/openbsd/man4/man4.sparc64/zx.4 b/static/openbsd/man4/man4.sparc64/zx.4 new file mode 100644 index 00000000..d40ddd2f --- /dev/null +++ b/static/openbsd/man4/man4.sparc64/zx.4 @@ -0,0 +1,95 @@ +.\" $OpenBSD: zx.4,v 1.13 2011/09/03 22:59:07 jmc Exp $ +.\" Copyright (c) 2003 Miodrag Vallat. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 3 2011 $ +.Dt ZX 4 sparc64 +.Os +.Sh NAME +.Nm zx +.Nd accelerated 24-bit color frame buffer +.Sh SYNOPSIS +.Cd "zx* at sbus?" +.Cd "wsdisplay* at zx?" +.Sh DESCRIPTION +The ZX and TurboZX +are dual-slot SBus color frame buffers, with graphics acceleration +and overlay capabilities. +They are also known as the +.Tn Sun +.Dq Leo +graphics card. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh DISPLAY RESOLUTION +The following resolutions are supported by the ZX frame buffer: +.Bl -column "Resolution" "Refresh Rate" "Details" -offset indent +.It Sy Resolution Ta Sy "Refresh Rate" Ta Sy "Details" +.It Li 1280x1024 Ta 76 Hz Ta Non-interlaced +.It Li 1280x1024 Ta 67 Hz Ta Non-interlaced +.It Li 1152x900 Ta 76 Hz Ta Non-interlaced +.It Li 1152x900 Ta 66 Hz Ta Non-interlaced +.It Li 1024x768 Ta 76 Hz Ta Non-interlaced +.It Li 1024x768 Ta 60 Hz Ta Non-interlaced +.\" Is it worth documenting the Stereo and TV modes? +.It Li 960x680 Ta 112 Hz Ta "Stereo, non-interlaced 56 Hz field rate per eye" +.It Li 960x680 Ta 108 Hz Ta "Stereo, non-interlaced 54 Hz field rate per eye" +.It Li 770x575 Ta 50 Hz Ta "Interlaced - PAL" +.It Li 640x480 Ta 59.94 Hz Ta "Interlaced - NTSC" +.El +.Pp +If the ZX frame buffer is connected to a monitor at boot time, it will +select its display resolution depending of the monitor +.Sq select code +provided by the 13W3 connector. +If the frame buffer is not connected to a monitor, the default resolution +of 1152x900, with a 66 Hz refresh rate, will be selected. +The selected resolutions are: +.Bl -column "sense code" "Resolution" "Refresh" "Monitor" +.It Sy Monitor Ta Sy Resolution Ta Sy Refresh Ta Sy Monitor +.It Sy "sense code" Ta "" Ta Sy Rate Ta Sy Type +.It Li 0 Ta 1024x768 Ta "76 Hz" Ta "X449A" +.It Li 1 Ta 1152x900 Ta "66 Hz" Ta "" +.It Li 2 Ta 1280x1024 Ta "76 Hz" Ta "X248A, GDM-205S" +.It Li 3 Ta 1152x900 Ta "66 Hz" Ta "GDM-1955A15, GDM-1604A15, CPD-1790" +.It Li 4 Ta 1280x1024 Ta "67 Hz" Ta "GDM-20D10, GDM-1962" +.It Li 5 Ta 1152x900 Ta "66 Hz" Ta "" +.It Li 6 Ta 1152x900 Ta "76 Hz" Ta "GDM-1662B, 17SMM4" +.It Li 7 Ta 1152x900 Ta "66 Hz" Ta "" +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr sbus 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh CAVEATS +There is currently no software interface to change the frame buffer +resolution at runtime. diff --git a/static/openbsd/man4/maxds.4 b/static/openbsd/man4/maxds.4 new file mode 100644 index 00000000..d90f2c03 --- /dev/null +++ b/static/openbsd/man4/maxds.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: maxds.4,v 1.7 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt MAXDS 4 +.Os +.Sh NAME +.Nm maxds +.Nd Maxim DS1624/DS1631/DS1721 temperature sensor +.Sh SYNOPSIS +.Cd "maxds* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Maxim DS1624/DS1631/DS1721 +temperature sensor. +The sensor possesses just one accurate temperature sensor; the +value is made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/maxrtc.4 b/static/openbsd/man4/maxrtc.4 new file mode 100644 index 00000000..1b9146ab --- /dev/null +++ b/static/openbsd/man4/maxrtc.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: maxrtc.4,v 1.4 2022/10/25 05:49:40 jmc Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt +.\" Copyright (c) 2016 Marcus Glocker +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 25 2022 $ +.Dt MAXRTC 4 +.Os +.Sh NAME +.Nm maxrtc +.Nd Maxim DS1307/DS1339 real-time clock +.Sh SYNOPSIS +.Cd "maxrtc* at iic?" +.Sh DESCRIPTION +The +.Nm +driver supports the Maxim DS1307 and DS1339 real-time clock chips, +which provide a low-power, full binary-coded decimal (BCD) clock/calendar. +In addition, the DS1307 comes with 56 bytes of NV SRAM. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marcus Glocker Aq Mt mglocker@openbsd.org . diff --git a/static/openbsd/man4/maxtmp.4 b/static/openbsd/man4/maxtmp.4 new file mode 100644 index 00000000..4cae2c8f --- /dev/null +++ b/static/openbsd/man4/maxtmp.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: maxtmp.4,v 1.9 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt MAXTMP 4 +.Os +.Sh NAME +.Nm maxtmp +.Nd Maxim MAX6642/MAX6690 temperature sensor +.Sh SYNOPSIS +.Cd "maxtmp* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Maxim 6642, Maxim 6657, Maxim 6658, +Maxim 6659, Maxim 6690, National LM86, National LM89, National LM90, +National LM99, and National LM99-1 temperature sensors. +The sensor possesses an internal temperature sensor and a link +to an external temperature sensor. +Both values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/mbg.4 b/static/openbsd/man4/mbg.4 new file mode 100644 index 00000000..af73669d --- /dev/null +++ b/static/openbsd/man4/mbg.4 @@ -0,0 +1,104 @@ +.\" $OpenBSD: mbg.4,v 1.16 2024/03/23 10:38:02 sthen Exp $ +.\" +.\" Copyright (c) 2006 Marc Balmer +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 23 2024 $ +.Dt MBG 4 +.Os +.Sh NAME +.Nm mbg +.Nd Meinberg Funkuhren timedelta sensor +.Sh SYNOPSIS +.Cd "mbg* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Meinberg Funkuhren radio clocks (time signal +station and GPS receivers). +.Nm +implements a timedelta sensor and the delta (in nanoseconds) between the +received time information and the local time can be accessed through the +.Xr sysctl 8 +interface. +.Pp +The card type is indicated in the sensor description. +Currently, the following cards are supported by +.Nm : +.Pp +.Bl -tag -width "GPS170XXX" -offset indent -compact +.It GPS170PCI +3.3V/5V 6-channel GPS receiver card +.It PCI32 +5V DCF77 time signal station receiver card +.It PCI509 +5V DCF77 time signal station receiver card +.It PCI510 +3.3V/5V DCF77 time signal station receiver card +.It PCI511 +3.3V/5V DCF77 time signal station receiver card +.It PEX511 +PCI Express DCF77 time signal station receiver card +.It PZF180PEX +PCI Express DCF77 time signal station receiver card +.El +.Pp +The quality of the timedelta is reported as the sensor status: +.Bl -tag -width "CRITICALXX" -offset indent +.It UNKNOWN +No valid time information has been received yet. +.It OK +The time information is valid and the timedelta is safe to use for +applications like +.Xr ntpd 8 . +.It WARN +The time information is still valid, but no new time information has been +decoded for twelve hours (four days in the case of a GPS170PCI card) due to +a reception or parity error. +The timedelta should be used with care. +.It CRITICAL +No valid time information has been received for more than twelve hours (or +four days in the case of a GPS170PCI card) since the sensor state degraded +from OK to WARN. +This is an indication that hardware should be checked to see if it is still +functional. +.El +.Pp +A second sensor provides the relative signal quality as a percentage. +The status of this sensor is used to report the status of the device itself: +.Bl -tag -width "CRITICALXX" -offset indent +.It OK +The clock is synchronized. +.It WARN +The device's clock is free running on the local oscillator. +For DCF77 receiver cards this is not an error and can happen due to the +nature of the signal transmission using longwave radio. +.It CRITICAL +Hardware failure, e.g. communication with the device failed. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr ntpd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Marc Balmer Aq Mt mbalmer@openbsd.org . diff --git a/static/openbsd/man4/mcprtc.4 b/static/openbsd/man4/mcprtc.4 new file mode 100644 index 00000000..629669ab --- /dev/null +++ b/static/openbsd/man4/mcprtc.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: mcprtc.4,v 1.1 2019/09/06 09:38:19 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 6 2019 $ +.Dt MCPRTC 4 +.Os +.Sh NAME +.Nm mcprtc +.Nd Microchip MCP79400 real-time clock +.Sh SYNOPSIS +.Cd "mcprtc* at iic? addr 0x6f" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Microchip MCP79400 real-time clock chip +and similar variants. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/mcx.4 b/static/openbsd/man4/mcx.4 new file mode 100644 index 00000000..fc39fee4 --- /dev/null +++ b/static/openbsd/man4/mcx.4 @@ -0,0 +1,66 @@ +.\" $OpenBSD: mcx.4,v 1.4 2024/03/21 04:10:37 jmatthew Exp $ +.\" +.\" Copyright (c) 2019 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 21 2024 $ +.Dt MCX 4 +.Os +.Sh NAME +.Nm mcx +.Nd Mellanox 5th generation Ethernet device +.Sh SYNOPSIS +.Cd "mcx* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports Mellanox 5th generation Ethernet devices. +Chipsets and cards in this group include: +.Pp +.Bl -bullet -offset indent -compact +.It +ConnectX-4 Lx EN +.It +ConnectX-4 EN +.It +ConnectX-5 EN +.It +ConnectX-6 EN +.It +ConnectX-6 Dx EN +.It +ConnectX-6 Lx EN +.El +.Pp +It supports SR-IOV virtual functions as well as physical functions. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org +and +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/mfi.4 b/static/openbsd/man4/mfi.4 new file mode 100644 index 00000000..b6a380a2 --- /dev/null +++ b/static/openbsd/man4/mfi.4 @@ -0,0 +1,103 @@ +.\" $OpenBSD: mfi.4,v 1.20 2013/11/08 11:07:42 mikeb Exp $ +.\" +.\" Written by Marco Peereboom +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY WASABI SYSTEMS, INC. ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL WASABI SYSTEMS, INC +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 8 2013 $ +.Dt MFI 4 +.Os +.Sh NAME +.Nm mfi +.Nd LSI Logic & Dell MegaRAID SAS RAID controller +.Sh SYNOPSIS +.Cd "mfi* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the MegaRAID SAS family of RAID controllers, +including: +.Pp +.Bl -dash -offset indent -compact +.It +Dell PERC 5/e, +PERC 5/i, +PERC 6/e, +PERC 6/i, +PERC H310, +PERC H700, +PERC H800 +.It +IBM ServeRAID M1115 +.It +Intel RAID Controller SRCSAS18E, +SRCSAS144E +.It +LSI Logic MegaRAID SAS 8300XLP, +MegaRAID SAS 8308ELP, +MegaRAID SAS 8344ELP, +MegaRAID SAS 8408E, +MegaRAID SAS 8480E, +MegaRAID SAS 8880EM2, +MegaRAID SAS 8888ELP, +MegaRAID SAS 9240-4i, +MegaRAID SAS 9240-8i, +MegaRAID SAS 9260-16i, +MegaRAID SAS 9260-4i, +MegaRAID SAS 9260-8i, +MegaRAID SAS 9260CV-4i, +MegaRAID SAS 9260CV-8i, +MegaRAID SAS 9261-8i, +MegaRAID SAS 9265-8i, +MegaRAID SAS 9280-16i4e, +MegaRAID SAS 9280-24i4e, +MegaRAID SAS 9280-4i4e, +MegaRAID SAS 9280-8e, +MegaRAID SAS 9285-8e +.El +.Pp +These controllers support RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, RAID 50 and +RAID 60 using either SAS or SATA II drives. +.Pp +Although the controllers are actual RAID controllers, +the driver makes them look just like SCSI controllers. +All RAID configuration is done through the controllers' BIOSes. +.Sh SEE ALSO +.Xr bio 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr bioctl 8 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marco Peereboom Aq Mt marco@openbsd.org . diff --git a/static/openbsd/man4/mfii.4 b/static/openbsd/man4/mfii.4 new file mode 100644 index 00000000..af47f766 --- /dev/null +++ b/static/openbsd/man4/mfii.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: mfii.4,v 1.8 2024/02/05 19:07:45 deraadt Exp $ +.\" +.\" Copyright (c) 2012 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 5 2024 $ +.Dt MFII 4 +.Os +.Sh NAME +.Nm mfii +.Nd LSI Logic MegaRAID SAS Fusion RAID controller +.Sh SYNOPSIS +.Cd "mfii* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the MegaRAID SAS Fusion family of RAID controllers +using the following chipsets: +.Pp +.Bl -dash -offset indent -compact +.It +SAS2208 +.It +SAS3008 +.It +SAS3108 +.It +SAS3404 +.It +SAS3408 +.It +SAS3416 +.It +SAS3504 +.It +SAS3508 +.It +SAS3516 +.It +SAS3816 +.It +SAS3916 +.El +.Pp +These controllers support RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, RAID 50 and +RAID 60 using either SAS or SATA II drives. +.Pp +Although the controllers are actual RAID controllers, +they appear as SCSI controllers. +All RAID configuration is done through the controllers' BIOSes. +.Sh SEE ALSO +.Xr bio 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr bioctl 8 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/mfokrtc.4 b/static/openbsd/man4/mfokrtc.4 new file mode 100644 index 00000000..777d2902 --- /dev/null +++ b/static/openbsd/man4/mfokrtc.4 @@ -0,0 +1,31 @@ +.\" $OpenBSD: mfokrtc.4,v 1.1 2020/09/30 22:23:40 patrick Exp $ +.\" +.\" Copyright (c) 2010 Miodrag Vallat. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 30 2020 $ +.Dt MFOKRTC 4 +.Os +.Sh NAME +.Nm mfokrtc +.Nd M41T8x real-time clock +.Sh SYNOPSIS +.Cd "mfokrtc* at iic? addr 0x68" +.Sh DESCRIPTION +The +.Nm +driver supports two-wire real-time clock chips of the M41T8x family. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 diff --git a/static/openbsd/man4/midi.4 b/static/openbsd/man4/midi.4 new file mode 100644 index 00000000..33fbc5d7 --- /dev/null +++ b/static/openbsd/man4/midi.4 @@ -0,0 +1,272 @@ +.\" $OpenBSD: midi.4,v 1.31 2022/03/31 17:30:05 naddy Exp $ +.\" +.\" Copyright (c) 2006 Alexandre Ratchov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt MIDI 4 +.Os +.Sh NAME +.Nm midi +.Nd raw device independent interface to MIDI ports +.Sh SYNOPSIS +.Cd "midi* at autri?" +.Cd "midi* at eap?" +.Cd "midi* at envy?" +.Cd "midi* at mpu?" +.Cd "midi* at sb?" +.Cd "midi* at umidi?" +.Cd "midi* at ym?" +.Sh DESCRIPTION +The +.Nm +driver makes MIDI ports available to user applications. +A +.Nm +device corresponds to 2 MIDI ports: one input port and one +output port. +Data received on the input port is not interpreted and is passed +to the user program as-is. +Similarly, data issued by the user program is sent as-is to the +output port. +.Pp +Only one process may hold open a +.Nm +device at a given time, although file descriptors may be shared +between processes once the first open completes. +If it is opened read-only (write-only), only the input (output) +MIDI port is available. +.Ss Writing to the device +A process can send raw MIDI data to the output port by using the +.Xr write 2 +system call. +Data is queued and the system call returns immediately; the data +is sent as fast as possible to the output MIDI port. +However, if the in-kernel buffer is full or the requested amount +is too large, then +.Xr write 2 +may block. +The current size of the in-kernel buffer is 1024 bytes, which +ensures that +.Xr write 2 +isn't blocking in most situations. +.Ss Reading from the device +Data received from the input MIDI port is stored into the +in-kernel buffer. +A process can retrieve its contents by using +the +.Xr read 2 +system call. +If there is less data than the amount requested for reading, then +a shorter amount is returned. +If no data is available, then the +.Xr read 2 +system call will block until data is received, +and then return immediately. +.Pp +The MIDI protocol has been designed for real-time performance and +doesn't support flow control. +An application must be able to read the incoming data fast enough +(the MIDI standard's maximum rate is 3125 bytes per second). +The kernel can buffer up to 1024 bytes; once the buffer is full +input will be silently discarded. +.Ss Polling the device +A process can use the +.Xr poll 2 +system call to poll for the following events: +.Bl -tag -width POLLOUT +.It Dv POLLIN +The in-kernel input buffer isn't empty, i.e. at least one byte is +available for reading. +A subsequent call to +.Xr read 2 +will not be blocking. +.It Dv POLLOUT +The in-kernel output buffer is empty, thus a subsequent call to +.Xr write 2 +will not be blocking if a reasonable amount of data is written +(currently less that 1024 bytes). +.El +.Pp +Using the +.Xr poll 2 +system call is the recommended way to handle multiple +.Nm +devices in a real-time MIDI application. +.Ss Non-blocking I/O +If the +.Nm +device is opened with the O_NONBLOCK flag (see +.Xr open 2 ) , +then subsequent calls to +.Xr read 2 +or +.Xr write 2 +will never block. +The +.Xr write 2 +system call may write less bytes than requested, or may return +EAGAIN if no data could be sent or queued. +Similarly, the +.Xr read 2 +system call may return EAGAIN if no input is available. +.Pp +Note that even if non-blocking I/O is not selected, +.Xr read 2 +and +.Xr write 2 +system calls are non-blocking when the kernel buffers permit it. +.Sh FILES +.Bl -tag -width /dev/rmidim -compact +.It Pa /dev/rmidi* +.Nm +devices +.El +.Sh EXAMPLES +The following command could record the memory dump of a +synthesizer in a file: +.Pp +.Dl $ cat -u /dev/rmidi2 >dumpfile +.Pp +A MIDI keyboard could be connected to a synthesizer by the +command: +.Pp +.Dl $ cat -u /dev/rmidi1 >/dev/rmidi2 +.Pp +The input port could be connected to the output port by the +command: +.Pp +.Dl $ cat -u <>/dev/rmidi1 >&0 +.Pp +The following example reads MIDI timing events from an input +device, MIDI common and voice events from another input device, and +sends the result to a third (output) device. +.Bd -literal -offset indent +#define BUFSIZE 0x100 +#define ISTIMING(c) ((c) == 0xf8 || (c) == 0xfa || (c) == 0xfc) +#define ISCOMMON(c) ((c) < 0xf8) + +int ofd; +struct pollfd ifd[2]; +unsigned char ibuf[BUFSIZE], obuf[2 * BUFSIZE]; +ssize_t iused, oused, i; + +ifd[0].events = ifd[1].events = POLLIN; +for (;;) { + oused = 0; + if (poll(ifd, 2, -1) == -1) + errx(1, "poll"); + if (ifd[0].revents & POLLIN) { + if ((iused = read(ifd[0].fd, ibuf, BUFSIZE)) == -1) + errx(1, "read"); + for (i = 0; i < iused; i++) + if (ISTIMING(ibuf[i])) + obuf[oused++] = ibuf[i]; + } + if (ifd[1].revents & POLLIN) { + if ((iused = read(ifd[1].fd, ibuf, BUFSIZE)) == -1) + errx(1, "read"); + for (i = 0; i < iused; i++) + if (ISCOMMON(ibuf[i])) + obuf[oused++] = ibuf[i]; + } + if (write(ofd, obuf, oused) == -1) + errx(1, "write"); +} +.Ed +.Pp +In the above example, unless kernel buffers are full, processing +is done in real-time without any noticeable latency; as expected, +the only blocking system call is +.Xr poll 2 . +.Sh ERRORS +If +.Xr open 2 , +.Xr read 2 , +.Xr write 2 , +or +.Xr poll 2 +fail then +.Xr errno 2 +may be set to one of: +.Bl -tag -width Er +.It Bq Er ENXIO +The device is opened read-only (write-only) but +.Xr write 2 +.Pf ( Xr read 2 ) +was called. +.It Bq Er EIO +The device is being detached while a process has been trying to +read or write (for instance an +.Xr umidi 4 +device has been unplugged). +.It Bq Er EAGAIN +Non-blocking I/O was selected and the output buffer is full (on +writing) or the input buffer is empty (on reading). +.It Bq Er EBUSY +The device is already open by another process. +.El +.Sh SEE ALSO +.Xr autri 4 , +.Xr eap 4 , +.Xr envy 4 , +.Xr mpu 4 , +.Xr sb 4 , +.Xr umidi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was originally written by +.An Lennart Augustsson +and later largely rewritten by +.An Alexandre Ratchov . +.Sh CAVEATS +MIDI hardware was designed for real time performance and software +using such hardware must be able to process MIDI events without +any noticeable latency (typically no more than 5ms, which +is the time it takes for sound to propagate 1.75 meters). +.Pp +The +.Ox +.Nm +driver processes data fast enough, however if a MIDI application +tries to write data faster than the hardware is able to process it +(typically 3125 bytes per second), then kernel buffers may become +full and the application may be blocked. +.Pp +The other common reason for MIDI data being delayed is the system +load. +Processes cannot be preempted while running in kernel mode. +If there are too many processes running concurrently (especially +if they are running a lot of expensive system calls) then the +scheduling of a real-time MIDI application may be delayed. +Even on low-end machines this delay hardly reaches a few +milliseconds provided that the system load is reasonable. +.Pp +A real-time MIDI application can avoid being swapped by locking +its memory (see +.Xr mlock 2 +and +.Xr mlockall 2 ) . +.Sh BUGS +For a given device, even if the physical MIDI input and output +ports are independent, there is no way for one process to use the +input MIDI port and for another process to use the output MIDI +port at the same time. diff --git a/static/openbsd/man4/mii.4 b/static/openbsd/man4/mii.4 new file mode 100644 index 00000000..453dac64 --- /dev/null +++ b/static/openbsd/man4/mii.4 @@ -0,0 +1,107 @@ +.\" $OpenBSD: mii.4,v 1.32 2023/03/06 06:56:49 jmc Exp $ +.\" $NetBSD: mii.4,v 1.1 1998/11/04 05:21:50 thorpej Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 6 2023 $ +.Dt MII 4 +.Os +.Sh NAME +.Nm mii +.Nd IEEE 802.3 Media Independent Interface +.Sh SYNOPSIS +.Cd "acphy* at mii?" +.Cd "amphy* at mii?" +.Cd "atphy* at mii?" +.Cd "bmtphy* at mii?" +.Cd "brgphy* at mii?" +.Cd "ciphy* at mii?" +.Cd "dcphy* at mii?" +.Cd "eephy* at mii?" +.Cd "etphy* at mii?" +.Cd "exphy* at mii?" +.Cd "gentbi* at mii?" +.Cd "icsphy* at mii?" +.Cd "ipgphy* at mii?" +.Cd "inphy* at mii?" +.Cd "iophy* at mii?" +.Cd "jmphy* at mii?" +.Cd "luphy* at mii?" +.Cd "lxtphy* at mii?" +.Cd "mtdphy* at mii?" +.Cd "nsgphy* at mii?" +.Cd "nsphy* at mii?" +.Cd "nsphyter* at mii?" +.Cd "qsphy* at mii?" +.Cd "rdcphy* at mii?" +.Cd "rgephy* at mii?" +.Cd "rlphy* at mii?" +.Cd "sqphy* at mii?" +.Cd "tlphy* at mii?" +.Cd "tqphy* at mii?" +.Cd "txphy* at mii?" +.Cd "ukphy* at mii?" +.Cd "urlphy* at mii?" +.Cd "xmphy* at mii?" +.Cd "ytphy* at mii?" +.Sh DESCRIPTION +Media Independent Interface is an IEEE standard serial bus for +connecting MACs (network controllers) to PHYs (physical media +interfaces). +The +.Nm +layer allows network device drivers to share support code for +various PHY models, and allows unused support for PHYs which +are not present in a system to be removed from the kernel. +.Pp +Network device drivers which use the +.Nm +layer carry the +.Dq mii +autoconfiguration attribute. +This allows kernel configuration files to simply specify PHYs as +described above in +.Sx SYNOPSIS . +.Pp +The following is an example of the messages displayed when a network +interface with an attached PHY is detected by the kernel: +.Bd -literal -offset indent +hme0 at sbus0 slot 1 offset 0x8c00000 pri 7: address 08:00:20:22:86:b8 rev 34 +nsphy0 at hme0 phy 1: DP83840 10/100 PHY, rev. 1 +.Ed +.Pp +Supported media types for the PHY can be displayed or set using the +.Xr ifconfig 8 +.Cm media +keyword. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/mlphy.4 b/static/openbsd/man4/mlphy.4 new file mode 100644 index 00000000..aa362902 --- /dev/null +++ b/static/openbsd/man4/mlphy.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: mlphy.4,v 1.1 2011/03/28 15:25:37 claudio Exp $ +.\" +.\" Copyright (c) 2011 Loganaden V. Velvindron +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: March 28 2011 $ +.Dt MLPHY 4 +.Os +.Sh NAME +.Nm mlphy +.Nd MicroLinear 6692 Ethernet PHY +.Sh SYNOPSIS +.Cd "mlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports MicroLinear 6692 10/100 Ethernet PHYs. +The MicroLinear PHY only supports 100baseTX operation but can advertise +10baseT operation for a possible companion PHY. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 +.Sh BUGS +The OUI and device identification of the MicroLinear 6692 PHY are +undefined and so +.Nm +only attaches to +.Xr tl 4 +devices using the +.Xr tlphy 4 +as companion PHY. diff --git a/static/openbsd/man4/mos.4 b/static/openbsd/man4/mos.4 new file mode 100644 index 00000000..bf0f200a --- /dev/null +++ b/static/openbsd/man4/mos.4 @@ -0,0 +1,126 @@ +.\" Copyright (c) 1997, 1998, 1999, 2000-2003 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/axe.4,v 1.3 2003/05/29 21:28:35 ru Exp $ +.\" $OpenBSD: mos.4,v 1.12 2022/02/18 10:24:32 jsg Exp $ +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt MOS 4 +.Os +.Sh NAME +.Nm mos +.Nd MosChip MCS7730/7830/7832 10/100 USB Ethernet device +.Sh SYNOPSIS +.Cd "mos* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Ethernet adapters based on the MosChip +MCS7730, MCS7830 and MCS7832 USB 2.0 chipsets, including the +following: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Delock 61147 +.It Sitecom LN-030 +.It Syba SY-U2LAN +.El +.Pp +All adapters operate with either USB 1.x or USB 2.0 controllers, +though performance with 1.x controllers is limited since +the USB 1.x standard specifies a maximum transfer speed of 12Mbps. +Users with USB 1.x controllers should therefore not expect to actually +achieve 100Mbps speeds with these devices. +.Pp +A 64-bit multicast hash table is supported, +single perfect filter entry for the station address, +all-multicast mode, and promiscuous mode. +Packets are +received and transmitted over separate USB bulk transfer endpoints. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width "autoselect" +.It autoselect +Enable autoselection of the media type and options (this is the default). +The user can manually override the autoselected mode by adding media +options to the appropriate +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width "full-duplex" +.It full-duplex +Force full-duplex operation. +.It half-duplex +Force half-duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "mos0: watchdog timeout" +A packet was queued for transmission and a transmit command was +issued, however the device failed to acknowledge the transmission +before a timeout expired. +.It "mos0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T "MosChip India" +.%U https://moschip.com +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Johann Christian Rode Aq Mt jcrode@gmx.net . diff --git a/static/openbsd/man4/moscom.4 b/static/openbsd/man4/moscom.4 new file mode 100644 index 00000000..1cfb7de1 --- /dev/null +++ b/static/openbsd/man4/moscom.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: moscom.4,v 1.4 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt MOSCOM 4 +.Os +.Sh NAME +.Nm moscom +.Nd MosChip Semiconductor MCS7703 based USB serial adapter +.Sh SYNOPSIS +.Cd "moscom* at uhub?" +.Cd "ucom* at moscom?" +.Sh DESCRIPTION +The +.Nm +driver supports MosChip Semiconductor MCS7703 based serial adapters. +.Pp +The following devices should work with the +.Nm +driver: +.Bd -literal -offset indent +Syba SY-USB-S +.Ed +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan Gray Aq Mt jsg@openbsd.org . diff --git a/static/openbsd/man4/mpath.4 b/static/openbsd/man4/mpath.4 new file mode 100644 index 00000000..366b6c9d --- /dev/null +++ b/static/openbsd/man4/mpath.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: mpath.4,v 1.6 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2009 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt MPATH 4 +.Os +.Sh NAME +.Nm mpath +.Nd SCSI multipath +.Sh SYNOPSIS +.Cd "emc* at scsibus?" +.Cd "hds* at scsibus?" +.Cd "rdac* at scsibus?" +.Cd "sym* at scsibus?" +.Pp +.Cd "mpath0 at root" +.Sh DESCRIPTION +.Nm +provides access, I/O multiplexing, and failover support to SCSI +logical units that can have multiple physical connections to the +system. +It uses connections presented by path drivers, for example +.Xr sym 4 , +as backends to a single device attached to its own +.Xr scsibus 4 . +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr emc 4 , +.Xr hds 4 , +.Xr intro 4 , +.Xr rdac 4 , +.Xr scsi 4 , +.Xr sym 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/mpe.4 b/static/openbsd/man4/mpe.4 new file mode 100644 index 00000000..91732bbe --- /dev/null +++ b/static/openbsd/man4/mpe.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: mpe.4,v 1.12 2021/05/14 13:10:20 kn Exp $ +.\" +.\" Copyright (C) 2008 Pierre-Yves Ritschard +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 14 2021 $ +.Dt MPE 4 +.Os +.Sh NAME +.Nm mpe +.Nd MPLS Provider Edge +.Sh SYNOPSIS +.Cd "pseudo-device mpe" +.Sh DESCRIPTION +The +.Nm +interface is a Multiprotocol Label Switching (MPLS) Provider Edge +pseudo-device used to enter and leave an MPLS domain. +.Pp +An +.Nm +interface can be created at runtime using the +.Ic ifconfig mpe Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The interface itself can be configured with +.Xr ifconfig 8 ; +see its manual page for more information. +.Sh IOCTLS +The following +.Xr ioctl 2 +calls are specific to +.Nm , +.Xr mpip 4 +and +.Xr mpw 4 +interfaces: +.Bl -tag -width "SIOCSETLABEL" -offset 3n +.It SIOCSETLABEL +Encapsulate packets entering this interface in MPLS using +the specified label. +.It SIOCGETLABEL +Report the label that packets entering this interface will be +tagged with. +.It SIOCDELLABEL +Unset the MPLS label. +.El +.\" +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr mpip 4 , +.Xr mpw 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr ldpd 8 , +.Xr netstart 8 +.\" +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 4.4 . +.\" +.Sh AUTHORS +The +.Nm +driver was written by +.An Pierre-Yves Ritschard Aq Mt pyr@openbsd.org . diff --git a/static/openbsd/man4/mpi.4 b/static/openbsd/man4/mpi.4 new file mode 100644 index 00000000..ffa4a546 --- /dev/null +++ b/static/openbsd/man4/mpi.4 @@ -0,0 +1,144 @@ +.\" $OpenBSD: mpi.4,v 1.20 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt MPI 4 +.Os +.Sh NAME +.Nm mpi +.Nd LSI Logic Fusion-MPT Message Passing Interface +.Sh SYNOPSIS +.Cd "mpi* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for storage controllers using the +LSI Logic Fusion-MPT Message Passing Interface +family of chipsets: +.Pp +.Bl -dash -offset indent -compact +.It +LSI Logic LSI53C1020, +LSI53C1020A, +LSI53C1030, +LSI53C1030T, +LSI53C1035, +LSIFC909, +LSIFC919, +LSIFC919X, +LSIFC929, +LSIFC929X, +LSIFC949, +LSIFC949E, +LSIFC949X, +LSISAS1064, +LSISAS1064E, +LSISAS1068, +LSISAS1068E +.El +.Pp +These chipsets can be found on the following controllers: +.Pp +.Bl -dash -offset indent -compact +.It +Apple Fibre Channel PCI Express Card, +Fibre Channel PCI-X Card +.It +Dell PERC 4/im, +SAS 5/E, +SAS 5/i, +SAS 5/iR, +SAS 6/iR +.It +Hewlett-Packard 8 Internal Port SAS Host Bus Adapter with RAID, +A7173A, +AB290A, +EH417AA +.It +LSI Logic LSI20320-R, +LSI21320-IS, +LSI21320-R, +LSI22320-R, +LSI40919H, +LSI40919LH, +LSI40919LO, +LSI40919O, +LSI40929H, +LSI40929LH, +LSI40929LO, +LSI40929O, +LSI7102XP, +LSI7102XP-LC, +LSI7104EP-LC, +LSI7104XP-LC, +LSI7202CP-LC, +LSI7202EP-LC, +LSI7202XP, +LSI7202XP-LC, +LSI7204EP-LC, +LSI7204XP-LC, +LSI7402XP, +LSI7402XP-LC, +LSI7404EP-LC, +LSI7404XP-LC, +LSISAS3041E-R, +LSISAS3041X-R, +LSISAS3080X-R, +LSISAS3442E-R, +LSISAS3442X, +LSISAS3442X-R, +LSISAS3800X, +LSISAS3801E, +LSISAS3801X, +LSISAS8208ELP, +LSISAS8208XLP, +LSIU320 +.El +.Pp +The LSI Logic LSI53C1030 is emulated in the following products: +.Pp +.Bl -dash -offset indent -compact +.It +VMware ESX Server 2.0 and higher, +GSX Server 3.0 and higher, +Player, +Server, +Workstation 4.5 and higher +.El +.Pp +Some models of these controllers have varying degrees of support for RAID 0 +and RAID 1. +.Sh SEE ALSO +.Xr bio 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr bioctl 8 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org +and +.An Marco Peereboom Aq Mt marco@openbsd.org . diff --git a/static/openbsd/man4/mpii.4 b/static/openbsd/man4/mpii.4 new file mode 100644 index 00000000..367e003e --- /dev/null +++ b/static/openbsd/man4/mpii.4 @@ -0,0 +1,107 @@ +.\" $OpenBSD: mpii.4,v 1.18 2025/11/29 23:19:12 jsg Exp $ +.\" +.\" Copyright (c) 2010 Marco Peereboom +.\" Copyright (c) 2009 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 29 2025 $ +.Dt MPII 4 +.Os +.Sh NAME +.Nm mpii +.Nd LSI Logic Fusion-MPT Message Passing Interface II +.Sh SYNOPSIS +.Cd "mpii* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for storage controllers using the +LSI Logic Fusion-MPT Message Passing Interface II +family of chipsets: +.Pp +.Bl -dash -offset indent -compact +.It +LSISAS2004, +LSISAS2008, +LSISAS2108, +LSISAS2208, +LSISAS2308, +LSISAS3004, +LSISAS3008, +LSISAS3108, +LSISAS3216, +LSISAS3224, +LSISAS3316, +LSISAS3324, +LSISAS3408, +LSISAS3416, +LSISAS3508, +LSISAS3516, +LSISAS3808, +LSISAS3816, +LSISAS3908, +LSISAS3916 +.El +.Pp +These chipsets can be found on the following controllers: +.Pp +.Bl -dash -offset indent -compact +.It +Dell PERC H200, HBA330, HBA345, HBA350, HBA355, 12Gbps SAS HBA +.It +IBM ServeRAID H1110 +.It +Lenovo N2215, ThinkSystem 430, ThinkSystem 440 +.It +LSI SAS 9200-8e, SAS 9207-8i, SAS 9211-4i, SAS 9211-8i +.It +Broadcom SAS 9300, HBA 9400, HBA 9500 +.It +Oracle SPARC T Series Platforms +.It +Supermicro AOC-S3808, AOC-S3816 +.El +.Pp +Some models of these controllers carry an Integrated RAID (IR) firmware +providing support for RAID levels 0, 1, 1E, 5 or 10 using SAS or SATA drives. +All RAID configuration is done through the controllers' BIOSes. +.Sh SEE ALSO +.Xr bio 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr bioctl 8 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An James Giannoules +and +.An Mike Belopuhov . +.Sh BUGS +The chips supported by +.Nm +do not use a SCSI-like identifier. +Instead they use an opaque ID and leave discovery order up to the operating +system. +The code to handle this is currently not implemented and therefore it is not a +good idea to run this driver on a multi-boot machine. diff --git a/static/openbsd/man4/mpip.4 b/static/openbsd/man4/mpip.4 new file mode 100644 index 00000000..89fb35c3 --- /dev/null +++ b/static/openbsd/man4/mpip.4 @@ -0,0 +1,103 @@ +.\" $OpenBSD: mpip.4,v 1.3 2021/03/18 14:22:04 kn Exp $ +.\" +.\" Copyright (C) 2019 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 18 2021 $ +.Dt MPIP 4 +.Os +.Sh NAME +.Nm mpip +.Nd MPLS IP layer 2 pseudowire +.Sh SYNOPSIS +.Cd "pseudo-device mpip" +.Sh DESCRIPTION +The +.Nm +interface is used to create an MPLS IP layer 2 tunnel between two points. +.Pp +An +.Nm +interface can be created at runtime using the +.Sy ifconfig Nm Ns Ar N Cm create +command, or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The interface itself can be configured with +.Xr ifconfig 8 . +.Pp +The local MPLS label, the remote MPLS label and neighbor, use of +pseudowire control words, or flow-aware transport are normally +configured after negotiation with a remote system using +.Xr ldpd 8 , +but it is also possible to configure them manually using +.Xr ifconfig 8 . +.Sh EXAMPLES +Create a pseudowire with local label 20 and remote label 21 on +neighbor 10.254.0.1: +.Bd -literal -offset indent +# ifconfig mpip5 create +# ifconfig mpip5 mplslabel 20 pweneighbor 21 10.254.0.1 +# ifconfig mpip5 up +.Ed +.Pp +Disable the use of the Pseudowire Emulation Edge-to-Edge (PWE3) +Control Word, and enable the use of a Flow label for Flow-Aware +Transport of Pseudowires: +.Bd -literal -offset indent +# ifconfig mpip5 -pwecw pwefat +.Ed +.Sh SEE ALSO +.Xr mpe 4 , +.Xr mpw 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr ldpd 8 , +.Xr netstart 8 +.Sh STANDARDS +.Rs +.%A S. Bryant +.%A P. Pate +.%D March 2005 +.%R RFC 3985 +.%T Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture +.Re +.Pp +.Rs +.%A S. Bryant +.%A G. Swallow +.%A L. Martini +.%D February 2005 +.%R RFC 4385 +.%T Pseudowire Emulation Edge-to-Edge (PWE3) Control Word \ +for Use over an MPLS PSN +.Re +.Pp +.Rs +.%A S. Bryant +.%A C. Filsfils +.%A U. Drafz +.%A V. Kompella +.%A J. Regan +.%A S. Amante +.%D November 2011 +.%R RFC 6391 +.%T Flow-Aware Transport of Pseudowires over an MPLS Packet Switched Network +.Re +.Sh HISTORY +The +.Nm +kernel interface first appeared in +.Ox 6.5 . diff --git a/static/openbsd/man4/mpu.4 b/static/openbsd/man4/mpu.4 new file mode 100644 index 00000000..22fc75df --- /dev/null +++ b/static/openbsd/man4/mpu.4 @@ -0,0 +1,60 @@ +.\" $OpenBSD: mpu.4,v 1.7 2009/03/19 20:18:45 jmc Exp $ +.\" $NetBSD: mpu.4,v 1.5 2001/03/30 14:34:27 minoura Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 19 2009 $ +.Dt MPU 4 +.Os +.Sh NAME +.Nm mpu +.Nd Roland/Yamaha MPU401 MIDI UART device +.Sh SYNOPSIS +.Cd "mpu* at isa? port 0x300" +.Cd "mpu* at isapnp?" +.Cd "midi* at mpu?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Roland/Yamaha MPU401 (and compatible) +MIDI UART cards. +.Pp +Access to the device is through the MIDI driver. +.\" .Pp +.\" The +.\" .Nm +.\" driver usually attaches to a sound card, but it can also sit +.\" directly on the ISA bus. +.Sh SEE ALSO +.Xr isa 4 , +.Xr midi 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.6 . diff --git a/static/openbsd/man4/mpw.4 b/static/openbsd/man4/mpw.4 new file mode 100644 index 00000000..2c78c95b --- /dev/null +++ b/static/openbsd/man4/mpw.4 @@ -0,0 +1,135 @@ +.\" $OpenBSD: mpw.4,v 1.10 2025/11/20 00:03:46 dlg Exp $ +.\" +.\" Copyright (C) 2015 Rafael Zalamena +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 20 2025 $ +.Dt MPW 4 +.Os +.Sh NAME +.Nm mpw +.Nd MPLS Ethernet pseudowire +.Sh SYNOPSIS +.Cd "pseudo-device mpw" +.Sh DESCRIPTION +The +.Nm +interface is used to create an MPLS Ethernet layer 2 tunnel between +two points. +.Pp +An +.Nm +interface can be created at runtime using the +.Sy ifconfig Nm Ns Ar N Cm create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The interface itself can be configured with +.Xr ifconfig 8 . +.Pp +The local MPLS label, the remote MPLS label and neighbor, use of +pseudowire control words, or flow-aware transport are normally +configured after negotiation with a remote system using +.Xr ldpd 8 , +but it is also possible to configure them manually using +.Xr ifconfig 8 . +.Sh EXAMPLES +Create a pseudowire with local label 20 and remote label 21 on +neighbor 10.254.0.1: +.Bd -literal -offset indent +# ifconfig mpw5 create +# ifconfig mpw5 mplslabel 20 pweneighbor 21 10.254.0.1 +# ifconfig mpw5 up +.Ed +.Pp +Enable the use of the Pseudowire Emulation Edge-to-Edge (PWE3) +Control Word, and disable the use of a Flow label for Flow-Aware +Transport of Pseudowires: +.Bd -literal -offset indent +# ifconfig mpw5 pwecw -pwefat +.Ed +.Pp +.Nm mpw +interfaces may be used to build a Virtual Private LAN Service +(VPLS) with +.Xr veb 4 +or +.Xr bridge 4 . +A VPLS is constructed with a full mesh of MPLS pseudowire tunnels +bridged between all peers, but this introduces loops in the topology. +To prevent broadcast, unknown unicast, and multicast packets received +from the VPLS being forwarded to its peers, all the pseudowire +interfaces can be configured to enforce the split-horizon forwarding +rule by adding them to the same protected bridge domain. +Different VPLS meshes can be joined together on the same bridge +using different identifiers for their protected domains: +.Bd -literal -offset indent +# ifconfig mpw10 create up +# ifconfig mpw11 create up +# ifconfig mpw12 create up +# ifconfig veb0 create +# ifconfig veb0 add em2 +# ifconfig veb0 add mpw10 add mpw11 add mpw12 +# ifconfig veb0 protected mpw10 1 +# ifconfig veb0 protected mpw11 1 +# ifconfig veb0 protected mpw12 1 +# ifconfig veb0 up +.Ed +.Sh SEE ALSO +.Xr mpe 4 , +.Xr mpip 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr ldpd 8 , +.Xr netstart 8 +.Rs +.%A S. Bryant +.%A P. Pate +.%D March 2005 +.%R RFC 3985 +.%T Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture +.Re +.Pp +.Rs +.%A S. Bryant +.%A G. Swallow +.%A L. Martini +.%D February 2005 +.%R RFC 4385 +.%T Pseudowire Emulation Edge-to-Edge (PWE3) Control Word \ +for Use over an MPLS PSN +.Re +.Pp +.Rs +.%A S. Bryant +.%A C. Filsfils +.%A U. Drafz +.%A V. Kompella +.%A J. Regan +.%A S. Amante +.%D November 2011 +.%R RFC 6391 +.%T Flow-Aware Transport of Pseudowires over an MPLS Packet Switched Network +.Re +.Sh HISTORY +The +.Nm +kernel interface first appeared in +.Ox 5.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Rafael Zalamena Aq Mt rzalamena@openbsd.org . diff --git a/static/openbsd/man4/msk.4 b/static/openbsd/man4/msk.4 new file mode 100644 index 00000000..819044a2 --- /dev/null +++ b/static/openbsd/man4/msk.4 @@ -0,0 +1,178 @@ +.\" $OpenBSD: msk.4,v 1.18 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/man4.i386/sk.4,v 1.3 1999/08/28 00:20:29 peter Exp $ +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt MSK 4 +.Os +.Sh NAME +.Nm msk , +.Nm mskc +.Nd Marvell Yukon-2 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "mskc* at pci?" +.Cd "msk* at mskc?" +.Cd "eephy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Marvell Yukon-2 88E802x, 88E805x, 88E806x, +and 88E807x based Gigabit Ethernet adapters and 88E803x/88E804x based +Fast Ethernet adapters, including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +D-Link DGE-550SX, multimode fiber adapter +.It +D-Link DGE-560SX, multimode fiber adapter +.It +D-Link DGE-550T B1, copper adapter +.It +D-Link DGE-560T, copper adapter +.It +SysKonnect SK-9E21 single port, copper adapter +.It +SysKonnect SK-9E22 dual port, copper adapter +.It +SysKonnect SK-9E81 single port, multimode fiber adapter +.It +SysKonnect SK-9E82 dual port, multimode fiber adapter +.It +SysKonnect SK-9E91 single port, single mode fiber adapter +.It +SysKonnect SK-9E92 dual port, single mode fiber adapter +.It +SysKonnect SK-9S21 single port, copper adapter +.It +SysKonnect SK-9S22 dual port, copper adapter +.It +SysKonnect SK-9S81 single port, multimode fiber adapter +.It +SysKonnect SK-9S82 dual port, multimode fiber adapter +.It +SysKonnect SK-9S91 single port, single mode fiber adapter +.It +SysKonnect SK-9S92 dual port, single mode fiber adapter +.It +SysKonnect SK-9E21D single port, copper adapter +.El +.Pp +The Yukon-2 88E802x, 88E805x, 88E806x, and 88E807x also support +jumbo frames. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width 1000baseSX +.It Cm autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It Cm 10baseT +Set 10Mbps operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 1000baseT +Set 1000baseT (Gigabit Ethernet) operation over twisted pair. +Both +.Cm full-duplex +and +.Cm half-duplex +modes are supported. +.It Cm 1000baseSX +Set 1000Mbps (Gigabit Ethernet) operation. +Both +.Cm full-duplex +and +.Cm half-duplex +modes are supported. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It Cm full-duplex +Force full duplex operation. +.It Cm half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by the card, try +.Ic ifconfig media . +For example, +.Ic ifconfig msk0 media . +.Sh SEE ALSO +.Xr arp 4 , +.Xr eephy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +.Sh BUGS +The +.Nm +driver does not support hardware receive IP checksum offload yet. diff --git a/static/openbsd/man4/msts.4 b/static/openbsd/man4/msts.4 new file mode 100644 index 00000000..827f5e1e --- /dev/null +++ b/static/openbsd/man4/msts.4 @@ -0,0 +1,95 @@ +.\" $OpenBSD: msts.4,v 1.4 2015/01/15 00:48:10 deraadt Exp $ +.\" +.\" Copyright (c) 2008 Marc Balmer +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt MSTS 4 +.Os +.Sh NAME +.Nm msts +.Nd Meinberg Standard Time String timedelta sensor +.Sh SYNOPSIS +.Cd "pseudo-device msts" Op Ar count +.Sh DESCRIPTION +This line discipline interfaces serial Meinberg devices. +.Pp +The line discipline is enabled by the following sequence: +.Bd -literal -offset indent +#include +int ldisc = MSTSDISC, fildes; ... +ioctl(fildes, TIOCSETD, &ldisc); +.Ed +.Pp +The byte stream is unaltered by the line discipline which +maintains a timedelta sensor using the MSTS data. +The timedelta sensor will appear as msts* in the list of sensors and the delta +(in nanoseconds) between the received time information and the local time can +be accessed through the +.Xr sysctl 8 +interface. +.Pp +The Meinberg radio clocks use the following default baudrates: +.Pp +.Bl -tag -width "GPS-receivers (external and PCI, COM0)XXX" -offset indent -compact +.It GPS-receivers (external and PCI, COM0) +19200/8N1 +.It GPS-receivers (external, COM1) +9600/8N1 +.It DCF77-receivers (external) +9600/7E2 +.It DCF77-receivers (PCI) +4800/8N1 +.El +.Sh SENSOR STATES +The quality of the timedelta is reported as the sensor status: +.Bl -tag -width "CRITICALXX" -offset indent +.It OK +The time information is valid. +The timedelta is safe to use for applications like +.Xr ntpd 8 . +.It WARN +The attached receiver has been indicating a warning condition +for at least the last ten minutes. +The timedelta should be used with care. +.It CRITICAL +tty timestamping has been turned on but there is no PPS signal present or the +receiver indicated a warning condition for at least the last twenty minutes. +Check your hardware. +Some receiver units need PPS to be manually turned on. +.El +.Pp +The status of a second sensor is used to report the status of the +device itself: +.Bl -tag -width "CRITICALXX" -offset indent +.It OK +The clock is synchronized, e.g. a GPS receiver has a fix. +.It WARN +The device issued a warning condition, e.g. a GPS receiver has no fix. +.El +.Sh SEE ALSO +.Xr tty 4 , +.Xr ldattach 8 , +.Xr ntpd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +interface first appeared in +.Ox 4.3 . +.Sh AUTHORS +The +.Nm +line discipline was written by +.An Marc Balmer Aq Mt mbalmer@openbsd.org . diff --git a/static/openbsd/man4/mtd.4 b/static/openbsd/man4/mtd.4 new file mode 100644 index 00000000..77a2d236 --- /dev/null +++ b/static/openbsd/man4/mtd.4 @@ -0,0 +1,70 @@ +.\" $OpenBSD: mtd.4,v 1.10 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2003 Oleg Safiullin +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice unmodified, this list of conditions, and the following +.\" disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt MTD 4 +.Os +.Sh NAME +.Nm mtd +.Nd Myson Technology MTD800/MTD803/MTD891 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "mtd* at pci?" +.Cd "mtdphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Myson MTD800/MTD803 Fast Ethernet and +MTD891 Gigabit Ethernet chips. +.Pp +Supported models include: +.Pp +.Bl -bullet -compact +.It +Safeway Lancard SW-10/100 PCI (model 117204) +.It +Surecom EP-320X-S +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr mii 4 , +.Xr mtdphy 4 , +.Xr pci 4 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Oleg Safiullin Aq Mt form@pdp11.org.ru +.Sh BUGS +The +.Nm +driver does not support Power Management. diff --git a/static/openbsd/man4/mtdphy.4 b/static/openbsd/man4/mtdphy.4 new file mode 100644 index 00000000..0d689bdf --- /dev/null +++ b/static/openbsd/man4/mtdphy.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: mtdphy.4,v 1.9 2007/05/31 19:19:51 jmc Exp $ +.\" +.\" Copyright (c) 1998 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt MTDPHY 4 +.Os +.Sh NAME +.Nm mtdphy +.Nd Myson MTD972 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "mtdphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Myson MTD972 10/100 Ethernet PHYs. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/mtintc.4 b/static/openbsd/man4/mtintc.4 new file mode 100644 index 00000000..3502acc2 --- /dev/null +++ b/static/openbsd/man4/mtintc.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: mtintc.4,v 1.2 2025/01/30 02:14:17 jsg Exp $ +.\" +.\" Copyright (c) 2025 James Hastings +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 30 2025 $ +.Dt MTINTC 4 +.Os +.Sh NAME +.Nm mtintc +.Nd MediaTek system interrupt controller +.Sh SYNOPSIS +.Cd "mtintc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the system interrupt controller +integrated on MediaTek SoCs. +The controller provides per-interrupt polarity inversion +and transparent forwarding to an +Arm Generic Interrupt Controller (GIC). +.Sh SEE ALSO +.Xr ampintc 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An James Hastings Aq Mt hastings@openbsd.org . diff --git a/static/openbsd/man4/mtio.4 b/static/openbsd/man4/mtio.4 new file mode 100644 index 00000000..8cea2ae6 --- /dev/null +++ b/static/openbsd/man4/mtio.4 @@ -0,0 +1,111 @@ +.\" $OpenBSD: mtio.4,v 1.16 2015/09/10 17:55:21 schwarze Exp $ +.\" $NetBSD: mtio.4,v 1.4 1996/03/03 17:13:54 thorpej Exp $ +.\" +.\" Copyright (c) 1983, 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)mtio.4 6.5 (Berkeley) 3/27/91 +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt MTIO 4 +.Os +.Sh NAME +.Nm mtio +.Nd magtape interface +.Sh SYNOPSIS +.In sys/mtio.h +.Sh DESCRIPTION +This interface concerns devices which are typical tape block devices, +see +.Xr physio 9 . +.Pp +The conventional device letters/numbers +is applicable to any of the transport/controller pairs. +(But note that only 1600 +.Tn BPI +is available with the +.Tn TS11 , +and that 800 +.Tn BPI +is not applicable to +.Tn TM78 . ) +.Pp +When the device last number is between +.Em 0-7 +the device will operate at 800 +.Tn BPI +(or its lowest density), between +.Em 8-15 +it will operate at 1600 +.Tn BPI +(or its second density), and between +.Em 16-23 +it will operate at 6250 +.Tn BPI . +.Pp +The rewind devices automatically rewind +when the last requested read, write or seek has finished, or the end of the tape +has been reached. +The letter +.Ql n +is usually prepended to +the name of the no-rewind devices. +.Pp +Unix tapes are written in multiples of 1024 byte block +records. +Two end-of-file markers mark the end of a tape, and +one end-of-file marker marks the end of a tape file. +If the tape is not to be rewound it is positioned with the +head in between the two tape marks, where the next write +will overwrite the second end-of-file marker. +.Pp +All of the magtape devices may be manipulated with the +.Xr mt 1 +command. +.Pp +The include file +.In sys/mtio.h +defines the various +.Xr ioctl 2 +operations available on raw magnetic tape. +.Sh FILES +.Bl -tag -width /dev/rmt? -compact +.It Pa /dev/mt? +.It Pa /dev/rmt? +.El +.Sh SEE ALSO +.Xr mt 1 , +.Xr tar 1 , +.Xr intro 4 , +.Xr st 4 +.Sh HISTORY +The +.Nm +manual appeared in +.Bx 4.2 . +.Sh BUGS +The status should be returned in a device independent format. diff --git a/static/openbsd/man4/mtrng.4 b/static/openbsd/man4/mtrng.4 new file mode 100644 index 00000000..b60f6151 --- /dev/null +++ b/static/openbsd/man4/mtrng.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: mtrng.4,v 1.1 2025/02/14 03:15:06 hastings Exp $ +.\" +.\" Copyright (c) 2025 James Hastings +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 14 2025 $ +.Dt MTRNG 4 +.Os +.Sh NAME +.Nm mtrng +.Nd MediaTek random number generator +.Sh SYNOPSIS +.Cd "mtrng* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the random number generator found on +MediaTek SoCs. +.Pp +It feeds the random subsystem's entropy pool with 32 bits of +random data every second. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An James Hastings Aq Mt hastings@openbsd.org . diff --git a/static/openbsd/man4/mtw.4 b/static/openbsd/man4/mtw.4 new file mode 100644 index 00000000..83d83fb2 --- /dev/null +++ b/static/openbsd/man4/mtw.4 @@ -0,0 +1,160 @@ +.\" $OpenBSD: mtw.4,v 1.4 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2021 James Hastings +.\" Copyright (c) 2008 Damien Bergamini +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt MTW 4 +.Os +.Sh NAME +.Nm mtw +.Nd MediaTek USB IEEE 802.11b/g/n wireless network device +.Sh SYNOPSIS +.Cd "mtw* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports USB 2.0 wireless adapters based on the MediaTek +MT7601U chipset. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver offloads both encryption and decryption of data frames to the +hardware for the WEP40, WEP104, TKIP(+MIC) and CCMP ciphers. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs the following firmware files, +which are loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It /etc/firmware/mtw-mt7601u +.El +.Sh HARDWARE +The following adapters should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It ASUS USB-N10 v2 +.It D-Link DWA-127 rev B1 +.It Edimax EW-7711UAn v2 +.It Edimax EW-7711ULn v2 +.It Foxconn WFU03 +.It Tenda U2 +.It Tenda W311MI v2 +.It TP-LINK TL-WN727N v4 +.It Yealink WF40 +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig mtw0 scan +.Pp +The following +.Xr hostname.if 5 +example configures mtw0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "mtw0: error N, could not read firmware ..." +For some reason, the driver was unable to read the microcode file from the +filesystem. +The file might be missing or corrupted. +.It "mtw0: could not load firmware" +An error occurred while attempting to upload the microcode to the onboard 8051 +microcontroller unit. +.It "mtw0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An James Hastings Aq Mt hastings@openbsd.org +based on the +.Xr run 4 +driver by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +The +.Nm +driver does not support any of the 802.11n capabilities offered by the +MT7601U chipset. +Additional work is required in +.Xr ieee80211 9 +before those features can be supported. diff --git a/static/openbsd/man4/mtxhci.4 b/static/openbsd/man4/mtxhci.4 new file mode 100644 index 00000000..701388d3 --- /dev/null +++ b/static/openbsd/man4/mtxhci.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: mtxhci.4,v 1.1 2025/03/25 04:21:07 hastings Exp $ +.\" +.\" Copyright (c) 2025 James Hastings +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 25 2025 $ +.Dt MTXHCI 4 +.Os +.Sh NAME +.Nm mtxhci +.Nd MediaTek USB xHCI controller +.Sh SYNOPSIS +.Cd "mtxhci* at fdt?" +.Cd "usb* at mtxhci?" +.Sh DESCRIPTION +The +.Nm +driver controls the interface logic and supports +the USB eXtensible Host Controller Interface +integrated on MediaTek SoCs. +.Pp +It provides an interface to +.Xr usb 4 +devices and supports all USB 3.0, 2.0 and 1.x device speeds. +.Sh SEE ALSO +.Xr intro 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An James Hastings Aq Mt hastings@openbsd.org . diff --git a/static/openbsd/man4/mue.4 b/static/openbsd/man4/mue.4 new file mode 100644 index 00000000..fe086ef0 --- /dev/null +++ b/static/openbsd/man4/mue.4 @@ -0,0 +1,59 @@ +.\" $OpenBSD: mue.4,v 1.4 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2018 Kevin Lo +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt MUE 4 +.Os +.Sh NAME +.Nm mue +.Nd Microchip LAN75xx/LAN78xx 10/100/1Gb USB Ethernet device +.Sh SYNOPSIS +.Cd "mue* at uhub?" +.Cd "ukphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports Microchip LAN7500/LAN7505/LAN7515/LAN7850 USB 2.0 Gigabit +Ethernet devices and LAN7800/LAN7801 USB 3.0 Gigabit Ethernet devices, +including the following: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Microchip EVB-LAN7800LC +.It Z-TEK ZE582 +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr ukphy 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Kevin Lo Aq Mt kevlo@openbsd.org . diff --git a/static/openbsd/man4/multicast.4 b/static/openbsd/man4/multicast.4 new file mode 100644 index 00000000..f01ff3b6 --- /dev/null +++ b/static/openbsd/man4/multicast.4 @@ -0,0 +1,888 @@ +.\" Copyright (c) 2001-2003 International Computer Science Institute +.\" +.\" Permission is hereby granted, free of charge, to any person obtaining a +.\" copy of this software and associated documentation files (the "Software"), +.\" to deal in the Software without restriction, including without limitation +.\" the rights to use, copy, modify, merge, publish, distribute, sublicense, +.\" and/or sell copies of the Software, and to permit persons to whom the +.\" Software is furnished to do so, subject to the following conditions: +.\" +.\" The above copyright notice and this permission notice shall be included in +.\" all copies or substantial portions of the Software. +.\" +.\" The names and trademarks of copyright holders may not be used in +.\" advertising or publicity pertaining to the software without specific +.\" prior permission. Title to copyright in this software and any associated +.\" documentation will at all times remain with the copyright holders. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +.\" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +.\" FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +.\" AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +.\" LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +.\" FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER +.\" DEALINGS IN THE SOFTWARE. +.\" +.\" $FreeBSD: src/share/man/man4/multicast.4,v 1.4 2004/07/09 09:22:36 ru Exp $ +.\" $OpenBSD: multicast.4,v 1.17 2024/01/23 08:20:30 jmc Exp $ +.\" $NetBSD: multicast.4,v 1.3 2004/09/12 13:12:26 wiz Exp $ +.\" +.Dd $Mdocdate: January 23 2024 $ +.Dt MULTICAST 4 +.Os +.\" +.Sh NAME +.Nm multicast +.Nd multicast routing +.\" +.Sh SYNOPSIS +.Cd "options MROUTING" +.Pp +.In sys/types.h +.In sys/socket.h +.In netinet/in.h +.In netinet/ip_mroute.h +.In netinet6/ip6_mroute.h +.Ft int +.Fn getsockopt "int s" IPPROTO_IP MRT_INIT "void *optval" "socklen_t *optlen" +.Ft int +.Fn setsockopt "int s" IPPROTO_IP MRT_INIT "const void *optval" "socklen_t optlen" +.Ft int +.Fn getsockopt "int s" IPPROTO_IPV6 MRT6_INIT "void *optval" "socklen_t *optlen" +.Ft int +.Fn setsockopt "int s" IPPROTO_IPV6 MRT6_INIT "const void *optval" "socklen_t optlen" +.Sh DESCRIPTION +Multicast routing is used to efficiently propagate data +packets to a set of multicast listeners in multipoint networks. +If unicast is used to replicate the data to all listeners, +then some of the network links may carry multiple copies of the same +data packets. +With multicast routing, the overhead is reduced to one copy +(at most) per network link. +.Pp +All multicast-capable routers must run a common multicast routing +protocol. +The Distance Vector Multicast Routing Protocol (DVMRP) +was the first developed multicast routing protocol. +Later, other protocols such as Multicast Extensions to OSPF (MOSPF) and +Core Based Trees (CBT) +were developed as well. +.Pp +To start multicast routing, +the user must enable multicast forwarding via the +.Xr sysctl 8 +variables +.Va net.inet.ip.mforwarding +and/or +.Va net.inet6.ip6.mforwarding , +and set +.Va multicast +to +.Dq YES +in +.Xr rc.conf.local 8 . +The user must also run a multicast routing capable user-level process, +such as +.Xr mrouted 8 . +From a developer's point of view, +the programming guide described in the +.Sx Programming Guide +section should be used to control the multicast forwarding in the kernel. +.\" +.Ss Programming Guide +This section provides information about the basic multicast routing API. +The so-called +.Dq advanced multicast API +is described in the +.Sx "Advanced Multicast API Programming Guide" +section. +.Pp +First, a multicast routing socket must be open. +That socket would be used +to control the multicast forwarding in the kernel. +Note that most operations below require certain privilege +(i.e., root privilege): +.Bd -literal -offset indent +/* IPv4 */ +int mrouter_s4; +mrouter_s4 = socket(AF_INET, SOCK_RAW, IPPROTO_IGMP); +.Ed +.Bd -literal -offset indent +int mrouter_s6; +mrouter_s6 = socket(AF_INET6, SOCK_RAW, IPPROTO_ICMPV6); +.Ed +.Pp +Note that if the router needs to open an IGMP or ICMPv6 socket +(IPv4 or IPv6, respectively) +for sending or receiving of IGMP or MLD multicast group membership messages, +then the same +.Va mrouter_s4 +or +.Va mrouter_s6 +sockets should be used +for sending and receiving respectively IGMP or MLD messages. +In the case of +.Bx Ns -derived +kernels, +it may be possible to open separate sockets +for IGMP or MLD messages only. +However, some other kernels (e.g., Linux) +require that the multicast +routing socket must be used for sending and receiving of IGMP or MLD +messages. +Therefore, for portability reasons, the multicast +routing socket should be reused for IGMP and MLD messages as well. +.Pp +After the multicast routing socket is open, it can be used to enable +or disable multicast forwarding in the kernel: +.Bd -literal -offset 5n +/* IPv4 */ +int v = 1; /* 1 to enable, or 0 to disable */ +setsockopt(mrouter_s4, IPPROTO_IP, MRT_INIT, &v, sizeof(v)); +.Ed +.Bd -literal -offset 5n +/* IPv6 */ +int v = 1; /* 1 to enable, or 0 to disable */ +setsockopt(mrouter_s6, IPPROTO_IPV6, MRT6_INIT, &v, sizeof(v)); +\&... +/* If necessary, filter all ICMPv6 messages */ +struct icmp6_filter filter; +ICMP6_FILTER_SETBLOCKALL(&filter); +setsockopt(mrouter_s6, IPPROTO_ICMPV6, ICMP6_FILTER, &filter, + sizeof(filter)); +.Ed +.Pp +For each network interface (e.g., physical or a virtual tunnel) +that would be used for multicast forwarding, a corresponding +multicast interface must be added to the kernel: +.Bd -literal -offset 3n +/* IPv4 */ +struct vifctl vc; +memset(&vc, 0, sizeof(vc)); +/* Assign all vifctl fields as appropriate */ +vc.vifc_vifi = vif_index; +vc.vifc_flags = vif_flags; +vc.vifc_threshold = min_ttl_threshold; +vc.vifc_rate_limit = max_rate_limit; +memcpy(&vc.vifc_lcl_addr, &vif_local_address, sizeof(vc.vifc_lcl_addr)); +if (vc.vifc_flags & VIFF_TUNNEL) + memcpy(&vc.vifc_rmt_addr, &vif_remote_address, + sizeof(vc.vifc_rmt_addr)); +setsockopt(mrouter_s4, IPPROTO_IP, MRT_ADD_VIF, &vc, sizeof(vc)); +.Ed +.Pp +The +.Va vif_index +must be unique per vif. +The +.Va vif_flags +contains the +.Dv VIFF_* +flags as defined in +.In netinet/ip_mroute.h . +The +.Va min_ttl_threshold +contains the minimum TTL a multicast data packet must have to be +forwarded on that vif. +Typically, it would be 1. +The +.Va max_rate_limit +contains the maximum rate (in bits/s) of the multicast data packets forwarded +on that vif. +A value of 0 means no limit. +The +.Va vif_local_address +contains the local IP address of the corresponding local interface. +The +.Va vif_remote_address +contains the remote IP address for DVMRP multicast tunnels. +.Bd -literal -offset indent +/* IPv6 */ +struct mif6ctl mc; +memset(&mc, 0, sizeof(mc)); +/* Assign all mif6ctl fields as appropriate */ +mc.mif6c_mifi = mif_index; +mc.mif6c_flags = mif_flags; +mc.mif6c_pifi = pif_index; +setsockopt(mrouter_s6, IPPROTO_IPV6, MRT6_ADD_MIF, &mc, sizeof(mc)); +.Ed +.Pp +The +.Va mif_index +must be unique per vif. +The +.Va mif_flags +contains the +.Dv MIFF_* +flags as defined in +.In netinet6/ip6_mroute.h . +The +.Va pif_index +is the physical interface index of the corresponding local interface. +.Pp +A multicast interface is deleted by: +.Bd -literal -offset indent +/* IPv4 */ +vifi_t vifi = vif_index; +setsockopt(mrouter_s4, IPPROTO_IP, MRT_DEL_VIF, &vifi, + sizeof(vifi)); +.Ed +.Bd -literal -offset indent +/* IPv6 */ +mifi_t mifi = mif_index; +setsockopt(mrouter_s6, IPPROTO_IPV6, MRT6_DEL_MIF, &mifi, + sizeof(mifi)); +.Ed +.Pp +After multicast forwarding is enabled, and the multicast virtual +interfaces have been +added, the kernel may deliver upcall messages (also called signals +later in this text) on the multicast routing socket that was open +earlier with +.Dv MRT_INIT +or +.Dv MRT6_INIT . +The IPv4 upcalls have a +.Vt "struct igmpmsg" +header (see +.In netinet/ip_mroute.h ) +with the +.Va im_mbz +field set to zero. +Note that this header follows the structure of +.Vt "struct ip" +with the protocol field +.Va ip_p +set to zero. +The IPv6 upcalls have a +.Vt "struct mrt6msg" +header (see +.In netinet6/ip6_mroute.h ) +with the +.Va im6_mbz +field set to zero. +Note that this header follows the structure of +.Vt "struct ip6_hdr" +with the next header field +.Va ip6_nxt +set to zero. +.Pp +The upcall header contains the +.Va im_msgtype +and +.Va im6_msgtype +fields, with the type of the upcall +.Dv IGMPMSG_* +and +.Dv MRT6MSG_* +for IPv4 and IPv6, respectively. +The values of the rest of the upcall header fields +and the body of the upcall message depend on the particular upcall type. +.Pp +If the upcall message type is +.Dv IGMPMSG_NOCACHE +or +.Dv MRT6MSG_NOCACHE , +this is an indication that a multicast packet has reached the multicast +router, but the router has no forwarding state for that packet. +Typically, the upcall would be a signal for the multicast routing +user-level process to install the appropriate Multicast Forwarding +Cache (MFC) entry in the kernel. +.Pp +An MFC entry is added by: +.Bd -literal -offset indent +/* IPv4 */ +struct mfcctl mc; +memset(&mc, 0, sizeof(mc)); +memcpy(&mc.mfcc_origin, &source_addr, sizeof(mc.mfcc_origin)); +memcpy(&mc.mfcc_mcastgrp, &group_addr, sizeof(mc.mfcc_mcastgrp)); +mc.mfcc_parent = iif_index; +for (i = 0; i < maxvifs; i++) + mc.mfcc_ttls[i] = oifs_ttl[i]; +setsockopt(mrouter_s4, IPPROTO_IP, MRT_ADD_MFC, &mc, sizeof(mc)); +.Ed +.Bd -literal -offset indent +/* IPv6 */ +struct mf6cctl mc; +memset(&mc, 0, sizeof(mc)); +memcpy(&mc.mf6cc_origin, &source_addr, sizeof(mc.mf6cc_origin)); +memcpy(&mc.mf6cc_mcastgrp, &group_addr, sizeof(mf6cc_mcastgrp)); +mc.mf6cc_parent = iif_index; +for (i = 0; i < maxvifs; i++) + if (oifs_ttl[i] > 0) + IF_SET(i, &mc.mf6cc_ifset); +setsockopt(mrouter_s4, IPPROTO_IPV6, MRT6_ADD_MFC, &mc, sizeof(mc)); +.Ed +.Pp +The +.Va source_addr +and +.Va group_addr +fields are the source and group address of the multicast packet (as set +in the upcall message). +The +.Va iif_index +is the virtual interface index of the multicast interface the multicast +packets for this specific source and group address should be received on. +The +.Va oifs_ttl[] +array contains the minimum TTL (per interface) a multicast packet +should have to be forwarded on an outgoing interface. +If the TTL value is zero, the corresponding interface is not included +in the set of outgoing interfaces. +Note that for IPv6 only the set of outgoing interfaces can +be specified. +.Pp +An MFC entry is deleted by: +.Bd -literal -offset indent +/* IPv4 */ +struct mfcctl mc; +memset(&mc, 0, sizeof(mc)); +memcpy(&mc.mfcc_origin, &source_addr, sizeof(mc.mfcc_origin)); +memcpy(&mc.mfcc_mcastgrp, &group_addr, sizeof(mc.mfcc_mcastgrp)); +setsockopt(mrouter_s4, IPPROTO_IP, MRT_DEL_MFC, &mc, sizeof(mc)); +.Ed +.Bd -literal -offset indent +/* IPv6 */ +struct mf6cctl mc; +memset(&mc, 0, sizeof(mc)); +memcpy(&mc.mf6cc_origin, &source_addr, sizeof(mc.mf6cc_origin)); +memcpy(&mc.mf6cc_mcastgrp, &group_addr, sizeof(mf6cc_mcastgrp)); +setsockopt(mrouter_s4, IPPROTO_IPV6, MRT6_DEL_MFC, &mc, sizeof(mc)); +.Ed +.Pp +The following method can be used to get various statistics per +installed MFC entry in the kernel (e.g., the number of forwarded +packets per source and group address): +.Bd -literal -offset indent +/* IPv4 */ +struct sioc_sg_req sgreq; +memset(&sgreq, 0, sizeof(sgreq)); +memcpy(&sgreq.src, &source_addr, sizeof(sgreq.src)); +memcpy(&sgreq.grp, &group_addr, sizeof(sgreq.grp)); +ioctl(mrouter_s4, SIOCGETSGCNT, &sgreq); +.Ed +.Bd -literal -offset indent +/* IPv6 */ +struct sioc_sg_req6 sgreq; +memset(&sgreq, 0, sizeof(sgreq)); +memcpy(&sgreq.src, &source_addr, sizeof(sgreq.src)); +memcpy(&sgreq.grp, &group_addr, sizeof(sgreq.grp)); +ioctl(mrouter_s6, SIOCGETSGCNT_IN6, &sgreq); +.Ed +.Pp +The following method can be used to get various statistics per +multicast virtual interface in the kernel (e.g., the number of forwarded +packets per interface): +.Bd -literal -offset indent +/* IPv4 */ +struct sioc_vif_req vreq; +memset(&vreq, 0, sizeof(vreq)); +vreq.vifi = vif_index; +ioctl(mrouter_s4, SIOCGETVIFCNT, &vreq); +.Ed +.Bd -literal -offset indent +/* IPv6 */ +struct sioc_mif_req6 mreq; +memset(&mreq, 0, sizeof(mreq)); +mreq.mifi = vif_index; +ioctl(mrouter_s6, SIOCGETMIFCNT_IN6, &mreq); +.Ed +.Ss Advanced Multicast API Programming Guide +Adding new features to the kernel makes it difficult +to preserve backward compatibility (binary and API), +and at the same time to allow user-level processes to take advantage of +the new features (if the kernel supports them). +.Pp +One of the mechanisms that allows preserving the backward +compatibility is a sort of negotiation +between the user-level process and the kernel: +.Bl -enum +.It +The user-level process tries to enable in the kernel the set of new +features (and the corresponding API) it would like to use. +.It +The kernel returns the (sub)set of features it knows about +and is willing to be enabled. +.It +The user-level process uses only that set of features +the kernel has agreed on. +.El +.\" +.Pp +To support backward compatibility, if the user-level process does not +ask for any new features, the kernel defaults to the basic +multicast API (see the +.Sx "Programming Guide" +section). +.\" XXX: edit as appropriate after the advanced multicast API is +.\" supported under IPv6 +Currently, the advanced multicast API exists only for IPv4; +in the future there will be IPv6 support as well. +.Pp +Below is a summary of the expandable API solution. +Note that all new options and structures are defined +in +.In netinet/ip_mroute.h +and +.In netinet6/ip6_mroute.h , +unless stated otherwise. +.Pp +The user-level process uses new +.Fn getsockopt Ns / Ns Fn setsockopt +options to +perform the API features negotiation with the kernel. +This negotiation must be performed right after the multicast routing +socket is open. +The set of desired/allowed features is stored in a bitset +(currently, in +.Vt uint32_t +i.e., maximum of 32 new features). +The new +.Fn getsockopt Ns / Ns Fn setsockopt +options are +.Dv MRT_API_SUPPORT +and +.Dv MRT_API_CONFIG . +An example: +.Bd -literal -offset 3n +uint32_t v; +getsockopt(sock, IPPROTO_IP, MRT_API_SUPPORT, &v, sizeof(v)); +.Ed +.Pp +This would set +.Va v +to the pre-defined bits that the kernel API supports. +The eight least significant bits in +.Vt uint32_t +are the same as the +eight possible flags +.Dv MRT_MFC_FLAGS_* +that can be used in +.Va mfcc_flags +as part of the new definition of +.Vt "struct mfcctl" +(see below about those flags), which leaves 24 flags for other new features. +The value returned by +.Fn getsockopt MRT_API_SUPPORT +is read-only; in other words, +.Fn setsockopt MRT_API_SUPPORT +would fail. +.Pp +To modify the API, and to set some specific feature in the kernel, then: +.Bd -literal -offset 3n +uint32_t v = MRT_MFC_FLAGS_DISABLE_WRONGVIF; +if (setsockopt(sock, IPPROTO_IP, MRT_API_CONFIG, &v, sizeof(v)) != 0) + return (ERROR); +if (v & MRT_MFC_FLAGS_DISABLE_WRONGVIF) + return (OK); /* Success */ +else + return (ERROR); +.Ed +.Pp +In other words, when +.Fn setsockopt MRT_API_CONFIG +is called, the +argument to it specifies the desired set of features to +be enabled in the API and the kernel. +The return value in +.Va v +is the actual (sub)set of features that were enabled in the kernel. +To obtain later the same set of features that were enabled, use: +.Bd -literal -offset indent +getsockopt(sock, IPPROTO_IP, MRT_API_CONFIG, &v, sizeof(v)); +.Ed +.Pp +The set of enabled features is global. +In other words, +.Fn setsockopt MRT_API_CONFIG +should be called right after +.Fn setsockopt MRT_INIT . +.Pp +Currently, the following set of new features is defined: +.Bd -literal +#define MRT_MFC_FLAGS_DISABLE_WRONGVIF (1 << 0)/*disable WRONGVIF signals*/ +#define MRT_MFC_FLAGS_BORDER_VIF (1 << 1) /* border vif */ +#define MRT_MFC_RP (1 << 8) /* enable RP address */ +#define MRT_MFC_BW_UPCALL (1 << 9) /* enable bw upcalls */ +.Ed +.\" .Pp +.\" In the future there might be: +.\" .Bd -literal +.\" #define MRT_MFC_GROUP_SPECIFIC (1 << 10) /* allow (*,G) MFC entries */ +.\" .Ed +.\" .Pp +.\" to allow (*,G) MFC entries (i.e., group-specific entries) in the kernel. +.\" For now this is left-out until it is clear whether +.\" (*,G) MFC support is the preferred solution instead of something more generic +.\" solution for example. +.\" +.\" 2. The newly defined struct mfcctl2. +.\" +.Pp +The advanced multicast API uses a newly defined +.Vt "struct mfcctl2" +instead of the traditional +.Vt "struct mfcctl" . +The original +.Vt "struct mfcctl" +is kept as is. +The new +.Vt "struct mfcctl2" +is: +.Bd -literal +/* + * The new argument structure for MRT_ADD_MFC and MRT_DEL_MFC overlays + * and extends the old struct mfcctl. + */ +struct mfcctl2 { + /* the mfcctl fields */ + struct in_addr mfcc_origin; /* ip origin of mcasts */ + struct in_addr mfcc_mcastgrp; /* multicast group associated*/ + vifi_t mfcc_parent; /* incoming vif */ + u_char mfcc_ttls[MAXVIFS];/* forwarding ttls on vifs */ + + /* extension fields */ + uint8_t mfcc_flags[MAXVIFS];/* the MRT_MFC_FLAGS_* flags*/ + struct in_addr mfcc_rp; /* the RP address */ +}; +.Ed +.Pp +The new fields are +.Va mfcc_flags[MAXVIFS] +and +.Va mfcc_rp . +Note that for compatibility reasons they are added at the end. +.Pp +The +.Va mfcc_flags[MAXVIFS] +field is used to set various flags per +interface per (S,G) entry. +Currently, the defined flags are: +.Bd -literal +#define MRT_MFC_FLAGS_DISABLE_WRONGVIF (1 << 0)/*disable WRONGVIF signals*/ +#define MRT_MFC_FLAGS_BORDER_VIF (1 << 1) /* border vif */ +.Ed +.Pp +The +.Dv MRT_MFC_FLAGS_DISABLE_WRONGVIF +flag is used to explicitly disable the +.Dv IGMPMSG_WRONGVIF +kernel signal at the (S,G) granularity if a multicast data packet +arrives on the wrong interface. +However, it should not be delivered for interfaces that are not set in +the outgoing interface, and that are not expecting to +become an incoming interface. +Hence, if the +.Dv MRT_MFC_FLAGS_DISABLE_WRONGVIF +flag is set for some of the +interfaces, then a data packet that arrives on that interface for +that MFC entry will NOT trigger a WRONGVIF signal. +If that flag is not set, then a signal is triggered (the default action). +.Pp +Typically, a multicast routing user-level process would need to know the +forwarding bandwidth for some data flow. +.Pp +The original solution for measuring the bandwidth of a dataflow was +that a user-level process would periodically +query the kernel about the number of forwarded packets/bytes per +(S,G), and then based on those numbers it would estimate whether a source +has been idle, or whether the source's transmission bandwidth is above a +threshold. +That solution is far from being scalable, hence the need for a new +mechanism for bandwidth monitoring. +.Pp +Below is a description of the bandwidth monitoring mechanism. +.Bl -bullet +.It +If the bandwidth of a data flow satisfies some pre-defined filter, +the kernel delivers an upcall on the multicast routing socket +to the multicast routing process that has installed that filter. +.It +The bandwidth-upcall filters are installed per (S,G). +There can be +more than one filter per (S,G). +.It +Instead of supporting all possible comparison operations +(i.e., < <= == != > >= ), there is support only for the +<= and >= operations, +because this makes the kernel-level implementation simpler, +and because practically we need only those two. +Furthermore, the missing operations can be simulated by secondary +user-level filtering of those <= and >= filters. +For example, to simulate !=, then we need to install filter +.Dq bw <= 0xffffffff , +and after an +upcall is received, we need to check whether +.Dq measured_bw != expected_bw . +.It +The bandwidth-upcall mechanism is enabled by +.Fn setsockopt MRT_API_CONFIG +for the +.Dv MRT_MFC_BW_UPCALL +flag. +.It +The bandwidth-upcall filters are added/deleted by the new +.Fn setsockopt MRT_ADD_BW_UPCALL +and +.Fn setsockopt MRT_DEL_BW_UPCALL +respectively (with the appropriate +.Vt "struct bw_upcall" +argument of course). +.El +.Pp +From an application point of view, a developer needs to know about +the following: +.Bd -literal +/* + * Structure for installing or delivering an upcall if the + * measured bandwidth is above or below a threshold. + * + * User programs (e.g. daemons) may have a need to know when the + * bandwidth used by some data flow is above or below some threshold. + * This interface allows the userland to specify the threshold (in + * bytes and/or packets) and the measurement interval. Flows are + * all packet with the same source and destination IP address. + * At the moment the code is only used for multicast destinations + * but there is nothing that prevents its use for unicast. + * + * The measurement interval cannot be shorter than some Tmin (3s). + * The threshold is set in packets and/or bytes per_interval. + * + * Measurement works as follows: + * + * For >= measurements: + * The first packet marks the start of a measurement interval. + * During an interval we count packets and bytes, and when we + * pass the threshold we deliver an upcall and we are done. + * The first packet after the end of the interval resets the + * count and restarts the measurement. + * + * For <= measurement: + * We start a timer to fire at the end of the interval, and + * then for each incoming packet we count packets and bytes. + * When the timer fires, we compare the value with the threshold, + * schedule an upcall if we are below, and restart the measurement + * (reschedule timer and zero counters). + */ + +struct bw_data { + struct timeval b_time; + uint64_t b_packets; + uint64_t b_bytes; +}; + +struct bw_upcall { + struct in_addr bu_src; /* source address */ + struct in_addr bu_dst; /* destination address */ + uint32_t bu_flags; /* misc flags (see below) */ +#define BW_UPCALL_UNIT_PACKETS (1 << 0) /* threshold (in packets) */ +#define BW_UPCALL_UNIT_BYTES (1 << 1) /* threshold (in bytes) */ +#define BW_UPCALL_GEQ (1 << 2) /* upcall if bw >= threshold */ +#define BW_UPCALL_LEQ (1 << 3) /* upcall if bw <= threshold */ +#define BW_UPCALL_DELETE_ALL (1 << 4) /* delete all upcalls for s,d*/ + struct bw_data bu_threshold; /* the bw threshold */ + struct bw_data bu_measured; /* the measured bw */ +}; + +/* max. number of upcalls to deliver together */ +#define BW_UPCALLS_MAX 128 +/* min. threshold time interval for bandwidth measurement */ +#define BW_UPCALL_THRESHOLD_INTERVAL_MIN_SEC 3 +#define BW_UPCALL_THRESHOLD_INTERVAL_MIN_USEC 0 +.Ed +.Pp +The +.Vt bw_upcall +structure is used as an argument to +.Fn setsockopt MRT_ADD_BW_UPCALL +and +.Fn setsockopt MRT_DEL_BW_UPCALL . +Each +.Fn setsockopt MRT_ADD_BW_UPCALL +installs a filter in the kernel +for the source and destination address in the +.Vt bw_upcall +argument, +and that filter will trigger an upcall according to the following +pseudo-algorithm: +.Bd -literal + if (bw_upcall_oper IS ">=") { + if (((bw_upcall_unit & PACKETS == PACKETS) && + (measured_packets >= threshold_packets)) || + ((bw_upcall_unit & BYTES == BYTES) && + (measured_bytes >= threshold_bytes))) + SEND_UPCALL("measured bandwidth is >= threshold"); + } + if (bw_upcall_oper IS "<=" && measured_interval >= threshold_interval) { + if (((bw_upcall_unit & PACKETS == PACKETS) && + (measured_packets <= threshold_packets)) || + ((bw_upcall_unit & BYTES == BYTES) && + (measured_bytes <= threshold_bytes))) + SEND_UPCALL("measured bandwidth is <= threshold"); + } +.Ed +.Pp +In the same +.Vt bw_upcall , +the unit can be specified in both BYTES and PACKETS. +However, the GEQ and LEQ flags are mutually exclusive. +.Pp +Basically, an upcall is delivered if the measured bandwidth is >= or +<= the threshold bandwidth (within the specified measurement +interval). +For practical reasons, the smallest value for the measurement +interval is 3 seconds. +If smaller values are allowed, then the bandwidth +estimation may be less accurate, or the potentially very high frequency +of the generated upcalls may introduce too much overhead. +For the >= operation, the answer may be known before the end of +.Va threshold_interval , +therefore the upcall may be delivered earlier. +For the <= operation however, we must wait +until the threshold interval has expired to know the answer. +.Sh EXAMPLES +.Bd -literal -offset indent +struct bw_upcall bw_upcall; +/* Assign all bw_upcall fields as appropriate */ +memset(&bw_upcall, 0, sizeof(bw_upcall)); +memcpy(&bw_upcall.bu_src, &source, sizeof(bw_upcall.bu_src)); +memcpy(&bw_upcall.bu_dst, &group, sizeof(bw_upcall.bu_dst)); +bw_upcall.bu_threshold.b_data = threshold_interval; +bw_upcall.bu_threshold.b_packets = threshold_packets; +bw_upcall.bu_threshold.b_bytes = threshold_bytes; +if (is_threshold_in_packets) + bw_upcall.bu_flags |= BW_UPCALL_UNIT_PACKETS; +if (is_threshold_in_bytes) + bw_upcall.bu_flags |= BW_UPCALL_UNIT_BYTES; +do { + if (is_geq_upcall) { + bw_upcall.bu_flags |= BW_UPCALL_GEQ; + break; + } + if (is_leq_upcall) { + bw_upcall.bu_flags |= BW_UPCALL_LEQ; + break; + } + return (ERROR); +} while (0); +setsockopt(mrouter_s4, IPPROTO_IP, MRT_ADD_BW_UPCALL, + &bw_upcall, sizeof(bw_upcall)); +.Ed +.Pp +To delete a single filter, use +.Dv MRT_DEL_BW_UPCALL , +and the fields of bw_upcall must be set to +exactly same as when +.Dv MRT_ADD_BW_UPCALL +was called. +.Pp +To delete all bandwidth filters for a given (S,G), then +only the +.Va bu_src +and +.Va bu_dst +fields in +.Vt "struct bw_upcall" +need to be set, and then just set only the +.Dv BW_UPCALL_DELETE_ALL +flag inside field +.Va bw_upcall.bu_flags . +.Pp +The bandwidth upcalls are received by aggregating them in the new upcall +message: +.Bd -literal -offset indent +#define IGMPMSG_BW_UPCALL 4 /* BW monitoring upcall */ +.Ed +.Pp +This message is an array of +.Vt "struct bw_upcall" +elements (up to +.Dv BW_UPCALLS_MAX += 128). +The upcalls are +delivered when there are 128 pending upcalls, or when 1 second has +expired since the previous upcall (whichever comes first). +In an +.Vt "struct upcall" +element, the +.Va bu_measured +field is filled in to +indicate the particular measured values. +However, because of the way +the particular intervals are measured, the user should be careful how +.Va bu_measured.b_time +is used. +For example, if the +filter is installed to trigger an upcall if the number of packets +is >= 1, then +.Va bu_measured +may have a value of zero in the upcalls after the +first one, because the measured interval for >= filters is +.Dq clocked +by the forwarded packets. +Hence, this upcall mechanism should not be used for measuring +the exact value of the bandwidth of the forwarded data. +To measure the exact bandwidth, the user would need to +get the forwarded packets statistics with the +.Fn ioctl SIOCGETSGCNT +mechanism +(see the +.Sx Programming Guide +section). +.Pp +Note that the upcalls for a filter are delivered until the specific +filter is deleted, but no more frequently than once per +.Va bu_threshold.b_time . +For example, if the filter is specified to +deliver a signal if bw >= 1 packet, the first packet will trigger a +signal, but the next upcall will be triggered no earlier than +.Va bu_threshold.b_time +after the previous upcall. +.\" +.Sh SEE ALSO +.Xr getsockopt 2 , +.Xr recvfrom 2 , +.Xr recvmsg 2 , +.Xr setsockopt 2 , +.Xr socket 2 , +.Xr icmp6 4 , +.Xr inet 4 , +.Xr inet6 4 , +.Xr intro 4 , +.Xr ip 4 , +.Xr ip6 4 , +.Xr mrouted 8 , +.Xr sysctl 8 +.\" +.Sh AUTHORS +.An -nosplit +The original multicast code was written by +.An David Waitzman +(BBN Labs), +and later modified by the following individuals: +.An Steve Deering +(Stanford), +.An Mark J. Steiglitz +(Stanford), +.An Van Jacobson +(LBL), +.An Ajit Thyagarajan +(PARC), +.An Bill Fenner +(PARC). +.Pp +The IPv6 multicast support was implemented by the KAME project +.Pq Lk https://www.kame.net , +and was based on the IPv4 multicast code. +The advanced multicast API and the multicast bandwidth +monitoring were implemented by +.An Pavlin Radoslavov +(ICSI) +in collaboration with +.An Chris Brown +(NextHop). +.Pp +This manual page was written by +.An Pavlin Radoslavov +(ICSI). diff --git a/static/openbsd/man4/mvclock.4 b/static/openbsd/man4/mvclock.4 new file mode 100644 index 00000000..722cc85c --- /dev/null +++ b/static/openbsd/man4/mvclock.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: mvclock.4,v 1.1 2018/03/31 10:12:57 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2018 $ +.Dt MVCLOCK 4 +.Os +.Sh NAME +.Nm mvclock +.Nd Marvell Armada Clock and Reset Control +.Sh SYNOPSIS +.Cd "mvclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls clock gating for integrated components of Marvell Armada SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/mvdog.4 b/static/openbsd/man4/mvdog.4 new file mode 100644 index 00000000..a8e9b0ed --- /dev/null +++ b/static/openbsd/man4/mvdog.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: mvdog.4,v 1.1 2019/09/05 18:38:30 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 5 2019 $ +.Dt MVDOG 4 +.Os +.Sh NAME +.Nm mvdog +.Nd Marvell Armada 3700 watchdog timer +.Sh SYNOPSIS +.Cd "mvdog* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the integrated watchdog timer in the Marvell +Armada 3700 SoC. +.Sh SEE ALSO +.Xr intro 4 , +.Xr watchdog 4 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/mvgicp.4 b/static/openbsd/man4/mvgicp.4 new file mode 100644 index 00000000..876fcbe9 --- /dev/null +++ b/static/openbsd/man4/mvgicp.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: mvgicp.4,v 1.1 2019/04/02 04:03:48 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 2 2019 $ +.Dt MVGICP 4 +.Os +.Sh NAME +.Nm mvgicp +.Nd Marvell ARMADA 7K/8K GICP controller +.Sh SYNOPSIS +.Cd "mvgicp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GICP controller found on the +Marvell ARMADA 7K/8K SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@openbsd.org . diff --git a/static/openbsd/man4/mvgpio.4 b/static/openbsd/man4/mvgpio.4 new file mode 100644 index 00000000..52e5e53e --- /dev/null +++ b/static/openbsd/man4/mvgpio.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: mvgpio.4,v 1.2 2018/03/31 13:12:50 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2018 $ +.Dt MVGPIO 4 +.Os +.Sh NAME +.Nm mvgpio +.Nd Marvell Armada GPIO controller +.Sh SYNOPSIS +.Cd "mvgpio* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO ports found on Marvell Armada SoCs. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/mvicu.4 b/static/openbsd/man4/mvicu.4 new file mode 100644 index 00000000..4070c21d --- /dev/null +++ b/static/openbsd/man4/mvicu.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: mvicu.4,v 1.2 2018/03/31 09:56:51 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2018 $ +.Dt MVICU 4 +.Os +.Sh NAME +.Nm mvicu +.Nd Marvell Armada Interrupt Consolidation Unit +.Sh SYNOPSIS +.Cd "mvicu* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the interrupt controller integrated on the +CP110 block of the Marvell Armada 70x0/80x0 SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +.Sh BUGS +The +.Nm +driver relies on the hardware being initialized by the firmware. diff --git a/static/openbsd/man4/mviic.4 b/static/openbsd/man4/mviic.4 new file mode 100644 index 00000000..3742d908 --- /dev/null +++ b/static/openbsd/man4/mviic.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: mviic.4,v 1.2 2019/10/07 19:38:11 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 7 2019 $ +.Dt MVIIC 4 +.Os +.Sh NAME +.Nm mviic +.Nd Marvell Armada 3700 onboard I2C controller +.Sh SYNOPSIS +.Cd "mviic* at fdt?" +.Cd "iic* at mviic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the I2C controller found on the Marvell +Armada 3700 SoC. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/mvkpcie.4 b/static/openbsd/man4/mvkpcie.4 new file mode 100644 index 00000000..e080a04e --- /dev/null +++ b/static/openbsd/man4/mvkpcie.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: mvkpcie.4,v 1.1 2020/12/03 19:23:28 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECI`AL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 3 2020 $ +.Dt MVKPCIE 4 +.Os +.Sh NAME +.Nm mvkpcie +.Nd Marvell ARMADA 3700 Host/PCIe bridge +.Sh SYNOPSIS +.Cd "mvkpcie* at fdt?" +.Cd "pci* at mvkpcie?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PCIe controller found on the +Marvell ARMADA 3710/3720 SoC. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/mvneta.4 b/static/openbsd/man4/mvneta.4 new file mode 100644 index 00000000..55fa5924 --- /dev/null +++ b/static/openbsd/man4/mvneta.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: mvneta.4,v 1.2 2023/03/02 11:49:45 jsg Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 2 2023 $ +.Dt MVNETA 4 +.Os +.Sh NAME +.Nm mvneta , +.Nm mvmdio +.Nd Marvell ARMADA Ethernet device +.Sh SYNOPSIS +.Cd "mvmdio* at fdt?" +.Cd "mvneta* at fdt?" +.Cd "eephy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Ethernet controller on the Marvell ARMADA +37x, 38x and 37xx series SoCs. +Access to the MDIO bus is provided by the +.Nm mvmdio +driver. +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr eephy 4 , +.Xr ifmedia 4 , +.Xr mii 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . diff --git a/static/openbsd/man4/mvpinctrl.4 b/static/openbsd/man4/mvpinctrl.4 new file mode 100644 index 00000000..acbb5ef6 --- /dev/null +++ b/static/openbsd/man4/mvpinctrl.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: mvpinctrl.4,v 1.2 2019/05/11 15:44:23 patrick Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 11 2019 $ +.Dt MVPINCTRL 4 +.Os +.Sh NAME +.Nm mvpinctrl +.Nd Marvell Armada pin multiplexing +.Sh SYNOPSIS +.Cd "mvpinctrl* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver uses pin control data from the device tree to configure the +MPP pins on Marvell Armada SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se +and +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/mvpp.4 b/static/openbsd/man4/mvpp.4 new file mode 100644 index 00000000..a12618d9 --- /dev/null +++ b/static/openbsd/man4/mvpp.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: mvpp.4,v 1.1 2020/06/25 12:26:31 patrick Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 25 2020 $ +.Dt MVPP 4 +.Os +.Sh NAME +.Nm mvpp , +.Nm mvppc +.Nd Marvell ARMADA Ethernet device +.Sh SYNOPSIS +.Cd "mvppc* at fdt?" +.Cd "mvpp* at mvppc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Ethernet controller on the Marvell ARMADA +70x0 and 80x0 series SoCs. +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr mii 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/mvrng.4 b/static/openbsd/man4/mvrng.4 new file mode 100644 index 00000000..265948d1 --- /dev/null +++ b/static/openbsd/man4/mvrng.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: mvrng.4,v 1.2 2018/04/07 13:30:03 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 7 2018 $ +.Dt MVRNG 4 +.Os +.Sh NAME +.Nm mvrng +.Nd Marvell ARMADA 7K/8K random number generator +.Sh SYNOPSIS +.Cd "mvrng* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the random number generator found on the +Marvell ARMADA 7K/8K SoCs. +.Pp +It feeds the random subsystem's entropy pool with 128 bits of random +data every second. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/mvrtc.4 b/static/openbsd/man4/mvrtc.4 new file mode 100644 index 00000000..a3860862 --- /dev/null +++ b/static/openbsd/man4/mvrtc.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: mvrtc.4,v 1.3 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt MVRTC 4 +.Os +.Sh NAME +.Nm mvrtc +.Nd Marvell Armada real-time clock +.Sh SYNOPSIS +.Cd "mvrtc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the RTC found on Marvell Armada SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/mvspi.4 b/static/openbsd/man4/mvspi.4 new file mode 100644 index 00000000..7d507f8e --- /dev/null +++ b/static/openbsd/man4/mvspi.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: mvspi.4,v 1.1 2019/10/07 19:43:00 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 7 2019 $ +.Dt MVSPI 4 +.Os +.Sh NAME +.Nm mvspi +.Nd Marvell Armada 3700 onboard SPI controller +.Sh SYNOPSIS +.Cd "mvspi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SPI controller found on the Marvell +Armada 3700 SoC. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/mvsw.4 b/static/openbsd/man4/mvsw.4 new file mode 100644 index 00000000..b61b5896 --- /dev/null +++ b/static/openbsd/man4/mvsw.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: mvsw.4,v 1.1 2020/11/29 22:23:51 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 29 2020 $ +.Dt MVSW 4 +.Os +.Sh NAME +.Nm mvsw +.Nd Marvell 88E6141/88E6341 switch +.Sh SYNOPSIS +.Cd "mvsw* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Marvell 88E6141/88E6341 switch. +The driver configures the hardware as an unmanaged switch that +forwards packets between all ports. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/mvtemp.4 b/static/openbsd/man4/mvtemp.4 new file mode 100644 index 00000000..e5dedc5d --- /dev/null +++ b/static/openbsd/man4/mvtemp.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: mvtemp.4,v 1.4 2023/03/12 10:49:05 jmatthew Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 12 2023 $ +.Dt MVTEMP 4 +.Os +.Sh NAME +.Nm mvtemp +.Nd Marvell Armada temperature sensor +.Sh SYNOPSIS +.Cd "mvtemp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor found on the +Marvell Armada 380, 7K and 8K SoCs. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/mvuart.4 b/static/openbsd/man4/mvuart.4 new file mode 100644 index 00000000..009b68ca --- /dev/null +++ b/static/openbsd/man4/mvuart.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: mvuart.4,v 1.1 2019/05/11 15:47:58 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 11 2019 $ +.Dt MVUART 4 +.Os +.Sh NAME +.Nm mvuart +.Nd Marvell Armada Universal Asynchronous Receiver/Transmitter +.Sh SYNOPSIS +.Cd "mvuart* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Marvell Armada Universal Asynchronous +Receiver/Transmitter (UART). +.Sh SEE ALSO +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/myx.4 b/static/openbsd/man4/myx.4 new file mode 100644 index 00000000..c44c3f01 --- /dev/null +++ b/static/openbsd/man4/myx.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: myx.4,v 1.7 2022/02/17 12:24:08 jsg Exp $ +.\" +.\" Copyright (c) 2007 Reyk Floeter +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 17 2022 $ +.Dt MYX 4 +.Os +.Sh NAME +.Nm myx +.Nd Myricom Myri-10G PCI Express 10Gb Ethernet device +.Sh SYNOPSIS +.Cd "myx* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports the Myricom Myri-10G PCI Express 10Gb Ethernet +adapters based on the Myricom Lanai-Z8E and Lanai-Z8ES chipsets, +including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +Myricom 10G-PCIE-8A-C Adapter (10GbaseCX4) +.It +Myricom 10G-PCIE-8A-R Adapter (10GbaseSR/LR) +.It +Myricom 10G-PCIE-8A-Q Adapter (10G XAUI) +.It +Myricom 10G-PCIE2-8B2-2S Adapter (10GbaseSR/LR) +.It +Myricom 10G-PCIE2-8C2-2S Adapter (10GbaseSR/LR/LRM) +.El +.Pp +Low profile versions are supported as well. +.Sh FILES +The adapter needs a firmware file, which is selected and loaded on +demand by the driver when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/myx-eth_z8e +.It Pa /etc/firmware/myx-ethp_z8e +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Reyk Floeter Aq Mt reyk@openbsd.org . +.Sh CAVEATS +While the firmware supports reading module information for +.Xr ifconfig 8 +.Cm transceiver +to use, it does not support writing to the module. +This prevents configuration of the module, which may prevent +.Xr ifconfig 8 +from reading the right data from the module where other network +cards succeed. diff --git a/static/openbsd/man4/ne.4 b/static/openbsd/man4/ne.4 new file mode 100644 index 00000000..d7e5d78d --- /dev/null +++ b/static/openbsd/man4/ne.4 @@ -0,0 +1,154 @@ +.\" $OpenBSD: ne.4,v 1.35 2011/09/03 22:59:07 jmc Exp $ +.\" $NetBSD: ne.4,v 1.4 1998/02/22 05:21:20 enami Exp $ +.\" +.\" Copyright (c) 1997 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 3 2011 $ +.Dt NE 4 +.Os +.Sh NAME +.Nm ne +.Nd NE2000 and compatible 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "ne0 at isa? port 0x240 irq 9" +.Cd "ne1 at isa? port 0x300 irq 10" +.Cd "ne2 at isa? port 0x280 irq 9" +.Cd "ne* at isapnp?" +.Cd "ne* at pci?" +.Cd "ne* at pcmcia?" +.Cd "acphy* at mii?" +.Cd "bmtphy* at mii?" +.Cd "lxtphy* at mii?" +.Cd "nsphyter* at mii?" +.Sh DESCRIPTION +The +.Nm +device driver supports NE2000 and compatible (including NE1000) Ethernet +cards, including: +.Bl -column "Linksys Trust Combo EthernetCard, EtherFast 10/100" "PCMCIA" +.It Em "Name" Ta Em "Bus" +.It Li "Accton EN2212, EN2216" Ta PCMCIA +.It Li "Addtron W89C926 Ethernet" Ta PCMCIA +.It Li "Allied Telesis LA-PCM" Ta PCMCIA +.It Li "AmbiCom AMB8002T" Ta PCMCIA +.It Li "Arowana FE" Ta PCMCIA +.It Li "Belkin F5D5020" Ta PCMCIA +.It Li "Billionton Systems CFLT2-10B" Ta CF +.It Li "Billionton Systems CFLT2-10N" Ta CF +.It Li "Billionton Systems LNT-10TN" Ta PCMCIA +.It Li "Buffalo LPC-CF-CLT" Ta CF +.It Li "Buffalo LPC4-CLX" Ta PCMCIA +.It Li "Buffalo LPC3-CLT" Ta PCMCIA +.It Li "CNet NE2000, FastEthernet" Ta PCMCIA +.It Li "Compex PCI Ethernet" Ta PCI +.It Li "Compex Linkport ENET-B" Ta PCMCIA +.It Li "Corega PCC-T, PCC-TD, EtherII PCC-T" Ta PCMCIA +.It Li "Corega FastEther PCC-T, FastEther PCC-TX" Ta PCMCIA +.It Li "Corega FastEther PCC-TXD, FastEther PCC-TXF" Ta PCMCIA +.It Li "D-Link DE-650, DE-660, DE-660+, DFE-670TXD" Ta PCMCIA +.It Li "Dayna CommuniCard E" Ta PCMCIA +.It Li "Digital DEPCM-XX" Ta PCMCIA +.It Li "Dual NE2000" Ta PCMCIA +.It Li "Edimax NE2000" Ta PCMCIA +.It Li "Genius ME 3000II SE" Ta PCMCIA +.It Li "Grey Cell GCS2000 Gold II" Ta PCMCIA +.It Li "GVC NIC-2000p, NP0335" Ta PCMCIA +.It Li "Hawking CF686TX" Ta CF +.It Li "Hawking PN650TX" Ta PCMCIA +.It Li "I-O DATA PCLA, PCLA/TE" Ta PCMCIA +.It Li "I-O DATA PCET/TX-R" Ta PCMCIA +.It Li "IC-Card" Ta PCMCIA +.It Li "Kingston KNE-PC2" Ta PCMCIA +.It Li "KTI PCI Ethernet" Ta PCI +.It Li "Linksys PCMPC100, EC2T Combo" Ta PCMCIA +.It Li "Linksys EthernetCard, Combo EthernetCard" Ta PCMCIA +.It Li "Linksys Trust Combo EthernetCard, EtherFast 10/100" Ta PCMCIA +.It Li "MACNICA ME1 for JEIDA" Ta PCMCIA +.It Li "Melco LPC3-TX" Ta PCMCIA +.It Li "National Semiconductor InfoMover" Ta PCMCIA +.It Li "NDC Instant-Link" Ta PCMCIA +.It Li "Netgear FA410TX, FA410TXC, FA411" Ta PCMCIA +.It Li "NetVin NV5000" Ta PCI +.It Li "Network Everywhere NP10T" Ta PCMCIA +.It Li "New Media LiveWire 10/100" Ta PCMCIA +.It Li "Planet SmartCom 2000" Ta PCMCIA +.It Li "Planex FNW-3600-T, FNW-3700-T" Ta PCMCIA +.It Li "Premax PE-200" Ta PCMCIA +.It Li "Realtek RT8029" Ta PCI +.It Li "Relia Technologies Ethernet" Ta PCMCIA +.It Li "RPTI EP-400, EP-401" Ta PCMCIA +.It Li "Seiko Epson EN10B" Ta PCMCIA +.It Li "SMC EZCard, 8041" Ta PCMCIA +.It Li "SMC EZCard, 8041TX" Ta PCMCIA +.It Li "Socket Communications LP-CF, LP-E" Ta PCMCIA +.It Li "Socket Communications CF 10/100" Ta CF +.It Li "SVEC PN650TX, ComboCard, LANCard" Ta PCMCIA +.It Li "Surecom NE-34" Ta PCI +.It Li "Synergy S21810" Ta PCMCIA +.It Li "Tamarack TC3299CE" Ta CF +.It Li "Tamarack NE2000" Ta PCMCIA +.It Li "Telecom Device TCD-HPC100" Ta PCMCIA +.It Li "TRENDnet TE-CF100" Ta CF +.It Li "VIA Technologies VT86C926" Ta PCI +.It Li "Winbond W89C940" Ta PCI +.It Li "Winbond W89C940F" Ta PCI +.It Li "Wisecom T210CT, iPort" Ta PCMCIA +.It Li "Xircom CFE-10" Ta PCMCIA +.El +.Sh MEDIA SELECTION +The Realtek 8019 (ISA, ISAPnP, some PCMCIA) and Realtek 8029 (PCI) +NE2000-compatible Ethernet chips include support for software media +selection. +If one of these chips is detected by the driver, the list of supported media +will be displayed. +.Pp +For all other chips supported by the +.Nm +driver, media selection must be performed either via card jumper settings or +by vendor-supplied configuration programs. +.Sh DIAGNOSTICS +.Bl -diag +.It "ne0: where did the card go?" +The driver found the card, but was unable to make the card respond +to complete the configuration sequence. +.El +.Sh SEE ALSO +.Xr acphy 4 , +.Xr bmtphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr isapnp 4 , +.Xr lxtphy 4 , +.Xr netintro 4 , +.Xr nsphyter 4 , +.Xr pci 4 , +.Xr pcmcia 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/neo.4 b/static/openbsd/man4/neo.4 new file mode 100644 index 00000000..3a09414e --- /dev/null +++ b/static/openbsd/man4/neo.4 @@ -0,0 +1,67 @@ +.\" $OpenBSD: neo.4,v 1.14 2023/09/11 05:07:34 jsg Exp $ +.\" +.\" Copyright (c) 1998 Constantine Paul Sapuntzakis +.\" All rights reserved +.\" +.\" Author: Constantine Paul Sapuntzakis (csapuntz@cvs.openbsd.org) +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The author's name or those of the contributors may not be used to +.\" endorse or promote products derived from this software without +.\" specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 11 2023 $ +.Dt NEO 4 +.Os +.Sh NAME +.Nm neo +.Nd NeoMagic 256AV/ZX audio device +.Sh SYNOPSIS +.Cd "neo* at pci?" +.Cd "audio* at neo?" +.Sh DESCRIPTION +The +.Nm +driver provides support for NeoMagic MagicMedia 256AV and 256ZX +audio chips found in many laptops, and perhaps on some PCI cards. +.Sh FILES +The driver needs a firmware file, +which is loaded on demand when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/neo-coefficients +.El +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 2.7 . +.Sh BUGS +This driver has some bugs because NeoMagic refuses to provide documentation, +even though they are discontinuing their products. +At the time of contact, all persons working at the company were hiding +behind their receptionist as if in a stage of siege. diff --git a/static/openbsd/man4/nep.4 b/static/openbsd/man4/nep.4 new file mode 100644 index 00000000..f81993cc --- /dev/null +++ b/static/openbsd/man4/nep.4 @@ -0,0 +1,84 @@ +.\" $OpenBSD: nep.4,v 1.3 2022/09/07 01:22:08 jsg Exp $ +.\" +.\" Copyright (c) 2015 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 7 2022 $ +.Dt NEP 4 +.Os +.Sh NAME +.Nm nep +.Nd Sun Neptune 10Gb Ethernet device +.Sh SYNOPSIS +.Cd "nep* at pci?" +.Cd "brgphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various NICs based on the Sun Neptune +Ethernet controller chips, including the following: +.Pp +.Bl -bullet -compact -offset indent +.It +Sun Quad GbE UTP x8 PCI Express Card +.It +Sun Quad GbE UTP x8 PCIe ExpressModule +.El +.Pp +It uses an internal or external PHY or an external 10-bit interface. +.Pp +The +.Nm +driver supports several media types, which are selected via the +.Xr ifconfig 8 +command. +The supported media types are: +.Bl -tag -width "media" -offset indent +.It Cm media No autoselect +Attempt to autoselect the media type (default) +.It Cm media No 1000baseT Cm mediaopt No full-duplex +Use 1000baseT on copper, full duplex +.It Cm media No 1000baseT Cm mediaopt No half-duplex +Use 1000baseT on copper, half duplex +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Use 100baseTX, full duplex +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Use 100baseTX, half duplex +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr brgphy 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +.Ox +support for +.Nm +first appeared in +.Ox 5.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +.Sh BUGS +The +.Nm +driver currently only supports 1Gb Ethernet NICs. +It also does not yet use many of the advanced features the Neptune +chip offers. diff --git a/static/openbsd/man4/netintro.4 b/static/openbsd/man4/netintro.4 new file mode 100644 index 00000000..773dac20 --- /dev/null +++ b/static/openbsd/man4/netintro.4 @@ -0,0 +1,549 @@ +.\" $OpenBSD: netintro.4,v 1.55 2024/09/23 20:38:49 kn Exp $ +.\" $NetBSD: netintro.4,v 1.4 1995/10/19 08:03:40 jtc Exp $ +.\" +.\" Copyright (c) 1983, 1990, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)netintro.4 8.2 (Berkeley) 11/30/93 +.\" +.Dd $Mdocdate: September 23 2024 $ +.Dt NETINTRO 4 +.Os +.Sh NAME +.Nm netintro +.Nd introduction to networking facilities +.Sh SYNOPSIS +.In sys/socket.h +.In net/route.h +.In net/if.h +.Sh DESCRIPTION +This section is a general introduction to the networking facilities +available in the system. +Documentation in this part of section +4 is broken up into three areas: +.Em protocol families +(domains), +.Em protocols , +and +.Em network interfaces . +.Pp +All network protocols are associated with a specific +.Em protocol family . +A protocol family provides basic services to the protocol +implementation to allow it to function within a specific +network environment. +These services may include packet fragmentation and reassembly, routing, +addressing, and basic transport. +A protocol family may support multiple methods of addressing, though +the current protocol implementations do not. +A protocol family is normally comprised of a number of protocols, one per +.Xr socket 2 +type. +It is not required that a protocol family support all socket types. +A protocol family may contain multiple protocols supporting the same socket +abstraction. +.Pp +A protocol supports one of the socket abstractions detailed in +.Xr socket 2 . +A specific protocol may be accessed either by creating a +socket of the appropriate type and protocol family, or +by requesting the protocol explicitly when creating a socket. +Protocols normally accept only one type of address format, +usually determined by the addressing structure inherent in +the design of the protocol family/network architecture. +Certain semantics of the basic socket abstractions are +protocol specific. +All protocols are expected to support the basic model for their particular +socket type, but may, in addition, provide non-standard facilities or +extensions to a mechanism. +For example, a protocol supporting the +.Dv SOCK_STREAM +abstraction may allow more than one byte of out-of-band +data to be transmitted per out-of-band message. +.Pp +A network interface is similar to a device interface. +Network interfaces comprise the lowest layer of the +networking subsystem, interacting with the actual transport +hardware. +An interface may support one or more protocol families and/or address formats. +The SYNOPSIS section of each network interface entry gives a sample +specification of the related drivers for use in providing a system description +to the +.Xr config 8 +program. +The DIAGNOSTICS section lists messages which may appear on the console +and/or in the system error log, +.Pa /var/log/messages +(see +.Xr syslogd 8 ) , +due to errors in device operation. +.Pp +Network interfaces may be collected together into interface groups. +An interface group is a container that can be used generically when +referring to any interface related by some criteria. +When an action is performed on an interface group, such as packet +filtering by the +.Xr pf 4 +subsystem, the operation will be applied to each member interface in the +group, if supported by the subsystem. +The +.Xr ifconfig 8 +utility can be used to view and assign membership of an interface to an +interface group with the +.Cm group +modifier. +.Sh PROTOCOLS +The system currently supports the +Internet protocols (IPv4 and IPv6), +MPLS, +and a few others. +Raw socket interfaces are provided to the IP protocol +layer of the +Internet. +Consult the appropriate manual pages in this section for more +information regarding the support for each protocol family. +.Sh ADDRESSING +Associated with each protocol family is an address +format. +All network addresses adhere to a general structure, called a +.Vt sockaddr , +described below. +However, each protocol imposes a finer, more specific structure, generally +renaming the variant, which is discussed in the protocol family manual +page alluded to above. +.Bd -literal -offset indent +struct sockaddr { + u_int8_t sa_len; /* total length */ + sa_family_t sa_family; /* address family */ + char sa_data[14]; /* actually longer */ +}; +.Ed +.Pp +The field +.Va sa_len +contains the total length of the structure, +which may exceed 16 bytes. +The following address values for +.Va sa_family +are known to the system +(and additional formats are defined for possible future implementation): +.Bd -literal +#define AF_UNIX 1 /* local to host */ +#define AF_INET 2 /* internetwork: UDP, TCP, etc. */ +#define AF_INET6 24 /* IPv6 */ +#define AF_MPLS 33 /* Multiprotocol Label Switching */ +.Ed +.Pp +The +.Va sa_data +field contains the actual address value. +Note that it may be longer than 14 bytes. +.Sh ROUTING +.Ox +provides some packet routing facilities. +The kernel maintains a routing information database, which +is used in selecting the appropriate network interface when +transmitting packets. +.Pp +A user process (or possibly multiple co-operating processes) +maintains this database by sending messages over a special kind +of socket. +This supplants fixed-size +.Xr ioctl 2 Ns s +used in earlier releases. +.Pp +This facility is described in +.Xr route 4 . +.Sh INTERFACES +Each network interface in a system corresponds to a +path through which messages may be sent and received. +A network interface usually has a hardware device associated with it, +though certain interfaces such as the loopback interface, +.Xr lo 4 , +do not. +.Pp +The following +.Xr ioctl 2 +calls may be used to manipulate network interfaces. +The +.Xr ioctl 2 +is made on a socket (typically of type +.Dv SOCK_DGRAM ) +in the desired domain. +Most of the requests +take an +.Vt ifreq +structure pointer as their parameter. +This structure is as follows: +.Bd -literal +struct ifreq { + char ifr_name[IFNAMSIZ]; /* if name, e.g. "en0" */ + union { + struct sockaddr ifru_addr; + struct sockaddr ifru_dstaddr; + struct sockaddr ifru_broadaddr; + short ifru_flags; + int ifru_metric; + int64_t ifru_vnetid; + uint64_t ifru_media; + caddr_t ifru_data; + unsigned int ifru_index; + } ifr_ifru; +#define ifr_addr ifr_ifru.ifru_addr /* address */ +#define ifr_dstaddr ifr_ifru.ifru_dstaddr /* other end of p-to-p link */ +#define ifr_broadaddr ifr_ifru.ifru_broadaddr /* broadcast address */ +#define ifr_flags ifr_ifru.ifru_flags /* flags */ +#define ifr_metric ifr_ifru.ifru_metric /* metric */ +#define ifr_mtu ifr_ifru.ifru_metric /* mtu (overload) */ +#define ifr_hardmtu ifr_ifru.ifru_metric /* hardmtu (overload) */ +#define ifr_media ifr_ifru.ifru_media /* media options */ +#define ifr_rdomainid ifr_ifru.ifru_metric /* VRF instance (overload) */ +#define ifr_vnetid ifr_ifru.ifru_vnetid /* Virtual Net Id */ +#define ifr_ttl ifr_ifru.ifru_metric /* tunnel TTL (overload) */ +#define ifr_df ifr_ifru.ifru_metric /* tunnel DF (overload) */ +#define ifr_data ifr_ifru.ifru_data /* for use by interface */ +#define ifr_index ifr_ifru.ifru_index /* interface index */ +#define ifr_llprio ifr_ifru.ifru_metric /* link layer priority */ +#define ifr_hdrprio ifr_ifru.ifru_metric /* header prio field config */ +#define ifr_pwe3 ifr_ifru.ifru_metric /* PWE3 type */ +}; +.Ed +.Pp +The supported +.Xr ioctl 2 +requests are: +.Bl -tag -width Ds +.It Dv SIOCSIFADDR Fa "struct ifreq *" +Set the interface address for a protocol family. +Following the address assignment, the +.Dq initialization +routine for the +interface is called. +.Pp +This call has been deprecated and superseded by the +.Dv SIOCAIFADDR +call, described below. +.It Dv SIOCSIFDSTADDR Fa "struct ifreq *" +Set the point-to-point address for a protocol family and interface. +.Pp +This call has been deprecated and superseded by the +.Dv SIOCAIFADDR +call, described below. +.It Dv SIOCSIFBRDADDR Fa "struct ifreq *" +Set the broadcast address for a protocol family and interface. +.Pp +This call has been deprecated and superseded by the +.Dv SIOCAIFADDR +call, described below. +.It Dv SIOCGIFADDR Fa "struct ifreq *" +Get the interface address for a protocol family. +.It Dv SIOCGIFDSTADDR Fa "struct ifreq *" +Get the point-to-point address for a protocol family and interface. +.It Dv SIOCGIFBRDADDR Fa "struct ifreq *" +Get the broadcast address for a protocol family and interface. +.It Dv SIOCGIFDESCR Fa "struct ifreq *" +Get the interface description, returned in the +.Va ifru_data +field. +.It Dv SIOCSIFDESCR Fa "struct ifreq *" +Set the interface description to the value of the +.Va ifru_data +field, limited to the size of +.Dv IFDESCRSIZE . +.It Dv SIOCSIFFLAGS Fa "struct ifreq *" +Set the interface flags. +If the interface is marked down, any processes currently routing packets +through the interface are notified; some interfaces may be reset so that +incoming packets are no longer received. +When marked up again, the interface is reinitialized. +.It Dv SIOCGIFFLAGS Fa "struct ifreq *" +Get the interface flags. +.It Dv SIOCGIFXFLAGS Fa "struct ifreq *" +Get the extended interface flags. +.It Dv SIOCSIFMTU Fa "struct ifreq *" +Set the MTU of the interface. +.It Dv SIOCGIFMTU Fa "struct ifreq *" +Get the current MTU of the interface. +.It Dv SIOCGIFHARDMTU Fa "struct ifreq *" +Get the maximum hardware MTU of the interface. +.It Dv SIOCSIFMEDIA Fa "struct ifreq *" +Set the interface media settings. +See +.Xr ifmedia 4 +for possible values. +.It Dv SIOCGIFMEDIA Fa "struct ifmediareq *" +Get the interface media settings. +The +.Vt ifmediareq +structure is as follows: +.Bd -literal +struct ifmediareq { + char ifm_name[IFNAMSIZ]; /* if name, e.g. "en0" */ + uint64_t ifm_current; /* get/set current media options */ + uint64_t ifm_mask; /* don't care mask */ + uint64_t ifm_status; /* media status */ + uint64_t ifm_active; /* active options */ + int ifm_count; /* # entries in ifm_ulist array */ + uint64_t *ifm_ulist; /* media words */ +}; +.Ed +.Pp +See +.Xr ifmedia 4 +for interpreting this value. +.It Dv SIOCSIFMETRIC Fa "struct ifreq *" +Set the interface routing metric. +The metric is used only by user-level routers. +.It Dv SIOCGIFMETRIC Fa "struct ifreq *" +Get the interface metric. +.It Dv SIOCSIFPRIORITY Fa "struct ifreq *" +Set the interface routing priority. +The interface routing priority influences the resulting routing priority of +new static routes added to the kernel using the specified interface. +The value is in the range of 0 to 16 with smaller numbers being better. +.It Dv SIOCGIFPRIORITY Fa "struct ifreq *" +Get the interface priority. +.It Dv SIOCGIFRDOMAIN Fa "struct ifreq *" +Get the interface routing domain. +This identifies which routing table is used for the interface. +.It Dv SIOCAIFADDR Fa "struct ifaliasreq *" +An interface may have more than one address associated with it +in some protocols. +This request provides a means to add additional addresses (or modify +characteristics of the primary address if the default address for the +address family is specified). +.Pp +Rather than making separate calls to set destination or broadcast addresses, +or network masks (now an integral feature of multiple protocols), a separate +structure, +.Vt ifaliasreq , +is used to specify all three facets simultaneously (see below). +One would use a slightly tailored version of this structure specific +to each family (replacing each +.Vt sockaddr +by one +of the family-specific type). +One should always set the length of a +.Vt sockaddr , +as described in +.Xr ioctl 2 . +.Pp +The +.Vt ifaliasreq +structure is as follows: +.Bd -literal +struct ifaliasreq { + char ifra_name[IFNAMSIZ]; /* if name, e.g. "en0" */ + union { + struct sockaddr ifrau_addr; + int ifrau_align; + } ifra_ifrau; +#ifndef ifra_addr +#define ifra_addr ifra_ifrau.ifrau_addr +#endif + struct sockaddr ifra_dstaddr; +#define ifra_broadaddr ifra_dstaddr + struct sockaddr ifra_mask; +}; +.Ed +.It Dv SIOCDIFADDR Fa "struct ifreq *" +This request deletes the specified address from the list +associated with an interface. +It also uses the +.Vt ifaliasreq +structure to allow for the possibility of protocols allowing +multiple masks or destination addresses, and also adopts the +convention that specification of the default address means +to delete the first address for the interface belonging to +the address family in which the original socket was opened. +.It Dv SIOCGIFCONF Fa "struct ifconf *" +Get the interface configuration list. +This request takes an +.Vt ifconf +structure (see below) as a value-result parameter. +The +.Va ifc_len +field should be initially set to the size of the buffer +pointed to by +.Va ifc_buf . +On return it will contain the length, in bytes, of the +configuration list. +.Pp +Alternately, if the +.Va ifc_len +passed in is set to 0, +.Dv SIOCGIFCONF +will set +.Va ifc_len +to the size that +.Va ifc_buf +needs to be to fit the entire configuration list and will not +fill in the other parameters. +This is useful for determining the exact size that +.Va ifc_buf +needs to be in advance. +Note, however, that this is an extension +that not all operating systems support. +.Bd -literal +struct ifconf { + int ifc_len; /* size of associated buffer */ + union { + caddr_t ifcu_buf; + struct ifreq *ifcu_req; + } ifc_ifcu; +#define ifc_buf ifc_ifcu.ifcu_buf /* buffer address */ +#define ifc_req ifc_ifcu.ifcu_req /* array of structures returned */ +}; +.Ed +.It Dv SIOCIFCREATE Fa "struct ifreq *" +Attempt to create the specified interface. +.It Dv SIOCIFDESTROY Fa "struct ifreq *" +Attempt to destroy the specified interface. +.It Dv SIOCIFGCLONERS Fa "struct if_clonereq *" +Get the list of clonable interfaces. +This request takes an +.Vt if_clonereq +structure pointer (see below) as a value-result parameter. +The +.Va ifcr_count +field should be set to the number of +.Dv IFNAMSIZ Ns -sized +strings that can fit in the buffer pointed to by +.Va ifcr_buffer . +On return, +.Va ifcr_total +will be set to the number of clonable interfaces, and the buffer pointed +to by +.Va ifcr_buffer +will be filled with the names of clonable interfaces aligned on +.Dv IFNAMSIZ +boundaries. +.Pp +The +.Vt if_clonereq +structure is as follows: +.Bd -literal +struct if_clonereq { + int ifcr_total; /* total cloners (out) */ + int ifcr_count; /* room for this many in user buffer */ + char *ifcr_buffer; /* buffer for cloner names */ +}; +.Ed +.It Dv SIOCAIFGROUP Fa "struct ifgroupreq *" +Associate the interface named by +.Va ifgr_name +with the interface group named by +.Va ifgr_group . +The +.Vt ifgroupreq +structure is as follows: +.Bd -literal +struct ifg_req { + union { + char ifgrqu_group[IFNAMSIZ]; + char ifgrqu_member[IFNAMSIZ]; + } ifgrq_ifgrqu; +#define ifgrq_group ifgrq_ifgrqu.ifgrqu_group +#define ifgrq_member ifgrq_ifgrqu.ifgrqu_member +}; + +struct ifgroupreq { + char ifgr_name[IFNAMSIZ]; + u_int ifgr_len; + union { + char ifgru_group[IFNAMSIZ]; + struct ifg_req *ifgru_groups; + struct ifg_attrib ifgru_attrib; + } ifgr_ifgru; +#define ifgr_group ifgr_ifgru.ifgru_group +#define ifgr_groups ifgr_ifgru.ifgru_groups +#define ifgr_attrib ifgr_ifgru.ifgru_attrib +}; +.Ed +.It Dv SIOCGIFGROUP Fa "struct ifgroupreq *" +Retrieve the list of groups for which an interface is a member. +The interface is named by +.Va ifgr_name . +On enter, the amount of memory in which the group names will +be written is stored in +.Va ifgr_len , +and the group names themselves will be written to the memory +pointed to by +.Va ifgr_groups . +On return, the amount of memory actually written is returned in +.Va ifgr_len . +.Pp +Alternately, if the +.Va ifgr_len +passed in is set to 0, +.Dv SIOCGIFGROUP +will set +.Va ifgr_len +to the size that +.Va ifgr_groups +needs to be to fit the entire group list and will not +fill in the other parameters. +This is useful for determining the exact size that +.Va ifgr_groups +needs to be in advance. +.It Dv SIOCDIFGROUP Fa "struct ifgroupreq *" +Remove the membership of the interface named by +.Va ifgr_name +from the group +.Va ifgr_group . +.El +.Sh SEE ALSO +.Xr netstat 1 , +.Xr ioctl 2 , +.Xr socket 2 , +.Xr arp 4 , +.Xr bridge 4 , +.Xr ifmedia 4 , +.Xr inet 4 , +.Xr intro 4 , +.Xr ip 4 , +.Xr ip6 4 , +.Xr lo 4 , +.Xr mpe 4 , +.Xr pf 4 , +.Xr tcp 4 , +.Xr udp 4 , +.Xr unix 4 , +.Xr hosts 5 , +.Xr bgpd 8 , +.Xr config 8 , +.Xr ifconfig 8 , +.Xr mrouted 8 , +.Xr netstart 8 , +.Xr ospfd 8 , +.Xr ripd 8 , +.Xr route 8 +.Sh HISTORY +The +.Nm +manual appeared in +.Bx 4.3 Tahoe . diff --git a/static/openbsd/man4/nfe.4 b/static/openbsd/man4/nfe.4 new file mode 100644 index 00000000..bbea2778 --- /dev/null +++ b/static/openbsd/man4/nfe.4 @@ -0,0 +1,101 @@ +.\" $OpenBSD: nfe.4,v 1.23 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2006 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt NFE 4 +.Os +.Sh NAME +.Nm nfe +.Nd NVIDIA nForce MCP 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "nfe* at pci?" +.Cd "atphy* at mii?" +.Cd "brgphy* at mii?" +.Cd "ciphy* at mii?" +.Cd "eephy* at mii?" +.Cd "icsphy* at mii?" +.Cd "rgephy* at mii?" +.Cd "rlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports Fast Ethernet and Gigabit Ethernet adapters based +on the NVIDIA nForce Media and Communications Processors (MCP), +the nForce, nForce 2, nForce 3, CK804, MCP04, MCP51, MCP55, +MCP61, MCP65, MCP67, MCP73, MCP77, MCP79 and MCP89 Ethernet +controller chips. +.Pp +The +.Nm +driver supports IPv4 transmit/receive IP/TCP/UDP checksum offload +with the nForce 3, CK804, MCP55, MCP77, MCP79 and MCP89 chipsets +and VLAN tag insertion and stripping with the MCP55 chipset. +.Pp +The +.Nm +driver additionally supports Wake on LAN (WoL). +See +.Xr arp 8 +and +.Xr ifconfig 8 +for more details. +.Pp +The +.Nm +driver supports the following +.Ar media +types: +.Pp +.Bl -tag -width autoselect -compact +.It Cm autoselect +Enable autoselection of the media type and options. +.It Cm 10baseT +Set 10Mbps operation. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.It Cm 1000baseT +Set 1000Mbps (Gigabit Ethernet) operation (recent models only). +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr atphy 4 , +.Xr brgphy 4 , +.Xr ciphy 4 , +.Xr eephy 4 , +.Xr icsphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr rgephy 4 , +.Xr rlphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan Gray Aq Mt jsg@openbsd.org +and +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +NVIDIA refuse to release any documentation on their products. diff --git a/static/openbsd/man4/ngbe.4 b/static/openbsd/man4/ngbe.4 new file mode 100644 index 00000000..165e82e3 --- /dev/null +++ b/static/openbsd/man4/ngbe.4 @@ -0,0 +1,79 @@ +.\" $OpenBSD: ngbe.4,v 1.2 2023/03/31 13:45:13 jmc Exp $ +.\" +.\" Copyright (c) 2023 Kevin Lo +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2023 $ +.Dt NGBE 4 +.Os +.Sh NAME +.Nm ngbe +.Nd WangXun WX1860 PCI Express 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "ngbe* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI Express Gigabit Ethernet adapters based +on the WangXun WX1860AL1 and WX1860A2 Ethernet controllers, +including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +LR-LINK LRES2034PT (WX1860AL1) +.It +LR-LINK LRES2045PT (WX1860A2) +.El +.Pp +The +.Nm +driver supports IPv4 receive IP/TCP/UDP checksum offload and VLAN +tag insertion and stripping. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width autoselect -offset indent +.It autoselect +Enables auto-negotiation for speed and duplex. +.It 10baseT Cm mediaopt No full-duplex +Sets 10Mbps operation. +.It 100baseTX Cm mediaopt No full-duplex +Sets 100Mbps operation. +.It 1000baseT +Sets 1000Mbps operation. +Only full-duplex mode is supported at this speed. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Kevin Lo Aq Mt kevlo@openbsd.org . diff --git a/static/openbsd/man4/nge.4 b/static/openbsd/man4/nge.4 new file mode 100644 index 00000000..b26fcba3 --- /dev/null +++ b/static/openbsd/man4/nge.4 @@ -0,0 +1,166 @@ +.\" $OpenBSD: nge.4,v 1.41 2022/02/17 12:24:08 jsg Exp $ +.\" Copyright (c) 2001 Wind River Systems +.\" Copyright (c) 1997, 1998, 1999, 2000, 2001 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: nge.4,v 1.11 2002/08/08 18:30:39 ambrisko Exp $ +.\" +.Dd $Mdocdate: February 17 2022 $ +.Dt NGE 4 +.Os +.Sh NAME +.Nm nge +.Nd National Semiconductor PCI 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "nge* at pci?" +.Cd "nsgphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various NICs based on the National Semiconductor +DP83820 and DP83821 Gigabit Ethernet controller chips, including the +following: +.Pp +.Bl -bullet -compact +.It +Addtron AEG320T +.It +Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T (64-bit PCI) +.It +Asante FriendlyNet GigaNIX 1000TA and 1000TPC +.It +D-Link DGE-500T +.It +Linksys EG1032v1 (32-bit PCI) and EG1064v1 (64-bit PCI) +.It +Netgear GA621 +.It +Netgear GA622T +.It +SMC EZ Card 1000 (SMC9462TX) +.It +Surecom Technology EP-320G-TX +.It +TRENDnet TEG-PCITX (32-bit PCI) and TEG-PCITX2 (64-bit PCI) +.El +.Pp +The +.Nm +driver supports IPv4 receive IP/TCP/UDP checksum offload, VLAN tag +insertion and stripping, as well as a 2048-bit multicast hash filter +and up to 4 pattern match buffers. +.Pp +The +.Nm +driver also supports jumbo frames. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It Cm autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It Cm 10baseT +Set 10Mbps operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 1000baseT +Set 1000baseT operation over twisted pair. +Both +.Cm full-duplex +and +.Cm half-duplex +modes are supported. +.It Cm 1000baseSX +Set 1000Mbps (Gigabit Ethernet) operation. +Both +.Cm full-duplex +and +.Cm half-duplex +modes are supported. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It Cm full-duplex +Force full duplex operation. +.It Cm half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr nsgphy 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T National Semiconductor DP83820 datasheet +.Re +.Rs +.%T National Semiconductor DP83861 datasheet +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@bsdi.com . diff --git a/static/openbsd/man4/nhi.4 b/static/openbsd/man4/nhi.4 new file mode 100644 index 00000000..c3486418 --- /dev/null +++ b/static/openbsd/man4/nhi.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: nhi.4,v 1.2 2025/11/03 20:56:08 jsg Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 3 2025 $ +.Dt NHI 4 +.Os +.Sh NAME +.Nm nhi +.Nd USB4 host interface +.Sh SYNOPSIS +.Cd "nhi* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the USB4 host interface. +.Pp +The driver does not implement any meaningful USB4 connection manager +functionality. +It only puts the router that is part of the host interface into a sleep state +during suspend. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr xhci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/nmea.4 b/static/openbsd/man4/nmea.4 new file mode 100644 index 00000000..5c56c0c0 --- /dev/null +++ b/static/openbsd/man4/nmea.4 @@ -0,0 +1,121 @@ +.\" $OpenBSD: nmea.4,v 1.28 2019/01/27 07:15:57 jmc Exp $ +.\" +.\" Copyright (c) 2006, 2007 Marc Balmer +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 27 2019 $ +.Dt NMEA 4 +.Os +.Sh NAME +.Nm nmea +.Nd NMEA 0183 timedelta sensor +.Sh SYNOPSIS +.Cd "pseudo-device nmea" Op Ar count +.Sh DESCRIPTION +This line discipline interfaces NMEA devices, +such as GPS receivers attached to a serial or USB port. +.Pp +The line discipline is enabled by the following sequence: +.Bd -literal -offset indent +#include +int ldisc = NMEADISC, fildes; ... +ioctl(fildes, TIOCSETD, &ldisc); +.Ed +.Pp +The byte stream is unaltered by the line discipline which +maintains timedelta and position sensors using the NMEA data. +The sensors will appear as nmea* in the list. +The timedelta (nanoseconds difference between the received time +information and the local time), position (calculated latitude +and longitude in degrees), altitude and speed can be accessed +through the +.Xr sysctl 8 +interface. +.Pp +The +.Nm +line discipline decodes the following NMEA 0183 sentences: +.Bl -tag -width "RMCXX" +.It RMC +Recommended Minimum Specific GPS/TRANSIT Data. +The time and date information, position and speed are extracted. +The warning indication is used to provide the sensor status (see below). +If the attached device sends the RMC message in the 13-field format, +the operation mode of the GPS device is reported in the sensor description. +The sensor timestamp is copied from the tty timestamp if a device with PPS +is being used and tty timestamping has been turned on. +Otherwise the sensor timestamp is taken when the initial `$' character of +a message block is received from the NMEA device. +.It GGA +Current fix data. +The altitude in meters is extracted. +.El +.Pp +Messages source are recognised by the first two characters of the NMEA +sentence according to the following prefixes: +.Pp +.Bl -tag -width "XXXXX" -offset indent -compact +.It GP +GPS +.It GA +Galileo +.It BD +BeiDou +.It GL +Glonass +.It GN +Generic GNSS +.El +.Sh SENSOR STATES +The quality of the timedelta is reported as the sensor status: +.Bl -tag -width "CRITICALXX" -offset indent +.It OK +The time information and position are valid. +The timedelta is safe to use for applications like +.Xr ntpd 8 . +.It WARN +The attached GPS receiver has been indicating a warning condition +for at least the last ten minutes. +The timedelta should be used with care. +.It CRITICAL +tty timestamping has been turned on but there is no PPS signal present or the +GPS receiver indicated a warning condition for at least the last twenty +minutes. +Check your hardware. +Some GPS units need PPS to be manually turned on. +.El +.Pp +The status of a second sensor is used to report the status of the +device itself: +.Bl -tag -width "CRITICALXX" -offset indent +.It OK +The clock is synchronized, e.g. a GPS receiver has a fix. +.It WARN +The device issued a warning condition, e.g. a GPS receiver has no fix. +.El +.Sh SEE ALSO +.Xr tty 4 , +.Xr ldattach 8 , +.Xr ntpd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +interface first appeared in +.Ox 4.0 . +.Sh AUTHORS +The +.Nm +line discipline was written by +.An Marc Balmer Aq Mt mbalmer@openbsd.org . diff --git a/static/openbsd/man4/nsclpcsio.4 b/static/openbsd/man4/nsclpcsio.4 new file mode 100644 index 00000000..34ba10ad --- /dev/null +++ b/static/openbsd/man4/nsclpcsio.4 @@ -0,0 +1,96 @@ +.\" $OpenBSD: nsclpcsio.4,v 1.11 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2004 Markus Friedl +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt NSCLPCSIO 4 +.Os +.Sh NAME +.Nm nsclpcsio +.Nd National Semiconductor PC87366 LPC Super I/O with GPIO +.Sh SYNOPSIS +.Cd "nsclpcsio* at isa?" +.Cd "gpio* at nsclpcsio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the National Semiconductor PC87366 LPC Super I/O. +The Super I/O module incorporates several logical devices, the following +ones are supported: GPIO, VLM and TMS. +.Pp +The GPIO logical device provides 29 I/O pins which can be accessed +through the +.Xr gpio 4 +framework. +The +.Xr gpioctl 8 +program allows easy manipulation of the pins from userland. +.Pp +VLM and TMS logical devices provides hardware monitoring capabilities +to be used with the +.Xr sysctl 8 +interface. +The following 17 monitoring sensors are available: +.Bl -column "Sensor" "Units" "Typical" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical Use" +.It Li "TSENS1" Ta "uK" Ta "Remote diode" +.It Li "TSENS2" Ta "uK" Ta "Remote diode" +.It Li "TNSC" Ta "uK" Ta "Local diode" +.It Li "VSENS0" Ta "uV DC" Ta "External source" +.It Li "VSENS1" Ta "uV DC" Ta "External source" +.It Li "VSENS2" Ta "uV DC" Ta "External source" +.It Li "VSENS3" Ta "uV DC" Ta "External source" +.It Li "VSENS4" Ta "uV DC" Ta "External source" +.It Li "VSENS5" Ta "uV DC" Ta "External source" +.It Li "VSENS6" Ta "uV DC" Ta "External source" +.It Li "VSB" Ta "uV DC" Ta "VSB" +.It Li "VDD" Ta "uV DC" Ta "VDD" +.It Li "VBAT" Ta "uV DC" Ta "VBAT" +.It Li "AVDD" Ta "uV DC" Ta "AVDD" +.It Li "TS1" Ta "uV DC" Ta "Thermistor" +.It Li "TS2" Ta "uV DC" Ta "Thermistor" +.It Li "TS3" Ta "uV DC" Ta "Thermistor" +.El +.Sh SEE ALSO +.Xr gpio 4 , +.Xr isa 4 , +.Xr gpioctl 8 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx 2.0 , +.Ox +support was added in +.Ox 3.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Matthias Drochner Aq Mt drochner@netbsd.org +for +.Nx +and then ported to +.Ox 3.5 +by +.An Markus Friedl Aq Mt markus@openbsd.org . +.Tn GPIO +support was added in +.Ox 3.6 +by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/nsgphy.4 b/static/openbsd/man4/nsgphy.4 new file mode 100644 index 00000000..9468928b --- /dev/null +++ b/static/openbsd/man4/nsgphy.4 @@ -0,0 +1,33 @@ +.\" $OpenBSD: nsgphy.4,v 1.12 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2001 Nathan L. Binkert +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: September 8 2021 $ +.Dt NSGPHY 4 +.Os +.Sh NAME +.Nm nsgphy +.Nd National Semiconductor DP83891/DP83861/DP83865 10/100/1Gb Ethernet PHY +.Sh SYNOPSIS +.Cd "nsgphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the National Semiconductor DP83891, DP83861 and +DP83865 10/100/1Gb Ethernet PHYs. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/nsphy.4 b/static/openbsd/man4/nsphy.4 new file mode 100644 index 00000000..d1e2fa44 --- /dev/null +++ b/static/openbsd/man4/nsphy.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: nsphy.4,v 1.11 2020/01/24 05:08:02 jsg Exp $ +.\" $NetBSD: nsphy.4,v 1.1 1998/11/04 05:53:59 thorpej Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 24 2020 $ +.Dt NSPHY 4 +.Os +.Sh NAME +.Nm nsphy +.Nd National Semiconductor DP83840 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "nsphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the National Semiconductor DP83840 and DP83840A 10/100 +Ethernet PHYs. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/nsphyter.4 b/static/openbsd/man4/nsphyter.4 new file mode 100644 index 00000000..027c6bd4 --- /dev/null +++ b/static/openbsd/man4/nsphyter.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: nsphyter.4,v 1.12 2020/01/24 05:08:02 jsg Exp $ +.\" +.\" Copyright (c) 2000 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 24 2020 $ +.Dt NSPHYTER 4 +.Os +.Sh NAME +.Nm nsphyter +.Nd National Semiconductor DP83815/DP83843/DP83847 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "nsphyter* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the National Semiconductor +PHYTER DP83843/DP83847 +Ethernet PHYs. +This driver also supports the integrated PHY on the +MacPHYTER DP83815. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr nsphy 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/null.4 b/static/openbsd/man4/null.4 new file mode 100644 index 00000000..6135e92d --- /dev/null +++ b/static/openbsd/man4/null.4 @@ -0,0 +1,61 @@ +.\" $OpenBSD: null.4,v 1.5 2019/08/31 16:26:24 schwarze Exp $ +.\" $NetBSD: null.4,v 1.3 1994/11/30 16:22:29 jtc Exp $ +.\" +.\" Copyright (c) 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)null.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: August 31 2019 $ +.Dt NULL 4 +.Os +.Sh NAME +.Nm null +.Nd the null device +.Sh DESCRIPTION +The +.Nm +device accepts and reads data as any ordinary (and willing) file, +but throws it away. +The length of the +.Nm +device is always zero. +.Sh FILES +.Bl -tag -width /dev/null +.It Pa /dev/null +.El +.Sh SEE ALSO +.Xr zero 4 +.Sh HISTORY +.Nm +first appeared in +.At v4 +as an empty file, +.Pa /dev/null , +which returned end of file when being read from. +An implementation which could also be written to first appeared in +.At v5 . diff --git a/static/openbsd/man4/nviic.4 b/static/openbsd/man4/nviic.4 new file mode 100644 index 00000000..2938c228 --- /dev/null +++ b/static/openbsd/man4/nviic.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: nviic.4,v 1.13 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt NVIIC 4 +.Os +.Sh NAME +.Nm nviic +.Nd NVIDIA nForce2/3/4 SMBus controller +.Sh SYNOPSIS +.Cd "nviic* at pci?" +.Cd "iic* at nviic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the NVIDIA nForce2/3/4 +and MCP51/55/61/65/67/73/77/79/89 SMBus +host interface to be used with the +.Xr iic 4 +framework. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . +.Sh BUGS +The driver doesn't support I2C commands with a data buffer size of more +than 2 bytes. diff --git a/static/openbsd/man4/nvme.4 b/static/openbsd/man4/nvme.4 new file mode 100644 index 00000000..137534b4 --- /dev/null +++ b/static/openbsd/man4/nvme.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: nvme.4,v 1.4 2024/09/26 06:10:34 jmc Exp $ +.\" +.\" Copyright (c) 2016 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 26 2024 $ +.Dt NVME 4 +.Os +.Sh NAME +.Nm nvme +.Nd Non-Volatile Memory Host Controller Interface +.Sh SYNOPSIS +.Cd "nvme* at pci?" +.Cd "nvme* at aplns? # arm64" +.Sh DESCRIPTION +The +.Nm +driver provides support for NVMe, or NVM Express, +storage controllers conforming to the +Non-Volatile Memory Host Controller Interface specification. +.Pp +Although the NVMe specification provides its own command set, the +.Nm +driver provides access to the storage via a SCSI translation layer. +.Pp +Sensor values are made available through the +.Va hw.sensors +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr aplns 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/nvt.4 b/static/openbsd/man4/nvt.4 new file mode 100644 index 00000000..b90200ec --- /dev/null +++ b/static/openbsd/man4/nvt.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: nvt.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2011 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt NVT 4 +.Os +.Sh NAME +.Nm nvt +.Nd Nuvoton W83795G/ADG temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "nvt* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Tn Nuvoton +W83795G and W83795ADG hardware monitors. +These devices possess several voltage, temperature and fan speed sensors. +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/oce.4 b/static/openbsd/man4/oce.4 new file mode 100644 index 00000000..ed427275 --- /dev/null +++ b/static/openbsd/man4/oce.4 @@ -0,0 +1,68 @@ +.\" $OpenBSD: oce.4,v 1.4 2018/01/28 12:59:12 jmc Exp $ +.\" +.\" Copyright (c) 2012 Mike Belopuhov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 28 2018 $ +.Dt OCE 4 +.Os +.Sh NAME +.Nm oce +.Nd Emulex OneConnect 10Gb Ethernet device +.Sh SYNOPSIS +.Cd "oce* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports Emulex OneConnect 10Gb Ethernet adapters based on +the BladeEngine 2, BladeEngine 3 and Lancer chipsets, including the +following: +.Pp +.Bl -bullet -offset indent -compact +.It +Emulex OCe11102 (SPF+/10GbaseSR or 10GbaseT) +.It +Emulex OCe10102 (SPF+/10GbaseSR) +.It +HP NC550M Flex-10 (10GbaseKR) +.It +HP NC552M Flex-10 (10GbaseKR) +.It +HP NC550SFP (SPF+/10GbaseSR) +.It +HP NC552SFP (SPF+/10GbaseSR) +.It +IBM System x 10GbE (SPF+/10GbaseSR) +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by Emulex and ported from +.Fx +by +.An Mike Belopuhov . diff --git a/static/openbsd/man4/ociic.4 b/static/openbsd/man4/ociic.4 new file mode 100644 index 00000000..4c95d897 --- /dev/null +++ b/static/openbsd/man4/ociic.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: ociic.4,v 1.1 2021/06/16 13:56:46 kettenis Exp $ +.\" +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 16 2021 $ +.Dt OCIIC 4 +.Os +.Sh NAME +.Nm ociic +.Nd OpenCores I2C controller +.Sh SYNOPSIS +.Cd "ociic* at fdt?" +.Cd "iic* at ociic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the OpenCores I2C controller such as the +I2C controller integrated on the SiFive FU540/FU740 SoCs. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/ohci.4 b/static/openbsd/man4/ohci.4 new file mode 100644 index 00000000..23d2d21b --- /dev/null +++ b/static/openbsd/man4/ohci.4 @@ -0,0 +1,65 @@ +.\" $OpenBSD: ohci.4,v 1.16 2021/12/29 18:44:52 patrick Exp $ +.\" $NetBSD: ohci.4,v 1.5 1999/11/23 01:47:34 augustss Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 29 2021 $ +.Dt OHCI 4 +.Os +.Sh NAME +.Nm ohci +.Nd USB Open Host Controller Interface +.Sh SYNOPSIS +.Cd "ohci* at acpi?" +.Cd "ohci* at cardbus?" +.Cd "ohci* at fdt?" +.Cd "ohci* at pci?" +.Cd "ohci* at voyager? " Pq loongson +.Cd "usb* at ohci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Open Host Controller Interface, +which provides an interface to +.Xr usb 4 +devices. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr cardbus 4 , +.Xr ehci 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr uhci 4 , +.Xr usb 4 , +.Xr voyager 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.7 . diff --git a/static/openbsd/man4/onewire.4 b/static/openbsd/man4/onewire.4 new file mode 100644 index 00000000..c4de7c67 --- /dev/null +++ b/static/openbsd/man4/onewire.4 @@ -0,0 +1,75 @@ +.\" $OpenBSD: onewire.4,v 1.13 2021/08/21 18:28:52 jmc Exp $ +.\" +.\" Copyright (c) 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 21 2021 $ +.Dt ONEWIRE 4 +.Os +.Sh NAME +.Nm onewire +.Nd 1-Wire bus +.Sh SYNOPSIS +.Cd "onewire* at gpioow?" +.Cd "onewire* at uow?" +.Pp +.Cd "option ONEWIREVERBOSE" +.Sh DESCRIPTION +1-Wire bus was originally developed by Dallas Semiconductor for connecting +integrated circuits. +It is commonly used for connecting devices such as electronic keys, EEPROMs, +temperature sensors, real-time clocks, security chips, etc. +.Pp +The +.Nm +driver provides a uniform programming interface layer between +1-Wire master controllers and various 1-Wire slave devices. +Each 1-Wire master controller attaches a +.Nm +framework; several slave devices can then be attached to the +.Nm +bus. +.Pp +The driver supports plugging and unplugging slave devices on the fly. +.Sh SUPPORTED MASTERS +.Bl -tag -width 11n -offset ind -compact +.It Xr gpioow 4 +1-Wire bus bit-banging through GPIO pin +.It Xr uow 4 +Maxim/Dallas DS2490 USB 1-Wire adapter +.El +.Sh SUPPORTED SLAVES +.Bl -tag -width 11n -offset ind -compact +.It Xr owctr 4 +1-Wire counter device +.It Xr owid 4 +1-Wire ID device +.It Xr owsbm 4 +1-Wire smart battery monitor device +.It Xr owtemp 4 +1-Wire temperature device +.El +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/oosiop.4 b/static/openbsd/man4/oosiop.4 new file mode 100644 index 00000000..6e804e86 --- /dev/null +++ b/static/openbsd/man4/oosiop.4 @@ -0,0 +1,111 @@ +.\" $OpenBSD: oosiop.4,v 1.11 2022/02/17 12:24:08 jsg Exp $ +.\" $NetBSD: osiop.4,v 1.2 2001/09/22 01:44:55 wiz Exp $ +.\" +.\" Copyright (c) 2001 Izumi Tsutsui. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 17 2022 $ +.Dt OOSIOP 4 +.Os +.Sh NAME +.Nm oosiop +.Nd Symbios/NCR 53C700 SCSI driver +.Sh SYNOPSIS +.Cd "# hppa" +.Cd "oosiop* at gsc? irq 9" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Tn Symbios/NCR +53C700 +.Tn SCSI +controller chip. +.Pp +The +.Tn Symbios/NCR +53C710 +.Tn SCSI +controller is handled by the +.Xr osiop 4 +driver, while the +.Tn Symbios/NCR +53C8xx +.Tn PCI +.Tn SCSI +host adapters are handled by the +.Xr siop 4 +driver. +.\" .Sh CONFIGURATION +.\" The +.\" .Nm +.\" driver supports the following +.\" .Sy flags +.\" for use in +.\" .Xr config 8 +.\" files: +.\" .Pp +.\" .Bl -tag -compact -width "bits 8-15:" +.\" .It bits 0-7 : +.\" disable disconnect/reselect for the corresponding +.\" .Tn SCSI +.\" target +.\" .It bits 8-15 : +.\" disable synchronous negotiation for +.\" .Tn SCSI +.\" target +.\" .It bits 16 : +.\" disable DMA interrupts +.\" .El +.\" .Pp +.\" .Qq Target +.\" is synonymous with +.\" .Tn SCSI +.\" ID number. +.\" .Pp +.\" Note that +.\" .Tn SCSI +.\" tape drives should be allowed to perform disconnect/reselect or performance +.\" will suffer. +.\" .Sh BUGS +.\" Neither +.\" .Tn DMA +.\" or synchronous data transfers are currently supported. +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr osiop 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr siop 4 , +.Xr st 4 , +.Xr uk 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx 1.6 , +and was ported to +.Ox 3.5 . diff --git a/static/openbsd/man4/openprom.4 b/static/openbsd/man4/openprom.4 new file mode 100644 index 00000000..e7b52eae --- /dev/null +++ b/static/openbsd/man4/openprom.4 @@ -0,0 +1,169 @@ +.\" $OpenBSD: openprom.4,v 1.3 2026/04/21 20:00:55 jca Exp $ +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This software was developed by the Computer Systems Engineering group +.\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and +.\" contributed to Berkeley. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)openprom.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: April 21 2026 $ +.Dt OPENPROM 4 +.Os +.Sh NAME +.Nm openprom +.Nd OPENPROM interface +.Sh SYNOPSIS +.In machine/openpromio.h +.Sh DESCRIPTION +The file +.Pa /dev/openprom +is an interface to the OPENPROM. +This interface is highly stylized, +ioctls are used for all operations. +These ioctls refer to +.Dq nodes , +which are simply +.Dq magic +integer values describing data areas. +Occasionally the number 0 may be used or returned instead, +as described below. +.Pp +The calls that take and/or return a node +use a pointer to an +.Vt int +variable for this purpose; +others use a pointer to a +.Vt struct opiocdesc +descriptor, +which contains a node and two counted strings. +The first string is comprised of the fields +.Li op_namelen +(an +.Vt int ) +and +.Li op_name +(a +.Vt char * ) , +giving the name of a field. +The second string is comprised of the fields +.Li op_buflen +and +.Li op_buf , +used analogously. +These two counted strings work in a +.Dq value-result +fashion. +At entry to the ioctl, +the counts are expected to reflect the buffer size; +on return, +the counts are updated to reflect the buffer contents. +.Pp +The following ioctls are supported: +.Bl -tag -width OPIOCGETOPTNODE +.It Dv OPIOCGETOPTNODE +Takes nothing, and fills in the options node number. +.It Dv OPIOCGETNEXT +Takes a node number and returns the number of the following node. +The node following the last node is number 0; +the node following number 0 is the first node. +.It Dv OPIOCGETCHILD +Takes a node number and returns the number of the first +.Dq child +of that node. +This child may have siblings; these can be discovered by using +.Dv OPIOCGETNEXT . +.It Dv OPIOCGET +Fills in the value of the named property for the given node. +If no such property is associated with that node, +the value length is set to -1. +If the named property exists but has no value, +the value length is set to 0. +.It Dv OPIOCSET +Writes the given value under the given name. +The OPENPROM may refuse this operation, +in this case +.Dv EINVAL +is returned. +.It Dv OPIOCNEXTPROP +Finds the property whose name follows the given name +in OPENPROM internal order. +The resulting name is returned in the value field. +If the named property is the last, the +.Dq next +name is the empty string. +As with +.Dv OPIOCGETNEXT , +the next name after the empty string is the first name. +.El +.Sh FILES +.Pa /dev/openprom +.Sh ERRORS +The following may result in rejection of an operation: +.Bl -tag -width "[ENAMETOOLONG]" +.It Bq Er EINVAL +The given node number +is not zero +and does not correspond to any valid node, +or is zero where zero is not allowed. +.It Bq Er EBADF +The requested operation requires permissions not specified at the call to +.Fn open . +.It Bq Er ENAMETOOLONG +The given name or value field +exceeds the maximum allowed length (8191 bytes). +.It Bq Er ENOMEM +Memory could not be allocated. +.It Bq Er ENOTTY +The ioctl is not supported on this architecture. +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr eeprom 8 +.Sh HISTORY +The +.Nm +interface first appeared in +.Ox 3.0 +for sparc64. +It has been available on macppc since +.Ox 4.3 , +on octeon since +.Ox 6.0 , +on armv7 since +.Ox 6.0 , +on arm64 since +.Ox 6.1 , +on powerpc64 since +.Ox 6.8 , +and on riscv64 since +.Ox 7.0 . +.Sh BUGS +Due to limitations within the OPENPROM itself, +these functions run at elevated priority +and may adversely affect system performance. diff --git a/static/openbsd/man4/options.4 b/static/openbsd/man4/options.4 new file mode 100644 index 00000000..635532df --- /dev/null +++ b/static/openbsd/man4/options.4 @@ -0,0 +1,551 @@ +.\" $OpenBSD: options.4,v 1.273 2025/06/01 00:32:54 rsadowski Exp $ +.\" $NetBSD: options.4,v 1.21 1997/06/25 03:13:00 thorpej Exp $ +.\" +.\" Copyright (c) 1998 Theo de Raadt +.\" Copyright (c) 1998 Todd Miller +.\" Copyright (c) 1998 Gene Skonicki +.\" Copyright (c) 1996 +.\" Perry E. Metzger. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgment: +.\" This product includes software developed for the NetBSD Project +.\" by Perry E. Metzger. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: June 1 2025 $ +.Dt OPTIONS 4 +.Os +.Sh NAME +.Nm options +.Nd kernel configuration options +.Sh SYNOPSIS +.Cd option ... +.Sh DESCRIPTION +This manual page describes a number of miscellaneous kernel +configuration options that may be specified in a kernel config file. +See +.Xr config 8 +for information on how to configure and build kernels. +.Em Note : +options are passed to the compile process as +.Fl D +flags to the C compiler. +.Sh DEBUGGING OPTIONS +.Bl -ohang +.It Cd makeoptions DEBUG="" +Do not build the debug kernel +.Pa bsd.gdb . +Normally, +.Pa bsd.gdb +is built +(in addition to the regular +.Pa bsd +kernel) +and is used for debugging kernels and their crash dumps with +.Xr gdb 1 . +A crash dump can be debugged by starting gdb with +.Pa bsd.gdb +as an argument (no core file) and then using the gdb command +.Dq target kvm COREFILE . +.It Cd makeoptions PROF="-pg" +The +.Fl pg +flag causes the kernel to be compiled with support for profiling. +The +.Cm option GPROF +is required for the kernel compile to succeed. +.It Cd option ACCOUNTING +Adds support for the +.Xr acct 2 +system call. +.It Cd option DDB +Compiles in a kernel debugger for diagnosing kernel problems. +See +.Xr ddb 4 . +.It Cd option DDB_SAFE_CONSOLE +Allows a break into the kernel debugger during boot. +Useful when debugging problems that can cause +.Xr init 8 +to fail. +.It Cd option DEBUG +Turns on miscellaneous kernel debugging. +Since options are turned into preprocessor defines (see above), +.Cm option DEBUG +is equivalent to doing a +.Em #define DEBUG +throughout the kernel. +Much of the kernel has +.Em #ifdef DEBUG +conditional debugging code. +Note that many parts of the kernel (typically device drivers) include their own +.Em #ifdef XXX_DEBUG +conditionals instead. +.It Cd option DIAGNOSTIC +Adds code to the kernel that does internal consistency checks. +This code will cause the kernel to panic if corruption of internal data +structures is detected. +.It Cd option GPROF +Adds code to the kernel for kernel profiling with +.Xr kgmon 8 . +.It Cd option KTRACE +Adds hooks for the system call tracing facility, which allows users to +watch the system call invocation behavior of processes. +See +.Xr ktrace 1 . +.It Cd option KUBSAN +Detect undefined behavior in the kernel. +See +.Xr kubsan 4 . +.It Cd option NO_PROPOLICE +Do not compile the kernel with the ProPolice stack protection. +See +.Xr gcc-local 1 +for more information about ProPolice. +.It Cd option PTRACE +Adds hooks for the process tracing facility, allowing a process to +control and observe another process. +See +.Xr ptrace 2 . +.It Cd option SMALL_KERNEL +Removes some features and some optimizations from the kernel to reduce the +size of the resulting kernel binary. +This option is used on some installation media and should not be used +for general purpose kernels. +.It Cd option VFSLCKDEBUG +Turns on debugging for the Virtual File System interface. +See +.Xr vfs 9 . +.It Cd option WITNESS +Compiles in a lock checker for detecting lock order violations in the kernel. +See +.Xr witness 4 . +.It Cd option WITNESS_COUNT= Ns Ar integer +Maximum number of lock types that are tracked by +.Xr witness 4 . +It defaults to 1536. +.It Cd option WITNESS_LOCKTRACE +Enable +.Xr witness 4 +lock stack trace saving at boot. +The feature is disabled by default and has to be enabled by setting the +.Va kern.witness.locktrace +.Xr sysctl 8 +variable. +.It Cd option WITNESS_WATCH +Enable +.Xr witness 4 +at boot. +By default, the subsystem is disabled and has to be enabled at runtime +by raising the +.Va kern.witness.watch +.Xr sysctl 8 +variable. +.El +.Sh FILE SYSTEMS +.Bl -ohang +.It Cd option CD9660 +Includes code for the ISO 9660 + Rock Ridge file system, which is the +standard file system used on many CD-ROMs. +It also supports Joliet extensions. +See +.Xr mount_cd9660 8 . +.It Cd option FFS +Includes code implementing the Berkeley Fast File System +.Em ( FFS ) . +Most machines need this if they are not running diskless. +.It Cd option FFS2 +Includes code implementing the enhanced Fast File System +.Em ( FFS2 ) . +.It Cd option MFS +Include the memory file system +.Em ( MFS ) . +This file system stores files in swappable memory, and produces +notable performance improvements when it is used as the file store +for +.Pa /tmp +or similar mount points. +See +.Xr mount_mfs 8 . +.It Cd option MSDOSFS +Includes support for the MS-DOS FAT file system. +The kernel also implements the Windows 95 +extensions which permit the use of longer, mixed-case file names. +See +.Xr mount_msdos 8 +and +.Xr fsck_msdos 8 . +.It Cd option NFSCLIENT +Include the client side of the +.Em NFS +(Network File System) remote file sharing protocol. +Although the bulk of the code implementing +.Em NFS +is kernel based, several user level daemons are needed for it to work. +See +.Xr mount_nfs 8 +for details on NFS. +.It Cd option NTFS +Includes support for reading NTFS file systems. +See +.Xr mount_ntfs 8 . +.It Cd option UDF +Includes code for the UDF file systems typically found on DVD discs. +See +.Xr mount_udf 8 . +.It Cd option TMPFS +Includes code for the TMPFS efficient memory file system. +See +.Xr mount_tmpfs 8 . +.El +.Sh FILE SYSTEM OPTIONS +.Bl -ohang +.It Cd option BUFCACHEPERCENT= Ns Ar integer +The maximum percentage of DMA-reachable physical memory the buffer cache may use. +.It Cd option EXT2FS_SYSTEM_FLAGS +This option changes the behavior of the APPEND and IMMUTABLE flags +for a file on an +.Em EXT2FS +filesystem. +Without this option, the superuser or owner of the file can set and clear them. +With this option, only the superuser can set them, and they can't be cleared +if the securelevel is greater than 0. +See also +.Xr chflags 1 . +.It Cd option FIFO +Adds support for +.At V +style FIFOs (i.e., +.Dq named pipes ) . +This option is recommended in almost all cases as many programs use these. +.It Cd option NFSSERVER +Include the server side of the +.Em NFS +(Network File System) remote file sharing protocol. +Although the bulk of the code implementing +.Em NFS +is kernel based, several user level daemons are needed for it to +work. +See +.Xr mountd 8 +and +.Xr nfsd 8 . +.It Cd option QUOTA +Enables kernel support for file system quotas. +See +.Xr quotaon 8 , +.Xr edquota 8 , +.Xr repquota 8 , +and +.Xr quota 1 . +Note that quotas only work on +.Dq ffs +file systems, although +.Xr rpc.rquotad 8 +permits them to be accessed over +.Em NFS . +.It Cd option UFS_DIRHASH +This option enables using an in memory hash table to speed lookups +in large directories. +.El +.Sh MISCELLANEOUS OPTIONS +.Bl -ohang +.It Cd option APERTURE +Provide in-kernel support for controlling VGA framebuffer mapping +and PCI configuration registers by user-processes +(such as an X Window System server). +See +.Xr xf86 4 . +This option is supported on the +.Va alpha , +.Va amd64 , +.Va i386 , +.Va macppc , +and +.Va sparc64 +architectures. +.It Cd option BOOT_CONFIG +Adds support for the +.Fl c +boot option (User Kernel Config). +Allows modification of kernel settings (e.g., device parameters) before +booting the system. +See +.Xr boot_config 8 . +.It Cd option CRYPTO +Enables support for the kernel cryptographic framework. +See +.Xr crypto 9 . +While not IP specific, this option is usually used in conjunction with option +.Em IPSEC . +.It Cd option EISAVERBOSE +Makes the boot process more verbose for EISA peripherals. +See +.Xr eisa 4 . +.It Cd option KMEMSTATS +The kernel memory allocator, +.Xr malloc 9 , +will keep statistics on its performance if this option is enabled. +.It Cd option MULTIPROCESSOR +On those architectures that have it, this enables multiprocessor support. +.It Cd option PCIVERBOSE +Makes the boot process more verbose for PCI peripherals +(vendor names and other information is printed, etc.). +See +.Xr pci 4 . +.It Cd option PCMCIAVERBOSE +Makes the boot process more verbose for PCMCIA peripherals. +See +.Xr pcmcia 4 . +.It Cd option USER_PCICONF +Enables the user level access to the PCI bus configuration space +through ioctls on the +.Pa /dev/pci +device. +It's used by +.Xr Xorg 1 +and +.Xr pcidump 8 . +See +.Xr pci 4 . +.It Cd option UVM_SWAP_ENCRYPT +Enables kernel support for encrypting pages that are written out to +swap storage. +Swap encryption prevents sensitive data from remaining +on the disk even after the operating system has been shut down. +This option should be turned on if cryptographic filesystems are used. +The sysctl variable +.Em vm.swapencrypt.enable +controls its behaviour. +See +.Xr sysctl 8 +and +.Xr sysctl 2 . +.El +.Sh NETWORKING OPTIONS +.Bl -ohang +.It Cd option ENCDEBUG +This option permits the conditional logging of IPsec debugging information, +and requires the +.Em IPSEC +option. +Debug logging can be turned on/off through the use of the +.Em net.inet.ip.encdebug +sysctl variable. +If +.Em net.inet.ip.encdebug +is 1, debug logging is on. +See +.Xr sysctl 8 +and +.Xr sysctl 2 . +.It Cd option INET6 +Includes support for the IPv6 protocol stack. +See +.Xr inet6 4 . +.Em INET6 +enables multicast routing code as well. +.It Cd option IPSEC +This option enables IP security protocol support. +See +.Xr ipsec 4 +for more details. +.It Cd option MROUTING +Includes support for IP multicast routers. +Multicast routing is controlled by the +.Xr mrouted 8 +daemon. +.It Cd option PIPEX +Includes pipex in-kernel acceleration for PPPoE, L2TP or PPTP. +See +.Xr pipex 4 . +.It Cd option PPP_BSDCOMP +Enables BSD compressor for PPP connections. +.It Cd option PPP_DEFLATE +For use in conjunction with PPP_BSDCOMP; provides an interface to zlib for PPP +for deflate compression/decompression. +.It Cd option PPPOE_TERM_UNKNOWN_SESSIONS +Send PADT to terminate open sessions before connecting. +See +.Xr pppoe 4 . +.It Cd option SOCKET_SPLICE +Enables zero-copy socket splicing in the kernel. +See +.Dv SO_SPLICE +in +.Xr setsockopt 2 +and +.Xr sosplice 9 . +.It Cd option TCP_ECN +Turns on Explicit Congestion Notification (RFC 3168). +.Em ECN +allows intermediate routers to use the Congestion Experienced +codepoint in the IP header as an indication of congestion, and allows +TCP to adjust the transmission rate using this signal. +Both communication endpoints negotiate enabling +.Em ECN +functionality at the TCP connection establishment. +.It Cd option TCP_SIGNATURE +Turns on support for the TCP MD5 Signature option (RFC 2385). +This is used by +Internet backbone routers to provide per-packet authentication for the TCP +packets used to communicate BGP routing information. +You will also need a +routing daemon that supports this option in order to actually use it. +.El +.Sh OPERATION RELATED OPTIONS +.Bl -ohang -compact +.It Cd option BUFPAGES= Ns Ar value +This option sets the number of pages available for the buffer cache. +The default value is machine dependent, often calculated as +between 5% and 10% of total available RAM. +.Pp +.It Cd option NKMEMPAGES= Ns Ar value +Size of kernel malloc area in PAGE_SIZE-sized logical pages. +This area is covered by the kernel submap +.Em kmem_map . +The kernel attempts to auto-size this map based on the amount of +physical memory in the system. +Platform-specific code may place bounds on this computed size, +which may be viewed with the +.Xr sysctl 8 +variable +.Em vm.nkmempages . +.El +.Sh SCSI SUBSYSTEM OPTIONS +See +.Xr scsi 4 . +.Bl -ohang +.It Cd option SCSI_DELAY= Ns Ar value +Delay for +.Ar value +seconds before starting to probe the first SCSI bus. +This can be used if a SCSI device needs extra time to get ready. +.It Cd option SCSIDEBUG +Enable printing of SCSI subsystem debugging info to the console. +Debugging info on the probing and attachment of all SCSI devices will +be printed. +.Pp +Additional information can be requested by setting +.Em SCSIDEBUG_BUSES , +.Em SCSIDEBUG_LEVEL , +.Em SCSIDEBUG_LUNS +and +.Em SCSIDEBUG_TARGETS . +.It Cd option SCSIDEBUG_BUSES= Ns Ar value +Define which SCSI buses will print debug info. +Each bit enables debugging info for the corresponding bus. +e.g. a value of 0x1 enables debug info for bus 0. +.It Cd option SCSIDEBUG_LEVEL= Ns Ar value +Define which of the four levels of debugging info are printed. +Each bit enables a level, and multiple levels are specified by setting multiple +bits. +.Bd -literal -offset indent +0x0010 (SDEV_DB1) SCSI commands, errors, and data +0x0020 (SDEV_DB2) routine flow +0x0040 (SDEV_DB3) routine internals +0x0080 (SDEV_DB4) miscellaneous addition debugging +.Ed +.Pp +.Em SCSIDEBUG_LEVEL +defaults to a value of 0x0030 (SDEV_DB1|SDEV_DB2). +.It Cd option SCSIDEBUG_LUNS= Ns Ar value +Define which SCSI luns will print debug info. +Each bit enables debugging info for the corresponding lun. +.It Cd option SCSIDEBUG_TARGETS= Ns Ar value +Define which SCSI targets will print debug info. +Each bit enables debugging info for the corresponding target. +.It Cd option SCSITERSE +Terser SCSI error messages. +This omits the table for decoding ASC/ASCQ info, saving about 30KB. +.El +.Sh SYSTEM V IPC OPTIONS +.Bl -ohang +.It Cd option SEMMNI= Ns Ar value +Number of semaphore identifiers (also called semaphore handles +and semaphore sets) available in the system. +Default value is 10. +The kernel allocates memory for the control structures at startup, +so arbitrarily large values should be avoided. +.It Cd option SEMMNS= Ns Ar value +Maximum number of semaphores in all sets in the system. +Default value is 60. +.It Cd option SEMMNU= Ns Ar value +Maximum number of semaphore undo structures in the system. +Default value is 30. +.It Cd option SEMUME= Ns Ar value +Maximum number of per-process undo operation entries in the +system. +Semaphore undo operations are invoked by the kernel when +.Xr semop 2 +is called with the SEM_UNDO flag and the process holding +the semaphores terminates unexpectedly. +Default value is 10. +.It Cd option SHMMAXPGS= Ns Ar value +Sets the maximum number of +.At V +style shared memory pages that are available through the +.Xr shmget 2 +system call. +Default value is 1024 on most architectures. +See +.Pa /usr/include/machine/vmparam.h +for the default. +.It Cd option SYSVMSG +Includes support for +.At V +style message queues. +See +.Xr msgctl 2 , +.Xr msgget 2 , +.Xr msgrcv 2 , +.Xr msgsnd 2 . +.It Cd option SYSVSEM +Includes support for +.At V +style semaphores. +See +.Xr semctl 2 , +.Xr semget 2 , +.Xr semop 2 . +.It Cd option SYSVSHM +Includes support for +.At V +style shared memory. +See +.Xr shmat 2 , +.Xr shmctl 2 , +.Xr shmdt 2 , +.Xr shmget 2 . +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr files.conf 5 , +.Xr config 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +man page first appeared in +.Ox 2.3 . diff --git a/static/openbsd/man4/osiop.4 b/static/openbsd/man4/osiop.4 new file mode 100644 index 00000000..1bbef213 --- /dev/null +++ b/static/openbsd/man4/osiop.4 @@ -0,0 +1,113 @@ +.\" $OpenBSD: osiop.4,v 1.15 2022/02/17 12:24:08 jsg Exp $ +.\" $NetBSD: osiop.4,v 1.2 2001/09/22 01:44:55 wiz Exp $ +.\" +.\" Copyright (c) 2001 Izumi Tsutsui. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 17 2022 $ +.Dt OSIOP 4 +.Os +.Sh NAME +.Nm osiop +.Nd Symbios/NCR 53C710 SCSI driver +.Sh SYNOPSIS +.Cd "osiop* at gsc? irq 9 " Pq "hppa" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Tn Symbios/NCR +53C710 +.Tn SCSI +controller chip. +.Pp +The +.Tn Symbios/NCR +53C700 +.Tn SCSI +controller is handled by the +.Xr oosiop 4 +driver, while the +.Tn Symbios/NCR +53C8xx +.Tn PCI +.Tn SCSI +host adapters are handled by the +.Xr siop 4 +driver. +.Sh CONFIGURATION +The +.Nm +driver supports the following +.Sy flags +for use in +.Xr config 8 +files: +.Pp +.Bl -tag -compact -width "bits 8-15:" +.It bits 0-7 : +disable disconnect/reselect for the corresponding +.Tn SCSI +target +.It bits 8-15 : +disable synchronous negotiation for +.Tn SCSI +target +.It bits 16 : +disable DMA interrupts +.El +.Pp +.Qq Target +is synonymous with +.Tn SCSI +ID number. +.Pp +Note that +.Tn SCSI +tape drives should be allowed to perform disconnect/reselect or performance +will suffer. +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr oosiop 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr siop 4 , +.Xr st 4 , +.Xr uk 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx 1.6 . +.Pp +The original +.Tn NCR +53C710 +driver appeared in +.Nx 1.0 +amiga port, and +.An Izumi Tsutsui Aq Mt tsutsui@ceres.dti.ne.jp +modified the driver and made it machine-independent. diff --git a/static/openbsd/man4/otus.4 b/static/openbsd/man4/otus.4 new file mode 100644 index 00000000..f6234c2e --- /dev/null +++ b/static/openbsd/man4/otus.4 @@ -0,0 +1,177 @@ +.\" $OpenBSD: otus.4,v 1.38 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2009 Damien Bergamini +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt OTUS 4 +.Os +.Sh NAME +.Nm otus +.Nd Atheros USB IEEE 802.11a/b/g/n wireless network device +.Sh SYNOPSIS +.Cd "otus* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports USB 2.0 wireless network devices based on Atheros +Communications AR9001U chipset. +.Pp +The AR9001U chipset is made of an AR9170 MAC/Baseband +and an AR9101 (1T2R), AR9102 (2T2R) or AR9104 (dual-band 2T2R) +Radio. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs at least version 1.0 of the following firmware files, +which are loaded when an interface is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/otus-init +.It Pa /etc/firmware/otus-main +.El +.Pp +Although these firmware files are freely redistributable, their usage +is restricted. +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh HARDWARE +The following adapters should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It 3Com 3CRUSBN275 +.It Arcadyan WN7512 +.\" .It AVM FRITZ!WLAN USB Stick N +.It CACE AirPcap \&Nx +.It D-Link DWA-130 rev \&D1 +.It D-Link DWA-160 rev A1 +.It D-Link DWA-160 rev A2 +.It IO-Data WN-GDN/US2 +.It NEC Aterm WL300NU-G +.It Netgear WNDA3100 +.It Netgear WN111 v2 +.It Planex GW-US300 +.It SMC Networks SMCWUSB-N2 +.It TP-Link TL-WN821N v1, v2 +.It Ubiquiti SR71 USB +.It Unex DNUA-81 +.It Z-Com UB81 +.It Z-Com UB82 +.It ZyXEL NWD-271N +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig otus0 scan +.Pp +The following +.Xr hostname.if 5 +example configures otus0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "otus0: error N, could not read firmware ..." +For some reason, the driver was unable to read the microcode file from the +filesystem. +The file might be missing or corrupted. +.It "otus0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr +based on source code licensed under the ISC released in 2008 by Atheros +Communications for Linux. +.Sh CAVEATS +The AVM FRITZ!WLAN USB Stick N adapter is currently not supported. +.Pp +The +.Nm +driver does not support any of the 802.11n capabilities offered by the +AR9001U chipset. +Additional work is required in +.Xr ieee80211 9 +before those features can be supported. diff --git a/static/openbsd/man4/owctr.4 b/static/openbsd/man4/owctr.4 new file mode 100644 index 00000000..bcaf404a --- /dev/null +++ b/static/openbsd/man4/owctr.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: owctr.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2010 John L. Scarfone +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt OWCTR 4 +.Os +.Sh NAME +.Nm owctr +.Nd 1-Wire counter device +.Sh SYNOPSIS +.Cd "owctr* at onewire?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the externally triggered counters on the +DS2423 chip. +The supported chip contains a 4096-bit SRAM and four 32-bit counters. +The two externally triggered counters are accessible by the +.Xr sysctl 8 +interface. +.Pp +The following chips are supported by the driver: +.Pp +.Bl -bullet -compact -offset indent +.It +Maxim/Dallas DS2423 +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr onewire 4 , +.Xr owsbm 4 , +.Xr owtemp 4 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An John L. Scarfone Aq Mt john@scarfone.net . diff --git a/static/openbsd/man4/owid.4 b/static/openbsd/man4/owid.4 new file mode 100644 index 00000000..52ab6119 --- /dev/null +++ b/static/openbsd/man4/owid.4 @@ -0,0 +1,54 @@ +.\" $OpenBSD: owid.4,v 1.6 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt OWID 4 +.Os +.Sh NAME +.Nm owid +.Nd 1-Wire ID device +.Sh SYNOPSIS +.Cd "owid* at onewire?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the 1-Wire serial number family type device. +This device can't do anything except report its unique serial number. +The serial number is available through the +.Xr sysctl 8 +interface. +.Pp +The following chips are supported by the driver: +.Pp +.Bl -bullet -compact -offset indent +.It +Maxim/Dallas DS1990 +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr onewire 4 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/owsbm.4 b/static/openbsd/man4/owsbm.4 new file mode 100644 index 00000000..98e5b811 --- /dev/null +++ b/static/openbsd/man4/owsbm.4 @@ -0,0 +1,65 @@ +.\" $OpenBSD: owsbm.4,v 1.6 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2007 Aaron Linville +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt OWSBM 4 +.Os +.Sh NAME +.Nm owsbm +.Nd 1-Wire smart battery monitor device +.Sh SYNOPSIS +.Cd "owsbm* at onewire?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the 1-Wire smart battery monitor. +The sensor possesses a temperature sensor, an A/D converter for measuring both +battery voltage and current, a current accumulator of both incoming and +outgoing current, an elapsed time and 40 bytes of nonvolatile EEPROM. +.Pp +Only the three voltages (VDD, VAD, CR) and temperature are accessible by +the +.Xr sysctl 8 +interface. +.Pp +The following chips are supported by the driver: +.Pp +.Bl -bullet -compact -offset indent +.It +Maxim/Dallas DS2438 +.El +.Sh MEASURING CURRENT +The sensor does not measure current directly. +Instead it measures the voltage across the Rsens pins. +.Bd -literal -offset indent +I = Voltage CR / Rsens (where Rsens is in Ohms) +.Ed +.Sh SEE ALSO +.Xr intro 4 , +.Xr onewire 4 , +.Xr owtemp 4 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Aaron Linville Aq Mt aaron@linville.org . diff --git a/static/openbsd/man4/owtemp.4 b/static/openbsd/man4/owtemp.4 new file mode 100644 index 00000000..270c9fb8 --- /dev/null +++ b/static/openbsd/man4/owtemp.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: owtemp.4,v 1.8 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt OWTEMP 4 +.Os +.Sh NAME +.Nm owtemp +.Nd 1-Wire temperature device +.Sh SYNOPSIS +.Cd "owtemp* at onewire?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the 1-Wire temperature sensor. +The sensor possesses a single temperature value that can be accessed +through the +.Xr sysctl 8 +interface. +.Pp +The following chips are supported by the driver: +.Pp +.Bl -bullet -compact -offset indent +.It +Maxim/Dallas DS1820/DS18B20/DS18S20/DS1822 +.It +Maxim/Dallas DS1920 +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr onewire 4 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/pair.4 b/static/openbsd/man4/pair.4 new file mode 100644 index 00000000..c720a707 --- /dev/null +++ b/static/openbsd/man4/pair.4 @@ -0,0 +1,110 @@ +.\" $OpenBSD: pair.4,v 1.4 2015/10/30 10:48:55 reyk Exp $ +.\" +.\" Copyright (c) 2015 Reyk Floeter +.\" Copyright (c) 2009 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 30 2015 $ +.Dt PAIR 4 +.Os +.Sh NAME +.Nm pair +.Nd virtual Ethernet interface pair +.Sh SYNOPSIS +.Cd "pseudo-device pair" +.Sh DESCRIPTION +The +.Nm +interface simulates a normal Ethernet interface by encapsulating +standard network frames with an Ethernet header, specifically for use +in a pair of interfaces that are interconnected with each other. +.Pp +To use it, the administrator needs to create two +.Nm +interfaces and connect them; +the interfaces are +.Sq patched , +as would be done with physical network ports. +All packets that are sent on the first interface are received on the +second interface. +.Sh EXAMPLES +Set up a pair of interfaces where each of them is a member of a different +.Xr rdomain 4 : +.Bd -literal -offset indent +# ifconfig pair1 rdomain 1 10.1.1.1/24 up +# ifconfig pair2 rdomain 2 10.1.1.2/24 up +# ifconfig pair1 patch pair2 +# route -T 1 exec ping 10.1.1.2 +.Ed +.Pp +When adding multiple +.Nm +to multiple +.Xr bridge 4 +interfaces, it is possible to create a loop; +the system load will go up while it is busy sending packets from one +bridge to another and back. +By design, the driver does not prevent such loops by itself, but it is +possible to use the Spanning Tree Protocol (STP) to detect and remove +loops in the virtual network topology: +.Bd -literal -offset indent +# ifconfig pair0 up +# ifconfig pair1 rdomain 1 patch pair0 up +# ifconfig pair2 up +# ifconfig pair3 rdomain 1 patch pair2 up +# ifconfig bridge0 add pair0 add pair2 stp pair0 stp pair2 up +# ifconfig bridge1 add pair1 add pair3 stp pair1 stp pair3 up +.Ed +.Sh SEE ALSO +.Xr bridge 4 , +.Xr inet 4 , +.Xr inet6 4 , +.Xr rdomain 4 , +.Xr vether 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh HISTORY +The +.Nm +interface first appeared in +.Ox 5.9 . +.Sh AUTHORS +The +.Nm +driver is based on +.Xr vether 4 +by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . +It has been extended and turned into +.Nm +by +.An Reyk Floeter Aq Mt reyk@openbsd.org . +.Sh CAVEATS +Unlike +.Xr vether 4 , +the +.Nm +interface cannot be used as a stand-alone member in a +.Xr bridge 4 : +the link state remains down until it is connected to the second interface. +Any associated routes will be marked down until it is patched. +Use +.Xr vether 4 +as a bridge endpoint for routing purposes instead. +.Sh BUGS +Like +.Xr tun 4 , +the Ethernet address chosen will be partially random, and may +occasionally collide with another address. diff --git a/static/openbsd/man4/pcagpio.4 b/static/openbsd/man4/pcagpio.4 new file mode 100644 index 00000000..8247114c --- /dev/null +++ b/static/openbsd/man4/pcagpio.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: pcagpio.4,v 1.11 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PCAGPIO 4 +.Os +.Sh NAME +.Nm pcagpio +.Nd Philips PCA955[4567] GPIO controller +.Sh SYNOPSIS +.Cd "pcagpio* at iic?" +.Cd "gpio* at pcagpio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Philips PCA955[4567] GPIO controllers. +The PCA955[467] devices have 8 pins and the PCA9555 device has 16 pins +which can be configured as either inputs or outputs, and accessed +using +.Xr gpioctl 8 . +.\" Both values are made available through the +.\" .Xr sysctl 8 +.\" interface. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr iic 4 , +.Xr intro 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/pcaled.4 b/static/openbsd/man4/pcaled.4 new file mode 100644 index 00000000..ec7f7460 --- /dev/null +++ b/static/openbsd/man4/pcaled.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: pcaled.4,v 1.6 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PCALED 4 +.Os +.Sh NAME +.Nm pcaled +.Nd Philips PCA9532/PCA9552 GPIO LED dimmer +.Sh SYNOPSIS +.Cd "pcaled* at iic?" +.Cd "gpio* at pcaled?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Philips PCA9532 and PCA9552 GPIO controllers +which are specifically optimized to dim LEDs in 256 discrete steps. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr iic 4 , +.Xr intro 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@openbsd.org . diff --git a/static/openbsd/man4/pcamux.4 b/static/openbsd/man4/pcamux.4 new file mode 100644 index 00000000..a03729fb --- /dev/null +++ b/static/openbsd/man4/pcamux.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: pcamux.4,v 1.4 2020/11/13 10:14:53 patrick Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 13 2020 $ +.Dt PCAMUX 4 +.Os +.Sh NAME +.Nm pcamux +.Nd Philips PCA954[678] I2C switch/mux +.Sh SYNOPSIS +.Cd "pcamux* at iic?" +.Cd "iic* at pcamux?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Philips PCA954[68] I2C switch +and Philips PCA9547 I2C mux, which is used with the +.Xr iic 4 +framework. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/pcdisplay.4 b/static/openbsd/man4/pcdisplay.4 new file mode 100644 index 00000000..671ee270 --- /dev/null +++ b/static/openbsd/man4/pcdisplay.4 @@ -0,0 +1,64 @@ +.\" $OpenBSD: pcdisplay.4,v 1.11 2007/05/31 19:19:51 jmc Exp $ +.\" $NetBSD: pcdisplay.4,v 1.3 2000/05/13 15:22:17 mycroft Exp $ +.\" +.\" Copyright (c) 1999 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt PCDISPLAY 4 +.Os +.Sh NAME +.Nm pcdisplay +.Nd PC display adapter driver for wscons +.Sh SYNOPSIS +.Cd "pcdisplay0 at isa?" +.Cd "wsdisplay* at pcdisplay?" +.Cd "option PCDISPLAY_SOFTCURSOR" +.Sh DESCRIPTION +This driver supports PC display adapter hardware within the +.Xr wscons 4 +console framework. +It doesn't provide direct device driver entry points but makes its +functions available via the internal +.Xr wsdisplay 4 +interface. +.Pp +The +.Nm +driver is intended as a minimal +.Dq catch-all +driver for the different kinds of MDA, CGA and EGA compatible adapters. +It doesn't support multiple screens, nor colors or font loading. +.Pp +Supported kernel option(s): +.Bl -tag -width xxxx +.It Cd option PCDISPLAY_SOFTCURSOR +Use a large, non-blinking cursor generated by software. +The default is to use the cursor provided by the underlying display hardware. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr vga 4 , +.Xr wscons 4 diff --git a/static/openbsd/man4/pcfadc.4 b/static/openbsd/man4/pcfadc.4 new file mode 100644 index 00000000..3226a82c --- /dev/null +++ b/static/openbsd/man4/pcfadc.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: pcfadc.4,v 1.7 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Damien Miller +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PCFADC 4 +.Os +.Sh NAME +.Nm pcfadc +.Nd Philips PCF8591 temperature sensor +.Sh SYNOPSIS +.Cd "pcfadc* at iic?" +.Sh DESCRIPTION +The +.Nm +driver supports the PCF8591 I2C analog to digital converter, making +its readings available through a +.Xr sysctl 8 +interface. +.Pp +The driver reads up to four A/D lines configured as temperature inputs. +Sensor names, type and calibration information are read from OpenFirmware. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Damien Miller Aq Mt djm@openbsd.org . diff --git a/static/openbsd/man4/pcfiic.4 b/static/openbsd/man4/pcfiic.4 new file mode 100644 index 00000000..dd300ce8 --- /dev/null +++ b/static/openbsd/man4/pcfiic.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: pcfiic.4,v 1.5 2020/06/18 20:39:28 jmc Exp $ +.\" +.\" Copyright (c) 2006 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2020 $ +.Dt PCFIIC 4 +.Os +.Sh NAME +.Nm pcfiic +.Nd Philips PCF8584 I2C controller +.Sh SYNOPSIS +.Cd "# sparc64" +.Cd "pcfiic* at ebus?" +.Cd "iic* at pcfiic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Philips PCF8584 I2C controller to be +used with the +.Xr iic 4 +framework. +.Sh SEE ALSO +.Xr ebus 4 , +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/pcfrtc.4 b/static/openbsd/man4/pcfrtc.4 new file mode 100644 index 00000000..5a13aa39 --- /dev/null +++ b/static/openbsd/man4/pcfrtc.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: pcfrtc.4,v 1.3 2018/11/20 09:06:08 reyk Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt +.\" Copyright (c) 2016 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 20 2018 $ +.Dt PCFRTC 4 +.Os +.Sh NAME +.Nm pcfrtc +.Nd NXP PCF8523 real-time clock +.Sh SYNOPSIS +.Cd "pcfrtc* at iic? addr 0x68" +.Sh DESCRIPTION +The +.Nm +driver provides support for the NXP PCF8523 real-time clock chip. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/pchb.4 b/static/openbsd/man4/pchb.4 new file mode 100644 index 00000000..a3c83318 --- /dev/null +++ b/static/openbsd/man4/pchb.4 @@ -0,0 +1,62 @@ +.\" $OpenBSD: pchb.4,v 1.18 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Michael Shalayeff, 2000. Public Domain. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PCHB 4 +.Os +.Sh NAME +.Nm pchb +.Nd PCI-Host Bridge +.Sh SYNOPSIS +.Cd "pchb* at pci?" +.Cd "pci* at pchb?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI-Host adapter-specific functions. +Support is provided for the following devices: +.Bl -tag -width Ds -offset indent +.It i450 PCIset (Orion) +Supports additional PCI buses. +.It Reliance Computer ROSB4, CNB20HE, CNB20LE +Supports additional PCI buses. +.It i82424ZX (Saturn) +Disables CPU-PCI write posting. +.It i82443BX +Provides workaround for the following errata: +"An incorrect address may be driven on the +DRAM bus, resulting in memory data being +fetched from the wrong location." +.It i82810/810E, i82815/815E, i82820, i82840 +Supports the random numbers generator, +supplying random bytes from the system's thermal noise. +Driven by periodic checks for available data from the generator, +it supplies entropy to the +.Xr random 4 +driver for common usage. +.El +.Pp +On amd64 and i386 systems, most PCI devices of class +.Nm Bridge +and sub-class +.Nm Bridge Host +are supported just as PCI attachment points. +A few other system control devices not listed here are supported by +.Nm . +.Pp +The macppc port supports several Apple and Motorola bridges. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr random 4 +.Sh HISTORY +Random number generator support first appeared in +.Ox 2.7 . +.Sh AUTHORS +Support for true RNG present on i82810 chips was added by +.An Michael Shalayeff Aq Mt mickey@openbsd.org . +.Sh BUGS +Real RNG probe should fix the PCI scanning loop so it would find the Firmware +Hub (i82802) which actually contains the RNG device and +probe it as a real PCI device (i.e., common PCI registers are there). diff --git a/static/openbsd/man4/pchgpio.4 b/static/openbsd/man4/pchgpio.4 new file mode 100644 index 00000000..0d74fc81 --- /dev/null +++ b/static/openbsd/man4/pchgpio.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: pchgpio.4,v 1.1 2020/11/15 17:44:06 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 15 2020 $ +.Dt PCHGPIO 4 +.Os +.Sh NAME +.Nm pchgpio +.Nd Intel PCH GPIO controller +.Sh SYNOPSIS +.Cd "pchgpio* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO controllers found on Intel PCHs. +It does not provide direct device driver entry points but makes its +functions available to +.Xr acpi 4 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org +and +.An James Hastings . diff --git a/static/openbsd/man4/pchtemp.4 b/static/openbsd/man4/pchtemp.4 new file mode 100644 index 00000000..eb06d65d --- /dev/null +++ b/static/openbsd/man4/pchtemp.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: pchtemp.4,v 1.4 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2015 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt PCHTEMP 4 +.Os +.Sh NAME +.Nm pchtemp +.Nd Intel PCH temperature sensor +.Sh SYNOPSIS +.Cd "pchtemp* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor in the Intel X99, +C610 series, 9 series and 100 series platform controller hub (PCH). +.Pp +These sensors provide 0.5 degC resolution. +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +.Sh CAVEATS +The temperature sensor only attached if it has been enabled by the +BIOS. diff --git a/static/openbsd/man4/pci.4 b/static/openbsd/man4/pci.4 new file mode 100644 index 00000000..7a91b22e --- /dev/null +++ b/static/openbsd/man4/pci.4 @@ -0,0 +1,627 @@ +.\" $OpenBSD: pci.4,v 1.414 2025/12/30 23:13:22 jsg Exp $ +.\" $NetBSD: pci.4,v 1.29 2000/04/01 00:32:23 tsarna Exp $ +.\" +.\" Copyright (c) 2000 Theo de Raadt. All rights reserved. +.\" Copyright (c) 1997 Jason R. Thorpe. All rights reserved. +.\" Copyright (c) 1997 Jonathan Stone +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgements: +.\" This product includes software developed by Jonathan Stone +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 30 2025 $ +.Dt PCI 4 +.Os +.Sh NAME +.Nm pci +.Nd introduction to PCI bus support +.Sh SYNOPSIS +.Cd "# alpha" +.Cd "pci* at apecs?" +.Cd "pci* at cia?" +.Cd "pci* at irongate?" +.Cd "pci* at lca?" +.Cd "pci* at tsp?" +.Cd "pci* at mcpcia?" +.Pp +.Cd "# amd64, i386" +.Cd "pci* at mainbus0" +.Pp +.Cd "# arm64" +.Cd "pci* at acpipci?" +.Cd "pci* at bcmpcie?" +.Cd "pci* at dwpcie?" +.Cd "pci* at mvkpcie?" +.Cd "pci* at pciecam?" +.Cd "pci* at rkpcie?" +.Pp +.Cd "# armv7" +.Cd "pci* at mvpcie?" +.Cd "pci* at pciecam?" +.Pp +.Cd "# hppa" +.Cd "pci* at dino?" +.Cd "pci* at elroy?" +.Pp +.Cd "# landisk" +.Cd "pci* at shpcic?" +.Pp +.Cd "# loongson" +.Cd "pci* at bonito?" +.Cd "pci* at htb?" +.Pp +.Cd "# macppc" +.Cd "pci* at mpcpcibr?" +.Cd "pci* at ht?" +.Cd "pci* at hpb?" +.Pp +.Cd "# octeon" +.Cd "pci* at octpcie?" +.Pp +.Cd "# riscv64" +.Cd "pci* at dwpcie?" +.Cd "pci* at pciecam?" +.Pp +.Cd "# sparc64" +.Cd "pci* at psycho?" +.Cd "pci* at schizo?" +.Cd "pci* at pyro?" +.Cd "pci* at vpci?" +.Pp +.Cd "# all architectures" +.Cd "pci* at pchb?" +.Cd "pci* at ppb?" +.Sh DESCRIPTION +The system includes a machine-independent PCI bus subsystem and +several machine-independent PCI device drivers. +.Pp +Note that interrupt mappings on the i386 may require that you configure +your BIOS to reserve sufficient interrupts as "PCI/ISAPnP" so that there +are sufficient interrupts remaining to configure the discovered PCI +devices. +For more information, see +.Xr pcibios 4 . +.Pp +.Ox +provides support for the following devices. +Note that not all architectures support all devices. +.Ss SCSI host adapters +.Bl -tag -width 10n -offset ind -compact +.It Xr adv 4 , Xr adw 4 +AdvanSys PCI SCSI interface +.It Xr ahc 4 +Adaptec VL/EISA/PCI SCSI interface +.It Xr ahd 4 +Adaptec PCI/PCI-X AIC79xx-based Ultra320 SCSI interface +.It Xr iha 4 +Initio INIC-940/950 based PCI SCSI interface +.It Xr mpi 4 +LSI Logic Fusion-MPT Message Passing Interface +.It Xr mpii 4 +LSI Logic Fusion-MPT Message Passing Interface II +.It Xr nvme 4 +Non-Volatile Memory Host Controller Interface +.It Xr pcscp 4 +Advanced Micro Devices Am53c974 PCscsi-PCI SCSI interface +.It Xr qla 4 +QLogic ISP2100/2200/2300 Fibre Channel controller +.It Xr qle 4 +QLogic ISP2400/2500 Fibre Channel controller +.It Xr qlw 4 +QLogic ISP1000/1020/1x40/1x80/1x160 SCSI controller +.It Xr siop 4 +LSI/Symbios Logic/NCR 53c8xx SCSI interface +.It Xr trm 4 +TRM-S1040 based PCI SCSI interface +.It Xr ufshci 4 +Universal Flash Storage Host Controller Interface +.It Xr vmwpvs 4 +VMware Paravirtual SCSI +.El +.Ss IDE disk controllers +.Bl -tag -width "kauaiata(4)" -offset ind -compact +.It Xr ahci 4 +Advanced Host Controller Interface for Serial ATA +.It Xr jmb 4 +JMicron JMB36x SATA II and PATA Host Controller +.It Xr kauaiata 4 +ATA100 HD controller on PCI bus +.It Xr pciide 4 +PCI IDE controller driver +.It Xr sili 4 +Silicon Image 3124/3132/3531 SATA controller +.El +.Ss RAID and cache controllers +.Bl -tag -width 10n -offset ind -compact +.It Xr aac 4 +Adaptec SAS/SATA/SCSI RAID controller +.It Xr ami 4 +American Megatrends Inc. MegaRAID PATA/SATA/SCSI RAID controller +.It Xr arc 4 +Areca Technology Corporation SAS/SATA RAID controller +.It Xr cac 4 +Compaq Smart Array 2/3/4 SCSI RAID controller +.It Xr ciss 4 +Compaq Smart Array SAS/SATA/SCSI RAID controller +.It Xr gdt 4 +ICP-Vortex and Intel GDT SATA/SCSI RAID controller +.It Xr ips 4 +IBM SATA/SCSI ServeRAID controller +.It Xr mfi 4 +LSI Logic & Dell MegaRAID SAS RAID controller +.It Xr mfii 4 +LSI Logic MegaRAID SAS Fusion RAID controller +.It Xr twe 4 +3ware 5000/6000/7000/8000 series PATA/SATA RAID controller +.El +.Ss Wired network interfaces +.Bl -tag -width 10n -offset ind -compact +.It Xr age 4 +Attansic L1 10/100/1Gb Ethernet device +.It Xr alc 4 +Atheros AR813x/AR815x/AR816x/AR817x 10/100/1Gb Ethernet device +.It Xr ale 4 +Atheros AR8121/AR8113/AR8114 10/100/1Gb Ethernet device +.It Xr aq 4 +Aquantia AQC1xx 1Gb/2.5Gb/5Gb/10Gb PCIe Ethernet device +.It Xr bce 4 +Broadcom BCM4401 10/100 Ethernet device +.It Xr bge 4 +Broadcom BCM57xx/BCM590x 10/100/1Gb Ethernet device +.It Xr bnx 4 +Broadcom NetXtreme II 10/100/1Gb Ethernet device +.It Xr bnxt 4 +Broadcom NetXtreme-C/E 10Gb/25Gb/40Gb/50Gb Ethernet device +.It Xr cas 4 +Sun Cassini 10/100/1Gb Ethernet device +.It Xr dc 4 +DEC/Intel 21140/21142/21143/21145 and clones 10/100 Ethernet device +.It Xr de 4 +DEC DC21x4x (Tulip) 10/100 Ethernet device +.It Xr dwqe 4 +Synopsys DesignWare Ethernet Quality-of-Service Controller +.It Xr em 4 +Intel PRO/1000 10/100/1Gb Ethernet device +.It Xr ep 4 +3Com EtherLink III and Fast EtherLink III 10/100 Ethernet device +.It Xr epic 4 +SMC 83C170 (EPIC/100) 10/100 Ethernet device +.It Xr et 4 +Agere/LSI ET1310 10/100/1Gb Ethernet device +.It Xr fxp 4 +Intel EtherExpress PRO/100 10/100 Ethernet device +.It Xr gem 4 +GEM 10/100/1Gb Ethernet device +.It Xr hme 4 +Sun Happy Meal 10/100 Ethernet device +.It Xr iavf 4 +Intel Ethernet adaptive virtual function device +.It Xr ice 4 +Intel Ethernet 800 series PCI Express 1Gb/10Gb/25Gb/50Gb/100Gb Ethernet device +.It Xr igc 4 +Intel I225/I226 1Gb/2.5Gb Ethernet device +.It Xr ix 4 +Intel 82598/82599/X540/X550 PCI Express 100/1Gb/10Gb Ethernet device +.It Xr ixgb 4 +Intel PRO/10GbE 10Gb Ethernet device +.It Xr ixl 4 +Intel Ethernet 700 series Ethernet device +.It Xr ixv 4 +Intel 10Gb Ethernet virtual function device +.It Xr jme 4 +JMicron JMC25x/JMC26x 10/100/1Gb Ethernet device +.It Xr lge 4 +Level 1 LXT1001 NetCellerator PCI 1Gb Ethernet device +.It Xr lii 4 +Attansic L2 10/100 Ethernet device +.It Xr mcx 4 +Mellanox 5th generation Ethernet device +.It Xr msk 4 +Marvell Yukon-2 10/100/1Gb Ethernet device +.It Xr mtd 4 +Myson Technology MTD800/MTD803/MTD891 10/100/1Gb Ethernet device +.It Xr myx 4 +Myricom Myri-10G PCI Express 10Gb Ethernet device +.It Xr ne 4 +NE2000 and compatible 10/100 Ethernet device +.It Xr nep 4 +Sun Neptune 10Gb Ethernet device +.It Xr nfe 4 +NVIDIA nForce MCP 10/100/1Gb Ethernet device +.It Xr ngbe 4 +WangXun WX1860 PCI Express 10/100/1Gb Ethernet device +.It Xr nge 4 +National Semiconductor PCI 10/100/1Gb Ethernet device +.It Xr oce 4 +Emulex OneConnect 10Gb Ethernet device +.It Xr pcn 4 +AMD PCnet-PCI 10/100 Ethernet device +.It Xr re 4 +Realtek 8139C+/8169/816xS/811xS/8168/810xE 10/100/1Gb Ethernet device +.It Xr rge 4 +Realtek 8125/8126/8127 PCI Express 10/100/1Gb/2.5Gb/5Gb/10Gb Ethernet device +.It Xr rl 4 +Realtek 8129/8139 10/100 Ethernet device +.It Xr se 4 +SiS 190/191 10/100/1Gb Ethernet device +.It Xr sf 4 +Adaptec AIC-6915 "Starfire" PCI 10/100 Ethernet device +.It Xr sis 4 +SiS 900, SiS 7016, and NS DP83815/6 10/100 Ethernet device +.It Xr sk 4 +SysKonnect XMAC II and Marvell Yukon 10/100/1Gb Ethernet device +.It Xr ste 4 +Sundance Technologies ST201 10/100 Ethernet device +.It Xr stge 4 +Sundance/Tamarack TC9021 1Gb Ethernet device +.It Xr tht 4 +Tehuti Networks 10Gb Ethernet device +.It Xr ti 4 +Alteon Networks Tigon I and II 1Gb Ethernet device +.It Xr tl 4 +Texas Instruments ThunderLAN 10/100 Ethernet device +.It Xr txp 4 +3Com 3XP Typhoon/Sidewinder (3CR990) 10/100 Ethernet device +.It Xr vge 4 +VIA Velocity 10/100/1Gb Ethernet device +.It Xr vic 4 +VMware VMXnet Virtual Interface Controller device +.It Xr vmx 4 +VMware VMXNET3 Virtual Interface Controller device +.It Xr vr 4 +VIA Rhine I/II/III 10/100 Ethernet device +.It Xr vte 4 +RDC R6040 10/100 Ethernet device +.It Xr wb 4 +Winbond W89C840F 10/100 Ethernet device +.It Xr xge 4 +Neterion Xframe/Xframe II 10Gb Ethernet device +.It Xr xl 4 +3Com EtherLink XL and Fast EtherLink XL 10/100 Ethernet device +.El +.Ss Wireless network interfaces +.Bl -tag -width 10n -offset ind -compact +.It Xr acx 4 +TI ACX100/ACX111 IEEE 802.11a/b/g wireless network device +.It Xr an 4 +Aironet Communications 4500/4800 IEEE 802.11FH/b wireless network device +.It Xr ath 4 +Atheros IEEE 802.11a/b/g wireless network device with GPIO +.It Xr athn 4 +Atheros IEEE 802.11a/b/g/n wireless network device +.It Xr atw 4 +ADMtek ADM8211 IEEE 802.11b wireless network device +.It Xr bwfm 4 +Broadcom and Cypress IEEE 802.11a/ac/ax/b/g/n wireless network device +.It Xr bwi 4 +Broadcom AirForce IEEE 802.11b/g wireless network device +.It Xr ipw 4 +Intel PRO/Wireless 2100 IEEE 802.11b wireless network device +.It Xr iwi 4 +Intel +PRO/Wireless 2200BG/2225BG/2915ABG IEEE 802.11a/b/g wireless network device +.It Xr iwn 4 +Intel WiFi Link and Centrino IEEE 802.11a/b/g/n wireless network device +.It Xr iwm 4 +Intel 7000/8000/9000 IEEE 802.11a/ac/b/g/n wireless network device +.It Xr iwx 4 +Intel AX200/AX201/AX210/AX211 IEEE 802.11a/ac/ax/b/g/n wireless network device +.It Xr malo 4 +Marvell Libertas IEEE 802.11b/g wireless network device +.It Xr pgt 4 +Conexant/Intersil Prism GT Full-MAC IEEE 802.11a/b/g wireless network device +.It Xr qwx 4 +Qualcomm IEEE 802.11a/ac/ax/b/g/n wireless network device +.It Xr ral 4 +Ralink Technology/MediaTek IEEE 802.11a/b/g/n wireless network device +.It Xr rtw 4 +Realtek RTL8180L IEEE 802.11b wireless network device +.It Xr rtwn 4 +Realtek RTL8188CE/RTL8188EE/RTL8192CE/RTL8723AE PCIe IEEE 802.11b/g/n wireless +network device +.It Xr wi 4 +WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b wireless network +device +.It Xr wpi 4 +Intel PRO/Wireless 3945ABG IEEE 802.11a/b/g wireless network device +.El +.Ss Cryptography accelerators +.Bl -tag -width 10n -offset ind -compact +.It Xr ccp 4 +AMD cryptographic co-processor +.It Xr glxsb 4 +Geode LX Security Block crypto accelerator +.El +.Ss Serial interfaces +.Bl -tag -width 10n -offset ind -compact +.It Xr cy 4 +Cyclades Cyclom-4Y, -8Y, and -16Y asynchronous serial communications devices +.It Xr cz 4 +Cyclades-Z series multi-port serial adapter device +.It Xr puc 4 +PCI +.Dq universal +communications card driver +.El +.Ss Display adapters +.Bl -tag -width 11n -offset ind -compact +.It Xr astfb 4 +Aspeed BMC frame buffer +.It Xr gfxp 4 +accelerated color frame buffer +.It Xr ifb 4 +inextricable frame buffer +.It Xr machfb 4 +accelerated color frame buffer +.It Xr radeonfb 4 +accelerated color frame buffer +.It Xr raptor 4 +accelerated color frame buffer +.It Xr sisfb 4 +SiS 315 Pro frame buffer +.It Xr smfb 4 +Silicon Motion frame buffer +.It Xr sti 4 +HP Standard Text Interface +.It Xr tga 4 +DECchip 21030 (TGA) graphics driver +.It Xr vga 4 +VGA graphics cards +.It Xr vgafb 4 +VGA frame buffer +.El +.Ss Audio devices +.Bl -tag -width 10n -offset ind -compact +.It Xr auacer 4 +Acer Labs I/O Controller Hub integrated AC'97 audio device +.It Xr auglx 4 +AMD Geode LX CS5536 integrated AC'97 audio device +.It Xr auich 4 +Intel ICH integrated AC'97 audio device +.It Xr auixp 4 +ATI SB200/SB300/SB400/SB600 integrated AC'97 audio device +.It Xr autri 4 +Trident 4DWAVE-DX/NX, SiS 7018, ALi M5451 audio device +.It Xr auvia 4 +VIA VT82C686A/VT8233/VT8235/VT8237 integrated AC'97 audio device +.It Xr azalia 4 +generic High Definition Audio device +.It Xr clcs 4 +Cirrus Logic CS4280/CS4610/CS4615 audio device +.It Xr clct 4 +Cirrus Logic CS4281 audio device +.It Xr cmpci 4 +C-Media CMI8338/CMI8738/CMI8768 PCI audio device +.It Xr eap 4 +Ensoniq AudioPCI audio device +.It Xr emu 4 +Creative Labs SBLive!, PCI 512, and Audigy audio device +.It Xr envy 4 +VIA Envy24 audio device +.It Xr esa 4 +ESS Technology Allegro-1/Maestro-3 family audio device +.It Xr eso 4 +ESS Technology Solo-1 PCI AudioDrive audio device +.It Xr fms 4 +Forte Media FM801 audio device +.It Xr maestro 4 +ESS Maestro 1 and 2 audio device +.It Xr neo 4 +NeoMagic 256AV/ZX audio device +.It Xr sv 4 +S3 SonicVibes audio device +.It Xr yds 4 +Yamaha DS-XG audio device +.El +.Ss Time receiver devices +.Bl -tag -width 10n -offset ind -compact +.It Xr mbg 4 +Meinberg Funkuhren timedelta sensor +.El +.Ss Radio receiver devices +.Bl -tag -width 10n -offset ind -compact +.It Xr fms 4 +Forte Media FM801 audio device +.El +.Ss Hardware Sensors +.Bl -tag -width 10n -offset ind -compact +.It Xr berkwdt 4 +Berkshire Products watchdog timer device +.It Xr geodesc 4 +Geode SC1100/SCx200 IAOC watchdog timer device +.It Xr ichwdt 4 +Intel 6300ESB ICH watchdog timer device +.It Xr itherm 4 +Intel 3400 temperature sensor +.It Xr kate 4 +AMD K8 temperature sensor +.It Xr km 4 +AMD K10 temperature sensor +.It Xr ksmn 4 +AMD K17 temperature sensor over SMN +.It Xr pchtemp 4 +Intel PCH temperature sensor +.It Xr pwdog 4 +Quancom PWDOG1 watchdog timer device +.It Xr viapm 4 +VIA SMBus controller and VIA VT82C686A/VT8231 hardware monitor +.It Xr wdt 4 +ICS PCI-WDT500/501 watchdog timer device +.El +.Ss Miscellaneous devices +.Bl -tag -width "amdpcib(4)" -offset ind -compact +.It Xr alipm 4 +Acer Labs M7101 SMBus controller +.It Xr amas 4 +AMD memory address map +.It Xr amdiic 4 +AMD-8111 SMBus controller +.It Xr amdpcib 4 +AMD-8111 series LPC bridge and timecounter +.It Xr amdpm 4 +AMD-756/766/768/8111 Power Management and SMBus controller +.It Xr bktr 4 +Brooktree Bt848/849/878/879 PCI TV tuners and video capture boards +.It Xr cbb 4 +PCI Yenta compatible CardBus bridges +.It Xr drm 4 +Direct Rendering Manager device +.It Xr dwiic 4 +Synopsys DesignWare I2C controller +.It Xr ehci 4 +USB Enhanced Host Controller Interface +.It Xr gcu 4 +Intel EP80579 Global Configuration Unit +.It Xr glxpcib 4 +CS5536 PCI-ISA Bridge with timecounter, watchdog timer, and GPIO +.It Xr gscpcib 4 +National Semiconductor Geode SC1100 PCI-ISA bridge with GPIO +.It Xr gscpm 4 +National Semiconductor Geode SC1100 SMI/ACPI module +.It Xr hpb 4 +HyperTransport-PCI bridge +.It Xr ichiic 4 +Intel ICH SMBus controller +.It Xr ichpcib 4 +Intel ICHx/ICHx-M LPC bridges +.It Xr iosf 4 +Intel OnChip System Fabric device +.It Xr nviic 4 +NVIDIA nForce2/3/4 SMBus controller +.It Xr ohci 4 +USB Open Host Controller Interface +.It Xr pcib 4 +PCI-ISA bridge +.It Xr pcic 4 +PCI PCMCIA controllers, including the Cirrus Logic GD6729 +.It Xr piixpm 4 +Intel PIIX SMBus controller +.It Xr ppb 4 +PCI-PCI bridge +.It Xr rtsx 4 +Realtek SD card reader +.It Xr sbbc 4 +PCI BootBus Controller +.It Xr sdhc 4 +SD Host Controller +.It Xr ssio 4 +National Semiconductor PC87560 Legacy IO +.It Xr tcpcib 4 +Intel Atom E600 series LPC bridge and watchdog timer +.It Xr uhci 4 +USB Universal Host Controller Interface +.It Xr viapm 4 +VIA SMBus controller +.It Xr virtio 4 +VirtIO support driver +.It Xr voyager 4 +Silicon Motion Mobile Multimedia Companion Chip +.It Xr xspd 4 +XenSource Platform Device driver +.El +.Sh IOCTLS +If the kernel is compiled with the +.Va USER_PCICONF +kernel option, the following +.Xr ioctl 2 +calls are supported by the +.Nm +driver. +They are defined in the header file +.In sys/pciio.h . +.Bl -tag -width Ds +.It PCIOCREAD Fa "struct pci_io *" +This +.Xr ioctl 2 +reads the PCI configuration registers specified by the passed-in +.Va pci_io +structure. +The +.Va pci_io +structure consists of the following fields: +.Bl -tag -width pi_width +.It pi_sel +A +.Va pcisel +structure which specifies the bus, slot and function the user would like to +query. +.It pi_reg +The PCI configuration register the user would like to access. +.It pi_width +The width, in bytes, of the data the user would like to read. +This value can be only 4. +.It pi_data +The data returned by the kernel. +.El +.It PCIOCWRITE Fa "struct pci_io *" +This +.Xr ioctl 2 +allows users to write to the PCI device specified in the passed-in +.Va pci_io +structure. +The +.Va pci_io +structure is described above. +The limitations on data width described for +reading registers, above, also apply to writing PCI configuration registers. +.It PCIOCGETROM Fa "struct pci_rom *" +This +.Xr ioctl 2 +allows users to read the contents of the PCI ROM specified in the passed-in +.Va pci_rom +structure. +The +.Va pci_rom +structure consists of the following fields: +.Bl -tag -width pr_romlen +.It pr_sel +A +.Va pcisel +structure which specifies the bus, slot and function the user would like to +query. +.It pr_romlen +Size of the buffer to store the contents of the ROM. +Upon return, this field will contain the size of the ROM +.It pr_rom +The address of the buffer to store the contents of the ROM. +.El +.Pp +If the ROM is larger than the specified buffer size, +.Dv ENOMEM +will be returned. +.El +.Sh FILES +.Bl -tag -width /dev/pci* -compact +.It Pa /dev/pci* +Character device for the +.Nm +driver. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr pcidump 8 +.Sh HISTORY +The machine-independent PCI subsystem appeared in +.Ox 1.2 . diff --git a/static/openbsd/man4/pcib.4 b/static/openbsd/man4/pcib.4 new file mode 100644 index 00000000..e7a9dac3 --- /dev/null +++ b/static/openbsd/man4/pcib.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: pcib.4,v 1.4 2007/05/31 19:19:51 jmc Exp $ +.\" +.\" Copyright (c) 2004 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt PCIB 4 +.Os +.Sh NAME +.Nm pcib +.Nd PCI-ISA bridge +.Sh SYNOPSIS +.Cd "pcib* at pci?" +.Cd "isa* at pcib?" +.Sh DESCRIPTION +The +.Nm +driver supports generic +.Tn PCI-ISA +bridges. +These devices are largely transparent and provide no user accessible +entry points. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr pci 4 diff --git a/static/openbsd/man4/pciide.4 b/static/openbsd/man4/pciide.4 new file mode 100644 index 00000000..40f33fb9 --- /dev/null +++ b/static/openbsd/man4/pciide.4 @@ -0,0 +1,188 @@ +.\" $OpenBSD: pciide.4,v 1.89 2014/07/13 23:36:09 sasano Exp $ +.\" $NetBSD: pciide.4,v 1.8 1999/03/16 01:19:17 garbled Exp $ +.\" +.\" Copyright (c) 1998 Manuel Bouyer. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by the University of +.\" California, Berkeley and its contributors. +.\" 4. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 13 2014 $ +.Dt PCIIDE 4 +.Os +.Sh NAME +.Nm pciide +.Nd PCI IDE controller driver +.Sh SYNOPSIS +.Cd "pciide* at pci? flags 0x0000" +.Cd "pciide* at jmb? flags 0x0000" +.Pp +.Cd "option PCIIDE_AMD756_ENABLEDMA" +.Cd "option PCIIDE_CMD064x_DISABLE" +.Cd "option PCIIDE_CMD0646U_ENABLEUDMA" +.Pp +.Cd "atapiscsi* at pciide? flags 0x0000" +.Cd "wd* at pciide? flags 0x0000" +.Sh DESCRIPTION +The +.Nm +driver supports the PCI IDE controllers as specified in the +"PCI IDE controller specification, revision 1.0" draft, as well as the +Serial ATA controllers working either in parallel ATA compatibility mode or +in native serial mode. +It provides the core functions for the +.Xr wd 4 +and +.Xr atapiscsi 4 +drivers. +This driver includes specific, enhanced support for the CMD Tech +PCI0640 controller and IDE DMA/UltraDMA support for the following PCI IDE +controllers: +.Pp +.Bl -bullet -compact -offset indent +.It +Acard ATP850U, ATP860, ATP860-A, ATP865-A, ATP865-R +.It +Acer Labs M5229 +.It +Adaptec AAR-1210SA +.It +AMD 756, 766, 768, 8111, Hudson-2 +.It +ATI SB200, SB300, SB400, SB600, SB700 (IDE only) +.It +CMD Tech PCI0640, PCI0643, PCI0646, PCI0648, PCI0649, PCI0680 +.It +Contaq Microsystems/Cypress CY82C693 +.It +HighPoint HPT366, HPT370, HPT372, HPT302, HPT371, HPT374 +.It +Intel 6300ESB/6321ESB +.It +Intel 82801 +(ICH/ICH0/ICH2/ICH3/ICH4/ICH4-M/ICH5/ICH5R/\& +ICH6/ICH6M/ICH6R/ICH7/ICH7M/ICH7R/ICH7M DH/ICH8/ICH8M/\& +ICH9/ICH9M) +.It +Intel PIIX, PIIX3, and PIIX4 +.It +ITE IT8211F, IT8212F +.It +JMicron JMB361/3/5/6/8 +.It +National Semiconductor PC87415 +.It +National Semiconductor SCx200 (found on SC1100 SoC) +.It +NVIDIA nForce/nForce2/nForce2-400/nForce3/nForce3-250/nForce4, +MCP04/MCP51/MCP55/MCP61/MCP65/MCP67/MCP73/MCP77/MCP89 +.It +Phison PS5000 +.It +Promise PDC20246, PDC20262, PDC20265, PDC20267, PDC20268, PDC20268R, +PDC20269, PDC20271, PDC20275, PDC20276, PDC20277, PDC20318, PDC20319, +PDC20371, PDC20375, PDC20376, PDC20377, PDC20378, PDC20379, PDC20571, +PDC20575, PDC20579, PDC20771, PDC20775, PDC40518, PDC40519, PDC40718, +PDC40719, PDC40779 +.It +RDC R1012 +.It +ServerWorks SATA, OSB4, CSB5, CSB6 (including support for the third channel) +.It +Silicon Image SiI3112, SiI3512, SiI3114 +.It +Silicon Integrated System 180, 181, 5513 (5597/5598), 540, 550, +620, 630, 630S, 633, 635, 640, 645, 645DX, 648, 650, 651, 652, 655, 658, 661, +730, 733, 735, 740, 745, 746, 748, 750, 751, 752, 755, 760, 962, 963 +.It +VIA Technologies CX700, VT82C586/A/B, VT82C596A/B, VT82C686A/B, VT8231, VT8366, +VT8233, VT8235, VT8237, VT8237A/S, VT8251, VT6410, VT6415, VX700, VX855, VX900 +.El +.Pp +Some of these controllers are only available in multifunction PCI chips. +.Pp +The +.Li 0x0001 +flag forces the +.Nm +driver to use DMA when there is no explicit DMA mode setting support for +the controller but DMA is present. +If the BIOS didn't configure the controller properly, this can +cause a machine hang. +.Sh SEE ALSO +.Xr atapiscsi 4 , +.Xr intro 4 , +.Xr jmb 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr wd 4 , +.Xr wdc 4 +.Sh BUGS +There's no way to know reliably if a CMD064x controller is enabled or not. +If the driver finds a PCI064x, it will assume it is enabled unless +.Dv PCIIDE_CMD064x_DISABLE +is specified in the kernel config file. +This will be a problem only if the controller has been disabled in the BIOS +and another controller has been installed which uses the ISA legacy I/O ports +and interrupts. +.Pp +The CMD0646U is reportedly unable to operate properly in UltraDMA mode. +UltraDMA will not be enabled on this controller unless +.Dv PCIIDE_CMD0646U_ENABLEUDMA +is specified in the kernel config file. +.Pp +For proper operation of UltraDMA 3 and higher modes +a 40-pin, 80-conductor cable must be used. +On some controllers, the +.Nm +driver can probe the chip and see if it +detects that an 80-conductor or 40-conductor cable was used. +If not, it will down-grade to UltraDMA 2 mode. +On other controllers, no such capability exists, and the driver assumes +you are using an 80-conductor cable. +If you are getting errors about +corrupted data, check to make sure you are using the correct cable. +An 80-conductor cable is recommended for any IDE installation, not just +ones using faster UltraDMA modes, because it will decrease electrical +noise and increase data reliability. +.Pp +The AMD756 chip revision D2 has a bug affecting DMA (but not Ultra-DMA) +modes. +The workaround documented by AMD is to not use DMA on any drive which +does not support Ultra-DMA modes. +This does not appear to be necessary on all drives, the +PCIIDE_AMD756_ENABLEDMA option can be used to force multiword DMA +on the buggy revisions. +Multiword DMA can eventually be disabled on a per-drive basis with config +flags, see +.Xr wd 4 . +The bug, if triggered, will cause a total system hang. +.Pp +The timings used for the PIO and DMA modes for controllers listed above +are for a PCI bus running at 30 or 33 MHz. +These timings will work on a slower bus, +but they may cause errors on an over-clocked bus. diff --git a/static/openbsd/man4/pckbc.4 b/static/openbsd/man4/pckbc.4 new file mode 100644 index 00000000..36445d56 --- /dev/null +++ b/static/openbsd/man4/pckbc.4 @@ -0,0 +1,79 @@ +.\" $OpenBSD: pckbc.4,v 1.19 2025/02/10 11:41:19 miod Exp $ +.\" $NetBSD: pckbc.4,v 1.2 2000/06/16 06:42:31 augustss Exp $ +.\" +.\" Copyright (c) 1999 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 10 2025 $ +.Dt PCKBC 4 +.Os +.Sh NAME +.Nm pckbc +.Nd PC (ISA) keyboard controller driver +.Sh SYNOPSIS +.Cd "pckbc* at isa? flags 0x00 " Pq "alpha, amd64, i386, loongson" +.Cd "pckbc* at acpi? flags 0x00 " Pq "amd64" +.Cd "pckbc* at ebus? " Pq "sparc64" +.Cd "pckbd* at pckbc?" +.Cd "pms* at pckbc?" +.Sh DESCRIPTION +The +.Nm +driver handles resource allocation and device attachment for the +traditional PC/AT keyboard controller, or emulations thereof. +It provides up to two logical connections for child devices, the +.Dq keyboard +slot for a keyboard and the +.Dq auxiliary +slot for mice (the latter might be missing in older keyboard controllers, +or recent emulations). +.Pp +To avoid attaching a phantom PS/2 keyboard device, the +.Xr isa 4 +attachment of the +.Nm +driver will attempt to detect USB legacy keyboard emulation on amd64 and i386 +systems. +Unfortunately, the detection heuristics may fail on older systems with a real +PS/2 keyboard. +The keyboard can be forced to attach on these systems, by changing the +device flags to 1. +.Pp +The +.Xr acpi 4 +attachment of the +.Nm +driver defaults to attach only where it would perform better than its legacy +.Xr isa 4 +attachment. +Should this logic be insufficient, it is possible to force it to always attach, +by changing its device flags to 1. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr ebus 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr pckbd 4 , +.Xr pms 4 , +.Xr boot_config 8 diff --git a/static/openbsd/man4/pckbd.4 b/static/openbsd/man4/pckbd.4 new file mode 100644 index 00000000..507d7337 --- /dev/null +++ b/static/openbsd/man4/pckbd.4 @@ -0,0 +1,226 @@ +.\" $OpenBSD: pckbd.4,v 1.42 2021/05/01 16:11:09 visa Exp $ +.\" $NetBSD: pckbd.4,v 1.3 1999/12/21 11:31:07 drochner Exp $ +.\" +.\" Copyright (c) 1999 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 1 2021 $ +.Dt PCKBD 4 +.Os +.Sh NAME +.Nm pckbd +.Nd PC keyboard driver for wscons +.Sh SYNOPSIS +.Cd "pckbd* at pckbc?" +.Cd "pckbd* at gsckbc?" Pq hppa +.Cd "wskbd* at pckbd?" +.Cd "option PCKBD_LAYOUT=XXX" +.Sh DESCRIPTION +This driver supports PC/AT keyboards within the +.Xr wscons 4 +console framework. +It doesn't provide direct device driver entry points but makes its +functions available via the internal +.Xr wskbd 4 +interface. +.Pp +The +.Nm +driver supports a number of different key mappings which +can be chosen from with the kernel option +.Dq PCKBD_LAYOUT +at compile time or with the utility +.Xr wsconsctl 8 +(variable: +.Dq keyboard.encoding ) +at runtime. +Other mappings can be used if the whole keymap is replaced by means of +.Xr wsconsctl 8 . +The built-in mappings are at this time: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It KB_BE +.Pq be +Belgium French. +.It KB_BR +.Pq br +Brazilian. +.It KB_CF +.Pq cf +Canadian French. +.It KB_DE +.Pq de +German with +.Dq dead accents . +.It KB_DK +.Pq dk +Danish with +.Dq dead accents . +.It KB_ES +.Pq es +Spanish. +.It KB_FR +.Pq fr +French. +.It KB_FR | KB_DVORAK +.Pq fr.dvorak +French keyboard with +.Dq Dvorak-Bepo +layout. +.It KB_HU +.Pq hu +Hungarian. +.It KB_IS +.Pq is +Icelandic with +.Dq dead accents . +.It KB_IT +.Pq it +Italian. +.It KB_JP +.Pq jp +Japanese. +.It KB_LA +.Pq la +Latinamerican. +.It KB_LT +.Pq \< +Lithuanian in +.Dq ISO 8859-13 . +.It KB_LV +.Pq \&lv +Latvian +.It KB_NL +.Pq \&nl +Dutch with +.Dq dead accents . +.It KB_NO +.Pq no +Norwegian with +.Dq dead accents . +.It KB_PL +.Pq pl +Polish in +.Dq ISO 8859-2 . +.It KB_PT +.Pq pt +Portuguese. +.It KB_RU +.Pq ru +Russian in +.Dq KOI8 . +.It KB_SF +.Pq sf +Swiss French with +.Dq dead accents . +.It KB_SG +.Pq sg +Swiss German with +.Dq dead accents . +.It KB_SI +.Pq si +Slovenian. +.It KB_SV +.Pq sv +Swedish with +.Dq dead accents . +.It KB_TR +.Pq tr +Turkish in +.Dq ISO 8859-9 +with +.Dq dead accents . +.It KB_UA +.Pq ua +Ukrainian in +.Dq KOI8 . +.It KB_UK +.Pq uk +British. +.It KB_US +.Pq us +English/US keyboard mapping (default). +.It KB_US | KB_COLEMAK +.Pq us.colemak +English/US keyboard with +.Dq Colemak +layout. +.It KB_US | KB_DECLK +.Pq us.declk +English/US mapping for +DEC LK400-style keyboards with PC keyboard interface (eg LK461). +.It KB_US | KB_DVORAK +.Pq us.dvorak +English/US keyboard with +.Dq Dvorak +layout. +.El +.Pp +The KB_DE, KB_DK, KB_IS, KB_NO, KB_SF, KB_SG, KB_SV and KB_TR +mappings can be used in the KB_NODEAD +.Pq .nodead +variant. +This switches off the +.Dq dead accents . +.Pp +The KB_BE, KB_FR, KB_FR | KB_DVORAK, KB_JP, KB_UK, KB_US, +KB_US | KB_DVORAK and KB_US | KB_COLEMAK +mappings can be modified +to swap the left Control and the Caps Lock keys by the +KB_SWAPCTRLCAPS variant bit or the +.Dq .swapctrlcaps +suffix. +.Pp +The KB_METAESC +.Pq .metaesc +option can be applied to any layout. +If set, keys pressed together +with the ALT modifier are prefixed by an ESC character. +(Standard behaviour is to add 128 to the ASCII value.) +.Pp +Because PC keyboard hardware doesn't contain a beeper, requests for +.Dq keyboard beeps +cannot be handled directly. +On alpha and i386, a helper device attached to the pcppi +driver allows use of the standard ISA speaker for this purpose. +.Sh EXAMPLES +To set a German keyboard layout without +.Dq dead accents +and sending an ESC character before the key symbol if the ALT +key is pressed simultaneously, use +.Ic wsconsctl keyboard.encoding=de.nodead.metaesc . +To set it at kernel build time, add +the following to the kernel configuration file: +.Bd -literal -offset indent +option PCKBD_LAYOUT="(KB_DE|KB_NODEAD|KB_METAESC)" +.Ed +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr pckbc 4 , +.Xr wskbd 4 , +.Xr wsconsctl 8 +.Sh BUGS +The list of built-in mappings doesn't follow any logic. +It grew as people submitted what they needed. diff --git a/static/openbsd/man4/pcmcia.4 b/static/openbsd/man4/pcmcia.4 new file mode 100644 index 00000000..3893b503 --- /dev/null +++ b/static/openbsd/man4/pcmcia.4 @@ -0,0 +1,159 @@ +.\" $OpenBSD: pcmcia.4,v 1.66 2019/12/13 20:57:54 deraadt Exp $ +.\" $NetBSD: pcmcia.4,v 1.4 1998/06/07 09:10:30 enami Exp $ +.\" +.\" Copyright (c) 1997 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 13 2019 $ +.Dt PCMCIA 4 +.Os +.Sh NAME +.Nm pcmcia , +.Nm pcic +.Nd introduction to PCMCIA (PC Card) support +.Sh SYNOPSIS +.Cd "# i386" +.Cd "pcic0 at isa? port 0x3e0 iomem 0xd0000 iosiz 0x10000" +.Cd "pcic1 at isa? port 0x3e2 iomem 0xe0000 iosiz 0x4000" +.Cd "pcic2 at isa? port 0x3e4 iomem 0xe0000 iosiz 0x4000" +.Cd "pcic* at isapnp?" +.Cd "pcic* at pci? dev?" +.Cd "pcmcia* at pcic?" +.Pp +.Cd "# i386" +.Cd "tcic0 at isa? port 0x240 iomem 0xd0000 iosiz 0x10000" +.Cd "pcmcia* at tcic?" +.Pp +.Cd "# luna88k" +.Cd "pcic0 at cbus? port 0x3e0 iomem 0xd0000 iosiz 0x10000" +.Cd "pcmcia* at pcic?" +.Pp +.Cd "# sparc64" +.Cd "stp* at sbus?" +.Cd "pcmcia* at stp?" +.Pp +.Cd "# all architectures" +.Cd "cbb* at pci?" +.Cd "cardslot* at cbb? flags 0x0000" +.Cd "pcmcia* at cardslot?" +.Sh DESCRIPTION +The +.Nm +subsystem provides machine-independent bus support and +drivers for PCMCIA (PC Card) +devices. +.Pp +.Ox +provides support for the following devices. +Note that not all architectures support all devices. +.Ss Serial interfaces and modems +.Bl -tag -width 12n -offset ind -compact +.It Xr com 4 +serial communications interface +.El +.Ss Wired network interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr ep 4 +3Com EtherLink III and Fast EtherLink III 10/100 Ethernet device +.It Xr ne 4 +NE2000 and compatible 10/100 Ethernet device +.It Xr sm 4 +SMC91C9x and SMC91C1xx-based 10/100 Ethernet device +.It Xr xe 4 +Xircom-based 16-bit PCMCIA 10/100 Ethernet device +.El +.Ss Wireless network interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr an 4 +Aironet Communications 4500/4800 IEEE 802.11FH/b wireless network device +.It Xr malo 4 +Marvell Libertas IEEE 802.11b/g wireless network device +.It Xr wi 4 +WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b wireless network device +.El +.Ss SCSI controllers +.Bl -tag -width 12n -offset ind -compact +.It Xr aic 4 +Adaptec AIC-6260 and AIC-6360 SCSI interface +.El +.Ss IDE controllers +.Bl -tag -width 12n -offset ind -compact +.It Xr wdc 4 +WD100x compatible hard disk controller driver +.El +.Pp +The supported PCMCIA controllers are those that are i82365 compatible. +.Sh NOTES +On some +.Nm +adapters, for instance the +.Xr sbus 4 Ns -based +.Xr stp 4 , +the +.Nm +bus will be mapped in big-endian format instead of the natural (and +preferred) little endian format. +Unfortunately such controllers lack the hardware facility to swap bytes, +and it is not efficient to convert all drivers to always know about this. +While 8 bit drivers can invisibly work on such a bus, 16 bit +drivers will need modification to handle this. +So far, +.Xr wi 4 +is the only driver to require these modifications. +.Pp +If the +.Nm +adapter is not detected, or if +.Nm +events (such as card insertion) do not occur, there may be a +.Tn PCI +card BIOS mapped in the same memory space the +.Nm +driver is configured to use (this is often the case with Ethernet +card boot ROMs). +The output from +.Xr dmesg 8 +should contain a line beginning with +.Dq bios0 +that lists the memory address and size of mapped regions. +If there is a conflict, you can use +.Xr boot_config 8 +to change the iomem parameter of the +.Em pcic +device to a non-overlapping address, such as 0xd8000 for +.Em pcic0 . +Some experimentation may be required to find a working value; in some +cases the size parameter of the +.Em pcic +device may need to be decreased to avoid a conflict. +.Sh SEE ALSO +.Xr cardbus 4 , +.Xr intro 4 , +.Xr isa 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.3 . diff --git a/static/openbsd/man4/pcn.4 b/static/openbsd/man4/pcn.4 new file mode 100644 index 00000000..24733a1a --- /dev/null +++ b/static/openbsd/man4/pcn.4 @@ -0,0 +1,112 @@ +.\" $OpenBSD: pcn.4,v 1.10 2013/07/16 16:05:49 schwarze Exp $ +.\" $NetBSD: pcn.4,v 1.3 2001/09/11 22:52:53 wiz Exp $ +.\" +.\" Copyright 2001 Wasabi Systems, Inc. +.\" All rights reserved. +.\" +.\" Written by Jason R. Thorpe for Wasabi Systems, Inc. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed for the NetBSD Project by +.\" Wasabi Systems, Inc. +.\" 4. The name of Wasabi Systems, Inc. may not be used to endorse +.\" or promote products derived from this software without specific prior +.\" written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY WASABI SYSTEMS, INC. ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL WASABI SYSTEMS, INC +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PCN 4 +.Os +.Sh NAME +.Nm pcn +.Nd AMD PCnet-PCI 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "pcn* at pci?" +.Cd "acphy* at mii?" +.Cd "amphy* at mii?" +.Cd "lxtphy* at mii?" +.Cd "nsphy* at mii?" +.Sh DESCRIPTION +The +.Nm +device driver supports Ethernet interfaces based on the AMD +PCnet-PCI family of Ethernet chips. +The chips supported by the +.Nm +driver include: +.Bl -bullet +.It +Am79c970 PCnet-PCI Single-Chip Ethernet Controller for PCI +Local Bus +.It +Am79c970A PCnet-PCI II Single-Chip Full-Duplex Ethernet Controller +for PCI Local Bus +.It +Am79c971 PCnet-FAST Single-Chip Full-Duplex 10/100Mbps +Ethernet Controller for PCI Local Bus +.It +Am79c972 PCnet-FAST+ Enhanced 10/100Mbps PCI Ethernet Controller +with OnNow Support +.It +Am79c973/Am79c975 PCnet-FAST III Single-Chip 10/100Mbps PCI +Ethernet Controller with Integrated PHY +.El +.Pp +PCnet-PCI chips are found on some Hewlett-Packard PCI Ethernet +boards, and on the Allied Telesyn AT-2700TX PCI Ethernet board. +They are also found on some processor evaluation boards as an +example peripheral. +.Pp +The +.Nm +driver also supports the emulated PCnet-PCI interface provided +by VMware. +.Sh SEE ALSO +.Xr acphy 4 , +.Xr amphy 4 , +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr lxtphy 4 , +.Xr mii 4 , +.Xr netintro 4 , +.Xr nsphy 4 , +.Xr pci 4 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx 1.6 . +.Ox +support was added in +.Ox 3.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jason R. Thorpe Aq Mt thorpej@wasabisystems.com +and ported to +.Ox +by +.An Brad Smith Aq Mt brad@openbsd.org . diff --git a/static/openbsd/man4/pcppi.4 b/static/openbsd/man4/pcppi.4 new file mode 100644 index 00000000..2d9ac10c --- /dev/null +++ b/static/openbsd/man4/pcppi.4 @@ -0,0 +1,66 @@ +.\" $OpenBSD: pcppi.4,v 1.12 2010/07/31 09:38:03 jmc Exp $ +.\" $NetBSD: pcppi.4,v 1.5 2001/10/02 20:37:00 augustss Exp $ +.\" +.\" Copyright (c) 1999 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 31 2010 $ +.Dt PCPPI 4 +.Os +.Sh NAME +.Nm pcppi +.Nd PC (ISA) control and timer port driver +.Sh SYNOPSIS +.Cd "pcppi* at isa?" +.Cd "spkr0 at pcppi?" +.Sh DESCRIPTION +The +.Nm +driver handles resource allocation and device attachment for the +ports related to the ISA speaker in the traditional PC/AT +.Dq design . +These are the +.Dq system control port +(which was implemented by the 8255 +.Dq PPI +in the XT, hence the name of this driver) +at I/O address 0x61 and the first 8253 timer at 0x40-0x43. +.Pp +The +.Nm +driver provides its child devices with the ability to output simple +tones through the PC speaker. +The +.Xr speaker 4 +device uses this to synthesize sounds. +It also provides helper functions to the +.Xr pckbd 4 +driver as a substitute for a +.Dq keyboard beep , +because the PC keyboard hardware doesn't provide this. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr pckbd 4 , +.Xr speaker 4 diff --git a/static/openbsd/man4/pcscp.4 b/static/openbsd/man4/pcscp.4 new file mode 100644 index 00000000..ef479f25 --- /dev/null +++ b/static/openbsd/man4/pcscp.4 @@ -0,0 +1,63 @@ +.\" $OpenBSD: pcscp.4,v 1.17 2022/02/18 10:24:32 jsg Exp $ +.\" $NetBSD: pcscp.4,v 1.3 1999/09/12 18:47:12 kleink Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt PCSCP 4 +.Os +.Sh NAME +.Nm pcscp +.Nd Advanced Micro Devices Am53c974 PCscsi-PCI SCSI interface +.Sh SYNOPSIS +.Cd "pcscp* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Advanced Micro Devices Am53c974 +PCscsi-PCI SCSI controller and boards using this chip, including +the Tekram DC-390 PCI SCSI host adapter. +.Pp +For Tekram DC-390U/F PCI SCSI host adapters, use the +.Xr siop 4 +driver. +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 +.Pp +.Lk https://www.amd.com +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.9 . +.Sh BUGS +The driver currently ignores EEPROM settings, which establish +per-target parameters etc. diff --git a/static/openbsd/man4/pcxrtc.4 b/static/openbsd/man4/pcxrtc.4 new file mode 100644 index 00000000..620c1808 --- /dev/null +++ b/static/openbsd/man4/pcxrtc.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: pcxrtc.4,v 1.3 2018/11/20 09:06:08 reyk Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt +.\" Copyright (c) 2017 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 20 2018 $ +.Dt PCXRTC 4 +.Os +.Sh NAME +.Nm pcxrtc +.Nd NXP PCF8563 real-time clock +.Sh SYNOPSIS +.Cd "pcxrtc* at iic? addr 0x51" +.Sh DESCRIPTION +The +.Nm +driver provides support for the NXP PCF8563 real-time clock chip. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/pcyrtc.4 b/static/openbsd/man4/pcyrtc.4 new file mode 100644 index 00000000..ba9fff4d --- /dev/null +++ b/static/openbsd/man4/pcyrtc.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: pcyrtc.4,v 1.1 2021/11/22 20:24:41 kettenis Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt +.\" Copyright (c) 2016 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 22 2021 $ +.Dt PCYRTC 4 +.Os +.Sh NAME +.Nm pcyrtc +.Nd NXP PCF85063A/TP real-time clock +.Sh SYNOPSIS +.Cd "pcyrtc* at iic? addr 0x51" +.Sh DESCRIPTION +The +.Nm +driver provides support for the NXP PCF85063A/TP real-time clock chip. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/pf.4 b/static/openbsd/man4/pf.4 new file mode 100644 index 00000000..e0a506f8 --- /dev/null +++ b/static/openbsd/man4/pf.4 @@ -0,0 +1,1126 @@ +.\" $OpenBSD: pf.4,v 1.95 2023/07/05 12:00:01 sashan Exp $ +.\" +.\" Copyright (C) 2001, Kjell Wooding. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the project nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 5 2023 $ +.Dt PF 4 +.Os +.Sh NAME +.Nm pf +.Nd packet filter +.Sh SYNOPSIS +.Cd "pseudo-device pf" +.Sh DESCRIPTION +Packet filtering takes place in the kernel. +A pseudo-device, +.Pa /dev/pf , +allows userland processes to control the +behavior of the packet filter through an +.Xr ioctl 2 +interface. +There are commands to enable and disable the filter, load rulesets, +add and remove individual rules or state table entries, +and retrieve statistics. +The most commonly used functions are covered by +.Xr pfctl 8 . +.Pp +Operations loading or reading a ruleset that involve more than a single +.Xr ioctl 2 +call require a so-called +.Sy ticket , +which allows +.Nm +to deal with concurrent operations. +For certain +.Xr ioctl 2 +commands (currently +.Dv DIOCGETRULES ) +the number of tickets a program can get is limited. +The programs must explicitly release their tickets using the +.Dv DIOCXEND +command to avoid hitting the limit. +All tickets which are not freed by +.Dv DIOCXEND +are released when the program closes +.Pa /dev/pf . +.Pp +Fields of +.Xr ioctl 2 +parameter structures that refer to packet data (like +addresses and ports) are generally expected in network byte-order. +.Pp +Rules and address tables are contained in so-called +.Em anchors . +When servicing an +.Xr ioctl 2 +request, if the anchor field of the argument structure is empty, +the kernel will use the default anchor (i.e., the main ruleset) +in operations. +Anchors are specified by name and may be nested, with components +separated by +.Sq / +characters, similar to how file system hierarchies are laid out. +The final component of the anchor path is the anchor under which +operations will be performed. +Anchor names with characters after the terminating null byte are +considered invalid; if used in an ioctl, +.Er EINVAL +will be returned. +.Sh IOCTL INTERFACE +.Nm +supports the following +.Xr ioctl 2 +commands, available through +.In net/pfvar.h : +.Bl -tag -width xxxxxx +.It Dv DIOCSTART +Start the packet filter. +.It Dv DIOCSTOP +Stop the packet filter. +.It Dv DIOCADDRULE Fa "struct pfioc_rule *pr" +.Bd -literal +struct pfioc_rule { + u_int32_t action; + u_int32_t ticket; + u_int32_t nr; + char anchor[PATH_MAX]; + char anchor_call[PATH_MAX]; + struct pf_rule rule; +}; +.Ed +.Pp +Add +.Va rule +at the end of the inactive ruleset. +This call requires a +.Va ticket +obtained through a preceding +.Dv DIOCXBEGIN +call. +The optional +.Va anchor +name indicates the anchor in which to append the rule. +.Va nr +and +.Va action +are ignored. +.It Dv DIOCADDQUEUE Fa "struct pfioc_queue *q" +Add a queue. +.Bd -literal +struct pfioc_queue { + u_int32_t ticket; + u_int nr; + struct pf_queuespec queue; +}; +.Ed +.It Dv DIOCGETRULES Fa "struct pfioc_rule *pr" +Get a +.Va ticket +for subsequent +.Dv DIOCGETRULE +calls and the number +.Va nr +of rules in the active ruleset. +The ticket should be released by the +.Dv DIOCXEND +command. +.It Dv DIOCGETRULE Fa "struct pfioc_rule *pr" +Get a +.Va rule +by its number +.Va nr +using the +.Va ticket +obtained through a preceding +.Dv DIOCGETRULES +call. +If +.Va action +is set to +.Dv PF_GET_CLR_CNTR , +the per-rule statistics on the requested rule are cleared. +.It Dv DIOCGETQUEUES Fa "struct pfioc_queue *pq" +Get a +.Va ticket +for subsequent +.Dv DIOCGETQUEUE +calls and the number +.Va nr +of queues in the active list. +.It Dv DIOCGETQUEUE Fa "struct pfioc_queue *pq" +Get the queueing discipline +by its number +.Va nr +using the +.Va ticket +obtained through a preceding +.Dv DIOCGETQUEUES +call. +.It Dv DIOCGETQSTATS Fa "struct pfioc_qstats *pq" +Get the statistics on a queue. +.Bd -literal +struct pfioc_qstats { + u_int32_t ticket; + u_int32_t nr; + struct pf_queuespec queue; + void *buf; + int nbytes; +}; +.Ed +.Pp +This call fills in a pointer to the buffer of statistics +.Va buf , +of length +.Va nbytes , +for the queue specified by +.Va nr . +.It Dv DIOCGETRULESETS Fa "struct pfioc_ruleset *pr" +.Bd -literal +struct pfioc_ruleset { + u_int32_t nr; + char path[PATH_MAX]; + char name[PF_ANCHOR_NAME_SIZE]; +}; +.Ed +.Pp +Get the number +.Va nr +of rulesets (i.e., anchors) directly attached to the anchor named by +.Va path +for use in subsequent +.Dv DIOCGETRULESET +calls. +Nested anchors, since they are not directly attached to the given +anchor, will not be included. +This ioctl returns +.Er EINVAL +if the given anchor does not exist. +.It Dv DIOCGETRULESET Fa "struct pfioc_ruleset *pr" +Get a ruleset (i.e., an anchor) +.Va name +by its number +.Va nr +from the given anchor +.Va path , +the maximum number of which can be obtained from a preceding +.Dv DIOCGETRULESETS +call. +This ioctl returns +.Er EINVAL +if the given anchor does not exist or +.Er EBUSY +if another process is concurrently updating a ruleset. +.It Dv DIOCADDSTATE Fa "struct pfioc_state *ps" +Add a state entry. +.Bd -literal +struct pfioc_state { + struct pfsync_state state; +}; +.Ed +.It Dv DIOCGETSTATE Fa "struct pfioc_state *ps" +Extract the entry identified by the +.Va id +and +.Va creatorid +fields of the +.Va state +structure from the state table. +.It Dv DIOCKILLSTATES Fa "struct pfioc_state_kill *psk" +Remove matching entries from the state table. +This ioctl returns the number of killed states in +.Va psk_killed . +.Bd -literal +struct pfioc_state_kill { + struct pf_state_cmp psk_pfcmp; + sa_family_t psk_af; + int psk_proto; + struct pf_rule_addr psk_src; + struct pf_rule_addr psk_dst; + char psk_ifname[IFNAMSIZ]; + char psk_label[PF_RULE_LABEL_SIZE]; + u_int psk_killed; + u_int16_t psk_rdomain; +}; +.Ed +.It Dv DIOCCLRSTATES Fa "struct pfioc_state_kill *psk" +Clear all states. +It works like +.Dv DIOCKILLSTATES , +but ignores all fields of the +.Vt pfioc_state_kill +structure, except +.Va psk_ifname . +.It Dv DIOCGETSTATUS Fa "struct pf_status *s" +Get the internal packet filter statistics. +.Bd -literal +struct pf_status { + u_int64_t counters[PFRES_MAX]; + u_int64_t lcounters[LCNT_MAX]; /* limit counters */ + u_int64_t fcounters[FCNT_MAX]; + u_int64_t scounters[SCNT_MAX]; + u_int64_t pcounters[2][2][3]; + u_int64_t bcounters[2][2]; + u_int64_t stateid; + u_int64_t syncookies_inflight[2]; /* unACKed SYNcookies */ + time_t since; + u_int32_t running; + u_int32_t states; + u_int32_t states_halfopen; + u_int32_t src_nodes; + u_int32_t debug; + u_int32_t hostid; + u_int32_t reass; /* reassembly */ + u_int8_t syncookies_active; + u_int8_t syncookies_mode; /* never/always/adaptive */ + u_int8_t pad[2]; + char ifname[IFNAMSIZ]; + u_int8_t pf_chksum[PF_MD5_DIGEST_LENGTH]; +}; +.Ed +.It Dv DIOCCLRSTATUS +Clear the internal packet filter statistics. +.It Dv DIOCNATLOOK Fa "struct pfioc_natlook *pnl" +Look up a state table entry by source and destination addresses and ports. +.Bd -literal +struct pfioc_natlook { + struct pf_addr saddr; + struct pf_addr daddr; + struct pf_addr rsaddr; + struct pf_addr rdaddr; + u_int16_t rdomain; + u_int16_t rrdomain; + u_int16_t sport; + u_int16_t dport; + u_int16_t rsport; + u_int16_t rdport; + sa_family_t af; + u_int8_t proto; + u_int8_t direction; +}; +.Ed +.Pp +This was primarily used to support transparent proxies with rdr-to rules. +New proxies should use divert-to rules instead. +These do not require access to the privileged +.Pa /dev/pf +device and preserve the original destination address for +.Xr getsockname 2 . +For +.Dv SOCK_DGRAM +sockets, the +.Xr ip 4 +socket options +.Dv IP_RECVDSTADDR +and +.Dv IP_RECVDSTPORT +can be used to retrieve the destination address and port. +.It Dv DIOCSETDEBUG Fa "u_int32_t *level" +Set the debug level. +See the +.Xr syslog 3 +man page for a list of valid debug levels. +.It Dv DIOCGETSTATES Fa "struct pfioc_states *ps" +Get state table entries. +.Bd -literal +struct pfioc_states { + size_t ps_len; + union { + caddr_t psu_buf; + struct pfsync_state *psu_states; + } ps_u; +#define ps_buf ps_u.psu_buf +#define ps_states ps_u.psu_states +}; +.Ed +.Pp +If +.Va ps_len +is non-zero on entry, as many states as possible that can fit into this +size will be copied into the supplied buffer +.Va ps_states . +On exit, +.Va ps_len +is always set to the total size required to hold all state table entries +(i.e., it is set to +.Li sizeof(struct pfsync_state) * nr ) . +.It Dv DIOCCHANGERULE Fa "struct pfioc_rule *pcr" +Add or remove the +.Va rule +in the ruleset specified by +.Va rule.action . +.Pp +The type of operation to be performed is indicated by +.Va action , +which can be any of the following: +.Bd -literal +enum { PF_CHANGE_NONE, PF_CHANGE_ADD_HEAD, PF_CHANGE_ADD_TAIL, + PF_CHANGE_ADD_BEFORE, PF_CHANGE_ADD_AFTER, + PF_CHANGE_REMOVE, PF_CHANGE_GET_TICKET }; +.Ed +.Pp +.Va ticket +must be set to the value obtained with +.Dv PF_CHANGE_GET_TICKET +for all actions except +.Dv PF_CHANGE_GET_TICKET . +.Va anchor +indicates to which anchor the operation applies. +.Va nr +indicates the rule number against which +.Dv PF_CHANGE_ADD_BEFORE , +.Dv PF_CHANGE_ADD_AFTER , +or +.Dv PF_CHANGE_REMOVE +actions are applied. +.It Dv DIOCSETTIMEOUT Fa "struct pfioc_tm *pt" +.Bd -literal +struct pfioc_tm { + int timeout; + int seconds; +}; +.Ed +.Pp +Set the state timeout of +.Va timeout +to +.Va seconds . +The old value will be placed into +.Va seconds . +For possible values of +.Va timeout , +consult the +.Dv PFTM_* +values in +.In net/pfvar.h . +.It Dv DIOCGETTIMEOUT Fa "struct pfioc_tm *pt" +Get the state timeout of +.Va timeout . +The value will be placed into the +.Va seconds +field. +.It Dv DIOCSETLIMIT Fa "struct pfioc_limit *pl" +Set the hard limits on the memory pools used by the packet filter. +.Bd -literal +struct pfioc_limit { + int index; + unsigned limit; +}; + +enum { PF_LIMIT_STATES, PF_LIMIT_SRC_NODES, PF_LIMIT_FRAGS, + PF_LIMIT_TABLES, PF_LIMIT_TABLE_ENTRIES, PF_LIMIT_PKTDELAY_PKTS, + PF_LIMIT_ANCHORS, PF_LIMIT_MAX }; +.Ed +.It Dv DIOCGETLIMIT Fa "struct pfioc_limit *pl" +Get the hard +.Va limit +for the memory pool indicated by +.Va index . +.It Dv DIOCRCLRTABLES Fa "struct pfioc_table *io" +Clear all tables. +All the ioctls that manipulate radix tables +use the same structure described below. +For +.Dv DIOCRCLRTABLES , +.Va pfrio_ndel +contains on exit the number of tables deleted. +.Bd -literal +struct pfioc_table { + struct pfr_table pfrio_table; + void *pfrio_buffer; + int pfrio_esize; + int pfrio_size; + int pfrio_size2; + int pfrio_nadd; + int pfrio_ndel; + int pfrio_nchange; + int pfrio_flags; + u_int32_t pfrio_ticket; +}; +#define pfrio_exists pfrio_nadd +#define pfrio_nzero pfrio_nadd +#define pfrio_nmatch pfrio_nadd +#define pfrio_naddr pfrio_size2 +#define pfrio_setflag pfrio_size2 +#define pfrio_clrflag pfrio_nadd +.Ed +.It Dv DIOCRADDTABLES Fa "struct pfioc_table *io" +Create one or more tables. +On entry, +.Va pfrio_buffer +must point to an array of +.Vt struct pfr_table +containing at least +.Vt pfrio_size +elements. +.Vt pfrio_esize +must be the size of +.Vt struct pfr_table . +On exit, +.Va pfrio_nadd +contains the number of tables effectively created. +.Bd -literal +struct pfr_table { + char pfrt_anchor[PATH_MAX]; + char pfrt_name[PF_TABLE_NAME_SIZE]; + u_int32_t pfrt_flags; + u_int8_t pfrt_fback; +}; +.Ed +.It Dv DIOCRDELTABLES Fa "struct pfioc_table *io" +Delete one or more tables. +On entry, +.Va pfrio_buffer +must point to an array of +.Vt struct pfr_table +containing at least +.Vt pfrio_size +elements. +.Vt pfrio_esize +must be the size of +.Vt struct pfr_table . +On exit, +.Va pfrio_ndel +contains the number of tables effectively deleted. +.It Dv DIOCRGETTABLES Fa "struct pfioc_table *io" +Get the list of all tables. +On entry, +.Va pfrio_buffer[pfrio_size] +contains a valid writeable buffer for +.Vt pfr_table +structures. +On exit, +.Va pfrio_size +contains the number of tables written into the buffer. +If the buffer is too small, the kernel does not store anything but just +returns the required buffer size, without error. +.It Dv DIOCRGETTSTATS Fa "struct pfioc_table *io" +This call is like +.Dv DIOCRGETTABLES +but is used to get an array of +.Vt pfr_tstats +structures. +.Bd -literal +struct pfr_tstats { + struct pfr_table pfrts_t; + u_int64_t pfrts_packets + [PFR_DIR_MAX][PFR_OP_TABLE_MAX]; + u_int64_t pfrts_bytes + [PFR_DIR_MAX][PFR_OP_TABLE_MAX]; + u_int64_t pfrts_match; + u_int64_t pfrts_nomatch; + time_t pfrts_tzero; + int pfrts_cnt; + int pfrts_refcnt[PFR_REFCNT_MAX]; +}; +#define pfrts_name pfrts_t.pfrt_name +#define pfrts_flags pfrts_t.pfrt_flags +.Ed +.It Dv DIOCRCLRTSTATS Fa "struct pfioc_table *io" +Clear the statistics of one or more tables. +On entry, +.Va pfrio_buffer +must point to an array of +.Vt struct pfr_table +containing at least +.Vt pfrio_size +elements. +.Vt pfrio_esize +must be the size of +.Vt struct pfr_table . +On exit, +.Va pfrio_nzero +contains the number of tables effectively cleared. +.It Dv DIOCRCLRADDRS Fa "struct pfioc_table *io" +Clear all addresses in a table. +On entry, +.Va pfrio_table +contains the table to clear. +On exit, +.Va pfrio_ndel +contains the number of addresses removed. +.It Dv DIOCRADDADDRS Fa "struct pfioc_table *io" +Add one or more addresses to a table. +On entry, +.Va pfrio_table +contains the table ID and +.Va pfrio_buffer +must point to an array of +.Vt struct pfr_addr +containing at least +.Vt pfrio_size +elements to add to the table. +.Vt pfrio_esize +must be the size of +.Vt struct pfr_addr . +On exit, +.Va pfrio_nadd +contains the number of addresses effectively added. +.Bd -literal +struct pfr_addr { + union { + struct in_addr _pfra_ip4addr; + struct in6_addr _pfra_ip6addr; + } pfra_u; + char pfra_ifname[IFNAMSIZ]; + u_int32_t pfra_states; + u_int16_t pfra_weight; + u_int8_t pfra_af; + u_int8_t pfra_net; + u_int8_t pfra_not; + u_int8_t pfra_fback; + u_int8_t pfra_type; + u_int8_t pad[7]; +}; +#define pfra_ip4addr pfra_u._pfra_ip4addr +#define pfra_ip6addr pfra_u._pfra_ip6addr +.Ed +.It Dv DIOCRDELADDRS Fa "struct pfioc_table *io" +Delete one or more addresses from a table. +On entry, +.Va pfrio_table +contains the table ID and +.Va pfrio_buffer +must point to an array of +.Vt struct pfr_addr +containing at least +.Vt pfrio_size +elements to delete from the table. +.Vt pfrio_esize +must be the size of +.Vt struct pfr_addr . +On exit, +.Va pfrio_ndel +contains the number of addresses effectively deleted. +.It Dv DIOCRSETADDRS Fa "struct pfioc_table *io" +Replace the content of a table by a new address list. +This is the most complicated command, which uses all the structure members. +.Pp +On entry, +.Va pfrio_table +contains the table ID and +.Va pfrio_buffer +must point to an array of +.Vt struct pfr_addr +containing at least +.Vt pfrio_size +elements which become the new contents of the table. +.Vt pfrio_esize +must be the size of +.Vt struct pfr_addr . +Additionally, if +.Va pfrio_size2 +is non-zero, +.Va pfrio_buffer[pfrio_size..pfrio_size2] +must be a writeable buffer, into which the kernel can copy the +addresses that have been deleted during the replace operation. +On exit, +.Va pfrio_ndel , +.Va pfrio_nadd , +and +.Va pfrio_nchange +contain the number of addresses deleted, added, and changed by the +kernel. +If +.Va pfrio_size2 +was set on entry, +.Va pfrio_size2 +will point to the size of the buffer used, exactly like +.Dv DIOCRGETADDRS . +.It Dv DIOCRGETADDRS Fa "struct pfioc_table *io" +Get all the addresses of a table. +On entry, +.Va pfrio_table +contains the table ID and +.Va pfrio_buffer[pfrio_size] +contains a valid writeable buffer for +.Vt pfr_addr +structures. +On exit, +.Va pfrio_size +contains the number of addresses written into the buffer. +If the buffer was too small, the kernel does not store anything but just +returns the required buffer size, without returning an error. +.It Dv DIOCRGETASTATS Fa "struct pfioc_table *io" +This call is like +.Dv DIOCRGETADDRS +but is used to get an array of +.Vt pfr_astats +structures. +.Bd -literal +struct pfr_astats { + struct pfr_addr pfras_a; + u_int64_t pfras_packets + [PFR_DIR_MAX][PFR_OP_ADDR_MAX]; + u_int64_t pfras_bytes + [PFR_DIR_MAX][PFR_OP_ADDR_MAX]; + time_t pfras_tzero; +}; +.Ed +.It Dv DIOCRCLRASTATS Fa "struct pfioc_table *io" +Clear the statistics of one or more addresses. +On entry, +.Va pfrio_table +contains the table ID and +.Va pfrio_buffer +must point to an array of +.Vt struct pfr_addr +containing at least +.Vt pfrio_size +elements to be cleared from the table. +.Vt pfrio_esize +must be the size of +.Vt struct pfr_addr . +On exit, +.Va pfrio_nzero +contains the number of addresses effectively cleared. +.It Dv DIOCRTSTADDRS Fa "struct pfioc_table *io" +Test if the given addresses match a table. +On entry, +.Va pfrio_table +contains the table ID and +.Va pfrio_buffer +must point to an array of +.Vt struct pfr_addr +containing at least +.Vt pfrio_size +elements, each of which will be tested for a match in the table. +.Vt pfrio_esize +must be the size of +.Vt struct pfr_addr . +On exit, the kernel updates the +.Vt pfr_addr +array by setting the +.Va pfra_fback +member appropriately. +.It Dv DIOCRSETTFLAGS Fa "struct pfioc_table *io" +Change the +.Dv PFR_TFLAG_CONST +or +.Dv PFR_TFLAG_PERSIST +flags of a table. +On entry, +.Va pfrio_buffer +must point to an array of +.Vt struct pfr_table +containing at least +.Vt pfrio_size +elements. +.Va pfrio_esize +must be the size of +.Vt struct pfr_table . +.Va pfrio_setflag +must contain the flags to add, while +.Va pfrio_clrflag +must contain the flags to remove. +On exit, +.Va pfrio_nchange +and +.Va pfrio_ndel +contain the number of tables altered or deleted by the kernel. +Yes, tables can be deleted if one removes the +.Dv PFR_TFLAG_PERSIST +flag of an unreferenced table. +.It Dv DIOCRINADEFINE Fa "struct pfioc_table *io" +Defines a table in the inactive set. +On entry, +.Va pfrio_table +contains the table ID and +.Va pfrio_buffer[pfrio_size] +contains an array of +.Vt pfr_addr +structures to put in the table. +A valid ticket must also be supplied to +.Va pfrio_ticket . +On exit, +.Va pfrio_nadd +contains 0 if the table was already defined in the inactive list +or 1 if a new table has been created. +.Va pfrio_naddr +contains the number of addresses effectively put in the table. +.It Dv DIOCXBEGIN Fa "struct pfioc_trans *io" +.Bd -literal +struct pfioc_trans { + int size; /* number of elements */ + int esize; /* size of each element in bytes */ + struct pfioc_trans_e { + int type; + char anchor[PATH_MAX]; + u_int32_t ticket; + } *array; +}; +.Ed +.Pp +Clear all the inactive rulesets specified in the +.Vt pfioc_trans_e +array. +For each ruleset, a ticket is returned for subsequent "add rule" ioctls, +as well as for the +.Dv DIOCXCOMMIT +and +.Dv DIOCXROLLBACK +calls. +.Pp +Ruleset types, identified by +.Va type , +can be one of the following: +.Pp +.Bl -tag -width PF_TRANS_RULESET -offset ind -compact +.It Dv PF_TRANS_RULESET +Filter rules. +.It Dv PF_TRANS_TABLE +Address tables. +.El +.It Dv DIOCXCOMMIT Fa "struct pfioc_trans *io" +Atomically switch a vector of inactive rulesets to the active rulesets. +This call is implemented as a standard two-phase commit, which will either +fail for all rulesets or completely succeed. +All tickets need to be valid. +This ioctl returns +.Er EBUSY +if another process is concurrently updating some of the same rulesets. +.It Dv DIOCXROLLBACK Fa "struct pfioc_trans *io" +Clean up the kernel by undoing all changes that have taken place on the +inactive rulesets since the last +.Dv DIOCXBEGIN . +.Dv DIOCXROLLBACK +will silently ignore rulesets for which the ticket is invalid. +.It Dv DIOCXEND Fa "u_int32_t *ticket" +Release the ticket obtained by the +.Dv DIOCGETRULES +command. +.It Dv DIOCSETHOSTID Fa "u_int32_t *hostid" +Set the host ID, which is used by +.Xr pfsync 4 +to identify which host created state table entries. +.It Dv DIOCOSFPFLUSH +Flush the passive OS fingerprint table. +.It Dv DIOCOSFPADD Fa "struct pf_osfp_ioctl *io" +.Bd -literal +struct pf_osfp_ioctl { + struct pf_osfp_entry fp_os; + pf_tcpopts_t fp_tcpopts; /* packed TCP options */ + u_int16_t fp_wsize; /* TCP window size */ + u_int16_t fp_psize; /* ip->ip_len */ + u_int16_t fp_mss; /* TCP MSS */ + u_int16_t fp_flags; + u_int8_t fp_optcnt; /* TCP option count */ + u_int8_t fp_wscale; /* TCP window scaling */ + u_int8_t fp_ttl; /* IPv4 TTL */ + + int fp_getnum; /* DIOCOSFPGET number */ +}; + +struct pf_osfp_entry { + SLIST_ENTRY(pf_osfp_entry) fp_entry; + pf_osfp_t fp_os; + int fp_enflags; +#define PF_OSFP_EXPANDED 0x001 /* expanded entry */ +#define PF_OSFP_GENERIC 0x002 /* generic signature */ +#define PF_OSFP_NODETAIL 0x004 /* no p0f details */ +#define PF_OSFP_LEN 32 + u_char fp_class_nm[PF_OSFP_LEN]; + u_char fp_version_nm[PF_OSFP_LEN]; + u_char fp_subtype_nm[PF_OSFP_LEN]; +}; +.Ed +.Pp +Add a passive OS fingerprint to the table. +Set +.Va fp_os.fp_os +to the packed fingerprint, +.Va fp_os.fp_class_nm +to the name of the class (Linux, Windows, etc), +.Va fp_os.fp_version_nm +to the name of the version (NT, 95, 98), and +.Va fp_os.fp_subtype_nm +to the name of the subtype or patchlevel. +The members +.Va fp_mss , +.Va fp_wsize , +.Va fp_psize , +.Va fp_ttl , +.Va fp_optcnt , +and +.Va fp_wscale +are set to the TCP MSS, the TCP window size, the IP length, the IP TTL, +the number of TCP options, and the TCP window scaling constant of the +TCP SYN packet, respectively. +.Pp +The +.Va fp_flags +member is filled according to the +.In net/pfvar.h +include file +.Dv PF_OSFP_* +defines. +The +.Va fp_tcpopts +member contains packed TCP options. +Each option uses +.Dv PF_OSFP_TCPOPT_BITS +bits in the packed value. +Options include any of +.Dv PF_OSFP_TCPOPT_NOP , +.Dv PF_OSFP_TCPOPT_SACK , +.Dv PF_OSFP_TCPOPT_WSCALE , +.Dv PF_OSFP_TCPOPT_MSS , +or +.Dv PF_OSFP_TCPOPT_TS . +.Pp +The +.Va fp_getnum +member is not used with this ioctl. +.Pp +The structure's slack space must be zeroed for correct operation; +.Xr memset 3 +the whole structure to zero before filling and sending to the kernel. +.It Dv DIOCOSFPGET Fa "struct pf_osfp_ioctl *io" +Get the passive OS fingerprint number +.Va fp_getnum +from the kernel's fingerprint list. +The rest of the structure members will come back filled. +Get the whole list by repeatedly incrementing the +.Va fp_getnum +number until the ioctl returns +.Er EBUSY . +.It Dv DIOCGETSRCNODES Fa "struct pfioc_src_nodes *psn" +.Bd -literal +struct pfioc_src_nodes { + size_t psn_len; + union { + caddr_t psu_buf; + struct pf_src_node *psu_src_nodes; + } psn_u; +#define psn_buf psn_u.psu_buf +#define psn_src_nodes psn_u.psu_src_nodes +}; +.Ed +.Pp +Get the list of source nodes kept by sticky addresses and source +tracking. +The ioctl must be called once with +.Va psn_len +set to 0. +If the ioctl returns without error, +.Va psn_len +will be set to the size of the buffer required to hold all the +.Va pf_src_node +structures held in the table. +A buffer of this size should then be allocated, and a pointer to this buffer +placed in +.Va psn_buf . +The ioctl must then be called again to fill this buffer with the actual +source node data. +After that call, +.Va psn_len +will be set to the length of the buffer actually used. +.It Dv DIOCCLRSRCNODES +Clear the tree of source tracking nodes. +.It Dv DIOCIGETIFACES Fa "struct pfioc_iface *io" +Get the list of interfaces and interface groups known to +.Nm . +All the ioctls that manipulate interfaces +use the same structure described below: +.Bd -literal +struct pfioc_iface { + char pfiio_name[IFNAMSIZ]; + void *pfiio_buffer; + int pfiio_esize; + int pfiio_size; + int pfiio_nzero; + int pfiio_flags; +}; +.Ed +.Pp +If not empty, +.Va pfiio_name +can be used to restrict the search to a specific interface or group. +.Va pfiio_buffer[pfiio_size] +is the user-supplied buffer for returning the data. +On entry, +.Va pfiio_size +contains the number of +.Vt pfi_kif +entries that can fit into the buffer. +The kernel will replace this value by the real number of entries it wants +to return. +.Va pfiio_esize +should be set to +.Li sizeof(struct pfi_kif) . +.Pp +The data is returned in the +.Vt pfi_kif +structure described below: +.Bd -literal +struct pfi_kif { + char pfik_name[IFNAMSIZ]; + RB_ENTRY(pfi_kif) pfik_tree; + u_int64_t pfik_packets[2][2][2]; + u_int64_t pfik_bytes[2][2][2]; + time_t pfik_tzero; + int pfik_flags; + int pfik_flags_new; + void *pfik_ah_cookie; + struct ifnet *pfik_ifp; + struct ifg_group *pfik_group; + int pfik_states; + int pfik_rules; + int pfik_routes; + int pfik_srcnodes; + int pfik_flagrefs; + TAILQ_HEAD(, pfi_dynaddr) pfik_dynaddrs; +}; +.Ed +.It Dv DIOCSETSTATUSIF Fa "struct pfioc_iface *pi" +Specify the interface for which statistics are accumulated. +.It Dv DIOCSETIFFLAG Fa "struct pfioc_iface *io" +Set the user settable flags (described above) of the +.Nm +internal interface description. +The filtering process is the same as for +.Dv DIOCIGETIFACES . +.Bd -literal +#define PFI_IFLAG_SKIP 0x0100 /* skip filtering on interface */ +.Ed +.It Dv DIOCCLRIFFLAG Fa "struct pfioc_iface *io" +Works as +.Dv DIOCSETIFFLAG +above but clears the flags. +.It Dv DIOCKILLSRCNODES Fa "struct pfioc_src_node_kill *psnk" +Explicitly remove source tracking nodes. +.Bd -literal +struct pfioc_src_node_kill { + sa_family_t psnk_af; + struct pf_rule_addr psnk_src; + struct pf_rule_addr psnk_dst; + u_int psnk_killed; +}; +.Ed +.El +.Sh FILES +.Bl -tag -width /dev/pf -compact +.It Pa /dev/pf +packet filtering device. +.El +.Sh EXAMPLES +The following example demonstrates how to use the +.Dv DIOCGETLIMIT +command to show the hard limit of a memory pool used by the packet filter: +.Bd -literal +#include +#include +#include +#include + +#include +#include +#include + +#include +#include +#include +#include +#include + +static const struct { + const char *name; + int index; +} pf_limits[] = { + { "states", PF_LIMIT_STATES }, + { "src-nodes", PF_LIMIT_SRC_NODES }, + { "frags", PF_LIMIT_FRAGS }, + { "tables", PF_LIMIT_TABLES }, + { "table-entries", PF_LIMIT_TABLE_ENTRIES }, + { "anchors", PF_LIMIT_ANCHORS }, + { NULL, 0 } +}; + +void +usage(void) +{ + int i; + + fprintf(stderr, "usage: %s [", getprogname()); + for (i = 0; pf_limits[i].name; i++) + fprintf(stderr, "%s%s", (i > 0 ? "|" : ""), pf_limits[i].name); + fprintf(stderr, "]\en"); + exit(1); +} + +int +main(int argc, char *argv[]) +{ + struct pfioc_limit pl; + int i, dev; + int pool_index = -1; + + if (argc != 2) + usage(); + + for (i = 0; pf_limits[i].name; i++) + if (strcmp(argv[1], pf_limits[i].name) == 0) { + pool_index = pf_limits[i].index; + break; + } + + if (pool_index == -1) { + warnx("no such memory pool: %s", argv[1]); + usage(); + } + + dev = open("/dev/pf", O_RDWR); + if (dev == -1) + err(1, "open(\e"/dev/pf\e") failed"); + + memset(&pl, 0, sizeof(struct pfioc_limit)); + pl.index = pool_index; + + if (ioctl(dev, DIOCGETLIMIT, &pl) == -1) + err(1, "DIOCGETLIMIT"); + + printf("The %s memory pool has ", pf_limits[i].name); + if (pl.limit == UINT_MAX) + printf("unlimited entries.\en"); + else + printf("a hard limit of %u entries.\en", pl.limit); + + return 0; +} +.Ed +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr bridge 4 , +.Xr pflog 4 , +.Xr pflow 4 , +.Xr pfsync 4 , +.Xr pf.conf 5 , +.Xr pfctl 8 +.Sh HISTORY +The +.Nm +packet filtering mechanism first appeared in +.Ox 3.0 . diff --git a/static/openbsd/man4/pflog.4 b/static/openbsd/man4/pflog.4 new file mode 100644 index 00000000..6fb0c845 --- /dev/null +++ b/static/openbsd/man4/pflog.4 @@ -0,0 +1,111 @@ +.\" $OpenBSD: pflog.4,v 1.12 2014/01/21 03:15:46 schwarze Exp $ +.\" +.\" Copyright (c) 2001 Tobias Weingartner +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 21 2014 $ +.Dt PFLOG 4 +.Os +.Sh NAME +.Nm pflog +.Nd packet filter logging interface +.Sh SYNOPSIS +.Cd "pseudo-device pflog" +.Sh DESCRIPTION +The +.Nm pflog +interface is a pseudo-device which makes visible all packets logged by +the packet filter, +.Xr pf 4 . +Logged packets can easily be monitored in real +time by invoking +.Xr tcpdump 8 +on the +.Nm +interface, or stored to disk using +.Xr pflogd 8 . +.Pp +The pflog0 interface is created automatically at boot if both +.Xr pf 4 +and +.Xr pflogd 8 +are enabled; +further instances can be created using +.Xr ifconfig 8 . +.Pp +Each packet retrieved on this interface has a header associated +with it of length +.Dv PFLOG_HDRLEN . +This header documents the address family, interface name, rule +number, reason, action, and direction of the packet that was logged. +This structure, defined in +.In net/if_pflog.h +looks like +.Bd -literal -offset indent +struct pfloghdr { + u_int8_t length; + sa_family_t af; + u_int8_t action; + u_int8_t reason; + char ifname[IFNAMSIZ]; + char ruleset[PFLOG_RULESET_NAME_SIZE]; + u_int32_t rulenr; + u_int32_t subrulenr; + uid_t uid; + pid_t pid; + uid_t rule_uid; + pid_t rule_pid; + u_int8_t dir; + u_int8_t rewritten; + sa_family_t naf; + u_int8_t pad[1]; + struct pf_addr saddr; + struct pf_addr daddr; + u_int16_t sport; + u_int16_t dport; +}; +.Ed +.Sh EXAMPLES +Create a +.Nm +interface +and monitor all packets logged on it: +.Bd -literal -offset indent +# ifconfig pflog1 up +# tcpdump -n -e -ttt -i pflog1 +.Ed +.Sh SEE ALSO +.Xr inet 4 , +.Xr inet6 4 , +.Xr netintro 4 , +.Xr pf 4 , +.Xr ifconfig 8 , +.Xr pflogd 8 , +.Xr tcpdump 8 +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 3.0 . +.\" .Sh BUGS +.\" Anything here? diff --git a/static/openbsd/man4/pflow.4 b/static/openbsd/man4/pflow.4 new file mode 100644 index 00000000..bdcf5e95 --- /dev/null +++ b/static/openbsd/man4/pflow.4 @@ -0,0 +1,136 @@ +.\" $OpenBSD: pflow.4,v 1.19 2014/03/29 11:26:03 florian Exp $ +.\" +.\" Copyright (c) 2008 Henning Brauer +.\" Copyright (c) 2008 Joerg Goltermann +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 29 2014 $ +.Dt PFLOW 4 +.Os +.Sh NAME +.Nm pflow +.Nd kernel interface for pflow data export +.Sh SYNOPSIS +.Cd "pseudo-device pflow" +.Sh DESCRIPTION +The +.Nm +interface is a pseudo-device which exports +.Nm +accounting data from the kernel using +.Xr udp 4 +packets. +.Nm +is compatible with netflow version 5 and IPFIX (10). +The data is extracted from the +.Xr pf 4 +state table. +.Pp +Multiple +.Nm +interfaces can be created at runtime using the +.Ic ifconfig pflow Ns Ar N Ic create +command. +Each interface must be configured with a flow receiver IP address +and a flow receiver port number. +.Pp +Only states created by a rule marked with the +.Ar pflow +keyword are exported by the +.Nm +interface. +.Pp +The +.Nm +interface will attempt to export multiple +.Nm +records in one +UDP packet, but will not hold a record for longer than 30 seconds. +The packet size and thus the maximum number of flows is controlled by the +.Cm mtu +parameter of +.Xr ifconfig 8 . +.Pp +Each packet seen on this interface has one header and a variable number of +flows. +The header indicates the version of the protocol, number of +flows in the packet, a unique sequence number, system time, and an engine +ID and type. +Header and flow structs are defined in +.In net/if_pflow.h . +.Pp +There is a one-to-one correspondence between packets seen by +.Xr bpf 4 +on the +.Nm +interface and packets sent out to the flow receiver. +That is, a packet with 30 flows on +.Nm +means that the same 30 flows were sent out to the receiver. +.Pp +The +.Nm +source and destination addresses are controlled by +.Xr ifconfig 8 . +.Cm flowsrc +is the sender IP address of the UDP packet which can be used +to identify the source of the data on the +.Nm +collector. +.Cm flowdst +defines the collector IP address and the port. +The +.Cm flowdst +IP address and port must be defined to enable the export of flows. +.Pp +For example, the following command sets 10.0.0.1 as the source +and 10.0.0.2:1234 as destination: +.Bd -literal -offset indent +# ifconfig pflow0 flowsrc 10.0.0.1 flowdst 10.0.0.2:1234 +.Ed +.Pp +The protocol is set to IPFIX with the following command: +.Bd -literal -offset indent +# ifconfig pflow0 pflowproto 10 +.Ed +.Sh SEE ALSO +.Xr netintro 4 , +.Xr pf 4 , +.Xr udp 4 , +.Xr pf.conf 5 , +.Xr ifconfig 8 , +.Xr tcpdump 8 +.Sh STANDARDS +.Rs +.%A B. Claise +.%D January 2008 +.%R RFC 5101 +.%T "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information" +.Re +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 4.5 . +.Sh BUGS +A state created by +.Xr pfsync 4 +can have a creation or expiration time before the machine came up. +In this case, +.Nm +pretends such flows were created or expired when the machine came up. +.Pp +The IPFIX implementation is incomplete: +The required transport protocol SCTP is not supported. +Transport over TCP and DTLS protected flow export is also not supported. diff --git a/static/openbsd/man4/pfsync.4 b/static/openbsd/man4/pfsync.4 new file mode 100644 index 00000000..59909deb --- /dev/null +++ b/static/openbsd/man4/pfsync.4 @@ -0,0 +1,260 @@ +.\" $OpenBSD: pfsync.4,v 1.41 2026/04/16 07:42:45 dgl Exp $ +.\" +.\" Copyright (c) 2002 Michael Shalayeff +.\" Copyright (c) 2003-2004 Ryan McBride +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND, +.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: April 16 2026 $ +.Dt PFSYNC 4 +.Os +.Sh NAME +.Nm pfsync +.Nd packet filter state table synchronisation interface +.Sh SYNOPSIS +.Cd "pseudo-device pfsync" +.Sh DESCRIPTION +The +.Nm +interface is a pseudo-device which exposes certain changes to the state +table used by +.Xr pf 4 . +State changes can be viewed by invoking +.Xr tcpdump 8 +on the +.Nm +interface. +If configured with a physical synchronisation interface, +.Nm +will also send state changes out on that interface, +and insert state changes received on that interface from other systems +into the state table. +.Pp +.Nm +traffic must be carried over a secure link, either on a +direct unshared wire or inside an encrypted transport, because +the protocol sends and processes private information and does +not protect itself against disclosure, and by itself has no +message authenticity or integrity protections. +.Pp +By default, all local changes to the state table are exposed via +.Nm . +State changes from packets received by +.Nm +over the network are not rebroadcast. +Updates to states created by a rule marked with the +.Ar no-sync +keyword are ignored by the +.Nm +interface (see +.Xr pf.conf 5 +for details). +.Pp +The +.Nm +interface will attempt to collapse multiple state updates into a single +packet where possible. +The maximum number of times a single state can be updated before a +.Nm +packet will be sent out is controlled by the +.Xr ifconfig 8 +.Ar maxupd +parameter. +The sending out of a +.Nm +packet will be delayed by a maximum of one second. +.Pp +Where more than one firewall might actively handle packets, e.g. with certain +.Xr ospfd 8 , +.Xr bgpd 8 +or +.Xr carp 4 +configurations, it is beneficial to defer transmission of the initial +packet of a connection. +The +.Nm +state insert message is sent immediately; the packet is queued until +either this message is acknowledged by another system, or a timeout has +expired. +This behaviour is enabled with the +.Ar defer +parameter to +.Xr ifconfig 8 . +.Sh NETWORK SYNCHRONISATION +States can be synchronised between two or more firewalls using this +interface, by specifying a synchronisation interface using +.Xr ifconfig 8 . +For example, the following command configures an address on fxp0 and +sets it as the synchronisation interface: +.Bd -literal -offset indent +# ifconfig fxp0 inet 172.19.13.1/28 +# ifconfig pfsync0 syncdev fxp0 +.Ed +.Pp +By default, state change messages are sent out on the synchronisation +interface using IP multicast packets to the 224.0.0.240 group address. +An alternative destination address for +.Nm +packets can be specified using the +.Ic syncpeer +keyword. +.\" This can be used in combination with +.\" .Xr ipsec 4 +.\" to protect the synchronisation traffic. +.\" In such a configuration, the syncdev should be set to the +.\" .Xr enc 4 +.\" interface, as this is where the traffic arrives when it is decapsulated, +.\" e.g.: +.\" .Bd -literal -offset indent +.\" # ifconfig pfsync0 syncpeer 10.0.0.2 syncdev enc0 +.\" .Ed +.Pp +It is important that the pfsync traffic be well secured +as there is no authentication on the protocol and it would +be trivial to spoof packets which create states, bypassing the pf ruleset. +Only run the pfsync protocol on a trusted network \- ideally a network +dedicated to pfsync messages such as a crossover cable between two firewalls. +.\" or specify a peer address and protect the traffic with +.\" .Xr ipsec 4 . +.Pp +.Nm +will increase the +.Xr carp 4 +demotion counter for any interface groups associated with the interface +by 32 during initialisation, and by 1 if the +.Nm +link is down or if a bulk update fails. +.Sh EXAMPLES +.Nm +and +.Xr carp 4 +can be used together to provide automatic failover of a pair of firewalls +configured in parallel. +One firewall will handle all traffic until it dies, is shut down, or is +manually demoted, at which point the second firewall will take over +automatically. +.Pp +Both firewalls in this example have three +.Xr sis 4 +interfaces. +sis0 is the external interface, on the 10.0.0.0/24 subnet; sis1 is the +internal interface, on the 192.168.0.0/24 subnet; and sis2 is the +.Nm +interface, using the 192.168.254.0/24 subnet. +A crossover cable connects the two firewalls via their sis2 interfaces. +On all three interfaces, firewall A uses the .254 address, while firewall B +uses .253. +The interfaces are configured as follows (firewall A unless otherwise +indicated): +.Pp +.Pa /etc/hostname.sis0 : +.Dl inet 10.0.0.254 255.255.255.0 NONE +.Pp +.Pa /etc/hostname.sis1 : +.Dl inet 192.168.0.254 255.255.255.0 NONE +.Pp +.Pa /etc/hostname.sis2 : +.Dl inet 192.168.254.254 255.255.255.0 NONE +.Pp +.Pa /etc/hostname.carp0 : +.Bd -literal -offset indent -compact +inet 10.0.0.1 255.255.255.0 10.0.0.255 \e + vhid 1 carpdev sis0 pass foo +.Ed +.Pp +.Pa /etc/hostname.carp1 : +.Bd -literal -offset indent -compact +inet 192.168.0.1 255.255.255.0 192.168.0.255 \e + vhid 2 carpdev sis1 pass bar +.Ed +.Pp +.Pa /etc/hostname.pfsync0 : +.Bd -literal -offset indent -compact +syncdev sis2 +up +.Ed +.Pp +.Xr pf 4 +must also be configured to allow +.Nm +and +.Xr carp 4 +traffic through. +The following should be added to the top of +.Pa /etc/pf.conf : +.Bd -literal -offset indent +pass quick on { sis2 } proto pfsync keep state (no-sync) +pass on { sis0 sis1 } proto carp keep state (no-sync) +.Ed +.Pp +It is preferable that one firewall handle the forwarding of all the traffic, +therefore the +.Ar advskew +on the backup firewall's +.Xr carp 4 +interfaces should be set to something higher than +the primary's. +For example, if firewall B is the backup, its +.Pa /etc/hostname.carp1 +would look like this: +.Bd -literal -offset indent +inet 192.168.0.1 255.255.255.0 192.168.0.255 \e + vhid 2 pass bar advskew 100 +.Ed +.Pp +The following must also be added to +.Pa /etc/sysctl.conf : +.Bd -literal -offset indent +net.inet.carp.preempt=1 +.Ed +.Sh SEE ALSO +.Xr bpf 4 , +.Xr carp 4 , +.\" .Xr enc 4 , +.Xr inet 4 , +.Xr inet6 4 , +.\" .Xr ipsec 4 , +.Xr netintro 4 , +.Xr pf 4 , +.Xr hostname.if 5 , +.Xr pf.conf 5 , +.Xr protocols 5 , +.Xr ifconfig 8 , +.Xr ifstated 8 , +.Xr tcpdump 8 +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 3.3 . +.Pp +The +.Nm +protocol and kernel implementation were significantly modified between +.Ox 4.4 +and +.Ox 4.5 . +The two protocols are incompatible and will not interoperate. +.Sh BUGS +.Nm +does not currently work with +.Xr ipsec 4 . diff --git a/static/openbsd/man4/pgt.4 b/static/openbsd/man4/pgt.4 new file mode 100644 index 00000000..98ce10de --- /dev/null +++ b/static/openbsd/man4/pgt.4 @@ -0,0 +1,201 @@ +.\" $OpenBSD: pgt.4,v 1.47 2022/01/05 17:39:25 jmc Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt. +.\" Copyright (c) 2006 The DragonFly Project. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in +.\" the documentation and/or other materials provided with the +.\" distribution. +.\" 3. Neither the name of The DragonFly Project nor the names of its +.\" contributors may be used to endorse or promote products derived +.\" from this software without specific, prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +.\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE +.\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT +.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 5 2022 $ +.Dt PGT 4 +.Os +.Sh NAME +.Nm pgt +.Nd Conexant/Intersil Prism GT Full-MAC IEEE 802.11a/b/g wireless network device +.Sh SYNOPSIS +.Cd "pgt* at cardbus?" +.Cd "pgt* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Conexant/Intersil GT-series devices +which can support the Full-MAC firmware, using the ISL3877, +ISL3880, and ISL3890 chips. +The +.Nm +driver will not (yet) work on similar devices using the ISL3886 or +similar chips which use the Soft-MAC firmware. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.It Host AP +In this mode the driver acts as an access point (base station) +for other cards. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use hardware +Wired Equivalent Privacy (WEP). +It is strongly recommended that WEP +not be used as the sole mechanism +to secure wireless communication, +due to serious weaknesses in it. +.Pp +In BSS mode, +the driver supports powersave mode, +which can be enabled via +.Xr ifconfig 8 . +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs a set of firmware files which are loaded when +an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/pgt-isl3877 +.It Pa /etc/firmware/pgt-isl3890 +.El +.Pp +These firmware files are not free because Conexant refuses +to grant distribution rights. +In fact they have rebuffed thousands +of attempts to start a dialogue on this issue. +As a result, even though +.Ox +includes the driver, the firmware files cannot be included and +users have to download these files on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh HARDWARE +The following cards are among those supported by the +.Nm +driver: +.Bl -column "NETGEAR WG511 (Taiwanese, not Chinese)" "ISL3880" "CardBus" -offset 6n +.It Em Card Ta Em Chip Ta Em Bus +.It "3COM 3CRWE154G72" Ta ISL3880 Ta CardBus +.It "D-Link DWL-g650 A1" Ta ISL3890 Ta PCI +.It "I-O Data WN-G54/CB" Ta ISL3890 Ta PCI +.It "I4 Z-Com XG-600" Ta ISL3890 Ta PCI +.It "I4 Z-Com XG-900" Ta ISL3890 Ta PCI +.It "Intersil PRISM Indigo" Ta ISL3877 Ta PCI +.It "Intersil PRISM Duette" Ta ISL3890 Ta PCI +.It "NETGEAR WG511 (Taiwanese, not Chinese)" Ta ISL3890 Ta CardBus +.It "PLANEX GW-DS54G" Ta ISL3890 Ta PCI +.It "SMC EZ Connect g 2.4GHz SMC2802W" Ta ISL3890 Ta PCI +.It "SMC EZ Connect g 2.4GHz SMC2835W-v2" Ta ISL3890 Ta CardBus +.It "SMC 2802Wv2" Ta ISL3890 Ta PCI +.It "Soyo Aerielink" Ta ISL3890 Ta CardBus +.It "ZyXEL ZyAIR G-100" Ta ISL3890 Ta CardBus +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig pgt0 scan +.Pp +The following +.Xr hostname.if 5 +example configures pgt0 to join network +.Dq mynwid , +using WEP key +.Dq mywepkey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +nwid mynwid nwkey mywepkey +inet autoconf +.Ed +.Pp +The following +.Xr hostname.if 5 +example creates a host-based access point on boot: +.Bd -literal -offset indent +mediaopt hostap +nwid mynwid nwkey mywepkey +inet 192.168.1.1 255.255.255.0 +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr cardbus 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr hostapd 8 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was originally written for +.Fx +by +.An Brian Fundakowski , +and then rewritten for +.Ox +by +.An Marcus Glocker +and +.An Claudio Jeker . +.Sh CAVEATS +Host AP mode doesn't support power saving. +Clients attempting to use power saving mode may experience significant +packet loss (disabling power saving on the client will fix this). diff --git a/static/openbsd/man4/piixpm.4 b/static/openbsd/man4/piixpm.4 new file mode 100644 index 00000000..1b47397d --- /dev/null +++ b/static/openbsd/man4/piixpm.4 @@ -0,0 +1,72 @@ +.\" $OpenBSD: piixpm.4,v 1.20 2019/12/16 21:46:44 claudio Exp $ +.\" +.\" Copyright (c) 2004, 2005 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 16 2019 $ +.Dt PIIXPM 4 +.Os +.Sh NAME +.Nm piixpm +.Nd Intel PIIX SMBus controller +.Sh SYNOPSIS +.Cd "piixpm* at pci?" +.Cd "iic* at piixpm?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Intel PIIX and compatible Power Management +controller. +Only the SMBus host interface is supported and can be used with the +.Xr iic 4 +framework. +.Pp +Supported chipsets: +.Pp +.Bl -bullet -compact -offset indent +.It +AMD Hudson-2, FCH (KERNCZ) +.It +ATI SB200, SB300, SB400, SB600, SB700, SB800 +.It +Intel 82371AB (PIIX4), 82440MX +.It +ServerWorks OSB4, CSB5, CSB6, HT-1000, HT-1100 +.It +SMSC Victory66 +.El +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.7 +to provide support for the power management (ACPI) timer. +In +.Ox 3.9 , +power management support was dropped in favor of +.Xr acpitimer 4 +and SMBus functionality was added. +.Sh AUTHORS +.An -nosplit +The current +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . +.Sh BUGS +The driver doesn't support I2C commands with a data buffer size of more +than 2 bytes. diff --git a/static/openbsd/man4/pijuice.4 b/static/openbsd/man4/pijuice.4 new file mode 100644 index 00000000..3d2ca754 --- /dev/null +++ b/static/openbsd/man4/pijuice.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: pijuice.4,v 1.4 2022/10/24 09:23:27 jsg Exp $ +.\" +.\" Copyright (c) 2022 Marcus Glocker +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 24 2022 $ +.Dt PIJUICE 4 +.Os +.Sh NAME +.Nm pijuice +.Nd PiJuice HAT UPS +.Sh SYNOPSIS +.Cd "pijuice* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PiJuice HAT, +an uninterruptible power supply for the Raspberry Pi. +The integrated STM32F030CCT6 micro controller provides access through the I2C +bus to several battery status values. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr maxrtc 4 , +.Xr apm 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marcus Glocker Aq Mt mglocker@openbsd.org . +.Sh CAVEATS +The PiJuice HAT EEPROM currently doesn't contain the device tree information +to match and attach this device. +It requires a custom device tree blob overlay which gets loaded during the +bootstrapping process. diff --git a/static/openbsd/man4/pinctrl.4 b/static/openbsd/man4/pinctrl.4 new file mode 100644 index 00000000..9c0e3744 --- /dev/null +++ b/static/openbsd/man4/pinctrl.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: pinctrl.4,v 1.2 2018/08/26 20:36:57 jmc Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 26 2018 $ +.Dt PINCTRL 4 +.Os +.Sh NAME +.Nm pinctrl +.Nd generic pin multiplexing +.Sh SYNOPSIS +.Cd "pinctrl* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver uses pin control data from the device tree to select one of +multiple possible roles available for pins on various SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/pipex.4 b/static/openbsd/man4/pipex.4 new file mode 100644 index 00000000..4d7b357a --- /dev/null +++ b/static/openbsd/man4/pipex.4 @@ -0,0 +1,269 @@ +.\" $OpenBSD: pipex.4,v 1.15 2022/07/12 08:58:53 mvs Exp $ +.\" +.\" Copyright (c) 2012 YASUOKA Masahiko +.\" Copyright (c) 2010 SUENAGA Hiroki +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 12 2022 $ +.Dt PIPEX 4 +.Os +.Sh NAME +.Nm pipex +.Nd PPP IP EXtension to handle IP/PPP frames in-kernel +.Sh SYNOPSIS +.Cd "option PIPEX" +.Pp +.In sys/types.h +.In sys/socket.h +.In sys/ioctl.h +.In net/if.h +.In net/pipex.h +.Sh DESCRIPTION +.Nm +is used with +.Xr pppac 4 +and +.Xr pppx 4 , +and handles PPP frames and forwards IP packets in-kernel. +It accelerates the performance of packet forwarding, because it reduces +copying of packets between kernel and userland. +.Nm +is disabled by default. +To enable it, set +.Va net.pipex.enable +to +.Sq 1 +using +.Xr sysctl 8 . +.Pp +.Nm +adds some extensions to the +.Xr ioctl 2 +requests to +.Xr pppac 4 +or +.Xr pppx 4 +devices. +The added requests are as follows: +.Bl -tag -width Ds +.It Dv PIPEXASESSION Fa "struct pipex_session_req *" +Add a new PPP session to be handled by +.Nm . +The status of the session is passed as a +.Vt pipex_session_req +structure. +The +.Vt pipex_session_req +structure has the following definition: +.Bd -literal +struct pipex_session_req { + int pr_protocol; /* tunnel protocol */ +#define PIPEX_PROTO_L2TP 1 /* protocol L2TP */ +#define PIPEX_PROTO_PPTP 2 /* protocol PPTP */ +#define PIPEX_PROTO_PPPOE 3 /* protocol PPPoE */ + uint16_t pr_session_id; /* session-id */ + uint16_t pr_peer_session_id; /* peer's session-id */ + uint32_t pr_ppp_flags; /* ppp configuration flags */ +#define PIPEX_PPP_ACFC_ACCEPTED 0x0001 /* ACFC accepted */ +#define PIPEX_PPP_PFC_ACCEPTED 0x0002 /* PFC accepted */ +#define PIPEX_PPP_ACFC_ENABLED 0x0004 /* ACFC enabled */ +#define PIPEX_PPP_PFC_ENABLED 0x0008 /* PFC enabled */ +#define PIPEX_PPP_MPPE_ACCEPTED 0x0010 /* MPPE accepted */ +#define PIPEX_PPP_MPPE_ENABLED 0x0020 /* MPPE enabled */ +#define PIPEX_PPP_MPPE_REQUIRED 0x0040 /* MPPE is required */ +#define PIPEX_PPP_HAS_ACF 0x0080 /* has ACF */ +#define PIPEX_PPP_ADJUST_TCPMSS 0x0100 /* do tcpmss adjustment */ +#define PIPEX_PPP_INGRESS_FILTER 0x0200 /* do ingress filter */ + int8_t pr_ccp_id; /* ccp current packet id */ + int pr_ppp_id; /* ppp id. */ + uint16_t pr_peer_mru; /* peer's mru */ + uint16_t pr_timeout_sec; /* idle timer */ + + struct in_addr pr_ip_srcaddr; /* local IP address */ + struct in_addr pr_ip_address; /* framed IP address */ + struct in_addr pr_ip_netmask; /* framed IP netmask */ + struct sockaddr_in6 pr_ip6_address; /* framed IPv6 address */ + int pr_ip6_prefixlen; /* framed IPv6 prefix + length */ + union { + struct { + uint32_t snd_nxt; /* send next */ + uint32_t rcv_nxt; /* receive next */ + uint32_t snd_una; /* unacked */ + uint32_t rcv_acked; /* recv acked */ + int winsz; /* window size */ + int maxwinsz; /* max window size */ + int peer_maxwinsz; /* peer's max window size */ + } pptp; + struct { + /* select protocol options: 1 for enable */ + uint32_t option_flags; + #define PIPEX_L2TP_USE_SEQUENCING 0x00000001 + /* use sequence number + on L2TP data messages */ + + uint16_t tunnel_id; /* our tunnel-id */ + uint16_t peer_tunnel_id; /* peer's tunnel-id */ + uint32_t ns_nxt; /* send next */ + uint32_t nr_nxt; /* receive next */ + uint32_t ns_una; /* unacked */ + uint32_t nr_acked; /* recv acked */ + uint32_t ipsecflowinfo; /* IPsec flow id for NAT-T */ + } l2tp; + struct { + char over_ifname[IF_NAMESIZE]; + /* ethernet ifname */ + } pppoe; + } pr_proto; + struct sockaddr_storage pr_peer_address; + /* peer address of tunnel */ + struct sockaddr_storage pr_local_address; + /* our address of tunnel */ + struct pipex_mppe_req pr_mppe_recv; + /* mppe key for receive */ + struct pipex_mppe_req pr_mppe_send; + /* mppe key for send */ +}; +.Ed +.Pp +The +.Vt pipex_mppe_req +structure that was used by +.Va pr_mppe_recv +and +.Va pr_mppe_send +has the following definition: +.Bd -literal +struct pipex_mppe_req { + int16_t stateless; /* mppe key mode. + 1 for stateless */ + int16_t keylenbits; /* mppe key length(in bits)*/ + u_char master_key[PIPEX_MPPE_KEYLEN]; + /* mppe master key */ +}; +.Ed +.It Dv PIPEXDSESSION Fa "struct pipex_session_close_req *" +Delete the specified session from the kernel. +Specify the session using a +.Vt pipex_session_close_req +structure, which has the following definition: +.Bd -literal +struct pipex_session_close_req { + int psr_protocol; /* tunnel protocol */ + uint16_t psr_session_id; /* session-id */ + struct pipex_statistics psr_stat; /* statistics */ +}; +.Ed +.Pp +The +.Va psr_protocol +and +.Va psr_session_id +fields used to specify the session are mandatory. +On successful return, the +.Va psr_stat +field is filled by the kernel. +See +.Dv PIPEXGSTAT +section for a description of the +.Vt pipex_statistics +structure. +.It Dv PIPEXGSTAT Fa "struct pipex_session_stat_req *" +Get statistics for the specified session. +Specify the session using a +.Vt pipex_session_stat_req +structure, which has the following definition: +.Bd -literal +struct pipex_session_stat_req { + int psr_protocol; /* tunnel protocol */ + uint16_t psr_session_id; /* session-id */ + struct pipex_statistics psr_stat; /* statistics */ +}; +.Ed +.Pp +The +.Va psr_protocol +and +.Va psr_session_id +fields used to specify the session are mandatory. +On successful return, the +.Va psr_stat +field is filled by the kernel. +The +.Vt pipex_statistics +structure has the following definition: +.Bd -literal +struct pipex_statistics { + uint32_t ipackets; /* packets received from tunnel */ + uint32_t ierrors; /* error packets received from tunnel */ + uint64_t ibytes; /* number of received bytes from tunnel */ + uint32_t opackets; /* packets sent to tunnel */ + uint32_t oerrors; /* error packets on sending to tunnel */ + uint64_t obytes; /* number of sent bytes to tunnel */ + + uint32_t idle_time; /* idle time in seconds */ +}; +.Ed +.It Dv PIPEXGCLOSED Fa "struct pipex_session_list_req *" +Get a list of closed sessions. +.Nm +reserves closed sessions for 30 seconds +for userland programs to get statistical information. +On successful return, +the +.Vt pipex_session_list_req +structure is filled by the kernel. +The structure has the following definition. +.Bd -literal +struct pipex_session_list_req { + uint8_t plr_flags; +#define PIPEX_LISTREQ_MORE 0x01 /* has more session */ + int plr_ppp_id_count; /* count of PPP id */ + int plr_ppp_id[PIPEX_MAX_LISTREQ]; /* PPP id */ +}; +.Ed +.It Dv PIPEXSIFDESCR Fa "struct pipex_session_descr_req *" +Set the +.Xr pppx 4 +interface's description of the session. +This command doesn't work on +.Xr pppac 4 +devices. +Specify the session and its description using a +.Vt pipex_session_descr_req +structure, which has the following definition: +.Bd -literal +struct pipex_session_descr_req { + int pdr_protocol; /* tunnel protocol */ + uint16_t pdr_session_id; /* session-id */ + char pdr_descr[IFDESCRSIZE]; /* description */ +}; +.Ed +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr pppac 4 , +.Xr pppx 4 , +.Xr npppd 8 , +.Xr sysctl 8 +.Sh AUTHORS +The +.Nm +was written by +.An Internet Initiative Japan Inc . +.Sh BUGS +.Xr pppx 4 +does not allow sessions with +.Ic pr_timeout_sec +set to any value other than 0. diff --git a/static/openbsd/man4/plgpio.4 b/static/openbsd/man4/plgpio.4 new file mode 100644 index 00000000..d3db97f6 --- /dev/null +++ b/static/openbsd/man4/plgpio.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: plgpio.4,v 1.1 2018/08/26 18:10:16 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 26 2018 $ +.Dt PLGPIO 4 +.Os +.Sh NAME +.Nm plgpio +.Nd ARM PrimeCell PL061 GPIO controller +.Sh SYNOPSIS +.Cd "plgpio* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the ARM PrimeCell PL061 GPIO controller. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 +.Rs +.%T ARM PrimeCell General Purpose Input/Output (PL011) Technical Reference Manual +.%V ARM DDI 0190 +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/plrtc.4 b/static/openbsd/man4/plrtc.4 new file mode 100644 index 00000000..93ab8a23 --- /dev/null +++ b/static/openbsd/man4/plrtc.4 @@ -0,0 +1,37 @@ +.\" $OpenBSD: plrtc.4,v 1.2 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" Copyright (c) 2015 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt PLRTC 4 +.Os +.Sh NAME +.Nm plrtc +.Nd ARM PrimeCell PL031 real-time clock +.Sh SYNOPSIS +.Cd "plrtc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the ARM PrimeCell PL031 real-time clock. +.Rs +.%T ARM PrimeCell Real Time Clock (PL031) Technical Reference Manual +.%V ARM DDI 0224 +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.8 . diff --git a/static/openbsd/man4/pluart.4 b/static/openbsd/man4/pluart.4 new file mode 100644 index 00000000..a5cc8448 --- /dev/null +++ b/static/openbsd/man4/pluart.4 @@ -0,0 +1,40 @@ +.\" $OpenBSD: pluart.4,v 1.2 2018/07/02 15:39:33 kettenis Exp $ +.\" +.\" Copyright (c) 2015 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 2 2018 $ +.Dt PLUART 4 +.Os +.Sh NAME +.Nm pluart +.Nd ARM PrimeCell PL011 UART +.Sh SYNOPSIS +.Cd "pluart* at acpi?" +.Cd "pluart* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the ARM PrimeCell PL011 UART. +.Sh SEE ALSO +.Xr tty 4 +.Rs +.%T ARM PrimeCell UART (PL011) Technical Reference Manual +.%V ARM DDI 0183 +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.8 . diff --git a/static/openbsd/man4/pms.4 b/static/openbsd/man4/pms.4 new file mode 100644 index 00000000..6902e98a --- /dev/null +++ b/static/openbsd/man4/pms.4 @@ -0,0 +1,74 @@ +.\" $OpenBSD: pms.4,v 1.13 2021/05/01 16:11:09 visa Exp $ +.\" $NetBSD: pms.4,v 1.4 2000/07/05 15:45:34 msaitoh Exp $ +.\" +.\" Copyright (c) 1993 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed for the +.\" NetBSD Project. See http://www.netbsd.org/ for +.\" information about NetBSD. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" <> +.\" +.Dd $Mdocdate: May 1 2021 $ +.Dt PMS 4 +.Os +.Sh NAME +.Nm pms +.Nd PS/2 auxiliary port mouse driver +.Sh SYNOPSIS +.Cd "pms* at pckbc?" +.Cd "pms* at gsckbc?" Pq "hppa" +.Cd "wsmouse* at pms? mux 0" +.Sh DESCRIPTION +The +.Nm pms +drivers provide an interface to PS/2 auxiliary port mice within the +.Xr wscons 4 +framework. +Parent device in terms of the autoconfiguration framework can be +either +.Xr gsckbc 4 , +the PS/2 input port controller found on hppa machines, or +.Xr pckbc 4 , +the standard PC keyboard controller found on most other machines. +.Dq pms +is a generic driver which supports mice using common variants of the PS/2 +protocol, including wheel mice of the +.Dq IntelliMouse +breed. +Wheel movements are mapped to a third (z-) axis. +Mouse related data are accessed by +.Xr wsmouse 4 +devices. +.Sh SEE ALSO +.Xr gsckbc 4 , +.Xr intro 4 , +.Xr lms 4 , +.Xr mms 4 , +.Xr pckbc 4 , +.Xr ums 4 , +.Xr wsmouse 4 diff --git a/static/openbsd/man4/ppb.4 b/static/openbsd/man4/ppb.4 new file mode 100644 index 00000000..5bdaf6fa --- /dev/null +++ b/static/openbsd/man4/ppb.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: ppb.4,v 1.10 2015/06/03 15:43:55 mpi Exp $ +.\" +.\" Copyright (c) 2003 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 3 2015 $ +.Dt PPB 4 +.Os +.Sh NAME +.Nm ppb +.Nd PCI-PCI bridge +.Sh SYNOPSIS +.Cd "ppb* at pci?" +.Cd "pci* at ppb?" +.Sh DESCRIPTION +The +.Nm +driver supports generic PCI-PCI bridges, +including PCI expansion backplanes. +These devices are largely transparent and provide no user accessible +entry points. +.Sh SEE ALSO +.Xr pci 4 diff --git a/static/openbsd/man4/ppp.4 b/static/openbsd/man4/ppp.4 new file mode 100644 index 00000000..a74a8706 --- /dev/null +++ b/static/openbsd/man4/ppp.4 @@ -0,0 +1,82 @@ +.\" $OpenBSD: ppp.4,v 1.17 2024/02/28 16:08:34 denis Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" From: @(#)lo.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: February 28 2024 $ +.Dt PPP 4 +.Os +.Sh NAME +.Nm ppp +.Nd Point-to-Point Protocol network interface +.Sh SYNOPSIS +.Cd "pseudo-device ppp" +.Sh DESCRIPTION +The +.Nm +interface allows serial lines to be used as network interfaces using the +.Em Point-to-Point Protocol +(PPP). +.Pp +A +.Nm +interface can be created at runtime using the +.Ic ifconfig ppp Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It ppp0: afX not supported +The interface was handed +a message with addresses formatted in an unsuitable address +family; the packet was dropped. +.El +.Sh SEE ALSO +.Xr inet 4 , +.Xr pppoe 4 , +.Xr pppx 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 , +.Xr pppd 8 , +.Xr pppstats 8 +.Sh STANDARDS +.Rs +.%A W. Simpson +.%D July 1994 +.%R RFC 1661 +.%T The Point-to-Point Protocol (PPP) +.Re +.Sh HISTORY +The +.Nm +device appeared in +.Ox 1.2 . diff --git a/static/openbsd/man4/pppoe.4 b/static/openbsd/man4/pppoe.4 new file mode 100644 index 00000000..ca0cd209 --- /dev/null +++ b/static/openbsd/man4/pppoe.4 @@ -0,0 +1,248 @@ +.\" $OpenBSD: pppoe.4,v 1.36 2022/05/27 15:45:02 jmc Exp $ +.\" $NetBSD: pppoe.4,v 1.26 2003/10/02 07:06:36 wiz Exp $ +.\" +.\" Copyright (c) 2002 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Martin Husemann . +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 27 2022 $ +.Dt PPPOE 4 +.Os +.Sh NAME +.Nm pppoe +.Nd PPP Over Ethernet protocol network interface +.Sh SYNOPSIS +.Cd "pseudo-device pppoe" +.Sh DESCRIPTION +The +.Nm +interface encapsulates +.Em Point-to-Point Protocol (PPP) +packets inside Ethernet frames as defined by RFC 2516. +.Pp +This is often used to connect a router via a DSL modem to +an access concentrator. +The +.Nm +interface does not by itself transmit or receive frames, +but needs an Ethernet interface to do so. +This Ethernet interface is connected to the +.Nm +interface via +.Xr ifconfig 8 . +The Ethernet interface needs to be marked UP, but does not need to have an +IP address. +.Pp +There are two basic modes of operation, controlled via the +.Em link1 +switch. +The default mode, +.Em link1 +not being set, tries to keep the configured session open all the +time. +If the session is disconnected, a new connection attempt is started +immediately. +The +.Dq dial on demand +mode, selected by setting +.Em link1 , +only establishes a connection when data is being sent to the interface. +.Pp +Before a +.Nm +interface is usable, it needs to be configured. +The following steps are necessary: +.Bl -bullet +.It +Create the interface. +.It +Connect an Ethernet interface. +This interface is used for the physical communication. +As noted above it must be marked UP, but need not have an IP address. +.It +Configure authentication. +The PPP session needs to identify the client to the peer. +For more details on the available options see +.Xr ifconfig 8 . +.It +If using IPv6, configure a link-local address. +.El +.Pp +This all is typically accomplished using an +.Pa /etc/hostname.pppoe0 +file. +A typical file looks like this: +.Bd -literal -offset indent +inet 0.0.0.0 255.255.255.255 NONE \e + pppoedev em0 authproto pap \e + authname 'testcaller' authkey 'donttell' up +dest 0.0.0.1 +inet6 eui64 +!/sbin/route add default -ifp pppoe0 0.0.0.1 +!/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0 +.Ed +.Pp +The physical interface must also be marked +.Ql up : +.Bd -literal -offset indent +# echo "up" > /etc/hostname.em0 +.Ed +.Pp +Since this is a PPP interface, the addresses assigned to the interface +may change during PPP negotiation. +In the above example, 0.0.0.0 and 0.0.0.1 serve as placeholders for +dynamic address configuration. +.Pp +If the local address is set to wildcard address 0.0.0.0, it will +be changed to an address suggested by the peer. +.Pp +If the destination address is set to a wildcard address in the range +from 0.0.0.1 to 0.0.0.255, it will be changed to an address suggested +by the peer, and if a default route which uses this interface exists +the gateway will be changed to the suggested address as well. +.Pp +Otherwise, PPP negotiation will only agree to exactly the IPv4 addresses +which are configured on the interface. +.Sh KERNEL OPTIONS +.Nm +does not interfere with other PPPoE implementations +running on the same machine. +However under some circumstances +(such as after a crash or power failure) +the peer device might initially refuse to +reestablish a new PPPoE connection +because there is already an open session. +This would be indicated by the client sending a high number of PADI packets +before successfully connecting. +The +.Nm +driver can be told to kill all unknown PPPoE sessions +by sending a PADT packet to explicitly terminate the old session. +Add the following to the kernel config file: +.Pp +.Dl option PPPOE_TERM_UNKNOWN_SESSIONS +.Sh PPPOE AND MTU/MSS +PPPoE has an 8-byte header. +When run over a network interface with the +standard Ethernet maximum transmission unit (MTU) of 1500 bytes, +this reduces the maximum available MTU to 1492. +.Nm +sets the default MTU to this value. +Unfortunately issues can occur when the path between +the two endpoints of a TCP connection are not able to carry +same sized packets, +leading to possible packet fragmentation and sometimes packet loss. +In that case the maximum packet size can be set using the +.Cm max-mss +option in +.Xr pf.conf 5 . +For example: +.Pp +.Dl match on pppoe0 scrub (max-mss 1440) +.Sh MTU/MSS NEGOTIATION +When using a PPPoE device configured for a higher MTU ("jumbo frames"), +the MTU for the +.Nm +device can also be raised. +In this case +.Nm +attempts to negotiate the higher size with the other PPPoE endpoint +using the RFC 4638 protocol. +This can allow standard Ethernet packet sizes (1500 bytes) +to be carried over PPPoE. +For example, in +.Pa /etc/hostname.pppoe0 : +.Bd -literal -offset indent +inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \e + pppoedev em0 authproto pap \e + authname 'testcaller' authkey 'donttell' up +dest 0.0.0.1 +!/sbin/route add default -ifp pppoe0 0.0.0.1 +.Ed +.Pp +The physical interface would also have to be configured correspondingly: +.Bd -literal -offset indent +# echo "up mtu 1508" > /etc/hostname.em0 +.Ed +.Pp +However, RFC 4638 negotiation only takes into account the MTU configured +on the endpoints, not the maximum MTU supported on the path between them. +If the path cannot pass the larger Ethernet frames, negotiation will succeed +but the larger frames will be dropped. +For this reason it is important to test the connection with large packets +when enabling a higher MTU. +.Sh SEE ALSO +.Xr sppp 4 , +.Xr hostname.if 5 , +.Xr pf.conf 5 , +.Xr ifconfig 8 +.Sh STANDARDS +.Rs +.%A L. Mamakos +.%A K. Lidl +.%A J. Evarts +.%A D. Carrel +.%A D. Simone +.%A R. Wheeler +.%D February 1999 +.%R RFC 2516 +.%T A Method for Transmitting PPP Over Ethernet (PPPoE) +.Re +.Pp +.Rs +.%A P. Arberg +.%A D. Kourkouzelis +.%A M. Duckett +.%A T. Anschutz +.%A J. Moisand +.%D September 2006 +.%R RFC 4638 +.%T Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE) +.Re +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 3.7 . +.Sh BUGS +This implementation is client side only. +.Pp +It is important to specify +.Dq Li netmask 255.255.255.255 +to +.Xr ifconfig 8 . +If the netmask is unspecified, it will be set to 8 when 0.0.0.0 is +configured to the interface, and it will persist after negotiation. +.Pp +The presence of a +.Xr mygate 5 +file will interfere with the routing table. +Make sure this file is either empty or does not exist. +.Pp +Two +.Nm +interfaces configured with the same wildcard destination address +cannot share a routing table. diff --git a/static/openbsd/man4/pppx.4 b/static/openbsd/man4/pppx.4 new file mode 100644 index 00000000..f6ee0acd --- /dev/null +++ b/static/openbsd/man4/pppx.4 @@ -0,0 +1,86 @@ +.\" $OpenBSD: pppx.4,v 1.5 2020/01/23 00:31:40 dlg Exp $ +.\" +.\" Copyright (c) 2013 YASUOKA Masahiko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 23 2020 $ +.Dt PPPX 4 +.Os +.Sh NAME +.Nm pppx , +.Nm pppac +.Nd PPP multiplexer device +.Sh SYNOPSIS +.Cd "pseudo-device pppx" +.Pp +.In sys/socket.h +.In sys/ioctl.h +.In net/pipex.h +.Sh DESCRIPTION +The +.Nm pppx +and +.Nm pppac +drivers works with the +.Xr npppd 8 +daemon to provide network interfaces for Point-to-Point Protocol (PPP) +sessions by request from the daemon. +.Nm pppx +operates by allocating a network interface for each PPP +session. +.Nm pppac +concentrates multiple PPP sessions on a single network interface. +The interfaces also work with +.Xr pipex 4 +to accelerate the performance of data packet forwarding, +and supports ioctls which are added by +.Xr pipex 4 . +.Pp +To use +.Nm pppx +or +.Nm pppac +from +.Xr npppd 8 +the administrator needs to configure the interface configuration in +.Xr npppd.conf 5 . +Also the administrator needs to enable +.Xr pipex 4 +by setting +.Va net.pipex.enable +to +.Sq 1 +using +.Xr sysctl 8 . +.Sh SEE ALSO +.Xr inet 4 , +.Xr inet6 4 , +.Xr pipex 4 , +.Xr hostname.if 5 , +.Xr npppd.conf 5 , +.Xr netstart 8 , +.Xr npppd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm pppx +driver first appeared in +.Ox 5.3 . +The +.Nm pppac +interface driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org +.An Claudio Jeker Aq Mt claudio@openbsd.org diff --git a/static/openbsd/man4/psci.4 b/static/openbsd/man4/psci.4 new file mode 100644 index 00000000..e96ff1e8 --- /dev/null +++ b/static/openbsd/man4/psci.4 @@ -0,0 +1,34 @@ +.\" $OpenBSD: psci.4,v 1.1 2018/03/31 03:22:34 jsg Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2018 $ +.Dt PSCI 4 +.Os +.Sh NAME +.Nm psci +.Nd Power State Coordination Interface +.Sh SYNOPSIS +.Cd "psci* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver handles system reset and power down for systems that conform +to the ARM Power State Coordination Interface specification. +.Sh SEE ALSO +.Rs +.%T Power State Coordination Interface (PSCI) specification +.%N ARM DEN 0022C +.Re diff --git a/static/openbsd/man4/psp.4 b/static/openbsd/man4/psp.4 new file mode 100644 index 00000000..9682d84d --- /dev/null +++ b/static/openbsd/man4/psp.4 @@ -0,0 +1,373 @@ +.\" $OpenBSD: psp.4,v 1.4 2024/09/17 04:12:57 jsg Exp $ +.\" +.\" Copyright (c) 2024 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 17 2024 $ +.Dt PSP 4 +.Os +.Sh NAME +.Nm psp +.Nd AMD Platform Security Processor +.Sh SYNOPSIS +.Cd "psp* at ccp?" +.Sh DESCRIPTION +The +.Nm +driver provides an interface to the AMD Platform Security Processor. +The interface can be accessed through the +.Xr ioctl 2 +interface exposed by +.Pa /dev/psp . +.Pp +.Xr vmd 8 +uses +.Nm +to configure and launch SEV-enabled guests. +.Sh IOCTL INTERFACE +The +.Xr ioctl 2 +command codes below are defined in +.In dev/ic/pspvar.h . +.Bl -tag -width xxxxxx +.It Dv PSP_IOC_GET_PSTATUS Fa "struct psp_platform_status *pspst" +Collect the current status of the platform. +.Bd -literal +struct psp_platform_status { + /* Output parameters from PSP_CMD_PLATFORMSTATUS */ + uint8_t api_major; + uint8_t api_minor; + uint8_t state; + uint8_t owner; + uint32_t cfges_build; + uint32_t guest_count; +} __packed; +.Ed +.Pp +.Va api_major +and +.Va api_minor +indicate the PSP firmware version. +.Pp +The current platform state is indicated by +.Va state . +The following values are defined: +.Bl -tag -width PSP_PSTATE_WORKING -compact +.It PSP_PSTATE_UNINIT +The platform is uninitialized. +.It PSP_PSTATE_INIT +The platform is initialized but not managing any guests. +.It PSP_PSTATE_WORKING +The platform is initialized and currently managing guests. +.El +.Pp +.Va owner +indicates whether the platform is self-owned or externally owned. +.Pp +Bit 0 of +.Va cfgs_build +indicates whether SEV-ES is configured on the platform or not. +Bits 31:24 indicate the firmware build ID. +.Pp +.Va guest_count +indicates the number of valid guests currently maintained by the +firmware. +.It Dv PSP_IOC_DF_FLUSH +This command flushes all write buffers of the CPU's data fabric. +It must be invoked after deactivating one or more guests with +.Dv PSP_IOC_DEACTIVATE . +.It Dv PSP_IOC_DECOMMISSION Fa "struct psp_decommission *pspdec" +Deletes all guest context of the guest identified by +.Va handle . +.Bd -literal +struct psp_decommission { + /* Input parameter for PSP_CMD_DECOMMISSION */ + uint32_t handle; +} __packed; +.Ed +.It Dv PSP_IOC_GET_GSTATUS +Retrieves status information about an SEV-enabled guest identified by +.Va handle . +.Bd -literal +struct psp_guest_status { + /* Input parameter for PSP_CMD_GUESTSTATUS */ + uint32_t handle; + + /* Output parameters from PSP_CMD_GUESTSTATUS */ + uint32_t policy; + uint32_t asid; + uint8_t state; +} __packed; +.Ed +.Pp +.Va policy +indicates the policy used for this guest. +.Va asid +indicates the guest's address space identifier (ASID). +.Pp +The state of the guest is indicated by +.Va state . +The following values are defined: +.Bl -tag -width PSP_GSTATE_RUNNING -compact +.It PSP_GSTATE_UNINIT +The guest is uninitialized. +.It PSP_GSTATE_LUPDATE +The guest is currently being launched and plaintext data is imported. +.It PSP_GSTATE_LSECRET +The guest is currently being launched and ciphertext data is imported. +.It PSP_GSTATE_RUNNING +The guest is fully launched. +.It PSP_GSTATE_SUPDATE +The guest is migrated to another machine. +.It PSP_GSTATE_RUPDATE +The guest is migrated from another machine. +.It PSP_GSTATE_SENT +Thee guest has bin migrated to another machine. +.El +.It Dv PSP_IOC_LAUNCH_START +This command encrypts a guest's memory. +.Bd -literal +struct psp_launch_start { + /* Input/Output parameter for PSP_CMD_LAUNCH_START */ + uint32_t handle; + + /* Input parameters for PSP_CMD_LAUNCH_START */ + uint32_t policy; + + /* The following input parameters are not used yet */ + uint64_t dh_cert_paddr; + uint32_t dh_cert_len; + uint32_t reserved; + uint64_t session_paddr; + uint32_t session_len; +} __packed; +.Ed +.Pp +If +.Va handle +is zero, a new key is created. +A unique handle is assigned to the guest and returned in +.Va handle . +.Pp +.Va policy +specifies the policy used for that guest. +.Pp +.Va dh_cert_paddr , +.Va dh_cert len , +.Va session_paddr +and +.Va session_len +are currently not used. +.It Dv PSP_IOC_LAUNCH_UPDATE_DATA +This command encrypts data of the guest identified by +.Va handle . +.Bd -literal +struct psp_launch_update_data { + /* Input parameters for PSP_CMD_LAUNCH_UPDATE_DATA */ + uint32_t handle; + uint32_t reserved; + uint64_t paddr; + uint32_t length; +} __packed; +.Ed +.Pp +.Va paddr +and +.Va length +specify the address and length of the data to be encrypted. +Both values must be a multiple of 16 bytes. +.It Dv PSP_IOC_LAUNCH_MEASURE +This commands generates a measurement of the guest's memory. +The guest is identified by +.Va handle . +.Bd -literal +struct psp_measure { + /* Output buffer for PSP_CMD_LAUNCH_MEASURE */ + uint8_t measure[32]; + uint8_t measure_nonce[16]; +} __packed; + +struct psp_launch_measure { + /* Input parameters for PSP_CMD_LAUNCH_MEASURE */ + uint32_t handle; + uint32_t reserved; + uint64_t measure_paddr; + + /* Input/output parameter for PSP_CMD_LAUNCH_MEASURE */ + uint32_t measure_len; + uint32_t padding; + + /* Output buffer from PSP_CMD_LAUNCH_MEASURE */ + struct psp_measure psp_measure; /* 64bit aligned */ +#define measure psp_measure.measure +#define measure_nonce psp_measure.measure_nonce +} __packed; +.Ed +.Pp +.Va measure_paddr +is currently not used and +.Va measure_len +must always be +.Li sizeof(struct psp_measure) . +.Pp +.Va psp_measure +contains the buffers +.Va measure +and +.Va measure_nonce . +These contain the measurement and nonce generated by the PSP. +.It Dv PSP_IOC_LAUNCH_FINISH +This command finalizes the launch of the guest identified by +.Va handle . +.Bd -literal +struct psp_launch_finish { + /* Input parameter for PSP_CMD_LAUNCH_FINISH */ + uint32_t handle; +} __packed; +.Ed +.It Dv PSP_IOC_ATTESTATION +This command generates an attestation report signed by the PSP with +a platform specific key. +.Bd -literal +struct psp_report { + /* Output buffer for PSP_CMD_ATTESTATION */ + uint8_t report_nonce[16]; + uint8_t report_launch_digest[32]; + uint32_t report_policy; + uint32_t report_sig_usage; + uint32_t report_sig_algo; + uint32_t reserved2; + uint8_t report_sig1[144]; +} __packed; + +struct psp_attestation { + /* Input parameters for PSP_CMD_ATTESTATION */ + uint32_t handle; + uint32_t reserved; + uint64_t attest_paddr; + uint8_t attest_nonce[16]; + + /* Input/output parameter from PSP_CMD_ATTESTATION */ + uint32_t attest_len; + uint32_t padding; + + /* Output parameter from PSP_CMD_ATTESTATION */ + struct psp_report psp_report; /* 64bit aligned */ +#define report_nonce psp_report.report_nonce +#define report_launch_digest psp_report.report_launch_digest +#define report_policy psp_report.report_policy +#define report_sig_usage psp_report.report_sig_usage; +#define report_report_sig_alg psp_report.report_sig_algo; +#define report_report_sig1 psp_report.report_sig1; +} __packed; +.Ed +.Pp +.Va handle +identifies the guest. +.Va attest_paddr +is currently not used. +.Va attest_nonce +is the nonce returned by a previous +.Dv PSP_IOC_LAUNCH_MEASURE +command. +.Va attest_len +must always be +.Li sizeof(struct psp_report) . +.Pp +The attestation report is returned in +.Va psp_report . +The format of the report is defined by +.Li struct psp_report . +.It Dv PSP_IOC_ACTIVATE +This commands associates the context of the guest identified by +.Va handle +with the address space identifier provided in +.Va asid . +.Bd -literal +struct psp_activate { + /* Input parameters for PSP_CMD_ACTIVATE */ + uint32_t handle; + uint32_t asid; +} __packed; +.Ed +.It Dv PSP_IOC_DEACTIVATE +This command dissociates the context of the guest identified by +.Va handle +from its current the address space identifier. +.Bd -literal +struct psp_deactivate { + /* Input parameter for PSP_CMD_DEACTIVATE */ + uint32_t handle; +} __packed; +.Ed +.It Dv PSP_IOC_SNP_GET_PSTATUS +This command returns the state of a SEV-SNP enabled platform. +.Bd -literal +struct psp_snp_platform_status { + uint8_t api_major; + uint8_t api_minor; + uint8_t state; + uint8_t is_rmp_init; + uint32_t build; + uint32_t features; + uint32_t guest_count; + uint64_t current_tcb; + uint64_t reported_tcb; +} __packed; +.Ed +.It Dv PSP_IOC_GUEST_SHUTDOWN +This command shuts down a guest identified by +.Va handle . +.Bd -literal +struct psp_guest_shutdown { + /* Input parameter for PSP_CMD_GUEST_SHUTDOWN */ + uint32_t handle; +} __packed; +.Ed +.Pp +The command combines +.Dv PSP_IOC_DEACTIVATE +and +.Dv PSP_IOC_DECOMMISSION +in a single +.Xr ioctl 2 +call. +.El +.Sh FILES +.Bl -tag -width /dev/psp +.It Pa /dev/psp +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr ccp 4 , +.Xr vmd 8 +.Rs +.%T Secure Encrypted Virtualization API +.%O Publication #55766 +.Re +.Rs +.%T SEV Secure Nested Paging Firmware ABI Specification +.%O Publication #56860 +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Hans-Joerg Hoexer Aq Mt hshoexer@genua.de . diff --git a/static/openbsd/man4/pty.4 b/static/openbsd/man4/pty.4 new file mode 100644 index 00000000..6ac98d7b --- /dev/null +++ b/static/openbsd/man4/pty.4 @@ -0,0 +1,311 @@ +.\" $OpenBSD: pty.4,v 1.26 2022/10/13 21:37:05 jmc Exp $ +.\" $NetBSD: pty.4,v 1.4 1998/03/21 03:14:30 fair Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)pty.4 8.2 (Berkeley) 11/30/93 +.\" +.Dd $Mdocdate: October 13 2022 $ +.Dt PTY 4 +.Os +.Sh NAME +.Nm pty , +.Nm ptm +.Nd pseudo terminal driver +.Sh SYNOPSIS +.Cd "pseudo-device pty" Op Ar count +.Sh DESCRIPTION +The +.Nm +driver provides support for a device-pair termed a +.Em pseudo terminal . +A pseudo terminal is a pair of character devices, a +.Em master +device and a +.Em slave +device. +The slave device provides to a process an interface identical to that +described in +.Xr tty 4 . +However, whereas all other devices which provide the +interface described in +.Xr tty 4 +have a hardware device of some sort behind them, the slave +device has, instead, another process manipulating +it through the master half of the pseudo terminal. +That is, anything written on the master device is +given to the slave device as input and anything written +on the slave device is presented as input on the master +device. +.Pp +In configuring, if an optional +.Ar count +is given in +the specification, space for that number of pseudo terminal pairs is +preallocated. +If the count is missing or is less than 2, a default count of 8 is used. +This is not a hard limit--space for additional pseudo terminal pairs +is allocated on demand up to the limit of 992. +.Pp +The following +.Xr ioctl 2 +calls apply only to pseudo terminals and may only be applied to the +.Nm +master: +.Bl -tag -width TIOCREMOTE +.It Dv TIOCEXT Fa int *on +If +.Fa on +points to a non-zero integer, +enable +external processing. +Otherwise, +disable external processing. +.Pp +While external processing is enabled, input line editing, character echo, +and mapping of control characters to signals are disabled +regardless of the terminal's +.Xr termios 4 +settings. +.It Dv TIOCSTOP Fa void +Stops output to a terminal (e.g., like typing +.Ql ^S ) . +.It Dv TIOCSTART Fa void +Restarts output +.Po +stopped by +.Dv TIOCSTOP +or by typing +.Ql ^S +.Pc . +.It Dv TIOCPKT Fa int *on +If +.Fa on +points to a non-zero integer, +enable packet mode. +Otherwise, +disable packet mode. +.Pp +While packet mode is enabled, each subsequent +.Xr read 2 +from the +.Nm +master will either return data written to the +.Nm +slave preceded by a zero byte (symbolically defined as +.Dv TIOCPKT_DATA ) , +or a single byte reflecting control +status information. +In the latter case, the byte is an inclusive-or of zero or more of the bits: +.Bl -tag -width TIOCPKT_FLUSHWRITE +.It Dv TIOCPKT_FLUSHREAD +whenever the read queue for the terminal is flushed. +.It Dv TIOCPKT_FLUSHWRITE +whenever the write queue for the terminal is flushed. +.It Dv TIOCPKT_STOP +whenever output to the terminal is stopped a la +.Ql ^S . +.It Dv TIOCPKT_START +whenever output to the terminal is restarted. +.It Dv TIOCPKT_DOSTOP +whenever +.Em t_stopc +is +.Ql ^S +and +.Em t_startc +is +.Ql ^Q . +.It Dv TIOCPKT_NOSTOP +whenever the start and stop characters are not +.Ql ^S/^Q . +.It Dv TIOCPKT_IOCTL +whenever the terminal's +.Xr termios 4 +settings change while external processing is enabled. +.Pp +Additionally, when the +.Dv TIOCPKT_IOCTL +bit is set, the remainder of the data read +from the +.Nm +master is a copy of the new +.Xr termios 4 +structure. +.El +.Pp +While this mode is in use, the presence of control status information +to be read from the master side may be detected by a +.Xr select 2 +for exceptional conditions. +.It Dv TIOCUCNTL Fa int *on +If +.Fa on +points to a non-zero integer, +enable a mode that allows a small number of simple user +.Xr ioctl 2 +commands to be passed through the pseudo terminal, +using a protocol similar to that of +.Dv TIOCPKT . +The +.Dv TIOCUCNTL +and +.Dv TIOCPKT +modes are mutually exclusive. +This mode is enabled from the master side of a pseudo terminal. +Each subsequent +.Xr read 2 +from the master side will return data written on the slave part of +the pseudo terminal preceded by a zero byte, +or a single byte reflecting a user control operation on the slave side. +A user control command consists of a special +.Xr ioctl 2 +operation with no data; the command is given as +.Dv UIOCCMD Ns (n) , +where +.Ar n +is a number in the range 1-255. +The operation value +.Ar n +will be received as a single byte on the next +.Xr read 2 +from the master side. +The +.Xr ioctl 2 +.Dv UIOCCMD Ns (0) +is a no-op that may be used to probe for +the existence of this facility. +.Pp +While this mode is in use, any of the +.Dv TIOCSBRK +and +.Dv TIOCCBRK +ioctl requests issued on the slave part of the pseudo terminal will be +translated to a +.Dv TIOCUCNTL_SBRK +or +.Dv TIOCUCNTL_CBRK +user command on the master side. +.Pp +As with +.Dv TIOCPKT +mode, command operations may be detected with a +.Xr select 2 +for exceptional conditions. +.It Dv TIOCREMOTE Fa int *on +If +.Fa on +points to a non-zero integer, +enable a mode for the master half of a pseudo terminal, +independent of +.Dv TIOCPKT . +This mode causes input to the pseudo terminal +to be flow controlled and not input edited (regardless of the terminal mode). +Each write to the controlling terminal produces a record boundary for the +process reading the terminal. +In normal usage, a write of data is like the data typed as a line +on the terminal; a write of 0 bytes is like typing an end-of-file +character. +.Dv TIOCREMOTE +can be used when doing remote line +editing in a window manager, or whenever flow controlled input +is required. +.El +.Pp +The standard way to allocate +.Nm +devices is through +.Xr openpty 3 , +a function which internally uses a +.Dv PTMGET +.Xr ioctl 2 +call on the +.Pa /dev/ptm +device. +The +.Dv PTMGET +command allocates a free pseudo terminal, changes its ownership to +the caller, revokes the access privileges for all previous users, +opens the file descriptors for the master and slave devices and returns +them to the caller in +.Fa struct ptmget . +.Bd -literal -offset indent +struct ptmget { + int cfd; + int sfd; + char cn[16]; + char sn[16]; +}; +.Ed +.Pp +The +.Va cfd +and +.Va sfd +fields are the file descriptors for the controlling and slave terminals. +The +.Va cn +and +.Va sn +fields are the file names of the controlling and slave devices. +.Sh FILES +.Bl -tag -width /dev/tty[p-zP-T][0-9a-zA-Z]x -compact +.It Pa /dev/pty[p-zP-T][0-9a-zA-Z] +master pseudo terminals +.It Pa /dev/tty[p-zP-T][0-9a-zA-Z] +slave pseudo terminals +.It Pa /dev/ptm +pseudo terminal management device +.El +.Sh SEE ALSO +.Xr openpty 3 , +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver appeared in +.Bx 4.2 . +The +.Pa /dev/ptm +device was added in +.Ox 3.5 . +.Sh CAVEATS +The +.Pa ptm +device will only work on systems where the +.Pa /dev +directory has been properly populated with +.Nm +device nodes following the naming convention used in +.Ox . +Since +.Pa ptm +impersonates the super user for some operations it needs to perform +to complete the allocation of a pseudo terminal, the +.Pa /dev +directory must also be writeable by the super user. diff --git a/static/openbsd/man4/puc.4 b/static/openbsd/man4/puc.4 new file mode 100644 index 00000000..07e9cf5a --- /dev/null +++ b/static/openbsd/man4/puc.4 @@ -0,0 +1,215 @@ +.\" $OpenBSD: puc.4,v 1.53 2017/08/06 11:12:03 uaa Exp $ +.\" $NetBSD: puc.4,v 1.7 1999/07/03 05:55:23 cgd Exp $ +.\" +.\" Copyright (c) 1998 Christopher G. Demetriou. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christopher G. Demetriou +.\" for the NetBSD Project. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 6 2017 $ +.Dt PUC 4 +.Os +.Sh NAME +.Nm puc +.Nd PCI universal communications card driver +.Sh SYNOPSIS +.Cd "puc* at pci?" +.Cd "puc* at cardbus?" +.Cd "lpt* at puc?" +.Cd "com* at puc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI communications cards containing +simple communications ports, such as NS16550-family +.Pf ( Nm com ) +serial ports and standard PC-like +.Pf ( Nm lpt ) +parallel ports. +The driver is called +.Dq universal +because the interfaces to these devices aren't nearly as well +defined and standard as they should be. +.Pp +The driver currently supports the following cards and controllers: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Tn "ASIX AX99100 (4 port serial)" +.It Tn "AT&T/Lucent Venus Modem (found on IBM 33L4618, Actiontec 56K)" +.It Tn "Avlab Low Profile PCI 4S Quartet (4 port serial)" +.It Tn "Avlab PCI 2S (2 port serial)" +.It Tn "Boca Research Turbo Serial 654 (4 port serial)" +.It Tn "Boca Research Turbo Serial 658 (8 port serial)" +.It Tn "Brainboxes Instashield IS-200 with BB16PCI958 (2 port serial)" +.It Tn "Cronyx Omega-PCI (8 port serial)" +.It Tn "Decision Computer Inc PCCOM PCI 2 Port (2 port serial)" +.It Tn "Decision Computer Inc PCCOM PCI 4 Port (4 port serial)" +.It Tn "Decision Computer Inc PCCOM PCI 8 Port (8 port serial)" +.It Tn "Digi International Digi Neo 4 (4 port serial)" +.It Tn "Digi International Digi Neo 8 (8 port serial)" +.It Tn "Dolphin Peripherals 4014 (dual parallel)" +.It Tn "Dolphin Peripherals 4035 (dual serial)" +.It Tn "Exsys EX-41098 (4 port serial)" +.It Tn "IBM 4810 SurePOS 300 Series SCC (4 port serial)" +.It Tn "Koutech IOFLEX-2S (dual serial)" +.It Tn "Kouwell Model-223 (2 port serial, 1 port parallel)" +.It Tn "Lava Computers 2SP-PCI (parallel port)" +.It Tn "Lava Computers 2SP-PCI and Quattro-PCI (dual serial)" +.It Tn "Lava Computers Octopus-550" +.It Tn "Lava LavaPort-650" +.It Tn "MosChip MCS9865 (1, 2 and 4 port serial)" +.It Tn "Moxa Technologies Co., Ltd. PCI I/O Card 4S (4 port serial)" +.It Tn "Moxa Technologies Co., Ltd. C104H/PCI (4 port serial)" +.It Tn "Moxa Technologies Co., Ltd. CP104/PCI (4 port serial)" +.It Tn "Moxa Technologies Co., Ltd. C168H/PCI (8 port serial)" +.It Tn "Moxa Technologies Co., Ltd. CP168U/PCI (8 port serial)" +.It Tn "NEC PK-UG-X008 (serial)" +.It Tn "NEC PK-UG-X001 K56flex PCI (modem)" +.It Tn "NetMos 1P (1 port parallel)" +.It Tn "NetMos 2S1P (2 port serial and 1 port parallel)" +.It Tn "NetMos 2S (2 port serial)" +.It Tn "NetMos 4S (4 port serial)" +.It Tn "NetMos 6S (6 port serial)" +.It Tn "Oxford OX16PCI952 (2 port serial, 1 port parallel)" +.It Tn "Oxford OX16PCI954 (4 port serial, 1 port parallel)" +.It Tn "PLX 9016 (8 port serial)" +.It Tn "QEMU PCI Serial" +.It Tn "QEMU PCI Serial 2x" +.It Tn "QEMU PCI Serial 4x" +.It Tn "SIIG Cyber 2P1S PCI (dual parallel and single serial)" +.It Tn "SIIG Cyber 2S1P PCI (dual serial and single parallel)" +.It Tn "SIIG Cyber 4S PCI (quad serial)" +.It Tn "SIIG Cyber I/O PCI (single serial and single parallel)" +.It Tn "SIIG Cyber Parallel Dual PCI (dual parallel)" +.It Tn "SIIG Cyber Parallel PCI (single parallel)" +.It Tn "SIIG Cyber Serial Dual PCI (dual serial)" +.It Tn "SIIG Cyber Serial PCI (single serial)" +.It Tn "SIIG Cyber 8S PCI 16C850" +.It Tn "SUNIX 400x (1 port parallel)" +.It Tn "SUNIX 401x (2 port parallel)" +.It Tn "SUNIX 402x (1 port serial)" +.It Tn "SUNIX 403x (2 port serial)" +.It Tn "SUNIX 405x (4 port serial)" +.It Tn "SUNIX 406x (8 port serial)" +.It Tn "SUNIX 407x (2 port serial and 1 port parallel)" +.It Tn "SUNIX 408x (2 port serial and 2 port parallel)" +.It Tn "SUNIX 409x (4 port serial and 2 port parallel)" +.It Tn "SUNIX 5008 (1 port parallel)" +.It Tn "SUNIX 5016 (16 port serial)" +.It Tn "SUNIX 5027 (1 port serial)" +.It Tn "SUNIX 5037 (2 port serial)" +.It Tn "SUNIX 5056 (4 port serial)" +.It Tn "SUNIX 5066 (8 port serial)" +.It Tn "SUNIX 5069 (1 port serial and 1 port parallel)" +.It Tn "SUNIX 5079 (2 port serial and 1 port parallel)" +.It Tn "SUNIX 5099 (4 port serial and 1 port parallel)" +.It Tn "Syba Tech Ltd. PCI-4S2P-550-ECP (4 port serial and 2 port parallel)" +.It Tn "US Robotics 3CP5609 PCI (modem)" +.It Tn "VScom PCI 800 (8 port serial, probably OEM)" +.It Tn "VScom PCI 011H (1 port parallel)" +.It Tn "VScom PCI 100H (1 port serial)" +.It Tn "VScom PCI 110H (1 port serial and 1 port parallel)" +.It Tn "VScom PCI 200H (2 port serial)" +.It Tn "VScom PCI 210H (2 port serial and 1 port parallel)" +.It Tn "VScom PCI 400H (4 port serial)" +.It Tn "VScom PCI 410H (4 port serial and 1 port parallel)" +.It Tn "VScom PCI 800H (8 port serial)" +.It Tn "VScom PCI 100L (1 port serial)" +.It Tn "VScom PCI 200L (2 port serial)" +.It Tn "VScom PCI 210L (2 port serial and 1 port parallel)" +.It Tn "VScom PCI 400L (4 port serial)" +.It Tn "VScom PCI 400S (4 port serial)" +.It Tn "VScom PCI 800L (8 port serial)" +.El +.Pp +The driver does not support these cards: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Tn "Dolphin Peripherals 4006 (single parallel)" +.It Tn "Dolphin Peripherals 4025 (single serial)" +.It Tn "Dolphin Peripherals 4078 (dual serial and single parallel)" +.El +.Pp +but support for them (and for similar cards) should be trivial to add. +.Pp +The +.Ar port +locator is used to identify the port (starting from 0) on the +communications card that a subdevice is supposed to attach to. +Typically, the numbering of ports is explained in a card's +hardware documentation, and the port numbers used by the driver +are the same as (or one off from, e.g., the manual uses ports +numbered starting from 1) those described in the documentation. +.Sh SEE ALSO +.Xr cardbus 4 , +.Xr com 4 , +.Xr intro 4 , +.Xr lpt 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx 1.4 . +.Ox +support was added in +.Ox 2.7 . +CardBus support was added in +.Ox 4.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Chris Demetriou . +.Sh BUGS +The current design of this driver keeps any +.Nm com +ports on these cards from easily being used as console. +Of course, because boards with those are PCI boards, they also suffer +from dynamic address assignment, which also means that they +can't easily be used as console. +.Pp +Some of the cards supported by this driver have jumper-selectable +.Nm com +port clock multipliers, which are unsupported by this driver. +Those can be easily accommodated with driver flags, or by +using a properly scaled baud rate when talking to the card. +.Pp +Some of the cards supported by this driver, e.g., the VScom PCI-800, +have software-selectable +.Nm com +port clock multipliers, which are unsupported by this driver. +Those can be accommodated using internal driver flags, or by using +a properly scaled baud rate when talking to the card. +.Pp +Some ports use an +.Nm lpt +driver other than the machine-independent driver. +Those ports will not be able to use +.Nm lpt +ports attached to +.Nm +devices. diff --git a/static/openbsd/man4/pvbus.4 b/static/openbsd/man4/pvbus.4 new file mode 100644 index 00000000..33b6a22e --- /dev/null +++ b/static/openbsd/man4/pvbus.4 @@ -0,0 +1,170 @@ +.\" $OpenBSD: pvbus.4,v 1.15 2023/01/07 06:40:21 asou Exp $ +.\" +.\" Copyright (c) 2015 Reyk Floeter +.\" Copyright (c) 2006 Jason McIntyre +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 7 2023 $ +.Dt PVBUS 4 +.Os +.Sh NAME +.Nm pvbus +.Nd paravirtual device tree root +.Sh SYNOPSIS +.Cd "pvbus0 at mainbus0" +.Pp +.In sys/types.h +.In sys/ioctl.h +.In dev/pv/pvvar.h +.Sh DESCRIPTION +.Nm +is used on virtual machines that are running on hypervisors. +It provides a pseudo-bus for all paravirtual devices that do not +attach to a well-known bus like +.Xr pci 4 . +The +.Nm +driver is responsible for detecting the hypervisor interface, +checking the capabilities, attaching the paravirtual devices, +and providing access to supported information stores. +.Ss Supported hypervisors +.Bl -tag -width 13n -offset ind -compact +.It KVM +Kernel-based Virtual Machine +.It Hyper-V +Microsoft Hyper-V +.It OpenBSD +.Ox +.Xr vmm 4 +.It VMware +VMware vSphere Hypervisor and ESXi +.It Xen +Xen VMM +.El +.Pp +Note that a hypervisor can attempt to emulate other hypervisors, so +multiple hypervisor interfaces may be available on the same host. +.Ss VMware paravirtual devices +.Bl -tag -width 13n -offset ind -compact +.It Xr vmt 4 +VMware Tools driver and +.Dq guestinfo +information store +.El +.Ss Hyper-V paravirtual devices +.Bl -tag -width 13n -offset ind -compact +.It Xr hvn 4 +Hyper-V virtual networking interface +.It Xr hvs 4 +Hyper-V virtual disk +.It Xr hyperv 4 +Hyper-V guest nexus device +.El +.Ss Xen paravirtual devices +.Bl -tag -width 13n -offset ind -compact +.It Xr xbf 4 +Xen Blkfront virtual disk +.It Xr xen 4 +Xen domU nexus device and XenStore information store +.It Xr xnf 4 +Xen Netfront virtual networking interface +.El +.Sh IOCTL INTERFACE +.Nm +supports +.Xr ioctl 2 +commands to exchange information with the hypervisor interface, +as implemented in the +.Xr hostctl 8 +program. +Each detected hypervisor interface is available as a character special +device file, +.Pa /dev/pvbus0 , +.Pa /dev/pvbus1 , +etc. +All available commands use the same +.Fa pvbus_req +structure: +.Bd -literal +struct pvbus_req { + size_t pvr_keylen; + char *pvr_key; + size_t pvr_valuelen; + char *pvr_value; +}; +.Ed +.Pp +The caller is responsible for attaching character buffers to the +.Fa pvr_key +and +.Fa pvr_value +fields and to set their length in +.Fa pvr_keylen +and +.Fa pvr_valuelen +accordingly. +All keys and values are nul-terminated strings. +.Pp +The following +.Xr ioctl 2 +commands are available: +.Bl -tag -width PVBUSIOC_KVWRITE +.It Dv PVBUSIOC_KVREAD +Read the value from +.Fa pvr_key +and return it in +.Fa pvr_value . +If +.Fa pvr_valuelen +is not enough for the value, +the command will fail and +.Xr errno 2 +is set to +.Er ERANGE . +.It Dv PVBUSIOC_KVTYPE +Return the type of the attached hypervisor interface as a string in +.Fa pvr_key ; +see +.Sx Supported hypervisors . +.It Dv PVBUSIOC_KVWRITE +Write the new value +.Fa pvr_value +to the key +.Fa pvr_key . +This command requires write permissions on the device file. +.El +.Sh FILES +.Bl -tag -width "/dev/pvbusX" -compact +.It /dev/pvbus Ns Ar u +.Nm +device unit +.Ar u +file. +.El +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr intro 4 , +.Xr mainbus 4 , +.Xr vmm 4 , +.Xr hostctl 8 +.Sh HISTORY +The +.Nm +pseudo-bus first appeared in +.Ox 5.8 . +.Sh AUTHORS +The +.Nm +pseudo-bus was written by +.An Reyk Floeter Aq Mt reyk@openbsd.org . diff --git a/static/openbsd/man4/pvclock.4 b/static/openbsd/man4/pvclock.4 new file mode 100644 index 00000000..d3fd872b --- /dev/null +++ b/static/openbsd/man4/pvclock.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: pvclock.4,v 1.2 2018/11/23 17:21:37 jmc Exp $ +.\" +.\" Copyright (c) 2018 Reyk Floeter +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 23 2018 $ +.Dt PVCLOCK 4 +.Os +.Sh NAME +.Nm pvclock +.Nd paravirtual clock driver +.Sh SYNOPSIS +.Cd "pvclock* at pvbus?" +.Sh DESCRIPTION +The +.Nm +driver supports the paravirtual clock that is available in KVM and +other hypervisors. +.Nm +uses a shared page between the host and the hypervisor to synchronize +the TSC clock in an efficient way. +.Sh SEE ALSO +.Xr pvbus 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Reyk Floeter Aq Mt reyk@openbsd.org . diff --git a/static/openbsd/man4/pwdog.4 b/static/openbsd/man4/pwdog.4 new file mode 100644 index 00000000..5995b636 --- /dev/null +++ b/static/openbsd/man4/pwdog.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: pwdog.4,v 1.7 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Marc Balmer +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt PWDOG 4 +.Os +.Sh NAME +.Nm pwdog +.Nd Quancom PWDOG1 watchdog timer device +.Sh SYNOPSIS +.Cd "pwdog0 at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Quancom PWDOG1 boards. +.Pp +If the kernel crashes, the watchdog timer is not reset and the system will +reboot (assuming a proper connection is made between the PWDOG1 and +the motherboard). +Alternatively, the watchdog can be reinitialized via a userland process which +ensures that process scheduling, not just kernel timeout processing, is still +taking place. +See +.Xr watchdog 4 +and +.Xr watchdogd 8 +for more information. +.Pp +The timeout period of the PWDOG1 card is set using DIP switches and cannot +be changed by software. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr watchdog 4 , +.Xr watchdogd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Marc Balmer Aq Mt mbalmer@openbsd.org . diff --git a/static/openbsd/man4/pwmbl.4 b/static/openbsd/man4/pwmbl.4 new file mode 100644 index 00000000..06567e37 --- /dev/null +++ b/static/openbsd/man4/pwmbl.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: pwmbl.4,v 1.2 2019/10/22 08:54:29 jmc Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 22 2019 $ +.Dt PWMBL 4 +.Os +.Sh NAME +.Nm pwmbl +.Nd PWM backlight controller +.Sh SYNOPSIS +.Cd "pwmbl* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for backlight controllers that are controlled +by a PWM signal. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Krystian Lewandowski . diff --git a/static/openbsd/man4/pwmfan.4 b/static/openbsd/man4/pwmfan.4 new file mode 100644 index 00000000..8f56e41d --- /dev/null +++ b/static/openbsd/man4/pwmfan.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: pwmfan.4,v 1.1 2019/12/03 09:40:56 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 3 2019 $ +.Dt PWMFAN 4 +.Os +.Sh NAME +.Nm pwmfan +.Nd PWM fan controller +.Sh SYNOPSIS +.Cd "pwmfan* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for fans that are controlled by a PWM signal. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/pwmleds.4 b/static/openbsd/man4/pwmleds.4 new file mode 100644 index 00000000..9aea6be0 --- /dev/null +++ b/static/openbsd/man4/pwmleds.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: pwmleds.4,v 1.1 2022/11/23 23:47:05 kettenis Exp $ +.\" +.\" Copyright (c) 2021 Klemens Nanni +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 23 2022 $ +.Dt PWMLEDS 4 +.Os +.Sh NAME +.Nm pwmleds +.Nd PWM LEDs +.Sh SYNOPSIS +.Cd "pwmleds* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for LEDs controlled by Pulse Width Modulation +(PWM). +.Pp +Currently, only keyboard backlight LEDs are supported. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/pwmreg.4 b/static/openbsd/man4/pwmreg.4 new file mode 100644 index 00000000..40140e93 --- /dev/null +++ b/static/openbsd/man4/pwmreg.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: pwmreg.4,v 1.1 2019/09/30 21:00:51 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 30 2019 $ +.Dt PWMREG 4 +.Os +.Sh NAME +.Nm pwmreg +.Nd PWM voltage regulator +.Sh SYNOPSIS +.Cd "pwmreg* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for voltage regulators that are controlled by +a PWM signal. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/qccpu.4 b/static/openbsd/man4/qccpu.4 new file mode 100644 index 00000000..e824dee7 --- /dev/null +++ b/static/openbsd/man4/qccpu.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: qccpu.4,v 1.1 2023/07/01 16:39:11 drahn Exp $ +.\" +.\" Copyright (c) 2023 Dale Rahn +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 1 2023 $ +.Dt QCCPU 4 +.Os +.Sh NAME +.Nm qccpu +.Nd Qualcomm Snapdragon CPU power states +.Sh SYNOPSIS +.Cd "qccpu* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for managing the CPU power states on Qualcomm +Snapdragon SoCs. +These power states can be set to reduce power usage and extend battery +life through the +.Va hw.setperf +.Xr sysctl 2 +mechanism. +.Sh SEE ALSO +.Xr sysctl 2 , +.Xr intro 4 , +.Xr apmd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@openbsd.org . diff --git a/static/openbsd/man4/qccpucp.4 b/static/openbsd/man4/qccpucp.4 new file mode 100644 index 00000000..59dacee6 --- /dev/null +++ b/static/openbsd/man4/qccpucp.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: qccpucp.4,v 1.2 2024/11/19 18:39:34 jmc Exp $ +.\" +.\" Copyright (c) 2024 Tobias Heider +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 19 2024 $ +.Dt QCCPUCP 4 +.Os +.Sh NAME +.Nm qccpucp +.Nd Qualcomm CPUCP mailbox controller +.Sh SYNOPSIS +.Cd "qccpucp* at fdt?" +.Sh DESCRIPTION +The +.Nm +handles communication with the Qualcomm CPUSS Control Processor. +It is used as a doorbell for CPU frequency management via +.Xr scmi 4 +on Qualcomm Snapdragon X Elite devices. +.Sh SEE ALSO +.Xr intro 4 , +.Xr scmi 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Tobias Heider Aq Mt tobhe@openbsd.org . diff --git a/static/openbsd/man4/qcdpc.4 b/static/openbsd/man4/qcdpc.4 new file mode 100644 index 00000000..788e4553 --- /dev/null +++ b/static/openbsd/man4/qcdpc.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: qcdpc.4,v 1.3 2025/07/18 09:31:23 jsg Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 18 2025 $ +.Dt QCDPC 4 +.Os +.Sh NAME +.Nm qcdpc +.Nd Qualcomm DisplayPort Controller +.Sh SYNOPSIS +.Cd "qcdpc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the DisplayPort controller that is part of +the MSM Mobile Display Subsystem (MDSS) found on the Qualcomm +Snapdragon SoCs. +It provides backlight control for some eDP display panels. +.Sh SEE ALSO +.Xr drm 4 , +.Xr intro 4 , +.Xr qcdrm 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/qcdrm.4 b/static/openbsd/man4/qcdrm.4 new file mode 100644 index 00000000..91420f51 --- /dev/null +++ b/static/openbsd/man4/qcdrm.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: qcdrm.4,v 1.2 2025/07/18 09:31:23 jsg Exp $ +.\" +.\" Copyright (c) 2025 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 18 2025 $ +.Dt QCDRM 4 +.Os +.Sh NAME +.Nm qcdrm +.Nd Qualcomm Snapdragon DRM subsystem +.Sh SYNOPSIS +.Cd "qcdrm* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the MSM Mobile Display Subsystem (MDSS) +found on the Qualcomm Snapdragon SoCs. +.Sh SEE ALSO +.Xr drm 4 , +.Xr intro 4 , +.Xr qcdpc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +.Sh BUGS +The +.Nm +driver does not implement any usable DRM functionality yet. diff --git a/static/openbsd/man4/qcdwusb.4 b/static/openbsd/man4/qcdwusb.4 new file mode 100644 index 00000000..7d8d093d --- /dev/null +++ b/static/openbsd/man4/qcdwusb.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: qcdwusb.4,v 1.2 2022/11/10 12:59:26 patrick Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 10 2022 $ +.Dt QCDWUSB 4 +.Os +.Sh NAME +.Nm qcdwusb +.Nd Qualcomm USB 3.0 glue logic +.Sh SYNOPSIS +.Cd "qcdwusb* at fdt?" +.Cd "xhci* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the interface logic for the Synopsys DesignWare USB 3.0 +controller found on various Qualcomm Snapdragon SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr xhci 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/qcgpio.4 b/static/openbsd/man4/qcgpio.4 new file mode 100644 index 00000000..827782b3 --- /dev/null +++ b/static/openbsd/man4/qcgpio.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: qcgpio.4,v 1.2 2024/08/01 21:55:48 mglocker Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 1 2024 $ +.Dt QCGPIO 4 +.Os +.Sh NAME +.Nm qcgpio +.Nd Qualcomm Snapdragon GPIO controller +.Sh SYNOPSIS +.Cd "qcgpio* at acpi?" +.Cd "qcgpio* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO controller found on Qualcomm +Snapdragon SoCs. +It does not provide direct device driver entry points but makes its +functions available to +.Xr acpi 4 . +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/qciic.4 b/static/openbsd/man4/qciic.4 new file mode 100644 index 00000000..82d323fa --- /dev/null +++ b/static/openbsd/man4/qciic.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: qciic.4,v 1.1 2022/11/10 12:36:38 patrick Exp $ +.\" +.\" Copyright (c) 2016 Jonathan Gray +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 10 2022 $ +.Dt QCIIC 4 +.Os +.Sh NAME +.Nm qciic +.Nd Qualcomm Snapdragon GENI I2C controller +.Sh SYNOPSIS +.Cd "qciic* at acpi?" +.Cd "iic* at qciic?" +.Sh DESCRIPTION +The +.Nm +driver supports the GENI I2C controller found on Qualcomm Snapdragon +SoCs for use with the +.Xr iic 4 +framework. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr iic 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/qcpdc.4 b/static/openbsd/man4/qcpdc.4 new file mode 100644 index 00000000..b4034c6f --- /dev/null +++ b/static/openbsd/man4/qcpdc.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: qcpdc.4,v 1.2 2022/11/10 12:59:26 patrick Exp $ +.\" +.\" Copyright (c) 2022 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 10 2022 $ +.Dt QCPDC 4 +.Os +.Sh NAME +.Nm qcpdc +.Nd Qualcomm power domain controller +.Sh SYNOPSIS +.Cd "qcpdc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Qualcomm power domain controller (PDC). +It acts as a "transparent" interrupt controller and hands interrupt +handlers to the parent interrupt controller. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/qcpmic.4 b/static/openbsd/man4/qcpmic.4 new file mode 100644 index 00000000..7aeb04b1 --- /dev/null +++ b/static/openbsd/man4/qcpmic.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: qcpmic.4,v 1.3 2022/11/10 19:10:50 jmc Exp $ +.\" +.\" Copyright (c) 2022 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 10 2022 $ +.Dt QCPMIC 4 +.Os +.Sh NAME +.Nm qcpmic +.Nd Qualcomm Power Management IC +.Sh SYNOPSIS +.Cd "qcpmic* at qcspmi?" +.Cd "qcpmicgpio* at qcpmic?" +.Cd "qcpon* at qcpmic?" +.Cd "qcpwm* at qcpmic?" +.Cd "qcrtc* at qcpmic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PMIC found on various Qualcomm +Snapdragon SoCs. +The functionality for the hardware blocks found in each PMIC is +implemented in the children attaching to this driver. +.Sh SEE ALSO +.Xr intro 4 , +.Xr qcpmicgpio 4 , +.Xr qcpon 4 , +.Xr qcpwm 4 , +.Xr qcrtc 4 , +.Xr qcspmi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/qcpmicgpio.4 b/static/openbsd/man4/qcpmicgpio.4 new file mode 100644 index 00000000..1a1e3eb6 --- /dev/null +++ b/static/openbsd/man4/qcpmicgpio.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: qcpmicgpio.4,v 1.2 2022/11/10 19:10:50 jmc Exp $ +.\" +.\" Copyright (c) 2022 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 10 2022 $ +.Dt QCPMICGPIO 4 +.Os +.Sh NAME +.Nm qcpmicgpio +.Nd Qualcomm PMIC GPIO controller +.Sh SYNOPSIS +.Cd "qcpmicgpio* at qcpmic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO ports found on Qualcomm Snapdragon +SoCs. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 , +.Xr qcpmic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/qcpon.4 b/static/openbsd/man4/qcpon.4 new file mode 100644 index 00000000..97f6ad43 --- /dev/null +++ b/static/openbsd/man4/qcpon.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: qcpon.4,v 1.2 2022/11/10 19:10:50 jmc Exp $ +.\" +.\" Copyright (c) 2022 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 10 2022 $ +.Dt QCPON 4 +.Os +.Sh NAME +.Nm qcpon +.Nd Qualcomm PON controller +.Sh SYNOPSIS +.Cd "qcpon* at qcpmic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PON controllers integrated on various +Qualcomm Snapdragon SoCs. +This controller contains the power button. +.Sh SEE ALSO +.Xr intro 4 , +.Xr qcpmic 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/qcpwm.4 b/static/openbsd/man4/qcpwm.4 new file mode 100644 index 00000000..bc260093 --- /dev/null +++ b/static/openbsd/man4/qcpwm.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: qcpwm.4,v 1.2 2022/11/10 19:10:50 jmc Exp $ +.\" +.\" Copyright (c) 2022 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 10 2022 $ +.Dt QCPWM 4 +.Os +.Sh NAME +.Nm qcpwm +.Nd Qualcomm PWM controller +.Sh SYNOPSIS +.Cd "qcpwm* at qcpmic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PWM controllers integrated on various +Qualcomm Snapdragon SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr qcpmic 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/qcrng.4 b/static/openbsd/man4/qcrng.4 new file mode 100644 index 00000000..2943227d --- /dev/null +++ b/static/openbsd/man4/qcrng.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: qcrng.4,v 1.2 2023/09/27 20:30:19 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 27 2023 $ +.Dt QCRNG 4 +.Os +.Sh NAME +.Nm qcrng +.Nd Qualcomm Snapdragon random number generator +.Sh SYNOPSIS +.Cd "qcrng* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the random number generator found on the +Qualcomm Snapdragon SoCs. +.Pp +It feeds the random subsystem's entropy pool with 32 bits of random +data every second. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Peter Hessler Aq Mt phessler@openbsd.org , +based on the +.Xr amlrng 4 +driver by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/qcrtc.4 b/static/openbsd/man4/qcrtc.4 new file mode 100644 index 00000000..486b86e3 --- /dev/null +++ b/static/openbsd/man4/qcrtc.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: qcrtc.4,v 1.2 2022/11/10 19:10:50 jmc Exp $ +.\" +.\" Copyright (c) 2022 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 10 2022 $ +.Dt QCRTC 4 +.Os +.Sh NAME +.Nm qcrtc +.Nd Qualcomm real-time clock +.Sh SYNOPSIS +.Cd "qcrtc* at qcpmic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the RTC integrated on various Qualcomm +Snapdragon SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr qcpmic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/qcspmi.4 b/static/openbsd/man4/qcspmi.4 new file mode 100644 index 00000000..f479469b --- /dev/null +++ b/static/openbsd/man4/qcspmi.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: qcspmi.4,v 1.2 2022/11/10 19:10:50 jmc Exp $ +.\" +.\" Copyright (c) 2022 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 10 2022 $ +.Dt QCSPMI 4 +.Os +.Sh NAME +.Nm qcspmi +.Nd Qualcomm SPMI controller +.Sh SYNOPSIS +.Cd "qcspmi* at fdt?" +.Cd "qcpmic* at qcspmi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SPMI controller found on various +Qualcomm Snapdragon SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr qcpmic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/qcuart.4 b/static/openbsd/man4/qcuart.4 new file mode 100644 index 00000000..5d52132b --- /dev/null +++ b/static/openbsd/man4/qcuart.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: qcuart.4,v 1.2 2026/01/31 20:19:41 kettenis Exp $ +.\" +.\" Copyright (c) 2026 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 31 2026 $ +.Dt QCUART 4 +.Os +.Sh NAME +.Nm qcuart +.Nd Qualcomm GENI UART +.Sh SYNOPSIS +.Cd "qcuart* at acpi?" +.Cd "qcuart* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver supports the Qualcomm GENI UART. +.Sh SEE ALSO +.Xr tty 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/qla.4 b/static/openbsd/man4/qla.4 new file mode 100644 index 00000000..33144460 --- /dev/null +++ b/static/openbsd/man4/qla.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: qla.4,v 1.11 2014/03/16 08:28:55 deraadt Exp $ +.\" +.\" Copyright (c) 2014 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 16 2014 $ +.Dt QLA 4 +.Os +.Sh NAME +.Nm qla +.Nd QLogic ISP2100/2200/2300 Fibre Channel controller +.Sh SYNOPSIS +.Cd "qla* at pci?" +.Cd "qla* at sbus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for 1G and 2G QLogic Fibre Channel +host bus adapters using the ISP2100, ISP2200, and ISP2300 chipsets. +.Pp +.Nm +provides no ability to configure an adapter's parameters at runtime; +all configuration must be done prior to booting +.Ox . +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr qle 4 , +.Xr qlw 4 , +.Xr sbus 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . diff --git a/static/openbsd/man4/qle.4 b/static/openbsd/man4/qle.4 new file mode 100644 index 00000000..d86658a7 --- /dev/null +++ b/static/openbsd/man4/qle.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: qle.4,v 1.10 2015/01/21 22:33:22 tedu Exp $ +.\" +.\" Copyright (c) 2014 Jonathan Matthew +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 21 2015 $ +.Dt QLE 4 +.Os +.Sh NAME +.Nm qle +.Nd QLogic ISP2400/2500 Fibre Channel controller +.Sh SYNOPSIS +.Cd "qle* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for 4G and 8G QLogic Fibre Channel host bus +adapters using the ISP2400 and ISP2500 family of chipsets. +.Pp +.Nm +provides no ability to configure an adapter's parameters at runtime; +all configuration must be done prior to booting +.Ox . +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr qla 4 , +.Xr qlw 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . diff --git a/static/openbsd/man4/qlw.4 b/static/openbsd/man4/qlw.4 new file mode 100644 index 00000000..b7ba4f61 --- /dev/null +++ b/static/openbsd/man4/qlw.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: qlw.4,v 1.5 2015/01/21 22:33:22 tedu Exp $ +.\" +.\" Copyright (c) 2014 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 21 2015 $ +.Dt QLW 4 +.Os +.Sh NAME +.Nm qlw +.Nd QLogic ISP1000/1020/1x40/1x80/1x160 SCSI controller +.Sh SYNOPSIS +.Cd "qlw* at pci?" +.Cd "qlw* at sbus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for QLogic Ultra Wide SCSI host bus adapters +using the ISP1000, ISP1020/1040, ISP1080/1240/1280 and ISP10160/12160 chips. +.Pp +.Nm +provides no ability to configure an adapter's parameters at runtime; +all configuration must be done prior to booting +.Ox . +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr qla 4 , +.Xr qle 4 , +.Xr sbus 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org , +based on the +.Xr qla 4 +driver written by +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . diff --git a/static/openbsd/man4/qsphy.4 b/static/openbsd/man4/qsphy.4 new file mode 100644 index 00000000..4a452936 --- /dev/null +++ b/static/openbsd/man4/qsphy.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: qsphy.4,v 1.9 2020/01/24 05:08:02 jsg Exp $ +.\" $NetBSD: qsphy.4,v 1.1 1998/11/04 05:53:59 thorpej Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 24 2020 $ +.Dt QSPHY 4 +.Os +.Sh NAME +.Nm qsphy +.Nd Quality Semiconductor QS6612 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "qsphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Quality Semiconductor QS6612 10/100 Ethernet PHYs. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/qwx.4 b/static/openbsd/man4/qwx.4 new file mode 100644 index 00000000..e87ac0f2 --- /dev/null +++ b/static/openbsd/man4/qwx.4 @@ -0,0 +1,145 @@ +.\" $OpenBSD: qwx.4,v 1.10 2025/12/01 16:57:36 stsp Exp $ +.\" +.\" Copyright (c) 2022 Martin Pieuchot +.\" Copyright (c) 2024 Stefan Sperling +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 1 2025 $ +.Dt QWX 4 +.Os +.Sh NAME +.Nm qwx +.Nd Qualcomm IEEE 802.11a/ac/ax/b/g/n wireless network device +.Sh SYNOPSIS +.Cd "qwx* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Qualcomm Technologies QCNFA765 +802.11ax devices. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver offloads both encryption and decryption of unicast data frames to the +hardware for the CCMP cipher. +.Pp +The +.Nm +driver supports protected management frames (PMF) which prevents spoofing +of management frames such as deauthentication, disassociation, and block-ack +negotiation, on networks using WPA. +.Pp +In BSS mode the driver supports background scanning; +see +.Xr ifconfig 8 . +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs the following firmware files, +which are loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/qwx-wcn6855-hw2.0-amss +.It Pa /etc/firmware/qwx-wcn6855-hw2.0-board-2 +.It Pa /etc/firmware/qwx-wcn6855-hw2.0-m3 +.It Pa /etc/firmware/qwx-wcn6855-hw2.0-regdb +.It Pa /etc/firmware/qwx-wcn6855-hw2.1-amss +.It Pa /etc/firmware/qwx-wcn6855-hw2.1-board-2 +.It Pa /etc/firmware/qwx-wcn6855-hw2.1-m3 +.It Pa /etc/firmware/qwx-wcn6855-hw2.1-regdb +.El +.Pp +These firmware files are not free because Qualcomm refuses to grant +distribution rights without contractual obligations. +As a result, even though +.Ox +includes the driver, the firmware files cannot be included and +users have to download these files on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig qwx0 scan +.Pp +The following +.Xr hostname.if 5 +example configures qwx0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.5 . +.Sh CAVEATS +The +.Nm +driver does not support any of the 802.11ac and 802.11ax +capabilities offered by the hardware. +.Sh BUGS +Broadcast and Multicast frames are only received on networks which +do not use encryption or which use WPA. +This prevents ARP and IPv6 from working correctly on networks which +use WEP encryption. diff --git a/static/openbsd/man4/radio.4 b/static/openbsd/man4/radio.4 new file mode 100644 index 00000000..9f572d00 --- /dev/null +++ b/static/openbsd/man4/radio.4 @@ -0,0 +1,249 @@ +.\" $RuOBSD: radio.4,v 1.4 2001/10/26 05:38:43 form Exp $ +.\" $OpenBSD: radio.4,v 1.32 2021/02/01 07:09:37 jmc Exp $ +.\" +.\" Copyright (c) 2001 Vladimir Popov +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF +.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON +.\" ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 1 2021 $ +.Dt RADIO 4 +.Os +.Sh NAME +.Nm radio +.Nd device-independent radio driver layer +.Sh SYNOPSIS +.Cd "radio* at bktr?" +.Cd "radio* at fms?" +.Cd "radio* at udsbr?" +.Pp +.In sys/types.h +.In sys/ioctl.h +.In sys/radioio.h +.Sh DESCRIPTION +The +.Nm +driver provides support for various FM radio cards. +It provides a uniform programming interface layer above different underlying +radio hardware drivers. +.Pp +For radio tuner controlling there is a single device file available: +.Pa /dev/radio . +.Pp +The following +.Xr ioctl 2 +commands are supported: +.Pp +.Bl -tag -width indent -compact +.It Dv RIOCSSRCH Fa int +This command assumes that a signal search is required and gives direction +of search to the driver \- 0 to search down and any non-zero value to search up. +.It Dv RIOCGINFO Fa "struct radio_info" +.It Dv RIOCSINFO Fa "struct radio_info" +Get or set the current hardware device information into the +.Fa radio_info +structure. +.Bd -literal +struct radio_info { + int mute; + int volume; + int stereo; + int rfreq; /* reference frequency */ + int lock; /* locking field strength */ + u_int32_t freq; /* in kHz */ + u_int32_t caps; /* card capabilities */ +#define RADIO_CAPS_DETECT_STEREO (1<<0) +#define RADIO_CAPS_DETECT_SIGNAL (1<<1) +#define RADIO_CAPS_SET_MONO (1<<2) +#define RADIO_CAPS_HW_SEARCH (1<<3) +#define RADIO_CAPS_HW_AFC (1<<4) +#define RADIO_CAPS_REFERENCE_FREQ (1<<5) +#define RADIO_CAPS_LOCK_SENSITIVITY (1<<6) +#define RADIO_CARD_TYPE (0xFF<<16) + u_int32_t info; +#define RADIO_INFO_STEREO (1<<0) +#define RADIO_INFO_SIGNAL (1<<1) + u_int32_t tuner_mode; +#define RADIO_TUNER_MODE_RADIO (1<<0) +#define RADIO_TUNER_MODE_TV (1<<1) + u_int32_t chan; + u_int32_t chnlset; +}; +.Ed +.Pp +The +.Va mute +field is a boolean. +.Pp +The +.Va volume +field holds the card volume information and can be at most 255. +.Pp +The +.Va stereo +field is a boolean. +.Pp +The +.Va rfreq +holds information about the card reference frequency (not all cards support +this feature). +.Pp +The +.Va lock +field holds information about the card locking field strength during +an automatic search for cards that support this feature. +.Pp +The +.Va freq +field is the frequency in kHz the card is tuned to. +.Pp +The +.Va tuner_mode +field is the current tuning mode of the tuner. +Valid modes are: +.Pp +.Bl -tag -width indent -compact +.It Dv RADIO_TUNER_MODE_RADIO +The tuner operates in FM radio mode. +.It Dv RADIO_TUNER_MODE_TV +The tuner operates in TV mode. +.El +.Pp +The +.Va caps +field is read-only and describes the card capabilities. +The capabilities can have the following values: +.Pp +.Bl -tag -width indent -compact +.It Dv RADIO_CAPS_DETECT_STEREO +The device can determine if it is tuned to a stereo signal. +.It Dv RADIO_CAPS_DETECT_SIGNAL +The device can determine if it is tuned or not. +.It Dv RADIO_CAPS_SET_MONO +The device is capable of forcibly setting its output to mono. +.It Dv RADIO_CAPS_HW_SEARCH +The device can do hardware search. +.It Dv RADIO_CAPS_HW_AFC +The device has an internal hardware automatic frequency control. +.It Dv RADIO_CAPS_REFERENCE_FREQ +The device allows changing the reference frequency of a received signal. +.It Dv RADIO_CAPS_LOCK_SENSITIVITY +The device allows changing the station lock sensitivity used during search +operation. +.It Dv RADIO_CARD_TYPE +Some cards have several different incarnations. +This allows the variant of the card to be determined. +Currently not used. +.El +.Pp +The +.Va info +field is read-only and describes the current state of the card \- +tuned/not tuned, stereo signal/mono signal. +.Pp +.Bl -tag -width indent -compact +.It Dv RADIO_INFO_STEREO +Informs whether the device receives a stereo or mono signal. +.It Dv RADIO_INFO_SIGNAL +Informs whether the device receives a valid signal or noise. +.El +.Pp +The +.Va chan +holds the TV channel the card is tuned to. +.Pp +The +.Va chnlset +specifies the TV channel set currently being used. +The tuner uses the current channel set to derive the tuning frequency +from the channel number. +Western Europe is the default channel set. +The following is a list of valid channel sets: +.Pp +.Bl -tag -width indent -compact +.It 1 +U.S.A. Broadcast +.It 2 +U.S.A. Cable IRC +.It 3 +U.S.A. Cable HRC +.It 4 +Western Europe +.It 5 +Japan Broadcast +.It 6 +Japan Cable +.It 7 +Former U.S.S.R. and C.I.S. Countries +.It 8 +Australia +.It 9 +France +.El +.El +.Pp +Either +.Va freq +or +.Va chan +can be used to tune to FM radio stations or TV channels, +respectively. +Some devices may not support both functionalities. +.Sh CHIPSETS +The TEA5757; TEA5759 is a 44-pin integrated AM/FM stereo radio circuit. +The radio part is based on the TEA5712. +The TEA5757 is used in FM-standards in which the local oscillator frequency +is above the radio frequency (e.g. European and American standards). +The TEA5759 is the version in which the oscillator frequency is below +the radio frequency (e.g. Japanese standards). +To conform with the Japanese standards, it is necessary to set the flags' least +significant bit to 1. +The TEA5757; TEA5759 has a 25-bit read-write shift register. +The TEA5757 chips are used in +.Xr fms 4 +cards. +.Sh FILES +.Bl -tag -width /dev/radio -compact +.It Pa /dev/radio +.El +.Sh SEE ALSO +.Xr radioctl 1 , +.Xr ioctl 2 , +.Xr bktr 4 , +.Xr fms 4 , +.Xr intro 4 , +.Xr udsbr 4 , +.Xr radio 9 +.Sh HISTORY +The +.Nm +device driver appeared in +.Ox 3.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Vladimir Popov Aq Mt jumbo@narod.ru +and +.An Maxim Tsyplakov Aq Mt tm@oganer.net . +The man page was written by +.An Vladimir Popov Aq Mt jumbo@narod.ru . diff --git a/static/openbsd/man4/ral.4 b/static/openbsd/man4/ral.4 new file mode 100644 index 00000000..710d6104 --- /dev/null +++ b/static/openbsd/man4/ral.4 @@ -0,0 +1,369 @@ +.\" $OpenBSD: ral.4,v 1.118 2025/03/25 19:57:54 jmc Exp $ +.\" +.\" Copyright (c) 2005-2010 Damien Bergamini +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 25 2025 $ +.Dt RAL 4 +.Os +.Sh NAME +.Nm ral +.Nd Ralink Technology/MediaTek IEEE 802.11a/b/g/n wireless network device +.Sh SYNOPSIS +.Cd "ral* at cardbus?" +.Cd "ral* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports PCI/PCIe/CardBus wireless adapters based on the Ralink RT2500, +RT2501, RT2600, RT2700, RT2800, RT3090 and RT3900E chipsets. +.Pp +The RT2500 chipset is the first generation of 802.11b/g adapters from Ralink. +It consists of two integrated chips, an RT2560 MAC/BBP and an RT2525 radio +transceiver. +.Pp +The RT2501 chipset is the second generation of 802.11a/b/g adapters from +Ralink. +It consists of two integrated chips, an RT2561 MAC/BBP and an RT2527 radio +transceiver. +This chipset provides support for the IEEE 802.11e standard with multiple +hardware transmission queues and allows scatter/gather for efficient DMA +operations. +.Pp +The RT2600 chipset consists of two integrated chips, an RT2661 MAC/BBP and an +RT2529 radio transceiver. +This chipset uses the MIMO (multiple-input multiple-output) technology with +multiple radio transceivers to extend the operating range of the adapter and +to achieve higher throughput. +However, the RT2600 chipset does not support any of the 802.11n features. +.Pp +The RT2700 chipset is a low-cost version of the RT2800 chipset. +It supports a single transmit path and two receiver paths (1T2R). +It consists of two integrated chips, an RT2760 or RT2790 (PCIe) MAC/BBP and +an RT2720 (2.4GHz) or RT2750 (2.4GHz/5GHz) radio transceiver. +.Pp +The RT2800 chipset is the first generation of 802.11n adapters from Ralink. +It consists of two integrated chips, an RT2860 or RT2890 (PCIe) MAC/BBP and +an RT2820 (2.4GHz) or RT2850 (2.4GHz/5GHz) radio transceiver. +The RT2800 chipset supports two transmit paths and up to three receiver +paths (2T2R/2T3R). +It can achieve speeds up to 144Mbps (20MHz bandwidth) and 300Mbps (40MHz +bandwidth.) +.Pp +The RT3090 chipset is the first generation of single-chip 802.11n adapters +from Ralink. +.Pp +The RT3900E chipset is a single-chip 802.11n adapter from Ralink. +The MAC/Baseband Processor can be an RT3290, RT5390 or RT5392. +The RT3290 is a combo 802.11n and Bluetooth chip. +It operates in the 2GHz spectrum and supports one transmit path and on one +receiver path (1T1R). +The RT5390 chip operates in the 2GHz spectrum and supports one transmit path +and one receiver path (1T1R). +The RT5392 chip operates in the 2GHz spectrum and supports up to two transmit +paths and two receiver paths (2T2R). +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.It Host AP +In this mode the driver acts as an access point (base station) +for other cards. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +.Pp +The +.Nm +driver relies on the software 802.11 stack for both encryption and +decryption of data frames on the RT2500, RT2501 and RT2600 chipsets. +On the RT2700 and RT2800 chipsets, the +.Nm +driver offloads both encryption and decryption of data frames to the +hardware for the WEP40, WEP104, TKIP(+MIC) and CCMP ciphers. +.Pp +The transmit speed is user-selectable or can be adapted automatically by the +driver depending on the number of hardware transmission retries. +.Pp +In Host AP mode, +devices with the RT2700, RT2800, RT3090, and RT3900E chipsets +are compatible with clients using powersave. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The RT2501, RT2600, RT2700 and RT2800 chipsets require the following firmware +files to be loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It /etc/firmware/ral-rt2561 +.It /etc/firmware/ral-rt2561s +.It /etc/firmware/ral-rt2661 +.It /etc/firmware/ral-rt2860 +.It /etc/firmware/ral-rt3290 +.El +.Pp +The RT2500 chipset does not require a firmware file to operate. +.Sh HARDWARE +The following PCI adapters should work: +.Bd -filled +A-Link WL54H. +AirLive WN-5000PCI. +Amigo AWI-926W. +AMIT WL531P. +AOpen AOI-831. +ASUS WL-130G. +ASUS WL-130N. +ASUS WIFI-G-AAY. +Atlantis Land A02-PCI-W54. +Belkin F5D7000 v3. +Canyon CN-WF511. +CNet CWP-854. +Compex WLP54G. +Conceptronic C54Ri. +Corega CG-WLPCI54GL. +D-Link DWA-525 rev A2. +Digitus DN-7006G-RA. +Dynalink WLG25PCI. +E-Tech WGPI02. +Edimax EW-7128g. +Edimax EW-7628Ig. +Edimax EW-7728In. +Eminent EM3037. +Encore ENLWI-G-RLAM. +Eusso UGL2454-VPR. +Fiberline WL-400P. +Foxconn WLL-3350. +Gigabyte GN-WPKG. +Gigabyte GN-WP01GS. +Gigabyte GN-WI02GM. +Gigabyte GN-WP01GM. +Hawking HWP54GR. +Hercules HWGPCI-54. +iNexQ CR054g-009 (R03). +JAHT WN-4054PCI. +KCORP LifeStyle KLS-660. +LevelOne WNC-0301 v2. +Linksys WMP54G v4. +Longshine LCS-8031N. +Micronet SP906GK. +Minitar MN54GPC-R. +MSI MS-6834. +MSI PC54G2. +OvisLink EVO-W54PCI. +PheeNet HWL-PCIG/RA. +Planex PCI-GW-DS300N. +Pro-Nets PC80211G. +Repotec RP-WP0854. +SATech SN-54P. +Signamax 065-1798. +Sitecom WL-115. +SparkLAN WL-660R. +Surecom EP-9321-g. +Surecom EP-9321-g1. +Sweex LC700030. +TekComm NE-9321-g. +Tonze PC-6200C. +Unex CR054g-R02. +Zinwell ZWX-G361. +Zonet ZEW1600. +.Ed +.Pp +The following CardBus adapters should work: +.Bd -filled +A-Link WL54PC. +Alfa AWPC036. +Amigo AWI-914W. +AMIT WL531C. +ASUS WL-107G. +Atlantis Land A02-PCM-W54. +Belkin F5D7010 v2. +Canyon CN-WF513. +CC&C WL-2102. +CNet CWC-854. +Compex WL54. +Conceptronic C54RC. +Corega CG-WLCB54GL. +Digiconnect WL591C. +Digitus DN-7001G-RA. +Dynalink WLG25CARDBUS. +E-Tech WGPC02. +E-Tech WGPC03. +Edimax EW-7108PCg. +Edimax EW-7708PN. +Eminent EM3036. +Encore ENPWI-G-RLAM. +Eusso UGL2454-01R. +Fiberline WL-400X. +Gigabyte GN-WMKG. +Gigabyte GN-WM01GS. +Gigabyte GN-WM01GM. +Hawking HWC54GR. +Hercules HWGPCMCIA-54. +JAHT WN-4054P(E). +KCORP LifeStyle KLS-611. +LevelOne WPC-0301 v2. +Micronet SP908GK V3. +Minitar MN54GCB-R. +MSI CB54G2. +MSI MS-6835. +Pro-Nets CB80211G. +Repotec RP-WB7108. +SATech SN-54C. +Sitecom WL-112. +SparkLAN WL-611R. +SparkLAN WPCR-501. +Surecom EP-9428-g. +Sweex LC500050. +TekComm NE-9428-g. +Tonze PW-6200C. +Unex MR054g-R02. +Zinwell ZWX-G160. +Zonet ZEW1500. +.Ed +.Pp +The following Mini PCI adapters should work: +.Bd -filled +Amigo AWI-922W. +Billionton MIWLGRL. +Gigabyte GN-WIKG. +Gigabyte GN-WI01GS. +Gigabyte GN-WI02GM. +MSI MP54G2. +MSI MS-6833. +SparkLAN WMIR-215GN. +Tonze PC-620C. +Zinwell ZWX-G360. +.Ed +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig ral0 scan +.Pp +The following +.Xr hostname.if 5 +example configures ral0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +nwid mynwid wpakey mywpakey +inet autoconf +.Ed +.Pp +The following +.Xr hostname.if 5 +example creates a host-based access point on boot: +.Bd -literal -offset indent +mediaopt hostap +nwid mynwid wpakey mywpakey +inet 192.168.1.1 255.255.255.0 +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr cardbus 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr hostapd 8 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.7 . +Support for the RT2501 and RT2600 chipsets was added in +.Ox 3.9 . +Support for the RT2800 chipset was added in +.Ox 4.3 . +Support for the RT2700 chipset was added in +.Ox 4.4 . +Support for the RT3090 chipset was added in +.Ox 4.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +The +.Nm +driver does not make use of the hardware cryptographic engine present on +the RT2500, RT2501 and RT2600 chipsets. +.Pp +The +.Nm +driver does not support any of the 802.11n capabilities offered by +the RT2700, RT2800 and RT3090 chipsets. +Additional work is required in +.Xr ieee80211 9 +before those features can be supported. +.Pp +On the RT2500, RT2501 and RT2600 chipsets, host AP mode doesn't +support power saving. +Clients attempting to use power saving mode may experience significant +packet loss. +.Pp +Some PCI +.Nm +adapters seem to strictly require a system supporting PCI 2.2 or greater and +will likely not work in systems based on older revisions of the PCI +specification. +Check the board's PCI version before purchasing the card. diff --git a/static/openbsd/man4/random.4 b/static/openbsd/man4/random.4 new file mode 100644 index 00000000..e4bca376 --- /dev/null +++ b/static/openbsd/man4/random.4 @@ -0,0 +1,92 @@ +.\" $OpenBSD: random.4,v 1.36 2020/05/29 03:27:29 deraadt Exp $ +.\" +.\" Copyright (c) 1996, 1997 Michael Shalayeff +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 29 2020 $ +.Dt RANDOM 4 +.Os +.Sh NAME +.Nm random , +.Nm urandom +.Nd random data source device +.Sh DESCRIPTION +The +.Nm urandom +device produces high quality pseudo-random output data without ever +blocking. +.Pp +Entropy data stored previously is provided to the kernel during the +boot sequence and used as inner-state of a stream cipher. +High quality data is available immediately upon kernel startup. +System activity (such as disk, network, and clock device interrupts), +and hardware random generator output is collected, whitened with a crc +and hash, then periodically folded together with stream cipher +inner-state and outer-state to create a new inner state. +Reads from all consumers (including the kernel itself, which makes many +requests per second) are sliced from the same output stream, which carves +the stream cipher output unpredictably and helps improve forward and +backtracking protection beyond the strength of the stream cipher. +.Pp +The +.Nm urandom +device is intended to be used in scripts. +In C programs, use the +.Xr arc4random 3 +family of functions instead, which can be called in almost all +coding environments, including +.Xr pthreads 3 , +.Xr chroot 2 , +.Xr pledge 2 , +and +.Xr unveil 2 , +and which avoids accessing a filesystem device every time. +.Pp +For portability reasons, never use +.Pa /dev/random . +On +.Ox , +it is an alias for +.Pa /dev/urandom , +but on many other systems misbehaves by blocking because their +random number generators lack a robust boot-time initialization sequence. +.Sh FILES +.Bl -tag -width /dev/urandom -compact +.It Pa /dev/urandom +.El +.Sh SEE ALSO +.Xr arc4random 3 , +.Xr amdpm 4 , +.Xr glxsb 4 , +.Xr pchb 4 , +.Xr arc4random 9 +.Sh HISTORY +A +.Nm +device first appeared in Linux in 1994. +The +.Nm random +and +.Nm urandom +devices have been available since +.Ox 2.0 . diff --git a/static/openbsd/man4/rd.4 b/static/openbsd/man4/rd.4 new file mode 100644 index 00000000..fca90612 --- /dev/null +++ b/static/openbsd/man4/rd.4 @@ -0,0 +1,30 @@ +.\" $OpenBSD: rd.4,v 1.7 2019/04/16 13:58:45 sunil Exp $ +.\" +.\" This file is in the public domain. +.\" +.Dd $Mdocdate: April 16 2019 $ +.Dt RD 4 +.Os +.Sh NAME +.Nm rd +.Nd ramdisk driver +.Sh SYNOPSIS +.Cd "pseudo-device rd" Op Ar count +.Sh DESCRIPTION +The +.Nm +driver enables use of system or user memory as a disk. +Memory for the disk must be allocated and initialized inside the +kernel image at build-time using the +.Cm rdsetroot +tool. +.Sh FILES +.Bl -tag -width /dev/rrd??XXX -compact +.It Pa "/dev/rd??" +Block mode ramdisk devices. +.It Pa "/dev/rrd??" +Raw mode ramdisk devices. +.El +.Sh SEE ALSO +.Xr elf 5 , +.Xr rdsetroot 8 diff --git a/static/openbsd/man4/rdac.4 b/static/openbsd/man4/rdac.4 new file mode 100644 index 00000000..124efcaa --- /dev/null +++ b/static/openbsd/man4/rdac.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: rdac.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2011 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt RDAC 4 +.Os +.Sh NAME +.Nm rdac +.Nd Engenio/LSI RDAC SCSI devices +.Sh SYNOPSIS +.Cd "rdac* at scsibus?" +.Sh DESCRIPTION +The +.Nm +driver attaches to Engenio/LSI RDAC SCSI logical units. +Each path to an active service processor attached to by +.Nm +is presented to +.Xr mpath 4 +which uses it as a backend to the logical unit attached to its own +.Xr scsibus 4 . +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr intro 4 , +.Xr mpath 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.0 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/rdcphy.4 b/static/openbsd/man4/rdcphy.4 new file mode 100644 index 00000000..02d809f2 --- /dev/null +++ b/static/openbsd/man4/rdcphy.4 @@ -0,0 +1,33 @@ +.\" $OpenBSD: rdcphy.4,v 1.1 2011/01/15 04:35:34 kevlo Exp $ +.\" +.\" Copyright (c) 2011 Kevin Lo +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 15 2011 $ +.Dt RDCPHY 4 +.Os +.Sh NAME +.Nm rdcphy +.Nd RDC Semiconductor R6040 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "rdcphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the RDC Semiconductor R6040 10/100 Ethernet PHY. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/rdomain.4 b/static/openbsd/man4/rdomain.4 new file mode 100644 index 00000000..06100606 --- /dev/null +++ b/static/openbsd/man4/rdomain.4 @@ -0,0 +1,161 @@ +.\" $OpenBSD: rdomain.4,v 1.19 2022/07/29 18:28:32 kn Exp $ +.\" +.\" Copyright (c) 2015 Peter Hessler +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 29 2022 $ +.Dt RDOMAIN 4 +.Os +.Sh NAME +.Nm rtable , +.Nm rdomain +.Nd routing tables and routing domains +.Sh DESCRIPTION +The traditional kernel routing system had a single table for routes and +allowed only non-conflicting IP address assignments. +The +.Nm rtable +feature allows multiple lookup tables for routes. +The +.Nm rdomain +feature provides a way to logically segment a router +between network paths. +.Ss Routing tables +Each +.Nm rtable +contains routes for outbound network packets. +A routing domain can contain more than one +.Nm rtable . +Multiple routing tables are commonly used for Policy Based Routing. +.Pp +The highest ID that can be used for an +.Nm rtable +is 255. +.Ss Routing domains +Each +.Nm rdomain +is a completely separate address space in the kernel. +An IP address (e.g. 10.0.0.1/16) can be assigned in more than one +.Nm rdomain , +but cannot be assigned more than once per +.Nm rdomain . +An interface belongs to one and only one +.Nm rdomain . +The interface's +.Nm rdomain +determines which rdomain an incoming packet will +be in. +Virtual interfaces do not need to belong to the same +.Nm rdomain +as the parent. +Each +.Nm rdomain +contains at least one routing table. +.Pp +Network traffic within an +.Nm rdomain +stays within the current routing domain. +.Xr pf 4 +is used to move traffic from one +.Nm rdomain +to a different +.Nm rdomain . +.Pp +When an interface is assigned to a non-existent +.Nm rdomain , +it gets created automatically. +At the same time an +.Nm rtable +with the same ID and a +.Xr lo 4 +interface with a unit number matching the ID get created and assigned to the new +domain. +.Pp +An rdomain can be deleted by removing all interfaces from it and then +destroying the +.Xr lo 4 +interface with the unit number matching the ID. +.Pp +The highest ID that can be used for an +.Nm rdomain +is 255. +.Sh EXAMPLES +Put em0 and lo4 in rdomain 4: +.Bd -literal -offset indent +# ifconfig em0 rdomain 4 +# ifconfig lo4 inet 127.0.0.1/8 +# ifconfig em0 192.0.2.100/24 +.Ed +.Pp +List all rdomains with associated interfaces and routing tables: +.Pp +.Dl $ netstat -R +.Pp +Set a default route and localhost reject route within rtable 4: +.Bd -literal -offset indent +# route -T4 -qn add -net 127 127.0.0.1 -reject +# route -T4 -n add default 192.0.2.1 +.Ed +.Pp +Start +.Xr sshd 8 +in rtable 4: +.Pp +.Dl # route -T4 exec /usr/sbin/sshd +.Pp +Display the routing table used by each process: +.Pp +.Dl $ ps aux -o rtable +.Pp +Display the routing table of the current process: +.Pp +.Dl $ id -R +.Pp +A +.Xr pf.conf 5 +snippet to block incoming port 80, +and nat-to and move to rtable 0 on interface em1: +.Bd -literal -offset indent +block in on rdomain 4 proto tcp to any port 80 +match out on rdomain 4 to !$internal_net nat-to (em1) rtable 0 +.Ed +.Pp +Delete rdomain 4 again: +.Bd -literal -offset indent +# ifconfig em0 -rdomain +# ifconfig lo4 destroy +.Ed +.Sh SEE ALSO +.Xr id 1 , +.Xr netstat 1 , +.Xr ps 1 , +.Xr lo 4 , +.Xr route 4 , +.Xr pf.conf 5 , +.Xr ifconfig 8 , +.Xr route 8 +.Sh HISTORY +.Ox +support for +.Nm rdomain +first appeared in +.Ox 4.9 +and IPv6 support first appeared in +.Ox 5.5 . +.Sh CAVEATS +No tool is available to assign more than one rtable to an rdomain +other than to the default one (0). +.Pp +An rtable cannot be deleted. +Deleting an rdomain will move its rtable into the default rdomain. diff --git a/static/openbsd/man4/re.4 b/static/openbsd/man4/re.4 new file mode 100644 index 00000000..cedbd80f --- /dev/null +++ b/static/openbsd/man4/re.4 @@ -0,0 +1,221 @@ +.\" $OpenBSD: re.4,v 1.56 2022/02/18 10:24:32 jsg Exp $ +.\" Copyright (c) 2003 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/re.4,v 1.4 2004/03/04 06:42:46 sanpei Exp $ +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt RE 4 +.Os +.Sh NAME +.Nm re +.Nd Realtek 8139C+/8169/816xS/811xS/8168/810xE 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "re* at pci?" +.Cd "re* at cardbus?" +.Cd "eephy* at mii?" +.Cd "rgephy* at mii?" +.Cd "rlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various NICs based on the +Realtek RTL8139C+, RTL8169, RTL816xS, RTL811xS, RTL8168 and +RTL810xE PCI and PCI Express Ethernet controllers, +including the following: +.Pp +.Bl -bullet -compact +.It +Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+) +.It +Buffalo LGY-PCI-GT (8169S) +.It +Compaq Evo N1015v Integrated Ethernet (8139C+) +.It +Corega CG-LAPCIGT (8169S) +.It +D-Link DGE-528T (8169S) +.It +D-Link DGE-530T C1 (8169/8110SB) +.It +D-Link DGE-660TD (8169/8110SB) +.It +Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S) +.It +LevelOne GNC-0105T (8169S) +.It +Linksys EG1032v3 (8169S) +.It +Netgear GA311 (8169S) +.It +Netgear GA511 PC Card (8169) +.It +PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S) +.It +Surecom EP-320G-TX1 (8169S) +.It +TTTech MC322 (8139C+) +.It +US Robotics USR997902 (8169S) +.It +Xterasys XN-152 10/100/1000 NIC (8169) +.El +.Pp +NICs based on the 8139C+ and 810xE are capable of 10 and 100Mbps speeds +over CAT5 cable. +NICs based on the 8169, 816xS, 811xS and 8168 are capable of 10, 100 and +1000Mbps operation. +.Pp +All +.Nm +NICs support +IPv4 transmit/receive IP/TCP/UDP checksum offload, VLAN tag insertion and +stripping, and use a descriptor-based DMA mechanism. +The 8102E(L), 8103E(L), 8168C/8111C, 8168D/8111D, 8168DP/8111DP and +8168E/8111E chips also support IPv6 receive TCP/UDP checksum offload. +.Pp +The 8139C+ is a single-chip solution combining both a 10/100 MAC and PHY. +The 8169 is a 10/100/1000 MAC only, requiring a GMII or TBI external PHY. +The 8169S, 8110S, 8111B and 8168 are single-chip devices +containing both a 10/100/1000 MAC and 10/100/1000 copper PHY. +Standalone 10/100/1000 cards are available in both 32-bit PCI and 64-bit +PCI models. +The 8110S and 8111B are designed for embedded LAN-on-motherboard applications. +.Pp +The 8168, 8169, 8169S and 8110S also support jumbo frames. +.Pp +The +.Nm +driver additionally supports Wake on LAN (WoL). +See +.Xr arp 8 +and +.Xr ifconfig 8 +for more details. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width 10baseTXUTP +.It autoselect +Enable autoselection of the media type and options. +The user can manually override the autoselected mode by adding media options +to the appropriate +.Xr hostname.if 5 +file. +.It 10baseT/UTP +Set 10Mbps operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 1000baseT +Set 1000baseT operation over twisted pair. +The Realtek GigE chips support 1000Mbps in +.Ar full-duplex +mode only. +.\" .It 1000baseSX +.\" Set 1000Mbps (Gigabit Ethernet) operation. +.\" Both +.\" .Ar full-duplex +.\" and +.\" .Ar half-duplex +.\" modes are supported. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation. +.It half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr eephy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr rgephy 4 , +.Xr rlphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T Realtek Semiconductor RTL8139C+, RTL8169, RTL8169S and RTL8110S datasheets +.%U https://www.realtek.com/en +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@windriver.com +and ported to +.Ox +by +.An Peter Valchev Aq Mt pvalchev@openbsd.org . +.Sh BUGS +The Xterasys XN-152 32-bit PCI NIC, which uses the RTL8169 MAC and +Marvell 88E1000 PHY, has a defect that causes DMA corruption +if the board is plugged into a 64-bit PCI slot. +The defect lies in the board design, not the chip itself: the PCI REQ64# +and ACK64# lines should be pulled high, but they are not. +The result is that the 8169 chip is tricked into performing 64-bit DMA +transfers even though a 64-bit data path between the NIC and the bus does +not actually exist. +.Pp +Unfortunately, it is not possible to correct this problem in software. +The user should ensure the NIC is installed in a 32-bit PCI slot to avoid +this problem. diff --git a/static/openbsd/man4/rge.4 b/static/openbsd/man4/rge.4 new file mode 100644 index 00000000..8a1b3bf4 --- /dev/null +++ b/static/openbsd/man4/rge.4 @@ -0,0 +1,75 @@ +.\" $OpenBSD: rge.4,v 1.9 2025/09/19 00:42:06 kevlo Exp $ +.\" +.\" Copyright (c) 2019, 2020, 2024 Kevin Lo +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 19 2025 $ +.Dt RGE 4 +.Os +.Sh NAME +.Nm rge +.Nd Realtek 8125/8126/8127 PCI Express 10/100/1Gb/2.5Gb/5Gb/10Gb +Ethernet device +.Sh SYNOPSIS +.Cd "rge* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for NICs based on the +Realtek RTL8125, RTL8126 and RTL8127 PCI Express Ethernet controllers, +including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +IOCrest IO-PCE8126-GLAN Adapter (5000baseT) +.It +Realtek 8125/8125B 2.5GbE Adapter (2500baseT) +.It +Rivet Networks Killer E3000 Adapter (2500baseT) +.It +TP-LINK TL-NG421 Adapter (2500baseT) +.El +.Pp +NICs based on the RTL8125 are capable of 10, 100, 1000 and 2500Mbps operation. +NICs based on the RTL8126 are capable of 10, 100, 1000, 2500 and +5000Mbps operation. +The RTL8127 supports 10Gbps speed. +.Pp +The +.Nm +driver additionally supports Wake on LAN (WoL). +See +.Xr arp 8 +and +.Xr ifconfig 8 +for more details. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Kevin Lo Aq Mt kevlo@openbsd.org . diff --git a/static/openbsd/man4/rgephy.4 b/static/openbsd/man4/rgephy.4 new file mode 100644 index 00000000..6041aab0 --- /dev/null +++ b/static/openbsd/man4/rgephy.4 @@ -0,0 +1,34 @@ +.\" $OpenBSD: rgephy.4,v 1.10 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2004 Peter Valchev +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt RGEPHY 4 +.Os +.Sh NAME +.Nm rgephy +.Nd Realtek 8169S/8110S/8211B/8211C 10/100/1Gb Ethernet PHY +.Sh SYNOPSIS +.Cd "rgephy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the internal PHY found on Realtek 8169S/8110S +Ethernet adapters and the external 8211B/8211C PHY. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/ricohrtc.4 b/static/openbsd/man4/ricohrtc.4 new file mode 100644 index 00000000..7442709d --- /dev/null +++ b/static/openbsd/man4/ricohrtc.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: ricohrtc.4,v 1.5 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt RICOHRTC 4 +.Os +.Sh NAME +.Nm ricohrtc +.Nd Ricoh RS5C372 real-time clock +.Sh SYNOPSIS +.Cd "ricohrtc* at iic? addr 0x32" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Ricoh RS5C372 real-time clock chip. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Dale Rahn Aq Mt drahn@openbsd.org . diff --git a/static/openbsd/man4/rkanxdp.4 b/static/openbsd/man4/rkanxdp.4 new file mode 100644 index 00000000..5cdfb4f7 --- /dev/null +++ b/static/openbsd/man4/rkanxdp.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: rkanxdp.4,v 1.4 2020/03/05 03:03:26 jsg Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 5 2020 $ +.Dt RKANXDP 4 +.Os +.Sh NAME +.Nm rkanxdp +.Nd Rockchip eDP transmitter +.Sh SYNOPSIS +.Cd "rkanxdp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the Analogix eDP transmitter integrated on +Rockchip SoCs. +.Sh SEE ALSO +.Xr drm 4 , +.Xr intro 4 , +.Xr rkdrm 4 , +.Xr rkdwhdmi 4 , +.Xr rkvop 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan A. Kollasch +for +.Nx +and ported to +.Ox +by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/rkclock.4 b/static/openbsd/man4/rkclock.4 new file mode 100644 index 00000000..c84004e5 --- /dev/null +++ b/static/openbsd/man4/rkclock.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: rkclock.4,v 1.2 2018/03/31 09:44:35 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2018 $ +.Dt RKCLOCK 4 +.Os +.Sh NAME +.Nm rkclock +.Nd Rockchip Clock and Reset Unit +.Sh SYNOPSIS +.Cd "rkclock* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls clock gating for integrated components of Rockchip SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkcomphy.4 b/static/openbsd/man4/rkcomphy.4 new file mode 100644 index 00000000..319b90cc --- /dev/null +++ b/static/openbsd/man4/rkcomphy.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: rkcomphy.4,v 1.3 2026/03/26 06:12:38 jmatthew Exp $ +.\" +.\" Copyright (c) 2023 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 26 2026 $ +.Dt RKCOMPHY 4 +.Os +.Sh NAME +.Nm rkcomphy +.Nd Rockchip PCIe/USB3/SATA/QSGMII PHY +.Sh SYNOPSIS +.Cd "rkcomphy* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the combo PIPE PHY integrated on Rockchip +RK3528, RK3566/RK3568 and RK3588 SoCs. +The PHY supports the PCIe 2.0 (2.5 GT/s and 5 GT/s), USB 3.0 (5 Gbps), +SATA (1.5 Gbit/s, 3 Gbit/s and 6 Gbit/s) and QSGMII (1.25 Gbit/s and 5 +Gbit/s) protocols. +The +.Nm +driver does not implement support for QSGMII, and on the RK3528 SoC, +only PCIe is supported. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkdrm.4 b/static/openbsd/man4/rkdrm.4 new file mode 100644 index 00000000..55f25efc --- /dev/null +++ b/static/openbsd/man4/rkdrm.4 @@ -0,0 +1,54 @@ +.\" $OpenBSD: rkdrm.4,v 1.3 2020/03/04 23:10:55 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 4 2020 $ +.Dt RKDRM 4 +.Os +.Sh NAME +.Nm rkdrm +.Nd Rockchip DRM subsystem +.Sh SYNOPSIS +.Cd "rkdrm* at fdt?" +.Cd "drm* at rkdrm?" +.Cd "wsdisplay* at rkdrm?" +.Sh DESCRIPTION +The +.Nm +driver provides kernel mode setting (KMS) functionality for the +graphics hardware integrated on Rockchip SoCs. +.Sh SEE ALSO +.Xr drm 4 , +.Xr intro 4 , +.Xr rkanxdp 4 , +.Xr rkdwhdmi 4 , +.Xr rkvop 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared D. McNeill +for +.Nx +and ported to +.Ox +by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/rkdwhdmi.4 b/static/openbsd/man4/rkdwhdmi.4 new file mode 100644 index 00000000..f84a9ef4 --- /dev/null +++ b/static/openbsd/man4/rkdwhdmi.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: rkdwhdmi.4,v 1.5 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt RKDWHDMI 4 +.Os +.Sh NAME +.Nm rkdwhdmi +.Nd Rockchip HDMI transmitter +.Sh SYNOPSIS +.Cd "rkdwhdmi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the Synopsys DesignWare HDMI transmitter integrated on +Rockchip SoCs. +.Sh SEE ALSO +.Xr drm 4 , +.Xr intro 4 , +.Xr rkanxdp 4 , +.Xr rkdrm 4 , +.Xr rkvop 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared D. McNeill +for +.Nx +and ported to +.Ox +by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkdwusb.4 b/static/openbsd/man4/rkdwusb.4 new file mode 100644 index 00000000..2aa72590 --- /dev/null +++ b/static/openbsd/man4/rkdwusb.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: rkdwusb.4,v 1.1 2018/08/27 20:09:29 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 27 2018 $ +.Dt RKDWUSB 4 +.Os +.Sh NAME +.Nm rkdwusb +.Nd Rockchip USB 3.0 glue logic +.Sh SYNOPSIS +.Cd "rkdwusb* at fdt?" +.Cd "xhci* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the interface logic for the Synopsys DesignWare USB +3.0 controller on Rockchip SoCs. +.Sh SEE ALSO +.Xr intro 4 , +.Xr xhci 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkemmcphy.4 b/static/openbsd/man4/rkemmcphy.4 new file mode 100644 index 00000000..8a519128 --- /dev/null +++ b/static/openbsd/man4/rkemmcphy.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: rkemmcphy.4,v 1.1 2019/12/03 09:46:46 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 3 2019 $ +.Dt RKEMMCPHY 4 +.Os +.Sh NAME +.Nm rkemmcphy +.Nd Rockchip eMMC PHY +.Sh SYNOPSIS +.Cd "rkemmcphy* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the eMMC PHY integrated on Rockchip SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/rkgpio.4 b/static/openbsd/man4/rkgpio.4 new file mode 100644 index 00000000..7d5c9e71 --- /dev/null +++ b/static/openbsd/man4/rkgpio.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: rkgpio.4,v 1.1 2018/04/01 09:03:25 jsg Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 1 2018 $ +.Dt RKGPIO 4 +.Os +.Sh NAME +.Nm rkgpio +.Nd Rockchip GPIO controller +.Sh SYNOPSIS +.Cd "rkgpio* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO ports found on Rockchip SoCs. +It does not provide direct device driver entry points but makes its +functions available to other drivers. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkgrf.4 b/static/openbsd/man4/rkgrf.4 new file mode 100644 index 00000000..21ea3d36 --- /dev/null +++ b/static/openbsd/man4/rkgrf.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: rkgrf.4,v 1.2 2018/03/31 09:44:35 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2018 $ +.Dt RKGRF 4 +.Os +.Sh NAME +.Nm rkgrf +.Nd Rockchip Generic Register File +.Sh SYNOPSIS +.Cd "rkgrf* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver makes the Generic Register Files in Rockchip SoCs available to other +drivers through the regmap interface. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkiic.4 b/static/openbsd/man4/rkiic.4 new file mode 100644 index 00000000..6e9b6085 --- /dev/null +++ b/static/openbsd/man4/rkiic.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: rkiic.4,v 1.1 2018/04/01 09:03:25 jsg Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 1 2018 $ +.Dt RKIIC 4 +.Os +.Sh NAME +.Nm rkiic +.Nd Rockchip I2C controller +.Sh SYNOPSIS +.Cd "rkiic* at fdt?" +.Cd "iic* at rkiic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the I2C controller integrated in various +Rockchip SoCs. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkiis.4 b/static/openbsd/man4/rkiis.4 new file mode 100644 index 00000000..a468ac8b --- /dev/null +++ b/static/openbsd/man4/rkiis.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: rkiis.4,v 1.1 2020/06/11 00:10:57 patrick Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 11 2020 $ +.Dt RKIIS 4 +.Os +.Sh NAME +.Nm rkiis +.Nd Rockchip I2S controller +.Sh SYNOPSIS +.Cd "rkiis* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the I2S controller integrated in various +Rockchip SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared McNeill Aq Mt jmcneill@invisible.ca +for +.Nx +and ported to +.Ox +by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/rkiovd.4 b/static/openbsd/man4/rkiovd.4 new file mode 100644 index 00000000..ad27fd73 --- /dev/null +++ b/static/openbsd/man4/rkiovd.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: rkiovd.4,v 1.1 2023/04/01 08:48:04 kettenis Exp $ +.\" +.\" Copyright (c) 2023 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 1 2023 $ +.Dt RKIOVD 4 +.Os +.Sh NAME +.Nm rkiovd +.Nd Rockchip I/O voltage domains +.Sh SYNOPSIS +.Cd "rkiovd* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the I/O voltage domains of the Rockchip RK3566/RK3568 +SoCs. +It makes sure the voltage configuration of the domains stays +synchronized with the regulators that supply the voltage to these +domains. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkpcie.4 b/static/openbsd/man4/rkpcie.4 new file mode 100644 index 00000000..1632fd2d --- /dev/null +++ b/static/openbsd/man4/rkpcie.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: rkpcie.4,v 1.3 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt RKPCIE 4 +.Os +.Sh NAME +.Nm rkpcie +.Nd Rockchip RK3399 Host/PCIe bridge +.Sh SYNOPSIS +.Cd "rkpcie* at fdt?" +.Cd "pci* at rkpcie?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PCIe controller found on the +Rockchip RK3399 SoC. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkpciephy.4 b/static/openbsd/man4/rkpciephy.4 new file mode 100644 index 00000000..e613f6ae --- /dev/null +++ b/static/openbsd/man4/rkpciephy.4 @@ -0,0 +1,41 @@ +.\" $OpenBSD: rkpciephy.4,v 1.1 2023/03/19 11:22:50 kettenis Exp $ +.\" +.\" Copyright (c) 2023 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 19 2023 $ +.Dt RKPCIEPHY 4 +.Os +.Sh NAME +.Nm rkpciephy +.Nd Rockchip PCIe 3.0 PHY +.Sh SYNOPSIS +.Cd "rkpciephy* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the PCIe 3.0 PHY integrated on Rockchip RK3568 SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkpinctrl.4 b/static/openbsd/man4/rkpinctrl.4 new file mode 100644 index 00000000..2fa1e937 --- /dev/null +++ b/static/openbsd/man4/rkpinctrl.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: rkpinctrl.4,v 1.2 2018/03/31 09:44:35 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2018 $ +.Dt RKPINCTRL 4 +.Os +.Sh NAME +.Nm rkpinctrl +.Nd Rockchip pin multiplexing +.Sh SYNOPSIS +.Cd "rkpinctrl* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver uses pin control data from the device tree to select one of +multiple possible roles available for pins on Rockchip SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkpmic.4 b/static/openbsd/man4/rkpmic.4 new file mode 100644 index 00000000..ecb17288 --- /dev/null +++ b/static/openbsd/man4/rkpmic.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: rkpmic.4,v 1.3 2024/03/02 20:22:13 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 2 2024 $ +.Dt RKPMIC 4 +.Os +.Sh NAME +.Nm rkpmic +.Nd Rockchip RK8xx Power Management IC +.Sh SYNOPSIS +.Cd "rkpmic* at iic?" +.Cd "rkpmic* at spi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the voltage regulators and real-time clock in the +Rockchip RK805, RK806, RK808 and RK809 Power Management ICs. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkpwm.4 b/static/openbsd/man4/rkpwm.4 new file mode 100644 index 00000000..6ee9f197 --- /dev/null +++ b/static/openbsd/man4/rkpwm.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: rkpwm.4,v 1.1 2019/12/03 09:37:04 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 3 2019 $ +.Dt RKPWM 4 +.Os +.Sh NAME +.Nm rkpwm +.Nd Rockchip PWM controller +.Sh SYNOPSIS +.Cd "rkpwm* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PWM controllers integrated on various +Rockchip SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/rkrng.4 b/static/openbsd/man4/rkrng.4 new file mode 100644 index 00000000..de6c7cae --- /dev/null +++ b/static/openbsd/man4/rkrng.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: rkrng.4,v 1.2 2020/04/05 13:19:49 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 5 2020 $ +.Dt RKRNG 4 +.Os +.Sh NAME +.Nm rkrng +.Nd Rockchip random number generator +.Sh SYNOPSIS +.Cd "rkrng* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the random number generator found on the +Rockchip SoCs. +.Pp +It feeds the random subsystem's entropy pool with 256 bits of random +data every second. +.Sh SEE ALSO +.Xr intro 4 , +.Xr random 4 , +.Xr arc4random 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkspi.4 b/static/openbsd/man4/rkspi.4 new file mode 100644 index 00000000..1b8482ed --- /dev/null +++ b/static/openbsd/man4/rkspi.4 @@ -0,0 +1,43 @@ +.\" $OpenBSD: rkspi.4,v 1.1 2024/03/02 20:21:33 kettenis Exp $ +.\" +.\" Copyright (c) 2024 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 2 2024 $ +.Dt RKSPI 4 +.Os +.Sh NAME +.Nm rkspi +.Nd Rockchip SPI controller +.Sh SYNOPSIS +.Cd "rkspi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SPI controller integrated on various +Rockchip SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se +and +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rktcphy.4 b/static/openbsd/man4/rktcphy.4 new file mode 100644 index 00000000..829ac6c2 --- /dev/null +++ b/static/openbsd/man4/rktcphy.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: rktcphy.4,v 1.1 2021/06/29 12:51:18 patrick Exp $ +.\" +.\" Copyright (c) 2021 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 29 2021 $ +.Dt RKTCPHY 4 +.Os +.Sh NAME +.Nm rktcphy +.Nd Rockchip Type-C PHY +.Sh SYNOPSIS +.Cd "rktcphy* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the Type-C PHY integrated on Rockchip SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Emmanuel Vadot +for +.Fx +and ported to +.Ox +by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/rktemp.4 b/static/openbsd/man4/rktemp.4 new file mode 100644 index 00000000..79c7d104 --- /dev/null +++ b/static/openbsd/man4/rktemp.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: rktemp.4,v 1.5 2024/06/12 09:08:43 kettenis Exp $ +.\" +.\" Copyright (c) 2016 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 12 2024 $ +.Dt RKTEMP 4 +.Os +.Sh NAME +.Nm rktemp +.Nd Rockchip temperature monitor +.Sh SYNOPSIS +.Cd "rktemp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensor found on the +Rockchip RK3288, RK3308, RK3328, RK3399 RK356x and RK3588 SoCs. +It configures the SoC to reset itself if the temperature raises above +a certain temperature to protect it from damage caused by overheating. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/rkusbphy.4 b/static/openbsd/man4/rkusbphy.4 new file mode 100644 index 00000000..a140aedf --- /dev/null +++ b/static/openbsd/man4/rkusbphy.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: rkusbphy.4,v 1.1 2023/04/02 01:40:52 dlg Exp $ +.\" +.\" Copyright (c) 2023 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 2 2023 $ +.Dt RKUSBPHY 4 +.Os +.Sh NAME +.Nm rkusbphy +.Nd Rockchip USB2PHY with Innosilicon IP driver +.Sh SYNOPSIS +.Cd "rkusbphy* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the USB2PHY integrated on Rockchip RK3566/RK3568 +SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/rkvop.4 b/static/openbsd/man4/rkvop.4 new file mode 100644 index 00000000..68e6778a --- /dev/null +++ b/static/openbsd/man4/rkvop.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: rkvop.4,v 1.3 2020/03/04 23:10:55 jmc Exp $ +.\" +.\" Copyright (c) 2020 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 4 2020 $ +.Dt RKVOP 4 +.Os +.Sh NAME +.Nm rkvop +.Nd Rockchip video output processor +.Sh SYNOPSIS +.Cd "rkvop* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver controls the video output processor integrated on +Rockchip SoCs. +.Sh SEE ALSO +.Xr drm 4 , +.Xr intro 4 , +.Xr rkanxdp 4 , +.Xr rkdrm 4 , +.Xr rkdwhdmi 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared D. McNeill +for +.Nx +and ported to +.Ox +by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/rl.4 b/static/openbsd/man4/rl.4 new file mode 100644 index 00000000..e769b715 --- /dev/null +++ b/static/openbsd/man4/rl.4 @@ -0,0 +1,222 @@ +.\" $OpenBSD: rl.4,v 1.37 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 1997, 1998 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: rl.4,v 1.7 1998/12/24 18:52:47 wpaul Exp $ +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt RL 4 +.Os +.Sh NAME +.Nm rl +.Nd Realtek 8129/8139 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "rl* at pci?" +.Cd "rl* at cardbus?" +.Cd "rlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI Ethernet adapters and embedded +controllers based on the Realtek 8129 and 8139 Fast Ethernet controller +chips. +This includes, among others, the following cards: +.Pp +.Bl -item -offset indent -compact +.It +Accton MPX5030 CardBus +.It +Allied Telesyn AT2550 +.It +Corega FEther CB-TXD 10/100 Ethernet +.It +D-Link DFE-520TX C1, DFE-530TX+, DFE-538TX, DFE-690TXD +.It +Encore ENL832-TX-RENT 10/100 M PCI +.It +Genius GF100TXR +.It +KTX-9130TX 10/100 Fast Ethernet +.It +Longshine LCS-8038TX-R +.It +NDC Communications NE100TX-E +.It +Netgear FA311 v2 +.It +Netronix Inc. EA-1210 NetEther 10/100 +.It +Nortel BayStack 21 +.It +OvisLink LEF-8129TX, LEF-8139TX +.It +SMC EZ Card 10/100 PCI 1211-TX +.It +TRENDnet TE100-PCBUSR CardBus +.El +.Pp +The Realtek controllers use bus master DMA but do not use a +descriptor-based data transfer mechanism. +The receiver uses a single fixed size ring buffer from which packets must be +copied into mbufs. +For transmission, there are only four outbound packet +address registers which require all outgoing packets to be stored +as contiguous buffers. +Furthermore, outbound packet buffers must be longword aligned or else +transmission will fail. +.Pp +The 8129 differs from the 8139 in that the 8139 has an internal +PHY which is controlled through special direct access registers +whereas the 8129 uses an external PHY via an MII bus. +The 8139 supports both 10 and 100Mbps speeds in either full or half duplex. +The 8129 can support the same speeds and modes given an appropriate +PHY chip. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +This is only supported if the PHY chip attached to the Realtek controller +supports NWAY autonegotiation. +The user can manually override the autoselected mode by adding media options +to the appropriate +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation. +.It half-duplex +Force half duplex operation. +.El +.Pp +Note that the 100baseTX media type is only available if supported +by the adapter. +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "rl0: couldn't map memory" +A fatal initialization error has occurred. +.It "rl0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "rl0: watchdog timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.It "rl0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.It "rl0: no memory for tx list" +The driver failed to allocate an mbuf for the transmitter ring when +allocating a pad buffer or collapsing an mbuf chain into a cluster. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr rlphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%B The Realtek 8129 and 8139 datasheets +.%O ftp.realtek.com.tw:/lancard/data sheet +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 3.0 . +.Ox +support first appeared in +.Ox 2.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ctr.columbia.edu . +.Sh BUGS +Since outbound packets must be longword aligned, the transmit +routine has to copy an unaligned packet into an mbuf cluster buffer +before transmission. +The driver abuses the fact that the cluster buffer +pool is allocated at system startup time in a contiguous region starting +at a page boundary. +Since cluster buffers are 2048 bytes, they are +longword aligned by definition. +The driver probably should not be +depending on this characteristic. +.Pp +The Realtek data sheets are of especially poor quality: the grammar +and spelling are awful and there is a lot of information missing, +particularly concerning the receiver operation. +One particularly important fact that the data sheets fail to mention +relates to the way in which the chip fills in the receive buffer. +When an interrupt is posted to signal that a frame has been received, +it is possible that another frame might be in the process of being +copied into the receive buffer while the driver is busy handling +the first one. +If the driver +manages to finish processing the first frame before the chip is done +DMAing the rest of the next frame, the driver may attempt to process +the next frame in the buffer before the chip has had a chance to finish +DMAing all of it. +.Pp +The driver can check for an incomplete frame by inspecting the frame +length in the header preceding the actual packet data: an incomplete +frame will have the magic length of 0xFFF0. +When the driver encounters this value, it knows that it has finished +processing all currently available packets. +Neither this magic value nor its significance are +documented anywhere in the Realtek data sheets. diff --git a/static/openbsd/man4/rlphy.4 b/static/openbsd/man4/rlphy.4 new file mode 100644 index 00000000..5842482c --- /dev/null +++ b/static/openbsd/man4/rlphy.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: rlphy.4,v 1.15 2009/07/31 14:20:29 jmc Exp $ +.\" +.\" Copyright (c) 1998 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 31 2009 $ +.Dt RLPHY 4 +.Os +.Sh NAME +.Nm rlphy +.Nd Realtek 8139/8201L Ethernet PHY +.Sh SYNOPSIS +.Cd "rlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the internal physical layer interface (PHY) found on +Realtek Semiconductor +.Tn RTL8139 +based Ethernet adapters, the Realtek Semiconductor +.Tn RTL8201L +Ethernet PHY chip and the IC Plus Corp +.Tn IP101 +Ethernet PHY chip. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/route.4 b/static/openbsd/man4/route.4 new file mode 100644 index 00000000..5f96e4f0 --- /dev/null +++ b/static/openbsd/man4/route.4 @@ -0,0 +1,518 @@ +.\" $OpenBSD: route.4,v 1.56 2021/11/10 20:24:22 bket Exp $ +.\" $NetBSD: route.4,v 1.3 1994/11/30 16:22:31 jtc Exp $ +.\" +.\" Copyright (c) 1990, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)route.4 8.6 (Berkeley) 4/19/94 +.\" +.Dd $Mdocdate: November 10 2021 $ +.Dt ROUTE 4 +.Os +.Sh NAME +.Nm route +.Nd kernel packet forwarding database +.Sh SYNOPSIS +.In sys/socket.h +.In net/if.h +.In net/route.h +.Ft int +.Fn socket AF_ROUTE SOCK_RAW family +.Sh DESCRIPTION +.Ox +provides some packet routing facilities. +The kernel maintains a routing information database, which +is used in selecting the appropriate network interface when +transmitting packets. +.Pp +A user process (or possibly multiple co-operating processes) +maintains this database by sending messages over a special kind +of socket. +This supplants fixed size +.Xr ioctl 2 Ns 's +used in earlier releases. +Routing table changes may only be carried out by the super user. +.Pp +The operating system may spontaneously emit routing messages in response +to external events, such as receipt of a redirect, or failure to +locate a suitable route for a request. +The message types are described in greater detail below. +.Pp +Routing database entries come in two flavors: for a specific +host, or for all hosts on a generic subnetwork (as specified +by a bit mask and value under the mask). +The effect of wildcard or default route may be achieved by using +a mask of all zeros, and there may be hierarchical routes. +.Pp +When the system is booted and addresses are assigned +to the network interfaces, each protocol family +installs a routing table entry for each interface when it is ready for traffic. +Normally the protocol specifies the route +through each interface as a +.Dq direct +connection to the destination host +or network. +If the route is direct, the transport layer of a protocol family usually +requests the packet be sent to the same host specified in the packet. +Otherwise, the interface is requested to address the packet to the gateway +listed in the routing entry (i.e., the packet is forwarded). +.Pp +When routing a packet, +the kernel will attempt to find +the most specific route matching the destination. +(If there are two different mask and value-under-the-mask pairs +that match, the more specific is the one with more bits in the mask. +A route to a host is regarded as being supplied with a mask of +as many ones as there are bits in the destination.) +If no entry is found, the destination is declared to be unreachable, +and a routing\-miss message is generated if there are any +listeners on the routing control socket described below. +.Pp +If there are two identical destinations, the route priority acts as a +tie-breaker. +If there are multiple routes to the same destination, +the one with the lowest priority wins. +The kernel assigns certain default priorities based on the type of +route, as given in the table below. +For connected and static routes, this default priority is added to the +interface's priority. +.Pp +A wildcard routing entry is specified with a zero +destination address value and a mask of all zeroes. +Wildcard routes will be used +when the system fails to find other routes matching the +destination. +The combination of wildcard routes and routing redirects can provide +an economical mechanism for routing traffic. +Routes created by redirects from wildcard routes and other routes +will be marked +.Em cloned , +until their +.Dq parent +from which they were created has disappeared. +.Pp +Route labels can be attached to routes and may contain arbitrary +information about the route. +Labels are sent over the routing socket (see below) as +.Vt sockaddr_rtlabel +structures. +.Ss The Routing Socket +One opens the channel for passing routing control messages +by using the +.Xr socket 2 +call shown in the +.Sx SYNOPSIS +above. +.Pp +The +.Fa family +parameter may be +.Dv AF_UNSPEC , +which will provide +routing information for all address families, or can be restricted +to a specific address family by specifying which one is desired. +There can be more than one routing socket open per system. +.Pp +Messages are formed by a header followed by a small +number of +.Vt sockaddr +structures (which are variable length), +interpreted by position, and delimited +by the length entry in the +.Vt sockaddr . +An example of a message with four addresses might be an +IPv4 route addition: the destination, netmask, gateway, and label, +since both netmasks and labels are sent over the routing socket as +.Vt sockaddr +structures. +The interpretation of which addresses are present is given by a +bit mask within the header, and the sequence is least significant +to most significant bit within the vector. +.Pp +Any messages sent to the kernel are returned, and copies are sent +to all interested listeners. +The kernel will provide the process ID +of the sender, and the sender may use an additional sequence +field to distinguish between outstanding messages. +However, message replies may be lost when kernel buffers are exhausted. +.Pp +The kernel may reject certain messages, and will indicate this +by filling in the +.Va rtm_errno +field. +The routing code returns +.Er EEXIST +if +requested to duplicate an existing entry, +.Er ESRCH +if +requested to delete a non-existent entry, +or +.Er ENOBUFS +if insufficient resources were available +to install a new route. +In the current implementation, all routing processes run locally, +and the values for +.Va rtm_errno +are available through the normal +.Va errno +mechanism, even if the routing reply message is lost. +.Pp +A process may avoid the expense of reading replies to +its own messages by issuing a +.Xr setsockopt 2 +call indicating that the +.Dv SO_USELOOPBACK +option at the +.Dv SOL_SOCKET +level is to be turned off. +A process may ignore all messages from the routing socket +by doing a +.Xr shutdown 2 +system call for further input. +.Pp +There are three filter options that can be used to restrict the received route messages +to a subset of all the route messages processed by the kernel: +.Pp +.Bl -tag -width xxxxxxxx -compact +.It ROUTE_TABLEFILTER +.It ROUTE_MSGFILTER +.It ROUTE_FLAGFILTER +.El +.Pp +A process can specify an alternate routing table by using the +.Dv ROUTE_TABLEFILTER +.Xr setsockopt 2 . +A value of +.Dv RTABLE_ANY +specifies all routing tables. +For example, to receive messages for routing table 5: +.Bd -literal -offset indent +unsigned int rdomain = 5; + +if (setsockopt(routefd, AF_ROUTE, ROUTE_TABLEFILTER, + &rdomain, sizeof(rdomain)) == -1) + err(1, "setsockopt(ROUTE_TABLEFILTER)"); +.Ed +.Pp +A process can specify which route message types it's interested in +by using +.Dv ROUTE_FILTER(int type) +and issuing a setsockopt call with the +.Dv ROUTE_MSGFILTER +option at the +.Dv AF_ROUTE +level. +For example, to only get interface specific messages: +.Bd -literal -offset indent +unsigned int rtfilter; + +rtfilter = ROUTE_FILTER(RTM_IFINFO) | + ROUTE_FILTER(RTM_IFANNOUNCE); + +if (setsockopt(routefd, AF_ROUTE, ROUTE_MSGFILTER, + &rtfilter, sizeof(rtfilter)) == -1) + err(1, "setsockopt(ROUTE_MSGFILTER)"); +.Ed +.Pp +Similarly, a process can specify that it is only interested in messages +relating to routes where the priority is no more than a certain value +by issuing a setsockopt call with the +.Dv ROUTE_PRIOFILTER +option. +For example, to select only local, directly connected and static routes: +.Bd -literal -offset indent +unsigned int maxprio = RTP_STATIC; + +if (setsockopt(routefd, AF_ROUTE, ROUTE_PRIOFILTER, + &maxprio, sizeof(maxprio)) == -1) + err(1, "setsockopt(ROUTE_PRIOFILTER)"); +.Ed +.Pp +The +.Dv ROUTE_FLAGFILTER +socket option can be used to exclude a subset of +.Vt rtm_flags +flags from the received route messages: +.Bd -literal -offset indent +int rtfilter = RTF_LLINFO | RTF_BROADCAST; + +if (setsockopt(routefd, AF_ROUTE, ROUTE_FLAGFILTER, &rtfilter, + sizeof(rtfilter)) == -1) + err(1, "setsockopt(ROUTE_FLAGFILTER)"); +.Ed +.Pp +The predefined constants for the routing priorities are: +.Bd -literal +#define RTP_NONE 0 /* unset priority use sane default */ +#define RTP_LOCAL 1 /* local address routes (must be the highest) */ +#define RTP_CONNECTED 4 /* directly connected routes */ +#define RTP_STATIC 8 /* static routes base priority */ +#define RTP_EIGRP 28 /* EIGRP routes */ +#define RTP_OSPF 32 /* OSPF routes */ +#define RTP_ISIS 36 /* IS-IS routes */ +#define RTP_RIP 40 /* RIP routes */ +#define RTP_BGP 48 /* BGP routes */ +#define RTP_DEFAULT 56 /* routes that have nothing set */ +#define RTP_PROPOSAL_STATIC 57 +#define RTP_PROPOSAL_DHCLIENT 58 +#define RTP_PROPOSAL_SLAAC 59 +#define RTP_PROPOSAL_UMB 60 +#define RTP_PROPOSAL_PPP 61 +#define RTP_PROPOSAL_SOLICIT 62 /* request reply of all RTM_PROPOSAL */ +#define RTP_MAX 63 /* maximum priority */ +#define RTP_ANY 64 /* any of the above */ +#define RTP_MASK 0x7f +#define RTP_DOWN 0x80 /* route/link is down */ +.Ed +.Pp +If a route is in use when it is deleted, +the routing entry will be marked down and removed from the routing table, +but the resources associated with it will not +be reclaimed until all references to it are released. +User processes can obtain information about the routing +entry to a specific destination by using a +.Dv RTM_GET +message or via the +.Dv PF_ROUTE +.Xr sysctl 2 . +.Pp +Messages include: +.Bd -literal +#define RTM_ADD 0x1 /* Add Route */ +#define RTM_DELETE 0x2 /* Delete Route */ +#define RTM_CHANGE 0x3 /* Change Metrics or flags */ +#define RTM_GET 0x4 /* Report Metrics */ +#define RTM_LOSING 0x5 /* Kernel Suspects Partitioning */ +#define RTM_REDIRECT 0x6 /* Told to use different route */ +#define RTM_MISS 0x7 /* Lookup failed on this address */ +#define RTM_RESOLVE 0xb /* req to resolve dst to LL addr */ +#define RTM_NEWADDR 0xc /* address being added to iface */ +#define RTM_DELADDR 0xd /* address being removed from iface */ +#define RTM_IFINFO 0xe /* iface going up/down etc. */ +#define RTM_IFANNOUNCE 0xf /* iface arrival/departure */ +#define RTM_DESYNC 0x10 /* route socket buffer overflow */ +#define RTM_INVALIDATE 0x11 /* Invalidate cache of L2 route */ +.Ed +.Pp +A message header consists of one of the following: +.Bd -literal +struct rt_msghdr { + u_short rtm_msglen; /* to skip over non-understood messages */ + u_char rtm_version; /* future binary compatibility */ + u_char rtm_type; /* message type */ + u_short rtm_hdrlen; /* sizeof(rt_msghdr) to skip over the header */ + u_short rtm_index; /* index for associated ifp */ + u_short rtm_tableid; /* routing table id */ + u_char rtm_priority; /* routing priority */ + u_char rtm_mpls; /* MPLS additional infos */ + int rtm_addrs; /* bitmask identifying sockaddrs in msg */ + int rtm_flags; /* flags, incl. kern & message, e.g. DONE */ + int rtm_fmask; /* bitmask used in RTM_CHANGE message */ + pid_t rtm_pid; /* identify sender */ + int rtm_seq; /* for sender to identify action */ + int rtm_errno; /* why failed */ + u_int rtm_inits; /* which metrics we are initializing */ + struct rt_metrics rtm_rmx; /* metrics themselves */ +}; + +struct if_msghdr { + u_short ifm_msglen; /* to skip over non-understood messages */ + u_char ifm_version; /* future binary compatibility */ + u_char ifm_type; /* message type */ + u_short ifm_hdrlen; /* sizeof(if_msghdr) to skip over the header */ + u_short ifm_index; /* index for associated ifp */ + u_short ifm_tableid; /* routing table id */ + u_char ifm_pad1; + u_char ifm_pad2; + int ifm_addrs; /* like rtm_addrs */ + int ifm_flags; /* value of if_flags */ + int ifm_xflags; + struct if_data ifm_data;/* statistics and other data about if */ +}; + +struct ifa_msghdr { + u_short ifam_msglen; /* to skip over non-understood messages */ + u_char ifam_version; /* future binary compatibility */ + u_char ifam_type; /* message type */ + u_short ifam_hdrlen; /* sizeof(ifa_msghdr) to skip over the header */ + u_short ifam_index; /* index for associated ifp */ + u_short ifam_tableid; /* routing table id */ + u_char ifam_pad1; + u_char ifam_pad2; + int ifam_addrs; /* like rtm_addrs */ + int ifam_flags; /* value of ifa_flags */ + int ifam_metric; /* value of ifa_metric */ +}; + +struct if_announcemsghdr { + u_short ifan_msglen; /* to skip over non-understood messages */ + u_char ifan_version; /* future binary compatibility */ + u_char ifan_type; /* message type */ + u_short ifan_hdrlen; /* sizeof(ifa_msghdr) to skip over the header */ + u_short ifan_index; /* index for associated ifp */ + u_short ifan_what; /* what type of announcement */ + char ifan_name[IFNAMSIZ]; /* if name, e.g. "en0" */ +}; +.Ed +.Pp +The +.Dv RTM_IFINFO +message uses an +.Vt if_msghdr +header, the +.Dv RTM_NEWADDR +and +.Dv RTM_DELADDR +messages use an +.Vt ifa_msghdr +header, +the +.Dv RTM_IFANNOUNCE +message uses an +.Vt if_announcemsghdr +header, +.Dv RTM_INVALIDATE +is used only internally in the kernel and should never appear in a route +message, +and all other messages use the +.Vt rt_msghdr +header. +.Pp +The metrics structure is: +.Bd -literal +struct rt_metrics { + u_int64_t rmx_pksent; /* packets sent using this route */ + int64_t rmx_expire; /* lifetime for route, e.g. redirect */ + u_int rmx_locks; /* Kernel must leave these values */ + u_int rmx_mtu; /* MTU for this path */ + u_int rmx_refcnt; /* # references hold */ + u_int rmx_hopcount; /* max hops expected */ + u_int rmx_recvpipe; /* inbound delay-bandwidth product */ + u_int rmx_sendpipe; /* outbound delay-bandwidth product */ + u_int rmx_ssthresh; /* outbound gateway buffer limit */ + u_int rmx_rtt; /* estimated round trip time */ + u_int rmx_rttvar; /* estimated rtt variance */ + u_int rmx_pad; +}; +.Ed +.Pp +Only +.Va rmx_mtu , rmx_expire , rmx_pksent , +and +.Va rmx_locks +are used by the kernel routing table. +All other values will be ignored when inserting them into the kernel and are +set to zero in routing messages sent by the kernel. +They are left for compatibility reasons with other systems. +.Pp +Flags include the values: +.Bd -literal +#define RTF_UP 0x1 /* route usable */ +#define RTF_GATEWAY 0x2 /* destination is a gateway */ +#define RTF_HOST 0x4 /* host entry (net otherwise) */ +#define RTF_REJECT 0x8 /* host or net unreachable */ +#define RTF_DYNAMIC 0x10 /* created dynamically (by redirect) */ +#define RTF_MODIFIED 0x20 /* modified dynamically (by redirect) */ +#define RTF_DONE 0x40 /* message confirmed */ +#define RTF_CLONING 0x100 /* generate new routes on use */ +#define RTF_MULTICAST 0x200 /* route associated to a mcast addr. */ +#define RTF_LLINFO 0x400 /* generated by ARP or NDP */ +#define RTF_STATIC 0x800 /* manually added */ +#define RTF_BLACKHOLE 0x1000 /* just discard pkts (during updates) */ +#define RTF_PROTO3 0x2000 /* protocol specific routing flag */ +#define RTF_PROTO2 0x4000 /* protocol specific routing flag */ +#define RTF_PROTO1 0x8000 /* protocol specific routing flag */ +#define RTF_CLONED 0x10000 /* this is a cloned route */ +#define RTF_MPATH 0x40000 /* multipath route or operation */ +#define RTF_MPLS 0x100000 /* MPLS additional infos */ +#define RTF_LOCAL 0x200000 /* route to a local address */ +#define RTF_BROADCAST 0x400000 /* route associated to a bcast addr. */ +#define RTF_CONNECTED 0x800000 /* interface route */ +.Ed +.Pp +The following flags (defined as +.Dv RTF_FMASK ) +can be changed by an RTM_CHANGE request: +.Dv RTF_LLINFO , +.Dv RTF_PROTO1 , +.Dv RTF_PROTO2 , +.Dv RTF_PROTO3 , +.Dv RTF_BLACKHOLE , +.Dv RTF_REJECT , +.Dv RTF_STATIC +and +.Dv RTF_MPLS . +.Pp +Specifiers for metric values in +.Va rmx_locks +and +.Va rtm_inits +are: +.Bd -literal +#define RTV_MTU 0x1 /* init or lock _mtu */ +#define RTV_HOPCOUNT 0x2 /* init or lock _hopcount */ +#define RTV_EXPIRE 0x4 /* init or lock _expire */ +#define RTV_RPIPE 0x8 /* init or lock _recvpipe */ +#define RTV_SPIPE 0x10 /* init or lock _sendpipe */ +#define RTV_SSTHRESH 0x20 /* init or lock _ssthresh */ +#define RTV_RTT 0x40 /* init or lock _rtt */ +#define RTV_RTTVAR 0x80 /* init or lock _rttvar */ +.Ed +.Pp +Only +.Dv RTV_MTU +and +.Dv RTV_EXPIRE +should be used; all other flags are ignored. +.Pp +Specifiers for which addresses are present in the messages are: +.Bd -literal +#define RTA_DST 0x1 /* destination sockaddr present */ +#define RTA_GATEWAY 0x2 /* gateway sockaddr present */ +#define RTA_NETMASK 0x4 /* netmask sockaddr present */ +#define RTA_IFP 0x10 /* interface name sockaddr present */ +#define RTA_IFA 0x20 /* interface addr sockaddr present */ +#define RTA_AUTHOR 0x40 /* sockaddr for author of redirect */ +#define RTA_BRD 0x80 /* for NEWADDR, bcast or p-p dest addr */ +#define RTA_SRC 0x100 /* source sockaddr present */ +#define RTA_SRCMASK 0x200 /* source netmask present */ +#define RTA_LABEL 0x400 /* route label present */ +.Ed +.Sh SEE ALSO +.Xr netstat 1 , +.Xr socket 2 , +.Xr sysctl 2 , +.Xr rtable 4 , +.Xr mygate 5 , +.Xr route 8 , +.Xr route 9 +.Sh HISTORY +A +.Dv PF_ROUTE +protocol family first appeared in +.Bx 4.3 Reno . diff --git a/static/openbsd/man4/rport.4 b/static/openbsd/man4/rport.4 new file mode 100644 index 00000000..11c9e558 --- /dev/null +++ b/static/openbsd/man4/rport.4 @@ -0,0 +1,85 @@ +.\" $OpenBSD: rport.4,v 1.2 2024/08/31 13:39:36 jmc Exp $ +.\" +.\" Copyright (c) 2024 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 31 2024 $ +.Dt RPORT 4 +.Os +.Sh NAME +.Nm rport +.Nd rdomain port interface pseudo-device +.Sh SYNOPSIS +.Cd "pseudo-device rport" +.Sh DESCRIPTION +The +.Nm +driver provides point-to-point interfaces for layer 3 connectivity +between +.Xr rdomain 4 +instances. +.Pp +Layer 3 connectivity between a pair of rdomains can be established +by creating an +.Nm +interface in each rdomain, and connecting them together by configuring +one of these interfaces as the parent of the other. +.Pp +.Nm +interfaces can be created at runtime using the +.Ic ifconfig rport Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The interface itself can be configured with +.Xr ifconfig 8 ; +see its manual page for more information. +.Sh EXAMPLES +Create two +.Nm +interfaces in separate +.Xr rdomain 4 +instances and connect them together: +.Bd -literal -offset indent +# ifconfig rport0 create rdomain 0 up +# ifconfig rport1 create rdomain 1 parent rport0 up +# ifconfig rport0 inet 192.168.0.0/32 192.168.0.1 +# ifconfig rport1 inet 192.168.0.1/32 192.168.0.0 +.Ed +.Sh SEE ALSO +.Xr netintro 4 , +.Xr veb 4 , +.Xr hostname.if 5 , +.Xr pf.conf 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.6 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org . +.Sh CAVEATS +A pair of +.Nm +interfaces must be created for each connection between a pair of rdomains. +Alternatively, if peering between multiple +.Xr rdomain 4 +instances is required, a single +.Xr veb 4 +interface with a +.Xr vport 4 +interface for each rdomain can be used instead. diff --git a/static/openbsd/man4/rsu.4 b/static/openbsd/man4/rsu.4 new file mode 100644 index 00000000..76362b3c --- /dev/null +++ b/static/openbsd/man4/rsu.4 @@ -0,0 +1,158 @@ +.\" $OpenBSD: rsu.4,v 1.27 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2010 Damien Bergamini +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt RSU 4 +.Os +.Sh NAME +.Nm rsu +.Nd Realtek RTL8188SU/RTL8192SU USB IEEE 802.11b/g/n wireless network device +.Sh SYNOPSIS +.Cd "rsu* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports USB 2.0 wireless network devices based on Realtek +RTL8188SU, RTL8191SU and RTL8192SU chipsets. +.Pp +The RTL8188SU is a highly integrated 802.11n adapter that combines +a MAC, a 1T1R capable baseband and an RF in a single chip. +It operates in the 2GHz spectrum only. +.Pp +The RTL8191SU is a highly integrated multiple-in, single-out (MISO) +802.11n adapter that combines a MAC, a 1T2R capable baseband and an +RF in a single chip. +It operates in the 2GHz spectrum only. +.Pp +The RTL8192SU is a highly integrated multiple-in, multiple-out (MIMO) +802.11n adapter that combines a MAC, a 2T2R capable baseband and an +RF in a single chip. +It operates in the 2GHz spectrum only. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The adapter needs firmware files to run, which are loaded on demand by +the driver when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/rsu-rtl8712 +.El +.Sh HARDWARE +The following adapters should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It ASUS USB-N10 +.It ASUS WL-167G V3 +.It Belkin F7D1101 v1 +.It D-Link DWA-131 A1 +.It Hercules HWGUn-54 +.It Hercules HWNUm-300 +.It Planex GW-USNano +.It Sitecom WL-349 v1 +.It Sitecom WL-353 +.It Sweex LW154 +.It TRENDnet TEW-648UB +.It TRENDnet TEW-649UB +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig rsu0 scan +.Pp +The following +.Xr hostname.if 5 +example configures rsu0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "rsu0: error N, could not read firmware ..." +For some reason, the driver was unable to read the microcode file from the +filesystem. +The file might be missing or corrupted. +.It "rsu0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +The +.Nm +driver does not support any of the 802.11n capabilities offered by the +adapters. +Additional work is required in +.Xr ieee80211 9 +before those features can be supported. diff --git a/static/openbsd/man4/rtsx.4 b/static/openbsd/man4/rtsx.4 new file mode 100644 index 00000000..951907de --- /dev/null +++ b/static/openbsd/man4/rtsx.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: rtsx.4,v 1.10 2017/09/06 13:07:38 jcs Exp $ +.\" +.\" Theo de Raadt, 2006. Public Domain. +.\" Stefan Sperling, 2012. Public Domain. +.\" +.Dd $Mdocdate: September 6 2017 $ +.Dt RTSX 4 +.Os +.Sh NAME +.Nm rtsx +.Nd Realtek SD card reader +.Sh SYNOPSIS +.Cd "rtsx* at pci?" +.Cd "sdmmc* at rtsx?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Realtek RTS5209, RTS5227, RTS5229, +RTS522A, RTS5249, RTS525A, RTL8402, RTL8411, and RTL8411B SD card readers. +.Pp +The +.Xr sdmmc 4 +subsystem performs SD/MMC transactions to communicate with SD +or SDHC devices inserted into the SD slot. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sdmmc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Stefan Sperling Aq Mt stsp@openbsd.org . +.Sh BUGS +The +.Nm +driver does not support MS (Memory Stick) and xD (Extreme Digital) devices +even though the hardware supports them. +.Pp +Support for SDIO interrupts is not implemented. diff --git a/static/openbsd/man4/rtw.4 b/static/openbsd/man4/rtw.4 new file mode 100644 index 00000000..d5c06a60 --- /dev/null +++ b/static/openbsd/man4/rtw.4 @@ -0,0 +1,186 @@ +.\" $OpenBSD: rtw.4,v 1.49 2025/03/27 10:21:53 jmc Exp $ +.\" +.\" Copyright (c) 2004 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt RTW 4 +.Os +.Sh NAME +.Nm rtw +.Nd Realtek RTL8180L IEEE 802.11b wireless network device +.Sh SYNOPSIS +.Cd "rtw* at cardbus?" +.Cd "rtw* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports PCI/CardBus 802.11b wireless adapters based on the +Realtek RTL8180L. +.Pp +A variety of radio transceivers can be found in these devices, including +the Philips SA2400A, Maxim MAX2820, and GCT GRF5101. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.It Host AP +In this mode the driver acts as an access point (base station) +for other cards. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use software +Wired Equivalent Privacy (WEP). +It is strongly recommended that WEP +not be used as the sole mechanism +to secure wireless communication, +due to serious weaknesses in it. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh HARDWARE +The following adapters should work: +.Bl -column "GigaFast WF721-AEX (R* serial)" "GRF5101" "Cardbus" -offset 6n +.It Em Card Ta Em Radio Ta Em Bus +.\".It Li "Acer Aspire 1357 LMi" Ta SA2400 Ta Mini PCI +.It Li "Allnet ALL0182" Ta SA2400 Ta CardBus +.\".It Li "Belkin F5D6001 V3" Ta SA2400 Ta PCI +.It Li "Belkin F5D6020 V3" Ta SA2400 Ta CardBus +.It Li "Buffalo WLI-CB-B11" Ta SA2400 Ta CardBus +.It Li "Corega CG-WLCB11V3" Ta SA2400 Ta CardBus +.\".It Li "D-Link DWL-510" Ta SA2400 Ta PCI +.\".It Li "D-Link DWL-520 rev D" Ta ? Ta PCI +.It Li "D-Link DWL-610" Ta ? Ta CardBus +.\".It Li "Encore ENLWI-PCI1-NT" Ta SA2400 Ta PCI +.It Li "Edimax EW-7106" Ta SA2400 Ta CardBus +.\".It Li "Edimax EW-7126" Ta GRF5101 Ta PCI +.\".It Li "Gigabyte GN-WLMR101" Ta SA2400 Ta PCI +.It Li "GigaFast WF721-AEX (R* serial)" Ta "GRF5101" Ta CardBus +.\".It Li "HomeLine HLW-PCC200" Ta "GRF5101" Ta CardBus +.It Li "Jensen AirLink 6011" Ta GRF5101 Ta CardBus +.It Li "Level-One WPC-0101" Ta SA2400 Ta CardBus +.It Li "Linksys WPC11 v4" Ta MAX2820 Ta CardBus +.\".It Li "Longshine LCS-8031-R" Ta GRF5101 Ta PCI +.\".It Li "Mentor WLPCI04330073" Ta SA2400 Ta CardBus +.\".It Li "Micronet SP906BB" Ta ? Ta PCI +.It Li "Netgear MA521" Ta SA2400 Ta CardBus +.It Li "Ovislink AirLive WL-1120PCM" Ta SA2400 Ta CardBus +.\".It Li "Pheenet WL-11PCIR" Ta SA2400 Ta PCI +.It Li "Planet WL-3553" Ta SA2400 Ta CardBus +.It Li "Q-Tec 770WC" Ta SA2400 Ta CardBus +.It Li "Q-Tec 775WC" Ta SA2400 Ta CardBus +.\".It "Repotec RP-WP7126" Ta GRF5101 Ta PCI +.It Li "Roper FreeLan 802.11b" Ta SA2400 Ta CardBus +.It Li "SAFECOM SWLCR-1100" Ta SA2400 Ta CardBus +.\".It Li "Surecom EP-9428" Ta ? Ta CardBus +.\".It Li "Sweex LC700010" Ta GRF5101 Ta PCI +.\".It "Tonze PC-2100T" Ta GRF5101 Ta PCI +.\".It Li "Topcom Skyr@cer 4011b" Ta ? Ta CardBus +.\".It "TP-Link TL-WN250/251" Ta GRF5101 Ta PCI +.It Li "TRENDnet TEW-226PC" Ta ? Ta CardBus +.\".It Li "TRENDnet TEW-288PI" Ta SA2400 Ta PCI +.It Li "VCTnet PC-11B1" Ta SA2400 Ta CardBus +.It Li "Winstron CB-200B" Ta SA2400 Ta CardBus +.It Li "Zonet ZEW1000" Ta GRF5101 Ta CardBus +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig rtw0 scan +.Pp +The following +.Xr hostname.if 5 +example configures rtw0 to join network +.Dq mynwid , +using WEP key +.Dq mywepkey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +nwid mynwid nwkey mywepkey +inet autoconf +.Ed +.Pp +The following +.Xr hostname.if 5 +example creates a host-based access point on boot: +.Bd -literal -offset indent +mediaopt hostap +nwid mynwid nwkey mywepkey +inet 192.168.1.1 255.255.255.0 +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr cardbus 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr hostapd 8 , +.Xr ifconfig 8 +.Rs +.%T Realtek +.%U https://www.realtek.com/en +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Young Aq Mt dyoung@NetBSD.org +and ported to +.Ox +by +.An Jonathan Gray Aq Mt jsg@openbsd.org . +.Sh CAVEATS +GCT refuse to release any documentation on their GRF5101 RF transceiver. +.Pp +While PCI devices will attach, most of them are not able to transmit. +.Pp +Host AP mode doesn't support power saving. +Clients attempting to use power saving mode may experience significant +packet loss (disabling power saving on the client will fix this). diff --git a/static/openbsd/man4/rtwn.4 b/static/openbsd/man4/rtwn.4 new file mode 100644 index 00000000..df2ed438 --- /dev/null +++ b/static/openbsd/man4/rtwn.4 @@ -0,0 +1,154 @@ +.\" $OpenBSD: rtwn.4,v 1.14 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2010 Damien Bergamini +.\" Copyright (c) 2015 Stefan Sperling +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt RTWN 4 +.Os +.Sh NAME +.Nm rtwn +.Nd Realtek RTL8188CE/RTL8188EE/RTL8192CE/RTL8723AE PCIe IEEE 802.11b/g/n +wireless network device +.Sh SYNOPSIS +.Cd "rtwn* at pci? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports PCIe wireless network devices based on the Realtek +RTL8188CE, RTL8188EE, RTL8192CE and RTL8723AE chipsets. +.Pp +The RTL8188CE, RTL8188EE and RTL8723AE are highly integrated 802.11n adapters +that combine a MAC, a 1T1R capable baseband and an RF in a single chip. +The RTL8723AE also includes a Bluetooth 2.1/3.0/4.0 controller. +.Pp +The RTL8192CE is a highly integrated multiple-in, multiple-out (MIMO) +802.11n adapter that combines a MAC, a 2T2R capable baseband and an +RF in a single chip. +.Pp +These devices operate in the 2GHz spectrum only. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The adapter needs firmware files to run, which are loaded on demand by +the driver when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/rtwn-rtl8188e +.It Pa /etc/firmware/rtwn-rtl8192cU +.It Pa /etc/firmware/rtwn-rtl8192cU_B +.It Pa /etc/firmware/rtwn-rtl8723 +.It Pa /etc/firmware/rtwn-rtl8723_B +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig rtwn0 scan +.Pp +The following +.Xr hostname.if 5 +example configures rtwn0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "rtwn0: could not read firmware ..." +For some reason, the driver was unable to read the microcode file from the +filesystem. +The file might be missing or corrupted. +.It "rtwn0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An -nosplit +.An Stefan Sperling Aq Mt stsp@openbsd.org . +It was based on the +.Xr urtwn 4 +driver written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +The +.Nm +driver does not support any of the 802.11n capabilities offered by the +adapters. +Additional work is required in +.Xr ieee80211 9 +before those features can be supported. diff --git a/static/openbsd/man4/rum.4 b/static/openbsd/man4/rum.4 new file mode 100644 index 00000000..f44d3ca0 --- /dev/null +++ b/static/openbsd/man4/rum.4 @@ -0,0 +1,226 @@ +.\" $OpenBSD: rum.4,v 1.64 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2005-2007 +.\" Damien Bergamini +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt RUM 4 +.Os +.Sh NAME +.Nm rum +.Nd Ralink Technology/MediaTek USB IEEE 802.11a/b/g wireless network device +.Sh SYNOPSIS +.Cd "rum* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports USB 2.0 and PCI Express Mini Card wireless adapters based on the +Ralink RT2501USB and RT2601USB chipsets. +.Pp +Ralink PCI Express Mini Card adapters show up as normal USB 2.0 devices and are +thus handled by the +.Nm +driver. +.Pp +The RT2501USB chipset is the second generation of 802.11a/b/g adapters from +Ralink. +It consists of two integrated chips, an RT2571W MAC/BBP and an RT2528 or +RT5226 radio transceiver. +.Pp +The RT2601USB chipset consists of two integrated chips, an RT2671 MAC/BBP and +an RT2527 or RT5225 radio transceiver. +This chipset uses the MIMO (multiple-input multiple-output) technology with +multiple antennas to extend the operating range of the adapter and to achieve +higher throughput. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.It Host AP +In this mode the driver acts as an access point (base station) +for other cards. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver relies on the software 802.11 stack for both encryption and decryption +of data frames. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The following firmware file is loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It /etc/firmware/rum-rt2573 +.El +.Sh HARDWARE +The following adapters should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It 3Com Aolynk WUB320g +.It Abocom WUG2700 +.It Airlink101 AWLL5025 +.It ASUS WL-167g ver 2 +.It Atlantis Land A02-UP1-W54 +.It Belkin F5D7050 ver 3 +.It Belkin F5D9050 ver 3 +.It Belkin F5D9050C +.It Buffalo WLI-U2-SG54HG +.It Buffalo WLI-U2-SG54HP +.It Buffalo WLI-U2-G54HP +.It CNet CWD-854 ver F +.It Conceptronic C54RU ver 2 +.It Corega CG-WLUSB2GL +.It Corega CG-WLUSB2GO +.It Corega CG-WLUSB2GPX +.It D-Link DWA-110 +.It D-Link DWA-111 +.It "D-Link DWL-G122 rev C1" +.It D-Link WUA-1340 +.It Digitus DN-7003GR +.It Edimax EW-7318Ug +.It Edimax EW-7318USg +.It Edimax EW-7618Ug +.It Gigabyte GN-WB01GS +.It Gigabyte GN-WI05GS +.It Hawking HWUG1 +.It Hawking HWU54DM +.It Hercules HWGUSB2-54-LB +.It Hercules HWGUSB2-54V2-AP +.It LevelOne WNC-0301USB v3 +.It Linksys WUSB200 +.It Linksys WUSB54G rev C +.It Linksys WUSB54GR +.It Planex GW-US54HP +.It Planex GW-US54Mini2 +.It Planex GW-USMM +.It Senao NUB-3701 +.It Sitecom WL-113 ver 2 +.It Sitecom WL-172 +.It Sweex LW053 +.It TP-LINK TL-WN321G +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig rum0 scan +.Pp +The following +.Xr hostname.if 5 +example configures rum0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +nwid mynwid wpakey mywpakey +inet autoconf +.Ed +.Pp +The following +.Xr hostname.if 5 +example creates a host-based access point on boot: +.Bd -literal -offset indent +mediaopt hostap +nwid mynwid wpakey mywpakey +inet 192.168.1.1 255.255.255.0 +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "rum0: error N, could not read firmware ..." +For some reason, the driver was unable to read the microcode file from the +filesystem. +The file might be missing or corrupted. +.It "rum0: could not load 8051 microcode" +An error occurred while attempting to upload the microcode to the onboard 8051 +microcontroller unit. +.It "rum0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr hostapd 8 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Niall O'Higgins Aq Mt niallo@openbsd.org +and +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +The +.Nm +driver supports automatic control of the transmit speed in BSS mode only. +Therefore the use of a +.Nm +adapter in Host AP mode is discouraged. diff --git a/static/openbsd/man4/run.4 b/static/openbsd/man4/run.4 new file mode 100644 index 00000000..f92302aa --- /dev/null +++ b/static/openbsd/man4/run.4 @@ -0,0 +1,243 @@ +.\" $OpenBSD: run.4,v 1.58 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2008 Damien Bergamini +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt RUN 4 +.Os +.Sh NAME +.Nm run +.Nd Ralink Technology/MediaTek USB IEEE 802.11a/b/g/n wireless network device +.Sh SYNOPSIS +.Cd "run* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports USB 2.0 wireless adapters based on the Ralink RT2700U, +RT2800U, RT3000U and RT3900E chipsets. +.Pp +The RT2700U chipset consists of two integrated chips, an RT2770 MAC/BBP and +an RT2720 (1T2R) or RT2750 (dual-band 1T2R) radio transceiver. +.Pp +The RT2800U chipset consists of two integrated chips, an RT2870 MAC/BBP and +an RT2820 (2T3R) or RT2850 (dual-band 2T3R) radio transceiver. +.Pp +The RT3000U is a single-chip solution based on an RT3070 MAC/BBP and +an RT3020 (1T1R), RT3021 (1T2R), RT3022 (2T2R) or RT3052 (dual-band 2T2R) +radio transceiver. +.Pp +The RT3900E is a single-chip solution based on an RT3593, RT5390, +RT5392 or an RT5592 MAC/BBP and an RT3053 (dual-band 3T3R), +RT5370 (1T1R), RT5372 (2T2R), or RT5572 (dual-band 2T2R) +radio transceiver. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver offloads both encryption and decryption of data frames to the +hardware for the WEP40, WEP104, TKIP(+MIC) and CCMP ciphers. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs the following firmware files, +which are loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It /etc/firmware/run-rt2870 +.It /etc/firmware/run-rt3071 +.El +.Sh HARDWARE +The following adapters should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Airlink101 AWLL6090 +.It ASUS USB-N11 +.It ASUS USB-N13 ver. A1 +.It ASUS USB-N53 +.It ASUS USB-N66 +.It ASUS WL-160N +.It Belkin F5D8051 ver 3000 +.It Belkin F5D8053 +.It Belkin F5D8055 +.It Belkin F6D4050 ver 1 +.It Belkin F6D4050 ver 2 +.It Belkin F7D1101 ver 2 +.It Belkin F9L1103 +.It Buffalo WLI-UC-AG300N +.It Buffalo WLI-UC-G300N +.It Buffalo WLI-UC-G301N +.It Buffalo WLI-UC-GN +.It Buffalo WLI-UC-GNHP +.It Buffalo WLI-UC-GNM +.It Buffalo WLI-UC-GNM2 +.It Cisco AM10 +.It Corega CG-WLUSB2GNL +.It Corega CG-WLUSB2GNR +.It Corega CG-WLUSB300AGN +.It Corega CG-WLUSB300GNM +.It D-Link DWA-125 rev B2 +.It D-Link DWA-127 +.It D-Link DWA-130 rev B1, F1 +.It D-Link DWA-140 rev B1, B2, B3, \&D1 +.It D-Link DWA-160 rev B2 +.It D-Link DWA-162 +.It DrayTek Vigor N61 +.It Edimax EW-7711UAn +.It Edimax EW-7711USn +.It Edimax EW-7711UTn +.It Edimax EW-7717Un +.It Edimax EW-7718Un +.It Edimax EW-7722UTn +.It Edimax EW-7733UnD +.It Gigabyte GN-WB30N +.It Gigabyte GN-WB31N +.It Gigabyte GN-WB32L +.It Hawking HWDN1 +.It Hawking HWUN1 +.It Hawking HWUN2 +.It Hercules HWNU-300 +.It Keebox W150NU +.It Linksys AE1000 +.It Linksys WUSB54GC v3 +.It Linksys WUSB600N +.It LogiLink WL0084B +.It Logitec gLAN-W150NU2BK +.It Logitec LAN-W150N/U2 +.It Logitec LAN-W300N/U2 +.It Logitec LAN-W300N/U2S +.It Mvix Nubbin MS-811N +.It Planex GW-USMicroN +.It Planex GW-US300MiniS +.It Sitecom WL-182 +.It Sitecom WL-188 +.It Sitecom WL-301 +.It Sitecom WL-302 +.It Sitecom WL-315 +.It Sitecom WLA-4000 +.It Sitecom WLA-5000 +.It SMC SMCWUSBS-N2 +.It Sweex LW153 +.It Sweex LW303 +.It Sweex LW313 +.It Tenda W311M +.It TP-LINK TL-WDN3200 +.It TP-LINK TL-WN727N v3 +.It TRENDnet TEW-645UB +.It Unex DNUR-81 +.It Unex DNUR-82 +.It ZyXEL NWD-211AN +.It ZyXEL NWD-271N +.It ZyXEL NWD2105 +.It ZyXEL NWD210N +.It ZyXEL NWD2205 +.It ZyXEL NWD270N +.It ZyXEL NWD2705 +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig run0 scan +.Pp +The following +.Xr hostname.if 5 +example configures run0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "run0: error N, could not read firmware ..." +For some reason, the driver was unable to read the microcode file from the +filesystem. +The file might be missing or corrupted. +.It "run0: could not load 8051 microcode" +An error occurred while attempting to upload the microcode to the onboard 8051 +microcontroller unit. +.It "run0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +The +.Nm +driver does not support any of the 802.11n capabilities offered by the +RT2800 and RT3000 chipsets. +Additional work is required in +.Xr ieee80211 9 +before those features can be supported. diff --git a/static/openbsd/man4/safte.4 b/static/openbsd/man4/safte.4 new file mode 100644 index 00000000..1add92c1 --- /dev/null +++ b/static/openbsd/man4/safte.4 @@ -0,0 +1,68 @@ +.\" $OpenBSD: safte.4,v 1.8 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: July 16 2013 $ +.Dt SAFTE 4 +.Os +.Sh NAME +.Nm safte +.Nd SCSI Accessed Fault-Tolerant Enclosure +.Sh SYNOPSIS +.Cd "safte* at scsibus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for monitoring the various environmental sensors +present in SCSI enclosures using the SCSI Accessed Fault-Tolerant Enclosure +command set. +The hardware monitor is used with the +.Xr sysctl 8 +interface. +.Pp +SAF-TE compliant devices can provide an arbitrary set of sensors from the +following types: +.Bl -column "Sensor" "Units" "Typical" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical Use" +.It Li "temp" Ta "uK" Ta "temperature" +.It Li "fan" Ta "RPM" Ta "fan" +.It Li "psu" Ta "On/Off" Ta "power supply" +.It Li "doorlock" Ta "On/Off" Ta "door lock" +.It Li "alarm" Ta "On/Off" Ta "enclosure alarm" +.El +.Pp +Sensor data is updated every 10 seconds. +.Pp +An enclosure may provide environmental information using an alternative +to the SCSI Accessed Fault-Tolerant Enclosure command set used by this driver. +Enclosures using the SCSI Enclosure Services command set +may be monitored by the +.Xr ses 4 +driver. +.Sh SEE ALSO +.Xr intro 4 , +.Xr scsibus 4 , +.Xr ses 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/sbus.4 b/static/openbsd/man4/sbus.4 new file mode 100644 index 00000000..ed95a163 --- /dev/null +++ b/static/openbsd/man4/sbus.4 @@ -0,0 +1,156 @@ +.\" $OpenBSD: sbus.4,v 1.55 2021/09/08 20:29:21 jmc Exp $ +.\" $NetBSD: sbus.4,v 1.5 2002/01/21 17:54:10 wiz Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Paul Kranenburg. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt SBUS 4 +.Os +.Sh NAME +.Nm sbus +.Nd introduction to SBus bus support +.Sh SYNOPSIS +.Cd "sbus* at mainbus?" +.Cd "sbus* at xbox?" +.Sh DESCRIPTION +These +.Nm +attachments are specific to the sparc64 port. +.Pp +.Nm +is an I/O interconnect bus mostly found in SPARC workstations +and small to medium server class systems. +It supports both on-board peripherals and extension boards. +The +.Nm +specifications define the bus protocol as well as the electrical and +mechanical properties of the extension slots. +.Pp +.Ox +provides support for the following devices. +Note that not all architectures support all devices. +.Ss Audio interfaces +.Bl -tag -width 13n -offset ind -compact +.It Xr audiocs 4 +SPARC CS4231 audio device +.El +.Ss SCSI interfaces +.Bl -tag -width 13n -offset ind -compact +.It Xr esp 4 +ESP NCR 53c94 on-board or SBus SCSI interface +.It Xr qla 4 +QLogic ISP2100/2200/2300 Fibre Channel controller +.It Xr qlw 4 +QLogic ISP1000/1020/1x40/1x80/1x160 SCSI controller +.El +.Ss Network interfaces +.Bl -tag -width 13n -offset ind -compact +.It Xr be 4 +SPARC 10/100 Ethernet device +.It Xr gem 4 +GEM 10/100/1Gb Ethernet device +.It Xr hme 4 +Sun Happy Meal 10/100 Ethernet device +.It Xr le 4 +AMD LANCE Ethernet device +.It Xr lebuffer 4 , Xr ledma 4 +AMD LANCE Ethernet device +.It Xr qe 4 +SPARC 10/100 Ethernet device +.It Xr qec 4 +SPARC Quad Ethernet Controller +.It Xr ti 4 +Alteon Networks Tigon I and II Gigabit Ethernet device +.El +.Ss Bridges +.Bl -tag -width 13n -offset ind -compact +.It Xr stp 4 +SBus PCMCIA bridge +.El +.Ss Graphics devices +.Bl -tag -width 13n -offset ind -compact +.It Xr agten 4 +Fujitsu AG-10e accelerated 24-bit color frame buffer +.It Xr bwtwo 4 +Monochromatic frame buffer +.It Xr cgsix 4 +Accelerated 8-bit color frame buffer +.It Xr cgthree 4 +8-bit color frame buffer +.It Xr cgtwelve 4 +Accelerated 24-bit color frame buffer +.It Xr mgx 4 +SMS MGX and MGXPlus accelerated 24-bit color frame buffers +.It Xr rfx 4 +Vitec/Connectware/AP&D +RasterFlex framebuffer series +.It Xr tvtwo 4 +Accelerated 24-bit color frame buffer +.It Xr vigra 4 +8-bit SBus color frame buffer with VGA-compatible modes +.It Xr zx 4 +Accelerated 24-bit color frame buffer +.El +.Ss Serial and parallel interfaces +.Bl -tag -width 13n -offset ind -compact +.It Xr apio 4 +Aurora Technologies pio1 parallel port card +.It Xr asio 4 +Aurora Technologies pio2 serial port card +.It Xr bpp 4 +parallel port +.It Xr magma 4 +Magma LC series Serial/Parallel Interface cards +.It Xr spif 4 +Sun Serial/Parallel Interface card +.It Xr zs 4 +Zilog 8530 (ZSCC) serial communications driver +.El +.Ss Miscellaneous devices +.Bl -tag -width 13n -offset ind -compact +.It Xr auxio 4 +Miscellaneous I/O controls +.It Xr clock 4 +real-time clock +.It Xr fdc 4 +NEC765 compatible floppy disk driver +.It Xr uperf 4 +Performance counters on the host bridge +.It Xr xbox 4 +SBus Expansion subsystem +.El +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The machine-independent +.Nm sbus +subsystem appeared in +.Nx 1.3 . +.Ox +support first appeared in +.Ox 2.0 . diff --git a/static/openbsd/man4/schsio.4 b/static/openbsd/man4/schsio.4 new file mode 100644 index 00000000..e68ed8de --- /dev/null +++ b/static/openbsd/man4/schsio.4 @@ -0,0 +1,95 @@ +.\" $OpenBSD: schsio.4,v 1.4 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Michael Knudsen +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: July 16 2013 $ +.Dt SCHSIO 4 +.Os +.Sh NAME +.Nm schsio +.Nd SMSC SCH311x LPC Super I/O +.Sh SYNOPSIS +.Cd "schsio* at isa? port 0x2e flags 0x0000" +.Cd "schsio* at isa? port 0x4e flags 0x0000" +.Cd "schsio* at isa? port 0x162e flags 0x0000" +.Cd "schsio* at isa? port 0x164e flags 0x0000" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SMSC SCH3112, SCH3114, and SCH3116 +ICs. +Among other things, the devices contain environment sensors, a watchdog +timer, and fan control. +The +.Nm +driver supports the environment sensors and the watchdog timer. +.Pp +The hardware provides the following sensors: +.Bl -column "Internal diode" "Units" "Typical" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical use" +.It Li "Internal diode" Ta "uK" Ta "IC internal thermal diode" +.It Li "Remote diode 1" Ta "uK" Ta "External thermal diode" +.It Li "Remove diode 2" Ta "uK" Ta "External thermal diode" +.It Li "FAN1" Ta "RPM" Ta "Fan tachometer" +.It Li "FAN2" Ta "RPM" Ta "Fan tachometer" +.It Li "FAN3" Ta "RPM" Ta "Fan tachometer" +.It Li "+2.5V" Ta "uV" Ta "Voltage" +.It Li "+1.5V (Vccp)" Ta "uV" Ta "Voltage" +.It Li "+3.3V (VCC)" Ta "uV" Ta "Voltage" +.It Li "+5V" Ta "uV" Ta "Voltage" +.It Li "+12V" Ta "uV" Ta "Voltage" +.It Li "+3.3V (VTR)" Ta "uV" Ta "Voltage" +.It Li "+3V (Vbat)" Ta "uV" Ta "Voltage" +.El +.Pp +.Nm +provides the standard +.Xr watchdog 4 +interface and may be used with +.Xr watchdogd 8 . +The watchdog timer may be configured to a value from 1 second to 255 +minutes. +The watchdog timer has a resolution of 1 second in the timeout interval +1 to 255 seconds. +Outside this interval, the resolution is 1 minute. +.Pp +Note that the pin used for signalling the timer expiration is +configurable and may on some boards be intended for other uses than this. +Because of this, the chip may not by default be configured to use the +pin for watchdog operation. +To force the +.Nm +device to use the pin for watchdog operation, the driver may be +configured with an +.Xr autoconf 9 +.Ar flags +setting of 0x0001. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr watchdog 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 , +.Xr watchdogd 8 , +.Xr autoconf 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Michael Knudsen Aq Mt mk@openbsd.org . diff --git a/static/openbsd/man4/scmi.4 b/static/openbsd/man4/scmi.4 new file mode 100644 index 00000000..0ec7f88a --- /dev/null +++ b/static/openbsd/man4/scmi.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: scmi.4,v 1.3 2023/04/09 06:27:52 jsg Exp $ +.\" +.\" Copyright (c) 2023 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 9 2023 $ +.Dt SCMI 4 +.Os +.Sh NAME +.Nm scmi +.Nd System Control and Management Interface +.Sh SYNOPSIS +.Cd "scmi* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver handles clocks that are managed through the ARM System +Control and Management Interface specification. +.Sh SEE ALSO +.Rs +.%T System Control and Management Interface (SCMI) specification +.%N ARM DEN 0056C +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/scsi.4 b/static/openbsd/man4/scsi.4 new file mode 100644 index 00000000..4a011b16 --- /dev/null +++ b/static/openbsd/man4/scsi.4 @@ -0,0 +1,183 @@ +.\" $OpenBSD: scsi.4,v 1.40 2025/11/24 09:52:11 jsg Exp $ +.\" +.\" Copyright (c) 1996 +.\" Julian Elischer . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 24 2025 $ +.Dt SCSI 4 +.Os +.Sh NAME +.Nm scsi , +.Nm scsibus +.Nd SCSI system +.Sh SYNOPSIS +.Cd "cd* at scsibus?" +.Cd "ch* at scsibus?" +.Cd "safte* at scsibus?" +.Cd "sd* at scsibus?" +.Cd "ses* at scsibus?" +.Cd "st* at scsibus?" +.Cd "uk* at scsibus?" +.Pp +.Cd "# multipath support" +.Cd "emc* at scsibus?" +.Cd "hds* at scsibus?" +.Cd "rdac* at scsibus?" +.Cd "sym* at scsibus?" +.Sh DESCRIPTION +The +.Em SCSI +system provides a uniform and modular system for the implementation +of drivers to control various SCSI devices, and to utilize different +SCSI host adapters through host adapter drivers. +When the system probes the +.Em SCSI +buses, it attaches any devices it finds to the appropriate +drivers. +If no driver seems appropriate, then it attaches the device to the +uk (unknown) driver so that user level SCSI ioctls may +still be performed against the device. +.Sh KERNEL CONFIGURATION +The option SCSIDEBUG enables the debug ioctl. +.Pp +All devices and the SCSI buses support boot time allocation so that +an upper number of devices and controllers does not need to be configured; +.Cd "sd* at scsibus?" +will suffice for any number of disk drivers. +.Pp +The devices are either +.Em wired +so they appear as a particular device unit or +.Em counted +so that they appear as the next available unused unit. +.Pp +To configure a driver in the kernel without wiring down the device use a +config line similar to +.Cd "ch* at scsibus?" +to include the changer driver. +.Pp +To wire down a unit use a config line similar to +.Cd "ch1 at scsibus0 target 4 lun 0" +to assign changer 1 as the changer with SCSI ID 4, +SCSI logical unit 0 on SCSI bus 0. +Individual scsibuses can be wired down to specific controllers with +a config line similar to +.Cd "scsibus0 at ahc0" +which assigns SCSI bus 0 to the first unit using the ahc driver. +For controllers supporting more than one bus, +the particular bus can be specified as in +.Cd "scsibus3 at ahc1 bus 1" +which assigns scsibus 1 to the second bus probed on the ahc1 device. +.Pp +When there is a mixture of wired down and counted devices then the +counting begins with the first non-wired down unit for a particular +type. +That is, if a disk is wired down as +.Cd "sd1 at scsibus?" , +then the first non-wired disk shall come on line as +.Em sd2 . +.Sh IOCTLS +There are a number of ioctls that work on any +.Em SCSI +device. +They are defined in +.In sys/scsiio.h +and can be applied against any SCSI device that permits them. +For the tape, it must be applied against the control +device. +See the manual page for each device type for more information about +how generic SCSI ioctls may be applied to a specific device. +.Bl -tag -width DIOCSDINFO____ +.It Dv SCIOCRESET +Reset a device. +.It Dv SCIOCDEBUG Fa "int *" +Turn on debugging. +All SCSI operations originating from this device's driver +will be traced to the console, along with other information. +Debugging is controlled by four bits, described in the header file. +If no debugging is configured into the kernel, debugging will have +no effect. +.Em SCSI +debugging is controlled by the configuration option +.Em SCSIDEBUG . +.It Dv SCIOCCOMMAND Fa "scsireq_t *" +Take a SCSI command and data from a user process and apply them to the SCSI +device. +Return all status information and return data to the process. +The ioctl will return a successful status even if the device rejected the +command. +As all status is returned to the user, it is up to the user +process to examine this information to decide the success of the command. +.It Dv SCIOCIDENTIFY Fa "struct scsi_addr *" +Ask the driver what its bus, target and lun are. +In addition, the device type, ATAPI or SCSI, is returned. +.El +.Sh ADAPTERS +The system allows common device drivers to work through many different +types of adapters. +The adapters take requests from the upper layers and do all I/O between the +.Em SCSI +bus and the system. +The maximum size of a transfer is governed by the adapter. +Most adapters can transfer 64KB in a single operation, and many can transfer +larger amounts. +.Sh DIAGNOSTICS +When the kernel is compiled with option SCSIDEBUG, the SCIOCDEBUG ioctl +can be used to enable various amounts of tracing information on any +specific device. +Devices not being traced will not produce trace information. +The four bits that make up the debug level each control certain types +of debugging information. +.Bl -tag -width "Bit 0" +.It Dv Bit 0 +shows all SCSI bus operations including SCSI commands, +error information and the first 48 bytes of any data transferred. +.It Dv Bit 1 +shows routines called. +.It Dv Bit 2 +shows information about what branches are taken and often some +of the return values of functions. +.It Dv Bit 3 +shows more detailed information including DMA scatter-gather logs. +.El +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr emc 4 , +.Xr hds 4 , +.Xr intro 4 , +.Xr mpath 4 , +.Xr rdac 4 , +.Xr safte 4 , +.Xr sd 4 , +.Xr ses 4 , +.Xr st 4 , +.Xr sym 4 , +.Xr uk 4 , +.Xr scsi 8 +.Sh HISTORY +This +.Nm +system appeared in Mach 2.5 at TRW. diff --git a/static/openbsd/man4/sd.4 b/static/openbsd/man4/sd.4 new file mode 100644 index 00000000..02d30c6c --- /dev/null +++ b/static/openbsd/man4/sd.4 @@ -0,0 +1,225 @@ +.\" $OpenBSD: sd.4,v 1.21 2024/12/21 01:00:31 jsg Exp $ +.\" $NetBSD: sd.4,v 1.3 1996/10/20 23:15:23 explorer Exp $ +.\" +.\" Copyright (c) 1996 +.\" Julian Elischer . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 21 2024 $ +.Dt SD 4 +.Os +.Sh NAME +.Nm sd +.Nd SCSI disk driver +.Sh SYNOPSIS +.Cd "sd* at scsibus?" +.Cd "#sd0 at scsibus0 target 3 lun 0" Pq fixed-configuration example +.Sh DESCRIPTION +The +.Nm +driver provides support for a +.Tn SCSI +disk. +It allows the disk to be divided up into a set of pseudo devices called +.Em partitions . +In general the interfaces are similar to those described by +.Xr wd 4 . +.Pp +.Tn SCSI +devices have a fairly high level interface to the system and talk to it via +a +.Tn SCSI +host adapter +(e.g., +.Xr ahc 4 ) . +A +.Tn SCSI +adapter must also be separately configured into the system +before a +.Tn SCSI +disk can be configured. +.Pp +When the +.Tn SCSI +adapter is probed during boot, the +.Tn SCSI +bus is scanned for devices. +Any devices found which answer as +.Sq Em Direct +type devices will be attached to the +.Nm +driver. +.\"In +.\".Fx +.\"releases prior to 2.1, the first found was attached as +.\".Li sd0 , +.\"the second +.\".Li sd1 , +.\"and so on. +.\"Beginning in 2.1 it became possible to lock down the assignment of +.\"devices on the +.\".Tn SCSI +.\"bus to particular units of the +.\".Nm +.\"device; refer to +.\".Xr scsi 4 +.\"for details on kernel configuration. +.Sh PARTITIONING +.\"The +.\".Nm +.\"driver allows the disk to have two levels of partitioning. +.\"One layer, called the +.\".Dq slice layer , +.\"is used to separate the +.\".Fx +.\"areas of the disk from areas used by other operating systems. +.\"The second layer is the native +.\".Bx 4.4 +.\"partitioning scheme, +.\".Xr disklabel 5 , +.\"which is used to subdivide the +.\".Fx +.\"slices into areas for individual filesystems and swap spaces. +.\"For more information, see +.\".Xr fdisk 8 +.\"and +.\".Xr disklabel 8 , +.\"respectively.) +On many systems +.Xr disklabel 8 +is used to partition the drive into filesystems. +On some systems the +.Ox +portion of the disk resides within a native partition, and another +program is used to create the +.Ox +portion. +.Pp +For example, the i386 port uses +.Xr fdisk 8 +to partition the disk into a BIOS level partition. +This allows sharing the disk with other operating systems. +.\"If an uninitialized disk is opened, the slice table will be +.\"initialized with a fictitious +.\".Fx +.\"slice spanning the entire disk. Similarly, if an uninitialized +.\"(or +.\".No non- Ns Fx ) +.\"slice is opened, its disklabel will be initialized with parameters returned +.\"by the drive and a single +.\".Sq Li c +.\"partition encompassing the entire slice. +.Sh IOCTLS +The following +.Xr ioctl 2 +calls apply to +.Tn SCSI +disks as well as to other disks. +They are defined in the header file +.In sys/dkio.h . +.Bl -tag -width Ds +.\".It Dv DIOCSBAD +.\"Usually used to set up a bad-block mapping system on the disk. +.\".Tn SCSI +.\"drive incorporate their own bad-block mapping so this command is not +.\"implemented. +.It Dv DIOCGDINFO Fa "struct disklabel *" +Read, from the kernel, the in-core copy of the disklabel for the +drive. +This may be a fictitious disklabel if the drive has never +been initialized, in which case it will contain information read +from the +.Tn SCSI +inquiry commands. +.It Dv DIOCSDINFO Fa "struct disklabel *" +Give the driver a new disklabel to use. +The driver +.Em will not +write the new +disklabel to the disk. +.It Dv DIOCWDINFO Fa "struct disklabel *" +Give the driver a new disklabel to use. +The driver +.Em will +write the new disklabel to the disk. +.It Dv DIOCLOCK Fa "int *" +Lock the media cartridge into the device, or unlock a cartridge previously +locked. +Used to prevent user and software eject while the media is in use. +.It Dv DIOCEJECT +Eject the media cartridge from a removable device. +.It Dv DIOCINQ Fa "struct dk_inquiry *" +Read the devices product information. +.El +.Pp +In addition, the +.Xr scsi 4 +general +.Fn ioctl +commands may be used with the +.Nm +driver, but only against the +.Sq Li c +(whole disk) partition. +.Sh NOTES +If a removable device is attached to the +.Nm +driver, then the act of changing the media will invalidate the +disklabel and information held within the kernel. +To avoid corruption, all access to the device will be discarded until there +are no more open file descriptors referencing the device. +During this period, all new open attempts will be rejected. +When no more open file descriptors reference the device, the first next +open will load a new set of parameters (including disklabel) for the drive. +.Sh FILES +.Bl -tag -width /dev/rsdXXXXX -compact +.It Pa /dev/sd Ns Ar u Ns Ar p +block mode +.Tn SCSI +disk unit +.Ar u , +partition +.Ar p +.It Pa /dev/rsd Ns Ar u Ns Ar p +raw mode +.Tn SCSI +disk unit +.Ar u , +partition +.Ar p +.El +.Sh DIAGNOSTICS +None. +.Sh SEE ALSO +.Xr intro 4 , +.Xr scsi 4 , +.Xr wd 4 , +.Xr disklabel 5 , +.Xr disklabel 8 , +.Xr fdisk 8 +.Sh HISTORY +.An Julian Elischer +wrote +.Nm +for Mach 2.5 and ported it to 386BSD. diff --git a/static/openbsd/man4/sdhc.4 b/static/openbsd/man4/sdhc.4 new file mode 100644 index 00000000..272d17b2 --- /dev/null +++ b/static/openbsd/man4/sdhc.4 @@ -0,0 +1,39 @@ +.\" $OpenBSD: sdhc.4,v 1.7 2020/08/06 10:10:16 jsg Exp $ +.\" +.\" Theo de Raadt, 2006. Public Domain. +.\" +.Dd $Mdocdate: August 6 2020 $ +.Dt SDHC 4 +.Os +.Sh NAME +.Nm sdhc +.Nd SD Host Controller +.Sh SYNOPSIS +.Cd "sdhc* at acpi?" +.Cd "sdhc* at fdt?" +.Cd "sdhc* at pci?" +.Cd "sdmmc* at sdhc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for SD controllers following the +SD Host Controller Standard Simplified Specification. +.Pp +The +.Xr sdmmc 4 +subsystem performs SD/MMC transactions to communicate with +whatever MMC, SD, SDHC, or SDIO devices are inserted into the SD slot. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sdmmc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Uwe Stuehler Aq Mt uwe@openbsd.org . diff --git a/static/openbsd/man4/sdmmc.4 b/static/openbsd/man4/sdmmc.4 new file mode 100644 index 00000000..789e43db --- /dev/null +++ b/static/openbsd/man4/sdmmc.4 @@ -0,0 +1,66 @@ +.\" $OpenBSD: sdmmc.4,v 1.15 2022/01/19 13:45:22 visa Exp $ +.\" +.\" Theo de Raadt, 2006. Public Domain. +.\" +.Dd $Mdocdate: January 19 2022 $ +.Dt SDMMC 4 +.Os +.Sh NAME +.Nm sdmmc +.Nd SD bus +.Sh SYNOPSIS +.Cd "# arm64" +.Cd "sdmmc* at amlmmc?" +.Cd "sdmmc* at bcmsdhost?" +.Cd "sdmmc* at dwmmc?" +.Cd "sdmmc* at imxesdhc?" +.Cd "sdmmc* at sximmc?" +.Pp +.Cd "# armv7" +.Cd "sdmmc* at bcmsdhost?" +.Cd "sdmmc* at dwmmc?" +.Cd "sdmmc* at imxesdhc?" +.Cd "sdmmc* at mvpxa?" +.Cd "sdmmc* at ommmc?" +.Cd "sdmmc* at sximmc?" +.Pp +.Cd "# octeon" +.Cd "sdmmc* at octmmc?" +.Pp +.Cd "# riscv64" +.Cd "sdmmc* at cdsdhc?" +.Cd "sdmmc* at dwmmc?" +.Pp +.Cd "# sparc64" +.Cd "sdmmc* at wbsd?" +.Pp +.Cd "# all architectures" +.Cd "sdmmc* at rtsx?" +.Cd "sdmmc* at sdhc?" +.Sh DESCRIPTION +The +.Nm +subsystem provides machine-independent bus support and drivers for +SD/MMC devices. +.Pp +Standard SD/SDHC memory devices will show up as a fake SCSI disk, using +.Xr scsibus 4 +and +.Xr sd 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr rtsx 4 , +.Xr scsibus 4 , +.Xr sd 4 , +.Xr sdhc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Uwe Stuehler Aq Mt uwe@openbsd.org . diff --git a/static/openbsd/man4/sdtemp.4 b/static/openbsd/man4/sdtemp.4 new file mode 100644 index 00000000..d2e983a3 --- /dev/null +++ b/static/openbsd/man4/sdtemp.4 @@ -0,0 +1,69 @@ +.\" $OpenBSD: sdtemp.4,v 1.11 2014/11/14 07:24:12 jsg Exp $ +.\" +.\" Copyright (c) 2008 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 14 2014 $ +.Dt SDTEMP 4 +.Os +.Sh NAME +.Nm sdtemp +.Nd SO-DIMM (JC-42.4) temperature sensor +.Sh SYNOPSIS +.Cd "sdtemp* at iic?" +.Sh DESCRIPTION +The +.Nm +driver retrieves temperature sensor information from memory +modules which contain sensor chips defined in JEDEC JC-42.4. +.Pp +Current sensor chips include: +.Pp +.Bl -tag -width Dv -offset indent -compact +.It ADT ADT7408 +.It Atmel AT30TS00 +.It Atmel AT30TSE002 +.It Atmel AT30TSE004 +.It Giantec GT30TS00 +.It Giantec GT34TS02 +.It IDT TSE2002B3 +.It IDT TSE2002GB2 +.It IDT TSE2004GB2 +.It IDT TS3000B3 +.It IDT TS3000GB0 +.It IDT TS3000GB2 +.It IDT TS3001GB2 +.It Maxim 6604 +.It Microchip MCP9804 +.It Microchip MCP9805 +.It Microchip MCP98242 +.It Microchip MCP98243 +.It Microchip MCP98244 +.It NXP SE97 +.It NXP SE98 +.It ON CAT34TS02 +.It ON CAT34TS04 +.It ON CAT6095 +.It ST STTS424 +.It ST STTS2002 +.It ST STTS2004 +.It ST STTS3000 +.El +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.4 . diff --git a/static/openbsd/man4/se.4 b/static/openbsd/man4/se.4 new file mode 100644 index 00000000..409f1e22 --- /dev/null +++ b/static/openbsd/man4/se.4 @@ -0,0 +1,162 @@ +.\" $OpenBSD: se.4,v 1.9 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 2010 +.\" Christopher Zimmermann . All rights reserved. +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/sis.4,v 1.2 1999/11/15 23:14:27 phantom Exp $ +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt SE 4 +.Os +.Sh NAME +.Nm se +.Nd SiS 190/191 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "se* at pci?" +.Cd "atphy* at mii?" +.Cd "brgphy* at mii?" +.Cd "eephy* at mii?" +.Cd "etphy* at mii?" +.Cd "rlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SiS190 Fast Ethernet controller +integrated into the SiS965L and SiS966L southbridges, +and the SiS191 Gigabit controller +integrated into the SiS965 and SiS966 southbridges. +.Pp +Both SiS 190 and SiS 191 embed an Ethernet MAC with external PHY. +They use a bus master DMA and a scatter/gather descriptor scheme +and include a 64-bit multicast hash filter. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 1000baseSX +Set 1000Mbps (Gigabit Ethernet) on fiber operation. +Only +.Ar full-duplex +mode is supported at this speed. +.It 1000baseT +Set 1000Mbps (Gigabit Ethernet) on copper operation. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation. +.It half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "se0: EEPROM read timeout" +The driver could not read the controller's MAC address from its EEPROM. +.It "se0: invalid EEPROM signature" +The driver could not find the expected EEPROM signature and could not read +the controller's MAC address. +.It "se0: Could not find PCI-ISA bridge" +The driver could not read the controller's MAC address from the CMOS memory +connected to the PCI-ISA bridge. +.It "se0: PHY read timeout" +The driver could not read data from the PHY. +.It "se0: PHY write timeout" +The driver could not write data to the PHY. +.It "se0: watchdog timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr atphy 4 , +.Xr brgphy 4 , +.Xr eephy 4 , +.Xr etphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr rlphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was adapted by +.An Alexander Pohoyda Aq Mt alexander.pohoyda@gmx.net +from the +.Xr sis 4 +driver written by +.An Bill Paul Aq Mt wpaul@ee.columbia.edu , +and ported to +.Ox +by +.An Christopher Zimmermann Aq Mt madroach@zakweb.de . +SiS 191 support was added by +.An Nikolay Denev Aq Mt ndenev@gmail.com . diff --git a/static/openbsd/man4/sec.4 b/static/openbsd/man4/sec.4 new file mode 100644 index 00000000..dd172271 --- /dev/null +++ b/static/openbsd/man4/sec.4 @@ -0,0 +1,156 @@ +.\" $OpenBSD: sec.4,v 1.6 2024/09/20 01:15:53 dlg Exp $ +.\" +.\" Copyright (c) 2023 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 20 2024 $ +.Dt SEC 4 +.Os +.Sh NAME +.Nm sec +.Nd route based IPsec VPN tunnel interface pseudo-device +.Sh SYNOPSIS +.Cd "pseudo-device sec" +.Sh DESCRIPTION +The +.Nm +driver provides point-to-point tunnel interfaces for IPv4 and IPv6 +protected by the +.Xr ipsec 4 +Encapsulating Security Payload (ESP) +protocol. +.Pp +Traffic is encapsulated in the ESP protocol and forwarded to the +remote endpoint by routing over a +.Nm +interface rather than matching policy in the IPsec Security Policy +Database (SPD). +.Nm +interfaces require the configuration of IPsec Security Associations (SAs) +.\" with the interface extension +between the local and remote endpoints. +Negotiation of interface SAs is supported by +.Xr iked 8 +and +.Xr isakmpd 8 +(the latter via +.Xr ipsecctl 8 ) . +.\" These IPsec IKE daemons negotiate ESP tunnel mode between 0.0.0.0/0 +.\" and 0.0.0.0/0. +.Pp +.Nm +interfaces can be created at runtime using the +.Ic ifconfig sec Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The interface itself can be configured with +.Xr ifconfig 8 ; +see its manual page for more information. +.Sh EXAMPLES +.Nm +can be used to provide secure and confidential IP connectivity +between sites over the public internet. +For example, a cloud provider may provide connectivity between +networks they host for a customer, and that customers own +.Dq on premises +networks using IPsec tunnels. +.Ox +can be set up on the customer side given the following parameters: +.Pp +.Bl -tag -width Customer-Gateway -offset indent -compact +.It Pre-Shared Key +7kA7evdkd50Q5YdCCF9t8eftgEgL4vk2 +.El +.Pp +Outside IP Addresses: +.Bl -tag -width Customer-Gateway -offset indent -compact +.It Customer Gateway +192.0.2.8 +.It Provider Gateway +198.51.100.14 +.El +.Pp +Inside IP Addresses: +.Bl -tag -width Customer-Gateway -offset indent -compact +.It Customer Gateway +169.254.229.42/30 +.It Provider Gateway +169.254.229.41/30 +.El +.Pp +A +.Nm +interface can be configured on the customer gateway: +.Bd -literal -offset indent +# ifconfig sec0 create +# ifconfig sec0 inet 169.254.229.42/30 169.254.229.41 +# ifconfig sec0 up +.Ed +.Pp +.Xr iked 8 +can be used for IKEv2 negotiation of the IPsec tunnel with the following +.Xr iked.conf 5 +configuration: +.Bd -literal -offset indent +ikev2 "s2s" active \\ + from any to any \\ + local 192.0.2.8 peer 198.51.100.14 \\ + psk "7kA7evdkd50Q5YdCCF9t8eftgEgL4vk2" \\ + iface sec0 +.Ed +.Pp +Alternatively, IKEv1 negotiation of the IPsec tunnel SAs is supported by +.Xr isakmpd 8 +and +.Xr ipsecctl 8 . +The equivalent +.Xr ipsec.conf 5 +configuration for the given parameters follows: +.Bd -literal -offset indent +ike interface sec0 \\ + local 192.0.2.8 peer 198.51.100.14 \\ + psk "7kA7evdkd50Q5YdCCF9t8eftgEgL4vk2" +.Ed +.Pp +Once the Security Associations are established, communication between +the customer and provider gateways is enabled. +.Pp +Routes to networks hosted by the provider can be added using the +providers +.Dq inside IP +address as the gateway address, or negotiated using a dynamic routing +protocol. +Multiple +.Nm +interfaces may be configured to talk to separate provider gateways, +providing redundancy or multiple paths between sites. +.Sh SEE ALSO +.Xr ipsec 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr pf.conf 5 , +.Xr ifconfig 8 , +.Xr iked 8 , +.Xr ipsecctl 8 , +.Xr isakmpd 8 , +.Xr netstart 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/ses.4 b/static/openbsd/man4/ses.4 new file mode 100644 index 00000000..e2f0712a --- /dev/null +++ b/static/openbsd/man4/ses.4 @@ -0,0 +1,84 @@ +.\" $OpenBSD: ses.4,v 1.20 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: July 16 2013 $ +.Dt SES 4 +.Os +.Sh NAME +.Nm ses +.Nd SCSI Enclosure Services +.Sh SYNOPSIS +.Cd "ses* at scsibus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for monitoring the various environmental sensors +present in SCSI enclosures using the SCSI Enclosure Services command set. +The hardware monitoring is accessed via the +.Va hw.sensors +.Xr sysctl 8 +variable. +.Pp +SCSI devices have a fairly high level interface to the system and talk to it +via a SCSI host adapter (e.g.\& +.Xr ahc 4 ) . +A SCSI adapter must also be separately configured into the system before a +SCSI enclosure can be configured. +.Pp +When the SCSI adapter is probed during boot, the SCSI bus is scanned for +devices. +Any SCSI-2 devices of type +.Dq Enclosure service +or SCSI-3 devices of type +.Dq Processor +will be attached to the +.Nm +driver. +.Pp +SES compliant devices can provide an arbitrary set of sensors which may +include the following types: +.Bl -column "Sensor" "Units" "Typical" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical Use" +.It Li "temp" Ta "uK" Ta "temperature" +.It Li "fan" Ta "RPM" Ta "fan" +.It Li "psu" Ta "On/Off" Ta "power supply" +.It Li "doorlock" Ta "On/Off" Ta "door lock" +.It Li "alarm" Ta "On/Off" Ta "enclosure alarm" +.El +.Pp +Sensor data is updated every 10 seconds. +.Pp +An enclosure may provide environmental information using an alternative +command set to the SCSI Enclosure Services used by this driver. +Enclosures using the SCSI Accessed Fault-Tolerant Enclosure command set +may be monitored by the +.Xr safte 4 +driver. +.Sh SEE ALSO +.Xr intro 4 , +.Xr safte 4 , +.Xr scsibus 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/sf.4 b/static/openbsd/man4/sf.4 new file mode 100644 index 00000000..7c581297 --- /dev/null +++ b/static/openbsd/man4/sf.4 @@ -0,0 +1,185 @@ +.\" $OpenBSD: sf.4,v 1.26 2022/02/18 10:24:32 jsg Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/man4.i386/sf.4,v 1.4 1999/09/26 18:35:30 wpaul Exp $ +.\" +.\" $NetBSD: sf.4,v 1.5 2003/03/31 12:34:49 bjh21 Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt SF 4 +.Os +.Sh NAME +.Nm sf +.Nd Adaptec AIC-6915 "Starfire" PCI 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "sf* at pci?" +.Cd "sqphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Adaptec Duralink Fast Ethernet adapters +based on the Adaptec AIC-6915 "Starfire" chipset. +This includes the following: +.Pp +.Bl -bullet -offset indent -compact +.It +ANA-62011 64-bit single port 10/100baseTX +.It +ANA-62022 64-bit dual port 10/100baseTX +.It +ANA-62044 64-bit quad port 10/100baseTX +.It +ANA-69011 32-bit single port 10/100baseTX +.It +ANA-62020 64-bit single port 100baseFX +.El +.Pp +The AIC-6915 is a bus master controller with an MII interface. +It supports high and low priority transmit and receive queues, TCP/IP +checksum offload, multiple DMA descriptor formats and both polling +and producer/consumer DMA models. +The AIC-6915 receive filtering options include a 16 entry perfect +filter, a 512-bit hash table for multicast addresses, a 512-bit hash +table for priority address matching and VLAN filtering. +An external MII-compliant transceiver is required for media interfacing. +.Pp +Multiport adapters consist of several AIC-6915 controllers connected +via a PCI to PCI bridge. +Each controller is treated as a separate interface by the +.Nm +driver. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation. +.It half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr sqphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T The Adaptec AIC-6915 Programmer's Manual +.%U https://download.adaptec.com/pdfs/user_guides/aic6915_pg.pdf +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 2.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jason R. Thorpe Aq Mt thorpej@NetBSD.org +and ported to +.Ox +by +.An Martin Reindl Aq Mt martin@openbsd.org . +.Sh BUGS +The +.Nm +driver does not support the IPv4/TCP/UDP checksum function of the AIC-6915. +.Pp +The +.Nm +driver does not support the VLAN function of the AIC-6915. diff --git a/static/openbsd/man4/sili.4 b/static/openbsd/man4/sili.4 new file mode 100644 index 00000000..b9ca0db4 --- /dev/null +++ b/static/openbsd/man4/sili.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: sili.4,v 1.6 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2007 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt SILI 4 +.Os +.Sh NAME +.Nm sili +.Nd Silicon Image 3124/3132/3531 SATA controller +.Sh SYNOPSIS +.Cd "sili* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for SATA controllers using the Silicon Image +3124/3132/3531 SATALink chipsets. +.Pp +Although +.Nm +controllers are actual ATA controllers, the driver emulates SCSI via a +translation layer. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org +and +.An Christopher Pascoe Aq Mt pascoe@openbsd.org . diff --git a/static/openbsd/man4/simpleamp.4 b/static/openbsd/man4/simpleamp.4 new file mode 100644 index 00000000..82a471f4 --- /dev/null +++ b/static/openbsd/man4/simpleamp.4 @@ -0,0 +1,40 @@ +.\" $OpenBSD: simpleamp.4,v 1.1 2020/06/11 00:20:46 patrick Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 11 2020 $ +.Dt SIMPLEAMP 4 +.Os +.Sh NAME +.Nm simpleamp +.Nd simple audio amplifier +.Sh SYNOPSIS +.Cd "simpleamp* at fdt?" +.Sh DESCRIPTION +.Nm +is a generic driver for audio amplifier. +.Sh SEE ALSO +.Xr intro 4 , +.Xr simpleaudio 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/simpleaudio.4 b/static/openbsd/man4/simpleaudio.4 new file mode 100644 index 00000000..c685a252 --- /dev/null +++ b/static/openbsd/man4/simpleaudio.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: simpleaudio.4,v 1.3 2021/04/08 11:53:16 jmc Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 8 2021 $ +.Dt SIMPLEAUDIO 4 +.Os +.Sh NAME +.Nm simpleaudio +.Nd simple audio card +.Sh SYNOPSIS +.Cd "simpleaudio* at fdt?" +.Cd "audio* at simpleaudio?" +.Sh DESCRIPTION +.Nm +is a generic driver for audio cards. +It represents the logical connection of the DMA controller, +the codec, and auxiliary devices like a speaker amplifier. +.Sh SEE ALSO +.Xr audio 4 , +.Xr graphaudio 4 , +.Xr intro 4 , +.Xr simpleamp 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/simplefb.4 b/static/openbsd/man4/simplefb.4 new file mode 100644 index 00000000..90ff117f --- /dev/null +++ b/static/openbsd/man4/simplefb.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: simplefb.4,v 1.2 2019/01/19 21:48:10 sthen Exp $ +.\" +.\" Copyright (c) 2017 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 19 2019 $ +.Dt SIMPLEFB 4 +.Os +.Sh NAME +.Nm simplefb +.Nd simple frame buffer +.Sh SYNOPSIS +.Cd "simplefb* at fdt?" +.Cd "wsdisplay* at simplefb?" +.Sh DESCRIPTION +The +.Nm +driver supports the frame buffer set up by firmware or the bootloader +on systems that use a device tree to describe the hardware. +.Pp +The +.Nm +driver interfaces the frame buffer with the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/simplepanel.4 b/static/openbsd/man4/simplepanel.4 new file mode 100644 index 00000000..6145932c --- /dev/null +++ b/static/openbsd/man4/simplepanel.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: simplepanel.4,v 1.1 2020/04/13 11:54:43 jmc Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 13 2020 $ +.Dt SIMPLEPANEL 4 +.Os +.Sh NAME +.Nm simplepanel +.Nd simple panel display +.Sh SYNOPSIS +.Cd "simplepanel* at mainbus?" +.Sh DESCRIPTION +.Nm +is a generic driver for panels, +integrated into the +.Xr drm 4 +subsystem. +It also provides a hardcoded mode for the +Pinebook Pro display panel. +.Sh SEE ALSO +.Xr mainbus 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@openbsd.org . diff --git a/static/openbsd/man4/siop.4 b/static/openbsd/man4/siop.4 new file mode 100644 index 00000000..ea30bf96 --- /dev/null +++ b/static/openbsd/man4/siop.4 @@ -0,0 +1,140 @@ +.\" $OpenBSD: siop.4,v 1.21 2022/02/17 12:24:08 jsg Exp $ +.\" $NetBSD: siop.4,v 1.3 2000/10/23 16:38:10 bouyer Exp $ +.\" +.\" Copyright (c) 2000 Manuel Bouyer. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by the University of +.\" California, Berkeley and its contributors. +.\" 4. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 17 2022 $ +.Dt SIOP 4 +.Os +.Sh NAME +.Nm siop +.Nd LSI/Symbios Logic/NCR 53c8xx SCSI interface +.Sh SYNOPSIS +.Cd "siop* at pci?" +.Pp +.Cd "# hppa" +.Cd "siop* at mainbus? irq 3" +.Cd "siop* at phantomas? irq 3" +.Cd "siop* at uturn? irq 3" +.Sh DESCRIPTION +The +.Nm +driver provides support for following LSI/Symbios Logic/NCR 53c8xx and +related +.Tn SCSI +controller chips: +.Pp +.Bl -dash -compact -offset indent +.It +53c720 and 53c770 (Fast-Wide +.Tn SCSI ) +.It +53c810, 53c810a and 53c815 (Fast +.Tn SCSI ) +.It +53c820, 53c825 and 53c825a (Fast-Wide +.Tn SCSI ) +.It +53c860 (Ultra +.Tn SCSI ) +.It +53c875 and 53c875j (Ultra-Wide +.Tn SCSI ) +.It +53c876 (Dual Ultra-Wide +.Tn SCSI ) +.It +53c885 (Ultra-Wide +.Tn SCSI +and +.Tn Ethernet ) +.It +53c895 and 53c895a (Ultra2-Wide +.Tn SCSI ) +.It +53c896 (PCI 64bit, dual Ultra2-Wide +.Tn SCSI ) +.It +53c1010 (PCI 64bit, dual Ultra3-Wide +.Tn SCSI . +.Em NOTE : +at this time +.Nm +supports at most Ultra2-Wide with this chip) +.It +53c1510D (dual Ultra2-Wide +.Tn SCSI ) +.El +.Pp +.Nm +replaces the older +.Nm ncr +driver which supported most of these devices. +.Pp +Older 53C700 and 53C710 controllers are supported by the +.Xr oosiop 4 +and +.Xr osiop 4 +drivers, respectively. +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr oosiop 4 , +.Xr osiop 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Nx 1.5 , +.Ox +support was added in +.Ox 2.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Manuel Bouyer Aq Mt Manuel.Bouyer@lip6.fr +for +.Nx . +It was ported to +.Ox +with 53c1010 support added by +.An Ken Westerback Aq Mt krw@openbsd.org +using code from the +.Fx +sym-2 driver written by +.An Gerard Roudier Aq Mt groudier@FreeBSD.org . diff --git a/static/openbsd/man4/sis.4 b/static/openbsd/man4/sis.4 new file mode 100644 index 00000000..0d5d42ac --- /dev/null +++ b/static/openbsd/man4/sis.4 @@ -0,0 +1,172 @@ +.\" $OpenBSD: sis.4,v 1.35 2022/02/18 10:24:32 jsg Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/sis.4,v 1.2 1999/11/15 23:14:27 phantom Exp $ +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt SIS 4 +.Os +.Sh NAME +.Nm sis +.Nd SiS 900, SiS 7016, and NS DP83815/6 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "sis* at pci?" +.Cd "icsphy* at mii?" +.Cd "nsphyter* at mii?" +.Cd "rlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI Ethernet adapters and embedded +controllers based on the Silicon Integrated Systems SiS 900 / +SiS 7016 Fast Ethernet controller chips, and National +Semiconductor DP83815 (MacPHYTER) / DP83816 (MacPHYTER-II) PCI +Ethernet controller chips, including the following: +.Pp +.Bl -bullet -compact +.It +@Nifty FNECHARD IFC USUP-TX +.It +MELCO LGY-PCI-TXC +.It +Netgear FA311, FA312, FA331 +.It +Soekris Engineering lan1621, lan1641 +.El +.Pp +The SiS 900 is a 100Mbps Ethernet MAC and MII-compliant transceiver +in a single package. +It uses a bus master DMA and a scatter/gather descriptor scheme. +The SiS 7016 is similar to the SiS 900 except that it has no internal PHY, +requiring instead an external transceiver to be attached to its MII interface. +The SiS 900 and SiS 7016 both have a 128-bit multicast hash filter +and a single perfect filter entry for the station address. +.Pp +The NS DP83815 and DP83816 are also 100Mbps Ethernet MACs +with integrated PHY. +The NatSemi chips and the SiS chips share many of the same features and +a fairly similar programming interface, and hence are supported +by the same driver. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation. +.It half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "sis0: couldn't map ports/memory" +A fatal initialization error has occurred. +.It "sis0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "sis0: watchdog timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.It "sis0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.It "sis0: no memory for tx list" +The driver failed to allocate an mbuf for the transmitter ring when +allocating a pad buffer or collapsing an mbuf chain into a cluster. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr icsphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr nsphyter 4 , +.Xr pci 4 , +.Xr rlphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T SiS 900 and SiS 7016 datasheets +.%U https://www.sis.com +.Re +.Rs +.%T NatSemi DP83815 and DP83816 datasheets +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 3.0 . +.Ox +support was added in +.Ox 2.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ee.columbia.edu +and ported to +.Ox +by +.An Aaron Campbell Aq Mt aaron@openbsd.org . diff --git a/static/openbsd/man4/sk.4 b/static/openbsd/man4/sk.4 new file mode 100644 index 00000000..0e1db6f1 --- /dev/null +++ b/static/openbsd/man4/sk.4 @@ -0,0 +1,210 @@ +.\" $OpenBSD: sk.4,v 1.70 2022/02/17 12:24:08 jsg Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/man4.i386/sk.4,v 1.3 1999/08/28 00:20:29 peter Exp $ +.\" +.Dd $Mdocdate: February 17 2022 $ +.Dt SK 4 +.Os +.Sh NAME +.Nm sk , +.Nm skc +.Nd SysKonnect XMAC II and Marvell Yukon 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "skc* at pci?" +.Cd "sk* at skc?" +.Cd "brgphy* at mii?" +.Cd "eephy* at mii?" +.Cd "xmphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for SysKonnect GEnesis and Marvell Yukon +88E8001, 88E8003 and 88E8010 based Gigabit Ethernet adapters, +including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +3Com 3c940 single port, copper adapter +.It +3Com 3c2000-T single port, copper adapter +.It +Allied Telesis AT-2916T, copper adapter +.It +Belkin F5D5005 v1000, copper adapter +.It +D-Link DGE-530T A1, copper adapter +.It +D-Link DGE-530T B1, copper adapter +.It +Fujitsu PP028GE1U, multimode fiber adapter +.It +Fujitsu PP028GE1X, multimode fiber adapter +.It +Fujitsu PW008GE1U, copper adapter +.It +Fujitsu PW008GE1X, copper adapter +.It +Linksys EG1032v2, copper adapter +.It +Linksys EG1064v2, copper adapter +.It +SMC 9452TX, copper adapter +.It +SysKonnect SK-9521 V2.0 single port, copper adapter +.It +SysKonnect SK-9821 single port, copper adapter +.It +SysKonnect SK-9821 V2.0 single port, copper adapter +.It +SysKonnect SK-9822 dual port, copper adapter +.It +SysKonnect SK-9841 single port, single mode fiber adapter +.It +SysKonnect SK-9842 dual port, single mode fiber adapter +.It +SysKonnect SK-9843 single port, multimode fiber adapter +.It +SysKonnect SK-9843 V2.0 single port, copper adapter +.It +SysKonnect SK-9844 dual port, multimode fiber adapter +.El +.Pp +The SysKonnect based adapters consist of two main components: the +XaQti Corp.\& +XMAC II Gigabit MAC (sk) and the SysKonnect GEnesis controller ASIC (skc). +The XMAC provides the Gigabit MAC and PHY support +while the GEnesis provides an interface to the PCI bus, DMA support, +packet buffering and arbitration. +The GEnesis can control up to two XMACs simultaneously, +allowing dual-port NIC configurations. +.Pp +The Marvell based adapters are a single integrated circuit, but are +still presented as a separate MAC (sk) and controller ASIC (skc). +.Pp +The GEnesis and Yukon 88E8001, 88E8003 and 88E8010 also support +jumbo frames. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width 1000baseSX +.It Cm autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It Cm 10baseT +Set 10Mbps operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 1000baseT +Set 1000baseT (Gigabit Ethernet) operation over twisted pair. +Both +.Cm full-duplex +and +.Cm half-duplex +modes are supported. +.It Cm 1000baseSX +Set 1000Mbps (Gigabit Ethernet) operation. +Both +.Cm full-duplex +and +.Cm half-duplex +modes are supported. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It Cm full-duplex +Force full duplex operation. +.It Cm half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by the card, try +.Ic ifconfig media . +For example, +.Ic ifconfig sk0 media . +.Sh SEE ALSO +.Xr arp 4 , +.Xr brgphy 4 , +.Xr eephy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr xmphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T XaQti XMAC II datasheet +.Re +.Rs +.%T SysKonnect GEnesis programming manual +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 3.0 , +and +.Ox +support was added in +.Ox 2.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ctr.columbia.edu . diff --git a/static/openbsd/man4/sm.4 b/static/openbsd/man4/sm.4 new file mode 100644 index 00000000..a331dd21 --- /dev/null +++ b/static/openbsd/man4/sm.4 @@ -0,0 +1,121 @@ +.\" $OpenBSD: sm.4,v 1.19 2012/06/20 19:37:15 jmc Exp $ +.\" $NetBSD: sm.4,v 1.3 1998/08/09 00:39:02 thorpej Exp $ +.\" +.\" Copyright (c) 1997 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 20 2012 $ +.Dt SM 4 +.Os +.Sh NAME +.Nm sm +.Nd SMC91C9x and SMC91C1xx-based 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "sm0 at isa? port 0x300 irq 10" +.Cd "sm* at pcmcia?" +.Cd "nsphy* at mii?" +.Sh DESCRIPTION +The +.Nm +device driver supports SMC91C9x and SMC91C1xx-based Ethernet interfaces. +.Pp +The ISA attachment of the +.Nm +driver supports any SMC91C9x-based Ethernet interface on the ISA +bus, including the EFA Info*Express SVC VLB interface, and the +on-board SMC91C9x Ethernet found in many embedded PCs and laptop +docking stations. +.Pp +The PCMCIA attachment of the +.Nm +driver supports Megahertz X-JACK Ethernet cards, NewMedia BASICS Ethernet +cards, and SMC EtherEZ 8020 series cards. +.Sh MEDIA SELECTION +The SMC91C1xx supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +The user can manually override the autoselected mode by adding media options +to the appropriate +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.El +.Pp +The SMC91C9x supports AUI and UTP media types: +.Pp +To enable the AUI media, select the +.Em 10base5 +or +.Em aui +media type with +.Xr ifconfig 8 Ns 's +.Sq media +directive. +To select UTP, select the +.Em 10baseT +or +.Em utp +media type. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "sm0: unable to read MAC address from CIS" +This indicates that the Ethernet address, which is stored in the +CIS information on the Megahertz X-JACK PCMCIA Ethernet card, is +corrupted. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr netintro 4 , +.Xr nsphy 4 , +.Xr pcmcia 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/smsc.4 b/static/openbsd/man4/smsc.4 new file mode 100644 index 00000000..8d4984bd --- /dev/null +++ b/static/openbsd/man4/smsc.4 @@ -0,0 +1,66 @@ +.\" $OpenBSD: smsc.4,v 1.5 2014/04/08 01:18:19 brad Exp $ +.\" +.\" Copyright (c) 2012 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 8 2014 $ +.Dt SMSC 4 +.Os +.Sh NAME +.Nm smsc +.Nd SMSC LAN95xx 10/100 USB Ethernet device +.Sh SYNOPSIS +.Cd "smsc* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver supports SMSC LAN9500/LAN9500A/LAN9530/LAN9730/LAN89530 USB 2.0 10/100 +Ethernet devices and LAN951x USB 2.0 hub and 10/100 Ethernet devices, including: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Gamber Johnson MAG Docking Station 7160-0204 +.It Gamber Johnson MAG Docking Station 7160-0205 +.It Gamber Johnson MAG Docking Station 7160-0227 +.It GWC Technology HE2440 +.It HP USB Media Port Replicator +.It j5create Newport Station JUD200 +.It Kensington Universal Notebook Docking Station (K33926US) +.It LevelOne USB-0501 +.It Samsung Central Station monitors +.It StarTech USBVGADOCK2 +.It XPower XP2440 +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr mii 4 , +.Xr netintro 4 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Ben Gray Aq Mt bgray@freebsd.org . diff --git a/static/openbsd/man4/sncodec.4 b/static/openbsd/man4/sncodec.4 new file mode 100644 index 00000000..d63f3a59 --- /dev/null +++ b/static/openbsd/man4/sncodec.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: sncodec.4,v 1.1 2023/02/03 13:28:51 kettenis Exp $ +.\" +.\" Copyright (c) 2023 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 3 2023 $ +.Dt SNCODEC 4 +.Os +.Sh NAME +.Nm sncodec +.Nd Texas Instruments TAS2764 digital amplifier +.Sh SYNOPSIS +.Cd "sncodec* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Texas Instruments TAS2764/SN012776 +digital amplifier. +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/softraid.4 b/static/openbsd/man4/softraid.4 new file mode 100644 index 00000000..78a352d3 --- /dev/null +++ b/static/openbsd/man4/softraid.4 @@ -0,0 +1,273 @@ +.\" $OpenBSD: softraid.4,v 1.56 2025/04/13 13:17:31 jmc Exp $ +.\" +.\" Copyright (c) 2007 Todd T. Fries +.\" Copyright (c) 2007 Marco Peereboom +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 13 2025 $ +.Dt SOFTRAID 4 +.Os +.Sh NAME +.Nm softraid +.Nd software RAID +.Sh SYNOPSIS +.Cd "softraid0 at root" +.Sh DESCRIPTION +The +.Nm +device emulates a Host Bus Adapter (HBA) that provides RAID and other I/O +related services. +The +.Nm +device provides a scaffold to implement more complex I/O transformation +disciplines. +For example, one can tie chunks together into a mirroring discipline. +There really is no limit on what type of discipline one can write as long +as it fits the SCSI model. +.Pp +.Nm +supports a number of +.Em disciplines . +A discipline is a collection of functions +that provides specific I/O functionality. +This includes I/O path, bring-up, failure recovery, and statistical +information gathering. +Essentially a discipline is a lower +level driver that provides the I/O transformation for the softraid +device. +.Pp +A +.Em volume +is a virtual disk device that is made up of a collection of chunks. +.Pp +A +.Em chunk +is a partition or storage area of fstype +.Dq RAID . +.Xr disklabel 8 +is used to alter the fstype. +.Pp +Currently +.Nm +supports the following disciplines: +.Bl -ohang -offset indent +.It RAID 0 +A +.Em striping +discipline. +It segments data over a number of chunks to increase performance. +RAID 0 does not provide for data loss (redundancy). +.It RAID 1 +A +.Em mirroring +discipline. +It copies data across more than one chunk to provide for data loss. +Read performance is increased, +though at the cost of write speed. +Unlike traditional RAID 1, +.Nm +supports the use of more than two chunks in a RAID 1 setup. +.It RAID 5 +A +.Em striping +discipline with +.Em floating parity +across all chunks. +It stripes data across chunks and provides parity to prevent data loss of +a single chunk failure. +Read performance is increased; +write performance does incur additional overhead. +.It CRYPTO +An +.Em encrypting +discipline. +It encrypts data on a single chunk to provide for data confidentiality. +CRYPTO does not provide redundancy. +.It CONCAT +A +.Em concatenating +discipline. +It writes data to each chunk in sequence to provide increased capacity. +CONCAT does not provide redundancy. +.It RAID 1C +A +.Em mirroring +and +.Em encrypting +discipline. +It encrypts data to provide for data confidentiality and copies the +encrypted data across more than one chunk to prevent data loss in +case of a chunk failure. +Unlike traditional RAID 1, +.Nm +supports the use of more than two chunks in a RAID 1C setup. +.El +.Pp +.Xr installboot 8 +may be used to install +.Xr boot 8 +in the boot storage area of the +.Nm +volume. +All chunks in the volume will then be bootable. +Boot support is currently limited to the CRYPTO, RAID 1, and RAID 1C disciplines +on the amd64, arm64, riscv64 and sparc64 platforms. +Boot support on i386 is limited to CRYPTO and RAID 1. +On sparc64, bootable chunks must be RAID partitions using the letter +.Sq a . +At the +.Xr boot 8 +prompt, softraid volumes have names beginning with +.Sq sr +and can be booted from like a normal disk device. +CRYPTO and 1C volumes will require a decryption passphrase or keydisk +at boot time. +.Pp +The status of +.Nm +volumes is reported via +.Xr sysctl 8 +such that it can be monitored by +.Xr sensorsd 8 . +Each volume has one fourth level node named +.Va hw.sensors.softraid0.drive Ns Ar N , +where +.Ar N +is a small integer indexing the volume. +The format of the volume status is: +.Pp +.D1 Ar value Po Ar device Pc , Ar status +.Pp +The +.Ar device +identifies the +.Nm +volume. +The following combinations of +.Ar value +and +.Ar status +can occur: +.Bl -tag -width Ds -offset indent +.It Sy online , OK +The volume is operating normally. +.It Sy degraded , WARNING +The volume as a whole is operational, but not all of its chunks are. +In many cases, using +.Xr bioctl 8 +.Fl R +to rebuild the failed chunk is advisable. +.It Sy rebuilding , WARNING +A rebuild operation was recently started and has not yet completed. +.It Sy failed , CRITICAL +The device is currently unable to process I/O. +.It Sy unknown , UNKNOWN +The status is unknown to the system. +.El +.Sh EXAMPLES +An example to create a 3 chunk RAID 1 from scratch is as follows: +.Pp +Initialize the partition tables of all disks: +.Bd -literal -offset indent +# fdisk -iy wd1 +# fdisk -iy wd2 +# fdisk -iy wd3 +.Ed +.Pp +Now create RAID partitions on all disks: +.Bd -literal -offset indent +# echo 'RAID *' | disklabel -wAT- wd1 +# echo 'RAID *' | disklabel -wAT- wd2 +# echo 'RAID *' | disklabel -wAT- wd3 +.Ed +.Pp +Assemble the RAID volume: +.Bd -literal -offset indent +# bioctl -c 1 -l /dev/wd1a,/dev/wd2a,/dev/wd3a softraid0 +.Ed +.Pp +The console will show what device was added to the system: +.Bd -literal -offset indent +scsibus0 at softraid0: 1 targets +sd0 at scsibus0 targ 0 lun 0: SCSI2 +sd0: 1MB, 0 cyl, 255 head, 63 sec, 512 bytes/sec, 3714 sec total +.Ed +.Pp +It is good practice to wipe the front of the disk before using it: +.Bd -literal -offset indent +# dd if=/dev/zero of=/dev/rsd0c bs=1m count=1 +.Ed +.Pp +Initialize the partition table and create a filesystem on the +new RAID volume: +.Bd -literal -offset indent +# fdisk -iy sd0 +# echo '/ *' | disklabel -wAT- sd0 +# newfs /dev/rsd0a +.Ed +.Pp +The RAID volume is now ready to be used as a normal disk device. +See +.Xr bioctl 8 +for more information on configuration of RAID sets. +.Pp +Install +.Xr boot 8 +on the RAID volume, writing boot loaders to all 3 chunks: +.Bd -literal -offset indent +# installboot sd0 +.Ed +.Pp +At the +.Xr boot 8 +prompt, load the /bsd kernel from the RAID volume: +.Bd -literal -offset indent +boot> boot sr0a:/bsd +.Ed +.Sh SEE ALSO +.Xr bio 4 , +.Xr bioctl 8 , +.Xr boot 8 , +.Xr boot_sparc64 8 , +.Xr disklabel 8 , +.Xr fdisk 8 , +.Xr installboot 8 , +.Xr newfs 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . +.Sh AUTHORS +.An Marco Peereboom . +.Sh CAVEATS +The driver relies on underlying hardware to properly fail chunks. +.Pp +The RAID 1 discipline does not initialize the mirror upon creation. +This is by design because all sectors that are read are written first. +There is no point in wasting a lot of time syncing random data. +.Pp +The RAID 5 discipline does not initialize parity upon creation, instead parity +is only updated upon write. +.Pp +Stacking disciplines (CRYPTO on top of RAID 5, for example) is not +supported at this time. +.Pp +Currently there is no automated mechanism to recover from failed disks. +.Pp +Certain RAID levels can protect against some data loss +due to component failure. +RAID is +.Em not +a substitute for good backup practices. diff --git a/static/openbsd/man4/spdmem.4 b/static/openbsd/man4/spdmem.4 new file mode 100644 index 00000000..5e0ccfb7 --- /dev/null +++ b/static/openbsd/man4/spdmem.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: spdmem.4,v 1.8 2021/05/01 16:11:09 visa Exp $ +.\" +.\" Copyright (c) 2007 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 1 2021 $ +.Dt SPDMEM 4 +.Os +.Sh NAME +.Nm spdmem +.Nd Serial Presence Detect memory +.Sh SYNOPSIS +.Cd "spdmem* at iic?" +.Pp +.Cd "# macppc" +.Cd "spdmem* at mem?" +.Sh DESCRIPTION +The +.Nm +driver retrieves information about memory modules from an +onboard EEPROM, standardised as JEDEC 21-C. +Currently +.Nm +is able to decode information relating to SDRAM and DDR/DDR2/DDR3 SDRAM. +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Nicolas Joly , +.An Paul Goyette , +and +.An Tobias Nygren +and ported to +.Ox +by +.An Jonathan Gray Aq Mt jsg@openbsd.org . diff --git a/static/openbsd/man4/speaker.4 b/static/openbsd/man4/speaker.4 new file mode 100644 index 00000000..89add7b3 --- /dev/null +++ b/static/openbsd/man4/speaker.4 @@ -0,0 +1,231 @@ +.\" $OpenBSD: speaker.4,v 1.12 2024/07/18 05:44:46 jmc Exp $ +.\" $NetBSD: speaker.4,v 1.9 1998/08/18 08:16:56 augustss Exp $ +.\" +.\" Copyright (c) 1993 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christopher G. Demetriou. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 18 2024 $ +.Dt SPKR 4 +.Os +.Sh NAME +.Nm speaker , +.Nm spkr +.Nd console speaker device driver +.Sh SYNOPSIS +.Cd "spkr0 at pcppi?" +.Sh DESCRIPTION +The +.Nm +device driver allows applications to control the built-in speaker on +machines providing a PCPPI speaker interface. +.Pp +Only one process may have this device open at any given time; +.Xr open 2 +and +.Xr close 2 +are used to lock and relinquish it. +An attempt to +.Fn open +when another process has the device locked will return \-1 with an +.Er EBUSY +error indication. +Writes to the device are interpreted as +.Dq play strings +in a simple ASCII melody notation. +An +.Fn ioctl +for tone generation at arbitrary frequencies is also supported. +.Pp +Sound-generation does +.Em not +monopolize the processor; in fact, the driver +spends most of its time sleeping while the PC hardware is emitting tones. +Other processes may emit beeps while the driver is running. +.Pp +Applications may call +.Fn ioctl +on a speaker file descriptor to control the speaker driver directly; +definitions for the +.Fn ioctl +interface are in +.In dev/isa/spkrio.h . +The +.Vt tone_t +structure used in these calls has two fields, +specifying a frequency (in Hz) and a duration (in 1/100ths of a second). +A frequency of zero is interpreted as a rest. +.Pp +At present there are two such ioctls. +The +.Dv SPKRTONE +ioctl accepts a pointer to a single tone structure as a third argument and +plays it. +The +.Dv SPKRTUNE +ioctl accepts a pointer to the first of an array of tone structures and plays +them in continuous sequence; this array must be terminated by a final member +with a zero duration. +.Pp +The play-string language is modelled on the PLAY statement conventions of +IBM BASIC 2.0. +The MB, MF and X primitives of PLAY are not useful in a UNIX environment and +are omitted. +The +.Dq octave-tracking +feature is also new. +.Pp +There are 84 accessible notes numbered 1-84 in 7 octaves, each running from +C to B, numbered 0-6; the scale is equal-tempered A440 and octave 3 starts +with middle C. +By default, the play function emits half-second notes with the last 1/16th +second being +.Dq rest time . +.Pp +Play strings are interpreted left to right as a series of play command groups; +letter case is ignored. +Play command groups are as follows: +.Bl -tag -width xxx +.It CDEFGAB +Letters A through G cause the corresponding note to be played in the current +octave. +A note letter may optionally be followed by an +.Dq accidental sign , +one of +.Ql # , +.Ql + , +or +.Ql - ; +the first two of these cause it to be sharped one half-tone, the last causes +it to be flatted one half-tone. +It may also be followed by a time value number and by sustain dots (see below). +Time values are interpreted as for the L command below. +.It O Aq Ar n +If +.Ar n +is numeric, this sets the current octave. +.Ar n +may also be one of +.Sq L +or +.Sq N +to enable or disable octave-tracking (it is disabled by default). +When octave-tracking is on, interpretation of a pair of letter notes will +change octaves if necessary in order to make the smallest possible jump between +notes. +Thus +.Qq olbc +will be played as +.Qq olb>c , +and +.Qq olcb +as +.Qq olc , +.Ql < , +and +.Ql O[0123456] . +.Bd -literal -offset indent +> -- bump the current octave up one. +< -- drop the current octave down one. +.Ed +.It N Aq Ar n +Play note +.Ar n , +.Ar n +being 1 to 84 or 0 for a rest of current time value. +May be followed by sustain dots. +.It L Aq Ar n +Sets the current time value for notes. +The default is L4, quarter notes. +The lowest possible value is 1; values up to 64 are accepted. +L1 sets whole notes, L2 sets half notes, L4 sets quarter notes, etc. +.It P Aq Ar n +Pause (rest), with +.Ar n +interpreted as for L. +May be followed by sustain dots. +May also be written +.Ql ~ . +.It T Aq Ar n +Sets the number of quarter notes per minute; default is 120. +Musical names for common tempi are: +.Bl -column "Description" "Larghissimo" "Beats per minute" -offset indent +.It Em "Description" Ta Em "Tempo" Ta Em "Beats per Minute" +.It "very slow" Ta Larghissimo Ta 40\(en60 +.It "very slow" Ta Largo Ta 40\(en60 +.It "very slow" Ta Larghetto Ta 60\(en66 +.It "very slow" Ta Grave Ta 60\(en66 +.It "very slow" Ta Lento Ta 60\(en66 +.It "slow" Ta Adagio Ta 66\(en76 +.It "slow" Ta Adagietto Ta 66\(en76 +.It "medium" Ta Andante Ta 76\(en108 +.It "medium" Ta Andantino Ta 76\(en108 +.It "fast" Ta Moderato Ta 108\(en120 +.It "fast" Ta Allegretto Ta 108\(en120 +.It "fast" Ta Allegro Ta 120\(en168 +.It "fast" Ta Vivace Ta 120\(en168 +.It "fast" Ta Veloce Ta 120\(en168 +.It "very fast" Ta Presto Ta 168\(en208 +.It "very fast" Ta Prestissimo Ta 168\(en208 +.El +.It M[LNS] +Set articulation. +MN (N for normal) is the default; the last 1/8th of the note's value is rest +time. +You can set ML for legato (no rest space) or MS (staccato) 1/4 rest space. +.El +.Pp +Notes (that is, CDEFGAB or N command character groups) may be followed by +sustain dots. +Each dot causes the note's value to be lengthened by one-half for each one. +Thus, a note dotted once is held for 3/2 of its undotted value; +dotted twice, it is held 9/4, and three times would give 27/8. +.Pp +Whitespace in play strings is simply skipped and may be used to separate +melody sections. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/speaker +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr pcppi 4 +.Sh AUTHORS +.An Eric S. Raymond Aq Mt esr@snark.thyrsus.com , +Feb 1990 +.Sh BUGS +Due to roundoff in the pitch tables and slop in the tone-generation and timer +hardware (neither of which was designed for precision), neither pitch accuracy +nor timings will be mathematically exact. +.Pp +There is no volume control. +.Pp +In play strings which are very long (longer than your system's physical I/O +blocks) note suffixes or numbers may occasionally be parsed incorrectly due +to crossing a block boundary. diff --git a/static/openbsd/man4/sppp.4 b/static/openbsd/man4/sppp.4 new file mode 100644 index 00000000..026e6603 --- /dev/null +++ b/static/openbsd/man4/sppp.4 @@ -0,0 +1,308 @@ +.\" $OpenBSD: sppp.4,v 1.28 2023/03/23 12:43:38 stsp Exp $ +.\" +.\" Copyright (c) 1997 Joerg Wunsch +.\" +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: March 23 2023 $ +.Dt SPPP 4 +.Os +.Sh NAME +.Nm sppp +.Nd PPP and Link Control Protocol +.Sh SYNOPSIS +.Cd "pseudo-device sppp" Op Ar count +.Sh DESCRIPTION +The +.Nm +network layer implements the state machine and Link Control +Protocol (LCP) of the +Point-to-Point Protocol (PPP) +as described in RFC 1661. +Note that this layer does not provide network interfaces of its own, it is +rather intended to be layered on +top of drivers providing a point-to-point connection that +wish to run a PPP stack over it. +The corresponding network interfaces have to be provided by these hardware +drivers. +.Pp +The +.Nm +layer provides three basic modes of operation. +The default mode, with no special flags set, is to create the +PPP connection (administrative +.Em Open +event to the LCP layer) as soon as the interface is taken up with the +.Xr ifconfig 8 +command. +Taking the interface down again will terminate the LCP layer +and thus all other layers on top. +The link will also terminate itself as soon as no Network Control Protocol +(NCP) is open anymore, indicating that the lower layers are no longer needed. +.Pp +Setting the link-level flag +.Cm link0 +with +.Xr ifconfig 8 +will cause the respective network interface to go into +.Em passive +mode. +This means the administrative +.Em Open +event to the LCP layer will be delayed until after the lower layers +signal an +.Em Up +event (rise of +.Dq carrier ) . +This can be used by the lower layers to support +a dial-in connection where the physical layer isn't available +immediately at startup, but only after some external event arrives. +Receipt of a +.Em Down +event from the lower layer will not take the interface completely down +in this case. +.Pp +Finally, setting the flag +.Cm link1 +will cause the interface to operate in +.Em dial-on-demand +mode. +This is also only useful if the lower layers support the notion +of a carrier (like with an ISDN line). +Upon configuring the respective interface, it will delay the administrative +.Em Open +event to the LCP layer until either an outbound network packet +arrives, or until the lower layers signal an +.Em Up +event, indicating an inbound connection. +As with passive mode, receipt of a +.Em Down +event (loss of carrier) will not automatically take the interface down, +thus it remains available for further connections. +.Pp +The +.Nm +layer supports the +.Em debug +interface flag, which can be set with +.Xr ifconfig 8 . +If this flag is set, the various control protocol packets being +exchanged as well as the option negotiation between both ends of the +link will be logged at level +.Dv LOG_DEBUG . +This can be helpful to examine configuration problems during the first +attempts to set up a new configuration. +Without this flag being set, only the major phase transitions will be +logged at level +.Dv LOG_INFO . +.Pp +It is possible to leave the local interface IP address open for +negotiation by setting it to 0.0.0.0. +This requires that the remote peer can correctly supply a value for it +based on the identity of the caller, or on the remote address supplied +by this side. +Due to the way the IPCP option negotiation works, this address is +supplied late during the negotiation, which could cause the remote peer +to make false assumptions. +.Pp +In a similar spirit the remote address can be set to a magical value in +the range 0.0.0.1 to 0.0.0.255, which means that we don't care what +address the remote side will use, as long as it is not 0.0.0.0. +This is useful if your ISP has several dial-in servers. +You can of course +.Ic route add +something or other 0.0.0.1 +and it will do exactly what you would want it to. +.Pp +Once a connection is established, +the device will send out a nameserver proposal, +which +.Xr resolvd 8 +can act on. +If during IPCP negotiation no DNS server options were exchanged, +the nameserver proposal will be empty. +.Pp +The PAP and CHAP authentication protocols, as described in RFCs 1334 +and 1994, respectively, are also implemented. +Their parameters are controlled by the +.Xr ifconfig 8 +utility. +.Sh EXAMPLES +Display the settings for pppoe0. +The interface is currently in the +.Em establish +phase and tries to connect to the remote peer; +other possible PPP phases are +.Em dead , +.Em authenticate , +.Em network , +or +.Em terminate . +Both ends of the connection use the CHAP protocol, the local client +tells the remote peer the system name +.Ql uriah , +and the peer is expected to authenticate by the name +.Ql ifb-gw . +Once the initial CHAP handshake has been successful, no further CHAP +challenges will be transmitted. +There are supposedly some known CHAP secrets for both ends of the link +which are not displayed. +.Bd -literal -offset indent +$ ifconfig pppoe0 +pppoe0: flags=8851 mtu 1492 + dev: em0 state: PADI sent + sid: 0x0 PADI retries: 0 PADR retries: 0 + sppp: phase establish authproto chap authname "uriah" \e + peerproto chap peername "ifb-gw" norechallenge + groups: pppoe + inet 0.0.0.0 --> 0.0.0.1 netmask 0xffffffff +.Ed +.Pp +A possible call to +.Xr ifconfig 8 +that could have been used to bring the interface into the state shown +by the previous example: +.Bd -literal -offset indent +# ifconfig em0 up +# ifconfig pppoe0 0.0.0.0 0.0.0.1 netmask 0xffffffff \e + pppoedev em0 \e + authproto chap authname uriah authkey "some secret" \e + peerproto chap peername "ifb-gw" peerkey "another" \e + peerflag norechallenge \e + up +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It : illegal in state +An event happened that should not happen for the current state +the respective control protocol is in. +See RFC 1661 for a description of the state automaton. +.It : loopback +The state automaton detected a line loopback (that is, it was talking +with itself). +The interface will be temporarily disabled. +.It : up +The LCP layer is running again, after a line loopback had previously +been detected. +.It : down +The keepalive facility detected the line being unresponsive. +Keepalive must be explicitly requested by the lower layers in order to +take place. +.El +.Sh SEE ALSO +.Xr inet 4 , +.Xr pppoe 4 , +.Xr ifconfig 8 +.Sh STANDARDS +.Rs +.%A G. McGregor +.%D May 1992 +.%R RFC 1332 +.%T The PPP Internet Protocol Control Protocol (IPCP) +.Re +.Pp +.Rs +.%A B. Lloyd +.%A W. Simpson +.%D October 1992 +.%R RFC 1334 +.%T PPP Authentication Protocols +.Re +.Pp +.Rs +.%A W. Simpson +.%D July 1994 +.%R RFC 1661 +.%T The Point-to-Point Protocol (PPP) +.Re +.Pp +.Rs +.%A S. Cobb +.%D December 1995 +.%R RFC 1877 +.%T PPP Internet Protocol Control Protocol Extensions for Name Server Addresses +.Re +.Pp +.Rs +.%A W. Simpson +.%D August 1996 +.%R RFC 1994 +.%T PPP Challenge Handshake Authentication Protocol (CHAP) +.Re +.Pp +.Rs +.%A S. Varada +.%A D. Haskins +.%A E. Allen +.%D September 2007 +.%R RFC 5072 +.%T IP Version 6 over PPP +.Re +.Sh AUTHORS +.An -nosplit +The original implementation of +.Nm +was written in 1994 at Cronyx Ltd., Moscow, by +.An Serge Vakulenko Aq Mt vak@cronyx.ru . +.An Joerg Wunsch Aq Mt joerg_wunsch@uriah.heep.sax.de +rewrote a large part in 1997 in order +to fully implement the state machine as described in RFC 1661, so it +could also be used for dialup lines. +He also wrote the initial version of this man page. +Serge later on wrote a basic implementation for PAP and CHAP, which +served as the base for the current implementation, done again by +Joerg Wunsch. +.Pp +.An Reyk Floeter +implemented +.Nm +support for +.Xr ifconfig 8 +in +.Ox 4.0 +in order to remove the original +.Ql spppcontrol +utility, which was previously used to configure and display the +.Nm +settings. +.Sh BUGS +Many. +.Pp +Negotiation loop avoidance is not fully implemented. +If the negotiation doesn't converge, this can cause an endless loop. +.Pp +The various parameters that should be adjustable per RFC 1661 are +currently hard-coded into the kernel, and should be made accessible +through +.Xr ifconfig 8 . +.Pp +.Em Passive +mode has not been tested extensively. +.Pp +More NCPs should be implemented, as well as other control protocols +for authentication and link quality reporting. +.Pp +IPCP should support VJ header compression. +.Pp +Link-level compression protocols should be supported. diff --git a/static/openbsd/man4/sqphy.4 b/static/openbsd/man4/sqphy.4 new file mode 100644 index 00000000..7c52ca47 --- /dev/null +++ b/static/openbsd/man4/sqphy.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: sqphy.4,v 1.12 2020/01/24 05:08:02 jsg Exp $ +.\" $NetBSD: sqphy.4,v 1.1 1998/11/04 05:53:59 thorpej Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 24 2020 $ +.Dt SQPHY 4 +.Os +.Sh NAME +.Nm sqphy +.Nd Seeq 80220/80221, 80223, 80225 and 84220 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "sqphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Seeq 80220/80221, 80223, 80225 and 84220 10/100 Ethernet +PHYs. +The 80223 is a 3.3 volt version of the 80221. +The 80225 is a stripped down version of the 80223. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/ssdfb.4 b/static/openbsd/man4/ssdfb.4 new file mode 100644 index 00000000..3e6b9588 --- /dev/null +++ b/static/openbsd/man4/ssdfb.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: ssdfb.4,v 1.3 2019/10/07 20:37:16 patrick Exp $ +.\" +.\" Copyright (c) 2019 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 7 2019 $ +.Dt SSDFB 4 +.Os +.Sh NAME +.Nm ssdfb +.Nd Solomon Systech SSD1306/SSD1309 OLED display module +.Sh SYNOPSIS +.Cd "ssdfb* at iic?" +.Cd "ssdfb* at spi?" +.Cd "wsdisplay* at ssdfb?" +.Sh DESCRIPTION +The +.Nm +driver supports OLED display modules based on the Solomon Systech SSD1306 or +SSD1309 chips. +The support for partial updates in both the chip and the driver improves the +display's responsiveness. +Due to the small resolution of about 128x64 the display makes most sense as a +text-based terminal. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/st.4 b/static/openbsd/man4/st.4 new file mode 100644 index 00000000..43159d35 --- /dev/null +++ b/static/openbsd/man4/st.4 @@ -0,0 +1,308 @@ +.\" $OpenBSD: st.4,v 1.22 2024/12/21 01:00:31 jsg Exp $ +.\" $NetBSD: st.4,v 1.2 1996/10/20 23:15:24 explorer Exp $ +.\" +.\" Copyright (c) 1996 +.\" Julian Elischer . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 21 2024 $ +.Dt ST 4 +.Os +.Sh NAME +.Nm st +.Nd SCSI tape driver +.Sh SYNOPSIS +.Cd "st* at scsibus?" +.Cd "#st0 at scsibus0 target 4 lun 0" Pq fixed-configuration example +.Sh DESCRIPTION +The +.Nm +driver provides support for +.Tn SCSI +tape drives. +.Pp +.Tn SCSI +devices have a relatively high level interface and talk to the system via a +.Tn SCSI +adapter and a +.Tn SCSI +adapter driver +e.g.\& +.Xr ahc 4 . +The +.Tn SCSI +adapter must be separately configured into the system before a +.Tn SCSI +tape can be configured. +.Pp +As the +.Tn SCSI +adapter is probed during boot, the +.Tn SCSI +bus is scanned for devices. +Any devices found which answer as +.Em Sequential +type devices will be attached to the +.Nm +driver. +.Sh MOUNT SESSIONS +The +.Nm +driver is based around the concept of a +.Em mount session , +which is defined as the period between the time that a tape is +mounted and the time when it is unmounted. +Any parameters set during a mount session remain in effect for the remainder +of the session or until replaced. +The tape can be unmounted, bringing the session to a close in several ways. +These include: +.Bl -enum +.It +Closing an +.Dq unmount device . +.It +Using the +.Dv MTOFFL +.Xr ioctl 2 +command, reachable through the +.Cm offline +command of +.Xr mt 1 . +.El +.Sh EJECT and REWIND +Bit 0 of the minor number specifies whether a rewind is attempted when the +device is closed. +When it is set, the device will not attempt a rewind on close +and the device will have an +.Sq n +in its name. +For example, +.Pa /dev/rst0 +will rewind on close but +.Pa /dev/nrst0 +will not. +.Pp +Bit 1 of the minor number specifies whether an eject is attempted when the +device is closed. +When it is set, the device will attempt to eject its media on close +and the device will have an +.Sq e +in its name. +For example, +.Pa /dev/erst0 +will eject its media on close but +.Pa /dev/rst0 +will not. +.Pp +If both bit 0 and bit 1 are set then an eject will +be attempted without a rewind and the device will have both an +.Sq e +and an +.Sq n +in its name. +For example, +.Pa /dev/enrst0 +will eject its media without first rewinding it on close. +.Pp +There is no guarantee that the attempted eject or rewind will be supported +by the actual hardware. +.Sh BLOCKING MODES +.Tn SCSI +tapes may run in either +.Em variable +or +.Em fixed +block-size modes. +Most +.Tn QIC Ns -type +devices run in fixed block-size mode, whereas most nine-track tapes +and many new cartridge formats allow variable block-size. +The difference between the two is as follows: +.Bl -inset +.It Variable block-size: +Each write made to the device results in a single logical record +written to the tape. +One can never read or write +.Em part +of a record from tape (though you may request a larger block and +read a smaller record); nor can one read multiple blocks. +Data from a single write is therefore read by a single read. +The block size used may be any value supported by the device, the +.Tn SCSI +adapter and the system (usually between 1 byte and 64 Kbytes, +sometimes more). +.Pp +When reading a variable record/block from the tape, the head is +logically considered to be immediately after the last item read, +and before the next item after that. +If the next item is a file mark, but it was never read, then the next +process to read will immediately hit the file mark and receive an +end-of-file notification. +.It Fixed block-size +data written by the user is passed to the tape as a succession of +fixed size blocks. +It may be contiguous in memory, but it is considered to be a series of +independent blocks. +One may never write an amount of data that is not an exact multiple of the +blocksize. +One may read and write the same data as a different set of records. +In other words, blocks that were written together may be read separately, +and vice-versa. +.Pp +If one requests more blocks than remain in the file, the drive will +encounter the file mark. +Because there is some data to return (unless there were no records before +the file mark), the read will succeed, returning that data. +The next read will return immediately with an +.Dv EOF . +(As above, if the file mark is never read, it remains for the next process +to read if in no-rewind mode.) +.El +.Sh FILE MARK HANDLING +The handling of file marks on write is automatic. +If the user has written to the tape, and has not done a read since the last +write, then a file mark will be written to the tape when the device is closed. +If a rewind is requested after a write, then the driver +assumes that the last file on the tape has been written, and ensures +that there are two file marks written to the tape. +The exception to this is that there seems to be a standard (which we follow, +but don't understand why) that certain types of tape do not actually +write two file marks to tape, but when read, report a +.Dq phantom +file mark when the last file is read. +These devices include the QIC family of devices. +(It might be that this set of devices is the same set as that of fixed. +This has not yet been determined, and they are treated as separate +behaviors by the driver at this time.) +.Sh IOCTLS +The following +.Xr ioctl 2 +calls apply to +.Tn SCSI +tapes. +Some also apply to other tapes. +They are defined in the header file +.In sys/mtio.h . +.\" +.\" Almost all of this discussion belongs in a separate mt(4) +.\" manual page, since it is common to all magnetic tapes. +.\" +.Bl -tag -width MTIOCEEOT +.It Dv MTIOCGET Fa "struct mtget *" +Retrieve the status and parameters of the tape. +.It Dv MTIOCTOP "struct mtop *" +Perform a multiplexed operation. +The argument structure is as follows: +.Bd -literal -offset indent +struct mtop { + short mt_op; + int mt_count; +}; +.Ed +.Pp +The following operation values are defined for +.Va mt_op : +.Bl -tag -width MTSELDNSTY +.It Dv MTWEOF +Write +.Va mt_count +end of file marks at the present head position. +.It Dv MTFSF +Skip over +.Va mt_count +file marks. +Leave the head on the EOM side of the last skipped file mark. +.It Dv MTBSF +Skip +.Em backwards +over +.Va mt_count +file marks. +Leave the head on the BOM (beginning of media) side of the last skipped +file mark. +.It Dv MTFSR +Skip forwards over +.Va mt_count +records. +.It Dv MTBSR +Skip backwards over +.Va mt_count +records. +.It Dv MTREW +Rewind the device to the beginning of the media. +.It Dv MTOFFL +Rewind the media (and, if possible, eject). +Even if the device cannot eject the media, it will often no longer respond +to normal requests. +.It Dv MTNOP +No-op; set status only. +.It Dv MTCACHE +Enable controller buffering. +.It Dv MTNOCACHE +Disable controller buffering. +.It Dv MTSETBSIZ +Set the blocksize to use for the device/mode. +If the device is capable of variable blocksize operation, and the blocksize +is set to 0, then the drive will be driven in variable mode. +This parameter is in effect for the present mount session only. +.It Dv MTSETDNSTY +Set the density value (see +.Xr mt 1 ) +to use when running in the mode opened (minor bits 2 and 3). +This parameter is in effect for the present +mount session only. +.El +.It Dv MTIOCIEOT +Set end-of-tape processing (not presently supported for +.Nm +devices). +.It Dv MTIOCEEOT +Set end-of-tape processing (not presently supported for +.Nm +devices). +.El +.Sh FILES +.Bl -tag -width /dev/[e][n][r]st[0-9] -compact +.It Pa /dev/[e][n][r]st[0-9] +General form. +.It Pa /dev/rst0 +No eject, rewind on close. +.It Pa /dev/nrst0 +No eject, no rewind on close. +.It Pa /dev/erst0 +Eject, rewind on close. +.It Pa /dev/enrst0 +Eject, no rewind on close. +.El +.Sh SEE ALSO +.Xr chio 1 , +.Xr mt 1 , +.Xr intro 4 , +.Xr mtio 4 , +.Xr scsi 4 +.Sh HISTORY +.An Julian Elischer +wrote +.Nm +for Mach 2.5 and ported it to 386BSD. diff --git a/static/openbsd/man4/ste.4 b/static/openbsd/man4/ste.4 new file mode 100644 index 00000000..56dd4b72 --- /dev/null +++ b/static/openbsd/man4/ste.4 @@ -0,0 +1,154 @@ +.\" $OpenBSD: ste.4,v 1.27 2022/02/17 12:24:08 jsg Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/ste.4,v 1.3 1999/11/15 23:14:27 phantom Exp $ +.\" +.Dd $Mdocdate: February 17 2022 $ +.Dt STE 4 +.Os +.Sh NAME +.Nm ste +.Nd Sundance Technologies ST201 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "ste* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI Ethernet adapters and embedded +controllers based on the Sundance Technologies ST201 PCI Fast +Ethernet controller chip. +This includes: +.Pp +.Bl -bullet -offset indent -compact +.It +D-Link DFE-550TX +.It +D-Link DFE-580TX +.It +Encore ENL832-TX-ICNT 10/100 M PCI +.El +.Pp +The Sundance ST201 uses bus master DMA and is designed to be a +3Com EtherLink XL work-alike. +It uses the same DMA descriptor structure and is very similar in operation, +however its register layout is different. +The ST201 has a 64-bit multicast hash filter and a single perfect filter +entry for the station address. +It supports both 10 and 100Mbps speeds in either full or half duplex +using an MII transceiver. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation. +.It half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "ste0: couldn't map ports/memory" +A fatal initialization error has occurred. +.It "ste0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "ste0: watchdog timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.It "ste0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.It "ste0: no memory for tx list" +The driver failed to allocate an mbuf for the transmitter ring when +allocating a pad buffer or collapsing an mbuf chain into a cluster. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T Sundance ST201 data sheet +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 3.0 . +.Ox +support was added in +.Ox 2.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ee.columbia.edu +and ported to +.Ox +by +.An Aaron Campbell Aq Mt aaron@openbsd.org . diff --git a/static/openbsd/man4/stge.4 b/static/openbsd/man4/stge.4 new file mode 100644 index 00000000..49976dba --- /dev/null +++ b/static/openbsd/man4/stge.4 @@ -0,0 +1,90 @@ +.\" $OpenBSD: stge.4,v 1.22 2021/09/08 20:29:21 jmc Exp $ +.\" $NetBSD: stge.4,v 1.5 2001/09/11 22:52:54 wiz Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt STGE 4 +.Os +.Sh NAME +.Nm stge +.Nd Sundance/Tamarack TC9021 1Gb Ethernet device +.Sh SYNOPSIS +.Cd "stge* at pci?" +.Cd "eephy* at mii?" +.Cd "gentbi* at mii?" +.Cd "ipgphy* at mii?" +.Sh DESCRIPTION +The +.Nm +device driver supports the Sundance/Tamarack TC9021 Gigabit Ethernet +chip. +.Pp +The Sundance/Tamarack TC9021 chip is found on adapters such as the +following: +.Pp +.Bl -bullet -compact +.It +Allied Telesis CentreCOM LA1000-PCI-T +.It +Antares Microsystems TC9021 +.It +Asus NX1101 +.It +D-Link DGE-550T +.El +.Pp +It uses an external PHY or an external 10-bit interface. +.Pp +The +.Nm +driver supports +IPv4 receive IP/TCP/UDP checksum offload and +VLAN tag insertion and stripping. +.Sh SEE ALSO +.Xr arp 4 , +.Xr eephy 4 , +.Xr gentbi 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr ipgphy 4 , +.Xr mii 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Jason R. Thorpe Aq Mt thorpej@netbsd.org . diff --git a/static/openbsd/man4/sti.4 b/static/openbsd/man4/sti.4 new file mode 100644 index 00000000..c00df6b1 --- /dev/null +++ b/static/openbsd/man4/sti.4 @@ -0,0 +1,275 @@ +.\" $OpenBSD: sti.4,v 1.27 2024/08/20 05:52:04 jsg Exp $ +.\" +.\" Copyright (c) 2001 Michael Shalayeff +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR OR HIS RELATIVES BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF MIND, USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING +.\" IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 20 2024 $ +.Dt STI 4 +.Os +.Sh NAME +.Nm sti +.Nd HP Standard Text Interface +.Sh SYNOPSIS +.Cd "sti* at mainbus0" +.Cd "sti* at pci?" +.Cd "sti* at phantomas0" +.Cd "wsdisplay* at sti?" +.Sh DESCRIPTION +The +.Nm +was created by HP to provide uniform frame-buffer access operations +for their 9000/300 and 9000/700 series of workstations. +.Pp +The following models are supported +(though not all features or frame buffer depths may be available): +.Bl -column "Visualize FX4/FX6" "Bits" "Mem" "3D" "Machines/Cards" -offset left +.It Sy "Model" Ta Sy "Bits" Ta Sy "Mem" Ta Sy "3D" Ta Sy "Machines/Cards" +.It "VRX" Ta 8 Ta "2" Ta "" Ta "HP9000/362/382" +.It "EVRX" Ta "8" Ta "2" Ta "" Ta "HP9000/425e" +.It "Timber" Ta "8" Ta "2" Ta "" Ta "HP9000/705/710" +.It "GRX" Ta "8g" Ta "2" Ta "" Ta "SGC" +.It "CRX" Ta "8" Ta "2" Ta "" Ta "SGC" +.It "Tomcat" Ta "8" Ta "2" Ta "" Ta "SGC" +.It "Stinger" Ta "8" Ta "2" Ta "" Ta "HP9000/7[12]5/74[257]i" +.It "Artist" Ta "8" Ta "2" Ta "" Ta "HP9000/712/7[12]5/74[38]i" +.It "CRX-24" Ta "24" Ta "16" Ta "" Ta "SGC" +.\" .It "CRX-24Z" Ta "24" Ta "16" Ta "y" Ta "SGC" +.\" .It "CRX-48Z" Ta "24" Ta "16" Ta "y" Ta "SGC/GSC" +.It "HCRX-8" Ta "8" Ta "2" Ta "" Ta "GSC" +.\" .It "HCRX-8Z" Ta "8" Ta "2" Ta "y" Ta "GSC" +.It "HCRX-24" Ta "24" Ta "16" Ta "" Ta "GSC" +.\" .It "HCRX-24Z" Ta "24" Ta "16" Ta "y" Ta "GSC" +.\" .It "Visualize 8" Ta "8" Ta "2" Ta "y" Ta "GSC" +.It "Visualize EG" Ta "16" Ta "2" Ta "" Ta "HP B/C-class, GSC/PCI" +.\" .It "Visualize 24" Ta "24" Ta "16" Ta "y" Ta "GSC" +.\" .It "Visualize 48" Ta "24" Ta "16" Ta "y" Ta "GSC" +.\" .It "Visualize 48XP" Ta "24" Ta "16" Ta "y" Ta "GSC" +.It "Visualize FXe" Ta "24" Ta "24" Ta "y" Ta "PCI 32/66" +.It "Visualize FX2" Ta "24" Ta "24" Ta "y" Ta "PCI 64/66" +.It "Visualize FX4/FX6" Ta "24" Ta "32" Ta "y" Ta "PCI 64/66" +.\" .It "Visualize FX5pro" Ta "24" Ta "64" Ta "y" Ta "PCI 64/66" +.\" .It "Visualize FX10pro" Ta "24" Ta "128" Ta "y" Ta "PCI 64/66" +.El +.Pp +Implementation consists of a set of functions burnt in to the PROM +on the card and providing the following set of functions (see below +for PROM revision history on functions supported by particular PROM +revision): +.Pp +.Bl -bullet -compact +.It +Initialize graphics. +.It +State management. +.It +Print a character onto the screen using currently selected font. +.It +Copy a region of the frame-buffer to another location. +.It +Self testing. +.It +Exception handling. +.It +Frame-buffer configuration enquiry. +.It +Setting colour-map entry. +.It +DMA parameters. +.It +Flow control. +.It +User timing. +.It +Processing management. +.It +Miscellaneous utility functions. +.El +.Pp +There are two modes for accessing the PROM: +.Dq byte +and +.Dq word +mode. +In +.Dq byte +mode each 4-byte word contains only the low-ordered big-endian +byte of data; i.e., to compose one word of data 4 words should be read +and low-ordered bytes of those should be shifted correspondingly. +In +.Dq word +mode each word contains all 4 bytes of valid data. +.Pp +PROM revision history: +.Bl -tag -width "00.00" -compact +.It 8.02 +Original release. +.It 8.03 +.Bl -bullet -compact +.It +OSF-extended self test (a.k.a fast). +.It +Restore display. +.El +.It 8.04 +.Bl -bullet -compact +.\" global cfg +.\" rename global cfg ext +.\" global cfg ext +.It +Implement +.Nm curr_mon +function. +.It +Graphical boot screen. +.\" sti_mem_addr +.\" dd +.\" num mons +.\" mon tbl +.\" user data +.\" sti mem req +.\" user data size +.\" maxtime +.\" mon tbl desc struct +.\" init_inptr +.\" rename init_inptr_ext +.\" init_inptr_ext +.\" config mon type +.\" cmt change +.\" font unpmv +.\" non text +.It +Implement +.Dq block move . +.\" non-text +.It +Implement +.Dq set colour-map entry . +.It +Implement word mode. +.It +Support for multiple monitors. +.It +Support +.Nm user_data +.Nm +space usage. +.It +Support for extra memory. +.It +Support for +.Nm Windows NT (tm) . +.It +Monitor frequency reference. +.It +Early console. +.It +Support added for: PCXL, +.Nm GSC +bus, ROM-less operation. +.El +.It 8.05 +.Bl -bullet -compact +.It +Interrupt support. +.It +Report card's power usage. +.It +Birds of Prey. +.It +User interrupts. +.El +.It 8.06 +.Bl -bullet -compact +.It +Multiple fonts. +.It +Monitor table descriptor strings. +.It +PCXL2 and PCXU monitor descriptors. +.El +.It 8.08 +.Bl -bullet -compact +.It +HP-UX 10 support for Visualize FX +.It +.Nm dma_ctrl +function added. +.It +.Nm flow_ctrl +function added. +.It +.Nm user_timing +function added. +.El +.It 8.09 +.Bl -bullet -compact +.It +Addition changes for +.Nm Visualize FX +due to rearchitecture for performance. +.It +.Nm process_mgr +function added. +.El +.It 8.10 +PCXL2 and PCXU dual +.Nm PCI +EPROM map mode, implemented on +.Nm Visualize EG . +.It 8.11 +Support for HP-UX non-implicit locking DMA, implemented on +.Nm Visualize FXe . +.It 8.12 +.Nm sti_util +function added (flashing under HP-UX and other sideband traffic). +.It 8.13 +Colour frame buffer support. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr phantomas 4 , +.Xr wsdisplay 4 +.Pp +.Rs +.%T Standard Text Interface For Graphics Devices +.%N Revision 8.13 +.%D March 1, 2000 +.%I Hewlett-Packard +.Re +.Sh HISTORY +The +.Nm +driver was written by +.An Michael Shalayeff Aq Mt mickey@openbsd.org +for HPPA +port for +.Ox 2.7 . +.\" .Pp +.\" .Xr pci 4 +.\" attachment code was written by +.\" .An Miod Vallat . +.Sh BUGS +Currently, neither scroll back nor screen blanking functions +are implemented. diff --git a/static/openbsd/man4/stp.4 b/static/openbsd/man4/stp.4 new file mode 100644 index 00000000..6745c5da --- /dev/null +++ b/static/openbsd/man4/stp.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: stp.4,v 1.11 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: nell.4,v 1.2 2002/03/29 16:23:50 wiz Exp $ +.\" +.\" Copyright (c) 2002 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Martin Husemann . +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt STP 4 +.Os +.Sh NAME +.Nm stp +.Nd SBus PCMCIA bridge +.Sh SYNOPSIS +.Cd "stp* at sbus?" +.Cd "pcmcia* at stp?" +.Sh DESCRIPTION +The +.Nm +is a +.Xr pcmcia 4 +bridge for +.Xr sbus 4 . +It uses the STP4020 chipset and it is SUN part number 501-2367. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pcmcia 4 , +.Xr sbus 4 diff --git a/static/openbsd/man4/sv.4 b/static/openbsd/man4/sv.4 new file mode 100644 index 00000000..04fa016c --- /dev/null +++ b/static/openbsd/man4/sv.4 @@ -0,0 +1,73 @@ +.\" $OpenBSD: sv.4,v 1.16 2009/11/02 22:31:50 sobrado Exp $ +.\" +.\" Copyright (c) 1998 Constantine Paul Sapuntzakis +.\" All rights reserved +.\" +.\" Author: Constantine Paul Sapuntzakis (csapuntz@cvs.openbsd.org) +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The author's name or those of the contributors may not be used to +.\" endorse or promote products derived from this software without +.\" specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 2 2009 $ +.Dt SV 4 +.Os +.Sh NAME +.Nm sv +.Nd S3 SonicVibes audio device +.Sh SYNOPSIS +.Cd "sv* at pci?" +.Cd "audio* at sv?" +.Sh DESCRIPTION +The +.Nm +driver provides support for S3 SonicVibes (S3-617) chipset-based +cards. +Disabling the SRS 3-D spatial feature of the chip is recommended for higher +quality audio. +This can be done in software by issuing the following command: +.Bd -literal -offset indent +$ mixerctl outputs.spatial=off +.Ed +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +This driver is based on the +.Xr eap 4 +driver by Lennart Augustsson. +The +.Nm +device driver first appeared in +.Ox 2.6 . +.Sh BUGS +The "FM" DAC, wavetable synth, and MIDI port are not +supported. +Recording at a rate different from playback is supported by +the chip but not the driver. +The mixer does not allow control of reverb, digital loopback, or 3-D SRS +features. +The chip does not support exact record speeds (it seems) of 11025Hz, +22050Hz, and so on, used by Windows audio. +Usually, the actual record is rate is around +/- 50Hz of the specified. diff --git a/static/openbsd/man4/sxiccmu.4 b/static/openbsd/man4/sxiccmu.4 new file mode 100644 index 00000000..691bc413 --- /dev/null +++ b/static/openbsd/man4/sxiccmu.4 @@ -0,0 +1,35 @@ +.\" $OpenBSD: sxiccmu.4,v 1.2 2019/02/01 01:26:50 jsg Exp $ +.\" +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 1 2019 $ +.Dt SXICCMU 4 +.Os +.Sh NAME +.Nm sxiccmu +.Nd Allwinner clock control module device +.Sh SYNOPSIS +.Cd "sxiccmu* at fdt? early 1" +.Sh DESCRIPTION +The +.Nm +driver provides support for the clock control module device integrated in +Allwinner Technology A10, A10s, A20, A23, A33, A64, A80, H3, H5, R40 and V40 +SoCs. +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.5 . diff --git a/static/openbsd/man4/sxidog.4 b/static/openbsd/man4/sxidog.4 new file mode 100644 index 00000000..5f901811 --- /dev/null +++ b/static/openbsd/man4/sxidog.4 @@ -0,0 +1,34 @@ +.\" $OpenBSD: sxidog.4,v 1.1 2019/10/16 22:24:45 kettenis Exp $ +.\" +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 16 2019 $ +.Dt SXIDOG 4 +.Os +.Sh NAME +.Nm sxidog +.Nd A1X/A20 watchdog timer device +.Sh SYNOPSIS +.Cd "sxidog* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the watchdog timer device integrated in Allwinner +Technology A1X/A20 SoCs. +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.5 . diff --git a/static/openbsd/man4/sximmc.4 b/static/openbsd/man4/sximmc.4 new file mode 100644 index 00000000..b6db373b --- /dev/null +++ b/static/openbsd/man4/sximmc.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: sximmc.4,v 1.3 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2016 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt SXIMMC 4 +.Os +.Sh NAME +.Nm sximmc +.Nd SD/MMC controller +.Sh SYNOPSIS +.Cd "sximmc* at fdt?" +.Cd "sdmmc* at sximmc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the MMC/SD/SDIO controller integrated on +Allwinner A1X/A20 SoCs. +.Pp +The +.Xr sdmmc 4 +subsystem performs SD/MMC transactions to communicate with +MMC, SD, SDHC, or SDIO devices inserted into the SD slot. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sdmmc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared D. McNeill +for +.Nx +and ported to +.Ox +by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/sxipio.4 b/static/openbsd/man4/sxipio.4 new file mode 100644 index 00000000..277a3ec2 --- /dev/null +++ b/static/openbsd/man4/sxipio.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: sxipio.4,v 1.1 2018/03/31 03:22:34 jsg Exp $ +.\" +.\" Copyright (c) 2014 Raphael Graf +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2018 $ +.Dt SXIPIO 4 +.Os +.Sh NAME +.Nm sxipio +.Nd Allwinner GPIO controller +.Sh SYNOPSIS +.Cd "sxipio* at fdt? early 1" +.Cd "gpio* at sxipio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the GPIO controller integrated in Allwinner +Technology A10, A10s, A13, A20, A23, A33, A64, A80, GR8, H3, H5 and R40 SoCs. +The devices have several ports for multi-functional pins which can be configured +as either inputs or outputs, and accessed using +.Xr gpioctl 8 . +.\" Both values are made available through the +.\" .Xr sysctl 8 +.\" interface. +.Sh SEE ALSO +.Xr gpio 4 , +.Xr gpioctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . diff --git a/static/openbsd/man4/sxipwm.4 b/static/openbsd/man4/sxipwm.4 new file mode 100644 index 00000000..c8b5d815 --- /dev/null +++ b/static/openbsd/man4/sxipwm.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: sxipwm.4,v 1.2 2019/12/03 09:34:53 patrick Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 3 2019 $ +.Dt SXIPWM 4 +.Os +.Sh NAME +.Nm sxipwm +.Nd Allwinner PWM controller +.Sh SYNOPSIS +.Cd "sxipwm* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the PWM controllers integrated on various +Allwinner SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Krystian Lewandowski . diff --git a/static/openbsd/man4/sxirintc.4 b/static/openbsd/man4/sxirintc.4 new file mode 100644 index 00000000..9fdba3f5 --- /dev/null +++ b/static/openbsd/man4/sxirintc.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: sxirintc.4,v 1.1 2022/09/12 17:30:32 kettenis Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 12 2022 $ +.Dt SXIRINTC 4 +.Os +.Sh NAME +.Nm sxirintc +.Nd Allwinner wakeup interrupt controller +.Sh SYNOPSIS +.Cd "sxirintc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the wakeup interrupt controller +integrated on Allwinner A23/A31/A33/A64/A83T/H3/H5 SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/sxirsb.4 b/static/openbsd/man4/sxirsb.4 new file mode 100644 index 00000000..ee1a33a6 --- /dev/null +++ b/static/openbsd/man4/sxirsb.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: sxirsb.4,v 1.2 2017/12/16 18:28:16 jmc Exp $ +.\" +.\" Copyright (c) 2017 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 16 2017 $ +.Dt SXIRSB 4 +.Os +.Sh NAME +.Nm sxirsb +.Nd Allwinner Reduced Serial Bus controller +.Sh SYNOPSIS +.Cd "sxirsb* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Reduced Serial Bus (RSB) controller +integrated on Allwinner A23/A33/A64/A80/A83T SoCs. +RSB is a two-wire bus developed by X-Powers as a high-speed +alternative to I2C for connecting integrated circuits. +It is typically used for connecting devices such as power management +ICs and audio codecs. +.Sh SEE ALSO +.Xr acrtc 4 , +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/sxirtc.4 b/static/openbsd/man4/sxirtc.4 new file mode 100644 index 00000000..076b7b04 --- /dev/null +++ b/static/openbsd/man4/sxirtc.4 @@ -0,0 +1,35 @@ +.\" $OpenBSD: sxirtc.4,v 1.2 2018/06/18 06:06:52 jmc Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 18 2018 $ +.Dt SXIRTC 4 +.Os +.Sh NAME +.Nm sxirtc +.Nd Allwinner real-time clock +.Sh SYNOPSIS +.Cd "sxirtc* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the real-time clock found in Allwinner SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . diff --git a/static/openbsd/man4/sxisid.4 b/static/openbsd/man4/sxisid.4 new file mode 100644 index 00000000..8bce6089 --- /dev/null +++ b/static/openbsd/man4/sxisid.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: sxisid.4,v 1.3 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt SXISID 4 +.Os +.Sh NAME +.Nm sxisid +.Nd Allwinner security ID +.Sh SYNOPSIS +.Cd "sxisid* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for reading the on-chip eFuses integrated on +various Allwinner SoCs. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Krystian Lewandowski +and +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/sxisyscon.4 b/static/openbsd/man4/sxisyscon.4 new file mode 100644 index 00000000..68b71c39 --- /dev/null +++ b/static/openbsd/man4/sxisyscon.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: sxisyscon.4,v 1.1 2019/08/11 11:23:32 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 11 2019 $ +.Dt SXISYSCON 4 +.Os +.Sh NAME +.Nm sxisyscon +.Nd System controller +.Sh SYNOPSIS +.Cd "sxisyscon* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides access to a set of miscellaneous hardware registers to +other device drivers. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/sxitemp.4 b/static/openbsd/man4/sxitemp.4 new file mode 100644 index 00000000..1ffc5789 --- /dev/null +++ b/static/openbsd/man4/sxitemp.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: sxitemp.4,v 1.4 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2017 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt SXITEMP 4 +.Os +.Sh NAME +.Nm sxitemp +.Nd Allwinner temperature monitor +.Sh SYNOPSIS +.Cd "sxitemp* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the temperature sensors found on the +Allwinner A64, H3, H5 and R40/V40 SoCs. +.Pp +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/sxitwi.4 b/static/openbsd/man4/sxitwi.4 new file mode 100644 index 00000000..08809c29 --- /dev/null +++ b/static/openbsd/man4/sxitwi.4 @@ -0,0 +1,38 @@ +.\" $OpenBSD: sxitwi.4,v 1.1 2018/03/31 08:07:42 jsg Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2018 $ +.Dt SXITWI 4 +.Os +.Sh NAME +.Nm sxitwi +.Nd Allwinner Two Wire Interface +.Sh SYNOPSIS +.Cd "sxitwi* at fdt?" +.Cd "iic* at sxitwi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the I2C compatible Two Wire Interface +integrated in various Allwinner processors. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.3 . diff --git a/static/openbsd/man4/sym.4 b/static/openbsd/man4/sym.4 new file mode 100644 index 00000000..c3922ee8 --- /dev/null +++ b/static/openbsd/man4/sym.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: sym.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2011 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt SYM 4 +.Os +.Sh NAME +.Nm sym +.Nd symmetric access SCSI devices +.Sh SYNOPSIS +.Cd "sym* at scsibus?" +.Sh DESCRIPTION +The +.Nm +driver attaches to SCSI logical units that support symmetric access, +i.e. all paths to the device are as good as each other. +Each path attached to by +.Nm +is presented to +.Xr mpath 4 +which uses it as a backend to the logical unit attached to its own +.Xr scsibus 4 . +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr intro 4 , +.Xr mpath 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.0 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/sypwr.4 b/static/openbsd/man4/sypwr.4 new file mode 100644 index 00000000..31902912 --- /dev/null +++ b/static/openbsd/man4/sypwr.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: sypwr.4,v 1.2 2018/03/31 09:44:35 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 31 2018 $ +.Dt SYPWR 4 +.Os +.Sh NAME +.Nm sypwr +.Nd Silergy SY8106A voltage regulator +.Sh SYNOPSIS +.Cd "sypwr* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Silergy SY8106A voltage regulator. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/syscon.4 b/static/openbsd/man4/syscon.4 new file mode 100644 index 00000000..82e629f8 --- /dev/null +++ b/static/openbsd/man4/syscon.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: syscon.4,v 1.2 2018/04/01 12:05:03 kettenis Exp $ +.\" +.\" Copyright (c) 2018 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 1 2018 $ +.Dt SYSCON 4 +.Os +.Sh NAME +.Nm syscon +.Nd System controller +.Sh SYNOPSIS +.Cd "syscon* at fdt?" +.Sh DESCRIPTION +The +.Nm +driver provides access to a set of miscellaneous hardware registers to +other device drivers. +The driver may also provide system reset and power off functionality +if such functionality is provided through hardware registers in such a +set. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/tascodec.4 b/static/openbsd/man4/tascodec.4 new file mode 100644 index 00000000..611d5570 --- /dev/null +++ b/static/openbsd/man4/tascodec.4 @@ -0,0 +1,42 @@ +.\" $OpenBSD: tascodec.4,v 1.1 2022/08/06 12:00:18 kettenis Exp $ +.\" +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 6 2022 $ +.Dt TASCODEC 4 +.Os +.Sh NAME +.Nm tascodec +.Nd Texas Instruments TAS2770 digital amplifier +.Sh SYNOPSIS +.Cd "tascodec* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Texas Instruments TAS2770/TAS5770 +digital amplifier. +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/tcic.4 b/static/openbsd/man4/tcic.4 new file mode 100644 index 00000000..96c5a955 --- /dev/null +++ b/static/openbsd/man4/tcic.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: tcic.4,v 1.7 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: tcic.4,v 1.1 2000/02/12 11:14:14 fair Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt TCIC 4 +.Os +.Sh NAME +.Nm tcic +.Nd Databook PCMCIA controller driver +.Sh SYNOPSIS +.Cd "tcic0 at isa? port 0x240 iomem 0xd0000 iosiz 0x4000" +.Cd "pcmcia* at tcic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Tn Databook +DB86082, DB86084, DB86184, and DB86072 +.Tn PCMCIA +controllers. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr pcmcia 4 +.Sh HISTORY +The +.Nm +driver appeared in +.Nx 1.4 . +.Ox +support first appeared in +.Ox 2.8 . diff --git a/static/openbsd/man4/tcp.4 b/static/openbsd/man4/tcp.4 new file mode 100644 index 00000000..aee8d4ce --- /dev/null +++ b/static/openbsd/man4/tcp.4 @@ -0,0 +1,251 @@ +.\" $OpenBSD: tcp.4,v 1.28 2024/12/01 08:11:14 pascal Exp $ +.\" $NetBSD: tcp.4,v 1.3 1994/11/30 16:22:35 jtc Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)tcp.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: December 1 2024 $ +.Dt TCP 4 +.Os +.Sh NAME +.Nm tcp +.Nd Internet Transmission Control Protocol +.Sh SYNOPSIS +.In sys/socket.h +.In netinet/in.h +.In netinet/tcp.h +.Ft int +.Fn socket AF_INET SOCK_STREAM 0 +.Ft int +.Fn socket AF_INET6 SOCK_STREAM 0 +.Sh DESCRIPTION +The +.Tn TCP +protocol provides a reliable, flow-controlled, two-way +transmission of data. +It is a byte-stream protocol used to support the +.Dv SOCK_STREAM +abstraction. +TCP uses the standard +Internet address format and, in addition, provides a per-host +collection of +.Dq port addresses . +Thus, each address is composed +of an Internet address specifying the host and network, with +a specific +.Tn TCP +port on the host identifying the peer entity. +.Pp +Sockets utilizing the TCP protocol are either +.Dq active +or +.Dq passive . +Active sockets initiate connections to passive +sockets. +By default +.Tn TCP +sockets are created active; to create a +passive socket the +.Xr listen 2 +system call must be used +after binding the socket with the +.Xr bind 2 +system call. +Only passive sockets may use the +.Xr accept 2 +call to accept incoming connections. +Only active sockets may use the +.Xr connect 2 +call to initiate connections. +.Pp +Passive sockets may +.Dq underspecify +their location to match +incoming connection requests from multiple networks. +This technique, termed +.Dq wildcard addressing , +allows a single +server to provide service to clients on multiple networks. +To create a socket which listens on all networks, the Internet +address +.Dv INADDR_ANY +must be bound. +The +.Tn TCP +port may still be specified +at this time; if the port is not specified the system will assign one. +Once a connection has been established, the socket's address is +fixed by the peer entity's location. +The address assigned to the socket is the address associated with +the network interface through which packets are being transmitted +and received. +Normally this address corresponds to the peer entity's network. +.Pp +.Tn TCP +supports several socket options which are set with +.Xr setsockopt 2 +and tested with +.Xr getsockopt 2 . +.Bl -ohang +.It Cd TCP_INFO +Retrieve information about a socket's underlying TCP session. +.Dv TCP_INFO +is only used with +.Fn getsockopt . +The argument is a pointer to an instance of +.Vt "struct tcp_info" +(from +.In netinet/tcp.h ) . +.It Cd TCP_NODELAY +Under most circumstances, +.Tn TCP +sends data when it is presented; +when outstanding data has not yet been acknowledged, it gathers +small amounts of output to be sent in a single packet once +an acknowledgement is received. +For a small number of clients, such as window systems +that send a stream of mouse events which receive no replies, +this packetization may cause significant delays. +Therefore, +.Tn TCP +provides a boolean option, +.Dv TCP_NODELAY +(from +.In netinet/tcp.h ) , +to defeat this algorithm. +.It Cd TCP_NOPUSH +By convention, the +.Tn TCP +sender will set the +.Dq push +bit and begin transmission immediately (if permitted) at the +end of every user call to +.Xr write 2 +or +.Xr writev 2 . +When this option is set to a non-zero value, +.Tn TCP +will delay sending any data at all until either the socket +is closed, the internal send buffer is filled, or this option +is set to a zero value. +.It Cd TCP_MAXSEG +Set the maximum segment size for this connection. +The maximum segment size can only be lowered. +.It Cd TCP_SACK_ENABLE +Use selective acknowledgements for this connection. +Additional information about +segments already received can be transmitted back to the sender, +thus indicating segments that have been lost and allowing for +a swifter recovery. +Both communication endpoints need to support +.Em SACK . +The fallback behaviour is NewReno fast recovery phase, which allows +one lost segment to be recovered per round trip time. +When more than one segment has been dropped per window, the transmission can +continue without waiting for a retransmission timeout. +.It Cd TCP_MD5SIG +Use TCP MD5 signatures per RFC 2385. +This requires +.Em Security Associations +to be set up, which can be done using +.Xr ipsecctl 8 . +When a listening socket has +.Em TCP_MD5SIG +set, it accepts connections with MD5 signatures only from sources for which a +.Em Security Association +is set up. +Connections without MD5 signatures are only accepted from sources for which no +.Em Security Association +is set up. +The connected socket only has +.Em TCP_MD5SIG +set if the connection is protected with MD5 signatures. +.El +.Pp +The option level for the +.Xr setsockopt 2 +call is the protocol number for +.Tn TCP , +available from +.Xr getprotobyname 3 . +.Pp +Options at the +.Tn IP +transport level may be used with +.Tn TCP ; +see +.Xr ip 4 +or +.Xr ip6 4 . +Incoming connection requests that are source-routed are noted, +and the reverse source route is used in responding. +.Sh DIAGNOSTICS +A socket operation may fail with one of the following errors returned: +.Bl -tag -width [EADDRNOTAVAIL] +.It Bq Er EISCONN +when trying to establish a connection on a socket which +already has one; +.It Bq Er ENOBUFS +when the system runs out of memory for +an internal data structure; +.It Bq Er ETIMEDOUT +when a connection was dropped +due to excessive retransmissions; +.It Bq Er ECONNRESET +when the remote peer +forces the connection to be closed; +.It Bq Er ECONNREFUSED +when the remote +peer actively refuses connection establishment (usually because +no process is listening to the port); +.It Bq Er EADDRINUSE +when an attempt +is made to create a socket with a port which has already been +allocated; +.It Bq Er EADDRNOTAVAIL +when an attempt is made to create a +socket with a network address for which no network interface +exists. +.El +.Sh SEE ALSO +.Xr tcpbench 1 , +.Xr getsockopt 2 , +.Xr socket 2 , +.Xr inet 4 , +.Xr inet6 4 , +.Xr ip 4 , +.Xr ip6 4 , +.Xr netintro 4 , +.Xr ipsecctl 8 , +.Xr tcpdrop 8 +.Sh HISTORY +The +.Nm +protocol stack appeared in +.Bx 4.2 . diff --git a/static/openbsd/man4/tcpci.4 b/static/openbsd/man4/tcpci.4 new file mode 100644 index 00000000..b92cdda5 --- /dev/null +++ b/static/openbsd/man4/tcpci.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: tcpci.4,v 1.1 2020/04/27 21:36:07 patrick Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 27 2020 $ +.Dt TCPCI 4 +.Os +.Sh NAME +.Nm tcpci +.Nd USB Type-C Port Controller Interface +.Sh SYNOPSIS +.Cd "tcpci* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the USB Type-C Port Controller Interface. +It takes care of plug and unplug events on the USB Type-C port and discovers +the orientation of the plug so that the USB SuperSpeed pins can be routed +correctly. +Additionally it enables power on the USB Type-C port when a sink +is connected to power attached devices. +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Patrick Wildt Aq Mt patrick@blueri.se . diff --git a/static/openbsd/man4/termios.4 b/static/openbsd/man4/termios.4 new file mode 100644 index 00000000..51aa9ba4 --- /dev/null +++ b/static/openbsd/man4/termios.4 @@ -0,0 +1,1539 @@ +.\" $OpenBSD: termios.4,v 1.40 2021/11/09 16:11:21 jmc Exp $ +.\" $NetBSD: termios.4,v 1.5 1994/11/30 16:22:36 jtc Exp $ +.\" +.\" Copyright (c) 1991, 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)termios.4 8.4 (Berkeley) 4/19/94 +.\" +.Dd $Mdocdate: November 9 2021 $ +.Dt TERMIOS 4 +.Os +.Sh NAME +.Nm termios +.Nd general terminal line discipline +.Sh SYNOPSIS +.In termios.h +.Sh DESCRIPTION +This describes a general terminal line discipline that is +supported on tty asynchronous communication ports. +.Ss Opening a Terminal Device File +When a terminal file is opened, it normally causes the process to wait +until a connection is established. +For most hardware, the presence of a connection is indicated by the assertion +of the hardware +.Dv CARRIER line . +If the termios structure associated with the terminal file has the +.Dv CLOCAL +flag set in the cflag, or if the +.Dv O_NONBLOCK +flag is set +in the +.Xr open 2 +call, then the open will succeed even without +a connection being present. +In practice, applications +seldom open these files; they are opened by special programs, such +as +.Xr getty 8 +or +.Xr sshd 8 , +and become +an application's standard input, output, and error files. +.Ss Job Control in a Nutshell +Every process is associated with a particular process group and session. +The grouping is hierarchical: every member of a particular process group is a +member of the same session. +This structuring is used in managing groups of related processes for purposes +of +.\" .Gw "job control" ; +.Em "job control" ; +that is, the +ability from the keyboard (or from program control) to simultaneously +stop or restart +a complex command (a command composed of one or more related +processes). +The grouping into process groups allows delivering of signals that stop or +start the group as a whole, along with arbitrating which process group has +access to the single controlling terminal. +The grouping at a higher layer into sessions is to restrict +the job control related signals and system calls to within processes +resulting from a particular instance of a "login". +Typically, a session is created when a user logs in, and the login terminal +is set up to be the controlling terminal; all processes spawned from that +login shell are in the same session, and inherit the controlling +terminal. +A job control shell +operating interactively (that is, reading commands from a terminal) +normally groups related processes together by placing them into the +same process group. +A set of processes in the same process group is collectively referred to as +a "job". +When the foreground process group of the terminal is the same as the process +group of a particular job, that job is said to be in the "foreground". +When the process group of the terminal is different than the process group of +a job (but is still the controlling terminal), that job is said +to be in the "background". +Normally the shell reads a command and starts the job that implements that +command. +If the command is to be started in the foreground (typical), it sets the +process group of the terminal to the process group of the started job, waits +for the job to complete, and then sets the process group of the terminal +back to its own process group (it puts itself into the foreground). +If the job is to be started in the background (as denoted by the shell +operator "&"), it never changes the process group of the terminal and doesn't +wait for the job to complete (that is, it immediately attempts to read the next +command). +If the job is started in the foreground, the user may type a key (usually +.Ql \&^Z ) +which generates the terminal stop signal +.Pq Dv SIGTSTP +and has the effect of stopping the entire job. +The shell will notice that the job stopped, and will resume running after +placing itself in the foreground. +The shell also has commands for placing stopped jobs in the background, +and for placing stopped or background jobs into the foreground. +.Ss Orphaned Process Groups +An orphaned process group is a process group that has no process +whose parent is in a different process group, yet is in the same +session. +Conceptually it means a process group that doesn't have +a parent that could do anything if it were to be stopped. +For example, the initial login shell is typically in an orphaned +process group. +Orphaned process groups are immune to keyboard generated stop +signals and job control signals resulting from reads or writes to the +controlling terminal. +.Ss The Controlling Terminal +A terminal may belong to a process as its controlling terminal. +Each process of a session that has a controlling terminal has the same +controlling terminal. +A terminal may be the controlling terminal for at most one session. +The controlling terminal for a session is allocated by the session leader +by issuing the +.Dv TIOCSCTTY +ioctl. +A controlling terminal is never acquired by merely opening a terminal device +file. +When a controlling terminal becomes +associated with a session, its foreground process group is set to +the process group of the session leader. +.Pp +The controlling terminal is inherited by a child process during a +.Xr fork 2 +function call. +A process relinquishes its controlling terminal when it creates a new session +with the +.Xr setsid 2 +function; other processes remaining in the old session that had this terminal +as their controlling terminal continue to have it. +A process does not relinquish its +controlling terminal simply by closing all of its file descriptors +associated with the controlling terminal if other processes continue to +have it open. +.Pp +When a controlling process terminates, the controlling terminal is +disassociated from the current session, allowing it to be acquired by a +new session leader. +Subsequent access to the terminal by other processes in the earlier session +will be denied, with attempts to access the terminal treated as if modem +disconnect had been sensed. +.Ss Terminal Access Control +If a process is in the foreground process group of its controlling +terminal, read operations are allowed. +Any attempts by a process +in a background process group to read from its controlling terminal +causes a +.Dv SIGTTIN +signal to be sent to +the process's group +unless one of the +following special cases apply: If the reading process is ignoring or +blocking the +.Dv SIGTTIN +signal, or if the process group of the reading process is orphaned, the +.Xr read 2 +returns -1 with +.Va errno +set to +.Er EIO +and no +signal is sent. +The default action of the +.Dv SIGTTIN +signal is to stop the +process to which it is sent. +.Pp +If a process is in the foreground process group of its controlling +terminal, write operations are allowed. +Attempts by a process in a background process group to write to its +controlling terminal will cause the process group to be sent a +.Dv SIGTTOU +signal unless one of the following special cases apply: +If +.Dv TOSTOP +is not +set, or if +.Dv TOSTOP +is set and the process is ignoring or blocking the +.Dv SIGTTOU +signal, the process is allowed to write to the terminal and the +.Dv SIGTTOU +signal is not sent. +If +.Dv TOSTOP +is set, and the process group of +the writing process is orphaned, and the writing process is not ignoring +or blocking +.Dv SIGTTOU , +the +.Xr write 2 +returns -1 with +.Va errno +set to +.Er EIO +and no signal is sent. +.Pp +Certain calls that set terminal parameters are treated in the same +fashion as write, except that +.Dv TOSTOP +is ignored; that is, the effect is +identical to that of terminal writes when +.Dv TOSTOP +is set. +.Ss Input Processing and Reading Data +A terminal device associated with a terminal device file may operate in +full-duplex mode, so that data may arrive even while output is occurring. +Each terminal device file has associated with it an input queue, into +which incoming data is stored by the system before being read by a +process. +The system imposes a limit, +.Dv MAX_INPUT , +on the number of +bytes that may be stored in the input queue. +The behavior of the system when this limit is exceeded depends on the +setting of the +.Dv IMAXBEL +flag in the termios +.Fa c_iflag . +If this flag is set, the terminal +is sent an ASCII BEL +character each time a character is received +while the input queue is full. +Otherwise, the input queue is flushed upon receiving the character. +.Pp +Two general kinds of input processing are available, determined by +whether the terminal device file is in canonical mode or noncanonical +mode. +Additionally, input characters are processed according to the +.Fa c_iflag +and +.Fa c_lflag +fields. +Such processing can include echoing, which in general means transmitting +input characters immediately back to the terminal when they are received +from the terminal. +This is useful for terminals that can operate in full-duplex mode. +.Pp +The manner in which data is provided to a process reading from a terminal +device file is dependent on whether the terminal device file is in +canonical or noncanonical mode. +.Pp +Another dependency is whether the +.Dv O_NONBLOCK +flag is set by +.Fn open +or +.Fn fcntl . +If the +.Dv O_NONBLOCK +flag is clear, then the read request is +blocked until data is available or a signal has been received. +If the +.Dv O_NONBLOCK +flag is set, then the read request is completed, without +blocking, in one of three ways: +.Bl -enum -offset indent +.It +If there is enough data available to satisfy the entire request, +and the read completes successfully the number of bytes read is returned. +.It +If there is not enough data available to satisfy the entire +request, and the read completes successfully, having read as +much data as possible, the number of bytes read is returned. +.It +If there is no data available, the read returns -1, with +.Va errno +set to +.Er EAGAIN . +.El +.Pp +When data is available depends on whether the input processing mode is +canonical or noncanonical. +.Ss Canonical Mode Input Processing +In canonical mode input processing, terminal input is processed in units +of lines. +A line is delimited by a newline +.Ql \&\en +character, an end-of-file +.Pq Dv EOF +character, or an end-of-line +.Pq Dv EOL +character. +See the +.Sx "Special Characters" +section for +more information on +.Dv EOF +and +.Dv EOL . +This means that a read request will +not return until an entire line has been typed, or a signal has been +received. +Also, no matter how many bytes are requested in the read call, +at most one line is returned. +It is not, however, necessary to read a whole line at once; any number +of bytes, even one, may be requested in a read without losing information. +.Pp +.Dv MAX_CANON +is a limit on the +number of bytes in a line. +The behavior of the system when this limit is +exceeded is the same as when the input queue limit +.Dv MAX_INPUT , +is exceeded. +.Pp +Erase and kill processing occur when either of two special characters, +the +.Dv ERASE +and +.Dv KILL +characters (see the +.Sx "Special Characters section" ) , +is received. +This processing affects data in the input queue that has not yet been +delimited by a newline +.Dv NL , +.Dv EOF , +or +.Dv EOL +character. +This un-delimited data makes up the current line. +The +.Dv ERASE +character deletes the last +character in the current line, if there is any. +The +.Dv KILL +character +deletes all data in the current line, if there is any. +The +.Dv ERASE +and +.Dv KILL +characters have no effect if there is no data in the current line. +The +.Dv ERASE +and +.Dv KILL +characters themselves are not placed in the input +queue. +.Ss Noncanonical Mode Input Processing +In noncanonical mode input processing, input bytes are not assembled into +lines, and erase and kill processing does not occur. +The values of the +.Dv VMIN +and +.Dv VTIME +members of the +.Fa c_cc +array are used to determine how to +process the bytes received. +.Pp +.Dv VMIN +represents the minimum number of bytes that should be received when +the +.Xr read 2 +function successfully returns. +.Dv VTIME +is a timer of 0.1 second +granularity that is used to time out bursty and short term data +transmissions. +If +.Dv VMIN +is greater than +.Dv MAX_INPUT , +the response to the +request is undefined. +The four possible values for +.Dv VMIN +and +.Dv VTIME +and +their interactions are described below. +.Ss "Case A: VMIN > 0, VTIME > 0" +In this case +.Dv VTIME +serves as an inter-byte timer and is activated after +the first byte is received. +Since it is an inter-byte timer, it is reset after a byte is received. +The interaction between +.Dv VMIN +and +.Dv VTIME +is as +follows: as soon as one byte is received, the inter-byte timer is +started. +If +.Dv VMIN +bytes are received before the inter-byte timer expires +(remember that the timer is reset upon receipt of each byte), the read is +satisfied. +If the timer expires before +.Dv VMIN +bytes are received, the +characters received to that point are returned to the user. +Note that if +.Dv VTIME +expires at least one byte is returned because the timer would +not have been enabled unless a byte was received. +In this case +.Pf \&( Dv VMIN +> 0, +.Dv VTIME +> 0) the read blocks until the +.Dv VMIN +and +.Dv VTIME +mechanisms are +activated by the receipt of the first byte, or a signal is received. +If data is in the buffer at the time of the read(), the result is as +if data had been received immediately after the read(). +.Ss "Case B: VMIN > 0, VTIME = 0" +In this case, since the value of +.Dv VTIME +is zero, the timer plays no role +and only +.Dv VMIN +is significant. +A pending read is not satisfied until +.Dv VMIN +bytes are received (i.e., the pending read blocks until +.Dv VMIN +bytes +are received), or a signal is received. +A program that uses this case to read record-based terminal I/O +may block indefinitely in the read +operation. +.Ss "Case C: VMIN = 0, VTIME > 0" +In this case, since +.Dv VMIN += 0, +.Dv VTIME +no longer represents an inter-byte +timer. +It now serves as a read timer that is activated as soon as the +read function is processed. +A read is satisfied as soon as a single byte is received or the read +timer expires. +Note that in this case if the timer expires, no bytes are returned. +If the timer does not expire, the only way the read can be satisfied is +if a byte is received. +In this case the read will not block indefinitely waiting for a byte; if +no byte is received within +.Dv VTIME Ns *0.1 +seconds after the read is initiated, +the read returns a value of zero, having read no data. +If data is in the buffer at the time of the read, the timer is started +as if data had been received immediately after the read. +.Ss Case D: VMIN = 0, VTIME = 0 +The minimum of either the number of bytes requested or the number of +bytes currently available is returned without waiting for more +bytes to be input. +If no characters are available, read returns a value of zero, having +read no data. +.Ss Writing Data and Output Processing +When a process writes one or more bytes to a terminal device file, they +are processed according to the +.Fa c_oflag +field (see the +.Sx Output Modes +section). +The +implementation may provide a buffering mechanism; as such, when a call to +write() completes, all of the bytes written have been scheduled for +transmission to the device, but the transmission will not necessarily +have been completed. +.\" See also .Sx "6.4.2" for the effects of +.\" .Dv O_NONBLOCK +.\" on write. +.Ss Special Characters +Certain characters have special functions on input or output or both. +These functions are summarized as follows: +.Bl -tag -width indent +.It Dv INTR +Special character on input and is recognized if the +.Dv ISIG +flag (see the +.Sx "Local Modes" +section) is enabled. +Generates a +.Dv SIGINT +signal which is sent to all processes in the foreground +process group for which the terminal is the controlling +terminal. +If +.Dv ISIG +is set, the +.Dv INTR +character is +discarded when processed. +.It Dv QUIT +Special character on input and is recognized if the +.Dv ISIG +flag is enabled. +Generates a +.Dv SIGQUIT +signal which is +sent to all processes in the foreground process group +for which the terminal is the controlling terminal. +If +.Dv ISIG +is set, the +.Dv QUIT +character is discarded when +processed. +.It Dv ERASE +Special character on input and is recognized if the +.Dv ICANON +flag is set. +Erases the last character in the current line; see +.Sx "Canonical Mode Input Processing" . +It does not erase beyond the start of a line, as delimited by a +.Dv NL , +.Dv EOF , +or +.Dv EOL +character. +If +.Dv ICANON +is set, the +.Dv ERASE +character is +discarded when processed. +.It Dv KILL +Special character on input and is recognized if the +.Dv ICANON +flag is set. +Deletes the entire line, as delimited by a +.Dv NL , +.Dv EOF , +or +.Dv EOL +character. +If +.Dv ICANON +is set, the +.Dv KILL +character is discarded when processed. +.It Dv EOF +Special character on input and is recognized if the +.Dv ICANON +flag is set. +When received, all the bytes waiting to be read are immediately passed to the +process, without waiting for a newline, and the +.Dv EOF +is discarded. +Thus, if there are no bytes waiting (that +is, the +.Dv EOF +occurred at the beginning of a line), a byte +count of zero is returned from the read(), +representing an end-of-file indication. +If +.Dv ICANON +is +set, the +.Dv EOF +character is discarded when processed. +.It Dv NL +Special character on input and is recognized if the +.Dv ICANON +flag is set. +It is the line delimiter +.Ql \&\en . +.It Dv EOL +Special character on input and is recognized if the +.Dv ICANON +flag is set. +Is an additional line delimiter, +like +.Dv NL . +.It Dv SUSP +If the +.Dv ISIG +flag is enabled, receipt of the +.Dv SUSP +character causes a +.Dv SIGTSTP +signal to be sent to all processes in the +foreground process group for which the terminal is the +controlling terminal, and the +.Dv SUSP +character is +discarded when processed. +.It Dv STOP +Special character on both input and output and is +recognized if the +.Dv IXON +(output control) or +.Dv IXOFF +(input +control) flag is set. +Can be used to temporarily suspend output. +It is useful with fast terminals to prevent output from disappearing +before it can be read. +If +.Dv IXON +is set, the +.Dv STOP +character is discarded when +processed. +.It Dv START +Special character on both input and output and is +recognized if the +.Dv IXON +(output control) or +.Dv IXOFF +(input +control) flag is set. +Can be used to resume output that has been suspended by a +.Dv STOP +character. +If +.Dv IXON +is set, the +.Dv START +character is discarded when processed. +.It Dv CR +Special character on input and is recognized if the +.Dv ICANON +flag is set; it is the +.Ql \&\er , +as denoted in the C Standard {2}. +When +.Dv ICANON +and +.Dv ICRNL +are set and +.Dv IGNCR +is not set, this character is translated into a +.Dv NL , +and +has the same effect as a +.Dv NL +character. +.El +.Pp +The following special characters are extensions defined by this +system and are not a part of 1003.1 termios. +.Bl -tag -width indent +.It Dv EOL2 +Secondary +.Dv EOL +character. +Same function as +.Dv EOL . +.It Dv WERASE +Special character on input and is recognized if the +.Dv ICANON +flag is set. +Erases the last word in the current +line according to one of two algorithms. +If the +.Dv ALTWERASE +flag is not set, first any preceding whitespace is +erased, and then the maximal sequence of non-whitespace +characters. +If +.Dv ALTWERASE +is set, first any preceding +whitespace is erased, and then the maximal sequence +of alphabetic/underscores or non alphabetic/underscores. +As a special case in this second algorithm, the first previous +non-whitespace character is skipped in determining +whether the preceding word is a sequence of +alphabetic/underscores. +This sounds confusing but turns out to be quite practical. +.It Dv REPRINT +Special character on input and is recognized if the +.Dv ICANON +flag is set. +Causes the current input edit line +to be retyped. +.It Dv DSUSP +Has similar actions to the +.Dv SUSP +character, except that +the +.Dv SIGTSTP +signal is delivered when one of the processes +in the foreground process group issues a read() to the +controlling terminal. +.It Dv LNEXT +Special character on input and is recognized if the +.Dv IEXTEN +flag is set. +Receipt of this character causes the next character to be taken literally. +.It Dv DISCARD +Special character on input and is recognized if the +.Dv IEXTEN +flag is set. +Receipt of this character toggles the flushing of terminal output. +.It Dv STATUS +Special character on input and is recognized if the +.Dv ICANON +flag is set. +Receipt of this character causes a +.Dv SIGINFO +signal to be sent to the foreground process group of the +terminal. +Also, if the +.Dv NOKERNINFO +flag is not set, it +causes the kernel to write a status message to the terminal +that displays the current load average, the name of the +command in the foreground, its process ID, the symbolic +wait channel, the number of user and system seconds used, +the percentage of CPU the process is getting, and the resident +set size of the process. +.El +.Pp +The +.Dv NL +and +.Dv CR +characters cannot be changed. +The values for all the remaining characters can be set and are +described later in the document under +.Sx Special Control Characters . +.Pp +Special +character functions associated with changeable special control characters +can be disabled individually by setting their value to +.Dv _POSIX_VDISABLE ; +see +.Sx "Special Control Characters" . +.Pp +If two or more special characters have the same value, the function +performed when that character is received is undefined. +.Ss Modem Disconnect +If a modem disconnect is detected by the terminal interface for a +controlling terminal, and if +.Dv CLOCAL +is not set in the +.Fa c_cflag +field for +the terminal, the +.Dv SIGHUP +signal is sent to the controlling +process associated with the terminal. +Unless other arrangements have been made, this causes the controlling +process to terminate. +Any subsequent call to the read() function returns the value zero, +indicating end of file. +Thus, processes that read a terminal file and test for end-of-file can +terminate appropriately after a disconnect. +.\" If the +.\" .Er EIO +.\" condition specified in 6.1.1.4 that applies +.\" when the implementation supports job control also exists, it is +.\" unspecified whether the +.\" .Dv EOF +.\" condition or the +.\" .Pf [ Dv EIO +.\" ] is returned. +Any +subsequent write() to the terminal device returns -1, with +.Va errno +set to +.Er EIO , +until the device is closed. +.Sh General Terminal Interface +.Ss Closing a Terminal Device File +The last process to close a terminal device file causes any output +to be sent to the device and any input to be discarded. +Then, if +.Dv HUPCL +is set in the control modes, and the communications port supports a +disconnect function, the terminal device performs a disconnect. +.Ss Parameters That Can Be Set +Routines that need to control certain terminal I/O characteristics +do so by using the termios structure as defined in the header +.In termios.h . +This structure contains minimally four scalar elements of bit flags +and one array of special characters. +The scalar flag elements are +named: +.Fa c_iflag , +.Fa c_oflag , +.Fa c_cflag , +and +.Fa c_lflag . +The character array is named +.Fa c_cc , +and its maximum index is +.Dv NCCS . +.Ss Input Modes +Values of the +.Fa c_iflag +field describe the basic +terminal input control, and are composed of +following masks: +.Pp +.Bl -tag -width IMAXBEL -offset indent -compact +.It Dv IGNBRK +/* ignore BREAK condition */ +.It Dv BRKINT +/* map BREAK to SIGINT */ +.It Dv IGNPAR +/* ignore (discard) parity errors */ +.It Dv PARMRK +/* mark parity and framing errors */ +.It Dv INPCK +/* enable checking of parity errors */ +.It Dv ISTRIP +/* strip 8th bit off chars */ +.It Dv INLCR +/* map NL into CR */ +.It Dv IGNCR +/* ignore CR */ +.It Dv ICRNL +/* map CR to NL (ala CRMOD) */ +.It Dv IXON +/* enable output flow control */ +.It Dv IXOFF +/* enable input flow control */ +.It Dv IXANY +/* any char will restart after stop */ +.It Dv IMAXBEL +/* ring bell on input queue full */ +.It Dv IUCLC +/* translate upper case to lower case */ +.El +.Pp +In the context of asynchronous serial data transmission, a break +condition is defined as a sequence of zero-valued bits that continues for +more than the time to send one byte. +The entire sequence of zero-valued bits is interpreted as a single break +condition, even if it continues for a time equivalent to more than one byte. +In contexts other than asynchronous serial data transmission the definition +of a break condition is implementation defined. +.Pp +If +.Dv IGNBRK +is set, a break condition detected on input is ignored, that +is, not put on the input queue and therefore not read by any process. +If +.Dv IGNBRK +is not set and +.Dv BRKINT +is set, the break condition flushes the +input and output queues and if the terminal is the controlling terminal +of a foreground process group, the break condition generates a +single +.Dv SIGINT +signal to that foreground process group. +If neither +.Dv IGNBRK +nor +.Dv BRKINT +is set, a break condition is read as a single +.Ql \&\e0 , +or if +.Dv PARMRK +is set, as +.Ql \&\e377 , +.Ql \&\e0 , +.Ql \&\e0 . +.Pp +If +.Dv IGNPAR +is set, a byte with a framing or parity error (other than +break) is ignored. +.Pp +If +.Dv PARMRK +is set, and +.Dv IGNPAR +is not set, a byte with a framing or parity +error (other than break) is given to the application as the +three-character sequence +.Ql \&\e377 , +.Ql \&\e0 , +X, where +.Ql \&\e377 , +.Ql \&\e0 +is a two-character +flag preceding each sequence and X is the data of the character received +in error. +To avoid ambiguity in this case, if +.Dv ISTRIP +is not set, a valid +character of +.Ql \&\e377 +is given to the application as +.Ql \&\e377 , +.Ql \&\e377 . +If +neither +.Dv PARMRK +nor +.Dv IGNPAR +is set, a framing or parity error (other than +break) is given to the application as a single character +.Ql \&\e0 . +.Pp +If +.Dv INPCK +is set, input parity checking is enabled. +If +.Dv INPCK +is not set, +input parity checking is disabled, allowing output parity generation +without input parity errors. +Note that whether input parity checking is enabled or disabled is independent +of whether parity detection is enabled or disabled (see +.Sx "Control Modes" ) . +If parity detection is enabled but input +parity checking is disabled, the hardware to which the terminal is +connected recognizes the parity bit, but the terminal special file +does not check whether this bit is set correctly or not. +.Pp +If +.Dv ISTRIP +is set, valid input bytes are first stripped to seven bits, +otherwise all eight bits are processed. +.Pp +If +.Dv INLCR +is set, a received +.Dv NL +character is translated into a +.Dv CR +character. +If +.Dv IGNCR +is set, a received +.Dv CR +character is ignored (not +read). +If +.Dv IGNCR +is not set and +.Dv ICRNL +is set, a received +.Dv CR +character is +translated into a +.Dv NL +character. +.Pp +If +.Dv IXON +is set, start/stop output control is enabled. +A received +.Dv STOP +character suspends output and a received +.Dv START +character +restarts output. +If +.Dv IXANY +is also set, then any character may +restart output. +When +.Dv IXON +is set, +.Dv START +and +.Dv STOP +characters are not +read, but merely perform flow control functions. +When +.Dv IXON +is not set, +the +.Dv START +and +.Dv STOP +characters are read. +.Pp +If +.Dv IXOFF +is set, start/stop input control is enabled. +The system shall transmit one or more +.Dv STOP +characters, which are intended to cause the +terminal device to stop transmitting data, as needed to prevent the input +queue from overflowing and causing the undefined behavior described in +.Sx "Input Processing and Reading Data" , +and shall transmit one or more +.Dv START +characters, which are +intended to cause the terminal device to resume transmitting data, as +soon as the device can continue transmitting data without risk of +overflowing the input queue. +The precise conditions under which +.Dv STOP +and +.Dv START +characters are transmitted are implementation defined. +.Pp +If +.Dv IMAXBEL +is set and the input queue is full, subsequent input shall cause an +ASCII BEL character to be transmitted to +the output queue. +.Pp +If +.Dv IUCLC +is set, characters will be translated from upper to lower case on +input. +.Pp +The initial input control value after open() is implementation defined. +.Ss Output Modes +Values of the +.Fa c_oflag +field describe the basic terminal output control, +and are composed of the following masks: +.Pp +.Bl -tag -width OXTABS -offset indent -compact +.It Dv OPOST +/* enable following output processing */ +.It Dv ONLCR +/* map NL to CR-NL (ala +.Dv CRMOD ) +*/ +.It Dv OXTABS +/* expand tabs to spaces */ +.It Dv ONOEOT +/* discard +.Dv EOT Ns 's +.Pq ^D +on output */ +.It Dv OCRNL +/* map CR to NL */ +.It Dv OLCUC +/* translate lower case to upper case */ +.It Dv ONOCR +/* No CR output at column 0 */ +.It Dv ONLRET +/* NL performs the CR function */ +.El +.Pp +If +.Dv OPOST +is set, the remaining flag masks are interpreted as follows; +otherwise characters are transmitted without change. +.Pp +If +.Dv ONLCR +is set, newlines are translated to carriage return, linefeeds. +.Pp +If +.Dv OXTABS +is set, tabs are expanded to the appropriate number of +spaces (assuming 8 column tab stops). +.Pp +If +.Dv ONOEOT +is set, ASCII EOT characters are discarded on output. +.Pp +If +.Dv OCRNL +is set, carriage returns are translated to newlines. +.Pp +If +.Dv OLCUC +is set, lower case is translated to upper case on output. +.Pp +If +.Dv ONOCR +is set, no CR character is output when at column 0. +.Pp +If +.Dv ONLRET +is set, NL also performs CR on output, and reset current +column to 0. +.Ss Control Modes +Values of the +.Fa c_cflag +field describe the basic +terminal hardware control, and are composed of the +following masks. +Not all values +specified are supported by all hardware. +.Pp +.Bl -tag -width CRTSXIFLOW -offset indent -compact +.It Dv CSIZE +/* character size mask */ +.It Dv CS5 +/* 5 bits (pseudo) */ +.It Dv CS6 +/* 6 bits */ +.It Dv CS7 +/* 7 bits */ +.It Dv CS8 +/* 8 bits */ +.It Dv CSTOPB +/* send 2 stop bits */ +.It Dv CREAD +/* enable receiver */ +.It Dv PARENB +/* parity enable */ +.It Dv PARODD +/* odd parity, else even */ +.It Dv HUPCL +/* hang up on last close */ +.It Dv CLOCAL +/* ignore modem status lines */ +.It Dv CCTS_OFLOW +/* +.Dv CTS +flow control of output */ +.It Dv CRTSCTS +/* same as +.Dv CCTS_OFLOW +*/ +.It Dv CRTS_IFLOW +/* RTS flow control of input */ +.It Dv MDMBUF +/* flow control output via Carrier */ +.El +.Pp +The +.Dv CSIZE +bits specify the byte size in bits for both transmission and +reception. +The +.Fa c_cflag +is masked with +.Dv CSIZE +and compared with the +values +.Dv CS5 , +.Dv CS6 , +.Dv CS7 , +or +.Dv CS8 . +This size does not include the parity bit, if any. +If +.Dv CSTOPB +is set, two stop bits are used, otherwise one stop bit. +For example, at 110 baud, two stop bits are normally used. +.Pp +If +.Dv CREAD +is set, the receiver is enabled. +Otherwise, no character is received. +Not all hardware supports this bit. +In fact, this flag is pretty silly and if it were not part of the +.Nm +specification it would be omitted. +.Pp +If +.Dv PARENB +is set, parity generation and detection are enabled and a parity +bit is added to each character. +If parity is enabled, +.Dv PARODD +specifies +odd parity if set, otherwise even parity is used. +.Pp +If +.Dv HUPCL +is set, the modem control lines for the port are lowered +when the last process with the port open closes the port or the process +terminates. +The modem connection is broken. +.Pp +If +.Dv CLOCAL +is set, a connection does not depend on the state of the modem +status lines. +If +.Dv CLOCAL +is clear, the modem status lines are +monitored. +.Pp +Under normal circumstances, a call to the open() function waits for +the modem connection to complete. +However, if the +.Dv O_NONBLOCK +flag is set +or if +.Dv CLOCAL +has been set, the open() function returns +immediately without waiting for the connection. +.Pp +If +.Dv CCTS_OFLOW +.Pf ( Dv CRTSCTS ) +is set, +transmission is stopped when +.Dv CTS +is lowered and resumed when +.Dv CTS +is raised. +.Pp +If +.Dv MDMBUF +is set then output flow control is controlled by the state +of Carrier Detect. +.Pp +If the object for which the control modes are set is not an asynchronous +serial connection, some of the modes may be ignored; for example, if an +attempt is made to set the baud rate on a network connection to a +terminal on another host, the baud rate may or may not be set on the +connection between that terminal and the machine it is directly connected +to. +.Ss Local Modes +Values of the +.Fa c_lflag +field describe the control of +various functions, and are composed of the following +masks. +.Pp +.Bl -tag -width NOKERNINFO -offset indent -compact +.It Dv ECHOKE +/* visual erase for line kill */ +.It Dv ECHOE +/* visually erase chars */ +.It Dv ECHOK +/* echo NL after line kill */ +.It Dv ECHO +/* enable echoing */ +.It Dv ECHONL +/* echo +.Dv NL +even if +.Dv ECHO +is off */ +.It Dv ECHOPRT +/* visual erase mode for hardcopy */ +.It Dv ECHOCTL +/* echo control chars as ^(Char) */ +.It Dv ISIG +/* enable signals +.Dv INTR , +.Dv QUIT , +.Dv [D]SUSP +*/ +.It Dv ICANON +/* canonicalize input lines */ +.It Dv ALTWERASE +/* use alternate +.Dv WERASE +algorithm */ +.It Dv IEXTEN +/* enable +.Dv DISCARD +and +.Dv LNEXT +*/ +.It Dv EXTPROC +/* external processing */ +.It Dv TOSTOP +/* stop background jobs from output */ +.It Dv FLUSHO +/* output being flushed (state) */ +.It Dv NOKERNINFO +/* no kernel output from +.Dv VSTATUS +*/ +.It Dv PENDIN +/* XXX retype pending input (state) */ +.It Dv NOFLSH +/* don't flush after interrupt */ +.It Dv XCASE +/* canonical upper/lower case */ +.El +.Pp +If +.Dv ECHO +is set, input characters are echoed back to the terminal. +If +.Dv ECHO +is not set, input characters are not echoed. +.Pp +If +.Dv ECHOE +and +.Dv ICANON +are set, the +.Dv ERASE +character causes the terminal +to erase the last character in the current line from the display, if +possible. +If there is no character to erase, an implementation may echo +an indication that this was the case or do nothing. +.Pp +If +.Dv ECHOK +and +.Dv ICANON +are set, the +.Dv KILL +character causes +the current line to be discarded and the system echoes the +.Ql \&\en +character after the +.Dv KILL +character. +.Pp +If +.Dv ECHOKE +and +.Dv ICANON +are set, the +.Dv KILL +character causes the current line to be discarded and the system causes +the terminal to erase the line from the display. +.Pp +If +.Dv ECHOPRT +and +.Dv ICANON +are set, the system assumes that the display is a printing device and prints a +backslash and the erased characters when processing +.Dv ERASE +characters, followed by a forward slash. +.Pp +If +.Dv ECHOCTL +is set, the system echoes control characters +in a visible fashion using a caret followed by the control character. +.Pp +If +.Dv ALTWERASE +is set, the system uses an alternative algorithm +for determining what constitutes a word when processing +.Dv WERASE +characters (see +.Dv WERASE ) . +.Pp +If +.Dv ECHONL +and +.Dv ICANON +are set, the +.Ql \&\en +character echoes even if +.Dv ECHO +is not set. +.Pp +If +.Dv ICANON +is set, canonical processing is enabled. +This enables the erase and kill edit functions, and the assembly of input +characters into lines delimited by +.Dv NL , +.Dv EOF , +and +.Dv EOL , +as described in +.Sx "Canonical Mode Input Processing" . +.Pp +If +.Dv ICANON +is not set, read requests are satisfied directly from the input +queue. +A read is not satisfied until at least +.Dv VMIN +bytes have been received or the timeout value +.Dv VTIME +expired between bytes. +The time value represents tenths of seconds. +See +.Sx "Noncanonical Mode Input Processing" +for more details. +.Pp +If +.Dv ISIG +is set, each input character is checked against the special +control characters +.Dv INTR , +.Dv QUIT , +and +.Dv SUSP +(job control only). +If an input character matches one of these control characters, the function +associated with that character is performed. +If +.Dv ISIG +is not set, no +checking is done. +Thus these special input functions are possible only +if +.Dv ISIG +is set. +.Pp +If +.Dv IEXTEN +is set, implementation-defined functions are recognized +from the input data. +How +.Dv IEXTEN +being set +interacts with +.Dv ICANON , +.Dv ISIG , +.Dv IXON , +or +.Dv IXOFF +is implementation defined. +If +.Dv IEXTEN +is not set, then +implementation-defined functions are not recognized, and the +corresponding input characters are not processed as described for +.Dv ICANON , +.Dv ISIG , +.Dv IXON , +and +.Dv IXOFF . +.Pp +If +.Dv NOFLSH +is set, the normal flush of the input and output queues +associated with the +.Dv INTR , +.Dv QUIT , +and +.Dv SUSP +characters +is not done. +.Pp +If +.Dv XCASE +and +.Dv ICANON +is set, an upper case character is preserved on input if prefixed by +a \e character. +In addition, this prefix is added to upper case characters on output. +.Pp +In addition, the following special character translations are in effect: +.Bl -column "for:" "use:" -offset indent +.It Em "for:" Ta Em "use:" +.It Dv ` Ta \&\e' +.It Dv \&| Ta \&\e! +.It Dv ~ Ta \&\e^ +.It Dv { Ta \&\e( +.It Dv } Ta \&\e) +.It Dv \&\e Ta \&\e\e +.El +.Pp +If +.Dv TOSTOP +is set, the signal +.Dv SIGTTOU +is sent to the process group of a process that tries to write to +its controlling terminal if it is not in the foreground process group for +that terminal. +This signal, by default, stops the members of the process group. +Otherwise, the output generated by that process is output to the +current output stream. +Processes that are blocking or ignoring +.Dv SIGTTOU +signals are excepted and allowed to produce output and the +.Dv SIGTTOU +signal +is not sent. +.Pp +If +.Dv NOKERNINFO +is set, the kernel does not produce a status message +when processing +.Dv STATUS +characters (see +.Dv STATUS ) . +.Ss Special Control Characters +The special control characters values are defined by the array +.Fa c_cc . +This table lists the array index, the corresponding special character, +and the system default value. +For an accurate list of the system defaults, consult the header file +.In sys/ttydefaults.h . +.Bl -column "Index Name" "Special Character" -offset indent +.It Em "Index Name" Ta Em "Special Character" Ta Em "Default Value" +.It Dv VEOF Ta EOF Ta \&^D +.It Dv VEOL Ta EOL Ta _POSIX_VDISABLE +.It Dv VEOL2 Ta EOL2 Ta _POSIX_VDISABLE +.It Dv VERASE Ta ERASE Ta \&^? Ql \&\e177 +.It Dv VWERASE Ta WERASE Ta \&^W +.It Dv VKILL Ta KILL Ta \&^U +.It Dv VREPRINT Ta REPRINT Ta \&^R +.It Dv VINTR Ta INTR Ta \&^C +.It Dv VQUIT Ta QUIT Ta \&^\e\e Ql \&\e34 +.It Dv VSUSP Ta SUSP Ta \&^Z +.It Dv VDSUSP Ta DSUSP Ta \&^Y +.It Dv VSTART Ta START Ta \&^Q +.It Dv VSTOP Ta STOP Ta \&^S +.It Dv VLNEXT Ta LNEXT Ta \&^V +.It Dv VDISCARD Ta DISCARD Ta \&^O +.It Dv VMIN Ta --- Ta \&1 +.It Dv VTIME Ta --- Ta \&0 +.It Dv VSTATUS Ta STATUS Ta \&^T +.El +.Pp +If the +value of one of the changeable special control characters (see +.Sx "Special Characters" ) +is +.Dv _POSIX_VDISABLE , +that function is disabled; that is, no input +data is recognized as the disabled special character. +If +.Dv ICANON +is +not set, the value of +.Dv _POSIX_VDISABLE +has no special meaning for the +.Dv VMIN +and +.Dv VTIME +entries of the +.Fa c_cc +array. +.Pp +The initial values of the flags and control characters +after open() is set according to the values in the header +.In sys/ttydefaults.h . +.Sh SEE ALSO +.Xr tcgetattr 3 , +.Xr tcsetattr 3 diff --git a/static/openbsd/man4/thmc.4 b/static/openbsd/man4/thmc.4 new file mode 100644 index 00000000..be293c0a --- /dev/null +++ b/static/openbsd/man4/thmc.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: thmc.4,v 1.4 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt THMC 4 +.Os +.Sh NAME +.Nm thmc +.Nd TI THMC50, Analog ADM1022/1028 temperature sensor +.Sh SYNOPSIS +.Cd "thmc* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides minimal support for the TI THMC50, Analog ADM1022 +and Analog ADM1028 temperature sensor. +The device possesses internal and external temperature sensors, +These values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Theo de Raadt Aq Mt deraadt@openbsd.org . diff --git a/static/openbsd/man4/tht.4 b/static/openbsd/man4/tht.4 new file mode 100644 index 00000000..a9f4caf8 --- /dev/null +++ b/static/openbsd/man4/tht.4 @@ -0,0 +1,73 @@ +.\" $OpenBSD: tht.4,v 1.8 2022/02/17 12:24:08 jsg Exp $ +.\" +.\" Copyright (c) 2007 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 17 2022 $ +.Dt THT 4 +.Os +.Sh NAME +.Nm tht , +.Nm thtc +.Nd Tehuti Networks 10Gb Ethernet device +.Sh SYNOPSIS +.Cd "thtc* at pci?" +.Cd "tht* at thtc?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Tehuti Networks 10 Gigabit Ethernet +controllers and adapters, including the following: +.Pp +.Bl -bullet -compact +.It +TN3017-S 10 GbE Single Port XAUI Server Controller +.It +TN3017-D 10 GbE Dual Port XAUI Server Controller +.It +TN7581-D 10 GbE Dual XFP Server Adapter +.It +TN7585-D 10 GbE Dual CX4 Low Profile Server Adapter +.It +TN7588-S 10 GbE Single 10GBASET Low Profile Server Adapter +.It +TN7588-D 10 GbE Dual 10GBASET Low Profile Server Adapter +.It +TN7589-S 10 GbE Single CX4 Low Profile Server Adapter +.El +.Sh FILES +The adapter needs a firmware file, which is loaded on demand by the +driver when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/tht +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/ti.4 b/static/openbsd/man4/ti.4 new file mode 100644 index 00000000..0b524401 --- /dev/null +++ b/static/openbsd/man4/ti.4 @@ -0,0 +1,210 @@ +.\" $OpenBSD: ti.4,v 1.45 2021/09/08 20:29:21 jmc Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: src/share/man/man4/ti.4,v 1.11 2000/08/10 19:47:32 billf Exp $ +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt TI 4 +.Os +.Sh NAME +.Nm ti +.Nd Alteon Networks Tigon I and II 1Gb Ethernet device +.Sh SYNOPSIS +.Cd "ti* at pci?" +.Cd "ti* at sbus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Gigabit Ethernet adapters based on the +Alteon Networks Tigon Gigabit Ethernet controller chip, including +the following: +.Pp +.Bl -bullet -compact -offset indent +.It +3Com 3C985-SX Gigabit Ethernet (1000baseSX) +.It +3Com 3C985B-SX Gigabit Ethernet (1000baseSX) +.It +Alteon AceNIC V Gigabit Ethernet (1000baseSX) +.It +Alteon AceNIC V Gigabit Ethernet (1000baseT) +.It +Digital EtherWORKS 1000SX PCI Gigabit Ethernet (1000baseSX) +.It +Farallon PN9000SX Gigabit Ethernet (1000baseSX) +.It +Netgear GA620 Gigabit Ethernet (1000baseSX) +.It +Netgear GA620T Gigabit Ethernet (1000baseT) +.It +Silicon Graphics Gigabit Ethernet (1000baseSX) +.It +Silicon Graphics Gigabit Ethernet (1000baseT) +.It +Sun Vector Gigabit Ethernet (1000baseSX) +.El +.Pp +The Tigon contains an embedded R4000 CPU, Gigabit MAC, dual DMA channels and +a PCI interface unit. +The Tigon II contains two R4000 CPUs and other refinements. +Either chip can be used in either a 32-bit or 64-bit PCI slot. +Communication with the chip is achieved via PCI shared memory and +bus master DMA. +SBus cards are also available and use a special bridge chip. +The Tigon I and II support hardware multicast address filtering, +VLAN tag insertion and stripping, and jumbo frames. +.Pp +While the Tigon chipset supports 10, 100 and 1000Mbps speeds, support for +10 and 100Mbps speeds is only available on boards with the proper +transceivers. +Most adapters are only designed to work at 1000Mbps, however the driver +should support those NICs that work at lower speeds as well. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 1000baseSX +Set 1000Mbps (Gigabit Ethernet) on fiber operation. +Only +.Ar full-duplex +mode is supported at this speed. +.It 1000baseT +Set 1000Mbps (Gigabit Ethernet) on copper operation. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation +.It half-duplex +Force half duplex operation +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh FILES +Two firmware files are necessary, for Tigon 1 and Tigon 2 devices. +These are loaded on demand +when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/tigon1 +.It Pa /etc/firmware/tigon2 +.El +.Sh DIAGNOSTICS +.Bl -diag +.It "ti0: couldn't map memory" +A fatal initialization error has occurred. +.It "ti0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "ti0: no memory for softc struct!" +The driver failed to allocate memory for per-device instance information +during initialization. +.It "ti0: failed to enable memory mapping!" +The driver failed to initialize PCI shared memory mapping. +This might happen if the card is not in a bus-master slot. +.It "ti0: no memory for jumbo buffers!" +The driver failed to allocate memory for jumbo frames during +initialization. +.It "ti0: bios thinks we're in a 64 bit slot, but we aren't" +The BIOS has programmed the NIC as though it had been installed in +a 64-bit PCI slot, but in fact the NIC is in a 32-bit slot. +This happens as a result of a bug in some BIOSes. +This can be worked around on the Tigon II, but +on the Tigon I initialization will fail. +.It "ti0: board self-diagnostics failed!" +The ROMFAIL bit in the CPU state register was set after system +startup, indicating that the on-board NIC diagnostics failed. +.It "ti0: unknown hwrev" +The driver detected a board with an unsupported hardware revision. +The +.Nm +driver supports revision 4 (Tigon 1) and revision 6 (Tigon 2) chips +and has firmware only for those devices. +.It "ti0: watchdog timeout -- resetting" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr sbus 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 3.0 . +.Ox +support first appeared in +.Ox 2.6 . +SBus support was added in +.Ox 4.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@bsdi.com . +SBus support was added by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/tipd.4 b/static/openbsd/man4/tipd.4 new file mode 100644 index 00000000..f357d8e5 --- /dev/null +++ b/static/openbsd/man4/tipd.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: tipd.4,v 1.2 2022/12/12 20:44:00 kettenis Exp $ +.\" +.\" Copyright (c) 2020 Patrick Wildt +.\" Copyright (c) 2022 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 12 2022 $ +.Dt TIPD 4 +.Os +.Sh NAME +.Nm tipd +.Nd TI USB Type-C power delivery controller +.Sh SYNOPSIS +.Cd "tipd* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the TI TPS6598x and CD321x Type-C power +delivery controllers. +It takes care of plug and unplug events on the USB Type-C port. +Additionally it enables power on the USB Type-C port when a sink +is connected to power attached devices. +.Sh SEE ALSO +.Xr iic 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/tipmic.4 b/static/openbsd/man4/tipmic.4 new file mode 100644 index 00000000..f144d315 --- /dev/null +++ b/static/openbsd/man4/tipmic.4 @@ -0,0 +1,51 @@ +.\" $OpenBSD: tipmic.4,v 1.2 2020/06/20 21:16:14 jmc Exp $ +.\" +.\" Copyright (c) 2018 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 20 2020 $ +.Dt TIPMIC 4 +.Os +.Sh NAME +.Nm tipmic +.Nd Intel Dollar Cove TI Power Management IC +.Sh SYNOPSIS +.Cd "tipmic* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Dq Intel +Dollar Cove TI Power Management ICs. +These devices have temperature and voltage sensors and provide power +management functionality. +Sensor values are made available to +.Xr acpi 4 +to support Thermal Zones. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr acpitz 4 , +.Xr iic 4 , +.Xr intro 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/titmp.4 b/static/openbsd/man4/titmp.4 new file mode 100644 index 00000000..9f6daa11 --- /dev/null +++ b/static/openbsd/man4/titmp.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: titmp.4,v 1.1 2021/06/23 15:32:40 kettenis Exp $ +.\" +.\" Copyright (c) 2005 Theo de Raadt +.\" Copyright (c) 2021 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 23 2021 $ +.Dt TITMP 4 +.Os +.Sh NAME +.Nm titmp +.Nd TI TMP451 temperature sensor +.Sh SYNOPSIS +.Cd "titmp* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the TI TMP451 temperature sensor. +The sensor possesses an internal temperature sensor and a link +to an external temperature sensor. +Both values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/tl.4 b/static/openbsd/man4/tl.4 new file mode 100644 index 00000000..6497936d --- /dev/null +++ b/static/openbsd/man4/tl.4 @@ -0,0 +1,142 @@ +.\" $OpenBSD: tl.4,v 1.22 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 1997, 1998 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $Id: tl.4,v 1.22 2013/07/16 16:05:49 schwarze Exp $ +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt TL 4 +.Os +.Sh NAME +.Nm tl +.Nd Texas Instruments ThunderLAN 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "tl* at pci?" +.Cd "lxtphy* at mii?" +.Cd "mlphy* at mii?" +.Cd "nsphy* at mii?" +.Cd "tlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI Ethernet adapters based on the Texas +Instruments ThunderLAN Ethernet controller chip. +This includes a large number of Compaq PCI-bus Ethernet adapters as well as +the integrated Ethernet controllers built in to several models +of Compaq Prosignia servers and Compaq Deskpro desktop machines. +This driver also supports the Olicom OC-2135/2138, OC-2325 and OC-2326 +10/100 TX UTP adapters and the Racore 8165 10/100baseTX and 8148 +10baseT/100baseTX/100baseFX multi-personality cards. +.Pp +The ThunderLAN controller has a standard MII interface that supports +up to 32 physical interface devices (PHYs). +It also has a built-in 10baseT PHY hardwired at MII address 31, which may be +used in some 10Mbps-only hardware configurations. +In 100Mbps configurations, a National Semiconductor DP83840A or other +MII-compliant PHY may be attached to the ThunderLAN's MII bus. +If a DP83840A or equivalent is available, the ThunderLAN chip can operate +at either 100Mbps or 10Mbps in either half-duplex or full-duplex modes. +The ThunderLAN's built-in PHY and the DP83840A also support autonegotiation. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +Note that this option is only available on those PHYs that support +autonegotiation. +Also, the PHY will not advertise those modes that have been explicitly +disabled using the following media options. +.It 10baseT +Set 10Mbps operation. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.It 10base5 +Enable AUI/BNC interface (useful only with the built-in PHY). +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation. +.It half-duplex +Force half duplex operation. +.It hw-loopback +Enable hardware loopback mode. +.El +.Pp +Note that the 100baseTX media type is only available if supported +by the PHY. +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "tl0: couldn't map memory" +A fatal initialization error has occurred. +.It "tl0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "tl0: device timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.It "tl0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.It "tl0: no memory for tx list" +The driver failed to allocate an mbuf for the transmitter ring when +allocating a pad buffer or collapsing an mbuf chain into a cluster. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr lxtphy 4 , +.Xr mlphy 4 , +.Xr netintro 4 , +.Xr nsphy 4 , +.Xr pci 4 , +.Xr tlphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 2.2 . +.Ox +support first appeared in +.Ox 2.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ctr.columbia.edu . diff --git a/static/openbsd/man4/tlphy.4 b/static/openbsd/man4/tlphy.4 new file mode 100644 index 00000000..72006957 --- /dev/null +++ b/static/openbsd/man4/tlphy.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: tlphy.4,v 1.10 2009/07/31 14:20:29 jmc Exp $ +.\" $NetBSD: tlphy.4,v 1.1 1998/11/04 05:53:59 thorpej Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 31 2009 $ +.Dt TLPHY 4 +.Os +.Sh NAME +.Nm tlphy +.Nd Texas Instruments ThunderLAN internal Ethernet PHY +.Sh SYNOPSIS +.Cd "tlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the internal PHY on TI ThunderLAN Ethernet interfaces. +The ThunderLAN PHY supports 10base5 (AUI) and 10base2 (BNC) on some +ThunderLAN implementations. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/tpm.4 b/static/openbsd/man4/tpm.4 new file mode 100644 index 00000000..83991628 --- /dev/null +++ b/static/openbsd/man4/tpm.4 @@ -0,0 +1,64 @@ +.\" $OpenBSD: tpm.4,v 1.3 2021/09/12 16:37:42 jmc Exp $ +.\" +.\" Copyright (c) 2010 Hans-Joerg Hoexer +.\" Copyright (c) 2016 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 12 2021 $ +.Dt TPM 4 +.Os +.Sh NAME +.Nm tpm +.Nd Trusted Platform Module device +.Sh SYNOPSIS +.Cd "tpm* at acpi?" +.Sh DESCRIPTION +The +.Nm +driver supports devices implementing the TPM Interface Spec 1.2. +.Pp +Supported devices include: +.Pp +.Bl -bullet -compact -offset indent +.It +Atmel 97SC3203 +.It +Broadcom BCM0102 +.It +Infineon IFX SLD 9630 TT 1.1 and IFX SLB 9635 TT 1.2 +.It +Intel INTC0102 +.It +Sinosun SNS SSX35 +.It +STM ST19WP18 +.It +Winbond WEC WPCT200 +.El +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was initially written by +.An Michael Shalayeff +and +.An Hans-Joerg Hoexer . +.Sh CAVEATS +Functionality is limited to instructing the device to save its state before a +system suspend. diff --git a/static/openbsd/man4/tpmr.4 b/static/openbsd/man4/tpmr.4 new file mode 100644 index 00000000..69758dd5 --- /dev/null +++ b/static/openbsd/man4/tpmr.4 @@ -0,0 +1,162 @@ +.\" $OpenBSD: tpmr.4,v 1.10 2021/07/28 19:19:38 benno Exp $ +.\" +.\" Copyright (c) 2019 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 28 2021 $ +.Dt TPMR 4 +.Os +.Sh NAME +.Nm tpmr +.Nd IEEE 802.1Q Two-Port MAC Relay interface +.Sh SYNOPSIS +.Cd "pseudo-device tpmr" +.Sh DESCRIPTION +The +.Nm +driver implements an 802.1Q (originally 802.1aj) Two-Port MAC Relay +(TPMR). +A TPMR is a simplified Ethernet bridge with exactly two member ports, +and it unconditionally relays Ethernet packets between those ports. +.Pp +.Nm +interfaces can be created at runtime using the +.Ic ifconfig tpmr Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +.Pp +Other forms of Ethernet bridging are available using the +.Xr bridge 4 +Ethernet bridge driver and the +.Xr veb 4 +Virtual Ethernet Bridge device. +Link aggregation of Ethernet interfaces can be achieved +using the +.Xr aggr 4 +and +.Xr trunk 4 +drivers. +.Sh IOCTLS +The following +.Xr ioctl 2 +calls and their structures are commonly use by +.Nm +and +.Xr bridge 4 : +.Pp +.Bl -bullet -offset indent -compact +.It +.Dv SIOCBRDGADD +.It +.Dv SIOCBRDGDEL +.El +.Sh EXAMPLES +.Nm +can be used to cross-connect Ethernet devices that support different +physical media. +For example, a device that supports a 100baseTX half-duplex connection +can be connected to a switch with 1000baseSX optical ports by using +.Nm +with a pair of physical network interfaces, each of which supports +the required media types. +If +.Xr fxp 4 +is used to connect to the 100baseTX device, and +.Xr em 4 +is used to connect to the 1000baseSX switch, the following configuration +can be used: +.Bd -literal -offset indent +# ifconfig tpmr0 create +# ifconfig tpmr0 add fxp0 add em0 +# ifconfig fxp0 up +# ifconfig em0 up +# ifconfig tpmr0 up +.Ed +.Pp +Multiple TPMRs can be chained to transport Ethernet traffic for a +pair of devices over another network. +Given two physically separate Ethernet switches, TPMRs can be used +as follows to provide a point-to-point Ethernet link between them. +.Nm +with the +.Cm link0 +flag set allows the use of the Link Aggregation Control Protocol (LACP) +or Spanning Tree Protocol (STP) by the switches to detect communication +failures or connectivity loops respectively, which is not possible +using +.Xr bridge 4 +as it filters those protocols. +.Pp +If Host A connected to Router B has the external IP address 192.0.2.10 +on em0, Host D connected to Router C has the external IP address +198.51.100.14 on em0, and both hosts have em1 connected to the +switches, the following configuration can be used to connect the +switches together. +.Xr etherip 4 +is used to transport the Ethernet packets over the IP network. +.Bd -literal +Switch X ---- Host A ---------- tunnel ----------- Host D ---- Switch E + \e / + \e / + +---- Router B ---- Router C ----+ +.Ed +.Pp +Create the +.Nm +and +.Xr etherip 4 +interfaces: +.Bd -literal -offset indent +# ifconfig etherip0 create +# ifconfig tpmr0 create link0 +.Ed +.Pp +Configure the etherip interface: +.Bd -literal -offset indent +(on Host A) # ifconfig etherip0 tunnel 192.0.2.10 198.51.100.14 up +(on Host D) # ifconfig etherip0 tunnel 198.51.100.14 192.0.2.10 up +.Ed +.Pp +Add the etherip interface and physical interface to the TPMR: +.Bd -literal -offset indent +# ifconfig tpmr0 add em1 add etherip0 up +.Ed +.Pp +An equivalent setup using MPLS pseudowires instead of IP as the +transport can be built using +.Xr mpw 4 +interfaces. +.Sh SEE ALSO +.Xr aggr 4 , +.Xr bridge 4 , +.Xr pf 4 , +.Xr trunk 4 , +.Xr veb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.\" .Sh STANDARDS +.\" .Rs +.\" .%T IEEE 802.1Q +.\" .Re +.\" .Rs +.\" .%T IEEE 802.1aj +.\" .Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . diff --git a/static/openbsd/man4/tqphy.4 b/static/openbsd/man4/tqphy.4 new file mode 100644 index 00000000..6d9270d6 --- /dev/null +++ b/static/openbsd/man4/tqphy.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: tqphy.4,v 1.8 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: tqphy.4,v 1.2 1999/09/05 00:27:43 soren Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt TQPHY 4 +.Os +.Sh NAME +.Nm tqphy +.Nd TDK Semiconductor 78Q2120 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "tqphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the TDK Semiconductor 78Q2120 PHY found in at least some +CardBus Ethernet cards and the 3Com 574 PCMCIA card. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/trm.4 b/static/openbsd/man4/trm.4 new file mode 100644 index 00000000..fa429852 --- /dev/null +++ b/static/openbsd/man4/trm.4 @@ -0,0 +1,77 @@ +.\" $OpenBSD: trm.4,v 1.11 2022/02/18 10:24:32 jsg Exp $ +.\" +.\" Copyright (c) 2001-2002, Ashley R. Martens and Kenneth R. Westerback. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt TRM 4 +.Os +.Sh NAME +.Nm trm +.Nd TRM-S1040 based PCI SCSI interface +.Sh SYNOPSIS +.Cd "trm* at pci?" +.Sh DESCRIPTION +The +.Nm +driver supports PCI SCSI host adapters based on Tekram's TRM-S1040 +chip, including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +Tekram DC395U/UW/F +.It +Tekram DC315/U +.El +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 , +.Xr uk 4 +.Pp +.Lk https://www.tekram.com +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written for +.Ox +by +.An Kenneth R. Westerback +and +.An Ashley R. Martens , +based on a +.Nx +driver by +.An Erich Chen , +which was ported to +.Ox +by +.An Martin Akesson . diff --git a/static/openbsd/man4/trunk.4 b/static/openbsd/man4/trunk.4 new file mode 100644 index 00000000..a4370ec9 --- /dev/null +++ b/static/openbsd/man4/trunk.4 @@ -0,0 +1,147 @@ +.\" $OpenBSD: trunk.4,v 1.33 2026/03/17 05:20:55 deraadt Exp $ +.\" +.\" Copyright (c) 2005, 2006 Reyk Floeter +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 17 2026 $ +.Dt TRUNK 4 +.Os +.Sh NAME +.Nm trunk +.Nd link aggregation and link failover interface +.Sh SYNOPSIS +.Cd "pseudo-device trunk" +.Sh DESCRIPTION +The +.Nm +interface allows aggregation of multiple network interfaces as one virtual +.Nm +interface. +.Pp +A +.Nm +interface can be created using the +.Ic ifconfig trunk Ns Ar N Ic create +command. +.Pp +The driver currently supports the trunk protocols +.Ic broadcast , +.Ic failover , +.Ic loadbalance , +.Ic none , +and +.Ic roundrobin +(the default). +The protocols determine which ports are used for outgoing traffic +and whether a specific port accepts incoming traffic. +The interface link state is used to validate if the port is active or +not. +.Bl -tag -width loadbalance +.It Ic broadcast +Sends frames to all ports of the trunk and receives frames on any +port of the trunk. +.It Ic failover +Sends and receives traffic only through the master port. +If the master port becomes unavailable, +the next active port is used. +The first interface added is the master port; +any interfaces added after that are used as failover devices. +.It Ic loadbalance +Distributes outgoing traffic through all active ports +and accepts incoming traffic from any active port. +A hash of the protocol header is used to maintain packet ordering. +The hash includes the Ethernet source and destination address and, if +available, the VLAN tag, and the IP source and destination address. +.It Ic none +This protocol is intended to do nothing: it disables any traffic without +disabling the +.Nm +interface itself. +.It Ic roundrobin +Distributes outgoing traffic through all active ports +and accepts incoming traffic from any active port. +A round-robin scheduler is used to aggregate the traffic. +.El +.Pp +The configuration can be done at runtime or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +.Pp +.Nm +does not implement +IEEE 802.1AX (formerly 802.3ad) Link Aggregation +.Va (LACP ) , +which is supported by +.Xr aggr 4 . +.Sh EXAMPLES +Create a simple round robin trunk with two +.Xr bge 4 +Gigabit Ethernet +interfaces: +.Bd -literal -offset indent +# ifconfig bge0 up +# ifconfig bge1 up +# ifconfig trunk0 trunkport bge0 trunkport bge1 \e + 192.168.1.1 netmask 255.255.255.0 +.Ed +.Pp +The following example uses an active failover trunk to set up roaming +between wired and wireless networks using two network devices. +Whenever the wired master interface is unplugged, the wireless failover +device will be used: +.Bd -literal -offset indent +# ifconfig em0 up +# ifconfig ath0 nwid my_net up +# ifconfig trunk0 trunkproto failover trunkport em0 trunkport ath0 \e + 192.168.1.1 netmask 255.255.255.0 +.Ed +.Sh SEE ALSO +.Xr aggr 4 , +.Xr inet 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 3.8 . +Support for 802.3ad Link Aggregation was added in +.Ox 4.4 +and removed in +.Ox 7.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Reyk Floeter Aq Mt reyk@openbsd.org . +.Sh CAVEATS +The trunk protocols +.Ic loadbalance +and +.Ic roundrobin +require a switch which supports IEEE 802.3ad static link aggregation; +otherwise protocols +such as +.Xr inet6 4 +duplicate address detection (DAD) +cannot properly deal with duplicate packets. +.Pp +The +.Nm +interface takes its MTU from the first +.Ic trunkport . +To avoid mismatches, adding a child interface with a different +MTU is not permitted. diff --git a/static/openbsd/man4/tsl.4 b/static/openbsd/man4/tsl.4 new file mode 100644 index 00000000..7ef78063 --- /dev/null +++ b/static/openbsd/man4/tsl.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: tsl.4,v 1.10 2015/10/02 09:29:02 sobrado Exp $ +.\" +.\" Copyright (c) 2005 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 2 2015 $ +.Dt TSL 4 +.Os +.Sh NAME +.Nm tsl +.Nd TAOS TSL2560/61 light sensor +.Sh SYNOPSIS +.Cd "tsl* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the TAOS TSL2560/61 light-to-digital +converters that transform light intensity into a digital signal +output. +These sensors contain a broadband photodiode and an +infrared-responding photodiode allowing the ambient light level to be +determined, as experienced by the human eye. +This illuminance (in lux) is made available through the +.Xr sysctl 8 +interface and can, for example, be used to adjust the backlight of LCD +screens to lighting conditions. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/tty.4 b/static/openbsd/man4/tty.4 new file mode 100644 index 00000000..a47a26e3 --- /dev/null +++ b/static/openbsd/man4/tty.4 @@ -0,0 +1,511 @@ +.\" $OpenBSD: tty.4,v 1.56 2024/08/16 16:10:27 florian Exp $ +.\" $NetBSD: tty.4,v 1.4 1996/03/19 04:26:01 paulus Exp $ +.\" +.\" Copyright (c) 1991, 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)tty.4 8.3 (Berkeley) 4/19/94 +.\" +.Dd $Mdocdate: August 16 2024 $ +.Dt TTY 4 +.Os +.Sh NAME +.Nm tty , +.Nm cua +.Nd general terminal interface +.Sh SYNOPSIS +.In sys/ioctl.h +.Sh DESCRIPTION +This section describes the interface to the terminal drivers +in the system. +.Ss Terminal Special Files +Each hardware terminal port (such as a serial port) on the system usually has a +terminal special device file associated with it in the directory +.Pa /dev/ +(for +example, +.Pa /dev/tty03 ) . +When a user logs into +the system on one of these hardware terminal ports, the system has already +opened the associated device and prepared the line for normal interactive +use (see +.Xr getty 8 ) . +There is also a special case of a terminal file that connects not to +a hardware terminal port, but to another program on the other side. +These special terminal devices are called +.Em ptys +and provide the mechanism necessary to give users the same interface to the +system when logging in over a network (using +.Xr ssh 1 +for example). +Even in these cases the details of how the terminal +file was opened and set up is already handled by special software +in the system. +Thus, users do not normally need to worry about the details of +how these lines are opened or used. +.Pp +For hardware terminal ports, dial-out is supported through matching +device nodes called calling units. +For instance, the terminal called +.Pa /dev/tty03 +would have a matching calling unit called +.Pa /dev/cua03 . +These two devices are normally differentiated by creating the calling +unit device node with a minor number 128 greater than the dial-in +device node. +Whereas the dial-in device (the +.Em tty ) +normally +requires a hardware signal to indicate to the system that it is active, +the dial-out device (the +.Em cua ) +does not, and hence can communicate unimpeded +with a device such as a modem, or with another system over a serial link. +This means that a process like +.Xr getty 8 +will wait on a dial-in device until a connection is established. +Meanwhile, a dial-out connection can be established on the dial-out +device (for the very same hardware terminal port) without disturbing +anything else on the system. +The +.Xr getty 8 +process does not even notice that anything is happening on the terminal +port. +If a connecting call comes in after the dial-out connection has finished, the +.Xr getty 8 +process will deal with it properly, without having noticed the +intervening dial-out action. +For more information on dial-out, see +.Xr cu 1 . +.Pp +When an interactive user logs in, the system prepares the line to +behave in a certain way (called a +.Em "line discipline" ) , +described in +.Xr stty 1 +at the command level, and in +.Xr termios 4 +at the programming level. +To change settings associated with a login terminal, +refer to the preceding man pages for the common cases. +The remainder of this man page is concerned with describing details of using +and controlling terminal devices at a low level, such as that possibly +required by a program wishing to provide features similar to those provided +by the system. +.Ss Line disciplines +A terminal file is used like any other file in the system in that +it can be opened, read, and written to using standard system +calls. +For each existing terminal file, there is a software processing module +called a +.Em "line discipline" +associated with it. +The +.Em "line discipline" +essentially glues the low level device driver code with the high +level generic interface routines (such as +.Xr read 2 +and +.Xr write 2 ) , +and is responsible for implementing the semantics associated +with the device. +When a terminal file is first opened by a program, the default +.Em "line discipline" +called the +.Dv termios +line discipline is associated with the file. +This is the primary line discipline that is used in most cases and provides +the semantics that users normally associate with a terminal. +When the +.Dv termios +line discipline is in effect, the terminal file behaves and is +operated according to the rules described in +.Xr termios 4 . +Refer to that man page for a full description of the terminal +semantics. +The operations described here +generally represent features common +across all +.Em "line disciplines" , +although some of these calls may not +make sense in conjunction with a line discipline other than +.Dv termios , +and some may not be supported by the underlying +hardware (or lack thereof, as in the case of ptys). +.Ss Terminal File Operations +All of the following operations are invoked using the +.Xr ioctl 2 +system call. +Refer to that man page for a description of the +.Em request +and +.Em argp +parameters. +In addition to the ioctl +.Em requests +defined here, the specific line discipline +in effect will define other +.Em requests +specific to it (actually +.Xr termios 4 +defines them as function calls, not ioctl +.Em requests ) . +The following section lists the available ioctl requests. +The name of the request, a description of its purpose, and the typed +.Em argp +parameter (if any) +are listed. +For example, the first entry says +.Pp +.D1 Em "TIOCSETD int *ldisc" +.Pp +and would be called on the terminal associated with +file descriptor zero by the following code fragment: +.Bd -literal + int ldisc; + + ldisc = TTYDISC; + ioctl(0, TIOCSETD, &ldisc); +.Ed +.Ss Terminal File Request Descriptions +.Bl -tag -width TIOCGWINSZ +.It Dv TIOCSETD Fa int *ldisc +Change to the new line discipline pointed to by +.Fa ldisc . +The available line disciplines currently available are: +.Pp +.Bl -tag -width TIOCGWINSZ -compact +.It TTYDISC +Termios interactive line discipline. +.It PPPDISC +Point-to-Point Protocol line discipline. +.It NMEADISC +NMEA 0183 line discipline. +.It MSTSDISC +Meinberg Standard Time String line discipline. +.El +.It Dv TIOCGETD Fa int *ldisc +Return the current line discipline in the integer pointed to by +.Fa ldisc . +.It Dv TIOCSBRK Fa void +Set the terminal hardware into BREAK condition. +.It Dv TIOCCBRK Fa void +Clear the terminal hardware BREAK condition. +.It Dv TIOCSDTR Fa void +Assert data terminal ready (DTR). +.It Dv TIOCCDTR Fa void +Clear data terminal ready (DTR). +.It Dv TIOCGPGRP Fa int *tpgrp +Return the current process group the terminal is associated +with in the integer pointed to by +.Fa tpgrp . +This is the underlying call that implements the +.Xr tcgetpgrp 3 +call. +.It Dv TIOCSPGRP Fa int *tpgrp +Associate the terminal with the process group (as an integer) pointed to by +.Fa tpgrp . +This is the underlying call that implements the +.Xr tcsetpgrp 3 +call. +.It Dv TIOCGETA Fa struct termios *term +Place the current value of the termios state associated with the +device in the termios structure pointed to by +.Fa term . +This is the underlying call that implements the +.Xr tcgetattr 3 +call. +.It Dv TIOCSETA Fa struct termios *term +Set the termios state associated with the device immediately. +This is the underlying call that implements the +.Xr tcsetattr 3 +call with the +.Dv TCSANOW +option. +.It Dv TIOCSETAW Fa struct termios *term +First wait for any output to complete, then set the termios state +associated with the device. +This is the underlying call that implements the +.Xr tcsetattr 3 +call with the +.Dv TCSADRAIN +option. +.It Dv TIOCSETAF Fa struct termios *term +First wait for any output to complete, clear any pending input, +then set the termios state associated with the device. +This is the underlying call that implements the +.Xr tcsetattr 3 +call with the +.Dv TCSAFLUSH +option. +.It Dv TIOCOUTQ Fa int *num +Place the current number of characters in the output queue in the +integer pointed to by +.Fa num . +.It Dv TIOCNOTTY Fa void +This call is obsolete but left for compatibility. +In the past, when a process that didn't have a controlling terminal +.Po +see +.Em The Controlling Terminal +in +.Xr termios 4 +.Pc +first opened a terminal device, it acquired that terminal as its +controlling terminal. +For some programs this was a hazard as they didn't want a controlling +terminal in the first place, and this provided a mechanism to disassociate +the controlling terminal from the calling process. +It +.Em must +be called by opening the file +.Pa /dev/tty +and calling +.Dv TIOCNOTTY +on that file descriptor. +.Pp +The current system does not allocate a controlling terminal to +a process on an +.Xr open 2 +call: there is a specific ioctl called +.Dv TIOCSCTTY +to make a terminal the controlling +terminal. +In addition, a program can +.Xr fork 2 +and call the +.Xr setsid 2 +system call which will place the process into its own session - which +has the effect of disassociating it from the controlling terminal. +This is the new and preferred method for programs to lose their controlling +terminal. +.It Dv TIOCSETVERAUTH Fa int *secs +Indicate that the current user has successfully authenticated to this session. +Future authentication checks may then be bypassed by performing a +.Dv TIOCCHKVERAUTH +check. +The verified authentication status will expire after +.Fa secs +seconds. +Only root may perform this operation. +.It Dv TIOCCLRVERAUTH Fa void +Clear any verified auth status associated with this session. +.It Dv TIOCCHKVERAUTH Fa void +Check the verified auth status of this session. +The calling process must have the same real user ID and +parent process as the process which called +.Dv TIOCSETVERAUTH . +A zero return indicates success. +.It Dv TIOCSTOP Fa void +Stop output on the terminal (like typing ^S at the keyboard). +.It Dv TIOCSTART Fa void +Start output on the terminal (like typing ^Q at the keyboard). +.It Dv TIOCSCTTY Fa void +Make the terminal the controlling terminal for the process (the process +must not currently have a controlling terminal). +.It Dv TIOCDRAIN Fa void +Wait until all output is drained. +.It Dv TIOCEXCL Fa void +Set exclusive use on the terminal. +No further opens are permitted except by root. +Of course, this means that programs that are run by root (or setuid) +will not obey the exclusive setting - which limits the usefulness +of this feature. +.It Dv TIOCNXCL Fa void +Clear exclusive use of the terminal. +Further opens are permitted. +.It Dv TIOCFLUSH Fa int *what +If the value of the int pointed to by +.Fa what +contains the +.Dv FREAD +bit as defined in +.In sys/fcntl.h , +then all characters in the input queue are cleared. +If it contains the +.Dv FWRITE +bit, then all characters in the output queue are cleared. +If the value of the integer is zero, then it behaves as if both the +.Dv FREAD +and +.Dv FWRITE +bits were set (i.e., clears both queues). +.It Dv TIOCGWINSZ Fa struct winsize *ws +Put the window size information associated with the terminal in the +.Va winsize +structure pointed to by +.Fa ws . +The window size structure contains the number of rows and columns (and pixels +if appropriate) of the devices attached to the terminal. +It is set by user software and is the means by which most full\&-screen +oriented programs determine the screen size. +.It Dv TIOCSWINSZ Fa struct winsize *ws +Set the window size associated with the terminal to be the value in +the +.Va winsize +structure pointed to by +.Fa ws +(see above). +.It Dv TIOCCONS Fa int *on +If +.Fa on +points to a non-zero integer, redirect kernel console output +.Po +see +.Xr printf 9 +.Pc +to this terminal. +If +.Fa on +points to a zero integer, redirect kernel console output back to the normal +console. +This is usually used on workstations to redirect kernel messages +to a particular window. +.It Dv TIOCMSET Fa int *state +The integer pointed to by +.Fa state +contains bits that correspond to modem state. +Following is a list of defined variables and the modem state they represent: +.Pp +.Bl -tag -width TIOCMXCTS -compact +.It TIOCM_LE +Line Enable. +.It TIOCM_DTR +Data Terminal Ready. +.It TIOCM_RTS +Request To Send. +.It TIOCM_ST +Secondary Transmit. +.It TIOCM_SR +Secondary Receive. +.It TIOCM_CTS +Clear To Send. +.It TIOCM_CAR +Carrier Detect. +.It TIOCM_CD +Carrier Detect (synonym). +.It TIOCM_RNG +Ring Indication. +.It TIOCM_RI +Ring Indication (synonym). +.It TIOCM_DSR +Data Set Ready. +.El +.Pp +This call sets the terminal modem state to that represented by +.Fa state . +Not all terminals may support this. +.It Dv TIOCMGET Fa int *state +Return the current state of the terminal modem lines as represented +above in the integer pointed to by +.Fa state . +.It Dv TIOCMBIS Fa int *state +The bits in the integer pointed to by +.Fa state +represent modem state as described above; however, the state is OR-ed +in with the current state. +.It Dv TIOCMBIC Fa int *state +The bits in the integer pointed to by +.Fa state +represent modem state as described above; however, each bit which is on +in +.Fa state +is cleared in the terminal. +.It Dv TIOCGTSTAMP Fa struct timeval *timeval +Return the (single) timestamp. +.It Dv TIOCSTSTAMP Fa struct tstamps *tstamps +Chooses the conditions which will cause the current system time to be +immediately copied to the terminal timestamp storage. +This is often used to determine exactly the moment at which one or +more of these events occurred, though only one can be monitored. +Only +.Dv TIOCM_CTS +and +.Dv TIOCM_CAR +are honoured in +.Va tstamps.ts_set +and +.Va tstamps.ts_clr ; +these indicate which raising and lowering events on the respective lines +should cause a timestamp capture. +.It Dv TIOCSFLAGS Fa int *state +The bits in the integer pointed to by +.Fa state +contain bits that correspond to serial port state. +Following is a list of defined variables and the serial port state they +represent: +.Pp +.Bl -tag -width TIOCFLAG_SOFTCAR -compact +.It TIOCFLAG_SOFTCAR +Ignore hardware carrier. +.It TIOCFLAG_CLOCAL +Set clocal on open. +.It TIOCFLAG_CRTSCTS +Set crtscts on open. +.It TIOCFLAG_MDMBUF +Set mdmbuf on open. +.El +.Pp +This call sets the serial port state to that represented by +.Fa state . +Not all serial ports may support this. +.It Dv TIOCGFLAGS Fa int *state +Return the current state of the serial port as represented +above in the integer pointed to by +.Fa state . +.It Dv TIOCSTAT Fa void +Causes the kernel to write a status message to the terminal that displays the +current load average, +the name of the command in the foreground, +its process ID, +the symbolic wait channel, +the number of user and system seconds used, +the percentage of CPU the process is getting, +and the resident set size of the process. +.El +.Sh FILES +.Bl -tag -width /dev/tty -compact +.It Pa /dev/tty +controlling terminal, if any +.El +.Sh SEE ALSO +.Xr cu 1 , +.Xr stty 1 , +.Xr tty 1 , +.Xr ioctl 2 , +.Xr pty 4 , +.Xr termios 4 , +.Xr ttys 5 , +.Xr getty 8 +.Sh HISTORY +A console typewriter device +.Pa /dev/tty +and asynchronous communication interfaces +.Pa /dev/tty[0-5] +first appeared in +.At v1 . +The cua support is inspired by similar support in SunOS. diff --git a/static/openbsd/man4/tun.4 b/static/openbsd/man4/tun.4 new file mode 100644 index 00000000..1c2ccdbf --- /dev/null +++ b/static/openbsd/man4/tun.4 @@ -0,0 +1,337 @@ +.\" $OpenBSD: tun.4,v 1.52 2024/11/18 22:33:58 dlg Exp $ +.\" +.\" Copyright (c) 2003 Marcus D. Watts All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, and the entire permission notice in its entirety, +.\" including the disclaimer of warranties. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote +.\" products derived from this software without specific prior +.\" written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, +.\" INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY +.\" AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL +.\" MARCUS D. WATTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS +.\" OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND +.\" ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR +.\" TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE +.\" USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 18 2024 $ +.Dt TUN 4 +.Os +.Sh NAME +.Nm tun , +.Nm tap +.Nd network tunnel pseudo-device +.Sh SYNOPSIS +.Cd "pseudo-device tun" +.Pp +.In sys/types.h +.In net/if_tun.h +.Sh DESCRIPTION +The +.Nm tun +pseudo-device driver provides character special devices for +communicating with the kernel network stack via the +.Nm tun +and +.Nm tap +network interfaces. +Packets sent to these interfaces can be read from the device special +file by a userland process and processed as desired. +Packets written to the device special file by the userland process +are injected back into the kernel networking subsystem. +.Pp +.Nm tun +and +.Nm tap +interfaces can be created at runtime using the +.Ic ifconfig iface Ns Ar N Ic create +command, or by opening the character special devices +.Pa /dev/tunN +or +.Pa /dev/tapN +respectively. +.Pp +The minor number of the device special files are associated with +the unit number of the network interfaces. +.Pp +Each device has an exclusive open property: it cannot be opened +if it is already open and in use by another process. +On the last close of the device all queued packets are discarded. +If the device was created by opening a device special file +it will be automatically destroyed. +The last close of a device special file associated with an interface +created via +.Xr ifconfig 8 +will be marked as not running and traffic sent out the will be dropped. +.Pp +Each read returns at most one packet; if insufficient +buffer space is provided, the packet is truncated. +Each write supplies exactly one packet. +Writes never block. +If the protocol queue is full, the packet is dropped, a +.Dq collision +is counted, and +.Er ENOBUFS +is returned. +.Pp +The following +.Xr ioctl 2 +special commands defined in +.In net/if_tun.h +are supported: +.Pp +.Bl -tag -width indent -compact +.It Dv TUNGIFINFO Fa "struct tuninfo *" +.It Dv TUNSIFINFO Fa "struct tuninfo *" +Get or set the interface characteristics. +.Bd -literal +/* iface info */ +struct tuninfo { + u_int mtu; + u_short type; + u_short flags; + u_int baudrate; +}; +.Ed +.Pp +.Va flags +and +.Va type +are set by the kernel when an interface is created, +and must be set to the same values that the kernel provided. +.Pp +.It Dv TUNSIFMODE Fa int * +Provided for backwards compatibility. +The flags set must match what the kernel initialised them to. +.Pp +.It Dv TUNSCAP Fa struct tun_capabilities * +Enable the prepending of network packets with a +.Vt struct tun_hdr +offload header, +and set which interface offload capabilities userland can +handle on behalf of the kernel. +.Bd -literal +struct tun_capabilities { + uint32_t tun_if_capabilities; +}; +.Ed +.Pp +The +.Fa tun_if_capabilities +field is set with IFCAP values from +.In net/if.h . +It is acceptable to enable the offload header without enabling any +interface offload capabilities. +.Pp +The prepending of network packets with a +.Vt struct tun_hdr +offload header is disabled, +and the interface offload capabilities are reset when the device +special file is closed. +.Pp +.It Dv TUNGCAP Fa struct tun_capabilities * +Get which interface offload capabilities are currently enabled. +If the interface has not been configured with +.Dv TUNSCAP +this command will fail with +.Er ENODEV . +.Pp +.It Dv TUNDCAP +Disable the prepending of network packets with the +.Vt struct tun_hdr +offload header, +and clear interface offload capabilities. +.El +.Pp +The generic ioctls +.Dv FIONREAD , +.Dv FIONBIO , +.Dv FIOASYNC , +.Dv FIOSETOWN , +.Dv FIOGETOWN +are also supported. +.Ss Point-to-Point Layer 3 tunnel interface (tun) +Each packet read from or written to a +.Nm tun +interface is prefixed with a tunnel header consisting of +a 4-byte network byte order integer containing the address family of +the packet. +.Nm tun +supports +.Dv AF_INET , +.Dv AF_INET6 , +and +.Dv AF_MPLS +packets. +.Ss Ethernet tunnel interface (tap) +Each packet read from or written to a +.Nm tap +interface is an Ethernet packet. +The Ethernet CRC at the end of the frame is not required. +.Pp +The device special files for +.Nm tap +interfaces support the following additional +.Xr ioctl 2 +commands: +.Pp +.Bl -tag -width indent -compact +.It Dv SIOCGIFADDR Fa uint8_t Ns [ETHER_ADDR_LEN] +.It Dv SIOCSIFADDR Fa uint8_t Ns [ETHER_ADDR_LEN] +Get or set the link layer address (MAC address) of the interface. +.El +.Ss Network offload support +When network offload support has been enabled with the +.Dv TUNSCAP +.Xr ioctl 2 +command, +.Va struct tun_hdr +is prepended to packets read from and written to the device special +file. +.Pp +The kernel will populate the offload header for reads from the +device special file depending on which interface offload capabilities +are enabled. +A program may use any offload feature when writing to the device +special file regardless of which interface offload capabilities are +enabled. +The offload header can be read from one device special file and +written directly to another without interpretation or modification. +.Bd -literal +struct tun_hdr { + uint16_t th_flags; + uint16_t th_pad; + uint16_t th_vtag; + uint16_t th_mss; +}; +.Ed +.Pp +The fields in the +.Va struct tun_hdr +are in host native byte order. +.Pp +The following flags can be set in +.Fa th_flags +to specify which offloads are requested for the current packet: +.Pp +.Bl -tag -width "TUN_H_ICMP_CSUM" -compact +.It Dv TUN_H_VTAG +.Fa th_vtag +is set. +.It Dv TUN_H_TCP_MSS +TCP segmentation offload is requested for the current packet. +The maximum segment size is specified in +.Fa th_mss . +.It Dv TUN_H_IPV4_CSUM +IPv4 header checksum calculation requested. +.It Dv TUN_H_TCP_CSUM +TCP checksum calculation requested. +.It Dv TUN_H_UDP_CSUM +UDP checksum calculation requested. +.It Dv TUN_H_ICMP_CSUM +ICMP checksum calculation requested. +.El +.Pp +Only one of +.Dv TUN_H_TCP_CSUM , +.Dv TUN_H_UDP_CSUM , +and +.Dv TUN_H_ICMP_CSUM +can be specified at a time. +.Dv TUN_H_VTAG +can only be used with +.Nm tap +interfaces. +.Pp +.Fa th_pad +should be set to 0 when writing to the device special file, and +ignored when reading from the device special file. +.Sh FILES +.Bl -tag -width /dev/tun* -compact +.It Pa /dev/tun* +.It Pa /dev/tap* +.El +.Sh ERRORS +If open fails, +.Xr errno 2 +may be set to one of: +.Bl -tag -width Er +.It Bq Er ENXIO +Not that many devices configured. +.\" The associated interface existed, but is being destroyed. +.It Bq Er EBUSY +Device was already open. +.El +.Pp +If a +.Xr write 2 +call fails, +.Xr errno 2 +is set to one of: +.Bl -tag -width Er +.It Bq Er EMSGSIZE +The packet supplied was too small or too large. +The maximum sized packet allowed is currently 16384 bytes. +.It Bq Er ENOMEM +There were no mbufs. +.\" .It Bq Er ENOBUFS +.\" The queue for the outgoing protocol is full. +.El +.Pp +.Xr ioctl 2 +commands may fail with: +.Bl -tag -width Er +.It Bq Er EINVAL +Invalid parameters were specified. +.It Bq Er ENOTTY +Unrecognized ioctl command. +.El +.Pp +A +.Xr read 2 +call may fail because of: +.Bl -tag -width Er +.It Bq Er EIO +The associated interface has been destroyed. +.It Bq Er EWOULDBLOCK +Non-blocking I/O was selected and no packets were available. +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr inet 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh HISTORY +.Nm tun +interfaces originally supported both Layer 3 and Ethernet packets +by reconfiguring the type of interface with +.Dv TUNSIFINFO . +Ethernet packet support was split into the separate +.Nm tap +interface in +.Ox 5.9 . +.Sh AUTHORS +.Nm tun +was written by +.An Julian Onions Aq Mt Julian.Onions@nexor.co.uk +at Nottingham University. +.Pp +The +.Nm tap +interface functionality was written by +.An Claudio Jeker Aq Mt claudio@openbsd.org . diff --git a/static/openbsd/man4/twe.4 b/static/openbsd/man4/twe.4 new file mode 100644 index 00000000..3c17da82 --- /dev/null +++ b/static/openbsd/man4/twe.4 @@ -0,0 +1,89 @@ +.\" $OpenBSD: twe.4,v 1.29 2014/11/15 14:41:02 bentley Exp $ +.\" +.\" Michael Shalayeff, 2000. Public Domain. +.\" +.Dd $Mdocdate: November 15 2014 $ +.Dt TWE 4 +.Os +.Sh NAME +.Nm twe +.Nd 3ware 5000/6000/7000/8000 series PATA/SATA RAID controller +.Sh SYNOPSIS +.Cd "twe* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for AMCC's 3ware 5000/6000/7000/8000 series PATA/SATA +RAID adapters. +These adapters were formerly known as +.Dq 3ware Escalade . +.Pp +These controllers support 2, 4, 8, or 12 ATA disk drives and provide RAID 0, +RAID 1, RAID 5, RAID 10, and JBOD configurations. +All the RAID set volume management is done via the card's BIOS. +.Pp +Even though the card uses ATA drives, this driver makes drives +and/or RAID sets appear as +.Xr sd 4 . +.Pp +The +.Nm +driver supports the following AMCC 3ware PATA/SATA RAID adapters: +.Pp +.Tn 5000 series , +.Tn 6000 series , +.Tn 7000-2 , +.Tn 7006-2 , +.Tn 7500-4LP , +.Tn 7500-8 , +.Tn 7500-12 , +.Tn 7506-4LP , +.Tn 7506-8 , +.Tn 7506-12 , +.Tn 8006-2LP , +.Tn 8500-4LP , +.Tn 8500-8 , +.Tn 8500-12 , +.Tn 8506-4LP , +.Tn 8506-8 , +.Tn 8506-8MI , +.Tn 8506-12 , +and +.Tn 8506-12MI . +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 , +.Xr sd 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Michael Shalayeff Aq Mt mickey@openbsd.org , +inspired by the +.Fx +driver by +.An Mike Smith Aq Mt msmith@freebsd.org . +.Sh BUGS +The card's BIOS seems to conflict with some other disk controllers +which have their own BIOS, if such devices are configured earlier +than this one. +To avoid this situation, place +.Nm +cards in the lowest numbered slot before other SCSI or RAID disk controllers. +.Pp +The current 3ware firmware is known to fail if a redundant configuration +is selected (RAID1 or RAID10) and the array is heavily used +(e.g. installation) before the controller has finished initializing the array. +In this case, create the array, boot the installation media, and +leave the array idle until all controller activity has ceased. +.Pp +None of the volume management or monitoring functions provided by the +card's firmware are supported due to the fact that information +on these functions is not public. diff --git a/static/openbsd/man4/txp.4 b/static/openbsd/man4/txp.4 new file mode 100644 index 00000000..d75b9281 --- /dev/null +++ b/static/openbsd/man4/txp.4 @@ -0,0 +1,122 @@ +.\" $OpenBSD: txp.4,v 1.23 2008/10/28 06:27:28 brad Exp $ +.\" +.\" Copyright (c) 2001 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: October 28 2008 $ +.Dt TXP 4 +.Os +.Sh NAME +.Nm txp +.Nd 3Com 3XP Typhoon/Sidewinder (3CR990) 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "txp* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Tn 3Com +.Tn Typhoon/Sidewinder +Fast Ethernet chipset, including the following: +.Pp +.Bl -bullet -offset indent -compact +.It +3Com 3CR990-TX-95 +.It +3Com 3CR990-TX-97 +.It +3Com 3CR990SVR95 +.It +3Com 3CR990SVR97 +.El +.Pp +The +.Nm +driver supports IPv4 receive IP/TCP/UDP checksum offload, IPv4 +transmit IP checksum offload, and VLAN tag insertion and stripping. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width 100baseTX +.It Cm autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It Cm 10baseT +Set 10Mbps operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It Cm full-duplex +Force full duplex operation. +.It Cm half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh FILES +The driver needs a firmware file, +which is loaded on demand when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/3c990 +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.9 . diff --git a/static/openbsd/man4/txphy.4 b/static/openbsd/man4/txphy.4 new file mode 100644 index 00000000..f5bdffa0 --- /dev/null +++ b/static/openbsd/man4/txphy.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: txphy.4,v 1.7 2007/05/31 19:19:52 jmc Exp $ +.\" +.\" Copyright (c) 1999 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt TXPHY 4 +.Os +.Sh NAME +.Nm txphy +.Nd Texas Instruments TNETE2101 10/100 Ethernet PHY +.Sh SYNOPSIS +.Cd "txphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the Texas Instruments TNETE2101 10/100 Ethernet PHYs. +These PHYs are found on a variety of Ethernet interfaces. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/uaq.4 b/static/openbsd/man4/uaq.4 new file mode 100644 index 00000000..de6647db --- /dev/null +++ b/static/openbsd/man4/uaq.4 @@ -0,0 +1,74 @@ +.\" $OpenBSD: uaq.4,v 1.4 2022/05/15 01:28:27 jmatthew Exp $ +.\" +.\" Copyright (c) 2021 Jonathan Matthew +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 15 2022 $ +.Dt UAQ 4 +.Os +.Sh NAME +.Nm uaq +.Nd Aquantia AQC111U/AQC112U 100/1Gb/2.5Gb/5Gb USB Ethernet device +.Sh SYNOPSIS +.Cd "uaq* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Ethernet adapters based on the Aquantia +AQC111U and AQC112U chipsets, including the following: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Aquantia AQtion USB to 5GbE Controller +.It ASIX USB 3.1 Gen1 to 5G Multi-Gigabit Ethernet Adapter +.It ASIX USB 3.1 Gen1 to 2.5G Multi-Gigabit Ethernet Adapter +.It QNAP QNA-UC5G1T USB to 5GbE Adapter +.It Sabrent NT-SS5G USB to 5GbE Adapter +.It StarTech USG5GA30 USB to 5GbE Adapter +.It TRENDnet TUC-ET5G USB-C 3.1 to 5GBASE-T Ethernet Adapter +.El +.Pp +The AQC111U and AQC112U contain an integrated Multi-Gig Ethernet MAC and +PHY, supporting 100, 1000, 2500 and, in the AQC111U, 5000Mbps operation. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr mii 4 , +.Xr netintro 4 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Jonathan Matthew Aq Mt jmatthew@openbsd.org . diff --git a/static/openbsd/man4/uark.4 b/static/openbsd/man4/uark.4 new file mode 100644 index 00000000..3ac5d5fc --- /dev/null +++ b/static/openbsd/man4/uark.4 @@ -0,0 +1,61 @@ +.\" $OpenBSD: uark.4,v 1.5 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt UARK 4 +.Os +.Sh NAME +.Nm uark +.Nd Arkmicro Technologies ARK3116 based USB serial adapter +.Sh SYNOPSIS +.Cd "uark* at uhub?" +.Cd "ucom* at uark?" +.Sh DESCRIPTION +The +.Nm +driver supports Arkmicro Technologies ARK3116 based serial adapters. +.Pp +The following devices should work with the +.Nm +driver: +.Bd -literal -offset indent +HL USB-RS232 +HugePine USB-UART +KQ-U8A Data Cable +Skymaster USB to RS232 +.Ed +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan Gray Aq Mt jsg@openbsd.org . +.Sh CAVEATS +Setting hardware flow control is not currently supported. +It is not yet known how to ask the hardware to send a break. +.Pp +Arkmicro Technologies do not reply to requests of documentation +for their products. diff --git a/static/openbsd/man4/uath.4 b/static/openbsd/man4/uath.4 new file mode 100644 index 00000000..ee636341 --- /dev/null +++ b/static/openbsd/man4/uath.4 @@ -0,0 +1,186 @@ +.\" $OpenBSD: uath.4,v 1.40 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2006 +.\" Damien Bergamini +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt UATH 4 +.Os +.Sh NAME +.Nm uath +.Nd Atheros USB IEEE 802.11a/b/g wireless network device +.Sh SYNOPSIS +.Cd "uath* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports USB 2.0 wireless network devices based on Atheros +Communications fifth generation AR5005UG and AR5005UX chipsets. +.Pp +The AR5005UG chipset is made of an AR5523 multiprotocol MAC/baseband processor +and an AR2112 Radio-on-a-Chip that can operate between 2300 and 2500MHz +(802.11b/g). +.Pp +The AR5005UX chipset is made of an AR5523 multiprotocol MAC/baseband processor +and an AR5112 dual band Radio-on-a-Chip that can operate between 2300 and +2500MHz (802.11b/g) or 4900 and 5850MHz (802.11a). +.Pp +The AR5005UG and AR5005UX chipsets both have an integrated 32-bit MIPS +R4000-class processor that runs a firmware and manages, among other things, +the automatic control of the transmit rate and the calibration of the radio. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +.Nm +supports hardware WEP. +It can be typically configured in one of three modes: +no encryption; 40-bit encryption; or 104-bit encryption. +It is strongly recommended that WEP +not be used as the sole mechanism +to secure wireless communication, +due to serious weaknesses in it. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The following firmware file is loaded when a device is plugged: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/uath-ar5523 +.El +.Pp +This firmware file is not freely redistributable. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh HARDWARE +The following adapters should work: +.Bl -column "TRENDware International TEW-444UB" "AR5005UX" -offset 6n +.It Em Adapter Ta Em Chipset +.\".It Belkin F6D3050 AR5005UX +.It Li "Compex WLU108AG" Ta AR5005UX +.It Li "Compex WLU108G" Ta AR5005UG +.\".It Li "D-Link DWL-AG132" Ta AR5005UX +.It Li "D-Link DWL-G132" Ta AR5005UG +.\".It Li "Edimax EW-7315Ug" Ta AR5005UG (AR2414???) +.\".It Li "Lancom USB-54ag" Ta AR5005UX +.\".It Li "NEC WL54TU" Ta AR5005UX +.It Li "IODATA WN-G54/US" Ta AR5005UG +.It Li "MELCO WLI-U2-KAMG54" Ta AR5005UX +.It Li "Netgear WG111T" Ta AR5005UG +.It Li "Netgear WG111U" Ta AR5005UX +.It Li "Netgear WPN111" Ta AR5005UG +.It Li "Olitec 000544" Ta AR5005UG +.It Li "Philips SNU6500" Ta AR5005UG +.It Li "PLANET WDL-U357" Ta AR5005UX +.\".It Li "Senao WUB-8004" Ta AR5005UX +.It Li "Siemens Gigaset 108" Ta AR5005UG +.It Li "SMC SMCWUSBT-G" Ta AR5005UG +.It Li "SMC SMCWUSBT-G2" Ta AR5005UG +.\".It Li "SparkLAN WL-685GS" Ta AR5005UG +.It Li "SparkLAN WL-785A" Ta AR5005UX +.It Li "TP-Link TL-WN620G" Ta AR5005UG +.It Li "TRENDware International TEW-444UB" Ta AR5005UG +.It Li "TRENDware International TEW-504UB" Ta AR5005UX +.It Li "Unex Technology UR054ag" Ta AR5005UX +.\".It Li "Wistron NeWeb DCUA-81" Ta AR5005UX +.\".It Li "Wistron NeWeb DRUA-81" Ta AR5005UG +.\".It Li "Wistron NeWeb DRUA-82" Ta AR5005UX +.\".It Li "ZyXEL G-200 v2" Ta AR5005UG +.It Li "ZyXEL XtremeMIMO M-202" Ta AR5005UX +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig uath0 scan +.Pp +The following +.Xr hostname.if 5 +example configures uath0 to join network +.Dq mynwid , +using WEP key +.Dq mywepkey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid nwkey mywepkey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "uath0: error N, could not read firmware ..." +For some reason, the driver was unable to read the firmware image from the +filesystem. +The file might be missing or corrupted. +.It "uath0: could not load firmware (error=...)" +An error occurred while attempting to upload the firmware to the onboard +MIPS R4000 processor. +.It "uath0: could not initialize adapter" +The firmware was uploaded successfully but did not initialize properly or +in time. +.It "uath0: could not send command 0xXX (error=...)" +An attempt to send a command to the firmware failed. +.It "uath0: timeout waiting for command reply" +A read command was sent to the firmware but the firmware failed to reply in +time. +.It "uath0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +Atheros Communications refuses to release any documentation for their products. +Atheros proprietary 108 Mbps mode (aka Super AG mode) is not supported. +.Pp +The +.Nm +driver does not attempt to do any regulation of radio frequencies. diff --git a/static/openbsd/man4/uaudio.4 b/static/openbsd/man4/uaudio.4 new file mode 100644 index 00000000..0c4c6be5 --- /dev/null +++ b/static/openbsd/man4/uaudio.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: uaudio.4,v 1.8 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: uaudio.4,v 1.5.4.1 1999/12/27 18:30:46 wrstuden Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt UAUDIO 4 +.Os +.Sh NAME +.Nm uaudio +.Nd USB audio devices +.Sh SYNOPSIS +.Cd "uaudio* at uhub?" +.Cd "audio* at uaudio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB audio class devices. +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.7 . diff --git a/static/openbsd/man4/ubcmtp.4 b/static/openbsd/man4/ubcmtp.4 new file mode 100644 index 00000000..25a1ecaf --- /dev/null +++ b/static/openbsd/man4/ubcmtp.4 @@ -0,0 +1,59 @@ +.\" $OpenBSD: ubcmtp.4,v 1.3 2020/08/21 17:42:45 mglocker Exp $ +.\" +.\" Copyright (c) 2014, joshua stein +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the copyright holder may not be used to endorse or +.\" promote products derived from this software without specific +.\" prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 21 2020 $ +.Dt UBCMTP 4 +.Os +.Sh NAME +.Nm ubcmtp +.Nd Broadcom trackpad mouse +.Sh SYNOPSIS +.Cd "ubcmtp* at uhub?" +.Cd "wsmouse* at ubcmtp? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides support for Broadcom multi-touch trackpads found on +newer Apple MacBook, MacBook Pro, and MacBook Air laptops. +.Sh SEE ALSO +.Xr uhub 4 , +.Xr usb 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . diff --git a/static/openbsd/man4/uberry.4 b/static/openbsd/man4/uberry.4 new file mode 100644 index 00000000..767e3a47 --- /dev/null +++ b/static/openbsd/man4/uberry.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: uberry.4,v 1.6 2015/04/02 14:24:02 jasper Exp $ +.\" +.\" Copyright (c) 2006 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 2 2015 $ +.Dt UBERRY 4 +.Os +.Sh NAME +.Nm uberry +.Nd Research In Motion BlackBerry +.Sh SYNOPSIS +.Cd "uberry* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides the most minimal support for the USB-connected +Research In Motion BlackBerry devices, permitting them to be +charged and powered from a USB port. +.Sh SEE ALSO +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Ox 4.1 . +.Sh BUGS +The +.Nm +driver is not able to charge a 7750 (USB cradle model) which has a +completely dead battery, and we do not know why. diff --git a/static/openbsd/man4/ubsa.4 b/static/openbsd/man4/ubsa.4 new file mode 100644 index 00000000..d8325144 --- /dev/null +++ b/static/openbsd/man4/ubsa.4 @@ -0,0 +1,82 @@ +.\" $OpenBSD: ubsa.4,v 1.23 2009/02/24 13:35:55 yuo Exp $ +.\" $NetBSD: ubsa.4,v 1.1 2002/10/08 13:18:42 augustss Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 24 2009 $ +.Dt UBSA 4 +.Os +.Sh NAME +.Nm ubsa +.Nd Belkin USB serial adapter +.Sh SYNOPSIS +.Cd "ubsa* at uhub?" +.Cd "ucom* at ubsa?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the USB-to-RS232 Bridge chip used by a variety of +serial adapters from Belkin and other vendors. +.Pp +Some 3G (UMTS/GPRS/GSM) +.Xr cardbus 4 +devices use a Belkin serial adapter and an +.Xr ohci 4 +controller to provide a common AT interface. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh HARDWARE +The +.Nm +driver supports the following adapters: +.Pp +.Bl -tag -width Dv -offset indent -compact +.It Axesstel MV100H +.It Belkin F5U103 +.It Belkin F5U120 +.It e-Tek Labs Kwik232 +.It GoHubs GoCOM232 +.It Peracom single port serial adapter +.It Qualcomm, Inc. ZTE AC8700 +.It Qualcomm, Inc. ZTE CDMA Technologies MSM +.El +.Sh SEE ALSO +.Xr cardbus 4 , +.Xr tty 4 , +.Xr ucom 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Fx 5.0 +and was ported to +.Ox 3.3 . diff --git a/static/openbsd/man4/ucc.4 b/static/openbsd/man4/ucc.4 new file mode 100644 index 00000000..675875ef --- /dev/null +++ b/static/openbsd/man4/ucc.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: ucc.4,v 1.1 2021/08/20 05:25:23 anton Exp $ +.\" +.\" Copyright (c) 2021 Anton Lindqvist +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 20 2021 $ +.Dt UCC 4 +.Os +.Sh NAME +.Nm ucc +.Nd Consumer Control keyboards +.Sh SYNOPSIS +.Cd "ucc* at uhidev?" +.Cd "wsbkd* at ucc? mux 1" +.Sh DESCRIPTION +The +.Nm +driver provides support for Consumer Control pseudo keyboards, often used to +expose audio and application launch keys. +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhidev 4 , +.Xr usb 4 , +.Xr wskbd 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Anton Lindqvist Aq Mt anton@openbsd.org . diff --git a/static/openbsd/man4/uchcom.4 b/static/openbsd/man4/uchcom.4 new file mode 100644 index 00000000..fc983d1b --- /dev/null +++ b/static/openbsd/man4/uchcom.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: uchcom.4,v 1.4 2024/05/15 01:41:18 kevlo Exp $ +.\" +.\" Copyright (c) 2007 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 15 2024 $ +.Dt UCHCOM 4 +.Os +.Sh NAME +.Nm uchcom +.Nd WinChipHead CH9102/343/341/340 based USB serial adapter +.Sh SYNOPSIS +.Cd "uchcom* at uhub?" +.Cd "ucom* at uchcom?" +.Sh DESCRIPTION +The +.Nm +driver supports WinChipHead CH9102/343/341/340 serial devices. +.Pp +The CH341/340 devices only support a variety of baud rates +up to 921600. +CH9102/343 devices support any baud rate up to 6 Mbps. +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Takuya SHIOZAKI Aq Mt tshiozak@netbsd.org +and ported to +.Ox +by +.An Jonathan Gray Aq Mt jsg@openbsd.org . diff --git a/static/openbsd/man4/ucom.4 b/static/openbsd/man4/ucom.4 new file mode 100644 index 00000000..5bec190e --- /dev/null +++ b/static/openbsd/man4/ucom.4 @@ -0,0 +1,96 @@ +.\" $OpenBSD: ucom.4,v 1.35 2024/05/15 01:41:18 kevlo Exp $ +.\" $NetBSD: ucom.4,v 1.3 2000/04/14 14:55:18 augustss Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 15 2024 $ +.Dt UCOM 4 +.Os +.Sh NAME +.Nm ucom +.Nd USB tty support +.Sh SYNOPSIS +.Cd "ucom* at moscom?" # MosChip Semiconductor MCS7703 +.Cd "ucom* at uark?" # Arkmicro Technologies +.Cd "ucom* at ubsa?" # Belkin +.Cd "ucom* at uchcom?" # WinChipHead CH9102/343/341/340 +.Cd "ucom* at ucycom?" # Cypress +.Cd "ucom* at uftdi?" # FTDI +.Cd "ucom* at uipaq?" # iPAQ +.Cd "ucom* at ukspan?" # Keyspan +.Cd "ucom* at umcs?" # MosChip Semiconductor multiport +.Cd "ucom* at umct?" # MCT +.Cd "ucom* at umodem?" # Standardized umodem +.Cd "ucom* at umsm?" # Qualcomm MSM +.Cd "ucom* at uplcom?" # Prolific PL-2303 +.Cd "ucom* at uscom?" # simple USB serial adapters +.Cd "ucom* at uslcom?" # Silicon Laboratories CP2101/CP2102 +.Cd "ucom* at uslhcom?" # Silicon Laboratories CP2110 +.Cd "ucom* at uticom?" # Texas Instruments TUSB3410 +.Cd "ucom* at uvisor?" # Handspring Visor +.Cd "ucom* at uvscom?" # SUNTAC Slipper U VS-10U +.Cd "ucom* at uxrcom?" # Exar XR21V1410 +.Sh DESCRIPTION +The +.Nm +driver attaches to USB modems, serial ports, and other devices that need +to look like a tty. +The +.Nm +driver behaves like a +.Xr tty 4 : +this means that normal programs such as +.Xr cu 1 +or +.Xr pppd 8 +can be used to access the device. +.Pp +The +.Va portno +locator can be used to decide which port to use for devices that have +multiple external ports. +.Sh FILES +.Bl -tag -width "/dev/ttyU?XX" -compact +.It Pa /dev/ttyU? +tty devices +.It Pa /dev/cuaU? +call out devices (see +.Xr tty 4 ) +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr tty 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver appeared in +.Nx 1.5 . +.Ox +support was added in +.Ox 2.7 . diff --git a/static/openbsd/man4/ucrcom.4 b/static/openbsd/man4/ucrcom.4 new file mode 100644 index 00000000..9604920b --- /dev/null +++ b/static/openbsd/man4/ucrcom.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: ucrcom.4,v 1.1 2019/05/12 00:49:30 jsg Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 12 2019 $ +.Dt UCRCOM 4 +.Os +.Sh NAME +.Nm ucrcom +.Nd Chromebook USB serial console +.Sh SYNOPSIS +.Cd "ucrcom* at uhub?" +.Cd "ucom* at ucrcom?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the serial console of some Chromebooks. +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/ucycom.4 b/static/openbsd/man4/ucycom.4 new file mode 100644 index 00000000..4c46b796 --- /dev/null +++ b/static/openbsd/man4/ucycom.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: ucycom.4,v 1.6 2018/10/08 09:49:12 sthen Exp $ +.\" $NetBSD: ucycom.4,v 1.1 2005/07/30 06:14:49 skrll Exp $ +.\" +.\" Copyright (c) 2005 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Nick Hudson +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: October 8 2018 $ +.Dt UCYCOM 4 +.Os +.Sh NAME +.Nm ucycom +.Nd Cypress microcontroller based USB serial adapter +.Sh SYNOPSIS +.Cd "ucycom* at uhidev?" +.Cd "ucom* at ucycom?" +.Sh DESCRIPTION +The +.Nm +driver supports +.Xr usb 4 +serial devices based on Cypress microcontrollers. +The following adapters are supported: +.Pp +.Bl -tag -width Dv -offset indent -compact +.It Various low-cost USB-RS232 adapters +.It DeLorme Earthmate GPS receiver +.El +.Pp +The driver acts as a bridge between +.Xr uhidev 4 +and the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhidev 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Nx +and later in +.Ox 4.0 . diff --git a/static/openbsd/man4/udav.4 b/static/openbsd/man4/udav.4 new file mode 100644 index 00000000..3f58633d --- /dev/null +++ b/static/openbsd/man4/udav.4 @@ -0,0 +1,109 @@ +.\" $OpenBSD: udav.4,v 1.17 2015/07/15 18:02:15 sobrado Exp $ +.\" $NetBSD: udav.4,v 1.1 2003/08/22 06:42:01 itojun Exp $ +.\" +.\" Copyright (c) 2003 +.\" Shingo WATANABE . All rights reserved. +.\" Copyright (c) 2014 +.\" Takayoshi SASANO . (RD9700 support) +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 15 2015 $ +.Dt UDAV 4 +.Os +.Sh NAME +.Nm udav +.Nd Davicom DM9601 10/100 USB Ethernet device +.Sh SYNOPSIS +.Cd "udav* at uhub?" +.Cd "amphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB +.Tn Ethernet +adapters based on the Davicom DM9601 USB-ether bridge chip. +.Pp +The +.Nm +driver supports the following adapters: +.Pp +.Bl -tag -width Dv -offset indent -compact +.It Tn Corega FEther USB-TXC +.It Tn HenTong WK-668 +.It Tn Konig CMP-NWUSB10 +.It Tn ShanTou ST268 +.It Tn ShanTou ZT6688 +.It Tn ShanTou ADM8515 +.El +.Pp +The +.Nm +driver also supports CoreChip RD9700. +As many of these units ship with the same MAC address, it is +highly recommended to use +.Xr ifconfig 8 +.Cm lladdr +to set the address manually, or +.Cm lladdr random +to assign a random address. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr amphy 4 , +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr mii 4 , +.Xr netintro 4 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T Davicom DM9601 data sheet +.%U http://www.davicom.com.tw/big5/download/Data%20Sheet/DM9601-DS-P01-930914.pdf +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Shingo WATANABE Aq Mt nabe@nabechan.org +and ported to +.Ox +by +.An Jonathan Gray Aq Mt jsg@openbsd.org . +.Pp +RD9700 support by +.An Takayoshi SASANO Aq Mt uaa@uaa.org.uk . +.Sh BUGS +The RD9700 sometimes lacks zero-length packets to terminate +USB transactions, which can cause USB IOERRORs. diff --git a/static/openbsd/man4/udcf.4 b/static/openbsd/man4/udcf.4 new file mode 100644 index 00000000..1e4d6ac9 --- /dev/null +++ b/static/openbsd/man4/udcf.4 @@ -0,0 +1,101 @@ +.\" $OpenBSD: udcf.4,v 1.27 2015/06/07 20:13:13 claudio Exp $ +.\" +.\" Copyright (c) 2006 - 2008 Marc Balmer +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 7 2015 $ +.Dt UDCF 4 +.Os +.Sh NAME +.Nm udcf +.Nd Gude ADS Expert mouseCLOCK USB timedelta sensor +.Sh SYNOPSIS +.Cd "udcf* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Gude ADS Expert mouseCLOCK USB and +the Expert mouseCLOCK USB II, receivers for the German DCF77. +While receivers for the British MSF time signal station are also +being made, +.Nm +lacks support for them. +.Pp +.Nm +implements a timedelta sensor and the delta (in nanoseconds) between the +received time information and the local time can be accessed through the +.Xr sysctl 8 +interface. +The clock type is indicated in the sensor description: +.Bl -tag -width "CRITICALXX" -offset indent +.It DCF77 +German DCF77 time signal station +(77.5 kHz longwave transmitter located in Mainflingen near Frankfurt). +.El +.Pp +The quality of the timedelta is reported as the sensor status: +.Bl -tag -width "CRITICALXX" -offset indent +.It UNKNOWN +No valid time information has been received yet. +.It OK +The time information is valid and the timedelta is safe to use for +applications like +.Xr ntpd 8 . +.It WARN +The time information is still valid, but no new time information has been +decoded for at least 5 minutes due to a reception or parity error. +The timedelta should be used with care. +.It CRITICAL +No valid time information has been received for more than 15 minutes since +the sensor state degraded from OK to WARN. +This is an indication that hardware should be checked +to see if it is still functional. +The timedelta will eventually degrade to a lie +as all computer internal clocks have a drift. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr ntpd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marc Balmer Aq Mt mbalmer@openbsd.org . +.Sh CAVEATS +DCF77 uses a 77.5 kHz long wave radio signal transmitted from near Frankfurt, +Germany. +Up to about 900 km, the radio signal can travel directly to the receiver, +providing a linearly increasing time offset based on distance. +Due to the curvature of the Earth, beyond this distance the signal must +bounce off the lower ionosphere (residing at approximately 70 km elevation +during the day, and 90 km at night), thus causing a non-linearly increasing +time offset which can only be roughly calculated using trigonometry. +Since the distance and transmission geometry is not known, +the clock receivers and +.Nm +driver currently make no effort to calculate this offset. +We simply assume that the offset is small. +.Pp +In Germany, the train system uses DCF77 clocks. +As the distance from Frankfurt increases, +trains can be expected to run later. diff --git a/static/openbsd/man4/udl.4 b/static/openbsd/man4/udl.4 new file mode 100644 index 00000000..0c9e8120 --- /dev/null +++ b/static/openbsd/man4/udl.4 @@ -0,0 +1,79 @@ +.\" $OpenBSD: udl.4,v 1.24 2023/05/10 22:23:25 jmc Exp $ +.\" +.\" Copyright (c) 2009 Marcus Glocker +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 10 2023 $ +.Dt UDL 4 +.Os +.Sh NAME +.Nm udl +.Nd DisplayLink DL-120/DL-160 USB display devices +.Sh SYNOPSIS +.Cd "udl* at uhub?" +.Cd "wsdisplay* at udl?" +.Sh DESCRIPTION +The +.Nm +driver supports USB display devices based on the DisplayLink DL-120/DL-160 +graphic chip. +.Sh HARDWARE +The following devices should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Century Corp. Japan Plus One LCD-8000U +.It Century Corp. Japan Plus One LCD-4300U +.It DisplayLink USB to DVI +.It ForwardVideo EasyCAP008 USB to DVI +.It HP USB 2.0 Docking Station (FQ834) +.It HP USB Graphics Adapter (NL571) +.It IOGEAR USB 2.0 External DVI (GUC2020) +.It Koenig CMP-USBVGA10 and CMP-USBVGA11 +.It Lenovo 45K5296 USB to DVI +.It Lenovo ThinkVision LT1421 +.It Lilliput UM-70 +.It Nanovision MiMo UM-710 and UM-740 +.It Rextron VCUD60 USB to DVI +.It Samsung LD220 +.It StarTech CONV-USB2DVI +.It Sunweit USB to DVI +.It Toshiba Video Dock +.It Unitek Y-2240 USB to DVI +.It VideoHome NBdock1920 +.El +.Sh FILES +The device can process compressed data (Huffman pixel difference method) +to reduce the USB payload. +To generate the compressed data, +the driver needs to load a Huffman table, +which is stored in the following binary file: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/udl_huffman +.El +.Pp +If the Huffman table can't be loaded, the driver will fall back to +uncompressed mode. +.Sh SEE ALSO +.Xr intro 4 , +.Xr usb 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.6 . +.Sh AUTHORS +.An Marcus Glocker Aq Mt mglocker@openbsd.org diff --git a/static/openbsd/man4/udp.4 b/static/openbsd/man4/udp.4 new file mode 100644 index 00000000..3a00302a --- /dev/null +++ b/static/openbsd/man4/udp.4 @@ -0,0 +1,143 @@ +.\" $OpenBSD: udp.4,v 1.13 2015/09/10 17:55:21 schwarze Exp $ +.\" $NetBSD: udp.4,v 1.3 1994/11/30 16:22:41 jtc Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)udp.4 8.1 (Berkeley) 6/5/93 +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt UDP 4 +.Os +.Sh NAME +.Nm udp +.Nd Internet User Datagram Protocol +.Sh SYNOPSIS +.In sys/socket.h +.In netinet/in.h +.Ft int +.Fn socket AF_INET SOCK_DGRAM 0 +.Ft int +.Fn socket AF_INET6 SOCK_DGRAM 0 +.Sh DESCRIPTION +.Tn UDP +is a simple, unreliable datagram protocol which is used +to support the +.Dv SOCK_DGRAM +abstraction for the Internet +protocol family. +.Tn UDP +sockets are connectionless, and are +normally used with the +.Xr sendto 2 +and +.Xr recvfrom 2 +calls, though the +.Xr connect 2 +call may also be used to fix the destination for future +packets (in which case the +.Xr recv 2 +or +.Xr read 2 +and +.Xr send 2 +or +.Xr write 2 +system calls may be used). +.Pp +.Tn UDP +address formats are identical to those used by +.Tn TCP . +In particular +.Tn UDP +provides a port identifier in addition +to the normal Internet address format. +Note that the +.Tn UDP +port +space is separate from the +.Tn TCP +port space (i.e. a +.Tn UDP +port +may not be +.Dq connected +to a +.Tn TCP +port). +In addition broadcast packets may be sent (assuming the underlying network +supports this) by using a reserved +.Dq broadcast address ; +this address +is network interface dependent. +.Pp +Options at the +.Tn IP +transport level may be used with +.Tn UDP ; +see +.Xr ip 4 +or +.Xr ip6 4 . +.Sh DIAGNOSTICS +A socket operation may fail with one of the following errors returned: +.Bl -tag -width [EADDRNOTAVAIL] +.It Bq Er EISCONN +when trying to establish a connection on a socket which +already has one, or when trying to send a datagram with the destination +address specified and the socket is already connected; +.It Bq Er ENOTCONN +when trying to send a datagram, but +no destination address is specified, and the socket hasn't been +connected; +.It Bq Er ENOBUFS +when the system runs out of memory for +an internal data structure; +.It Bq Er EADDRINUSE +when an attempt +is made to create a socket with a port which has already been +allocated; +.It Bq Er EADDRNOTAVAIL +when an attempt is made to create a +socket with a network address for which no network interface +exists. +.El +.Sh SEE ALSO +.Xr getsockopt 2 , +.Xr recv 2 , +.Xr send 2 , +.Xr socket 2 , +.Xr inet 4 , +.Xr inet6 4 , +.Xr ip 4 , +.Xr ip6 4 , +.Xr netintro 4 +.Sh HISTORY +The +.Nm +protocol appeared in +.Bx 4.2 . diff --git a/static/openbsd/man4/udsbr.4 b/static/openbsd/man4/udsbr.4 new file mode 100644 index 00000000..01460e2d --- /dev/null +++ b/static/openbsd/man4/udsbr.4 @@ -0,0 +1,60 @@ +.\" $OpenBSD: udsbr.4,v 1.7 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: udsbr.4,v 1.1 2002/01/02 03:15:03 augustss Exp $ +.\" +.\" Copyright (c) 2002 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt UDSBR 4 +.Os +.Sh NAME +.Nm udsbr +.Nd D-Link DSB-R100 USB radio device +.Sh SYNOPSIS +.Cd "udsbr* at uhub?" +.Cd "radio* at udsbr?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the D-Link DSB-R100 USB radio. +.Pp +The device is accessed through the +.Xr radio 4 +driver. +.Pp +The DSB-R100 is a rather poor radio and the only feedback that +you can get from the radio is if it has a stereo signal or not. +.Sh SEE ALSO +.Xr intro 4 , +.Xr radio 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.2 . diff --git a/static/openbsd/man4/ufshci.4 b/static/openbsd/man4/ufshci.4 new file mode 100644 index 00000000..4b1cf54c --- /dev/null +++ b/static/openbsd/man4/ufshci.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: ufshci.4,v 1.3 2024/07/31 10:07:33 mglocker Exp $ +.\" +.\" Copyright (c) 2023 Marcus Glocker +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.Dd $Mdocdate: July 31 2024 $ +.Dt UFSHCI 4 +.Os +.Sh NAME +.Nm ufshci +.Nd Universal Flash Storage Host Controller Interface +.Sh SYNOPSIS +.Cd "ufshci* at acpi?" +.Cd "ufshci* at fdt?" +.Cd "ufshci* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Universal Flash Storage (UFS) Host Controllers +conforming to the JESD223C and JESD220C version 2.1 specifications. +.Pp +UFS uses NAND flash, and is based on the SCSI architectural model. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr intro 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marcus Glocker Aq Mt mglocker@openbsd.org . diff --git a/static/openbsd/man4/uftdi.4 b/static/openbsd/man4/uftdi.4 new file mode 100644 index 00000000..f45a91f7 --- /dev/null +++ b/static/openbsd/man4/uftdi.4 @@ -0,0 +1,64 @@ +.\" $OpenBSD: uftdi.4,v 1.29 2014/01/12 03:07:41 deraadt Exp $ +.\" $NetBSD: uftdi.4,v 1.3 2001/01/13 20:53:22 nathanw Exp $ +.\" +.\" Copyright (c) 2000 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 12 2014 $ +.Dt UFTDI 4 +.Os +.Sh NAME +.Nm uftdi +.Nd FTDI USB serial adapter +.Sh SYNOPSIS +.Cd "uftdi* at uhub?" +.Cd "ucom* at uftdi?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various serial adapters based on the FTDI +FT8U100AX, FT8U232AM, FT8U245AM, FT232B/H/R, FT245B/R, FT2232C/D/H/L, +FT4232H and FT-X series chips. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver appeared in +.Nx 1.5 . +.Ox +support was added in +.Ox 2.9 . diff --git a/static/openbsd/man4/ugen.4 b/static/openbsd/man4/ugen.4 new file mode 100644 index 00000000..ebf11e44 --- /dev/null +++ b/static/openbsd/man4/ugen.4 @@ -0,0 +1,294 @@ +.\" $OpenBSD: ugen.4,v 1.19 2022/03/31 17:27:21 naddy Exp $ +.\" $NetBSD: ugen.4,v 1.7 1999/07/30 01:32:05 augustss Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt UGEN 4 +.Os +.Sh NAME +.Nm ugen +.Nd USB generic device support +.Sh SYNOPSIS +.Cd "ugen* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for all USB devices that do not have +a special driver. +It supports access to all parts of the device, but not in a way that is as +convenient as a special purpose driver. +.Pp +There can be up to 127 USB devices connected to a USB bus. +Each USB device can have up to 16 endpoints. +Each of these endpoints will communicate in one of four different modes: +control, isochronous, bulk, or interrupt. +Each of the endpoints will have a different device node. +The four least significant bits in the minor device number determine which +endpoint the device accesses and the rest of the bits determine which +USB device. +.Pp +If an endpoint address is used both for input and output, the device +can be opened for both read or write. +.Pp +To find out what endpoints exist there are a series of +.Xr ioctl 2 +operations available for the control endpoint that return the USB descriptors +of the device, configurations, interfaces, and endpoints. +.Pp +The control transfer mode can only happen on the control endpoint, +which is always endpoint 0. +Control requests are issued by +.Xr ioctl 2 +calls. +.\" .Pp +.\" The isochronous transfer mode can be in or out depending on the +.\" endpoint. To perform I/O on an isochronous endpoint +.\" .Xr read 2 +.\" and +.\" .Xr write 2 +.\" should be used. +.\" Before any I/O operations can take place, the transfer rate in +.\" bytes/second has to be set. This is done with +.\" .Xr ioctl 2 +.\" .Dv USB_SET_ISO_RATE . +.\" Performing this call sets up a buffer corresponding to +.\" about 1 second of data. +.Pp +The bulk transfer mode can be in or out depending on the +endpoint. +To perform I/O on a bulk endpoint +.Xr read 2 +and +.Xr write 2 +should be used. +All I/O operations on a bulk endpoint are unbuffered. +.Pp +The interrupt transfer mode can only be in. +To perform input from an interrupt endpoint +.Xr read 2 +should be used. +A moderate amount of buffering is done by the driver. +.Pp +All endpoints handle the following +.Xr ioctl 2 +calls: +.Pp +.Bl -tag -width indent -compact +.It Dv USB_SET_SHORT_XFER (int) +Allow short read transfer. +Normally a transfer from the device which is shorter than the request +specified is reported as an error. +.Pp +.It Dv USB_SET_TIMEOUT (int) +Set the timeout on the device operations, the time is specified +in milliseconds. +The value 0 is used to indicate that there is no timeout. +.El +.Pp +The control endpoint (endpoint 0) handles the following +.Xr ioctl 2 +calls: +.Pp +.Bl -tag -width indent -compact +.It Dv USB_GET_CONFIG (int) +Get the device configuration number. +.Pp +.It Dv USB_SET_CONFIG (int) +Set the device into the given configuration number. +This operation can only be performed when the control endpoint +is the sole open endpoint. +.Pp +.It Dv USB_GET_ALTINTERFACE (struct usb_alt_interface) +Get the alternative setting number for the interface with the given +index. +The +.Fa uai_config_index +is ignored in this call. +.Bd -literal +struct usb_alt_interface { + int uai_config_index; + int uai_interface_index; + int uai_alt_no; +}; +.Ed +.Pp +.It Dv USB_SET_ALTINTERFACE (struct usb_alt_interface) +Set the alternative setting to the given number in the interface with the +given index. +The +.Fa uai_config_index +is ignored in this call. +.Pp +This operation can only be performed when no endpoints for the interface +are open. +.Pp +.It Dv USB_GET_NO_ALT (struct usb_alt_interface) +Return the number of different alternate settings in the +.Fa uai_alt_no +field. +.Pp +.It Dv USB_GET_DEVICE_DESC (usb_device_descriptor_t) +Return the device descriptor. +.Pp +.It Dv USB_GET_CONFIG_DESC (struct usb_config_desc) +Return the descriptor for the configuration with the given index. +For convenience the current configuration can be specified by +.Dv USB_CURRENT_CONFIG_INDEX . +.Bd -literal +struct usb_config_desc { + int ucd_config_index; + usb_config_descriptor_t ucd_desc; +}; +.Ed +.Pp +.It Dv USB_GET_INTERFACE_DESC (struct usb_interface_desc) +Return the interface descriptor for an interface specified by its +configuration index, interface index, and alternative index. +For convenience the current alternative can be specified by +.Dv USB_CURRENT_ALT_INDEX . +.Bd -literal +struct usb_interface_desc { + int uid_config_index; + int uid_interface_index; + int uid_alt_index; + usb_interface_descriptor_t uid_desc; +}; +.Ed +.Pp +.It Dv USB_GET_ENDPOINT_DESC (struct usb_endpoint_desc) +Return the endpoint descriptor for the endpoint specified by its +configuration index, interface index, alternative index, and +endpoint index. +.Bd -literal +struct usb_endpoint_desc { + int ued_config_index; + int ued_interface_index; + int ued_alt_index; + int ued_endpoint_index; + usb_endpoint_descriptor_t ued_desc; +}; +.Ed +.Pp +.It Dv USB_GET_FULL_DESC (struct usb_full_desc) +Return all the descriptors for the given configuration. +.Bd -literal +struct usb_full_desc { + int ufd_config_index; + u_int ufd_size; + u_char *ufd_data; +}; +.Ed +.Pp +The +.Fa ufd_data +field should point to a memory area of the size given in the +.Fa ufd_size +field. +The proper size can be determined by first issuing a +.Dv USB_GET_CONFIG_DESC +and inspecting the +.Fa wTotalLength +field. +.Pp +.It Dv USB_DO_REQUEST +Send a USB request to the device on the control endpoint. +Any data sent to/from the device is located at +.Fa ucr_data . +The size of the transferred data is determined from the +.Fa ucr_request . +The +.Fa ucr_addr +field is ignored in this call. +.Bd -literal +struct usb_ctl_request { + int ucr_addr; + usb_device_request_t ucr_request; + void *ucr_data; + int ucr_flags; +#define USBD_SHORT_XFER_OK 0x04 /* allow short reads */ + int ucr_actlen; /* actual length transferred */ +}; +.Ed +.Pp +This is a dangerous operation in that it can perform arbitrary operations +on the device. +Some of the most dangerous (e.g., changing the device address) are not +allowed. +.Pp +.It Dv USB_GET_DEVICEINFO (struct usb_device_info) +Get an information summary for the device. +This call will not issue any USB transactions. +.El +.Pp +Note that there are two different ways of addressing configurations, interfaces, +alternatives, and endpoints: by index or by number. +The index is the ordinal number (starting from 0) of the descriptor +as presented by the device. +The number is the respective number of the entity as found in its descriptor. +Enumeration of descriptors use the index, getting and setting typically uses +numbers. +.Pp +Example: +All endpoints (except the control endpoint) for the current configuration +can be found by iterating the +.Fa interface_index +from 0 to +.Fa config_desc->bNumInterfaces-1 +and for each of these iterating the +.Fa endpoint_index +from 0 to +.Fa interface_desc->bNumEndpoints-1 . +The +.Fa config_index +should be set to +.Dv USB_CURRENT_CONFIG_INDEX +and +.Fa alt_index +should be set to +.Dv USB_CURRENT_ALT_INDEX . +.Sh FILES +.Bl -tag -width Pa +.It Pa /dev/ugenN.EE +Endpoint +.Pa EE +of device +.Pa N . +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.6 . +.Sh BUGS +The driver is not yet finished; there is no access to isochronous endpoints. diff --git a/static/openbsd/man4/ugl.4 b/static/openbsd/man4/ugl.4 new file mode 100644 index 00000000..6cd13def --- /dev/null +++ b/static/openbsd/man4/ugl.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: ugl.4,v 1.1 2013/11/17 20:51:58 sasano Exp $ +.\" $NetBSD: upl.4,v 1.3 2000/08/12 17:59:12 augustss Exp $ +.\" +.\" Copyright (c) 2000 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 17 2013 $ +.Dt UGL 4 +.Os +.Sh NAME +.Nm ugl +.Nd Genesys Logic based host-to-host adapters +.Sh SYNOPSIS +.Cd "ugl* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Genesys Logic GL620USB-A based host-to-host +USB connectors. +.Pp +The +.Nm +driver appears as an Ethernet interface and should be configured with +.Xr ifconfig 8 +in the same way as other Ethernet interfaces. +It does not support different media types or options. +.Sh SEE ALSO +.Xr netintro 4 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/ugold.4 b/static/openbsd/man4/ugold.4 new file mode 100644 index 00000000..1868b7ff --- /dev/null +++ b/static/openbsd/man4/ugold.4 @@ -0,0 +1,80 @@ +.\" $OpenBSD: ugold.4,v 1.11 2024/07/27 17:31:49 miod Exp $ +.\" +.\" Copyright (c) 2013 Takayoshi SASANO +.\" Copyright (c) 2013 Martin Pieuchot +.\" Copyright (c) 2015 Joerg Jung +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 27 2024 $ +.Dt UGOLD 4 +.Os +.Sh NAME +.Nm ugold +.Nd TEMPer gold HID thermometer and hygrometer +.Sh SYNOPSIS +.Cd "ugold* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCsensors TEMPer gold devices. +The following devices are supported by the +.Nm +driver: +.Bl -column "RDing TEMPerHUM1V1.0" "1 Temperature" -offset indent +.It Em "Device" Ta Em "Sensors" +.It Li "RDing TEMPer1V1.2" Ta "1 Temperature" +.It Li "RDing TEMPerV1.4" Ta "1 Temperature" +.It Li "RDing TEMPer1F_V4.1" Ta "1 Temperature (external)" +.It Li "RDing TEMPer2_V4.1" Ta "2 Temperature (internal/external)" +.It Li "RDing TEMPerGold_V3.1" Ta "1 Temperature" +.It Li "RDing TEMPerGold_V3.4" Ta "1 Temperature" +.It Li "RDing TEMPerGold_V3.5" Ta "1 Temperature" +.It Li "RDing TEMPerHum1V1.0" Ta "1 Temperature and 1 Humidity" +.It Li "RDing TEMPerHum1V1.2" Ta "1 Temperature and 1 Humidity" +.It Li "RDing TEMPerHUM_V3.9" Ta "1 Temperature and 1 Humidity" +.It Li "RDing TEMPerHUM_V4.0" Ta "1 Temperature and 1 Humidity" +.It Li "RDing TEMPerHUM_V4.1" Ta "1 Temperature and 1 Humidity" +.It Li "RDing TEMPer1F_H1V1.5F" Ta "1 Temperature and 1 Humidity" +.It Li "RDing TEMPerX_V3.1" Ta "1 Temperature and 1 Humidity" +.It Li "RDing TEMPerX_V3.3" Ta "1 Temperature and 1 Humidity" +.El +.Pp +The driver possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhidev 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Takayoshi SASANO Aq Mt uaa@openbsd.org +and +.An Martin Pieuchot Aq Mt mpi@openbsd.org . +.Pp +TEMPerHUM support was added by +.An Joerg Jung Aq Mt jung@openbsd.org . +.Sh CAVEATS +Linearization and temperature compensation for the humidity values of the +TEMPerHUM1V1.0 is not implemented. diff --git a/static/openbsd/man4/uguru.4 b/static/openbsd/man4/uguru.4 new file mode 100644 index 00000000..8c2fb4d9 --- /dev/null +++ b/static/openbsd/man4/uguru.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: uguru.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2010 Mikko Tolmunen +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: July 16 2013 $ +.Dt UGURU 4 +.Os +.Sh NAME +.Nm uguru +.Nd ABIT temperature, voltage and fan sensors +.Sh SYNOPSIS +.Cd "uguru0 at isa? port 0xe0" +.Sh DESCRIPTION +The +.Nm +driver provides support for the microcontroller +found in various +.Tn ABIT +motherboards which serves as +the gateway chip between system management software +and hardware. +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.8 +.Sh AUTHORS +The +.Nm +driver was written by +.An Mikko Tolmunen Aq Mt oskari@sefirosu.org . +.Sh BUGS +Interrupt support is unimplemented. diff --git a/static/openbsd/man4/uhci.4 b/static/openbsd/man4/uhci.4 new file mode 100644 index 00000000..9a5f58b2 --- /dev/null +++ b/static/openbsd/man4/uhci.4 @@ -0,0 +1,60 @@ +.\" $OpenBSD: uhci.4,v 1.13 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: uhci.4,v 1.3 1999/09/12 18:47:12 kleink Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt UHCI 4 +.Os +.Sh NAME +.Nm uhci +.Nd USB Universal Host Controller Interface +.Sh SYNOPSIS +.Cd "uhci* at cardbus?" +.Cd "uhci* at pci?" +.Cd "usb* at uhci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Universal Host Controller Interface, +which provides an interface to +.Xr usb 4 +devices. +.Sh SEE ALSO +.Xr cardbus 4 , +.Xr ehci 4 , +.Xr intro 4 , +.Xr ohci 4 , +.Xr pci 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.7 . diff --git a/static/openbsd/man4/uhid.4 b/static/openbsd/man4/uhid.4 new file mode 100644 index 00000000..447a6ee8 --- /dev/null +++ b/static/openbsd/man4/uhid.4 @@ -0,0 +1,181 @@ +.\" $OpenBSD: uhid.4,v 1.20 2021/09/15 04:59:26 anton Exp $ +.\" $NetBSD: uhid.4,v 1.13 2001/12/29 14:41:59 augustss Exp $ +.\" +.\" Copyright (c) 1999, 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 15 2021 $ +.Dt UHID 4 +.Os +.Sh NAME +.Nm uhid +.Nd USB generic HID support +.Sh SYNOPSIS +.Cd "uhid* at uhidev?" +.Pp +.In dev/usb/usb.h +.Sh DESCRIPTION +The +.Nm +driver provides support for all HID (Human Interface Device) interfaces +in USB devices that do not have a special driver. +.Pp +The device handles the following +.Xr ioctl 2 +calls: +.Bl -tag -width indent +.It Dv USB_GET_DEVICEINFO Fa struct usb_device_info *devinfo +Get summarized information about the device. +.It Dv USB_GET_REPORT_ID Fa int *repid +Get the report identifier used by this HID report. +.It Dv USB_GET_REPORT_DESC Fa struct usb_ctl_report_desc *repdesc +Get the HID report descriptor. +Using this descriptor the exact layout and meaning of data to/from +the device can be found. +The report descriptor is delivered without any processing. +.Bd -literal +struct usb_ctl_report_desc { + int ucrd_size; + u_char ucrd_data[1024]; /* filled data size will vary */ +}; +.Ed +.It Dv USB_GET_REPORT Fa struct usb_ctl_report *rep +Get a report from the device without waiting for data on +the interrupt pipe. +The +.Fa ucr_report +field indicates which report is requested. +It should be +.Dv UHID_INPUT_REPORT , +.Dv UHID_OUTPUT_REPORT , +or +.Dv UHID_FEATURE_REPORT . +.Bd -literal +struct usb_ctl_report { + int ucr_report; + u_char ucr_data[1024]; /* filled data size will vary */ +}; +.Ed +.It Dv USB_SET_REPORT Fa struct usb_ctl_report *rep +Set a report in the device. +The +.Dv report +field indicates which report is to be set. +It should be +.Dv UHID_INPUT_REPORT , +.Dv UHID_OUTPUT_REPORT , +or +.Dv UHID_FEATURE_REPORT . +.El +.Pp +The generic ioctls +.Dv FIONBIO +and +.Dv FIOASYNC +are supported by +.Nm . +.Pp +Use +.Xr read 2 +to get data from the device. +Data should be read in chunks of the size prescribed by the report descriptor. +.Pp +Use +.Xr write 2 +to send data to the device. +Equivalent to issuing an +.Xr ioctl 2 +.Dv USB_SET_REPORT +request with the report set to +.Dv UHID_OUTPUT_REPORT . +Data should be written in chunks of the size prescribed by the report +descriptor. +.Sh FILES +.Bl -tag -width /dev/tun* -compact +.It Pa /dev/uhid* +.El +.Sh ERRORS +If +.Xr ioctl 2 +fails, +.Xr errno 2 +is set to one of the following: +.Bl -tag -width Er +.It Bq Er EIO +The device could not fulfill a +.Dv USB_GET_REPORT +or +.Dv USB_SET_REPORT +request. +.It Bq Er EINVAL +The report specified by the +.Fa ucr_report +field in a +.Dv USB_GET_REPORT +or +.Dv USB_SET_REPORT +request was invalid. +.It Bq Er ENOTTY +Unrecognized command. +.El +.Pp +If +.Xr read 2 +fails, +.Xr errno 2 +is set to one of the following: +.Bl -tag -width Er +.It Bq Er EIO +The device has already been detached. +.It Bq Er EWOULDBLOCK +Non-blocking I/O was selected and no data were available. +.El +.Pp +If +.Xr write 2 +fails, +.Xr errno 2 +is set to one of the following: +.Bl -tag -width Er +.It Bq Er EIO +The device has already been detached or the same device does not have a +corresponding output report. +.It Bq Er EMSGSIZE +The size of the supplied data exceeds the size of the output report. +.El +.Sh SEE ALSO +.Xr usbhidctl 1 , +.Xr usbhid 3 , +.Xr intro 4 , +.Xr uhidev 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.6 . diff --git a/static/openbsd/man4/uhidev.4 b/static/openbsd/man4/uhidev.4 new file mode 100644 index 00000000..2f6bb7f0 --- /dev/null +++ b/static/openbsd/man4/uhidev.4 @@ -0,0 +1,102 @@ +.\" $OpenBSD: uhidev.4,v 1.15 2021/08/20 05:25:23 anton Exp $ +.\" $NetBSD: uhidev.4,v 1.2 2001/12/29 03:06:41 augustss Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 20 2021 $ +.Dt UHIDEV 4 +.Os +.Sh NAME +.Nm uhidev +.Nd USB Human Interface Device support +.Sh SYNOPSIS +.Cd "uhidev* at uhub?" +.Cd "fido* at uhidev?" +.Cd "ucc* at uhidev?" +.Cd "ucycom* at uhidev?" +.Cd "ugold* at uhidev?" +.Cd "uhid* at uhidev?" +.Cd "uhidpp* at uhidev?" +.Cd "ujoy* at uhidev?" +.Cd "ukbd* at uhidev?" +.Cd "ums* at uhidev?" +.Cd "umstc* at uhidev?" +.Cd "umt* at uhidev?" +.Cd "uoaklux* at uhidev?" +.Cd "uoakrh* at uhidev?" +.Cd "uoakv* at uhidev?" +.Cd "upd* at uhidev?" +.Cd "uslhcom* at uhidev?" +.Cd "uthum* at uhidev?" +.Cd "utpms* at uhidev?" +.Cd "utrh* at uhidev?" +.Cd "utwitch* at uhidev?" +.Cd "uwacom* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver handles all Human Interface Devices. +Each HID device can have several components, e.g., a keyboard and a mouse. +These components use different report identifiers (a byte) to +distinguish which one data is coming from. +The +.Nm +driver has other drivers attached that handle particular +kinds of devices and +.Nm +only dispatches data to them based on the report id. +.Sh SEE ALSO +.Xr fido 4 , +.Xr intro 4 , +.Xr ucc 4 , +.Xr ucycom 4 , +.Xr ugold 4 , +.Xr uhid 4 , +.Xr uhidpp 4 , +.Xr ujoy 4 , +.Xr ukbd 4 , +.Xr ums 4 , +.Xr umstc 4 , +.Xr umt 4 , +.Xr uoaklux 4 , +.Xr uoakrh 4 , +.Xr uoakv 4 , +.Xr upd 4 , +.Xr usb 4 , +.Xr uslhcom 4 , +.Xr uthum 4 , +.Xr utpms 4 , +.Xr utrh 4 , +.Xr utwitch 4 , +.Xr uwacom 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 3.2 . diff --git a/static/openbsd/man4/uhidpp.4 b/static/openbsd/man4/uhidpp.4 new file mode 100644 index 00000000..d2cda804 --- /dev/null +++ b/static/openbsd/man4/uhidpp.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: uhidpp.4,v 1.3 2021/08/17 18:08:51 anton Exp $ +.\" +.\" Copyright (c) 2021 Anton Lindqvist +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 17 2021 $ +.Dt UHIDPP 4 +.Os +.Sh NAME +.Nm uhidpp +.Nd Logitech HID++ devices +.Sh SYNOPSIS +.Cd "uhidpp* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Logitech HID++ devices. +It exposes a collection of battery sensor values which are made available +through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhidev 4 , +.Xr usb 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Anton Lindqvist Aq Mt anton@openbsd.org . diff --git a/static/openbsd/man4/uipaq.4 b/static/openbsd/man4/uipaq.4 new file mode 100644 index 00000000..a1c67184 --- /dev/null +++ b/static/openbsd/man4/uipaq.4 @@ -0,0 +1,73 @@ +.\" $OpenBSD: uipaq.4,v 1.10 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: uipaq.4,v 1.6 2001/05/22 00:21:25 jhawk Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt UIPAQ 4 +.Os +.Sh NAME +.Nm uipaq +.Nd iPAQ USB units +.Sh SYNOPSIS +.Cd "uipaq* at uhub?" +.Cd "ucom* at uipaq?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the USB serial emulation provided +by the iPAQ devices. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh HARDWARE +The +.Nm +driver supports the following adapters: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Alltel UTStarcom PPC6700 +.It Asus MyPal A730 +.It Casio BE300 +.It Compaq IPaq PocketPC +.It HP iPAQ 22xx/Jornada 548 +.It HP Jornada 568 +.It HTC SmartPhone +.El +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Ox +support was added in +.Ox 3.8 . diff --git a/static/openbsd/man4/ujoy.4 b/static/openbsd/man4/ujoy.4 new file mode 100644 index 00000000..b05b36e5 --- /dev/null +++ b/static/openbsd/man4/ujoy.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: ujoy.4,v 1.2 2021/01/27 14:58:06 jmc Exp $ +.\" +.\" Copyright (c) 2020 Thomas Frohwein +.\" Copyright (c) 2020 Bryan Steele +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 27 2021 $ +.Dt UJOY 4 +.Os +.Sh NAME +.Nm ujoy +.Nd USB joystick/gamecontroller +.Sh SYNOPSIS +.Cd "ujoy* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB joysticks and other gamecontrollers. +They are Human Interface Devices (HID) which can be accessed via the +.Pa /dev/ujoy/N +interface. +.Pp +The driver is compatible with +.Xr read 2 , +and a subset of +.Xr ioctl 2 +operations of the generic +.Xr uhid 4 +device. +.Sh FILES +.Bl -tag -width /dev/ujoy/* -compact +.It Pa /dev/ujoy/* +.El +.Sh SEE ALSO +.Xr uhid 4 , +.Xr uhidev 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . diff --git a/static/openbsd/man4/uk.4 b/static/openbsd/man4/uk.4 new file mode 100644 index 00000000..0cb01316 --- /dev/null +++ b/static/openbsd/man4/uk.4 @@ -0,0 +1,76 @@ +.\" $OpenBSD: uk.4,v 1.19 2024/12/21 01:00:31 jsg Exp $ +.\" $NetBSD: uk.4,v 1.3 1996/10/20 23:15:26 explorer Exp $ +.\" +.\" Copyright (c) 1996 +.\" Julian Elischer . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: December 21 2024 $ +.Dt UK 4 +.Os +.Sh NAME +.Nm uk +.Nd SCSI user-level driver +.Sh SYNOPSIS +.Cd "uk* at scsibus?" +.Sh DESCRIPTION +The +.Nm +driver provides support for a +process to address devices on the SCSI bus for which there is no configured +driver. +.Pp +A SCSI adapter must also be separately configured into the system +before this driver makes sense. +.Sh IOCTLS +The +.Nm +driver has no ioctls of its own but rather acts as a medium for the +generic +.Xr scsi 4 +ioctls. +These are described in +.In sys/scsiio.h . +.Sh FILES +.Bl -tag -width /dev/uk[0-255] -compact +.It Pa /dev/uk[0-255] +uk{x} is the 'xth' unknown device found. +.El +.Sh DIAGNOSTICS +All +.Xr scsi 4 +debug ioctls work on +.Nm +devices. +.Sh SEE ALSO +.Xr cd 4 , +.Xr ch 4 , +.Xr scsi 4 , +.Xr sd 4 , +.Xr st 4 +.Sh HISTORY +The +.Nm +driver appeared in +.Nx 1.0 . diff --git a/static/openbsd/man4/ukbd.4 b/static/openbsd/man4/ukbd.4 new file mode 100644 index 00000000..3c14d2ec --- /dev/null +++ b/static/openbsd/man4/ukbd.4 @@ -0,0 +1,270 @@ +.\" $OpenBSD: ukbd.4,v 1.22 2019/05/11 14:19:16 abieber Exp $ +.\" $NetBSD: ukbd.4,v 1.10 2001/12/29 15:12:32 augustss Exp $ +.\" +.\" Copyright (c) 1999, 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.\" Copyright (c) 1999 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 11 2019 $ +.Dt UKBD 4 +.Os +.Sh NAME +.Nm ukbd +.Nd USB keyboard support +.Sh SYNOPSIS +.Cd "ukbd* at uhidev?" +.Cd "wskbd* at ukbd?" +.Cd "option UKBD_LAYOUT=XXX" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB keyboards i.e. HID devices in the +.Dq keyboard +class. +Access to the keyboard is through the +.Xr wskbd 4 +driver. +.Pp +The +.Nm +driver supports a number of different key mappings which +can be chosen from with the kernel option +.Dq UKBD_LAYOUT +at compile time or with the utility +.Xr wsconsctl 8 +(variable: +.Dq keyboard.encoding ) +at runtime. +Other mappings can be used if the whole keymap is replaced by means of +.Xr wsconsctl 8 . +The built-in mappings are at this time: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It KB_BE +.Pq be +Belgium French. +.It KB_BR +.Pq br +Brazilian. +.It KB_CF +.Pq cf +Canadian French. +.It KB_DE +.Pq de +German with +.Dq dead accents . +.It KB_DK +.Pq dk +Danish with +.Dq dead accents . +.It KB_ES +.Pq es +Spanish. +.It KB_FR +.Pq fr +French. +.It KB_FR | KB_APPLE +.Pq fr.apple +French for +.Tn Apple +black USB keyboards. +.It KB_FR | KB_DVORAK +.Pq fr.dvorak +French keyboard with +.Dq Dvorak-Bepo +layout. +.It KB_HU +.Pq hu +Hungarian. +.It KB_IS +.Pq is +Icelandic with +.Dq dead accents . +.It KB_IT +.Pq it +Italian. +.It KB_JP +.Pq jp +Japanese. +.It KB_LA +.Pq la +Latinamerican. +.It KB_LT +.Pq \< +Lithuanian in +.Dq ISO 8859-13 . +.It KB_LV +.Pq \&lv +Latvian +.It KB_NL +.Pq \&nl +Dutch with +.Dq dead accents . +.It KB_NO +.Pq no +Norwegian with +.Dq dead accents . +.It KB_PL +.Pq pl +Polish in +.Dq ISO 8859-2 . +.It KB_PT +.Pq pt +Portuguese. +.It KB_PT | KB_APPLE +.Pq pt.apple +Portuguese for +.Tn Apple +black USB keyboards. +.It KB_RU +.Pq ru +Russian in +.Dq KOI8 . +.It KB_SF +.Pq sf +Swiss French with +.Dq dead accents . +.It KB_SG +.Pq sg +Swiss German with +.Dq dead accents . +.It KB_SI +.Pq si +Slovenian. +.It KB_SV +.Pq sv +Swedish with +.Dq dead accents . +.It KB_TR +.Pq tr +Turkish in +.Dq ISO 8859-9 +with +.Dq dead accents . +.It KB_UA +.Pq ua +Ukrainian in +.Dq KOI8 . +.It KB_UK +.Pq uk +British. +.It KB_US +.Pq us +English/US keyboard mapping (default). +.It KB_US | KB_COLEMAK +.Pq us.colemak +English/US keyboard with +.Dq Colemak +layout. +.It KB_US | KB_DVORAK +.Pq us.dvorak +English/US keyboard with +.Dq Dvorak +layout. +.El +.Pp +The KB_DE, KB_DK, KB_IS, KB_NO, KB_SF, KB_SG, KB_SV and KB_TR +mappings can be used in the KB_NODEAD +.Pq .nodead +variant. +This switches off the +.Dq dead accents . +.Pp +The KB_BE, KB_FR, KB_FR | KB_APPLE, KB_FR | KB_DVORAK, KB_JP, KB_UK, KB_US, +KB_US | KB_DVORAK and KB_US | KB_COLEMAK +mappings can be modified +to swap the left Control and the Caps Lock keys by the +KB_SWAPCTRLCAPS variant bit or the +.Dq .swapctrlcaps +suffix. +.Pp +The KB_METAESC +.Pq .metaesc +option can be applied to any layout. +If set, keys pressed together +with the ALT modifier are prefixed by an ESC character. +(Standard behaviour is to add 128 to the ASCII value.) +.Sh EXAMPLES +To set a German keyboard layout without +.Dq dead accents +and sending an ESC character before the key symbol if the ALT +key is pressed simultaneously, use +.Ic wsconsctl keyboard.encoding=de.nodead.metaesc . +To set it at kernel build time, add the following +to the kernel configuration file: +.Bd -literal -offset indent +option UKBD_LAYOUT="(KB_DE|KB_NODEAD|KB_METAESC)" +.Ed +.Sh SEE ALSO +.Xr usbhidctl 1 , +.Xr intro 4 , +.Xr uhidev 4 , +.Xr usb 4 , +.Xr wskbd 4 , +.Xr wsconsctl 8 +.Sh HISTORY +The +.Nm +driver +appeared in +.Nx 1.4 . +.Ox +support was added in +.Ox 2.8 . +.Sh BUGS +The +.Nm +driver is brought into action rather late in the boot process, so if +it is used as the console driver then +.Xr ddb 4 +is not usable until late in the boot. +.Pp +The list of built-in mappings doesn't follow any logic. +It grew as people submitted what they needed. diff --git a/static/openbsd/man4/ukphy.4 b/static/openbsd/man4/ukphy.4 new file mode 100644 index 00000000..3343956e --- /dev/null +++ b/static/openbsd/man4/ukphy.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: ukphy.4,v 1.11 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: ukphy.4,v 1.1 1999/09/08 13:59:07 soren Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt UKPHY 4 +.Os +.Sh NAME +.Nm ukphy +.Nd generic/unknown IEEE 802.3u Ethernet PHY +.Sh SYNOPSIS +.Cd "ukphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the basic functionality of most Ethernet PHYs. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 +.Sh CAVEATS +In areas where the programming interface for PHYs differ, such +as detecting the currently active medium, this driver often +does not work optimally. +When available, it is best to use a PHY-specific driver. diff --git a/static/openbsd/man4/ukspan.4 b/static/openbsd/man4/ukspan.4 new file mode 100644 index 00000000..f672b006 --- /dev/null +++ b/static/openbsd/man4/ukspan.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: ukspan.4,v 1.3 2020/02/17 19:33:51 jasper Exp $ +.\" Copyright (c) 2019 Cody Cutler +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 17 2020 $ +.Dt UKSPAN 4 +.Os +.Sh NAME +.Nm ukspan +.Nd Keyspan USB serial adapter +.Sh SYNOPSIS +.Cd "ukspan* at uhub?" +.Cd "ucom* at ukspan?" +.Sh DESCRIPTION +The +.Nm +driver supports the TrippLite Keyspan USA-19HS serial adapter, which is made +accessible through +.Xr ucom 4 . +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Cody Cutler Aq Mt ccutler@csail.mit.edu . diff --git a/static/openbsd/man4/ulpt.4 b/static/openbsd/man4/ulpt.4 new file mode 100644 index 00000000..d2d5a8d6 --- /dev/null +++ b/static/openbsd/man4/ulpt.4 @@ -0,0 +1,86 @@ +.\" $OpenBSD: ulpt.4,v 1.13 2013/02/04 11:42:36 stsp Exp $ +.\" $NetBSD: ulpt.4,v 1.4 1999/08/23 12:32:19 augustss Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: February 4 2013 $ +.Dt ULPT 4 +.Os +.Sh NAME +.Nm ulpt +.Nd USB printer support +.Sh SYNOPSIS +.Cd "ulpt* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB printers that follow the printer +bi- or uni-directional protocol. +The bits in the minor number select various features of the driver. +.Bl -column "Minor Bit" "Functionxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -offset indent +.It Em "Minor Bit" Ta Em Function +.It 64 Ta "Do not initialize the device on the port." +.El +.Sh FILES +.Bl -tag -width Pa +.It Pa /dev/ulpt? +.El +.Pp +For some HP LaserJet printer models (1000, 1005, 1018, 1020), the driver needs +at least version 1.0 of the following firmware files, which are loaded when a +printer is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It /etc/firmware/ulpt-hp1000 +.It /etc/firmware/ulpt-hp1005 +.It /etc/firmware/ulpt-hp1018 +.It /etc/firmware/ulpt-hp1020 +.El +.Pp +These firmware files are not free because HP refuses to grant +distribution rights. +As a result, even though +.Ox +includes the driver, the firmware files cannot be included and +users have to download these files on their own. +A port which can download and install the firmware can be found in +.Pa /usr/ports/sysutils/firmware/ulpt . +.Sh SEE ALSO +.Xr intro 4 , +.Xr lpt 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Nx 1.4 . +.Ox +support was added in +.Ox 2.7 . diff --git a/static/openbsd/man4/umass.4 b/static/openbsd/man4/umass.4 new file mode 100644 index 00000000..6847323f --- /dev/null +++ b/static/openbsd/man4/umass.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: umass.4,v 1.8 2021/06/14 06:27:22 jsg Exp $ +.\" $NetBSD: umass.4,v 1.1 1999/08/29 17:26:22 augustss Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 14 2021 $ +.Dt UMASS 4 +.Os +.Sh NAME +.Nm umass +.Nd USB mass storage support +.Sh SYNOPSIS +.Cd "umass* at uhub?" +.\" .Cd "atapibus* at umass?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB mass storage class devices. +.Sh SEE ALSO +.Xr scsi 4 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr disklabel 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Fx 4.0 . +.Ox +support was added in +.Ox 2.7 . diff --git a/static/openbsd/man4/umb.4 b/static/openbsd/man4/umb.4 new file mode 100644 index 00000000..c7ff19e1 --- /dev/null +++ b/static/openbsd/man4/umb.4 @@ -0,0 +1,95 @@ +.\" $OpenBSD: umb.4,v 1.19 2024/05/23 08:06:22 kevlo Exp $ +.\" +.\" Copyright (c) 2016 genua mbH +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 23 2024 $ +.Dt UMB 4 +.Os +.Sh NAME +.Nm umb +.Nd USB Mobile Broadband Interface Model (MBIM) +.Sh SYNOPSIS +.Cd "umb* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB MBIM devices. +.Pp +MBIM devices establish connections via cellular networks such as +GPRS, UMTS, and LTE. +They appear as a regular point-to-point network interface, +transporting raw IP frames. +Once a connection is established, +the device will automatically set an IP address +and send out a nameserver proposal, +which +.Xr resolvd 8 +can act on. +.Pp +Required configuration parameters like PIN and APN have to be set +with +.Xr ifconfig 8 . +Once the SIM card has been unlocked with the correct PIN, it +will remain in this state until the MBIM device is power-cycled. +In case the device is connected to an "always-on" USB port, +it may be possible to connect to a provider without entering the +PIN again even if the system was rebooted. +.Sh HARDWARE +The following devices should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Dell DW5821e +.It Ericsson H5321gw and N5321gw +.It Fibocom L831-EAU +.\" .It Huawei ME906s -- attaches but needs more work +.It Medion Mobile S4222 (MediaTek OEM) +.It Quectel EC25 +.It Quectel EM060K +.It Quectel RM500Q +.It SIMCom SIM7600 +.It SIMCom SIM8262E-M2 +.It Sierra Wireless EM7345 +.It Sierra Wireless EM7455 +.It Sierra Wireless EM8805 +.It Sierra Wireless MC8305 +.El +.Sh EXAMPLES +The following +.Xr hostname.if 5 +example configures umb0 to set the APN to +.Dq internet , +enabling data roaming, +and obtaining an IP address using IPv6 stateless address autoconfiguration: +.Bd -literal -offset indent +pin 1234 +apn internet +inet6 autoconf +roaming +.Ed +.Sh SEE ALSO +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr route 8 +.Rs +.%T "Universal Serial Bus Communications Class Subclass Specification for Mobile Broadband Interface Model" +.%U https://www.usb.org/document-library/mobile-broadband-interface-model-v10-errata-1-and-adopters-agreement +.Re +.Sh CAVEATS +Devices which fail to provide a conforming MBIM implementation will +probably be attached as some other driver, such as +.Xr umsm 4 . diff --git a/static/openbsd/man4/umbg.4 b/static/openbsd/man4/umbg.4 new file mode 100644 index 00000000..77c5e934 --- /dev/null +++ b/static/openbsd/man4/umbg.4 @@ -0,0 +1,81 @@ +.\" $OpenBSD: umbg.4,v 1.6 2019/03/26 16:41:35 jmc Exp $ +.\" +.\" Copyright (c) 2007 Marc Balmer +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 26 2019 $ +.Dt UMBG 4 +.Os +.Sh NAME +.Nm umbg +.Nd Meinberg Funkuhren USB5131 and DCF600USB timedelta sensors +.Sh SYNOPSIS +.Cd "umbg* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Meinberg Funkuhren USB5131 and +DCF600USB time signal receivers for the German DCF77 station. +.Nm +implements a timedelta sensor and the delta (in nanoseconds) between the +received time information and the local time can be accessed through the +.Xr sysctl 8 +interface. +.Pp +The quality of the timedelta is reported as the sensor status: +.Bl -tag -width "CRITICALXX" -offset indent +.It UNKNOWN +No valid time information has been received yet. +.It OK +The time information is valid and the timedelta is safe to use for +applications like +.Xr ntpd 8 . +.It WARN +The time information is still valid, but no new time information has been +decoded for at least twelve hours due to a reception or parity error. +The timedelta should be used with care. +.It CRITICAL +No valid time information has been received for more than twelve hours since +the sensor state degraded from OK to WARN. +This is an indication that hardware should be checked +to see if it is still functional. +.El +.Pp +A second sensor provides the relative signal quality as a percentage. +The status of this sensor is used to report the status of the device itself: +.Bl -tag -width "CRITICALXX" -offset indent +.It OK +The clock is synchronized. +.It WARN +The device's clock is free running on the local oscillator. +This is not an error and can happen due to the nature of the signal +transmission using longwave radio. +.It CRITICAL +Hardware failure, e.g. communication with the device failed. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr usb 4 , +.Xr ntpd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Marc Balmer Aq Mt mbalmer@openbsd.org . diff --git a/static/openbsd/man4/umcs.4 b/static/openbsd/man4/umcs.4 new file mode 100644 index 00000000..2b220809 --- /dev/null +++ b/static/openbsd/man4/umcs.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: umcs.4,v 1.1 2014/12/04 11:06:34 mpi Exp $ +.\" +.\" Copyright (c) 2014 Martin Pieuchot +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 4 2014 $ +.Dt UMCS 4 +.Os +.Sh NAME +.Nm umcs +.Nd MosChip Semiconductor based USB multiport serial adapter +.Sh SYNOPSIS +.Cd "umcs* at uhub?" +.Cd "ucom* at umcs?" +.Sh DESCRIPTION +The +.Nm +driver supports various MosChip Semiconductor based serial adapters. +.Pp +The following devices should work with the +.Nm +driver: +.Bd -literal -offset indent +LogiLink AU0033 +ST Lab U-360 +ST Lab U-400 +.Ed +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.7 . diff --git a/static/openbsd/man4/umct.4 b/static/openbsd/man4/umct.4 new file mode 100644 index 00000000..c38944e1 --- /dev/null +++ b/static/openbsd/man4/umct.4 @@ -0,0 +1,73 @@ +.\" $OpenBSD: umct.4,v 1.14 2019/01/21 23:47:10 jmatthew Exp $ +.\" $NetBSD: umct.4,v 1.5 2002/02/07 03:15:09 ross Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 21 2019 $ +.Dt UMCT 4 +.Os +.Sh NAME +.Nm umct +.Nd MCT USB-RS232 USB serial adapter +.Sh SYNOPSIS +.Cd "umct* at uhub?" +.Cd "ucom* at umct?" +.Sh DESCRIPTION +The +.Nm +driver provides support for MCT USB-to-RS232 Converter and their family +products. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh HARDWARE +The +.Nm +driver supports the following adapters: +.Pp +.Bl -tag -width Dv -offset indent -compact +.It Belkin F5U109 +.It Belkin F5U409 +.It D-Link DU-H3SP USB BAY +.It "MCT USB-RS232 Converter 9 pin Model U232-P9" +.It MCT USB-RS232 Converter 25 pin Model U232-P25 +.It Sitecom USB-RS232 Converter +.El +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 3.2 . diff --git a/static/openbsd/man4/umidi.4 b/static/openbsd/man4/umidi.4 new file mode 100644 index 00000000..f3dcf2c1 --- /dev/null +++ b/static/openbsd/man4/umidi.4 @@ -0,0 +1,72 @@ +.\" $OpenBSD: umidi.4,v 1.8 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: umidi.4,v 1.4 2002/02/07 03:15:09 ross Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt UMIDI 4 +.Os +.Sh NAME +.Nm umidi +.Nd USB MIDI devices +.Sh SYNOPSIS +.Cd "umidi* at uhub?" +.Cd "midi* at umidi?" +.Sh DESCRIPTION +The +.Nm +driver supports USB MIDI devices that follow the USB MIDI standard. +It also supports the following vendor specific devices: +.Pp +.Bl -tag -width Dv -offset indent -compact +.It Tn Roland UM1 +.It Tn Yamaha UX256 +.It Tn Yamaha UX96 +.It Tn other Yamaha MIDI devices (hopefully) +.El +.Pp +The +.Nm +driver is accessible through the +.Xr midi 4 +driver. +.Sh SEE ALSO +.Xr midi 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 3.2 . +.Sh CAVEATS +Some USB MIDI devices provide a switch for selecting between +a vendor specific mode and standard USB MIDI mode. +Selecting standard USB MIDI mode may allow a device to attach as +.Nm +rather than +.Xr ugen 4 . +This is particularly true for Roland branded devices. diff --git a/static/openbsd/man4/umodem.4 b/static/openbsd/man4/umodem.4 new file mode 100644 index 00000000..fb115563 --- /dev/null +++ b/static/openbsd/man4/umodem.4 @@ -0,0 +1,72 @@ +.\" $OpenBSD: umodem.4,v 1.8 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: umodem.4,v 1.4 2000/01/25 08:32:05 augustss Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt UMODEM 4 +.Os +.Sh NAME +.Nm umodem +.Nd USB modem support +.Sh SYNOPSIS +.Cd "umodem* at uhub?" +.Cd "ucom* at umodem?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB modems in the Communication +Device Class using the Abstract Control Model. +These modems are basically standard serial line modems, but they are +accessed via USB instead. +They support a regular AT command set. +The commands can either be multiplexed with the data stream +or handled through separate pipes. +In the latter case the AT commands have to be given on a device separate +from the data device. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver appeared in +.Nx 1.5 . +.Ox +support was added in +.Ox 2.7 . +.Sh BUGS +Only modems with multiplexed commands and data are supported +at the moment. diff --git a/static/openbsd/man4/ums.4 b/static/openbsd/man4/ums.4 new file mode 100644 index 00000000..1dc02faa --- /dev/null +++ b/static/openbsd/man4/ums.4 @@ -0,0 +1,75 @@ +.\" $OpenBSD: ums.4,v 1.12 2013/08/10 07:28:33 jmc Exp $ +.\" $NetBSD: ums.4,v 1.7 2001/12/28 17:38:00 augustss Exp $ +.\" +.\" Copyright (c) 1999, 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 10 2013 $ +.Dt UMS 4 +.Os +.Sh NAME +.Nm ums +.Nd USB HID mouse, touchscreen and digitiser devices +.Sh SYNOPSIS +.Cd "ums* at uhidev?" +.Cd "wsmouse* at ums? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB HID mice, touchscreens and digitisers. +Access to these devices is through the +.Xr wscons 4 +driver. +.Pp +If the touchscreen sensor is poorly aligned, then +.Xr xtsscale 1 +should be used to provide calibration results to the +.Nm +driver. +.Sh SEE ALSO +.Xr xtsscale 1 , +.Xr uhidev 4 , +.Xr usb 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Ox 2.8 . +.Sh AUTHORS +.An -nosplit +HID touchscreen and digitiser support was written by +.An Robert Nagy +and +.An Matthieu Herrb +then later merged into the generic +.Nm +driver by +.An Edd Barrett . +.Sh CAVEATS +Touchscreen and digitiser pressure sensitivity is not yet implemented. diff --git a/static/openbsd/man4/umsm.4 b/static/openbsd/man4/umsm.4 new file mode 100644 index 00000000..3f7d93e6 --- /dev/null +++ b/static/openbsd/man4/umsm.4 @@ -0,0 +1,248 @@ +.\" $OpenBSD: umsm.4,v 1.97 2024/05/23 08:06:22 kevlo Exp $ +.\" +.\" Copyright (c) 2006 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 23 2024 $ +.Dt UMSM 4 +.Os +.Sh NAME +.Nm umsm +.Nd Qualcomm MSM modem device +.Sh SYNOPSIS +.Cd "umsm* at uhub?" +.Cd "ucom* at umsm?" +.Sh DESCRIPTION +The +.Nm +driver supports Qualcomm MSM modem adapters. +The MSM chipset is found in EVDO, UMTS and LTE capable modems. +Typically these are CardBus and PCI Express Mini Cards that incorporate a +USB controller with the actual device attached to it. +.Pp +The following devices are known to work with the +.Nm +driver: +.Bl -column "Medion Mobile S4012 (Huawei E1550 OEM)" "Bus" -offset 6n +.It Em Device Ta Em Bus +.It Li "AirPrime PC5220" Ta "CardBus" +.It Li "Alcatel One Touch X060" Ta "USB" +.It Li "Alcatel One Touch X200" Ta "USB" +.It Li "Alcatel One Touch X210" Ta "USB" +.It Li "Alcatel One Touch X220" Ta "USB" +.It Li "AnyDATA ADU-500A" Ta "USB" +.It Li "AnyDATA ADU-E100H" Ta "USB" +.It Li "AnyDATA A2502" Ta "USB" +.It Li "C-motech CNU 680" Ta "USB" +.It Li "Emobile D01HW (Huawei OEM)" Ta "USB" +.It Li "Emobile D02HW (Huawei OEM)" Ta "USB" +.It Li "Emobile D12HW (Huawei OEM)" Ta "USB" +.It Li "Emobile D22HW (Huawei OEM)" Ta "USB" +.It Li "Emobile D31HW (Huawei OEM)" Ta "USB" +.It Li "Emobile H12HW (Huawei OEM)" Ta "USB" +.It Li "Emobile D21LC (longcheer OEM)" Ta "USB" +.It Li "Huawei Mobile E156G" Ta "USB" +.It Li "Huawei Mobile E160E" Ta "USB" +.It Li "Huawei Mobile E161" Ta "USB" +.It Li "Huawei Mobile E160g" Ta "USB" +.It Li "Huawei Mobile E1692" Ta "USB" +.It Li "Huawei Mobile E172" Ta "USB" +.It Li "Huawei Mobile E173" Ta "USB" +.It Li "Huawei Mobile E173s" Ta "USB" +.It Li "Huawei Mobile E180" Ta "USB" +.It Li "Huawei Mobile E181" Ta "USB" +.It Li "Huawei Mobile E182" Ta "USB" +.It Li "Huawei Mobile E220" Ta "USB" +.It Li "Huawei Mobile E303" Ta "USB" +.It Li "Huawei Mobile E352" Ta "USB" +.It Li "Huawei Mobile E353" Ta "USB" +.It Li "Huawei Mobile E392" Ta "USB" +.It Li "Huawei Mobile E510" Ta "USB" +.It Li "Huawei Mobile E1550" Ta "USB" +.It Li "Huawei Mobile E1750" Ta "USB" +.It Li "Huawei Mobile E1752" Ta "USB" +.It Li "Huawei Mobile E1820" Ta "USB" +.It Li "Huawei Mobile E3372" Ta "USB" +.It Li "Huawei Mobile EM770W" Ta "PCI Express Mini Card" +.It Li "Huawei Mobile K4510" Ta "USB" +.It Li "Huawei Mobile K4511" Ta "USB" +.It Li "Huawei Mobile Connect E169g" Ta "USB" +.It Li "Huawei Mobile Connect E618" Ta "USB" +.It Li "Huawei Mobile Connect E620" Ta "USB" +.It Li "IIJMobile 120FU (ZTE OEM)" Ta "USB" +.It Li "Kyocera KPC650" Ta "CardBus" +.It Li "Medion Mobile S4012 (Huawei E1550 OEM)" Ta "USB" +.It Li "Medion Mobile S4222 (MediaTek OEM)" Ta "USB" +.It Li "Novatel Wireless ES620" Ta "USB" +.It Li "Novatel Wireless Ovation U727" Ta "USB" +.It Li "Novatel Wireless U760" Ta "USB" +.It Li "NTT DoCoMo A2502" Ta "USB" +.It Li "ONDA Communication H600" Ta "CardBus" +.It Li "ONDA Communication MSA110UP" Ta "USB" +.It Li "Option GlobeSurfer iCON 7.2" Ta "USB" +.It Li "Option GlobeTrotter 3G+" Ta "CardBus" +.It Li "Option GlobeTrotter 3G Quad" Ta "CardBus" +.It Li "Option GlobeTrotter 3G Quad Plus" Ta "CardBus" +.It Li "Option GlobeTrotter GT Fusion" Ta "CardBus" +.It Li "Option GlobeTrotter GT Max" Ta "CardBus" +.It Li "Option GlobeTrotter HSDPA" Ta "USB" +.It Li "Option iCON 225" Ta "USB" +.It Li "Option iCON 505" Ta "USB" +.It Li "Option GlobeTrotter HSUPA 380E" Ta "PCI Express Mini Card" +.It Li "Quectel EC25" Ta "PCI Express Mini Card" +.It Li "Quectel EM060K" Ta "M.2" +.It Li "Sierra Wireless MC8755" Ta "PCI Express Mini Card" +.It Li "Sierra Wireless MC8775" Ta "PCI Express Mini Card" +.It Li "Sierra Wireless MC8790" Ta "PCI Express Mini Card" +.It Li "Sierra Wireless AirCard 580" Ta "CardBus" +.It Li "Sierra Wireless AirCard 875" Ta "CardBus" +.It Li "Sierra Wireless AirCard 881" Ta "CardBus" +.It Li "Sierra Wireless AirCard 881U" Ta "USB" +.It Li "Sierra Wireless Inc. USB 305" Ta "USB" +.It Li "Simcom SIM7600E" Ta "PCI Express Mini Card" +.It Li "Softbank C01SW (Sierra OEM)" Ta "USB" +.It Li "Toshiba 3G HSDPA MiniCard" Ta "PCI Express Mini Card" +.It Li "Vodafone Mobile Connect 3G" Ta "CardBus" +.It Li "Vodafone Mobile Broadband K3765" Ta "USB" +.It Li "Vodafone Mobile Broadband K3772" Ta "USB" +.It Li "ZTE AC2746" Ta "USB" +.It Li "ZTE MF112" Ta "USB" +.It Li "ZTE MF190" Ta "USB" +.It Li "ZTE MF633" Ta "USB" +.It Li "ZTE MF637" Ta "USB" +.El +.Pp +Devices suspected of being compatible are: +.Bl -column "Option GlobeTrotter HSDPA ICON225" "Bus" -offset 6n +.It Em Device Ta Em Bus +.It Li "Dell W5500" Ta "PCI Express Mini Card" +.It Li "Huawei E270+" Ta "USB" +.It Li "Huawei E1690" Ta "USB" +.It Li "Huawei E1762" Ta "USB" +.It Li "Novatel Wireless ExpressCard" Ta "ExpressCard" +.It Li "Novatel Wireless Merlin V620" Ta "CardBus" +.It Li "Novatel Wireless Merlin V740" Ta "CardBus" +.It Li "Novatel Wireless Merlin X950D" Ta "ExpressCard" +.It Li "Novatel Wireless MC950D" Ta "USB" +.It Li "Novatel Wireless S720" Ta "CardBus" +.It Li "Novatel Wireless U720" Ta "USB" +.It Li "Novatel Wireless U740" Ta "CardBus" +.It Li "Novatel Wireless U870" Ta "CardBus" +.It Li "Novatel Wireless V720" Ta "CardBus" +.It Li "Novatel Wireless X950D" Ta "ExpressCard" +.It Li "Novatel Wireless XU870 HSDPA" Ta "ExpressCard" +.It Li "Sierra Wireless AirCard 595" Ta "CardBus" +.It Li "Sierra Wireless AirCard 597E" Ta "CardBus" +.It Li "Sierra Wireless AirCard 880" Ta "CardBus" +.It Li "Sierra Wireless AirCard 880E" Ta "ExpressCard" +.It Li "Sierra Wireless AirCard 880U" Ta "USB" +.It Li "Sierra Wireless AirCard 881E" Ta "ExpressCard" +.It Li "Sierra Wireless AirCard 885U" Ta "USB" +.It Li "Sierra Wireless C597" Ta "USB" +.It Li "Sierra Wireless EM5625" Ta "USB" +.It Li "Sierra Wireless MC5720" Ta "PCI Express Mini Card" +.It Li "Sierra Wireless MC5725" Ta "PCI Express Mini Card" +.It Li "Sierra Wireless MC8765" Ta "PCI Express Mini Card" +.It Li "Sierra Wireless MC8780" Ta "PCI Express Mini Card" +.It Li "Sierra Wireless MC8781" Ta "PCI Express Mini Card" +.El +.Pp +Some modems have multiple serial ports, +however almost all modems have only one effective serial port +for PPP connections. +For example, the Huawei E220 has two serial ports, +but only the first port can be used to make connections; +the second one is for management. +The Option GlobeTrotter HSDPA/HSUPA modems have three serial ports, +but only the last port can be used to make PPP connections. +The Medion Mobile S4222 has four serial ports, but only the first +port can be used to make connections. +.Pp +Some modems require multi-link PPP operation. +For example, the Huawei E1550 has four serial ports. +When initiating a connection, the control commands have to be issued +on the third port, and after that the actual PPP connection comes +up on the first port. +The function of the second and fourth ports is unknown. +.Sh EXAMPLES +An example demand dial configuration for Cingular Wireless using +.Xr pppd 8 : +.Pp +.Pa /etc/ppp/cingular-chat : +.Bd -literal -offset indent +TIMEOUT 10 +REPORT CONNECT +ABORT BUSY +ABORT 'NO CARRIER' +ABORT ERROR +\&'' ATZ OK AT&F OK +AT+CGDCONT=1,"IP","isp.cingular" OK +ATD*99***1# CONNECT +.Ed +.Pp +.Pa /etc/ppp/peers/ac875 : +.Bd -literal -offset indent +cuaU0 +115200 +debug +noauth +nocrtscts +:10.254.254.1 +ipcp-accept-remote +defaultroute +user isp@cingulargprs.com +demand +active-filter 'not udp port 123' +persist +idle 600 +connect "/usr/sbin/chat -v -f /etc/ppp/cingular-chat" +.Ed +.Pp +.Pa /etc/ppp/chap-secrets : +.Bd -literal -offset indent +# Secrets for authentication using CHAP +# client server secret IP addresses +isp@cingulargprs.com * CINGULAR1 +.Ed +.Pp +.Xr pppd 8 +is then started using: +.Pp +.Dl # pppd call ac875 +.Sh SEE ALSO +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr pppd 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan Gray Aq Mt jsg@openbsd.org +and +.An Yojiro UO Aq Mt yuo@nui.org . +.Sh CAVEATS +For Verizon Wireless (and possibly other services), +cards require a one-time activation before they will work; +.Nm +does not currently support this. +.Pp +The additional IEEE 802.11 wireless chipset found in the Option +GlobeTrotter GT FUSION is not yet supported. diff --git a/static/openbsd/man4/umstc.4 b/static/openbsd/man4/umstc.4 new file mode 100644 index 00000000..bd34f7df --- /dev/null +++ b/static/openbsd/man4/umstc.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: umstc.4,v 1.2 2020/06/01 01:52:21 jcs Exp $ +.\" +.\" Copyright (c) 2020 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 1 2020 $ +.Dt UMSTC 4 +.Os +.Sh NAME +.Nm umstc +.Nd Microsoft Surface Type Cover keyboard +.Sh SYNOPSIS +.Cd "umstc* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver responds to some special keys on the Microsoft Type Cover +keyboard, such as volume and screen brightness keys. +.Sh SEE ALSO +.Xr uhidev 4 , +.Xr usb 4 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@jcs.org . diff --git a/static/openbsd/man4/umt.4 b/static/openbsd/man4/umt.4 new file mode 100644 index 00000000..7abfe305 --- /dev/null +++ b/static/openbsd/man4/umt.4 @@ -0,0 +1,47 @@ +.\" $OpenBSD: umt.4,v 1.1 2018/08/25 20:31:31 jcs Exp $ +.\" +.\" Copyright (c) 2016-2018 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 25 2018 $ +.Dt UMT 4 +.Os +.Sh NAME +.Nm umt +.Nd USB HID multitouch touchpad devices +.Sh SYNOPSIS +.Cd "umt* at uhidev?" +.Cd "wsmouse* at umt? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB HID touchpads conforming to the +Windows Precision Touchpad standard. +Access to these devices is through the +.Xr wscons 4 +driver. +.Sh SEE ALSO +.Xr uhidev 4 , +.Xr ums 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . diff --git a/static/openbsd/man4/unix.4 b/static/openbsd/man4/unix.4 new file mode 100644 index 00000000..98970239 --- /dev/null +++ b/static/openbsd/man4/unix.4 @@ -0,0 +1,171 @@ +.\" $OpenBSD: unix.4,v 1.15 2021/08/21 18:18:05 jmc Exp $ +.\" $NetBSD: unix.4,v 1.3 1994/11/30 16:22:43 jtc Exp $ +.\" +.\" Copyright (c) 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)unix.4 8.1 (Berkeley) 6/9/93 +.\" +.Dd $Mdocdate: August 21 2021 $ +.Dt UNIX 4 +.Os +.Sh NAME +.Nm unix +.Nd UNIX-domain protocol family +.Sh SYNOPSIS +.In sys/types.h +.In sys/un.h +.Sh DESCRIPTION +The +.Ux Ns -domain +protocol family is a collection of protocols +that provides local (on-machine) interprocess +communication through the normal +.Xr socket 2 +mechanisms. +The +.Ux Ns -domain +family supports the +.Dv SOCK_STREAM , +.Dv SOCK_SEQPACKET , +and +.Dv SOCK_DGRAM +socket types and uses +filesystem pathnames for addressing. +.Sh ADDRESSING +.Ux Ns -domain +addresses are variable-length filesystem pathnames of +at most 104 characters. +The include file +.In sys/un.h +defines this address: +.Bd -literal -offset indent +struct sockaddr_un { + u_char sun_len; + u_char sun_family; + char sun_path[104]; +}; +.Ed +.Pp +Binding a name to a +.Ux Ns -domain +socket with +.Xr bind 2 +causes a socket file to be created in the filesystem. +This file is +.Em not +removed when the socket is closed\(em\c +.Xr unlink 2 +must be used to remove the file. +.Pp +The +.Ux Ns -domain +protocol family does not support broadcast addressing or any form +of +.Dq wildcard +matching on incoming messages. +All addresses are absolute- or relative-pathnames +of other +.Ux Ns -domain +sockets. +Normal filesystem access-control mechanisms are also +applied when referencing pathnames; e.g., the destination +of a +.Xr connect 2 +or +.Xr sendto 2 +must be writable. +.Sh PROTOCOLS +The +.Ux Ns -domain +protocol family is comprised of simple +transport protocols that support the +.Dv SOCK_STREAM , +.Dv SOCK_SEQPACKET , +and +.Dv SOCK_DGRAM +abstractions. +.Dv SOCK_STREAM +and +.Dv SOCK_SEQPACKET +sockets also support the communication of +.Ux +file descriptors through the use of the +.Ar msg_control +field in the +.Ar msg +argument to +.Xr sendmsg 2 +and +.Xr recvmsg 2 . +.Pp +Any valid descriptor may be sent in a message. +The file descriptor(s) to be passed are described using a +.Ar struct cmsghdr +that is defined in the include file +.In sys/socket.h . +The type of the message is +.Dv SCM_RIGHTS , +and the data portion of the messages is an array of integers +representing the file descriptors to be passed. +The number of descriptors being passed is defined +by the length field of the message; +the length field is the sum of the size of the header +plus the size of the array of file descriptors. +.Pp +The received descriptor is a +.Em duplicate +of the sender's descriptor, as if it were created with a call to +.Xr dup 2 . +Per-process descriptor flags, set with +.Xr fcntl 2 , +are +.Em not +passed to a receiver. +Descriptors that are awaiting delivery, or that are +purposely not received, are automatically closed by the system +when the destination socket is closed. +.Sh SEE ALSO +.Xr socket 2 , +.Xr netintro 4 +.Rs +.\" 4.4BSD PSD:20 +.%A S. Sechrest +.%T \&An Introductory 4.4BSD Interprocess Communication Tutorial +.%B 4.4BSD Programmer's Supplementary Documents (PSD) +.Re +.Rs +.\" 4.4BSD PSD:21 +.%A S. J. Leffler +.%A R. S. Fabry +.%A W. N. Joy +.%A P. Lapsley +.%A S. Miller +.%A C. Torek +.%T \&An Advanced 4.4BSD Interprocess Communication Tutorial +.%B 4.4BSD Programmer's Supplementary Documents (PSD) +.Re diff --git a/static/openbsd/man4/uoaklux.4 b/static/openbsd/man4/uoaklux.4 new file mode 100644 index 00000000..c86603b0 --- /dev/null +++ b/static/openbsd/man4/uoaklux.4 @@ -0,0 +1,60 @@ +.\" $OpenBSD: uoaklux.4,v 1.7 2024/01/03 09:19:22 kevlo Exp $ +.\" +.\" Copyright (c) 2012 Yojiro UO +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 3 2024 $ +.Dt UOAKLUX 4 +.Os +.Sh NAME +.Nm uoaklux +.Nd Toradex OAK USB illuminance sensor +.Sh SYNOPSIS +.Cd "uoaklux* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Toradex OAK LUX. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +.Pp +The illuminance date unit is "Lux". +Because the sensing cycle of the illuminance sensor is faster than +the sensor framework update period, +the driver keeps maximum/minimum/average values as independent sensors. +.Pp +The device has a unique serial number, +indicated in the description part of the sensor value. +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhidev 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Rs +.%T Toradex Web Page +.%U http://developer.toradex.com/hardware-resources/usb-sensors-and-peripherals +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Yojiro UO Aq Mt yuo@nui.org . diff --git a/static/openbsd/man4/uoakrh.4 b/static/openbsd/man4/uoakrh.4 new file mode 100644 index 00000000..c9f676cf --- /dev/null +++ b/static/openbsd/man4/uoakrh.4 @@ -0,0 +1,56 @@ +.\" $OpenBSD: uoakrh.4,v 1.6 2024/01/03 09:19:22 kevlo Exp $ +.\" +.\" Copyright (c) 2012 Yojiro UO +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 3 2024 $ +.Dt UOAKRH 4 +.Os +.Sh NAME +.Nm uoakrh +.Nd Toradex OAK USB temperature and relative humidity sensor +.Sh SYNOPSIS +.Cd "uoakrh* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Toradex OAK RH. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +The relative humidity data unit is "%RH" and the temperature data +unit is "degC". +The device has a unique serial number, +indicated in the description part of the sensor value. +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhidev 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Rs +.%T Toradex Web Page +.%U http://developer.toradex.com/hardware-resources/usb-sensors-and-peripherals +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Yojiro UO Aq Mt yuo@nui.org . diff --git a/static/openbsd/man4/uoakv.4 b/static/openbsd/man4/uoakv.4 new file mode 100644 index 00000000..b2e40336 --- /dev/null +++ b/static/openbsd/man4/uoakv.4 @@ -0,0 +1,61 @@ +.\" $OpenBSD: uoakv.4,v 1.6 2024/01/03 09:19:22 kevlo Exp $ +.\" +.\" Copyright (c) 2012 Yojiro UO +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 3 2024 $ +.Dt UOAKV 4 +.Os +.Sh NAME +.Nm uoakv +.Nd Toradex OAK USB +/-10V 8channel ADC interface +.Sh SYNOPSIS +.Cd "uoakv* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Toradex OAK 10V device. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +.Pp +The ADC date unit is "VDC"(DC voltage) and the value is signed. +Because the Analog-Digital conversion cycle of the device is faster +than the sensor framework update cycle, +the driver keeps maximum/minimum/average values of each cycle as +independent sensors. +.Pp +The device has a unique serial number, +indicated in the description part of the sensor value. +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhidev 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Rs +.%T Toradex Web Page +.%U http://developer.toradex.com/hardware-resources/usb-sensors-and-peripherals +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Yojiro UO Aq Mt yuo@nui.org . diff --git a/static/openbsd/man4/uonerng.4 b/static/openbsd/man4/uonerng.4 new file mode 100644 index 00000000..a2ff7d06 --- /dev/null +++ b/static/openbsd/man4/uonerng.4 @@ -0,0 +1,71 @@ +.\" $OpenBSD: uonerng.4,v 1.4 2022/02/18 10:24:32 jsg Exp $ +.\" +.\" Copyright (c) 2015 Devin Reade +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt ONERNG 4 +.Os +.Sh NAME +.Nm uonerng +.Nd Moonbase Otago OneRNG TRNG +.Sh SYNOPSIS +.Cd "uonerng* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Moonbase Otago OneRNG, a USB true random +number generator (TRNG). +.Nm +reads raw entropy from the OneRNG and uses +.Xr enqueue_randomness 9 +to add it to the system entropy pool. +.Pp +The OneRNG is capable of operating in one of several modes, some of +which are intended for production use and some of which are for testing +and validating the hardware. +.Pp +.Nm +operates in the +.Qq Avalanche noise with whitener +mode, +which is also the manufacturer's default mode. +.Sh SEE ALSO +.Xr intro 4 , +.Xr usb 4 , +.Xr enqueue_randomness 9 +.Pp +Moonbase Otago: +.Lk https://onerng.info/onerng +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Devin Reade Aq Mt gdr@gno.org . +.Sh BUGS +The OneRNG permits downloading of the device firmware so that one may check +the firmware's cryptographic signature as provided by the manufacturer. +The +.Nm +driver does not perform nor support this action. +In order to currently perform such a validation, +it would be necessary to disable +.Nm +in the kernel and then download the firmware via the OneRNG's +emulated AT modem command set. diff --git a/static/openbsd/man4/uow.4 b/static/openbsd/man4/uow.4 new file mode 100644 index 00000000..7c632082 --- /dev/null +++ b/static/openbsd/man4/uow.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: uow.4,v 1.4 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt UOW 4 +.Os +.Sh NAME +.Nm uow +.Nd Maxim/Dallas DS2490 USB 1-Wire adapter +.Sh SYNOPSIS +.Cd "uow* at uhub?" +.Cd "onewire* at uow?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Maxim/Dallas DS2490 USB 1-Wire adapter. +.Pp +The following adapters should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It iButton DS9490/DS9490B/DS9490R +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr onewire 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/upd.4 b/static/openbsd/man4/upd.4 new file mode 100644 index 00000000..2384e852 --- /dev/null +++ b/static/openbsd/man4/upd.4 @@ -0,0 +1,101 @@ +.\" $OpenBSD: upd.4,v 1.6 2024/12/01 09:05:05 landry Exp $ +.\" +.\" Copyright (c) 2014 Andre de Oliveira +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 1 2024 $ +.Dt UPD 4 +.Os +.Sh NAME +.Nm upd +.Nd USB Power Devices sensor +.Sh SYNOPSIS +.Cd "upd* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for monitoring various sensors provided by +USB Power Devices (such as a UPS). +Supported sensor values are made available via the +.Xr sysctl 8 +interface. +.Pp +The following sensors are supported by the driver: +.Pp +.Bl -item -offset indent -compact +.It +BatteryPresent +.It +ShutdownImminent +.It +ACPresent +.It +PercentLoad +.It +Overload +.It +RelativeStateOfCharge +.It +AbsoluteStateOfCharge +.It +RemainingCapacity +.It +FullChargeCapacity +.It +Charging +.It +Discharging +.It +AtRateTimeToFull +.It +AtRateTimeToEmpty +.It +RunTimeToEmpty +.It +NeedReplacement +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhidev 4 , +.Xr sensorsd.conf 5 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Pp +The USB Power Devices specification can be found at: +.Lk https://www.usb.org/hid +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.6 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Andre de Oliveira . +.Sh BUGS +The +.Nm +driver does not indicate device health via aggregate or +individual sensor status. +Users who wish to monitor +.Nm +status using +.Xr sensorsd 8 +must manually establish +.Dq high +and +.Dq low +limits for sensor values of interest via +.Xr sensorsd.conf 5 . diff --git a/static/openbsd/man4/upgt.4 b/static/openbsd/man4/upgt.4 new file mode 100644 index 00000000..4d56cb5d --- /dev/null +++ b/static/openbsd/man4/upgt.4 @@ -0,0 +1,193 @@ +.\" $OpenBSD: upgt.4,v 1.33 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2007 Marcus Glocker +.\" Copyright (c) 2005-2007 +.\" Damien Bergamini +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" +.\" +.\" Copyright (c) 2006 Theo de Raadt. +.\" Copyright (c) 2006 The DragonFly Project. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in +.\" the documentation and/or other materials provided with the +.\" distribution. +.\" 3. Neither the name of The DragonFly Project nor the names of its +.\" contributors may be used to endorse or promote products derived +.\" from this software without specific, prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +.\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE +.\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT +.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt UPGT 4 +.Os +.Sh NAME +.Nm upgt +.Nd Conexant/Intersil PrismGT SoftMAC USB IEEE 802.11b/g wireless network device +.Sh SYNOPSIS +.Cd "upgt* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports the USB 2.0 Conexant/Intersil PrismGT series wireless +adapters based on the GW3887 chipset. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver relies on the software 802.11 stack for both encryption and decryption +of data frames. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs a firmware file which is loaded when an interface is +brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/upgt-gw3887 +.El +.\".Pp +.\"These firmware files are not free because Conexant/Intersil refuses +.\"to grant distribution rights. +.\"As a result, even though +.\".Ox +.\"includes the driver, the firmware files cannot be included and +.\"users have to download these files on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh HARDWARE +The following adapters should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Belkin F5D7050 (version 1000) +.It Cohiba Proto Board +.It D-Link DWL-G120 Cohiba +.It D-Link DWL-G122 rev A2 +.It FSC Connect2Air E-5400 USB D1700 +.It Gigaset USB Adapter 54 +.It Inventel UR045G +.It IOGear GWU513 +.It Linksys WUSB54AG +.It Linksys WUSB54G ver 2 +.It Medion MD40900 +.It Philips CPWUA054 +.It SMC EZ ConnectG SMC2862W-G +.It Sagem XG703A +.It Spinnaker DUT +.It Spinnaker Proto Board +.It Thomson SpeedTouch 121g +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig upgt0 scan +.Pp +The following +.Xr hostname.if 5 +example configures upgt0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.\".Xr hostapd 8 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Marcus Glocker Aq Mt mglocker@openbsd.org . +.Sh CAVEATS +The +.Nm +driver just supports the USB 2.0 devices (GW3887 chipset) but not the +USB 1.0 devices containing the NET2280, ISL3880, and ISL3886 chipsets. +Some further efforts would be necessary to add USB 1.0 support to the +driver. diff --git a/static/openbsd/man4/upl.4 b/static/openbsd/man4/upl.4 new file mode 100644 index 00000000..3f2e7c57 --- /dev/null +++ b/static/openbsd/man4/upl.4 @@ -0,0 +1,88 @@ +.\" $OpenBSD: upl.4,v 1.8 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: upl.4,v 1.3 2000/08/12 17:59:12 augustss Exp $ +.\" +.\" Copyright (c) 2000 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt UPL 4 +.Os +.Sh NAME +.Nm upl +.Nd Prolific based host-to-host adapters +.Sh SYNOPSIS +.Cd "upl* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Prolific PL2301/PL2302 based host-to-host +USB connectors. +.Pp +The +.Nm +driver appears as a point-to-point network interface and +should be configured with +.Xr ifconfig 8 +in the same way as other point-to-point interfaces. +The +.Nm +device supports IPv4 only. +.Sh HARDWARE +The +.Nm +driver supports the following adapters from the following vendors: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Tn Aserton +.It Tn Bencent +.It Tn Butterfly +.It Tn Camtel +.It Tn Inland +.It Tn Longshine +.It Tn PC Linq +.It Tn Prolific +.It Tn StarMount +.It Tn Univex +.It Tn VVMer +.El +.Pp +Belkin, Entrega, and Xircom do +.Em NOT +use this chip and are not supported by this driver. +.Sh SEE ALSO +.Xr netintro 4 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver appeared in +.Nx 1.5 . +.Ox +support was added in +.Ox 2.9 . diff --git a/static/openbsd/man4/uplcom.4 b/static/openbsd/man4/uplcom.4 new file mode 100644 index 00000000..1e5c6911 --- /dev/null +++ b/static/openbsd/man4/uplcom.4 @@ -0,0 +1,102 @@ +.\" $OpenBSD: uplcom.4,v 1.27 2017/08/08 16:40:23 anton Exp $ +.\" $NetBSD: uplcom.4,v 1.6 2001/05/22 00:21:25 jhawk Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 8 2017 $ +.Dt UPLCOM 4 +.Os +.Sh NAME +.Nm uplcom +.Nd Prolific PL-2303 USB serial adapter +.Sh SYNOPSIS +.Cd "uplcom* at uhub?" +.Cd "ucom* at uplcom?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Prolific PL-2303 USB-to-RS232 Bridge chip. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh HARDWARE +The +.Nm +driver supports the following adapters: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Alcatel One Touch 535/735 +.It Aten UC232A +.It Belkin F5U257 +.It Digitus DA-70145 +.It ELECOM UC-SGT +.It Ericsson DCU-10 & DCU-11, made by Susteen, Inc. +.It HAL Crossam2+USB +.It HIGH-EDGE HE800 +.It I/O DATA USB-RSAQ +.It I/O DATA USB-RSAQ2 +.It I/O DATA USB-RSAQ3 +.It I/O DATA USB-RSAQ5 +.It IOGEAR UC-232A +.It iTegno WM1080A +.It Leadtek 9531 GPS +.It Maxxtro UC-232A +.It Nokia CA-42 +.It Ours Technology DKU-5 clone +.It Palm 700WX +.It Pharos USB GPS +.It PLANEX USB-RS232 URS-03 +.It RATOC REX-USB60 +.It Samsung I330 cradle +.It Siemens X65 +.It Siemens X75 +.It Siemens SX1 +.It Sitecom USB-Serial CNA-104 +.It SOURCENEXT KeikaiDenwa 8 +.It Speed Dragon MS3303H +.It TDK USB-PDC Adapter UPA9664 +.It TDK USB-PHS Adapter UHA6400 +.It Tripp-Lite U209 +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Nx 1.6 . +.Ox +support was added in +.Ox 3.0 . diff --git a/static/openbsd/man4/ural.4 b/static/openbsd/man4/ural.4 new file mode 100644 index 00000000..6a526216 --- /dev/null +++ b/static/openbsd/man4/ural.4 @@ -0,0 +1,199 @@ +.\" $OpenBSD: ural.4,v 1.26 2025/03/25 19:57:54 jmc Exp $ +.\" +.\" Copyright (c) 2005-2007 +.\" Damien Bergamini +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 25 2025 $ +.Dt URAL 4 +.Os +.Sh NAME +.Nm ural +.Nd Ralink Technology/MediaTek USB IEEE 802.11b/g wireless network device +.Sh SYNOPSIS +.Cd "ural* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports USB 2.0 wireless adapters based on the Ralink RT2500USB +chipset. +.Pp +The RT2500USB chipset is the first generation of 802.11b/g adapters from Ralink. +It consists of two integrated chips, an RT2570 MAC/BBP and an RT2526 radio +transceiver. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer. +.It Host AP +In this mode the driver acts as an access point (base station) +for other cards. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver relies on the software 802.11 stack for both encryption and decryption +of data frames. +.Pp +The transmit speed is user-selectable or can be adapted automatically by the +driver depending on the number of hardware transmission retries. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh HARDWARE +The following adapters should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It AMIT WL532U +.It ASUS WL-167g v1 +.It Belkin F5D7050 v2000 +.It Buffalo WLI-U2-KG54 +.It Buffalo WLI-U2-KG54-AI +.It Buffalo WLI-U2-KG54-YB +.It CNet CWD-854 +.It Compex WLU54G 2A1100 +.It Conceptronic C54RU +.It D-Link DWL-G122 (b1) +.It Dynalink WLG25USB +.It E-Tech WGUS02 +.It Eminent EM3035 +.It Gigabyte GN-WBKG +.It Hercules HWGUSB2-54 +.It KCORP LifeStyle KLS-685 +.It Linksys HU200-TS +.It Linksys WUSB54G v4 +.It Linksys WUSB54GP v4 +.It MSI MS-6861 +.It MSI MS-6865 +.It MSI MS-6869 +.It Nintendo Wi-Fi USB Connector +.It Nova Tech NV-902W +.It OvisLink Evo-W54USB +.It SerComm UB801R +.It SparkLAN WL-685R +.It Sphairon UB801R +.It Surecom EP-9001-g rev 3A +.It Sweex LC100060 +.It Tonze UW-6200C +.It Zaapa ZNWUSB-54 +.It Zinwell ZPlus-G250 +.It Zinwell ZWX-G261 +.It Zonet ZEW2500P +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig ural0 scan +.Pp +The following +.Xr hostname.if 5 +example configures ural0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +nwid mynwid wpakey mywpakey +inet autoconf +.Ed +.Pp +The following +.Xr hostname.if 5 +example creates a host-based access point on boot: +.Bd -literal -offset indent +mediaopt hostap +nwid mynwid wpakey mywpakey +inet 192.168.1.1 255.255.255.0 +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "ural0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr hostapd 8 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.7 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +The +.Nm +driver supports automatic control of the transmit speed in BSS mode only. +Therefore the use of an +.Nm +adapter in Host AP mode is discouraged. +.Pp +Host AP mode doesn't support power saving. +Clients attempting to use power saving mode may experience significant +packet loss (disabling power saving on the client will fix this). diff --git a/static/openbsd/man4/ure.4 b/static/openbsd/man4/ure.4 new file mode 100644 index 00000000..3dd6ca89 --- /dev/null +++ b/static/openbsd/man4/ure.4 @@ -0,0 +1,77 @@ +.\" $OpenBSD: ure.4,v 1.11 2025/05/23 03:06:09 kevlo Exp $ +.\" +.\" Copyright (c) 2015 Kevin Lo +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" $FreeBSD: head/share/man/man4/ure.4 291557 2015-12-01 05:12:13Z kevlo $ +.\" +.Dd $Mdocdate: May 23 2025 $ +.Dt URE 4 +.Os +.Sh NAME +.Nm ure +.Nd Realtek RTL8152/RTL8153/RTL8156/RTL8157 10/100/1Gb/2.5Gb/5Gb \ +USB Ethernet device +.Sh SYNOPSIS +.Cd "ure* at uhub?" +.Cd "rgephy* at mii?" +.Cd "rlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB Ethernet adapters based on the Realtek +RTL8152, RTL8153, RTL8153B, RTL8153D, RTL8156, RTL8156B and RTL8157 chipsets. +.Pp +The RTL8152 contains an integrated Fast Ethernet MAC, which supports +both 10 and 100Mbps speeds in either full or half duplex. +The RTL8153, RTL8153B and RTL8153D have Gigabit Ethernet MACs and additionally +support 1000Mbps speeds. +NICs based on the RTL8156 and RTL8156B are capable of 10, 100, 1000 and +2500Mbps operation. +The RTL8157 is a USB 3.0 device, which contains a 10/100/1Gb/2.5Gb/5Gb +Ethernet MAC. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr mii 4 , +.Xr netintro 4 , +.Xr rgephy 4 , +.Xr rlphy 4 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Kevin Lo Aq Mt kevlo@FreeBSD.org . diff --git a/static/openbsd/man4/url.4 b/static/openbsd/man4/url.4 new file mode 100644 index 00000000..4ba4836d --- /dev/null +++ b/static/openbsd/man4/url.4 @@ -0,0 +1,99 @@ +.\" $OpenBSD: url.4,v 1.21 2013/07/16 16:05:49 schwarze Exp $ +.\" $NetBSD: url.4,v 1.4 2002/04/02 20:45:40 augustss Exp $ +.\" +.\" Copyright (c) 2002 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt URL 4 +.Os +.Sh NAME +.Nm url +.Nd Realtek RTL8150L 10/100 USB Ethernet device +.Sh SYNOPSIS +.Cd "url* at uhub?" +.Cd "urlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB +.Tn Ethernet +adapters based on the Realtek RTL8150L USB-ether bridge chip. +.Pp +The +.Nm +driver supports the following adapters: +.Pp +.Bl -tag -width Dv -offset indent -compact +.It Tn Abocom RTL8151 +.It Tn BAFO BF-310 +.It Tn Billionton USBKR-100 +.It Tn Compex UE202-B +.It Tn GreenHouse GH-USB100B +.It Tn GreenHouse GH-USB100B with HomePNA +.It Tn Hawking Technology HUF11 +.It Tn Linksys USB100M +.It Tn Longshine LCS-8138TX +.It Tn Melco Inc. LUA-KTX +.It Tn Micronet SP128AR +.It Tn NetComm NP1010 +.It Tn OQO model 01 (10/100) Ethernet +.It Tn Repotec RP-USB100-A +.It Tn SMC 2208USB/ETH +.It Tn TRENDnet TU-ET100C +.It Tn Zt USB10/100 +.It Tn ZyXEL Prestige +.It Tn Z-TEK ZK-R02 +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "url0: watchdog timeout" +A packet was queued for transmission and a transmit command was +issued, however the device failed to acknowledge the transmission +before a timeout expired. +.It "url0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr mii 4 , +.Xr netintro 4 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Shingo WATANABE Aq Mt nabe@nabechan.org . diff --git a/static/openbsd/man4/urlphy.4 b/static/openbsd/man4/urlphy.4 new file mode 100644 index 00000000..d538e1e9 --- /dev/null +++ b/static/openbsd/man4/urlphy.4 @@ -0,0 +1,35 @@ +.\" $OpenBSD: urlphy.4,v 1.7 2009/07/31 14:20:29 jmc Exp $ +.\" +.\" Copyright (c) 2002 Nathan L. Binkert +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 31 2009 $ +.Dt URLPHY 4 +.Os +.Sh NAME +.Nm urlphy +.Nd Realtek RTL8150L Ethernet PHY +.Sh SYNOPSIS +.Cd "urlphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the internal PHY found on Realtek RTL8150L USB Ethernet +devices (see +.Xr url 4 ) . +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/urndis.4 b/static/openbsd/man4/urndis.4 new file mode 100644 index 00000000..e5c2db96 --- /dev/null +++ b/static/openbsd/man4/urndis.4 @@ -0,0 +1,72 @@ +.\" Copyright (c) 2010 Michael Knudsen +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" +.\" - Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" - Redistributions in binary form must reproduce the above +.\" copyright notice, this list of conditions and the following +.\" disclaimer in the documentation and/or other materials provided +.\" with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +.\" "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +.\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE +.\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER +.\" CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $OpenBSD: urndis.4,v 1.15 2013/07/16 16:05:49 schwarze Exp $ +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt URNDIS 4 +.Os +.Sh NAME +.Nm urndis +.Nd USB Remote NDIS Ethernet device +.Sh SYNOPSIS +.Cd "urndis* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides Ethernet access over Remote NDIS (RNDIS), +allowing mobile devices such as phones and tablets to provide network access. +It is often referred to as USB tethering, +and in most cases must be explicitly enabled on the device. +.Pp +.Nm +should work with any USB RNDIS devices, +such as those commonly found on Android devices. +It does not support different media types or options. +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan Armani Aq Mt armani@openbsd.org , +.An Michael Knudsen Aq Mt mk@openbsd.org , +and +.An Fabien Romano Aq Mt fabien@openbsd.org . diff --git a/static/openbsd/man4/urng.4 b/static/openbsd/man4/urng.4 new file mode 100644 index 00000000..7a65ae50 --- /dev/null +++ b/static/openbsd/man4/urng.4 @@ -0,0 +1,59 @@ +.\" $OpenBSD: urng.4,v 1.5 2018/04/28 15:44:59 jasper Exp $ +.\" +.\" Copyright (c) 2015 Sean Levy +.\" Copyright (c) 2017 Jasper Lievisse Adriaanse +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 28 2018 $ +.Dt URNG 4 +.Os +.Sh NAME +.Nm urng +.Nd USB Random Number Generator devices +.Sh SYNOPSIS +.Cd "urng* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various true random number generator +(TRNG) devices connected via USB. +.Nm +reads raw entropy from the device at a (hardware dependent) interval +and stirs it into the system entropy pool with +.Xr enqueue_randomness 9 . +.Sh HARDWARE +The following devices are supported by this driver: +.Bl -tag -width "Altus Metrum" +.It Araneus Alea I and II +Capable of delivering 100kbit/sec of hardware-generated entropy. +.It Altus Metrum ChaosKey 1.0 +This device is capable of providing entropy at 10Mbit/s. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr usb 4 , +.Xr enqueue_randomness 9 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.2 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Aaron Bieber Aq Mt abieber@openbsd.org , +.An Jasper Lievisse Adriaanse Aq Mt jasper@openbsd.org , +and +.An Sean Levy Aq Mt attila@stalphonsos.com . diff --git a/static/openbsd/man4/urtw.4 b/static/openbsd/man4/urtw.4 new file mode 100644 index 00000000..d108503e --- /dev/null +++ b/static/openbsd/man4/urtw.4 @@ -0,0 +1,132 @@ +.\" $OpenBSD: urtw.4,v 1.31 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 2008 Weongyo Jeong +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt URTW 4 +.Os +.Sh NAME +.Nm urtw +.Nd Realtek RTL8187L/RTL8187B USB IEEE 802.11b/g wireless network device +.Sh SYNOPSIS +.Cd "urtw* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports USB 802.11b/g wireless adapters based on the +Realtek RTL8187L and RTL8187B. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver relies on the software 802.11 stack for both encryption and decryption +of data frames. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh HARDWARE +The following adapters should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Alfa AWUS036H +.It ASUS P5B Deluxe +.It Belkin F5D7050E +.It Digitus DN-7003GT +.It Linksys WUSB54GC v2 +.It Netgear WG111v2 +.It Netgear WG111v3 +.It Shuttle XPC Accessory PN20 +.It Sitecom WL-168 v1 +.It Sitecom WL-168 v4 +.It Surecom EP-9001-g rev 2A +.It TRENDnet TEW-424UB V3.xR +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig urtw0 scan +.Pp +The following +.Xr hostname.if 5 +example configures urtw0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.\".Xr hostapd 8 , +.Xr ifconfig 8 +.Pp +Realtek Semiconductor: +.Lk https://www.realtek.com/en +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Weongyo Jeong Aq Mt weongyo@FreeBSD.org . diff --git a/static/openbsd/man4/urtwn.4 b/static/openbsd/man4/urtwn.4 new file mode 100644 index 00000000..8d7f0d47 --- /dev/null +++ b/static/openbsd/man4/urtwn.4 @@ -0,0 +1,204 @@ +.\" $OpenBSD: urtwn.4,v 1.59 2025/10/27 17:47:46 hshoexer Exp $ +.\" +.\" Copyright (c) 2010 Damien Bergamini +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 27 2025 $ +.Dt URTWN 4 +.Os +.Sh NAME +.Nm urtwn +.Nd Realtek RTL8188CU/RTL8188EU/RTL8188FTV/RTL8192CU/RTL8192EU USB IEEE 802.11b/g/n wireless +network device +.Sh SYNOPSIS +.Cd "urtwn* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver supports USB 2.0 wireless network devices based on Realtek +RTL8188CU, RTL8188CE-VAU, RTL8188EU, RTL8188FTV, RTL8188RU, RTL8192CU +and RTL8192EU chipsets. +.Pp +The RTL8188CU, RTL8188EU and RTL8188FTV are highly integrated 802.11n adapters +that combine a MAC, a 1T1R capable baseband and an RF in a single chip. +They operate in the 2GHz spectrum only. +The RTL8188RU is a high-power variant of the RTL8188CU. +The RTL8188CE-VAU is a PCI Express Mini Card adapter that attaches +to the USB interface. +.Pp +The RTL8192CU and RTL8192EU are highly integrated multiple-in, multiple-out +(MIMO) 802.11n adapters that combine a MAC, a 2T2R capable baseband and an +RF in a single chip. +They operate in the 2GHz spectrum only. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The adapter needs firmware files to run, which are loaded on demand by +the driver when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/urtwn-rtl8192cT +.It Pa /etc/firmware/urtwn-rtl8192cU +.It Pa /etc/firmware/urtwn-rtl8192eu +.It Pa /etc/firmware/urtwn-rtl8188eu +.It Pa /etc/firmware/urtwn-rtl8188ftv +.El +.Sh HARDWARE +The following adapters should work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Airlink101 AWLL5088 +.It Alfa AWUS036NHR +.It Approx APPUSB300NANO V1 +.It Aus. Linx AL-9604R1S +.It Asus USB-N10 NANO +.It Asus USB-N10 NANO B1 +.It B-Link BL-LW05-5R +.It Belkin F7D1102 Surf Wireless Micro +.It Comfast CF-WU710N v4 +.It D-Link DWA-121 +.It D-Link DWA-123 rev \&D1 +.It D-Link DWA-125 rev \&D1 +.It D-Link DWA-131 rev B, E1 +.It D-Link DWA-133 +.It D-Link DWA-135 +.It Digitus DN-7042 +.It Edimax EW-7811Un +.It Edimax EW-7811Un v2 +.It EDUP EP-N8508 +.It Elecom WDC-150SU2M +.It Full River FR-W100NUL +.It Hercules Wireless N USB Pico HWNUp-150 +.It IO-DATA WN-G150UM +.It ISY IWL4000 USB Wireless Micro Adapter +.It Mercusys MW150US V2 +.It Netgear WNA1000A +.It Netgear WNA1000M +.It Netgear WNA1000Mv2 +.It On Networks N300MA +.It Patriot PCUSBW1150 +.It Planex GW-USEco300 +.It Planex GW-USNano2 +.It Planex GW-USValue-EZ +.It Planex GW-USWExtreme +.It POWCHIP POW-N18 +.It Prolink WN2201 +.It Sitecom WL-365 +.It Sitecom WLA-2100 v2 +.It Solwise NET-WL-UMD-606N +.It TP-LINK TL-WN722N v2 +.It TP-LINK TL-WN723N v3 +.It TP-LINK TL-WN725N v2 +.It TP-LINK TL-WN821N v4 +.It TP-LINK TL-WN821N v5 +.It TP-LINK TL-WN822N v4 +.It TP-LINK TL-WN822N v5 +.It TP-LINK TL-WN823N v3 +.It TRENDnet TEW-648UBM +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig urtwn0 scan +.Pp +The following +.Xr hostname.if 5 +example configures urtwn0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "urtwn0: error N, could not read firmware ..." +For some reason, the driver was unable to read the microcode file from the +filesystem. +The file might be missing or corrupted. +.It "urtwn0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . +.Sh CAVEATS +The +.Nm +driver does not support any of the 802.11n capabilities offered by the +adapters. +Additional work is required in +.Xr ieee80211 9 +before those features can be supported. diff --git a/static/openbsd/man4/usb.4 b/static/openbsd/man4/usb.4 new file mode 100644 index 00000000..2472677e --- /dev/null +++ b/static/openbsd/man4/usb.4 @@ -0,0 +1,704 @@ +.\" $OpenBSD: usb.4,v 1.222 2025/05/23 03:06:09 kevlo Exp $ +.\" $NetBSD: usb.4,v 1.15 1999/07/29 14:20:32 augustss Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 23 2025 $ +.Dt USB 4 +.Os +.Sh NAME +.Nm usb , +.Nm uhub +.Nd introduction to Universal Serial Bus support +.Sh SYNOPSIS +.Cd "# arm specific" +.Cd "mtxhci* at fdt?" +.Cd "usb* at mtxhci?" +.Pp +.Cd "# octeon specific" +.Cd "dwctwo0 at iobus? irq 56" +.Pp +.Cd "# all architectures" +.Cd "ehci* at cardbus?" +.Cd "ohci* at cardbus?" +.Cd "uhci* at cardbus?" +.Cd "ehci* at fdt?" +.Cd "ohci* at fdt?" +.Cd "xhci* at fdt?" +.Cd "ehci* at pci?" +.Cd "ohci* at pci?" +.Cd "uhci* at pci?" +.Cd "xhci* at pci?" +.Cd "usb* at dwctwo?" +.Cd "usb* at ehci? flags 0x00" +.Cd "usb* at ohci? flags 0x00" +.Cd "usb* at uhci? flags 0x00" +.Cd "usb* at xhci? flags 0x00" +.Cd "uhub* at usb?" +.Cd "uhub* at uhub?" +.Pp +.Cd option USBVERBOSE +.Pp +.In dev/usb/usb.h +.In dev/usb/usbhid.h +.Sh DESCRIPTION +.Ox +provides machine-independent bus support and drivers for Universal +Serial Bus (USB) devices. +.Pp +The +.Ox +.Nm +driver has three layers (like +.Xr scsi 4 +and +.Xr pcmcia 4 ) : +the controller, the bus, and the device layer. +The controller attaches to a physical bus (like +.Xr pci 4 +or +.Xr cardbus 4 ) . +The USB bus attaches to the controller and the root hub attaches +to the USB bus. +Devices, which may include further hubs, attach to the root hub. +The attachment forms the same tree structure as the physical USB +device tree. +For each USB device there may be additional drivers attached to it. +.Pp +The +.Cm uhub +driver controls USB hubs and must always be present since there is +at least one root hub in any USB system. +.Pp +The +.Cm flags +are used to specify if the devices on the USB bus should be probed +early in the boot process. +If the +.Cm flags +are specified with a value of 1, the USB bus will be probed when +the USB host device is attached instead of waiting until kernel +processes start running. +.Pp +.Ox +provides support for the following devices. +Note that not all architectures support all devices. +.Ss Storage devices +.Bl -tag -width 12n -offset ind -compact +.It Xr umass 4 +USB Mass Storage Devices, e.g., external disk drives +.El +.Ss Wired network interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr aue 4 +ADMtek AN986/ADM8511 Pegasus family 10/100 USB Ethernet device +.It Xr axe 4 +ASIX Electronics AX88172/AX88178/AX88772 10/100/1Gb USB Ethernet device +.It Xr axen 4 +ASIX Electronics AX88179/AX88179A/AX88772D 10/100/1Gb USB Ethernet device +.It Xr cdce 4 +USB Communication Device Class Ethernet device +.It Xr cue 4 +CATC USB-EL1201A USB Ethernet device +.It Xr kue 4 +Kawasaki LSI KL5KUSB101B USB Ethernet device +.It Xr mos 4 +MosChip MCS7730/7830/7832 10/100 USB Ethernet device +.It Xr mue 4 +Microchip LAN75xx/LAN78xx 10/100/1Gb USB Ethernet device +.It Xr smsc 4 +SMSC LAN95xx 10/100 USB Ethernet device +.It Xr uaq 4 +Aquantia AQC111U/AQC112U 100/1Gb/2.5Gb/5Gb USB Ethernet device +.It Xr udav 4 +Davicom DM9601 10/100 USB Ethernet device +.It Xr ure 4 +Realtek RTL8152/RTL8153/RTL8156/RTL8157 10/100/1Gb/2.5Gb/5Gb USB Ethernet device +.It Xr url 4 +Realtek RTL8150L 10/100 USB Ethernet device +.It Xr urndis 4 +USB Remote NDIS Ethernet device +.El +.Ss Wireless network interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr athn 4 +Atheros IEEE 802.11a/b/g/n wireless network device +.It Xr atu 4 +Atmel AT76C50x IEEE 802.11b wireless network device +.It Xr bwfm 4 +Broadcom and Cypress IEEE 802.11a/ac/ax/b/g/n wireless network device +.It Xr mtw 4 +MediaTek USB IEEE 802.11b/g/n wireless network device +.It Xr otus 4 +Atheros USB IEEE 802.11a/b/g/n wireless network device +.It Xr rsu 4 +Realtek RTL8188SU/RTL8192SU USB IEEE 802.11b/g/n wireless network device +.It Xr rum 4 +Ralink Technology/MediaTek USB IEEE 802.11a/b/g wireless network device +.It Xr run 4 +Ralink Technology/MediaTek USB IEEE 802.11a/b/g/n wireless network device +.It Xr uath 4 +Atheros USB IEEE 802.11a/b/g wireless network device +.It Xr upgt 4 +Conexant/Intersil PrismGT SoftMAC USB IEEE 802.11b/g wireless network device +.It Xr ural 4 +Ralink Technology/MediaTek USB IEEE 802.11b/g wireless network device +.It Xr urtw 4 +Realtek RTL8187L/RTL8187B USB IEEE 802.11b/g wireless network device +.It Xr urtwn 4 +Realtek RTL8188CU/RTL8188EU/RTL8188FTV/RTL8192CU/RTL8192EU USB IEEE 802.11b/g/n wireless +network device +.It Xr wi 4 +Intersil PRISM 2-3 IEEE 802.11b wireless network device +.It Xr zyd 4 +ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless network device +.El +.Ss Serial and parallel interfaces +.Bl -tag -width 12n -offset ind -compact +.It Xr moscom 4 +MosChip Semiconductor MCS7703 based USB serial adapter +.It Xr uark 4 +Arkmicro Technologies ARK3116 based USB serial adapter +.It Xr ubsa 4 +Belkin USB serial adapter +.It Xr uchcom 4 +WinChipHead CH9102/343/341/340 based USB serial adapter +.It Xr ucom 4 +USB tty support +.It Xr ucrcom 4 +Chromebook USB serial console +.It Xr ucycom 4 +Cypress microcontroller based USB serial adapter +.It Xr uftdi 4 +FTDI USB serial adapter +.It Xr uipaq 4 +iPAQ USB units +.It Xr ukspan 4 +Keyspan USB serial adapter +.It Xr ulpt 4 +USB printer support +.It Xr umcs 4 +MosChip Semiconductor based USB multiport serial adapter +.It Xr umct 4 +MCT USB-RS232 USB serial adapter +.It Xr umodem 4 +USB modem support +.It Xr umsm 4 +Qualcomm MSM modem device +.It Xr uplcom 4 +Prolific PL-2303 USB serial adapter +.It Xr uscom 4 +simple USB serial adapters +.It Xr uslcom 4 +Silicon Laboratories CP210x based USB serial adapter +.It Xr uslhcom 4 +Silicon Laboratories CP2110 based USB serial adapter +.It Xr uticom 4 +Texas Instruments TUSB3410 USB serial adapter +.It Xr uvisor 4 +USB Handspring Visor +.It Xr uvscom 4 +SUNTAC Slipper U VS-10U USB serial adapter +.It Xr uxrcom 4 +Exar XR21V1410 USB serial adapter +.El +.Ss Audio devices +.Bl -tag -width 12n -offset ind -compact +.It Xr uaudio 4 +USB audio devices +.It Xr umidi 4 +USB MIDI devices +.El +.Ss Video devices +.Bl -tag -width 12n -offset ind -compact +.It Xr udl 4 +DisplayLink DL-120/DL-160 USB display devices +.It Xr utvfu 4 +USB Fushicai USBTV007 audio/video capture device +.It Xr uvideo 4 +USB video devices +.El +.Ss Time receiver devices +.Bl -tag -width 12n -offset ind -compact +.It Xr udcf 4 +Gude ADS Expert mouseCLOCK USB timedelta sensor +.It Xr umbg 4 +Meinberg Funkuhren USB5131 timedelta sensor +.El +.Ss Radio receiver devices +.Bl -tag -width 12n -offset ind -compact +.It Xr udsbr 4 +D-Link DSB-R100 USB radio device +.El +.Ss Human Interface Devices +.Bl -tag -width 12n -offset ind -compact +.It Xr fido 4 +FIDO/U2F security keys +.It Xr ubcmtp 4 +Broadcom trackpad mouse +.It Xr ucc 4 +Consumer Control keyboards +.It Xr ugold 4 +TEMPer gold HID thermometer and hygrometer +.It Xr uhid 4 +Generic driver for Human Interface Devices +.It Xr uhidev 4 +Base driver for all Human Interface Devices +.It Xr uhidpp 4 +Logitech HID++ devices +.It Xr ujoy 4 +USB joysticks/gamecontrollers +.It Xr ukbd 4 +USB keyboards that follow the boot protocol +.It Xr ums 4 +USB HID mouse, touchscreen and digitiser devices +.It Xr umstc 4 +Microsoft Surface Type Cover keyboard +.It Xr umt 4 +USB HID multitouch touchpad devices +.It Xr uoaklux 4 +Toradex OAK USB illuminance sensor +.It Xr uoakrh 4 +Toradex OAK USB temperature and relative humidity sensor +.It Xr uoakv 4 +Toradex OAK USB +/-10V 8channel ADC interface +.It Xr upd 4 +USB Power Devices sensor +.It Xr uthum 4 +TEMPer HID thermometer and hygrometer +.It Xr utpms 4 +Apple touchpad mouse +.It Xr utrh 4 +USBRH temperature and humidity sensor +.It Xr utwitch 4 +YUREX USB twitch/jiggle of knee sensor +.It Xr uwacom 4 +Wacom USB tablets +.El +.Ss WAN network devices +.Bl -tag -width 12n -offset ind -compact +.It Xr umb 4 +USB Mobile Broadband Interface Model (MBIM) +.El +.Ss Miscellaneous devices +.Bl -tag -width 12n -offset ind -compact +.It Xr uberry 4 +Research In Motion BlackBerry +.It Xr ugen 4 +USB generic device support +.It Xr ugl 4 +Genesys Logic based host-to-host adapters +.It Xr uonerng 4 +Moonbase Otago OneRNG TRNG +.It Xr uow 4 +Maxim/Dallas DS2490 USB 1-Wire adapter +.It Xr upl 4 +Prolific based host-to-host adapters +.It Xr urng 4 +USB Random Number Generator devices +.It Xr usps 4 +USPS composite AC power and temperature sensor +.It Xr uts 4 +USB touchscreen support +.El +.Sh INTRODUCTION TO USB +There are different versions of the USB +which provide different speeds. +USB 3 can operate up to 5.0Gb/s. +USB 2 operates at 480Mb/s, while USB versions 1 and 1.1 operate at +12 Mb/s and 1.5 Mb/s for low speed devices. +Each USB has a host controller that is the master of the bus; +all other devices on the bus only speak when spoken to. +.Pp +There can be up to 127 devices (apart from the host controller) +on a bus, each with its own address. +The addresses are assigned +dynamically by the host when each device is attached to the bus. +.Pp +Within each device there can be up to 16 endpoints. +Each endpoint +is individually addressed and the addresses are static. +Each of these endpoints will communicate in one of four different modes: +control, isochronous, bulk, or interrupt. +A device always has at least one endpoint. +This is a control endpoint at address 0 +and is used to give commands to the device and extract basic data, +such as descriptors, from the device. +Each endpoint, except the control endpoint, is unidirectional. +.Pp +The endpoints in a device are grouped into interfaces. +An interface is a logical unit within a device; e.g., +a compound device with both a keyboard and a trackball would present +one interface for each. +An interface can sometimes be set into different modes, +called alternate settings, which affects how it operates. +Different alternate settings can have different endpoints +within it. +.Pp +A device may operate in different configurations. +Depending on the +configuration the device may present different sets of endpoints +and interfaces. +.Pp +Each device located on a hub has several +.Xr config 8 +locators: +.Pp +.Bl -tag -width configuration -compact +.It Cd port +Number of the port on closest upstream hub. +.It Cd configuration +Configuration the device must be in for this driver to attach. +This locator does not set the configuration; it is iterated by the bus +enumeration. +.It Cd interface +Interface number within a device that an interface driver attaches to. +.It Cd vendor +16-bit vendor ID of the device. +.It Cd product +16-bit product ID of the device. +.It Cd release +16-bit release (revision) number of the device. +.El +.Pp +The first locator can be used to pin down a particular device +according to its physical position in the device tree. +The last three locators can be used to pin down a particular +device according to what device it actually is. +.Pp +The bus enumeration of the USB bus proceeds in several steps: +.Bl -enum +.It +Any device-specific driver can attach to the device. +.It +If none is found, any device class specific driver can attach. +.It +If none is found, all configurations are iterated over. +For each configuration all the interfaces are iterated over and interface +drivers can attach. +If any interface driver attached in a certain +configuration, the iteration over configurations is stopped. +.It +If still no drivers have been found, the generic USB driver can attach. +.El +.Sh USB CONTROLLER INTERFACE +Use the following to get access to the USB specific structures +and defines: +.Bd -literal -offset indent +#include +.Ed +.Pp +The +.Pa /dev/usbN +device can be opened and a few operations can be performed on it. +The following +.Xr ioctl 2 +commands are supported on the controller device: +.Bl -tag -width xxxxxx +.It Dv USB_DEVICEINFO Fa "struct usb_device_info" +This command can be used to retrieve some information about a device +on the bus. +The +.Va udi_addr +field should be filled before the call and the other fields will +be filled by information about the device on that address. +Should no such device exist, an error is reported. +.Bd -literal +#define USB_MAX_DEVNAMES 4 +#define USB_MAX_DEVNAMELEN 16 +struct usb_device_info { + u_int8_t udi_bus; + u_int8_t udi_addr; /* device address */ + char udi_product[USB_MAX_STRING_LEN]; + char udi_vendor[USB_MAX_STRING_LEN]; + char udi_release[8]; + u_int16_t udi_productNo; + u_int16_t udi_vendorNo; + u_int16_t udi_releaseNo; + u_int8_t udi_class; + u_int8_t udi_subclass; + u_int8_t udi_protocol; + u_int8_t udi_config; + u_int8_t udi_speed; +#define USB_SPEED_LOW 1 +#define USB_SPEED_FULL 2 +#define USB_SPEED_HIGH 3 +#define USB_SPEED_SUPER 4 + u_int8_t udi_port; + int udi_power; /* power consumption */ + int udi_nports; + char udi_devnames[USB_MAX_DEVNAMES] + [USB_MAX_DEVNAMELEN]; + u_int32_t udi_ports[16]; /* hub only */ + char udi_serial[USB_MAX_STRING_LEN]; +}; +.Ed +.Pp +The +.Va udi_bus +field contains the device unit number of the device. +.Pp +The +.Va udi_product , +.Va udi_vendor , +and +.Va udi_release +fields contain self-explanatory descriptions of the device. +The +.Va udi_productNo , +.Va udi_vendorNo , +and +.Va udi_releaseNo +fields contain numeric identifiers for the device. +.Pp +The +.Va udi_class +and +.Va udi_subclass +fields contain the device class and subclass. +.Pp +The +.Va udi_config +field shows the current configuration of the device. +.Pp +The +.Va udi_protocol +field contains the device protocol as given from the device. +.Pp +The +.Va udi_speed +field +contains the speed of the device. +.Pp +The +.Va udi_power +field shows the power consumption in milli-amps drawn at 5 volts +or is zero if the device is self powered. +.Pp +The +.Va udi_devnames +field contains the names and instance numbers of the device drivers +for the devices attached to this device. +.Pp +If the device is a hub, the +.Va udi_nports +field is non-zero and the +.Va udi_ports +field contains the addresses of the connected devices. +If no device is connected to a port, one of the +.Dv USB_PORT_* +values indicates its status. +.It Dv USB_DEVICESTATS Fa "struct usb_device_stats" +This command retrieves statistics about the controller. +.Bd -unfilled +struct usb_device_stats { + u_long uds_requests[4]; +}; +.Ed +.Pp +The +.Va uds_requests +field is indexed by the transfer kind, i.e.\& +.Dv UE_* , +and indicates how many transfers of each kind have been completed +by the controller. +.It Dv USB_DEVICE_GET_DDESC Fa "struct usb_device_ddesc" +This command can be used to retrieve the device descriptor +of a device on the bus. +The +.Va udd_addr +field needs to be filled with the bus device address: +.Bd -literal +struct usb_device_ddesc { + u_int8_t udd_bus; + u_int8_t udd_addr; /* device address */ + usb_device_descriptor_t udd_desc; +}; +.Ed +.Pp +The +.Va udd_bus +field contains the device unit number. +.Pp +The +.Va udd_desc +field contains the device descriptor structure. +.It Dv USB_DEVICE_GET_CDESC Fa "struct usb_device_cdesc" +This command can be used to retrieve the configuration descriptor for the +given configuration of a device on the bus. +The +.Va udc_addr +field needs to be filled with the bus device address. +The +.Va udc_config_index +field needs to be filled with the configuration index for the +relevant configuration descriptor. +For convenience the current configuration can be specified by +.Dv USB_CURRENT_CONFIG_INDEX : +.Bd -literal +struct usb_device_cdesc { + u_int8_t udc_bus; + u_int8_t udc_addr; /* device address */ + int udc_config_index; + usb_config_descriptor_t udc_desc; +}; +.Ed +.Pp +The +.Va udc_bus +field contains the device unit number. +.Pp +The +.Va udc_desc +field contains the configuration descriptor structure. +.It Dv USB_DEVICE_GET_FDESC Fa "struct usb_device_fdesc" +This command can be used to retrieve all descriptors for the +given configuration of a device on the bus. +The +.Va udf_addr +field needs to be filled with the bus device address. +The +.Va udf_config_index +field needs to be filled with the configuration index for the +relevant configuration descriptor. +For convenience the current configuration can be specified by +.Dv USB_CURRENT_CONFIG_INDEX . +The +.Va udf_data +field needs to point to a memory area of the size given in the +.Va udf_size +field. +The proper size can be determined by first issuing a +.Dv USB_DEVICE_GET_CDESC +command and inspecting the +.Va wTotalLength +field: +.Bd -literal +struct usb_device_fdesc { + u_int8_t udf_bus; + u_int8_t udf_addr; /* device address */ + int udf_config_index; + u_int udf_size; + u_char *udf_data; +}; +.Ed +.Pp +The +.Va udf_bus +field contains the device unit number. +.Pp +The +.Va udf_data +field contains all descriptors. +.It Dv USB_REQUEST Fa "struct usb_ctl_request" +This command can be used to execute arbitrary requests on the control pipe. +This is +.Em DANGEROUS +and should be used with great care since it +can destroy the bus integrity. +.Pp +The +.Vt usb_ctl_request +structure has the following definition: +.Bd -literal +typedef struct { + uByte bmRequestType; + uByte bRequest; + uWord wValue; + uWord wIndex; + uWord wLength; +} __packed usb_device_request_t; + +struct usb_ctl_request { + int ucr_addr; + usb_device_request_t ucr_request; + void *ucr_data; + int ucr_flags; +#define USBD_SHORT_XFER_OK 0x04 /* allow short reads */ + int ucr_actlen; /* actual length transferred */ +}; +.Ed +.Pp +The +.Va ucr_addr +field identifies the device on which to perform the request. +The +.Va ucr_request +field identifies parameters of the request, such as length and type. +The +.Va ucr_data +field contains the location where data will be read from or written to. +The +.Va ucr_flags +field specifies options for the request, and the +.Va ucr_actlen +field contains the actual length transferred as the result of the request. +.El +.Pp +The include file +.In dev/usb/usb.h +contains definitions for the types used by the various +.Xr ioctl 2 +calls. +The naming convention of the fields for the various USB descriptors +exactly follows the naming in the USB specification. +Byte sized fields can be accessed directly, but word (16-bit) +sized fields must be accessed by the +.Fn UGETW field +and +.Fn USETW field value +macros and double word (32-bit) sized fields must be accessed by the +.Fn UGETDW field +and +.Fn USETDW field value +macros to handle byte order and alignment properly. +.Pp +The include file +.In dev/usb/usbhid.h +similarly contains the definitions for +Human Interface Devices (HID). +.Sh SEE ALSO +.Xr usbhidaction 1 , +.Xr usbhidctl 1 , +.Xr ioctl 2 , +.Xr dwctwo 4 , +.Xr ehci 4 , +.Xr ohci 4 , +.Xr uhci 4 , +.Xr xhci 4 , +.Xr config 8 , +.Xr usbdevs 8 +.Pp +The USB specifications can be found at: +.Lk https://www.usb.org/documents +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 2.6 . diff --git a/static/openbsd/man4/uscom.4 b/static/openbsd/man4/uscom.4 new file mode 100644 index 00000000..0c250bfb --- /dev/null +++ b/static/openbsd/man4/uscom.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: uscom.4,v 1.4 2019/02/24 17:37:42 patrick Exp $ +.\" +.\" Copyright (c) 2006 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 24 2019 $ +.Dt USCOM 4 +.Os +.Sh NAME +.Nm uscom +.Nd simple USB serial adapters +.Sh SYNOPSIS +.Cd "uscom* at uhub?" +.Cd "ucom* at uscom?" +.Sh DESCRIPTION +The +.Nm +driver supports simple USB serial adapters that don't need a custom driver. +.Pp +The following devices should work with the +.Nm +driver: +.Bd -literal -offset indent +HP 39G +HP 49G +Dynastream ANT USB-2 Stick +Dynastream ANT USB-m Stick +.Ed +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.6 . diff --git a/static/openbsd/man4/uslcom.4 b/static/openbsd/man4/uslcom.4 new file mode 100644 index 00000000..34976866 --- /dev/null +++ b/static/openbsd/man4/uslcom.4 @@ -0,0 +1,84 @@ +.\" $OpenBSD: uslcom.4,v 1.16 2021/12/13 13:57:48 visa Exp $ +.\" +.\" Copyright (c) 2006 Jonathan Gray +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 13 2021 $ +.Dt USLCOM 4 +.Os +.Sh NAME +.Nm uslcom +.Nd Silicon Laboratories CP210x based USB serial adapter +.Sh SYNOPSIS +.Cd "uslcom* at uhub?" +.Cd "ucom* at uslcom?" +.Sh DESCRIPTION +The +.Nm +driver supports Silicon Laboratories CP2101/CP2102/CP2103/CP2104/CP2105/CP2108 +based serial adapters. +.Pp +The CP2101/CP2102/CP2103 devices only support a variety of baud rates +up to 921600. +CP2104, CP2105 and CP2108 devices support any baud rate up to 2 Mbps. +.Pp +The following devices should work with the +.Nm +driver: +.Bd -literal -offset indent +Aerocomm Radio +Argussoft ISP +Aruba Networks USB-to-UART +Baltech card reader +Burnside Telecom Desktop Mobile +chip45.com Crumb128 module +Clipsal 5500PCU C-Bus +Dynastream ANT2USB +Elan Digital Systems USBscope50 +Elan Digital Systems USBwave12 +Elan Digital Systems USBpulse100 +Elan Digital Systems USBcount50 +Enfora EDG1228 +Gemalto Prox-PU/CU Smartcard Readers +IRZ MC35pu GSM Terminal +Jablotron PC-60B +Juniper SRX 300/320/340/345/550M/1500 USB console +Lipowsky Baby-JTAG +Lipowsky Baby-LIN +Lipowsky HARP-1 +MobiData GPRS Modem +Pololu USB to Serial +Ruckus ICX 7150 USB console +SPORTident BSM7-D-USB +Tracient RFID +Track Systems Traqmate +West Mountain Radio RIGblaster P&P +West Mountain Radio RIGtalk +.Ed +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jonathan Gray Aq Mt jsg@openbsd.org . diff --git a/static/openbsd/man4/uslhcom.4 b/static/openbsd/man4/uslhcom.4 new file mode 100644 index 00000000..e7f31aae --- /dev/null +++ b/static/openbsd/man4/uslhcom.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: uslhcom.4,v 1.2 2015/01/05 19:59:40 uaa Exp $ +.\" +.\" Copyright (c) 2015 Takayoshi SASANO +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 5 2015 $ +.Dt USLHCOM 4 +.Os +.Sh NAME +.Nm uslhcom +.Nd Silicon Laboratories CP2110 based USB serial adapter +.Sh SYNOPSIS +.Cd "uslhcom* at uhidev?" +.Cd "ucom* at uslhcom?" +.Sh DESCRIPTION +The +.Nm +driver supports USB HID (Human Interface Device) based serial adapters. +The following devices are supported: +.Pp +.Bl -tag -width Dev -offset indent -compact +.It Silicon Laboratory CP2110 +.El +.Pp +The driver acts as a bridge between +.Xr uhidev 4 +and the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhidev 4 , +.Xr usb 4 diff --git a/static/openbsd/man4/usps.4 b/static/openbsd/man4/usps.4 new file mode 100644 index 00000000..ab9e7422 --- /dev/null +++ b/static/openbsd/man4/usps.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: usps.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2011 Yojiro UO +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt USPS 4 +.Os +.Sh NAME +.Nm usps +.Nd USPS composite AC power and temperature sensor +.Sh SYNOPSIS +.Cd "usps* at uhub?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Fujitsu Component Smart Power Strip FX-5204PS. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +As well as AC voltage, +the device provides the electricity power supply frequency, +per port electricity consumption, +and device temperature. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Yojiro UO Aq Mt yuo@nui.org . diff --git a/static/openbsd/man4/uthum.4 b/static/openbsd/man4/uthum.4 new file mode 100644 index 00000000..d7fe89f0 --- /dev/null +++ b/static/openbsd/man4/uthum.4 @@ -0,0 +1,63 @@ +.\" $OpenBSD: uthum.4,v 1.8 2013/09/06 18:11:42 jmc Exp $ +.\" +.\" Copyright (c) 2009 Yojiro UO +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 6 2013 $ +.Dt UTHUM 4 +.Os +.Sh NAME +.Nm uthum +.Nd TEMPer HID thermometer and hygrometer +.Sh SYNOPSIS +.Cd "uthum* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for pcsensors TEMPer devices. +The following devices are supported by the +.Nm +driver: +.Bl -column "TEMPerNTCXXX" "Sensors" -offset indent +.It Em "Device" Ta Em "Sensors" +.It Li "TEMPerHUM" Ta "1 Temperature and 1 Humidity" +.It Li "TEMPer" Ta "1 Temperature (internal)" +.It Li "TEMPer1" Ta "1 Temperature (external)" +.It Li "TEMPer2" Ta "2 Temperature (internal/external)" +.It Li "TEMPerNTC" Ta "2 Temperature (internal/external)" +.El +.Pp +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +The humidity data unit is "%RH" (relative humidity) and the +temperature data unit is "degC". +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhidev 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Yojiro UO Aq Mt yuo@nui.org . +.Sh BUGS +There is not enough support for the external temperature sensor +of the TEMPerNTC. +Currently the +.Nm +driver supports about 0 degC to 120 degC for the sensor. diff --git a/static/openbsd/man4/uticom.4 b/static/openbsd/man4/uticom.4 new file mode 100644 index 00000000..10aa7316 --- /dev/null +++ b/static/openbsd/man4/uticom.4 @@ -0,0 +1,78 @@ +.\" $OpenBSD: uticom.4,v 1.8 2013/07/16 16:05:49 schwarze Exp $ +.\" Copyright (c) 2007 +.\" The DragonFly Project. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in +.\" the documentation and/or other materials provided with the +.\" distribution. +.\" 3. Neither the name of The DragonFly Project nor the names of its +.\" contributors may be used to endorse or promote products derived +.\" from this software without specific, prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT +.\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS +.\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE +.\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT +.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt UTICOM 4 +.Os +.Sh NAME +.Nm uticom +.Nd Texas Instruments TUSB3410 USB serial adapter +.Sh SYNOPSIS +.Cd "uticom* at uhub?" +.Cd "ucom* at uticom?" +.Sh DESCRIPTION +The +.Nm +driver supports serial port functionality on devices based on the +Texas Instruments TUSB3410 serial to USB converter chip. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Dmitry Komissaroff Aq Mt dxi@mail.ru +and +.An Hasso Tepper Aq Mt hasso@estpak.ee . +.Sh CAVEATS +The +.Nm +driver doesn't support devices that have an internal EEPROM with firmware, +since such firmware is different to that supplied with +.Ox . +.Pp +Devices with multiple ports will attach all ports, though only +the first port can be used for now. diff --git a/static/openbsd/man4/utpms.4 b/static/openbsd/man4/utpms.4 new file mode 100644 index 00000000..b0c40d79 --- /dev/null +++ b/static/openbsd/man4/utpms.4 @@ -0,0 +1,59 @@ +.\" $OpenBSD: utpms.4,v 1.3 2013/06/01 17:37:47 jmc Exp $ +.\" +.\" Copyright (c) 1999, 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 1 2013 $ +.Dt UTPMS 4 +.Os +.Sh NAME +.Nm utpms +.Nd Apple touchpad mouse +.Sh SYNOPSIS +.Cd "utpms* at uhidev?" +.Cd "wsmouse* at utpms? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides support for the touchpads +on new Apple PowerBooks and iBooks that are +not standard USB HID mice. +Access to the mouse is through the +.Xr wscons 4 +driver. +.Sh SEE ALSO +.Xr uhidev 4 , +.Xr usb 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Ox 3.9 , +originally called +.Nm tpms . diff --git a/static/openbsd/man4/utrh.4 b/static/openbsd/man4/utrh.4 new file mode 100644 index 00000000..f58d05d7 --- /dev/null +++ b/static/openbsd/man4/utrh.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: utrh.4,v 1.4 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Yojiro UO +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt UTRH 4 +.Os +.Sh NAME +.Nm utrh +.Nd USBRH temperature and humidity sensor +.Sh SYNOPSIS +.Cd "utrh* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Strawberry Linux's USBRH device. +The sensor possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +The humidity data unit is "%RH" and the temperature data unit +is "degC". +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhidev 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Yojiro UO Aq Mt yuo@nui.org . diff --git a/static/openbsd/man4/uts.4 b/static/openbsd/man4/uts.4 new file mode 100644 index 00000000..d8b6a28a --- /dev/null +++ b/static/openbsd/man4/uts.4 @@ -0,0 +1,72 @@ +.\" $OpenBSD: uts.4,v 1.13 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Robert Nagy +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt UTS 4 +.Os +.Sh NAME +.Nm uts +.Nd USB touchscreen support +.Sh SYNOPSIS +.Cd "uts* at uhub?" +.Cd "wsmouse* at uts? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides support for USB touchscreens. +Access to the touchscreen is provided through the +.Xr wscons 4 +framework. +.Pp +Touching the screen will emulate mouse button 0 being pressed. +.Pp +The touchscreen sensor is poorly aligned, therefore +.Xr xtsscale 1 +should be used to provide calibration results to the +.Nm +driver. +.Pp +The +.Nm +driver works with the following touchscreens and panels: +.Pp +.Bl -dash -offset indent -compact +.It +Gunze USB Touch Panel +.It +Hantouch +.It +LG L1510SF LCD Monitor +.It +Origin AE X15e HTPC case with 7" LCD +.El +.Sh SEE ALSO +.Xr xtsscale 1 , +.Xr uhub 4 , +.Xr usb 4 , +.Xr wscons 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.2 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Robert Nagy Aq Mt robert@openbsd.org . diff --git a/static/openbsd/man4/utvfu.4 b/static/openbsd/man4/utvfu.4 new file mode 100644 index 00000000..bab7cb5b --- /dev/null +++ b/static/openbsd/man4/utvfu.4 @@ -0,0 +1,58 @@ +.\" $OpenBSD: utvfu.4,v 1.4 2016/06/04 20:54:13 jmc Exp $ +.\" +.\" Copyright (c) 2016 Patrick Keshishian. All rights reserved. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 4 2016 $ +.Dt UTVFU 4 +.Os +.Sh NAME +.Nm utvfu +.Nd USB Fushicai USBTV007 audio/video capture device +.Sh SYNOPSIS +.Cd "utvfu* at uhub?" +.Cd "audio* at utvfu?" +.Cd "video* at utvfu?" +.Sh DESCRIPTION +The +.Nm +driver supports USB Audio/Video capture devices based on the Fushicai +USBTV007 chip. +The following product models are known to work: +.Pp +.Bl -bullet -offset indent -compact +.It +Play X Store Capture +.It +YXGOOD EasyCAP +.El +.Pp +If the +.Nm +device attaches successfully, it will attach the +.Xr audio 4 +and +.Xr video 4 +drivers to provide higher-level access. +.Sh SEE ALSO +.Xr audio 4 , +.Xr intro 4 , +.Xr usb 4 , +.Xr video 4 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Ox 6.0 . diff --git a/static/openbsd/man4/utwitch.4 b/static/openbsd/man4/utwitch.4 new file mode 100644 index 00000000..7ef83639 --- /dev/null +++ b/static/openbsd/man4/utwitch.4 @@ -0,0 +1,55 @@ +.\" $OpenBSD: utwitch.4,v 1.5 2013/08/07 06:37:02 jmc Exp $ +.\" +.\" Copyright (c) 2010 Yojiro UO +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 7 2013 $ +.Dt UTWITCH 4 +.Os +.Sh NAME +.Nm utwitch +.Nd YUREX USB twitch/jiggle of knee sensor +.Sh SYNOPSIS +.Cd "utwitch* at uhidev?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Maywa-denki & KAYAC YUREX device. +The device has a sensor to count user's leg twitch and it +possesses a collection of sensor values which are +made available through the +.Xr sysctl 8 +interface. +The counter unit for twitch is "BBU" (BinBo-YUsuri or +Bounding Body from Unconsciousness) and the unit for BBU speed +is "mBBU/sec" (milli BBU per second). +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhidev 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Rs +.%T The YUREX Web Page +.%U http://bbu.kayac.com/en/about/ +.Re +.Sh HISTORY +The +.Nm +driver was originally named uyurex. +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Yojiro UO Aq Mt yuo@nui.org . diff --git a/static/openbsd/man4/uvideo.4 b/static/openbsd/man4/uvideo.4 new file mode 100644 index 00000000..ef3dc3fe --- /dev/null +++ b/static/openbsd/man4/uvideo.4 @@ -0,0 +1,152 @@ +.\" $OpenBSD: uvideo.4,v 1.45 2025/08/14 13:14:44 kirill Exp $ +.\" +.\" Copyright (c) 2008 Ian Darwin. All rights reserved. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 14 2025 $ +.Dt UVIDEO 4 +.Os +.Sh NAME +.Nm uvideo +.Nd USB video devices +.Sh SYNOPSIS +.Cd "uvideo* at uhub?" +.Cd "video* at uvideo?" +.Sh DESCRIPTION +The +.Nm +driver supports a range of USB Video Class (UVC) devices including webcams, +camcorders and other cameras. +UVC is a generic specification and many USB video devices follow it. +The following models are known to work: +.Pp +.Bl -bullet -offset indent -compact +.It +Apple built-in iSight +.It +Chen-Source CM12402 Eagle IR Cam +.It +Chicony Electronics 4807 (Lenovo X300 647815G Notebooks) +.It +Dynex 1.3MP Webcam +.It +Elgato Facecam Pro +.It +eMPIA Technology 2761 (ASUS EeePC 701 Notebooks) +.It +Jabra PanaCast 20 +.It +Lenovo EasyCamera (Lenovo IdeaPad s10e Notebooks) +.It +Logitech QuickCam for Notebooks Pro +.It +Logitech QuickCam Communicate Deluxe +.It +Logitech QuickCam Communicate MP +.It +Logitech QuickCam Deluxe for Notebooks +.It +Logitech QuickCam E 3500 Plus +.It +Logitech QuickCam Fusion +.It +Logitech QuickCam OEM (Dell Notebooks) +.It +Logitech QuickCam Orbit AF +.It +Logitech QuickCam Orbit MP +.It +Logitech QuickCam Pro for Notebooks +.It +Logitech QuickCam Pro 5000 +.It +Logitech QuickCam Pro 9000 +.It +Logitech QuickCam Sphere AF +.It +Logitech QuickCam Sphere MP +.It +Logitech QuickCam Ultra Vision +.It +Logitech Webcam C200 +.It +Logitech Webcam C310 +.It +Logitech Webcam C500 +.It +Logitech Webcam C920 Pro +.It +Logitech Webcam C922 Pro +.It +Logitech Webcam C930e +.It +Logitech Webcam Pro 9000 +.It +Microsoft LifeCam NX-6000 +.It +Microsoft LifeCam VX-500 +.It +Microsoft LifeCam VX-700 +.It +OmniVision OV7670 (Dell XPS M1330 Notebooks) +.It +Panasonic NV-GS320 Camcorder +.It +Rocketfish 2MP AF Webcam +.It +Sonix USB 2.0 Camera +.It +SunplusIT Inc (Lenovo X1 Carbon 6th Generation Notebooks) +.It +SuYin Acer Crystal Eye (Acer AspireOne Notebooks) +.It +Vimicro Corp USB 2.0 Camera +.El +.Pp +If the +.Nm +device attaches successfully, it will attach the +.Xr video 4 +driver to provide higher-level access. +.Sh FILES +The driver needs a set of firmware for some devices which are loaded when +a device gets attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/uvideo_isight_05ac-8300 +.It Pa /etc/firmware/uvideo_r5u87x_05ca-1803 +.It Pa /etc/firmware/uvideo_r5u87x_05ca-1810 +.It Pa /etc/firmware/uvideo_r5u87x_05ca-1812 +.It Pa /etc/firmware/uvideo_r5u87x_05ca-1835 +.It Pa /etc/firmware/uvideo_r5u87x_05ca-1836 +.It Pa /etc/firmware/uvideo_r5u87x_05ca-1837 +.It Pa /etc/firmware/uvideo_r5u87x_05ca-1839 +.It Pa /etc/firmware/uvideo_r5u87x_05ca-183a +.It Pa /etc/firmware/uvideo_r5u87x_05ca-183b +.It Pa /etc/firmware/uvideo_r5u87x_05ca-183e +.It Pa /etc/firmware/uvideo_r5u87x_05ca-1841 +.El +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr usb 4 , +.Xr video 4 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Ox 4.4 . diff --git a/static/openbsd/man4/uvisor.4 b/static/openbsd/man4/uvisor.4 new file mode 100644 index 00000000..092703d0 --- /dev/null +++ b/static/openbsd/man4/uvisor.4 @@ -0,0 +1,63 @@ +.\" $OpenBSD: uvisor.4,v 1.7 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: uvisor.4,v 1.2 2000/03/31 13:08:01 hubertf Exp $ +.\" +.\" Copyright (c) 2000 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt UVISOR 4 +.Os +.Sh NAME +.Nm uvisor +.Nd USB Handspring Visor +.Sh SYNOPSIS +.Cd "uvisor* at uhub?" +.Cd "ucom* at uvisor?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Handspring Visor, a Palmpilot compatible PDA. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +The usual Pilot tools can be used to access the Visor. +.Sh SEE ALSO +.Xr intro 4 , +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver appeared in +.Nx 1.5 . +.Ox +support was added in +.Ox 2.8 . diff --git a/static/openbsd/man4/uvscom.4 b/static/openbsd/man4/uvscom.4 new file mode 100644 index 00000000..efd0cfc3 --- /dev/null +++ b/static/openbsd/man4/uvscom.4 @@ -0,0 +1,63 @@ +.\" $OpenBSD: uvscom.4,v 1.6 2008/06/26 05:42:07 ray Exp $ +.\" $NetBSD: uvscom.4,v 1.1 2002/03/19 15:17:49 augustss Exp $ +.\" +.\" Copyright (c) 2002 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Lennart Augustsson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: June 26 2008 $ +.Dt UVSCOM 4 +.Os +.Sh NAME +.Nm uvscom +.Nd SUNTAC Slipper U VS-10U USB serial adapter +.Sh SYNOPSIS +.Cd "uvscom* at uhub?" +.Cd "ucom* at uvscom?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SUNTAC Slipper U VS-10U chip. +Slipper U is a PC Card to USB converter for data communication card +adapters. +It supports DDI Pocket's Air H" C@rd, C@rd H" 64, NTT's P-in, +P-in m@ster, and various other data communication card adapters. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Fx +and later in +.Ox 3.3 . diff --git a/static/openbsd/man4/uwacom.4 b/static/openbsd/man4/uwacom.4 new file mode 100644 index 00000000..59b0d804 --- /dev/null +++ b/static/openbsd/man4/uwacom.4 @@ -0,0 +1,70 @@ +.\" $OpenBSD: uwacom.4,v 1.5 2023/08/12 20:49:29 miod Exp $ +.\" +.\" Copyright (c) 2016 Frank Groeneveld +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 12 2023 $ +.Dt UWACOM 4 +.Os +.Sh NAME +.Nm uwacom +.Nd Wacom USB tablets +.Sh SYNOPSIS +.Cd "uwacom* at uhidev?" +.Cd "wsmouse* at uwacom? mux 0" +.Sh DESCRIPTION +The +.Nm +driver provides basic support for Wacom USB tablets. +Access to these devices is through the +.Xr wscons 4 +framework. +.Pp +Absolute positioning of the mouse cursor can be done by hovering the pen above +the tablet. +Touching the tablet with the pen tip will emulate mouse button 0, +while the two pen buttons will emulate button 1 and button 2. +.Pp +The +.Nm +driver supports the following Wacom tablets: +.Bl -column "Intuos Draw" "Model Number" -offset 6n +.It Em Name Ta Em Model Number +.It Li Intuos Draw Ta CTL-490 +.It Li Intuos S Ta CTL-4100 +.It Li One S Ta CTL-472 +.It Li One M Ta CTL-672 +.El +.Sh SEE ALSO +.Xr uhidev 4 , +.Xr usb 4 , +.Xr wsmouse 4 +.Sh HISTORY +The +.Nm +driver +first appeared in +.Ox 6.1 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Frank Groeneveld Aq Mt frank@frankgroeneveld.nl . +Support for +.Dq S +models was written by +.An Vladimir Meshcheriakov Aq Mt vladimir.meshcheriakov@epita.fr . +.Sh CAVEATS +Advanced features such as pen tip pressure are not supported. diff --git a/static/openbsd/man4/uxrcom.4 b/static/openbsd/man4/uxrcom.4 new file mode 100644 index 00000000..d049518e --- /dev/null +++ b/static/openbsd/man4/uxrcom.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: uxrcom.4,v 1.1 2019/03/27 22:11:21 kettenis Exp $ +.\" +.\" Copyright (c) 2019 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 27 2019 $ +.Dt UXRCOM 4 +.Os +.Sh NAME +.Nm uxrcom +.Nd Exar XR21V1410 USB serial adapter +.Sh SYNOPSIS +.Cd "uxrcom* at uhub?" +.Cd "ucom* at uxrcom?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Exar XR21V1410 serial adapters. +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr uhub 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 6.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/veb.4 b/static/openbsd/man4/veb.4 new file mode 100644 index 00000000..9c8ccd80 --- /dev/null +++ b/static/openbsd/man4/veb.4 @@ -0,0 +1,180 @@ +.\" $OpenBSD: veb.4,v 1.7 2025/11/25 11:56:49 jsg Exp $ +.\" +.\" Copyright (c) 2021 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 25 2025 $ +.Dt VEB 4 +.Os +.Sh NAME +.Nm veb , +.Nm vport +.Nd Virtual Ethernet Bridge network device +.Sh SYNOPSIS +.Cd "pseudo-device veb" +.Sh DESCRIPTION +The +.Nm veb +pseudo-device supports the creation of a single layer 2 Ethernet +network between multiple ports. +Ethernet interfaces are added to the +.Nm veb +bridge to be used as ports. +Unlike +.Xr bridge 4 , +.Nm veb +takes over the operation of the interfaces that are added as ports. +They are then independent of the host network stack: the individual +Ethernet ports no longer function as independent devices and cannot +be configured with +.Xr inet 4 +or +.Xr inet6 4 +addresses or other layer-3 features themselves. +.Pp +The Ethernet network managed by +.Nm veb +can be connected to the network stack by creating a +.Nm vport +interface and adding it as a port to the bridge. +From the perspective of the host network stack, a +.Nm vport +interface acts as a normal interface connected to an Ethernet +network and can be configured with addresses. +.Pp +.Nm veb +is an IEEE 802.1Q VLAN aware bridge. +A single +.Nm veb +instance can manage multiple independent and isolated Ethernet +networks scoped by VLAN identifiers. +Every packet traversing the bridge is associated with a VLAN, either +by the identifier in 802.1Q VLAN tagged packets or by the VLAN +identifier assigned to port interfaces for untagged packets. +.Pp +Multiple +.Nm vport +interfaces can be attached to a single bridge to connect the network +stack to different VLANs within the bridge, or to connect multiple +routing domains to a single VLAN. +.Pp +.Nm veb +is a learning bridge that maintains a database of Ethernet addresses +and the port that each address in a VLAN is reachable with. +The bridge learns about the reachability of Ethernet addresses by +reading the source address on packets received by ports, and then +entering the address and port into the table dynamically. +Static address entries may also be configured in the table, disabling +dynamic learning for that address. +Ethernet address learning can be disabled on individual ports. +.Pp +When forwarding a packet, the address table is searched for the +destination Ethernet address in the relevant VLAN and the packet +is sent to the associated port in the table entry. +If no entry is found in the table, or the packet is addressed to a +multicast or broadcast address, the packet is flooded to all other +ports on the bridge. +Flooding of packets to unknown unicast addresses can be disabled +on individual ports. +.Pp +.Nm veb +provides multiple mechanisms for filtering packets traversing the +bridge. +.Pp +By default +.Nm veb +filters IEEE 802.1Q VLAN tagged packets on a port until a set of +allowed VLAN identifiers is configured. +Packets without IEEE 802.1Q VLAN tags are assigned the native +VLAN identifier configured on the port for untagged packets. +Alternatively, a port can be configured to drop untagged packets, +or have processing declined by the bridge and passed through to the +network stack. +.Pp +Ports can be configured as members of protected domains to restrict +communication between them. +This can be used to construct Virtual Private LAN Service (VPLS) +topologies with protected domains enforcing a split-horizon forwarding +rule. +.Nm veb +supports RFC 5517 Private VLANs to provide isolation between ports +within a VLAN, and as part of a larger PVLAN network topology. +The PVLAN implementation also provides support for configuring ports +with the pvptags flag to communicate with VLAN aware but PVLAN +unaware equipment using only primary VLAN identifiers for VLAN +tagged packets. +.Pp +.Nm veb +can filter Ethernet packets entering or leaving ports using bridge +rules. +Ports can be configured to only allow relaying of IP +(and ARP/RARP) packets by setting the blocknonip flag. +.Pp +.Xr pf 4 +can be used to filter IP packets as they enter or leave the bridge. +By default this filtering is disabled, but can be enabled by setting +the link1 flag. +This filtering only applies to untagged packets on ports. +The exception to this policy is on +.Nm vport +interfaces, where +.Xr pf 4 +runs as packets enter and leave the network stack regardless of +the value of the link1 flag. +A consequence of this behaviour is that packets traversing +.Nm vport +interfaces appear to travel in the opposite direction to packets +travelling over other ports. +.\" Packets traversing vport interfaces get their direction relative +.\" to the host network stack, while other ports get their direction +.\" from their relationship to the bridge. +.Pp +.Nm veb +supports the addition of span ports to the bridge. +Span ports transmit a copy of every packet received by the bridge, +allowing for passive monitoring of traffic on a separate host. +.\" .Pp +.\" .Nm veb +.\" interfaces support the following +.\" .Xr ioctl 2 +.\" calls: +.Sh SEE ALSO +.Xr ipsec 4 , +.Xr options 4 , +.Xr pf 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh STANDARDS +.Rs +.%T IEEE 802.1Q standard +.%U https://standards.ieee.org/standard/802_1Q-2018.html +.Re +.Pp +.Rs +.%A S. HomChaudhuri +.%A M. Foschiano +.%D February 2010 +.%R RFC 5517 +.%T Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.9 . +VLAN and PVLAN support was added in +.Ox 7.9 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org diff --git a/static/openbsd/man4/vether.4 b/static/openbsd/man4/vether.4 new file mode 100644 index 00000000..f7f68cf6 --- /dev/null +++ b/static/openbsd/man4/vether.4 @@ -0,0 +1,60 @@ +.\" $OpenBSD: vether.4,v 1.5 2017/10/17 22:47:58 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Theo de Raadt +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 17 2017 $ +.Dt VETHER 4 +.Os +.Sh NAME +.Nm vether +.Nd virtual Ethernet interface +.Sh SYNOPSIS +.Cd "pseudo-device vether" +.Sh DESCRIPTION +The +.Nm +interface simulates a normal Ethernet interface by encapsulating +standard network frames with an Ethernet header, specifically +for use as a member in a +.Xr bridge 4 . +.Pp +To use +.Nm +the administrator needs to configure an address onto the interface +so that packets can be routed to it. +An Ethernet header will be prepended and, if the +.Nm +interface is a member of a +.Xr bridge 4 , +the frame will show up there. +.Sh SEE ALSO +.Xr bridge 4 , +.Xr inet 4 , +.Xr inet6 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh HISTORY +The +.Nm +interface first appeared in +.Ox 4.7 . +.Sh AUTHORS +.An Theo de Raadt Aq Mt deraadt@openbsd.org +.Sh BUGS +Like +.Xr tun 4 , +the Ethernet address chosen will be partially random, and may +occasionally collide with another address. diff --git a/static/openbsd/man4/vga.4 b/static/openbsd/man4/vga.4 new file mode 100644 index 00000000..5bb610fc --- /dev/null +++ b/static/openbsd/man4/vga.4 @@ -0,0 +1,134 @@ +.\" $OpenBSD: vga.4,v 1.17 2013/10/19 14:32:45 miod Exp $ +.\" $NetBSD: vga.4,v 1.2.4.1 2000/08/09 07:48:40 drochner Exp $ +.\" +.\" Copyright (c) 1999, 2000 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: October 19 2013 $ +.Dt VGA 4 +.Os +.Sh NAME +.Nm vga +.Nd VGA graphics driver for wscons +.Sh SYNOPSIS +.Cd "vga0 at isa?" +.Cd "vga* at pci?" +.Cd "wsdisplay* at vga?" +.Cd "agp* at vga?" +.Sh DESCRIPTION +This driver handles VGA graphics hardware within the +.Xr wscons 4 +console framework. +It doesn't provide direct device driver entry points but makes its +functions available via the internal +.Xr wsdisplay 4 +interface. +.Pp +The +.Nm +driver supports multiple virtual screens on one physical display. +The screens allocated on one display can be of different +.Dq types , +where a type refers to various display properties. +The type is determined at the time the virtual screen is created and can't +be changed later. +Screens are either created at kernel startup (then the default type is used) +or later with help of the +.Xr wsconscfg 8 +utility. +.Pp +Currently, the following screen types are supported: +.Bl -hang +.It 80x25 +This is the standard VGA text mode with 80 columns and 25 rows. +16 different colors can be displayed at the same time. +Characters are 8 x 16 pixels large, and a font consists of 256 characters. +A built-in font of this size is always present on a VGA card. +It's also possible to use a downloaded font instead. +.It 80x25bf +A modified version of the previous. +It only allows 8 colors to be displayed. +In exchange, it can access two fonts at the same time, so that 512 +different characters can be displayed. +.It 80x40 +A text mode with 80 columns and 40 rows. +Similar to the standard mode, 16 colors and 256 characters are available. +Characters are 8 x 10 pixels large. +For this mode to be useful, a font of that character size must be downloaded. +.It 80x40bf +A modified version of the previous. +It only allows 8 colors to be displayed. +In exchange, it can access two fonts at the same time, so that 512 +different characters can be displayed. +.It 80x50 +A text mode with 80 columns and 50 rows. +Similar to the standard mode, 16 colors and 256 characters are available. +Characters are 8 x 8 pixels large. +For this mode to be useful, a font of that character size must be downloaded. +.It 80x50bf +A modified version of the previous. +It only allows 8 colors to be displayed. +In exchange, it can access two fonts at the same time, so that 512 +different characters can be displayed. +.It 80x24 +A variant of the +.Dq 80x25 +screen type which displays 24 lines only. +It uses the standard 8x16 VGA font. +This mode might be useful for applications which depend on closer +DEC VT100 compatibility. +.It 80x24bf +A modified version of the previous. +It only allows 8 colors to be displayed. +In exchange, it can access two fonts at the same time, so that 512 +different characters can be displayed. +.El +.Pp +The +.Nm +driver can display fonts of the original IBM type and ISO-8859-1 encoded fonts. +.Sh SEE ALSO +.Xr agp 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr pcdisplay 4 , +.Xr pci 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 , +.Xr wsconscfg 8 , +.Xr wsfontload 8 +.Sh BUGS +Only a subset of the possible text modes is supported. +.Pp +VGA cards are supposed to emulate an MDA if a monochrome display is connected. +In this case, the device will naturally not support colors at all, but +offer the capability to display underlined characters instead. +The +.Dq 80x25bf , +.Dq 80x40bf , +.Dq 80x50bf , +and +.Dq 80x24bf +screen types will not be available. +This mode of operation is not tested. diff --git a/static/openbsd/man4/vgafb.4 b/static/openbsd/man4/vgafb.4 new file mode 100644 index 00000000..a509dc27 --- /dev/null +++ b/static/openbsd/man4/vgafb.4 @@ -0,0 +1,54 @@ +.\" $OpenBSD: vgafb.4,v 1.4 2018/04/23 06:24:33 jmc Exp $ +.\" +.\" Copyright (c) 2002 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: April 23 2018 $ +.Dt VGAFB 4 +.Os +.Sh NAME +.Nm vgafb +.Nd VGA frame buffer +.Sh SYNOPSIS +.Cd # sparc64, macppc +.Cd "vgafb* at pci?" +.Cd "wsdisplay* at vgafb?" +.Sh DESCRIPTION +The +.Nm +is a memory based color frame buffer driver for the +.Xr wscons 4 +console framework. +It does not provide direct device driver entry points +but makes its functions available via the internal +.Xr wsdisplay 4 +interface. +Both unaccelerated access as a dumb framebuffer and +accelerated access methods are provided to +.Xr wscons 4 . +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 diff --git a/static/openbsd/man4/vge.4 b/static/openbsd/man4/vge.4 new file mode 100644 index 00000000..78e98216 --- /dev/null +++ b/static/openbsd/man4/vge.4 @@ -0,0 +1,152 @@ +.\" $OpenBSD: vge.4,v 1.23 2021/09/08 20:29:21 jmc Exp $ +.\" $FreeBSD: vge.4,v 1.6 2004/11/24 19:06:43 brueffer Exp $ +.\" +.\" Copyright (c) 2004 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 8 2021 $ +.Dt VGE 4 +.Os +.Sh NAME +.Nm vge +.Nd VIA Velocity 10/100/1Gb Ethernet device +.Sh SYNOPSIS +.Cd "vge* at pci?" +.Cd "ciphy* at mii?" +.Cd "ipgphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for various NICs and embedded Ethernet interfaces +based on the VIA Networking Technologies VT6120, VT6122, VT6130 and VT6132 +Gigabit Ethernet controller chips, including the following: +.Pp +.Bl -bullet -compact +.It +ZyXEL GN650-T 64-bit PCI Gigabit Ethernet NIC (ZX1701) +.It +ZyXEL GN670-T 32-bit PCI Gigabit Ethernet NIC (ZX1702) +.El +.Pp +The VT6120/VT6122 is a 33/66MHz 64-bit PCI device which combines a tri-speed +MAC with an integrated 10/100/1000 copper PHY. +(Some older cards use an external PHY.) +The VT6130/VT6132 is the PCI Express version. +The MAC supports IPv4 transmit/receive IP/TCP/UDP checksum offload, +VLAN tag insertion and stripping, a 64-entry CAM filter and a 64-entry +VLAN filter, 64-bit multicast hash filter, 4 separate transmit DMA +queues, flow control and jumbo frames (not on VT6130/VT6132). +The Velocity family has a 16K receive FIFO and 48K transmit FIFO. +.Pp +The +.Nm +driver takes advantage of the IPv4 transmit/receive IP/TCP/UDP checksum +offload, VLAN tag insertion and stripping, and the CAM filter support. +The CAM filter is used for multicast address filtering to provide +64 perfect multicast address filter support. +If it is necessary for the interface to join more than 64 multicast +groups, the driver will switch over to using the hash filter. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width 10baseTXUTP +.It Cm autoselect +Enable autoselection of the media type and options. +The user can manually override the autoselected mode by adding media +options to the appropriate +.Xr hostname.if 5 +file. +.It Cm 10baseT/UTP +Set 10Mbps operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Xr ifconfig 8 +.Ic mediaopt +option can also be used to select either +.Cm full-duplex +or +.Cm half-duplex +modes. +.It Cm 1000baseT +Set 1000baseT operation over twisted pair. +Both +.Cm full-duplex +and +.Cm half-duplex +modes are supported. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It Cm full-duplex +Force full duplex operation. +.It Cm half-duplex +Force half duplex operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ciphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr ipgphy 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 3.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@windriver.com +and ported to +.Ox +by +.An Peter Valchev Aq Mt pvalchev@openbsd.org . diff --git a/static/openbsd/man4/viapm.4 b/static/openbsd/man4/viapm.4 new file mode 100644 index 00000000..0c888691 --- /dev/null +++ b/static/openbsd/man4/viapm.4 @@ -0,0 +1,103 @@ +.\" $OpenBSD: viapm.4,v 1.12 2018/07/05 10:09:11 fcambus Exp $ +.\" +.\" Copyright (c) 2006 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 5 2018 $ +.Dt VIAPM 4 +.Os +.Sh NAME +.Nm viapm +.Nd VIA SMBus controller and VIA VT82C686A/VT8231 hardware monitor +.Sh SYNOPSIS +.Cd "viapm* at pci?" +.Cd "iic* at viapm?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the bus control and power management +component of the VIA VT82C596, VT82C596B, VT82C686A, VT8231, VT8233, +VT8233A, VT8235, VT8237, VT8237A, VT8237S, VT8251, CX700, VX800, +VX855 and VX900 South Bridges. +Only the SMBus host interface is supported and can be used with the +.Xr iic 4 +framework. +.Pp +The +.Nm +driver provides support for the hardware monitor in the VIA VT82C686A +and VT8231 South Bridges. +The hardware monitor is used with the +.Xr sysctl 8 +interface. +.Pp +The device has 10 sensors: +.Bl -column "Sensor" "Units" "Typical" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical Use" +.It Li "TSENS1" Ta "uK" Ta "CPU temperature" +.It Li "TSENS2" Ta "uK" Ta "System temperature" +.It Li "TSENS3" Ta "uK" Ta "Unknown" +.It Li "FAN1" Ta "RPM" Ta "CPU fan" +.It Li "FAN2" Ta "RPM" Ta "System fan" +.It Li "VSENS1" Ta "uV DC" Ta "CPU core voltage (2.0V)" +.It Li "VSENS2" Ta "uV DC" Ta "North Bridge core voltage (2.5V)" +.It Li "Vcore" Ta "uV DC" Ta "Internal core voltage (3.3V)" +.It Li "VSENS3" Ta "uV DC" Ta "+5V" +.It Li "VSENS4" Ta "uV DC" Ta "+12V" +.El +.Pp +Sensor data is updated every 1.5 seconds. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr pci 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Pp +The +.Nm viaenv +driver first appeared in +.Nx 1.5 . +.Ox +support was added in +.Ox 3.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . +.Pp +The +.Nm viaenv +driver was written by +.An Johan Danielsson +and ported to +.Ox 3.4 +by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . +It was merged with +.Nm +in +.Ox 5.0 . +.Sh BUGS +The driver doesn't support commands with a data buffer size of more +than 2 bytes. +.Pp +Interrupt support is unimplemented, as is support for setting values. diff --git a/static/openbsd/man4/viasio.4 b/static/openbsd/man4/viasio.4 new file mode 100644 index 00000000..52a5fdb1 --- /dev/null +++ b/static/openbsd/man4/viasio.4 @@ -0,0 +1,77 @@ +.\" $OpenBSD: viasio.4,v 1.6 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2005 Alexander Yurchenko +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt VIASIO 4 +.Os +.Sh NAME +.Nm viasio +.Nd VIA VT1211 LPC Super I/O +.Sh SYNOPSIS +.Cd "viasio* at isa? port 0x2e flags 0x0000" +.Cd "viasio* at isa? port 0x4e flags 0x0000" +.Sh DESCRIPTION +The +.Nm +driver provides support for the VIA VT1211 LPC Super I/O IC. +The hardware monitoring and watchdog timer functions are currently +supported. +.Pp +The hardware monitor provides hardware monitoring capabilities +to be used with the +.Xr sysctl 8 +interface. +The following monitoring sensors are available: +.Bl -column "Sensor" "UnitsXXXXX" "Typical" -offset indent +.It Sy "Sensor" Ta Sy "Units" Ta Sy "Typical use" +.It Li "TEMP1" Ta "uK" Ta "Pentium II type thermal diode" +.It Li "UCH1" Ta "uK or uV DC" Ta "CPU temperature" +.It Li "UCH2" Ta "uK or uV DC" Ta "System temperature" +.It Li "UCH3" Ta "uK or uV DC" Ta "CPU core voltage" +.It Li "UCH4" Ta "uK or uV DC" Ta "+5V" +.It Li "UCH5" Ta "uK or uV DC" Ta "+12V" +.It Li "+3.3V" Ta "uV" Ta "Internal +3.3V" +.It Li "FAN1" Ta "RPM" Ta "Fan tachometer" +.It Li "FAN2" Ta "RPM" Ta "Fan tachometer" +.El +.Pp +If the hardware monitor is not enabled by firmware, the driver can try +to enable it if value 0x0001 is present in the +.Ar flags . +Note that enabling the hardware monitor can lead to unexpected results. +.Pp +The watchdog timer provides a standard +.Xr watchdog 4 +interface. +If the watchdog timer is not enabled by firmware, the driver can try +to enable it if value 0x0002 is present in the +.Ar flags . +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr watchdog 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.8 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Alexander Yurchenko Aq Mt grange@openbsd.org . diff --git a/static/openbsd/man4/vic.4 b/static/openbsd/man4/vic.4 new file mode 100644 index 00000000..5dd56794 --- /dev/null +++ b/static/openbsd/man4/vic.4 @@ -0,0 +1,106 @@ +.\" $OpenBSD: vic.4,v 1.25 2018/01/04 20:09:56 jmc Exp $ +.\" +.\" Copyright (c) 2006 Reyk Floeter +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 4 2018 $ +.Dt VIC 4 +.Os +.Sh NAME +.Nm vic +.Nd VMware VMXnet Virtual Interface Controller device +.Sh SYNOPSIS +.Cd vic* at pci? +.Sh DESCRIPTION +The +.Nm +driver provides support for the VMXnet virtual NIC available in virtual +machines by VMware. +It appears as a simple Ethernet device but is actually a virtual network +interface to the underlying host operating system. +.Pp +This driver supports the +.Ic vmxnet +driver protocol, as an alternative to the emulated +.Xr pcn 4 +and +.Xr em 4 +interfaces also available in the VMware environment. +The +.Nm vic +driver is optimized for the virtual machine, it can provide advanced +capabilities depending on the underlying host operating system and +the physical network interface controller of the host. +.Pp +The +.Nm +driver supports VMware virtual NICs provided by the following products: +.Pp +.Bl -bullet -compact -offset indent +.It +VMware ESX 2.0 and newer +.It +VMware GSX 2.5 and newer +.It +VMware Server 1.0 and newer +.It +VMware Workstation 4.5 and newer +.It +VMware Fusion 1.0 and newer +.El +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width autoselect +.It autoselect +Enable autoselection of the media type and options. +The driver always uses the fastest available speed and the media +options provided by the underlying host of the virtual machine. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh EXAMPLES +The following entry must be added to the VMware configuration file +to provide the +.Nm +device: +.Bd -literal -offset indent +ethernet0.virtualDev = "vmxnet" +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr em 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr pcn 4 , +.Xr vmx 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Reyk Floeter Aq Mt reyk@openbsd.org +and +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/video.4 b/static/openbsd/man4/video.4 new file mode 100644 index 00000000..bfed8a80 --- /dev/null +++ b/static/openbsd/man4/video.4 @@ -0,0 +1,510 @@ +.\" $OpenBSD: video.4,v 1.21 2025/01/15 20:34:50 kirill Exp $ +.\" +.\" Copyright (c) 2008 Marcus Glocker +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 15 2025 $ +.Dt VIDEO 4 +.Os +.Sh NAME +.Nm video +.Nd device-independent video driver layer +.Sh SYNOPSIS +.Cd "video* at uvideo?" +.Pp +.In sys/types.h +.In sys/ioctl.h +.In sys/videoio.h +.Sh DESCRIPTION +The +.Nm +driver provides support for various video devices. +It provides a uniform programming interface layer +above different underlying video hardware drivers. +The +.Nm +driver uses the V4L2 (Video for Linux Two) API which is widely used by video +applications. +Therefore this document mainly describes the V4L2 API parts +which are supported by the +.Nm +driver. +.Pp +For security reasons video recording is blanked by default. +To achieve this, the +.Nm +driver blanks image data received from the underlying video hardware driver. +The superuser can change this behavior using the +.Va kern.video.record +.Xr sysctl 2 +variable: +.Bd -literal -offset indent +kern.video.record=0 # Recording is blanked (default) +kern.video.record=1 # Recording is enabled +.Ed +.Sh IOCTLS +The following +.Xr ioctl 2 +commands are supported: +.Bl -tag -width Ds +.It Dv VIDIOC_QUERYCAP Fa "struct v4l2_capability *" +Query device capabilities. +.Bd -literal +struct v4l2_capability { + u_int8_t driver[16]; + u_int8_t card[32]; + u_int8_t bus_info[32]; + u_int32_t version; + u_int32_t capabilities; + u_int32_t device_caps; + u_int32_t reserved[3]; +}; +.Ed +.It Dv VIDIOC_ENUM_FMT Fa "struct v4l2_fmtdesc *" +Enumerate image formats. +.Bd -literal +struct v4l2_fmtdesc { + u_int32_t index; + u_int32_t type; + u_int32_t flags; + u_int8_t description[32]; + u_int32_t pixelformat; + u_int32_t mbus_code; + u_int32_t reserved[3]; +}; +.Ed +.It Dv VIDIOC_S_FMT Fa "struct v4l2_format *" +Set the data format. +.Bd -literal +struct v4l2_format { + u_int32_t type; + union { + struct v4l2_pix_format pix; + struct v4l2_pix_format_mplane pix_mp; + struct v4l2_window win; + struct v4l2_vbi_format vbi; + struct v4l2_sliced_vbi_format sliced; + struct v4l2_sdr_format sdr; + struct v4l2_meta_format meta; + u_int8_t raw_data[200]; + } fmt; +}; +.Ed +.It Dv VIDIOC_G_FMT Fa "struct v4l2_format *" +Get the data format. +.Pp +Same structure as for +.Dv VIDIOC_S_FMT . +.It Dv VIDIOC_ENUMINPUT Fa "struct v4l2_input *" +Enumerate video inputs. +.Bd -literal +struct v4l2_input { + u_int32_t index; + u_int8_t name[32]; + u_int32_t type; + u_int32_t audioset; + u_int32_t tuner; + v4l2_std_id std; + u_int32_t status; + u_int32_t capabilities; + u_int32_t reserved[3]; +}; +.Ed +.It Dv VIDIOC_G_INPUT Fa "int *" +Get the current video input. +.It Dv VIDIOC_S_INPUT Fa "int *" +Select the current video input. +.It Dv VIDIOC_REQBUFS Fa "struct v4l2_requestbuffers *" +Initiate memory mapping or user pointer I/O. +.Bd -literal +struct v4l2_requestbuffers { + u_int32_t count; + u_int32_t type; + u_int32_t memory; + u_int32_t capabilities; + u_Int32_t flags; + u_int32_t reserved[3]; +}; +.Ed +.It Dv VIDIOC_QUERYBUF Fa "struct v4l2_buffer *" +Query the status of a buffer. +.Bd -literal +struct v4l2_buffer { + u_int32_t index; + u_int32_t type; + u_int32_t bytesused; + u_int32_t flags; + u_int32_t field; + struct timeval timestamp; + struct v4l2_timecode timecode; + u_int32_t sequence; + u_int32_t memory; + union { + u_int32_t offset; + unsigned long userptr; + struct v4l2_plane *planes; + int32_t fd; + } m; + u_int32_t length; + u_int32_t reserved2; + union { + int32_t request_fd; + u_int32_t reserved; + } +}; +.Ed +.It Dv VIDIOC_QBUF Fa "struct v4l2_buffer *" +Add a buffer to the queue. +.Pp +Same structure as for +.Dv VIDIOC_QUERYBUF . +.It Dv VIDIOC_DQBUF Fa "struct v4l2_buffer *" +Remove a buffer from the queue. +.Pp +Same structure as for +.Dv VIDIOC_QUERYBUF . +.It Dv VIDIOC_STREAMON Fa "int *" +Start video stream. +.It Dv VIDIOC_STREAMOFF Fa "int *" +Stop video stream. +.It Dv VIDIOC_TRY_FMT Fa "struct v4l2_format *" +Try a data format. +.Pp +Same structure as for +.Dv VIDIOC_S_FMT . +.It Dv VIDIOC_ENUM_FRAMEINTERVALS Fa "struct v4l2_frmivalenum *" +Enumerate frame intervals. +.Bd -literal +struct v4l2_frmivalenum { + u_int32_t index; + u_int32_t pixel_format; + u_int32_t width; + u_int32_t height; + u_int32_t type; + union { + struct v4l2_fract discrete; + struct v4l2_frmival_stepwise stepwise; + }; + u_int32_t reserved[2]; +}; + +struct v4l2_frmival_stepwise { + struct v4l2_fract min; + struct v4l2_fract max; + struct v4l2_fract step; +}; +.Ed +.It Dv VIDIOC_S_PARM Fa "struct v4l2_streamparm *" +Set streaming parameters. +.Bd -literal +struct v4l2_streamparm { + u_int32_t type; + union { + struct v4l2_captureparm capture; + struct v4l2_outputparm output; + u_int8_t raw_data[200]; + } parm; +}; + +struct v4l2_captureparm { + u_int32_t capability; + u_int32_t capturemode; + struct v4l2_fract timeperframe; + u_int32_t extendedmode; + u_int32_t readbuffers; + u_int32_t reserved[4]; +}; + +struct v4l2_outputparm { + u_int32_t capability; + u_int32_t outputmode; + struct v4l2_fract timeperframe; + u_int32_t extendedmode; + u_int32_t writebuffers; + u_int32_t reserved[4]; +}; +.Ed +.It Dv VIDIOC_G_PARM Fa "struct v4l2_streamparm *" +Get the streaming parameters. +.Pp +Same structures as for +.Dv VIDIOC_S_PARM . +.It Dv VIDIOC_QUERYCTRL Fa "struct v4l2_queryctrl *" +Enumerate control items. +.Bd -literal +struct v4l2_queryctrl { + u_int32_t id; + u_int32_t type; + u_int8_t name[32]; + int32_t minimum; + int32_t maximum; + int32_t step; + int32_t default_value; + u_int32_t flags; + u_int32_t reserved[2]; +}; +.Ed +.El +.Pp +Command independent enumerations are: +.Bd -literal +enum v4l2_buf_type { + V4L2_BUF_TYPE_VIDEO_CAPTURE = 1, + V4L2_BUF_TYPE_VIDEO_OUTPUT = 2, + V4L2_BUF_TYPE_VIDEO_OVERLAY = 3, + V4L2_BUF_TYPE_VBI_CAPTURE = 4, + V4L2_BUF_TYPE_VBI_OUTPUT = 5, + V4L2_BUF_TYPE_SLICED_VBI_CAPTURE = 6, + V4L2_BUF_TYPE_SLICED_VBI_OUTPUT = 7, + V4L2_BUF_TYPE_VIDEO_OUTPUT_OVERLAY = 8, + V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE = 9, + V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE = 10, + V4L2_BUF_TYPE_SDR_CAPTURE = 11, + V4L2_BUF_TYPE_SDR_OUTPUT = 12, + V4L2_BUF_TYPE_META_CAPTURE = 13, + V4L2_BUF_TYPE_META_OUTPUT = 14, + /* Deprecated, do not use */ + V4L2_BUF_TYPE_PRIVATE = 0x80, +}; + +enum v4l2_memory { + V4L2_MEMORY_MMAP = 1, + V4L2_MEMORY_USERPTR = 2, + V4L2_MEMORY_OVERLAY = 3, + V4L2_MEMORY_DMABUF = 4, +}; + +enum v4l2_ctrl_type { + V4L2_CTRL_TYPE_INTEGER = 1, + V4L2_CTRL_TYPE_BOOLEAN = 2, + V4L2_CTRL_TYPE_MENU = 3, + V4L2_CTRL_TYPE_BUTTON = 4, + V4L2_CTRL_TYPE_INTEGER64 = 5, + V4L2_CTRL_TYPE_CTRL_CLASS = 6, + V4L2_CTRL_TYPE_STRING = 7, + V4L2_CTRL_TYPE_BITMASK = 8, + V4L2_CTRL_TYPE_INTEGER_MENU = 9, + V4L2_CTRL_COMPOUND_TYPES = 0x0100, + V4L2_CTRL_TYPE_U8 = 0x0100, + V4L2_CTRL_TYPE_U16 = 0x0101, + V4L2_CTRL_TYPE_U32 = 0x0102, + V4L2_CTRL_TYPE_AREA = 0x0106, + + /* Compound types are >= 0x0100 */ + V4L2_CTRL_TYPE_HDR10_CLL_INFO = 0x0110, + V4L2_CTRL_TYPE_HDR10_MASTERING_DISPLAY = 0x0111, + + V4L2_CTRL_TYPE_H264_SPS = 0x0200, + V4L2_CTRL_TYPE_H264_PPS = 0x0201, + V4L2_CTRL_TYPE_H264_SCALING_MATRIX = 0x0202, + V4L2_CTRL_TYPE_H264_SLICE_PARAMS = 0x0203, + V4L2_CTRL_TYPE_H264_DECODE_PARAMS = 0x0204, + V4L2_CTRL_TYPE_H264_PRED_WEIGHTS = 0x0205, + + V4L2_CTRL_TYPE_FWHT_PARAMS = 0x0220, + + V4L2_CTRL_TYPE_VP8_FRAME = 0x0240, + + V4L2_CTRL_TYPE_MPEG2_QUANTISATION = 0x0250, + V4L2_CTRL_TYPE_MPEG2_SEQUENCE = 0x0251, + V4L2_CTRL_TYPE_MPEG2_PICTURE = 0x0252, + + V4L2_CTRL_TYPE_VP9_COMPRESSED_HDR = 0x0260, + V4L2_CTRL_TYPE_VP9_FRAME = 0x0261, + + V4L2_CTRL_TYPE_HEVC_SPS = 0x0270, + V4L2_CTRL_TYPE_HEVC_PPS = 0x0271, + V4L2_CTRL_TYPE_HEVC_SLICE_PARAMS = 0x0272, + V4L2_CTRL_TYPE_HEVC_SCALING_MATRIX = 0x0273, + V4L2_CTRL_TYPE_HEVC_DECODE_PARAMS = 0x0274, + + V4L2_CTRL_TYPE_AV1_SEQUENCE = 0x280, + V4L2_CTRL_TYPE_AV1_TILE_GROUP_ENTRY = 0x281, + V4L2_CTRL_TYPE_AV1_FRAME = 0x282, + V4L2_CTRL_TYPE_AV1_FILM_GRAIN = 0x283, +}; + +enum v4l2_frmivaltypes { + V4L2_FRMIVAL_TYPE_DISCRETE = 1, + V4L2_FRMIVAL_TYPE_CONTINUOUS = 2, + V4L2_FRMIVAL_TYPE_STEPWISE = 3, +}; +.Ed +.Pp +Command independent structures are: +.Bd -literal +struct v4l2_pix_format { + u_int32_t width; + u_int32_t height; + u_int32_t pixelformat; + u_int32_t field; + u_int32_t bytesperline; + u_int32_t sizeimage; + u_int32_t colorspace; + u_int32_t priv; + u_int32_t flags; + union { + u_int32_t ycbcr_enc; + u_int32_t hsv_enc; + }; + u_int32_t quantization; + u_int32_t xfer_func; +}; + +struct v4l2_window { + struct v4l2_rect w; + u_int32_t field; + u_int32_t chromakey; + struct v4l2_clip *clips; + u_int32_t clipcount; + void __user *bitmap; + u_int8_t global_alpha; +}; + +struct v4l2_vbi_format { + u_int32_t sampling_rate; + u_int32_t offset; + u_int32_t samples_per_line; + u_int32_t sample_format; + int32_t start[2]; + u_int32_t count[2]; + u_int32_t flags; + u_int32_t reserved[2]; +}; + +struct v4l2_sliced_vbi_format { + u_int16_t service_set; + u_int16_t service_lines[2][24]; + u_int32_t io_size; + u_int32_t reserved[2]; +}; + +struct v4l2_fract { + u_int32_t numerator; + u_int32_t denominator; +}; +.Ed +.Pp +Command independent typedefs are: +.Bd -literal +typedef u_int64_t v4l2_std_id; +.Ed +.Sh READ +Video data can be accessed via the +.Xr read 2 +system call. +The main iteration for userland applications occurs as follow: +.Pp +.Bl -enum -compact -offset indent +.It +Open /dev/video* via the +.Xr open 2 +system call. +.It +Read video data from the device via the +.Xr read 2 +system call. +The video stream will be started automatically with the first +read, which means there is no need to issue a +.Dv VIDIOC_STREAMON +command. +The read will always return a consistent video frame, if no error occurs. +.It +Process video data and start over again with step 2. +.It +When finished, stop the video stream via the +.Xr close 2 +system call. +.El +.Pp +The +.Xr select 2 , +.Xr poll 2 +and +.Xr kqueue 2 +system calls are supported for this access type. +They will signal when a frame is ready for reading without blocking. +.Sh MMAP +Video data can be accessed via the +.Xr mmap 2 +system call. +The main iteration for userland applications occurs as follow: +.Pp +.Bl -enum -compact -offset indent +.It +Open /dev/video* via the +.Xr open 2 +system call. +.It +Request desired number of buffers via the +.Dv VIDIOC_REQBUFS +ioctl command. +The maximum number of available buffers is normally limited by the hardware +driver. +.It +Get the length and offset for the previously requested buffers via the +.Dv VIDIOC_QUERYBUF +ioctl command and map the buffers via the +.Xr mmap 2 +system call. +.It +Initially queue the buffers via the +.Dv VIDIOC_QBUF +ioctl command. +.It +Start the video stream via the +.Dv VIDIOC_STREAMON +ioctl command. +.It +Dequeue one buffer via the +.Dv VIDIOC_DQBUF +ioctl command. +If the queue is empty, +the ioctl will block until a buffer gets queued or an error occurs +(e.g. a timeout). +.It +Process video data. +.It +Requeue the buffer via the +.Dv VIDIOC_QBUF +ioctl command and start over again with step 6. +.It +When finished, stop the video stream via the +.Dv VIDIOC_STREAMOFF +ioctl command. +.El +.Pp +The +.Xr select 2 , +.Xr poll 2 +and +.Xr kqueue 2 +system calls are supported for this access type. +They will signal when at least one frame is ready for dequeuing, +allowing to call the +.Dv VIDIOC_DQBUF +ioctl command without blocking. +.Sh FILES +.Bl -tag -width /dev/video -compact +.It Pa /dev/video +.El +.Sh SEE ALSO +.Xr video 1 , +.Xr ioctl 2 , +.Xr uvideo 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . diff --git a/static/openbsd/man4/vio.4 b/static/openbsd/man4/vio.4 new file mode 100644 index 00000000..e3c71394 --- /dev/null +++ b/static/openbsd/man4/vio.4 @@ -0,0 +1,62 @@ +.\" $OpenBSD: vio.4,v 1.16 2021/05/24 17:29:56 dv Exp $ +.\" +.\" Copyright (c) 2012 Stefan Fritsch +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: May 24 2021 $ +.Dt VIO 4 +.Os +.Sh NAME +.Nm vio +.Nd VirtIO network device +.Sh SYNOPSIS +.Cd "vio* at virtio? flags 0x00" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Xr virtio 4 +network interface provided by bhyve, KVM, QEMU, VirtualBox, and +.Xr vmd 8 . +.Pp +Setting the bit 0x2 in the flags disables the RingEventIndex feature. +This can be tried as a workaround for possible bugs in host implementations of +.Nm +at the cost of slightly reduced performance. +.Pp +Setting the bit 0x100 in the flags forces the interface to be always in +promiscuous mode. +This can be used as a workaround for a bug in QEMU before version 1.7.2 that +prevents packets with a VLAN tag from being sent to the guest. +.Sh SEE ALSO +.Xr intro 4 , +.Xr virtio 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was ported to +.Ox +and improved by +.An Stefan Fritsch Aq Mt sf@sfritsch.de . +It is based on the +.Nx +.Nm vioif +driver by +.An Minoura Makoto . diff --git a/static/openbsd/man4/vioblk.4 b/static/openbsd/man4/vioblk.4 new file mode 100644 index 00000000..d6a76046 --- /dev/null +++ b/static/openbsd/man4/vioblk.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: vioblk.4,v 1.8 2021/06/14 06:27:22 jsg Exp $ +.\" +.\" Copyright (c) 2012 Stefan Fritsch +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 14 2021 $ +.Dt VIOBLK 4 +.Os +.Sh NAME +.Nm vioblk +.Nd VirtIO disk +.Sh SYNOPSIS +.Cd "vioblk* at virtio?" +.Sh DESCRIPTION +The +.Nm +driver provides a virtual disk using a +.Xr virtio 4 +block device provided by bhyve, KVM, QEMU, and VirtualBox. +.Sh SEE ALSO +.Xr intro 4 , +.Xr scsi 4 , +.Xr virtio 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Stefan Fritsch Aq Mt sf@sfritsch.de , +based on the +.Xr vdsk 4 +driver by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/viocon.4 b/static/openbsd/man4/viocon.4 new file mode 100644 index 00000000..55cd9fff --- /dev/null +++ b/static/openbsd/man4/viocon.4 @@ -0,0 +1,59 @@ +.\" $OpenBSD: viocon.4,v 1.3 2017/06/21 08:21:14 akfaew Exp $ +.\" +.\" Copyright (c) 2015 Stefan Fritsch +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 21 2017 $ +.Dt VIOCON 4 +.Os +.Sh NAME +.Nm viocon +.Nd VirtIO console device +.Sh SYNOPSIS +.Cd "viocon* at virtio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Xr virtio 4 +console interface provided by KVM, QEMU, and others. +.Pp +It provides serial ports that are attached as ttys. +Use as a kernel console for +.Ox +is not yet supported. +The multiport feature is not yet supported. +.Sh FILES +.Bl -tag -width Pa -compact +.It Pa /dev/ttyVI00 +.It Pa /dev/ttyVI10 +.It Pa /dev/ttyVI20 +.It Pa /dev/ttyVI30 +.It Pa /dev/ttyVI40 +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr tty 4 , +.Xr virtio 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Stefan Fritsch Aq Mt sf@sfritsch.de . diff --git a/static/openbsd/man4/viogpu.4 b/static/openbsd/man4/viogpu.4 new file mode 100644 index 00000000..c3a50bc0 --- /dev/null +++ b/static/openbsd/man4/viogpu.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: viogpu.4,v 1.2 2023/04/20 20:33:55 jmc Exp $ +.\" +.\" Copyright (c) 2023 joshua stein +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: April 20 2023 $ +.Dt VIOGPU 4 +.Os +.Sh NAME +.Nm viogpu +.Nd VirtIO GPU device +.Sh SYNOPSIS +.Cd "viogpu* at virtio?" +.Cd "wsdisplay* at viogpu?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Xr virtio 4 +GPU interface provided by QEMU and other virtual machines to create a +.Xr wscons 4 +console. +.Sh SEE ALSO +.Xr intro 4 , +.Xr virtio 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 7.4 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An joshua stein Aq Mt jcs@openbsd.org . diff --git a/static/openbsd/man4/viomb.4 b/static/openbsd/man4/viomb.4 new file mode 100644 index 00000000..cc46ee91 --- /dev/null +++ b/static/openbsd/man4/viomb.4 @@ -0,0 +1,73 @@ +.\" $NetBSD: viomb.4,v 1.2 2011/11/26 22:36:14 wiz Exp $ +.\" $OpenBSD: viomb.4,v 1.2 2013/01/16 00:30:48 brad Exp $ +.\" Copyright (c) 2012 Dinar Talypov +.\" Copyright (C) 2011 Minoura Makoto. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 16 2013 $ +.Dt VIOMB 4 +.Os +.Sh NAME +.Nm viomb +.Nd VirtIO memory ballooning driver +.Sh SYNOPSIS +.Cd "viomb* at virtio?" +.Sh DESCRIPTION +The +.Nm +driver supports the virtio-compliant memory ballooning device. +.Pp +Memory ballooning works as follows: +.Pp +.Bl -enum -compact +.It +The host operator requests a guest to return some amount of memory to the host +(via, for example, the QEMU monitor balloon command). +.It +The hypervisor sends the request via the VirtIO memory ballooning device. +.It +The guest +.Nm +driver requests allocation of that amount of physical memory from the +.Ox +memory management system. +.It +The +.Nm +device tells the hypervisor the guest physical memory address of the +allocated memory via the VirtIO memory ballooning device. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr virtio 4 +.Rs +.%A Rusty Russell, IBM Corporation +.%T Virtio PCI Card Specification +.%U http://ozlabs.org/~rusty/virtio-spec/ +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 5.3 . diff --git a/static/openbsd/man4/viornd.4 b/static/openbsd/man4/viornd.4 new file mode 100644 index 00000000..3200aa6d --- /dev/null +++ b/static/openbsd/man4/viornd.4 @@ -0,0 +1,60 @@ +.\" $OpenBSD: viornd.4,v 1.2 2015/02/17 16:29:16 bentley Exp $ +.\" +.\" Copyright (c) 2014 Stefan Fritsch +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: February 17 2015 $ +.Dt VIORND 4 +.Os +.Sh NAME +.Nm viornd +.Nd VirtIO random number device +.Sh SYNOPSIS +.Cd "viornd* at virtio? flags 0x00" +.Sh DESCRIPTION +The +.Nm +driver provides a virtual random number generator using a +.Xr virtio 4 +entropy device provided by QEMU 1.3 and later, and possibly by other +hypervisors. +.Pp +As there is currently no way for +.Nm +to determine how much entropy is needed, the second byte of the flags value +can be used to configure how often it should request more entropy from the +host. +If the second lowest byte of the flags has a value from 1 to 15, +.Nm +will ask for 16 bytes of entropy every 15 * (1 << value) seconds. +For example, flags == 0x100 means an interval of 30 seconds, +0x500 means 8 minutes, 0xa00 means 256 minutes, and 0xf00 means about 6 days. +For flags == 0, a default value will be used (currently 8 minutes). +If the bit 0x1000 is set in the flags, +.Nm +will only request entropy from the host once during system boot. +.Sh SEE ALSO +.Xr intro 4 , +.Xr virtio 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Stefan Fritsch Aq Mt sf@sfritsch.de . diff --git a/static/openbsd/man4/vioscsi.4 b/static/openbsd/man4/vioscsi.4 new file mode 100644 index 00000000..c7ea9547 --- /dev/null +++ b/static/openbsd/man4/vioscsi.4 @@ -0,0 +1,46 @@ +.\" $OpenBSD: vioscsi.4,v 1.3 2021/06/14 06:27:22 jsg Exp $ +.\" +.\" Copyright (c) 2013 Google Inc. +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: June 14 2021 $ +.Dt VIOSCSI 4 +.Os +.Sh NAME +.Nm vioscsi +.Nd VirtIO SCSI adapter +.Sh SYNOPSIS +.Cd "vioscsi* at virtio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for +.Xr virtio 4 +SCSI adapters. +.Sh SEE ALSO +.Xr intro 4 , +.Xr scsi 4 , +.Xr virtio 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Matthew Dempsky Aq Mt matthew@dempsky.org . +.Sh BUGS +Device hotplug is not supported yet. diff --git a/static/openbsd/man4/virtio.4 b/static/openbsd/man4/virtio.4 new file mode 100644 index 00000000..a2095c78 --- /dev/null +++ b/static/openbsd/man4/virtio.4 @@ -0,0 +1,86 @@ +.\" $OpenBSD: virtio.4,v 1.18 2025/01/29 14:03:18 sf Exp $ +.\" +.\" Copyright (c) 2012 Stefan Fritsch +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 29 2025 $ +.Dt VIRTIO 4 +.Os +.Sh NAME +.Nm virtio +.Nd VirtIO support driver +.Sh SYNOPSIS +.Cd "virtio* at fdt?" +.Cd "virtio* at pci? flags 0x00" +.Sh DESCRIPTION +The +.Nm +driver provides support service for paravirtualized devices using the VirtIO +protocol. +Such devices are provided by bhyve, KVM, QEMU, VirtualBox, and +.Xr vmm 4 . +.Pp +Currently there are drivers for the following +.Nm +devices: +.Pp +.Bl -tag -width "vioscsi(4)XXX" -offset indent -compact +.It Xr vio 4 +VirtIO network device +.It Xr vioblk 4 +VirtIO disk +.It Xr viocon 4 +VirtIO console device +.It Xr viogpu 4 +VirtIO GPU device +.It Xr viomb 4 +VirtIO memory ballooning driver +.It Xr viornd 4 +VirtIO random number device +.It Xr vioscsi 4 +VirtIO SCSI adapter +.It Xr vmmci 4 +.Xr vmm 4 +control interface +.El +.Pp +The +.Nm +driver conforms to the virtio 0.9.5 specification. +The virtio 1.0 standard is only supported for PCI devices. +.Pp +By default 1.x is preferred over 0.9. +This can be changed by setting the bit 0x8 in the flags. +.Sh SEE ALSO +.Xr intro 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was ported to +.Ox +and improved by +.An Stefan Fritsch Aq Mt sf@sfritsch.de . +It is based on the +.Nx +driver by +.An Minoura Makoto . +.Sh BUGS +.Nm +big-endian architectures are not yet supported. diff --git a/static/openbsd/man4/vlan.4 b/static/openbsd/man4/vlan.4 new file mode 100644 index 00000000..da947ac4 --- /dev/null +++ b/static/openbsd/man4/vlan.4 @@ -0,0 +1,213 @@ +.\" $OpenBSD: vlan.4,v 1.54 2025/11/24 03:02:38 dlg Exp $ +.\" +.\" Copyright (c) 2000 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of Zembu Labs, Inc. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 24 2025 $ +.Dt VLAN 4 +.Os +.Sh NAME +.Nm vlan , +.Nm svlan +.Nd IEEE 802.1Q and 802.1ad pseudo-device +.Sh SYNOPSIS +.Cd "pseudo-device vlan" +.Sh DESCRIPTION +The +.Nm vlan +driver provides network interfaces supporting Virtual Local Area +Networks (VLANs) on Ethernet networks. +.Nm vlan +interfaces implement virtual networks using the IEEE 802.1Q protocol. +.Nm svlan +interfaces implement virtual networks using the IEEE 802.1ad protocol. +.Pp +.Nm svlan +interfaces allow construction of IEEE 802.1ad-compliant provider bridges. +.Nm vlan +and +.Nm svlan +interfaces can be configured to provide QinQ or stacked VLANs. +.Pp +The interfaces can be created at runtime using the +.Ic ifconfig vlan Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The interface itself can be configured with +.Xr ifconfig 8 ; +see its manual page for more information. +.Pp +.Nm vlan +and +.Nm svlan +interfaces must be configured with a parent Ethernet interface to +operate, and a virtual network identifier. +Packets transmitted through a +.Nm vlan +or +.Nm svlan +interface will be encapsulated in their respective protocols and +transmitted on the specified physical interface. +802.1Q and 802.1ad packets received on the parent interface will be +matched to the +.Nm vlan +and +.Nm svlan +interfaces by their respective protocol and virtual network +identifiers, and decapsulated for reception on the associated virtual +interfaces. +.Pp +The 802.1Q and 802.1ad protocols include a priority field. +By default, the 802.1p priority in a transmitted packet is based on the +priority of packets sent over the interface, which may +be altered via +.Xr pf.conf 5 ; +see the +.Cm prio +option for more information. +Alternatively, +.Cm txprio +can set a specific priority for transmitted packets. +.Pp +.Nm vlan +and +.Nm svlan +interfaces support the following +.Xr ioctl 2 Ns s : +.Bl -tag -width indent -offset 3n +.It Dv SIOCSIFPARENT Fa "struct if_parent *" +Set the parent interface. +The parent may only be configured while the virtual interface is +administratively down. +.It Dv SIOCGIFPARENT Fa "struct if_parent *" +Get the currently configured parent interface. +.It Dv SIOCDIFPARENT Fa "struct ifreq *" +Delete the parent interface configuration. +The parent may only be removed while the virtual interface is +administratively down. +.It Dv SIOCSVNETID Fa "struct ifreq *" +Set the virtual network identifier. +Valid identifiers are in the range 1 to 4094. +.It Dv SIOCGVNETID Fa "struct ifreq *" +Get the currently configured virtual network identifier. +.It Dv SIOCDVNETID Fa "struct ifreq *" +Clear the current virtual network identifier. +Virtual interfaces without a configured virtual network identifier +will use 0 in their protocols tag field. +.It Dv SIOCSIFLLADDR Fa "struct ifreq *" +Configure a custom MAC address on the virtual interface. +When the virtual interface is using a custom MAC address, the parent +interface will be configured to promiscuously receive packets. +When operating without a custom MAC address, the virtual interface +will inherit the parent interfaces MAC address. +Configuring 00:00:00:00:00:00 as the MAC address will clear the +custom MAC address configuration and resume operation with the +parents MAC address. +.El +.Pp +.Nm vlan +and +.Nm svlan +interfaces use the following capability on parent interfaces: +.Bl -tag -width "IFCAP_VLAN_HWTAGGING" -offset 3n +.It IFCAP_VLAN_MTU +The parent interface can handle full sized frames, plus the size +of the vlan tag. +.El +.Pp +.Nm vlan +interfaces use the following capability on parent interfaces: +.Bl -tag -width "IFCAP_VLAN_HWTAGGING" -offset 3n +.It IFCAP_VLAN_HWTAGGING +The parent interface will offload the encapsulation and decapsulation +of 802.1Q frames. +.El +.Sh EXAMPLES +Create an 802.1Q virtual interface on top of the physical interface +em0, with virtual network identifier 5: +.Bd -literal -offset indent +# ifconfig vlan0 create +# ifconfig vlan0 parent em0 vnetid 5 +# ifconfig vlan0 10.1.1.100/24 +.Ed +.Pp +Create an 802.1Q VLAN interface on network 10, on top of an 802.1ad +provider bridge on network 8, on top of the physical interface bge0: +.Bd -literal -offset indent +# ifconfig svlan0 create +# ifconfig svlan0 parent bge0 vnetid 8 +# ifconfig svlan0 up +# ifconfig vlan0 create +# ifconfig vlan0 parent svlan0 vnetid 10 +# ifconfig vlan0 10.1.1.101/24 +.Ed +.Pp +Configure an 802.1Q VLAN interface with a custom MAC address: +.Bd -literal -offset indent +# ifconfig vlan0 lladdr fe:e1:ba:d0:84:0e +.Ed +.Pp +Remove a custom MAC address from an 802.1Q VLAN interface: +.Bd -literal -offset indent +# ifconfig vlan0 lladdr 00:00:00:00:00:00 +.Ed +.Pp +Force the use of priority 1 for transmitted packets, regardless of +the packet priority: +.Bd -literal -offset indent +# ifconfig vlan0 txprio 1 +.Ed +.Sh SEE ALSO +.Xr inet 4 , +.Xr ip 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr pf.conf 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh STANDARDS +.Rs +.%T IEEE 802.1Q standard +.%U https://standards.ieee.org/standard/802_1Q-2018.html +.Re +.Pp +.Rs +.%Q Provider Bridges, QinQ +.%T IEEE 802.1ad standard +.Re +.Sh AUTHORS +Originally +.An Garrett Wollman Aq Mt wollman@freebsd.org . +.Sh CAVEATS +Some Ethernet chips will either discard or truncate +Ethernet frames that are larger than 1514 bytes. +This causes a problem as 802.1Q and 802.1ad tagged frames can be +up to 1518 bytes. +Most controller chips can be told not to discard large frames +and/or to increase the allowed frame size. diff --git a/static/openbsd/man4/vmmci.4 b/static/openbsd/man4/vmmci.4 new file mode 100644 index 00000000..52d57fbf --- /dev/null +++ b/static/openbsd/man4/vmmci.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: vmmci.4,v 1.2 2017/01/13 16:02:27 jmc Exp $ +.\" +.\" Copyright (c) 2017 Reyk Floeter +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 13 2017 $ +.Dt VMMCI 4 +.Os +.Sh NAME +.Nm vmmci +.Nd VMM control interface +.Sh SYNOPSIS +.Cd "vmmci* at virtio?" +.Sh DESCRIPTION +The +.Nm +driver provides a control interface for virtual machines running inside +.Ox +.Xr vmm 4 +(virtual machine monitor) +hosts. +.Pp +The driver handles shutdown and reboot requests from the +.Xr vmm 4 +host by signalling +.Xr init 8 +with +.Dv SIGUSR2 +and +.Dv SIGINT +respectively. +.Sh SEE ALSO +.Xr pvbus 4 , +.Xr vmm 4 , +.Xr init 8 , +.Xr vmd 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Reyk Floeter Aq Mt reyk@openbsd.org . diff --git a/static/openbsd/man4/vmt.4 b/static/openbsd/man4/vmt.4 new file mode 100644 index 00000000..aa3290fc --- /dev/null +++ b/static/openbsd/man4/vmt.4 @@ -0,0 +1,66 @@ +.\" $OpenBSD: vmt.4,v 1.10 2021/01/15 06:16:21 jmatthew Exp $ +.\" +.\" Copyright (c) 2008 Marco Peereboom +.\" Text was heavily borrowed from the IPMI spec V1.5 +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: January 15 2021 $ +.Dt VMT 4 +.Os +.Sh NAME +.Nm vmt +.Nd VMware Tools driver +.Sh SYNOPSIS +.Cd "vmt0 at pvbus0" +.Sh DESCRIPTION +The +.Nm +driver is a kernel level implementation of VMware Tools. +VMware Tools are intended to provide better support for operating systems +running inside virtual machines. +.Pp +.Nm +handles shutdown and reboot requests from the host by signalling +.Xr init 8 +with +.Dv SIGUSR2 +and +.Dv SIGINT +respectively. +.Nm +will log notifications that the guest has been suspended or resumed by the +host. +It also provides access to the host machine's clock as a timedelta sensor. +.Pp +.Nm +reports the guest's hostname and all non-loopback IP addresses to the host. +.Sh SEE ALSO +.Xr pvbus 4 , +.Xr init 8 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Pp +A +.Sy vmwh +helper program is available via +.Xr packages 7 . +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/vmwpvs.4 b/static/openbsd/man4/vmwpvs.4 new file mode 100644 index 00000000..8bf8e13f --- /dev/null +++ b/static/openbsd/man4/vmwpvs.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: vmwpvs.4,v 1.2 2014/08/25 14:46:08 jsg Exp $ +.\" +.\" Copyright (c) 2013 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: August 25 2014 $ +.Dt VMWPVS 4 +.Os +.Sh NAME +.Nm vmwpvs +.Nd VMware Paravirtual SCSI +.Sh SYNOPSIS +.Cd "vmwpvs* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for storage controllers using the +Paravirtual SCSI interface a VMware hypervisor can provide to its guests. +.Sh EXAMPLES +The following entry must be added to the VMware configuration file +to provide the +.Nm +device: +.Bd -literal -offset indent +scsi0.virtualDev = "pvscsi" +.Ed +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An David Gwynne . diff --git a/static/openbsd/man4/vmx.4 b/static/openbsd/man4/vmx.4 new file mode 100644 index 00000000..f8d5fc2c --- /dev/null +++ b/static/openbsd/man4/vmx.4 @@ -0,0 +1,116 @@ +.\" $OpenBSD: vmx.4,v 1.2 2017/10/17 22:47:58 schwarze Exp $ +.\" +.\" Copyright (c) 2006,2013 Reyk Floeter +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 17 2017 $ +.Dt VMX 4 +.Os +.Sh NAME +.Nm vmx +.Nd VMware VMXNET3 Virtual Interface Controller device +.Sh SYNOPSIS +.Cd vmx* at pci? +.Sh DESCRIPTION +The +.Nm +driver provides support for the VMXNET3 virtual NIC available in virtual +machines by VMware. +It appears as a simple Ethernet device but is actually a virtual network +interface to the underlying host operating system. +.Pp +This driver supports the +.Ic VMXNET3 +driver protocol, as an alternative to the emulated +.Xr pcn 4 , +.Xr em 4 +and the earlier VMXNET +.Xr vic 4 +interfaces also available in the VMware environment. +The +.Nm vmx +driver is optimized for the virtual machine, it can provide advanced +capabilities depending on the underlying host operating system and +the physical network interface controller of the host. +In comparison to the earlier VMXNET versions, +as supported by the +.Xr vic 4 +driver, +VMXNET3 supports additional features like multiqueue support, IPv6 +checksum offloading, MSI/MSI-X support and hardware VLAN tagging in +VMware's VLAN Guest Tagging (VGT) mode. +.Pp +The +.Nm +driver supports VMXNET3 VMware virtual NICs provided by the virtual +machine hardware version 7 or newer, as provided by the following +products: +.Pp +.Bl -bullet -compact -offset indent +.It +VMware ESX/ESXi 4.0 and newer +.It +VMware Server 2.0 and newer +.It +VMware Workstation 6.5 and newer +.It +VMware Fusion 2.0 and newer +.El +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width autoselect +.It autoselect +Enable autoselection of the media type and options. +The driver always uses the fastest available speed and the media +options provided by the underlying host of the virtual machine. +.It 10GbaseT mediaopt full-duplex +Set 10Gbps operation. +.It 1000baseT mediaopt full-duplex +Set 1000Mbps operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh EXAMPLES +The following entry must be added to the VMware configuration file +to provide the +.Nm +device: +.Bd -literal -offset indent +ethernet0.virtualDev = "vmxnet3" +.Ed +.Sh SEE ALSO +.Xr arp 4 , +.Xr em 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr pcn 4 , +.Xr vic 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.5 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Tsubai Masanari . diff --git a/static/openbsd/man4/vnd.4 b/static/openbsd/man4/vnd.4 new file mode 100644 index 00000000..43224c85 --- /dev/null +++ b/static/openbsd/man4/vnd.4 @@ -0,0 +1,165 @@ +.\" $OpenBSD: vnd.4,v 1.28 2014/07/02 22:35:42 matthew Exp $ +.\" $NetBSD: vnd.4,v 1.1 1995/12/30 18:10:48 thorpej Exp $ +.\" +.\" Copyright (c) 1995 Jason R. Thorpe. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed for the NetBSD Project +.\" by Jason R. Thorpe. +.\" 4. Neither the name of the author nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 2 2014 $ +.Dt VND 4 +.Os +.Sh NAME +.Nm vnd +.Nd vnode disk driver +.Sh SYNOPSIS +.Cd "pseudo-device vnd" Op Ar count +.Sh DESCRIPTION +The +.Nm +driver provides a disk-like interface to a file. +This is useful for a variety of applications, such as building miniroot or +floppy disk images. +.Pp +This document assumes familiarity with how to generate kernels and +how to properly configure disks and pseudo-devices in a kernel +configuration file. +.Pp +In order to compile in support for +.Nm vnd +devices, a line similar to the following must be present in the kernel +configuration file: +.Bd -unfilled -offset indent +pseudo-device vnd 4 # vnode disk driver +.Ed +.Pp +The +.Ar count +argument is how many +.Nm vnds +memory is allocated for at boot time. +In this example, no more than 4 +.Nm vnds +may be configured. +.Pp +There is a run-time utility that is used for configuring +.Nm vnds . +See +.Xr vnconfig 8 +for more information. +.Sh IOCTL INTERFACE +The following +.Xr ioctl 2 +calls are defined in +.In dev/vndioctl.h : +.Bl -tag -width Ds +.It Dv VNDIOCSET Fa "struct vnd_ioctl *" +Associate the file +.Va vnd_file +with a +.Nm +pseudo device, optionally encrypted using the Blowfish cipher and the key +specified in +.Va vnd_key +of length +.Va vnd_keylen . +The size of the configured device is returned in +.Va vnd_size . +.Bd -literal -offset indent +struct vnd_ioctl { + char *vnd_file; + off_t vnd_size; + u_char *vnd_key; + int vnd_keylen; +}; +.Ed +.It Dv VNDIOCCLR Fa "struct vnd_ioctl *" +Disassociate a +.Nm +device. +.It Dv VNDIOCGET Fa "struct vnd_user *" +Get the associated file name, device, inode number, and unit number of a +.Nm +device. +If +.Va vnu_unit +is \-1, information on the +.Nm +device corresponding to the file descriptor passed to +.Xr ioctl 2 +will be returned. +Otherwise, +.Va vnu_unit +may contain the unit number of another +.Nm +device. +This allows for opening just +.Li vnd0 +and querying all available devices. +.Bd -literal -offset indent +struct vnd_user { + char vnufile[VNDNLEN]; + int vnu_unit; + dev_t vnu_dev; + ino_t vnu_ino; +}; +.Ed +.El +.Pp +Additionally, some +.Xr disklabel 8 +related +.Xr ioctl 2 +calls defined in +.In sys/dkio.h +are available: +.Dv DIOCGDINFO , +.Dv DIOCSDINFO , +and +.Dv DIOCWDINFO . +They are documented in +.Xr sd 4 . +.Sh FILES +.Bl -tag -width /dev/{,r}vnd* -compact +.It Pa /dev/{,r}vnd* +.Nm +device special files +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr sd 4 , +.Xr disklabel 5 , +.Xr config 8 , +.Xr disklabel 8 , +.Xr fdisk 8 , +.Xr fsck 8 , +.Xr MAKEDEV 8 , +.Xr mount 8 , +.Xr newfs 8 , +.Xr vnconfig 8 diff --git a/static/openbsd/man4/vr.4 b/static/openbsd/man4/vr.4 new file mode 100644 index 00000000..ea5dfcdf --- /dev/null +++ b/static/openbsd/man4/vr.4 @@ -0,0 +1,187 @@ +.\" $OpenBSD: vr.4,v 1.39 2022/02/18 10:24:32 jsg Exp $ +.\" +.\" Copyright (c) 1997, 1998 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: vr.4,v 1.3 1999/03/25 00:52:44 wpaul Exp $ +.\" +.Dd $Mdocdate: February 18 2022 $ +.Dt VR 4 +.Os +.Sh NAME +.Nm vr +.Nd VIA Rhine I/II/III 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "vr* at pci?" +.Cd "amphy* at mii?" +.Cd "icsphy* at mii?" +.Cd "sqphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI Ethernet adapters and embedded +controllers based on the VIA Technologies VT3043 Rhine I, +VT86C100A Rhine II, VT6102 Rhine II, and VT6105/VT6105M Rhine III +Fast Ethernet controller chips, including the following: +.Pp +.Bl -bullet -compact +.It +AOpen/Acer ALN-320 +.It +D-Link DFE-520TX, DFE-530TX +.It +Hawking Technologies PN102TX +.It +Soekris Engineering lan1741 +.El +.Pp +The VIA Rhine chips use bus master DMA and have a software interface +designed to resemble that of the DEC 21x4x "tulip" chips. +The major differences are that the receive filter in the Rhine chips is +much simpler and is programmed through registers rather than by +downloading a special setup frame through the transmit DMA engine, +and that on older chips transmit and receive DMA buffers must be +longword aligned. +The Rhine chips are meant to be interfaced with external +physical layer devices via an MII bus. +They support both 10 and 100Mbps speeds in either full or half duplex. +.Pp +The +.Nm +driver for the VT6105M controller supports IPv4 IP/TCP/UDP transmit/receive +checksum offload and VLAN tag insertion and stripping. +The +.Nm +driver additionally supports Wake on LAN (WoL). +See +.Xr arp 8 +and +.Xr ifconfig 8 +for more details. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation. +.It half-duplex +Force half duplex operation. +.El +.Pp +Note that the 100baseTX media type is only available if supported +by the adapter. +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "vr0: couldn't map memory" +A fatal initialization error has occurred. +.It "vr0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "vr0: watchdog timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.It "vr0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.It "vr0: no memory for tx list" +The driver failed to allocate an mbuf for the transmitter ring when +allocating a pad buffer or collapsing an mbuf chain into a cluster. +.El +.Sh SEE ALSO +.Xr amphy 4 , +.Xr arp 4 , +.Xr icsphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr sqphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T The VIA Technologies VT86C100A data sheet +.%U https://www.viatech.com +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 3.0 . +.Ox +support first appeared in +.Ox 2.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ctr.columbia.edu . +.Sh CAVEATS +The +.Nm +driver copies transmit mbuf chains into longword-aligned buffers prior +to transmission in order to pacify the VT3043 and VT86C100A chips. +If buffers are not aligned correctly, the chip will round the +supplied buffer address and begin DMAing from the wrong location. +This buffer copying impairs transmit performance on slower systems but can't +be avoided. +On faster machines (e.g., a Pentium II), the performance +impact is much less noticeable. diff --git a/static/openbsd/man4/vscsi.4 b/static/openbsd/man4/vscsi.4 new file mode 100644 index 00000000..e3b2b54d --- /dev/null +++ b/static/openbsd/man4/vscsi.4 @@ -0,0 +1,126 @@ +.\" $OpenBSD: vscsi.4,v 1.14 2017/09/12 15:06:20 schwarze Exp $ +.\" +.\" Copyright (c) 2008 David Gwynne +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: September 12 2017 $ +.Dt VSCSI 4 +.Os +.Sh NAME +.Nm vscsi +.Nd virtual SCSI controller +.Sh SYNOPSIS +.Cd "vscsi0 at root" +.Pp +.In sys/types.h +.In sys/ioctl.h +.In scsi/scsi_all.h +.In dev/vscsivar.h +.Sh DESCRIPTION +The +.Nm +device takes commands from the kernel SCSI midlayer and makes them available +to userland for handling. +Using this interface it is possible to implement virtual SCSI devices that are +usable by the kernel. +.Pp +The following +.Xr ioctl 2 +commands are provided to allow userland to dequeue SCSI commands and reply to +them: +.Pp +.Bl -tag -width Ds -compact +.It Dv VSCSI_I2T Fa "struct vscsi_ioc_i2t *" +Dequeue a SCSI command. +If no SCSI commands are available to dequeue, +.Xr ioctl 2 +will fail and set +.Va errno +to +.Dv EAGAIN . +.Pp +When one or more SCSI commands are available to dequeue, +.Xr select 2 +will indicate the descriptor as ready to read. +.Bd -literal -offset indent +struct vscsi_ioc_i2t { + int tag; + + u_int target; + u_int lun; + + struct scsi_generic cmd; + size_t cmdlen; + + size_t datalen; + int direction; +#define VSCSI_DIR_NONE 0 +#define VSCSI_DIR_READ 1 +#define VSCSI_DIR_WRITE 2 +}; +.Ed +.Pp +.It Dv VSCSI_DATA_READ Fa "struct vscsi_ioc_data *" +.It Dv VSCSI_DATA_WRITE Fa "struct vscsi_ioc_data *" +Read or write data in response to a SCSI command identified by tag. +.Bd -literal -offset indent +struct vscsi_ioc_data { + int tag; + + void * data; + size_t datalen; +}; +.Ed +.Pp +.It Dv VSCSI_T2I Fa "struct vscsi_ioc_t2i *" +Signal completion of a SCSI command identified by tag. +.Bd -literal -offset indent +struct vscsi_ioc_t2i { + int tag; + + int status; +#define VSCSI_STAT_DONE 0 +#define VSCSI_STAT_SENSE 1 +#define VSCSI_STAT_RESET 2 +#define VSCSI_STAT_ERR 3 + struct scsi_sense_data sense; +}; +.Ed +.Pp +.It Dv VSCSI_REQPROBE Fa "struct vscsi_ioc_devevent *" +.It Dv VSCSI_REQDETACH Fa "struct vscsi_ioc_devevent *" +Request a probe or a detach of the device at the addresses specified by the +target and lun fields. +.Bd -literal -offset indent +struct vscsi_ioc_devevent { + u_int target; + u_int lun; +}; +.Ed +.El +.Sh FILES +.Bl -tag -width /dev/vscsi0 +.It /dev/vscsi0 +.El +.Sh SEE ALSO +.Xr ioctl 2 , +.Xr intro 4 , +.Xr scsi 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.5 . +.Sh AUTHORS +.An David Gwynne Aq Mt dlg@openbsd.org . diff --git a/static/openbsd/man4/vte.4 b/static/openbsd/man4/vte.4 new file mode 100644 index 00000000..5156b156 --- /dev/null +++ b/static/openbsd/man4/vte.4 @@ -0,0 +1,82 @@ +.\" $OpenBSD: vte.4,v 1.4 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2011 Kevin Lo +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt VTE 4 +.Os +.Sh NAME +.Nm vte +.Nd RDC R6040 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "vte* at pci?" +.Cd "rdcphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Ethernet interfaces based on the +RDC R6040 Ethernet chipset which is commonly found on +Vortex86 System On a Chip (SoC). +.Pp +The +.Nm +driver supports interrupt moderation mechanism, a 64-bit multicast +hash filter. +.Pp +The following +.Ar media +types are supported: +.Pp +.Bl -tag -width autoselect -compact +.It Cm autoselect +Enable autoselection of the media type and options. +.It Cm 10baseT +Set 10Mbps operation. +.It Cm 100baseTX +Set 100Mbps (Fast Ethernet) operation. +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by the card, try +.Ic ifconfig media . +For example, +.Ic ifconfig vte0 media . +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr rdcphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 4.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Pyun YongHyeon +for +.Fx +and ported to +.Ox +by +.An Kevin Lo Aq Mt kevlo@openbsd.org . diff --git a/static/openbsd/man4/vxlan.4 b/static/openbsd/man4/vxlan.4 new file mode 100644 index 00000000..a753b505 --- /dev/null +++ b/static/openbsd/man4/vxlan.4 @@ -0,0 +1,245 @@ +.\" $OpenBSD: vxlan.4,v 1.20 2023/11/23 03:36:42 dlg Exp $ +.\" +.\" Copyright (c) 2013 Reyk Floeter +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: November 23 2023 $ +.Dt VXLAN 4 +.Os +.Sh NAME +.Nm vxlan +.Nd Virtual eXtensible Local Area Network tunnel interface +.Sh SYNOPSIS +.Cd "pseudo-device vxlan" +.Sh DESCRIPTION +The +.Nm +pseudo-device provides interfaces for tunnelling or overlaying +Ethernet networks on top of IPv4 and IPv6 networks using the +Virtual eXtensible Local Area Network (VXLAN) protocol. +.Pp +VXLAN datagrams consist of an Ethernet payload encapsulated by an +8-byte VXLAN header, which in turn is encapsulated by UDP and IP +headers. +Different VXLAN tunnels or overlays between the same VXLAN Tunnel +Endpoints (VTEPs) can be distinguished by an optional 24-bit Virtual +Network Identifier (VNI). +.Pp +A +.Nm +interface can be created using the +.Ic ifconfig vxlan Ns Ar N Ic create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +.Pp +For correct operation, encapsulated traffic must not be routed +over the interface itself. +This can be implemented by adding a distinct or a more specific +route to the tunnel destination than the hosts or networks routed +via the tunnel interface. +Alternatively, the tunnel traffic may be configured in a separate +routing table to the encapsulated traffic. +.Pp +The interface can operate in the following tunnel modes: +.Bl -tag -width multicast +.It Ic point-to-point mode +When a unicast IP address is configured as the tunnel destination, +all traffic is sent to a single tunnel endpoint. +.It Ic learning mode +When a multicast IP address is configured as the tunnel destination, +.Nm +operates as a learning bridge. +Broadcast, multicast, and unknown unicast packets are sent to the +specified multicast group. +Packets received by the tunnel source address are used to dynamically +learn the endpoint addresses for the encapsulated Ethernet source +addresses. +.It Ic endpoint mode +When configured without a tunnel destination address, +.Nm +operates as a bridge, but with learning disabled. +Endpoints for Ethernet addresses must be added explicitly before +packets will be encapsulated for those addresses. +All valid VXLAN packets sent to the local address will be accepted. +.El +.Pp +.Nm +supports the following +.Xr ioctl 2 +calls for configuration: +.Bl -tag -width indent -offset 3n +.It Dv SIOCSLIFPHYADDR Fa "struct if_laddrreq *" +Set the IPv4 or IPv6 addresses used for the exchange of encapsulated +traffic. +The interface will operate in point-to-point mode if the destination +address is unicast, +learning mode if the destination address is multicast, +or endpoint mode if the destination address is unspecified. +A non-standard UDP port for VXLAN packets can be specified by the +port in the source address, otherwise use 0 to request the default. +The addresses may only be configured while the interface is down. +.It Dv SIOCGLIFPHYADDR Fa "struct if_laddrreq *" +Get the addresses configured for the exchange of encapsulated packets. +.It Dv SIOCDIFPHYADDR Fa "struct ifreq *" +Clear the addresses used for the exchange of encapsulated packets. +The addresses may only be cleared while the interface is down. +.It Dv SIOCSVNETID Fa "struct ifreq *" +Configure a virtual network identifier for use in the VXLAN header. +The virtual network identifier may only be configured while the +interface is down. +.It Dv SIOCGVNETID Fa "struct ifreq *" +Get the virtual network identifier used in the VXLAN header. +.It Dv SIOCDVNETID Fa "struct ifreq *" +Remove the virtual network identifier. +The virtual network identifier may only be disabled while the +interface is down. +.It Dv SIOCSLIFPHYRTABLE Fa "struct ifreq *" +Set the routing table the encapsulated traffic operates in. +The routing table may only be configured while the interface is down. +.It Dv SIOCGLIFPHYRTABLE Fa "struct ifreq *" +Get the routing table the encapsulated traffic operates in. +.It Dv SIOCSLIFPHYTTL Fa "struct ifreq *" +Set the Time-To-Live field in IPv4 encapsulation headers, or the +Hop Limit field in IPv6 encapsulation headers. +.It Dv SIOCGLIFPHYTTL Fa "struct ifreq *" +Get the value used in the Time-To-Live field in an IPv4 encapsulation +header or the Hop Limit field in an IPv6 encapsulation header. +.It Dv SIOCSLIFPHYDF Fa "struct ifreq *" +Configure whether the encapsulated traffic sent by the interface +can be fragmented or not. +This sets the Don't Fragment (DF) bit on IPv4 packets, +and disables fragmentation of IPv6 packets. +.It Dv SIOCGLIFPHYDF Fa "struct ifreq *" +Get whether the encapsulated traffic sent by the interface can be +fragmented or not. +.It Dv SIOCSRXHPRIO Fa "struct ifreq *" +Set the priority value for received packets. +Values may be from 0 to 7, +.Dv IF_HDRPRIO_PACKET +to specify that the current priority of a packet should be kept, +or +.Dv IF_HDRPRIO_OUTER +to use the value in the Type of Service field in IPv4 +or the Traffic Class field in IPv6 encapsulation headers. +.It Dv SIOCGRXHPRIO Fa "struct ifreq *" +Get the priority value for received packets. +.It Dv SIOCSTXHPRIO Fa "struct ifreq *" +Set the priority value used in the Type of Service field in IPv4 +headers, or the Traffic Class field in IPv6 headers. +Values may be from 0 to 7, or +.Dv IF_HDRPRIO_PACKET +to specify that the current priority of a packet should be used. +.It Dv SIOCGTXHPRIO Fa "struct ifreq *" +Get the priority value used in the Type of Service field in IPv4 +headers, or the Traffic Class field in IPv6 headers. +.It Dv SIOCSIFPARENT Fa "struct if_parent *" +Configure which interface will be joined to the multicast group +specified by the tunnel destination address. +The parent interface may only be configured for interfaces in +learning mode, and while the interface is down. +.It Dv SIOCGIFPARENT Fa "struct if_parent *" +Get the name of the interface used for multicast communication. +.It Dv SIOCDIFPARENT Fa "struct ifreq *" +Remove the configuration of the interface used for multicast +communication. +.El +.Sh EXAMPLES +Create a point-to-point tunnel using Virtual Network Identifier 5: +.Bd -literal -offset indent +# ifconfig vxlan0 tunnel 192.168.1.100 192.168.1.200 vnetid 5 +# ifconfig vxlan0 10.1.1.100/24 +.Ed +.Pp +The following examples creates a learning overlay network: +.Bd -literal -offset indent +# ifconfig vxlan0 tunnel 192.168.1.100 239.1.1.100 +# ifconfig vxlan0 parent ix0 +# ifconfig vxlan0 vnetid 7395 +# ifconfig vxlan0 10.1.2.100/24 +.Ed +.Pp +Prior to the assignment of UDP port 4789 by IANA, some early VXLAN +implementations used port 8472. +A non-standard port can be specified with the tunnel source +address: +.Bd -literal -offset indent +# ifconfig vxlan0 tunnel 192.168.1.100:8472 239.1.1.100 +.Ed +.Sh SECURITY +.Nm +does not provide any integrated security features. +It is designed to be a simple protocol that can be used in trusted +data center environments, to carry VM traffic between virtual machine +hypervisors, and provide virtualized layer 2 networks in Cloud +infrastructures. +.Pp +To protect +.Nm +tunnels, the traffic can be protected with IPsec to add authentication +and encryption for confidentiality. +.Pp +The Packet Filter (PF) can be used to filter tunnel traffic with +endpoint policies in +.Xr pf.conf 5 : +.Bd -literal -offset indent +table { 192.168.1.200, 192.168.1.201 } +block in on em0 +pass out on em0 +pass in on em0 proto udp from to port vxlan +.Ed +.Pp +The Time-to-Live (TTL) value of the tunnel can be set to 1 or a low +value to restrict the traffic to the local network: +.Bd -literal -offset indent +# ifconfig vxlan0 tunnelttl 1 +.Ed +.Sh SEE ALSO +.Xr inet 4 , +.Xr udp 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Sh STANDARDS +.Rs +.%A M. Mahalingam +.%A D. Dutt +.%A K. Duda +.%A P. Agarwal +.%A L. Kreeger +.%A T. Sridhar +.%A M. Bursell +.%A C. Wright +.%D August 2014 +.%R RFC 7348 +.%T Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks +.Re +.Sh HISTORY +The +.Nm +device first appeared in +.Ox 5.5 . +.Sh CAVEATS +The +.Nm +interface requires at least 50 bytes for the IP, UDP and VXLAN +protocol overhead and optionally 4 bytes for the encapsulated VLAN tag. +The default MTU is set to 1500 bytes but can be adjusted if the +transport interfaces carrying the tunnel traffic do not support larger +MTUs, the tunnel traffic is leaving the local network, or if +interoperability with another implementation requires running a +decreased MTU of 1450 bytes. +In any other case, it is commonly recommended to set the MTU of the +transport interfaces to at least 1600 bytes. diff --git a/static/openbsd/man4/watchdog.4 b/static/openbsd/man4/watchdog.4 new file mode 100644 index 00000000..c14e3068 --- /dev/null +++ b/static/openbsd/man4/watchdog.4 @@ -0,0 +1,96 @@ +.\" $OpenBSD: watchdog.4,v 1.11 2009/05/21 16:07:25 mk Exp $ +.\" +.\" Copyright (c) 2004-2006 Michael Knudsen +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.Dd $Mdocdate: May 21 2009 $ +.Dt WATCHDOG 4 +.Os +.Sh NAME +.Nm watchdog +.Nd hardware timers/counters for quick crash recovery +.Sh DESCRIPTION +Hardware watchdog timers are devices that reboot the machine when it +hangs. +The kernel continually resets the watchdog clock on a regular basis. +Thus, if the kernel halts, the clock will time out and reset the machine. +Watchdog timers may be configured to be reset from userland +to cause a reboot if process scheduling fails; +see +.Xr watchdogd 8 +for further information. +.Pp +A number of hardware watchdogs are supported, and all are configured +using +.Xr sysctl 8 +under the +.Va kern.watchdog +name: +.Bl -tag -width kern.watchdog.period -offset indent +.It Va kern.watchdog.auto +Automatically reset +.Pq Sq tickle +the watchdog timer but disable it at system shutdown time. +.It Va kern.watchdog.period +The timeout in seconds. +Setting it to zero disables the watchdog timer. +.El +.Pp +In situations where the machine provides vital services which are not +handled completely in kernel space, e.g. mail exchange, it may be +desirable to reboot the machine if process scheduling fails. +This is done by setting +.Va kern.watchdog.auto +to zero and running a process which repeatedly sets +.Va kern.watchdog.period +to the desired timeout value. +Then, if process scheduling fails, the process resetting the timer will +not be run, leading to the machine being rebooted. +Note that the kernel will not automatically disable an enabled watchdog at +system shutdown time when +.Va kern.watchdog.auto +is set to zero. +.Pp +Watchdog timers should be used in high-availability environments where +getting machines up and running quickly after a crash is more important +than determining the cause of the crash. +A watchdog timer enables a crashed machine to autonomously attempt to +recover quickly after a system failure. +.Pp +Note that this also means that it is unwise to combine watchdog timers +with +.Xr ddb 4 +since the latter may prevent the former from resetting the +watchdog timeout before it expires. +This means that the machine will be rebooted before any debugging +can be done. +In other words: For mission critical machines, disable +.Xr ddb 4 +by adding +.Dq ddb.panic=0 +to +.Xr sysctl.conf 5 +since this will give the chance to perform a crash dump and reboot. +Simply setting the watchdog will lose the debug trace of what went +wrong. +.Sh SEE ALSO +.Xr ddb 4 , +.Xr sysctl.conf 5 , +.Xr config 8 , +.Xr sysctl 8 , +.Xr watchdogd 8 +.Sh BUGS +For systems with multiple watchdog timers available, only a single +one can be used at a time. +There is currently no way of selecting which device is used; the first +discovered by the kernel is selected. diff --git a/static/openbsd/man4/wb.4 b/static/openbsd/man4/wb.4 new file mode 100644 index 00000000..2329854e --- /dev/null +++ b/static/openbsd/man4/wb.4 @@ -0,0 +1,157 @@ +.\" $OpenBSD: wb.4,v 1.21 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 1997, 1998 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: wb.4,v 1.2 1998/12/05 09:31:25 rnordier Exp $ +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt WB 4 +.Os +.Sh NAME +.Nm wb +.Nd Winbond W89C840F 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "wb* at pci?" +.Cd "amphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver provides support for PCI Ethernet adapters and embedded +controllers based on the Winbond W89C840F Fast Ethernet controller chip. +This includes the TRENDnet TE100-PCIE and various other cheap boards. +The 840F should not be confused with the 940F, which is +an NE2000 clone and only supports 10Mbps speeds. +.Pp +The Winbond controller uses bus master DMA and is designed to be +a DEC "tulip" work-alike. +It differs from the standard DEC design +in several ways: the control and status registers are spaced 4 +bytes apart instead of 8, and the receive filter is programmed through +registers rather than by downloading a special setup frame via +the transmit DMA engine. +Using an external PHY, the Winbond chip +supports both 10 and 100Mbps speeds in either full or half duplex. +.Pp +The +.Nm +driver supports the following media types: +.Bl -tag -width full-duplex +.It autoselect +Enable autoselection of the media type and options. +This is only supported if the PHY chip attached to the Winbond controller +supports NWAY autonegotiation. +The user can manually override +the autoselected mode by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It 10baseT +Set 10Mbps operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.It 100baseTX +Set 100Mbps (Fast Ethernet) operation. +The +.Ar mediaopt +option can also be used to select either +.Ar full-duplex +or +.Ar half-duplex +modes. +.El +.Pp +The +.Nm +driver supports the following media options: +.Bl -tag -width full-duplex +.It full-duplex +Force full duplex operation. +.It half-duplex +Force half duplex operation. +.El +.Pp +Note that the 100baseTX media type is only available if supported +by the adapter. +For more information on configuring this device, see +.Xr ifconfig 8 . +.Sh DIAGNOSTICS +.Bl -diag +.It "wb0: couldn't map memory" +A fatal initialization error has occurred. +.It "wb0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "wb0: watchdog timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.It "wb0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.It "wb0: no memory for tx list" +The driver failed to allocate an mbuf for the transmitter ring when +allocating a pad buffer or collapsing an mbuf chain into a cluster. +.El +.Sh SEE ALSO +.Xr amphy 4 , +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 3.0 . +.Ox +support first appeared in +.Ox 2.5 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ctr.columbia.edu . +.Sh BUGS +The Winbond chip seems to behave strangely in some cases when the +link partner switches modes. +If, for example, both sides are set to 10Mbps half-duplex, and the other end +is changed to 100Mbps full-duplex, the Winbond's receiver suddenly starts +writing trash all over the RX descriptors. +The +.Nm +driver handles this by forcing a reset of both the controller +chip and attached PHY. +This is drastic, but it appears to be the only way to recover properly from +this condition. diff --git a/static/openbsd/man4/wbenv.4 b/static/openbsd/man4/wbenv.4 new file mode 100644 index 00000000..a74f151d --- /dev/null +++ b/static/openbsd/man4/wbenv.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: wbenv.4,v 1.6 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2006 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt WBENV 4 +.Os +.Sh NAME +.Nm wbenv +.Nd Winbond W83L784R/W83L785R/W83L785TS-L temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "wbenv* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the +.Tn Winbond +W83L784R, W83L785R and W83L785TS-L hardware monitors to be used with +the +.Xr sysctl 8 +interface. +.Pp +The W83L874R and W83L785R possess several voltage, temperature and fan +speed sensors. +The W83L785TS-L only has a single temperature sensor. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 3.9 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/wbng.4 b/static/openbsd/man4/wbng.4 new file mode 100644 index 00000000..3a7c7cd0 --- /dev/null +++ b/static/openbsd/man4/wbng.4 @@ -0,0 +1,49 @@ +.\" $OpenBSD: wbng.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2007 Constantine A. Murenin +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt WBNG 4 +.Os +.Sh NAME +.Nm wbng +.Nd Winbond W83793G temperature, voltage, and fan sensor +.Sh SYNOPSIS +.Cd "wbng* at iic?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Winbond W83793G Hardware Monitor. +The device provides 10 voltage sensors, +6 temperature sensors and 12 fan sensors. +Sensor values are made available through the +.Xr sysctl 8 +interface. +.Sh SEE ALSO +.Xr iic 4 , +.Xr intro 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Constantine A. Murenin Aq Mt cnst@openbsd.org . diff --git a/static/openbsd/man4/wbsd.4 b/static/openbsd/man4/wbsd.4 new file mode 100644 index 00000000..871d1426 --- /dev/null +++ b/static/openbsd/man4/wbsd.4 @@ -0,0 +1,53 @@ +.\" $OpenBSD: wbsd.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2009 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt WBSD 4 +.Os +.Sh NAME +.Nm wbsd +.Nd Winbond W83L518D/W83L519D SD memory card interface +.Sh SYNOPSIS +.Cd "wbsd* at ebus?" +.Cd "sdmmc* at wbsd?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the SD memory card interface of the +Winbond W83L518D/W83L519D integrated media reader. +.Pp +The +.Xr sdmmc 4 +subsystem performs SD/MMC transactions to communicate with +whatever MMC, SD, SDHC, or SDIO devices are inserted into the SD slot. +.Sh SEE ALSO +.Xr intro 4 , +.Xr sdmmc 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.7 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Jared D. McNeill Aq Mt jmcneill@invisible.ca +and ported to +.Ox +by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/wbsio.4 b/static/openbsd/man4/wbsio.4 new file mode 100644 index 00000000..39f88a5c --- /dev/null +++ b/static/openbsd/man4/wbsio.4 @@ -0,0 +1,48 @@ +.\" $OpenBSD: wbsio.4,v 1.3 2013/07/16 16:05:49 schwarze Exp $ +.\" +.\" Copyright (c) 2008 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt WBSIO 4 +.Os +.Sh NAME +.Nm wbsio +.Nd Winbond LPC Super I/O +.Sh SYNOPSIS +.Cd "wbsio* at isa? port 0x2e" +.Cd "wbsio* at isa? port 0x4e" +.Sh DESCRIPTION +The +.Nm +driver provides support for the Winbond LPC Super I/O ICs. +Only the hardware monitoring function is currently supported. +.Pp +Support for the hardware monitor function is provided through the +.Xr lm 4 +driver. +.Sh SEE ALSO +.Xr intro 4 , +.Xr isa 4 , +.Xr lm 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.3 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/wd.4 b/static/openbsd/man4/wd.4 new file mode 100644 index 00000000..a25658bd --- /dev/null +++ b/static/openbsd/man4/wd.4 @@ -0,0 +1,75 @@ +.\" $OpenBSD: wd.4,v 1.13 2007/05/31 19:19:53 jmc Exp $ +.\" $NetBSD: wd.4,v 1.4 1999/04/25 00:00:05 mjl Exp $ +.\" +.\" Copyright (c) 1994 James A. Jegers +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt WD 4 +.Os +.Sh NAME +.Nm wd +.Nd WD100x compatible hard disk driver +.Sh SYNOPSIS +.Cd "wd* at wdc? flags 0x0000" +.Cd "wd* at pciide? flags 0x0000" +.Sh DESCRIPTION +The +.Nm +driver supports hard disks which emulate the Western Digital WD100x. +This includes standard MFM, RLL, ESDI, IDE, and EIDE drives, as well as +Serial ATA drives, and PCMCIA/CF storage media. +.Pp +The +.Cm flags +are used only with controllers that support DMA operations and +mode settings (like some +.Xr pciide 4 +controllers). +The lowest order (rightmost) nibble of the +.Cm flags +define the PIO mode to use. +The next four bits indicate the DMA mode and the third nibble the UltraDMA +mode. +.Pp +For each set of four bits, the 3 lower bits define the mode to use +and the last bit must be set to 1 for this setting to be used. +For DMA and UltraDMA, 0xf (1111) means +.Dq disable . +For example, a +.Cm flags +value of 0x0fac (1111 1010 1100) +means +.Do +use PIO mode 4, DMA mode 2, disable UltraDMA +.Dc . +The special setting 0x0000 means +.Dq use whatever the drive claims to support . +.Sh SEE ALSO +.Xr intro 4 , +.Xr pciide 4 , +.Xr scsi 4 , +.Xr wdc 4 , +.Xr disklabel 5 , +.Xr atactl 8 , +.Xr disklabel 8 , +.Xr fdisk 8 diff --git a/static/openbsd/man4/wdc.4 b/static/openbsd/man4/wdc.4 new file mode 100644 index 00000000..f7ecb125 --- /dev/null +++ b/static/openbsd/man4/wdc.4 @@ -0,0 +1,88 @@ +.\" $OpenBSD: wdc.4,v 1.16 2007/05/31 19:19:53 jmc Exp $ +.\" $NetBSD: wdc.4,v 1.4 1999/05/19 14:44:02 bouyer Exp $ +.\" +.\" Copyright (c) 1998 Manuel Bouyer. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by the University of +.\" California, Berkeley and its contributors. +.\" 4. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt WDC 4 +.Os +.Sh NAME +.Nm wdc +.Nd WD100x compatible hard disk controller driver +.Sh SYNOPSIS +.Cd "# alpha/i386" +.Cd "wdc0 at isa? port 0x1f0 irq 14 flags 0x00" +.Cd "wdc1 at isa? port 0x170 irq 15 flags 0x00" +.Cd "wdc* at isapnp?" +.Pp +.Cd "# macppc" +.Cd "wdc* at macobio?" +.Cd "wdc* at kauaiata?" +.Pp +.Cd "# landisk" +.Cd wdc0 at obio? port 0x14000000 irq 10 +.Pp +.Cd "# all architectures" +.Cd "wdc* at pcmcia?" +.Pp +.Cd "atapiscsi* at wdc?* flags 0x0000" +.Cd "wd* at wdc? flags 0x0000" +.Sh DESCRIPTION +The +.Nm +driver provides the basic functions for the +.Xr wd 4 +and +.Xr atapiscsi 4 +drivers. +It supports IDE and EIDE controllers, as well as MFM, RLL, and ESDI on +the ISA bus. +PCI IDE controllers in legacy mode are also supported, but the +.Xr pciide 4 +driver may provide more functionality. +.Pp +For the +.Xr isa 4 +front-end, setting +.Cm flags +to 0x01 enables 32-bit I/O negotiation. +This is known to cause problems with some motherboards. +.Sh SEE ALSO +.Xr atapiscsi 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr isapnp 4 , +.Xr macobio 4 , +.Xr obio 4 , +.Xr pciide 4 , +.Xr pcmcia 4 , +.Xr scsi 4 , +.Xr wd 4 diff --git a/static/openbsd/man4/we.4 b/static/openbsd/man4/we.4 new file mode 100644 index 00000000..16f7d6eb --- /dev/null +++ b/static/openbsd/man4/we.4 @@ -0,0 +1,117 @@ +.\" $OpenBSD: we.4,v 1.16 2015/09/10 15:16:43 schwarze Exp $ +.\" $NetBSD: we.4,v 1.4 1998/08/09 00:39:02 thorpej Exp $ +.\" +.\" Copyright (c) 1997 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, +.\" NASA Ames Research Center. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: September 10 2015 $ +.Dt WE 4 +.Os +.Sh NAME +.Nm we +.Nd Western Digital/SMC WD80x3, SMC Elite Ultra, and SMC EtherEZ Ethernet device +.Sh SYNOPSIS +.Cd "we0 at isa? port 0x280 iomem 0xd0000 irq 9" +.Cd "we1 at isa? port 0x300 iomem 0xcc000 irq 10" +.Cd "we* at isapnp?" +.Sh DESCRIPTION +The +.Nm +device driver supports Western Digital/SMC WD80x3, SMC Elite Ultra, and +SMC EtherEZ Ethernet cards. +.Sh MEDIA SELECTION +The ability to select media from software is dependent on the particular +model of WD/SMC card. +The following models support only manual configuration: WD8003S, WD8003E, +and WD8013EBT. +.Pp +Other WD/SMC 80x3 interfaces support two types of media on a single card. +All support the AUI media type. +The other media is either BNC or UTP being a transceiver. +Software cannot differentiate between BNC and UTP cards. +On some models, the AUI port is always active. +.Pp +The SMC Elite Ultra and SMC EtherEZ interfaces support three media on +a single card: AUI, BNC, and UTP. +If the transceiver is active, the BNC media is selected. +Otherwise, the AUI and UTP ports are both active. +Cards of this vintage may also be found which lack one or two of the +connectors. +These cards also know what interrupt they are configured for, and will +correct such problems (for further interrupt issues, see +.Xr isa 4 +and +.Xr pci 4 ) . +.Pp +The SMC EtherEZ does not yet work correctly in +.Xr isapnp 4 +mode. +The SMC Elite Ultra does not work in +.Dq soft configuration +mode. +.Pp +To enable the AUI media, select the +.Em 10base5 +or +.Em aui +media type with +.Xr ifconfig 8 Ns 's +.Sq media +directive. +To select the other media (transceiver), select the +.Em 10base2 +or +.Em bnc +media type. +.Sh DIAGNOSTICS +.Bl -diag +.It "we0: overriding IRQ to " +The IRQ specified in the kernel configuration file is different from that +found in the card's configuration registers. +The value in the kernel configuration file is being overridden by the one +configured into the card. +.It "we0: can't wildcard IRQ on a " +The IRQ was wildcarded in the kernel configuration file, and the card is +a WD8003S, WD8003E, or WD8013EBT, which do not support software IRQ +configuration. +.It "we0: failed to clear shared memory at offset " +The memory test was unable to clear the interface's shared memory +region. +This often indicates that the card is configured at a conflicting +.Em iomem +address. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr isa 4 , +.Xr isapnp 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/wg.4 b/static/openbsd/man4/wg.4 new file mode 100644 index 00000000..e6516221 --- /dev/null +++ b/static/openbsd/man4/wg.4 @@ -0,0 +1,226 @@ +.\" $OpenBSD: wg.4,v 1.10 2021/03/14 10:08:38 jmc Exp $ +.\" Copyright (c) 2020 Matt Dunwoodie +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 14 2021 $ +.Dt WG 4 +.Os +.Sh NAME +.Nm wg +.Nd WireGuard pseudo-device +.Sh SYNOPSIS +.Cd "pseudo-device wg" +.Sh DESCRIPTION +The +.Nm wg +driver provides Virtual Private Network (VPN) interfaces for the secure +exchange of layer 3 traffic with other WireGuard peers using the WireGuard +protocol. +.Pp +A +.Nm wg +interface recognises one or more peers, establishes a secure tunnel with +each on demand, and tracks each peer's UDP endpoint for exchanging encrypted +traffic with. +.Pp +The interfaces can be created at runtime using the +.Ic ifconfig Cm wg Ns Ar N Cm create +command or by setting up a +.Xr hostname.if 5 +configuration file for +.Xr netstart 8 . +The interface itself can be configured with +.Xr ifconfig 8 . +.Pp +.Nm wg +interfaces support the following +.Xr ioctl 2 Ns s : +.Bl -tag -width Ds -offset indent +.It Dv SIOCSWG Fa "struct wg_data_io *" +Set the device configuration. +.It Dv SIOCGWG Fa "struct wg_data_io *" +Get the device configuration. +.El +.Pp +The following glossary provides a brief overview of WireGuard +terminology: +.Bl -tag -width indent -offset 3n +.It Peer +Peers exchange IPv4 or IPv6 traffic over secure tunnels. +Each +.Nm wg +interface may be configured to recognise one or more peers. +.It Key +Each peer uses its private key and corresponding public key to +identify itself to others. +A peer configures a +.Nm wg +interface with its own private key and with the public keys of its peers. +.It Preshared key +In addition to the public keys, each peer pair may be configured with a +unique pre-shared symmetric key. +This is used in their handshake to guard against future compromise of the +peers' encrypted tunnel if a quantum-computational attack on their +Diffie-Hellman exchange becomes feasible. +It is optional, but recommended. +.It Allowed IPs +A single +.Nm wg +interface may maintain concurrent tunnels connecting diverse networks. +The interface therefore implements rudimentary routing and reverse-path +filtering functions for its tunneled traffic. +These functions reference a set of allowed IP ranges configured against +each peer. +.Pp +The interface will route outbound tunneled traffic to the peer configured +with the most specific matching allowed IP address range, or drop it +if no such match exists. +.Pp +The interface will accept tunneled traffic only from the peer +configured with the most specific matching allowed IP address range +for the incoming traffic, or drop it if no such match exists. +That is, tunneled traffic routed to a given peer cannot return through +another peer of the same +.Nm wg +interface. +This ensures that peers cannot spoof another's traffic. +.It Handshake +Two peers handshake to mutually authenticate each other and to +establish a shared series of secret ephemeral encryption keys. +Any peer may initiate a handshake. +Handshakes occur only when there is traffic to send, and recur every +two minutes during transfers. +.It Connectionless +Due to the handshake behavior, there is no connected or disconnected +state. +.El +.Ss Keys +Private keys for WireGuard can be generated from any sufficiently +secure random source. +The Curve25519 keys and the preshared keys are both 32 bytes +long and are commonly encoded in base64 for ease of use. +.Pp +Keys can be generated with +.Xr openssl 1 +as follows: +.Pp +.Dl $ openssl rand -base64 32 +.Pp +Although a valid Curve25519 key must have 5 bits set to +specific values, this is done by the interface and so it +will accept any random 32-byte base64 string. +.Pp +When an interface has a private key set with +.Nm wgkey , +the corresponding +public key is shown in the status output of the interface: +.Bd -literal -offset indent +# ifconfig wg1 | grep wgpubkey + wgpubkey NW5l2q2MArV5ZXpVXSZwBOyqhohOf8ImDgUB+jPtJps= +.Ed +.Sh EXAMPLES +Create two +.Nm wg +interfaces in separate +.Xr rdomain 4 Ns s , +which is of no practical use +but demonstrates two interfaces on the same machine: +.Bd -literal -offset indent +#!/bin/sh + +# create interfaces; set random private keys +ifconfig wg1 create wgport 7111 wgkey `openssl rand -base64 32` rdomain 1 +ifconfig wg2 create wgport 7222 wgkey `openssl rand -base64 32` rdomain 2 + +# retrieve the public keys associated with the private keys +PUB1="`ifconfig wg1 | grep 'wgpubkey' | cut -d ' ' -f 2`" +PUB2="`ifconfig wg2 | grep 'wgpubkey' | cut -d ' ' -f 2`" + +ifconfig wg1 wgpeer $PUB2 wgendpoint 127.0.0.1 7222 wgaip 192.168.5.2/32 +ifconfig wg2 wgpeer $PUB1 wgendpoint 127.0.0.1 7111 wgaip 192.168.5.1/32 +ifconfig wg1 192.168.5.1/24 +ifconfig wg2 192.168.5.2/24 +.Ed +.Pp +After this, ping one interface from the other: +.Pp +.Dl $ route -T1 exec ping 192.168.5.2 +.Pp +The two interfaces are able to communicate through the UDP tunnel +which resides in the default +.Xr rdomain 4 . +.Pp +Show the listening sockets: +.Pp +.Dl $ netstat -ln +.Sh DIAGNOSTICS +The +.Nm +interface supports runtime debugging, which can be enabled with: +.Pp +.D1 Ic ifconfig Cm wg Ns Ar N Cm debug +.Pp +Some common error messages include: +.Bl -diag +.It "Handshake for peer X did not complete after 5 seconds, retrying" +Peer X did not reply to our initiation packet, for example because: +.Bl -bullet +.It +The peer does not have the local interface configured as a peer. +Peers must be able to mutually authenticate each other. +.It +The peer endpoint IP address is incorrectly configured. +.It +There are firewall rules preventing communication between hosts. +.El +.It "Invalid handshake initiation" +The incoming handshake packet could not be processed. +This is likely due to the local interface not containing +the correct public key for the peer. +.It "Invalid initiation MAC" +The incoming handshake initiation packet had an invalid MAC. +This is likely because the initiation sender has the wrong public key +for the handshake receiver. +.It "Packet has unallowed src IP from peer X" +After decryption, an incoming data packet has a source IP address that +is not assigned to the allowed IPs of Peer X. +.El +.Sh SEE ALSO +.Xr inet 4 , +.Xr ip 4 , +.Xr netintro 4 , +.Xr hostname.if 5 , +.Xr pf.conf 5 , +.Xr ifconfig 8 , +.Xr netstart 8 +.Rs +.%T WireGuard whitepaper +.%U https://www.wireguard.com/papers/wireguard.pdf +.Re +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.8 . +.Sh AUTHORS +.An -nosplit +The +.Ox +.Nm +driver was developed by +.An Matt Dunwoodie Aq Mt ncon@noconroy.net +and +.An Jason A. Donenfeld Aq Mt Jason@zx2c4.com , +based on code written by +.An Jason A. Donenfeld . diff --git a/static/openbsd/man4/wi.4 b/static/openbsd/man4/wi.4 new file mode 100644 index 00000000..1808d5fe --- /dev/null +++ b/static/openbsd/man4/wi.4 @@ -0,0 +1,393 @@ +.\" $OpenBSD: wi.4,v 1.31 2025/03/27 15:12:14 jmc Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: wi.4,v 1.3 1999/05/22 16:12:43 wpaul Exp $ +.\" +.Dd $Mdocdate: March 27 2025 $ +.Dt WI 4 +.Os +.Sh NAME +.Nm wi +.Nd WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b wireless network device +.Sh SYNOPSIS +.Cd "# all architectures" +.Cd "wi* at pci?" +.Cd "wi* at pcmcia? function ?" +.Cd "wi* at uhub? port ?" +.Pp +.Cd "# macppc extra attachment" +.Cd "wi* at macobio?" +.Sh DESCRIPTION +The +.Nm +driver provides support for wireless network adapters based around +the Lucent Hermes, Intersil PRISM-2, Intersil PRISM-2.5, Intersil PRISM-3, +and Symbol Spectrum24 chipsets. +All five chipsets provide a similar interface to the driver. +.Pp +The +.Nm +driver encapsulates all IP and ARP traffic as 802.11 frames, though +it can receive either 802.11 or 802.3 frames. +Transmit speed is selectable between 1Mbps fixed, 2Mbps fixed, 2Mbps +with auto fallback, 5.5Mbps, 8Mbps, or 11Mbps, depending on hardware. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It IBSS mode +Also known as +.Em IEEE ad-hoc +mode or +.Em peer-to-peer +mode. +This is the standardized method of operating without an access point. +Stations associate with a service set. +However, actual connections between stations are peer-to-peer +as in ad-hoc mode. +Cards with very old firmware revisions do not support this mode. +.It IBSS master +Also know as +.Em Host IBSS +mode. +In this mode the station takes on part of the role of an access point, +though traffic does not pass through it to reach the other stations. +When a group of stations are operating in IBSS mode, one of them must be +the master, specifying the network name of the service set. +.It Host AP +In this mode the driver acts as an access point (base station) +for other cards. +Only cards based on the Intersil chipsets support this mode. +Furthermore, this mode is not supported on USB devices. +.It ad-hoc mode +More accurately known as +.Em ad-hoc demo mode . +This mode does not require an access point; the adapter communicates with +other ad-hoc stations within range on a peer-to-peer basis. +This mode is not specified by the IEEE 802.11 standard and there +may be problems interoperating with adapters manufactured by different vendors. +.El +.Pp +The +.Nm +driver can be configured to use both software and hardware +Wired Equivalent Privacy (WEP). +It is strongly recommended that WEP +not be used as the sole mechanism +to secure wireless communication, +due to serious weaknesses in it. +.Pp +The Lucent WaveLAN/IEEE Silver and Gold cards as well as the Intersil +and Symbol cards have support for WEP encryption. +The WaveLAN Gold as well as newer Intersil and Symbol cards support +104-bit keys, the others only accept 40-bit keys. +The Lucent WaveLAN/IEEE Bronze cards do not support WEP at all. +See also +.Sx CAVEATS +below. +.Pp +In BSS mode, +the driver supports powersave mode, +which can be enabled via +.Xr ifconfig 8 . +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh HARDWARE +Cards supported by the +.Nm +driver come in a variety of packages, though the most common +are of the PCMCIA type. +In many cases, the PCI version of a wireless card is simply +a PCMCIA card bundled with a PCI adapter. +The PCI adapters come in two flavors: true PCMCIA bridges and +dumb PCMCIA bridges. +A true PCMCIA bridge (such as those sold by Lucent) will attach +as a real PCMCIA controller. +The wireless card will then attach to the PCMCIA bus. +Wireless cards in PCMCIA slots may be inserted and ejected on the fly. +A dumb bridge, on the other hand, does not show up as a true PCMCIA bus. +The wireless card will simply appear to the host as a normal PCI +device and will not require any PCMCIA support. +Cards in this type of adapter should only be removed when the +machine is powered down. +.Pp +The following cards are among those supported by the +.Nm +driver: +.Bl -column "Linksys Instant Wireless WPC11 2.5" "Prism-2.5" "PCMCIA" +.It Sy Card Ta Sy Chip Ta Sy Bus +.It 3Com AirConnect 3CRWE737A Ta Spectrum24 Ta PCMCIA +.It 3Com AirConnect 3CRWE777A Ta Prism-2 Ta PCI +.It Acer Warplink USB-400 Ta Prism-3 Ta USB +.It Actiontec HWC01170 Ta Prism-2.5 Ta PCMCIA +.It Actiontec HWU01170 Ta Prism-3 Ta USB +.It Adaptec AWN-8030 Ta Prism-2.5 Ta PCMCIA +.It Addtron AWA-100 Ta Prism-2 Ta PCI +.It Addtron AWP-100 Ta Prism-2 Ta PCMCIA +.It Agere ORiNOCO Ta Hermes Ta PCMCIA +.It AirVast WM168b Ta Prism-3 Ta USB +.It AmbiCom WL1100C-CF Ta Prism-3 Ta CF +.It Ambit WLAN Ta Prism-3 Ta USB +.It Apacer Wireless Steno MB112 Ta Prism-3 Ta USB +.It Apple Airport Ta Hermes Ta macobio +.It ARtem Onair Ta Hermes Ta PCMCIA +.It ASUS SpaceLink WL-100 Ta Prism-2.5 Ta PCMCIA +.It ASUS SpaceLink WL-110 Ta Prism-2.5 Ta CF +.It ASUS WL-140 Ta Prism-3 Ta USB +.It Belkin F5D6020 (version 1 only) Ta Prism-2 Ta PCMCIA +.It Belkin F5D6001 (version 1 only) Ta Prism-2 Ta PCI +.It Belkin F5D6060 (version 1 only) Ta Prism-2.5 Ta CF +.It Buffalo AirStation Ta Prism-2 Ta PCMCIA +.It Buffalo AirStation Ta Prism-2 Ta CF +.It Cabletron RoamAbout Ta Hermes Ta PCMCIA +.It Compaq Agency NC5004 Ta Prism-2 Ta PCMCIA +.It Compaq W100 Ta Prism-3 Ta USB +.It Contec FLEXLAN/FX-DS110-PCC Ta Prism-2 Ta PCMCIA +.It Corega PCC-11 Ta Prism-2 Ta PCMCIA +.It Corega PCCA-11 Ta Prism-2 Ta PCMCIA +.It Corega PCCB-11 Ta Prism-2 Ta PCMCIA +.It Corega CGWLPCIA11 Ta Prism-2 Ta PCI +.It Corega WLUSB-11 Ta Prism-3 Ta USB +.It Corega WLUSB-11 Key Ta Prism-3 Ta USB +.It D-Link DCF-660W Ta Prism-2 Ta CF +.It D-Link DWL-120 (rev F) Ta Prism-3 Ta USB +.It D-Link DWL-122 Ta Prism-3 Ta USB +.It D-Link DWL-520 (rev A and B only) Ta Prism-2.5 Ta PCI +.It D-Link DWL-650 (rev A1-J3 only) Ta Prism-2.5 Ta PCMCIA +.It ELSA XI300 Ta Prism-2 Ta PCMCIA +.It ELSA XI325 Ta Prism-2.5 Ta PCMCIA +.It ELSA XI325H Ta Prism-2.5 Ta PCMCIA +.It ELSA XI800 Ta Prism-2 Ta CF +.It EMTAC A2424i Ta Prism-2 Ta PCMCIA +.It Ericsson Wireless LAN CARD C11 Ta Spectrum24 Ta PCMCIA +.It Gemtek WL-311 Ta Prism-2.5 Ta PCMCIA +.It Hawking Technology WE110P Ta Prism-2.5 Ta PCMCIA +.It I-O DATA WN-B11/PCM Ta Prism-2 Ta PCMCIA +.It I-O DATA WN-B11/USB Ta Prism-3 Ta USB +.It Intel PRO/Wireless 2011 Ta Spectrum24 Ta PCMCIA +.It Intel PRO/Wireless 2011B Ta Prism-3 Ta USB +.It Intersil Prism II Ta Prism-2 Ta PCMCIA +.It Intersil Mini PCI Ta Prism-2.5 Ta PCI +.It Intersil ISL3872 Ta Prism-3 Ta PCI +.It Intersil Prism 2X Ta Prism-3 Ta USB +.It JVC MP-XP7250 Ta Prism-3 Ta USB +.It Linksys WCF12 Ta Prism-3 Ta CF +.It Linksys Instant Wireless WPC11 Ta Prism-2 Ta PCMCIA +.It Linksys Instant Wireless WPC11 2.5 Ta Prism-2.5 Ta PCMCIA +.It Linksys Instant Wireless WPC11 3.0 Ta Prism-3 Ta PCMCIA +.It Linksys WUSB11 v3.0 Ta Prism-3 Ta USB +.It Linksys WUSB12 Ta Prism-3 Ta USB +.It Longshine 8301 Ta Prism-2 Ta PCI +.It Lucent WaveLAN Ta Hermes Ta PCMCIA +.It Melco WLI-USB-KB11 Ta Prism-3 Ta USB +.It Melco WLI-USB-KS11G Ta Prism-3 Ta USB +.It Melco WLI-USB-S11 Ta Prism-3 Ta USB +.It Microsoft MN510 Ta Prism-3 Ta USB +.It Microsoft MN520 Ta Prism-2.5 Ta PCMCIA +.It NANOSPEED ROOT-RZ2000 Ta Prism-2 Ta PCMCIA +.It NDC/Sohoware NCP130 Ta Prism-2 Ta PCI +.It NEC CMZ-RT-WP Ta Prism-2 Ta PCMCIA +.It Netgear MA111 (version 1 only) Ta Prism-3 Ta USB +.It Netgear MA311 Ta Prism-2.5 Ta PCI +.It Netgear MA401 Ta Prism-2 Ta PCMCIA +.It Netgear MA401RA Ta Prism-2.5 Ta PCMCIA +.It Netgear MA701 Ta Prism-2.5 Ta CF +.It Nokia C020 Wireless LAN Ta Prism-I Ta PCMCIA +.It Nokia C110/C111 Wireless LAN Ta Prism-2 Ta PCMCIA +.It Nortel E-mobility 211818-A Ta Spectrum24 Ta PCI +.It NTT-ME 11Mbps Wireless LAN Ta Prism-2 Ta PCMCIA +.It Pheenet WL-503IA Ta Prism-3 Ta USB +.It Planex GW-NS11H Ta Prism-3 Ta PCMCIA +.It Planex GW-US11H Ta Prism-3 Ta USB +.It Pretec Compact WLAN OC-WLBXX-A Ta Prism-2.5 Ta CF +.It Proxim Harmony Ta Prism-2 Ta PCMCIA +.It Proxim RangeLAN-DS Ta Prism-2 Ta PCMCIA +.It Samsung MagicLAN SWL-2000N Ta Prism-2 Ta PCMCIA +.It Samsung MagicLAN SWL-2210P Ta Prism-2 Ta PCI +.It Senao NL-2511CF Ta Prism-3 Ta CF +.It Senao NL-2511MP Ta Prism-2.5 Ta PCI +.It Siemens SpeedStream SS1021 Ta Prism-2 Ta PCMCIA +.It Siemens SpeedStream SS1022 Ta Prism-3 Ta USB +.It Sitecom WL-022 Ta Prism-3 Ta USB +.It SMC 2632 EZ Connect Ta Prism-2 Ta PCMCIA +.It Symbol Spectrum24 Ta Spectrum24 Ta PCMCIA +.It Symbol LA4123 Ta Spectrum24 Ta PCI +.It Syntax USB-400 Ta Prism-3 Ta USB +.It TDK LAK-CD011WL Ta Prism-2 Ta PCMCIA +.It US Robotics 1120 Ta Prism-3 Ta USB +.It US Robotics 2410 Ta Prism-2 Ta PCMCIA +.It US Robotics 2445 Ta Prism-2 Ta PCMCIA +.It ViewSonic Airsync Ta Prism-2.5 Ta USB +.It Z-Com XI-725/726 Ta Prism-2.5 Ta USB +.It Z-Com XI-735 Ta Prism-3 Ta USB +.It ZyXEL ZyAIR B-200 Ta Prism-3 Ta USB +.El +.Pp +Note that some of the PRISM-II adapters only work at 3.3V, hence +.Xr cardbus 4 +support is required for those cards to set VCC correctly, even +though they are really 16-bit cards. +.Pp +USB support is still experimental and the device may stop functioning +during normal use. +Resetting the device by configuring the interface down and back up again will +normally reactivate it. +.Pp +Several vendors sell PCI adapters built around the PLX Technology 9050 +or 9052 chip. +The following such adapters are supported or expected to work: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It 3Com AirConnect 3CRWE777A (3.3V) +.It Addtron AWA-100 +.It Belkin F5D6000 (a rebadged WL11000P) +.It Eumitcom WL11000P +.It Global Sun Technology GL24110P (untested) +.It Global Sun Technology GL24110P02 +.It Linksys WDT11 (a rebadged GL24110P02) +.It Longshine 8031 +.It Netgear MA301 +.It Siemens/Efficient Networks SpeedStream 1023 +.It US Robotics 2415 (rebadged WL11000P) +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig wi0 scan +.Pp +The following +.Xr hostname.if 5 +example configures wi0 to join network +.Dq mynwid , +using WEP key +.Dq mywepkey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +nwid mynwid nwkey mywepkey +inet autoconf +.Ed +.Pp +The following +.Xr hostname.if 5 +example creates a host-based access point on boot: +.Bd -literal -offset indent +inet 192.168.1.1 255.255.255.0 +mediaopt hostap +nwid mynwid nwkey mywepkey +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "wi0: init failed" +The WaveLAN card failed to come ready after an initialization command +was issued. +.It "wi0: failed to allocate N bytes on NIC" +The driver was unable to allocate memory for transmit frames in the +NIC's on-board RAM. +.It "wi0: device timeout" +The WaveLAN failed to generate an interrupt to acknowledge a transmit +command. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr pcmcia 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Rs +.%T HCF Light programming specification +.Re +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 3.0 . +.Ox +support was added in +.Ox 2.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ctr.columbia.edu +and ported to +.Ox +by +.An Niklas Hallqvist Aq Mt niklas@appli.se . +.Sh CAVEATS +The original Lucent WaveLAN cards usually default to channel 3; +newer cards use channel 10 by default. +Non-Lucent cards vary, for instance the Addtron cards use channel +11 by default. +See +.Xr ifconfig 8 +for information on how to change the channel. +.Pp +Not all 3.3V +.Nm +PCMCIA cards work. +.Pp +IBSS creation does not currently work with Symbol cards. +.Pp +The host-based access point mode on the Intersil PRISM cards has +bugs when used with firmware versions prior to 0.8.3 and is completely +unusable with firmware versions prior to 0.8.0 and 1.4.0-1.4.2. +.Pp +Software WEP is currently only supported in Host AP and BSS modes. +Furthermore, software WEP is currently incapable of decrypting +fragmented frames. +Lucent-based cards using firmware 8.10 and above fragment encrypted +frames sent at 11Mbps. +To work around this, Lucent clients with this firmware revision +connecting to a Host AP server should use a 2Mbps connection or +upgrade their firmware to version 8.72. +.Pp +Host AP mode doesn't support WDS. +.Pp +Support for USB devices is buggy. +Host AP mode and AP scanning are not currently supported with USB devices. diff --git a/static/openbsd/man4/witness.4 b/static/openbsd/man4/witness.4 new file mode 100644 index 00000000..bcdfe669 --- /dev/null +++ b/static/openbsd/man4/witness.4 @@ -0,0 +1,95 @@ +.\" $OpenBSD: witness.4,v 1.5 2019/01/29 14:07:15 visa Exp $ +.\" +.\" Copyright (c) 2001 John H. Baldwin +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" $FreeBSD: head/share/man/man4/witness.4 301719 2016-06-09 06:55:00Z trasz $ +.\" +.Dd $Mdocdate: January 29 2019 $ +.Dt WITNESS 4 +.Os +.Sh NAME +.Nm witness +.Nd lock validation facility +.Sh DESCRIPTION +The +.Nm +module keeps track of the locks acquired and released by each thread. +It also keeps track of the order in which locks are acquired with respect +to each other. +Each time a lock is acquired, +.Nm +uses these two lists to verify that a lock is not being acquired in the +wrong order. +If a lock order violation is detected, then a message is printed to the +kernel console detailing the locks involved and the locations in question. +.Pp +The +.Nm +code also checks various other conditions such as verifying that one +does not recurse on a non-recursive lock, +or attempt an upgrade on a shared lock held by another thread. +If any of these checks fail, then the kernel will panic. +.Pp +The behaviour of +.Nm +is controlled by the +.Va kern.witness.watch +.Xr sysctl 8 +variable. +Valid values for it are: +.Pp +.Bl -tag -width 1nr -compact -offset indent +.It \-1 +disable +.Nm witness +completely +.It 0 +disable error checking +.It 1 +print a message if an error is detected +.It 2 +print a message and a stack trace if possible +.It 3 +like 2 but also drop into the kernel debugger +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr options 4 , +.Xr sysctl 8 , +.Xr mutex 9 , +.Xr rwlock 9 +.Sh HISTORY +The +.Nm +code first appeared in +.Bsx 5.0 +and was imported from there into +.Fx 5.0 . +The +.Ox +port was derived from +.Fx +and first appeared in +.Ox 6.2 . diff --git a/static/openbsd/man4/wpi.4 b/static/openbsd/man4/wpi.4 new file mode 100644 index 00000000..5ee6cbaa --- /dev/null +++ b/static/openbsd/man4/wpi.4 @@ -0,0 +1,168 @@ +.\" $OpenBSD: wpi.4,v 1.46 2025/03/25 19:57:54 jmc Exp $ +.\" +.\" Copyright (c) 2006, 2007 +.\" Damien Bergamini . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice unmodified, this list of conditions, and the following +.\" disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 25 2025 $ +.Dt WPI 4 +.Os +.Sh NAME +.Nm wpi +.Nd Intel PRO/Wireless 3945ABG IEEE 802.11a/b/g wireless network device +.Sh SYNOPSIS +.Cd "wpi* at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for Intel +PRO/Wireless 3945ABG Mini PCI Express network adapters. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver offloads both encryption and decryption of unicast data frames to the +hardware for the CCMP cipher. +.Pp +In BSS mode, +the driver supports powersave mode, +which can be enabled via +.Xr ifconfig 8 . +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The driver needs at least version 3.1 of the following firmware file, +which is loaded when an interface is brought up: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/wpi-3945abg +.El +.Pp +This firmware file is not free because Intel refuses to grant +distribution rights without contractual obligations. +As a result, even though +.Ox +includes the driver, the firmware file cannot be included and +users have to download this file on their own. +.Pp +A prepackaged version of the firmware can be installed using +.Xr fw_update 8 . +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig wpi0 scan +.Pp +The following +.Xr hostname.if 5 +example configures wpi0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "wpi0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.It "wpi0: fatal firmware error" +For some reason, the firmware crashed. +The driver will reset the hardware. +This should not happen. +.It "wpi0: Radio transmitter is off" +The radio transmitter is off and thus no packet can go out. +The driver will reset the hardware. +Make sure the laptop radio switch is on. +.It "wpi0: error N, could not read firmware ..." +For some reason, the driver was unable to read the firmware image from the +filesystem. +The file might be missing or corrupted. +.It "wpi0: firmware file too short: N bytes" +The firmware image is corrupted and can't be loaded into the adapter. +.It "wpi0: could not load firmware" +An attempt to load the firmware into the adapter failed. +The driver will reset the hardware. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Damien Bergamini Aq Mt damien.bergamini@free.fr . diff --git a/static/openbsd/man4/wscons.4 b/static/openbsd/man4/wscons.4 new file mode 100644 index 00000000..5c7de07b --- /dev/null +++ b/static/openbsd/man4/wscons.4 @@ -0,0 +1,251 @@ +.\" $OpenBSD: wscons.4,v 1.24 2023/11/12 09:21:36 dlg Exp $ +.\" $NetBSD: wscons.4,v 1.11 2000/04/13 11:14:42 is Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: November 12 2023 $ +.Dt WSCONS 4 +.Os +.Sh NAME +.Nm wscons +.Nd workstation console access +.Sh SYNOPSIS +.Cd option WSEMUL_SUN +.Cd option WSEMUL_NO_VT100 +.Cd option WSEMUL_DEFAULT=\&"xxx\&" +.Cd option WS_KERNEL_FG=WSCOL_XXX +.Cd option WS_KERNEL_BG=WSCOL_XXX +.Cd option WSDISPLAY_COMPAT_USL +.Cd option WSDISPLAY_COMPAT_RAWKBD +.Pp +.Cd "wsdisplay* at ..." +.Cd "wskbd* at ... mux N" +.Cd "wsmouse* at ... mux N" +.Pp +.Cd "pseudo-device wsmux" Op Ar count +.Sh DESCRIPTION +The +.Nm +driver provides support for machine-independent access to the console. +.Pp +.Nm +is made of a number of cooperating modules, in particular +.Bl -bullet +.It +Hardware support for display adapters, keyboards and mice; see +.Xr wsdisplay 4 , +.Xr wskbd 4 , +and +.Xr wsmouse 4 . +.It +Input event multiplexor; see +.Xr wsmux 4 . +.It +Terminal emulation modules (see below). +.It +Compatibility options to support control operations and other low-level +behaviour of existing terminal drivers (see below). +.El +.Ss Terminal emulations +.Nm +does not define its own set of terminal control sequences and special keyboard +codes in terms of +.Xr termcap 5 . +Instead, a +.Dq terminal emulation +is assigned to each virtual screen when the screen is created (see +.Xr wsconscfg 8 ) . +Different terminal emulations can be active at the same time on one display. +.Pp +The following choices are available: +.Bl -tag -width vt100 +.It dumb +This minimal terminal support is always available. +No control sequences are supported besides the ASCII control characters. +The cursor is not addressable. +Only ASCII keyboard codes will be delivered, cursor and functions keys +do not work. +.It sun +The +.Dq sun +console emulation is available by default on the sparc64 architecture, +or if +.Cd option WSEMUL_SUN +was specified at kernel build time. +It supports the control sequences of +.Tn SUN +machine consoles and delivers its keyboard codes for function and +keypad keys (as far as present on the actually used keyboard). +.Pp +ANSI colors are also supported on this emulation, if the +.Ev TERM +environment variable is set to +.Ar rcons-color . +.Pp +This emulation is sufficient for full-screen applications. +.It vt100 +is available by default, but can be disabled with +.Cd option WSEMUL_NO_VT100 . +It provides the most commonly used functions of +.Tn DEC VT100 +terminals with some extensions introduced by the +.Tn DEC VT220 +and +.Tn DEC VT320 +models. +The features of the original +.Tn VT100 +which are not, or not completely, implemented are: +.Bl -bullet +.It +.Tn VT52 +support, 132-column-mode, smooth scroll, light background, keyboard +autorepeat control, external printer support, keyboard locking, +newline/linefeed switching: Escape sequences related +to these features are ignored or answered with standard replies. +(DECANM, DECCOLM, DECSCLM, DECSCNM, DECARM, DECPFF, DECPEX, KAM, LNM) +.It +Function keys are not reprogrammable and fonts cannot be downloaded. +DECUDK and DECDLD sequences will be ignored. +.It +Neither C1 control set characters will be recognized nor will 8-bit keyboard +codes be delivered. +.It +The +.Dq DEC supplemental graphic +font is approximated by the ISO-latin-1 font, though there are +subtle differences. +.It +The actual rendering quality depends on the underlying graphics +hardware driver. +Characters might be missing in the available fonts and be +substituted by more or less fitting replacements. +.Pp +Depending on the keyboard used, not all function keys might be available. +.El +.Pp +In addition to the plain +.Tn VT100 +functions, the following features are supported: +.Bl -bullet +.It +ANSI colors +.It +Some +.Tn VT220 +-like presentation state settings and -reports (DECRSPS), especially +tabulator settings. +.El +.Pp +In most applications, +.Nm +will work sufficiently as a +.Tn VT220 +emulator. +.El +.Pp +The +.Va WSEMUL_DEFAULT +kernel option allows selecting one of the described terminal options +as the default choice. +The default goes into effect at kernel startup, i.e., +for the operating system console or additional screens allocated +through the +.Va WSDISPLAY_DEFAULTSCREENS +option (see +.Xr wsdisplay 4 ) , +or if no emulation type was passed to the +.Xr wsconscfg 8 +utility. +.Pp +.Em Compatibility options : +these options allow running X servers or other programs using low-level +console driver functions which were written specifically for other +console drivers to run on +.Ox +systems. +The options are in particular: +.Bl -tag -width WSDISPLAY_COMPAT_xxxxxxxx +.It Cd WSDISPLAY_COMPAT_USL +Support the protocol for switches between multiple virtual screens on +one display as used by most PC-UNIX variants. +.It Cd WSDISPLAY_COMPAT_RAWKBD +Allows getting raw XT keyboard scancodes from PC keyboards as needed +by X servers. +.El +.Pp +.Em Other options : +.Bl -tag -width 3n +.It Cd option WS_KERNEL_FG=WSCOL_XXX +.It Cd option WS_KERNEL_BG=WSCOL_XXX +.It Cd option \&WS_KERNEL_COLATTR="(WSATTR_XXX | WSATTR_YYY)" +.It Cd option \&WS_KERNEL_MONOATTR="(WSATTR_XXX | WSATTR_YYY)" +Make console output originating from the kernel appear differently +than output from user level programs (via +.Pa /dev/console +or the specific tty +device like +.Pa /dev/ttyC0 ) . +.Dq WS_KERNEL_FG +and +.Dq WS_KERNEL_BG +set the foreground/background used on color displays. +.Pp +The +.Dq WSCOL_XXX +arguments are colors as defined in +.Pa /usr/include/dev/wscons/wsdisplayvar.h . +.Dq WS_KERNEL_COLATTR +and +.Dq WS_KERNEL_MONOATTR +are additional attribute flags used on color or monochrome displays, +respectively. +The arguments are defined in the same header file. +Whether the attributes +are supported or not depends on the actually used graphics adapter. +These options are ignored by the +.Dq dumb +terminal emulation. +.It Cd option WSCOMPAT_USL_SYNCTIMEOUT=nnn +The virtual screen switching protocol enabled by +.Dq WSDISPLAY_COMPAT_USL +uses a somewhat complex handshake protocol to pass control to user programs +as X servers controlling a virtual screen. +To avoid a non-responsive application locking the whole console system, a +screen switch will be rolled back if the user application does not respond +to a screen switch request within some time. +This option sets the timeout (in seconds); +the default value is 5 seconds. +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr wsdisplay 4 , +.Xr wskbd 4 , +.Xr wsmouse 4 , +.Xr wsmux 4 , +.Xr wsconscfg 8 , +.Xr wsconsctl 8 , +.Xr wsfontload 8 , +.Xr wsmoused 8 diff --git a/static/openbsd/man4/wsdisplay.4 b/static/openbsd/man4/wsdisplay.4 new file mode 100644 index 00000000..e1d7eb6c --- /dev/null +++ b/static/openbsd/man4/wsdisplay.4 @@ -0,0 +1,713 @@ +.\" $OpenBSD: wsdisplay.4,v 1.57 2022/03/31 17:27:21 naddy Exp $ +.\" $NetBSD: wsdisplay.4,v 1.5 2000/05/13 15:22:19 mycroft Exp $ +.\" +.\" Copyright (c) 2005, Miodrag Vallat. +.\" Copyright (c) 1999 Matthias Drochner. +.\" Copyright (c) 2002 Ben Harris. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 31 2022 $ +.Dt WSDISPLAY 4 +.Os +.Sh NAME +.Nm wsdisplay +.Nd generic display device support in wscons +.Sh SYNOPSIS +.Cd "wsdisplay* at ..." +.Cd "option WSDISPLAY_DEFAULTSCREENS=N" +.Sh DESCRIPTION +The +.Nm +driver is an abstraction layer for display devices within the +.Xr wscons 4 +framework. +It attaches to the hardware specific display device driver and +makes it available as text terminal or graphics interface. +.Pp +Display devices have the ability to display characters on them +(without help of an X server), either directly by hardware or through +software drawing pixel data into the display memory. +The +.Nm +driver will connect a terminal emulation module and provide a +tty-like software interface. +.Pp +The +.Em console +locator in the configuration line refers to the device's use as output +part of the operating system console. +A device specification containing a positive value here will only match +if the device is in use as system console. +(The console device selection in early system startup is not influenced.) +This way, the console device can be connected to a known +.Nm wsdisplay +device instance. +.Pp +The +.Em mux +locator in the configuration line refers to the +.Xr wsmux 4 +that will be used to get keyboard events. +If this locator is -1, no mux will be used. +.Pp +The logical unit of an independent contents displayed on a display +(sometimes referred to as +.Dq virtual terminal ) +is called a +.Dq screen +here. +If the underlying device driver supports it, multiple screens can +be used on one display. +(As of this writing, only the +.Xr lcd 4 +and +.Xr vga 4 +display drivers provide this ability.) +Screens have different minor device numbers and separate tty instances. +One screen possesses the +.Dq focus , +this means it is displayed on the display and its tty device will get +the keyboard input. +(In some cases, if no screen is set up or if a screen +was just deleted, it is possible that no focus is present at all.) +The focus can be switched by either special keyboard input (typically +CTL-ALT-Fn) or an ioctl command issued by a user program. +Screens are set up or deleted through the +.Pa /dev/ttyCcfg +control device (preferably using the +.Xr wsconscfg 8 +utility). +Alternatively, the compile-time +.Cd "option WSDISPLAY_DEFAULTSCREENS=N" +will set up N screens of the display driver's default type and using +the system's default terminal emulator at autoconfiguration time. +.Pp +In addition and with help from backend drivers the following features +are also provided: +.Bl -bullet +.It +Loading, deleting and listing the loaded fonts. +.It +Browsing backwards in the screen output, the size of the +buffer for saved text is defined by the particular hardware driver. +.It +Blanking the screen by timing out on inactivity in the +screen holding the input focus. +Awakening activities consist of: +.Pp +.Bl -bullet -compact +.It +pressing any keys on the keyboard; +.It +moving or clicking the mouse; +.It +any output to the screen. +.El +.Pp +Blanking the screen is usually done by disabling the horizontal sync +signal on video output, but may also include blanking the vertical +sync in which case most monitors go into power saving mode. +See +.Xr wsconsctl 8 +for controlling variables. +.El +.Pp +Consult the back-end drivers' documentation for which features are supported +for each particular hardware type. +.Ss IOCTL INTERFACE +The following +.Xr ioctl 2 +calls are provided by the +.Nm +driver or by devices which use it. +Their definitions are found in +.In dev/wscons/wsconsio.h . +.Bl -tag -width 4n +.It Dv WSDISPLAYIO_GTYPE Fa u_int +Retrieve the type of the display. +The list of types is in +.In dev/wscons/wsconsio.h . +.It Dv WSDISPLAYIO_GINFO Fa "struct wsdisplay_fbinfo" +Retrieve basic information about a framebuffer display. +The returned structure is as follows: +.Bd -literal -offset indent +struct wsdisplay_fbinfo { + u_int height; + u_int width; + u_int depth; + u_int cmsize; +}; +.Ed +.Pp +The +.Va height +and +.Va width +members are counted in pixels. +The +.Va depth +member indicates the number of bits per pixel, and +.Va cmsize +indicates the number of color map entries accessible through +.Dv WSDISPLAYIO_GETCMAP +and +.Dv WSDISPLAYIO_PUTCMAP . +This call is likely to be unavailable on text-only displays. +.It Dv WSDISPLAYIO_GETSCREENTYPE Fa "struct wsdisplay_screentype" +Retrieve basic information about a screen. +The returned structure is as follows: +.Bd -literal -offset indent +struct wsdisplay_screentype { + int idx; + int nidx; + char name[WSSCREEN_NAME_SIZE]; + int ncols, nrows; + int fontwidth, fontheight; +}; +.Ed +.Pp +The +.Va idx +field indicates the index of the screen. +The +.Va nidx +field indicates the number of screens. +The +.Va name +field contains a human readable string used to identify the screen. +The +.Va ncols +and +.Va nrows +fields indicate the available number of columns and rows. +The +.Va fontwidth +and +.Va fontheight +fields indicate the dimensions of a character cell, in pixels. +.It Dv WSDISPLAYIO_GETCMAP Fa "struct wsdisplay_cmap" +Retrieve the current color map from the display. +This call needs the +following structure set up beforehand: +.Bd -literal -offset indent +struct wsdisplay_cmap { + u_int index; + u_int count; + u_char *red; + u_char *green; + u_char *blue; +}; +.Ed +.Pp +The +.Va index +and +.Va count +members specify the range of color map entries to retrieve. +The +.Va red , +.Va green , +and +.Va blue +members should each point to an array of +.Va count +.Vt u_char Ns s . +On return, these will be filled in with the appropriate entries from the +color map. +On all displays that support this call, values range from 0 for minimum +intensity to 255 for maximum intensity, even if the display does not use +eight bits internally to represent intensity. +.It Dv WSDISPLAYIO_PUTCMAP Fa "struct wsdisplay_cmap" +Change the display's color map. +The argument structure is the same as for +.Dv WSDISPLAYIO_GETCMAP , +but +.Va red , +.Va green , +and +.Va blue +are taken as pointers to the values to use to set the color map. +This call is not available on displays with fixed color maps. +.It Dv WSDISPLAYIO_GVIDEO Fa u_int +Get the current state of the display's video output. +Possible values are: +.Bl -tag -width 21n +.It Dv WSDISPLAYIO_VIDEO_OFF +The display is blanked. +.It Dv WSDISPLAYIO_VIDEO_ON +The display is enabled. +.El +.It Dv WSDISPLAYIO_SVIDEO Fa u_int +Set the state of the display's video output. +See +.Dv WSDISPLAYIO_GVIDEO +above for possible values. +.It Dv WSDISPLAYIO_GCURPOS Fa "struct wsdisplay_curpos" +Retrieve the current position of the hardware cursor. +The returned structure +is as follows: +.Bd -literal -offset indent +struct wsdisplay_curpos { + u_int x, y; +}; +.Ed +.Pp +The +.Va x +and +.Va y +members count the number of pixels right and down, respectively, from +the top-left corner of the display to the hot spot of the cursor. +This call is not available on displays without a hardware cursor. +.It Dv WSDISPLAYIO_SCURPOS Fa "struct wsdisplay_curpos" +Set the current cursor position. +The argument structure, and its semantics, +are the same as for +.Dv WSDISPLAYIO_GCURPOS . +This call is not available on displays without a hardware cursor. +.It Dv WSDISPLAYIO_GCURMAX Fa "struct wsdisplay_curpos" +Retrieve the maximum size of cursor supported by the display. +The +.Va x +and +.Va y +members of the returned structure indicate the maximum number of pixel rows +and columns, respectively, in a hardware cursor on this display. +This call is not available on displays without a hardware cursor. +.It Dv WSDISPLAYIO_GCURSOR Fa "struct wsdisplay_cursor" +Retrieve some or all of the hardware cursor's attributes. +The argument structure is as follows: +.Bd -literal -offset indent +struct wsdisplay_cursor { + u_int which; + u_int enable; + struct wsdisplay_curpos pos; + struct wsdisplay_curpos hot; + struct wsdisplay_cmap cmap; + struct wsdisplay_curpos size; + u_char *image; + u_char *mask; +}; +.Pp +.Ed +The +.Va which +member indicates which of the values the application requires to be returned. +It should contain the logical OR of the following flags: +.Bl -tag -width 4n +.It Dv WSDISPLAY_CURSOR_DOCUR +Get +.Va enable , +which indicates whether the cursor is currently displayed (non-zero) or +not (zero). +.It Dv WSDISPLAY_CURSOR_DOPOS +Get +.Va pos , +which indicates the current position of the cursor on the display, as +would be returned by +.Dv WSDISPLAYIO_GCURPOS . +.It Dv WSDISPLAY_CURSOR_DOHOT +Get +.Va hot , +which indicates the location of the +.Dq hot spot +within the cursor. +This is the point on the cursor whose position on the display is treated +as being the position of the cursor by other calls. +Its location is counted in pixels from the top-left corner of the cursor. +.It Dv WSDISPLAY_CURSOR_DOCMAP +Get +.Va cmap , +which indicates the current cursor color map. +Unlike in a call to +.Dv WSDISPLAYIO_GETCMAP , +.Va cmap +here need not have its +.Va index +and +.Va count +members initialized. +They will be set to 0 and 2 respectively by the call. +This means that +.Va cmap . Ns Va red , +.Va cmap . Ns Va green , +and +.Va cmap . Ns Va blue +must each point to at least enough space to hold two +.Vt u_char Ns s . +.It Dv WSDISPLAY_CURSOR_DOSHAPE +Get +.Va size , image , +and +.Va mask . +These are, respectively, the dimensions of the cursor in pixels, the +bitmap of set pixels in the cursor and the bitmap of opaque pixels in +the cursor. +The format in which these bitmaps are returned, and hence the amount of +space that must be provided by the application, are device-dependent. +.It Dv WSDISPLAY_CURSOR_DOALL +Get all of the above. +.El +.Pp +The device may elect to return information that was not requested by the user, +so those elements of +.Vt struct wsdisplay_cursor +which are pointers should be initialized to +.Dv NULL +if not otherwise used. +This call is not available on displays without a hardware cursor. +.It Dv WSDISPLAYIO_SCURSOR Fa "struct wsdisplay_cursor" +Set some or all of the hardware cursor's attributes. +The argument structure is the same as for +.Dv WSDISPLAYIO_GCURSOR . +The +.Va which +member specifies which attributes of the cursor are to be changed. +It should contain the logical OR of the following flags: +.Bl -tag -width 4n +.It Dv WSDISPLAY_CURSOR_DOCUR +If +.Va enable +is zero, hide the cursor. +Otherwise, display it. +.It Dv WSDISPLAY_CURSOR_DOPOS +Set the cursor's position on the display to +.Va pos , +the same as +.Dv WSDISPLAYIO_SCURPOS . +.It Dv WSDISPLAY_CURSOR_DOHOT +Set the +.Dq hot spot +of the cursor, as defined above, to +.Va hot . +.It Dv WSDISPLAY_CURSOR_DOCMAP +Set some or all of the cursor color map based on +.Va cmap . +The +.Va index +and +.Va count +elements of +.Va cmap +indicate which color map entries to set, and the entries themselves come from +.Va cmap . Ns Va red , +.Va cmap . Ns Va green , +and +.Va cmap . Ns Va blue . +.It Dv WSDISPLAY_CURSOR_DOSHAPE +Set the cursor shape from +.Va size , image , +.Va mask . +See above for their meanings. +.It Dv WSDISPLAY_CURSOR_DOALL +Do all of the above. +.El +.Pp +This call is not available on displays without a hardware cursor. +.It Dv WSDISPLAYIO_GMODE Fa u_int +Get the current mode of the display. +Possible results include: +.Bl -tag -width 4n +.It Dv WSDISPLAYIO_MODE_EMUL +The display is in emulating (text) mode. +.It Dv WSDISPLAYIO_MODE_MAPPED +The display is in mapped (graphics) mode. +.It Dv WSDISPLAYIO_MODE_DUMBFB +The display is in mapped (frame buffer) mode. +.El +.It Dv WSDISPLAYIO_SMODE Fa u_int +Set the current mode of the display. +For possible arguments, see +.Dv WSDISPLAYIO_GMODE . +.It Dv WSDISPLAYIO_LDFONT Fa "struct wsdisplay_font" +Loads a font specified by the wsdisplay_font structure. +.Bd -literal -offset indent +struct wsdisplay_font { + char name[WSFONT_NAME_SIZE]; + int index; + int firstchar, numchars; + int encoding; + u_int fontwidth, fontheight, stride; + int bitorder, byteorder; + void *cookie; + void *data; +}; +.Ed +.Pp +The +.Va name +field contains a human readable string used to identify the font. +The +.Va index +field may be used to select a driver-specific font resource (for non-raster +frame buffers). +A value of -1 will pick the first available slot. +The +.Va firstchar +field contains the index of the first character in the font, starting at zero. +The +.Va numchars +field contains the number of characters in the font. +The +.Va encoding +field describes the font character encoding, using one of the following values: +.Bl -tag -width 4n +.It Dv WSDISPLAY_FONTENC_ISO +ISO-8859-1 encoding +.Pq also known as Latin-1 . +This is the preferred encoding for raster frame buffers. +.It Dv WSDISPLAY_FONTENC_IBM +IBM code page number 437. +This is the preferred encoding for text-mode displays. +.El +.Pp +The +.Va fontwidth +and +.Va fontheight +fields specify the dimensions of a character cell. +The +.Va stride +field specify the number of bytes of font data per character cell line (usually +.Va fontwidth +rounded up to a byte boundary). +The +.Va bitorder +and +.Va byteorder +fields specify the bit- and byte-ordering of the font data, using either one of +the following values: +.Bl -tag -width 4n +.It Dv WSDISPLAY_FONTORDER_L2R +Leftmost data contained in the most significant bits (left-to-right ordering). +This is the most commonly encountered case. +.It Dv WSDISPLAY_FONTORDER_R2L +Leftmost data contained in the least significant bits (right-to-left ordering). +.El +.Pp +The +.Va data +field contains the font character data to be loaded. +The +.Va cookie +field is reserved for internal purposes. +.It Dv WSDISPLAYIO_LSFONT Fa "struct wsdisplay_font" +Retrieves the data for a loaded font into the wsdisplay_font structure. +The +.Va index +field is set to the font resource to query. +For the argument structure, see +.Dv WSDISPLAYIO_LDFONT . +.\" Dv WSDISPLAYIO_DELFONT Fa "struct wsdisplay_font" +.It Dv WSDISPLAYIO_USEFONT Fa "struct wsdisplay_font" +Selects the font specified in the +.Va name +field. +An empty +.Va name +selects the next available font. +For the argument structure, see +.Dv WSDISPLAYIO_LDFONT . +.It Dv WSDISPLAYIO_GBURNER Fa "struct wsdisplay_burner" +Retrieves the state of the screen burner. +The returned structure is as follows: +.Bd -literal -offset indent +struct wsdisplay_burner { + u_int off; + u_int on; + u_int flags; +}; +.Ed +.Pp +The +.Va off +member contains the inactivity time before the screen is turned off, +in milliseconds. +The +.Va on +member contains the time before the screen is turned back on, +in milliseconds. +The +.Va flags +member contains a logical OR of the following flags: +.Bl -tag -width 4n +.It Dv WSDISPLAY_BURN_VBLANK +When turning the display off, disable the vertical synchronization signal. +.It Dv WSDISPLAY_BURN_KBD +Monitor keyboard activity. +.It Dv WSDISPLAY_BURN_MOUSE +Monitor mouse activity +(this only works for mice using the +.Xr wsmouse 4 +driver). +.It Dv WSDISPLAY_BURN_OUTPUT +Monitor display output activity. +.El +.Pp +If none of the activity source flags are set, the screen burner is disabled. +.It Dv WSDISPLAYIO_SBURNER Fa "struct wsdisplay_burner" +Sets the state of the screen burner. +The argument structure, and its semantics, are the same as for +.Dv WSDISPLAYIO_GBURNER . +.It Dv WSDISPLAYIO_ADDSCREEN Fa "struct wsdisplay_addscreendata" +Creates a new screen. +.Bd -literal -offset indent +struct wsdisplay_addscreendata { + int idx; /* screen index */ + char screentype[WSSCREEN_NAME_SIZE]; + char emul[WSEMUL_NAME_SIZE]; +}; +.Ed +.Pp +The +.Va idx +field is the index of the screen to be configured. +The +.Va screentype +field is matched against builtin screen types, which will be driver-dependent. +The +.Va emul +field indicates the terminal emulation type. +Available terminal emulations are: +.Bl -tag -width 5n +.It sun +Sun terminal emulation. +This is the default on the sparc64 architecture. +.It vt100 +Dec VT100 terminal emulation, with some VT220 features. +This is the default on all other architectures. +.It dumb +Dumb terminal. +.El +.Pp +An empty string will select the default emulation. +.It Dv WSDISPLAYIO_DELSCREEN Fa "struct wsdisplay_delscreendata" +Deletes an existing screen. +.Bd -literal -offset indent +struct wsdisplay_delscreendata { + int idx; /* screen index */ + int flags; +}; +.Ed +.Pp +The +.Va idx +field indicates the index of the screen to be deleted. +The +.Va flags +field is a logical OR of zero or more of the following: +.Bl -tag -width 4n +.It Dv WSDISPLAY_DELSCR_FORCE +Force deletion of screen even if in use by a userspace program. +.It Dv WSDISPLAY_DELSCR_QUIET +Don't report deletion to console. +.El +.It Dv WSDISPLAYIO_GETSCREEN Fa "struct wsdisplay_addscreendata" +Returns information on the screen indicated by +.Va idx +or the current screen if +.Va idx +is -1. +The screen and emulation types are returned in the same structure +.Pq see Dv WSDISPLAYIO_GETPARAM . +.It Dv WSDISPLAYIO_SETSCREEN Fa u_int +Switch to the screen with the given index. +.It Dv WSDISPLAYIO_WSMOUSED Fa "struct wscons_event" +This call is used by the +.Xr wsmoused 8 +daemon to inject mouse events gathered from serial mice, as well as +various control events. +.It Dv WSDISPLAYIO_GETPARAM Fa "struct wsdisplay_param" +Retrieves the state of a display parameter. +This call needs the following structure set up beforehand: +.Bd -literal -offset indent +struct wsdisplay_param { + int param; + int min, max, curval; + int reserved[4]; +}; +.Ed +.Pp +The +.Va param +member should be set with the parameter to be returned. +The following parameters are supported: +.Bl -tag -width 4n +.It Dv WSDISPLAYIO_PARAM_BACKLIGHT +The intensity of the display backlight (usually on laptop computers). +.It Dv WSDISPLAYIO_PARAM_BRIGHTNESS +The brightness level. +.It Dv WSDISPLAYIO_PARAM_CONTRAST +The contrast level. +.El +.Pp +On return, +.Va min +and +.Va max +specify the allowed range for the value, while +.Va curval +specifies the current setting. +Not all parameters are supported by all display drivers. +.It Dv WSDISPLAYIO_SETPARAM Fa "struct wsdisplay_param" +Sets a display parameter. +The argument structure is the same as for +.Dv WSDISPLAYIO_GETPARAM , +with the +.Va param +and +.Va curval +members filled in. +Not all parameters are supported by all display drivers. +.It Dv WSDISPLAYIO_LINEBYTES Fa u_int +Get the number of bytes per row when the device is in +.Dv WSDISPLAYIO_MODE_DUMBFB +mode. +.El +.Sh FILES +.Bl -tag -width /usr/include/dev/wscons/wsconsio.h -compact +.It Pa /dev/tty[C-F]* +terminal devices (per screen) +.It Pa /dev/tty[C-F]cfg +control device (per screen) +.It Pa /usr/include/dev/wscons/wsconsio.h +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr tty 4 , +.Xr wscons 4 , +.Xr wsmux 4 , +.Xr wsconscfg 8 , +.Xr wsconsctl 8 , +.Xr wsfontload 8 +.Sh BUGS +The +.Nm +code currently limits the number of screens on one display to 12. +.Pp +The terms +.Dq wscons +and +.Dq wsdisplay +are not cleanly distinguished in the code and in manual pages. diff --git a/static/openbsd/man4/wskbd.4 b/static/openbsd/man4/wskbd.4 new file mode 100644 index 00000000..56c3f03c --- /dev/null +++ b/static/openbsd/man4/wskbd.4 @@ -0,0 +1,274 @@ +.\" $OpenBSD: wskbd.4,v 1.25 2025/08/16 11:28:25 matthieu Exp $ +.\" $NetBSD: wskbd.4,v 1.5 2000/03/20 11:51:59 pk Exp $ +.\" +.\" Copyright (c) 1999 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 16 2025 $ +.Dt WSKBD 4 +.Os +.Sh NAME +.Nm wskbd +.Nd generic keyboard support in wscons +.Sh SYNOPSIS +.Cd "wskbd* at ..." +.Sh DESCRIPTION +The +.Nm +driver handles common tasks for keyboards within the +.Xr wscons 4 +framework. +It is attached to the hardware specific keyboard drivers and +provides their connection to +.Dq wsdisplay +devices and a character device interface. +.Pp +The common keyboard support consists of: +.Bl -bullet +.It +Mapping from keycodes (defined by the specific keyboard driver) to +keysyms (hardware independent, defined in +.Pa /usr/include/dev/wscons/wsksymdef.h ) . +.It +Handling of +.Dq compose +sequences. +Characters commonly not present as separate keys on keyboards +can be generated after either a special +.Dq compose +key is pressed or a +.Dq dead accent +character is used. +.It +Certain translations, like turning an +.Dq ALT +modifier into an +.Dq ESC +prefix. +.It +Automatic key repetition +.Pf ( Dq typematic ) . +.It +Parameter handling for +.Dq keyboard bells . +.It +Generation of +.Dq keyboard events +for use by X servers. +.El +.Pp +The +.Nm +driver provides a number of ioctl functions to control key maps +and other parameters. +These functions are accessible through the associated +.Dq wsdisplay +device as well. +A complete list is in +.Pa /usr/include/dev/wscons/wsconsio.h . +The +.Xr wsconsctl 8 +utility allows access to key maps and other variables. +.Pp +The +.Em console +locator in the configuration line refers to the device's use as input +part of the operating system console. +A device specification containing a positive value here will only match +if the device is in use as system console. +(The console device selection in early system startup is not influenced.) +This way, the console device can be connected to a known +.Nm wskbd +device instance. +.Pp +The +.Nm +driver traps certain key sequences intended to perform special functions. +The +.Cm Ctrl+Alt+Esc +sequence will initiate the +.Xr ddb 4 +kernel debugger if the +.Dq ddb.console +.Xr sysctl 8 +variable is set. +When attached to a +.Xr wsdisplay 4 +device, +.Cm Ctrl+Alt+Fx +switches virtual terminals and the +.Cm Shift+PgUp +and +.Cm Shift+PgDn +combinations provide scrollback functionality if the underlying hardware +driver supports it. +When audio devices are supported, keys +.Cm Mute , +.Cm VolumeUp +and +.Cm VolumeDown +tweak mixer settings. +.Ss Keyboard encodings +The following encodings are supported. +Device drivers for legacy keyboard interfaces may only support a subset +of these. +However, generally, all encodings are supported by +.Xr pckbd 4 +and +.Xr ukbd 4 . +.Bl -column ".Li us.colemak" ".Dv KB_US|KB_COLEMAK" +.It Sy "wsconsctl" Ta Sy "define" Ta Sy "language" +.It Li user Ta Dv KB_USER Ta User-defined +.It Li us Ta Dv KB_US Ta English/US keyboard mapping (default) +.It Li uk Ta Dv KB_UK Ta English/UK keyboard mapping +.It Li be Ta Dv KB_BE Ta Belgian +.It Li br Ta Dv KB_BR Ta Brazilian with +.Dq dead accents +.It Li cf Ta Dv KB_CF Ta Canadian French +.It Li dk Ta Dv KB_DK Ta Danish with +.Dq dead accents +.It Li nl Ta Dv KB_NL Ta Dutch +.It Li ee Ta Dv KB_EE Ta Estonian with +.Dq dead accents +.It Li fr Ta Dv KB_FR Ta French +.It Li de Ta Dv KB_DE Ta German QWERTZ with +.Dq dead accents +.It Li hu Ta Dv KB_HU Ta Hungarian +.It Li is Ta Dv KB_IS Ta Icelandic with +.Dq dead accents +.It Li it Ta Dv KB_IT Ta Italian +.It Li jp Ta Dv KB_JP Ta Japanese +.It Li la Ta Dv KB_LA Ta Latin American Spanish +.It Li no Ta Dv KB_NO Ta Norwegian with +.Dq dead accents +.It Li pl Ta Dv KB_PL Ta Polish +.It Li pt Ta Dv KB_PT Ta Portuguese +.It Li ru Ta Dv KB_RU Ta Russian +.It Li es Ta Dv KB_ES Ta Spanish +.It Li sv Ta Dv KB_SV Ta Swedish with +.Dq dead accents +.It Li sf Ta Dv KB_SF Ta Swiss French +.It Li sg Ta Dv KB_SG Ta Swiss German +.It Li tr Ta Dv KB_TR Ta Turkish (QWERTY) with +.Dq dead accents +.It Li ua Ta Dv KB_UA Ta Ukrainian +.It Li us.declk Ta Dv "KB_US|KB_DECLK" Ta English/US mapping for +.Tn DEC LK400 Ns - Ns style +keyboards with PC keyboard interface (e.g., +.Tn LK461 ) +.It Li us.dvorak Ta Dv "KB_US|KB_DVORAK" Ta English/US keyboard with +.Dq Dvorak +layout +.It Li us.colemak Ta Dv "KB_US|KB_COLEMAK" Ta English/US keyboard with +.Dq Colemak +layout +.El +.Pp +The +.Dq Li \&.nodead +suffix +.Dv ( KB_NODEAD +flag) +can be applied to layouts with +.Dq dead accents +to switch them off. +.Pp +The +.Dv KB_US , +.Dv KB_UK , +.Dv KB_FR , +.Dv KB_JP +and +.Dv KB_US|KB_DVORAK +mappings can be modified +to swap the left +.Aq Ctrl +and the +.Aq CapsLock +keys by the +.Dv KB_SWAPCTRLCAPS +variant bit or the +.Dq Li .swapctrlcaps +suffix. +.Pp +The +.Dq Li .metaesc +suffix +.Dv ( KB_METAESC +flag) +option can be applied to any layout. +If set, keys pressed together +with the +.Tn ALT +modifier are prefixed by an +.Tn ESC +character. +(Standard behaviour is to add 128 to the +.Tn ASCII +value.) +.Ss Ioctls +The following +.Xr ioctl 2 +calls are provided by the +.Nm +driver or by devices which use it. +Their definitions are found in +.In dev/wscons/wsconsio.h . +.Bl -tag -width Dv +.It Dv WSKBDIO_GTYPE +Get the keyboard type. +.It Dv WSKBDIO_GETMODE +Get the keyboard mode, 0 means translated through keyboard map, 1 means raw. +.It Dv WSKBDIO_SETMODE +Set the keyboard mode. +.It Dv WSKBDIO_COMPLEXBELL , WSKBDIO_SETBELL , WSKBDIO_GETBELL , WSKBDIO_SETDEFAULTBELL , WSKBDIO_GETDEFAULTBELL Pq Vt "struct wskbd_bell_data" +Get and set keyboard bell settings. +.It Dv WSKBDIO_SETKEYREPEAT , WSKBDIO_GETKEYREPEAT , WSKBDIO_SETDEFAULTKEYREPEAT , WSKBDIO_GETDEFAULTKEYREPEAT Pq Vt "struct wskbd_keyrepeat_data" +Get and set keyboard autorepeat settings. +.It Dv WSKBDIO_SETLEDS , WSKBDIO_GETLEDS Pq Vt "int" +Get and set keyboard LED settings. +.It Dv WSKBDIO_GETMAP , WSKBDIO_SETMAP Pq Vt "struct wskbd_map_data" +Get and set keyboard keymapping settings. +.It Dv WSKBDIO_GETBACKLIGHT, WSKBDIO_SETBACKLIGHT Pq Vt "struct wskbd_backlight" +Get and set keyboard backlight +.It Dv WSKBDIO_GETENCODING , WSKBDIO_SETENCODING Pq Vt "kbd_t" +Get and set keyboard encoding settings. +.El +.Sh FILES +.Bl -tag -width /usr/include/dev/wscons/wsksymdef.h -compact +.It Pa /dev/wskbd* +.It Pa /usr/include/dev/wscons/wsksymdef.h +.It Pa /usr/include/dev/wscons/wsconsio.h +.El +.Sh SEE ALSO +.Xr akbd 4 , +.Xr comkbd 4 , +.Xr hilkbd 4 , +.Xr intro 4 , +.Xr pckbd 4 , +.Xr ukbd 4 , +.Xr wscons 4 , +.Xr wsmux 4 , +.Xr zskbd 4 , +.Xr wsconsctl 8 diff --git a/static/openbsd/man4/wsmouse.4 b/static/openbsd/man4/wsmouse.4 new file mode 100644 index 00000000..ee9bf561 --- /dev/null +++ b/static/openbsd/man4/wsmouse.4 @@ -0,0 +1,233 @@ +.\" $OpenBSD: wsmouse.4,v 1.26 2026/04/12 12:35:06 jsg Exp $ +.\" $NetBSD: wsmouse.4,v 1.3 1999/12/06 14:52:08 augustss Exp $ +.\" +.\" Copyright (c) 2018 Ulf Brosziewski +.\" Copyright (c) 1999 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd $Mdocdate: April 12 2026 $ +.Dt WSMOUSE 4 +.Os +.Sh NAME +.Nm wsmouse +.Nd generic mouse support in wscons +.Sh SYNOPSIS +.Cd "wsmouse* at ..." +.Sh DESCRIPTION +The +.Nm +driver is an abstraction layer for mice and other pointing devices within the +.Xr wscons 4 +framework. +It is attached to the hardware specific drivers and +provides a character device interface which returns +.Fa struct wscons_event +via +.Xr read 2 . +For use with X servers, +.Dq mouse events +or +.Dq touch events +can be generated. +.Pp +The +.Nm +driver provides a number of ioctl functions to control various parameters (see +.Pa /usr/include/dev/wscons/wsconsio.h ) . +The +.Xr wsconsctl 8 +utility gives access to these variables. +.Pp +Touchpad input is processed in one of two modes: +In +.Dq absolute mode , +the +.Nm +driver generates touch events. +Absolute mode is activated by +.Xr synaptics 4 . +In +.Dq compatibility mode , +which is the default, +.Nm +converts the input internally and generates mouse events. +.Xr wsconsctl 8 +can query and set several configuration parameters for this mode. +The composite field names have the form +.Cm mouse Ns Oo Ar N Oc . Ns Cm tp . Ns Ar field +where +.Ar N +is the index of the +.Nm +device. +If +.Ar N +is omitted, commands apply to +.Pa /dev/wsmouse0 . +.Bl -tag -width Ds +.It Cm mouse.reverse_scrolling +Reverse direction of scrolling. +.It Cm mouse.scaling +The value is a scale coefficient that is applied to the relative +coordinates. +It determines the base speed of the pointer. +.It Cm mouse.tp.tapping +Contacts on the touchpad that are immediately released again can +be mapped to mouse button clicks. +This list of three parameters configures these mappings, in the order: +.Bd -literal -offset indent +.Sm off +.Ar one-finger , two-finger , three-finger +.Sm on +.Ed +.Pp +Setting a parameter to a positive value enables that tap gesture +and maps it to the given mouse button. +To disable all three tap gestures at once, provide the single value of 0. +Conversely, a single non-zero value will enable one-finger, two-finger, and +three-finger tap gestures with their default mappings of left +button, right button, and middle button, respectively. +If, within a short time interval, a second touch follows a tap gesture +mapped to a left-button click, the button-up event is not issued +until that touch ends +.Pq Dq tap-and-drag . +.It Cm mouse.tp.mtbuttons +This feature is supported for some clickpads. +If enabled, two-finger clicks - with the fingers side by side - generate +left-button events, and three-finger clicks generate middle-button events. +.It Cm mouse.tp.swapsides +If this parameter has a non-zero value, the order of software +button areas is inverted. +If edge scrolling is enabled, the scroll area is set up at the left +edge of the touchpad. +.It Cm mouse.tp.disable +A non-zero value disables pointer movement, tapping, and scrolling. +Software buttons (and external physical buttons) will work as usual. +.It Cm mouse.tp.edges +This field contains a list of four values that define the relative +sizes of the edge areas, in the order: +.Bd -literal -offset indent +.Sm off +.Ar top , right , bottom , left +.Sm on +.Ed +.Pp +The unit is percent of the total height of the touchpad surface, or +of its total width, respectively. +In order to mitigate the effects of accidental touches, the driver +ignores most types of input from an edge area (see below). +If an edge area contains software buttons, they fill up the space +provided. +.El +.Pp +The automatic configuration enables two-finger scrolling and sets up +edge areas at the vertical edges. +On clickpads - where the device surface serves as a single, large +button - it provides three software button areas at the bottom edge, +for left-button, middle-button, and right-button clicks. +On some laptops with a trackpoint, the software buttons are at the +top edge. +Vertical edge scrolling will be enabled on older touchpads that do not +report contact counts. +.Pp +A touch that starts and remains in an edge area does not trigger pointer +movement. +At the vertical edges and the top edge, tapping and two-finger scrolling +require that at least one touch is in the main area of the touchpad (the +exact behaviour of a single-touch device depends on its firmware in this +case). +When multi-touch input is available, a touch is ignored if it rests in +the bottom area while there are other inputs - movement, scrolling, or +tapping -, and the driver continues to ignore it as long as and whenever +other touches are present. +.Ss Ioctls +The following +.Xr ioctl 2 +calls are provided by the +.Nm +driver or by devices which use it. +Their definitions are found in +.Pa dev/wscons/wsconsio.h . +.Bl -tag -width Dv +.It Dv WSKBDIO_GTYPE +Get the mouse or device type. +.It Dv WSMOUSEIO_SRES Pq Vt "int" +Set the resolution of the pointer. +Not applicable to all mouse types. +.It Dv WSMOUSEIO_GCALIBCOORDS, WSMOUSEIO_SCALIBCOORDS Pq Vt "struct wsmouse_calibcoords" +Get and set device calibration data for touchscreens. +.It Dv WSMOUSEIO_SETMODE Pq Vt "int" +Sets the mode of a touchpad device +.Po Li WSMOUSE_COMPAT +or +.Li WSMOUSE_NATIVE Pc +.It Dv WSMOUSEIO_GETPARAMS, WSMOUSEIO_SETPARAMS Pq Vt "struct wsmouse_parameters" +Obtain and set various mouse parameters as a key/value set. +Currently these primarily relate to touchpads. +The structure +.Vt struct wsmouse_parameters +is defined as follows: +.Bd -literal -offset indent +struct wsmouse_param { + enum wsmousecfg key; + int value; +}; + +struct wsmouse_parameters { + struct wsmouse_param *params; + unsigned int nparams; +}; +.Ed +.Pp +The number of parameters to read or write must be specified in +.Va nparams . +For each parameter, when +.Dv WSMOUSEIO_GETPARAMS +is used, a key must be specified. +When +.Dv WSMOUSEIO_SETPARAMS +is used, a key and a value must be specified. +A single ioctl may retrieve up to +.Dv WSMOUSECFG_MAX +.Va nparams . +.El +.Sh FILES +.Bl -tag -width /usr/include/dev/wscons/wsconsio.h -compact +.It Pa /dev/wsmouse* +.It Pa /usr/include/dev/wscons/wsconsio.h +.El +.Sh SEE ALSO +.Xr ams 4 , +.Xr hilms 4 , +.Xr intro 4 , +.Xr lms 4 , +.Xr mms 4 , +.Xr pms 4 , +.Xr ubcmtp 4 , +.Xr ums 4 , +.Xr utpms 4 , +.Xr wscons 4 , +.Xr wsmux 4 , +.Xr wsconsctl 8 , +.Xr wsmoused 8 diff --git a/static/openbsd/man4/wsmux.4 b/static/openbsd/man4/wsmux.4 new file mode 100644 index 00000000..85b7bcc4 --- /dev/null +++ b/static/openbsd/man4/wsmux.4 @@ -0,0 +1,146 @@ +.\" $OpenBSD: wsmux.4,v 1.17 2025/08/16 13:33:48 jsg Exp $ +.\" $NetBSD: wsmux.4,v 1.2 1999/11/03 22:01:40 castor Exp $ +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: August 16 2025 $ +.Dt WSMUX 4 +.Os +.Sh NAME +.Nm wsmux +.Nd console keyboard/mouse multiplexor for wscons +.Sh SYNOPSIS +.Cd "wskbd* at ... mux N" +.Cd "wsmouse* at ... mux N" +.Pp +.Cd "pseudo-device wsmux" Op Ar count +.Sh DESCRIPTION +The +.Nm +is a pseudo-device driver that allows several +.Xr wscons 4 +input devices to have their events multiplexed into one stream. +.Pp +The typical usage for this device is to have two multiplexors, one +for mouse events and one for keyboard events. +All +.Xr wsmouse 4 +devices should direct their events to the mouse mux (normally 0) +and all keyboard devices, except the console, should direct their +events to the keyboard mux (normally 1). +A device will send its events to the mux indicated by the +.Va mux +locator. +If none is given, the device will not use a multiplexor. +The keyboard multiplexor should be connected to the display, using +the +.Xr wsconscfg 8 +command. +It will then receive all keystrokes from all keyboards and, furthermore, +keyboards can be dynamically attached and detached without further +user interaction. +In a similar way, the window system will open the mouse multiplexor +and receive all mouse events; mice can also be dynamically attached +and detached. +.Pp +It is also possible to inject events into a multiplexor from a user program. +This is used by the +.Xr wsmoused 8 +daemon to take data from a mouse connected to a serial port and +make it appear on the standard mouse mux. +.Ss Ioctls +.Nm +supports +.Xr ioctl 2 +commands to configure and manage events that are returned. +The following commands are available: +.Bl -tag -width Dv +.It Dv WSMUXIO_INJECTEVENT Pq Vt "struct wscons_event" +injects a synthetic event to the given device. +Used by +.Xr wsmoused 8 . +This command uses the same +.Vt wscons_event +structure as returned by +.Xr read 2 +on +.Xr wscons 4 +input devices as input. +.Bd -literal +struct wscons_event { + u_int type; + int value; + struct timespec time; +}; +.Ed +.It Dv WSMUXIO_ADD_DEVICE Pq Vt "struct wsmux_device" +adds a device to the mux. +This commands uses a +.Vt wsmux_device +structure as input. +.Bd -literal +struct wsmux_device { + int type; +#define WSMUX_MOUSE 1 +#define WSMUX_KBD 2 +#define WSMUX_MUX 3 + int idx; +}; +.Ed +.It Dv WSMUXIO_REMOVE_DEVICE Pq Vt "struct wsmux_device" +removes a device from the mux. +.It Dv WSMUXIO_LIST_DEVICES Pq Vt "struct wsmux_device_list" +returns an array of WSMUX_MAXDEV elements describing the devices attached to +the mux. +The array is composed of +.Fa wsmux_device +structures enclosed in a +.Fa wsmux_device_list +structure. +.Bd -literal +struct wsmux_device_list { + int ndevices; + struct wsmux_device devices[WSMUX_MAXDEV]; +}; +.Ed +.El +.Sh FILES +.Bl -item -compact +.It +.Pa /dev/wsmouse +.It +.Pa /dev/wskbd +.It +.Pa /usr/include/dev/wscons/wsconsio.h +.El +.Sh SEE ALSO +.Xr intro 4 , +.Xr wscons 4 , +.Xr wsdisplay 4 , +.Xr wskbd 4 , +.Xr wsmouse 4 , +.Xr wsconscfg 8 , +.Xr wsconsctl 8 , +.Xr wsmoused 8 diff --git a/static/openbsd/man4/xbf.4 b/static/openbsd/man4/xbf.4 new file mode 100644 index 00000000..b5fdf414 --- /dev/null +++ b/static/openbsd/man4/xbf.4 @@ -0,0 +1,57 @@ +.\" $OpenBSD: xbf.4,v 1.2 2016/12/07 17:11:09 jmc Exp $ +.\" +.\" Copyright (c) 2016 Mike Belopuhov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 7 2016 $ +.Dt XBF 4 +.Os +.Sh NAME +.Nm xbf +.Nd Xen Blkfront virtual disk +.Sh SYNOPSIS +.Cd "xbf* at xen?" +.Sh DESCRIPTION +The +.Nm +driver provides support for a paravirtual disk interface +.Qq Blkfront , +native to the Xen hypervisor. +.Pp +During attach the +.Nm +driver will ask the hypervisor to switch all configured virtual disks +over to the Blkfront interface regardless of the VM configuration. +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr intro 4 , +.Xr xen 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 6.1 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mike Belopuhov Aq Mt mikeb@openbsd.org +based on the +.Xr vdsk 4 +driver by +.An -nosplit +.An Mark Kettenis Aq Mt kettenis@openbsd.org , +inspired by the +.Fx +implementation. diff --git a/static/openbsd/man4/xe.4 b/static/openbsd/man4/xe.4 new file mode 100644 index 00000000..6708b901 --- /dev/null +++ b/static/openbsd/man4/xe.4 @@ -0,0 +1,62 @@ +.\" $OpenBSD: xe.4,v 1.12 2007/05/31 19:19:53 jmc Exp $ +.\" +.\" Copyright (c) 1999 Niklas Hallqvist +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 31 2007 $ +.Dt XE 4 +.Os +.Sh NAME +.Nm xe +.Nd Xircom-based 16-bit PCMCIA 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "xe* at pcmcia?" +.Cd "icsphy* at mii?" +.Sh DESCRIPTION +The +.Nm +interface provides access to a 10/100 Mb/s Ethernet network via a +Xircom Ethernet card. +The Ethernet cards known to be supported by the +.Nm +interface are: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Xircom Realport +.It Xircom CE3 +.El +.Pp +However, most 16-bit Xircom Ethernet cards should work. +.Sh SEE ALSO +.Xr arp 4 , +.Xr icsphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr pcmcia 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver appeared in +.Ox 2.5 . diff --git a/static/openbsd/man4/xen.4 b/static/openbsd/man4/xen.4 new file mode 100644 index 00000000..45cb7f98 --- /dev/null +++ b/static/openbsd/man4/xen.4 @@ -0,0 +1,77 @@ +.\" $OpenBSD: xen.4,v 1.3 2021/10/21 15:56:17 denis Exp $ +.\" +.\" Copyright (c) 2015 Mike Belopuhov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: October 21 2021 $ +.Dt XEN 4 +.Os +.Sh NAME +.Nm xen +.Nd Xen domU nexus device +.Sh SYNOPSIS +.Cd "xen0 at pvbus?" +.Sh DESCRIPTION +.Nm +driver performs HVM domU guest initialization, provides abstraction for +virtual Xen interrupts, access to the XenStore configuration storage as +well as a device probing facility for paravirtualized devices such as +disk and network interfaces. +.Pp +When running under XenServer, to let the host know that the guest has +finished initializing and to allow graceful shutdown, set the following +XenStore properties with +.Xr hostctl 8 +in +.Xr rc.local 8 : +.Bd -literal -offset indent +ostype=$(sysctl -n kern.ostype) +osrelease=$(sysctl -n kern.osrelease) + +# XenServer Tools version +hostctl attr/PVAddons/MajorVersion 6 +hostctl attr/PVAddons/MinorVersion 2 +hostctl attr/PVAddons/MicroVersion 0 +hostctl attr/PVAddons/BuildVersion 76888 +hostctl attr/PVAddons/Installed 1 + +# OS version +hostctl data/os_name "$ostype $osrelease" +hostctl data/os_uname $osrelease +hostctl data/os_distro $ostype + +# Inform Xen of IPs bound to the VM +hostctl attr/vif/0/ipv4/0 192.0.2.1 +hostctl attr/vif/0/ipv6/0 2001:db8::1 + +# Update XenStore +hostctl data/updated 1 +.Ed +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr intro 4 , +.Xr pvbus 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mike Belopuhov Aq Mt mikeb@openbsd.org +from scratch, inspired by the +.Fx +implementation. diff --git a/static/openbsd/man4/xf86.4 b/static/openbsd/man4/xf86.4 new file mode 100644 index 00000000..c421df9b --- /dev/null +++ b/static/openbsd/man4/xf86.4 @@ -0,0 +1,119 @@ +.\" $OpenBSD: xf86.4,v 1.19 2015/05/28 20:53:05 jcs Exp $ +.\" +.\" Copyright (c) 1998 Matthieu Herrb +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: May 28 2015 $ +.Dt XF86 4 +.Os +.Sh NAME +.Nm xf86 +.Nd X Window System aperture driver +.Sh SYNOPSIS +.Cd "option APERTURE" +.Sh DESCRIPTION +On +the alpha, amd64, i386, macppc, and sparc64 architectures, +the +.Pa /dev/xf86 +driver provides access to the memory and I/O ports of a VGA board +and to the PCI configuration registers +for use by the X servers +when running with a kernel security level greater than 0. +.Pp +The X servers require the use of this driver for +.Xr isa 4 +or +.Xr pci 4 +video cards on +.Ar alpha , +.Ar amd64 , +.Ar i386 , +.Ar macppc , +and +.Ar sparc64 . +.Sh ACCESS CONTROL +Access to the +.Pa /dev/xf86 +device is allowed when the +.Xr sysctl 8 +variable +.Va machdep.allowaperture +is greater than or equal to 1. +This variable (which has a default value of 0) +can only be raised when the security level +is less than or equal to 0, so it should be +set in +.Pa /etc/sysctl.conf . +The possible values for +.Va machdep.allowaperture +are: +.Bl -tag -width Ds +.It 0 +the aperture driver is disabled. +Opening it returns +.Dv EPERM . +.It 1 +the aperture driver allows access to standard VGA framebuffer and BIOS. +Access to +.Xr pci 4 +configuration registers is also allowed. +.It 2 +in addition to allowing access to +.Xr pci 4 +configuration registers, +the aperture driver allows access to the whole first megabyte of physical +memory, permitting use of the int10 emulation in X.Org 6.8 and later. +Note that this can cause some security problems, since the process that +has access to the aperture driver can also access part of the kernel +memory. +This mode is not supported on alpha or sparc64. +.It 3 +the aperture driver allows multiple processes to concurrently access +.Xr pci 4 +configuration registers and the whole first megabyte of physical memory. +.El +.Sh SEE ALSO +.Xr Xorg 1 , +.Xr options 4 , +.Xr pci 4 , +.Xr sysctl.conf 5 , +.Xr securelevel 7 , +.Xr config 8 , +.Xr sysctl 8 +.Sh HISTORY +.Pa /dev/xf86 +was integrated as an in-kernel device on +.Ox 2.3 . +It is required in order to allow access to I/O ports for all X servers since +.Ox 2.4 . +.Sh AUTHORS +The aperture driver was written by +.An Matthieu Herrb . +.Sh BUGS +This driver allows access to all addresses above +.Va physmem . +It should be restricted to the actual address range of the video +memory. diff --git a/static/openbsd/man4/xge.4 b/static/openbsd/man4/xge.4 new file mode 100644 index 00000000..970f35ae --- /dev/null +++ b/static/openbsd/man4/xge.4 @@ -0,0 +1,97 @@ +.\" $OpenBSD: xge.4,v 1.20 2013/07/16 16:05:49 schwarze Exp $ +.\" $NetBSD: xge.4,v 1.2 2005/09/10 22:48:09 wiz Exp $ +.\" +.\" Copyright (c) 2005, SUNET, Swedish University Computer Network. +.\" All rights reserved. +.\" +.\" Written by Anders Magnusson for SUNET, Swedish University Computer Network. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed for the NetBSD Project by +.\" SUNET, Swedish University Computer Network. +.\" 4. The name of SUNET may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY SUNET ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SUNET +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 16 2013 $ +.Dt XGE 4 +.Os +.Sh NAME +.Nm xge +.Nd Neterion Xframe/Xframe II 10Gb Ethernet device +.Sh SYNOPSIS +.Cd "xge* at pci?" +.Sh DESCRIPTION +The +.Nm +device driver provides support for various NICs based on the Neterion +Xframe and Xframe II controller chips, including the following: +.Pp +.Bl -bullet -compact +.It +Fujitsu PRIMEQUEST 10GBASE-SR LAN Card (Xframe II) +.It +Hitachi PCI-X 10 Gigabit Ethernet Adapter (Xframe II) +.It +HP AB287A 10 Gigabit Ethernet Adapter (Xframe) +.It +IBM 10GbE SR Server Adapter (Xframe II) +.It +IBM 10 Gb Ethernet-LR PCI-X 2.0 DDR Adapter (Xframe II) +.It +IBM 10 Gb Ethernet-SR PCI-X 2.0 DDR Adapter (Xframe II) +.It +Neterion/S2io Xframe (Xframe) +.It +Neterion Xframe II (Xframe II) +.It +Neterion Xframe II Sun Fire (Xframe II) +.It +Neterion Xframe E (Xframe II) +.It +SGI 10 Gigabit Ethernet Network Adapter (Xframe) +.El +.Pp +The Xframe and Xframe II support IPv4 transmit/receive IP/TCP/UDP +checksum offload and VLAN tag insertion and stripping. +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr netintro 4 , +.Xr pci 4 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 4.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Anders Magnusson Aq Mt ragge@ludd.luth.se +and ported to +.Ox +by +.An Brad Smith Aq Mt brad@openbsd.org . diff --git a/static/openbsd/man4/xhci.4 b/static/openbsd/man4/xhci.4 new file mode 100644 index 00000000..fecc3e57 --- /dev/null +++ b/static/openbsd/man4/xhci.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: xhci.4,v 1.4 2021/12/29 18:44:52 patrick Exp $ +.\" +.\" Copyright (c) 2014 Martin Pieuchot +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 29 2021 $ +.Dt XHCI 4 +.Os +.Sh NAME +.Nm xhci +.Nd USB eXtensible Host Controller Interface +.Sh SYNOPSIS +.Cd "xhci* at acpi?" +.Cd "xhci* at fdt?" +.Cd "xhci* at pci?" +.Cd "usb* at xhci?" +.Sh DESCRIPTION +The +.Nm +driver provides support for the USB eXtensible Host Controller Interface, +which provides an interface to +.Xr usb 4 +devices. +.Pp +xHCI controllers support all USB 3.0, 2.0 and 1.x device speeds. +.Sh SEE ALSO +.Xr acpi 4 , +.Xr pci 4 , +.Xr usb 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Ox 5.6 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Martin Pieuchot Aq Mt mpi@openbsd.org . diff --git a/static/openbsd/man4/xl.4 b/static/openbsd/man4/xl.4 new file mode 100644 index 00000000..15b78fa4 --- /dev/null +++ b/static/openbsd/man4/xl.4 @@ -0,0 +1,209 @@ +.\" $OpenBSD: xl.4,v 1.48 2013/08/14 06:32:35 jmc Exp $ +.\" +.\" Copyright (c) 1997, 1998 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" $FreeBSD: xl.4,v 1.1 1998/08/16 17:19:58 wpaul Exp $ +.\" +.Dd $Mdocdate: August 14 2013 $ +.Dt XL 4 +.Os +.Sh NAME +.Nm xl +.Nd 3Com EtherLink XL and Fast EtherLink XL 10/100 Ethernet device +.Sh SYNOPSIS +.Cd "xl* at pci?" +.Cd "xl* at cardbus?" +.Cd "amphy* at mii?" +.Cd "bmtphy* at mii?" +.Cd "exphy* at mii?" +.Cd "nsphy* at mii?" +.Cd "tqphy* at mii?" +.Sh DESCRIPTION +The +.Nm +device driver supports the 3Com EtherLink XL and Fast EtherLink XL family +of Ethernet cards, and embedded controllers based on the 3Com +.Dq boomerang +and +.Dq cyclone +bus master EtherLink XL chips. +This includes, among others, the following models: +.Pp +.Bl -tag -width 3CXXXXX -offset indent -compact +.It 3C555 +EtherLink XL Mini PCI +.It 3C556 +EtherLink XL Mini PCI +.It 3C556B +EtherLink XL Mini PCI +.It 3C575 +10/100 LAN CardBus PC Card +.It 3C656 +10/100 LAN+Modem CardBus PC Card +.It 3C900 +EtherLink XL PCI +.It 3C900B +EtherLink XL PCI +.It 3C905 +Fast EtherLink XL PCI +.It 3C905B +Fast EtherLink XL PCI +.It 3C905C +Fast EtherLink XL PCI +.It 3C980 +Fast EtherLink Server NIC +.It 3CSOHO +OfficeConnect Fast Ethernet NIC +.It 9201 +NVIDIA nForce2 integrated 3Com 9201 (nForce2-ST, nForce2-GT) +.It 920BEMB +3c920B-EMB-WNM Integrated Fast Ethernet. +.El +.Pp +Category 3, 4 or 5 unshielded twisted-pair (UTP) cable should be used for +RJ-45 (10baseT), thick Ethernet coaxial (RG59 B/U, 50 ohm) for AUI/DIX, +and thin Ethernet coaxial (RG58 A/U or C/U, 50 ohm +/- 4) for BNC (10base2). +Some 3Com NICs also support MII connectors (switchable 10/100Mbps UTP). +The 3C905B-FX and other similar cards are capable of 100Mbps over fiber. +.Pp +Hardware receive IP/TCP/UDP checksum offload for IPv4 is supported on the 3C905B. +.Pp +The +.Nm +driver additionally supports Wake on LAN (WoL). +See +.Xr arp 8 +and +.Xr ifconfig 8 +for more details. +.Pp +The following media types and options (as given to +.Xr ifconfig 8 ) +are supported: +.Bl -tag -width xxx -offset indent +.It Cm media No autoselect +Enable autoselection of media type and options. +Note that this media type is only available with +adapters that have external PHYs or built-in autonegotiation logic. +For 3C900 and 3C900B adapters, the driver +will choose the mode specified in the EEPROM. +This can be changed by adding media options to the appropriate +.Xr hostname.if 5 +file. +.It Cm media No 100baseFX Cm mediaopt No full-duplex +For those cards that support it, force full-duplex 100Mbps operation over fiber. +.It Cm media No 100baseFX Cm mediaopt No half-duplex +For those cards that support it, force half-duplex 100Mbps operation over fiber. +.It Cm media No 100baseTX Cm mediaopt No full-duplex +Set 100Mbps (Fast Ethernet) operation and force full-duplex mode. +.It Cm media No 100baseTX Cm mediaopt No half-duplex +Set 100Mbps (Fast Ethernet) operation and force half-duplex mode. +.It Cm media No 10baseT Cm mediaopt No full-duplex +Set 10baseT (UTP) operation and force full-duplex mode. +.It Cm media No 10baseT Cm mediaopt No half-duplex +Set 10baseT (UTP) operation and force half-duplex mode. +.It Cm media No 10base5 +Set 10base5 (thick-net) operation (half-duplex only). +.It Cm media No 10base2 +Set 10base2 (thin-net) operation (half-duplex only). +.El +.Pp +For more information on configuring this device, see +.Xr ifconfig 8 . +To view a list of media types and options supported by this card try +.Ic ifconfig media . +For example, +.Ic ifconfig xl0 media . +.Sh DIAGNOSTICS +.Bl -diag +.It "xl0: couldn't map memory" +A fatal initialization error has occurred. +.It "xl0: couldn't map interrupt" +A fatal initialization error has occurred. +.It "xl0: device timeout" +The device has stopped responding to the network, or there is a problem with +the network connection (cable). +.It "xl0: no memory for rx list" +The driver failed to allocate an mbuf for the receiver ring. +.It "xl0: no memory for tx list" +The driver failed to allocate an mbuf for the transmitter ring when +allocating a pad buffer or collapsing an mbuf chain into a cluster. +.It "xl0: command never completed!" +Some commands issued to the 3C90x ASIC take time to complete: the +driver is supposed to wait until the +.Dq command in progress +bit in the status register clears before continuing. +In some instances, this bit may not clear. +To avoid getting caught in an infinite wait loop, +the driver only polls the bit a finite number of times before +giving up, at which point it issues this message. +This message may be printed during driver initialization on slower machines. +If this message appears but the driver continues to function normally, the +message can probably be ignored. +.It "xl0: WARNING: no media options bits set in the media options register!" +This warning may appear when using the driver on some Dell Latitude +docking stations with built-in 3C905-TX adapters. +For whatever the reason, the +.Dq MII available +bit in the media options register on +this particular equipment is not set, even though it should be (the +3C905-TX always uses an external PHY transceiver). +The driver will +attempt to guess the proper media type based on the PCI device ID word. +The driver makes a lot of noise about this condition because +the author considers it a manufacturing defect. +.El +.Sh SEE ALSO +.Xr amphy 4 , +.Xr arp 4 , +.Xr bmtphy 4 , +.Xr cardbus 4 , +.Xr exphy 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr nsphy 4 , +.Xr tqphy 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Fx 3.0 . +.Ox +support was added in +.Ox 2.4 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Bill Paul Aq Mt wpaul@ctr.columbia.edu . diff --git a/static/openbsd/man4/xmphy.4 b/static/openbsd/man4/xmphy.4 new file mode 100644 index 00000000..71e4c561 --- /dev/null +++ b/static/openbsd/man4/xmphy.4 @@ -0,0 +1,45 @@ +.\" $OpenBSD: xmphy.4,v 1.12 2009/07/31 14:20:29 jmc Exp $ +.\" +.\"Copyright (c) 2000 Jason L. Wright (jason@thought.net) +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE +.\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, +.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN +.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: July 31 2009 $ +.Dt XMPHY 4 +.Os +.Sh NAME +.Nm xmphy +.Nd XaQti XMAC-II Gigabit Ethernet PHY +.Sh SYNOPSIS +.Cd "xmphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports XaQti XMAC-II PHY interfaces found on +SysKonnect Gigabit Ethernet cards (see +.Xr sk 4 ) . +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 diff --git a/static/openbsd/man4/xnf.4 b/static/openbsd/man4/xnf.4 new file mode 100644 index 00000000..db27803e --- /dev/null +++ b/static/openbsd/man4/xnf.4 @@ -0,0 +1,52 @@ +.\" $OpenBSD: xnf.4,v 1.6 2016/01/15 22:21:56 jmc Exp $ +.\" +.\" Copyright (c) 2016 Mike Belopuhov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: January 15 2016 $ +.Dt XNF 4 +.Os +.Sh NAME +.Nm xnf +.Nd Xen Netfront networking interface +.Sh SYNOPSIS +.Cd "xnf* at xen?" +.Sh DESCRIPTION +The +.Nm +driver provides support for a paravirtual networking interface +.Dq Netfront +native to the Xen hypervisor. +.Pp +During attach the +.Nm +driver will ask the hypervisor to switch all configured virtual interfaces +over to the Netfront interface regardless of the VM configuration. +.Sh SEE ALSO +.Xr autoconf 4 , +.Xr intro 4 , +.Xr xen 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mike Belopuhov Aq Mt mikeb@openbsd.org +from scratch, inspired by the +.Fx +implementation. diff --git a/static/openbsd/man4/xspd.4 b/static/openbsd/man4/xspd.4 new file mode 100644 index 00000000..049b4160 --- /dev/null +++ b/static/openbsd/man4/xspd.4 @@ -0,0 +1,50 @@ +.\" $OpenBSD: xspd.4,v 1.1 2015/12/09 00:34:09 mikeb Exp $ +.\" +.\" Copyright (c) 2015 Mike Belopuhov +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: December 9 2015 $ +.Dt XSPD 4 +.Os +.Sh NAME +.Nm xspd +.Nd XenSource Platform Device driver +.Sh SYNOPSIS +.Cd "xspd0 at pci?" +.Sh DESCRIPTION +The +.Nm +driver provides +.Xr xen 4 +with alternative means to deliver virtual interrupts into the guest +system via +.Xr pci 4 +interrupt allocation. +.Sh SEE ALSO +.Xr intro 4 , +.Xr pci 4 , +.Xr xen 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 5.9 . +.Sh AUTHORS +The +.Nm +driver was written by +.An Mike Belopuhov Aq Mt mikeb@openbsd.org +from scratch, inspired by the +.Fx +implementation. diff --git a/static/openbsd/man4/yds.4 b/static/openbsd/man4/yds.4 new file mode 100644 index 00000000..820a15a0 --- /dev/null +++ b/static/openbsd/man4/yds.4 @@ -0,0 +1,73 @@ +.\" $OpenBSD: yds.4,v 1.12 2015/01/15 20:37:36 schwarze Exp $ +.\" +.\" Copyright (c) 2001 Aaron Campbell. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: January 15 2015 $ +.Dt YDS 4 +.Os +.Sh NAME +.Nm yds +.Nd Yamaha DS-XG audio device +.Sh SYNOPSIS +.Cd "yds* at pci? flags 0x0000" +.Cd "audio* at yds?" +.Sh DESCRIPTION +The +.Nm +driver supports Yamaha DS-XG based sound chips, as found in, e.g., many +Sony Vaio notebooks. +.Pp +The flags can be used to pass additional information +to the +.Nm +driver. +.Pp +A value of 0x1000 forces the driver to disable the Sound Blaster +legacy mode. +This is needed to make the floppy work on some machines +but is disabled by default because it is known to break +.Xr apm 4 +support. +.Sh FILES +The driver needs a firmware file, +which is loaded on demand when the device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/yds +.El +.Sh SEE ALSO +.Xr ac97 4 , +.Xr audio 4 , +.Xr intro 4 , +.Xr pci 4 +.Sh HISTORY +The +.Nm +driver first appeared in +.Ox 2.9 . +.Sh AUTHORS +.An -nosplit +.An Kazuki Sakamoto +and +.An Minoura Makoto . diff --git a/static/openbsd/man4/ytphy.4 b/static/openbsd/man4/ytphy.4 new file mode 100644 index 00000000..abc7d104 --- /dev/null +++ b/static/openbsd/man4/ytphy.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: ytphy.4,v 1.1 2023/03/04 22:44:27 kettenis Exp $ +.\" +.\" Copyright (c) 2023 Mark Kettenis +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.Dd $Mdocdate: March 4 2023 $ +.Dt YTPHY 4 +.Os +.Sh NAME +.Nm ytphy +.Nd MotorComm YT8511 10/100/1Gb Ethernet PHY +.Sh SYNOPSIS +.Cd "ytphy* at mii?" +.Sh DESCRIPTION +The +.Nm +driver supports the MotorComm YT8511 10/100/1Gb Ethernet PHY. +.Sh SEE ALSO +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr mii 4 , +.Xr ifconfig 8 +.Sh HISTORY +The +.Nm +device driver first appeared in +.Ox 7.3 . +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Mark Kettenis Aq Mt kettenis@openbsd.org . diff --git a/static/openbsd/man4/zero.4 b/static/openbsd/man4/zero.4 new file mode 100644 index 00000000..0d8490f1 --- /dev/null +++ b/static/openbsd/man4/zero.4 @@ -0,0 +1,44 @@ +.\" $OpenBSD: zero.4,v 1.4 2007/05/31 19:19:53 jmc Exp $ +.\" +.\" Copyright (c) 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.Dd $Mdocdate: May 31 2007 $ +.Dt ZERO 4 +.Os +.Sh NAME +.Nm zero +.Nd the zero device +.Sh DESCRIPTION +The +.Nm +device provides an infinite stream of null (zero) bytes. +.Sh FILES +.Bl -tag -width /dev/zero +.It Pa /dev/zero +.El +.Sh SEE ALSO +.Xr null 4 diff --git a/static/openbsd/man4/zyd.4 b/static/openbsd/man4/zyd.4 new file mode 100644 index 00000000..d84b8636 --- /dev/null +++ b/static/openbsd/man4/zyd.4 @@ -0,0 +1,217 @@ +.\" $OpenBSD: zyd.4,v 1.49 2025/03/25 19:57:54 jmc Exp $ +.\" +.\" Copyright (c) 1997, 1998, 1999 +.\" Bill Paul . All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Bill Paul. +.\" 4. Neither the name of the author nor the names of any co-contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF +.\" THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd $Mdocdate: March 25 2025 $ +.Dt ZYD 4 +.Os +.Sh NAME +.Nm zyd +.Nd ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless network device +.Sh SYNOPSIS +.Cd "zyd* at uhub? port ?" +.Sh DESCRIPTION +The +.Nm +driver provides support for wireless network adapters based around +the ZyDAS ZD1211 and ZD1211B USB chips. +.Pp +These are the modes the +.Nm +driver can operate in: +.Bl -tag -width "IBSS-masterXX" +.It BSS mode +Also known as +.Em infrastructure +mode, this is used when associating with an access point, through +which all traffic passes. +This mode is the default. +.It monitor mode +In this mode the driver is able to receive packets without +associating with an access point. +This disables the internal receive filter and enables the card to +capture packets from networks which it wouldn't normally have access to, +or to scan for access points. +.El +.Pp +The +.Nm +driver can be configured to use +Wired Equivalent Privacy (WEP) or +Wi-Fi Protected Access (WPA1 and WPA2). +WPA2 is currently the most secure encryption standard for wireless networks +supported by +.Ox . +It is strongly recommended that neither WEP nor WPA1 +are used as the sole mechanism to secure wireless communication, +due to serious weaknesses. +WPA1 is disabled by default and may be enabled using the option +.Qq Cm wpaprotos Ar wpa1,wpa2 . +For standard WPA networks which use pre-shared keys (PSK), +keys are configured using the +.Qq Cm wpakey +option. +WPA-Enterprise networks require use of the wpa_supplicant package. +The +.Nm +driver relies on the software 802.11 stack for both encryption and decryption +of data frames. +.Pp +The +.Nm +driver can be configured at runtime with +.Xr ifconfig 8 +or on boot with +.Xr hostname.if 5 . +.Sh FILES +The adapter needs some firmware files, which are loaded on demand by the +driver when a device is attached: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It Pa /etc/firmware/zd1211 +.It Pa /etc/firmware/zd1211b +.El +.Sh HARDWARE +The following devices are known to be supported by the +.Nm +driver: +.Pp +.Bl -tag -width Ds -offset indent -compact +.It 3COM 3CRUSB10075 +.It Acer WLAN-G-US1 +.It Airlink+ AWLL3025 +.It Airlink 101 AWLL3026 +.It AOpen 802.11g WL54 +.It Asus A9T integrated wireless +.It Asus WL-159g +.It Belkin F5D7050 v.4000 +.It Billion BiPAC 3011G +.It Buffalo WLI-U2-KG54L +.It CC&C WL-2203B +.It DrayTek Vigor 550 +.It Edimax EW-7317UG +.It Edimax EW-7317LDG +.It Fiberline Networks WL-43OU +.It iNexQ UR055g +.It Linksys WUSBF54G +.It Longshine LCS-8131G3 +.It MSI US54SE +.It Philips SNU5600 +.It Planet WL-U356 +.It Planex GW-US54GD +.It Planex GW-US54GXS +.It Planex GW-US54GZL +.It Planex GW-US54Mini +.It Planex GW-US54ZGL +.It Safecom SWMULZ-5400 +.It Sagem XG 760A +.It Sagem XG 76NA +.It Sandberg Wireless G54 USB +.It Sitecom WL-113 +.It Sitecom WL-603 +.It SMC SMCWUSB-G +.It Sweex wireless USB 54 Mbps +.It Tekram/Siemens USB adapter +.It Telegent TG54USB +.It Trendnet TEW-424UB rev A +.It Trendnet TEW-429UB +.It TwinMOS G240 +.It US Robotics 5423 +.It X-Micro XWL-11GUZX +.It Yakumo QuickWLAN USB +.It Zonet ZEW2501 +.It ZyXEL AG-220 +.It ZyXEL AG-225H v2 +.It ZyXEL G-200 v2 +.It ZyXEL G-202 +.It ZyXEL G-220 +.El +.Sh EXAMPLES +The following example scans for available networks: +.Pp +.Dl # ifconfig zyd0 scan +.Pp +The following +.Xr hostname.if 5 +example configures zyd0 to join network +.Dq mynwid , +using WPA key +.Dq mywpakey , +obtaining an IP address using DHCP: +.Bd -literal -offset indent +join mynwid wpakey mywpakey +inet autoconf +.Ed +.Sh DIAGNOSTICS +.Bl -diag +.It "zyd0: error N, could not read firmware ..." +For some reason, the driver was unable to read the firmware image from the +filesystem. +The file might be missing or corrupted. +.It "zyd0: could not load firmware (error=N)" +An error occurred while attempting to upload the firmware to the onboard +microcontroller unit. +.It "zyd0: could not send command (error=...)" +An attempt to send a command to the firmware failed. +.It "zyd0: sorry, radio ... is not supported yet" +Support for the specified radio chip is not yet implemented in the driver. +The device will not attach. +.It "zyd0: device version mismatch: 0xXXXX (only >= 43.30 supported)" +Early revisions of the ZD1211 chipset are not supported by this driver. +The device will not attach. +.It "zyd0: device timeout" +A frame dispatched to the hardware for transmission did not complete in time. +The driver will reset the hardware. +This should not happen. +.El +.Sh SEE ALSO +.Xr arp 4 , +.Xr ifmedia 4 , +.Xr intro 4 , +.Xr netintro 4 , +.Xr usb 4 , +.Xr hostname.if 5 , +.Xr ifconfig 8 +.Sh AUTHORS +.An -nosplit +The +.Nm +driver was written by +.An Florian Stoehr Aq Mt ich@florian-stoehr.de , +.An Damien Bergamini Aq Mt damien.bergamini@free.fr , +and +.An Jonathan Gray Aq Mt jsg@openbsd.org . +.Sh CAVEATS +The +.Nm +driver does not support a lot of the functionality available in the hardware. +More work is required to properly support the IBSS and power management +features. -- cgit v1.2.3