| 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: <4FEDE184.7070109@freescale.com> Date: Fri, 29 Jun 2012 12:10:28 -0500 From: Scott Wood <scottwood@...escale.com> To: Timur Tabi <timur@...escale.com> CC: Zhao Chenhui-B35336 <B35336@...escale.com>, "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>, Wood Scott-B07421 <B07421@...escale.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "galak@...nel.crashing.org" <galak@...nel.crashing.org>, Li Yang-R58472 <r58472@...escale.com> Subject: Re: [PATCH v6 1/5] powerpc/85xx: implement hardware timebase sync On 06/29/2012 11:12 AM, Timur Tabi wrote: > Scott Wood wrote: >> Why is this different from anywhere else where we have a list of >> compatibles to match, often based on various SoCs? Note that we >> explicitly want to match only certain SoCs here. > > I was just hoping to find a way to avoid an ever increasing list of > compatible strings. PCI drivers have to put up with it, why should we be different? :-) > Other posts on this thread imply that this code could > work for all multi-core e500 parts. That list covers all multi-core e500v2 parts that I know of. Corenet based chips will need a slightly different implementation, since the registers are different. -Scott -- 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