Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp115313pxb; Thu, 21 Jan 2021 02:49:21 -0800 (PST) X-Google-Smtp-Source: ABdhPJz9GUTmBStPVsUIP8g4hW3va6ZAqtSBtXaQzk8ZoN8xmHu+7Cfx8YHHXZPaVXqKm6MzTMk+ X-Received: by 2002:a05:6402:2683:: with SMTP id w3mr10563111edd.378.1611226161134; Thu, 21 Jan 2021 02:49:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611226161; cv=none; d=google.com; s=arc-20160816; b=MUcGHum0CF4oz+30PDYlQT5Ut66yL4ok7Bff04lEqWAlQIuCqDuNyzZLL7HoTXJbQg 3JRWKV1WXJBpzHF/NREXDz7ZEpMKG/vB5TRcMiD1AqbY/t7rrGMAHoX9HQ8BtBhxozN2 4Xo+WqYhdeJWu0EFZ3w5VaTbjtXFluOwM3A2oEl+3ehTR0+T1UfyVq3bglRNJJbW7EqI oFppmnkJ/NWo610jisQMiu4ip00CV/ycIKBuyJeVs4OZ6J7GbdJ7m5/rvUFP5iOSpcwE PqOmnhzZP6WQNnhOR5+sbp2omW4XY0pU8X21MfDDSF0hJeoOgRl0qVhMSF/9OUnx7x6Y LCgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:user-agent:references:in-reply-to :subject:cc:to:from:date:content-transfer-encoding:mime-version :dkim-signature; bh=JDILWN2Qt0CRRMnHqdXZCjQvogas/S8Dy2MJuaJxQKk=; b=ojqCzAMKOt/kxNc1icP05OdGEeAplXfWcRUOyMLIJ0wl8Blcr8dA2JEhaTsGtVYJIt DyDkj+EWTyh3wsVXiw2da5AMG0sDkDiubMTnL0GjIUVXbq0zsUbT0n3eigQ85GYOb77N soWcJNnrNxkjRx1meB7Xoj/hfiicPrdoZ0olu7ciWT3GFKPRRrZomz+8vd5VOa3D8tDK Yu963bepCfTAYKGPTm0E0I73P2r1Gd9TvzEIhPLtGzYp3aZSuVgp5+kBguwVGjkVcinh QfviAmzITB3PaIlNQYBlbsP7sG/fey8hM+uhfx8ZfGNM5A6xEZRCM4PxxbWj8L7RYvb/ CMew== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2016061301 header.b="jC+SKLV/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z24si1931549edx.302.2021.01.21.02.48.57; Thu, 21 Jan 2021 02:49:21 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2016061301 header.b="jC+SKLV/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729833AbhAUKqj (ORCPT + 99 others); Thu, 21 Jan 2021 05:46:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59680 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729366AbhAUKmK (ORCPT ); Thu, 21 Jan 2021 05:42:10 -0500 Received: from ssl.serverraum.org (ssl.serverraum.org [IPv6:2a01:4f8:151:8464::1:2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B0278C0613D3; Thu, 21 Jan 2021 02:41:28 -0800 (PST) Received: from ssl.serverraum.org (web.serverraum.org [172.16.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id 0B01622FAD; Thu, 21 Jan 2021 11:41:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1611225687; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JDILWN2Qt0CRRMnHqdXZCjQvogas/S8Dy2MJuaJxQKk=; b=jC+SKLV/orq38gIrVKvQRdKd4J76RPnn0LqF4Vr8EwOfVD+f7XzPpnSFWHjDxMBql+/Ieb SUfOJajVatGzvLP2keWDGOdIYF9LNZAo00vXfO4Hil4mGO+XRb/PAOiOw1/hH5jsZbW4jp fyYxBLtSI35wjK6PQLFjp3ngBkrfckQ= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 21 Jan 2021 11:41:26 +0100 From: Michael Walle To: Michal Simek Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Rob Herring , Arnd Bergmann , Olof Johansson , soc@kernel.org Subject: Re: [PATCH 0/3] add Ebang EBAZ4205 support In-Reply-To: <8917c9a1-09e9-0a39-5732-da7f555ae9ad@xilinx.com> References: <20210120194033.26970-1-michael@walle.cc> <0a1c6ebf-1d5b-4f06-56db-f04e87d2ae9a@xilinx.com> <8917c9a1-09e9-0a39-5732-da7f555ae9ad@xilinx.com> User-Agent: Roundcube Webmail/1.4.10 Message-ID: X-Sender: michael@walle.cc Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Am 2021-01-21 11:23, schrieb Michal Simek: >>> Back to your case. Board is cheap which is not all the time case for >>> any >>> xilinx board but you have only uart, sd and partially described >>> ethernet >>> which doesn't work without PL. Is it worth to have this described? >> >> I got your point. But it is at least a jump start for the users if >> that >> board boots out of the box. And yes, its unfortunate, that ethernet >> just works if the PL is configured. This is already done by the >> bootloader, because there I do have the same problem. > > Zynq/ZynqMP boards can use U-Boot SPL. "Advantage" of this solution > especially for Zynq is that in u-boot there is open a way for adding > ps7_init file which is determined by device tree name. > I think it would make sense to add these DTs and also ps7_init to > U-Boot > project and wire it up with zynq_virt platform and then you can boot > Linux with using U-Boot's DT pointed by $fdtcontroladdr. > Then you will get support from scratch to be able to boot. I already have patches for u-boot (using SPL). But my impression was that linux is the master for the device trees. Esp. if there are some problems with the board its often useful to have an in-tree device tree. What is the difference between this board and the other zynq boards in the kernel? In any case, please make this decision now: will you accept this device tree or not? -michael