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 EA6DCC433FE for ; Mon, 7 Nov 2022 23:37:30 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 00F5885110; Tue, 8 Nov 2022 00:36:49 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; unprotected) header.d=chromium.org header.i=@chromium.org header.b="AIJJ0jBP"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 1412885110; Tue, 8 Nov 2022 00:36:48 +0100 (CET) Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 3FFF285116 for ; Tue, 8 Nov 2022 00:36:43 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=sjg@google.com Received: by mail-io1-xd2c.google.com with SMTP id b2so10209742iof.12 for ; Mon, 07 Nov 2022 15:36:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=WhqlJ7rl7Qm8DJfhM+8rm6tRr4nWK9N9VZFAWlcv37U=; b=AIJJ0jBPkOWANccUk3Xp2tLyAZLSughVf8ZnDDZ+t8szzAOxxka7uT8DlSUZ2bN+kA 4KXP6eLBdCsyUWHIA071GlmKdkhswzQw806yFil3hPjT74TWJ29rS5WEH+SruyBduC7j S4CGxus9mYm93tEH3TV3suynAZhEQSQN3rkjI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=WhqlJ7rl7Qm8DJfhM+8rm6tRr4nWK9N9VZFAWlcv37U=; b=h81XZzhaTNAUiQFNBGI1ypTY644X5zGDm/qrrrtlRks3yXtAFfhZTZllFILL+nQAJj PqQ6RuvmYbVNAGUa4ixc5WNJQGojF0wHoditVwSLJqlRjt5TMHsuBj3gTFT9PDX18ziK m0k5OhpActYj9HVW5305v5MBKHQyrDX5lZZyPj/YNkUIFRWb4joiy2N6hQif9ZpmzRzZ PdbXbkHtU3A5navy0oHTjy7O4gQamOK12I1QHOdEHD6dSZhzZml/irNaRAlQryavaNxK PayFf76gq7iJpBLHpziguRi7AQA5Zyvjzsyegriu7vvwssrMgHTIgIz93rgdKqCwsHuw uJ6A== X-Gm-Message-State: ACrzQf3uoYbM5e3U8iB+MUjj/kJLtL/aJyYcZeupYmpbC5l18xJHN5VL kHS69tkZP90rYohZilu+fqs7fSXYTBZe+4N5NYUjnA== X-Google-Smtp-Source: AMsMyM675ng4UqnCUOowXE4f2nxU8LG+IPRGieWKlFJ6YRwojQIvfaolL4kudX1yWXuc4TJtTK8IZBoOhsCS8i8dgVk= X-Received: by 2002:a02:3b68:0:b0:375:6a72:914f with SMTP id i40-20020a023b68000000b003756a72914fmr24046928jaf.26.1667864201548; Mon, 07 Nov 2022 15:36:41 -0800 (PST) MIME-Version: 1.0 References: <20220925150248.2524421-1-sjg@chromium.org> <20220925150248.2524421-21-sjg@chromium.org> <118b0cb6-ba55-2022-fa85-02ebf0df6c43@gmx.de> In-Reply-To: <118b0cb6-ba55-2022-fa85-02ebf0df6c43@gmx.de> From: Simon Glass Date: Mon, 7 Nov 2022 16:35:44 -0700 Message-ID: Subject: Re: [PATCH 20/45] sandbox: Add a way to specify the sandbox executable To: Heinrich Schuchardt Cc: Tom Rini , Andrew Scull , U-Boot Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 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.6 at phobos.denx.de X-Virus-Status: Clean Hi Heinrich, On Mon, 26 Sept 2022 at 00:49, Heinrich Schuchardt wrote: > > On 9/25/22 17:02, Simon Glass wrote: > > At present the sandbox executable is assumed to be arg[0] but this only > > works for a single jump (e.g. from SPL to U-Boot). Add a new arg to solve > > this issue, along with a detailed comment. > > What is the impact on os_relaunch()? > With current origin/master it fails on SPL: > > $ spl/u-boot-spl -S > > U-Boot SPL 2022.10-rc5-00012-g435596d57f (Sep 26 2022 - 08:40:30 +0200) > Creating new bloblist size 400 at c000 > Finished bloblist size 400 at c000 > Finished bloblist size 400 at c000 > Found existing bloblist size 400 at c000 > > > U-Boot 2022.10-rc5-00012-g435596d57f (Sep 26 2022 - 08:40:30 +0200) > > DRAM: 256 MiB > Core: 23 devices, 11 uclasses, devicetree: board > MMC: > Loading Environment from nowhere... OK > In: serial > Out: serial > Err: serial > Net: No ethernet found. > Hit any key to stop autoboot: 0 > => reset > resetting ... > Finished bloblist size 400 at bffd000 > Failed to read RAM buffer '/tmp/u-boot.mem.LypddQ': -1 > Expected bloblist at c000 not found (err=-2) > Creating new bloblist size 400 at c000 > > > U-Boot 2022.10-rc5-00012-g435596d57f (Sep 26 2022 - 08:40:30 +0200) > > u-boot: error: failed while parsing option: memory > try running with --help for more information. This does not change the behaviour of os_relaunch(), but I think it would be possible to use the argument to avoid this failure. Regards, Simon