Re: system broken

Hi, I did check again, at which commit the issue starts Last working version: commit: d355b578b7cc95c5b07fcecb217dbac4c05bd49c target: include selinux-variants if CONFIG_SELINUX is set First not working version: commit: 2dffadece9a7243a236ce7d91719787a671e23d4 ubus: prepare to run ubusd as non-

Re: system broken

Thanks for testing and reporting back. I have fixed a bunch of config migration issues which would lead to ubus not starting up (and system hanging in preinit). This should have been fixed by commit de7ca7dafadfd650d031e0379ce0c002868d5936 Author: Daniel Golle Date: Thu Oct 22 13:13:39 2020 +01

Re: system broken

With your last change commit: 0b31713c856a0d8c6fe2961113a9317f7c3659dc rpcd: adapt defaults for changed ubus.sock path both of my routers does boot without any issue. Thanks!! Regards, Hartmut Am 22.10.2020 um 18:03 schrieb Daniel Golle: > Thanks for testing and reporting back. > > I have fi

Re: Wakaama server

Yaro, Thanks, I'll give it a try. Cale Collins Field Applications Engineer Gateworks Corporation (805)781-2000 x37 3026 S. Higuera, San Luis Obispo, CA 93401 www.gateworks.com On Wed, Nov 11, 2020 at 11:44 AM Yaroslav Petrov wrote: > > Hi Cale, > > > You can use this example: > > https://githu

Re: Merging /usr

Hi, > It appears most of the major distros (Debian/Ubuntu, Fedora, Arch, > Solaris) have moved to merge the contents of /{bin,sbin,lib}/ into > /usr/{bin,sbin,lib}/, with top-level symbolic links added for > compatibility. Sounds good to me, do you have an estimate how much work this is? > There

Re: [missing subjects]

Hi, I think this was a misconfiguration in mailman (global "from_is_list" was set to "Wrap message"). Let's see if this reply mail looks better. Regards, Jo signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-d

Re: [missing subjects]

On 2020-06-26 14:15, Jo-Philipp Wich wrote: Hi, I think this was a misconfiguration in mailman (global "from_is_list" was set to "Wrap message"). Let's see if this reply mail looks better. Regards, Jo So far so good. ___ openwrt-devel mailing lis

Re: [missing subjects]

On 2020-06-26 19:29, Torbjorn Jansson wrote: On 2020-06-26 14:15, Jo-Philipp Wich wrote: Hi, I think this was a misconfiguration in mailman (global "from_is_list" was set to "Wrap message"). Let's see if this reply mail looks better. Regards, Jo So far so good. Looks like there still is

Re: netifd issue

e9hack kirjoitti 9.11.2023 klo 17.32: I face a strange behaviour since commit 516ab774cc16d4b04b3b17a067cbf2649f1adaeb (system-linux: fix race condition on bringing up wireless devices). After a reboot or a full restart of hostapd via 'wifi down; sleep 30; killall hostapd; sleep 5; wifi', only

Re: netifd issue

On 09.11.23 22:31, Hannu Nyman wrote: e9hack kirjoitti 9.11.2023 klo 17.32: I face a strange behaviour since commit 516ab774cc16d4b04b3b17a067cbf2649f1adaeb (system-linux: fix race condition on bringing up wireless devices). After a reboot or a full restart of hostapd via 'wifi down; sleep 30;

Re: netifd issue

On 10.11.23 13:59, Felix Fietkau wrote: On 09.11.23 22:31, Hannu Nyman wrote: e9hack kirjoitti 9.11.2023 klo 17.32: I face a strange behaviour since commit 516ab774cc16d4b04b3b17a067cbf2649f1adaeb (system-linux: fix race condition on bringing up wireless devices). After a reboot or a full rest

Re: netifd issue

Sorry, but it doesn't solve the issue. Regards, Hartmut Am 10.11.2023 um 14:13 schrieb Felix Fietkau: I think I found the cause of this regression while looking at the code again. It seems that the hotplug-added devices are removed too early based on DEV_EVENT_REMOVE events. Please try this fix

Re: netifd issue

Too fast. I did reboot with the old version again. The patched version does work. Sorry! Regards, Hartmut Am 10.11.2023 um 15:09 schrieb e9hack: Sorry, but it doesn't solve the issue. Regards, Hartmut Am 10.11.2023 um 14:13 schrieb Felix Fietkau: I think I found the cause of this regressio

