Hi,
It seems that the older patches got put into patchwork, and assigned to Petr
Štetiar?
Apologies for the mess I created.
I tried to put those patches to superseded?
Responses to feedback on my original patches, as well as the patch at the end.
Additional feedback and requests for changes/test
Daniel Bailey [2020-06-04 20:25:21]:
Hi,
> I'm curious about the process to get a patch accepted.
currently it's like in other FOSS project run by volunteers, so the resources
are scarce.
You send the contribution and then wait some time, ping, wait some more time,
try to poke someone of the
Hi all,
I'm curious about the process to get a patch accepted.
I followed the steps (and formatting guidelines) at
https://openwrt.org/submitting-patches and submitted a couple of patches
for procd last Friday and another one today. I submitted them to the list
alone because I couldn't tell if th
The command:(svn help export) does not display trust-server-cert
option by default even if it is supported with svn version 1.13.0.
Signed-off-by: kai zhang
---
include/download.mk | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/include/download.mk b/include/download.mk
in
Sometimes stage2 is unable to kill all processes which results in a
failed upgrade.
Rather than fully relying on stage2, let procd gracefully terminate
the services in the services AVL tree before handing control to
upgraded.
Signed-off-by: Daniel Bailey
---
service/service.c | 22 +
Daniel, thanks, that's what I ended up doing in the code for the `service list`.
Should I send the patch for `service list` and remove `service
list-enabled` and `service list-disabled`? Do people care about this
minor improvement?
On Thu, Jun 4, 2020 at 4:13 PM Daniel Bailey wrote:
>
> Somebody
Somebody who is better with jsonfilter than me might be able to clean this
up, but it does the trick:
#!/bin/sh
. /usr/share/libubox/jshn.sh
json_load "$(ubus call service list)"
json_get_keys SERVICES
for SERVICE in $SERVICES; do
echo "$SERVICE: `ubus call service list | jsonfilter -e
"@.$
From: Paul Spooren
The Linksys devices in mvebu target feature a mixed naming,
where parts are based on the official product name (device
node, image; e.g. WRT3200ACM) and parts are based on the
internal code name (DTS file name, compatible, LED labels;
e.g. rango). This inconsistent naming has b
> I agree with Felix. Having one ccache directory for multiple repos
> doesn't make much sense to me as most probably they are for different
> platforms. And even if they are for same platform there are more chances
> for ccache corruption and deleting it will affect all those repos. So it
> still
On Mon, Jun 1, 2020 at 9:39 PM Reuben Dowle wrote:
> When changing an interface MTU direct through ip command, netifd will get
> be out of sync. The netifd internally tracked MTU (discoverable through
> ubus call network.device status '{"name":"xxx"}' call will always show 1500
> (or whatever the
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
---
Changes in v2: none
...IPS-BCM63XX-add-support-for-BCM63268.patch | 18 --
...MIPS-BCM63XX-
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
---
Changes in v2: refresh
target/linux/bcm63xx/image/Ma
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: BCM53
On Thu, Jun 04, 2020 at 06:31:36AM -0700, Stan Grishin wrote:
> Thanks. Should I replace list-enabled and list-disabled with list, doing this:
I'm not sure it's anywhere close to the optimal solution with ubus and
jsonfilter, but I'm not well-versed in the area enough to suggest a
proper one, sorr
Thanks. Should I replace list-enabled and list-disabled with list, doing this:
if [ "$1" = "list" ]; then
for F in /etc/init.d/* ; do
printf "%-30s\t%10s\t%10s\n" "$F" \
$( $($F enabled) && echo "enabled" || echo "disabled" ) \
$
Did some quick experiments on my WRT1900ACv1 (Mamba) now that DSA is
finally in master...
I wonder if I have understood this correctly:
1) vlan_filtering is required when bridging tagged and untagged DSA
ports, and
2) all bridge ports, including the wireless VIFs, must be configured
with th
On Thu, Jun 04, 2020 at 02:56:31AM -0700, Stan Grishin wrote:
> If there's a one/two liner to figure out if a service is running or
> not,
ubus call service list '{ "verbose": true, "name": "openvpn" }' | \
jsonfilter -e '@.openvpn.instances["foo"].running
--
Be free, use free (http://www.g
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, please resend it as a proper
Gentile Utente,
distribuiamo Licenze originali ESD, COA, CARD e STICKERS Microsoft, Adobe,
Autodesk ..
( Direttiva n. 2009/24/CE e L.C.E.C. -128/2011 )
Esempi:
MS. Office 2019 Pro da Euro 25,00
MS. Server 2016 standardda Euro 46,00
MS. Win 10 Pro da Euro 12,00
MS.
On Wed, Jun 3, 2020 at 4:53 PM Michael Jones wrote:
>
>
>
> 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 ch
Hi Adrian,
> El 4 jun 2020, a las 10:16, Adrian Schmutzler
> escribió:
>
> Hi,
>
>> -Original Message-
>> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
>> On Behalf Of Daniel González Cabanelas
>> Sent: Donnerstag, 4. Juni 2020 00:48
>> To: openwrt-devel@lists.op
On 04.062020 at 09:58 Adrian Schmutzler wrote:
>
> Hi,
>
Hi Adrian,
> we regularly encounter the situation that devices are subject to changes
> that will make them incompatible to previous versions.
> Removing SUPPORTED_DEVICES will not really be helpful in most of these
> cases, as this only h
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Daniel González Cabanelas
> Sent: Donnerstag, 4. Juni 2020 00:48
> To: openwrt-devel@lists.openwrt.org
> Cc: nolt...@gmail.com
> Subject: [OpenWrt-Devel] [PATCH 4/4] bcm63xx: add
Hi,
we regularly encounter the situation that devices are subject to changes
that will make them incompatible to previous versions.
Removing SUPPORTED_DEVICES will not really be helpful in most of these
cases, as this only helps after a rename.
An easy way to address this would be the introductio
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of DENG Qingfang
> Sent: Donnerstag, 4. Juni 2020 06:30
> To: openwrt-devel@lists.openwrt.org
> Cc: Adrian Schmutzler ; Tomasz Maciej
> Nowak
> Subject: [OpenWrt-Devel] [PATCH] mveb
Hi All,
I've tried to bump this target to kernel 5.4 but failed to do so twice.
This target is not DT aware at all and the amount of efforts required to
do so are tremendous, which I cannot justify internally here.
Giving the facts that:
- The huge amount of effort required
- The SoC itsel
Ok, I assume it’s safe to drop this, since the bootloader is on a separate
partition and all Sercomm devices seem to have both bootloaders available from
factory.
> El 4 jun 2020, a las 0:48, Daniel González Cabanelas
> escribió:
>
> There is no need to include the CFE bootloader in the Serco
Hi Daniel,
Please, find my comments below:
> El 4 jun 2020, a las 0:48, Daniel González Cabanelas
> escribió:
>
> 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
29 matches
Mail list logo
