<?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>87be41f0 - char/agp: Remove frontend code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#87be41f0</link>
        <description>char/agp: Remove frontend codeThe AGP subsystem supports a user-space interface via /dev/agpgart. Itis only enabled with DRM support for mode setting in user space. (i.e.,CONFIG_DRM_LEGACY). All of that DRM code has been removed and the optionwill go away. Hence remove the AGP frontend.Modern DRM drivers with kernel mode setting handle AGP support internally.Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Reviewed-by: David Airlie &lt;airlied@gmail.com&gt;Reviewed-by: Daniel Vetter &lt;daniel@ffwll.ch&gt;Acked-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20231122122449.11588-14-tzimmermann@suse.de

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Wed, 22 Nov 2023 12:09:42 +0000</pubDate>
        <dc:creator>Thomas Zimmermann &lt;tzimmermann@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>cf8e8658 - arch: Remove Itanium (IA-64) architecture</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#cf8e8658</link>
        <description>arch: Remove Itanium (IA-64) architectureThe Itanium architecture is obsolete, and an informal survey [0] revealsthat any residual use of Itanium hardware in production is mostly HP-UXor OpenVMS based. The use of Linux on Itanium appears to be limited toenthusiasts that occasionally boot a fresh Linux kernel to see whetherthings are still working as intended, and perhaps to churn out somedistro packages that are rarely used in practice.None of the original companies behind Itanium still produce or supportany hardware or software for the architecture, and it is listed as&apos;Orphaned&apos; in the MAINTAINERS file, as apparently, none of the engineersthat contributed on behalf of those companies (nor anyone else, for thatmatter) have been willing to support or maintain the architectureupstream or even be responsible for applying the odd fix. The Intelfirmware team removed all IA-64 support from the Tianocore/EDK2reference implementation of EFI in 2018. (Itanium is the originalarchitecture for which EFI was developed, and the way Linux supports itdeviates significantly from other architectures.) Some distros, such asDebian and Gentoo, still maintain [unofficial] ia64 ports, but many havedropped support years ago.While the argument is being made [1] that there is a &apos;for the commongood&apos; angle to being able to build and run existing projects such as theGrid Community Toolkit [2] on Itanium for interoperability testing, thefact remains that none of those projects are known to be deployed onLinux/ia64, and very few people actually have access to such a system inthe first place. Even if there were ways imaginable in which Linux/ia64could be put to good use today, what matters is whether anyone isactually doing that, and this does not appear to be the case.There are no emulators widely available, and so boot testing Itanium isgenerally infeasible for ordinary contributors. GCC still supports IA-64but its compile farm [3] no longer has any IA-64 machines. GLIBC wouldlike to get rid of IA-64 [4] too because it would permit some overduecode cleanups. In summary, the benefits to the ecosystem of having IA-64be part of it are mostly theoretical, whereas the maintenance overheadof keeping it supported is real.So let&apos;s rip off the band aid, and remove the IA-64 arch code entirely.This follows the timeline proposed by the Debian/ia64 maintainer [5],which removes support in a controlled manner, leaving IA-64 in a knowngood state in the most recent LTS release. Other projects will followonce the kernel support is removed.[0] https://lore.kernel.org/all/CAMj1kXFCMh_578jniKpUtx_j8ByHnt=s7S+yQ+vGbKt9ud7+kQ@mail.gmail.com/[1] https://lore.kernel.org/all/0075883c-7c51-00f5-2c2d-5119c1820410@web.de/[2] https://gridcf.org/gct-docs/latest/index.html[3] https://cfarm.tetaneutral.net/machines/list/[4] https://lore.kernel.org/all/87bkiilpc4.fsf@mid.deneb.enyo.de/[5] https://lore.kernel.org/all/ff58a3e76e5102c94bb5946d99187b358def688a.camel@physik.fu-berlin.de/Acked-by: Tony Luck &lt;tony.luck@intel.com&gt;Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Thu, 20 Oct 2022 13:54:33 +0000</pubDate>
        <dc:creator>Ard Biesheuvel &lt;ardb@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>f9f92e7c - char/agp: Disable frontend without CONFIG_DRM_LEGACY</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#f9f92e7c</link>
        <description>char/agp: Disable frontend without CONFIG_DRM_LEGACYIt&apos;s probably full of bugs ready for exploiting by userspace. Andthere&apos;s not going to be any userspace for this without any of the drmlegacy drivers enabled too. So just couple it together.Note that the frontend is only the /dev/agp ioctl interface, which perAdam is only used by the i810 userspace drivers. All other drivers gothrough the drm bufmap agp handling abstraction apparently.v2: Augment commit message a bit from m-l feedback.Acked-by: Adam Jackson &lt;ajax@redhat.com&gt;Acked-by: Christian K&#246;nig &lt;christian.koenig@amd.com&gt;Acked-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;Cc: David Airlie &lt;airlied@linux.ie&gt;Cc: Adam Jackson &lt;ajax@redhat.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20201117214029.591896-1-daniel.vetter@ffwll.ch

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Tue, 17 Nov 2020 21:40:29 +0000</pubDate>
        <dc:creator>Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;</dc:creator>
    </item>
