Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 24 Oct 2002 20:15:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 24 Oct 2002 20:15:06 -0400 Received: from petasus.ch.intel.com ([143.182.124.5]:9811 "EHLO petasus.ch.intel.com") by vger.kernel.org with ESMTP id ; Thu, 24 Oct 2002 20:15:04 -0400 Message-ID: From: "Leech, Christopher" To: "'Jeff Garzik'" , "H. J. Lu" Cc: linux kernel Subject: RE: PCI device order problem Date: Thu, 24 Oct 2002 17:21:10 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1339 Lines: 35 I've heard some grumbling about this with specific motherboards and 82546 LOMs. While I understand what's happening, and that using nameif to manage this is the correct answer, I am a bit surprised that function 1 would be placed on the global PCI device list before function 0 for a multi-function device. -- Chris Leech > >>Without answering your specific question, but addressing $subject, > >>what > >>problem is caused by the PCI device order you see? > >> > >> > > > >It is different from the hardware documentation. The hardware manual > >says it has 2 NICs, NIC 1 (03:07.0) and NIC2 (03:07.1), which makes > >senses to me. NIC 1 is a special one which supports IPMI over LAN. > >Since we only use one NIC now, we'd like to use NIC 1 and > call it eth0. > > > > > > Well, overall, depending on ordering is error-prone (as you see). I > would suggest migrating to a less-fragile scheme. nameif and ethtool > together should get you exactly the device you need... > (though I wonder > why simply using eth1 is so awful, if this situation is constant...) > > Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/