summaryrefslogtreecommitdiffstats
path: root/sys/arch/macppc (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Use a consistant idiom/format when declaring scsi_adapter structureskrw2020-01-231-2/+2
| | | | | | | | | | | in drivers. Terse one liners, NULLs instead of 0's, explicitly specify all members, etc. Nuke #ifdef notyet blocks related to the scsi_adapter in aic. No intentional functional change. ok tedu@
* wire up pppac(4) to some majors on each arch.dlg2020-01-231-1/+2
| | | | | | | | i was lazy and just put them at the end of the existing set. fyi, i think major 51 is free on all archs if anyone is looking for another one. ok claudio@
* Import dt(4) a driver and framework for Dynamic Profiling.mpi2020-01-211-2/+3
| | | | | | | | | | | The design is fairly simple: events, in the form of descriptors on a ring, are being produced in any kernel context and being consumed by a userland process reading /dev/dt. Code and hooks are all guarded under '#if NDT > 0' so this commit shouldn't introduce any change as long as dt(4) is disable in GENERIC. ok kettenis@, visa@, jasper@, deraadt@
* remove unfinished macppc esp driver.tedu2020-01-213-470/+2
| | | | ok deraadt krw
* xlights(4): timeout_add(9) -> timeout_add_msec(9)cheloha2020-01-101-2/+2
| | | | | | | There are no units noted here, but macppc is a 100hz platform so it's safe to just assume 2500 milliseconds here. ok jsg@
* Use C99 designated initializers with struct filterops. In addition,visa2019-12-311-3/+7
| | | | | | make the structs const so that the data are put in .rodata. OK mpi@, deraadt@, anton@, bluhm@
* The boot loader allows to inspect memory with the hexdump command.bluhm2019-12-231-2/+7
| | | | | Document the new feature in boot(8) man page. OK jmc@ deraadt@
* Add fido(4), a HID driver for FIDO/U2F security keysreyk2019-12-172-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | While FIDO/U2F keys were already supported by the generic uhid(4) driver, this driver adds the first step to tighten the security of FIDO/U2F access. Specifically, users don't need read/write access to all USB/HID devices anymore and the driver also improves integration with pledge(2) and unveil(2): It is pledge-friendly because it doesn't require any ioctls to discover the device and unveil-friendly because it uses a single /dev/fido/* directory for its device nodes. It also allows to support FIDO/U2F in firefox without further weakening the "sandbox" of the browser. Firefox does not have a proper privsep design and many operations, such as U2F access, are handled directly by the main process. This means that the browser's "fat" main process needs direct read/write access to all USB HID devices, at least on other operating systems. With fido(4) we can support security keys in Firefox under OpenBSD without such a compromise. With this change, libfido2 stops using the ioctl to query the device vendor/product and just assumes "OpenBSD" "fido(4)" instead. The ioctl is still supported but there was no benefit in obtaining the vendor product or name; it also allows to use libfido2 under pledge. With feedback from deraadt@ and many others OK kettenis@ djm@ and jmc@ for the manpage bits
* Remove clause #3 from mrg@NetBSD license.mpi2019-12-051-3/+1
| | | | | | | In May 29 2008, Matthew R. Green removed it in NetBSD: github.com/IIJ-NetBSD/netbsd-src/commit/7ea20401d535da9996394136ef ok deraadt@
* Implement a hexdump command in the boot loader. This helps tobluhm2019-11-282-3/+4
| | | | | | inspect the memory layout that the firmware has created. It is especially useful for UEFI debugging. OK deraadt@ kettenis@
* The compiler -pg option implies -fno-ret-protector, as we want to disableguenther2019-11-071-2/+2
| | | | | | | | | | | retguard and similar when profiling. However, that missed all the .S files, as ${PROF} wasn't added when ${NORMAL_S} was converted from direct invocation of ${AS} to instead use ${CC}. Similarly, mcount.o still had retguards as it cannot be built with -pg. So: pass ${PROF} when compiling .S files, and compile "no profiling" files with -fno-ret-protector on archs with retguard. feedback and ok mpi@ mortimer@
* Use arc4 to bit-spread the 512-byte random buffer over the .openbsd.randomdataderaadt2019-10-292-4/+4
| | | | | | | | | section, which has grown a fair bit with the introduction of retguard. Mortimer discovered the repeated 512-byte sequence as retguard keys, and this resolves the issue. (Chacha does not fit on the media, so 1.5K early drop RC4 is hopefully sufficient in our KARL link universe) Version crank the bootblocks. sysupgrade -s will install new bootblocks. ok djm mortimer
* macppc: mediabay(4), smu(4), xlights(4): tsleep(9) -> tsleep_nsec(9)cheloha2019-10-084-11/+11
| | | | | | | | | This diff completely converts sys/arch/macppc to *sleep_nsec(9). Also convert dev/thermal.c while we're down here. Unsure what that file's driver's name is, if any. ok kn@ visa@
* Remove DST/TIMEZONE options(4) from kernel configs; ok jca@ deraadt@cheloha2019-09-041-3/+1
|
* Add clang support.kettenis2019-09-031-6/+11
|
* a sprinkling of function ansificationderaadt2019-09-0311-46/+43
|
* only need one start: label; ok kettenisderaadt2019-09-032-4/+3
|
* delete incorrect casts, and a bit if ansi functions; ok jcsderaadt2019-09-031-6/+5
|
* Use cmplw mnemonic instead of cmpl with only 3 operands. Make clang happy.kettenis2019-09-031-4/+4
| | | | ok deraadt@
* Replace empty body of while loop with continue statement.kettenis2019-09-031-2/+2
| | | | ok deraadt@
* ansify functionsderaadt2019-09-031-54/+22
| | | | ok jsg
* correct indent that triggered clang to freak out; with jsg.deraadt2019-09-031-3/+4
|
* Various fixes to make clang happy.kettenis2019-09-029-23/+46
| | | | ok deraadt@
* sysctl(2): add kern.utc_offset: successor to the DST/TIMEZONE options(4)cheloha2019-08-211-12/+4
| | | | | | | | | | | | | | | | | | | | | The DST and TIMEZONE options(4) are incompatible with KARL, so we need some other way to compensate for an RTC running with a known offset. Enter kern.utc_offset, an offset in minutes East of UTC. TIMEZONE has always been minutes West, but this is inconsistent with how everyone else talks about timezones, hence the flip. TIMEZONE has the advantage of being compiled into the binary. Our new sysctl(2) has no such luck, so it needs to be set as early as possible in boot, from sysctl.conf(5), so we can correct the kernel clock from the RTC's local time to UTC before daemons like ntpd(8) and cron(8) start. To encourage this, kern.utc_offset is made immutable after the securelevel(7) is raised to 1. Prompted by yasuoka@. Discussed with deraadt@, kettenis@, yasuoka@. Additional testing by yasuoka@. ok deraadt@, yasuoka@
* move to 6.6-betaderaadt2019-08-101-2/+2
|
* crank version, following fchmod changederaadt2019-08-041-3/+3
|
* In the bootblocks, after discovering and opening /bsd.upgrade, fchmod -xderaadt2019-08-032-4/+4
| | | | | | | | | | | | | | | | so the file cannot be re-executed upon the next boot. This provides a stronger one-shot-upgrade model than the upgrade script's rm /bsd.upgrade. Now various forms of upgrade failure will reboot into /bsd, which is probably more recoverable. Performing fchmod -x depends on (1) use of MI boot.c (not alpha/macppc/sparc64/sgi/octeon) and (2) "can write blocks" functionality in the IO layer. Most architectures have this support now. Two diagnostics "fchmod a-x %s: failed" and "/bsd.upgrade is not u+x" will remain in the tree while refinements happen for some of the laggard architectures. based upon a discussion florian tested in snapshots for more than a week without any complaints
* Get rid of `ddb_is_active' instead use `db_active'.mpi2019-07-201-7/+3
| | | | | | From Christian Ludwig <christian_ludwig at genua dot de> ok visa@
* Further improve the filesystem stability of kernel installation by KARL.deraadt2019-06-211-3/+2
| | | | | | | Use install -F to instead of cp, for fsync(2). Coupled with the new sync(8) in the reorder_kernel script, the window for a incomplete /bsd file on-disk due to a crash has now shrunk substantially. Discussion with kettenis, millert and tedu
* Enable ucrcom(4) on all architectures that have uslcom(4).kettenis2019-05-081-1/+3
| | | | ok deraadt@
* libsa's memcpy() is actually memmove(). make a proper memmove(), and givederaadt2019-04-202-4/+4
| | | | memcpy() correct behaviour. This also brings the bcopy() macro into line.
* Instead of using COPTS=-Oz (and similar) in make environment to forcederaadt2019-04-141-1/+2
| | | | | tightly-built ramdisk kernels, set the option in per-arch Makefile.inc based upon SMALL_KERNEL
* Update shared drm code, inteldrm(4) and radeondrm(4) from linux 4.4 tojsg2019-04-141-2/+4
| | | | | | | | | | | | | | | | | | | linux 4.19.34. Adds support for more Intel hardware: Broxton/Apollo Lake (was is_preliminary in 4.4) Amber Lake (another Kaby Lake refresh) Gemini Lake Coffee Lake Whiskey Lake Cannon Lake (though no hardware with Intel graphics ever shipped) Ice Lake (alpha support, hardware not released) This does not add support for new radeon hardware on the AMD side as newer radeons have a different kernel driver (amdgpu). Thanks to the OpenBSD Foundation for sponsoring this work, kettenis@ for helping and a bunch of other developers for testing.
* change marks[] array to uint64_t, so the code can track full 64-bitderaadt2019-04-101-2/+2
| | | | | details from the ELF header instead of faking it. Proposal from mlarkin, tested on most architectures already
* fast track ddb> reboot command to skip anything which might panic again.tedu2019-04-011-1/+5
| | | | ok deraadt
* umbg now supports DCF600USB as well; adjust comment. from weerd@sthen2019-03-221-2/+2
|
* crank to 6.5-betaderaadt2019-02-261-2/+2
|
* flense more trailing whitespacephessler2019-01-221-5/+5
|
* remove trailing whitespace in the Laptop Package part of the license text.phessler2019-01-221-4/+4
| | | | no words or punctation were modified.
* markup boot prompt commands using Ic, not Nm; ok jmc@anton2019-01-021-16/+16
|
* Enable USB bwfm(4) on macppc RAMDISK as well, matching GENERIC.stsp2018-09-221-1/+2
| | | | Passes 'make release' build.
* Enable bwfm(4) in GENERIC on macppc.stsp2018-09-211-1/+2
| | | | Tested by Christian Hammerschmidt.
* Enable uscom(4) where uslcom(4) is already present.mpi2018-08-221-1/+3
| | | | Based on a submisison from Jan Klemkow.
* crank to 6.4-betaderaadt2018-08-101-2/+2
|
* Move from sendsig() to its callers the initsiginfo() calls andguenther2018-07-101-4/+3
| | | | | | | | instead of passing sendsig() the code+type+val, pass a siginfo_t* to copy from. Eliminate the indirection through struct emul for sendsig(); we no longer have a SunOS4-compat version of sendsig() ok deraadt@
* Implement MAP_STACK option for mmap(). Synchronous faults (pagefault andderaadt2018-04-121-3/+3
| | | | | | | | | | | | | | syscall) confirm the stack register points at MAP_STACK memory, otherwise SIGSEGV is delivered. sigaltstack() and pthread_attr_setstack() are modified to create a MAP_STACK sub-region which satisfies alignment requirements. Observe that MAP_STACK can only be set/cleared by mmap(), which zeroes the contents of the region -- there is no mprotect() equivalent operation, so there is no MAP_STACK-adding gadget. This opportunistic software-emulation of a stack protection bit makes stack-pivot operations during ROPchain fragile (kind of like removing a tool from the toolbox). original discussion with tedu, uvm work by stefan, testing by mortimer ok kettenis
* move to 6.3-betaderaadt2018-02-281-2/+2
|
* Remove almost unused `flags' argument of suser().mpi2018-02-191-2/+2
| | | | | | | The account flag `ASU' will no longer be set but that makes suser() mpsafe since it no longer mess with a per-process field. No objection from millert@, ok tedu@, bluhm@
* prune files.* entries that refer to files not in treejsg2018-02-142-9/+2
| | | | ok krw@ mpi@
* Check for the existence of /bsd before trying to back it up to /obsd.tb2018-02-091-2/+2
| | | | | | Fixes 'make install' when /bsd is not present for some reason. ok rob florian, "fine with me" deraadt
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.