From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 791E3C32751 for ; Wed, 31 Jul 2019 07:33:22 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4A9C2208E3 for ; Wed, 31 Jul 2019 07:33:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="cnuqToGx" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4A9C2208E3 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-ID:In-Reply-To: Date:References:Subject:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=DdsG6fxxCNlxNcvVSrVNVxbnzcrS1caOpIQjxVWsepY=; b=cnuqToGxw2r9dE vfrT0udoK5tesWQ7ZRI4q7n4r/FN72MUObT9SJt50XSvxpNaC1Xcf2mH2EvyIiDfmCq+uIAFU07Hy q+VosdcpRfAPeeQm4j7t8ai25iKYs5acZeppo1a8+f4pGhjBoBJ+JDrk5uB5NrjwTAPslZCGufF6Q HgRlDRwPRzOqbfff1FK3u37hb6ofVPB5KXnMculGsOuxL2Lz0F5mOrQy9ownXilJ3+qc5gq5IMnsh eLtfrXI6PIo0+eINSs4MyFwjupkvpor+e2m73FBdeYYb96S+PPsD0gEV0sSZavjuK9mJkgMXYpYVs eu3oZH0soRubRAGc0HJA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hsj6r-00048P-QG; Wed, 31 Jul 2019 07:33:17 +0000 Received: from mx2.suse.de ([195.135.220.15] helo=mx1.suse.de) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hsj6p-000484-55 for linux-riscv@lists.infradead.org; Wed, 31 Jul 2019 07:33:16 +0000 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 8C90CAE52; Wed, 31 Jul 2019 07:33:13 +0000 (UTC) From: Andreas Schwab To: Paul Walmsley Subject: Re: 5.3-rc2: Found incompatible CPU References: X-Yow: I'm in a twist contest!! I'm in a bathtub! It's on Mars!! I'm in tip-top condition! Date: Wed, 31 Jul 2019 09:33:13 +0200 In-Reply-To: (Paul Walmsley's message of "Tue, 30 Jul 2019 15:09:56 -0700 (PDT)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2.90 (gnu/linux) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190731_003315_343256_4D11711E X-CRM114-Status: GOOD ( 11.11 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-riscv@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org On Jul 30 2019, Paul Walmsley wrote: > On Tue, 30 Jul 2019, Andreas Schwab wrote: > >> Trying to boot 5.3-rc2 on the HiFive I'm getting "Found incompatible >> CPU" for each cpu, which means that of_device_is_compatible(node, >> "riscv") is failing. Any idea? > > Here, v5.3-rc2 boots cleanly with upstream DT data, using BBL. > > I've noticed problems in the past with some bootloader configurations when > the DT data is loaded too close to the kernel. When the kernel is > uncompressed, some or all of the DT data can be overwritten, which can > cause mysterious DT parsing problems. Using the latest openSBI (which moved the FDT further away) didn't help. A fully modular kernel isn't that big anyway. And the fact that the cpus are found in the first place tells me that the FDT is intact in general. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv