| Age | Commit message (Collapse) | Author | Files | Lines |
|
entries to decide if the IFF_ALLMULTI flag should be set, check if there
is at least one real range between them.
This should not change the behavior of any driver but if you encounter
any problem, feel free to revert the offending chunk and ping me about
it.
ok naddy@, dlg@
|
|
ok deraadt@
|
|
entries to decide if the IFF_ALLMULTI flag should be set, check if there
is at least one real range between them.
Tested by naddy@
|
|
|
|
ok naddy@ sthen@
|
|
ok matthew guenther mikeb
|
|
no functional change.
ok sthen@
|
|
fix excessive timeouts and 'Michael mic' errors.
Problem pointed out by vigdis via bugs@
ok dlg@
|
|
from kimberley manning
|
|
from kimberley manning
|
|
from kimberley manning
|
|
|
|
present in this function, but I've been advised to walk away, and it
have been this way forever (and this code is not even enabled in GENERIC
by default anyway)
original bug found by Maxime Villard, thanks.
|
|
"ticks - start > interval" because the latter copes with ticks wrapping.
pointed out by guenther@
|
|
From Pedro Martelletto.
|
|
by passing a start/length in the HIB_INIT op. Then rebase all
hibernate-time block offsets to be relative to the start of that partition.
This simplifies things a lot.
ok mlarkin
|
|
miod@ cannot find two boards using the same media.
With precious punctuation review from guenther@, thanks!
ok deraadt@, henning@
|
|
The relevant code for enabling the HW's RX checksum offload support was checking
for the TX feature flag to know when to enable RX checksum offload but that flag
was removed/disabled with rev 1.140 which resulted in the RX checksum offload support
inadvertently being disabled.
ok naddy@
|
|
and make mfi(4) pass up the necessary information. Adding support for other
RAID controllers is left as an excercise to the reader.
ok deraadt@
|
|
probably due to incorrect programming of the system board ``Diagnostic Control
Register'', for which I do not have documentation yet; commited so as not to
lose this work, since the machine I was testing on has apparently commited
suicide and will no longer POST.
|
|
which is obviously not intended given how they are used in the ar9003 code.
No currently working athn(4) devices are affected by this change.
|
|
Verified by comparing register write traces.
No currently working athn(4) devices are affected by this change.
|
|
wsdisplay softc. Instead, since the knowledge about available fonts lies in
the parent driver itself, introduce a list_font wsdisplay_accessop which
queries a font index, suitable to use within the WSDISPLAYIO_LSFONT ioctl.
With this in place:
- there is no global wsdisplay limit on the number of fonts loaded. Such a
limit will be enforced by the display drivers themselves.
- built-in kernel fonts will now appear in the list of fonts.
Grow a list_font accesop for rasops, which relies upon wsfont_enum(), which
is turned into something useful (and abortable if you do not need to iterate
further). Not used by any rasops driver yet.
|
|
No functional change.
|
|
|
|
|
|
requested character in the font it is using, it suggests a question mark
character, instead of a space, so that the existence of the non-representable
character becomes visible.
Note that this is consistent with pcdisplay which suggests a diamond for
missing glyphs.
|
|
400 and 4300. Limited to PIO mode only for now, until the DMA controller is
tamed. Heavily based upon the MI aic(4) driver.
|
|
An earlier version didn't seem to work on a machine bmercer@
had access to a few months ago but this seems to work
with the onboard Ethernet in an ASUS Z87 board RD Thrush has.
|
|
ported from NetBSD.
Tested on hppa (720) and aviion (4600).
|
|
The dell perc 6/i sets this to zero (meaning bad) when it
decides the battery doesn't have enough capacity for it to
allow write back mode, but doesn't set any of the other flags
to tell us why.
ok dlg@, tested by sthen@
|
|
|
|
it seems to fix the occasional watchdog timeout when using MSI.
tested by many
|
|
while there, fix a few %d into %u
|
|
ok deraadt@
|
|
- the am7990_get() - now lance_get() - is unchanged.
- the interrupt acknowledge logic is unchanged, and will disable interrupts,
then acknowledge all interrupt conditions.
Add ILACC (79900) support (from NetBSD).
Both LANCE (am7990.c) and ILACC (am79900.c) code share as much common code
(lance.c) as possible. This affects all le(4) attachments, but the changes
are mostly mechanical, to split am7990-specific parts from lance-agnostic
parts.
Compile tested on all affected platforms. Tested on alpha, hp300, luna88k,
mvme88k, sparc, sparc64 and vax.
|
|
command byte. This allows at least my USB keyboard to be part of
the console on a Lenovo E20.
ok miod@
|
|
important (and write-only) register state; this will allow this driver to
be used as a console before it attaches, to be used shortly.
|
|
alternative to bcopy since noone uses it.
while there use memcpy instead of bcopy because we know the memory cannot
overlap.
ok henning@ matthew@ mikeb@ deraadt@
|
|
is responsible for the hangs seen by Henning. So put them back.
|
|
don't have to. Just remove these include lines.
Compiled on amd64 i386 sparc64; OK henning@ mikeb@
|
|
ok mpi@
|
|
support (rev 1.98). There is strong evidence that one of these causes hangs
on the Sun ERI as found on a v120.
ok henning@, deraadt@
|
|
variable the message doesn't make much sense.
Reported by Maxime Villard.
|
|
|
|
ok dlg@
|
|
|
|
stops the timeouts, and that DVACT_RESUME unwedges the soft state and
bring the hardware state back to normal operation.
Tested by rpe, thanks a lot!
|
|
machine-independent parts to MI land.
The MI code now allow MD configuration of the various input and output ports,
to allow for proper DCD/RTS/DTR monitoring and control. It will also allow
the second set of baud rates to be used (when possible, i.e. if both ports
can use the same BRG), allowing for 38400 bps mode.
|
|
ok otto
|