Re: [PATCH 2/2] realtek: add RTL821X_CHIP_ID

On Tue, 7 May 2024 at 12:16, Bjørn Mork wrote: > > Stijn Tintel writes: > > > On 27/04/2024 11:16, Bjørn Mork wrote: > >> st...@linux-ipv6.be writes: > >> > >>> phy_write_paged(phydev, 31, 27, 0x0002); > >>> val = phy_read_paged(phydev, 31, 28); > >> .. > >>> phy_write_paged(phydev,

Re: snort3 (at least) not building in 23.05

Hi Eric, On Tue, 9 Apr 2024 at 18:59, Eric via openwrt-devel wrote: > > The sender domain has a DMARC Reject/Quarantine policy which disallows > sending mailing list messages using the original "From" header. > > To mitigate this problem, the original message has been wrapped > automatically by

Re: [PATCH v2 6/9] router: Apply updated values from RFC8319 (updates RFC4861) to RA/ND

Hi, On Fri, 5 Apr 2024 at 13:11, Paul Donald wrote: > > From: Paul Donald > > https://www.rfc-editor.org/rfc/rfc8319#section-4 > > Signed-off-by: Paul Donald > Reviewed-by: Daniel Golle > --- > src/router.c | 6 -- > src/router.h | 21 - > 2 files changed, 24

Re: [PATCH 1/1] scripts: create kernel configuration upgrade script

On Wed, 7 Feb 2024 at 12:58, Felix Baumann via openwrt-devel wrote: > Am 7. Februar 2024 11:53:55 MEZ schrieb Jonas Gorski : > >On Wed, 7 Feb 2024 at 02:48, Elliott Mitchell wrote: > >> > >> Create a script for automating kernel version changes. This > >> gen

Re: [PATCH 1/1] scripts: create kernel configuration upgrade script

On Wed, 7 Feb 2024 at 02:48, Elliott Mitchell wrote: > > Create a script for automating kernel version changes. This > generates a pair of commits which cause history to remain attached > to all versioned configuration files. Why is this script needed? What exactly does it do? Does it preserve

Re: kernel config files and subtarget config-default files

Hi, On Mon, 22 Jan 2024 at 21:27, Tim Harvey wrote: > > Greetings, > > What is the best known method to add items to config-$KVER when you > have subtargets with individual config-default files - specifically > how are the items in this file ordered properly? Maybe the norm is to > put them

Re: [PATCH RESEND 06/11] Revert "x86/geode: enable X86_INTEL_LPSS to select PINCTRL"

On Wed, 13 Dec 2023 at 23:55, Elliott Mitchell wrote: > > On Wed, Dec 13, 2023 at 01:59:07PM +0100, Martin Schiller wrote: > > On 2023-12-13 02:45, Elliott Mitchell wrote: > > > > > > No idea, I wasn't able to find very much information when I looked at > > > this. > > > > > > I did find: > > >

Re: [PATCH RESEND 06/11] Revert "x86/geode: enable X86_INTEL_LPSS to select PINCTRL"

Hi, On Sun, 10 Dec 2023 at 18:51, Elliott Mitchell wrote: > > Date: Fri, 3 Nov 2023 22:57:43 -0700 > > Enabling an Intel chipset feature on a platform originally made by > National Semiconductor and later bought by AMD. Could we cut the Intel > enthusiasm? > > This reverts commit

Re: [PATCH RESEND 02/11] kernel/generic: remove CONFIG_FB_NOTIFY

Hi, On Sun, 10 Dec 2023 at 18:49, Elliott Mitchell wrote: > > Date: Tue, 25 Apr 2023 16:23:20 -0700 > > This option is automatically enabled by CONFIG_FB=y. There is no > reason to specifically enable it. Unfortunately this change will cause the symbol to appear in target configs when using

Re: [PATCH 07/20] kernel: copy all built kernel modules to root filesystem image

Hi, On Mon, 20 Nov 2023 at 02:37, Elliott Mitchell wrote: > > On Sat, Nov 18, 2023 at 07:57:35AM +0100, Felix Fietkau wrote: > > On 17.11.23 22:31, Elliott Mitchell wrote: > > > On Fri, Nov 17, 2023 at 05:20:33PM +0100, Felix Fietkau wrote: > > >> On 11.11.23 01:21, Elliott Mitchell wrote: > >

Re: [PATCH] Deactivate _FORTIFY_SOURCE in jitterentropy-base.c

Hi, On Mon, 30 Oct 2023 at 23:11, Hauke Mehrtens wrote: > > This fixes compilation with glibc. > > _FORTIFY_SOURCE only works with compiler optimizations activated. > We have to deactivate it when we set -O0. > > This fixes the following error message with glibc: > error: #warning

Re: [PATCH] build: explicitly specify Makefile generator

On Sun, 8 Oct 2023 at 18:56, wrote: > > From: Eicke Herbertz > > When CMAKE_GENERATOR environment variable is defined, CMake will use the > specified generator by default instead of "Unix Makefiles". > This breaks the build of packages setting PKG_USE_NINJA to 0, like > package/kernel/mt76.

Re: [PATCH v2 0/9] Resurrect OpenWrt IXP4xx support

Hi, On Thu, 28 Sept 2023 at 15:29, Linus Walleij wrote: > > XP4xx was deleted because of lack of maintenance in 2020. > > In the years since, the upstream Linux support for IXP4xx has > been rewritten from scratch. It is now pretty well supported > using device tree and modern subsystems that

Re: [PATCH v2 1/9] boot/apex: Restore the APEX boot loader

On Wed, 4 Oct 2023 at 14:51, Robert Marko wrote: > > On Thu, 28 Sept 2023 at 15:29, Linus Walleij wrote: > > > > This is a partial revert of the deletion of the IXP4xx > > target: we restore the APEX boot loader so we can use it > > for the NSLU2 and related targets. > > > > The APEX upstream is

Re: [PATCH] bmips: bcm6368-enetsw: Bump max MTU to 1536

setting MTU to 1500 on port 0 > > After this patch the error is gone. Did you test this? As in verified that 1536 bytes long frames are correctly received and sent? > Cc: Álvaro Fernández Rojas > Cc: Jonas Gorski > Signed-off-by: Linus Walleij > --- > .../bmips/files/drive

Re: [PATCH] urngd: fixes compilation with glibc

Hi, On Sat, 16 Sept 2023 at 05:57, Chukun Pan wrote: > > When compiling with glibc it will result in error: > 1. #warning _FORTIFY_SOURCE requires compiling with optimization (-O) > [-Werror=cpp] > Fix this by compiling with optimization (-O2) by default. > > 2.

Re: [PATCH] ath79: fix MikroTik CPLD driver build error on kernel 6.1

Hi, On Sat, 9 Sept 2023 at 04:44, Shiji Yang wrote: > > From: Shiji Yang > > Since kernel 5.18, the return type in device remove function has > changed from 'int' to 'void'. > > Signed-off-by: Shiji Yang > --- > target/linux/ath79/files/drivers/mfd/rb4xx-cpld.c | 6 ++ > 1 file changed, 6

Re: [PATCH] bcm53xx: Unconditionally build U-Boot for DIR-890L

On Mon, 4 Sept 2023 at 23:00, Linus Walleij wrote: > > On Mon, Sep 4, 2023 at 12:03 PM Rafał Miłecki wrote: > > > I don't see anything incorrect with Linus's original patch. Maybe we > > just have some dependency handling issue in u-boot generic .mk code? > > I have transient problem with the

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

On Mon, 5 Dec 2022 at 11:00, Arnd Bergmann wrote: > > On Sat, Dec 3, 2022, at 23:59, Bjørn Mork wrote: > > "Arnd Bergmann" writes: > >> On Sat, Dec 3, 2022, at 18:02, Bjørn Mork wrote: > >> > >>> Yes, I realize that ALL_KMODS only changes a small subset of symbols > >>> related to kmod packages.

Re: [PATCH] treewide: remove label = "cpu" from DSA dt-binding

On Wed, 30 Nov 2022 at 15:43, Arınç ÜNAL wrote: > > This is not used by the DSA dt-binding, so remove it from all devicetrees. > > Link: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9cc115d8d6f73dd260de1609182f3645844d6907 > Signed-off-by: Arınç ÜNAL > > --- >

Re: [PATCH] ramips: fix Unifi 6 Lite boot failure with v5.15 kernels

On Sun, 6 Nov 2022 at 12:50, Bjørn Mork wrote: > > Jonas Gorski writes: > > > An option is also to set a load address for the dtb in the FIT image, > > then U-Boot will relocate it before passing it to the kernel. > > Yes, that is worth trying. I thought th

Re: [PATCH] ramips: fix Unifi 6 Lite boot failure with v5.15 kernels

On Sat, 5 Nov 2022 at 09:46, Bjørn Mork wrote: > > David Bauer writes: > > On 11/4/22 09:29, Bjørn Mork wrote: > >> You are right that the bootloader must be fixed. But the vendor isn't > >> likely to do that as long as they run older kernels. I believe the > >> OpenWrt policy in such cases is

Re: [OpenWrt-Devel] Inquery

On Wed, 11 Dec 2019 at 15:22, Daniel Golle wrote: > As a community, we decided to give our self a set of minimal rules[1]. > And even though it is in the last position, rule #12 "Be nice to each > other." is meant just as serious as all the other rules. > > So here, not for the first time, you

Re: [OpenWrt-Devel] The meaning of Signed-off-by for netifd [Was: Re: [PATCH netifd] interface: warn if ip6hint is truncated]

Hi, On Tue, 3 Dec 2019 at 16:29, Hans Dedecker wrote: > > On Tue, Dec 3, 2019 at 3:59 PM Uwe Kleine-König > wrote: > > > > Hello Hans, > > > > On 12/3/19 8:50 AM, Hans Dedecker wrote: > > > On Fri, Nov 29, 2019 at 9:29 PM Uwe Kleine-König > > > wrote: > > >> > > >> On 11/29/19 8:50 PM, Hans

Re: [OpenWrt-Devel] [PATCH] uci: Fix Wformat-nonliteral warning

On Tue, 3 Dec 2019 at 01:54, Rosen Penev wrote: > > A const char * variable is being passed as a format string. Unfortunately, > this is not correct. > > A constant expression needs to be passed so that GCC can determine the > types of the format properly. > > Also fixed a different warning that

Re: [OpenWrt-Devel] [PATCH] firewall: Fix Wformat-nonliteral warning

Hi, On Fri, 29 Nov 2019 at 22:06, Rosen Penev wrote: > > Allows GCC to check the formats by switching to a define, which is a > constant expression. > > Fixes: > > warning: format not a string literal, argument types not checked > [-Wformat-nonliteral] > 207 | snprintf(buf, sizeof(buf), tmpl,

Re: [OpenWrt-Devel] [PATCH 2/4] kernel: add backported phy/phylink/sfp patches

On Wed, 27 Nov 2019 at 14:27, Russell King - ARM Linux admin wrote: > > On Wed, Nov 27, 2019 at 02:03:40PM +0100, Jonas Gorski wrote: > > On Wed, 27 Nov 2019 at 13:14, Russell King - ARM Linux admin > > wrote: > > > > > > On Wed, Nov 27, 2019 at

Re: [OpenWrt-Devel] [PATCH 2/4] kernel: add backported phy/phylink/sfp patches

On Wed, 27 Nov 2019 at 13:14, Russell King - ARM Linux admin wrote: > > On Wed, Nov 27, 2019 at 12:57:35PM +0100, Petr Štetiar wrote: > > Russell King - ARM Linux admin [2019-11-27 > > 10:35:10]: > > > > > It makes it very difficult to understand. For example, where is the > > > kernel + kmod

Re: [OpenWrt-Devel] [PATCH 1/4] kernel: remove obsolete phylink/SFP patches

On Mon, 25 Nov 2019 at 18:29, Russell King - ARM Linux admin wrote: > > On Mon, Nov 25, 2019 at 06:10:18PM +0100, Jonas Gorski wrote: > > On Mon, 25 Nov 2019 at 17:49, Russell King wrote: > > > > > > Remove the old phylink/SFP patches from the OpenWRT buil

Re: [OpenWrt-Devel] [PATCH 1/4] kernel: remove obsolete phylink/SFP patches

On Mon, 25 Nov 2019 at 17:49, Russell King wrote: > > Remove the old phylink/SFP patches from the OpenWRT build; these will > be updated with a new set in subsequent. > > 450-reprobe_sfp_phy is also removed for several reasons: > 1) it is not in mainline. > 2) it breaks copper modules that do not

