[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <99737F4847ED0A48AECC9F4A1974A4B80F82CB7A51@MNEXMB2.qlogic.org>
Date: Wed, 23 Jun 2010 06:49:18 -0500
From: Amit Salecha <amit.salecha@...gic.com>
To: Ben Hutchings <bhutchings@...arflare.com>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Ameen Rahman <ameen.rahman@...gic.com>,
Anirban Chakraborty <anirban.chakraborty@...gic.com>
Subject: RE: [PATCH] net: add dependency on fw class module
Actually that is not actually reflect to board type.
"board_type" is a encoding to find out number of physical port and phy speed.
NX3031 (netxen_nic) and QLOGIC CNA (qlcnic) device have some common board form.
But not all board types are valid for QLOGIC CNA device. We will clean this up.
Thanks for pointing this out.
-Amit
-----Original Message-----
From: Ben Hutchings [mailto:bhutchings@...arflare.com]
Sent: Wednesday, June 23, 2010 4:49 PM
To: Amit Salecha
Cc: davem@...emloft.net; netdev@...r.kernel.org; Ameen Rahman; Anirban Chakraborty
Subject: Re: [PATCH] net: add dependency on fw class module
On Tue, 2010-06-22 at 23:54 -0700, Amit Kumar Salecha wrote:
> From: Anirban Chakraborty <anirban.chakraborty@...gic.com>
>
> netxen_nic and qlcnic driver depends on firmware_class module.
[...]
By the way, I noticed that these drivers are very similar, and it looks
like qlcnic has code for a bunch of NetXen boards even though it doesn't
include their device IDs in its device ID table. Have you considered
merging the two?
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
Powered by blists - more mailing lists