<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>b1992c37 - kbuild: use $(src) instead of $(srctree)/$(src) for source directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#b1992c37</link>
        <description>kbuild: use $(src) instead of $(srctree)/$(src) for source directoryKbuild conventionally uses $(obj)/ for generated files, and $(src)/ forchecked-in source files. It is merely a convention without any functionaldifference. In fact, $(obj) and $(src) are exactly the same, as definedin scripts/Makefile.build:    src := $(obj)When the kernel is built in a separate output directory, $(src) doesnot accurately reflect the source directory location. While Kbuildresolves this discrepancy by specifying VPATH=$(srctree) to search forsource files, it does not cover all cases. For example, when adding aheader search path for local headers, -I$(srctree)/$(src) is typicallypassed to the compiler.This introduces inconsistency between upstream and downstream Makefilesbecause $(src) is used instead of $(srctree)/$(src) for the latter.To address this inconsistency, this commit changes the semantics of$(src) so that it always points to the directory in the source tree.Going forward, the variables used in Makefiles will have the followingmeanings:  $(obj)     - directory in the object tree  $(src)     - directory in the source tree  (changed by this commit)  $(objtree) - the top of the kernel object tree  $(srctree) - the top of the kernel source treeConsequently, $(srctree)/$(src) in upstream Makefiles need to be replacedwith $(src).Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Reviewed-by: Nicolas Schier &lt;nicolas@fjasle.eu&gt;

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Sat, 27 Apr 2024 14:55:02 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>0f485805 - wifi: brcmfmac: acpi: Add support for fetching Apple ACPI properties</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#0f485805</link>
        <description>wifi: brcmfmac: acpi: Add support for fetching Apple ACPI propertiesOn DT platforms, the module-instance and antenna-sku-info propertiesare passed in the DT. On ACPI platforms, module-instance is passed viathe analogous Apple device property mechanism, while the antenna SKUinfo is instead obtained via an ACPI method that grabs it fromnon-volatile storage.Add support for this, to allow proper firmware selection on Appleplatforms.Signed-off-by: Hector Martin &lt;marcan@marcan.st&gt;Reviewed-by: Julian Calaby &lt;julian.calaby@gmail.com&gt;Acked-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;Link: https://lore.kernel.org/r/20230214080034.3828-2-marcan@marcan.st

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Tue, 14 Feb 2023 08:00:33 +0000</pubDate>
        <dc:creator>Hector Martin &lt;marcan@marcan.st&gt;</dc:creator>
    </item>
<item>
        <title>b1d94be5 - wifi: brcmfmac: add support Broadcom BCA firmware api</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#b1d94be5</link>
        <description>wifi: brcmfmac: add support Broadcom BCA firmware apiBroadcom BCA division develops its own firmware api and as such willlikely diverge over time (or already has). Add support for handlingthis.Reviewed-by: Hante Meuleman &lt;hante.meuleman@broadcom.com&gt;Reviewed-by: Pieter-Paul Giesberts &lt;pieter-paul.giesberts@broadcom.com&gt;Reviewed-by: Franky Lin &lt;franky.lin@broadcom.com&gt;Signed-off-by: Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;Link: https://lore.kernel.org/r/20221129135446.151065-6-arend.vanspriel@broadcom.com

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Tue, 29 Nov 2022 13:54:44 +0000</pubDate>
        <dc:creator>Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;</dc:creator>
    </item>
<item>
        <title>f74f1ec2 - wifi: brcmfmac: add support for Cypress firmware api</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#f74f1ec2</link>
        <description>wifi: brcmfmac: add support for Cypress firmware apiCypress uses the brcmfmac driver and releases firmware which willlikely diverge over time (or already has). So adding support forhandling that.Reviewed-by: Hante Meuleman &lt;hante.meuleman@broadcom.com&gt;Reviewed-by: Pieter-Paul Giesberts &lt;pieter-paul.giesberts@broadcom.com&gt;Reviewed-by: Franky Lin &lt;franky.lin@broadcom.com&gt;Signed-off-by: Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;Link: https://lore.kernel.org/r/20221129135446.151065-5-arend.vanspriel@broadcom.com

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Tue, 29 Nov 2022 13:54:43 +0000</pubDate>
        <dc:creator>Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;</dc:creator>
    </item>
<item>
        <title>d6a5c562 - wifi: brcmfmac: add support for vendor-specific firmware api</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#d6a5c562</link>
        <description>wifi: brcmfmac: add support for vendor-specific firmware apiThe driver is being used by multiple vendors who develop the firmwareapi independently. So far the firmware api as used by the driver hasnot diverged (yet). This change adds framework for supporting multiplefirmware apis. The vendor-specific support code has to provide a numberof callback operations. Right now it is only attach and detach callbacksso no real functionality as the api is still common. This code onlyadds WCC variant anyway, which is selected for all devices right now.The vendor-specific part will be built in a separate module when thedriver is configured to be built as a module through Kconfig, ie. whenCONFIG_BRCMFMAC=m.Reviewed-by: Hante Meuleman &lt;hante.meuleman@broadcom.com&gt;Reviewed-by: Pieter-Paul Giesberts &lt;pieter-paul.giesberts@broadcom.com&gt;Reviewed-by: Franky Lin &lt;franky.lin@broadcom.com&gt;Signed-off-by: Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;Link: https://lore.kernel.org/r/20221129135446.151065-4-arend.vanspriel@broadcom.com

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Tue, 29 Nov 2022 13:54:42 +0000</pubDate>
        <dc:creator>Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;</dc:creator>
    </item>
