| Age | Commit message (Collapse) | Author |
|---|
|
plus cast to vaddr_t where necassary
from Miod's todo list
ok miod@
|
|
|
|
|
|
like all drivers should
ok miod
|
|
of the console device attachment, and to be able to work on system where there
are more than one dz device of the same type, one of it being the console one.
This also allows a different register layout than the dz@ibus one to be used
for the dz console device.
|
|
transmitter. On machines with glass console for which we do not have
a driver yet, and fall back to serial console, the PROM might not have
enabled it.
|
|
macro and related function pointers.
|
|
prints it. These should be the last offenders.
|
|
Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.
OK deraadt@
|
|
the hp300 related ones currently in use. CN_NORMAL becomes CN_LOWPRI,
CN_INTERNAL becomes CN_MIDPRI and CN_REMOTE becomes CN_HIGHPRI.
ok miod@
|
|
prompted by krw@
|
|
panic (for you ichc fans out there), disable the wscons console and force a
console device reselection, which ends up in picking a serial console.
This should not happen, but just in case, it's a less rude behaviour.
|
|
|
|
|
|
only, should work on model 76 (KA43) as well.
|
|
option boards.
|
|
obvious.
|
|
|
|
the nvram settings, as already done on KA46 (VS4k/6x); from Hans Rosenfeld
on port-vax@netbsd.
|
|
in strategy(), and were reusing it in start().
I first considered introducing a b_rawblkno field in struct buf, as has been
done in NetBSD, to stop this abuse.
However, it does not cost more to simply move the device-specific
``was-b_cylinder'' computation to the start() routine. Plus we get type fixes
(daddr64_t) for free, although this does not really matter for these
pedro-sized devices. Thus we do not need to grow struct buf for these
devices which really ought to live in your Attic (and my machineroom, of
course).
hp300 HP-IB tested, vax mfm not, but the logic is the same.
|
|
cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
|
|
|
|
size which is the REAL DISK SIZE. always. if a driver fails to set
this right, please fix it. agreed with otto and krw
|
|
|
|
type of all variables to daddr64_t. this includes the APIs for XXsize()
and XXdump(), all range checks inside bio drivers, internal variables
for disklabel handling, and even uvm's swap offsets. re-read numerous
times by otto, miod, krw, thib to look for errors
|
|
to size. tested on almost all machines, double checked by miod and krw
next comes the type handling surrounding these values
|
|
need the debug info uncomment the printf's you need. Crude but
effective way to suppress 'no disklabel' errors that pop up at the
most innconvenient times to frighten users. More elegant method,
DPRINTF-like constructs or something, later.
"Yay!" marco@ ok deraadt@
|
|
doing nothing and the mi code does not use it anymore anyway. No functional
change.
|
|
waste of 128KB of kvm.
|
|
existing alloc_attr function. This allows rasops_unpack_attr to be kept
private to rasops, yet available to the screen drivers.
|
|
driver to be able to tell how many wscons screens to attach to it,
instead of WSDISPLAY_DEFAULTSCREENS which is a global setting.
|
|
ok miod@ marco@ deraadt@
|
|
|
|
enable it in GENERIC and RAMDISK.
Completely untested due to lack of hardware (both my VS3100 are dual-SCSI),
but it hopefully can't hurt.
|
|
(it would only appear when booting after an UNJAM).
|
|
again.
|
|
|
|
|
|
|
|
- check for error bits in descriptors, and count and report errors
accordingly; make sure we do not pass up known-to-be-bad packets up the
receive path.
- check for various error conditions which would cause the transmit process
to go to suspended state, and recover from them, before the timeout expires.
- finally, on the VXT2000, the transmit process for some reason will reset
its ring position to the beginning of the ring every time it completes a
transmission burst, while we don't, so play with the head of ring register
behind its back. This makes my VXT2000+ (net)boot multiuser.
Tested on VXT2000 (ze@vxtbus), KA49 (ze@vsbus) and KA53 (ze@ibus); ok deraadt@
|
|
console works on color model, serial console works, ethernet attaches but
does not work correctly yet.
|
|
|
|
|
|
|
|
|
|
by aanriot@
|
|
burner routine, and do the colormap updates during vertical retrace, instead
of using a fixed delay.
|
|
|
|
smg forced to attach.
|
|
adapted from X11 via hp300.
|
