r331180 delphij March 19, 2018, 5:49 a.m.
MFC after:	2 weeks
r331153 mjg March 19, 2018, 12:25 a.m.
r331146 oshogbo March 18, 2018, 7:50 p.m.
We don't modified it in this function.
r331141 ian March 18, 2018, 6:58 p.m.
about the chip including the erase block size at attach time.

Also add myself to the copyrights since at this point svn blame would point
to me as the culprit for much of this.
r331140 imp March 18, 2018, 6:50 p.m.
creating them. Move them under the if after the all: target.  They are
just defines, so it doesn't really matter where we have them.

MFC After: 3 days
r331139 ian March 18, 2018, 6:37 p.m.
have these flags set in the ident table, but there was no code to support
using the smaller erase sizes.
r331138 ian March 18, 2018, 5:47 p.m.
status at all call points.  Combine the get_status and wait_for_ready
routines, since waiting for ready is the only reason to ever get status.
r331137 oshogbo March 18, 2018, 5:27 p.m.
I broke it in r331120.
r331136 ian March 18, 2018, 5:25 p.m.
all over the place.  Also pass the softc as the arg to all the internal
functions instead of passing a device_t and calling device_get_softc() in
each function.
r331135 markj March 18, 2018, 5:03 p.m.
Some of mmap(2)'s arguments are 64 bits wide.

MFC after:	3 days
r331134 markj March 18, 2018, 5:01 p.m.
Reported by:	Coverity, via cem
MFC after:	3 days
r331132 ian March 18, 2018, 4:52 p.m.
before starting them.

Using the wait-before logic would make sense if there was useful time-
consuming work that could be done between the end of one write and the
beginning of the next, but it also requires doing the wait-for-ready before
reading, because a prior write or erase could still be in progress.  Reading
is the far more common case, so adding a whole extra bus transaction to
check for ready before each read would soak up any small gains that might be
had from doing async writes.
r331131 markj March 18, 2018, 4:49 p.m.
Such pages are re-enqueued at the end of the fault handler, preserving
LRU. Rather than performing two separate operations per fault, simply
requeue the page at the end of the fault (or bump its activation count
if it resides in PQ_ACTIVE, avoiding the page queue lock entirely).
This elides some page lock and page queue lock operations in common
cases, e.g., CoW faults.

Note that we must still dequeue the source page for "optimized" CoW
faults since the page may not remain enqueued while it is moved to
another object.

Reviewed by:	alc, kib
Tested by:	pho
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D14625
r331130 markj March 18, 2018, 4:40 p.m.
In many cases the page is not enqueued so the change will have no
effect. However, the change is needed to support an optimization in
the fault handler and in some cases (sendfile, the buffer cache) it
was being emulated by the caller anyway.

Reviewed by:	alc
Tested by:	pho
MFC after:	2 weeks
X-Differential Revision: https://reviews.freebsd.org/D14625
r331129 ian March 18, 2018, 4:36 p.m.
parens in shift-and-mask expressions.  Reword and reflow some comments.