<?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>16934de4 - auxdisplay: linedisp: Group display drivers together</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#16934de4</link>
        <description>auxdisplay: linedisp: Group display drivers togetherFor better usability group the display drivers together in Kconfig.With this we will have the following sections:  - Character LCD  - Samsung KS0108 LCD controller  - Single character line display  - Character LCD with non-conforming interfaceKeep Makefile entries sorted alphabetically.While at it, drop redundant &apos;default n&apos; entries.Tested-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Tue, 26 Mar 2024 19:02:27 +0000</pubDate>
        <dc:creator>Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>899383f9 - auxdisplay: Add 7-segment LED display driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#899383f9</link>
        <description>auxdisplay: Add 7-segment LED display driverAdd a driver for a 7-segment LED display. At the moment only onecharacter is supported but it should be possible to expand this tosupport more characters and/or 14-segment displays in the future.Signed-off-by: Chris Packham &lt;chris.packham@alliedtelesis.co.nz&gt;Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Thu, 07 Mar 2024 19:50:51 +0000</pubDate>
        <dc:creator>Chris Packham &lt;chris.packham@alliedtelesis.co.nz&gt;</dc:creator>
    </item>
<item>
        <title>a9bcd02f - auxdisplay: Add driver for MAX695x 7-segment LED controllers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#a9bcd02f</link>
        <description>auxdisplay: Add driver for MAX695x 7-segment LED controllersAdd initial driver for the MAX6958 and MAX6959 7-segment LEDcontrollers.Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Mon, 26 Feb 2024 16:19:21 +0000</pubDate>
        <dc:creator>Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>7e76aece - auxdisplay: Extract character line display core support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#7e76aece</link>
        <description>auxdisplay: Extract character line display core supportExtract the character line display core support from the simple ASCIILCD driver for the MIPS Boston, Malta &amp; SEAD3 development boards intoits own subdriver, so it can be reused for other displays.As this moves the &quot;message&quot; device attribute in sysfs in a &quot;linedisp.N&quot;subdirectory, a symlink is added to preserve backwards compatibility.Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Signed-off-by: Miguel Ojeda &lt;ojeda@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Tue, 19 Oct 2021 14:45:05 +0000</pubDate>
        <dc:creator>Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;</dc:creator>
    </item>
<item>
        <title>8c9108d0 - auxdisplay: add a driver for lcd2s character display</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#8c9108d0</link>
        <description>auxdisplay: add a driver for lcd2s character displayThis driver allows to use a lcd2s 20x4 character display from Modtronixengineering as an auxdisplay charlcd device.Signed-off-by: Lars Poeschel &lt;poeschel@lemonage.de&gt;Signed-off-by: Miguel Ojeda &lt;ojeda@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Tue, 03 Nov 2020 09:58:28 +0000</pubDate>
        <dc:creator>Lars Poeschel &lt;poeschel@lemonage.de&gt;</dc:creator>
    </item>
<item>
        <title>718e05ed - auxdisplay: Introduce hd44780_common.[ch]</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#718e05ed</link>
        <description>auxdisplay: Introduce hd44780_common.[ch]There is some hd44780 specific code in charlcd and this code is used bymultiple drivers. To make charlcd independent from this device specificcode this has to be moved to a place where the multiple drivers canshare their common code. This common place is now introduced ashd44780_common.Reviewed-by: Willy Tarreau &lt;w@1wt.eu&gt;Signed-off-by: Lars Poeschel &lt;poeschel@lemonage.de&gt;Signed-off-by: Miguel Ojeda &lt;ojeda@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Tue, 03 Nov 2020 09:58:05 +0000</pubDate>
        <dc:creator>Lars Poeschel &lt;poeschel@lemonage.de&gt;</dc:creator>
    </item>
