[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <157393863283F442885425D2C45428562A4F5169@nasanexd02f.na.qualcomm.com>
Date: Thu, 23 Aug 2012 06:35:40 +0000
From: "Huang, Xiong" <xiong@....qualcomm.com>
To: David Miller <davem@...emloft.net>,
"Ren, Cloud" <cjren@....qualcomm.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
qca-linux-team <qca-linux-team@...lcomm.com>,
nic-devel <nic-devel@...lcomm.com>,
"Rodriguez, Luis" <rodrigue@....qualcomm.com>
Subject: RE: [PATCH v2] net: add new QCA alx ethernet driver
> This is why we require that portable, sane, interfaces are added to ethtool for
> driver diagnostics. That way users can perform a task in the same way
> regardless of what hardware and driver are underneath.
I quite agree you on using ethtool to implement it. we did consider it.
But ethtool has some limitation, for example, the NIC has built-in OTP (TWSI interface)
And Flash (External SPI interface), their properties are quite different with EEPROM which
Ethtool supports.
To support such memory (OTP/Flash), we need additional input parameters.
Same situation exists in diagnostic utility. Ethtool only provide two options : offline & online
That's too gross to locate which part/module of the chip is malfunction. we also need
more options to detect it.
that's why we finally selected a custom debugfs interface.
Thanks
Xiong
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists