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=-3.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,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 4E027C4BA0D for ; Wed, 26 Feb 2020 04:46:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DEC50222C2 for ; Wed, 26 Feb 2020 04:46:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="ofvWS/in" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726112AbgBZEqB (ORCPT ); Tue, 25 Feb 2020 23:46:01 -0500 Received: from mail-oi1-f193.google.com ([209.85.167.193]:42109 "EHLO mail-oi1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726039AbgBZEqB (ORCPT ); Tue, 25 Feb 2020 23:46:01 -0500 Received: by mail-oi1-f193.google.com with SMTP id j132so1727089oih.9 for ; Tue, 25 Feb 2020 20:46:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EKUyDP4lZW18OTJVqKNfcbTr/pNluBP+Ac8mA7k4evM=; b=ofvWS/inAusVCo3l1y8QovhX4A7p7BrHR3o/38cH5h/oY+oPPGklAZwzipfIf14QU6 potN5ZirnfbpuqlD3FbwCDt68S2VNziAe29j031oaTGqS5jme9cfqbcq9aS2Ev3tHZ+Y 4l+XyIFM0jvqUyCko5LHBk01vlk6v3SmOhxMU= 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=EKUyDP4lZW18OTJVqKNfcbTr/pNluBP+Ac8mA7k4evM=; b=W/RxRKOujBN3tC56Y1IAWvrv2WJDxe+fnsxMUdPuxNsZlHSmlxm/wuovf4lIil1+oc 8i5/bfc8ct7HtuGQqBYRu6bVXm9n715S0CMSZhDYQNDCHCuBr7DvO9JzcuhT4FMUSyyj D2kxykXDRWPnYlo7xOpPdJlD/oyWs9qAsiWFcf/FaiMaWEpy+4SUu5Pxz+SAnGCq7ppD xCL0qzjxH1NhqoRq/cIRHzCAwcok4cU84RgQC0FzgY7r1nBjgEVozk3eFP7ZaH14zXl2 iHrNFi0n4LYZWIBFAEuGfPkMk9A9XsSte7J64bDEpdI6AHnF4tsXqNKTgs+ynoRAED9P vG7w== X-Gm-Message-State: APjAAAVxqFvxCiFE0rf4I8KsH2Kcb28AToKw8bBN8EXN5rlIdQcuLeZR elYk3Z5Jvjvuladm8yNhbX0iTnr3gafRDQ== X-Google-Smtp-Source: APXvYqyYlJz6SdpKKsaTmzNG0mK2E9kBTt9FthIwXIM0tVPrG2goGshGjILQlRE1pVIZEYYGlwVwgg== X-Received: by 2002:aca:bcd7:: with SMTP id m206mr1774156oif.46.1582692359661; Tue, 25 Feb 2020 20:45:59 -0800 (PST) Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com. [209.85.210.51]) by smtp.gmail.com with ESMTPSA id n16sm336144otk.25.2020.02.25.20.45.58 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 25 Feb 2020 20:45:59 -0800 (PST) Received: by mail-ot1-f51.google.com with SMTP id 66so1760630otd.9 for ; Tue, 25 Feb 2020 20:45:58 -0800 (PST) X-Received: by 2002:a05:6830:13da:: with SMTP id e26mr1449424otq.97.1582692357955; Tue, 25 Feb 2020 20:45:57 -0800 (PST) MIME-Version: 1.0 References: <20200226033646.20949-1-gtk_ruiwang@mediatek.com> <20200226033646.20949-2-gtk_ruiwang@mediatek.com> <1582690790.6276.19.camel@mhfsdcap03> In-Reply-To: <1582690790.6276.19.camel@mhfsdcap03> From: Alexandre Courbot Date: Wed, 26 Feb 2020 13:45:46 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] mediatek: move MT8173 VPU FW to subfolder To: gtk_ruiwang List-Id: Cc: linux-firmware@kernel.org, Linux Media Mailing List , LKML , "moderated list:ARM/Mediatek SoC support" , "moderated list:ARM/Mediatek SoC support" , srv_heupstream@mediatek.com, Tomasz Figa , PoChun.Lin@mediatek.com, Longfei Wang , Yunfei Dong , Maoguang Meng Content-Type: text/plain; charset="UTF-8" Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org On Wed, Feb 26, 2020 at 1:20 PM gtk_ruiwang wrote: > > Dear Alex, > > Do you mean to create two symbolic link? > > lrwxrwxrwx 1 gtk_ruiwang gtk_ruiwang 25 Feb 26 11:52 vpu_d.bin -> > mediatek/mt8173/vpu_d.bin > lrwxrwxrwx 1 gtk_ruiwang gtk_ruiwang 25 Feb 26 11:52 vpu_p.bin -> > mediatek/mt8173/vpu_p.bin Yes, otherwise older kernels will become unable to use the firmware. I don't know whether these are supposed to stay forever or whether we can remove them after a while... presumably the former. Also the WHENCE file should probably be updated to list the new files. > > we create them at the linux-firmware root folder. > > Thanks > Best Regards > > On Wed, 2020-02-26 at 12:41 +0900, Alexandre Courbot wrote: > > On Wed, Feb 26, 2020 at 12:38 PM wrote: > > > > > > From: gtk_ruiwang > > > > > > Currently vpu_d.bin and vpu_p.bin are at the root of > > > linux-firmware git tree, it's not appropriate so we move > > > them to subfolder mediatek/mt8173 > > > > > > Release Version: 1.1.4 > > > > > > Signed-off-by: Rui Wang > > > --- > > > vpu_d.bin => mediatek/mt8173/vpu_d.bin | Bin > > > vpu_p.bin => mediatek/mt8173/vpu_p.bin | Bin > > > 2 files changed, 0 insertions(+), 0 deletions(-) > > > rename vpu_d.bin => mediatek/mt8173/vpu_d.bin (100%) > > > rename vpu_p.bin => mediatek/mt8173/vpu_p.bin (100%) > > > > This is nice as it removes some stuff from the root, but for > > compatibility with older kernels that don't know about the new path > > shouldn't we at least temporarily create a symbolic link between the > > old location and the new one? >