From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751286AbdKSDnc (ORCPT ); Sat, 18 Nov 2017 22:43:32 -0500 Received: from mail-pf0-f195.google.com ([209.85.192.195]:46809 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751072AbdKSDn1 (ORCPT ); Sat, 18 Nov 2017 22:43:27 -0500 X-Google-Smtp-Source: AGs4zMZHWEeSfCTlQhVnk8okv60lRMp3N2hcTv/YowoaZG+Hdupq0oP7UCIAtS2B2dvNAzNhhPcyBA== Date: Sat, 18 Nov 2017 19:43:25 -0800 From: Guenter Roeck To: Paul Burton Cc: linux-mips@linux-mips.org, Ralf Baechle , linux-kernel@vger.kernel.org Subject: Re: [22/26] MIPS: generic: Introduce generic DT-based board support Message-ID: <20171119034325.GA17384@roeck-us.net> References: <20160826153725.11629-23-paul.burton@imgtec.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160826153725.11629-23-paul.burton@imgtec.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 26, 2016 at 04:37:21PM +0100, Paul Burton wrote: > Introduce a "generic" platform, which aims to be board-agnostic by > making use of device trees passed by the boot protocol defined in the > MIPS UHI (Universal Hosting Interface) specification. Provision is made > for supporting boards which use a legacy boot protocol that can't be > changed, but adding support for such boards or any others is left to > followon patches. > > Right now the built kernels expect to be loaded to 0x80100000, ie. in > kseg0. This is fine for the vast majority of MIPS platforms, but > nevertheless it would be good to remove this limitation in the future by > mapping the kernel via the TLB such that it can be loaded anywhere & map > itself appropriately. > > Configuration is handled by dynamically generating configs using > scripts/kconfig/merge_config.sh, somewhat similar to the way powerpc > makes use of it. This allows for variations upon the configuration, eg. > differing architecture revisions or subsets of driver support for > differing boards, to be handled without having a large number of > defconfig files. > > Signed-off-by: Paul Burton Guess it is known that this patch causes failures when building "allmodconfig" on test systems such as 0day; it was reported by 0day some two months ago. nevertheless, the patch found its way into mainline without fix. Does anyone care, or should I simply disable "allmodconfig" test builds for mips ? Guenter