Re: netifd issue

On 10.11.23 15:21, e9hack wrote: Too fast. I did reboot with the old version again. The patched version does work. Fix pushed, thanks for testing! - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mai

Re: netifd issue

Felix Fietkau kirjoitti 10.11.2023 klo 16.38: On 10.11.23 15:21, e9hack wrote: Too fast. I did reboot with the old version again. The patched version does work. Fix pushed, thanks for testing! - Felix Thanks, I tested the current netifd with the fix, and it seems to work ok, again. Pleas

Re: openvpn issue

How does pppoe-wan get its IP? You may not be able to do much about that, but you can hint which IPv6 an interface gets using the assignment length, hint and prefix settings. I don't use openvpn, but perhaps it has something like this? I guess it would try to pick a source IP with the 'lowes

Re: openvpn issue

How does pppoe-wan get its IP? You may not be able to do much about that, but you can hint which IPv6 an interface gets using the assignment length, hint and prefix settings. I don't use openvpn, but perhaps it has something like this? I guess it would try to pick a source IP with the 'low

Re: openvpn issue

Am 18.12.2023 um 16:22 schrieb Paul D: How does pppoe-wan get its IP? It is retrieved by odhcp6c. You may not be able to do much about that, but you can hint which IPv6 an interface gets using the assignment length, hint and prefix settings. I don't use openvpn, but perhaps it has somethin

Re: openvpn issue

Anything useful here which could go in a PR or two on github? I've added multihome to luci: a5ed5976f4cf70a36863e69da8c055f855545f87 The --local param seems to be in there already. On 2023-12-18 17:30, e9hack wrote: Am 18.12.2023 um 16:22 schrieb Paul D: How does pppoe-wan get its IP? I

Re: RFC pkgs.staging.openwrt.org

Hi Paul - Best idea yet! Go for it. /ted On 1/5/2024 11:14:53 AM, "Paul Spooren" wrote: Hey all, tl;dr checkout https://pkgs.staging.openwrt.org/ As some may experienced, openwrt.org is slow an one (of many reasons) is that it stores and renders tables with all packages. Based on feedba

Re: GPON project?