<item>
        <title>a7dd0ac9 - brcmfmac: add xtlv support to firmware interface layer</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#a7dd0ac9</link>
        <description>brcmfmac: add xtlv support to firmware interface layerNewer firmware API require commands to use xtlv format. Add supportfor that in the firmware interface layer.Reviewed-by: Hante Meuleman &lt;hante.meuleman@broadcom.com&gt;Reviewed-by: Pieter-Paul Giesberts &lt;pieter-paul.giesberts@broadcom.com&gt;Reviewed-by: Franky Lin &lt;franky.lin@broadcom.com&gt;Signed-off-by: Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;Link: https://lore.kernel.org/r/1627505434-9544-4-git-send-email-arend.vanspriel@broadcom.com

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Wed, 28 Jul 2021 20:50:33 +0000</pubDate>
        <dc:creator>Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;</dc:creator>
    </item>
<item>
        <title>daeccac2 - brcmfmac: switch source files to using SPDX license identifier</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#daeccac2</link>
        <description>brcmfmac: switch source files to using SPDX license identifierWith ISC license text in place under the LICENSES folder switchto using the SPDX license identifier to refer to the ISC license.Reviewed-by: Hante Meuleman &lt;hante.meuleman@broadcom.com&gt;Reviewed-by: Pieter-Paul Giesberts &lt;pieter-paul.giesberts@broadcom.com&gt;Reviewed-by: Franky Lin &lt;franky.lin@broadcom.com&gt;Signed-off-by: Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Thu, 16 May 2019 12:04:09 +0000</pubDate>
        <dc:creator>Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;</dc:creator>
    </item>
<item>
        <title>030b4367 - wireless: prefix header search paths with $(srctree)/</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#030b4367</link>
        <description>wireless: prefix header search paths with $(srctree)/Currently, the Kbuild core manipulates header search paths in a crazyway [1].To fix this mess, I want all Makefiles to add explicit $(srctree)/ tothe search paths in the srctree. Some Makefiles are already written inthat way, but not all. The goal of this work is to make the notationconsistent, and finally get rid of the gross hacks.Having whitespaces after -I does not matter since commit 48f6e3cf5bc6(&quot;kbuild: do not drop -I without parameter&quot;).I also removed one header search path in:  drivers/net/wireless/broadcom/brcm80211/brcmutil/MakefileI was able to compile without it.[1]: https://patchwork.kernel.org/patch/9632347/Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Acked-by: Luca Coelho &lt;luciano.coelho@intel.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Fri, 25 Jan 2019 15:18:00 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>bd1e82bb - brcmfmac: Set board_type from DMI on x86 based machines</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#bd1e82bb</link>
        <description>brcmfmac: Set board_type from DMI on x86 based machinesFor x86 based machines, set the board_type used for nvram file selectionbased on the DMI sys-vendor and product-name strings.Since on some models these strings are too generic, this commit also addsa quirk table overriding the strings for models listed in that table.The board_type setting is used to load the board-specific nvram file witha board-specific name so that we can ship files for each supported boardin linux-firmware.Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Wed, 10 Oct 2018 11:01:02 +0000</pubDate>
        <dc:creator>Hans de Goede &lt;hdegoede@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>26ecfe01 - brcmfmac: only build fwsignal module for CONFIG_BRCMFMAC_PROTO_BCDC</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#26ecfe01</link>
        <description>brcmfmac: only build fwsignal module for CONFIG_BRCMFMAC_PROTO_BCDCThe fwsignal module is only referenced by the bcdc module and part of thebcdc protocol. So only build it when CONFIG_BRCMFMAC_PROTO_BCDC is selected.Fixes: acf8ac41dd73 (&quot;brcmfmac: remove reference to fwsignal data from struct brcmf_pub&quot;)Signed-off-by: Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Fri, 14 Apr 2017 21:27:37 +0000</pubDate>
        <dc:creator>Arend Van Spriel &lt;arend.vanspriel@broadcom.com&gt;</dc:creator>
    </item>
<item>
        <title>6bdf1e0e - Makefile: drop -D__CHECK_ENDIAN__ from cflags</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#6bdf1e0e</link>
        <description>Makefile: drop -D__CHECK_ENDIAN__ from cflagsThat&apos;s the default now, no need for makefiles to set it.Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;Acked-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;Acked-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Acked-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Acked-by: Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Thu, 15 Dec 2016 02:07:46 +0000</pubDate>
        <dc:creator>Michael S. Tsirkin &lt;mst@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>ac55136f - brcmfmac: move pno helper functions in separate source file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#ac55136f</link>
        <description>brcmfmac: move pno helper functions in separate source fileIntroducing new source file for pno related functionality. Movingexisting pno functions.Reviewed-by: Hante Meuleman &lt;hante.meuleman@broadcom.com&gt;Reviewed-by: Pieter-Paul Giesberts &lt;pieter-paul.giesberts@broadcom.com&gt;Reviewed-by: Franky Lin &lt;franky.lin@broadcom.com&gt;Signed-off-by: Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Wed, 23 Nov 2016 10:25:22 +0000</pubDate>
        <dc:creator>Arend Van Spriel &lt;arend.vanspriel@broadcom.com&gt;</dc:creator>
    </item>
<item>
        <title>05491d2c - brcm80211: move under broadcom vendor directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile#05491d2c</link>
        <description>brcm80211: move under broadcom vendor directoryPart of reorganising wireless drivers directory and Kconfig. Note that I had toedit Makefiles from subdirectories to use the new location.Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;

            List of files:
            /linux-6.15/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Makefile</description>
        <pubDate>Tue, 17 Nov 2015 17:52:05 +0000</pubDate>
        <dc:creator>Kalle Valo &lt;kvalo@codeaurora.org&gt;</dc:creator>
    </item>
</channel>
</rss>
