[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201221170048.29821-3-hongweiz@ami.com>
Date: Mon, 21 Dec 2020 12:00:47 -0500
From: Hongwei Zhang <hongweiz@....com>
To: <linux-aspeed@...ts.ozlabs.org>, <linux-kernel@...r.kernel.org>,
<openbmc@...ts.ozlabs.org>, Jakub Kicinski <kuba@...nel.org>,
David S Miller <davem@...emloft.net>
CC: Hongwei Zhang <hongweiz@....com>, netdev <netdev@...r.kernel.org>,
Joel Stanley <joel@....id.au>, Andrew Jeffery <andrew@...id.au>
Subject: [Aspeed,ncsi-rx, v1 0/1] net: ftgmac100: Fix AST2600EVB NCSI RX issue
Hi Andrew,
> From: Andrew Jeffery <andrew@...id.au>
>
> > Fix AST2600 EVB NCSI RX timeout issue by removing
> > FTGMAC100_RXDES0_RX_ERR bit from macro RXDES0_ANY_ERROR.
>
> But why? What is wrong with the EVB that this change resolves? Which revision of the EVB?
>
> The change affects all designs using the MAC, not just the AST2600 EVB. Why is this patch an
> appropriate course of action? Can we not add a quirk targeting the specific board (e.g. a devicetree
> property)?
You are correct. I was in a rush and didn't put this patch under whole picture
of the driver it affected. I revised the cover letter with more information, also
use a configurable flag to isolate the change. please review the new approach.
>
> Andrew
>
Thanks,
--Hongwei
Powered by blists - more mailing lists