<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/neocturne/target/linux, branch main</title>
<subtitle>Staging tree of Nora Schiffer</subtitle>
<id>https://git.openwrt.org/openwrt/staging/neocturne/atom?h=main</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/neocturne/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/'/>
<updated>2024-06-20T13:53:55Z</updated>
<entry>
<title>generic: platform/mikrotik: add NVMEM layout driver</title>
<updated>2024-06-20T13:53:55Z</updated>
<author>
<name>Robert Marko</name>
</author>
<published>2024-06-09T10:14:25Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/commit/?id=73a9f9f857947bc63fef1aefb7e2e4b906fb9d2b'/>
<id>urn:sha1:73a9f9f857947bc63fef1aefb7e2e4b906fb9d2b</id>
<content type='text'>
Currently, information from MikroTik hard_config is only available via
sysfs, meaning that we have to rely on userspace to for example setup MACs.

So, lets provide a basic NVMEM layout based driver to expose the same cells
as sysfs driver exposes.

Do note that the we dont extract the WLAN caldata and BDF-s at this point.

Reviewed-by: Thibaut VARÈNE &lt;hacks@slashdirt.org&gt;
Link: https://github.com/openwrt/openwrt/pull/15665
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
<entry>
<title>generic: platform/mikrotik: move hard config tag ID-s to a header</title>
<updated>2024-06-20T13:53:55Z</updated>
<author>
<name>Robert Marko</name>
</author>
<published>2024-06-10T10:20:11Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/commit/?id=65276193955924c2256f6c93bdfdf6d81ed585ff'/>
<id>urn:sha1:65276193955924c2256f6c93bdfdf6d81ed585ff</id>
<content type='text'>
Move the hard config tag ID-s to a separate header so they can be reused
by the NVMEM driver as well.

Link: https://github.com/openwrt/openwrt/pull/15665
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
<entry>
<title>ath79: trim useless package kmod-leds-reset for some devices</title>
<updated>2024-06-20T12:02:13Z</updated>
<author>
<name>Shiji Yang</name>
</author>
<published>2024-06-19T10:53:01Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/commit/?id=bc5633442867d4993ca7a9ab5bf6a7814bd27536'/>
<id>urn:sha1:bc5633442867d4993ca7a9ab5bf6a7814bd27536</id>
<content type='text'>
Only NETGEAR WNDR3x00 series devices have reset controller LED.

Signed-off-by: Shiji Yang &lt;yangshiji66@qq.com&gt;
</content>
</entry>
<entry>
<title>ath79: disable unnecessary driver CONFIG_LEDS_RESET</title>
<updated>2024-06-20T12:02:13Z</updated>
<author>
<name>Shiji Yang</name>
</author>
<published>2024-06-19T10:52:37Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/commit/?id=5901598586ca22a0747250ab14f1475ab7873a6f'/>
<id>urn:sha1:5901598586ca22a0747250ab14f1475ab7873a6f</id>
<content type='text'>
This driver has already been packed as a software package. There is
no need to build it into the kernel.

Signed-off-by: Shiji Yang &lt;yangshiji66@qq.com&gt;
</content>
</entry>
<entry>
<title>ath79: add back usb LED label for NETGEAR WNDR3x00 devices</title>
<updated>2024-06-20T12:02:13Z</updated>
<author>
<name>Shiji Yang</name>
</author>
<published>2024-06-19T10:52:03Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/commit/?id=66b41c4afd3d1cd7a674c773a5dd4025fe1cd0fb'/>
<id>urn:sha1:66b41c4afd3d1cd7a674c773a5dd4025fe1cd0fb</id>
<content type='text'>
The "reset-leds" driver does not support parsing color and function
properties.

Signed-off-by: Shiji Yang &lt;yangshiji66@qq.com&gt;
</content>
</entry>
<entry>
<title>bcm27xx: fix malformed upstream arm64 DT patch</title>
<updated>2024-06-20T03:55:08Z</updated>
<author>
<name>Álvaro Fernández Rojas</name>
</author>
<published>2024-06-19T18:17:44Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/commit/?id=0a07a3a13dae4a59808359341493416f3653dcce'/>
<id>urn:sha1:0a07a3a13dae4a59808359341493416f3653dcce</id>
<content type='text'>
This patch was causing buildbot issues when copying arm64 DT files since
bcm283x-rpi-csi1-2lane.dtsi and bcm283x-rpi-lan7515.dtsi were linked to
"../../../../arm/boot/dts/" instead of "../../../../arm/boot/dts/broadcom".
These files aren't needed, so let's remove them instead of fixing them.

