ix Fietkau wrote:
>
>
> > On 23. Jul 2020, at 13:44, Josh Bendavid wrote:
> >
> > "1. Have VLAN devices on top of vlan-enabled bridges to define hotplug
> > ops where applicable, so LAN could be a plain VLAN interface switch0.1
> > instead of its own bridge.
"1. Have VLAN devices on top of vlan-enabled bridges to define hotplug
ops where applicable, so LAN could be a plain VLAN interface switch0.1
instead of its own bridge."
By this you mean that the creation of the switch0.1 device will
trigger automatically through the hotplug op
"bridge vlan add de
Another option, as long as the standard method is to attach a wireless
interface to a bridge though the "option network" in the wifi-ifaces,
would be to add a corresponding "option pvid" to wifi-ifaces which
could then be propagated to the bridge when the wifi interface is
added.
On Thu, 23 Jul 20
Ok sure, but the documentation currently says "As WLAN interface names
may be dynamic or unpredictable, it is strongly recommended that they
be assigned to bridges using the network option in UCI wireless
configuration"
This is referring to the list of interfaces for the bridge, but
presumably the
Ok thanks, I agree this makes much more sense.
As Luiz mentioned earlier, this exposes more explicitly the
awkwardness of the "network" option for wifi-iface pointing to an
interface rather than a device.
Related to this, is it possible to add a wireless interface to a
bridge specifying a non-def
One thing which is a bit awkward as long as the bridge itself is
configured as an interface, is that as far as I have understood,
creating a tagged interface to the bridge requires first setting up an
interface for the bridge, e.g. with protocol Unmanaged, and then
setting up one or more vlan tagge
I guess the vlan_default_pvid setting would fit into the config device
block in this scheme?
On Wed, 15 Jul 2020 at 09:59, Jo-Philipp Wich wrote:
>
> Hi,
>
> > Changes:
> > - The device is created as a netifd bridge
> > - Bridge vlan sections should always refer to the bridge instead of
> > a
Ok thanks.
I think my main point was not that this belongs in interface per-se,
but that it makes sense for the configuration of vlan tagging to apply
to bridges in general (and to have as little as possible special
handling of dsa in uci, since the logic is that it should be possible
to configure
Hi,
I have a somewhat radical comment on this.
As far as I understand, the vlan filtering support in the linux bridge
subsystem is not specific to dsa, but can equally be configured for a
pure software bridge. The fact that the switch supports dsa/switchdev
then simply allows this to be transpare
Add support for TP-Link Archer C2600 to tplink-safeloader including partition
table and additional SupportList strings. Both factory and sysupgrade images
are supported.
Signed-off-by: Josh Bendavid
---
tools/firmware-utils/src/tplink-safeloader.c | 114 ++-
1 file
re. Kernel 4.1 build does
not boot currently.
Not tested: Hardware buttons.
Signed-off-by: Josh Bendavid
---
.../linux/ipq806x/base-files/etc/board.d/01_leds | 7 +
.../ipq806x/base-files/etc/board.d/02_network | 3 +-
.../etc/hotplug.d/firmware/11-ath10k-caldata | 66
:
http://lists.infradead.org/pipermail/ath10k/2015-November/006489.html. This
has also been discussed a bit further on the ath10k list here:
http://lists.infradead.org/pipermail/ath10k/2015-December/006613.html.
Signed-off-by: Josh Bendavid
---
.../kernel/mac80211/patches/941
:
http://lists.infradead.org/pipermail/ath10k/2015-November/006489.html. This
has also been discussed a bit further on the ath10k list here:
http://lists.infradead.org/pipermail/ath10k/2015-December/006613.html.
Signed-off-by: Josh Bendavid
---
.../mac80211/patches/941
The device tree file is similar to the current ap148 dts, with sata and nand
removed, and buttons/led's added.
Signed-off-by: Josh Bendavid
---
...qcom-add-TP-Link-Archer-C2600-device-tree.patch | 300 +
...qcom-add-TP-Link-Archer-C2600-device-tree.patch
rking: wireless status led's (these are not controlled through gpio, but
rather through the QCA9980 pcie chips). Also there is no way to set the wan
led to orange, which is possible in the stock firmware. Kernel 4.1 build does
not boot currently.
Not tested: Hardware buttons.
Signed-off-by: Jos
(Sorry, missed the changes to tplink-safeloader in firmware tools
here, have submitted a separate patch with just those)
On 17 December 2015 at 13:34, Josh Bendavid wrote:
> Add initial support for Archer C2600 to Makefiles and profiles along with
> needed modifications to tplink-safeloa
Needed modifications to tplink-safeloader to builder Archer C2600 images.
Adds partition table and support list strings and properly uses them.
Signed-off-by: Josh Bendavid
---
tools/firmware-utils/src/tplink-safeloader.c | 114 ++-
1 file changed, 111 insertions(+), 3
-off-by: Josh Bendavid
---
.../mac80211/patches/941-ath10k_skip_otp_check.patch | 15 +++
1 file changed, 15 insertions(+)
create mode 100644
package/kernel/mac80211/patches/941-ath10k_skip_otp_check.patch
diff --git a/package/kernel/mac80211/patches/941
The device tree file is similar to the current ap148 dts, with sata and nand
removed, and buttons/led's added.
Signed-off-by: Josh Bendavid
---
...qcom-add-TP-Link-Archer-C2600-device-tree.patch | 300 +
...qcom-add-TP-Link-Archer-C2600-device-tree.patch
Kernel 4.1 build does
not boot currently.
Not tested: Hardware buttons.
Signed-off-by: Josh Bendavid
---
include/image.mk | 11
.../linux/ipq806x/base-files/etc/board.d/01_leds | 7 +++
.../ipq806x/base-files/etc/board.d/02_network | 3 +-
.../etc
From: Josh Bendavid
Add initial support for Archer C2600 to Makefiles and profiles along with
needed modifications to tplink-safeloader in firmware-tools. The device tree
file is similar to the current ap148 dts, with sata and nand removed, and
buttons/led's added. This is sufficie
From: Josh Bendavid
Add initial support for Archer C2600 to Makefiles and profiles along with
needed modifications to tplink-safeloader in firmware-tools. The device
tree file is similar to the current ap148 dts, with sata and nand removed,
and buttons/led's added. This is sufficient to
(Sorry about the top posting)
For the flash, the stock firmware, and the factory images built with these
patches are using only the NOR flash as far as I know.
I am not 100% sure whether the NAND is physically there or not (what would
be the easiest way to check?)
(the vlan configuration inherited from the AP148 is working, which implies
that the connections and port mapping are the same)
On 7 December 2015 at 16:57, Josh Bendavid wrote:
> Ok thanks,
> Will clean up the white space + board name and resubmit (maybe also with
> the additional ch
t 3:20 PM, 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. Currently wired network is worki
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. Currently wired network is working, but
LED's/buttons/wireless are not. Updated to create a separate dts fil
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. Currently wired network is working, but
LED's/buttons/wireless are not.
Signed-off-by: Josh Bendavid
---
From: Josh Bendavid
Add support for Archer C2600 to tplink-safeloader by adding needed
partition table, and vendor information plus support list strings.
Additional string C2600 is enabled for the -B option.
Signed-off-by: Josh Bendavid
---
diff --git a/tools/firmware-utils/src/tplink
28 matches
Mail list logo
