<?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>fea0c645cdda00b15fa4b5b2998d564bcc75e72f - A driver for the DS28E17 1-Wire to I2C bridge chip.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#fea0c645cdda00b15fa4b5b2998d564bcc75e72f</link>
        <description>A driver for the DS28E17 1-Wire to I2C bridge chip.This chip acts like a 1-Wire slave device and provides a iic(4) masterat the end of the 1-Wire bus.  More or less it is the polar oppositeof the DS2482 [ds2482ow(4)] chip.This device couples well with ds2482ow(4) and can be used to provide aI2C bus at very great lengths from the controlling computer.All features of the chip are supported, except for 1-Wire overdrivesupport, which requires more work from the onewire(4) infrastructure.The chip does not support Read without Stop.  Attempts to do this willget turned into a Read with Stop and one will have to hope for thebest.  The chip also does not support zero length I2C reads or zerolength I2C writes.  This has the side effect of making the defaultmode, a zero length I2C write, for i2scan(8) return false positives.The alternative mode that i2cscan(8) can use, the single byte read,should work as expected.The chip has automatic support for end devices that do I2C clockstretching.It was noticed that this chip does not work with the gpioow(4) driver.That might be an interesting thing to debug if one has a good logicanalyzer on hand.  While the presence pulse is detected, the gpioow(4)driver is not able to complete the initial ROM enumeration.  TheDS28E17 works flawlessly when driven by a DS2482 [ds2482ow(4)] driverchip.  Poke me if you want any more details.The chip is pretty inexpensive and only requires a single cap to getit hooked up.  However, the package it comes in is only a 16-QFNpackage, so it could provide to be hard to solider onto a board forsome.  There are side tabs, so it was possible with a very small ironand lots of flux.  There is a slightly expensive breakout board soldby Mikroe that probably works well -&gt; https://www.mikroe.com/1-wire-i2c-click

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Thu, 23 Jan 2025 19:02:42 +0000</pubDate>
        <dc:creator>brad &lt;brad@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>8d3fa1acc28e1ff6af9c437324879065e5ba94a6 - Add ncm(4) a driver for USB Network Control Model</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#8d3fa1acc28e1ff6af9c437324879065e5ba94a6</link>
        <description>Add ncm(4) a driver for USB Network Control ModelSeen on my Google Pixel 8, which implements ncm instead of urndis.

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Mon, 20 Jan 2025 13:54:54 +0000</pubDate>
        <dc:creator>maya &lt;maya@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>93180dafca416a6043637ba1243e1f22c5ee2120 - Add a driver for the Maxim DS2482-100 and DS2482-800 I2C to 1-Wire</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#93180dafca416a6043637ba1243e1f22c5ee2120</link>
        <description>Add a driver for the Maxim DS2482-100 and DS2482-800 I2C to 1-Wirebridge.This chip provides a I2C device that then has 1 or 8 1-Wire busses onthe other side.  The 1-Wire buses show up as onewire(4) buses in theNetBSD.The chip can be used in situations where:* You have a I2C bus extended a long distance, say with a LTC4311  active terminator / extender or one of the differential I2C  extenders and you would like to have a 1-Wire device on the far end  and it isn&apos;t possible to add wiring to get to the far end.* You are either out of GPIO pins or the GPIO pins are not reliable  enough to use gpioow(4), but you do have working I2C.The DS2482 does all of the 1-Wire signals in hardware and provides fora couple of pullup options for the 1-Wire devices.All of the functions of the DS2482-100 and -800 are supported exceptfor overdrive speed support.  To do this will likely require some APIchanges to onewire(4).Breakout boards exist for the DS2482 for both variants, but theyappear to be more expensive than expected.  The chip itself is quietcheap and wasn&apos;t all that hard to SMD solder to a board.  No othercomponents are really needed.There are other members in the same family, the DS2482-101, DS2484 andDS2485.  The DS2482-101 has a sleep pin, but from the datasheetappears to program the same as the -100 variant.  The DS2484 has aslightly different way to set configuration information and probablywon&apos;t quite work with the driver, but isn&apos;t far off.  The DS2485 isvery different and would require a new driver to function.

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Mon, 04 Nov 2024 20:43:37 +0000</pubDate>
        <dc:creator>brad &lt;brad@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>375351f47f69413f3f25505414610ff54f26d458 - acpivmgenid(4): New driver for virtual machine generation ID.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#375351f47f69413f3f25505414610ff54f26d458</link>
        <description>acpivmgenid(4): New driver for virtual machine generation ID.Added to amd64/ALL and i386/ALL kernel configurations, and madeavailable as a loadable module acpivmgenid.kmod on x86, for now.TBD: Add to all ACPI-supporting GENERIC kernels.PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VMfork

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Mon, 26 Aug 2024 13:38:27 +0000</pubDate>
        <dc:creator>riastradh &lt;riastradh@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>0a864b32ba193b6a4090e2e190e22d95336a8318 - modules: Build `ipl` module only if MKIPFILTER is enabled</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#0a864b32ba193b6a4090e2e190e22d95336a8318</link>
        <description>modules: Build `ipl` module only if MKIPFILTER is enabled

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Thu, 18 Jul 2024 04:28:54 +0000</pubDate>
        <dc:creator>rin &lt;rin@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>8f43f9fe8803017240b7fad5d341a940c91646ee - Oooppss remove some local change that was accidentally committed</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#8f43f9fe8803017240b7fad5d341a940c91646ee</link>
        <description>Oooppss remove some local change that was accidentally committed

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Mon, 20 May 2024 18:14:38 +0000</pubDate>
        <dc:creator>pgoyette &lt;pgoyette@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>210acb050bd16f4496dd993d98975ab050707cd6 - Don&apos;t build the compat_110 module yet - there&apos;s no release_110  with which</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#210acb050bd16f4496dd993d98975ab050707cd6</link>
        <description>Don&apos;t build the compat_110 module yet - there&apos;s no release_110  with whichwe can be compatable.

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Mon, 20 May 2024 17:32:51 +0000</pubDate>
        <dc:creator>pgoyette &lt;pgoyette@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>67daa9c8c8b887320a3d4428c99cf22f77d1a259 - sys/modules: Don&apos;t make compat_110.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#67daa9c8c8b887320a3d4428c99cf22f77d1a259</link>
        <description>sys/modules: Don&apos;t make compat_110.Eventually we&apos;ll need this but it doesn&apos;t make sense until 11.0 isreleased.

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Mon, 20 May 2024 13:34:12 +0000</pubDate>
        <dc:creator>riastradh &lt;riastradh@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>381b1356d06b80c02bcf1fce3a8053bd593afe58 - version dup3</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#381b1356d06b80c02bcf1fce3a8053bd593afe58</link>
        <description>version dup3

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Sun, 19 May 2024 22:25:47 +0000</pubDate>
        <dc:creator>christos &lt;christos@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>3dc92541ecadb39b5ed11aaddb6152dc8cdb9d23 - port-arm/58194: Resurrect vmt(4) from bitrot</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#3dc92541ecadb39b5ed11aaddb6152dc8cdb9d23</link>
        <description>port-arm/58194: Resurrect vmt(4) from bitrotOn this architecture vmt(4) used to search for a node &quot;/hypervisor&quot; in theFDT and probed the VMware hypervisor call only when the node wasfound. However, things appear to have changed and VMware no longer providesthe FDT node.Since vmt(4) doesn&apos;t actually need to read anything from FDT, and thehypervisor call logically resides in virtual CPUs themselves, it would bebetter to attach it directly to cpu, just like how it&apos;s probed on x86.

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Thu, 09 May 2024 12:09:58 +0000</pubDate>
        <dc:creator>pho &lt;pho@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>2dda1941ab960be1373b0ecee199c56f3682d039 - bsd.own.mk: Enable MKLSJIT on aarch64.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#2dda1941ab960be1373b0ecee199c56f3682d039</link>
        <description>bsd.own.mk: Enable MKLSJIT on aarch64.Make sure there&apos;s only one copy of the conditional, in bsd.own.mk;just make sys/modules/Makefile conditional on MKSLJIT so we don&apos;thave to keep these in sync.As a workaround for PR 58106, tweak the conditional definition ofSLJIT_CACHE_FLUSH to use cpu_icache_sync_range only in _HARDKERNEL,and use __builtin___clear_cache in userland and in rump kernels.PR 58103: bpfjit.kmod is not built on aarch64

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Tue, 02 Apr 2024 22:37:34 +0000</pubDate>
        <dc:creator>riastradh &lt;riastradh@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>40cfbdd6f37ed783be0d378f91a3aaf35103db4d - acpihed(4): New driver for PNP0C33 to notify apei(4).</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#40cfbdd6f37ed783be0d378f91a3aaf35103db4d</link>
        <description>acpihed(4): New driver for PNP0C33 to notify apei(4).PNP0C33 denotes the ACPI Hardware Error Device, which exists only tobe a vector for event notifications.PR kern/58046

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Thu, 21 Mar 2024 02:36:01 +0000</pubDate>
        <dc:creator>riastradh &lt;riastradh@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>4b159fe528de68c639f4f9cd4d8b3ef59df8a58d - apei(4): New driver for ACPI Platform Error Interfaces.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#4b159fe528de68c639f4f9cd4d8b3ef59df8a58d</link>
        <description>apei(4): New driver for ACPI Platform Error Interfaces.For now it is wired up only in x86 ALL kernels, and built as a modulefor x86 and Arm.  Once it gets a little more testing on machines withAPEI, I would like to flip it on by default.PR kern/58046

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Wed, 20 Mar 2024 17:11:42 +0000</pubDate>
        <dc:creator>riastradh &lt;riastradh@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>cec94d4f24730f62e883e2693cb0b617c76324ef - skip this subdir for &quot;make includes&quot;.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#cec94d4f24730f62e883e2693cb0b617c76324ef</link>
        <description>skip this subdir for &quot;make includes&quot;.it&apos;s excessively slow and does nothing (nor should it.)

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Sat, 09 Mar 2024 06:53:48 +0000</pubDate>
        <dc:creator>mrg &lt;mrg@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>dd048da8dc1fb0d1d66aeabdf3ab0aa75f774d14 - Unhook radeondrm module from the build; it doesn&apos;t work, and</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#dd048da8dc1fb0d1d66aeabdf3ab0aa75f774d14</link>
        <description>Unhook radeondrm module from the build; it doesn&apos;t work, andit&apos;s just tempting someone to try it.  Leave the files aroundin case someone wants to pursue making this work.Should address kern/57793XXX Related modules from the same legacy era should probably beXXX removed, too, but so far only radeondrm has been reportedXXX as an issue.  Kep an eye out for sisdrm, savagedrm, tdfxdrm,XXX and r128drm.

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Tue, 26 Dec 2023 16:20:01 +0000</pubDate>
        <dc:creator>pgoyette &lt;pgoyette@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>670e7745862fb4fca41233d21c0678b2f168af3c - make owtemp a module</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#670e7745862fb4fca41233d21c0678b2f168af3c</link>
        <description>make owtemp a module

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Sun, 27 Aug 2023 13:20:09 +0000</pubDate>
        <dc:creator>kardel &lt;kardel@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>2c4d4878499fc28b3cc15c924782633084daed7c - viadrmums(4): build legacy VIA DRM UMS driver module for amd64.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#2c4d4878499fc28b3cc15c924782633084daed7c</link>
        <description>viadrmums(4): build legacy VIA DRM UMS driver module for amd64.This driver is not built-in by default, thus loadable module can help (un)luckyowners of 64-bit capable VIA (Nano/Eden) systems or early AMD/Intel systemswith some VIA chipsets, which include VIA integrated graphics.I also boldly added product IDs for few later models from VX8xx/VX9xx chipsetswithout 3D support (DX9_0) to &quot;expand&quot; the driver support to more systems.Tested successfully basic functionality on VX800, and partially successfullyon VX900 (on VX900 Xorg failed to initialize due to openchrome related issues,viadrmums attaches and it is by used the driver).Didn&apos;t test on VX855, I don&apos;t have one.Pull up to netbsd-10 is needed.

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Wed, 09 Aug 2023 09:36:26 +0000</pubDate>
        <dc:creator>andvar &lt;andvar@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>75b842b84762e0251223b719bf77fbef2e651bf6 - RISC-V support that works on QEMU with a single hart.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#75b842b84762e0251223b719bf77fbef2e651bf6</link>
        <description>RISC-V support that works on QEMU with a single hart.Thanks for Simon Burge for plic(4).

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Sun, 07 May 2023 12:41:45 +0000</pubDate>
        <dc:creator>skrll &lt;skrll@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>7b522c96ae2a81e8a10bc203232cdb2309892bb1 - sys/modules/Makefile: Use MACHINE_CPU, not MACHINE_ARCH, for aarch64.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#7b522c96ae2a81e8a10bc203232cdb2309892bb1</link>
        <description>sys/modules/Makefile: Use MACHINE_CPU, not MACHINE_ARCH, for aarch64.This way it covers both little-endian and big-endian.

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Thu, 13 Apr 2023 07:03:31 +0000</pubDate>
        <dc:creator>riastradh &lt;riastradh@NetBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>d5970c6d00eb942a1c19c7baf196b071c31e06b1 - aarch64: Build drm modules.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/netbsd-src/sys/modules/Makefile#d5970c6d00eb942a1c19c7baf196b071c31e06b1</link>
        <description>aarch64: Build drm modules.

            List of files:
            /netbsd-src/sys/modules/Makefile</description>
        <pubDate>Tue, 11 Apr 2023 10:30:41 +0000</pubDate>
        <dc:creator>riastradh &lt;riastradh@NetBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
