| Age | Commit message (Collapse) | Author | Files | Lines |
|
unused interrupts when a chatty peripheral is connected but is not
used.
|
|
OK mikeb@
|
|
than other Delta cards.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
allocation is clearly spelled out as ptr = malloc(sizeof(*ptr), ...)
|
|
|
|
|
|
|
|
hardware rx mtu always gets set to the maximum supported value we will hit
it for every received packet. Instead, use a larger mbuf cluster size on
strict alignment architectures such that we can always m_adj to make sure the
packets are properly aligned. This wastes some memory but simplifies things
considerably. Hopefully we can reduce the spillage in the near future by
taking advantage of recent improvements in the pool code.
ok mpi@, mikeb@, dlg@
|
|
|
|
|
|
|
|
for the pin configuration as well.
From Dmitry Alenichev. ok mlarkin@
|
|
ok stsp@
|
|
|
|
ok stsp@
|
|
|
|
|
|
|
|
|
|
|
|
the kernel lock.
ok mpi@, dlg@
|
|
|
|
This version also makes sure writes are properly aligned, preventing
the panics seen with the previous incarnation of this change.
Fixes battery status passthrough in vmware, brightness keys on my x220
and who knows what else.
ok mlarkin@, deraadt@
|
|
docks.
ok jsg@
|
|
7 years (for some parts, 9 years), and was only ever referenced in i386
anyway.
ok jsg@, matthieu@, armani@
|
|
use the constants where needed.
ok jsing@
|
|
pckbc0: unable to establish interrupt for irq 12pckbd0 at pckbc0 (kbd slot)
ok miod@
|
|
ST-506 support. Remove redundant 'precomp' variables/fields and rename
remaining few to 'features' to be consistant with the rest of the code.
Consensus that no ST-506 disks (requiring ISA cards, <120MB, usually
rife with bad sectors that can't be worked around) are still running
OpenBSD.
|
|
initialized yet.
|
|
instead of one per packet.
seems to let me send packets a little faster.
|
|
this removes the myx_buf structure and uses myx_slot instead. theyre
the same expcet slots dont have list entry structures, so theyre
smaller.
this cuts out four mutex ops per packet out of the tx handling.
just have to get rid of the atomic op per packet in myx_start now.
|
|
this lets me get rid of the locking around the refilling of the rx ring.
the timeout only runs refill if the rx ring is empty. we know rxeof
wont try and refill it in that situation because there's no packets
on the ring so we wont get interrupts for it. therefore we dont
need to lock between the timeout and rxeof cos they cant run at the
same time.
|
|
originally there were two mutex protected lists for rx packets, a
list of free packets, and a list of packets that were on the ring.
filling the ring popped packets off the free list, attached an mbuf
and dmamapped it, and pushed it onto the list of active packets.
the hw fills packets in order, so on rx completion we'd pop packets
the active list, unmap the mbuf and shove it up the stack before
putting the packet on the free list.
the problem with the lists is that every rx ring operation resulted
in two mutex ops. so 4 mutex ops per packet after you do both fill
and rxeof.
this replaces the mutexed lists with rings that shadow the hardware
rings. filling the rx ring pushes a producer index along, while
rxeof chases it with a consumer. because we know only one thing can
do either of those tasks at a time, we can get away with not using
atomic ops for them.
there's more to be done, but this is a good first step.
|
|
it to 0 immediately after a bzero() of the entire label. Nor in
swapping endianness since nobody looks at it. Don't touch the actual
field in disklabel. Yet.
ok deraadt@ as part of larger diff that needs splitting up.
|
|
|
|
one leak reported by Maxime Villard
initial patch from Christian Schulte (with spelling corrections in comments)
second leak corrected by myself
ok kettenis@
|
|
no binary update.
|
|
PAGE_SIZE boundaries. This is required to enforce proper separation of
sections when adding page protections (coming shortly).
This was in snaps before release with no reported side effects.
ok deraadt@
|
|
Pointed out by patrick keshishian <pkeshish at gmail.com>, thanks.
|
|
with no benefit.
ok millert, "correct" deraadt
|
|
'unknown command' dmesg lines for TEMPer devices and a
possible type command loop for unsupported TEMPerHUM devices,
moreover, 2 whitespace fixes while here
tested by myself and frederic cambus
ok mpi@
|
|
Add a workaround for a hardware bug were receiving of packets would stop
until the battery of the laptop was removed. The problem could be
triggered if the LAN cable was plugged in after the PHY had already been
initialized.
The workaround is already present in FreeBSD (e1000_ich8lan.c:
e1000_lv_jumbo_workaround_ich8lan()) and Linux. The commit messages of
b20a7744 and da1e2046 in Linux have some more details.
Found and ported from FreeBSD by Valentin Dornauer.
Tested by many.
ok deraadt@
|
|
problem reported by patrick keshishian (pkeshish (at) gmail.com)
based on diff from mlarkin@, ok mlarkin@ deraadt@
|