Age | Commit message (Collapse) | Author |
|
Not used yet but may become useful later.
|
|
Original work by Neil Ashford and dlg@
Feedback from jsg@
ok kettenis@, dlg@
|
|
Use a monotonic clock for timestamping LUNs to avoid problems when the
UTC clock jumps.
ok krw@
|
|
the Raspberry Pi4.
ok patrick@
|
|
|
|
does nothing at all.
The first one spotted as CID 1452976.
Reads good to millert@
ok mpi@
|
|
ok patrick@
|
|
This also adds panel support to rkanxdp(4). Code to hook up simplepanel(4)
is still missing and will come later.
ok patrick@
|
|
"Bump nvme(4) max physio() i/o size to 128K"
|
|
The coverity-related diff breaks sparc64's ability to read the disk.
ok deraadt
|
|
KASSERT(), or has already blown up by dereferencing the
pointer.
Two of the four invocations of ahci_get_pmp_ccb() check for
NULL. Save a couple of bytes by not bothering. Add comments
to the invocations to docuement the assumption.
|
|
printf()'s.
|
|
From Rob Schmersel
|
|
|
|
removal of internal queuing of scsi_xfer's. Put them out of their
misery. Nuke an obsolete comment in passing.
CID 1453357.
|
|
12. PAGE_SHIFT is 12 (a.k.a. PAGE_SIZE == 4096) or more on OpenBSD
architectures. So remove some dead code by unconditionally setting
sc_mps (memory page size) to 1 << PAGE_SHIFT.
CID 1491655.
No functional change.
|
|
sgl (scatter gather list) and prpl (physical region page list) are two
different things in the NVMe world. Only the latter is currently
implemented in nvme(4) so rename sc_max_sgl to sc_max_prpl to reflect
this.
No functional change.
|
|
different things in the NVMe world. Only the latter is currently
implemented in nvme(4) so rename sc_max_sgl to sc_max_prpl to reflect
this.
No functional change.
|
|
driver. The information by the driver is supposed more reliable than
the information which was set up earlier.
ok patrick
|
|
external tool to pre-process the NVRAM, even though it's simple to
do ourselves. This allows easier firmware distribution.
ok kurt@
|
|
|
|
ok patrick@
|
|
No functional change.
|
|
RK3399 SoC.
ok patrick@
|
|
and ffs(16)-1 with the constant results (i.e. 6 and 4). Add comments
to clarify use of these constants. Net result, one less invocation of
ffs(), softc smaller by one u_int, and less potential confusion over
'mps'.
No functional change.
|
|
Nuke the latter and use the former to get the same value.
|
|
|
|
This reduces drops caused by the ifq pressure drop mechanism and hence
increases throughput.
ok tobhe@
|
|
Yet another straightforward ticks-to-milliseconds conversion.
I am honestly unsure what particular driver this file belongs to. It
seems to be related to pcic(4) and/or pcmcia(4) so I've marked this
diff with pcic(4) in the summary line.
No complaints on tech@ after six weeks.
|
|
which amongst other things sets up the link and allows reading
the display's modelines over I2C. Taken from NetBSD and adjusted
to our layers.
ok kettenis@
|
|
|
|
|
|
radiotap header instead of using a fack mbuf in the stack.
OK stsp@
|
|
|
|
tossed it too.
|
|
|
|
Do not include <sys/kthread.h> where it is not needed and stop including
<sys/proc.h> in it.
ok visa@, anton@
|
|
|
|
OK claudio@
|
|
which is not bug free.
OK stsp@
|
|
mbuf which sits on the stack. Similar change was done in iwm(4) some time
ago.
OK stsp@
|
|
as static value of 16 * PAGE_SIZE (siop). But all end up with a max
i/o size of of MAXPHYS or more. So no need for their *_minphys.
|
|
value minphys() uses (MAXPHYS) are pointless since minphys() is always
called after the *_minphys() function.
MAXPHYS (64 * 1024) == 16 * 4096. 4096 is the smallest PAGE_SIZE we
have. So a *_minphys() function that caps the i/o size at N *
PAGE_SIZE where N is > 16 is just wasting cycles.
Nuke adv_minphys (40 * PAGE_SIZE), adw_minphys (254 * PAGE_SIZE),
ahc_minphys (128 * PAGE_SIZE), ahd_minphys (128 * PAGE_SIZE),
ami_minphys (26 * PAGE_SIZE), cac_minphys (65535 (!!!) * 512),
iha_minphsy (32 * PAGE_SIZE), trm_minphys (31 * PAGE_SIZE),
twe_minphys (62 * PAGE_SIZE). uha_minphys (32 * PAGE_SIZE),
|
|
work with nvme.
ok jmatthew
|
|
" ... it's really not necessary" since 128 * PAGE_SIZE will never be
less than MAXPHYS.
|
|
|
|
as (64 * 1024). Reduce confusion by using
MAXPHYS (a.k.a. (64 * 1024)) as other drivers
do.
|
|
nothing at all. MAXPHYS will be applied in minphys() and nothing at
all, well, doesn't do anything.
Also remove any '#define <blah> MAXPHYS' statements used solely to
disguise MAXPHYS in said functions.
|
|
'adw_switch' like all the cool kids do.
|
|
sc_link.adapter at trm_switch directly.
|