From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6698864930987180032 X-Received: by 2002:a1c:f916:: with SMTP id x22mr7841884wmh.81.1559713920868; Tue, 04 Jun 2019 22:52:00 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a5d:4e8c:: with SMTP id e12ls182607wru.2.gmail; Tue, 04 Jun 2019 22:52:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqx6iY/GtHHbt5USzvE3vwxwl9Q3UmdIFwLJIy3fuBGzE4Hdu2dOt6q1VZ6mpYY2ft5LuoDb X-Received: by 2002:a05:6000:a:: with SMTP id h10mr3119562wrx.215.1559713920376; Tue, 04 Jun 2019 22:52:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559713920; cv=none; d=google.com; s=arc-20160816; b=f4bh0kcuFOcYEBQ3EXYck2JnjAiFl8EBYRQjCbt2tT/EYbiLW4epmSRaubmx/cFJGI PYdMuVNfdRQdflbBdgZk13VqYF7vqhBHixLxy6LOvOksI2Bmy6t7oYTKJuSUjcNS96n2 jb3r+DnfuoZapdwgG3zfLYGmx+47ZBjlNfknaKBht9PeKRvYQ0CU5p1IkKq06FnZQ3s4 l1wQJTTWjxVQ93vF0oAWxByFj9VJYfpqnIq32l+qfB3jnz2TUF9mKcSRMjbJAiSiGb6H 9ebBMFvjcYow5ArUl4NcvGylE4CIRBy0ZBelFfpIjcOxUcyzcJSAK/yFgJPV3sdpIemw CymQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject; bh=9mCxmU2y9B8n+g95S6GiityQlHOoFMuRBB34obsH6Wc=; b=BMBEiusw43VPhiwt48oxKRrc6UQwSLqMaPdyQpxgUczezltBSnuNsxHcGST0mFsHzB QLv6hnOFN+ThZbmjrCqUV0mT2dIbSfRB3MRxGkDzQuEhDi3vt2jyGdNDc0yIbMzFFhW1 w6LyBzqoJtNiT1criMn35SlSucbLYfoH3pmjg31bLvukR4fP2gggBojHv0dJhLOhacSY D3AfQhHXui5qvvlRIk4DAwNf8XXOiuoARtQDtHap5cCQYTiTku3ytoA1zTucUGOiLLJl lASwx5QOx+DG0gbOp/ukmyUQ8adOh+rUdGmduNE7Vq2AoXyFntNfD7K8aQS92L92iFCk SAMA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id x6si1029169wmh.1.2019.06.04.22.52.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Jun 2019 22:52:00 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x555pxp6008211 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 5 Jun 2019 07:52:00 +0200 Received: from [167.87.9.211] ([167.87.9.211]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x555pwfA019438; Wed, 5 Jun 2019 07:51:58 +0200 Subject: Re: porting iwg20m to isar-cip-core To: daniel.sangorrin@toshiba.co.jp, cip-dev@lists.cip-project.org, isar-users@googlegroups.com References: <20190605021645.4464-1-daniel.sangorrin@toshiba.co.jp> From: Jan Kiszka Message-ID: Date: Wed, 5 Jun 2019 07:51:58 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: uSuXL8vAELSM On 05.06.19 07:34, daniel.sangorrin@toshiba.co.jp wrote: >> I tried to add a recipe for iwg20m's u-boot. That board >> only supports version 2013.01 and does not support distro boot. > [snip] >> As for the kernel image location, since we do not have u-boot >> distro support I will move it manually from the root partition >> to the boot partition using a postinstall script inside the >> customizations recipe. If there is a better option please >> let me know. > > OK, I figured it out. I just had to define KERNEL_IMAGE="zImage" (so that it gets deployed) and then add that variable to IMAGE_BOOT_FILES. > I would definitely recommend following the pre-existing pattern as they are working on a lot of different boards already. Primarily on ARMv8 (where most things are much better), but also on quite a few ARMv7 boards. That will avoid having to invent too much board-specific things over and over again. Missing distro boot is a PITA, I know, but the best workaround is specifying what missing command the user should inject into the legacy U-Boot so that it loads the boot.scr from the rootfs and has the required board-specific env vars set. If you can even rebuild the U-Boot, you may also inject those commands into the default env, just by enhancing the defconfig. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux