Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755218AbdLTM7f (ORCPT ); Wed, 20 Dec 2017 07:59:35 -0500 Received: from mail-oi0-f65.google.com ([209.85.218.65]:34018 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754931AbdLTM7c (ORCPT ); Wed, 20 Dec 2017 07:59:32 -0500 X-Google-Smtp-Source: ACJfBosqY3SXJxtEG4RTMhfKvp/111rzzdFFBxtaV/RwQde643A2Ho1/YrSG5wzgj/DGtQ6AEj/K65zzcEqk8CcQnsk= MIME-Version: 1.0 In-Reply-To: References: <20171116232239.16823-1-lukma@denx.de> <20171211233625.5689-1-lukma@denx.de> <1513153607.2439.2.camel@Nokia-N900> <20171217204122.0a10a5e1@jawa> <20171217222856.2c5937a4@jawa> From: Arnd Bergmann Date: Wed, 20 Dec 2017 13:59:31 +0100 X-Google-Sender-Auth: kV7ZOQJWA-7RYCBz1vn6GtDZhyU Message-ID: Subject: Re: [PATCH v5 0/4] ARM: ep93xx: ts72xx: Add support for BK3 board To: Linus Walleij Cc: Russell King , Jonas Jensen , Lukasz Majewski , Alexander Sverdlin , Hartley Sweeten , Linux ARM , Linux Kernel Mailing List , Olof Johansson Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1133 Lines: 24 On Wed, Dec 20, 2017 at 1:48 PM, Linus Walleij wrote: > On Mon, Dec 18, 2017 at 12:55 PM, Arnd Bergmann wrote: >> On Sun, Dec 17, 2017 at 10:28 PM, Lukasz Majewski wrote: >>>> It would also be helpful >>>> to test whether the -march=armv4t/--fix-v4bx workaround produces >>>> working binaries for you, in that case you could report to the gcc >>>> developers that the removal of armv4 can continue but that >>>> the --fix-v4bx option in ld needs to stay around. >>> >>> I may ask this issue on OE/Yocto mailing list as well.... >> >> To clarify, the only affected platforms are those based on either >> DEC/Intel StrongARM or Faraday FA526, i.e. EBSA-110, >> FootBridge, RPC, SA1100, Moxart and Gemini. > > It's a bit unfortunate since there are users and active contributors to > these architectures, I think the OE community is being missed out > just because they "are not Debian". :/ IIRC, OE already uses the --fix-v4bx workaround. I had an older patch to do the same in the kernel, let me resend it now, so you can try it and see if that works for you. Arnd