Age | Commit message (Collapse) | Author |
|
|
|
ok matthew@ deraadt@
|
|
ok guenther@
|
|
|
|
chip want it one-based.
|
|
|
|
Split inittodr/resettodr code from actual tod routines, to allow for
multiple tod routines in the near future.
Use the mi clock_ymdhms_to_secs and clock_secs_to_ymdhms routines.
|
|
and VME controller are supported; tod chip isn't supported yet (coming soon).
MVME236 memory boards are not supported and won't likely be (unless I get my
hands on one).
MVME181-1 boots multiuser (slowly) with MVME328 SCSI and MVME376 Ethernet
despite only having 8MB of memory onboard.
MVME180 untested; might need tweaking to get MVME SCSI and Ethernet boards
supported.
Many thanks to Matti Nummi for lending me an MVME181 board.
|
|
function pointers for all the board-specific code.
Add a bunch of `struct board' methods to cover most, if not all, of the
`per-board' logic. This allows most of the md drivers to be cleaned up and
no longer need to embed board-specific knowledge.
|
|
No functional change.
|
|
multiple tod routines in the near future.
Use the mi clock_ymdhms_to_secs and clock_secs_to_ymdhms routines.
|
|
Alter the 88200-specific code to enforce cache-inhibited page tables for
extremely old 88200 versions, and to disable write-back caching on systems
where xmem instructions do not behave correctly when applied to write-back
cached addresses.
No change introduced on 88110 systems, as well as most 88100 systems; the
affected systems are 88100 systems with 88100 revision < 10 and/or 88200
revision < 7; that is, only early MVME181 and MVME188 (not 188A) systems.
|
|
to work as soon as cn_tab is initialized. Allows us to correctly printf or
panic early on unrecognized systems. This used to be the case but got lost a
long time ago.
|
|
|
|
do not return from it, for extra fun. The good thing is that the existing
kernel console code logic issueing \n as \r\n works nicely with the regular
BUG output routines, so there was no reason to use this particular BUG routine
in the first place.
|
|
interface name.
|
|
network, using either the on-board interface (on MVME187 and MVME197) or
any MVME376.
While there, add MVME376 support to netboot.
|
|
towards getting Angelfire boards (MVME180/181) running.
|
|
a smarter seek routine which can seek forward and cope with the libsa gzip code
reading the first 4KB of a file upon open, only to discard the buffer because
it assumes we can always seek backwards.
These boot blocks had been broken since the switch to the MI libsa loadfile
code.
Reported for mvme88k by Michael Fritsch, thanks and sorry for taking too long
to fix.
|
|
ok deraadt miod
|
|
"looks good" deraadt@
|
|
to keep definitions our of user space. The MD files now follow a consistant
order -- all namespace intrusion is at the tail can be cleaned up
independently. locore, bootblocks, and libkvm still see enough visibility to
build. Checked on 90% of platforms...
|
|
kernel APR. Return write-back for every design but those involving 88410,
where write through is returned.
Apparently the use of writeback on single-processor kernels using 88410 (197SP,
197DP) has only been working by fat chance, and the last two years of uvm
changes, as well as the switch to ELF (causing kernel rodata to move `up')
exposes silent memory corruption on (88410-size) aliased addresses.
(I am guilty of not using my 197DP board much after making 197LE write-back
capable, as 197LE turned out to be faster and more stable, for I would have
noticed this earlier).
Further thought needs to happen about this. It might be possible to switch to
writeback by default again as long as bus_dma maps things write-through on
88410 designs, and perhaps with a part of the kernel mapped with a write-through
BATC, since BATC have precedence upon page tables. Right now I'm trying to get
a stable release out of the door.
|
|
#$%&#@! MC88410 chip. This will allow design-agonstic m88k-specific code to be
able to tell pure 88110 kernels apart from possible 88110+88410 ones.
|
|
uint64_t write. While there, implement a real wbinv routine instead of invoking
wb, then inv; this avoids unnecessary busswitch register juggling.
|
|
|
|
No functional change.
|
|
|
|
|
|
ok guenther millert kettenis
|
|
therefore I don't mind you rotting in the Attic for eternity (scheduled
to start on the 21st anyway, according to MayaBSD developers).
reminded by deraadt@
|
|
was removed in gcc4
ok miod@
|
|
|
|
|
|
apparently freeze, and in any case fail to load anything; if this happens,
tell the user what to do and return to the BUG (altering the configuration
from tftpboot itself doesn't seem to have any effect, unfortunately).
|
|
kernel (in dev/bugio.c)
|
|
|
|
|
|
|
|
paths are reflexive. It is now possible to fail part-way through a
suspend sequence, and recover along the resume code path.
Split DVACT_SUSPEND by adding a new DVACT_POWERDOWN method is used
after hibernate (and suspend too) to finish the job. Some drivers
must be converted at the same time to use this instead of shutdown hooks
(the others will follow at a later time)
ok kettenis mlarkin
|
|
|
|
cleaned up later.
ok deraadt@
|
|
built with -fno-pie. This gets the hairiest part of PIE out of the way ...
ok deraadt@
|
|
ok miod@
|
|
MI float.h which pulls in and defines the values that are needed from
there, and repair sys/limits.h so that it defines the values it needs
as well (depending on POSIX version, XPG version, etc). guenther has
a more exact selection of that coming for limits.h.
this also fixes a few mistakes for the vax.
reviewed by kettenis and guenther.
|
|
first few printfs (which happen before we have figured out which exact cpu
we are running on). Found the hard way by aoyama@ on luna88k, and we probably
have just been lucky on other platforms.
|
|
|
|
|
|
|
|
whole tlb (32 of 'em), with smarter `tlb probe and update with new pte if tlb
match found' code. This makes the 88110-specific pmap_update() unnecessary, as
updates are no longer aggregated to avoid the number of flushes. This also
makes tlb handling similar between 88100 and 88110, from the pmap's point of
view, so there is no need to use different routines.
No impact on 88100, no user-noticeable performance change on 88100 GENERIC,
slight improvement on 88110 GENERIC.MP.
|