From patchwork Sat Dec 26 16:05:42 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Yann E. MORIN" X-Patchwork-Id: 561107 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by ozlabs.org (Postfix) with ESMTP id BD81A140CBC for ; Sun, 27 Dec 2015 03:06:00 +1100 (AEDT) Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b=Cz6XQnTG; dkim-atps=neutral Received: from localhost (localhost [127.0.0.1]) by fraxinus.osuosl.org (Postfix) with ESMTP id 6B9888B043; Sat, 26 Dec 2015 16:05:59 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from fraxinus.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cEKUzfJZtN6B; Sat, 26 Dec 2015 16:05:54 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by fraxinus.osuosl.org (Postfix) with ESMTP id 062F48AF95; Sat, 26 Dec 2015 16:05:54 +0000 (UTC) X-Original-To: buildroot@lists.busybox.net Delivered-To: buildroot@osuosl.org Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by ash.osuosl.org (Postfix) with ESMTP id 0FB131C0CB7 for ; Sat, 26 Dec 2015 16:05:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by hemlock.osuosl.org (Postfix) with ESMTP id 0C5D493928 for ; Sat, 26 Dec 2015 16:05:53 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from hemlock.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81fZG99inr1r for ; Sat, 26 Dec 2015 16:05:52 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by hemlock.osuosl.org (Postfix) with ESMTPS id 0664793927 for ; Sat, 26 Dec 2015 16:05:52 +0000 (UTC) Received: by mail-wm0-f54.google.com with SMTP id p187so220558600wmp.0 for ; Sat, 26 Dec 2015 08:05:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:date:message-id:in-reply-to:references; bh=xeuh9hE8S3wCSh/EFrkuotvsH8lD0UzPOFBC2TUA56M=; b=Cz6XQnTGKGV2YS8S/6OqXPF0wnX8OjpFueLzjFZ9YPjzoo0XbsXQqQLtUAPL9wQZUv KULi1jZsD0AaxyAJhqZES3g+AnnCY72KNYlszv9aEepvLW0b0gNpXYX7mujxomzcHyVX lg6k9m1jEsIWfZAj2xDj0sB8d2h58rFhhOmhb9l8Cg8wWuUwob98//nr44Yzrd2XkN70 y7CTTo5eyx7bebnU44xj7H3UkfgX1SsCozyTLneoIXDWsN95PwSpgDZtrC5wMQhOZACd 3VAXbQ+PQi8k1kfsDXDRLlBpLT7QepLLrVna9ARQ2I81hIeIFAD3wC6u8H6iLZBxKvI0 Grug== X-Received: by 10.28.48.194 with SMTP id w185mr52440371wmw.73.1451145950338; Sat, 26 Dec 2015 08:05:50 -0800 (PST) Received: from gourin.bzh.lan (ns304657.ip-46-105-103.eu. [46.105.103.66]) by smtp.gmail.com with ESMTPSA id m65sm17787704wma.13.2015.12.26.08.05.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 26 Dec 2015 08:05:49 -0800 (PST) From: "Yann E. MORIN" To: buildroot@buildroot.org Date: Sat, 26 Dec 2015 17:05:42 +0100 Message-Id: <1c0398c75bfad861237b0ba006ac5aecf01fb5da.1451145472.git.yann.morin.1998@free.fr> X-Mailer: git-send-email 1.9.1 In-Reply-To: References: Cc: Thomas Petazzoni , "Yann E. MORIN" Subject: [Buildroot] [PATCH 2/5 v2] arch/arm: add option to enable an optional VFP unit X-BeenThere: buildroot@busybox.net X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Errors-To: buildroot-bounces@busybox.net Sender: "buildroot" Currently, the VFP selection for ARM is a little bit muddy: - some CPUs definitely do not have a VFP or NEON, - some CPUs definitely do have a VFP or NEON, - some CPUs may have a VFP or NEON. However, we currently conflate the availability of the VFP/NEON with the possibility to use them. Even is the user chooses a floating point strategy with a 'lower' solution (i.e. VFPv2 when a VFPv3 exists, or not using NEON when the CPU has it), some packages are still using the CPU-defined HW availaibility rather thean the usr's selection. Furthermore, for CPU that may have a VFP/NEON, there is no way for the user to actually specify that the HW is indeed available; the user can only specify the floating point strategy. This means that some packages or some package versions, like nodejs for example, can not be properly selected on some CPU cores, like Cortex-A9 which only may have a VFP. Like we have an option to enable an optional NEON unit, add a similar option to enable an optional VFP unit. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni --- arch/Config.in.arm | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/arch/Config.in.arm b/arch/Config.in.arm index feac16d..f2c5a58 100644 --- a/arch/Config.in.arm +++ b/arch/Config.in.arm @@ -194,6 +194,13 @@ config BR2_ARM_ENABLE_NEON Select this option if you are certain your particular implementation has NEON support and you want to use it. +config BR2_ARM_ENABLE_VFP + bool "Enable VFP extension support" + depends on BR2_ARM_CPU_MAYBE_HAS_VFPV2 + select BR2_ARM_CPU_HAS_VFPV4 if BR2_ARM_CPU_MAYBE_HAS_VFPV4 + select BR2_ARM_CPU_HAS_VFPV3 if BR2_ARM_CPU_MAYBE_HAS_VFPV3 + select BR2_ARM_CPU_HAS_VFPV2 if BR2_ARM_CPU_MAYBE_HAS_VFPV2 + choice prompt "Target ABI" depends on BR2_arm || BR2_armeb