<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/dev/sym, branch release/9.3.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F9.3.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F9.3.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2013-12-28T01:47:19Z</updated>
<entry>
<title>MFC r259880:</title>
<updated>2013-12-28T01:47:19Z</updated>
<author>
<name>Dimitry Andric</name>
<email>dim@FreeBSD.org</email>
</author>
<published>2013-12-28T01:47:19Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=1395851baa089fc161c2b2a4330bffdb480ae246'/>
<id>urn:sha1:1395851baa089fc161c2b2a4330bffdb480ae246</id>
<content type='text'>
In sys/dev/sym/sym_hipd.c, remove static functions sym_que_first(),
sym_que_last() and sym_remque_tail(), which are all unused since r53790.
</content>
</entry>
<entry>
<title>Merge r254263:</title>
<updated>2013-08-13T22:05:50Z</updated>
<author>
<name>Scott Long</name>
<email>scottl@FreeBSD.org</email>
</author>
<published>2013-08-13T22:05:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=cffe159b0e61cee6bce082f4bd05a4f06a1d53a9'/>
<id>urn:sha1:cffe159b0e61cee6bce082f4bd05a4f06a1d53a9</id>
<content type='text'>
Update PCI drivers to no longer look at the MEMIO-enabled bit in the PCI
command register.  The lazy BAR allocation code in FreeBSD sometimes
disables this bit when it detects a range conflict, and will re-enable
it on demand when a driver allocates the BAR.  Thus, the bit is no longer
a reliable indication of capability, and should not be checked.  This
results in the elimination of a lot of code from drivers, and also gives
the opportunity to simplify a lot of drivers to use a helper API to set
the busmaster enable bit.

This changes fixes some recent reports of disk controllers and their
associated drives/enclosures disappearing during boot.

Candidate for 9.2

Submitted by:	jhb
Reviewed by:	jfv, marius, adrian, achim
</content>
</entry>
<entry>
<title>MFC: r245263</title>
<updated>2013-06-18T15:17:29Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2013-06-18T15:17:29Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=411d22fafa754c4302362bf807ad4534ccc87cc4'/>
<id>urn:sha1:411d22fafa754c4302362bf807ad4534ccc87cc4</id>
<content type='text'>
Clang complains about the comparision of fak &lt; 0 always being
false. It is right. Delete it because on the next line we catch all
'negative' cases with the test &gt; 2, since 'negative' numbers are just
really big unsigned numbers and we do an identical action.
</content>
</entry>
<entry>
<title>MFC: r251403 (partial)</title>
<updated>2013-06-18T15:14:20Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2013-06-18T15:14:20Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=cb0c43759bec82242355c9f1e56d1b6de22f0d69'/>
<id>urn:sha1:cb0c43759bec82242355c9f1e56d1b6de22f0d69</id>
<content type='text'>
Flag sym(4) as supporting unmapped I/O; all necessary conversion actually
already has been done as part of r246713 (MFC'ed to stable/9 in r251874).
</content>
</entry>
<entry>
<title>Big MFC of the physbio changes necessary for unmapped I/O.  These changes</title>
<updated>2013-06-18T00:36:53Z</updated>
<author>
<name>Scott Long</name>
<email>scottl@FreeBSD.org</email>
</author>
<published>2013-06-18T00:36:53Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=039e422c063977ba9073fd2c93883dd8a5a36d48'/>
<id>urn:sha1:039e422c063977ba9073fd2c93883dd8a5a36d48</id>
<content type='text'>
have been in production at Netflix for several months with significant
success.

MFC r246713:

Reform the busdma API so that new types may be added without modifying
every architecture's busdma_machdep.c.  It is done by unifying the
bus_dmamap_load_buffer() routines so that they may be called from MI
code.  The MD busdma is then given a chance to do any final processing
in the complete() callback.

MFC r249538:
Some compilers issue a warning when wider integer is casted to narrow
pointer.  Supposedly shut down the warning by casting through
uintptr_t.

MFC r251479:
Simplify the checking of flags for cam_periph_mapmem().  This gets rid of
a lot of code redundancy and grossness at very minor expense.

MFC r251837:
MFC r251842:
Add infrastructure for doing compatibility shims, as has been sorely
needed for the last 10 years.  Far too much of the internal API is
exposed, and every small adjustment causes applications to stop working.
To kick this off, bump the API version to 0x17 as should have been done
with r246713, but add shims to compensate.  Thanks to the shims, there
should be no visible change in application behavior.

Submitted by:	kib, jeffr
Approved by:	kib
Obtained from:	Netflix
</content>
</entry>
<entry>
<title>MFC: r251402 (partial)</title>
<updated>2013-06-09T13:24:16Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2013-06-09T13:24:16Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=d158a840fe707080bb6232ff0a6649be6acd9fdc'/>
<id>urn:sha1:d158a840fe707080bb6232ff0a6649be6acd9fdc</id>
<content type='text'>
Handle/mark/nuke unused arguments.
</content>
</entry>
<entry>
<title>MFC: r251394</title>
<updated>2013-06-09T13:17:52Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2013-06-09T13:17:52Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0ab28c7886b0bbf6761cd6caacbf87d06b5dbd87'/>
<id>urn:sha1:0ab28c7886b0bbf6761cd6caacbf87d06b5dbd87</id>
<content type='text'>
CAM_DEV_QFREEZE handling should only be done on request submission but
neither on completion nor by SIM drivers in the first place. This issue
has been revealed by r249466.
</content>
</entry>
<entry>
<title>MFC 247266</title>
<updated>2013-03-28T14:25:09Z</updated>
<author>
<name>Matt Jacob</name>
<email>mjacob@FreeBSD.org</email>
</author>
<published>2013-03-28T14:25:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e402fccec1794855437cd50d50d5685fdadaaed6'/>
<id>urn:sha1:e402fccec1794855437cd50d50d5685fdadaaed6</id>
<content type='text'>
Don't try and negotiate sync mode if either period or offset are zero.
</content>
</entry>
<entry>
<title>MFC: r238621</title>
<updated>2012-07-22T14:32:49Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2012-07-22T14:32:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=c31edb1aad397b2017c4ed79ca22694d79338871'/>
<id>urn:sha1:c31edb1aad397b2017c4ed79ca22694d79338871</id>
<content type='text'>
Revert the use of BUS_DMA_ALLOCNOW when creating the DMA tag for user
data introduced in r236061 (MFC'ed to stable/9 in r237186). Using that
flag doesn't make that much sense on this case as the DMA maps using
it are also created during sym_pci_attach(). Moreover, due to the
maxsegsz parameter used, doing so may exhaust the bounce pages pool
on architectures requiring bounce pages. [1]
While at it, use a slightly more appropriate maxsegsz parameter.

PR:		169526
Submitted by:	Mike Watters [1]
Approved by:	re (kib)
</content>
</entry>
<entry>
<title>MFC: r237101</title>
<updated>2012-06-17T09:42:56Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2012-06-17T09:42:56Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=d1690a70b571788587b3561cc50ac77fc457fc82'/>
<id>urn:sha1:d1690a70b571788587b3561cc50ac77fc457fc82</id>
<content type='text'>
Fix a braino in r236469 (MFC'ed to stable/9 in r236468); the number of
DMA tags required for handling MAXPHYS should be based on PAGE_SIZE rather
than SYM_CONF_DMA_BOUNDARY.
While at it, reuse the SYM_CONF_MAX_SG macro for specifying the maximum
number of DMA tags so sym(4) itself doesn't size memory beyond what's
required for handling MAXPHYS.

PR:		168928
</content>
</entry>
</feed>
