Age | Commit message (Collapse) | Author |
|
|
|
way out anyway.
|
|
input and ok mickey.
|
|
|
|
|
|
|
|
|
|
From the Linux tg3 driver.
|
|
|
|
From the LSI Linux MPT driver.
|
|
ok brad
|
|
ok brad@
|
|
mixer_ctrl_t::un.value.num_channels in the case of the
combination of a mono pin and a stereo mixer.
From kent NetBSD
|
|
- unmap the good buffer in wpi_tx_intr
|
|
From kent NetBSD
|
|
|
|
|
|
was not properly reset) -- tested by Jean-Baptiste Campesato
- load the firmware block by block to avoid allocating a large amount of
contiguous memory, which may not be possible at the time the interface
is turned up.
- rename WPI_CONFIG_ASSOCIATED into WPI_STATE_ASSOCIATED
|
|
set the default pin direction depending on the pin's device, not color
- ALC882:
- add usingdac and usingadc
- remove alc882_init_widget() because it has no effect any more
- codec-specific mixer initialization for Realtek ALC882
- fix audio_format allocation for recording
From kent NetBSD
|
|
at least allowing the driver to recognize the codec type.
|
|
* azalia_codec_init_vtbl()
recognize the name of AD1983
* azalia_generic_codec_find_dac()
check validity of a node in a connection list
* introduce MIXER_DELTA, and simplify the code with it
* codec-specific mixer initialization for STAC9220
From kent NetBSD
Tested by a few end-users.
|
|
we read off the hardware and use to configure the driver with are set to
zero, so things dont really work like we want them to.
one of these fields is the pci subsystem id which is something we can fetch
really early in the attach process. so if the subsys is 0 then we go on and
fix up some of the values we get off the "hardware". now we can attach
disks on vmware.
"sneaky" and ok marco@ tested by and ok brad@
|
|
|
|
The SK-NET GENESIS document says reading the SK_ISSR register should stop
generating further interrupts, but it seems there is the possibility
of losing interrupts between reading the SK_ISSR register and determining
which interrupts have been reported. To cope with this situation we
continuously read the SK_ISSR register until there are no interrupts.
However, it seems that the above workaround does not fix all cases.
Add workaround code that tries to protect against false alarms from
the watchdog handler by trying to reclaim pending Tx descriptors
before resetting the hardware.
This should fix occasional watchdog timeouts seen with this driver.
From FreeBSD
|
|
|
|
modem support.
- Print the name of the STAC9220 codec.
From kent NetBSD
ok jason@
|
|
rename them like azalia_mixer_foo() to azalia_generic_mixer_foo()
* enable codec-specific code to hook any mixer operations such
as creating mixer items, or special handling for a specific
item.
* provide a custom mixer table specific to ALC260
* provide a custom mixer table specific to Fujitsu LOOX
From kent NetBSD
ok jason@
|
|
with non-ERP STAs. some bits are missing in net80211 though, so this
code won't be triggered yet.
|
|
From NetBSD
|
|
ok damien@
|
|
|
|
remove a useless define while there.
|
|
requested by deraadt@
|
|
but it seems Jumbo support is broken, so disable Jumbos for now.
issue reported by jolan@
|
|
watchdogd(4), so there's no point in supporting old, unused,
non-generic interfaces.
Tested by < jg , rilk - com>.
The sensors available on the WDT501 model will be supported later using
the sensors framework.
ok mickey markus
|
|
to be mapped in stge_start().
|
|
of B1 to account for the differences with the revision defines used in
OpenBSD's if_bgereg.h vs FreeBSD's.
|
|
|
|
|
|
functional change.
|
|
ok krw@
|
|
|
|
|
|
|
|
- set traffic class (in PCI config space) to 0
- clean up the interrupt handler
- always read/write the INTCTL register with 4 bytes
- before resetting, ensure RUN bit is zero
- zero the BDP regs during reset
- still has a bunch of hacks in it to get it working, but at least
it interrupts correctly on my workstation now.
|
|
- don't start AMRR if we have set a fixed rate
- fix TSF synchronization
- remove a x2 prototype + ;; (pointed out by Jean-Baptiste Campesato)
|
|
|
|
their multiport serial boards (SST series).
ok deraadt@
|
|
This appears to have been due to driver changes and the fact that
the status word seems to not be cleared. linux may have the same bug.
freebsd does clear the status word with and atomic read and clear
ops. we instead do best effort here to check for the interrupt being
ours by reading the status from the status block to a local copy,
then clearing the status word once we enter the interrupt handler
and using the local copy for checking link status
ok jason@
|
|
|