From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S271298AbTG2In7 (ORCPT ); Tue, 29 Jul 2003 04:43:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S271331AbTG2In6 (ORCPT ); Tue, 29 Jul 2003 04:43:58 -0400 Received: from [203.52.228.162] ([203.52.228.162]:56585 "EHLO gateway.reflexcs.com.au") by vger.kernel.org with ESMTP id S271298AbTG2In5 (ORCPT ); Tue, 29 Jul 2003 04:43:57 -0400 Message-ID: <3F2633E6.3030205@sage-aust.com.au> Date: Tue, 29 Jul 2003 16:44:22 +0800 From: Eric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Re: [PATCH] nvidia nforce 1.0-261 nvnet for kernel 2.5 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org from various hardware source the NVNET hardware is probably this: MCP integrated NVIDIA^R MAC + Realtek^R 8201BL PHY The specs on asus and epox refer to using the nvnet on the some fo their boards, in the detailed specs you get the above detail Hope it helps I could be persuaded to do some testing if required