Re: [OpenWrt-Devel] [PATCH libubox 1/9] enable extra compiler checks

On Wed, 20 Nov 2019 at 13:00, Petr Štetiar wrote: > > Let's enforce additional automatic checks enforced by the compiler in > order to catch possible errors during compilation. Does it still compile when only applying this patch? If not, you need to move it to after fixing all issues it now

Re: [OpenWrt-Devel] [PATCH] ath79: enable all space on Netgear ar9344-based WNDR routers

On Tue, 19 Nov 2019 at 17:59, Michal Cieslakiewicz wrote: > > > > > That was my question, if the "new" OpenWrt sysupgrade.bin still works > > in the initial flash. > > > > sysupgrade.bin for this model is in format tar+metadata, it is not > designed to be put into flash directly. Typo, I did

Re: [OpenWrt-Devel] [PATCH] ath79: enable all space on Netgear ar9344-based WNDR routers

On Tue, 19 Nov 2019 at 17:33, Michal Cieslakiewicz wrote: > > Hello, > > > > > Have you checked that flashing a factory.bin image through tftp still > > works? > > > > Yes, it works. On this router the easiest way to flash memory via tftp > is to enter uboot and execute 'fw_recovery' command,

Re: [OpenWrt-Devel] [PATCH] ath79: enable all space on Netgear ar9344-based WNDR routers

On Tue, 19 Nov 2019 at 16:18, Michal Cieslakiewicz wrote: > > Hello David, > > Two questions were raised just after publishing 'all-flash-space' patch. > Now I am ready to provide more information on these issues: > > 0. Downgrade to vendor firmware. > > It is possible. Just don't forget to erase

Re: [OpenWrt-Devel] [PATCH v2 maintainer-tools] patchwork-apply.sh: try to fix DMARC mangled patches

On Sun, 10 Nov 2019 at 10:05, Petr Štetiar wrote: > > In order to avoid DMARC plague in the commit messages: > > 87f9292300cf hostapd: add IEEE 802.11k support > 450d44a8ead2 openssl: change defaults: ENGINE:on, NPN:off, misc > eabc1ddc4541 build: Honour NO_COLOR in include/scan.mk >

Re: [OpenWrt-Devel] [PATCH maintainer-tools] patchwork-apply.sh: help spotting DMARC mangled patches

On Sat, 9 Nov 2019 at 13:55, Petr Štetiar wrote: > > Avoid DMARC plague in the commit messages: > > 87f9292300cf hostapd: add IEEE 802.11k support > 450d44a8ead2 openssl: change defaults: ENGINE:on, NPN:off, misc > eabc1ddc4541 build: Honour NO_COLOR in include/scan.mk > 3fb45576ac16

Re: [OpenWrt-Devel] [PATCH 2/2] base-files: rename SSID with EUI of mac address

On Sat, 9 Nov 2019 at 12:04, wrote: > > Hi, > > > -Original Message- > > From: Jonas Gorski [mailto:jonas.gor...@gmail.com] > > Sent: Samstag, 9. November 2019 10:37 > > To: Adrian Schmutzler > > Cc: OpenWrt Development List ; Rosy > > Song

Re: [OpenWrt-Devel] [PATCH 2/2] base-files: rename SSID with EUI of mac address

On Fri, 8 Nov 2019 at 12:49, Adrian Schmutzler wrote: > > If the label MAC address is provided for a device, the default SSID > will be set to contain the EUI of this address, e.g. OpenWrt-ddeeff. > > With multiple routers, this will help the user to identify his device > based on the MAC address

Re: [OpenWrt-Devel] [PATCH 1/4] dnsmasq: Activate LTO

On Fri, 1 Nov 2019 at 21:55, Hauke Mehrtens wrote: > > This decreases the binary size when PIE ASLR is activated by 8% on MIPS BE. > > old: > 202,020 /usr/sbin/dnsmasq > > new: > 185,676 /usr/sbin/dnsmasq Nice reduction. > > Signed-off-by: Hauke Mehrtens > --- >

Re: [OpenWrt-Devel] OpenWrt 19.07 release schedule ?

On Sun, 8 Sep 2019 at 21:19, Tom Psyborg wrote: > there seem to exist at least a dozen of critical bugs that one would > not like to have as a part of final release, to name a few: > > Mainline ath10k causes crahes in ipq806x / R7800 -> > https://bugs.openwrt.org/index.php?do=details_id=2480 We

Re: [OpenWrt-Devel] [PATCH] treewide: add Generic subtarget if missing

On Sun, 15 Sep 2019 at 12:49, Paul Spooren wrote: > > What you suggest is about what we have right now. This kind of creates a > > misleading situation where for some targets subtargets are present, while > > for others paths and image names are "fixed" in several places to include a > >

Re: [OpenWrt-Devel] [PATCH v2] brcm63xx: R5010UNv2: fix flash partitions for 16MB flash

On Wed, 21 Aug 2019 at 20:57, Daniel Gonzalez Cabanelas wrote: > > The router Nucom R5010UN v2 has the partitions defined for a 8MB flash, but > the > flash chip is 16MB size. Fix it > > Fixes: 474cde61234c ("brcm63xx: probe SPI flash through DT") > --- You are missing a SOB. Regards Jonas

Re: [OpenWrt-Devel] [PATCH] treewide: add Generic subtarget if missing

On Fri, 23 Aug 2019 at 11:04, Paul Spooren wrote: > As in 853e4dd OpenWrt should follow a unified structure, where every > device has a target/subtarget combination, if there is only one > subtarget, call it "Generic". This introduces predictable filenames. If it's about (I assume generated)

Re: [OpenWrt-Devel] Squashfs breakage lottery with UBI WAS: [PATCH RFC 2/2] amp821xx: use newly added pad-squashfs for Meraki MR24

On Sun, 1 Sep 2019 at 13:52, Russell Senior wrote: > > >>>>> "Jonas" == Jonas Gorski writes: > > >> It contains a patch at the end titled: "[PATCH] base-files: pad > >> root.squashfs to 64KiB in ubi volumes" This is another appro

Re: [OpenWrt-Devel] Squashfs breakage lottery with UBI WAS: [PATCH RFC 2/2] amp821xx: use newly added pad-squashfs for Meraki MR24

On Sat, 31 Aug 2019 at 15:31, Christian Lamparter wrote: > > Hello, > > On Saturday, August 31, 2019 2:09:55 PM CEST Jonas Gorski wrote: > > On Sat, 31 Aug 2019 at 01:19, Christian Lamparter > > wrote: > > > > > > On Friday, August 30,

Re: [OpenWrt-Devel] Squashfs breakage lottery with UBI WAS: [PATCH RFC 2/2] amp821xx: use newly added pad-squashfs for Meraki MR24

Hi, On Sat, 31 Aug 2019 at 01:19, Christian Lamparter wrote: > > On Friday, August 30, 2019 11:10:54 PM CEST Russell Senior wrote: > > > "Christian" == Christian Lamparter writes: > > > > Christian> Ok. > > > > Christian> I did push a patch titled: "build: remove harmful -nopad > >

Re: [OpenWrt-Devel] KERNEL_PATCHVER in master

On Wed, 12 Jun 2019 at 11:02, Koen Vandeputte wrote: > > > On 11.06.19 23:12, Jonas Gorski wrote: > > Hi, > > > > On Tue, 11 Jun 2019 at 23:08, Stijn Tintel wrote: > >> Hi, > >> > >> Since we now have a 19.07 branch, is it OK to switch KER

Re: [OpenWrt-Devel] [PATCH 2/2] kernel: package module for SafeXcel crypto engine

On Wed, 5 Jun 2019 at 16:32, Tomasz Maciej Nowak wrote: > > Supports EIP97 and EIP197 found on Armada 37xx, 7k and 8k SoCs. > Unfortunately firmware for EIP197 is not easily obtainable, therefore > to not cause lot of user requests directed at OpenWrt, package it as > module with explanation

Re: [OpenWrt-Devel] [PATCH V3 2/2] script/feeds: add a new command that allows generating a new feeds.conf

On Wed, 5 Jun 2019 at 15:28, John Crispin wrote: > > > On 05/06/2019 15:26, Jonas Gorski wrote: > > On Wed, 5 Jun 2019 at 15:16, John Crispin wrote: > >> > >> On 05/06/2019 15:11, Jonas Gorski wrote: > >>> On Wed, 5 Jun 2019 at 14:58, John Crispin wr

Re: [OpenWrt-Devel] [PATCH V3 2/2] script/feeds: add a new command that allows generating a new feeds.conf

On Wed, 5 Jun 2019 at 15:16, John Crispin wrote: > > > On 05/06/2019 15:11, Jonas Gorski wrote: > > On Wed, 5 Jun 2019 at 14:58, John Crispin wrote: > >> > >> On 05/06/2019 14:54, Jonas Gorski wrote: > >>> Hi, > >>> > >>> On W

Re: [OpenWrt-Devel] [PATCH V3 2/2] script/feeds: add a new command that allows generating a new feeds.conf

On Wed, 5 Jun 2019 at 14:58, John Crispin wrote: > > > On 05/06/2019 14:54, Jonas Gorski wrote: > > Hi, > > > > On Wed, 5 Jun 2019 at 14:33, John Crispin wrote: > >> > >> On 05/06/2019 13:35, Karl Palsson wrote: > >>> John Crisp

Re: [OpenWrt-Devel] [PATCH V3 2/2] script/feeds: add a new command that allows generating a new feeds.conf

Hi, On Wed, 5 Jun 2019 at 14:33, John Crispin wrote: > > > On 05/06/2019 13:35, Karl Palsson wrote: > > John Crispin wrote: > >> On 05/06/2019 12:17, Karl Palsson wrote: > >>> John Crispin wrote: > This can be used inside build setups for easy feeds.conf > generation. > >>> Could you

Re: [OpenWrt-Devel] [PATCH] config: enable some useful features on !SMALL_FLASH devices

On Tue, 15 Jan 2019 at 15:42, Daniel Golle wrote: > > Hi Jonas, > > On Mon, Jan 07, 2019 at 03:48:29PM +0100, Daniel Golle wrote: > > On Mon, Jan 07, 2019 at 02:39:26PM +, Jonas Gorski wrote: > > > On Mon, 7 Jan 2019 at 14:21, Daniel Golle wrote: > > > >

Re: [OpenWrt-Devel] [PATCH] config: enable some useful features on !SMALL_FLASH devices

On Mon, 7 Jan 2019 at 14:21, Daniel Golle wrote: > > On Mon, Jan 07, 2019 at 01:17:34PM +, Jonas Gorski wrote: > > On Mon, 7 Jan 2019 at 11:42, Petr Štetiar wrote: > > > > > > Daniel Golle [2019-01-07 10:03:09]: > > > > > > Hi, > > &

Re: [OpenWrt-Devel] [PATCH] config: enable some useful features on !SMALL_FLASH devices

On Mon, 7 Jan 2019 at 11:42, Petr Štetiar wrote: > > Daniel Golle [2019-01-07 10:03:09]: > > Hi, > > > One. The MT7621 EVB. The TP-LINK RE350 v1 can probably be converted to > > a more sane flash partition layout to gain another megabyte or so. > > I've looked only at mt7621, so this was just

Re: [OpenWrt-Devel] [PATCH] brcm63xx: perform a soft reset on the ehternet switch before its initializiation

Hi, On Sun, 11 Nov 2018 at 15:15, Daniel Gonzalez Cabanelas wrote: > Add a switch reset on brcm63xx SoCs to ensure a sane state before > initializiating the switch. > > Performing this reset on BCM6368 solves the ticket #1925 on the > Observa VH4032N: > > - brcm63xx: VH4032N: no traffic

Re: [OpenWrt-Devel] [PATCH] mvebu: fix the cortex-a9 fpu configure

On 30 August 2018 at 04:31, ayaka wrote: > Both Marvell Armada 37x and 38x support NEON and VFPv3, > so we enable the NEON FPU with the SIMD aliases. But the Armada XP doesn't, so this would break devices based on it (like the WRT1900AC v1). Regards Jonas > > Signed-off-by: ayaka > --- >

Re: [OpenWrt-Devel] [PATCH] [RFC] ath79: ag71xx: apply interface mode to MII0/1_CNTL on ar71xx/ar913x

Hi, On 16 August 2018 at 05:05, Chuanhong Guo wrote: > Signed-off-by: Chuanhong Guo > --- > RFC: > Previous discussion about this patch can be found on GitHub PR#1271. > This patch applies correct interface mode to MII0/1_CNTL register at > 0x1807/ > 0x18070004. But there is a small

Re: [OpenWrt-Devel] [PATCH 2/5] ath79: port cybertan_part from ar71xx

On 10 August 2018 at 23:24, Christian Lamparter wrote: > The cybertan_part mtd parser is ported over from ar71xx and converted > to integrate into the "firmware" mtd splitter. It will no longer add > the u-boot, nvram and art partitions, which were never part of the > special Cybertan header. > >

Re: [OpenWrt-Devel] [PATCH v3] base-files: make wifi report unknown command

On 9 August 2018 at 20:35, Thibaut wrote: > >> On 9 Aug 2018, at 19:58, Jonas Gorski wrote: >> >> On 9 August 2018 at 18:49, Thibaut VARÈNE wrote: >>> Avoid having /sbin/wifi silently ignore unknown keywords and execute >>> "enable"; instea

Re: [OpenWrt-Devel] [PATCH v3] base-files: make wifi report unknown command

On 9 August 2018 at 18:49, Thibaut VARÈNE wrote: > Avoid having /sbin/wifi silently ignore unknown keywords and execute > "enable"; instead display the help message and exit with an error. > > Spell out the 'enable' keyword and preserve the implicit assumption > that runing /sbin/wifi without

Re: [OpenWrt-Devel] [PATCH] mediatek: Fix amount of memory on U7623

