<?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 MINI2440</title>
    <link>http://nxr.netbsd.org/rss/src/sys/arch/evbarm/conf/MINI2440</link>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2005</copyright>
    <generator>Java</generator>
    
<item>
    <title>Remove last traces of 'options LKM' from kernel config files.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.35</description>
    <pubDate>Wed Mar 19 21:03:40 UTC 2025</pubDate>
    <dc:creator>jakllsch</dc:creator>
</item>

<item>
    <title>branches:  1.34.10;<br/>UFS/LFS dirhash:<br/>- Enable UFS_DIRHASH if the architecture or kernel model specific config<br/>  file can use 128MB of RAM or more.<br/>- Remove experimental tag from UFS_DIRHASH; it's been with RUMP kernel<br/>  and by a number of NetBSD developers for years.<br/>- Add LFS_DIRHASH if LFS was enabled.<br/>- Be somewhat consistent with FS options order.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.34</description>
    <pubDate>Sun Aug 07 02:52:25 UTC 2022</pubDate>
    <dc:creator>simonb</dc:creator>
</item>

<item>
    <title>Remove uscanner(4) driver<br/><br/>This exists for compatibility with a Linux interface which was apparently<br/>deprecated in Linux 2.6. There are various mailing list threads going<br/>back to 2004 where the usefulness of this driver is discussed, but<br/>the conclusion is that scanner software has all moved to using ugen(4)<br/>instead, and enabling this driver will not help you scan things.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.33</description>
    <pubDate>Tue Jun 29 10:22:35 UTC 2021</pubDate>
    <dc:creator>nia</dc:creator>
</item>

<item>
    <title>branches:  1.32.6;<br/>vether: Add to kernel configurations<br/><br/>It's only enabled if the kernel enabled bridge AND tap.<br/>Otherwise it's commented out.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.32</description>
    <pubDate>Sun Sep 27 13:48:50 UTC 2020</pubDate>
    <dc:creator>roy</dc:creator>
</item>

<item>
    <title>Remove references to BRIDGE_IPF, it is now compiled in by default.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.31</description>
    <pubDate>Sat Aug 01 08:20:48 UTC 2020</pubDate>
    <dc:creator>maxv</dc:creator>
</item>

<item>
    <title>Remove uyap, USB YAP phone firmware loader.<br/><br/>And the associated ezload EZ-USB code, which is only used by uyap.<br/>It could theoretically be used by other drivers, but none of them are<br/>in tree.<br/><br/>I suspect that this device isn't in use, as phone technology has improved<br/>a lot since 2001 when uyap(4) was added to the tree.<br/><br/>Proposed with no objections on netbsd-users on 13 April 2020</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.30</description>
    <pubDate>Sat May 16 13:46:11 UTC 2020</pubDate>
    <dc:creator>maya</dc:creator>
</item>

<item>
    <title>PMAP_DEBUG has been deleted on arm</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.29</description>
    <pubDate>Sat Apr 18 11:00:38 UTC 2020</pubDate>
    <dc:creator>skrll</dc:creator>
</item>

<item>
    <title>branches:  1.28.4;<br/>remove urio(4), a driver for the Rio500 MP3 player.<br/><br/>At this point it is highly unlikely this 1999 device still has users,<br/>but it still comes up in the context of maxv's USB-fuzzing (and any device<br/>could pretend to be a urio(4)), so it's best to get rid of it.<br/><br/>Renamed all major entries to obsolete, as was done in previous removals.<br/><br/>This still requires an update to sanitizers, but they're located in<br/>"external", perhaps it should be first committed upstream?<br/><br/>Proposed on tech-kern a month ago.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.28</description>
    <pubDate>Wed Jan 29 18:39:01 UTC 2020</pubDate>
    <dc:creator>maya</dc:creator>
</item>

