Jan 16, 2021 2:19:15 AM Pavel Šimerda <c...@simerda.eu>:
On 1/16/21 12:50 PM, Petr Štetiar wrote:
Pavel Šimerda <c...@simerda.eu> [2021-01-16 00:23:01]:
Hi,
My perspective is that we are working on *hardware enablement* here.
At
least some switch chips support Link Aggregation in addition to
hardware
switching and VLAN filtering. This will be handled by offloading the
LAG
configuration from the kernel team driver.
we're trying to keep the main tree minimal for details see following
link:
https://lists.infradead.org/pipermail/openwrt-devel/2019-August/024109.html
Hey Petr,
is this an idea in progress or is OpenWRT already heading towards that
goal?
It's an ongoing progress. If you look at the Git log multiple packages
were moved over the last weeks.
* The libteam package to support the team module (new package)
- Submitted in PATCH 2/2.
This one looks like material for packages feed.
So what is the correct approach? Please see my questions below.
1) Is it okay to modify libnl to build and distribute the libnl-cli
package so that I can base the libteam package on it?
2) How should I handle the netifd team module dependency on libteam to
get it accepted to netifd code base?
Cheers,
Pavel Šimerda
-- ynezz
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
--
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
