<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/dev/cas, branch releng/10.2</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=releng%2F10.2</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=releng%2F10.2'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2013-08-25T10:57:09Z</updated>
<entry>
<title>Give (*ext_free) an int return value allowing for very sophisticated</title>
<updated>2013-08-25T10:57:09Z</updated>
<author>
<name>Andre Oppermann</name>
<email>andre@FreeBSD.org</email>
</author>
<published>2013-08-25T10:57:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=bb25e5ab00bc882543960e212f182ffd5bb540f5'/>
<id>urn:sha1:bb25e5ab00bc882543960e212f182ffd5bb540f5</id>
<content type='text'>
external mbuf buffer management capabilities in the future.

For now only EXT_FREE_OK is defined with current legacy behavior.

Sponsored by:	The FreeBSD Foundation
</content>
</entry>
<entry>
<title>Add an mbuf pointer parameter to (*ext_free) to give the external</title>
<updated>2013-08-24T16:57:44Z</updated>
<author>
<name>Andre Oppermann</name>
<email>andre@FreeBSD.org</email>
</author>
<published>2013-08-24T16:57:44Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=9a736876096a84d749122a7c6e0e418683ed226f'/>
<id>urn:sha1:9a736876096a84d749122a7c6e0e418683ed226f</id>
<content type='text'>
free function access to the mbuf the external memory was attached
to.

Mechanically adjust all users to include the mbuf parameter.

This fixes a long standing annoyance for external free functions.
Before one had to sacrifice one of the argument pointers for this.

Sponsored by:	The FreeBSD Foundation
</content>
</entry>
<entry>
<title>- Correct mispellings of the word necessary</title>
<updated>2013-04-17T11:42:40Z</updated>
<author>
<name>Gabor Kovesdan</name>
<email>gabor@FreeBSD.org</email>
</author>
<published>2013-04-17T11:42:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a2098fea6ddaa8a24cb676c63cadbfa1b8fb0da8'/>
<id>urn:sha1:a2098fea6ddaa8a24cb676c63cadbfa1b8fb0da8</id>
<content type='text'>
Submitted by:	Christoph Mallon &lt;christoph.mallon@gmx.de&gt; (via private mail)
</content>
</entry>
<entry>
<title>- Move reporting of failures to disable RX/TX MAC under bootverbose as at</title>
<updated>2013-03-01T20:51:53Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2013-03-01T20:51:53Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a587c657efbc898b7937a9c14e10fdb8be346b18'/>
<id>urn:sha1:a587c657efbc898b7937a9c14e10fdb8be346b18</id>
<content type='text'>
  least the Saturn chips of 501-6738 cards may fail to do so the first
  time, which isn't fatal though.
  Reported by: Paul Keusemann
- Explain why we don't enable infinite bursts on sparc64.
- Given that these chips support memory write invalidate, make sure that
  it's enabled in the command register. Also make sure that PERR# and
  SERR# assertion is enabled.

MFC after:	1 week
</content>
</entry>
<entry>
<title>- Check the return value of taskqueue_start_threads().</title>
<updated>2013-01-25T23:44:02Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2013-01-25T23:44:02Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=7c2fdcac02c177db424a094c4771407e448eb1a4'/>
<id>urn:sha1:7c2fdcac02c177db424a094c4771407e448eb1a4</id>
<content type='text'>
- At least the Saturn chips of 501-6738 cards need a delay after freezing
  the external GMII pins before the internal PHY is accessible again. So
  wait a bit after (un)freezing these. Also don't touch the other bits of
  that configuration register. [1]
- Take advantage of nitems().

Reported and tested by: Paul Keusemann [1]

MFC after:	3 days
</content>
</entry>
<entry>
<title>Mechanically substitute flags from historic mbuf allocator with</title>
<updated>2012-12-04T09:32:43Z</updated>
<author>
<name>Gleb Smirnoff</name>
<email>glebius@FreeBSD.org</email>
</author>
<published>2012-12-04T09:32:43Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=c6499eccad497913a5025fbde8ae76da70e08043'/>
<id>urn:sha1:c6499eccad497913a5025fbde8ae76da70e08043</id>
<content type='text'>
malloc(9) flags in sys/dev.
</content>
</entry>
<entry>
<title>Remove duplicate const specifiers in many drivers (I hope I got all of</title>
<updated>2012-11-05T19:16:27Z</updated>
<author>
<name>Dimitry Andric</name>
<email>dim@FreeBSD.org</email>
</author>
<published>2012-11-05T19:16:27Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=29658c96ce9914fdf4ff4e3519fbec696ef32118'/>
<id>urn:sha1:29658c96ce9914fdf4ff4e3519fbec696ef32118</id>
<content type='text'>
them, please let me know if not).  Most of these are of the form:

static const struct bzzt_type {
	[...list of members...]
} const bzzt_devs[] = {
	[...list of initializers...]
};

The second const is unnecessary, as arrays cannot be modified anyway,
and if the elements are const, the whole thing is const automatically
(e.g. it is placed in .rodata).

I have verified this does not change the binary output of a full kernel
build (except for build timestamps embedded in the object files).

Reviewed by:	yongari, marius
MFC after:	1 week
</content>
</entry>
<entry>
<title>- There's no need to overwrite the default device method with the default</title>
<updated>2011-11-22T21:28:20Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2011-11-22T21:28:20Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4b7ec27007570e0ce4fe9dbb447e7afc131b487a'/>
<id>urn:sha1:4b7ec27007570e0ce4fe9dbb447e7afc131b487a</id>
<content type='text'>
  one. Interestingly, these are actually the default for quite some time
  (bus_generic_driver_added(9) since r52045 and bus_generic_print_child(9)
  since r52045) but even recently added device drivers do this unnecessarily.
  Discussed with: jhb, marcel
- While at it, use DEVMETHOD_END.
  Discussed with: jhb
- Also while at it, use __FBSDID.
</content>
</entry>
<entry>
<title>- Expand the scope of the lock in the interrupt routine to close races with</title>
<updated>2011-07-13T18:52:11Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2011-07-13T18:52:11Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=fcdbb666c0604a087a6c2114aab20131b39b6fd1'/>
<id>urn:sha1:fcdbb666c0604a087a6c2114aab20131b39b6fd1</id>
<content type='text'>
  checking IFF_DRV_RUNNING and simplify the code. This also involves holding
  the driver lock in the rx_ch callout.
- Just use ifp instead of sc-&gt;sc_ifp.

Submitted by:	jhb (mostly)
</content>
</entry>
<entry>
<title>Partially merge r223648, r223648 and r223949 from gem(4):</title>
<updated>2011-07-12T13:22:17Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2011-07-12T13:22:17Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5f8a9ae4a9cb54686da6aff5c4bba79f9edae591'/>
<id>urn:sha1:5f8a9ae4a9cb54686da6aff5c4bba79f9edae591</id>
<content type='text'>
- Consistently use the newly introduced sc_mac_rxcfg throughout the driver
  instead of reading the old content of CAS_MAC_RX_CONF.
- Increment if_iqdrops instead of if_ierrors in case of RX buffer allocation
  failure.
- According to the Cassini datasheet the RX MAC should also be disabled in
  cas_setladrf() before changing its configuration.
- Add error messages to gem_disable_{r,t}x() and take advantage of these
  throughout the driver instead of duplicating their functionality all over
  the place.
</content>
</entry>
</feed>