; > > > * Wi-Fi: MediaTek MT7976C (2x2 2.4 GHz + 3x3/2x2 + zero-wait DFS 5Ghz) > > > > * DRAM: 1 GiB DDR4 > > > > * Flash: 128 MiB SPI NAND+ 4 MiB SPI NOR > > > > * Ethernet: 2x RJ45 (2.5 GbE + 1 GbE) > > > > * USB (host): USB 2.0 (Type-A por

Re: hostapd crash

Hi, On 13.01.24 11:28, e9hack wrote: Hi, I did add one more AP to my wifi config for testing. This results in hostapd not starting for this device: Thu Jan 11 13:59:12 2024 daemon.notice hostapd: Exception in ubus function: left-hand side expression is null In __iface_pending_next(), file /

Re: hostapd crash

sob., 13 sty 2024 o 11:37 e9hack napisał(a): > > Hi, > > I did add one more AP to my wifi config for testing. This results in hostapd > not starting for this device: > > Thu Jan 11 13:59:12 2024 daemon.notice hostapd: Exception in ubus function: > left-hand side expression is null In __iface_pen

Re: hostapd crash

Thanks, this does fix the exception. Now I see the reale error: Sat Jan 13 15:52:30 2024 daemon.err hostapd: Could not set interface phy1-ap8 flags (UP): Resource busy Sat Jan 13 15:52:31 2024 daemon.err hostapd: Failed to add BSS (BSSID=xx:xx:xx:xx:xx:xx) Sat Jan 13 15:52:31 2024 daemon.notice

Re: hostapd crash

On 13.01.24 16:32, e9hack wrote: Thanks, this does fix the exception. Now I see the reale error: Sat Jan 13 15:52:30 2024 daemon.err hostapd: Could not set interface phy1-ap8 flags (UP): Resource busy Sat Jan 13 15:52:31 2024 daemon.err hostapd: Failed to add BSS (BSSID=xx:xx:xx:xx:xx:xx) Sat

Re: hostapd crash

Am 13.01.2024 um 16:47 schrieb Felix Fietkau: On 13.01.24 16:32, e9hack wrote: Thanks, this does fix the exception. Now I see the reale error: Sat Jan 13 15:52:30 2024 daemon.err hostapd: Could not set interface phy1-ap8 flags (UP): Resource busy Sat Jan 13 15:52:31 2024 daemon.err hostapd: Fa

Re: hostapd crash

On 13.01.24 16:58, e9hack wrote: Am 13.01.2024 um 16:47 schrieb Felix Fietkau: On 13.01.24 16:32, e9hack wrote: Thanks, this does fix the exception. Now I see the reale error: Sat Jan 13 15:52:30 2024 daemon.err hostapd: Could not set interface phy1-ap8 flags (UP): Resource busy Sat Jan 13 15

Re: makefile debugging

On 1/18/24 12:01, Tim Harvey wrote: Greetings, I seem to recall a way to ask OpenWrt's build system to output a list of all variable values used in the build but can't find it documented or in my notes. Does anyone know how to do that? Also, is there a way to output a post-processed Makefile af

Re: makefile debugging

Hi Tim, > I seem to recall a way to ask OpenWrt's build system to output a list > of all variable values used in the build but can't find it documented > or in my notes. Does anyone know how to do that? > > Also, is there a way to output a post-processed Makefile after all the > define foo gets d

Re: backports kick?

On 21.06.24 10:55, Janusz Dziedzic wrote: Hello, I see we have backports older than kernel on main (6.6.15 vs 6.6.32)? Is there plan to kick backports to smth like 6.10? I have 6.9.1 in my staging tree for testing. - Felix ___ openwrt-devel mailing

Re: backports kick?

pt., 21 cze 2024 o 12:59 Felix Fietkau napisał(a): > > On 21.06.24 10:55, Janusz Dziedzic wrote: > > Hello, > > I see we have backports older than kernel on main (6.6.15 vs 6.6.32)? > > Is there plan to kick backports to smth like 6.10? > > I have 6.9.1 in my staging tree for testing. > Nice, are

Re: backports kick?

On Mon, 24 Jun 2024 at 13:46, Janusz Dziedzic wrote: > > pt., 21 cze 2024 o 12:59 Felix Fietkau napisał(a): > > > > On 21.06.24 10:55, Janusz Dziedzic wrote: > > > Hello, > > > I see we have backports older than kernel on main (6.6.15 vs 6.6.32)? > > > Is there plan to kick backports to smth like

Re: backports kick?

On 24.06.24 13:46, Janusz Dziedzic wrote: pt., 21 cze 2024 o 12:59 Felix Fietkau napisał(a): On 21.06.24 10:55, Janusz Dziedzic wrote: > Hello, > I see we have backports older than kernel on main (6.6.15 vs 6.6.32)? > Is there plan to kick backports to smth like 6.10? I have 6.9.1 in my stagi

Re: backports kick?

pon., 24 cze 2024 o 14:38 Felix Fietkau napisał(a): > > On 24.06.24 13:46, Janusz Dziedzic wrote: > > pt., 21 cze 2024 o 12:59 Felix Fietkau napisał(a): > >> > >> On 21.06.24 10:55, Janusz Dziedzic wrote: > >> > Hello, > >> > I see we have backports older than kernel on main (6.6.15 vs 6.6.32)? >

Re: Mesh Problem

Follow-up: I tried it on an Atheros-based AP (Alfa N2Q) and found the same thing - works for unencrypted mesh, but adding wpad-mesh-mbedtls causes the mesh to fail completely, and mesh_params cannot be set: root@OpenWrt:~# iw phy0-mesh0 set mesh_param mesh_gate_announcements=1 command failed: Lin

Re: backports kick?

pon., 24 cze 2024 o 19:45 Janusz Dziedzic napisał(a): > > pon., 24 cze 2024 o 14:38 Felix Fietkau napisał(a): > > > > On 24.06.24 13:46, Janusz Dziedzic wrote: > > > pt., 21 cze 2024 o 12:59 Felix Fietkau napisał(a): > > >> > > >> On 21.06.24 10:55, Janusz Dziedzic wrote: > > >> > Hello, > > >>

Re: [OpenWrt-Devel] R: Re: Linking problem while building package

/rules.mk:86: CXX=$(TARGET_CROSS)g++ \Regards,Karthik Venkateswaran[EMAIL PROTECTED] wrote: -To: OpenWrt Development List From: Roberto Riggio <[EMAIL PROTECTED]>Sent by: [EMAIL PROTECTED]Date: 08/06/2008 11:00AMcc: OpenWrt Development List Subject: [OpenWrt-Devel] R: Re: Linking problem while bu

[OpenWrt-Devel] R: Re: R: Re: [PATCH] Firwal init order

cool :) - [EMAIL PROTECTED] ha scritto: > it is on the feature list to allow packages to define custom config > sections in /etc/config/firewall > > > Quoting Roberto Riggio <[EMAIL PROTECTED]>: > > > BTW. I have one question. Which is the suggested way for a package > to add > > rules f

