From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7062708050763710464 X-Received: by 2002:a1c:a595:: with SMTP id o143mr1132492wme.78.1644480756455; Thu, 10 Feb 2022 00:12:36 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:a3d0:: with SMTP id m16ls193311wrb.3.gmail; Thu, 10 Feb 2022 00:12:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJxthsc99w2dl7CUapjlnOAxTwvfwisX4KelQrsEBZcoWh4fzyFe3AF6cGoHaEIbhtPMYV0H X-Received: by 2002:a05:6000:1548:: with SMTP id 8mr5556411wry.232.1644480755736; Thu, 10 Feb 2022 00:12:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644480755; cv=none; d=google.com; s=arc-20160816; b=ypWfqKVgIgNBGH2dEPew5b09T1H0Z0pZZ3hHOo56PRNSMQxLv0bWDMYXgGrYILvr50 KRZneuH9rD/m50NKBda3444YtdY5+yibQu0jMImjovGsx8zd6cNRmAwVdB/tdR+dz0zo e6iuRn0MSsWiOcwn6AKRjcuYNQo9DdR9z9V8eO0WmraSlzjjEET7KeQQiRjtzxmQMP5K W1oUlr260hY8hTsoXovCt0TVb+jaLOOt4wgt441EZIijf7idrpRIgqskO/cm+JnJzhCo HfAM6Ff9wVxEQiydNpfudjJGy94IPADb5IgoDHTcDyj3U5vE/FZJ7iBl3FOsOS2Fg+JQ EDHQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-language:content-transfer-encoding:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject; bh=n7IHQ7BpE6QijWMbdvQFjfLuQa7pC1TdTYd9nhKzuRU=; b=yxDJm1vuscjoTLsAuD6X4iJX7AEt5oogId92DFi7Z1MyYWw2zd4+thTaDMELiV4MAW l+9wDqz65DqPnw+K/ZSG8ATSQRaw3T+JcG9w3P9xb9m3jJc/iMUtSc3KcgHuxs/LlVEn 72weTt9ynZF/nZIRXY8RsTHnrvyxyTupod52cGNkK2+wia4mL+/sZLFg0DzW7PEsFnAl jh2ilQydIeRMt1NLh5g7SBhTeWAeSEirqhtk0W5u2S0Brgyh0O82v7/NdwQ4W0c7+Yma u4GehPkuQZWUBvu+HfFTxpFZmpJeMpOsBO6Y4YPGo5TlqLvqFDKIl6XZ0/gUPjsJlblC ov8A== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=amikan@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id be15si44334wmb.0.2022.02.10.00.12.35 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Thu, 10 Feb 2022 00:12:35 -0800 (PST) Received-SPF: pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=amikan@ilbers.de Received: from [127.0.0.1] (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id 21A8CXMm028775 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 10 Feb 2022 09:12:34 +0100 Subject: Re: [PATCH 0/7] Rebuild phyBOARD-Mira UBI image generation To: "Schmidt, Adriaan" , "isar-users@googlegroups.com" References: <20220209135411.1313521-1-amikan@ilbers.de> From: Anton Mikanovich Message-ID: Date: Thu, 10 Feb 2022 11:12:33 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: D8/v3TKE2iMv 10.02.2022 09:52, Schmidt, Adriaan wrote: > Anton Mikanovich, 9. Februar 2022 14:54: >> Rebuild UBI image generation implementation to support any count of >> targets with different settings. This also will allow to build the same >> isar-image-base image for both UBI and non-UBI targets. >> Add correct UBI and UBIFS layouts for phyBOARD-Mira after that. > I've just posted a proposal to generally rework image generation > ([PATCH 0/6] imagetypes), which overlaps with your patches 1..3. > I admit that I don't fully understand the ubi(-ubifs) process, so my series > might actually break something here. But I can imagine that your image > changes could also get simpler if you put them on top of my imagetypes > patches. > > Adriaan The main idea here was to get rid of the old way of using complex image types (like existing fit image + ubifs image packed inside ubi image) when new custom image type need to be created for any custom config (like fit+ubifs->ubi, ubifs->ubi, etc). The new way allows us just to mention all images included. It looks like your approach will not brake things too much to implement the same changes after rebase on it.