[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AA14CBE.8000402@nvidia.com>
Date: Fri, 04 Sep 2009 13:22:06 -0400
From: Ayaz Abdulla <aabdulla@...dia.com>
To: David Miller <davem@...emloft.net>
CC: "manfred@...orfullife.com" <manfred@...orfullife.com>,
"akpm@...l.org" <akpm@...l.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] forcedeth: updated phy errata
David Miller wrote:
> From: Ayaz Abdulla <aabdulla@...dia.com>
> Date: Fri, 04 Sep 2009 09:57:59 -0400
>
>
>>Unfortunately, the phy vendors don't want us exposing the meaning of
>>their non-standard bits.
>
>
> So when you go away and some other developer tries to debug a problem
> in this area, then what happens? Do they just guess what those bits
> mean?
I understand your concern. However, NVIDIA will always be the maintainer
for these phy erratas and work with users to solve any issues. We have
access to the confidential documents provided by the vendors.
Phy vendors have said "No" in the past. I can request for 'opening up'
the bits again, but not all vendors will comply - resulting in no
support for forcedeth. This is currently the only way to provide a good
experience for the end user.
>
> Sorry, this sort of situation is unacceptable in this modern day and
> age. You'll need to work this out before I'm willing to take the
> patch.
--
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