From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760654AbZE0UzS (ORCPT ); Wed, 27 May 2009 16:55:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759071AbZE0UzD (ORCPT ); Wed, 27 May 2009 16:55:03 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:40865 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754941AbZE0UzA (ORCPT ); Wed, 27 May 2009 16:55:00 -0400 Date: Wed, 27 May 2009 13:55:00 -0700 (PDT) Message-Id: <20090527.135500.217447785.davem@davemloft.net> To: timur@freescale.com Cc: scottwood@freescale.com, rmk+lkml@arm.linux.org.uk, jacmet@sunsite.dk, r.schwebel@pengutronix.de, devicetree-discuss@ozlabs.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk, yuan-bo.ye@motorola.com Subject: Re: [RFC] [PATCH] Device Tree on ARM platform From: David Miller In-Reply-To: <4A1DA24D.5000101@freescale.com> References: <4A1D9A66.5020002@freescale.com> <20090527.132553.40558501.davem@davemloft.net> <4A1DA24D.5000101@freescale.com> X-Mailer: Mew version 6.2.51 on Emacs 22.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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Timur Tabi Date: Wed, 27 May 2009 15:27:57 -0500 > I asked what do drivers do when the MAC address is not in the OF > tree, and it is not programmed in hardware (any hardware). They either fail to probe the device or use a random MAC address, the later of which is severely frowned upon. From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [RFC] [PATCH] Device Tree on ARM platform Date: Wed, 27 May 2009 13:55:00 -0700 (PDT) Message-ID: <20090527.135500.217447785.davem@davemloft.net> References: <4A1D9A66.5020002@freescale.com> <20090527.132553.40558501.davem@davemloft.net> <4A1DA24D.5000101@freescale.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4A1DA24D.5000101-KZfg59tc24xl57MIdRCFDg@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org To: timur-KZfg59tc24xl57MIdRCFDg@public.gmane.org Cc: rmk+lkml-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org, devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org, yuan-bo.ye-3WKxDLwmzFNWk0Htik3J/w@public.gmane.org, linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org List-Id: devicetree@vger.kernel.org From: Timur Tabi Date: Wed, 27 May 2009 15:27:57 -0500 > I asked what do drivers do when the MAC address is not in the OF > tree, and it is not programmed in hardware (any hardware). They either fail to probe the device or use a random MAC address, the later of which is severely frowned upon.