On 6 August 2018 at 19:46, Kristian Evensen wrote: > While finalizing support for the U7623 with 512MB RAM, I made an embarrassing > error and configured 1GB RAM for the board. I also forgot to move memory > from the dtsi and to the dts. This commit takes care of my errors. > > While I am

Re: [OpenWrt-Devel] [PATCH] kernel: modules: fix kmod-regmap

On 3 August 2018 at 18:00, Christian Lamparter wrote: > diff --git a/package/kernel/linux/modules/other.mk > b/package/kernel/linux/modules/other.mk > index dd037cf86c..7e18a21db3 100644 > --- a/package/kernel/linux/modules/other.mk > +++ b/package/kernel/linux/modules/other.mk > @@ -718,7

Re: [OpenWrt-Devel] [PATCH] kernel: modules: fix kmod-regmap

On 1 August 2018 at 22:44, Christian Lamparter wrote: > On Wednesday, August 1, 2018 3:21:00 PM CEST Jonas Gorski wrote: >> On 30 July 2018 at 22:35, John Crispin wrote: >> > On 30/07/18 22:33, Christian Lamparter wrote: >> >> >> >> This patch fi

Re: [OpenWrt-Devel] [PATCH] kernel: modules: fix kmod-regmap

On 30 July 2018 at 22:35, John Crispin wrote: > > > On 30/07/18 22:33, Christian Lamparter wrote: >> >> This patch fixes the a compile issue that was triggered by >> apm821xx/sata when kmod-regmap was selected. >> >> The CONFIG_REGMAP is declared in drivers/base/regmap/Kconfig >> as type "bool"

Re: [OpenWrt-Devel] [LEDE-DEV] [RFC 1/2] downloads.mk: introduce name-agnostic PROJECT_GIT variable

On 5 January 2018 at 10:53, Jo-Philipp Wich wrote: > Introduce a name-agnostic PROJECT_GIT variable poiting to > https://git.openwrt.org/ and declare LEDE_GIT and OPENWRT_GIT > as aliases to it. > > After some transition time we can drop this alias variables. > > Signed-off-by:

[OpenWrt-Devel] Ownership for LEDE Members on OpenWrt (Was: extending OpenWrt packages maintainers by a new member)

On 19 December 2017 at 15:10, Ted Hess wrote: > Ack from me. > > While you're at it - Alexander Couzens (@lynxis) should have Member status > too. > > And... I wouldn't mind Owner status here since I have it everywhere else (If > someone would be so kind). Since we agreed

Re: [OpenWrt-Devel] [PATCH] linux: Get rid of 000-keep_initrafs_the_default.patch

Hi, On 22 July 2016 at 12:18, Alexey Brodkin wrote: > With that patch in place for initramfs no additional options are > reported for "/" partition. What's really important is missing > info about sizes. Which in its turn makes opkg think that there's > no space on

Re: [OpenWrt-Devel] [PATCH 1/2] layerscape: add ls1043ardb-64b target

Hi, On 13 July 2016 at 19:56, wrote: > From: Yutang Jiang > > Add support for NXP layerscape ls1043ardb-64b Dev board. Nice to see support for it here. A few things first, though > > ls1043ardb-64b target is using 4.1 kernel and rcw/u-boot/fman

Re: [OpenWrt-Devel] [PATCH 1/2] swconfig: implement (PHY) generic PORT_LINK setter

Hi, On 21 January 2016 at 14:55, Rafał Miłecki wrote: > It's quite common for switches to have PHY per port so we may use a > generic function for setting port link. We just need an API to access > PHYs which this patch also adds. > > Signed-off-by: Rafał Miłecki

Re: [OpenWrt-Devel] [PATCH] brcm63xx: Let the CFE partition in HG556a to be writeable

Hi, On Wed, Dec 2, 2015 at 9:37 PM, dani wrote: > In the HG556a router the partition mtd0, where CFE lives, is read only. > This patch allows this partition to be writeable. > > The BCM6358 SoC has two cores, but they are not identical. The second core has > half icache. >

Re: [OpenWrt-Devel] [PATCH] brcm63xx: add support for ZyXEL P870HNU-51b

Hi, On 20 December 2015 at 04:52, Mohammed Berdai wrote: > This router is a ZyXEL VDSL2 router and its board has : > chip ID: BCM6368B2, MIPS: 400MHz, > Total Flash size: 16384K with 128 sectors > Total Memory: 67108864 bytes (64MB) > Board Id (0-15): 96368MVWG > >

Re: [OpenWrt-Devel] [PATCH 1/2] b53: add internal API for accessing PHY regs

Hi, On 6 January 2016 at 20:02, Rafał Miłecki wrote: > Signed-off-by: Rafał Miłecki Please don't leave the commit log empty. E.g. state why you need to add this new function. > --- > .../generic/files/drivers/net/phy/b53/b53_mdio.c | 20 >

Re: [OpenWrt-Devel] [PATCH 2/2] b53: support setting port link state

Hi, On 6 January 2016 at 20:02, Rafał Miłecki wrote: > Signed-off-by: Rafał Miłecki > --- > .../generic/files/drivers/net/phy/b53/b53_common.c | 40 > ++ > 1 file changed, 40 insertions(+) > > diff --git

Re: [OpenWrt-Devel] [PATCH] brcm63xx: fix gpio ephy-reset

