Difference between revisions of "RK3566 EBC Reverse-Engineering"

Line 34:

At the very least, you should read up on the registers and calling convention used.

= Various Findings =

The driver isn't really something that can be mainlined as-is once reversed, as it makes a number of questionable design decisions.

* It's technically a DRM subsystem driver, but doesn't really utilise what DRM provides at all.

* It seems to register a new ioctl to set buffer attributes like width and height, despite DRM more than likely having a way for clients to tell a driver what size the framebuffer should be.

* It directly interacts with the PMIC instead of going through regulators/hwmon.

However, reverse engineering to know how it works provides a good baseline from which we can rewrite it in a more sensible manner.

= Debug Information =

@@ Line 34: / Line 34: @@
 At the very least, you should read up on the registers and calling convention used.
+= Various Findings =
+The driver isn't really something that can be mainlined as-is once reversed, as it makes a number of questionable design decisions.
+* It's technically a DRM subsystem driver, but doesn't really utilise what DRM provides at all.
+* It seems to register a new ioctl to set buffer attributes like width and height, despite DRM more than likely having a way for clients to tell a driver what size the framebuffer should be.
+* It directly interacts with the PMIC instead of going through regulators/hwmon.
+However, reverse engineering to know how it works provides a good baseline from which we can rewrite it in a more sensible manner.
 = Debug Information =

Difference between revisions of "RK3566 EBC Reverse-Engineering"

Navigation menu

Search