|
Revision tags: release/13.4.0-p5, release/13.5.0-p1, release/14.2.0-p3, release/13.5.0, release/14.2.0-p2, release/14.1.0-p8, release/13.4.0-p4, release/14.1.0-p7, release/14.2.0-p1, release/13.4.0-p3, release/14.2.0, release/13.4.0, release/14.1.0, release/13.3.0, release/14.0.0 |
|
| #
2ff63af9 |
| 16-Aug-2023 |
Warner Losh <[email protected]> |
sys: Remove $FreeBSD$: one-line .h pattern
Remove /^\s*\*+\s*\$FreeBSD\$.*$\n/
|
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0 |
|
| #
829a13fa |
| 09-May-2022 |
John Baldwin <[email protected]> |
Remove unused etherswitch_devclass.
|
|
Revision tags: release/12.3.0 |
|
| #
f5b29d0f |
| 23-Jun-2021 |
Kornel Duleba <[email protected]> |
etherswitch: Add a new striptagingress port flag
Felix switch found in LS1028A supports stripping VLAN tag on ingress, instead of egress. The striptag flag excepts the latter behaviour. Add a new fl
etherswitch: Add a new striptagingress port flag
Felix switch found in LS1028A supports stripping VLAN tag on ingress, instead of egress. The striptag flag excepts the latter behaviour. Add a new flag to support the feature.
Obtained from: Semihalf Sponsored by: Alstom Group Differential Revision: https://reviews.freebsd.org/D30922
show more ...
|
|
Revision tags: release/13.0.0, release/12.2.0, release/11.4.0 |
|
| #
c8645751 |
| 08-May-2020 |
Adrian Chadd <[email protected]> |
[etherswitch] bump register width to 32 bits.
Some ethernet switches have very large register windows; for example the AR8316 switch MIB starts at 0x20000.
Submitted by: Mori Hiroki <yamori813@yaho
[etherswitch] bump register width to 32 bits.
Some ethernet switches have very large register windows; for example the AR8316 switch MIB starts at 0x20000.
Submitted by: Mori Hiroki <[email protected]>
show more ...
|
|
Revision tags: release/12.1.0, release/11.3.0 |
|
| #
4e4cedb0 |
| 28-Jun-2019 |
Luiz Otavio O Souza <[email protected]> |
Add the 'drop tagged' flag support for ethernet switch ports.
This is intended to drop all 802.1q tagged packets on a port.
Sponsored by: Rubicon Communications, LLC (Netgate)
|
|
Revision tags: release/12.0.0, release/11.2.0 |
|
| #
15bd1a86 |
| 06-Feb-2018 |
Adrian Chadd <[email protected]> |
[etherswitch] add initial support for potentially configuring and fetching the switch MAC address.
Switches that originate their own frames (eg obvious ones like Pause frames) need a MAC address to
[etherswitch] add initial support for potentially configuring and fetching the switch MAC address.
Switches that originate their own frames (eg obvious ones like Pause frames) need a MAC address to use to send those frames from.
This API will hopefully begin to allow that to be configurable.
show more ...
|
| #
877d73ec |
| 02-Feb-2018 |
Adrian Chadd <[email protected]> |
[etherswitch] add the first pass of a simple API to flush and fetch the L2 address table from the ethernet switch.
This stuff may be a bit fluid during this -HEAD cycle as various other switch featu
[etherswitch] add the first pass of a simple API to flush and fetch the L2 address table from the ethernet switch.
This stuff may be a bit fluid during this -HEAD cycle as various other switch features are added, but the current stuff is enough to drive initial development and features on the atheros range of integrated and external switches.
* add a method to flush the whole address table; * add a method to flush all addresses on a given port; * add a method to download the address table; * .. and then a method to fetch entries from the address table.
The table fetch/read methods pass through to the drivers for now since the drivers may implement different ways of fetching/caching the address table data. The atheros devices for example fetch the table by iterating over the table through a set of registers and so you need to keep that locked whilst you iterate otherwise you may have the table flushed half way by a port status change.
This is a no-op until the userland and arswitch code shows up.
show more ...
|
|
Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0 |
|
| #
c94dc808 |
| 04-Aug-2016 |
Adrian Chadd <[email protected]> |
[etherswitch] add in an initial API for controlling per-port LED behaviour.
This is just implemented for the AR8327 for now.
Submitted by: Dan Nelson <[email protected]>
|
|
Revision tags: release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0 |
|
| #
cc320e37 |
| 23-Jul-2013 |
Luiz Otavio O Souza <[email protected]> |
Add a new flag (ETHERSWITCH_VID_VALID) to say what vlangroups are in use. This fix the case when etherswitch is printing the information of port 0 vlan group (in port based vlan mode) with no member
Add a new flag (ETHERSWITCH_VID_VALID) to say what vlangroups are in use. This fix the case when etherswitch is printing the information of port 0 vlan group (in port based vlan mode) with no member ports.
Add the ETHERSWITCH_VID_VALID support to ip17x driver.
Add the ETHERSWITCH_VID_VALID support to rt8366 driver.
arswitch doesn't need to be updated as it doesn't support vlans management yet.
Approved by: adrian (mentor)
show more ...
|
|
Revision tags: release/8.4.0 |
|
| #
a48a9355 |
| 08-May-2013 |
Adrian Chadd <[email protected]> |
Add the ability to change the vlan operation mode.
This adds a vlan capability field to etherswitch_info structure and some definitions of ports flags.
It adds the support to global config paramete
Add the ability to change the vlan operation mode.
This adds a vlan capability field to etherswitch_info structure and some definitions of ports flags.
It adds the support to global config parameters which right now is used only to switch between the vlan modes, but it is intended to be extended to support the setup of others parameters (STP, mirror, etc.).
Submitted by: Luiz Otavio O Souza <[email protected]> Reviewed by: ray
show more ...
|
| #
a3219359 |
| 22-Apr-2013 |
Adrian Chadd <[email protected]> |
Convert over the etherswitch framework to use VLAN IDs per port, rather than VLAN groups.
Some chips (eg this rtl8366rb) has a VLAN group per port - you first define a set of VLANs in a vlan group,
Convert over the etherswitch framework to use VLAN IDs per port, rather than VLAN groups.
Some chips (eg this rtl8366rb) has a VLAN group per port - you first define a set of VLANs in a vlan group, then you assign a VLAN group to a port.
Other chips (eg the AR8xxx switch chips) have a VLAN ID array per port - there's no group per se, just a list of vlans that can be configured.
So for now, the switch API will use the latter and rely on drivers doing the heavy lifting if one wishes to use the VLAN group method. Maybe later on both can be supported.
PR: kern/177878 PR: kern/177873 Submitted by: Luiz Otavio O Souza <[email protected]> Reviewed by: ray
show more ...
|
|
Revision tags: release/9.1.0 |
|
| #
a043e8c7 |
| 11-May-2012 |
Adrian Chadd <[email protected]> |
Commit the first pass of the etherswitch support.
This is designed to support the very basic ethernet switch chip behaviour, specifically:
* accessing switch register space; * accessing per-PHY reg
Commit the first pass of the etherswitch support.
This is designed to support the very basic ethernet switch chip behaviour, specifically:
* accessing switch register space; * accessing per-PHY registers (for switches that actually expose PHYs); * basic vlan group support, which applies for the rtl8366 driver but not for the atheros switches.
This also includes initial support for:
* rtl8366rb support - which is a 10/100/1000 switch which supports vlan groups; * Initial Atheros AR8316 switch support - which is a 10/100/1000 switch which supports an alternate vlan configuration (so the vlan group methods are stubbed.)
The general idea here is that the switch driver may speak to a variety of backend busses (mdio, i2c, spi, whatever) and expose:
* If applicable, one or more MDIO busses which ethernet interfaces can then attach PHYs to via miiproxy/mdioproxy;
* exposes miibusses, one for each port at the moment, so ..
* .. a PHY can be exposed on each miibus, for each switch port, with all of the existing MII/ifnet framework.
However:
* The ifnet is manually created for now, and it isn't linked into the interface list, nor can you (currently) send/receive frames on this ifnet. At some point in the future there may be _some_ support for this, for switches with a multi-port, isolated mode.
* I'm still in the process of sorting out correct(er) locking.
TODO:
* ray's switch code in zrouter (zrouter.org) includes a much more developed newbus API that covers the various switch methods, as well as a capability API so drivers, the switch layer and the userland utility can properly control the subset of supported features.
The plan is to sort that out later, once the rest of ray's switch drivers are brought over and extended to export MII busses and PHYs.
Submitted by: Stefan Bethke <[email protected]> Reviewed by: ray
show more ...
|