Signed-off-by: Álvaro Fernández Rojas &lt;noltari@gmail.com&gt;
Link: https://github.com/openwrt/openwrt/pull/15762
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>ath79: ag71xx: support probe defferal for getting MAC address</title>
<updated>2024-06-20T09:11:36Z</updated>
<author>
<name>Robert Marko</name>
</author>
<published>2024-06-19T09:26:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/commit/?id=150d0ceab7380538798df76a5d7d3c12a3632050'/>
<id>urn:sha1:150d0ceab7380538798df76a5d7d3c12a3632050</id>
<content type='text'>
Currently, of_get_ethdev_address() return is checked for any return error
code which means that trying to get the MAC from NVMEM cells that is backed
by MTD will fail if it was not probed before ag71xx.

So, lets check the return error code for EPROBE_DEFER and defer the ag71xx
probe in that case until the underlying NVMEM device is live.

Link: https://github.com/openwrt/openwrt/pull/15752
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
<entry>
<title>ipq40xx: net/ipqess: fix outbound port tag computation</title>
<updated>2024-06-20T08:52:26Z</updated>
<author>
<name>Matthias Schiffer</name>
</author>
<published>2024-06-19T23:05:51Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/commit/?id=0b6b54eca939a2cb757f854594863548fb93f21f'/>
<id>urn:sha1:0b6b54eca939a2cb757f854594863548fb93f21f</id>
<content type='text'>
Since the introduction of out-of-band tagging, writing the outbound tag
had been completely broken: First, in place of a port mask containing
the port number, just the port number itself was set in the register
value. Just after that, the full port mask 0x3e (all 5 external ports)
was set unconditionally.

This remained unnoticed because the switch would then use the FDB to
decide where to send unicast packets; broadcast and multicast packets
were however sent to every port.

Fix the port tag computation and only use the full port mask as a
fallback for non-DSA mode, as it was done in the older driver patches
used on Linux 5.15.

Fixes: cd9c7211241e ("ipq40xx: 6.1: use latest DSA and ethernet patches")
Signed-off-by: Matthias Schiffer &lt;mschiffer@universe-factory.net&gt;
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
<entry>
<title>kernel: bump 6.1 to 6.1.94</title>
<updated>2024-06-20T08:41:50Z</updated>
<author>
<name>Zxl hhyccc</name>
</author>
<published>2024-06-17T16:04:43Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/commit/?id=b004feaafbb9fef8964ccaacfd6cd17f2c6e330a'/>
<id>urn:sha1:b004feaafbb9fef8964ccaacfd6cd17f2c6e330a</id>
<content type='text'>
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.94

All other patches automatically rebased.

Build system: Kirkwood bcm53xx

Signed-off-by: Zxl hhyccc &lt;zxlhhy@gmail.com&gt;
</content>
</entry>
<entry>
<title>lantiq: fix pci driver once again</title>
<updated>2024-06-20T07:56:50Z</updated>
<author>
<name>Martin Schiller</name>
</author>
<published>2024-06-17T06:27:59Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/neocturne/commit/?id=f6fe19ed6dfaf0444cd80f530bf89f6878fd5936'/>
<id>urn:sha1:f6fe19ed6dfaf0444cd80f530bf89f6878fd5936</id>
<content type='text'>
In my previous attempt to solve the PCI problems for the lantiq targets,
I did not pay attention to the fact that the original accesses to the
GPIO took place in RAW mode. As a result, the polarity defined in the
device trees (apart from the initial value) was irrelevant.

In addition, the expected name of the GPIO in the dts has changed due to
the upstream change and therefore no RESET is currently performed.

As discussed in [1] on the linux-mips mailing list, we will now adapt
the dts files accordingly instead of patching the driver:

- dts property will be renamed to "reset-gpios"
- Polarity is set to "GPIO_ACTIVE_LOW".

I have verified this with a TP-Link TD-W8980. The PCI device is now
recognized by the system.

[1] https://patchwork.kernel.org/project/linux-mips/patch/20240607090400.1816612-1-ms@dev.tdt.de/

Signed-off-by: Martin Schiller &lt;ms@dev.tdt.de&gt;
Tested-by: Aleksander Jan Bajkowski &lt;olek2@wp.pl&gt; # Tested on AVM 7330 (ar9)
Link: https://github.com/openwrt/openwrt/pull/15731
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
</feed>
