Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp773058rwb; Thu, 22 Sep 2022 06:18:33 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7sl9MSJsDLeuwkLNLWak11uPyK4mG6R8meHTXPMbXPOo7t17KeQEYfcf/yY1Joq7LwPugj X-Received: by 2002:a17:902:ecd2:b0:178:3b53:ebf7 with SMTP id a18-20020a170902ecd200b001783b53ebf7mr3132847plh.28.1663852713564; Thu, 22 Sep 2022 06:18:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663852713; cv=none; d=google.com; s=arc-20160816; b=C0vop+g3iPIQjZ5JLFoqCafMoEv2C+Z0dajnEuctVjLU0+Z2/4EA9TNyc4k6VaPXoA NlND1Q3j19FJwqlScitFULkljQhaWJHiMngP7jomewJG8+EBnikM/MEhO5kIHoaarZqJ +M8wTnvH9UuY792NZc3RewaP6kpOImYt7W4Xu9Gefvh4NiAeooDjnOTE+25y9s8jPeAt IV3Q8pVRE0+zPW41WuE81Q4jd54lD3lurC/ufu+gzpNSjGxk6DtULHSxr8viYIt/a/DU srNqV1Ul2a/ZqTxe/nGwZX04m8y6npTt0PmURgiU9xNgQmXvtnAV60/p2fL15JTfILvs BQrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=/NSH+28o8XA6Ppc/ezGESlCnCEaIf9u0l5MX5VAHZuw=; b=KLwRkeK98xBy5zVZ2cJcoFj06ztxpiaqubWekzcY+GLViED+VyRZgcDQbu0qJL1VHr hva3M9ldfu9r7RSWL2ZY+HfKqyHVwmmvYoBqSEppDflD1YdxCogoPLX8VtMiuNuQhqqg 68UNWDtudQDAsQH3kRiSq/ameSkwgyhmmnsvyh+9AwlTQ/NzADtToH5Ne7orgSz+hiRz Tpiu8diEB9Scv66tYpltSJdncNNDWa+sv1GvWznukc+ZV6p3xGZ/0y02BPAVYdUbb9UZ VzUVYZKN5opjcIR9U5MqzYYIT5YSYb1L6i+KjXzyw/ANtm8p5u4PccyLJBYXBpD96z11 s12w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@marcan.st header.s=default header.b=q6ClAiMN; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=marcan.st Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h14-20020a170902f54e00b001769e08c554si5894842plf.545.2022.09.22.06.18.25; Thu, 22 Sep 2022 06:18:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@marcan.st header.s=default header.b=q6ClAiMN; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=marcan.st Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231283AbiIVNIr (ORCPT + 63 others); Thu, 22 Sep 2022 09:08:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53988 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231751AbiIVNIo (ORCPT ); Thu, 22 Sep 2022 09:08:44 -0400 Received: from mail.marcansoft.com (marcansoft.com [212.63.210.85]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 06815EBBD6; Thu, 22 Sep 2022 06:08:30 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: marcan@marcan.st) by mail.marcansoft.com (Postfix) with ESMTPSA id 2817641F12; Thu, 22 Sep 2022 13:08:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=marcan.st; s=default; t=1663852109; bh=icQWkxx6xaBpvv1YkBTD1bpN7od8H2KAyKOq4vcIuo0=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=q6ClAiMNXr93Ys9uLuWzN6aRggytNKr3Y8jNu6qRpFFktcOkJg3SKf+VzSL5aBBLn PSMFKtm8bLeXfBf0OxyE/6FzMVMRk4OHgg/fJa8u8AiP7/SGDszX0+Tn54mMdQ07a9 bHShPY1NZFsZFhBGHqzLiDNKpS5XTM99sQCzl8lAasBZQ6rsGxPdTFeacZVHG7XuVS tJFafqS92DHurw3p+u2DXiid4gFKvoZ4CVhlXDGlp1J+esJdBKsy0U0BkdIuDczFjW Iu7HFE5UDFpQC5cXLMm64bF8nXe+DbYxvRE6t6kJ+Ne1QhbZekSossn1spPxIbFQDU jZZq7ywarqEpg== Message-ID: Date: Thu, 22 Sep 2022 22:08:19 +0900 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [PATCH v2] brcmfmac: Add support for BCM43596 PCIe Wi-Fi Content-Language: es-ES To: Linus Walleij , Konrad Dybcio Cc: ~postmarketos/upstreaming@lists.sr.ht, martin.botka@somainline.org, angelogioacchino.delregno@somainline.org, marijn.suijten@somainline.org, jamipkettunen@somainline.org, Arend van Spriel , Franky Lin , Hante Meuleman , Kalle Valo , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , =?UTF-8?Q?Alvin_=c5=a0ipraga?= , Marek Vasut , "Zhao, Jiaqing" , "Russell King (Oracle)" , Soontak Lee , linux-wireless@vger.kernel.org, brcm80211-dev-list.pdl@broadcom.com, SHA-cyfmac-dev-list@infineon.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220921001630.56765-1-konrad.dybcio@somainline.org> <83b90478-3974-28e6-cf13-35fc4f62e0db@marcan.st> <13b8c67c-399c-d1a6-4929-61aea27aa57d@somainline.org> <0e65a8b2-0827-af1e-602c-76d9450e3d11@marcan.st> <7fd077c5-83f8-02e2-03c1-900a47f05dc1@somainline.org> From: Hector Martin In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 22/09/2022 22.02, Linus Walleij wrote: > On Thu, Sep 22, 2022 at 12:21 PM Konrad Dybcio > wrote: > >> Also worth noting is the 'somc' bit, meaning there are probably *some* SONY >> customizations, but that's also just a guess. > > What I have seen from BRCM customizations on Samsung phones is that > the per-device customization of firmware seems to involve the set-up of > some GPIO and power management pins. For example if integrated with > an SoC that has autonomous system resume, or if some GPIO line has > to be pulled to enable an external regulator or PA. > > To the best of my knowledge that customization is done by consultants > from Broadcom when working with the device manufacturer, and > eventually they roll a unique firmware for the device. Probably because > the firmware can only be signed for execution by Broadcom? I don't think the firmware is signed, they probably just don't want to share the source code with most customers? (Except Apple maybe, but Apple gets custom silicon too...). - Hector