summaryrefslogtreecommitdiff
path: root/share
AgeCommit message (Collapse)Author
2022-02-03Delete unused/obsolete M_* type values.Philip Guenther
ok miod@ mpi@
2022-01-31add kstat_remove to NAME and CONTEXT; ok dlgJason McIntyre
2022-01-31+kstat_destroyDavid Gwynne
2022-01-27cad(4): Mention PolarFire SoC.Visa Hankala
2022-01-21document show-listMarc Espie
2022-01-19Mention more controllers that provide sdmmc(4) bus.Visa Hankala
Initial diff from and OK jmc@
2022-01-18Add cdsdhc(4), a driver for the Cadence SD/SDIO/eMMC host controller.Visa Hankala
Tested on a PolarFire SoC.
2022-01-16initialies -> initializesJonathan Gray
ok visa@
2022-01-16stoeplizt -> stoeplitzJonathan Gray
2022-01-14get the list of things in the full identifier right.David Gwynne
2022-01-13fix the -width argument;Jason McIntyre
2022-01-13Tedu support for the -xsh4.2 argument to the mdoc(7) .St macroIngo Schwarze
because all of the following hold: * It is an alias for a part of an ancient standard that is no longer important. * To refer to that old standard, -xpg4.2 is readily available and portable. * It is unused in OpenBSD, FreeBSD, and NetBSD. * Groff never supported it. I agreed with G. Branden Robinson that deleting this from mandoc is preferable to adding it to groff.
2022-01-12In one of the examples, the tbl(7) source code displayedIngo Schwarze
contains a backslash that needs to be escaped, and the missing escaping resulted in very misleading formatting. Documentation bug found due to a question from Ted Bullock <tbullock at comlore dot com>.
2022-01-10fix SEE ALSO;Jason McIntyre
2022-01-10speelingDavid Gwynne
2022-01-10this should be most of the necessary info for this driver.David Gwynne
2022-01-10add a bit more.David Gwynne
2022-01-10tweak slightlyDavid Gwynne
2022-01-10aplsmc(4)Mark Kettenis
2022-01-10hang some flesh off the bones that jsg provided.David Gwynne
2022-01-10mark up the ioctl requests with DvDavid Gwynne
2022-01-10initial kstat.4Jonathan Gray
ok dlg@
2022-01-09do not call ranlib -t anymore because it does nothing except wasting time;Robert Nagy
ok jca@, millert@
2022-01-08Use ${.ALLSRC:M*.y} instead of ${.IMPSRC} as the input file for yacc,Patrick Wildt
to fix a bug where ${.IMPSRC} (aka $<) is used in a context where it is not neccessarily defined by OpenBSD make. This would sometime show up trying to build libpcap with the following error message: Using $< in a non-suffix rule context is a GNUmake idiom (<bsd.dep.mk>:47) The issue is with the rule for the grammar.h file that is generated by yacc from grammar.c. You can easily reproduce the bug with the following steps: - build libpcap from scratch: cd src/lib/libpcap && make clean all - remove the generated grammar.h file: rm obj*/grammar.h - build libpcap again (incremental build): make In normal builds this does not trigger as grammar.h is implicitly generated by the rule for grammar.c and when make checks for dependencies it simply finds grammar.h uptodate. However, incremental or parallel builds might decide to make grammar.h from grammar.y. Now, why is this only a problem for grammar.h but not for grammar.c? The answer to this question is burried deeply in OpenBSD's mk files. The snippet in bsd.dep.mk that triggers the error is a single rule statement that generates foo.c and foo.h from foo.y with a call to yacc -d. The rule is generated with a loop, i.e. it is not a prefix rule. However, a prefix rule context is required for the use of ${.IMPSRC} aka $<. For the .c file such a prefix rule is provided by bsd.sys.mk and this rule is in scope when make evaluates the yacc rule. However, for .h file generation from a .y file there is no such prefix rule defined in any of the Makefiles. Even if it were the .h suffix is missing from .SUFFIXES and the rule would not be considered. The obvious way to fix this would be to use $f instead of ${.IMPSRC}. However, this does not work as $f is then missing the path prefix and yacc won't find it if an obj directory is used. This is probably the reason for the use of ${.IMPSRC} in the first place. Committing on behalf of ehrhardt@ "I like the diff" deraadt@ ok guenther@
2022-01-07regenJonathan Gray
2022-01-07mention radeondrm on riscv64Jonathan Gray
2022-01-05adjust Xr for fw_update to section 8;Jason McIntyre
ok afresh sthen deraadt
2022-01-05formatting nit, noticed by jmc@, thx!Marc Espie
2022-01-05document -mMarc Espie
2022-01-05Add mpfclock(4), a driver for the PolarFire SoC MSS clock controller.Visa Hankala
OK kettenis@
2022-01-04Document ruby31 FLAVORJeremy Evans
2022-01-04- add LDAPJason McIntyre
- capitalise RADIUS when referring to the protocol - remove tis from raf czlonka ok sthen ajacoutot
2022-01-03the prism54 domain is long abandonedJonathan Gray
don't give any traffic to whoever registered it afterwards ok claudio@ stsp@
2022-01-02Mac -> MACJonathan Gray
2022-01-01Identifiier -> IdentifierJonathan Gray
2022-01-01eascape -> escapeJonathan Gray
2022-01-01approciate -> appropriateJonathan Gray
2021-12-30Sync rcexec with reality.Antoine Jacoutot
2021-12-30minor tweakAnton Lindqvist
2021-12-29Mention attachment and reference to acpi(4).Patrick Wildt
2021-12-26make 'set skip on ...' in pf.conf dynamicAlexandr Nedvedicky
This is an old issue in pf(4): whenever new interface appears in IP stack, we must reload pf.conf to apply 'set skip on ...' to newly plumbed network interfaces. Time has come to fix it. The idea is to also create pfi_kif for interfaces, which are referred by 'set skip on ...'. Such pfi_kif instances are created/destroyed by pfi_set_flags()/pfi_clear_flags(). claudio@ dragged my attention to this in Gouveia. Also his feedback helped me to put change into shape. OK claudio@
2021-12-24add mtw(4);Jason McIntyre
2021-12-24use -nosplit for AUTHORS;Jason McIntyre
2021-12-24iic.4: add apliic to the master listJason McIntyre
apliic.4: add arch to Dt
2021-12-24Add a manual page for mtw(4).hastings
ok stsp@
2021-12-24apliic(4)Patrick Wildt
2021-12-21Multiply the number of states in the example adaptive timeout calculationJonathan Matthew
by 10 so it works with the numbers in the config, which were previously multiplied. ok dlg@
2021-12-19aplmbox(4)Mark Kettenis
2021-12-16arm64 can boot from softraid too; ok patrickT.J. Townsend
2021-12-16Attach com over acpi on amd64. Some hardware uses a different interruptAnton Lindqvist
assignment compared to the the legacy one supported by com over isa. This causes the console to halt once userland takes over as no interrupts are received. The actual address and irq can be read from ACPI, kettenis@ already added support for arm64 which paved the way for amd64. Some consoles that previously attached over isa are now expected to attach over acpi. Thanks to patrick@ for testing on arm64. ok kettenis@