ARM: integrator: multiplatform advancements
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 6 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 6 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] ARM: integrator: multiplatform advancements
Quoted 4 lines · Linus Walleij
The *real* solution, one might argue is to convert the CLCD driver to DRM and add device tree bindings, but it appears that this is an orthogonal goal that has been attempted by other with mixed results.
What mixed results? You know, I find it rather sick that people run around trying to do this to a driver that I authored and maintain without one comment to me about it. It sometimes feels like people think I don't exist anymore.
The biggest complaint I've heard against DRM is the amount of code required. That's partly because we haven't - until now - had a good way to separate the "connectors" as stand-alone implementations separate from the core DRM drivers. I'm hopeful that by 3.15, we will see some implementations (imx-drm and armada) start making use of this.
Also, remember that DRM is Direct Rendering Manager, which incorporates Kernel Mode Setting. It's the KMS part which is most relevant to things like CLCD since it has no GPU. However, the non-KMS bits also are when you have something like a Mali GPU or other GPU.
We /really/ need these GPUs to move over to DRM - any ARM platform using a GPU today is inherently insecure since they all have been coded to push physical addresses around everywhere, which basically means userspace can use the GPU to access parts of the system such as overwriting bits of the kernel.
It's useless write-protecting the vectors page and/or the kernel text in a vain attempt to provide additional security if the GPU can be used from userspace to write to that RAM.
Having everything under DRM eliminates that problem because userspace only gets to deal with handles to the various buffers rather than physical addresses, which ensures that you can't specify an address for a buffer you don't own.
Signature · 3 lines
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad. Estimate before purchase was "up to 13.2Mbit".