On 09/25/2015 10:18 AM, santosh shilimkar wrote: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.
On 9/25/2015 7:50 AM, Nishanth Menon wrote:[...]
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?
Why the user space should care about exact SOC ?
examples vary - trivial one is: debug tools like omapconf or testing
tools like opentest 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