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: Sun, 08 Jul 2012 14:31:05 -0400 From: Jon Masters <jonathan@...masters.org> To: Arnd Bergmann <arnd@...db.de> CC: Olof Johansson <olof@...om.net>, Catalin Marinas <catalin.marinas@....com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 00/36] AArch64 Linux kernel port On 07/08/2012 03:54 AM, Jon Masters wrote: > In our bikeshedding conversations pondering future Fedora support, we've > pretty much settled on the aarch64 name now, and the hope is that we can > also avoid providing 32-bit compatibility (multi-arch) by relying on > virtualized guests for any 32-bit story. If that holds, we have some > flexibility to e.g. go for 64K page size, etc. if we want. Let me rephrase that to avoid missunderstanding. I am the strongest advocate of the "aarch64" name on our end. Others disagreed with that, but when the tooling, kernel, and other stuff settled on the same uniform name, it was my understanding that this was de facto settled. However, it would be wrong to say there are not dissenting viewpoints. My biggest fear here, however, is that we end up bikeshedding this to death, and we then have some use of one name, some of "arm64", and distros failing to agree on things like the correct triplet to use for the new architecture (we had some issues with this before). So, if we're going to argue over the name and make changes, let's do it now. There seems to be no value in the toolchain using one name, which is already upstream, and the kernel using another name. Jon. -- 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