<?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>2e4986cf - fwctl: Add basic structure for a class subsystem with a cdev</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#2e4986cf</link>
        <description>fwctl: Add basic structure for a class subsystem with a cdevCreate the class, character device and functions for a fwctl driver toun/register to the subsystem.A typical fwctl driver has a sysfs presence like:$ ls -l /dev/fwctl/fwctl0crw------- 1 root root 250, 0 Apr 25 19:16 /dev/fwctl/fwctl0$ ls /sys/class/fwctl/fwctl0dev  device  power  subsystem  uevent$ ls /sys/class/fwctl/fwctl0/device/infiniband/ibp0s10f0$ ls /sys/class/infiniband/ibp0s10f0/device/fwctl/fwctl0/$ ls /sys/devices/pci0000:00/0000:00:0a.0/fwctl/fwctl0dev  device  power  subsystem  ueventWhich allows userspace to link all the multi-subsystem driver componentstogether and learn the subsystem specific names for the device&apos;scomponents.Link: https://patch.msgid.link/r/1-v5-642aa0c94070+4447f-fwctl_jgg@nvidia.comReviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Reviewed-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Reviewed-by: Dave Jiang &lt;dave.jiang@intel.com&gt;Reviewed-by: Shannon Nelson &lt;shannon.nelson@amd.com&gt;Tested-by: Dave Jiang &lt;dave.jiang@intel.com&gt;Tested-by: Shannon Nelson &lt;shannon.nelson@amd.com&gt;Signed-off-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Fri, 28 Feb 2025 00:26:29 +0000</pubDate>
        <dc:creator>Jason Gunthorpe &lt;jgg@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>78efa53e - leds: Init leds class earlier</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#78efa53e</link>
        <description>leds: Init leds class earlierNPEM driver will require leds class, there is an init-order conflict.Make sure that LEDs initialization happens first and add comment.Link: https://lore.kernel.org/r/20240904104848.23480-2-mariusz.tkaczyk@linux.intel.comSuggested-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Signed-off-by: Mariusz Tkaczyk &lt;mariusz.tkaczyk@linux.intel.com&gt;Signed-off-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Tested-by: Stuart Hayes &lt;stuart.w.hayes@gmail.com&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Ilpo J&#228;rvinen &lt;ilpo.jarvinen@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Wed, 04 Sep 2024 10:48:46 +0000</pubDate>
        <dc:creator>Mariusz Tkaczyk &lt;mariusz.tkaczyk@linux.intel.com&gt;</dc:creator>
    </item>
<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/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/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>041d2a0e - Revert &quot;leds: Only descend into leds directory when CONFIG_NEW_LEDS is set&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#041d2a0e</link>
        <description>Revert &quot;leds: Only descend into leds directory when CONFIG_NEW_LEDS is set&quot;This reverts commit b1ae40a5db6191c42e2e45d726407096f030ee08.The ExpressWire library introduced in commit 25ae5f5f4168 (&quot;leds:Introduce ExpressWire library&quot;) does not depend on NEW_LEDS, but withoutthis revert it would never get compiled if NEW_LEDS is not enabled.Revert this commit to allow the library to be compiled.Link: https://lore.kernel.org/2cacd8dc-6150-4aa2-af9e-830a202fb0a8@app.fastmail.comSuggested-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Reviewed-by: Daniel Thompson &lt;daniel.thompson@linaro.org&gt;Signed-off-by: Duje Mihanovi&#263; &lt;duje.mihanovic@skole.hr&gt;Link: https://lore.kernel.org/r/20240216-expresswire-deps-v2-1-8be59c4a75f5@skole.hrSigned-off-by: Lee Jones &lt;lee@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Fri, 16 Feb 2024 21:15:43 +0000</pubDate>
        <dc:creator>Duje Mihanovi&#263; &lt;duje.mihanovic@skole.hr&gt;</dc:creator>
    </item>
