| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <56056FD9.5060000@ti.com> Date: Fri, 25 Sep 2015 11:01:29 -0500 From: Nishanth Menon <nm@...com> To: santosh shilimkar <santosh.shilimkar@...cle.com>, Nishanth Menon <nm@...com>, Murali Karicheri <m-karicheri2@...com>, Santosh Shilimkar <ssantosh@...nel.org> CC: <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists