9/25/2015 9:01 AM, Nishanth Menon wrote:
On 09/25/2015 10:18 AM, santosh shilimkar wrote:
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[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.
I guessed omapconf example is coming though Keystone has no such tool
yet ;-). Opentest shouldn't need that info either.
I do agree that having a soc along with board is useful in
longer run to accommodation more boards and variants.
And only on that merit, I am willing to take these patches.
Please refresh the series commit messages based on the
discussion so far and repost. Will pick it up then.
Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
