[PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags

On 09/25/2015 12:01 PM, Nishanth Menon wrote:

On 09/25/2015 10:18 AM, santosh shilimkar wrote:

quoted

On 9/25/2015 7:50 AM, Nishanth Menon wrote:

[...]

quoted

quoted

But, how about userspace
needing to know which SoC they are on, without needing to depend on
board->soc mapping? How do we help resolve that?

Believe it or not, user space tools that are custom to a specific SoC 
would require such knowledge. So I agree on this front that a SoC 
specific compatibility is cool to have. I think that should have been 
clear in the commit description.

My Acked-By: Murali Karicheri [off-list ref]

quoted

quoted

Why the user space should care about exact SOC ?

examples vary - trivial one is: debug tools like omapconf[1] or testing
tools like opentest[2] need some standard way to ensure Linux kernel is
functional - trusting the least set of parameters is usually what we
would prefer. while building a generic distro such as debian or yocto,
one prefers NOT to need to do a package build per SoC/perboard - that
never scales. instead, you'd like the same application run on different
systems dynamically.


[1] https://github.com/omapconf/omapconf
[2] http://arago-project.org/wiki/index.php/Opentest

-- 
Murali Karicheri
Linux Kernel, Keystone