<item>
        <title>689237ab - fbdev/intelfb: Remove driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#689237ab</link>
        <description>fbdev/intelfb: Remove driverFrom looking at the PCI IDs, every device supported by intelfb isalso supported by i915. Anyone still using intelfb should pleasemove on to i915, which does everything intelfb does but better.Removing intelfb is motivated by the driver&apos;s excessive use of theglobal screen_info state. The state belongs to architecture andfirmware code; device drivers should not attempt to access it. Butfixing intelfb would require a significant change in the driver&apos;sprobing logic. As intelfb has been obsolete for nearly 2 decades,it is probably not worth the effort. Let&apos;s just remove it. Alsoremove the related documentation.Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Acked-by: Maik Broemme &lt;mbroemme@libmpq.org&gt;Signed-off-by: Helge Deller &lt;deller@gmx.de&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Fri, 05 Jan 2024 09:10:36 +0000</pubDate>
        <dc:creator>Thomas Zimmermann &lt;tzimmermann@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>9a6c7821 - vlynq: remove bus driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#9a6c7821</link>
        <description>vlynq: remove bus driverThere are no users with a vlynq_driver in the Kernel tree. Also, onlythe AR7 platform ever initialized a VLYNQ bus, but AR7 is going to beremoved from the Kernel. OpenWRT had some out-of-tree drivers which theyprobably intended to upport, but AR7 devices are even there notsupported anymore because they are &quot;stuck with Kernel3.18&quot; [1]. This code can go.[1] https://openwrt.org/docs/techref/targets/ar7Signed-off-by: Wolfram Sang &lt;wsa+renesas@sang-engineering.com&gt;Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Acked-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: Thomas Bogendoerfer &lt;tsbogend@alpha.franken.de&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Fri, 22 Sep 2023 06:15:24 +0000</pubDate>
        <dc:creator>Wolfram Sang &lt;wsa+renesas@sang-engineering.com&gt;</dc:creator>
    </item>
<item>
        <title>9431063a - dpll: core: Add DPLL framework base functions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#9431063a</link>
        <description>dpll: core: Add DPLL framework base functionsDPLL framework is used to represent and configure DPLL devicesin systems. Each device that has DPLL and can configure inputsand outputs can use this framework.Implement core framework functions for further interactionswith device drivers implementing dpll subsystem, as well as forinteractions of DPLL netlink framework part with the subsystemitself.Co-developed-by: Milena Olech &lt;milena.olech@intel.com&gt;Signed-off-by: Milena Olech &lt;milena.olech@intel.com&gt;Co-developed-by: Michal Michalik &lt;michal.michalik@intel.com&gt;Signed-off-by: Michal Michalik &lt;michal.michalik@intel.com&gt;Signed-off-by: Vadim Fedorenko &lt;vadim.fedorenko@linux.dev&gt;Co-developed-by: Arkadiusz Kubalewski &lt;arkadiusz.kubalewski@intel.com&gt;Signed-off-by: Arkadiusz Kubalewski &lt;arkadiusz.kubalewski@intel.com&gt;Signed-off-by: Jiri Pirko &lt;jiri@nvidia.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Wed, 13 Sep 2023 20:49:37 +0000</pubDate>
        <dc:creator>Vadim Fedorenko &lt;vadim.fedorenko@linux.dev&gt;</dc:creator>
    </item>
