Hi Andrew,
On Jun 26, 2015, at 11:23 AM, Andrew Lunn and...@lunn.ch wrote:
>> >> +static int _mv88e6xxx_vtu_getnext(struct dsa_switch *ds, u16 vid,
>> >> + struct mv88e6xxx_vtu_entry *entry)
>> >> +{
>> >> +int ret, i;
>> >> +
>> >> +ret = _mv88e6xxx_vtu_wait(ds);
>> >> +
> >> +static int _mv88e6xxx_vtu_getnext(struct dsa_switch *ds, u16 vid,
> >> + struct mv88e6xxx_vtu_entry *entry)
> >> +{
> >> +int ret, i;
> >> +
> >> +ret = _mv88e6xxx_vtu_wait(ds);
> >> +if (ret < 0)
> >> +return ret;
> >> +
> >> +ret = _mv88e6xxx_reg_wri
Hi Andrew,
On Jun 26, 2015, at 10:04 AM, Andrew Lunn and...@lunn.ch wrote:
> On Tue, Jun 23, 2015 at 05:46:08PM -0400, Vivien Didelot wrote:
>> Implement the Get Next operation for the VLAN Table Unit, and a "vtu"
>> debugfs file to dump the hardware VLANs.
>>
>> A populated VTU can look like thi
On Tue, Jun 23, 2015 at 05:46:08PM -0400, Vivien Didelot wrote:
> Implement the Get Next operation for the VLAN Table Unit, and a "vtu"
> debugfs file to dump the hardware VLANs.
>
> A populated VTU can look like this:
>
> # cat /sys/kernel/debug/dsa0/vtu
> VID FID SID P0 P1 P2 P3 P4 P
Implement the Get Next operation for the VLAN Table Unit, and a "vtu"
debugfs file to dump the hardware VLANs.
A populated VTU can look like this:
# cat /sys/kernel/debug/dsa0/vtu
VID FID SID P0 P1 P2 P3 P4 P5 P6
550 562 0x x x u x t x
1000 1012 0x x t x x
