Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 11 Nov 2002 18:33:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 11 Nov 2002 18:33:24 -0500 Received: from pizda.ninka.net ([216.101.162.242]:8633 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Mon, 11 Nov 2002 18:33:23 -0500 Date: Mon, 11 Nov 2002 15:38:45 -0800 (PST) Message-Id: <20021111.153845.69968013.davem@redhat.com> To: roland@topspin.com Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] [RFC] increase MAX_ADDR_LEN From: "David S. Miller" In-Reply-To: <52r8drn0jk.fsf_-_@topspin.com> References: <20021111.151929.31543489.davem@redhat.com> <52r8drn0jk.fsf_-_@topspin.com> X-FalunGong: Information control. X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 470 Lines: 11 So how are apps able to specify such larger hw addresses to configure a driver if IFHWADDRLEN is still 6? I'm not going to increase MAX_ADDR_LEN if there is no user ABI capable of configuring such larger addresses properly. - 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/