src/sys/dev/drm2/drm_sysctl.c, branch releng/14.2 FreeBSD source tree sys: Remove $FreeBSD$: one-line .c pattern 2023-08-16T17:54:36+00:00 Warner Losh imp@FreeBSD.org 2023-08-16T17:54:36+00:00 685dc743dc3b5645e34836464128e1c0558b404b Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/ 
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
Remove an extra argument to SYSCTL_FOREACH 2022-10-05T09:27:48+00:00 Andrew Turner andrew@FreeBSD.org 2022-10-05T09:27:48+00:00 fbc9f1b2d6cf90c02b918671fb7791cf36472cfd This was missed in e0853c933661. Sponsored by: The FreeBSD Foundation 
This was missed in e0853c933661.

Sponsored by:	The FreeBSD Foundation
Use SYSCTL_FOREACH in drm2 2022-10-05T09:26:36+00:00 Andrew Turner andrew@FreeBSD.org 2022-10-05T09:24:13+00:00 e0853c9336616e4ca4ff41aab0f8ad91bb75fd42 This was added recently. Use it to get the correct _FOREACH macro. Sponsored by: The FreeBSD Foundation 
This was added recently. Use it to get the correct _FOREACH macro.

Sponsored by:	The FreeBSD Foundation
Mark more nodes as CTLFLAG_MPSAFE or CTLFLAG_NEEDGIANT (5 of many) 2020-02-16T17:11:54+00:00 Pawel Biernacki kaktus@FreeBSD.org 2020-02-16T17:11:54+00:00 59e4be225c4bca5e0e76b7703594d5c03a24a825 r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are still not MPSAFE (or already are but aren’t properly marked). Use it in preparation for a general review of all nodes. This is non-functional change that adds annotations to SYSCTL_NODE and SYSCTL_PROC nodes using one of the soon-to-be-required flags. Reviewed by: imp, kib Approved by: kib (mentor) Differential Revision: https://reviews.freebsd.org/D23633 
r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are
still not MPSAFE (or already are but aren’t properly marked). Use it in
preparation for a general review of all nodes.
This is non-functional change that adds annotations to SYSCTL_NODE and
SYSCTL_PROC nodes using one of the soon-to-be-required flags.

