Searched hist:249752 (Results 1 - 2 of 2) sorted by relevance
| /freebsd-11-stable/sbin/etherswitchcfg/ | ||
| H A D | etherswitchcfg.c | diff 249752 Mon Apr 22 03:55:17 MDT 2013 adrian 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 <loos.br@gmail.com> Reviewed by: ray |
| /freebsd-11-stable/sys/dev/etherswitch/rtl8366/ | ||
| H A D | rtl8366rb.c | diff 249752 Mon Apr 22 03:55:17 MDT 2013 adrian 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 <loos.br@gmail.com> Reviewed by: ray |
Completed in 174 milliseconds