<item>
        <title>24c764ab - auxdisplay: deconfuse configuration</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#24c764ab</link>
        <description>auxdisplay: deconfuse configurationThe auxdisplay Kconfig is confusing.  It creates two separate menuseven though the settings are closely related.  Moreover, the optionsfor setting the boot message depend on CONFIG_PARPORT even though theyare used by drivers that do not.Clear up the confusion by moving the &quot;Parallel port LCD/Keypad&quot; menuunder auxdisplay where it logically belongs.  Change the boot messageoptions to depend only on CONFIG_CHARLCD, making them accessible alsowhen only the HD44780 is selected.Since the &quot;Parallel port LCD/Keypad&quot; driver now has a new dependencyon CONFIG_AUXDISPLAY, rename its Kconfig symbol and keep the old onesuch that make oldconfig will not disable the driver.Signed-off-by: Mans Rullgard &lt;mans@mansr.com&gt;Signed-off-by: Miguel Ojeda &lt;miguel.ojeda.sandonis@gmail.com&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Fri, 01 Mar 2019 18:48:14 +0000</pubDate>
        <dc:creator>Mans Rullgard &lt;mans@mansr.com&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/auxdisplay/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/auxdisplay/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>00846a44 - auxdisplay: Move arm-charlcd.c to drivers/auxdisplay folder</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#00846a44</link>
        <description>auxdisplay: Move arm-charlcd.c to drivers/auxdisplay folderIt looks like arm-charlcd.c belongs to auxdisplay subsystem.Move it to drivers/auxdisplay folder.No functional changes intended.Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Tue, 04 Apr 2017 17:25:22 +0000</pubDate>
        <dc:creator>Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>51c1e9b5 - auxdisplay: Move panel.c to drivers/auxdisplay folder</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#51c1e9b5</link>
        <description>auxdisplay: Move panel.c to drivers/auxdisplay folderIt looks like panel.c belongs to auxdisplay subsystem.Move it to drivers/auxdisplay folder.No functional changes intended.Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Tue, 04 Apr 2017 17:25:21 +0000</pubDate>
        <dc:creator>Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>d47d8836 - auxdisplay: Add HD44780 Character LCD support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#d47d8836</link>
        <description>auxdisplay: Add HD44780 Character LCD supportThe Hitachi HD44780 Character LCD Controller is commonly used oncharacter LCDs that can display one or more lines of text.This driver supports character LCDs connected to GPIOs, using either a4-bit or 8-bit data bus, and provides access through the charlcd coreand /dev/lcd.Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Fri, 10 Mar 2017 14:15:21 +0000</pubDate>
        <dc:creator>Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;</dc:creator>
    </item>
<item>
        <title>39f8ea46 - auxdisplay: charlcd: Extract character LCD core from misc/panel</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#39f8ea46</link>
        <description>auxdisplay: charlcd: Extract character LCD core from misc/panelExtract the character LCD core from the Parallel port LCD/Keypad Paneldriver in the misc subsystem, and convert it into a subdriver in theauxdisplay subsystem.  This allows the character LCD core to be used byother drivers later.Compilation is controlled by its own Kconfig symbol CHARLCD, which is tobe selected by its users, but can be enabled manually forcompile-testing.All functions changed their prefix from &quot;lcd_&quot; to &quot;charlcd_&quot;, and gaineda &quot;struct charlcd *&quot; parameter to operate on a specific instance.While the driver API thus is ready to support multiple instances, thecurrent limitation of a single display (/dev/lcd has a single misc minorassigned) is retained.No functional changes intended.Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Fri, 10 Mar 2017 14:15:17 +0000</pubDate>
        <dc:creator>Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;</dc:creator>
    </item>
<item>
        <title>8992da44 - auxdisplay: ht16k33: Driver for LED controller</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#8992da44</link>
        <description>auxdisplay: ht16k33: Driver for LED controllerAdded a driver for the Holtek HT16K33 LED controller with keyscan.Signed-off-by: Robin van der Gracht &lt;robin@protonic.nl&gt;CC: Miguel Ojeda Sandonis &lt;miguel.ojeda.sandonis@gmail.com&gt;Acked-by: Rob Herring &lt;robh@kernel.org&gt;Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Mon, 07 Nov 2016 09:56:35 +0000</pubDate>
        <dc:creator>Robin van der Gracht &lt;robin@protonic.nl&gt;</dc:creator>
    </item>
