From: Vivien Didelot
Date: Sun, 12 Jul 2015 21:39:30 -0400 (EDT)
> I hardly see how this debug interface can be made generic to other
> DSA drivers, since the format of hardware tables or some registers
> seem very specific to the switch chip.
You feel this way because you are focusing on regist
Hi David,
On Jul 11, 2015, at 10:08 PM, David da...@davemloft.net wrote:
> From: Vivien Didelot
> Date: Sat, 11 Jul 2015 14:36:12 -0400 (EDT)
>
>> In the meantime, this is really useful for development. i.e. ensuring a good
>> switchdev/DSA interaction without being able to read and write direc
From: Vivien Didelot
Date: Sat, 11 Jul 2015 14:36:12 -0400 (EDT)
> In the meantime, this is really useful for development. i.e. ensuring a good
> switchdev/DSA interaction without being able to read and write directly the
> hardware VLAN table, is a bit a PITA. A dynamic debugfs looked appropriat
Hi David,
On Jul 11, 2015, at 2:01 AM, David da...@davemloft.net wrote:
> From: Vivien Didelot
> Date: Thu, 9 Jul 2015 17:13:29 -0400
>
>> Allow write access to the regs file in the debugfs interface, with the
>> following parameters:
>>
>> echo> regs
>>
>> Where "name" is the regist
From: Vivien Didelot
Date: Thu, 9 Jul 2015 17:13:29 -0400
> Allow write access to the regs file in the debugfs interface, with the
> following parameters:
>
> echo> regs
>
> Where "name" is the register name (as shown in the header row), "reg" is
> the register address (as shown in the
Allow write access to the regs file in the debugfs interface, with the
following parameters:
echo> regs
Where "name" is the register name (as shown in the header row), "reg" is
the register address (as shown in the first column) and "value" is the
16-bit value. e.g.:
echo GLOBAL 1a 5