Hi, On 12 December 2015 at 14:10, dani wrote: > Currently ephy-reset, which uses a GPIO for enabling external ethernet phys, > is broken. > This patch fix the problem. > > This problem causes in boards with external phys with a reset pin connected > to gpio, are >

Re: [OpenWrt-Devel] [PATCH] brcm63xx: add support for Huawei HG622

Hi, On 16 December 2015 at 23:05, Álvaro Fernández Rojas wrote: > Signed-off-by: Álvaro Fernández Rojas in the future I will reject patches with an empty commit message. Applied in r48305. Jonas ___

Re: [OpenWrt-Devel] [PATCH v3] Add support for C-style in dtsi files

Hi, you still haven't answered my questions: On Mon, Dec 7, 2015 at 4:07 PM, Nikolay Martynov wrote: > Current way of compuling dts files involves calling C preprocessor on > main dts file only. This means that dtsi includes cannot have C-style > includes. Why not?

Re: [OpenWrt-Devel] [PATCH] [ipq806x] Add initial support for TP-Link Archer C2600

}; > ++ > ++ phy@110f8830 { /* USB3 port 0 SS phy */ > ++ status = "ok"; > ++ }; > ++ > ++ usb30@0 { > ++ status = "ok"; > ++ }; > ++ > ++ usb30@1 { > ++ status = "ok"; > ++ }; > ++ > ++ pcie0: pci@1b50 { > ++ status = "ok"; > ++

Re: [OpenWrt-Devel] [PATCH] [ipq806x] Add initial support for TP-Link Archer C2600

Hi, please try to keep the number of replies low, ideally one. On Mon, Dec 7, 2015 at 5:05 PM, Josh Bendavid wrote: > (Sorry about the top posting) > and keep some context to what you are replying to. > For the flash, the stock firmware, and the factory images built

Re: [OpenWrt-Devel] [PATCH v3] Add support for C-style in dtsi files

On 07.12.2015 17:16, Nikolay Martynov wrote: > Sorry, I've missed those questions. Let me try answering them. > > Now also including the list. > > 2015-12-07 10:39 GMT-05:00 Jonas Gorski <j...@openwrt.org>: >> Hi, >> >> you still haven't answered my question

Re: [OpenWrt-Devel] [PATCH] [ipq806x] Add initial support for TP-Link Archer C2600

Hi, On Sat, Dec 5, 2015 at 5:13 AM, Josh Bendavid wrote: > From: Josh Bendavid > > Add initial support for Archer C2600 to Makefiles and profiles. This is > sufficient to build a working factory image. Sysupgrade image is not > implemented yet.

Re: [OpenWrt-Devel] [PATCH v2] Add support for C-style in dtsi files

Hi, On Fri, Dec 4, 2015 at 12:40 AM, Nikolay Martynov wrote: > Current way of compuling dts files involves calling C preprocessor on > main dts file only. This means that dtsi includes cannot have C-style > includes. Why not? Shouldn't they get processed as well as long as

Re: [OpenWrt-Devel] [PATCH v2] brcm63xx: Add NuCom R5010UNv2 support

Hi, On Mon, Nov 30, 2015 at 10:50 PM, dani wrote: > This patch adds support for the NuCom R5010UNv2. > > It's a BCM6328 based board. It has an onboard BCM43217 wifi chip. For this > wifi chip looks like the brcmsmac driver isn't still supported, b43 drivers > are used > for

Re: [OpenWrt-Devel] [PATCH v2] brcm63xx: Add NuCom R5010UNv2 support

Hi, On Tue, Dec 1, 2015 at 11:40 AM, dani wrote: > This patch adds support for the NuCom R5010UNv2. > > It's a BCM6328 based board. It has an onboard BCM43217 wifi chip. For this > wifi chip looks like the brcmsmac driver isn't still supported, b43 drivers > are used > for

Re: [OpenWrt-Devel] [PATCH] include/image.mk: Add dtb-install build function

Hi, On Tue, Dec 1, 2015 at 11:43 AM, Petr Štetiar wrote: > Signed-off-by: Petr Štetiar Please try to avoid empty commit logs. Also you don't add any users of this, so why should need this? Jonas ___ openwrt-devel

Re: [OpenWrt-Devel] ath9k-htc init

On Thu, Nov 26, 2015 at 2:07 PM, Alexey Brodkin <alexey.brod...@synopsys.com> wrote: > Hi Jonas, > > On Mon, 2015-11-23 at 16:48 +0100, Jonas Gorski wrote: >> On Mon, Nov 23, 2015 at 9:21 AM, Alexey Brodkin >> <alexey.brod...@synopsys.com> wrote: >> >

Re: [OpenWrt-Devel] [PATCH V2] oxnas: set irq of usb to cpu1

On Mon, Nov 23, 2015 at 8:43 AM, Shonn Lu wrote: >Subject: oxnas: set irq of usb to cpu1 Why? Please explain why this is needed/wanted. Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: [OpenWrt-Devel] [PATCH] axs10x: initilaze network for wireless access-point

n that case before issuing command above > one needs to populate /etc/config/wireless config: > -->8 > wifi detect > /etc/config/wireless > -->8 > > Signed-off-by: Alexey Brodkin <abrod...@synopsys.com> > Cc: Felix

Re: [OpenWrt-Devel] ath9k-htc init

On Mon, Nov 23, 2015 at 9:21 AM, Alexey Brodkin wrote: > Hi Felix, Jonas, > > While playing with my AXS101 board and USB WI-Fi dongles I bumped in > a couple of issues. Fortunately I found at least one dongle that > works quite nice. That's TP-Link TL-WN721N (or its

Re: [OpenWrt-Devel] [PATCH v2 1/2] pinctrl/lantiq: split xway_mfp into dedicated tables

On Mon, Nov 16, 2015 at 2:55 PM, Martin Schiller <mschil...@tdt.de> wrote: > On Mon, Nov 16, 2015 at 2:06 PM, Jonas Gorski <j...@openwrt.org> > wrote: >> On Mon, Nov 16, 2015 at 12:01 PM, Martin Schiller <mschil...@tdt.de> >> wrote: >> > This patch spli

Re: [OpenWrt-Devel] [PATCH v2 1/2] pinctrl/lantiq: split xway_mfp into dedicated tables

Hi, On Mon, Nov 16, 2015 at 12:01 PM, Martin Schiller wrote: > This patch splits the inadequate "pinctrl-xway" and "pinctrl-xr9" settings > into dedicated "pinctrl-ase", "pinctrl-danube", "pinctrl-xrx100" and > "pinctrl-xrx200" configuration tables. > > Based on the newest

Re: [OpenWrt-Devel] [PATCH 2/2 v4] linux: add support of Synopsys ARC770-based boards

Hi Alexey, On Tue, Nov 10, 2015 at 5:40 PM, Alexey Brodkin <alexey.brod...@synopsys.com> wrote: > Hi Jonas, > > On Tue, 2015-11-10 at 12:02 +0100, Jonas Gorski wrote: >> Hi Alexey, >> >> On Sat, Nov 7, 2015 at 2:25 PM, Alexey Brodkin >> <alexey.br

Re: [OpenWrt-Devel] [PATCH 2/2 v4] linux: add support of Synopsys ARC770-based boards

On Wed, Nov 11, 2015 at 1:38 PM, Alexey Brodkin <alexey.brod...@synopsys.com> wrote: > Hi Jonas, > > On Wed, 2015-11-11 at 12:19 +0100, Jonas Gorski wrote: >> Hi Alexey, >> >> On Tue, Nov 10, 2015 at 5:40 PM, Alexey Brodkin >> <alexey.brod...@synopsys.c

Re: [OpenWrt-Devel] [PATCH 2/2 v4] linux: add support of Synopsys ARC770-based boards

used to make sure built software still runs on > different HW configurations. > > Cc: Felix Fietkau <n...@openwrt.org> > Cc: Jo-Philipp Wich <j...@openwrt.org> > Cc: Jonas Gorski <j...@openwrt.org> > Signed-off-by: Alexey Brodkin <abrod...@synopsys.com

Re: [OpenWrt-Devel] [PATCH 2/2 v3] linux: add support of Synopsys ARC770-based boards

Hi Alexey, On Thu, Nov 5, 2015 at 8:39 PM, Alexey Brodkin <alexey.brod...@synopsys.com> wrote: > Hi Jonas, > > On Thu, 2015-11-05 at 20:04 +0100, Jonas Gorski wrote: >> Hi Alexey, >> >> On Thu, Nov 5, 2015 at 7:14 PM, Alexey Brodkin >> <alexey.

Re: [OpenWrt-Devel] [PATCH 2/2 v3] linux: add support of Synopsys ARC770-based boards

Hi Alexey, On Thu, Nov 5, 2015 at 7:14 PM, Alexey Brodkin <alexey.brod...@synopsys.com> wrote: > Hi Jonas, > > On Wed, 2015-11-04 at 20:22 +0300, Alexey Brodkin wrote: >> Hi Jonas, >> >> On Wed, 2015-11-04 at 13:06 +0100, Jonas Gorski wrote: >> > Hi,

Re: [OpenWrt-Devel] [PATCH 2/2 v3] linux: add support of Synopsys ARC770-based boards

Hi, On Tue, Nov 3, 2015 at 12:27 AM, Alexey Brodkin wrote: > This patch introduces support of new boards with ARC cores. > > [1] Synopsys SDP board > This is a new-generation development board from Synopsys that > consists of base-board and CPU tile-board

Re: [OpenWrt-Devel] Target profiles: making "make" build every profile

Hi, On Mon, Sep 14, 2015 at 11:30 AM, Rafał Miłecki wrote: > Quick summary: > Subtargets - used for building modified kernels > Profiles - used for including specific software > > There are two ways of using profiles: > > 1) Changing some software for all devices > Used when

Re: [OpenWrt-Devel] [PATCH] [SIGNED-OFF] Add initial support for WeIO board

Hi, On Tue, Sep 8, 2015 at 9:00 PM, Drasko DRASKOVIC wrote: > Subject: [PATCH] [SIGNED-OFF] Add initial support for WeIO board Please version your patches if you change them ([PATCH V2] etc) > Add support for WeIO board (http://we-io.net), which is based on >

Re: [OpenWrt-Devel] [PATCH][netifd] Bridge hairpin mode must be off by default

Hi, On Thu, Sep 10, 2015 at 3:00 PM, Dmitry Ivanov wrote: > Bridge hairpin mode must be off by default when multicast_to_unicast is > off. Enabling this mode leads to broadcast frames such as ARP and DHCP > being retransmitted back to AP in WDS configurations. > >

  1   2   3   4   5   6   7   >