<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test2/sys/dev/scc, branch release/11.3.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.3.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.3.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/'/>
<updated>2018-03-29T02:50:57Z</updated>
<entry>
<title>Revert r330897:</title>
<updated>2018-03-29T02:50:57Z</updated>
<author>
<name>Eitan Adler</name>
<email>eadler@FreeBSD.org</email>
</author>
<published>2018-03-29T02:50:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=4ab2e064d7950be84256d671a7ae93f87cc6aa36'/>
<id>urn:sha1:4ab2e064d7950be84256d671a7ae93f87cc6aa36</id>
<content type='text'>
This was intended to be a non-functional change. It wasn't. The commit
message was thus wrong. In addition it broke arm, and merged crypto
related code.

Revert with prejudice.

This revert skips files touched in r316370 since that commit was since
MFCed. This revert also skips files that require $FreeBSD$ property
changes.

Thank you to those who helped me get out of this mess including but not
limited to gonzo, kevans, rgrimes.

Requested by: gjb (re)
</content>
</entry>
<entry>
<title>Partial merge of the SPDX changes</title>
<updated>2018-03-14T03:19:51Z</updated>
<author>
<name>Eitan Adler</name>
<email>eadler@FreeBSD.org</email>
</author>
<published>2018-03-14T03:19:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=be5d0b9566b13fdf8cabebb63334cbec12bfc409'/>
<id>urn:sha1:be5d0b9566b13fdf8cabebb63334cbec12bfc409</id>
<content type='text'>
These changes are incomplete but are making it difficult
to determine what other changes can/should be merged.

No objections from:	pfg
</content>
</entry>
<entry>
<title>Replace some more default range checks with RMAN_IS_DEFAULT_RANGE().</title>
<updated>2016-03-02T03:26:56Z</updated>
<author>
<name>Justin Hibbits</name>
<email>jhibbits@FreeBSD.org</email>
</author>
<published>2016-03-02T03:26:56Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=82ed3cb0e4bf60f58b13368aa3a4a4f7e7ff9a57'/>
<id>urn:sha1:82ed3cb0e4bf60f58b13368aa3a4a4f7e7ff9a57</id>
<content type='text'>
This is a follow-on to r295832.
</content>
</entry>
<entry>
<title>Migrate many bus_alloc_resource() calls to bus_alloc_resource_anywhere().</title>
<updated>2016-02-27T03:38:01Z</updated>
<author>
<name>Justin Hibbits</name>
<email>jhibbits@FreeBSD.org</email>
</author>
<published>2016-02-27T03:38:01Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=c47476d7e6801deffc8b3c057d0fbf7d2335a0c2'/>
<id>urn:sha1:c47476d7e6801deffc8b3c057d0fbf7d2335a0c2</id>
<content type='text'>
Most calls to bus_alloc_resource() use "anywhere" as the range, with a given
count.  Migrate these to use the new bus_alloc_resource_anywhere() API.

Reviewed by:	jhb
Differential Revision:	https://reviews.freebsd.org/D5370
</content>
</entry>
<entry>
<title>Convert rman to use rman_res_t instead of u_long</title>
<updated>2016-01-27T02:23:54Z</updated>
<author>
<name>Justin Hibbits</name>
<email>jhibbits@FreeBSD.org</email>
</author>
<published>2016-01-27T02:23:54Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=2dd1bdf1834c53d048d3d9a7079b45afea5cecd7'/>
<id>urn:sha1:2dd1bdf1834c53d048d3d9a7079b45afea5cecd7</id>
<content type='text'>
Summary:
Migrate to using the semi-opaque type rman_res_t to specify rman resources.  For
now, this is still compatible with u_long.

This is step one in migrating rman to use uintmax_t for resources instead of
u_long.

Going forward, this could feasibly be used to specify architecture-specific
definitions of resource ranges, rather than baking a specific integer type into
the API.

This change has been broken out to facilitate MFC'ing drivers back to 10 without
breaking ABI.

Reviewed By: jhb
Sponsored by:	Alex Perez/Inertial Computing
Differential Revision: https://reviews.freebsd.org/D5075
</content>
</entry>
<entry>
<title>In sys/dev/scc, remove unused static function scc_setmreg().  While</title>
<updated>2013-12-29T20:23:08Z</updated>
<author>
<name>Dimitry Andric</name>
<email>dim@FreeBSD.org</email>
</author>
<published>2013-12-29T20:23:08Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=6ba26efcb5c13f16d7b9ee3ba1af9b0c80d81d5f'/>
<id>urn:sha1:6ba26efcb5c13f16d7b9ee3ba1af9b0c80d81d5f</id>
<content type='text'>
here, invoke scc_getmreg() in two more places where it can be used.

Reviewed by:	marcel
MFC after:	3 days
</content>
</entry>
<entry>
<title>Make r253899 compile.</title>
<updated>2013-08-03T21:24:52Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2013-08-03T21:24:52Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=eb84fc95061d8b4f540ac1befe4fdab834597378'/>
<id>urn:sha1:eb84fc95061d8b4f540ac1befe4fdab834597378</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Const'ify scc_driver_name.</title>
<updated>2013-08-02T23:31:51Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2013-08-02T23:31:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=1e53269ac2d96ce70747e18aa1942285ffee67dd'/>
<id>urn:sha1:1e53269ac2d96ce70747e18aa1942285ffee67dd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>- Use NULL instead of 0 for pointers.</title>
<updated>2013-08-02T23:30:32Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2013-08-02T23:30:32Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=71bda3eb9aa62e7073ad31ff4c374a21e2fc34ef'/>
<id>urn:sha1:71bda3eb9aa62e7073ad31ff4c374a21e2fc34ef</id>
<content type='text'>
- Remove unnecessary __RMAN_RESOURCE_VISIBLE.
</content>
</entry>
<entry>
<title>- Implement iclear methods for QUICC and SAB 82532. With r253161 in place,</title>
<updated>2013-08-02T23:28:49Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2013-08-02T23:28:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=c4b1deaf0d05e7ba715124b4c752edef80222115'/>
<id>urn:sha1:c4b1deaf0d05e7ba715124b4c752edef80222115</id>
<content type='text'>
  this is is crucial at least for the latter.
  What happens is that attaching uart(4) to scc(4) causes the SAB 82532 to
  "receive" something and trigger a SER_INT_RXREADY interrupt, given that
  at least fast/filter interrupts are already enabled. Prior to r253161,
  uart_bus_ihand() was set up at this point and handled that condition,
  i. e. read the RX FIFO and issued a Receive Message Complete.
  Now, uart_bus_ihand() and uart_intr() are setup after attaching uart(4),
  leaving the SER_INT_RXREADY interrupt triggered during the latter to
  be handled by the iclear method. However, with that method not implement,
  this in turn causes SAB 82532 to not issue any further SER_INT_RXREADY
  interrupts until the RX FIFO is full again. Thus, 15 received bytes go
  to nowhere, given that "the other half" of the RX FIFO is used for status
  information. Hence, implementing sab82532_bfe_iclear() fixes things again.
  Potentially, the same problem exists for QUICC.
- Remove unnecessary __RMAN_RESOURCE_VISIBLE.
- Remove a superfluous header.
- Use KOBJMETHOD_END.
- Mark unused arguments as such.
- Remove variables unused after initialization.

Reviewed by:	marcel (earlier version)
</content>
</entry>
</feed>