<item>
        <title>e2ad626f - pmdomain: Rename the genpd subsystem to pmdomain</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#e2ad626f</link>
        <description>pmdomain: Rename the genpd subsystem to pmdomainIt has been pointed out that naming a subsystem &quot;genpd&quot; isn&apos;t veryself-explanatory and the acronym itself that means Generic PM Domain, isknown only by a limited group of people.In a way to improve the situation, let&apos;s rename the subsystem to pmdomain,which ideally should indicate that this is about so called Power Domains or&quot;PM domains&quot; as we often also use within the Linux Kernel terminology.Suggested-by: Rafael J. Wysocki &lt;rafael@kernel.org&gt;Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Acked-by: Heiko Stuebner &lt;heiko@sntech.de&gt;Acked-by: Rafael J. Wysocki &lt;rafael@kernel.org&gt;Acked-by: Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;Link: https://lore.kernel.org/r/20230912221127.487327-1-ulf.hansson@linaro.org

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Tue, 12 Sep 2023 22:11:27 +0000</pubDate>
        <dc:creator>Ulf Hansson &lt;ulf.hansson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>d34599bc - cache: Add L2 cache management for Andes AX45MP RISC-V core</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#d34599bc</link>
        <description>cache: Add L2 cache management for Andes AX45MP RISC-V coreI/O Coherence Port (IOCP) provides an AXI interface for connectingexternal non-caching masters, such as DMA controllers. The accessesfrom IOCP are coherent with D-Caches and L2 Cache.IOCP is a specification option and is disabled on the Renesas RZ/FiveSoC due to this reason IP blocks using DMA will fail.The Andes AX45MP core has a Programmable Physical Memory Attributes (PMA)block that allows dynamic adjustment of memory attributes in the runtime.It contains a configurable amount of PMA entries implemented as CSRregisters to control the attributes of memory locations in interest.Below are the memory attributes supported:* Device, Non-bufferable* Device, bufferable* Memory, Non-cacheable, Non-bufferable* Memory, Non-cacheable, Bufferable* Memory, Write-back, No-allocate* Memory, Write-back, Read-allocate* Memory, Write-back, Write-allocate* Memory, Write-back, Read and Write-allocateMore info about PMA (section 10.3):Link: http://www.andestech.com/wp-content/uploads/AX45MP-1C-Rev.-5.0.0-Datasheet.pdfAs a workaround for SoCs with IOCP disabled CMO needs to be handled bysoftware. Firstly OpenSBI configures the memory region as&quot;Memory, Non-cacheable, Bufferable&quot; and passes this region as a globalshared dma pool as a DT node. With DMA_GLOBAL_POOL enabled all DMAallocations happen from this region and synchronization callbacks areimplemented to synchronize when doing DMA transactions.Example PMA region passes as a DT node from OpenSBI:    reserved-memory {        #address-cells = &lt;2&gt;;        #size-cells = &lt;2&gt;;        ranges;        pma_resv0@58000000 {            compatible = &quot;shared-dma-pool&quot;;            reg = &lt;0x0 0x58000000 0x0 0x08000000&gt;;            no-map;            linux,dma-default;        };    };Signed-off-by: Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;Reviewed-by: Conor Dooley &lt;conor.dooley@microchip.com&gt;Tested-by: Conor Dooley &lt;conor.dooley@microchip.com&gt; # tyre-kicking on a d1Link: https://lore.kernel.org/r/20230818135723.80612-6-prabhakar.mahadev-lad.rj@bp.renesas.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Fri, 18 Aug 2023 13:57:22 +0000</pubDate>
        <dc:creator>Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;</dc:creator>
    </item>
<item>
        <title>305b9f4f - s390: use obj-y to descend into drivers/s390/</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#305b9f4f</link>
        <description>s390: use obj-y to descend into drivers/s390/The single build rule does not work with the drivers-y syntax. [1]Use the standard obj-y syntax. It moves the objects from drivers/s390/to slightly lower address, but fixes the reported issue.[1]: https://lore.kernel.org/linux-kbuild/d57ba55f-20a3-b836-783d-b49c8a161b6e@kernel.org/T/#m27f781ab60acadfed8a9e9642f30d5414a5e2df3Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Tested-by: Jiri Slaby &lt;jirislaby@kernel.org&gt;Link: https://lore.kernel.org/r/20230721171358.3612099-1-masahiroy@kernel.orgSigned-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Fri, 21 Jul 2023 17:13:58 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>c1e213e5 - genpd: Create a new subsystem directory to host genpd providers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#c1e213e5</link>
        <description>genpd: Create a new subsystem directory to host genpd providersThere are currently ~60 users of the genpd provider interface, whichimplementations are sprinkled across various subsystems. To simplify withmaintenance let&apos;s create a new subsystem (drivers/genpd) and start movingthe providers in there.My intention is also to host a git tree to collect and to get the patchestested/integrated through the linux-next tree. Ideally this should releasesome of the burden on the soc maintainers.Note that, I will of course require acks/reviews from the current platformmaintainers, hence the MAINTAINERS file needs to be updated accordingly foreach genpd provider that is moved into the new genpd subsystem.Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Fri, 30 Jun 2023 13:26:26 +0000</pubDate>
        <dc:creator>Ulf Hansson &lt;ulf.hansson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>2959ab24 - cdx: add the cdx bus driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#2959ab24</link>
        <description>cdx: add the cdx bus driverIntroduce AMD CDX bus, which provides a mechanism for scanningand probing CDX devices. These devices are memory mapped onsystem bus for Application Processors(APUs).CDX devices can be changed dynamically in the Fabric and CDXbus interacts with CDX controller to rescan the bus andrediscover the devices.Signed-off-by: Nipun Gupta &lt;nipun.gupta@amd.com&gt;Reviewed-by: Pieter Jansen van Vuuren &lt;pieter.jansen-van-vuuren@amd.com&gt;Tested-by: Nikhil Agarwal &lt;nikhil.agarwal@amd.com&gt;Link: https://lore.kernel.org/r/20230313132636.31850-2-nipun.gupta@amd.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Mon, 13 Mar 2023 13:26:30 +0000</pubDate>
        <dc:creator>Nipun Gupta &lt;nipun.gupta@amd.com&gt;</dc:creator>
    </item>
