| 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
| ||
|
Date: Thu, 26 Feb 2015 22:58:53 +0000 From: Russell King - ARM Linux <linux@....linux.org.uk> To: Rob Herring <robherring2@...il.com> Cc: Mathieu Poirier <mathieu.poirier@...aro.org>, Will Deacon <will.deacon@....com>, "linux-api@...r.kernel.org" <linux-api@...r.kernel.org>, Jonathan Corbet <corbet@....net>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org> Subject: Re: [PATCH v2] coresight-stm: adding driver for CoreSight STM component On Thu, Feb 26, 2015 at 04:24:53PM -0600, Rob Herring wrote: > We really shouldn't do private implementation here. It there really > any reason not to allow readq/writeq generically for 32-bit or just > for arm32? My argument has always been that drivers should do the emulation of 64-bit accesses when there is no native support. IO registers tend to have side effects when read/written. How do we know whether the low-half or the high-half should be written first? This isn't something that an architecture can really dictate. What may be right for one hardware device may not be correct for another. -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. -- 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