<item>
        <title>defdeacb - char/agp: remove the sgi-agp driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#defdeacb</link>
        <description>char/agp: remove the sgi-agp driverThe SGI SN2 support is about to be removed.  Remove this driver thatdepends on the SN2 support.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Link: https://lkml.kernel.org/r/20190813072514.23299-4-hch@lst.deSigned-off-by: Tony Luck &lt;tony.luck@intel.com&gt;

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Tue, 13 Aug 2019 07:24:49 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>00fe639a - drm/i915: Make AGP support optional</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#00fe639a</link>
        <description>drm/i915: Make AGP support optionalWe only depend on the intel-gtt module for GTT frobbign on older gens.The intel_agp module is optional, except for UMS and some old XvMCuserland on gen3. So make AGP support optional. As before, we willfail the i915 init for UMS and gen3 KMS the same as before ifintel_agp isn&apos;t around.intel-gtt.c is left with a somewhat ugly ifdef mess, but I&apos;m goingto save that for a later cleaning.At least my gen2 still works with the patch and CONFIG_AGP=n.v2: Make i915 depend on X86 and PCI, and intel-gtt depend on PCISigned-off-by: Ville Syrj&#228;l&#228; &lt;ville.syrjala@linux.intel.com&gt;Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Tue, 05 Nov 2013 12:00:08 +0000</pubDate>
        <dc:creator>Ville Syrj&#228;l&#228; &lt;ville.syrjala@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>e2404e7c - agp/intel: make intel-gtt.c into a real source file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#e2404e7c</link>
        <description>agp/intel: make intel-gtt.c into a real source fileNow that the disentangling is complete, stop including intel-gtt.cfrom intel-agp.c.The linux build system _really_ doesn&apos;t allow .c source files with thesame name as the module. It fails with the following message when tryingto build such a bugger:make[3]: Circular drivers/char/agp/intel-agp.o &lt;- drivers/char/agp/intel-agp.o dependency dropped.Instead of renameing intel-agp.c I&apos;ve simply created a new module outof intel-gtt.c. Renaming intel-agp.ko to something else is not an optionfor it will surely kill someones boot process.This also paves the way to use the gtt code without loading the agpdriver.Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;Signed-off-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Wed, 08 Sep 2010 15:29:51 +0000</pubDate>
        <dc:creator>Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;</dc:creator>
    </item>
<item>
        <title>a5220b46 - [AGPGART] Fix modular agpgart ia64 allmodconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#a5220b46</link>
        <description>[AGPGART] Fix modular agpgart ia64 allmodconfigMy previous compat AGP patch broke modular AGPGART.Test built on;i386 CONFIG_AGP=y,mx86_64 CONFIG_AGP=yia64 CONFIG_AGP=mSigned-off-by: Zwane Mwaikambo &lt;zwane@infradead.org&gt;Cc: Kyle McMartin &lt;kyle@mcmartin.ca&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Dave Jones &lt;davej@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Fri, 16 Feb 2007 07:09:00 +0000</pubDate>
        <dc:creator>Zwane Mwaikambo &lt;zwane@infradead.org&gt;</dc:creator>
    </item>
<item>
        <title>0316fe83 - [AGPGART] compat ioctl</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#0316fe83</link>
        <description>[AGPGART] compat ioctlThe following video card requires the agpgart driver ioctlinterface in order to detect video memory.00:02.0 VGA compatible controller: Intel Corporation Mobile945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)Tested on a Thinkpad Z61t, Xorg.0.log from a 32bit debian Xorg is at;http://montezuma.homeunix.net/Xorg.0.logSigned-off-by: Zwane Mwaikambo &lt;zwane@infradead.org&gt;Signed-off-by: Dave Jones &lt;davej@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Tue, 30 Jan 2007 05:20:31 +0000</pubDate>
        <dc:creator>Zwane Mwaikambo &lt;zwane@infradead.org&gt;</dc:creator>
    </item>
<item>
        <title>08a64368 - [PARISC] Add support for Quicksilver AGPGART</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#08a64368</link>
        <description>[PARISC] Add support for Quicksilver AGPGARTSigned-off-by: Kyle McMartin &lt;kyle@parisc-linux.org&gt;

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Fri, 25 Aug 2006 01:33:40 +0000</pubDate>
        <dc:creator>Kyle McMartin &lt;kyle@parisc-linux.org&gt;</dc:creator>
    </item>
<item>
        <title>1da177e4 - Linux-2.6.12-rc2</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/char/agp/Makefile#1da177e4</link>
        <description>Linux-2.6.12-rc2Initial git repository build. I&apos;m not bothering with the full history,even though we have it. We can create a separate &quot;historical&quot; gitarchive of that later if we want to, and in the meantime it&apos;s about3.2GB when imported into git - space that would just make the earlygit days unnecessarily complicated, when we don&apos;t have a lot of goodinfrastructure for it.Let it rip!

            List of files:
            /linux-6.15/drivers/char/agp/Makefile</description>
        <pubDate>Sat, 16 Apr 2005 22:20:36 +0000</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@ppc970.osdl.org&gt;</dc:creator>
    </item>
</channel>
</rss>
