On 17-12-05 12:21 AM, Gal Pressman wrote:
On 04-Dec-17 22:16, Scott Branden wrote:
Hi Gal,
I do not understand you're comment - questions inline
On 17-12-03 12:07 AM, Gal Pressman wrote:
On 30-Nov-17 21:24, Scott Branden wrote:
Add ETHTOOL_RESET support via --reset command.
ie. ethtool
On 04-Dec-17 22:16, Scott Branden wrote:
> Hi Gal,
>
> I do not understand you're comment - questions inline
>
>
> On 17-12-03 12:07 AM, Gal Pressman wrote:
>> On 30-Nov-17 21:24, Scott Branden wrote:
>>> Add ETHTOOL_RESET support via --reset command.
>>>
>>> ie. ethtool --reset DEVNAME
>>>
>>> f
Hi Gal,
I do not understand you're comment - questions inline
On 17-12-03 12:07 AM, Gal Pressman wrote:
On 30-Nov-17 21:24, Scott Branden wrote:
Add ETHTOOL_RESET support via --reset command.
ie. ethtool --reset DEVNAME
flagnames currently match the ETH_RESET_xxx names:
mgmt,irq,dma,filte
On 30-Nov-17 21:24, Scott Branden wrote:
> Add ETHTOOL_RESET support via --reset command.
>
> ie. ethtool --reset DEVNAME
>
> flagnames currently match the ETH_RESET_xxx names:
> mgmt,irq,dma,filter,offload,mac,phy,ram,dedicated,all
>
> Alternatively, you can specific component bitfield directly
Add ETHTOOL_RESET support via --reset command.
ie. ethtool --reset DEVNAME
flagnames currently match the ETH_RESET_xxx names:
mgmt,irq,dma,filter,offload,mac,phy,ram,dedicated,all
Alternatively, you can specific component bitfield directly using
ethtool --reset DEVNAME flags %x
Signed-off-by: