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 Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C9F51C433EF for ; Mon, 29 Nov 2021 22:12:25 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 8BE6D82FE7; Mon, 29 Nov 2021 23:12:22 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="F8zjnjZ8"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 2B60480934; Mon, 29 Nov 2021 23:12:20 +0100 (CET) Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 58F5A82FD0 for ; Mon, 29 Nov 2021 23:12:16 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=mr.nuke.me@gmail.com Received: by mail-ot1-x32b.google.com with SMTP id n104-20020a9d2071000000b005799790cf0bso27553446ota.5 for ; Mon, 29 Nov 2021 14:12:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=0bN5Kd/MNiMlhEgSLBOx5KxR8l1LAcL0ZNlEAsMSal4=; b=F8zjnjZ8Pe1ysObo3C4miPoxzQoObC4kQ8NiyVHkLWlOjJJUf+TjtnbbzjtslZVNh8 JROZ3G6ODYHgOJDw7hpueelJfFjS/W9igvfodQSbDImc6HeuDOwpsqwE6pUxaZZd31dW J+p1nlFyk58RCJarAoorH5fMRJWbtYbHAN5jpFJwPhcB6ZYIzY3urzD/I452lOvfUOJv QgglR8u8MWAHaHauiFG8sKe6lC9vJDTTs23lZk5tV+5mqYuBVAiN4mVK6yk1ZiswKIM7 VxDR3ULjMRkFA8glGxhqjrzjIbPrcFzLXUTdor9gSNsdZkR0v5KBQIjluGEM6x9vRNaF NG8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=0bN5Kd/MNiMlhEgSLBOx5KxR8l1LAcL0ZNlEAsMSal4=; b=flF73XsZItsncVJCC2Epw/QK4l+3rdpmQEOi4AvQltN/FkVITBUGACWaCeWiOAWPn4 2IXItG1O7KTXYS38ZJg9F91IxCcIDTLva8KD1G/CHrUr0R7doX6F7IvMevfCMLDFWDm5 rurNwSVvAqf6H+zdIwfSMk5Fm+/ky/Jl4VxP2RvD6g6rBIB2BA1HPwkmuHi1HGM2oh58 R/Q2KcvWOpatF5WcwqhqQsRuEsA9ClpkQNYH3mSJ7M+deReFD++/h8A9ShHBJcIG+Ecw ft7NKnLaik9zOuRUFY3IpQGb9Nb26L3+V5R1OP6F+b8PyV3ErbUEfDM7veocihQHVM/s E9mw== X-Gm-Message-State: AOAM532i/fnAeaXUyKovrL+89RIlA9ZwJjMll80wAsQ0pinFbVjpWy6S 62MrT/ddJXhEi3FkBHdIpS89N4SCbWI= X-Google-Smtp-Source: ABdhPJzZnxG79evgGzV61+C4kMKQENB3eC6DEan/DxHsamrpLfO2wZtu9VoVOf1DYOQNy5rK3k8NvA== X-Received: by 2002:a9d:2aa3:: with SMTP id e32mr46978925otb.6.1638223934222; Mon, 29 Nov 2021 14:12:14 -0800 (PST) Received: from nuclearis3.gtech (c-98-195-139-126.hsd1.tx.comcast.net. [98.195.139.126]) by smtp.gmail.com with ESMTPSA id 184sm2058013oih.58.2021.11.29.14.12.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 29 Nov 2021 14:12:13 -0800 (PST) Subject: Re: a question about falcon mode To: Abder Cc: Chan Kim , U-Boot Mailing List References: <027001d7e1cb$14bc3b90$3e34b2b0$@etri.re.kr> <27ce6d77-2a3e-a9e2-cce2-00f76d7af57e@gmail.com> From: "Alex G." Message-ID: <77f0b37f-3e1f-168b-b577-835cbcd9506c@gmail.com> Date: Mon, 29 Nov 2021 16:12:12 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.37 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean On 11/26/21 4:36 PM, Abder wrote: > Hi Alex, > > Just a quick remarque that intrigued me: > > Le jeu. 25 nov. 2021 à 15:57, Alex G. a écrit : >> >> On 11/25/21 1:07 AM, Chan Kim wrote: >>> Hello all, >>> >>> I'm trying to implement falcon mode for our board. Then should I first >>> implement the normal mode(spl + proper)? >>> >>> It looks like so while I'm reading doc/README.falcon. (It says, after >>> loading kernel, DT etc. I should give 'spl export' command). >>> >> >> Falcon mode is a bit board dependent. There are a couple of ways you >> could go about this. >> >> The first is to have an "fdtargs" partition. This is where "spl export" >> comes in. Once you run "spl export", it will give a modified dtb at >> "$fdtargsaddr". It's that DTB that you need to write to your ftdargs >> partition. For example: >> >> > spl export fdt $loadaddr - $fdt_addr_r >> > mmc write $fdtargsaddr 0x9800 0x8000 >> >> In this example the ftdargs partition starts at sector 0x9800, and is >> 0x800 sectors long. >> >> >> The second option is to forget about "spl export" and "fdtargs", and >> package your kernel, devicetree, and overlays in a FIT container. You'd >> make sure to enable SPL_LOAD_FIT_APPLY_OVERLAY. There isn't much more to >> this other than the usual gotcha's with FIT and overlays. >> > > Do you mean by this that the SPL has the capability to generate the > "fdtargs" by it self (if we provide it with the dtb in the fitImage) ? > > Form my last experience with the falcon mode, I had a - not sure - > conclusion that the only way to generate the "fdtargs" is by using the > "spl export" command from uboot cmdline ! > because the reality of the fdtargs blob, as its name indicates, is not > just the fdt but it has also the bootargs (inside the chosen node ) > that are required by the kernel. So if you give only the DTB to the > SPL it will not work - to my knowledge -, cuz the data that will be > passed to the kernel needs to contain also the bootargs ! > > Can you please confirm to me if this capability is implemented on the > SPL and that we can actually forget about the "spl export" command ? It might not be obvious that an overlay can contain the "/chosen" node with the appropriate bootargs: /dts-v1/; /plugin/; / { fragment@1 { target-path = "/chosen"; __overlay__ { bootargs = "root=blablabla console=ttyeS0"; }; }; }; > Thanks > And apologies Chan for jumping on your thread, > > > Best regards, > -- > Abder >