<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/dev/cfe, branch release/12.3.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F12.3.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F12.3.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2021-10-07T03:27:26Z</updated>
<entry>
<title>sys/dev/cfi: include sys/types.h as well</title>
<updated>2021-10-07T03:27:26Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2020-01-02T22:52:31Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=af147ed09aa4d346b8526fb40a7016800664d33c'/>
<id>urn:sha1:af147ed09aa4d346b8526fb40a7016800664d33c</id>
<content type='text'>
This will soon be a dependency for machine/atomic.h on mips with the
introduction of 64-bit atomics; the scope here is pretty narrow, so throw it
here in the header just before systm.h, which includes machine/atomic.h

(cherry picked from commit 85ccd84cb3ce35f830cd4c07154152daf41181ef)
</content>
</entry>
<entry>
<title>MFC r360051: tty: convert tty_lock_assert to tty_assert_locked</title>
<updated>2020-04-24T13:31:22Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2020-04-24T13:31:22Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=74727284b626971c5209f162f593ec65d4606b64'/>
<id>urn:sha1:74727284b626971c5209f162f593ec65d4606b64</id>
<content type='text'>
A later change, currently being iterated on in D24459, will in-fact change
the lock type to an sx so that TTY drivers can sleep on it if they need to.
Committing this ahead of time to make the review in question a little more
palatable.

tty_lock_assert() is unfortunately still needed for now in two places to
make sure that the tty lock has not been recursed upon, for those scenarios
where it's supplied by the TTY driver and possibly a mutex that is allowed
to recurse.
</content>
</entry>
<entry>
<title>sys/dev: further adoption of SPDX licensing ID tags.</title>
<updated>2017-11-27T14:52:40Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-11-27T14:52:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=718cf2ccb9956613756ab15d7a0e28f2c8e91cab'/>
<id>urn:sha1:718cf2ccb9956613756ab15d7a0e28f2c8e91cab</id>
<content type='text'>
Mainly focus on files that use BSD 2-Clause license, however the tool I
was using misidentified many licenses so this was mostly a manual - error
prone - task.

The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.
</content>
</entry>
<entry>
<title>Sync CFE interface with upstream cfe-1.4.2 release.</title>
<updated>2016-08-01T16:26:08Z</updated>
<author>
<name>Landon J. Fuller</name>
<email>landonf@FreeBSD.org</email>
</author>
<published>2016-08-01T16:26:08Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=3cbea0b15cdbb3d3ae445a47057dc4efda9af4bb'/>
<id>urn:sha1:3cbea0b15cdbb3d3ae445a47057dc4efda9af4bb</id>
<content type='text'>
Approved by:	adrian (mentor)
Obtained from:	https://www.broadcom.com/support/communications-processors
Differential Revision:	https://reviews.freebsd.org/D7375
</content>
</entry>
<entry>
<title>Convert remaining {g,s}etenv-&gt;kern_{g,s}etenv</title>
<updated>2014-10-17T17:34:05Z</updated>
<author>
<name>Davide Italiano</name>
<email>davide@FreeBSD.org</email>
</author>
<published>2014-10-17T17:34:05Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=d9ca757cea4bc90ef070d1157da27c7fcbd88510'/>
<id>urn:sha1:d9ca757cea4bc90ef070d1157da27c7fcbd88510</id>
<content type='text'>
left over from r273174.