Reviewed by:	imp, kib
Approved by:	kib (mentor)
Differential Revision:	https://reviews.freebsd.org/D23633
Revert drm2 removal. 2018-08-24T00:02:00+00:00 Warner Losh imp@FreeBSD.org 2018-08-24T00:02:00+00:00 592ffb217505586a6c69e91549a3c14132875f16 Revert r338177, r338176, r338175, r338174, r338172 After long consultations with re@, core members and mmacy, revert these changes. Followup changes will be made to mark them as deprecated and prent a message about where to find the up-to-date driver. Followup commits will be made to make this clear in the installer. Followup commits to reduce POLA in ways we're still exploring. It's anticipated that after the freeze, this will be removed in 13-current (with the residual of the drm2 code copied to sys/arm/dev/drm2 for the TEGRA port's use w/o the intel or radeon drivers). Due to the impending freeze, there was no formal core vote for this. I've been talking to different core members all day, as well as Matt Macey and Glen Barber. Nobody is completely happy, all are grudgingly going along with this. Work is in progress to mitigate the negative effects as much as possible. Requested by: re@ (gjb, rgrimes) 
Revert r338177, r338176, r338175, r338174, r338172

After long consultations with re@, core members and mmacy, revert
these changes. Followup changes will be made to mark them as
deprecated and prent a message about where to find the up-to-date
driver.  Followup commits will be made to make this clear in the
installer. Followup commits to reduce POLA in ways we're still
exploring.

It's anticipated that after the freeze, this will be removed in
13-current (with the residual of the drm2 code copied to
sys/arm/dev/drm2 for the TEGRA port's use w/o the intel or
radeon drivers).

Due to the impending freeze, there was no formal core vote for
this. I've been talking to different core members all day, as well as
Matt Macey and Glen Barber. Nobody is completely happy, all are
grudgingly going along with this. Work is in progress to mitigate
the negative effects as much as possible.

Requested by: re@ (gjb, rgrimes)
Remove legacy drm and drm2 from tree 2018-08-22T01:50:12+00:00 Matt Macy mmacy@FreeBSD.org 2018-08-22T01:50:12+00:00 d157fbd5b4b59aa863cbb82d4ad08596996d3ab0 As discussed on the MLs drm2 conflicts with the ports' version and there is no upstream for most if not all of drm. Both have been merged in to a single port. Users on powerpc, 32-bit hardware, or with GPUs predating Radeon and i915 will need to install the graphics/drm-legacy-kmod. All other users should be able to use one of the LinuxKPI-based ports: graphics/drm-stable-kmod, graphics/drm-next-kmod, graphics/drm-devel-kmod. MFC: never Approved by: core@ 
As discussed on the MLs drm2 conflicts with the ports' version and there
is no upstream for most if not all of drm. Both have been merged in to
a single port.

Users on powerpc, 32-bit hardware, or with GPUs predating Radeon
and i915 will need to install the graphics/drm-legacy-kmod. All
other users should be able to use one of the LinuxKPI-based ports:
graphics/drm-stable-kmod, graphics/drm-next-kmod, graphics/drm-devel-kmod.

MFC: never
Approved by: core@
drm: Update the device-independent code to match Linux 3.8.13 2015-03-17T18:50:33+00:00 Jean-Sébastien Pédron dumbbell@FreeBSD.org 2015-03-17T18:50:33+00:00 455fa6518ac6e2c25197085a8b900451487642b4 This update brings few features: o Support for the setmaster/dropmaster ioctls. For instance, they are used to run multiple X servers simultaneously. o Support for minor devices. The only user-visible change is a new entry in /dev/dri but it is useless at the moment. This is a first step to support render nodes [1]. The main benefit is to greatly reduce the diff with Linux (at the expense of an unreadable commit diff). Hopefully, next upgrades will be easier. No updates were made to the drivers, beside adapting them to API changes. [1] https://en.wikipedia.org/wiki/Direct_Rendering_Manager#Render_nodes Tested by: Many people MFC after: 1 month Relnotes: yes 
This update brings few features:
    o  Support for the setmaster/dropmaster ioctls. For instance, they
       are used to run multiple X servers simultaneously.
    o  Support for minor devices. The only user-visible change is a new
       entry in /dev/dri but it is useless at the moment. This is a
       first step to support render nodes [1].

The main benefit is to greatly reduce the diff with Linux (at the
expense of an unreadable commit diff). Hopefully, next upgrades will be
easier.

No updates were made to the drivers, beside adapting them to API
changes.

[1] https://en.wikipedia.org/wiki/Direct_Rendering_Manager#Render_nodes

Tested by:	Many people
MFC after:	1 month
Relnotes:	yes
Adjust printf format specifiers for dev_t and ino_t in kernel. 2014-12-17T07:27:19+00:00 Gleb Kurtsou gleb@FreeBSD.org 2014-12-17T07:27:19+00:00 dde58752dbf08343d9b74b48ffabedbf5ca2e7e8 ino_t and dev_t are about to become uint64_t. Reviewed by: kib, mckusick 
ino_t and dev_t are about to become uint64_t.

Reviewed by:	kib, mckusick
Pull in r267961 and r267973 again. Fix for issues reported will follow. 2014-06-28T03:56:17+00:00 Hans Petter Selasky hselasky@FreeBSD.org 2014-06-28T03:56:17+00:00 af3b2549c4ba2ef00a7cbb4cb6836598bf0aefbe 






Revert r267961, r267973:
2014-06-27T22:05:21+00:00

Glen Barber
gjb@FreeBSD.org

2014-06-27T22:05:21+00:00

37a107a407cdb47ee0f4c4337e369e9973b34076

These changes prevent sysctl(8) from returning proper output,
such as:

 1) no output from sysctl(8)
 2) erroneously returning ENOMEM with tools like truss(1)
    or uname(1)
 truss: can not get etype: Cannot allocate memory





These changes prevent sysctl(8) from returning proper output,
such as:

 1) no output from sysctl(8)
 2) erroneously returning ENOMEM with tools like truss(1)
    or uname(1)
 truss: can not get etype: Cannot allocate memory