From: nm@ti•com (Nishanth Menon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags
Date: Fri, 25 Sep 2015 11:01:29 -0500 [thread overview]
Message-ID: <56056FD9.5060000@ti.com> (raw)
In-Reply-To: <560565AF.2010701@oracle.com>
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.
[1] https://github.com/omapconf/omapconf
[2] http://arago-project.org/wiki/index.php/Opentest
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-09-25 16:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 16:08 [PATCH 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches Nishanth Menon
2015-09-22 16:08 ` [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon
2015-09-23 18:05 ` Murali Karicheri
2015-09-23 19:15 ` Nishanth Menon
2015-09-23 18:19 ` santosh shilimkar
2015-09-24 14:05 ` Murali Karicheri
2015-09-24 14:20 ` Nishanth Menon
2015-09-24 15:54 ` Murali Karicheri
2015-09-25 14:50 ` Nishanth Menon
2015-09-25 15:18 ` santosh shilimkar
2015-09-25 16:01 ` Nishanth Menon [this message]
2015-09-25 16:15 ` santosh shilimkar
2015-09-25 17:38 ` Nishanth Menon
2015-10-02 16:09 ` santosh shilimkar
2015-10-03 23:44 ` Nishanth Menon
2015-10-04 0:16 ` santosh.shilimkar at oracle.com
2015-09-30 14:31 ` Murali Karicheri
2015-09-22 16:08 ` [PATCH 2/3] ARM: keystone: Update compatible to have SoC specific matches Nishanth Menon
2015-09-22 16:08 ` [PATCH 3/3] ARM: dts: keystone: Update SoC specific compatible flags Nishanth Menon
2015-10-03 23:38 ` [PATCH V2 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches Nishanth Menon
2015-10-03 23:38 ` [PATCH V2 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon
2015-10-03 23:38 ` [PATCH V2 2/3] ARM: keystone: Update compatible to have SoC specific matches Nishanth Menon
2015-10-03 23:38 ` [PATCH V2 3/3] ARM: dts: keystone: Update SoC specific compatible flags Nishanth Menon
2015-10-04 0:13 ` [PATCH V2 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches santosh.shilimkar at oracle.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56056FD9.5060000@ti.com \
--to=nm@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox