<?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 Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>3ce48580 - mtd: ubi: provide NVMEM layer over UBI volumes</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#3ce48580</link>
        <description>mtd: ubi: provide NVMEM layer over UBI volumesIn an ideal world we would like UBI to be used where ever possible on aNAND chip. And with UBI support in ARM Trusted Firmware and U-Boot itis possible to achieve an (almost-)all-UBI flash layout. Hence the needfor a way to also use UBI volumes to store board-level constants, suchas MAC addresses and calibration data of wireless interfaces.Add UBI volume NVMEM driver module exposing UBI volumes as NVMEMproviders. Allow UBI devices to have a &quot;volumes&quot; firmware subnode withvolumes which may be compatible with &quot;nvmem-cells&quot;.Access to UBI volumes via the NVMEM interface at this point isread-only, and it is slow, opening and closing the UBI volume for eachaccess due to limitations of the NVMEM provider API.Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;Signed-off-by: Richard Weinberger &lt;richard@nod.at&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Tue, 19 Dec 2023 02:33:48 +0000</pubDate>
        <dc:creator>Daniel Golle &lt;daniel@makrotopia.org&gt;</dc:creator>
    </item>
<item>
        <title>6931fb44 - ubi: Use the fault injection framework to enhance the fault injection capability</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#6931fb44</link>
        <description>ubi: Use the fault injection framework to enhance the fault injection capabilityTo make debug parameters configurable at run time, use thefault injection framework to reconstruct the debugfs interface,and retain the legacy fault injection interface.Now, the file emulate_failures and fault_attr files control whetherto enable fault emmulation.The file emulate_failures receives a mask that controls type andprocess of fault injection. Generally, for ease of use, you candirectly enter a mask with all 1s.echo 0xffff &gt; /sys/kernel/debug/ubi/ubi0/emulate_failuresAnd you need to configure other fault-injection capabilities fortesting purpose:echo 100 &gt; /sys/kernel/debug/ubi/fault_inject/emulate_power_cut/probabilityecho 15 &gt; /sys/kernel/debug/ubi/fault_inject/emulate_power_cut/spaceecho 2 &gt; /sys/kernel/debug/ubi/fault_inject/emulate_power_cut/verboseecho -1 &gt; /sys/kernel/debug/ubi/fault_inject/emulate_power_cut/timesThe CONFIG_MTD_UBI_FAULT_INJECTION to enable the Fault Injection isadded to kconfig.Signed-off-by: ZhaoLong Wang &lt;wangzhaolong1@huawei.com&gt;Reviewed-by: Zhihao Cheng &lt;chengzhihao1@huawei.com&gt;Signed-off-by: Richard Weinberger &lt;richard@nod.at&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Tue, 26 Dec 2023 01:01:09 +0000</pubDate>
        <dc:creator>ZhaoLong Wang &lt;wangzhaolong1@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#ec8f24b7</link>
        <description>treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is:  GPL-2.0-onlySigned-off-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/mtd/ubi/Kconfig</description>
        <pubDate>Sun, 19 May 2019 12:07:45 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>2fae1312 - UBI: Fix typos</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#2fae1312</link>
        <description>UBI: Fix typosSigned-off-by: Andrew F. Davis &lt;afd@ti.com&gt;Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Thu, 05 Jan 2017 20:44:49 +0000</pubDate>
        <dc:creator>Andrew F. Davis &lt;afd@ti.com&gt;</dc:creator>
    </item>
<item>
        <title>22d3ee5c - UBI: block: Add CONFIG_BLOCK dependency</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#22d3ee5c</link>
        <description>UBI: block: Add CONFIG_BLOCK dependencyThe UBI block driver depends on the block infrastructure. Add theproper dependency and fix a build error when CONFIG_BLOCK is not selected.Reported-by: kbuild test robot &lt;fengguang.wu@intel.com&gt;Signed-off-by: Ezequiel Garcia &lt;ezequiel.garcia@free-electrons.com&gt;Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Mon, 03 Mar 2014 16:42:40 +0000</pubDate>
        <dc:creator>Ezequiel Garcia &lt;ezequiel.garcia@free-electrons.com&gt;</dc:creator>
    </item>
<item>
        <title>9d54c8a3 - UBI: R/O block driver on top of UBI volumes</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#9d54c8a3</link>
        <description>UBI: R/O block driver on top of UBI volumesThis commit introduces read-only block device emulation on top of UBI volumes.Given UBI takes care of wear leveling and bad block management it&apos;s possibleto add a thin layer to enable block device access to UBI volumes.This allows to use a block-oriented filesystem on a flash device.The UBI block devices are meant to be used in conjunction with anyregular, block-oriented file system (e.g. ext4), although it&apos;s primarilytargeted at read-only file systems, such as squashfs.Block devices are created upon user request through new ioctls:UBI_IOCVOLATTBLK to attach and UBI_IOCVOLDETBLK to detach.Also, a new UBI module parameter is added &apos;ubi.block&apos;. This parameter isneeded in order to attach a block device on boot-up time, allowing tomount the rootfs on a ubiblock device.For instance, you could have these kernel parameters:  ubi.mtd=5 ubi.block=0,0 root=/dev/ubiblock0_0Or, if you compile ubi as a module:  $ modprobe ubi mtd=/dev/mtd5 block=/dev/ubi0_0Artem: amend commentaries and massage the patch a little bit.Signed-off-by: Ezequiel Garcia &lt;ezequiel.garcia@free-electrons.com&gt;Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Tue, 25 Feb 2014 16:25:22 +0000</pubDate>
        <dc:creator>Ezequiel Garcia &lt;ezequiel.garcia@free-electrons.com&gt;</dc:creator>
    </item>
<item>
        <title>76ac66e4 - UBI: Wire-up fastmap</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#76ac66e4</link>
        <description>UBI: Wire-up fastmapMake fastmap known to Kconfig, UBI Makefile and MAINTAINERS.Signed-off-by: Richard Weinberger &lt;richard@nod.at&gt;Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Wed, 26 Sep 2012 15:51:50 +0000</pubDate>
        <dc:creator>Richard Weinberger &lt;richard@nod.at&gt;</dc:creator>
    </item>
<item>
        <title>db7e21c2 - UBI: add max_beb_per1024 to attach ioctl</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#db7e21c2</link>
        <description>UBI: add max_beb_per1024 to attach ioctlThis patch provides a possibility to set the &quot;maximum expected number ofbad blocks per 1024 blocks&quot; (max_beb_per1024) for each mtd device usingthe UBI_IOCATT ioctl.Signed-off-by: Richard Genoud &lt;richard.genoud@gmail.com&gt;Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Mon, 20 Aug 2012 16:00:15 +0000</pubDate>
        <dc:creator>Richard Genoud &lt;richard.genoud@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>edac493d - UBI: allow specifying bad PEBs limit using module parameter</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#edac493d</link>
        <description>UBI: allow specifying bad PEBs limit using module parameterThis patch provides the possibility to adjust the &quot;maximum expected number ofbad blocks per 1024 blocks&quot; (max_beb_per1024) for each mtd device.The majority of NAND devices have their max_beb_per1024 equal to 20, butsometimes it&apos;s more.Now, we can adjust that via a kernel parameter:ubi.mtd=&lt;name|num|path&gt;[,&lt;vid_hdr_offs&gt;[,max_beb_per1024]]Signed-off-by: Richard Genoud &lt;richard.genoud@gmail.com&gt;Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Mon, 20 Aug 2012 16:00:14 +0000</pubDate>
        <dc:creator>Richard Genoud &lt;richard.genoud@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>ba4087e9 - UBI: use the whole MTD device size to get bad_peb_limit</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#ba4087e9</link>
        <description>UBI: use the whole MTD device size to get bad_peb_limitOn NAND flash devices, UBI reserves some physical erase blocks (PEB) forbad block handling. Today, the number of reserved PEB can only be set as apercentage of the total number of PEB in each MTD partition. For example, for aNAND flash with 128KiB PEB, 2 MTD partition of 20MiB (mtd0) and 100MiB (mtd1)and 2% reserved PEB: - the UBI device on mtd0 will have 2 PEB reserved - the UBI device on mtd1 will have 16 PEB reservedThe problem with this behaviour is that NAND flash manufacturers give aminimum number of valid block (NVB) during the endurance life of thedevice, e.g.:Parameter             Symbol    Min    Max    Unit      Notes--------------------------------------------------------------Valid block number     NVB     1004    1024   Blocks     1From this number we can deduce the maximum number of bad PEB that a device willcontain during its endurance life: a 128MiB NAND flash (1024 PEB) will not haveless than 20 bad blocks during the flash endurance life.But the manufacturer doesn&apos;t tell where those bad block will appear. He doesn&apos;tsay either if they will be equally disposed on the whole device (and I&apos;m prettysure they won&apos;t). So, according to the datasheets, we should reserve themaximum number of bad PEB for each UBI device (worst case scenario: 20 badblocks appears on the smallest MTD partition).So this patch make UBI use the whole MTD device size to calculate the maximumbad expected eraseblocks.The Kconfig option is in per1024 blocks, thus it can have a default value of 20which is *very* common for NAND devices.Signed-off-by: Richard Genoud &lt;richard.genoud@gmail.com&gt;Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Tue, 10 Jul 2012 16:23:41 +0000</pubDate>
        <dc:creator>Richard Genoud &lt;richard.genoud@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>1b2a5790 - UBI: kill CONFIG_MTD_UBI_BEB_RESERVE</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#1b2a5790</link>
        <description>UBI: kill CONFIG_MTD_UBI_BEB_RESERVECONFIG_MTD_UBI_BEB_RESERVE and MIN_RESEVED_PEBS are no longer used,since the amount of reserved eraseblocks for bad PEB handling is nowderived from &apos;ubi-&gt;bad_peb_limit&apos; (ubi&apos;s maximum expected baderaseblocks).Signed-off-by: Shmulik Ladkani &lt;shmulik.ladkani@gmail.com&gt;Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Wed, 04 Jul 2012 08:06:02 +0000</pubDate>
        <dc:creator>Shmulik Ladkani &lt;shmulik.ladkani@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>8beeb3bb - UBI: introduce new bad PEB limit</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#8beeb3bb</link>
        <description>UBI: introduce new bad PEB limitIntroduce &apos;ubi-&gt;bad_peb_limit&apos;, which specifies an upper limit of PEBsUBI expects to go bad.  Currently, it is initialized to a fixed percentageof total PEBs in the UBI device (configurable via CONFIG_MTD_UBI_BEB_LIMIT).The &apos;bad_peb_limit&apos; is intended to be used for calculating the amount of PEBsUBI needs to reserve for bad eraseblock handling.Artem: minor amendments.Signed-off-by: Shmulik Ladkani &lt;shmulik.ladkani@gmail.com&gt;Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Wed, 04 Jul 2012 08:06:00 +0000</pubDate>
        <dc:creator>Shmulik Ladkani &lt;shmulik.ladkani@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>54de1f1c - UBI: Change the default percentage of reserved PEB</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#54de1f1c</link>
        <description>UBI: Change the default percentage of reserved PEBThe actual value (1%) is too low for actual NAND devices, a hugemajority of device has 2% maximum bad blocks (SLC or MLC).(Actually it&apos;s 20 blocks on a 1024 blocks device, 40/2048...)Signed-off-by: Richard Genoud &lt;richard.genoud@gmail.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Fri, 29 Jun 2012 06:57:41 +0000</pubDate>
        <dc:creator>Richard Genoud &lt;richard.genoud@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>aa44d1d3 - UBI: remove Kconfig debugging option</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#aa44d1d3</link>
        <description>UBI: remove Kconfig debugging optionThis patch kills the UBI debugging Kconfig option completely and makes all thedebugging stuff to be always compiled-in. It was pain in the neck to maintainthis useless option because all users I am aware of have debugging enabledanyway - how else will you diagnose errors otherwise?Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Wed, 16 May 2012 15:09:08 +0000</pubDate>
        <dc:creator>Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>6bef0b67 - UBI: do not select KALLSYMS_ALL</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#6bef0b67</link>
        <description>UBI: do not select KALLSYMS_ALLAll UBI needs is to make sure we stacktraces when UBI debuggingis enabled. It is enough to select KALLSYMS for this, KALLSYMS_ALLis not necessary.And the current Kconfig line we have:select KALLSYMS_ALL if KALLSYMS &amp;&amp; DEBUG_KERNELis just too complex to be sane and right. But this &quot;if&quot; part thereis needed to prevent &quot;unmet direct dependency&quot; warnings, becauseKALLSYMS_ALL depends on KALLSYMS and DEBUG_KERNEL, so we cannotjust select KALLSYMS_ALL.Anyway, this feels messy, and we do not seem to really need KALLSYMS_ALL,so select KALLSYMS instead.Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;Acked-by: Randy Dunlap &lt;randy.dunlap@oracle.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Wed, 30 Mar 2011 08:27:08 +0000</pubDate>
        <dc:creator>Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;</dc:creator>
    </item>
<item>
        <title>28237e45 - UBI: make tests modes dynamic</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#28237e45</link>
        <description>UBI: make tests modes dynamicSimilarly to the debugging checks and message, make the test modesbe dynamically selected via the &quot;debug_tsts&quot; module parameter orvia the &quot;/sys/module/ubi/parameters/debug_tsts&quot; sysfs file. Thisis consistent with UBIFS as well.And now, since all the Kconfig knobs became dynamic, we can removethe Kconfig.debug file completely.Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Tue, 15 Mar 2011 08:30:40 +0000</pubDate>
        <dc:creator>Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;</dc:creator>
    </item>
<item>
        <title>1dd78632 - UBI: cleanup and simplify Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#1dd78632</link>
        <description>UBI: cleanup and simplify KconfigCleanup the Kconfig for UBI by using menuconfig to enable/disable the entiredriver. Remove the dependency checks for MTD_UBI and MTD_UBI_DEBUG bywrapping the options in if/endif blocks and remove any redundant checks.Remove all default n since that is the Kconfig default. Change menu &quot;AdditionalUBI debugging messages&quot; into a comment to remove one menu level.Signed-off-by: H Hartley Sweeten &lt;hsweeten@visionengravers.com&gt;Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Fri, 20 Aug 2010 00:28:50 +0000</pubDate>
        <dc:creator>H Hartley Sweeten &lt;hartleys@visionengravers.com&gt;</dc:creator>
    </item>
<item>
        <title>3f502622 - UBI: fix s/then/than/ typos</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#3f502622</link>
        <description>UBI: fix s/then/than/ typosSigned-off-by: Shinya Kuribayashi &lt;shinya.kuribayashi.px@renesas.com&gt;Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Thu, 06 May 2010 10:21:47 +0000</pubDate>
        <dc:creator>Shinya Kuribayashi &lt;shinya.kuribayashi.px@renesas.com&gt;</dc:creator>
    </item>
<item>
        <title>fa301231 - Kconfig: Remove useless and sometimes wrong comments</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#fa301231</link>
        <description>Kconfig: Remove useless and sometimes wrong commentsAdditionally, some excessive newlines removed.Signed-off-by: Michael Roth &lt;mroth@nessie.de&gt;Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Sun, 04 Oct 2009 16:14:29 +0000</pubDate>
        <dc:creator>Michael Roth &lt;mroth@nessie.de&gt;</dc:creator>
    </item>
<item>
        <title>2ba3d76a - UBI: make gluebi a separate module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mtd/ubi/Kconfig#2ba3d76a</link>
        <description>UBI: make gluebi a separate module[Artem: re-worked the patch: made it release resources when themodule is unloaded, made it do module referencing, made it reallyindependent on UBI, tested it with the UBI test-suite which canbe found in ubi-2.6.git/tests/ubi-tests, re-named most of thefuncs/variables to get rid of the &quot;ubi&quot; word and make namesconsistent.]Signed-off-by: Dmitry Pervushin &lt;dpervushin@embeddedalley.com&gt;Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;

            List of files:
            /linux-6.15/drivers/mtd/ubi/Kconfig</description>
        <pubDate>Sun, 31 May 2009 14:32:59 +0000</pubDate>
        <dc:creator>Dmitry Pervushin &lt;dpervushin@embeddedalley.com&gt;</dc:creator>
    </item>
</channel>
</rss>
