summaryrefslogtreecommitdiffstats
path: root/sys/arch/macppc (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Sync the nam2blk entries with the bdevsw table, which is thenaddy2018-01-271-3/+4
| | | | | definitive list of block devices supported on an architecture. ok kettenis@ deraadt@
* <machine/mutex.h> -> <sys/mutex.h>mpi2018-01-221-2/+2
|
* Always grab the KERNEL_LOCK() for !IPL_MPSAFE handlers.mpi2018-01-221-6/+5
| | | | Suggested by kettenis@, ok visa@
* Delete unnecessary <sys/file.h> includesguenther2017-12-301-2/+1
| | | | ok millert@ krw@
* fcntl(F_SETFL) invokes the FIONBIO and FIOASYNC ioctls internally, soguenther2017-12-141-1/+9
| | | | | | | the memory devices (/dev/null, /dev/zero, etc) need to permit them. problem noted, tweak, and testing by jeremy@ ok deraadt@
* In uvm Chuck decided backing store would not be allocated proactivelyderaadt2017-12-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | for blocks re-fetchable from the filesystem. However at reboot time, filesystems are unmounted, and since processes lack backing store they are killed. Since the scheduler is still running, in some cases init is killed... which drops us to ddb [noted by bluhm]. Solution is to convert filesystems to read-only [proposed by kettenis]. The tale follows: sys_reboot() should pass proc * to MD boot() to vfs_shutdown() which completes current IO with vfs_busy VB_WRITE|VB_WAIT, then calls VFS_MOUNT() with MNT_UPDATE | MNT_RDONLY, soon teaching us that *fs_mount() calls a copyin() late... so store the sizes in vfsconflist[] and move the copyin() to sys_mount()... and notice nfs_mount copyin() is size-variant, so kill legacy struct nfs_args3. Next we learn ffs_mount()'s MNT_UPDATE code is sharp and rusty especially wrt softdep, so fix some bugs adn add ~MNT_SOFTDEP to the downgrade. Some vnodes need a little more help, so tie them to &dead_vnops. ffs_mount calling DIOCCACHESYNC is causing a bit of grief still but this issue is seperate and will be dealt with in time. couple hundred reboots by bluhm and myself, advice from guenther and others at the hut
* Enable ne(4) at pcmcia.mpi2017-11-272-2/+4
| | | | Tested by & diff from Donovan Watteau.
* Since rev 1.502 of rc(8) it creates a /bsd.booted hard link. At theflorian2017-11-041-3/+5
| | | | | | | | | | | | | | | | | | | | end of rc we call reorder_kernel which creates a /obsd hard link to the same kernel. In the past obsd was only created when doing a manual make install in the kernel sources. There is no need for two backup hard links during boot, rearange the kernel Makefiles to restore previous behaviour and thus stopping reorder_kernel from scribbling over /obsd. Makes muscle memory of some kernel developers work again: /obsd can serve as a known good kernel; and there was much rejoycing... Discussed at length with benno, rpe, phessler and tb at p2k17. Seems like a good idea to deraadt. OK benno, phessler, rpe, tb
* remove mention of unused MACOBIOVERBOSE and NBUF optionsjsg2017-10-231-2/+1
|
* input files should not be .o; from Scott Chelohaderaadt2017-10-111-2/+2
|
* When option DDB_STRUCTINFO was removed from the kernel, too much frompatrick2017-09-281-1/+12
| | | | | | | | the kernel makefiles was removed which lead to C files not being re- compiled when a dependency changed. This can lead to panics in odd places and generally a broken system. ok deraadt@
* Remove option DDB_STRUCTINFO. Now that ddb(4) is CTF aware, similarmpi2017-09-121-27/+2
| | | | | | functionnalities are available in GENERIC. ok jasper@, deraadt@, guenther@, dlg@
* If you use sys/param.h, you don't need sys/types.hderaadt2017-09-088-16/+8
|
* swap ualea for urngjasper2017-08-281-2/+2
|
* crank to 6.2-betaderaadt2017-08-201-2/+2
|
* Use ctfstrip(1) by default to strip kernels.mpi2017-08-121-2/+2
| | | | ok deraadt@, jasper@
* Initialize the brightness to a valid value if found.anton2017-07-221-2/+4
| | | | ok deraadt@
* Stop automatically regenerating gap.o (and hence linking a new kernel)tb2017-07-181-4/+6
| | | | | | | | | | whenever make is issued. Only do this when there are actual source changes below /sys. This restores the behavior prior to the KARL implementation. Problem noticed and patiently explained by mpi implementation with a lot of help from espie ok mpi, espie, deraadt
* Pass the linker from make environment to makegap.sh. This is (only)visa2017-07-161-2/+2
| | | | | | a partial solution to cross compiling the kernel with KARL. OK deraadt@ a while ago
* put SYSTEM_SWAP_DEP out of its misery, it died in 1997, along with config.oldespie2017-06-291-2/+2
| | | | "go for it" deraadt@
* the illegal instruction is 0x00000000deraadt2017-06-271-3/+2
|
* dull dependency for copying makegap.sh to obj, so that installsderaadt2017-06-251-2/+2
| | | | | | without src and comp work. That is what we've designed for, but since we always have src and comp on our systems it is so easy to slide... problem first noted by rpe.
* Generate a gap.link script, and use that to generate gap.o. On multi-ABIderaadt2017-06-221-23/+14
| | | | | | | | architectures we must also link against a gapdummy.o to repair the ABI of the resulting .o file. Woe is me. Also repair install: target to update the linkkit & hash when a kernel is installed. ok rpe tb mlarkin and tested by others also
* Fix the remaining ';;'s in sys/tom2017-06-221-2/+2
|
* Split early startup code out of locore.S into locore0.S. Adjust linkderaadt2017-06-134-88/+164
| | | | | | | | | | | | | | run so that this locore0.o is always at the start of the executable. But randomize the link order of all other .o files in the kernel, so that their exec/rodata/data/bss segments land all over the place. As a result, the internal layout of every newly build bsd kernel is different from past kernels. Internal relative offsets are not known to an outside attacker. The only known offsets are in the startup code (which will be gone when it is smashed). The bootstrap code unmapping or smashing isn't done yet, and there is some potential for more bits from locore.S to move to locore0.S
* add a dummy ld.script. macppc does not use one of these yet, butderaadt2017-06-131-0/+0
| | | | | infrastructure that is coming requires an architecture to carry such a file.
* Prepare install_extint() for the vector being relative-negative (iederaadt2017-06-131-4/+5
| | | | | | lower in the address space). Previously it could only be higher than... uhm locore.o Discussed with drahn and tom
* make vers.o not depend on gap.o using a trick, because it is piece ofderaadt2017-06-111-2/+2
| | | | | fiction participating only in the linkphase. tricks from rpe and espie
* Use umask 077 instead of cp -p when installing the kernel as root.bluhm2017-06-111-2/+2
| | | | | | Otherwise owner of /bsd could be the build user with permissions inherited from the compile directory. OK deraadt@ tb@
* Create gap.S and gap.o with umask 077. Create lorder and bsd* with umask 007.deraadt2017-06-031-4/+5
| | | | | Prying eyes cannot look at the kernels in the compile directory. ok tb rpe, kernel developers seem unimpacted
* add a BUS_DMA_64BIT flag to bus_dma on all our archs.dlg2017-05-081-1/+2
| | | | | | | | | this is so drivers can advertise that they can handle 64 dma addresses to the platform. it may choose to handle dmamaps differently based on this flag. tweaks and ok tom@ ok kettenis@
* Rename Debugger() into db_enter().mpi2017-04-306-12/+12
| | | | | | | Using a name with the 'db_' prefix makes it invisible from the dynamic profiler. ok deraadt@, kettenis@, visa@
* Fix building profiling kernels by passing the -p flag to config(8)tb2017-03-151-1/+2
| | | | | | | if the kernel's name ends in .PROF. problem reported by jmc via mpi ok mpi
* Do not clear IFF_UP, even in the error path, clearing IFF_RUNNINGmpi2017-03-081-2/+2
| | | | | | | | | is enough. This flag should only be set by the stack, drivers shouldn't mess with it. Discussed with dlg@ and mikeb@, ok mikeb@, stsp@
* crank to 6.1-betaderaadt2017-03-041-2/+2
|
* Switch geteblks()'s size argument from int to size_t. It's called withnatano2017-02-281-3/+3
| | | | | | | unsigned variables as argument in most places anyway. Decrease the chance of signedness/range mismatch issues. ok stefan
* Unbreak 'config -p'.mpi2017-02-101-1/+1
| | | | ok tb@, jca@
* move counting if_opackets next to counting if_obytes in if_enqueue.dlg2017-01-222-6/+2
| | | | | | | this means packets are consistently counted in one place, unlike the many and various ways that drivers thought they should do it. ok mpi@ deraadt@
* Introduce the KEEPKERNELS variable: if this is set either in mk.conf ortb2017-01-221-2/+7
| | | | | | | | | | | | | | the environment, 'make cleandir' does not descend into kernel build directories. Thus, kernel object files survive 'make build' on slower architectures. WARNING: If you set this variable, you run the risk of breaking 'make release': Be sure to run 'make cleandir' from /sys/arch/$(machine)/compile before doing 'make release'. This issue will be addressed shortly. requested by kettenis; ok deraadt
* Fix typo, happend -> happenedjca2016-12-261-2/+2
|
* Harmonize battery state thresholds accross platforms.fcambus2016-12-051-6/+5
| | | | | | Use the same values hardcoded in sys/dev/acpi/acpi.c where possible. OK visa@
* Build kernel with DEBUG=-g by default.mpi2016-11-291-2/+2
| | | | | | | | | | | | | This will allow us to extract type informations from DWARF2 sections. It also makes developer life easier as debug information are now included in every object. Resulting kernels will be stripped using strip(1) instead of ld(1). Kernel build time increases by approximately 10%. However it is still possible to disable this by defining DEBUG="". ok kettenis@, bluhm@, natano@, jasper@, reyk@, deraadt@
* Clean up the kernel Makefile's:natano2016-11-151-16/+4
| | | | | | | | | | | - Remove the 'lint' target. lint has been removed with OpenBSD 5.2. - Remove the 'tags' target. It does nothing of value. - Replace 'clean::' with 'clean:', as requested by espie and millert, and remove files from the 'clean' target, that are never generated. - Don't create a file called 'depend' in 'make depend', but just do nothing instead. ok mpi tb
* Do not create machine@ symlinks in obj as root during includes:, buttb2016-11-061-2/+3
| | | | | | | | | defer their creation to later, so that they are owned by BUILDUSER. This eliminates the last root-owned files in obj/ from 'make build'. In addition, place a MACHINE == hppa test in hppa/stand/Makefile.inc to avoid creating bogus symlinks on all other archs. joint work with & ok natano, "let's try it" deraadt
* Two tweaks for compile/Makefile.inc:natano2016-11-051-3/+2
| | | | | | | | | | | | 1) Replace '.elif !exists(${OBJDIR}/Makefile)' with just '.else'. espie pointed out, that if the file existed, make wouldn't be reading this file, so the check is superflous. Less clutter. 2) Unconditionally define the 'clean' and 'cleandir' targets, also when obj doesn't exist. This changes the behaviour of 'make clean' to be successful (doing nothing) without obj@ or obj/. ok tb millert deraadt
* We don't generate an eddep script for kernel builds nowadays. The lastnatano2016-10-271-2/+2
| | | | | | | reference to eddep in the kernel Makefile I could find is in 4.3BSD, released some 30 years ago. ok tb millert
* make cleandir should skip the version file; ok otto millertderaadt2016-10-241-2/+2
|
* cleandir: target for kernel compile directoriesderaadt2016-10-153-7/+9
| | | | ok natano
* Kernel builds now happen in compile/CONFIG/obj@ -> /usr/obj/... [or ./obj/,deraadt2016-10-148-7/+36
| | | | | | | | | | | | | | | | if srctree is not rooted at /usr/src]. As a result, stock GENERIC & RAMDISK kernels are commited to the tree, to ensure the src tree can be "readonly" during builds, with all writes occuring inside the obj space. config -b options are handled by ../Makefile.inc. The canonical new way to configure one of these kernels is: % cd /sys/arch/amd64/compile/GENERIC.MP % doas make obj % make config % make % doas cp obj/bsd /bsd The build infrastructure will use this new mechanism in a de-escalation way using BUILDUSER. Much help from natano and tb.
* Apply consistency to forever loops with continue and NOTREACHEDtom2016-10-091-2/+3
| | | | Same thought from kettenis@, ok krw@ phessler@ millert@