<item>
        <title>8a3d95ea - dax/hmem: build hmem device support as module if possible</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#8a3d95ea</link>
        <description>dax/hmem: build hmem device support as module if possibleWhen device_hmem.o is enabled but dax itself is a loadable module, thedax_hmem support fails to link because Kbuild never compiles built-incode under drivers/dax:ERROR: modpost: &quot;walk_hmem_resources&quot; [drivers/dax/hmem/dax_hmem.ko] undefined!Make sure that drivers/dax is entered for compiling built-in codeeven with CONFIG_DAX=m.Fixes: 7dab174e2e27 (&quot;dax/hmem: Move hmem device registration to dax_hmem.ko&quot;)Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Link: https://lore.kernel.org/r/20230214131913.1431969-1-arnd@kernel.orgSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Tue, 14 Feb 2023 13:18:47 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>67d7c302 - kbuild: remove --include-dir MAKEFLAG from top Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#67d7c302</link>
        <description>kbuild: remove --include-dir MAKEFLAG from top MakefileI added $(srctree)/ to some included Makefiles in the following commits: - 3204a7fb98a3 (&quot;kbuild: prefix $(srctree)/ to some included Makefiles&quot;) - d82856395505 (&quot;kbuild: do not require sub-make for separate output tree builds&quot;)They were a preparation for removing --include-dir flag.I have never thought --include-dir useful. Rather, it _is_ harmful.For example, run the following commands:  $ make -s ARCH=x86 mrproper defconfig  $ make ARCH=arm O=foo dtbs  make[1]: Entering directory &apos;/tmp/linux/foo&apos;    HOSTCC  scripts/basic/fixdep  Error: kernelrelease not valid - run &apos;make prepare&apos; to update it    UPD     include/config/kernel.release  make[1]: Leaving directory &apos;/tmp/linux/foo&apos;The first command configures the source tree for x86. The next commandtries to build ARM device trees in the separate foo/ directory - thismust stop because the directory foo/ has not been configured yet.However, due to --include-dir=$(abs_srctree), the top Makefile includesthe wrong include/config/auto.conf from the source tree and continuesbuilding. Kbuild traverses the directory tree, but of course it doesnot work correctly. The Error message is also pointless - &apos;make prepare&apos;does not help at all for fixing the issue.This commit fixes more arch Makefile, and finally removes --include-dirfrom the top Makefile.There are more breakages under drivers/, but I do not volunteer to fixthem all. I just moved --include-dir to drivers/Makefile.With this commit, the second command will stop with a sensible message.  $ make -s ARCH=x86 mrproper defconfig  $ make ARCH=arm O=foo dtbs  make[1]: Entering directory &apos;/tmp/linux/foo&apos;    SYNC    include/config/auto.conf.cmd  ***  *** The source tree is not clean, please run &apos;make ARCH=arm mrproper&apos;  *** in /tmp/linux  ***  make[2]: *** [../Makefile:646: outputmakefile] Error 1  /tmp/linux/Makefile:770: include/config/auto.conf.cmd: No such file or directory  make[1]: *** [/tmp/linux/Makefile:793: include/config/auto.conf.cmd] Error 2  make[1]: Leaving directory &apos;/tmp/linux/foo&apos;  make: *** [Makefile:226: __sub-make] Error 2Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Sat, 28 Jan 2023 09:24:23 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>532a3829 - drivers: Restore alignment and newline in Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#532a3829</link>
        <description>drivers: Restore alignment and newline in MakefileThe introduction of drivers/accel/ broke alignment, and removed thenewline at the end of the file.  Fix all of that.Fixes: 35b137630f08 (&quot;accel/ivpu: Introduce a new DRM driver for Intel VPU&quot;)Signed-off-by: Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;Reviewed-by: Oded Gabbay &lt;ogabbay@kernel.org&gt;Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Signed-off-by: Jacek Lawrynowicz &lt;jacek.lawrynowicz@linux.intel.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20230124104145.3962497-1-geert+renesas@glider.be

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Tue, 24 Jan 2023 10:41:45 +0000</pubDate>
        <dc:creator>Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;</dc:creator>
    </item>
