A direct upgrade from previous swconfig version with incompatible
settings to DSA will break the internet.
Remove SUPPORTED_DEVICES so users cannot upgrade directly.
Signed-off-by: DENG Qingfang
---
target/linux/mvebu/image/cortexa9.mk | 7 ---
1 file changed, 7 deletions(-)
diff --git a/ta
The current one only looks for mt76x2e and mt7603e, and
does not work for 2 or more same Wi-Fi chips.
Refactor the script to cover those cases.
Signed-off-by: DENG Qingfang
---
.../mt7621/base-files/etc/init.d/set-irq-affinity | 26 ++
1 file changed, 7 insertions(+), 19 del
lists.openwrt.org ID: openwrt-devel@lists.openwrt.org
您的帐户 openwrt-devel@lists.openwrt.org 密码今天到期 6/3/2020 6:53:30 p.m.请使用下面的按钮继续输入相同的密码
见固定附件
注意：这是一次用户验证，目的是提供一个更安全的平台并关闭机器人或恶意用户旨在发送垃圾邮件和其他欺诈活动。.
版权所有©2019 lists.openwrt.org安全管理
<<<
On Wed, Jun 3, 2020 at 6:21 PM Stan Grishin wrote:
> To obtain the list of enabled (for autostart) services, you'd type
> service list-enabled. For disabled services service list-disabled. It
> is useful when you need to quickly check which services are
> enabled/disabled or when helping other us
Hi,
Is there any documentation on the testing infrastructure being used, and what
kind of unit test are expected.
I couldn't find any guide on the wiki, and I'm more familiarized with the Node
JS based workflows, and if there is some guide it will be faster than going
thru the code.
If you poin
To obtain the list of enabled (for autostart) services, you'd type
service list-enabled. For disabled services service list-disabled. It
is useful when you need to quickly check which services are
enabled/disabled or when helping other users troubleshoot.
An alternative to list-enabled/list-disabl
The BCM63167 is a BCM63268 SoC with a different physical packaging.
Add the CPU ID to allow supporting routers with this SoC (i.e Sercomm
H500-s)
Signed-off-by: Daniel González Cabanelas
---
...IPS-BCM63XX-add-support-for-BCM63268.patch | 18 --
...MIPS-BCM63XX-add-support-for-BCM63
There is no need to include the CFE bootloader in the Sercomm factory
images.
There might be a case when this could be useful:
- We are running the stock firmware on the first Sercomm image
- The second partition storing the botloader was erased (unlikely)
Even in this case flashing an image w
Not all CFEs will need to relocate the kernel (i.e H500-s), thererefore we'll
need
to pass a different address and not the LOADER_ENTRY
Let to pass the addr to the image creation when neccessary.
Signed-off-by: Daniel González Cabanelas
---
target/linux/bcm63xx/image/Makefile | 4 ++--
1 file
Sercomm H500-s is an xDSL dual band wireless router based on Broadcom
BCM63167 SoC
Hardware:
SoC: Broadcom BCM63167
CPU: BMIPS4350 V8.0, 400 MHz, 2 cores
Flash:NAND 128 MiB
RAM: DDR3 128 MiB
Ethernet: 4x 10/100/1000 Mbps
Switch: BCM531
On Wed, Jun 3, 2020 at 1:33 PM Ian Cooper wrote:
>
Use Reply All to get this posted to the mailing list.
>
> I got your libcxx-abi compiled. I just put together a quick hack so I didn't
> have to create new package makefiles for llvm-project or worry too much about
> versions in the name of the
On Tue, Jun 2, 2020 at 3:21 PM Hauke Mehrtens wrote:
>
> On 6/2/20 7:05 PM, Tim Harvey wrote:
> > The CPT module requires firmware which we add here as well.
> >
> > Signed-off-by: Tim Harvey
> > ---
> > v2: added license file for firmware
> > ---
> > target/linux/octeontx/config-5.4
From: DENG Qingfang
This migration script is meant for migration between 17.01 and newer
releases. Since 17.01 is EOL for quite some time already, let's just
drop it.
Signed-off-by: DENG Qingfang
[extend commit message]
Signed-off-by: Adrian Schmutzler
---
.../ieee80211/00-wifi-config-migrate
On Wed, Jun 3, 2020 at 6:42 AM Stan Grishin wrote:
> Implement service list-enabled and service list-disabled to provide an
> easy way
> for users to list enabled/disabled services from CLI.
>
> Signed-off-by: Stan Grishin
> ---
> package/base-files/files/etc/profile | 21 +
On Wed, Jun 3, 2020 at 3:22 AM 魏艳艳 wrote:
> Dear!
> I've tried to write configurations using UCI API in my projects, but
> they often cause my processes to crash, I don't know why？I hope you can
> help me。
> 1、platform：X86
> This is the information that my Program crashed
> (gdb) where
> #0
Tim Harvey [2020-06-03 08:25:54]:
Hi,
> are you simply saying it's not upstream and therefore not accepted?
yes, that's my view/decision.
BTW I didn't rejected the patch, just changed the status from "Under review"
to "Needs review/ACK", but I'm not going to merge it as it means additional
wor
On Wed, Jun 3, 2020 at 5:24 AM Petr Štetiar wrote:
>
> Tim Harvey [2020-05-28 06:56:44]:
>
> Hi,
>
> > The GSC sitting on i2c1 can NAK I2C transactions if it is busy
> > performing an ADC cycle. Allow enough retries to work around this.
>
> this looks like you either need to keep in your own vend
Josef Schlehofer [2020-06-03 15:50:59]:
Hi,
> Other guys who have commit access it seems that they are not doing that and
> merging it
fine with me, it's their decision.
> I think that your policy should be applied to all not just someone and
> should be followed by everyone.
it's not mine po
Hello,
On 03. 06. 20 14:53, Petr Štetiar wrote:
> Pali Rohár [2020-06-03 14:48:23]:
>
>> What do you suggest to put into commit description of such small change
>> where commit title already contains description of the whole change?
> lspci output as in your other patch, simply something, otherwi
Previously the dts were using a value determined by empirical testing,
because of a spi driver/clock bug. The bug was fixed quite some time
ago. 33 MHz is the default clock frequency used by RouterBOOT and thus
safe.
Signed-off-by: Tobias Schramm
---
target/linux/ramips/dts/mt7621_mikrotik_route
This patch increases the SPI clock speed on the rbm11g and rbm33g to
33 MHz. Initially it was set to a empirically determined value.
The bug necessitating the empirical testing has since been resolved.
33 MHz is the default used by RouterBOOT. It is well within spec of
the SPI flashes used. I've al
Pali Rohár [2020-06-03 14:48:23]:
> What do you suggest to put into commit description of such small change
> where commit title already contains description of the whole change?
lspci output as in your other patch, simply something, otherwise it means
additional work for me
-- ynezz
_
On Wednesday 03 June 2020 13:30:01 Petr Štetiar wrote:
> Pali Rohár [2020-05-20 14:33:05]:
>
> Hi, please next time don't forget to add commit description as it's
> mandatory. Thanks.
Hello Petr, thank you for taking these patches!
What do you suggest to put into commit description of such sma
Tim Harvey [2020-05-28 06:56:44]:
Hi,
> The GSC sitting on i2c1 can NAK I2C transactions if it is busy
> performing an ADC cycle. Allow enough retries to work around this.
this looks like you either need to keep in your own vendor tree or try to fix
properly upstream, thanks. So I'm not going t
Implement $initscript status-ubus as a short-hand for
ubus call service list "{'name': '$initscript'}"
Signed-off-by: Stan Grishin
---
package/base-files/files/etc/rc.common | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/package/base-files/files/etc
Implement service list-enabled and service list-disabled to provide an easy way
for users to list enabled/disabled services from CLI.
Signed-off-by: Stan Grishin
---
package/base-files/files/etc/profile | 21 +
1 file changed, 21 insertions(+)
diff --git a/package/base-files
Hello,
The following patch (submitted by you) has been updated in Patchwork:
* openwrt: [OpenWrt-Devel] iwinfo: add device id for Mikrotik R11e-5HacD
miniPCIe card
-
http://patchwork.ozlabs.org/project/openwrt/patch/mailman.1406.1586210362.2542.openwrt-de...@lists.openwrt.org/
- for:
Tobias Schramm [2020-04-09 15:09:55]:
> Previously the dts were using a value determined by empirical testing,
> because of a spi driver/clock bug. The bug was fixed quite some time
> ago. 33 MHz is the default clock frequency used by RouterBOOT and thus
> safe.
Saved patch to
OpenWrt-Devel-v2-
Pali Rohár [2020-05-20 14:33:05]:
Hi, please next time don't forget to add commit description as it's mandatory.
Thanks.
> Signed-off-by: Pali Rohár
> ---
> hardware.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hardware.txt b/hardware.txt
> index 07f61b7..64ab708 100644
> ---
Hi, please next time don't forget to add commit description as it's mandatory.
Thanks.
Johann Neuhauser via openwrt-devel
[2020-04-06 23:58:43]:
From: Johann Neuhauser
> To: openwrt-devel@lists.openwrt.org
> Cc: Johann Neuhauser
> Subject: [PATCH] iwinfo: add device id for Mikrotik R11e-5Ha
Hello,
The following patch (submitted by you) has been updated in Patchwork:
* openwrt: [OpenWrt-Devel] iwinfo: add device id for Mikrotik R11e-5HacD
miniPCIe card
-
http://patchwork.ozlabs.org/project/openwrt/patch/mailman.1406.1586210362.2542.openwrt-de...@lists.openwrt.org/
- for:
Hi,
please follow https://github.com/openwrt/packages/blob/master/CONTRIBUTING.md
-- ynezz
Eric Masson [2020-04-26 14:46:45]:
> From: Eric Masson
>
> ---
> net/nsd/files/nsd.init | 31 +++
> 1 file changed, 27 insertions(+), 4 deletions(-)
>
> diff --git a/net/n
Stan Grishin [2020-04-13 04:16:25]:
Hi,
> I've been using something similar on my system and propose the following
> patch (first submission to the list, be gentle ;)):
no worries, just read https://openwrt.org/submitting-patches and try again :-)
Commit subject should be "base-files: ..." and
Hi,
next time please do:
$ git format-patch -s1 --subject-prefix "PATCH libubox" ...
as described in https://openwrt.org/submitting-patches
Adrian Panella [2020-02-22 20:11:28]:
> Current function "blobmsg_add_json_from_file" only adds json file if it is
> an object, and it only returns the
Hello,
The following patch (submitted by you) has been updated in Patchwork:
* openwrt: [OpenWrt-Devel] Do not hard-code IS_TTY in script scripts/feeds
-
http://patchwork.ozlabs.org/project/openwrt/patch/mailman.2840.1586705844.2542.openwrt-de...@lists.openwrt.org/
- for: OpenWrt deve
Hi,
I tend to NAK this as it has the potential to interrupt a lot of downstream
tooling. Up until now I also never heard about about Zstd - while this doesn't
mean anything in the grand scheme of things I think it is a bit too "new" to
be used widely yet. Seems tar only supports it since beginning
R. Diez via openwrt-devel [2020-04-12
17:37:13]:
> 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 sof
Dear!
I've tried to write configurations using UCI API in my projects, but they
often cause my processes to crash, I don't know why？I hope you can help me。
1、platform：X86
This is the information that my Program crashed
(gdb) where
#0 0x7fef72046277 in raise () from /lib64/libc.so.6
#1 0x
38 matches
Mail list logo