<item>
        <title>0cad855f - auxdisplay: img-ascii-lcd: driver for simple ASCII LCD displays</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#0cad855f</link>
        <description>auxdisplay: img-ascii-lcd: driver for simple ASCII LCD displaysAdd a driver for simple ASCII LCD displays found on the MIPS Boston,Malta &amp; SEAD3 development boards. The Boston display is an independentmemory mapped device with a simple memory mapped 8 byte register spacecontaining the 8 ASCII characters to display. The Malta display isexposed as part of the Malta board registers, and provides 8 registerseach of which corresponds to one of the ASCII characters to display. TheSEAD3 display is slightly more complex, exposing an interface to anS6A0069 LCD controller via registers provided by the boards CPLD.However although the displays differ in their register interface, werequire similar functionality on each board so abstracting away thedifferences within a single driver allows us to share a significantamount of code &amp; ensure consistent behaviour.The driver displays the Linux kernel version as the default message, butallows the message to be changed via a character device. Messages longerthen the number of characters that the display can show will scroll.This provides different behaviour to the existing LCD display code forthe MIPS Malta or MIPS SEAD3 platforms in the following ways:  - The default string to display is not &quot;LINUX ON MALTA&quot; or &quot;LINUX ON    SEAD3&quot; but &quot;Linux&quot; followed by the version number of the kernel    (UTS_RELEASE).  - Since that string tends to be significantly longer it scrolls twice    as fast, moving every 500ms rather than every 1s.  - The LCD won&apos;t be updated until the driver is probed, so it doesn&apos;t    provide the early &quot;LINUX&quot; string.Signed-off-by: Paul Burton &lt;paul.burton@imgtec.com&gt;Cc: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;Cc: Miguel Ojeda Sandonis &lt;miguel.ojeda.sandonis@gmail.com&gt;Cc: Guenter Roeck &lt;linux@roeck-us.net&gt;Cc: David S. Miller &lt;davem@davemloft.net&gt;Cc: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Cc: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Cc: Andrew Morton &lt;akpm@linux-foundation.org&gt;Cc: linux-mips@linux-mips.orgCc: linux-kernel@vger.kernel.orgPatchwork: https://patchwork.linux-mips.org/patch/14062/Signed-off-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Fri, 26 Aug 2016 14:17:49 +0000</pubDate>
        <dc:creator>Paul Burton &lt;paul.burton@imgtec.com&gt;</dc:creator>
    </item>
<item>
        <title>70e84049 - [PATCH] drivers: add LCD support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/auxdisplay/Makefile#70e84049</link>
        <description>[PATCH] drivers: add LCD supportAdd support for auxiliary displays, the ks0108 LCD controller, thecfag12864b LCD and adds a framebuffer device: cfag12864bfb.- Add a &quot;auxdisplay/&quot; folder in &quot;drivers/&quot; for auxiliary display  drivers.- Add support for the ks0108 LCD Controller as a device driver.  (uses  parport interface)- Add support for the cfag12864b LCD as a device driver.  (uses ks0108  LCD Controller driver)- Add a framebuffer device called cfag12864bfb.  (uses cfag12864b LCD  driver)- Add the usual Documentation, includes, Makefiles, Kconfigs,  MAINTAINERS, CREDITS...- Miguel Ojeda will maintain all the stuff above.[rdunlap@xenotime.net: workqueue fixups][akpm@osdl.org: kconfig fix]Signed-off-by: Miguel Ojeda Sandonis &lt;maxextreme@gmail.com&gt;Cc: Greg KH &lt;greg@kroah.com&gt;Acked-by: Paulo Marques &lt;pmarques@grupopie.com&gt;Cc: &quot;Randy.Dunlap&quot; &lt;rdunlap@xenotime.net&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/drivers/auxdisplay/Makefile</description>
        <pubDate>Sat, 10 Feb 2007 09:44:32 +0000</pubDate>
        <dc:creator>Miguel Ojeda Sandonis &lt;maxextreme@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
