| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
overriden, not just DSDT. However, we do not support this feature yet.
|
|\ |
|
| | |
|
| |
| |
| |
| | |
ap mode 11h channel switch announcements
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Submitted by: "Paul B. Mahol" <onemda@gmail.com>
|
| |
| |
| |
| | |
Submitted by: Hans Petter Selasky
|
| |
| |
| |
| | |
Submitted by: Hans Petter Selasky
|
| |
| |
| |
| | |
Submitted by: Hans Petter Selasky
|
| |
| |
| |
| |
| |
| | |
properly in the CDEV private data.
Submitted by: Hans Petter Selasky
|
| |
| |
| |
| | |
Submitted by: Sylvestre Gallon
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- always maintain byte/mcast/drop stats via drbr
- move #define of IFNET_BUF_RING so that its picked
up by all files in the driver
- conditionalize IFNET_BUF_RING on the FreeBSD_version
bump just after it appeared in the tree.
Sponsored by: Myricom Inc.
|
| |
| |
| |
| |
| |
| |
| | |
when we've not stopped the card. It hangs the system when we touch
the CSR after bwistop.
This fixes the hanging on kldunload.
|
| |
| |
| |
| | |
on amd64 without this.
|
| |
| |
| |
| |
| |
| |
| | |
series POS terminals.
MFC after: 3 days
Submitted by: Marc Balmer <marc at msys.ch>
|
| |
| |
| |
| |
| | |
While I'm here correct description of 88E8070. 88E8070 is Yukon
Extreme and have gigabit PHY.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These controllers use newer descriptor format and the new descriptor
format uses status LE to indicate the status of checksum. Rx
checksummed value used in previous controllers were very cryptic
and I failed to understand how to use them. In addition most
controllers in previous generations had Rx checksum offloading bug.
While I'm here introduce a MSK_FLAG_NORX_CSUM flag to bypass
checking Rx checksum offloading as Yukon FE+ A0 has status LE bug.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
this feature hardware automatically computes TCP/UDP payload
offset. Introduce MSK_FLAG_AUTOTX_CSUM to mark the capability.
Yukon Extreme B0 revision is known to have a silicon for the
feature so disable it. Yukon Extreme B0 still can do Tx checksum
offloading but CPU have to compute TCP/UDP payload offset. To
enable traditional checksum offloading, disable automatic Tx
checksum calculation capability.
Yukon Extreme A0 revision could not use store-and-forward mode for
jumbo frames(silicon bug) so disable Tx checksum offloading for
jumbo frames.
I believe controllers that have MSK_FLAG_AUTOTX_CSUM capability or
new descriptor format do not have Tx checksum offload bug so
disable checksum offloading workaround for for short frames.
Tested by: jhb, Warren Block ( wblock <> wonkity dot com )
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Yukon Extreme uses new descriptor format for TSO and has Tx frame
parser which greatly reduces CPU cycles spent in computing TCP/UDP
payload offset calculation in Tx checksum offloading path. The new
descriptor format also removed TCP/UDP payload computation for TSO
which in turn results in better TSO performance. It seems Yukon
Extreme has a lot of new (unknown) features but only basic
offloading is supported at this time. So far there are two known
issues.
o Sometimes Rx overrun errors happen when pulling data over
gigabit link. Running over 100Mbps seem to ok.
o Ethernet hardware address shows all-zeroed value on 88E8070.
Assigning ethernet address with ifconfig is necessary to make it
work.
Support for Yukon Extreme is not perfect but it would be better
than having a non-working device. Special thanks to jbh who fixed
several bugs of initial patch.
Tested by: jhb, Warren Block ( wblock <> wonkity dot com )
|
| |
| |
| |
| |
| |
| |
| | |
found on Marvell Yukon Ultra, Marvell Yukon Extreme controllers.
While I'm here explicitly issue 'powerup' command for 88E1149 PHY.
Tested by: jhb, Warren Block ( wblock <> wonkity dot com )
|
| |
| |
| |
| | |
register after issuing 'powerup'.
|
| | |
|
| |
| |
| |
| | |
Log supported AHCI controller capabilities.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Each socket upcall is now invoked with the appropriate socket buffer
locked. It is not permissible to call soisconnected() with this lock
held; however, so socket upcalls now return an integer value. The two
possible values are SU_OK and SU_ISCONNECTED. If an upcall returns
SU_ISCONNECTED, then the soisconnected() will be invoked on the
socket after the socket buffer lock is dropped.
- A new API is provided for setting and clearing socket upcalls. The
API consists of soupcall_set() and soupcall_clear().
- To simplify locking, each socket buffer now has a separate upcall.
- When a socket upcall returns SU_ISCONNECTED, the upcall is cleared from
the receive socket buffer automatically. Note that a SO_SND upcall
should never return SU_ISCONNECTED.
- All this means that accept filters should now return SU_ISCONNECTED
instead of calling soisconnected() directly. They also no longer need
to explicitly clear the upcall on the new socket.
- The HTTP accept filter still uses soupcall_set() to manage its internal
state machine, but other accept filters no longer have any explicit
knowlege of socket upcall internals aside from their return value.
- The various RPC client upcalls currently drop the socket buffer lock
while invoking soreceive() as a temporary band-aid. The plan for
the future is to add a new flag to allow soreceive() to be called with
the socket buffer locked.
- The AIO callback for socket I/O is now also invoked with the socket
buffer locked. Previously sowakeup() would drop the socket buffer
lock only to call aio_swake() which immediately re-acquired the socket
buffer lock for the duration of the function call.
Discussed with: rwatson, rmacklem
|
|
|
|
|
|
| |
vnet context.
Approved by: julian (mentor)
|
|
|
|
| |
complain about it when we raise the WARNS level.
|
|
|
|
| |
that it prefixes the output with 'pci<domain>:<bus>:<device>:<function>: '.
|
| |
|
|
|
|
|
|
|
|
| |
using bus_dmamap_load_mbuf_sg() on it. This
prevents data corruption when the mxge MTU is
between 4076 and 8172 on machines with 4KB
pages and MXGE_VIRT_JUMBOS is in use (which it
isn't, in -current or -stable)
|
| |
|
| |
|
|
|
|
| |
PR: bin/96128
|
| |
|
|
|
|
|
| |
the ifdef) since it calls bwi_start_locked, which expects to the lock
to be held...
|
|
|
|
| |
Submitted by: Paul B. Mahol
|
|
|
|
| |
messages. No change to actual code.
|
|
|
|
|
|
|
| |
mic inputs. I have no idea what for it was made that time, but now I have
several reports that it should be removed to make microphones work. If
this quirk is still required for some systems then they should be identified
and specified explicitly.
|
|
|
|
|
| |
Desktop chipsets only for ICH7 series, so mark all ICH7M as ATA_SA150
instead of ATA_SA300.
|
|
|
|
| |
Tested by: Samuel Boivie <samuel at boivie.org>
|
|
|
|
|
|
|
|
| |
Because we only support a single argument to tf_param, use 16 bits for
the pitch and 16 bits for the duration. While there, make the argument
unsigned. There isn't a single param call that needs a signed integer.
Submitted by: danfe (modified)
|
|
|
|
|
|
|
|
| |
part identified as Sunplus Technology Inc. This
happens to sit in a Rosewill RX81U-ES-25A 2.5" SATA
to USB 2.0 external enclosure.
Reviewed by: Hans Petter Selasky
|
|
|
|
| |
Pointy hat to: attilio
|
|
|
|
| |
Tested by: zec
|