ARM: orion5x/dove/mv78xx0 multiplatform
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 5 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 5 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/5] ARM: orion5x/dove/mv78xx0 multiplatform
Quoted 4 lines · Jason Cooper
Quoted 3 lines · Arnd Bergmann
I think you are right this has come up in the past, but I don't see how it would work in practice without significant changes to driver subsystems:
Quoted 8 lines
Quoted 5 lines
The way we describe devices in DT is often very different from what we have for the traditional board files, and in some cases we don't even support platform data any more, so this would still depend on having properties according to the DT bindings, and require a large chunk of the same code that is doing DT at the moment.
yes, that's unfortunate. Perhaps the tinification links are still helpful to Detlef.
I've heard of the tinyfication project, but not paid too much attentions. I believe it's the wrong side around.
For busybox, patches that produce larger binaries without providing new functionality are just rejected.
Those that provide new functionality and such create bigger binaries must have a configuration option for still being able to get the old small binary.
If you accept patches that make the kernel bigger without a configuration option to avoid this, any tinyfication effort that tries to make the kernel small again afterwards is IMHO a noble but lost cause.
Detlef