Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263662AbUJ3JvK (ORCPT ); Sat, 30 Oct 2004 05:51:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263667AbUJ3JvK (ORCPT ); Sat, 30 Oct 2004 05:51:10 -0400 Received: from courier.cs.helsinki.fi ([128.214.9.1]:49901 "EHLO mail.cs.helsinki.fi") by vger.kernel.org with ESMTP id S263662AbUJ3JvF (ORCPT ); Sat, 30 Oct 2004 05:51:05 -0400 Subject: Re: net: generic netdev_ioaddr From: Pekka Enberg To: Krzysztof Halasa Cc: Al Viro , davem@davemloft.net, netdev@oss.sgi.com, linux-kernel@vger.kernel.org In-Reply-To: References: <1099044244.9566.0.camel@localhost> <20041029131607.GU24336@parcelfarce.linux.theplanet.co.uk> <20041029193827.GV24336@parcelfarce.linux.theplanet.co.uk> Date: Sat, 30 Oct 2004 12:52:26 +0300 Message-Id: <1099129946.10961.9.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Evolution 2.0.2 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1107 Lines: 31 Hi, Al Viro writes: > > What uses ->base_addr from the data returned by SIOCGIFMAP? On Fri, 2004-10-29 at 23:13 +0200, Krzysztof Halasa wrote: > > ifconfig I think: [snip] > With this driver it happens to be MMIO address. > > I understand presenting this value to users might have some value: > it can help determine the physical port/card for a given netdev. > But it should be something like a description text set by the driver > (ie. containing PCI bus/device, or even ISA address for ISA non-PnP > card, possibly with other information). It seems that the user can also setup dev->base_addr with "netdev=" kernel parameter before a driver starts probing (for example drivers/net/appletalk/cops.c). Should we get rid of "netdev=" too and push preconfiguring down to the drivers that actually use it? Pekka - 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/