<item>
        <title>72f2b0b2 - drivers/block: Move PARIDE protocol modules to drivers/ata/pata_parport</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#72f2b0b2</link>
        <description>drivers/block: Move PARIDE protocol modules to drivers/ata/pata_parportMove PARIDE protocol modules out of drivers/block intodrivers/ata/pata_parport and update the CONFIG_ symbol names toPATA_PARPORT.[Damien]The pata_parport driver file itsef is also moved together with theprotocol modules in drivers/ata/pata_parport.Signed-off-by: Ondrej Zary &lt;linux@zary.sk&gt;Acked-by: Jens Axboe &lt;axboe@kernel.dk&gt;Signed-off-by: Damien Le Moal &lt;damien.lemoal@opensource.wdc.com&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Mon, 30 Jan 2023 21:10:50 +0000</pubDate>
        <dc:creator>Ondrej Zary &lt;linux@zary.sk&gt;</dc:creator>
    </item>
<item>
        <title>246a1c4c - ata: pata_parport: add driver (PARIDE replacement)</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#246a1c4c</link>
        <description>ata: pata_parport: add driver (PARIDE replacement)The pata_parport is a libata-based replacement of the old PARIDEsubsystem - driver for parallel port IDE devices.It uses the original paride low-level protocol drivers but does notneed the high-level drivers (pd, pcd, pf, pt, pg). The IDE devicesbehind parallel port adapters are handled by the ATA layer.This will allow paride and its high-level drivers to be removed.Unfortunately, libata drivers cannot sleep so pata_parport claimsparport before activating the ata host and keeps it claimed (andprotocol connected) until the ata host is removed. This means thatno devices can be chained (neither other pata_parport devices nora printer).paride and pata_parport are mutually exclusive because the compiledprotocol drivers are incompatible.Tested with: - Imation SuperDisk LS-120 and HP C4381A (EPAT) - Freecom Parallel CD (FRPW) - Toshiba Mobile CD-RW 2793008 w/Freecom Parallel Cable rev.903 (FRIQ) - Backpack CD-RW 222011 and CD-RW 19350 (BPCK6)The following bugs in low-level protocol drivers were found and willbe fixed later:Note: EPP-32 mode is buggy in EPAT - and also in all other protocoldrivers - they don&apos;t handle non-multiple-of-4 block transferscorrectly. This causes problems with LS-120 drive.There is also another bug in EPAT: EPP modes don&apos;t work unless a 4-bitor 8-bit mode is used first (probably some initialization missing?).Once the device is initialized, EPP works until power cycle.So after device power on, you have to:echo &quot;parport0 epat 0&quot; &gt;/sys/bus/pata_parport/new_deviceecho pata_parport.0 &gt;/sys/bus/pata_parport/delete_deviceecho &quot;parport0 epat 4&quot; &gt;/sys/bus/pata_parport/new_device(autoprobe will initialize correctly as it tries the slowest modesfirst but you&apos;ll get the broken EPP-32 mode)Note: EPP modes are buggy in FRPW, only modes 0 and 1 work.Signed-off-by: Ondrej Zary &lt;linux@zary.sk&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Hannes Reinecke &lt;hare@suse.de&gt;Acked-by: Jens Axboe &lt;axboe@kernel.dk&gt;Signed-off-by: Damien Le Moal &lt;damien.lemoal@opensource.wdc.com&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Mon, 23 Jan 2023 19:09:54 +0000</pubDate>
        <dc:creator>Ondrej Zary &lt;linux@zary.sk&gt;</dc:creator>
    </item>