Re: [OpenWrt-Devel] [PATCH] Re: Preliminary support for NETGEAR WNR1000

2010.06.13. 20:54 keltezéssel, Colt Boyd írta: > I missed the 'mach-wnr1000.c' file from the patch the first time. It is > now in the patch. Yep, and it looks very similar to the mach-wnr2000.c. The WNR1000 v1 can work with the WNR2000's code, so you don't need to add a separate file. Addition

Re: [OpenWrt-Devel] Picocom should be re-included in packages.

On 12/08/14 16:53, Alive4Ever wrote: On latest Openwrt commits, picocom is missing. Formerly, picocom was available on Utilities/Terminal section of menuconfig. I think picocom should be re-included, because it's very handy and usable for serial diagnostics, especially on systems with o

Re: [OpenWrt-Devel] Picocom should be re-included in packages.

On Tue, Aug 12, 2014 at 9:57 AM, Daniel Petre wrote: > > > On 12/08/14 16:53, Alive4Ever wrote: >> >> On latest Openwrt commits, picocom is missing. Formerly, picocom >> was available on Utilities/Terminal section of menuconfig. >> >> I think picocom should

Re: [OpenWrt-Devel] Picocom should be re-included in packages.

Yes please, this is very crutial tool to all of us who use serial connections! I use ti all the time to troubleshoot and configure bluetooth serial modules (HC-05). I just use it with this command "picocom -b 38400 -c /dev/ttyATH0" ___ openwrt-devel mail

Re: [OpenWrt-Devel] Picocom should be re-included in packages.

;> was available on Utilities/Terminal section of menuconfig. >> >> I think picocom should be re-included, because it's very handy >> and usable for serial diagnostics, especially on systems with >> only 4 MB of flash, such as TL MR3220. > > > Hello, do you

Re: [OpenWrt-Devel] Picocom should be re-included in packages.

6:53, Alive4Ever wrote: > >> > >> On latest Openwrt commits, picocom is missing. Formerly, picocom > >> was available on Utilities/Terminal section of menuconfig. > >> > >> I think picocom should be re-included, because it's very handy > >

Re: [OpenWrt-Devel] Picocom should be re-included in packages.

On 13/08/2014 16:46, Etienne Champetier wrote: > Picocom is now in packages, thanks to sbyx/cyrus/Steven Barth I'm glad to hear that. May Steven Barth be blessed with happiness and joy. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https

Re: Re: [PATCH] ipq40xx: add support for GL.iNet GL-B2200

