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.3 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 D2F8EC43603 for ; Fri, 6 Dec 2019 12:38:46 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (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 8103221835 for ; Fri, 6 Dec 2019 12:38:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="jNzg9DxI" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8103221835 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.92.3) (envelope-from ) id 1idCs1-0004Dq-6a; Fri, 06 Dec 2019 07:38:05 -0500 Received: from mail-wm1-x332.google.com ([2a00:1450:4864:20::332]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1idCrx-0004Dk-N1 for kernelnewbies@kernelnewbies.org; Fri, 06 Dec 2019 07:38:01 -0500 Received: by mail-wm1-x332.google.com with SMTP id b11so7656742wmj.4 for ; Fri, 06 Dec 2019 04:38:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CX3o7igZwWMcuQypGn5lah5EGokKmwlBrg9hkBQi33s=; b=jNzg9DxIQiPonE34JuZ7U7lWxCrsZ296Hh6jlHQJjTaohgeP6NZjBawvHF30emj/MB yBVzFxm2cQUsFu/x+NyfJrOCtrGMfXiWZVogzwinWFsHegwT/QLG3FFxvJ33EjRk2R2I YivKJ5fLBM1Wz9FzFH8cYTLJQwWWoj6ZetaJOW6ja3hlm9EJQwGQKrf7xQUo7wY+9Mf0 1DpKFA4IvJZoc2IqmvQyRrrf1XfsW+pM1zrboQ+wYtykzNUq5W7aPSTim6al1WWWPpPp EqonxtudvmC/tUFakNrzFaTZBaRYg2oFDahPl3WCni3rIFlthcnjr/ImGy/8ZFUYbDNi JH9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CX3o7igZwWMcuQypGn5lah5EGokKmwlBrg9hkBQi33s=; b=GBGZiN/B/rq001yQwkQq43TMTjujJsXyOXq75UitbvyehvFZQqnu7K5oOGPQVzZuZy 7ErYfybwzYw9GBDttRDI2Hs7ugGdOKgJlMHqZypNWYYGiQFgDYn8oF+KrQ5jy6f2x47m FcFXXRBsVGuVz/Lyk40rmxC/3oc3uSRqmbDsI3FkB3iPSLI/mbZOYofx98fV5LqSNvpD 6D5UJh6+iMVhzywrOxPM61GLRE+JrHmjMRSnp5EVxk2jAX6oUUqP1H1lFUw8tthYhglQ n4HGH+e1qEzhar95hmeqO5WDItKeW3z0e0iZUaXKzfwzasIUQNBPoXvQ71o4RGFdgnq0 LgbQ== X-Gm-Message-State: APjAAAW26HXGI4C+U0qPCSFGfK/2L2WOn79T/wOxm9xg79H4Yii1PzTA 8JYFG8+fnEhJuajXDUFCpMmf56eGV4xkOQBbL/0= X-Google-Smtp-Source: APXvYqxOXHB5grBkqiNFQS10LAxUTYdpkwHVNaaYTpRj6vdExwbIMFONPGDB49AKy2vdIkKgHfnm5Q5LYX7eBJst3go= X-Received: by 2002:a1c:8095:: with SMTP id b143mr10943718wmd.7.1575635879117; Fri, 06 Dec 2019 04:37:59 -0800 (PST) MIME-Version: 1.0 References: <85045.1575631571@turing-police> In-Reply-To: <85045.1575631571@turing-police> From: Tomek Domek Date: Fri, 6 Dec 2019 13:37:48 +0100 Message-ID: Subject: Re: Missing FDT description in DTB To: =?UTF-8?Q?Valdis_Kl=C4=93tnieks?= Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9160970795736369553==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============9160970795736369553== Content-Type: multipart/alternative; boundary="000000000000dec9c005990850d4" --000000000000dec9c005990850d4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Yes, it is for bringup purpose. We have working uboot software and we split the code in order to have FSBL and SSBL and I had such problem but it was a matter of deleting "-f auto" and -E option from mkimage for building u-boot.img. Now FSBL, SSBL and kernel starts successfully. pt., 6 gru 2019 o 12:26 Valdis Kl=C4=93tnieks napisa=C5=82(a): > On Fri, 06 Dec 2019 10:03:34 +0100, Tomek Domek said: > > > And this uboot and spl is somekind of experimental software which is i= n > > the middle of creation. Could anyone try to guide what might be possibl= e > > the reason of the issue as I am a bit new in u-boot development? > > Is there a reason why you're using an experimental uboot/spl rather than > a known-stable working version for whatever hardware this is? > > (Of course, if this is bring-up of a new architecture that has never been > supported by uboot, so there's never been a working uboot for the device= , > it's > time to quote the movie Animal House: "My advice to you is to start > drinking > heavily") > > --000000000000dec9c005990850d4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes, it is for bringup purpose. We have working uboot soft= ware and we split the code in order to have FSBL and SSBL and I had such pr= oblem but it was a matter of deleting "-f auto" and -E option fro= m mkimage for building u-boot.img. Now FSBL, SSBL and kernel starts success= fully.

pt., 6 gru 2019 o 12:26=C2=A0Valdis Kl=C4=93tnieks <valdis.kletnieks@vt.edu> napisa=C5=82(a= ):
On Fri, 06 De= c 2019 10:03:34 +0100, Tomek Domek said:

>=C2=A0 And this uboot and spl is somekind of experimental software whic= h is in
> the middle of creation. Could anyone try to guide what might be possib= le
> the reason of the issue as I am a bit new in u-boot development?

Is there a reason why you're using an experimental uboot/spl rather tha= n
a known-stable working version for whatever hardware this is?

(Of course, if this is bring-up of a new architecture that has never been supported by uboot, so there's never been a=C2=A0 working uboot for the= device, it's
time to quote the movie Animal House: "My advice to you is to start dr= inking
heavily")

--000000000000dec9c005990850d4-- --===============9160970795736369553== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============9160970795736369553==--