From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id E8C026EF17; Mon, 20 Jun 2022 10:30:08 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 496) id 4D0396EEAD; Mon, 20 Jun 2022 10:30:06 +0000 (UTC) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) by atuin.qyliss.net (Postfix) with ESMTPS id 759AC6EF02 for ; Mon, 20 Jun 2022 10:30:03 +0000 (UTC) Received: by mail-ed1-x532.google.com with SMTP id e2so3528942edv.3 for ; Mon, 20 Jun 2022 03:30:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unikie.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=5LMHAE3aDdGM+a/HkAR9JkXL4lAOIqwQpZFSQO25yLk=; b=jEUHq+QE0E4wG5F8+MsuICCvqt8NNfnq+gxIDwIlMRXP9dIMxoJqw6vWtZk+arv9Ib si+sVRmZGjjuOYuOqwt06U/C5GVaaiB/i1cn66E8ks/M4pq9Csc0oP8n/ISKNgU7OqUB AELZi01a3vhMI+5wNGb7wElz64DjPnzt5Bj6O55VngYJYOp6LWdGucvku44TDFwknynh 6gwUXAKRbaLyID69xGFa1cgFQ6/eEExvBABl5I5OEGRqrh59Q3orUnVD0o1Cw9z6BIIA 2vZ9zO/9r6G1vTL8oXYQQ5KcqSpZIzQQMPtpZGKRCkKN+YLJkY3sVsbOJUJVZ9KU/xLQ xamw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5LMHAE3aDdGM+a/HkAR9JkXL4lAOIqwQpZFSQO25yLk=; b=d2z8kBC+qj9Sn09JrbVgHQWVbmZc8xpiHPSqw+5AXYa0fdTD3jnQTa43HmQkmCFo5Z jdV1UbbzrYkEBx1HlejXa75bcyPWMhUx11nx1NEQhXyMbikbeg6WMZaz5J29OmWn3kef vAd1aQNUzg5QY0sXFz78LgYCGrxHz88lZON0i+onsGTzaGRvfvYwAAoC3SXpZ5bMuKF3 BRfkLgCsrzNI2K/ipJr3BYGmTXWVVS4aIGMV7Q/2ZidGbV1FXGWvFjCXAAiO2LvG707z 6QMA3RR6DZNbtTA5Eb0z8R+v+boBP+jnMnc3iml8m08Sq8hTp/GUbNaYIxuLwGpjIMHV tGmQ== X-Gm-Message-State: AJIora+M7o6WZBQo0HTl1GLkH6uys+EJyI8o4rItnZMoscViZlmQdVSA Zr4PJWOE2TTdI5awJ9f2Z1YSOH/+R3u1RKGNZZsyAufWUzzcRw== X-Google-Smtp-Source: AGRyM1tuMFxsdFZe0Eetpgbqx1+pHenuxz96YLPNJtLlfbJa9XpvhDQ0xvqPSP30qDDT9QQExRrI2ZG128xIoY2kN5w= X-Received: by 2002:a50:fe98:0:b0:435:a8b:c4c3 with SMTP id d24-20020a50fe98000000b004350a8bc4c3mr29089916edt.78.1655721000133; Mon, 20 Jun 2022 03:30:00 -0700 (PDT) MIME-Version: 1.0 From: Ville Ilvonen Date: Mon, 20 Jun 2022 13:29:49 +0300 Message-ID: Subject: Workflow preferences - case aarch64 support To: discuss@spectrum-os.org Content-Type: text/plain; charset="UTF-8" Message-ID-Hash: Z5F5WZV6OOQO3VPCRDPXKGUUE6XAOXNL X-Message-ID-Hash: Z5F5WZV6OOQO3VPCRDPXKGUUE6XAOXNL X-MailFrom: ville.ilvonen@unikie.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-config-1; header-match-discuss.spectrum-os.org-0; header-match-discuss.spectrum-os.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.5 Precedence: list List-Id: General high-level discussion about Spectrum Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Hi all, Good news is that the work on aarch64 support has progressed to the point where the Spectrum host can be built natively and run on aarch64 HW. It's still a bunch of patches in various stages of WIP or review to spectrum or further up the stream. In short, to "nixpkgs-spectrum": 0001-Allow-static-building-of-dtc.patch 0002-Workaround-ld-script-segmentation-fault.patch /* may be not needed */ 0003-Add-imx8-specific-kernel.patch and to "spectrum": 0001-Add-imx8-kernel.patch Should anyone want to reproduce, please let me know and I'll try to find a solution to share them. Probably worth waiting for cross-compilation support unless you have powerful aarch64 at your disposal. In the meanwhile, we try to establish a mechanism to collaborate in branches of required upstream repos. It's fairly impractical to fork "nixpkgs-spectrum"-repo due to its' size, over 2GB, Which takes me to the discussion point - what's the workflow proposal on multiple people working on the same functionality in the same branch? If I'm not mistaken the email workflow creates a new branch for each author? Then someone would have to cherry-pick them to the same branch to integrate them in dev time hydra builds. Best, -Ville