<item>
        <title>e65e175b - habanalabs: move driver to accel subsystem</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#e65e175b</link>
        <description>habanalabs: move driver to accel subsystemNow that we have a subsystem for compute accelerators, move thehabanalabs driver to it.This patch only moves the files and fixes the Makefiles. Futurepatches will change the existing code to register to the accelsubsystem and expose the accel device char files instead of thehabanalabs device char files.Update the MAINTAINERS file to reflect this change.Signed-off-by: Oded Gabbay &lt;ogabbay@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Mon, 26 Dec 2022 21:05:00 +0000</pubDate>
        <dc:creator>Oded Gabbay &lt;ogabbay@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>35b13763 - accel/ivpu: Introduce a new DRM driver for Intel VPU</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#35b13763</link>
        <description>accel/ivpu: Introduce a new DRM driver for Intel VPUVPU stands for Versatile Processing Unit and it&apos;s a CPU-integratedinference accelerator for Computer Vision and Deep Learningapplications.The VPU device consist of following components:  - Buttress - provides CPU to VPU integration, interrupt, frequency and    power management.  - Memory Management Unit (based on ARM MMU-600) - translates VPU to    host DMA addresses, isolates user workloads.  - RISC based microcontroller - executes firmware that provides job    execution API for the kernel-mode driver  - Neural Compute Subsystem (NCS) - does the actual work, provides    Compute and Copy engines.  - Network on Chip (NoC) - network fabric connecting all the componentsThis driver supports VPU IP v2.7 integrated into Intel Meteor Lakeclient CPUs (14th generation).Module sources are at drivers/accel/ivpu and module name is&quot;intel_vpu.ko&quot;.This patch includes only very besic functionality:  - module, PCI device and IRQ initialization  - register definitions and low level register manipulation functions  - SET/GET_PARAM ioctls  - power up without firmwareCo-developed-by: Krystian Pradzynski &lt;krystian.pradzynski@linux.intel.com&gt;Signed-off-by: Krystian Pradzynski &lt;krystian.pradzynski@linux.intel.com&gt;Signed-off-by: Jacek Lawrynowicz &lt;jacek.lawrynowicz@linux.intel.com&gt;Reviewed-by: Oded Gabbay &lt;ogabbay@kernel.org&gt;Reviewed-by: Jeffrey Hugo &lt;quic_jhugo@quicinc.com&gt;Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20230117092723.60441-2-jacek.lawrynowicz@linux.intel.com

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Tue, 17 Jan 2023 09:27:17 +0000</pubDate>
        <dc:creator>Jacek Lawrynowicz &lt;jacek.lawrynowicz@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>25621bcc - HID: Kconfig: split HID support and hid-core compilation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Makefile#25621bcc</link>
        <description>HID: Kconfig: split HID support and hid-core compilationCurrently, we step into drivers/hid/ based on the value ofCONFIG_HID.However, that value is a tristate, meaning that it can be a module.As per the documentation, if we jump into the subdirectory byfollowing an obj-m, we can not compile anything inside thatsubdirectory in vmlinux. It is considered as a bug.To make things more friendly to HID-BPF, split HID (the HID coreparameter) from HID_SUPPORT (do we want any kind of HID support in thesystem?), and make this new config a boolean.Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Signed-off-by: Benjamin Tissoires &lt;benjamin.tissoires@redhat.com&gt;Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;

            List of files:
            /linux-6.15/drivers/Makefile</description>
        <pubDate>Thu, 03 Nov 2022 15:57:43 +0000</pubDate>
        <dc:creator>Benjamin Tissoires &lt;benjamin.tissoires@redhat.com&gt;</dc:creator>
    </item>
</channel>
</rss>