This patch now has merge conflict with tag v21.02.0 ``` Unmerged paths: (use "git add ..." to mark resolution) both modified: package/firmware/ipq-wifi/Makefile both modified: package/libs/uclient/Makefile both modified: target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-

Re: Re: [PATCH] ipq40xx: add support for GL.iNet GL-B2200

FYI Ref https://github.com/openwrt/openwrt/pull/4691 > The original patch is from and signed off by Li Zhang li.zh...@gl-inet.com > which can be seen from gl-inet@3b71749 > and > http://lists.openwrt.org/pipermail/openwrt-devel/2021-September/036363.html > > However, as of 2021-10-17, the above-

Re: [OpenWrt-Devel] Q: procd: re-evaluation of inittab entries

On Wed, 5 Dec 2018 at 06:00, Michael Heimpold wrote: > > Hi, > > I'm currently playing with USB gadget stuff. The goal is to run an Ethernet > link and a console over the USB link. I already selected the relevant kernel > modules and ACM device and RNDIS device is created on the USB host > system

Re: [OpenWrt-Devel] Q: procd: re-evaluation of inittab entries

ar yet) 2. inittab is parsed 3. entry is skipped because device does not exists yet 4. configuration of USB gadget with shell script and/or init script 5. device appears 6. hotplug-call tty is being called and running hotplug scripts So it seems that we need a feedback from hotplug script to proc

Re: [OpenWrt-Devel] Q: procd: re-evaluation of inittab entries

On 04/12/2018 22:59, Michael Heimpold wrote: Hi, I'm currently playing with USB gadget stuff. The goal is to run an Ethernet link and a console over the USB link. I already selected the relevant kernel modules and ACM device and RNDIS device is created on the USB host system - all fine so far.

Re: [OpenWrt-Devel] Q: procd: re-evaluation of inittab entries

On 05/12/2018 03:52, Yousong Zhou wrote: On Wed, 5 Dec 2018 at 06:00, Michael Heimpold wrote: Hi, I'm currently playing with USB gadget stuff. The goal is to run an Ethernet link and a console over the USB link. I already selected the relevant kernel modules and ACM device and RNDIS device is

Re: [OpenWrt-Devel] Q: procd: re-evaluation of inittab entries

nd running hotplug scripts So it seems that we need a feedback from hotplug script to procd to rescan inittab for formerly skipped items and re-trigger start in case of device is present now. Regards, mhei should have cleaned up the inbox and read all mails before replying. for a normal ttyX the ap

Re: [OpenWrt-Devel] CC release dates? (Was Re: [PATCH 1/2] oxnas: re-add support for kernel 3.14)

i intentionally don't set a date. i have done so in the past and got ranted at for not being on time. this happened with AA and BB so CC is illusive and will be ready when ready. all i will say is that i am already working on it, but you noticed that yourself :) On 05/12/2014 02:20, Karl P wrote:

Re: [OpenWrt-Devel] CC release dates? (Was Re: [PATCH 1/2] oxnas: re-add support for kernel 3.14)

Hi, do I understand it correctly. For CC is 3.14 planed? Thanks, Claudio -- Reviewing OpenWrt BB for Xmodus Systems XM1710E GSM/UMTS Router On 05.12.2014 09:07, John Crispin wrote: > i intentionally don't set a date. i have done so in the p

Re: [OpenWrt-Devel] CC release dates? (Was Re: [PATCH 1/2] oxnas: re-add support for kernel 3.14)

yes, 3.14 is baseline for CC On 05/12/2014 09:45, Claudio Thomas wrote: > Hi, do I understand it correctly. For CC is 3.14 planed? Thanks, > Claudio > > -- Reviewing OpenWrt BB for Xmodus Systems XM1710E GSM/UMTS Router > > > On 05.12.2

Re: [OpenWrt-Devel] R: Re: How to cycle over uci sections

Roberto Riggio wrote: > - "Tripp Lilley" <[EMAIL PROTECTED]> ha scritto: > >> config_foreach, I believe... > > Well no, this is true only if your sections are like this: > > config page > option display_name"Overview" > option menu"status" > > instea

Re: [OpenWrt-Devel] R: Re: Changeset 13936 broke the x86 target

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. Fixed with https://dev.openwrt.org/changeset/13963 - sorry for the long delay. ~ JoW -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJaSxVdputYINPTPMRAr0RAJ9xq

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

Hi All, You have some very good ideas. I would like to suggest using [requiring] BOTH md5sum and sha1. This is much harder to fake. I have already seen TWO DIFFERENT VERSIONS of the "same" wireless driver in the wild ??!! It seems that those of us who are successful [openwrt] attract a

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

Hi, On Wednesday 17 June 2009 03:38:01 Daniel Dickinson wrote: > No one seems to have responded to this, and I'd like to start working > on it next week. If developers could think about this and comment, it > would be appreciated. I'm not a core OpenWrt developer but was thinking about implement

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Malte. I like that .tar.gz idea, it would also cover devices like the Fonera where you have two separate images too. However, it's planned to introduce a unified image format for OpenWrt which would solve most of this issues so I haven't started w

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

Hi JoW, On Wednesday 17 June 2009 16:14:37 Jo-Philipp Wich wrote: > I like that .tar.gz idea, it would also cover devices like the Fonera > where you have two separate images too. > > However, it's planned to introduce a unified image format for OpenWrt > which would solve most of this issues so I

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

> "Malte" == Malte S Stretz writes: Hi, Malte> A broken tgz header will be recognized by these tools already. Malte> If we need any logic for flashing, we can also introduce a Malte> sysupgrade dir. Anything in there will go to /lib/upgrade Malte> before flashing. For even more flexib

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

Hi, On Wednesday 17 June 2009 22:01:24 Peter Korsgaard wrote: > Malte> A broken tgz header will be recognized by these tools already. > > Malte> If we need any logic for flashing, we can also introduce a > Malte> sysupgrade dir. Anything in there will go to /lib/upgrade > Malte> before flashi

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

Malte S. Stretz wrote: > Hi JoW, > > On Wednesday 17 June 2009 16:14:37 Jo-Philipp Wich wrote: >> I like that .tar.gz idea, it would also cover devices like the Fonera >> where you have two separate images too. >> >> However, it's planned to introduce a unified image format for OpenWrt >> which wo

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Malte. > There's no reason why the unified format couldn't be a tgz (or some other, > maybe uncompressed, format which carries a magic number) with some meta > informations :) Daniel's proposal sounded quite complicated to me. So I finally took

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

On Wed, 17 Jun 2009 23:08:17 +0200 Felix Fietkau wrote: > My plan for the unified format is to keep the on-flash format the same > as the input format. In the long run, I don't want any unpacking to be > done in sysupgrade or the web interface. The structure is roughly > like this: [second stage

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

Hello, On Sat, 20 Jun 2009 20:39:05 +0200 Jo-Philipp Wich wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi Malte. > > > There's no reason why the unified format couldn't be a tgz (or some other, > > maybe uncompressed, format which carries a magic number) with some meta > > in

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Frédéric. Thanks for trying it out. The Fonera2 uses "kernel" as partition name too, so I had a chance to test it. Attached is a newer version of platform.sh that does some more sanity checking on the mtd partitions and a simple patch for the Open

Re: [OpenWrt-Devel] Ping Re: RFC: LuCI Web Interface Image Format

Hello, On Tue, 23 Jun 2009 21:40:34 +0200 Jo-Philipp Wich wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi Frédéric. > > Thanks for trying it out. > The Fonera2 uses "kernel" as partition name too, so I had a chance to > test it. > > Attached is a newer version of platform.sh t

Re: [OpenWrt-Devel] [PATCH] zynq: Re-implement mkits.sh and use it

On 18/03/2016 11:19 PM, Jason Wu wrote: The new mkits.sh is a complete new implementation to support: - multi-configuration (upto 10 with -c option). First -c used defines the default conf used. - multi-image support - multiple kernel/fdt/ramdsik image (upto 50 images) - per image configuration

[OpenWrt-Devel] RE : Re: cc1: all warnings being treated as errors

Hello,On this particular case, a gcc bug report exists because this specific warning should not show when no other diagnostics are issued. I can't link to the exact report right now but a simple google search should show it. IIRC gcc-4.7 may behave more correctly.So the correct treatment is either

Re: Update buildbots (was: Re: Switch issues and CI to GitHub)

Etienne Champetier [2022-01-20 14:56:28]: Hi, > Any chance you can update the buildbots docker images ? > (I see only you 2 listed as admins here: https://openwrt.org/infrastructure) should be done. Cheers, Petr ___ openwrt-devel mailing list openw

Re: Re: [OpenWrt-Devel] mt76x8: Strange GPIO numbering on Onion Omega2+

Hi Gerd, > There is still one major issue migrating to 21.02 on my side: Reboot doesn't > work. I need to switch power off/on on my Omega2+. AFAIU it has somethoing to > do with the SPI 3byte/4byte mode. Older versions worked, but 4byte mode seems > to boot faster. BTW: spi-nor spi0.0: mx25l256

Re: Re: [OpenWrt-Devel] mt76x8: Strange GPIO numbering on Onion Omega2+

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 the mailing list software.--- Begin Message --- Hi Lukas, On Sat, Jun 12, 2021 at

Re: Re: Reliable way to get channel width from wifi scan

Using iw scan? We've done this in the spectrum analyser plugin in Gargoyle [1]. It's not what i would call reliable though as iw itself specifically says not to screen scrape the data. That being said, it has worked for several years now. [1] - https://github.com/ericpaulbishop/gargoyle/blob/mast

Re: Re: Reliable way to get channel width from wifi scan

Thx for the link. From a quick review you confirmed my fear. In the link the channel width is indirectly parsed by checking specific value from the wifi (upper or lower channel presence) (vht band for 5ghz). I think that the best way to implement this is using ubus. Since changing mac80211 code for

Re: [OpenWrt-Devel] [RFC PATCH] build: re-enable parallelism for mksquashfs

On 2018-11-05 00:19, Daniel Santos wrote: > This was disabled by commit dcd0e4a6727611f03eb3d3a75f073235f5f1229c due > to a threading bug back in 2009. The specifics of the bug are not given > in the commit message and squashfs-tools has had several updates to it's > parallelism since this time.

Re: [OpenWrt-Devel] [RFC PATCH] build: re-enable parallelism for mksquashfs

On 11/07/2018 01:52 PM, Felix Fietkau wrote: > On 2018-11-05 00:19, Daniel Santos wrote: >> This was disabled by commit dcd0e4a6727611f03eb3d3a75f073235f5f1229c due >> to a threading bug back in 2009. The specifics of the bug are not given >> in the commit message and squashfs-tools has had severa

Re: [OpenWrt-Devel] [RFC PATCH] build: re-enable parallelism for mksquashfs

Hi, > I'm not sure what you mean by the images being reproducible. It means that different mksquashfs runs with different amounts of CPUs on different hosts should yield bit-identical images having the same checksum given the same input. ~ Jo signature.asc Description: OpenPGP digital signat

Re: [OpenWrt-Devel] [RFC PATCH] build: re-enable parallelism for mksquashfs

On 2018-11-08 02:20, Daniel Santos wrote: > On 11/07/2018 01:52 PM, Felix Fietkau wrote: >> On 2018-11-05 00:19, Daniel Santos wrote: >>> This was disabled by commit dcd0e4a6727611f03eb3d3a75f073235f5f1229c due >>> to a threading bug back in 2009. The specifics of the bug are not given >>> in the

Re: [OpenWrt-Devel] [RFC PATCH] build: re-enable parallelism for mksquashfs

Op do, 8 nov 2018 om 2:20 , schreef Daniel Santos : On 11/07/2018 01:52 PM, Felix Fietkau wrote: On 2018-11-05 00:19, Daniel Santos wrote: This was disabled by commit dcd0e4a6727611f03eb3d3a75f073235f5f1229c due to a threading bug back in 2009. The specifics of the bug are not given in th

Re: [OpenWrt-Devel] [RFC PATCH] build: re-enable parallelism for mksquashfs

Ahh, thank you both for the clarification. On 11/08/2018 01:35 AM, Felix Fietkau wrote: > On 2018-11-08 02:20, Daniel Santos wrote: >> On 11/07/2018 01:52 PM, Felix Fietkau wrote: >>> On 2018-11-05 00:19, Daniel Santos wrote: This was disabled by commit dcd0e4a6727611f03eb3d3a75f073235f5f1229

Re: [OpenWrt-Devel] Releases [Was: Re: OpenWrt 20.X release plans]

On 20/01/20 10:01, Petr Štetiar wrote: Hauke Mehrtens [2020-01-19 18:17:10]: Hi, Does someone else other than jow know how to setup built bot for a new branch? Is this documented somewhere? It should be documented and at least 3 persons should be able (and willing) to do that. There is d

Re: Re: [PATCH RFC] aquantia-firmware: package MediaTek's Aquantia AQR113C firmware

It's actually possible to access the flash from Linux, as I tested a year ago. --- drivers/net/phy/aquantia_main.c | 462 +++- 1 file changed, 461 insertions(+), 1 deletion(-) diff --git a/drivers/net/phy/aquantia_main.c b/drivers/net/phy/aquantia_main.c index 6ecbc3f

Re: [OpenWrt-Devel] Documentation

Nathan Van Fleet wrote: > I don't think everyone needs access. Provided a few people act as > editors for full submissions and corrections, it should be fine. > I agree > I think from here we should choose the editor(s) and then list what > should be documented. I feel like just writing "ec

Re: [OpenWrt-Devel] tcsh

Never tried it (I personally prefer tcsh due to a lot of "old-school time" with freebsd and OS X, but I've only build OpenWrt "under" bash and zsh ...) I assume it is due to the differences between the shell-branches ..? -- Gregers Petersen, Anthropologist [EMAIL PROTECTED] www.wireless-owners

Re: [OpenWrt-Devel] SubmittingPatchesHowTo

D. Hugh Redelmeier wrote: > Gregers asked if I'd be willing to work on a HowTo about submitting > patches. > > I don't know enough to write one. So I did: > http://wiki.openwrt.org/SubmittingPatchesHowTo > > I admit that this isn't very good at all. Please fix it up -- the > beauty of wikis.

Re: [OpenWrt-Devel] SubmittingPatchesHowTo

Felix Fietkau wrote: > Thanks. > I improved it a bit now, I think we can start pointing people to it. > I'm planning to take a further look at it later today :-) -- Gregers Petersen, Anthropologist [EMAIL PROTECTED] www.wireless-ownership.org [EMAIL PROTECTED]

Re: [OpenWrt-Devel] [PATCH]

On Sun, Jun 29, 2008 at 12:31 PM, Stefan Monnier <[EMAIL PROTECTED]> wrote: > Here's a bunch of small patches I have and figure that some of that > should probably be integrated upstream: It's not as simple for the submitter, but since each of these are so functionally discrete it really would be

Re: [OpenWrt-Devel] 25c3

Hallo Alex, Nicht alle OpenWrt developers sprechen Deutsch ;) (my approximate translation below) Le Monday 10 November 2008 18:27:35 Alexander Morlang, vous avez écrit : > Hi, > das übliche Freifunk/wireless/openwrt/etc. konglomerat wird sich auch > auf dem kommenden chaos communication congress

Re: [OpenWrt-Devel] 25c3

Florian Fainelli wrote: > What do you think about getting a meeting (with Palinka and Absinthe) like > last year so that we can expose OpenWrt plans for the future and answer > questions ? hello, from c-base the best day for a meeting in the c-base mainhall like last year would be Mo 29.Dez.2

Re: [OpenWrt-Devel] 25c3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florian Fainelli schrieb: > Hallo Alex, > > Nicht alle OpenWrt developers sprechen Deutsch ;) > > (my approximate translation below) > thanks for translating, as i am a lazy fart, i would have delayed it until too late. one reason for at least CCi

Re: [OpenWrt-Devel] iproute2

On Thu, Jan 8, 2009 at 11:05, Chiang Kang Tan wrote: > Hi all, > > I'm having problem trying to use ip utility in iproute2 to set up some > routing rules. Basically as soon as I try to use ip rule, e.g. > > # ip rule add > > I get the following error: > > RTNETLINK answers: Address family not sup

Re: [OpenWrt-Devel] md5sums

Currently several snapshot package repositories have this issue. Also http://downloads.openwrt.org/snapshots/trunk/orion/packages/ Let's hope some developer/maintainer fixes the update process and we can use them again on the next refresh (I'm just a user too). Maddes On 15.07.2009 11:17, Koves

Re: [OpenWrt-Devel] md5sums

Hiya, what you can do to temporarily resolve the issue, is to manually download the tarball(s), run md5sum on the files and then adjust the sum in the package Makefile. Cheers, Johnny Matthias Buecher / Germany wrote: > Currently several snapshot package repositories have this issue. > Also h

Re: [OpenWrt-Devel] [PATCH]

Le Tuesday 13 July 2010 23:11:21, Ashok Rao a écrit : > r21799 by jow changed the staging install of libipq so that it is no > longer available as a static library but is dynamically linked in as a > shared library. However the libipq package was not being built. This > patch provides libipq.so as

Re: [OpenWrt-Devel] Buffer

On Fri, 2010-08-20 at 09:03 -0300, Airton Ishimori wrote: > How can I access the buffer infromation in the openwrt kernel?? Wich > can I use to access to query the buffer lenght?? It might help to be more specific, for example tell us what buffer you need to query HTH, Ithamar. ___

Re: [OpenWrt-Devel] Buffer

The buffer to receive packet from network. I want would know, how can I do it. How can I query the buffer lenght? -- Airton Ishimori On Fri, Aug 20, 2010 at 11:38, Ithamar R. Adema < ithamar.ad...@team-embedded.nl> wrote: > On Fri, 2010-08-20 at 09:03 -0300, Airton Ishimori wrote: > > How can

Re: [OpenWrt-Devel] kgdb?

Hello, On Thursday 12 May 2011 00:38:40 John Zavgren wrote: > Dear readers: > > I need to debug a kernel loadable module via gdb when the kernel is running > on a device that doesn't have a traditional DB9/RS232 serial interface. > Although, it does have a USB interface that I might be able to us

Re: [OpenWrt-Devel] kgdb?

there is a good howto regarding kgdb on lmo http://www.linux-mips.org/wiki/KGDB ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

<    1   2   3   4   5   6   7   8   9   10   >