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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B1070C6FA91 for ; Thu, 22 Sep 2022 13:08:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231644AbiIVNIw (ORCPT ); Thu, 22 Sep 2022 09:08:52 -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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@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