From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by ozlabs.org (Postfix) with ESMTP id 484A6DDF8C for ; Wed, 4 Mar 2009 02:23:39 +1100 (EST) Received: by yw-out-2324.google.com with SMTP id 5so1537289ywb.39 for ; Tue, 03 Mar 2009 07:23:37 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <3B1D47A2-329E-491E-B3AC-E76C1CE1762D@it-loops.com> <9d38520266f15d80352d1554e63c1ce6@localhost> Date: Tue, 3 Mar 2009 08:23:37 -0700 Message-ID: Subject: Re: PHY not found after migration of gianfar driver to an of_platform_driver From: Grant Likely To: Michael Guntsche Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-dev List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Mar 3, 2009 at 2:49 AM, Michael Guntsche wrote: > On Tue, 03 Mar 2009 08:35:02 +0100, Michael Guntsche > wrote: >> As for adding additional information to the tree, can I also use libfdt >> functions in platform/83xx/rbppc.c or is it better to do this via a >> dedicated platform_init that simpleboot then uses? I'd do this in the bootwrapper. I think it is easier to follow and understand that way. > Sorry, please forget this quesiton. Of course simpleboot only reads the > embedded tree > so if I change the tree there it is the same as changing the initial DTS > file. > I will try to boot with a standard vmlinux image and then add the values in > rbppc.c. Okay, that makes more sense. So, now if you want a common wrapper image to boot on all of the routerboard variants, then you need to pull all the tricks you have out of your hat to figure out what board it is running on so that the .dtb can be updated. Is there an eeprom or something on the board which might store serial numbers or MAC addresses? g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.