<item>
    <title>Remove the strip(4) - Starmode Radio IP - pseudo-device driver.  It is<br/>long since obsolete.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.27</description>
    <pubDate>Sun Jan 19 01:25:04 UTC 2020</pubDate>
    <dc:creator>thorpej</dc:creator>
</item>

<item>
    <title>branches:  1.26.6;<br/>Add ure(4) to kernel config files. Also add PHY drivers where necessary.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.26</description>
    <pubDate>Wed Feb 06 11:58:30 UTC 2019</pubDate>
    <dc:creator>rin</dc:creator>
</item>

<item>
    <title>remove the 'wd* at umass?' for the non-standardized and rare (extinct?)<br/>In-System Design ATA protocol over Bulk-Only devices from most kernels,<br/>leave only in i386/amd64 ALL; it's unmaintained and likely currently broken,<br/>lack of test hardware makes it impossible to support</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.25</description>
    <pubDate>Tue Oct 23 19:58:52 UTC 2018</pubDate>
    <dc:creator>jdolecek</dc:creator>
</item>

<item>
    <title>Add (commented out) mue(4) to where appropriate.<br/>Also add MII/PHY drivers for USB NICs if missing.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.24</description>
    <pubDate>Sat Aug 25 20:52:40 UTC 2018</pubDate>
    <dc:creator>rin</dc:creator>
</item>

<item>
    <title>Unreference IPF/PF from all the config files, and enable NPF instead when<br/>wanted. This also fixes some inconsistencies I saw in several files (eg<br/>IPF options while IPF was not compiled, IPF+PF enabled by default, etc).</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.23</description>
    <pubDate>Wed Aug 01 20:04:11 UTC 2018</pubDate>
    <dc:creator>maxv</dc:creator>
</item>

<item>
    <title>branches:  1.22.2;  1.22.4;<br/>clean up COMPAT_* options for native netbsd code:<br/>- new series of files that are useful for saying "i want everything<br/>  since netbsd 1.4", etc.<br/>- use the fact COMPAT_* options have future dependancies to remove<br/>  many redundant options.<br/><br/>removes about 3000 lines total across kernel configuration files.<br/>tested about 30 random kernels in the changed list.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.22</description>
    <pubDate>Thu Sep 14 07:58:40 UTC 2017</pubDate>
    <dc:creator>mrg</dc:creator>
</item>

<item>
    <title>Remove TCP_COMPAT_42 from the config files. Pass 3.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.21</description>
    <pubDate>Sat Jul 29 18:08:57 UTC 2017</pubDate>
    <dc:creator>maxv</dc:creator>
</item>

<item>
    <title>PR kern/51208<br/>Add DISKLABEL_EI option (and also FFS_EI if missing), commented out except for<br/>ALL on amd64 and i386.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.20</description>
    <pubDate>Sun Feb 19 07:47:00 UTC 2017</pubDate>
    <dc:creator>rin</dc:creator>
</item>

<item>
    <title>branches:  1.19.2;<br/>wildcard speaker attachments, now that we can handle many of them.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.19</description>
    <pubDate>Tue Dec 13 20:42:17 UTC 2016</pubDate>
    <dc:creator>christos</dc:creator>
</item>

<item>
    <title>remove VAUDIOSPEAKER for now, will be done differently.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.18</description>
    <pubDate>Sat Dec 10 23:03:23 UTC 2016</pubDate>
    <dc:creator>christos</dc:creator>
</item>

<item>
    <title>Add a synthesized pc beeper and keyboard bell for platforms with an audio<br/>device.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.17</description>
    <pubDate>Thu Dec 08 11:31:10 UTC 2016</pubDate>
    <dc:creator>nat</dc:creator>
</item>

<item>
    <title>branches:  1.16.2;<br/>Remove KMEMSTATS.</title>
    <description>/src/sys/arch/evbarm/conf/MINI2440 - 1.16</description>
    <pubDate>Wed Aug 12 07:53:57 UTC 2015</pubDate>
    <dc:creator>maxv</dc:creator>
</item>
</channel></rss>

