Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762275AbYA2AqY (ORCPT ); Mon, 28 Jan 2008 19:46:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754299AbYA2AqM (ORCPT ); Mon, 28 Jan 2008 19:46:12 -0500 Received: from hobbit.corpit.ru ([81.13.94.6]:23883 "EHLO hobbit.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753759AbYA2AqK (ORCPT ); Mon, 28 Jan 2008 19:46:10 -0500 Message-ID: <479E7750.9060304@msgid.tls.msk.ru> Date: Tue, 29 Jan 2008 03:46:08 +0300 From: Michael Tokarev Organization: Telecom Service, JSC User-Agent: Icedove 1.5.0.14pre (X11/20071018) MIME-Version: 1.0 To: Frederik Himpe CC: LKML , netdev@vger.kernel.org Subject: Re: Udev coldplugging loads 8139too driver instead of 8139cp References: <1201554992.13883.13.camel@Anastacia> In-Reply-To: <1201554992.13883.13.camel@Anastacia> X-Enigmail-Version: 0.94.2.0 OpenPGP: id=4F9CF57E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1716 Lines: 38 Frederik Himpe wrote: > Linux 2.6.24 kernel gives the following messages when udev coldplugging > loads the driver for my NIC: > > 8139too 0000:00:0b.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip > 8139too 0000:00:0b.0: Use the "8139cp" driver for improved performance and stability. There are 2 drivers for 8139-based NICs. For really different two kinds of hardware, which both uses the same PCI identifiers. Both drivers "claims" to work with all NICs with those PCI ids, because "externally" (by means of udev for example) it's impossible to distinguish the two kinds of hardware, it becomes clean only when the driver (either of the two) loads and actually checks which hardware we have here. Udev in fact loads both - 8139cp and 8139too. The difference is the ORDER in which it loads them - if for "cp-handled" hardware it first loads "too", too will complain as above and will NOT claim the device. The same is true for the opposite. So - in short - things has always been this way (thanks to realtec). I've seen similar (but opposite) effects on my systems, which are all should be serviced by 8139too driver but 8139cp loaded first - up till i gave up and just disabled 8139cp... I don't know what happened in 2.6.24, but my guess is that since 8139too-based hw is now alot more common, the two drivers are listed in the opposite order. In short: NotABug, or ComplainToRealtec (but that's waaaay too late and will not help anyway) ;) /mjt -- 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/