Reported by:    bz
</content>
</entry>
<entry>
<title>Use callout_*() rather than timeout()/untimeout().</title>
<updated>2014-05-30T15:46:10Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2014-05-30T15:46:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=f1f7034d11def7207cea9662ec6436b363123ae1'/>
<id>urn:sha1:f1f7034d11def7207cea9662ec6436b363123ae1</id>
<content type='text'>
Reviewed by:	imp
</content>
</entry>
<entry>
<title>More BUS_PROBE_NOWILDCARD sweeping. Some devices here (if_ath_ahb and siba)</title>
<updated>2013-10-29T14:19:42Z</updated>
<author>
<name>Nathan Whitehorn</name>
<email>nwhitehorn@FreeBSD.org</email>
</author>
<published>2013-10-29T14:19:42Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=feeec74df7e5dd8521ab85428f770dd92c5cf2da'/>
<id>urn:sha1:feeec74df7e5dd8521ab85428f770dd92c5cf2da</id>
<content type='text'>
resist easy conversion since they implement a great deal of their attach
logic inside probe(). Some of this could be fixed by moving it to attach(),
but some requires something more subtle than BUS_PROBE_NOWILDCARD.
</content>
</entry>
<entry>
<title>kern cons: introduce infrastructure for console grabbing by kernel</title>
<updated>2011-12-17T15:08:43Z</updated>
<author>
<name>Andriy Gapon</name>
<email>avg@FreeBSD.org</email>
</author>
<published>2011-12-17T15:08:43Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=9976156f12f1be7cb85c90e9ef54be06690bc955'/>
<id>urn:sha1:9976156f12f1be7cb85c90e9ef54be06690bc955</id>
<content type='text'>
At the moment grab and ungrab methods of all console drivers are no-ops.

Current intended meaning of the calls is that the kernel takes control of
console input.  In the future the semantics may be extended to mean that
the calling thread takes full ownership of the console (e.g. console
output from other threads could be suspended).

Inspired by:	bde
MFC after:	2 months
</content>
</entry>
<entry>
<title>Follow up to r225203 refining break-to-debugger run-time configuration</title>
<updated>2011-08-27T14:24:27Z</updated>
<author>
<name>Robert Watson</name>
<email>rwatson@FreeBSD.org</email>
</author>
<published>2011-08-27T14:24:27Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e5a0927394502ac7d7d0383c523490eb35f773dc'/>
<id>urn:sha1:e5a0927394502ac7d7d0383c523490eb35f773dc</id>
<content type='text'>
improvements:

(1) Implement new model in previously missed at91 UART driver
(2) Move BREAK_TO_DEBUGGER and ALT_BREAK_TO_DEBUGGER from opt_comconsole.h
    to opt_kdb.h (spotted by np)
(3) Garbage collect now-unused opt_comconsole.h

MFC after:	3 weeks
Approved by:	re (bz)
</content>
</entry>
<entry>
<title>Attempt to make break-to-debugger and alternative break-to-debugger more</title>
<updated>2011-08-26T21:46:36Z</updated>
<author>
<name>Robert Watson</name>
<email>rwatson@FreeBSD.org</email>
</author>
<published>2011-08-26T21:46:36Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4cf75455890c103c9a66cb791e88998aafd4f8ce'/>
<id>urn:sha1:4cf75455890c103c9a66cb791e88998aafd4f8ce</id>
<content type='text'>
accessible:

(1) Always compile in support for breaking into the debugger if options
    KDB is present in the kernel.

(2) Disable both by default, but allow them to be enabled via tunables
    and sysctls debug.kdb.break_to_debugger and
    debug.kdb.alt_break_to_debugger.

(3) options BREAK_TO_DEBUGGER and options ALT_BREAK_TO_DEBUGGER continue
    to behave as before -- only now instead of compiling in
    break-to-debugger support, they change the default values of the
    above sysctls to enable those features by default.  Current kernel
    configurations should, therefore, continue to behave as expected.

(4) Migrate alternative break-to-debugger state machine logic out of
    individual device drivers into centralised KDB code.  This has a
    number of upsides, but also one downside: it's now tricky to release
    sio spin locks when entering the debugger, so we don't.  However,
    similar logic does not exist in other device drivers, including uart.

(5) dcons requires some special handling; unlike other console types, it
    allows overriding KDB's own debugger selection, so we need a new
    interface to KDB to allow that to work.

GENERIC kernels in -CURRENT will now support break-to-debugger as long as
appropriate boot/run-time options are set, which should improve the
debuggability of BETA kernels significantly.

MFC after:	3 weeks
Reviewed by:	kib, nwhitehorn
Approved by:	re (bz)
</content>
</entry>
</feed>
