| Age | Commit message (Collapse) | Author |
|---|
|
a race condition existed where after a qec channel reset, accesses to the
MACE would cause an NMI: so wait for the MACE to come out of reset before
accessing.
- add ifmedia support (mainly so I can get at the link status from other code)
- move some of the spl handling around (more correct)
- rewrite qe_mcreset() again so that all it does is set the multicast filter
- use bzero to initialize the buffers and descriptors
- rearrange the MACE setup to conform to the suggestions in the datasheet
|
|
|
|
|
|
|
|
|
|
|
|
from NetBSD.
|
|
others soon. Some of this from NetBSD.
|
|
|
|
laptops; from FreeBSD. No special changes needed here, just the addition of
the EN2242's product ID since it is an ADMtek Centaur chip.
|
|
|
|
|
|
|
|
(some hardware drivers do not support this yet, i.e., vgafb in powerpc);
mickey@ ok
|
|
parts needed for wscons on i386 and alpha.
|
|
console framework. It doesn't provide direct device driver entry points
but makes its functions available via the internal wsdisplay(4) interface.
The pcdisplay driver is indended as a minimal ``catch-all'' driver for
the different kinds of MDA or CGA compatible adapters. It doesn't support
multiple screens, nor colors or font loading.
From NetBSD. Contains routines used by the vga(4) and ega(4) drivers, etc.
This is more MI stuff in prepartion for wscons on i386 and alpha.
|
|
|
|
files could probably be updated even a bit further (they are from mid-summer).
In addition, I've added support for console scrollback, somewhat inspired by
Linux's vgacon driver. Basically, instead of allocating our own buffer and
doing lots of copies, we take advantage of Video RAM and just modify the VGA
display origin register as appropriate. This approach has a few advantages:
simple to implement, no wasted KVM, it's fast, and after a boot you can now
scroll back all the way to the BIOS messages (assuming your msgbuf is of a
typical length :). Disadvantages are that the VRAM buffer is relatively
small (only 32k) and we do not support raster devices through this method.
(thanks to mickey@ for pointing this out).
The code for this is fairly unobtrusive, so should we come up with a better
approach to console scrollback at a later time (i.e., even more platform
independent) it should be easy to revert this.
We're one step further in porting nice features of PCVT over to wscons.
|
|
hooks into the lower-level display driver. The updated vga(4) driver I'm about
to commit has support for this. This is a fairly unobtrusive way to implement
scrollback while maintaining the abstraction of the wscons system.
|
|
the PGUP/PGDN keys.
|
|
|
|
|
|
devices are on the same interrupt).
|
|
(from NetBSD)
|
|
and Linux's pcidevs. This brooktree driver is an unmaintainable mess. Someone
should look into splitting this code up a bit into separate files, as has
already been done in NetBSD and FreeBSD.
|
|
anywhere quite yet, but useful to have these files in the tree while we work
towards wscons for i386 and alpha.
|
|
NetBSD. This will ease the pain when we bring in the pckbc MI keyboard
driver to be used for wscons/i386 and wscons/alpha.
|
|
|
|
- Allow it to compile with option WSDISPLAY_COMPAT_RAWKBD.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
bus interface was not previously implemented. This functionality is
required for the latest USB changes.
The bus_space_barrier does not perform any operation with this change,
it expects that the device mappings will be performed with the Guard
bit set which then should not require this forced sync.
|
|
This change is more portable, redefine the macros to use the host
letoh32/letoh16 instead of using possibly less efficient bswap routines.
|
|
|
|
Note that you have to recompile ipsecadm and isakmpd if you use a new
kernel.
|
|
make sure to check scoped address right on PMTUD.
sync with kame.
|
|
(NOTE: only root can do it)
|
|
traced proc. The vnode is in the proc and all functions need the proc.
|
|
|
|
|
|
|
|
fails.. it's still ENOMEM.
|
|
2.7 through the released 2.8.
As NetBSD describes the problem:
DMA failure still arise when AdvanSys U[2]W host adapters
are used in conjunction with Intel 82443BX Host
Bridge/Controller (rev. 0x03).
With a correct sg_cnt, scatter/gather lists with >1 element
no longer reference random(?) memory. Now the mystery
is why this didn't cause more problems on other chipsets.
Installs of 2.7 and 2.8 to a drive on an adw bus now work even
if the motherboard uses the 82443BX.
So many problems from one character ...
|
|
|
