From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v2] ARM: LPC32xx: Ethernet driver Date: Tue, 28 Feb 2012 14:13:34 -0500 (EST) Message-ID: <20120228.141334.569125676685228205.davem@davemloft.net> References: <4F4CD1D8.8030102@antcom.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: alexander.h.duyck@intel.com, baruch@tkos.co.il, ian.campbell@citrix.com, netdev@vger.kernel.org, eilong@broadcom.com, kevin.wells@nxp.com, w.sang@pengutronix.de, jeffrey.t.kirsher@intel.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org To: stigge@antcom.de Return-path: In-Reply-To: <4F4CD1D8.8030102@antcom.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org List-Id: netdev.vger.kernel.org From: Roland Stigge Date: Tue, 28 Feb 2012 14:08:40 +0100 > For the case that it _isn't_ initialized already, is it the right thing > to use a hard coded default MAC address to be replaced by the final one > in userspace? (I found such examples in some current micrel/ and amd/ > drivers.) You use a randomized ethernet address which can subsequently be fixed up by userspace, and we have very specific interfaces to make this very easy for you. It even sets an attribute which userland can query to see that the device has a randomized ethernet address rathern than a true assigned permanent one.