> On 5 Mar 2025, at 19:59, Lyude Paul wrote:
>
> We start off by introducing wrappers for the first important type of mode
> object: a DRM display connector. This introduces Connector DriverConnector> and ConnectorState. Both
> DriverConnector and DriverConnectorState must be implemented by KM
On 05/03/25 - 17:59, Lyude Paul wrote:
+
+// SAFETY: DRM connectors are refcounted mode objects
+unsafe impl RcModeObject for Connector {}
+
+// SAFETY:
+// * Via our type variants our data layout starts with `drm_connector`
+// * Since we don't expose `Connector` to users before it has been
in
On Fri, 2025-03-14 at 12:02 +0100, Maxime Ripard wrote:
> On Wed, Mar 05, 2025 at 05:59:20PM -0500, Lyude Paul wrote:
> > We start off by introducing wrappers for the first important type of mode
> > object: a DRM display connector. This introduces Connector > DriverConnector> and ConnectorState. B
On Wed, Mar 05, 2025 at 05:59:20PM -0500, Lyude Paul wrote:
> We start off by introducing wrappers for the first important type of mode
> object: a DRM display connector. This introduces Connector DriverConnector> and ConnectorState. Both
> DriverConnector and DriverConnectorState must be implement
We start off by introducing wrappers for the first important type of mode
object: a DRM display connector. This introduces Connector and ConnectorState. Both
DriverConnector and DriverConnectorState must be implemented by KMS
drivers, and a driver may have as many implementations of these two trait